Gilbert, My suggestion for having JCL/SET variables in a ASASYMBM "user" table has to do with what a program would see when it runs in the initiator. Of course, each step would see different variables/values.
Kirk Wolf Dovetailed Technologies http://dovetail.com On Sat, Sep 19, 2009 at 2:06 AM, Gilbert Saint-Flour <[email protected]>wrote: > Hardee, Charles H wrote: > > > I agree with Paul, why do you call this a problem. > > > > As Paul indicates, the substituted values would be those in effect when > > the step (EXEC as Paul said) is reached. > > If you have a SET for a variable name prior to step 1 and then a SET for > > the same variable name prior to step 2, isn't the intention to have > > different values available to the step? > > What Kirk Wolf calls "ASASYMB-style symbol table" has a simple format > because > each variable it contains has a single (and stable) value. The structure of > a "JCL variable symbols" table defined when the job's JCL is analysed would > be more complex because a variable can by set several times in a job, even > in > a job step. Example: > > // SET VAR=AAAAAAAA > //STEP1 EXEC PGM=MYPROG,PARM=&VAR > // SET VAR=SYS1.MACLIB > //DD1 DD DSN=&VAR,DISP=SHR > // SET VAR=SYS1.MODGEN > //DD2 DD DSN=&VAR,DISP=SHR > > When MYPROG looks for the value of &VAR, what does it find ? AAAAAAAA, > SYS1.MACLIB, or SYS1.MODGEN ? All three ? No, this definitely can't be > as > simple as ASASYMB. > > The "System static symbols" table is displayed in the SYMBOLS section of > SHOWMVS and SHOWzOS. The code was contributed to R618 in 1996 by DL. > > -- > Gilbert Saint-Flour > GSF Software > http://gsf-soft.com > > > > What I would like to see is something similar to the "environment" in > > the PC world. One would SET various variables to required values and > > then, programmatically, access the "environment" and retrieve a > > variable's value. That is, in effect, what a SYSIN DD would/could be > > used for, but, unfortunately, symbolics can't be used in SYSIN, or more > > generically, DD *, input. > > > > Chuck > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of Paul Gilmartin > > Sent: Friday, September 18, 2009 10:41 AM > > To: [email protected] > > Subject: Re: Reading DD card information > > > > On Fri, 18 Sep 2009 16:37:19 +0200, Gilbert Saint-Flour wrote: > > > >>Frank Swarbrick wrote: > >> > >>On 9/17/2009 at 2:13 PM, Kirk Wolf 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. > >> > > I would expect that the values passed to each job step would be the > > values of the JCL symbols in effect at the point of the EXEC statement. > > Why do you call this a problem? This parallels the behavior of > > symbolic substitution in PARM, DD statements, etc. > > > > -- 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
