Re: Reading QMHRCVPM data returned

Bruce,

Of course - that all makes perfect sense. I know (as do we all) about IBM's
Q* naming convention - I didn't know you had the A to I as well!

The only other thing that puzzled me is that you had to actually name all
the reserved fields as well - couldn't you have just not named them, rather
than use QSRVnnnnnn (or whatever it is). Actually, I can't remember whether
you can have unnamed subfields in RPG/400.....

Rory

On 5/18/07, Bruce Vining <bvining@xxxxxxxxxx> wrote:

All of the RPG generated names currently start with Q and a component
identifier (such as MH for message handler). It may surprise you, but
there are IBM standards in naming conventions to try and make sure IBM
generated names do not collide with names that a customer might use. If I
recall correctly the name space A to I (might be J) is IBMs with a special
exemption of Q for System i (and S/38 before that). As unlikely as it may
seem, generating a name RCVM0200 might have collided with a user variable
name in your program. By always prefixing the names with a Q we avoided
name space collisions.

You may notice that the names also avoid the use of vowels. This is be
avoid generating "interesting" "nasty" words :) I'm sure if I looked at
the code I could also pull out a few other things we're doing, but this is
what comes immediately to mind.

The naming that is currently in use really did have some thought put into
it :) The generated names aren't "great", but hopefully they do a half
decent job. For truely poor naming check out the OPM RPG names -- try
name uniqueness in 6 characters or less!

Bruce Vining