a) Ensure that all tapes output from the SARPAC are retained.
Note: Ensure that the Tape Management System retains all tapes that are created in any abended View procedure.
b) Run a SARTCP tapemap on the problem primary tape:
//XXXXXXXX JOB ...
//SARTCP EXEC PGM=SARTCP
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== Modify, if used
//SYSPRINT DD SYSOUT=*
//TAPEIN DD DISP=OLD,DSN=xxxxxx.xxxxxx.SARTAPE.T00nnnnn
//SYSIN DD DUMMY
c) If the primary tapemap runs to a RC=00, then there is nothing wrong with the tape.
With that, run the SARPAC process again, as it's possible that the problem could have been with a device, with no actual problem with the tape.
The SARPAC will pick up where it left off, calling for the last input and output tapes that it was using.
d) If the primary tapemap runs to other than a RC=00, then there probably is a problem with the tape.
Run a tapemap on the duplex tape, if one exists.
e) If the duplex tapemap runs to a RC=00:
. Uncatalog the primary tape.
. Use SARTCP to copy the duplex tape to a primary tape.
. Run SARPAC, and it will pick up where it left off.
f) If there are identical problems with the primary and duplex tape, use utility SARTCP to copy the problem primary tape to a new tape, using SKIP and NULL statements corresponding to what gets copied, depending on what the problem is.