On Fri, 3 Mar 2023 15:29:55 +0000, Farley, Peter wrote: >I don't know about LMCOPY, but my experience with TRANSMIT is similar. >Running a batch IKJEFT01 with a SYSPRINT DD in the JCL allocated to SYSOUT=* >and executing multiple TRANSMIT commands in SYSTSIN you still get SYS00003, >SYS00004, etc., outputs in the batch job, one for each TRANSMIT execution, >each with the IEBCOPY "SYSPRINT" output from the PDS copy operation, and NO >output to the allocated SYSPRINT DD at all.. I suspect in the case of >TRANSMIT that the TRANSMIT code (not IEBCOPY) is unconditionally dynamically >allocating SYSnnnnn to SYSOUT and then passing the generated DD name to >IEBCOPY in the callable PARM list. > I could imagine ISPF's passsing SPFLIST in place of SYSPRINT to any utility supporting an alternate DDNAME list (many do.) But the designers may have envisioned problems with incompatible attributes. If one such utility expects SYSPRINT DD RECFM=FBM,LRECL=121 and another RECFM=VBA,LECL=137, the concatenated SYSPTINT will be illegible.
IBM aimed for flexibility with the variety of data set attributes, but missed and shot itself in the foot instead. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
