If a SARTCP tape copy or tape map results in a SARTCP10 I/O Error, the SKIP control statement can be used to correct the tape.
If the following error is received at the end of a tape being mapped or copied:
SARTCP10 Input tape I/O error, ECB=41, BLOCK=nnnnnnn,SENSE=xxxxx
and a SARTCP TAPEMAP of both the primary and duplex tapes shows the following:
1 1 REPORT0001 ... ... 2585 2585 REPORT2585 ... 2586 2586 *** NULL *** SARTCP10 Input tape I/O error, ECB=41, BLOCK=nnnnnnn,SENSE=xxxxx
What are the control statements required, in a SARTCP COPY job, to re-create the primary and duplex tapes?
The SARTCP COPY job should be set up including the control statement (in this instance), as follows:
//XXXXXXXX JOB ... //SARTCPCP EXEC PGM=SARTCP //STEPLIB DD DISP=SHR,DSN=VIEW.CAILIB <=== Modify, if used //SYSPRINT DD SYSOUT=* //TAPEIN DD DISP=(OLD,DELETE),DSN=VIEW.DB1.SARTAPE.T00nnnnn //TAPEOUT DD DISP=(,CATLG), // DSN=VIEW.DB1.SARTAPE.T00nnnnn, // UNIT=(3490,,DEFER),VOL=(,RETAIN),LABEL=(,SL,EXPDT=99000) //SYSIN DD * SKIP 2586-9999 /*
The above job will copy the reports up to the last full report (in this case, 2585) and will bypass the report denoted by "* NULL*".
The above job should be run for both the primary (SARTAPE) and duplex (SARDPLX) tapes.
NOTE: The above can be used ONLY IF it precisely meets your condition. If you have a tape where the tapemap does not show reports in exact succession, or if your primary and duplex tapemaps are not identical, then you need to contact CA support for guidance.