Not DR, QA. Different TLA (TWO-letter Acronym!). But right, we don't need to reconstitute it with the LRECL, we just need to be able to read it. If I needed the LRECL I could put it in the file header (the separator in the combined data set), I guess.
And I guess I can infer from the "?" that a particular data set is a SYSPRINT or thereabouts; I was just surprised by it. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Farley, Peter Sent: Saturday, January 17, 2026 3:44 PM To: [email protected] Subject: Re: SDSF / ISFEXEC / ISFACT question I believe the OP’s original goal was stated to be the capture of the contents of outstanding spooled jobs after a DR exercise. Whether particular parts of the spooled jobs need or want to be a different RECFM or LRECL for later use is IMHO not relevant to that goal. As for not depending on DD name for a qualifier in the spool file DSN, if you look at the generated DSN’s for the spool files the qualifier before the question mark is actually the unique qualifier: “Dnnnnnnn” where nnnnnnn is the DSID, which is unique to each spool file. Peter From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Saturday, January 17, 2026 12:31 PM To: [email protected] Subject: Re: SDSF / ISFEXEC / ISFACT question On Fri, 16 Jan 2026 17:26:59 +0000, Farley, Peter wrote: > >The SDSF Rexx interface returns the LRECL of all splol files in the job as one >of the arrays returned from the action character “?” against a job. One only >needs to pre-scan the LRECL array for the largest value and allocate the >single output file as RECFM=VB with that maximum LRECL + 4 and no issues >should occur in writing output to that file from all spool files in the job. > That does poorly for SYSPUNCH. for example. Various subsequent utilities may require FB, 80, 3120. Phil's example showed only a job log. If that's all he wants to capture, the attributes are known a priori. I once broke SDSF edge testing with a SYSOUt record with 32752 data bytes. Fixed by APAR, peculiarly limited because of Hyrum's Law. DDon't rely on DDNAME as a qualifier. Duplicates can occur with DYNALLOC; FREE; DYNALLOC. -- 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 [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
