>> > > Example: >> > > >> > > // SET PARM1=NEW >> > > // EXEC PROC=FOO,PARM2=OLD >> > > >> > > In this example, while executing the FOO proc, you have >> JCL symbols >> > > PARM1 and PARM2. >> > > >> > > My question is this: does anyone know a way for a program to >> > > read the >> > > current JCL symbols? >> > > It could be that all of this information is washed away by >> > > the converter >> > > interpreter.... >> > > >> > > Kirk Wolf >> > > Dovetailed Technologies >> > >> > I am fairly sure that the information is indeed "washed away" by the >> > converter and not kept in any kind of control block that you can >> > __easily__ access. If you really wanted to, you might be able to get >> > hold of the JESJCL dataset like SDSF does and parse that >> out yourself. >> > <shiver> I looked and the information is NOT in the $INTTEXT spool >> > dataset. >> > >> > -- >> >> You can, of course, pass the required symbols as parm to the program: >> //PGM EXEC PMG=PROG1,PARM='SYMBOL1=&SYMBOL1,SYMBOL2=&SYMBOL2,...."' >> >> Kees. > >Very true. But I got the idea that the original person may have wanted >to write a subroutine or something to find out which "variables" have >been "set" and their associated "value". He didn't really say. The other >problem could be that old 100 character limit on the length of a PARM. >Like passing a UNIX file name into something. UNIX file names can be up >to 255 characters in length, assuming that I am remembering correctly. >
I have a program that is doing exactly what is described above, i.e. the symbols are being passed into the program on the parm. The 100 character limit has been a bit of an annoyance with this approach. I have also written another program that has already tackled the difficulty of parsing JCL, so I am now at the point where I am ready,willing and able to bite the bullet and go for broke by parsing JESJCL to get the symbols. FYI - I am doing this in COBOL, but before you say "You can't get there from here", I have no problem doing dynamic file allocations or chasing after MVS data areas, etc. I am quite comfortable making COBOL roll over and do stupid pet tricks. The question I have now is , how do I get to JESJCL from within an executing batch program? I can figure out how to make COBOL go there, I just don't know where the JESJCL data is located. Can anyone here tell me where to find it? Thanks, Bill Bass ---------------------------------------------------------------------- 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
