RE: Sub-Procedures (Follow-up Question)

When passing parms between programs, we typically pass them as character

types ... and how they receive and parse the parms.

Do I need to be concerned with this ... its internal parameter

validation handle this automatically?

Short answer - No.

Longer answer - you should not perpetuate what is a fundamentally wrong
system (passing everything as char) into subprocedures. Subprocs can (by
virtue of prototype keywords such as CONST) deal with some issues of
mis-matched types/sizes - but those same principals can also be applied to
program calls by using prototyping and using CALLP to replace CALL/PARM.
The RPG Redbook you mentioned earlier covers this too and there are many
articles on the web on the topic.

There is only one "nuance" in program parameter passing normally and that is
to realize that if a program is called from the command line that numeric
parms are 15,5 packed - I won't go into the rest of it here - it is well
covered in the FAQ. Quite why some shops adopt the char method of passing
parms and the resulting error prone code that goes with it is a mystery to
me.

Jon Paris
Partner400

www.Partner400.com