The other thing I don't understand is NUMBERED objects. What the hell
is program XYZ9934? Sure, you can wrote-learn what the common ones do
but we have an object-based system. Give things proper names! Decent
abbreviation standards can give meaningful names for most objects.
Variations on logical files or reports may need a numeric suffix but
surely these are the exception.
I use a standard where service programs are given names like XVERRH,
XVIFSX, etc but regular programs are given either a two or three
character value for the subsystem (IM, ITM, MRP PI, etc) and a three or
four digit number in sequence.
My reason for doing this how do you explain what a program does in 4
characters and more to the point, try to remember alphabet soup.
I learned from years of supporting users that people very quickly would
remember IM0001 or AR0099 but would never remember IMPARR. Someone calls
you up and starts feeding you a program name. The longer the name, the
worse it is. Gets to be a real pain but IM0001 is easy to say and easy
to remember. "You know my AR 99 report".
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact