Others may tell you authoritatively whether you can or cannot. I'll just add that if you can't, it shouldn't be very difficult to have the REXX read all the generated IEBCOPY files and display their contents in one, and even have it delete the originals if you feel daring.
--- Bob Bridges, [email protected], cell 336 382-7313 /* In matters of conscience, the law of majority has no place. -Mohandas Karamchand Gandhi (1869-1948) */ -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Cameron Conacher Sent: Thursday, March 2, 2023 18:57 I am using REXX (specifically LMCOPY) to copy PDS members from one library to another. Everything is working just fine. Everything copies as I expect it to. When the LMCOPY runs, it writes some IEBCOPY processing messages to a generated file name, which has a high level qualifier of the RACF ID under which the JOB runs. If two members are copied, LMCOPY is executed twice, and two IEBCOPY files are generated..... if 100 members are copied I get 100 IEBCOPY files generated. My question is this, can I direct all of the IEBCOPY output (assuming it is SYSPRINT) directed to one single output file? So, instead of seeing 100 individual IEBCOPY, I only get one single consolidated file with a name of my choosing? IEBCOPY appears to run under the covers for LMCOPY. I cannot see anywhere that LMCOPY accepts a parameter indicating where to send the IEBCOPY output. To help clarify things, I can use LMCOPY to copy PDS.LIBRAY1(Member1) to PDS.LIBRAY2(Member1) without any issues. But under the covers LMCOPY seems to run IEBCOPY and I see generated output files for IEBCOPY like RACFID.SPF101.IEBCOPY. Can I tell LMCOPY to inform IEBCOPY to use MYNAME.IEBCOPY.SYSPRINT instead of the generated name? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
