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.
Prefixes
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
Suffixes
We ask that the unique code incorporates your organization's name in some way because this helps us to support your VC/m implementation.
For Example...
%vcmyDunMif101
- A custom routine maintained by George James Software for Dunder Mifflin's VC/m
implementation.
%vcmzStark666
- A custom routine for Stark Industries' VC/m implementation, a routine that they
maintain.
See Also: Callouts