List Active SYSOUTs

SARTSLST creates a list of SYSOUTs that are still active on a specific tape or a range of tapes. SARTSLST reads the disk database; it does not mount any tapes. SARTSLST lists the active SYSOUTs by the CA View archival or DR tape sequence numbers.
view
SARTSLST creates a list of SYSOUTs that are still active on a specific tape or a range of tapes. SARTSLST reads the disk database; it does not mount any tapes. SARTSLST lists the active SYSOUTs by the CA View archival or DR tape sequence numbers.
If a tape is unreadable or lost, you can use this utility to determine whether there were any active SYSOUTs on the tape.
Contents
Automatic Re-Backup or Delete
You can code the CTLCARDS DD statement with the SARTSLST job to have SARTSLST automatically generate SARBCH input control statements to clean up a lost tape from the database.
Be aware of the following:
  • If the SYSOUT still has an active primary disk copy, a SARBCH CHANGE statement is created to mark the SYSOUT as not backed up, and the next backup cycle makes a new backup.
  • If the SYSOUT has no active primary disk copy, a SARBCH DELETE statement is created to delete the SYSOUT from the database.
Note:
Do not use SARTSLST if you use tape duplexing, and a duplex tape is available and readable. If the duplex tape was created with 3420 processing, you can use the SARTCP utility to recreate a primary copy from the duplex tape, and no database recovery is needed.
Recovering from *NoCat Tape Errors
The Not Cataloged (*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 you can use is to remove all database references to that tape.
The Group Control Record (GCR) for SYSOUT reports that exist only on the tapes that are no longer available must be deleted. This can be done from the Sysout Selection panel using the DELETE function, but the most convenient way to delete GCR records is to use the CA View utilities. The Tape List utility SARTSLST can be executed against the tape sequence number for a tape in error.
The 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 which 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=SAR.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=*
where 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 pointed to by the CTLCARDS DD statement contains one control statement for each SYSOUT report referencing the bad tape. The control statement is 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=SAR.CVDELOAD //SYSPRINT DD SYSOUT=* //SYSIN    DD DSN=SAR.CTLCARDS,DISP=OLD
This job removes all references to the bad tape, allowing SARPAC to execute correctly.
Job Control Statements
Sample execution JCL can be found in member HAEXTLST in your CVDEJCL data set.
These job control statements are necessary to execute SARTSLST:
  • JOB
    Initiates the job.
  • EXEC
    Specifies the program name (PGM=SARTSLST).
    The PARM parameter specifies the high-level name of the database, and the tape sequence number or a range of tapes to look up.
    Examples:
    • PARM= 'VIEW.SYSTEM1,14'
      Lists active reports on archival tape 14.
    • PARM= 'VIEW.SYSTEM1,5-100'
      Lists active reports on archival tapes 5 through 100.
    • PARM= 'VIEW.SYSTEM1,10-20,DR'
      Lists active reports on DR tapes 10 through 20.
  • STEPLIB DD
    Defines the load library containing SARTSLST.
    If the program resides in a linklist library, omit this statement.
  • SYSPRINT DD
    Defines the sequential output data set (normally SYSOUT) into which the listing of uncataloged tapes is written.
    If not a SYSOUT data set, DCB=BLKSIZE=nnn must be coded, where nnn is a multiple of 133.
  • SYSUDUMP
    Defines a file for MVS dump output.
  • CTLCARDS
    Specifies the creation of SARBCH statements to take action on the SYSOUT: the action is to either back it up again or delete it if there is no disk copy.