Frank Swarbrick wrote: On 9/17/2009 at 2:13 PM, Kirk Wolf<[email protected]> wrote: >> Not to drudge up old threads, but wouldn't it be nice if JCL PROC and >> SET variables were not thrown away by the converter/interpreter and >> instead placed in an ASASYMB-style symbol table by the initiator? >> This would be useful in so many ways....
That could be more complicated that the system-wide symbol table. One problem is probably that a variable can be set to several different values in a given job. > My god yes. VSE does this (allows symbolic JCL parms to be interrogated > programatically). I was hesitant to bring it up, as people seem to think I > just like to stir up trouble, but... :-) Frank, you're not the first one who has this problem during a VSE/MVS conversion, but there are several ways to pass the value of JCL variables to programs when PARM is not an option (used by IMS/DB or something else). I came up with and/or used several solutions to this problem over the years. The CCSS sub-system is one of them: http://gsf-soft.com/Products/CCSS.shtml but there are several other (fairly different) solutions. -- Gilbert Saint-Flour GSF Software http://gsf-soft.com/ -- Gilbert Saint-Flour GSF Software http://gsf-soft.com ---------------------------------------------------------------------- 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
