Passing parameters

[B.Morris]

Phil, by putting quotes around the whole CMD string, you're preventing the calling CL from replacing the parameters. You have to build up the command string. If I recall correctly, SBMRMTCMD doesn't like you to put expressions, so you'll need a temporary variable to build the command into: DCL &CMD TYPE(*CHAR) LEN(3000) ... chgvar &CMD 'CALL OP_PASS2 PARM(' + *CAT &PWD1 + *CAT &PWD2 + *CAT &PWD3 + *CAT &RTNMSG + *CAT &CORPSYS + *CAT ')' sbmrmtcmd CMD(&CMD) ... If any of the parameters might have more than one word (&RTNMSG?), you might need to add quotes, too: DCL &QUOTE TYPE(*CHAR) LEN(1) VALUE('''') ... chgvar &CMD 'CALL OP_PASS2 PARM(' + *CAT &PWD1 + *CAT &PWD2 + *CAT &PWD3 + *CAT &QUOTE *CAT &RTNMSG *CAT QUOTE + *CAT &CORPSYS + *CAT ')'

[Guest.Visitor]

Hello, I have a set of CL programs to change QSYSOPR passwords on over 300 remote AS/400. The two CL programs I run on the corporate system read the password from a display screen, runs a query against a file and submit a job to batch. This is where I have the problem passing the parameters. The job the CL submits to batch is the SBMRMTCMD to call the CL at the remote systems and passes the parameters. The remote CL does not like the parameters. Is there a place to get info on how to pass parameters within the SBMRMTCMD command? Any help is appreciated. The CL are copied to

op_pass.TXT

[Guest.Visitor]

I would like to know why you add 2 quotes because me I need only one quote before my parameter and one quote after my parameter. My results must be : call REPAGEC parm('password1' 'password2') but with your solution it's give me: parm (''password1''''password2'') Thanks to give me explication.