Yes, it is a strange restriction. My question came from my try to build a customization tool for our product that uses SYDEFS, instead of parmlib. I'll have to cut the dsname into pieces. The idea was to point to a parmlib of load library by do the customization outside the product.
Itschak On Thu, Feb 26, 2009 at 11:16 PM, Ted MacNEIL <[email protected]> wrote: > >I think the logic was to prevent JCL errors when symbols were expanded. > Whether or not that is correct, it is a very frustrating limitation. > > I agree. > Symbols in PROCs and INCLIBs do not suffer from that limitation. > If you get a JCL error, recode. > > The last proc/INCL I worked with was a special include for a PROC that was > used in 34 countries, but had different parameters based on the volume of > sales. > > It was: > > // SET SPACE=(CYL,(500,100)) -- for example > > And in the PROC: > > //DD1 DD SPACE=&SPACE, ... rest of DD statement > > The value was longer than the variable name, but it worked. > > If you had a JCL error (which I don't believe happened), you massaged the > PROC to 'fix' it. > > IIRC, JES2 didn't kill your job, if it got 'too long', but it's been a > while. > > So, I don't understand the SYMDEF restriction! > > - > Too busy driving to stop for gas! > > ---------------------------------------------------------------------- > 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
