Re: Use of RETAIN
Turned out to be an ACS rules issue. The storage person adjusted code in a manner suggested by IBM and found via Google search. We're going to test today to see if we can get all 12 steps and 400+ dumps onto one Jaguar 3592. -- 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
Re: Use of RETAIN
We're seeing indications of SMS ACS involvement and are working that angle with IBM. -- 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
Re: Use of RETAIN
Here is a short version of the job...and it croaks trying to open up the tape in the second part of the second step. We thought maybe it was a DD name conflict and changed the scheme for a test, same results...opened with IBM and will do the same with FDR folks. This job will be all generated by REXX to be dynamic. //TAPE1 DD DSN=PDR.TSTBKP.AIG002(+1), // DISP=(NEW,CATLG,DELETE), // UNIT=(TAPE92,,DEFER), // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // LABEL=(1,SL,EXPDT=99000), // VOL=(,RETAIN) //DISK2 DD UNIT=3390,DISP=SHR,VOL=SER=DBPK23 //TAPE2 DD DSN=PDR.TSTBKP.DBPK23(+1), // DISP=(NEW,CATLG,DELETE), // UNIT=(TAPE92,,DEFER), // LABEL=(2,SL,EXPDT=99000), // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // VOL=(PRIVATE,RETAIN,REF=*.TAPE1) //SYSIN DD DSN=PROD.PARMLIB(DR100),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSPRIN1 DD SYSOUT=* //SYSDUMP DD SYSOUT=* //ABRMAP DD SYSOUT=* //* End of Step //DUMP2 EXEC PGM=FDR,REGION=8M //DISKA DD UNIT=3390,DISP=SHR,VOL=SER=DB0034 //TAPEA DD DSN=PDR.TSTBKP.DB0034(+1), // DISP=(NEW,CATLG,DELETE), // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // UNIT=(TAPE92,,DEFER), // LABEL=(3,SL,EXPDT=99000), // VOL=(,RETAIN,,,REF=*.DUMP1.TAPE1) //DISKB DD UNIT=3390,DISP=SHR,VOL=SER=DB0035 //TAPEB DD DSN=PDR.TSTBKP.DB0035(+1), // DISP=(NEW,CATLG,DELETE), // UNIT=(TAPE92,,DEFER), // LABEL=(4,SL,EXPDT=99000), // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // VOL=(,RETAIN,,,REF=*.DUMP1.TAPE1) //SYSIN DD DSN=PROD.PARMLIB(DR100),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSPRIN1 DD SYSOUT=* //SYSDUMP DD SYSOUT=* //ABRMAP DD SYSOUT=* //NOTIFY EXEC PGM=WTOPGM,COND=((3,GT),EVEN), // PARM='JOB DRAIG001 BACKUP FAILED ON MVS' //NOTIFY EXEC PGM=WTOPGM,COND=(1,LT), // PARM='JOB DRAIG001 BACKUP SUCCESSFUL ON MVS' //* -- 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
Re: Use of RETAIN
In a message dated 9/14/2009 9:47:57 A.M. Central Daylight Time, daniel_mclaugh...@us.crawco.com writes: and it croaks trying to open up the tape in the second part of the second step. We thought maybe it was a DD name conflict and changed the scheme for a test, same results...opened with IBM and will do the same with FDR folks. This job will be all generated by REXX to Still miss Bruce Black(FDR). Anyway croakers generally issue messages? FDRABR keeps it's own catalog of backups and you should only need to point to the drive(s) once and it handles the rest. -- 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
Re: Use of RETAIN
Hi Daniel, On quick look, I don't see a problem. Have you sent this problem to us at Innovation? We haven't seen it yet. Please submit the job and output to the support email for us to review at your convenience. Thanks, Joseph Butz jb...@fdrinnovation.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Daniel McLaughlin Sent: Monday, September 14, 2009 10:48 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Use of RETAIN Here is a short version of the job...and it croaks trying to open up the tape in the second part of the second step. We thought maybe it was a DD name conflict and changed the scheme for a test, same results...opened with IBM and will do the same with FDR folks. This job will be all generated by REXX to be dynamic. //TAPE1 DD DSN=PDR.TSTBKP.AIG002(+1), // DISP=(NEW,CATLG,DELETE), // UNIT=(TAPE92,,DEFER), // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // LABEL=(1,SL,EXPDT=99000), // VOL=(,RETAIN) //DISK2 DD UNIT=3390,DISP=SHR,VOL=SER=DBPK23 //TAPE2 DD DSN=PDR.TSTBKP.DBPK23(+1), // DISP=(NEW,CATLG,DELETE), // UNIT=(TAPE92,,DEFER), // LABEL=(2,SL,EXPDT=99000), // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // VOL=(PRIVATE,RETAIN,REF=*.TAPE1) //SYSIN DD DSN=PROD.PARMLIB(DR100),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSPRIN1 DD SYSOUT=* //SYSDUMP DD SYSOUT=* //ABRMAP DD SYSOUT=* //* End of Step //DUMP2 EXEC PGM=FDR,REGION=8M //DISKA DD UNIT=3390,DISP=SHR,VOL=SER=DB0034 //TAPEA DD DSN=PDR.TSTBKP.DB0034(+1), // DISP=(NEW,CATLG,DELETE), // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // UNIT=(TAPE92,,DEFER), // LABEL=(3,SL,EXPDT=99000), // VOL=(,RETAIN,,,REF=*.DUMP1.TAPE1) //DISKB DD UNIT=3390,DISP=SHR,VOL=SER=DB0035 //TAPEB DD DSN=PDR.TSTBKP.DB0035(+1), // DISP=(NEW,CATLG,DELETE), // UNIT=(TAPE92,,DEFER), // LABEL=(4,SL,EXPDT=99000), // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // VOL=(,RETAIN,,,REF=*.DUMP1.TAPE1) //SYSIN DD DSN=PROD.PARMLIB(DR100),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSPRIN1 DD SYSOUT=* //SYSDUMP DD SYSOUT=* //ABRMAP DD SYSOUT=* //NOTIFY EXEC PGM=WTOPGM,COND=((3,GT),EVEN), // PARM='JOB DRAIG001 BACKUP FAILED ON MVS' //NOTIFY EXEC PGM=WTOPGM,COND=(1,LT), // PARM='JOB DRAIG001 BACKUP SUCCESSFUL ON MVS' //* -- 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
Re: Use of RETAIN
I'll be glad to share the JCL, the EXEC, as well once I get it to work. Still unable to get the tape to go from step to step. Here is JCL from step 1 to step 2. //DISKZ DD UNIT=3390,DISP=SHR,VOL=SER=DB0033 //TAPEZ DD DSN=PDR.TSTBKP.DB0033(+1), // DISP=(NEW,CATLG,DELETE),UNIT=TAPE92, // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // VOL=REF=PDR.TSTBKP.AIG002,LABEL=(35,SL,EXPDT=99000) //SYSIN DD DSN=PROD.PARMLIB(DR100),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSPRIN1 DD SYSOUT=* //SYSDUMP DD SYSOUT=* //ABRMAP DD SYSOUT=* //* End of Step //DuMP2 EXEC PGM=FDR,REGION=8M //DISK1 DD UNIT=3390,DISP=SHR,VOL=SER=DB0034 //TAPE1 DD DSN=PDR.TSTBKP.DB0034(+1), // DISP=(NEW,CATLG,DELETE),UNIT=TAPE92, // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // LABEL=(36,SL,EXPDT=99000), // VOL=REF=PDR.TSTBKP.AIG002 This is the latest iteration which just dies off the jump. I'm sure it has to do with the fact I'm using GDGs with (+1). When I was using a refer back to DUMP1, TAPE1 and RETAIN it was dropping the tape after step one and dying. As I said, I'm happy to share any of this and should have made an update. Mea Culpa! -- 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
Re: Use of RETAIN
Did you try the one step version with multiple dumps that I sent you. Tim -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of Daniel McLaughlin Sent: Friday, September 11, 2009 9:19 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Use of RETAIN I'll be glad to share the JCL, the EXEC, as well once I get it to work. Still unable to get the tape to go from step to step. Here is JCL from step 1 to step 2. //DISKZ DD UNIT=3390,DISP=SHR,VOL=SER=DB0033 //TAPEZ DD DSN=PDR.TSTBKP.DB0033(+1), // DISP=(NEW,CATLG,DELETE),UNIT=TAPE92, // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // VOL=REF=PDR.TSTBKP.AIG002,LABEL=(35,SL,EXPDT=99000) //SYSIN DD DSN=PROD.PARMLIB(DR100),DISP=SHR //SYSPRINT DD SYSOUT=* //SYSPRIN1 DD SYSOUT=* //SYSDUMP DD SYSOUT=* //ABRMAP DD SYSOUT=* //* End of Step //DuMP2 EXEC PGM=FDR,REGION=8M //DISK1 DD UNIT=3390,DISP=SHR,VOL=SER=DB0034 //TAPE1 DD DSN=PDR.TSTBKP.DB0034(+1), // DISP=(NEW,CATLG,DELETE),UNIT=TAPE92, // DCB=(IPOBAK.PATTERN.DSCB,BUFNO=10), // LABEL=(36,SL,EXPDT=99000), // VOL=REF=PDR.TSTBKP.AIG002 This is the latest iteration which just dies off the jump. I'm sure it has to do with the fact I'm using GDGs with (+1). When I was using a refer back to DUMP1, TAPE1 and RETAIN it was dropping the tape after step one and dying. As I said, I'm happy to share any of this and should have made an update. Mea Culpa! -- 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
Re: Use of RETAIN
I'm sure it has to do with the fact I'm using GDGs with (+1). When I was using a refer back to DUMP1, TAPE1 and RETAIN it was dropping the tape after step one and dying. GDG's are funny in the way relative generations work. The catalogue is not fully updated until after the job finished. So, if you are creating two generations in the same job, the second one has to be '(+2)'. '(+1)', even in a later step refers to the original 'new' generation. This continues with subsequent generations within the same job. - Too busy driving to stop for gas! -- 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
Re: Use of RETAIN
The originally specified JCL isn't exactly correct. If you were to call for a 2nd tape sometime before reaching file 10, the system would try to place that file on the 1st (full) tape, due to the way this refer-back is coded. Also, if allowed, there would be gaps in the file numbers (such as file 10 following file 8 with no file 9 present). The correct specification would be to refer back to the DD for the previous file on the tape. Original: //TAPE1DD DSN=CHGE.VOL1..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(1,SL), // VOLUME=(,RETAIN,SER=), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE2DD DSN=CHGE.VOL2..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(2,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE1), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE10 DD DSN=CHGE.VOL10..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(10,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE1), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) Corrected: //TAPE1DD DSN=CHGE.VOL1..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(1,SL), // VOLUME=(,RETAIN,SER=), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE2DD DSN=CHGE.VOL2..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(2,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE1), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) . . . //TAPE9DD DSN=CHGE.VOL9..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(9,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE8), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE10 DD DSN=CHGE.VOL10..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(10,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE9), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) -- 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
Re: Use of RETAIN
I agree with John, make the referback always to the previous step. When I was doing a lot of tape stacking, I also had a placeholder dataset for the first one on the initial tape. I would generate the JCL using a REXX to build the STEPNAME referback name and build a new job at step 255. Use of an instream PROC also makes the JCL more streamlined, make the referback a PROC JCL PARM. I have a feeling that if you only refer back to label 1, when a new volume is mounted, the job fails... On Fri, Sep 11, 2009 at 7:08 AM, John Laubenheimer jlaubenhei...@doitt.nyc.gov wrote: The originally specified JCL isn't exactly correct. If you were to call for a 2nd tape sometime before reaching file 10, the system would try to place that file on the 1st (full) tape, due to the way this refer-back is coded. Also, if allowed, there would be gaps in the file numbers (such as file 10 following file 8 with no file 9 present). The correct specification would be to refer back to the DD for the previous file on the tape. Original: //TAPE1 DD DSN=CHGE.VOL1..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(1,SL), // VOLUME=(,RETAIN,SER=), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE2 DD DSN=CHGE.VOL2..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(2,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE1), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE10 DD DSN=CHGE.VOL10..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(10,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE1), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) Corrected: //TAPE1 DD DSN=CHGE.VOL1..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(1,SL), // VOLUME=(,RETAIN,SER=), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE2 DD DSN=CHGE.VOL2..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(2,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE1), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) . . . //TAPE9 DD DSN=CHGE.VOL9..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(9,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE8), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE10 DD DSN=CHGE.VOL10..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(10,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE9), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) -- 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 -- Wayne V. Bickerdike -- 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
Re: Use of RETAIN
fyi, heres what I use, I just have 10 vols but same concept Just pass the dasd volser to the proc. //DUMPVOL PROC //DISK1DD UNIT=3390,VOL=SER=VOL1.,DISP=SHR //DISK2DD UNIT=3390,VOL=SER=VOL2.,DISP=SHR //DISK10 DD UNIT=3390,VOL=SER=VOL10.,DISP=SHR //TAPE1DD DSN=CHGE.VOL1..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(1,SL), // VOLUME=(,RETAIN,SER=), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE2DD DSN=CHGE.VOL2..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(2,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE1), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) //TAPE10 DD DSN=CHGE.VOL10..MAGSTAR(+1),DISP=(NEW,CATLG,DELETE), // UNIT=3590-1,LABEL=(10,SL), // VOLUME=(,RETAIN,REF=*.STEP01.TAPE1), // DCB=(MODEL,RECFM=U,LRECL=0,BLKSIZE=32760) // EXEC DUMPVOL, // VOL1=VOL001, // VOL2=VOL002, // VOL10=VOL010 Tim Brown Systems Specialist - Project Leader Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: tbr...@cenhud.com mailto:tbr...@cenhud.com Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of Daniel McLaughlin Sent: Wednesday, September 09, 2009 7:31 AM To: IBM-MAIN@bama.ua.edu Subject: Use of RETAIN OK...I'm a bit baffled and readily admit it. I've created an EXEC in REXX to create a 12 step job to dump 420 DASD volumes to one 3592. Step one runs along fine and stacks all the volumes, 35 of them, fine in the first step. When the next step starts it belches on the tape so I know it's not passed correctly. I am sure it has to do with the RETAIN option..so do I put that on the last file of the first step or the first file of the next or both? This is a DR type of thing and the EXEC, which I inherited with the job, works great. And yes...I have read the JCL User guide but it ain't helping a lot... -- 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
Re: Use of RETAIN
OK...I think I see that retain needs to be on each TAPE DD card and refer to the previous step. I thought once I declared that on the first tape statement in the next step that each tape within that step would automatically grab the tape. vol=(,retain,prev.step.tape) on first file, second step and subsequent Then vol=(*.prevtape) for following tapes within the step. And I think you are saying..PREV.STEP1.TAPE1 all the way through the JCL. So even step 7 would refer back to STEP1.TAPE1...?? The fog is lifting a little. -- 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
Re: Use of RETAIN
Mine is a one step job ! Step01 is the only step. Tim -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of Daniel McLaughlin Sent: Wednesday, September 09, 2009 7:48 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Use of RETAIN OK...I think I see that retain needs to be on each TAPE DD card and refer to the previous step. I thought once I declared that on the first tape statement in the next step that each tape within that step would automatically grab the tape. vol=(,retain,prev.step.tape) on first file, second step and subsequent Then vol=(*.prevtape) for following tapes within the step. And I think you are saying..PREV.STEP1.TAPE1 all the way through the JCL. So even step 7 would refer back to STEP1.TAPE1...?? The fog is lifting a little. -- 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
Re: Use of RETAIN
I see the pattern though and will try it out...thank you. -- 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
Re: Use of RETAIN
In a message dated 9/9/2009 6:48:17 A.M. Central Daylight Time, daniel_mclaugh...@us.crawco.com writes: The fog is lifting a little. Beware falling rocks? Should be preceding step in all instances. //STEP02 EXEC BACKUP,DDPREP=STEP01,DDLAB=2 //STEP03 EXEC BACKUP,DDPREP=STEP02,DDLAB=3 It works back to the first step as long as everything's contained on one volume. -- 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
Re: Use of RETAIN
On Wed, 9 Sep 2009 06:31:27 -0500, Daniel McLaughlin daniel_mclaugh...@us.crawco.com wrote: OK...I'm a bit baffled and readily admit it. I've created an EXEC in REXX to create a 12 step job to dump 420 DASD volumes to one 3592. Step one runs along fine and stacks all the volumes, 35 of them, fine in the first step. When the next step starts it belches on the tape so I know it's not passed correctly. I am sure it has to do with the RETAIN option..so do I put that on the last file of the first step or the first file of the next or both? This is a DR type of thing and the EXEC, which I inherited with the job, works great. And yes...I have read the JCL User guide but it ain't helping a lot... Sharing some of your JCL (output, resolved with any symbolics used) and also specific error information with an ABEND code would be helpful beyond guessing. 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
Re: Use of RETAIN
snip- OK...I'm a bit baffled and readily admit it. I've created an EXEC in REXX to create a 12 step job to dump 420 DASD volumes to one 3592. Step one runs along fine and stacks all the volumes, 35 of them, fine in the first step. When the next step starts it belches on the tape so I know it's not passed correctly. I am sure it has to do with the RETAIN option..so do I put that on the last file of the first step or the first file of the next or both? This is a DR type of thing and the EXEC, which I inherited with the job, works great. And yes...I have read the JCL User guide but it ain't helping a lot... --unsnip-- Let me suggest that you get together with a techie from Innovation. FDR products, specifically ABR and FDRDRP can be your greatest friends in a DR situation, provided you do the necessary legwork in getting FDRABR to manage your backups. We were only restoring 80 volumes during DR testing but FDRABR and FDRDRP cut our restore times to under 60 minutes on 3590 tapes. And no, I don't work for Innovation. :-) I'm just very impressed with their products. Rick -- 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
