I have a 50+ step backup job (using real 3590s) that has steps like:
//STEP049 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//DASD DD DISP=SHR,UNIT=3390,VOL=SER=HKYTD4
//BACKUP DD DSN=DR.T.DSS.HKYTD4.&SUF,DISP=(NEW,KEEP,DELETE),
// UNIT=3590,VOL=(,RETAIN,REF=*.STEP048.BACKUP),
// LABEL=(49,SL,RETPD=&DAYS),DCB=(MODEL.DSCB,BLKSIZE=0)
//SYSIN DD *
DUMP FULL INDD(DASD) OUTDD(BACKUP) ALLD(*) ADMIN TOL(IOER) ALLE
/*
//*
//STEP050 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//DASD DD DISP=SHR,UNIT=3390,VOL=SER=HKYTD5
//BACKUP DD DSN=DR.T.DSS.HKYTD5.&SUF,DISP=(NEW,KEEP,DELETE),
// UNIT=3590,VOL=(,RETAIN,REF=*.STEP049.BACKUP),
// LABEL=(50,SL,RETPD=&DAYS),DCB=(MODEL.DSCB,BLKSIZE=0)
//SYSIN DD *
DUMP FULL INDD(DASD) OUTDD(BACKUP) ALLD(*) ADMIN TOL(IOER) ALLE
/*
This job always worked on OS/390 2.10, but under z/OS 1.13, randomly,
when going to a new step, it wants the current tape mounted on a
different 3590. Additionally, it does not unload the tape from the first
drive.
Also: If I have only one drive online, it runs to completion. If I have
two drives, but the other one is busy, it runs to completion.
Info: This system is using RMM as a tape manager, but the files being
created on the tape are not defined in any storage group or RMM.
It is driving me batty. I have to be 'not seeing' something.
--
Tony Thigpen
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
