Thanks Robert, that looks useful for the rest of us as well. There are ISV products (we use JCLCHECK) that also perform this function as part of preparing JCL for production install, but freely shared code is good too.
However, even the best “checker” software can’t tell you if newly-introduced application files (especially GDG’s) that won’t exist until the first batch job to create them actually runs are going to be available after JCL turnover to production. Peter From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Robert Prins Sent: Friday, August 4, 2023 10:54 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Accessing JCL SETs in Rexx In essence, I've not used this since about forever, but when we, as in I, decided we needed to start using parametrized procs at Willis around the Y2K time, and people were frustrated by not being able to see the wood from the trees, I very quickly knocked up the code below, I have no clue if it's still working, but we used it in SDSF on the JCL of TYPRUN=SCAN submitted jobs, to get rid of all the IEF653I messages. Feel free to play around with it, if you see to improve it, please share your code, and if you don't like GPL'ed code, though! Robert <Code snipped> And yes, it requires, IIRC, nice parameters on procs and the invocation of procs and on set statements, so one per line. And no, it was a Q&D hack, so error-checking is non-existent, expect to invoke it lots of times after uncommenting the "trace ?r" or by preceding it with "EXECUTIL TS" Enjoy, Robert On Fri, 4 Aug 2023 at 11:04, Seymour J Metz <sme...@gmu.edu<mailto:sme...@gmu.edu>> wrote: > Back in the bad old days, IBM showed the expansion immediately after the > JCL. Alas, in MVS they chose to show it as a message in a separate JES > dataset. Have they moved IEF653I to be inline since then? > > > -- > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf > of Paul Gilmartin [0000042bfe9c879d-dmarc-requ...@listserv.ua.edu] > Sent: Friday, August 4, 2023 12:02 AM > To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU> > Subject: Re: Accessing JCL SETs in Rexx > > On Fri, 4 Aug 2023 03:32:01 +0000, Jon Perryman wrote: > > > > On Thursday, August 3, 2023 at 12:21:34 PM PDT, David Spiegel wrote: > >> My intention is to read a Job and make sure that all datasets are > available, > >> but, the dsnames contain SET variables. > > > >The converter / interpreter will resolve variables. Submit the job with > typerun scan or hold should generate the information you want. > > > I've found SCAN to be almost worthless. It doesn't always report invalid > data set names. > > >If you're not comfortable with control blocks, IPCS and dumps, then you > can use SDSF to extract the converted JCL albeit a little funky to process. > > > Is there a JES data set accessible by SDSF that shows symbols resolved? > what does it show if symbol resolution extends a line beyond column 71? > > In fact, any continuation that splits a data set name can be "a little > funky > to process." -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
