On Sun, 5 Dec 2021 10:05:22 -0400, Peter Relson wrote:
> ...
>Maybe BPXBATCH and SH do not process the parameter string as you are
>thinking/expecting they do.
>
>I have no idea what the BPXBATCH rule is for passing parameter data
>supplied on a SH statement. I think you have subsequently concluded that
>
The UNIX System Services Command Ref. makes this pretty clear:
BPXBATCH
Parameters
...
SH
Instructs BPXBATCH to start the shell and to run shell commands or scripts
provided from stdin or the specified program_name. BPXBATCH passes all
of the argument data, blanks included as is, to the shell as one parameter.
BPXBATCH PARM='SH command string'
...
If you specify SH with no program_name information, BPXBATCH attempts
to run anything read in from stdin.
(The first paragraph is awkward, even misleading in thee use of "specified
program_name". Should I submit an RCF to change it to:
SH
Instructs BPXBATCH to start the shell, passing it the entire remainder of
the argument data, blanks included as is, to the "sh -c" as one parameter.
?
That's the behavior I've experienced.)
May we assume without further explanation that's the PARM in "equivalent
JCL", described in the JCL Ref.?
>your problem is not with how the parameter string itself is presented to
>the BPXBATCH program, but further downstream. A bug in BPXBATCH
>processing (and/or a doc problem), is worth reporting.
>
Max MSGLEVEL should clarify sufficiently.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
