Thanks. I have this working, using ISFACT with PARM(NP SA), and then reading those temporary data sets and merging them in a format we like using EXECIO. Now, if I'd remembered to look at Mark's stuff first, I'd've probably saved myself some time; OTOH now I know more about using the interface, learned the hard way, so maybe it's a wash!
The motivation here is that we have CI stuff using Jenkins that runs z/OS tests. In order to keep things tidy, it deletes job output from SPOOL after it runs. This is fine when things work; when something fails, it means you have to rerun it, usually manually, to find out what the problem was. Of course the Jenkins stuff tries to report it, but that's a moving target--there's always ONE more detail you wish you had. (Hint: I didn't build this stuff in the first place, would not have done it this way.) This EXEC will let us save the job output before deleting it. FFDC, what a concept! -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Albertus de Wet Sent: Thursday, January 15, 2026 9:03 PM To: [email protected] Subject: Re: SDSF / ISFEXEC / ISFACT question Check out Mark Zelden's REXX utility: SDSF@DR <http://mzelden.com/mvsfiles/[email protected]>. It has a batch as well as online interface. I use it all the time during DR. A lot of other utils are very useful: http://mzelden.com/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
