The overwritten View tapes resembled each other with:
In Pos .Out Pos Rec Pos ID .................................. Jobname
------- ------- ------- -------------------------------- --------
......1 ......1 ....... *** UNKN ***
......2 ......2 ....... *** UNKN ***
......3 ......3 ......2 XXXXXXXX-RNN ................... XXXXXXXX
When another application writes over a portion of a View tape, the SARTCP COPY utility can be used to create a viable tape from the original tape. They ran SARTCP COPY, using their duplex tapes as input, to create new primary tapes:
//XXXXXXXX JOB ...
//SARTCP EXEC PGM=SARTCP
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== Modify, if used
//SYSPRINT DD SYSOUT=*
//TAPEIN DD DISP=OLD,DSN=view_hlq.SARDPLX.T00nnnnn
//TAPEOUT DD DISP=(,CATLG),
// DSN=view_hlq.SARTAPE.T00nnnnn,
// UNIT=(xxxx,,DEFER),VOL=(,RETAIN),LABEL=(,SL,EXPDT=99000)
//SYSIN DD *
SKIP 1
SKIP 2
NULL 1
NULL 2
/*
//
The tapes it created resulted with opening maps of:
In Pos .Out Pos Rec Pos ID .................................. Jobname
------- ------- ------- -------------------------------- --------
....... ......1 ....... *** NULL ***
....... ......2 ....... *** NULL ***
......1 .............. *** UNKN ***
......2 ....... ....... *** UNKN ***
......3 ......3 ......2 XXXXXXXX-RNN ................... XXXXXXXX
The resulting tapes could have their reports properly accessed and be used as input to SARTDR /TLOAD, in loading reports to the disk layer.