I can't seem to let this one go. On Wed, 27 Mar 2013 07:37:44 -0500, John Gilmore wrote: > >in which parm, like all strings declared to be varying, is here a >character string prefixed by a current-length signed-halfword value, >0 <= L <= 32767. > The modal opinion here is that the number should be 32760, not 32767.
It has been patiently explained to me here that STORAGE OBTAIN is biased toward doubleword multiples. But PARM contains a halfword length that doesn't count itself. So I'd expect the limit to be either 32758 (8*4095-2) or 32766 (8*4096-2). Again, why 32760? "signed-halfword value". Does your PL/I program verify the lower bound of 0? I can readily generate negative values with an assembler program or more easily with Rexx "attach LINKPGM". Easier to declare it an (unsigned short) and validate with a single compare. Continuing Ed G.'s line of thought: If he expects the interface to a program invoked with EXEC PARMDD= to be different from that to a program invoked with EXEC PARM=, does he in turn expect the CALL, LINK, ATTACH, and XCTL macros to be enhanced to support that new interface? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
