Convert the entire job to a REXX exec that runs onder TSO or ISPF batch. I've done the same with some jobs that would otherwise exceed the limit of 255 steps per job.
Robert On Fri, 16 Aug 2024 at 13:27, Steve Estle < [email protected]> wrote: > Hello All, > > I know we have a lot of REXX coders / developers on here so putting this > out as a "is this possible" question. > > Scenario: > > A recent effort brought a question to light. We have a home grown REXX > routine that dynamically generates dataset names and saves JES job spool > dataset off using IOF product routines. The dataset name generated is > unique as it includes jobname, jobnumber, and Julian date, timestamp in the > dynamically generated dataset name which occurs withing thisi REXX routine > (we call it BTCHSAVE). I'd like the ability to access this dynamically > generated dataset name as a JCL symbolic variable for subsequent downstream > job steps. Is there any way that REXX variables can be somehow be shared / > passed back to batch job JCL routine such that the dynamically generated > dataset name can be used in subsequent steps of the job? > > Let me know if anyone has tried to do this or not - possibly a future IDEA > for IBM. > > Thanks in advance, > > Steve Estle > Peraton Systems Programmer > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Robert AH Prins robert(a)prino(d)org The hitchhiking grandfather <https://prino.neocities.org/index.html> Some REXX code for use on z/OS <https://prino.neocities.org/zOS/zOS-Tools.html> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
