You could add an IEBGENER Step to copy the GDG.DSNAME.G0002V00 back into a dataset named GDG.DSNAME.G0001V00 if you like.
//GDG EXEC PGM=IEBGENER,COND=(0,NE) //SYSOUT DD SYSOUT=(,),OUTPUT=(*.JCL) //SYSPRINT DD SYSOUT=(,),OUTPUT=(*.JCL) //SYSUT1 DD DSN=GDG.DSNAME(+1),DISP=SHR, //SYSUT2 DD DSN=GDG.DSNAME.G0001V00, // DISP=(NEW,CATLG,DELETE, ...... //SYSIN DD DUMMY Hutchison, Gregory A. Oregon DOT DMVIS phone:503-945-7081 fax:503-945-5220 gregory.hutchi...@odot.state.or.us -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Fred Kaptein Sent: Tuesday, January 18, 2011 1:49 PM To: IBM-MAIN@bama.ua.edu Subject: Re: GDG Question There are too many JCL changes in other batch jobs, to change this to a non-GDG file. Reusing the same file without deleteing and reallocating the data set is an option. Thank you for your responses, we will take them into consideration. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
