I would assume the issue is that the code in MSI and NIP that reads the parmlib members doesn't have support for expansion of buffers, recall that PARMLIB is limited to 80 byte records, and if symbol substitution results in IPL failure, you have a major problem.
=============================================== Wayne Driscoll Omegamon DB2 L3 Support/Development wdrisco(AT)us.ibm.com =============================================== Paul Gilmartin <[email protected]> Sent by: IBM Mainframe Discussion List <[email protected]> 02/27/2009 09:05 AM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject Re: SYMDEF length limitations On Fri, 27 Feb 2009 09:28:02 -0500, Scott Rowe wrote: >Don't think JCL, think PARMLIB. > Think... PARMLIB... Think... OK. I have thought PARMLIB. What came to my mind was that the substitution techniques used in JCL processing to substitute a symbol value longer than that symbol's name ought to work equally well if employed in PARMLIB processing. >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Itschak Mugzach >Subject: Re: SYMDEF length limitations > >I RTFMed before asking, but it looked strange to me that the length of the >variable value is forced by the length of the variable name... -- gil ---------------------------------------------------------------------- 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
