The client's SARSTC task abended with a S0C4 condition during a View interim backup.
The problem, after review, was found to be an abend in a CA 1 program.
Release : 14.0
Component : CA View
The matter actually involved CA 1, as View in this case was found to be a victim.
The client was asked if there were any other jobs, requiring tape, that may have had a similar problem.
Regarding View, it wanted to be ensured that the View backup was successful, and that the tape was still viable.
To that end, a View tapemap could be run to verify the 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=VIEW_HLQ.SARTAPE.T00NNNNN
//SYSIN DD DUMMY
If the tape is good, then it needs to be ensure that the tape is retained.
For CA 1 Tape Management (CA 1), the ABE parameter determines how many days to keep tapes that are created from a job that abnormally terminates.
To override the default, CA 1 provides a customizable exit called TMSUX2B that can be modified to prevent CA View tapes from being scratched or overwritten in the event of an abnormal termination.
In this case, the View tape was determined to be good.