On Sun, 11 Jun 2017 08:07:47 -0500, Kirk Wolf wrote:
>FYI, here's a table that compares features of BPXBATCH, BPXBATSL, AOPBATCH
> (and COZBATCH).
>
>https://dovetail.com/products/cozbatch.html
>
Hmmm ... For BPXBATCH:
"PARM= args support quoting"
o For "PARM='SH ''string''', I see no restrictions on the string that can be
passed to sh. The programmer must simply play games with doubling
apostrophes and ampersands. Backslash is passed to sh intact.
o For "PARM='PGM tokens'", BPXBATCH breaks the PARM into tokens at
blanks but does not treat TAB (0x05) or semicolon as a token separator.
A programmer can sometimes exploit this behavior. e.g.:
EXEC PGM=BPXBATCH PARM='/bin/sh -c /bin/echo<TAB>Hello.;/bin/date'
"The size of the entire PARM field is limited to 100 characters."
That's only a JCL restriction.
o From Rexx I have successfully passed BPXBATCH a PARM
65535 characters long.
o PARMDD allows PARM of 32760 bytes. I haven't tried this with BPXBATCH.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
