I had sent an earlier post that got lost in the ether.... You could simply change the input of the COPY step to use the GDG generation you created in the BACKUP step.
Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Betten Sent: Tuesday, January 22, 2008 10:36 AM To: [email protected] Subject: Re: DFSORT anomaly? I would change the dataset names instead of changing the copy to a sort. Today, probably not much difference but if the file size grows over time, the copy is going to be faster and require less resources than a sort. I'd change the following Add a DD5 to your initial DEL005 step with a new data set named something like PECT.TBC.SE.ALC.TEMP.IMPOUT Change NCP0511 step to create PECT.TBC.SE.ALC.TEMP.IMPOUT Change IDCAM020 step's FILEIN to PECT.TBC.SE.ALC.TEMP.IMPOUT Change SORT01 step's SORTIN to PECT.TBC.SE.ALC.TEMP.IMPOUT You could also add another BR14 step right after the SORT01 step to delete the TEMP.IMPOUT if you want to avoid that extra copy occupying space. Have a nice day, ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
