Reports (TSSAFR1)

TSSAFR1 produces the following extraction reports:

BMC AMI FAST PATH RECOVERY FOR IMS MESSAGES report

The BMC AMI FAST PATH RECOVERY FOR IMS MESSAGES report, shown in the following figure, provides information about the parameters and options specified for a recovery:

DATE: 96/06/02   TIME: 18:06 BMC AMI FAST PATH RECOVERY FOR IMS MESSAGES (TSSAFR1 REL:4.2)

TSSA0101I - RECOVERY UTILITY PARAMETERS:
            - SUBSYS : OLBA
            - DBRC   : YES
            - RDS    : YES
            - DEDB   :   4
            - MSDB   : YES
            - PSBLIST: YES
            - LOGSEQ : YES
            - TBLENT : 500

TSSA0102I - RDS SELECTED: IMSRDS

TSSA0103I - DEDB RECOVERY CHECKPOINT-ID: 94020/1316268

TSSA0104I - RECON DATASET SELECTED: RECON2

TSSA0105I - DEDB RECOVERY LOG DATASET LIST:
            -TYPE      ----OPEN----- ----CLOSE---- VOLSER DSNAME
             PRIOLDS   94020 1316241 94020 1414140          CLD991.TD.QFR.OLDSP09

TSSA0140I - MSDB DATASET SELECTED: MSDBCP1

TSSA0143I - MSDB RECOVERY CHECKPOINT-ID: 94020/1256019

TSSA0145I - MSDB RECOVERY LOG DATASET LIST:
            -TYPE     ----OPEN----- ----CLOSE---- VOLSER DSNAME
             PRIOLDS 94020 1243486 94020 1257432        CLD991.TD.QFR.OLDSP07
             PRIOLDS 94020 1257432 94020 1316241        CLD991.TD.QFR.OLDSP08
             PRIOLDS 94020 1316241 94020 1414140        CLD991.TD.QFR.OLDSP09

TSSA0147I - PROCESSING SUMMARY:
            - NO. LOG RECORDS READ           :     9,392

            - NO. LOG RECORDS USED (4084)   :        17
            - NO. LOG RECORDS USED (4086)   :        29
            - NO. LOG RECORDS USED (4087)   :         7
            - NO. LOG RECORDS USED (4098)   :         1
            - NO. LOG RECORDS USED (5921)   :         0
            - NO. LOG RECORDS USED (5922)   :         0
            - NO. LOG RECORDS USED (5923)   :         0
            - NO. LOG RECORDS USED (5950)   :     2,902
            - NO. LOG RECORDS USED (5953)   :         0

            - NO. LOG RECORDS USED ( 07 )   :         0
            - NO. LOG RECORDS USED ( 08 )   :         0
            - NO. LOG RECORDS USED ( 37 )   :         0
            - NO. LOG RECORDS USED ( 41 )   :         0
            - NO. LOG RECORDS USED ( 47 )   :         1
            - NO. LOG RECORDS USED ( 50 )   :         0

The BMC AMI FAST PATH RECOVERY FOR IMS MESSAGES report includes the following information:

Segment	Description
RECOVERY UTILITY PARAMETERS	Parameters that are in effect for this execution of the utility
RDS SELECTED	Name of the selected restart data set
DEDB RECOVERY CHECKPOINT-ID	Selected or specified Checkpoint ID that is used as the starting point for DEDB recovery
RECON DATASET SELECTED	ddname of the RECON data set that is selected or specified
DEDB RECOVERY LOG DATASET LIST	List of the log data sets required for DEDB recovery. This list is not reported if DBRC=NO is specified and log data sets are provided through DD statements.
MSDB DATASET SELECTED	Name of the MSDB data set selected
MSDB RECOVERY CHECKPOINT-ID	Selected Checkpoint-ID that must be used as the starting point for MSDB recovery
MSDB RECOVERY LOG DATASET LIST	List of the log data sets that are required for MSDB recovery. This is not reported if DBRC=NO is specified.
PROCESSING SUMMARY	Total log records read and log records of each type selected

DEDB AREA STATUS REPORT

The DEDB AREA STATUS REPORT, shown in the following figure, provides information about the status of each DMAC that is defined to the IMS/VS system at the time of a system failure:

DATE: 96/06/02   TIME: 18:06    DEDB AREA STATUS REPORT             (TSSAFR1 REL:4.2)

DBDNAME AREA# DMACNAME FILE# AREADDN STATUS                                  AREA DATASET NAME
-------- ----- -------- ----- -------- ------------------------------------ -----------------

ZBCMA00D    1 ZBCMA01D    1 ZBCMA01D RECOVERY RECORDS GENERATED (      1) IOBV01A.ZBCMA01D

ZBCMB00D    1 ABCMB01D    2 ZBCMB01D RECOVERY RECORDS GENERATED (      1) IOBV01A.ZBCMB01D

ZDDAA00D    1 ZDDAA01D                NOT USED/INITIALIZED
ZDDAA00D    2 ZDDAA02D                NOT USED/INITIALIZED
ZDDAA00D    3 ZDDAA03D                NOT USED/INITIALIZED
ZDDAA00D    4 ZDDAA04D                NOT USED/INITIALIZED
ZDDAA00D    5 ZDDAA05D                NOT USED/INITIALIZED
ZDDAA00D    6 ZDDAA06D                NOT USED/INITIALIZED
ZDDAA00D    7 ZDDAA07D                NOT USED/INITIALIZED
ZDDAA00D    8 ZDDAA08D                NOT USED/INITIALIZED
ZDDAA00D    9 ZDDAA09D                NOT USED/INITIALIZED
ZDDAA00D   10 ZDDAA10D                NOT USED/INITIALIZED
ZDDAA00D   11 ZDDAA11D                NOT USED/INITIALIZED
ZDDAA00D   12 ZDDAA12D                NOT USED/INITIALIZED
ZDDAA00D   13 ZDDAA13D                NOT USED/INITIALIZED
ZDDAA00D   14 ZDDAA14D                NOT USED/INITIALIZED
ZDDAA00D   15 ZDDAA15D                NOT USED/INITIALIZED
ZDDAA00D   16 ZDDAA16D                NOT USED/INITIALIZED
ZDDAA00D   17 ZDDAA17D                NOT USED/INITIALIZED
ZDDAA00D   18 ZDDAA18D                NOT USED/INITIALIZED

ZLONA00D    1 ZLONA01D    3 ZLONA01D RECOVERY RECORDS GENERATED (      5) IOBV01A.ZLONA01D
ZLONA00D    2 ZLONA01D    4 ZLONA02D RECOVERY RECORDS GENERATED (      1) IOBV01A.ZLONA02D
ZLONA00D    3 ZLONA01D    1 ZLONA03D RECOVERY RECORDS GENERATED (      3) IOBV01A.ZLONA03D
ZLONA00D    4 ZLONA01D    2 ZLONA04D RECOVERY RECORDS GENERATED (      1) IOBV01A.ZLONA04D

ZNACA00D    1 ZNACA01D    3 ZNACA01D RECOVERY RECORDS GENERATED (      1) IOBV01A.ZNACA01D

ZPDAA00D    1 ZPDAA01D    4 ZPDAA01D RECOVERY RECORDS GENERATED (      6) IOBV01A.ZPDAA01D
ZPDAA00D    2 ZPDAA02D    1 ZPDAA02D RECOVERY RECORDS GENERATED (     11) IOBV01A.ZPDAA02D
ZPDAA00D    3 ZPDAA03D    2 ZPDAA03D RECOVERY RECORDS GENERATED (     21) IOBV01A.ZPDAA03D

The DEDB AREA STATUS REPORT includes the following information:

Segment	Description
DBDNAME	DBD name of the database in which the area is defined
AREA#	Associated area number
DMACNAME	DMAC name of the area
FILE#	File number ( DEDBnn) of the file containing any DEDB recovery records that were generated
AREADDN	Area ddname. For areas registered with DBRC, this name is the ddname that is registered in DBRC. For areas that are not registered with DBRC, this name is the ddname that is in the DBD (DD1).
STATUS	DMAC status can be one of the following states: NOT USED/INITIALIZED—The area data sets (ADSs) associated with this DMAC were not opened before the IMS system failure. Because the ADSs were not open, they do not require recovery. CLOSED PRIOR TO IMS FAILURE—ADSs were closed successfully before the IMS system failure. They do not require recovery. NOT UPDATED - RECOVERY NOT REQUIRED—ADS(s) were open in read only mode, or they were opened after the selected Checkpoint-ID, but were not updated. RECOVERY RECORDS GENERATED (Z,ZZZ,ZZ9)—The area was open and had been updated. The count of the number of DEDB update records generated is provided. At least one recovery record is built for any DMAC that was open when the checkpoint was taken. This record contains the DMAC information.
AREA DATASET NAME	Name of the ADS used

DEDB OUTPUT FILE Control REPORT

The DEDB OUTPUT FILE Control REPORT, shown in the following figure, provides information about the number of recovery records that are written to each output file for each DEDB area:

DATE: 96/06/02 TIME: 18:06      DEDB OUTPUT FILE Control REPORT TSSAFR1 REL:4.2)

FILE DDNAME DBDNAME AREA# DMACNAME #ADS'S #RECORDS #Control   #REJECTS
----------- -------- ----- -------- ------ --------- -------- --------

    DEDB01   ZBCMA00D    1 ZBCMA01D     1           1        1     N/A

             ZLONA00D    3 ZLONA03D     1           3        1     N/A

             ZPDAA00D    2 ZPDAA02D     1          11        1     N/A
             ZPDAA00D    6 ZPDAA06D     1          11        1     N/A
             ZPDAA00D   10 ZPDAA10D     1          21        1     N/A
             ZPDAA00D   14 ZPDAA14D     1         139        1     N/A
             ZPDAA00D   18 ZPDAA18D     1          21        1     N/A

             ZSAVA00D    2 ZSAVA02D     1          11        1     N/A
             ZSAVA00D    6 ZSAVA06D     1           1        1     N/A
             ZSAVA00D   10 ZSAVA10D     1          20        1     N/A
             ZSAVA00D   14 ZSAVA14D     1          68        1     N/A
             ZSAVA00D   18 ZSAVA18D     1           6        1     N/A

             ZTELA00D    3 ZTELA03D     1          44        1     N/A
             ZTELA00D    7 ZTELA07D     1          73        1     N/A
             ZTELA00D   11 ZTELA11D     1          56        1     N/A
             ZTELA00D   15 ZTELA15D     1          39        1     N/A

             ZTRMB00D    3 ZTRMB03D     1         114        1     N/A
             ZTRMB00D    7 ZTRMB07D     1          94        1     N/A
             ZTRMB00D   11 ZTRMB11D     1         138        1     N/A
                                              -------- ------- ------
             *** FILE TOTALS ***                   871              871

The DEDB OUTPUT FILE Control REPORT includes the following information:

Segment	Description
FILE DDNAME	ddname of the output file
DBDNAME	DBD name of the database that is being recovered
AREA#	Area number of the ADS that is being recovered
DMACNAME	DMAC name of the area that is being recovered
#ADS’S	Number of ADS that must be updated for this area
#RECORDS	Total number of DEDB recovery records that are generated for this area
#Control	Total number of control records generated for this file. The file total might be greater than the sum of the number of records generated for each DBD. This difference is caused by the presence of extraneous recovery records that are ignored by TSSAFR2 (for example, records written for an area that was subsequently closed by IMS). The file total does not match the number of records processed by the Sort. This difference is caused by the presence of area allocation records (required by TSSAFR2) that are not included in the record counts.
#REJECTS	Total number of reject records that are generated for this file. The number is the same for all DEDBnn files.

ACTIVE REGIONS AT TIME OF ABEND report

The ACTIVE REGIONS AT TIME OF ABEND report, shown in the following figure, provides a list of all PSTs that are active at the time of abend. It is generated only if PSBLIST=YES is specified. It is used to identify PSBs that require full-function backout:

DATE: 96/06/02    TIME: 18:06 ACTIVE REGIONS AT TIME OF ABEND (TSSAFR1 REL:4.2.0) PAGE: 1

REGI PSBNAME TRANCODE COMMENT          DBD LIST CHKPT-ID TIMESTAMP    JOBNAME   STEPNAME PGMNAME
---- ------- -------- ---------------- -------- -------- ----------- -------- -------- --------

    2 POLB0000         BACKOUT NOT REQUIRED

    3 POLB0000         BACKOUT NOT REQUIRED

    4 POLB0000         BACKOUT NOT REQUIRED

    5 POLB0000         BACKOUT NOT REQUIRED

    6 POLB0000         BACKOUT NOT REQUIRED

    7 TLON0001         BACKOUT REQUIRED     ZLONACCT
                                             ZLONCTL1
                                             ZLONHIST

    8 POLB0001         BACKOUT NOT REQUIRED

       POLB0001         BACKOUT NOT REQUIRED

   10 POLB0001         BACKOUT NOT REQUIRED

   11 POLB0001         BACKOUT NOT REQUIRED

   12 TOLBSCAN         BACKOUT NOT REQUIRED

The ACTIVE REGIONS AT TIME OF ABEND report includes the following information:

Segment	Description
REGI	Active region ID
PSBNAME	Name of the PSB that was active
TRANCODE	Name of the transaction that was active
COMMENT	The status of the PSB/transaction can be one of the following states: BACKOUT REQUIRED BACKOUT MAY BE REQUIRED BACKOUT NOT REQUIRED NO ACTIVE PROGRAM
DBD LIST	Names of all DBDs referenced by the PSB/transaction. DD statements for these DBDs must be provided to the backout utility.
CHKPT-ID	If the region contained a batch message processing (BMP) program, this field contains the ID of the last completed checkpoint
TIMESTAMP	If the region contained a BMP that issued symbolic checkpoints, this field contains the date and time of the last completed checkpoint
JOBNAME	Job name of the BMP that issued the symbolic checkpoint call
STEPNAME	Step name of the BMP that issued the symbolic checkpoint call
PGMNAME	Program name of the BMP that issued the symbolic checkpoint call