On Thu, 30 Nov 2017 18:40:01 -0800, Ed Jaffe wrote: >On 11/30/2017 4:32 PM, Charles Mills wrote: >> Thanks. >> >> Got it. In order for a program to be passed > 100 bytes from // EXEC it must >> be either not authorized or linked with LONGPARM (or both). >> >> Am I right on bullet one? Parms greater than 100 bytes are a PARMDD thing >> only, never a PARM= thing? > >You can *never* pass more than 100 bytes via PARM=. If you want a longer >parameter, you *must* use PARMDD. > >The interface as seen by the program is the same in both cases: halfword >length followed by data. > What about the ATTACH, XCTL, LINK, and LOAD/CALL macros. Prior to the innovation of the LONGPARM attribute it was the responsibility of either the parent or child task (not clearly documented which?) to verify PARM length. Do these nowadays respect the NOLONGPARM setting?
A defensively coded subroutine should *always* validate its arguments. It seems OS/360 developers were unaware of this. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
