RE: Parameters Stepping on each other

rpg400-l-request@xxxxxxxxxxxx wrote:

  1. RE: Parameters Stepping on each other (Fleming, Greg (ED))

I'm not sure if you intended your question to imply a qualitative
distinction by referring to the *CMD option as a (or "the") remedy, and
all other options as "workarounds". It seems to me like all options here
are workarounds, including the *CMD option, as they are all trying to
get around the fact that CL programs can't accurately pass parms greater
than 32 bytes. 

Greg:

It isn't CL programs it's the SBMJOB CMD() parameter being used to submit a 
CALL command. It's irrelevant what language is used to execute SBMJOB. The 
CMD() parameter was added to the SBMJOB command to make it easier to prompt a 
SBMJOB command in a command-line environment. In a compiled program, the CMD() 
parm may be inappropriate.

A *CMD object eliminates the use of a submitted CALL command when you want to 
use the CMD() parm regardless of the environment. The *CMD carries the 
parameter definitions along with it when the control is passed out of one job 
into another separate submitted job.

Tom Liotta