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
Custom routines which are maintained by you should take the prefix
We ask that the unique code incorporates your organization's name in some way because this helps us to support your Deltanji implementation.
%vcmyDunMif101 - A custom routine maintained by George James Software for Dunder Mifflin's Deltanji
%vcmzStark666 - A custom routine for Stark Industries' Deltanji implementation, a routine that
Custom component drivers have different naming constraints, documented here.
See Also: Callouts