From:
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=877&letternum=ENUSZP13-0013
o Support for passing parameter lists up to 32,760 bytes in length
to a program from JCL. A new PARMDD DD statement keyword is ...
??? A keyword on the DD statement? How will that work? I might more
easily understand a keyword on the EXEC statement. Will whatever DD
statement in the job step that asserts PARMDD be taken as the PARM for
the step?
... planned to allow more than 100 characters to be passed to any
program in JCL. A new LONGPARM binder attribute is planned to
enable APF-authorized programs to use this new function. ...
(Often discussed here as a security requirement.) A binder attribute
seems a much more orderly way to control it than YA PARMLIB member.
... No changes are planned to be needed for unauthorized programs.
This new support is intended to make it easier to pass a large
number of parameters to a program without writing intermediate
programs.
When long PARMS have been discussed here previously, the reactionaries
and IBM loyalists have objected, "Oh, no! We can't have that! Suddenly
programs that clearly failed on JCL errors will instead program check
on buffer overruns and our help desk bandwidth will be strained."
Well, if they're true IBM loyalists, now that IBM is blessing it they'll
welcome it. How will the more skeptical customers react?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
