Sorry if I wasn't clear. I meant that an LE option could be used to control whether a user batch program would see > 100 character parms. I'm suggesting that z/OS itself be extended to support > 100 character PARMS (somehow), but that an LE option would control whether a user program would ever see > 100 characters.
something like: JCLLONGPARM(option) where option = - TRIM (to 100 characters if too long) - ALLOW - DISALLOW (abends the job step if a PARM > 100 is used) IMO, the advantage of using an LE option to control a user program's visibility to the extension is that you can control it at an installation setting, as a jobstep setting or as a program setting using the capabilities of LE options. Kirk Wolf Dovetailed Technologies http://dovetail.com On Wed, Sep 23, 2009 at 11:55 AM, Ted MacNEIL <eamacn...@yahoo.ca> wrote: > >Sorry if this was already suggested, but how about a Language Environment > option that would enable/allow >100 parm values in JCL? > > Considering the limit is enforced by JES, the SWA, the convertor, and the > interpreter, LE wouldn't stand a chance. > The limit is there before LE sees it. > > - > Too busy driving to stop for gas! > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
