Thanks, that was a good tip. Here's an oddity. I picked a job at random and did a ? next to it, which shows: DDNAME StepName JESMSGLG JES2 JESJCL JES2 JESYSMSG JES2 SYSPRINT TSTDYNAL SYSPRINT TSTDYHDS
But ISFDSNAME for the last two returns a ? for the last qualifier: MJD2.MJDASTDS.JOB00645.D0000103.? Why isn't that SYSPRINT at least? It's harmless, I'm just wondering! Also, I see no ISFSTEPNAME. Is the StepName value not available -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Farley, Peter Sent: Friday, January 16, 2026 12:27 PM To: [email protected] Subject: Re: SDSF / ISFEXEC / ISFACT question That is not hard to handle when there are any significant differences in LRECL of the SYSOUT and JCL spool files. The SDSF Rexx interface returns the LRECL of all spool 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. Peter From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Friday, January 16, 2026 11:40 AM To: [email protected] Subject: Re: SDSF / ISFEXEC / ISFACT question On Fri, 16 Jan 2026 09:36:29 -0500, Phil Smith III wrote: > ... >This EXEC will let us save the job output before deleting it. FFDC, what a >concept! > How do you deal with various attributes among the numerous spool data sets which constitute a job? I could imagine writing each spool data set to a separate PS data set and building an index file to identify them.. -- 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
