On Thu, 29 Jan 2009 13:53:45 -0600, Tom Marchant <m42tom-ibmm...@yahoo.com> wrote:
>On Thu, 29 Jan 2009 12:35:37 -0600, Frank Swarbrick wrote: >> >>On a business day we'll have two jobs. The first one will look very much like >>this: >>//GDGTST3A JOB NOTIFY=&SYSUID,MSGCLASS=X,CLASS=A >>//BACKUP EXEC PGM=IEBGENER >>//SYSUT1 DD DISP=(OLD,DELETE,KEEP),DSN=PROD.XMIT.TXNFILE >>//SYSUT2 DD DISP=(NEW,CATLG,DELETE),DSN=PROD.APPL.TXNFILE(+1), >>// SPACE=(...) >>//SYSIN DD DUMMY >>//SYSPRINT DD DUMMY >>// >> >>This will copy all of the data from all of the generations of the "XMIT" >file to a >>new generation of the "APPL" file. If the copy succeeds then all of >>generations of the XMIT file are deleted. If it fails (out of space, or >>whatever) the XMIT generations remain so we can rerun when the issue is >>resolved. > >Maybe. If the gener abends, the XMIT group will be kept. If it fails with >a non-zero return code, they will be deleted. > >-- >Tom Marchant > For clarification, a non-zero COND CODE does not invoke ABNORMAL processing for the DISP= parameter. Only a job-step terminating with a USER or SYSTEM ABEND condition would cause the datasets to be deleted. Scott Barry SBBWorks, Inc. ---------------------------------------------------------------------- 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
