Previous Topic: Example 4: Consolidating Two Tapes of a Tape Storage GroupNext Topic: Database Utilities


Recovering from Not Cataloged Tape Errors

The *NOCAT error message appears in the SARPAC report for any tapes that are no longer in the MVS Catalog. If the catalog entry is missing and tape is still available, the tape can be cataloged using the IBM utilities. If the tape is truly not available, the only recovery procedure is to remove all database references to that tape.

You must delete the Group Control Record (GCR) for SYSOUT reports that exist only on the tapes that are no longer available. You can use:

The Tape List utility SARTSLST can be executed against the tape sequence number for a tape in error.

This utility creates a control statement stream that can be used with the CA View batch utility, SARBCH, to delete all references to that specific tape sequence.

The *NOCAT error message appears in the VOLSER column alongside the tape sequence that is in error as follows:

  TSEQ DATA SET NAME                      VOLSER
 ----- ---------------------------------- ------
     9 VIEW.SYSTEM1.SARTAPE.T0000009      *NOCAT

To remove all references to this tape, execute the SARTSLST utility with the tape sequence number as a parameter along with the high‑level database name. Add a DD statement for the creation of the control statement stream as follows:

//STEP1   EXEC PGM=SARTSLST,PARM='VIEW.SYSTEM1,9'
//STEPLIB  DD  DISP=SHR,DSN=CAI.CVDELOAD
//CTLCARDS DD  DSN=SAR.CTLCARDS,DISP=(,CATLG),
//             UNIT=SYSDA,SPACE=(TRK,(1,1)),
//             DCB=(,DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD  SYSOUT=*

The execution parameter contains the CA View database high‑level name followed by a comma and the tape sequence number of the tape in error.

The file indicated by the CTLCARDS DD statement contains one control statement for each SYSOUT report referencing the bad tape. The control statement will be either a /CHANGE or /DELETE statement.

If the SYSOUT report is still on the disk database, a /CHANGE control statement is created. This statement resets the backup indication so the file can be written to a new tape during the next backup cycle.

If the SYSOUT is no longer on the database, a /DELETE control statement is created. This statement removes the reference of this SYSOUT report for the tape.

The following statements are samples of the control statements created by SARTSLST:

/DELETE   ID=REPORT1  GEN=27 SEQ=00005
/CHANGE   ID=REPORT2  GEN=27 SEQ=00007 BACKUP=OFF

These statements can be used as input to the CA View batch utility SARBCH as follows:

//STEP1    EXEC PGM=SARBCH,PARM='VIEW.SYSTEM1'
//STEPLIB  DD DISP=SHR,DSN=CAI.CVDELOAD
//SYSPRINT DD SYSOUT=*
//SYSIN    DD DSN=SAR.CTLCARDS,DISP=OLD

This action removes all references to the bad tape, allowing SARPAC to execute correctly.

Return Codes set by SARPAC messages

Return Code

Message

16

SARPAC02 Expanded retention was never initialized

16

SARPAC03 Master index is already in use

8

SARPAC05 Error on input tape

16

SARPAC06 Error on output tape

4

SARPAC10 No SYSOUT groups require consolidation

0

SARPAC11 xxxxx SYSOUT groups copied

16

SARPAC15 Data base at incorrect level for this release

16

SARPAC16 SORT failed with RC=XXXX

0

SARPAC20 SYSIN control cards governing this SARPAC

16

SARPAC21 No TAPESEQ= or STORGRP= found

16

SARPAC22 Invalid or extraneous control card found

16

SARPAC23 Storage group not defined in database

16

SARPAC24 Invalid tape sequence number specification or tape sequence number(s) not found in database

16

SARPAC52 ***WARNING*** Run SARPAC to copy tapes following merge of databases

16

SARPAC86 Syntax error in REPORT keyword parameter

None

SARPAC97 Invalid command "xxxx"

None

SARPAC98 SARPAC will terminate after the current report is processed

16

SARDBIxx Database I/O Error 16