CA View - ERR Condition Noted in SARPAC Duplex Column for a Tape

Products

• OM Deliver
• OM View

Issue/Introduction

The client ran a View SARPAC job and received an ERR condition, in the Duplex field, for one of the tapes:

found errors on one of our duplex tapes. If the duplex tape is bad can we run a SARPAC to create a new primary and duplex?

                                               Used    Per
Tseq Data Set Name               Volser Total  Groups  cent Create     Yrs Dplx Lines       Yes/No, Remarks
---- --------------------------- ------ ------ ------- ---- ---------- --- ---- ----------- ------------------
137  XXXX.XXXXX.SARTAPE.T0000137 XXXXX 235383 207856   89  01/09/2019   1 ERR    XXXXXXXXX Y, SYSIN SELECTED

What should be done if there are differences shown between the primary and duplex tapes?
 

Environment

CA View - All Releases

Resolution

The "ERR" condition noted in the SARPAC "Dplx" column indicates that the primary and duplex tape do not match up in their content.
Note: The primary and duplex tapes are created so as to be exact duplicates.

As the error could be with either the primary or duplex tape, run the following SARTCP tapemap against both tapes: 

//XXXXXXXX JOB ... 
//SARTCP01 EXEC PGM=SARTCP 
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== Modify, if used 
//SYSPRINT DD SYSOUT=* 
//TAPEIN DD DISP=OLD,DSN=view_hlq.SARTAPE.T00nnnnn 
//SYSIN DD DUMMY 
// 

. Note: SARTAPE would be replaced with SARDPLX for the duplex tape. 

Note where there any differences between the tapes.

As to what is done from that point depends as to how the tapes compare. 

In this instance, the primary tape showed to have a "NULL" entry at the end, which the duplex tape did not have. 
So, here, it was suggested that the client run a SARPAC, on just the tape in question, to create a new primary and duplex tape.