RE: passing Call commands (with parms) from program to program

Bob,

If I take the contents of the variable containing the SBMJOB command and run it outside of a QCMDEXC command (read - interactively) then the submit will "take".

If I add another pair of quotes to the 7100109958, I get the variable's name cat'ed in rather than the variable's contents.

It seems that no matter how I configure the quote marks, the submission fails to translate concatenated string correctly. I'm sure that I'm not seeing something obvious.

steve

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche
Sent: Wednesday, October 20, 2010 8:57 AM
To: Midrange Systems Technical Discussion
Subject: RE: passing Call commands (with parms) from program to program

Have you tried looking at how your sbmjob is formed?

'SBMJOB cmd(call Program_Y ('PROGRAM_B ' '39' 'CALL PGM(PROGRAM_B)
PARM('7100109958')')) JOB(PROGRAM_B) JOBD(*USRPRF) JOBQ(*JOBD) JOBPTY(3)
HOLD(*JOBD)'

Your cmd breaks down into
call Program_Y
The parm list for program_Y is:
'PROGRAM_B '
'39'
'CALL PGM(PROGRAM_B) PARM('
7100109958
')'
)
If you look at it this way and read the error, it doesn't like the 7 from
the 7100109958 part of your parms. You need to handle the quotes in your
parm string differently. as single quotes they aren't the quote character,
they are acting as the quote delimiter to a character parm.