Adrian, I agree with you regarding the 32K, but after reading some posting it seems people asking for "unlimited" parms. I also would like to see some improvements in this area but everything beside 256 is a nightmare for me.
Of course LE runtime overriding is an issue with some user PARM. Perhaps LE should avoid using the PARM statement for those overrides. However, I believe everything beside 256 is strange to code in a JCL regardless of the mapping. I know BPXBATCH might be a big issue but AOPBATCH introduce a nice workaround. I believe Peter Relson receive a lot of input and will be able to find a common solution. Regard Roland -----Urspr�ngliche Nachricht----- Von: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag von Adrian H Auer-Hudson Gesendet: Samstag, 14. Mai 2005 01:25 An: [email protected] Betreff: Re: PARM= --- "Schiradin,Roland HG-Dir itb-db/dc" <[EMAIL PROTECTED]> wrote: From: "Schiradin,Roland HG-Dir itb-db/dc" <[EMAIL PROTECTED]> Date: Sat, 14 May 2005 00:59:54 +0200 To: [email protected] Subject: Re: PARM= All of our Cobol programs using the PARM will fail if the parm length exceed 32767 Linkage section. 01 OsParms. 05 OsParms-Length pic s9(4) comp. 05 OsParms-Data. 10 OsParms-CicsId. 15 OsParm-CicsId-1-5 pic x(5). 15 pic x(3). 10 pic x. 10 OsParms-Program pic x(8). 10 pic x. 10 OsParms-Quiet pic x(5). 88 No-Output value 'QUIET'. Procedure Division using OsParms. However it might be a nightmare to code the correct mapping for 32767 bytes in the JCL regardless of PARMX or DDNAMES Roland My habit has always been to comma delimit the elements of the PARM. I move the parm into working storage and unstring all but the first two bytes for the length held in said two bytes. It would be great to remove the 100 byte limitation. My initial thought was to go for the max addressable by 16 bits. However, I think it would be better to remain consistent with the length available when a sub program is called be another program. I have written programs designed for execution from a JCL exec, or, invocation by a calling program. We all know that it is unlikely any one would ever code a PARM on an exec with 32767 bytes of data. But to impose a shorter length is unnecessarily arbitrary. Have a great weekend Adrian. Webmaster, <http://www.losangelesmetro.net>. Supporter of "Expo Light Rail - Enabler for the Digital Coast" <http://www.friends4expo.org>. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
