Routine Naming Conventions

Custom routines should be named in the following way: they should include a prefix that determines who maintains the routine, and a suffix that identifies your organization and the routine.


Custom routines which are maintained by us, George James Software, should take the prefix %vcmy

Custom routines which are maintained by you should take the prefix%vcmz


We ask that the unique code incorporates your organization's name in some way because this helps us to support your Deltanji implementation.

For Example...

%vcmyDunMif101 - A custom routine maintained by George James Software for Dunder Mifflin's Deltanji implementation.

%vcmzStark666 - A custom routine for Stark Industries' Deltanji implementation, a routine that they maintain.

Component Drivers

Custom component drivers have different naming constraints, documented here.

See Also: Callouts