Restore a Generation or Selecting SYSOUT

Use the SARTDR utility to recreate and reload an entire archival disk generation or to select SYSOUT entries from tape. Also, the utility will re-add archival and DR tape information to the master index.
view
Use the SARTDR utility to recreate and reload an entire archival disk generation or to select SYSOUT entries from tape. Also, the utility will re-add archival and DR tape information to the master index.
Note:
When a primary tape is added back to the database, it does not automatically add the associated duplex and/or DR tape. Be sure to run TADD with each of these tapes.
The utility can be used to recover one or more generations of SYSOUT data or select SYSOUT entries that have been lost because of:
  • Accidental deletion of a database data set
  • Hardware error resulting in the loss of a database data set
  • Accidental or intentional cycling out of a tape or disk generation from within CA View
Note:
Error-free archival tapes must exist for the generations.
The SARTDR utility does not require exclusive access to the database; it can run while other database activities such as archiving or backing up are occurring.
Tape consolidation (SARPAC) must be run on a merged database for all original tapes before SARTDR/TADD can be used. Never TADD an original tape to a merged database before you run SARPAC.
Job Control Statements
Sample execution JCL can be found in member HAEXTDR in your CVDEJCL data set.
These job control statements are necessary to execute SARTDR.
  • JOB
    Initiates the job.
  • EXEC
    Specifies the program name (PGM=SARTDR) and the high-level name of the database as the PARM parameter (PARM='VIEW.SYSTEM1').
  • STEPLIB DD
    Defines the load library containing SARTDR.
    If the program resides in a linklist library, omit this statement.
  • SYSPRINT DD
    Defines the sequential output data set (normally SYSOUT) used for listing the statements and messages.
    If not a SYSOUT data set, DCB=BLKSIZE=nnn must be coded, where nnn is a multiple of 133.
  • anyname DD
    Defines one archival tape to be re-added to the master index file.
    The ddname must match the one that is specified on the TADD control statement.
    A DD statement must be included for each archival tape to be re-added. Omit this DD statement if no archival tapes are to be re-added.
  • SYSIN DD
    Defines the card-image data set containing the control statements.
SARTDR Control Statements
Control statements have the following general structure:
/
function parameters
  • The slash is coded in column 1 and is immediately followed by the name of the function to be performed.
  • One or more blanks must follow the function name and separate the function name from the parameters.
    Individual parameters are separated by one or more blanks and/or commas.
  • A statement that exceeds 71 characters must be continued on additional statements.
    When you continue a statement, interrupt the statement only between complete parameters or subparameters.
  • Comments can be included in the control statements by coding an asterisk in column 1 of the card image containing the comment.
TADD
Use the TADD control statement to specify an archival tape that is to be re-added to the master index. This function can be used to re-add an entire archival tape or to re-add specific reports, generations, or resource groups from an archival tape that has cycled out of CA View.
TADD cannot be used to move a report from one database to another database. TADD can only be used to bring an archived report/sysout from tape back to disk on the same database where the report/sysout was archived.
For example, assume that you expected to keep 100 generations of SYSOUT on tape but you actually only kept 90 (NGENT=90). Any tapes containing SYSOUT data older than 90 generations ago could be re-added to the master index with this function, if the tapes had not been overwritten since they had been cycled out of CA View. Note that it is even possible to re-add an overwritten tape by salvaging it first with the SARTCP utility.
Syntax:
/TADD DDNAME=
xxxxxxxx
ID=(sysout-id,…) GEN=(gen,…) RESOURCE=(name,…). UNIT=uuuuuuuu STORGRP=ssssssss
where:
  • DDNAME=
    xxxxxxxx
    Specifies the name of the DD statement used to define the archival tape to be added to the master index.
  • ID=(sysout-id,…)
    Optionally specifies a SYSOUT identifier, generic SYSOUT identifier, or a list of SYSOUT identifiers to be re-added to the master index.
    A generic SYSOUT identifier is specified by suffixing a portion of the SYSOUT identifier with an asterisk. If the
    id
    contains embedded blanks, commas, equal signs, parentheses, or quotes, it must be enclosed in quotes (single or double). Any quotes in Report-id must be entered as a pair of quotes because a non-paired quote will end the ID. For example, if the value were JIM’S REPORT it must be entered as ‘JIM’’S REPORT’ or “JIM’S REPORT”.
  • GEN=(gen,…)
    Optionally specifies the archival generation number or a list of archival generation numbers for which SYSOUT is to be re-added to the master index.
    If SYSOUT and generation numbers are specified, only the SYSOUTs for the specified generations are added to the database.
  • RESOURCE=(name,…).
    Optionally specifies the name of a resource group or a list of resource groups to be re-added to the master index.
  • UNIT=uuuuuuuu
    Specifies an optional one- to eight-character unit name.
  • STORGRP=ssssssss
    Specifies an optional one- to eight-character storage group name.
Note:
STORGRP and UNIT must be specified if reports are to be eligible for Expanded Access Server of Tape (SAREAS).
After SARTDR TADD runs, you must run SARPAC on the recovered tape if you have the Expanded Access Server and you recovered the tape with SARTCP SKIP and NULL statements.
When the CA VIEW database has ARCHCHG=baseyear specified, SARTDR verifies the baseyear from the tape against the CA VIEW database baseyear. TADD processes the tape only if the two baseyears are the same. For example, if a tape was created from a database with a baseyear of 2000, and the CA VIEW database baseyear is 1980, the TADD will not be allowed.
Example 1
In this example, VIEW.SYSTEM1.SARTAPE.T0000011 is to be re-added to the master index. The name of the database is VIEW.SYSTEM1.
The following job is run:
//EXAMPLE JOB ACCOUNT,PROGRAMMER //STEP1 EXEC PGM=SARTDR,PARM='VIEW.SYSTEM1' //STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR //SYSPRINT DD SYSOUT=* //TAPEIN DD VOL=SER=T00033,UNIT=TAPE, // DSN=VIEW.SYSTEM1.SARTAPE.T0000011, // DISP=SHR //SYSIN DD * /TADD DDNAME=TAPEIN
Example 2
In this example, reports from archival generation 267 are re-added to the master index from tape VIEW.SYSTEM1.SARTAPE.T0000103.
The following job is run:
//EXAMPLE JOB ACCOUNT,PROGRAMMER //STEP1 EXEC PGM=SARTDR,PARM='VIEW.SYSTEM1' //STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR //SYSPRINT DD SYSOUT=* //TAPEIN DD VOL=SER=T00326,UNIT=TAPE, // DSN=VIEW.SYSTEM1.SARTAPE.T0000103, // DISP=SHR //SYSIN DD * /TADD DDNAME=TAPEIN GEN=267
TLOAD
Use the TLOAD control statement to reload an entire disk archival generation from tape, specific reports, specific resource groups, or the entire contents of a tape. SYSOUTs are reloaded regardless of where they were originally archived, that is, SYSOUT groups originally archived Direct-to-Tape are reloaded to disk during the TLOAD.
TLOAD cannot be used to move a report from one database to another database. TLOAD can only be used to bring an archived report/sysout from tape back to disk on the same database where the report/sysout was archived.
Before reloading a disk archival generation with this function, you must verify that:
  • All archival tapes required for the generation are known to the product. Any tapes not known to the product can be re-added with the SARTDR TADD control statement.
  • All archival tapes required for the generation are available and error free. The SARTCP utility can be used to salvage an archival tape containing errors.
Syntax:
/TLOAD ID=(
sysout-id
,…) GEN=(
gen
,…) RESOURCE=(
name
,…) TAPESEQ=
sssss
SECOND
where:
  • ID=(sysout-id,…)
    Optionally specifies a SYSOUT identifier, generic SYSOUT identifier, or a list of SYSOUT identifiers to be reloaded to primary or secondary disk.
    If the
    id
    contains embedded blanks, commas, equal signs, parentheses, or quotes, it must be enclosed in quotes (single or double). Any quotes in Report-id must be entered as a pair of quotes because a non-paired quote ends the ID. For example, if the value is JIM’S REPORT, it must be entered as ‘JIM’’S REPORT’ or “JIM’S REPORT”.
    A generic SYSOUT identifier is specified by suffixing a portion of the SYSOUT identifier with an asterisk.
  • GEN=(gen,…)
    Optionally specifies the archival generation number or a list of archival generation numbers for which SYSOUT is to be reloaded to primary or secondary disk.
  • RESOURCE=(name,…)
    Optionally specifies a resource group or a list of resource groups to be reloaded to disk.
    Note:
    Resource groups are never loaded to the secondary disk.
  • TAPESEQ=ssssss
    Specifies the tape sequence number of the backup tape for which SYSOUTs are to be reloaded to primary or secondary disk
    If the last SYSOUT on the requested tape spans multiple tapes, SARTDR requests additional tape mounts to reload the entire SYSOUT.
  • SECOND
    Specifies the SYSOUTs that are to be loaded to secondary (Optical, Centera, etc.,) disk rather than primary disk. Resource groups are never loaded to secondary disk. Resource groups on a tape are bypassed. SECOND requires all secondary disk initialization parameters be established before execution of the /TLOAD SECOND function.
If both the generation number
and
the tape sequence number are specified, SYSOUTS for the specified generation that reside on the specified tape are reloaded to primary or secondary disk.
Example 1
In this example, suppose generation 1221 is to be loaded back to primary disk from the archival tapes. The name of the database is VIEW.SYSTEM1.
The following job is run:
//EXAMPLE JOB ACCOUNT,PROGRAMMER //STEP1 EXEC PGM=SARTDR,PARM='VIEW.SYSTEM1' //STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD * /TLOAD GEN=1221 /*
Example 2
In this example, CA View backup tape VIEW.SYSTEM1.SARTAPE.T0000143 is to be loaded back to secondary disk. The name of the database is VIEW.SYSTEM1.
The following job is run:
//EXAMPLE JOB ACCOUNT,PROGRAMMER //STEP1 EXEC PGM=SARTDR,PARM='VIEW.SYSTEM1' //STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD * /TLOAD TAPESEQ=143 /*