Previous Topic: Example JCLNext Topic: Index Area (IXX) Reports

REPORT (Generate Reports) › Directory (CXX) Reports › Sample Report: REPORT CXX - Impact Report

Sample Report: REPORT CXX - Impact Report

Date: mm/dd/ccyy    ********************************************************************************         Page:     1
                    *                                 CA Datacom/DB                                *
Time: hh.mm.ss      *                                General Utility                               *      Release: 12
                    *                   Copyright © 2009 CA. All rights reserved.                  *               SPnn
                    ********************************************************************************
 
                    CONTROL CARD(S)
                    .........1.........2.........3.........4.........5.........6.........7.........8
       Π           REPORT AREA=CXX,TYPE=I,DBID=16
 
                    FUNCTION=REPORT
                      AREA=CXX
                       TYPE=I
                       DBID=16
 
 
       Ž
Œ

The command exactly as entered.



An analysis of keywords encountered and expected. Any errors found are flagged with a note in the left margin.

Ž

Any messages related to syntax processing.

Date: mm/dd/ccyy    ********************************************************************************         Page:     2
                    *                                 CA Datacom/DB                                *
Time: hh.mm.ss      *                                General Utility                               *      Release: 12
                    *                   Copyright © 2009 CA. All rights reserved.                  *               SPnn
                    ******************************************************************************** Directory: PRODCXX
 
                                  IMPACT REPORT
                        ‘    ’
  BASE        AREA        TABLE ID        DISPOSITION
                                            “        ”
  997        A01         C01  001        LOADED      (01)
                         C02  002        LOADED      (00)
                         F01  103        LOADED      (01)
                         F02  104        INDEX NOT LOADED (00)
                                                         KEY TST01 LOADED
                                                         KEY TST02 NOT LOADED
                         F03  105        LOADED      (01)
                         K01  240        LOADED      (00)
                         RNA  207        LOADED      (00)
                         RNB  208        LOADED      (01)


The DATACOM-ID of the database containing the area.



The DATACOM-NAME of the area.

‘

The table name.

’

The table ID.

“

The reason as listed in the table on page Processing a DDPROD Request.

The TYPE=I report has been enhanced to provide information about cases in which the disposition (as shown in the previously shown example) of a table is INDEX NOT LOADED. In those cases, further information is provided regarding key-level status, that is, whether each individual key in the table is LOADED or NOT LOADED. This Impact Report enhancement allows you to see, after a catalog, what actions occurred relating to the need to load tables. With Version 12.0, a major feature is the index-level loaded status. In the previously shown example, the key-level status is listed for two keys, TST01 and TST02, in a table (F02 104) whose disposition is INDEX NOT LOADED. The rest of the Impact Report is as it was in the previous release, that is, tables whose disposition is LOADED have no need to also show the Version 12.0 key-level status.

”

The code as listed in the table on page Processing a DDPROD Request.