Skip to content
CA Datacom Core - 15.1
Documentation powered by DocOps

Directory (CXX) Reports

Last update April 26, 2019

The REPORT function provides several types of reports containing information about the contents of the Directory.

  • The Directory (CXX) Report shows the current status and control information for the Index, database, area, table, key, element, and special fields.
  • The Directory (CXX) Report with TYPE=B shows the current status and control information for the index, database, area, and table. It excludes information for key, element, and special fields.
  • The Space Utilization Report (selected by using the TYPE=A keyword) provides information about total tracks, records, blocks, and maximum percentages of block utilization and the space reclamation option specified.
  • The Directory (CXX) Report with TYPE=I shows the impact report of the table status results of the last CA Datacom® Datadictionary™ catalog of the database.
  • The Directory (CXX) Report with TYPE=K shows the full CXX options in place and also provides information about encryption as defined to the CXX and tables.
  • The Directory (CXX) Report with TYPE=P shows the current list of PREINIT data sets that are available for use during creation of a new:
    • database
    • index area
    • data area
  • The Directory (CXX) Report with TYPE=Z shows the optional CXX internal history entries that are activated using DBUTLTY CXXMAINT OPTION=ALTER,OPTION2=HIST00NN.
Note: You can obtain most of the CXX information in real time through SQL access to special system tables. These dynamic tables allow easy access of the data from any platform while the MUF is running. 

The following topics are discussed on this page:

When to Use

Use the information provided in a full Directory (CXX) Report to verify the current status and definitions currently in use. Use the space utilization option of the Directory Report to monitor space in your Directory, data, and Index areas. You can generate a Directory Report at any time for types A, B, K and Z. Type I requires the MUF to be enabled. For types A, B, and K the following apply:

  • If using Simplify mode and the MUF is enabled:
    The MUF is used for all completely current information. An internal COMM STATS is generated for each data base reported to update the CXX.
  • If using Simplify mode and the MUF is down:
    The report always expects to run with the MUF enabled. If not enabled, it expects to wait for the enable with the DELAY68 option of DBSIDPR. It may follow any previous function that runs with MUF only down or a function that sets execution to run without MUF using SET OPTION1= MUF_NOT_ENABLED. We do not recommend (but it is possible to use) function SET OPTION1=MUF_ENABLED_OR_DISABLED. If executed with the MUF down, the following section applies.
  • If not using Simplify mode or the MUF is down:
    The Directory (CXX) reports read and reflect the information from the CXX data set. This information is correct when the database is not currently open by the MUF or any Single User jobs, including DBUTLTY. Even when it is open, the information is usually adequately current. If opened by the MUF, the information can be made more accurate by executing the COMM STATS option prior to the report, because executing COMM STATS refreshes the data in the data set. The utility does not interact with the MUF.
    it is unlikely but possible for a return code 04 INVALID RECORD ID, with an internal return code of 47, to occur if maintenance is occurring at the same time the report is executing. Maintenance in this case includes the catalog of a database or SQL DDL processing. If this happens, the report should be executed again.

How to Use

You can execute this command in either Single User or with the MUF active.

Use the following control statement to request this report either with no TYPE= keyword or for types A and B. They have an optional DBID specification and optional TABLE specification:

                     ┌───────────────────────┐
►►─ REPORT AREA=CXX ─▼─┬───────────────────┬─┴─┬───────────┬──┬──────────────┬──►◄
                       ├─ ,DBID=nnnn ──────┤   ├─ ,TYPE=A ─┤  └─ ,TABLE=ttt ─┘
                       └─ ,DBID=nnnn-nnnn ─┘   └─ ,TYPE=B ─┘


Use the following control statement to request this report for types I and Z with an optional DBID specification:

                     ┌───────────────────────┐
►►─ REPORT AREA=CXX ─▼─┬───────────────────┬─┴──┬─ ,TYPE=I ─┬───────────────────►◄
                       ├─ ,DBID=nnnn ──────┤    └─ ,TYPE=Z ─┘   

                       └─ ,DBID=nnnn-mmmm ─┘


Use the following control statement to request this report for types K and P:

►►─ REPORT AREA=CXX ─┬─ ,TYPE=K ─┬─────────────────────────────────────────►◄
                     └─ ,TYPE=P ─┘

Command

  • REPORT
    Invokes the function to produce a report.

Required Keywords

  • AREA=CXX
    Requests the Directory Report.

Optional Keywords

  • ,DBID=
    DBID= is optional and may repeat (except not allowed with TYPE=K andf TYPE=P). Each occurrence may specify one valid database ID or a range of DBIDs nnnn-mmmm (a range, for example, such as 100-250).
    If DBID= is not specified, all databases are processed. That is, if a report is done without a DBID, the first page of the CXX report (without any TYPE= or with TYPE=K) has information about the full CXX.
    Every database specified by a DBID keyword is processed. Each database that is not defined, generates an error and fails the function after all the databases are processed. However, a database in a range not defined is ignored.

    Note: The DBID is not allowed for TYPE=K and TYPE=P executions.
  • ,TABLE=
    TABLE= is optional for TYPE=A, TYPE=B, and no TYPE= specified functions. With the keyword set only matching table names are printed. With TYPE=A the only the area line for the data area including the table is printed. Without TYPE=A the database and index information are not printed. It works the same if the DBID= keyword is also specified where only the one table in all qualified DBID(s) will be printed.
  • TYPE=A
    Specifies the Space Utilization Report be generated. Omitting this parameter produces a full Directory report. For more information on the TYPE=A report, see Type A - Directory Space Utilization.
  • ,TYPE=B
    Specifies a full report without key, element, and special fields. For more information on the TYPE=B report, see Type B - CXX Report.
  • ,TYPE=I
    Specifies the Impact Report be generated. Omitting this parameter produces a full Directory report. For more information on the TYPE=I report, see Type I - Impact Report.
  • ,TYPE=K
    Specifies the page one of a full CXX report (no TYPE= or TYPE=B) be produced with the addition of any Encryption information provided for the CXX in general and tables with any form of Encryption specified. For more information on the TYPE=K report, see Type K - Encryption Report.
  • ,TYPE=P
    Specifies the PREINIT data set report be generated. For more information on the TYPE=P report, see Type P - PREINIT Report.
  • TYPE=Z
    Specifies the CXX internal history entries currently saved (if any). For more information on the TYPE=Z report, see Type Z - CXX internal history Report.

Full Directory Report

To obtain current status and control information, generate a full Directory Report.

Example JCL Full CXX Report

The following example shows the command to generate a full Directory Report.

Note: Use the following as a guide to prepare your JCL. The JCL statements are for example only. Lowercase letters in a statement indicate a value you must supply. Code all statements to your site and installation standards.

 //jobname    See the previous note and JCL Requirements.
 //       EXEC PGM=DBUTLTY,REGION=2M
 //STEPLIB    See the previous note and JCL Requirements.
 //CXX      DD DSN=cxx.data.set,DISP=SHR           Directory data set
 //SYSIN    DD *                                   Command Input
         REPORT   AREA=CXX
 /*

Sample Report

The following is a sample report page. For an example report header, see Sample Report Headers.

Sample Report REPORT CXX - Full   

If a report is done without a DBID, the first page of the CXX report (without any TYPE= or with TYPE=K) has information about the full CXX. In the following example, a full CXX Report (without a DBID specified) displays the report. This same report information is provided with the TYPE=K report, except the TYPE=K report includes any encryption information (not provided below).

CONTROL AREA DIRECTORY                                      CXX VERSION - 15.0
DBCRBAS REQUIREMENT (ALL BASES OPEN)  -    76,728           CXX ENQ - SYSPLEX
NUMBER OF DATA BASES -    32                                DATA HIGH USED MARK - YES
DEVICE TYPE - 3390                                          DATASET EXTENT VALIDATION - YES
DYNAMIC FILE ALLOCATION ALLOWED - YES                       DATA FAST SEARCH - YES
SECURE USING JOBNAME - NO                                   CXX LEVEL -   1                      HISTORY CXX  -    1
SECURE ALLOWING SINGLE USER - NO                            SINGLE USER ALLOWED - NO
SQL MODE - SUPPORT ACTIVE - YES                             SIMPLIFY MODE - YES
           DATADICTIONARY BASE -     2
           DATA DEFINITION DIRECTORY BASE -     15          PREINIT AREAS - YES                  ALLOW_TA24  - YES

The following is a sample full CXX report showing partitioning for, in this example, a database with a DBID of 999.

Note: This example shows a few sample pages of the report. An actual report could of course be longer, continuing for as many pages as necessary.

                    CONTROL CARD(S)
                    .........1.........2.........3.........4.........5.........6.........7.........8
                    REPORT AREA=CXX,DBID=999
 
                    FUNCTION=REPORT
                       AREA=CXX
                       DBID=00999

This page of the report shows the following:

  • 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.

DATA BASE INFORMATION
 
DBCRBAS REQUIREMENTS FOR THIS BASE -     2,392  
DBCRKEL REQUIREMENTS FOR THIS BASE -     4,128 
NUMBER OF AREAS IN THIS BASE    -       3 
NUMBER OF TABLES IN THIS BASE   -       9     
NUMBER OF KEYS IN THIS BASE     -      33 
NUMBER OF ELEMENTS IN THIS BASE -       9 
LAST OPENED     - DATE--mm/dd/ccyy, TIME-hh.mm.ss
LAST RESTARTED  - DATE--mm/dd/ccyy, TIME-hh.mm.ss
LAST MAINTAINED - DATE--mm/dd/ccyy, TIME-hh.mm.ss
REPLICATED BASE  -  NO                                 BASE FORMAT -   3  
PARTITIONED BASE -  NO                                                        
UPDATE USERS    -   0  
READ ONLY USERS -   0 
OCCURRENCE - TOBIE_DATABASE_PTN P001 
SQL SECURITY -     NO 
 
INDEX INFORMATION  - IXX
DEVICE TYPE  -    3390                                  DYNAMIC EXTEND -    YES 
BLOCK LENGTH -   4,096                                  DYN.EXT.TRACKS -     15 
LEVELS         -     1                                  OLDEP          -    YES 
BLOCKS/TRACK -      12                                  CXXMAINT LINK  -    YES 
BLOCKS IN USE -      3                                  SECONDARY CYLS -      0 
BLOCKS UNUSED -     57                                  INDEX FORMAT   -      1 
TOTAL BLOCKS  -     60  
TOTAL TRACKS  -      5 
PERCENT FULL  -      5 
DATA SET NAME - JBND007.IXX5000                         INDEX DTF/DDNAME - IXX5000 
VOLUMES       - WRKD26          

This page of the report shows the following:

Database Information

  • DBCRBAS reports the number of bytes required to hold the control information for this database in memory when it is open. For information only. DBCRKEL reports the number of bytes required to hold all the key and element definitions for this database.
  • NUMBER OF ... IN THIS BASE is the count of the active areas, tables, keys, and elements in this database. If a key ID exists in more than one table, it is counted once for each table in which it occurs.
  • These fields report activity involving this database:
    • LAST OPENED
      Date and time of the last User Requirements Table open. If the table is currently open for read-only, the date and time can reflect a previous open for update. If the table was opened by multiple tasks concurrently, the date and time can reflect any of the tasks.
    • LAST RESTARTED
      Date and time of the last RESET CXX for this database.
    • LAST MAINTAINED
      Date and time that this database definition was last cataloged or maintained using the CXXMAINT options, except the ALTER option.

      Note: Certain SQL DDL statements update the CXX (such as CREATE TABLE, CREATE INDEX, and so on) and modify this date. Since these occur internally, you might not realize that the CXX has been updated on the date and time reflected in this field.
  • REPLICATED and PARTITIONED BASE indicate whether the database is CA Datacom® STAR replicated or partitioned.
  • BASE FORMAT is a number indicating feature support. If the database has been opened by Version 15.0, the number displayed is a 3. If the database has not been opened by Version 15.0, the number displayed can be a 1 or a 2, as was used by prior versions.
  • UPDATE USERS reports if the base is currently owned (locked) by a copy of CA Datacom®. A zero number means not owned, a not zero is owned. Without Simplify mode, the only number used is a 1. With Simplify, it may be a 2, indicating Simplify owned by DBUTLTY; a 3, indicating Simplify owned by MUF not for Single User DBUTLTY functions; or a 4, indicating Simplify owned by MUF for Single User DBUTLTY functions.
  • READ ONLY USERS reports zero (none) or one (one or more) if the database is opened in MUF without ACCESS=OPTIMIZE and all open URTs specified UPDATE=NO.
  • OCCURRENCE is the entity-occurrence name for the database, and the status/version in CA Datacom® Datadictionary™.
  • SQL SECURITY indicates whether SQL Security has been selected for the tables in this database. See Administrating for more information about security.
  • The INDEX INFORMATION - IXX heading indicates the start of the index information for the IXX Index Area. The IXX is always the first (or only) index area. If this database has a Multi-Dataset Index, after the information for the IXX, information is provided about each additional index area.
  • DEVICE TYPE and BLOCK LENGTH report the type of device containing this Index Area (IXX) and the block size chosen by CA Datacom®/DB for this Index Area.

    Note: When the Index Area or data area has not been INITed, the DEVICE is blanks.
  • LEVELS is the count of the number of high-level Index levels. See Administrating for information about the CA Datacom®/DB Index structure.
  • These lines report the space utilization for this Index Area:
    • BLOCKS /TRACK
      Number of Index blocks per track.
    • BLOCKS IN USE
      Number of Index blocks in use. Two blocks are always reserved for CA Datacom®/DB control information. If a system failure has occurred during processing, this number can be inaccurate.
    • BLOCKS UNUSED
      Count of the completely empty blocks in the Index. If a system failure has occurred during processing, this number can be inaccurate.
    • TOTAL BLOCKS
      Total blocks used by the Index.
    • TOTAL TRACKS
      Total tracks used by the Index.
    • PERCENT FULL
      Number of used blocks divided by total blocks. The value reported is an even percent. Decimals are truncated. If a system failure has occurred during processing, this number can be inaccurate.
  • DATA SET NAME is the data set name, if it is known. If the data set name is reported, a VOLUMES entry is included with volume serial numbers displayed. If necessary, multiple VOLUMES entries may be listed with 10 volume serial numbers per entry. The REPORT function obtains the volume serial numbers by issuing a catalog locate. If the locate fails, the locate return code is displayed.
  • DYNAMIC EXTEND is specified as YES or NO for the Index Area.
  • For DYN.EXT.TRACKS - n, the n provides that dynamic extend, whether set or not, is defined in tracks and not cylinders. If defined in cylinders, the field shows DYN.EXT.CYLS - n.

    Note: If DYNAMIC EXTEND is specified as YES and this is zero, the VTOC secondary allocation is used.
  • CA Datacom® has taken advantage of enhancements to z/OS environments to allow dynamic extend to be greater than 64K tracks.
  • OLDEP refers to old entry points. When OLDEP=NO is specified, the DBNTRY entry point is the only entry point supported. For more information about the OLDEP= keyword, see INIT IXX (Format Index Area).
  • CXXMAINT LINK provides the current setting of the CXXMAINT option of LINK=YES/NO. Set to YES, the default and recommended option, the open of the area validates that the CXX name, in the data set opened, is the same as the CXX name in the executing CXX. This edit protects users from confusing production and test data sets. Set to YES, the default and recommended option, the open of the area will cause validation that the CXX name in the data set opened is the same as the CXX name in the executing Directory (CXX). This edit is to protect users from confusing production and test data sets.
  • SECONDARY CYLS, the JCL secondary allocation value, is useful when using dynamic extends with the extend value not set in CA Datacom® Datadictionary™. SECONDARY CYLS is the size that is used by MVS. The size reported is the size that existed the last time the area was opened when the database was opened for update. During a dynamic extend, the size is subject to the data set having a specific JCL DD statement with a different secondary.
    The secondary allocation is only reported in cylinders. If the allocation was done in an average block, the secondary size from the JCL is converted into tracks (rounding down) and then into cylinders (rounding down). If the allocation was done in tracks, the secondary size from the JCL is converted into cylinders (rounding down). Therefore, a value reported as 0 (zero) could mean no secondary or a secondary of a size less than a full cylinder.
    The SECONDARY CYLS size is subject to a CXX BACKUP function and restored with the database restore. The information is not disabled if input into a previous release of CA Datacom® then subjected there to a backup before being restored into a Version 15.0 CXX. If the information is not currently correct, it is corrected the next time the data set is opened for update. This information is not intended to be a replacement for other Operating System tools that provide the secondary allocation in more detail. The number reported has a maximum size of 64k-1 (65535). This number reflects a size of 65535 and all larger sizes.
    When the DASD data set is not defined as temp or virtual, the SECONDARY CYLS value is updated each time the DASD data set is opened. The SECONDARY CYLS value is also updated each time the DASD data set is opened when opening the database for update, including when using SIMPLIFY mode or ACCESS OPTIMIZE.
    A blank (nothing displayed) is shown for SECONDARY CYLS if any of the following is true:
    • The data set has never been opened after Version 15.0 code was installed
    • The data set was opened without the database being opened for update.
    • The area was opened in MUF and defined as VIRTUAL.
    • The area was opened for update but was defined in the JCL as a TEMP data set, that is, a DSN starting with two ampersands (&&).
  • INDEX FORMAT is a number indicating feature support. Currently, the number is always 1. A future planned feature will have a value of 2.
  • INDEX DTF/DDNAME - IXX5000 provides the DTF name or DD name that is used by CA Datacom® to open this index area. The name is not an option.

TABLE NAME - C01  PARTITION - K01 2/3                 AREA NAME  - P02                       
OCCURRENCE - TOBIE_C01_997 P001                       OCCURRENCE - TOBIE_AREA_997 P001       
TABLE ID   -    1                                     AREA SQLNAME - TOBIE_AREA_997      
RECORD LENGTH    -     84 /     96                    BLOCK LENGTH      -       8,192            SLACK -   0     
RECORDS IN TABLE -          59,851                    OVERFLOWS IN AREA -     357,161                            
LENGTH OF KEY/ELEMENTS -  1,088                       BLOCKS IN USE -     1,674          HIGH USED TRACK -   320 
NUMBER OF KEYS        -       1                       BLOCKS UNUSED -       576                                  
NUMBER OF ELEMENTS    -       1                       TOTAL BLOCKS  -     2,250          CXXMAINT LINK  -    NO  
CHANGE MASTER KEY    - YES                            TOTAL TRACKS  -       375          DYNAMIC EXTEND -    YES 
DUPLICATE MASTER KEY - YES                         PERCENT FULL  -           74          DYN.EXT.TRACKS -      0 
RECOVER  - YES  ENCRYPTION - NONE                  DEVICE TYPE  -    3390                SECONDARY CYLS -
LOGGING  - YES                                        BLOCKS/TRACK -   12
PIPELINE - YES                                      DSOP MODE    - NO RECLAMATION 
DB COMPRESSION   - NO                              TABLE LOADED - YES, DATE--mm/dd/ccyy, TIME-hh.mm.ss  
USER COMPRESSION - NO                                 INDEX LOADED - YES                                 
CLUSTER KEY ID     -   0                              DATADICTIONARY BASE  -     2 
CLUSTER KEY LENGTH -   0                           DATA BASE ID CHANGE         - NO   
                                                      DEFINITION POSTED VIA  - DATADICTIONARY CATALOG 
AUTHID        - SYSUSR                                SQL-INTENT - Y                            
TABLE SQLNAME - K12_PTN                               UNIQUE ROW IDENTIFIERS (URI)    0 URI-REUSE NO 
DOMAIN CONSTRAINT - NO                                TABLE BEING REFERENCED       - NO  
DL1-T CONSTRAINT  - NO                             TABLE REFERENCING               - NO   
TABLE CONSTRAINED - NO                                ALL REFERENCING IN THIS BASE - YES 
CURRENT CHECK PENDING - LOAD SET          - NO        HISTORY CHECK PENDING - LOAD SET          - NO 
                        RELATED TABLE     - NO                                RELATED TABLE     - NO  
                        FORWARD RECOVERY  - NO                                FORWARD RECOVERY    NO 
TRIGGER(S)        - NO                                                        FORCED OFF        - NO 
CURRENT ROW(S) VIOLATE CONSTRAINT(S) -      NO        HISTORY ROW(S) VIOLATE CONSTRAINT(S)      - NO
DATA SET NAME - JBND007.P025000                       DATA  DTF/DDNAME - P025000                     
VOLUMES       - WRKD32          
KEY - NAME   ID   LENGTH  MASTER  NATIVE  UNIQUE  DIRECT  KEY INC  KEY USE  OCCURRENCE  /  KEY SQLNAME            STATUS 
*     TST01  0001      8   YES     YES     NO       NO      YES      ANY    TST01P001                             LD      
                                                                            TOBIE_K01_PTN_TST01                         

This page of the report displays the following information:

The following fields report table information:

  • TABLE NAME
    Name of a table in this database. If this is a table partition (Child) of a partitioned table, the table name represents the name of the partition. In addition, the literal PARTITION is present with 5 variable fields to assist in clarifying information about this partition. The first variable is the name of the Full Parent table. The next two variables, separated by a slash (/), are the relative number of this partition and the number of partitions. In this example, K12 is the second of three partitions, based upon the high value of this partition. The next two variables, separated by a dash (-), are the table name of the previous partition and the next partition, based upon the high values of the partitions. The first partition has blanks for the previous partition, and the last partition has blanks for the next partition.
  • OCCURRENCE
    CA Datacom® Datadictionary™ entity-occurrence name for the table and its status/version.
  • TABLE ID
    Internal table identifier.
  • Following Identifies the area containing the previously identified table:
  • AREA NAME
    DATACOM-NAME of the area. If multiple tables exist in this area, this information is duplicated for each table. If *HISTORY* follows the name, this entry has been logically deleted but still exists to provide the ability to back up the area.
  • OCCURRENCE
    CA Datacom® Datadictionary™ entity-occurrence name for the area and its status/version.
  • AREA SQLNAME
    Blank if table is not accessible by SQL, or if the database has not been cataloged with r9 or later.

The following fields report information about the contents of this table:

  • RECORD LENGTH
    The first value is the length of the user data which is delimited from the second value by a slash. The second denotes the length of the user data plus the CA Datacom®/DB Record Control Element (RCE).
  • RECORDS IN TABLE
    Number of records in the table. If a system failure has occurred during add/delete processing, this number can be inaccurate.
  • LENGTH OF KEY/ ELEMENTS
    Amount of storage needed by the MUF to hold the CXX control blocks that contain each key, element, or special field definitions for the given table.
  • NUMBER OF KEYS
    Number of keys defined for this table.
  • NUMBER OF ELEMENTS
    Number of elements defined for this table.
  • Following reports physical details about this data area:
  • BLOCK LENGTH
    Length of the data blocks in this area. If the area is to have a new block size during the next data INIT, the current size prints followed by a slash and the new block size.
  • SLACK - n
    The n specifies the slack size defined for the table in its definition.
  • OVERFLOWS IN AREA
    Number of records added to the area since the last area load.
  • BLOCKS IN USE
    Number of blocks in the data area that currently contain data. If a system failure has occurred during processing, this number can be inaccurate.
  • HIGH USED TRACK
    The number of tracks which must be processed to ensure that all data is read during the execution of a physical backup or GETPS. It also specifies the minimum number of tracks which must be formatted by the next load, and the minimum "move to" data set size (after dynamic extend for an ONLINE_AREA_MOVE. NONE indicates that either the high used mark option is set to off or the area has not been reloaded since it was turned on.
  • BLOCKS UNUSED
    Number of blocks that currently are completely empty. If a system failure has occurred during processing, this number can be inaccurate.
  • TOTAL BLOCKS
    Total blocks in this area.
  • CXXMAINT LINK - YES/NO
    Provides the current setting of the CXXMAINT option of LINK=YES/NO. Set to YES, the default and recommended option, the open of the area validates that the CXX name, in the data set opened, is the same as the CXX name in the executing CXX. This edit protects users from confusing production and test data sets.
  • TOTAL TRACKS
    Total tracks allocated to the area.
  • PERCENT FULL
    Percent full is calculated by dividing blocks in use by total blocks. The value reported is an even percent. Decimals are truncated. If a system failure has occurred during processing, this number can be inaccurate.
  • DEVICE TYPE
    Type of device containing this area.
    Note: When the Index Area or data area has not been INITed, the DEVICE is blanks.
  • BLOCKS/ TRACK
    Data blocks per track in this area.
  • DYNAMIC EXTEND
    Specifies whether dynamic extends are in effect for this data area.
  • DYN.EXT.TRACKS - n
    For DYN.EXT.TRACKS - n, the n provides that dynamic extend, whether set or not, is defined in tracks and not cylinders. If defined in cylinders, the field shows DYN.EXT.CYLS - n.
    Note: If DYNAMIC EXTEND is specified as YES and this is zero, the VTOC secondary allocation is used.
    CA Datacom® has taken advantage of enhancements to z/OS environments to allow dynamic extend to be greater than 64K tracks.
  • SECONDARY CYLS
    SECONDARY CYLS, the JCL secondary allocation value, is useful when using dynamic extends with the extend value not set in CA Datacom® Datadictionary™. SECONDARY CYLS is the size that is used by MVS. The size reported is the size that existed the last time the area was opened when the database was opened for update. During a dynamic extend, the size is subject to the data set having a specific JCL DD statement with a different secondary.
    The secondary allocation is only reported in cylinders. If the allocation was done in an average block, the secondary size from the JCL is converted into tracks (rounding down) and then into cylinders (rounding down). If the allocation was done in tracks, the secondary size from the JCL is converted into cylinders (rounding down). Therefore, a value reported as 0 (zero) could mean no secondary or a secondary of a size less than a full cylinder.
    The SECONDARY CYLS size is subject to a CXX BACKUP function and restored with the database restore. The information is not disabled if input into a previous release of CA Datacom® then subjected there to a backup before being restored into a Version 15.0 CXX. If the information is not currently correct, it is corrected the next time the data set is opened for update. This information is not intended to be a replacement for other Operating System tools that provide the secondary allocation in more detail. The number reported has a maximum size of 64k-1 (65535). This number reflects a size of 65535 and all larger sizes.
    When the DASD data set is not defined as temp or virtual, the SECONDARY CYLS value is updated each time the DASD data set is opened. The SECONDARY CYLS value is also updated each time the DASD data set is opened when opening the database for update, including when using SIMPLIFY mode or ACCESS OPTIMIZE.
    A blank (nothing displayed) is shown for SECONDARY CYLS if any of the following is true:
    • The data set has never been opened after Version 15.0 code was installed
    • The data set was opened without the database being opened for update.
    • The area was opened in MUF and defined as VIRTUAL.
    • The area was opened for update but was defined in the JCL as a TEMP data set, that is, a DSN starting with two ampersands (&&).
  • CHANGE MASTER KEY and DUPLICATE MASTER KEY
    Report whether the Master Key value can be changed during update processing and whether duplicate Master Key values are allowed.
  • RECOVER and LOGGING
    Rport whether CA Datacom®/DB recovery is activated for this table and whether logging is active for this table.
  • ENCRYPTION
    Is either NONE or the mode and type of encryption, such as (B(BASIC) A(AES128).
  • PIPELINE
    Indicates whether the Pipeline maintenance option is active for this table.
  • DSOP MODE
    Rports the data area space reclamation option for this table.
  • DB COMPRESSION and USER COMPRESSION
    Indicate whether CA Datacom®/DB compression is active for this table and whether user compression is used with this table. If user compression is used, the name of the compression module is displayed.

The following fields indicate whether the table and index are loaded.

  • TABLE LOADED
    NO specifies that the table is not loaded. When TABLE LOADED is NO and it was set not loaded as part of a catalog, then it may be followed by an explanation that might be one of the following, some of which involve information about partitioning:
    • AREA NAME CHANGED
      The area for this table has changed, so the table has been marked as not loaded.
    • ANOTHER PARTITION CHANGED
      The high-value value for the partition previous to this one has changed. Therefore, this partition must also be reloaded.
    • COMPRESSION CHANGED
      The compression option has changed, so the table needs to be reloaded.
    • COMPRESSION NAME CHANGED
      The name of user compression has changed, so the table needs to be reloaded.
    • PARTITION COLUMNS UNEQUAL
      The number of columns in the partition key are unequal, so the table needs to be reloaded.
    • PARTITION HIGH VALUES CHANGED
      The high value has changed, forcing the need to reload the table.
    • RECOVERY CHANGE
      The type of recovery has changed, forcing the need to reload the table.
    • RECORD LENGTH CHANGE
      The record length of the table has changed, forcing the need to reload the table.
    • SPECIAL FIELD CHANGE
      The change in the number of special fields has changed, forcing the need to reload the table.
    • TABLE ID CHANGE
      The table ID has changed, forcing the need to reload the table.
    • TO/FROM PARTITION
      Either the new table is partitioned and the old table is not, or the old table is partitioned and the new table is not. YES specifies that the table is loaded and the date and time of the last load are displayed.
  • INDEX LOADED
    • NO
      Indicates that the index is not loaded. This condition exists after a new definition is cataloged which defines a database that did not exist before. Also, if the index is initialized, it would be considered not loaded. Other conditions like errors during a load may also set index not loaded.
    • URI
      Indicates that the index exists for any required URI indexes and the space index is loaded. The data is not, however, indexed. This is normally set when a load is done with the INDEX=NO option. It can be set if a catalog is done which adds, deletes, or updates key definitions, so that the data is not considered indexed and must be rebuilt. The URI and space index, however, are correctly loaded. The forward recovery utility requires a YES or URI status to be able to correctly run.
    • YES
      Indicates that the index is loaded with all data indexed.
  • CLUSTER KEY ID and CLUSTER KEY LENGTH
    Reports the cluster key ID and length for this table. (If clustering by table, the cluster key ID is 0 and length is 3.)
  • AUTHID and TABLE SQLNAME
    Contain blanks, if not yet cataloged with r9 or later. If the table is accessible by SQL, in CA Datacom® Datadictionary™ the first and each r9 or later catalog provides information. If cataloged with r9 or later and the table is not accessible by SQL, AUTHID is blank and TABLE SQLNAME contains 'NO SQL ACCESS.'
  • DATADICTIONARY BASE
    the database ID of the CA Datacom® Datadictionary™ where the definitions were stored when this table was cataloged to the Directory.
  • DATA BASE ID CHANGE
    Indicates if the DBID has been changed during a LOAD AREA=CXX using NEWDBID=, or a CXXMAINT OPTION=DDPROD using NEWDBID=.
  • DEFINITION POSTED VIA
    Indicates if the table was posted to the Directory using the CA Datacom® Datadictionary™ CATALOG, the (DDCFBLD -CXX BUILD transaction and the CXXMAINT DDPROD option), or LOAD FROM BACKUP.
  • SQL INTENT
    Is Y if the table has been defined with full SQL access, R if the table is SQL read-only, or N if no SQL access is allowed, or * (an asterisk) if unknown because the structure was cataloged before the SQL INTENT option was supported.
  • UNIQUE ROW IDENTIFIERS (URI)
    Indicates whether the area is being processed with Unique Row Identifiers (URIs). NONE indicates the area is not being processed with URIs. If the area is being processed with URIs, the highest URI assigned is displayed.
  • URI-REUSE
    Indicates whether the CA Datacom® Datadictionary™ attribute URI-REUSE is set to yes or no. When URI-REUSE is set to Y (yes), when the URI count reaches 3G, an asynchronous scan of the data area is scheduled in the MUF. For more information on URIs and the URI reuse feature, see Administrating.

The following fields indicate which type of constraints apply for this table.

  • DOMAIN CONSTRAINT
    Indicates that CA Datacom®/DB domain constraints are in effect for this table.
  • DL1-T CONSTRAINT
    Indicates that CA Datacom® DL1 Transparency constraints are in effect for this table. See the CA Datacom® DL1 Transparency user documentation for more information.
  • TABLE CONSTRAINED
    Indicates if the table is constrained by SQL.
  • Following fields provide referential integrity information for this table.
  • TABLE BEING REFERENCED
    Indicates whether this table is referenced by another table or is the object in a relationship with another table.
  • TABLE REFERENCING
    Indicates whether this table references another table or is subject in a relationship with another table.
  • ALL REFERENCING IN THIS BASE
    Indicates whether all relationships to this table exist in this database.
    Note: If there is no relationship in either this database or any other, YES is indicated.
    Indicates whether the table needs to have referential integrity confirmed using the DBUTLTY CONFIRM function. The categories listed on the report indicate the function that was performed when the check pending was issued. See following item.

The following fields indicate the history of the table regarding referential integrity.

  • LOAD SET / RELATED TABLE / FORWARD RECOVERY
    Indicates the function that was being performed when the check pending was issued.
  • FORCED OFF
    Indicates whether a DBUTLTY CONFIRM function was executed using the FORCE parameter.
  • HISTORY ROW(S) VIOLATE CONSTRAINT(S)
    Indicates whether data in the row or rows violated an integrity constraint or constraints.
  • DATA SET NAME
    The data set name, if it is known. If the data set name is reported, a VOLUMES entry is included with volume serial numbers displayed. If necessary, multiple VOLUMES entries may be listed with 10 volume serial numbers per entry. The REPORT function obtains the volume serial numbers by issuing a catalog locate. If the locate fails, the locate return code is displayed.
  • DATA DTF/DDNAME - P025000
    Provides the DTF name or DD name that is used by CA Datacom® to open this data area. The name is not an option.

The following fields report all keys and their pertinent attributes defined for this table.

  • KEY SQLNAME
    Is blank if the table is not accessible by SQL, or if the database has not been cataloged with r9 or later. Otherwise, it contains the SQL name of the key.
  • STATUS
    STATUS on the KEY line occurs only if the base format is FORMAT 2. FORMAT 1 databases do not have a status at the key level. Below STATUS can be LD for loaded or NL for not loaded.
    The asterisk (*) below the key is blanks if the database is FORMAT 1 and is blanks if the key described is to be stored in the IXX Index Area (the default). If this key is to have its values stored in a different index area of a Multi-Dataset Index, the asterisk is replaced by the name of the area, for example, I01.

TABLE K12 CONTINUED
 
    - FIELDS - ORDER    SENSITIVE  NULL  START  LENGTH  OCCURRENCE           
               ASCEND   NOT SENS   NO       28       8  FIRST-RANDOM-NO P002 
                 .
                 .
                 .
 
ELEMENTS - NAME   SECURITY CODE   START  LENGTH   DATA TYPE  NULL COL.  OCCURRENCE   
           TSTEL     00-000           0      84   CHARACTER     YES     TSTEL P002

This page of the report shows the following:

  • Report of all columns (fields) defined for this key.
  • ORDER
    Indicates the sequence (ascending or descending) of field data in the index.
  • SENSITIVE
    Indicates if the field is data type sensitive.
  • FLOAT Floating-point number
    • NOT SENS Not data type sensitive
    • PACKED Packed decimal
    • SIGN INT Signed integer
    • ZONE DEC Zoned decimal
    • NULL Indicates whether the field accepts null values.
    • START Contains the displacement of the field in the table.
    • LENGTH Contains the length of the field.
    • OCCURRENCE Contains the entity-occurrence name and status/version of the field.
  • Report of all elements and their pertinent attributes defined for this table. The element security code (if any) is displayed in both two-digit hexadecimal and three-digit decimal value format.
    The element data type is always CHARACTER. The element null column (NULL COL) displays YES when the element has one or more fields whose columns can contain null values. NO indicates that the element has no fields that can contain null values.

TABLE K12 CONTINUED
 
PARTITION FULL PARENT NAMES  - K01 (SYSUSR                          ) (K01                             )  
PARTITION -ANY- PARENT NAMES - KA1 (SYSUSR                          ) (KA1                             )  
MOVE TO NEW PARTITION - NO   RESTRICTED  - YES                                                             
PARTITION FIELD NAME             SENSITIVE  START  LENGTH   HIGH VALUE                                    
RECORD-NO                        ZONE DEC       4       8   15                                            
DESCENDING-NO                    NOT SENS      44       8   99999991                                     

This page of the report shows the following fields for the Partitioning Information Table:

  • PARTITION FULL...
    Shows that K01 is the name of the Full Parent table in this database, in this example.
  • PARTITION -ANY-...
    Shows that KA1 is the name of the Any Parent table in this database, in this example.
  • (SYSUSR )
    Shows that SYSUSR is the table SQL authorization ID for both the Full Parent and the Any Parent table, in this example.
  • (K01 )
    Shows that the table SQL name of the Full Parent table is K01, in this example.
  • (KA1 )
    Shows that the table SQL name of the Any Parent table is KA1, in this example.
  • MOVE TO NEW PARTITION
    Indicates whether an update is allowed to move to a new partition. YES indicates that if a partition key is updated and that update would cause the record to move to a new partition, the move will take place. NO means the move will not take place, and a return code will be received.
  • RESTRICTED
    Refers to a restricted table, YES or NO. Applications cannot access Child tables directly within a partition if RESTRICTED - YES is indicated.

    Note: Child tables can, however, in cases where RESTRICTED is YES, still be accessed through the Parent table or Any Parent table.
  • PARTITION FIELD NAME
    Indicates the occurrence name of the field making up the partition key.
  • SENSITIVE
    Indicates whether the field is data type sensitive.
    • NOT SENS Not data type sensitive
    • PACKED Packed decimal
    • SIGN INT Signed integer
    • ZONE DEC Zoned decimal
  • START
    Shows the starting position of this field in the data record.
  • LENGTH
    Shows the length of the field in the data record.
  • HIGH VALUE
    Shows the high value of this partition. If this field contains unprintable characters, it will also be printed in hexadecimal format.

Sample Report REPORT CXX - Full - Special Fields

A list of certain special fields can appear after the elements section on the report. To appear on the list, the field must have the DBEDITS or NULL-INDICATOR attribute turned on. The DBEDITS attribute is turned on for all columns (fields) when the table is created through SQL.

When the DBEDITS attribute-value for a FIELD entity-occurrence is set to Y, additional information is stored in the Directory during a catalog. The records are edited by CA Datacom®/DB according to data type when they are added, loaded, or updated.

TABLE A11 CONTINUED
 
ELEMENTS - NAME   SECURITY CODE   START  LENGTH   DATA TYPE  NULL COL.  OCCURRENCE
 
           SQLEL     00-000           0      27   CHARACTER     YES     SQLEL P001
 
 
FIELDS - TYPE   NULL  FORCE  CHANGE  DEFAULT  VALUE                 START  LENGTH  OCCURRENCE    
         CHAR   NO    NO      YES    LITERAL  DEMOCHAR                  0       8  DEMCHAR P001  
         BIN    YES   NO      YES    LITERAL  9999                      8       5  DEMINT P001     
         BIN    YES   NO      YES    NO DFLT                           13       5  DEMINT2 P001  
         CHAR   YES   NO      YES    NO DFLT                           18       9  DEMCHAR2 P001

This page of the report shows the special columns (fields) for this table. Fields only appear if they have DBEDITS=Y or NULL-INDICATOR=Y.

  • TYPE
    Indicates the data type of the field or, if it was placed on the list because NULL-INDICATOR=Y, NOEDT to signify that the DBEDITS attribute is not turned on for this field.
    • BIN Binary in a database cataloged in a previous version (see SBIN and UBIN)
    • BIT Character field, bit data (not converted to or from PC)
    • CHAR Character
    • DATE SQL DATE
    • FLOAT Floating-point
    • GRAF Double-byte character set (replaces DBCS)
    • MIXED Character field which allows single-byte and double-byte characters (double-byte characters must be within Shift-Out/Shift-In pairs)
    • NOEDT No DBEDITS on this field
    • SBIN Signed binary (see BIN and UBIN)
    • SPACK Signed packed decimal
    • STAMP SQL TIMESTAMP
    • SZONE Signed zoned decimal
    • TIME SQL TIME
    • UBIN Unsigned binary (see BIN and SBIN)
    • UPACK Unsigned packed decimal
    • UZONE Unsigned zoned decimal
    • VBIT Variable length BIT
    • VCHAR Variable-length character
    • VGRAF Variable length GRAF (double-byte character set)
    • VMIX Variable length MIXED
  • NULL
    Indicates whether the field accepts no values (NULL-INDICATOR).
  • FORCE
    Indicates whether a value must be provided.
    • ADD Must supply a value when adding (FORCEADD).
    • ALL Must supply a value when adding or updating (FORCEADD and FORCEUPD).
    • NO A value is not required when adding or updating.
    • UPDT Must supply a value when updating (FORCEUPD).
  • CHANGE
    Indicates whether a change is allowed (UNCHANGEABLE).
  • DEFAULT
    Indicates the type of default value.
    • LITERAL - A specified value
    • NO DFLT - No default
    • STD - Standard default for type
    • SYSTEM - Indicates an accessor ID default (default system user)
    • USER - The system user ID (AUTHID)
  • VALUE
    Contains the specified value for a literal value.
  • START
    Contains the displacement of the field in the table.
  • LENGTH
    Contains the length of the field.
  • OCCURRENCE
    Contains the entity-occurrence name and status/version of the field.

Type A - Directory Space Utilization

Generate a Space Utilization Report to obtain information about the number of tracks and blocks allocated and the number of blocks in use, and other important space utilization information. The keyword and value TYPE=A in the control statement cause this information to print.

Encryption Report without TYPE=A

Table information relating to encryption is provided as part of the full REPORT AREA=CXX without TYPE=A. For an example, see Sample Report: ENCRYPT.

Example JCL Space Utilization CXX Report

The following example shows the command to generate a Space Utilization Report for the Directory.

Note: Use the following as a guide to prepare your JCL. The JCL statements are for example only. Lowercase letters in a statement indicate a value you must supply. Code all statements to your site and installation standards.

 //jobname    See the previous note and JCL Requirements.
 //       EXEC PGM=DBUTLTY,REGION=2M
 //STEPLIB    See the previous note and JCL Requirements.
 //CXX      DD DSN=cxx.data.set,DISP=SHR           Directory data set
 //SYSIN    DD *                                   Command Input
         REPORT   AREA=CXX,TYPE=A
 /*

Sample Report

The following example is a sample report page. For an example report header, see Sample Report Headers.

Sample Report REPORT CXX - Space Utilization 

                    CONTROL CARD(S)
                    .........1.........2.........3.........4.........5.........6.........7.........8
                    REPORT  AREA=CXX,TYPE=A
 
                    FUNCTION=REPORT
                       AREA=CXX
                       TYPE=A

This page of the report shows the following:

  • 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.

                             DATA AREA SPACE UTILIZATION REPORT
 
 
AREA DATA       TOTAL         TOTAL       TOTAL        USED    PERCENT     PARTIALLY  AREA REUSE
NAME BASE      TRACKS       RECORDS      BLOCKS      BLOCKS  FULL    MAX  EMPTY BLKS    OPTION
 
CXX               300           N/A       3,000         204     6      6         N/A  N/A
 
IXX       1         4           N/A          44          14    31     31         N/A  N/A
 DEM      1         2            17          62          11    17     17          80  CLUSTERING
 PAY      1         2           200          62          12    19     19           0  NO RECLAMATION
 PMF      1         2           200          62          16    25     25           0  NO RECLAMATION
 
IXX       2       140           N/A       1,540         817    53     53         N/A  N/A
 ALS      2         7           894          70          32    45     45           0  RANDOM
 ARA      2         1           106          10           5    50     50           1  RANDOM
 ATZ      2         5            22          55           2     3      3          19  RANDOM
 BAS      2         1            17          11           2    18     18           1  RANDOM
 DVW      2         1             6          11           2    18     18           1  RANDOM
 ELM      2         4           411          40          21    52     52           1  RANDOM
 FIL      2         2           183          22          10    45     45           0  RANDOM
 FLD      2        45         7,868         450         427    94     94           0  RANDOM
 HSD      2         6           192          60          37    61     61           0  RANDOM
  .    .            .            .           .           .     .     .            .    .
  .    .            .            .           .           .     .     .            .    .
  .    .            .            .           .           .     .     .            .    .

This page of the report provides the following information:

  • AREA NAME
    The DATACOM-NAME of the area and DATA BASE is the DATACOM-ID of the database containing the area. Summary statistics for the Directory (CXX) are always displayed on the first line.
  • TOTAL TRACKS
    The number of tracks allocated and accepted by CA Datacom®/DB for use in the area. If the actual number of tracks (blocks) allocated is larger, you should execute an EXTEND function to make the space available to CA Datacom®/DB.
  • TOTAL RECORDS
    For data areas, the number of records in the area. If a system failure has occurred during maintenance processing, this number can be inaccurate.
  • TOTAL BLOCKS
    Number of blocks in the area.
  • USED BLOCKS
    Number of blocks that contain data. If a system failure has occurred during maintenance processing, this number can be inaccurate.
  • PERCENT FULL and MAX
    Percentage full is calculated by dividing used blocks by total blocks. The value reported is an even percent. Decimals are truncated.
    Maximum percentage, sometimes referred to as "high-water mark," is calculated by dividing maximum used blocks by total blocks. Maximum used blocks is computed internally. This percentage is higher than FULL percentage when:
    • All records are deleted in a data block with space management option 1 or 3 (random or cluster). See Administrating for information about the data area space management options.
    • All Index entries are deleted in an Index block.
  • PARTIALLY EMPTY BLKS
    Blocks that contain sufficient space to hold the largest record in the area are considered to be partially empty. Even when all blocks contain data (percent full is 100), records can still be added, if partially empty blocks exist and a space reclamation option has been selected.
  • AREA REUSE OPTION
    The data area space management option used for the data area.

Type B - CXX Report

TYPE=B is equivalent to the full report for the database, area, and table information. However, it does not report any key, element, or field information.

An estimated half of the printed lines in (and time spent printing) a full CXX report are used to give static information about keys, elements, and fields. Most CXX reports are requested to view dynamic data information. In particular the data set names and volumes, and the table loaded status, all of which are available, without the static information, in a TYPE=B report.

Type I - Impact Report

Use TYPE=I to request an Impact Report after a CA Datacom® Datadictionary™ CATALOG. An Impact Report shows you the impact of the CATALOG. The valid values for the DBID specified in a TYPE=I request can range from 1 through 5000.

The MUF must be enabled to use TYPE=I.

When an Impact Report is obtained after a CXXMAINT DDPROD or using TYPE=I after a CA Datacom® Datadictionary™ CATALOG, the reasons are printed on the report. For more information and samples, see CXXMAINT DDPROD (Update Directory).

Impact CXX Report

The following shows the command to generate an Impact Report for the Directory, database 16.

Note: Use the following as a guide to prepare your JCL. The JCL statements are for example only. Lowercase letters in a statement indicate a value you must supply. Code all statements to your site and installation standards.

 //jobname    See the previous note and JCL Requirements.
 //       EXEC PGM=DBUTLTY,REGION=2M
 //STEPLIB    See the previous note and JCL Requirements.
 //CXX      DD DSN=cxx.data.set,DISP=SHR           Directory data set
 //SYSIN    DD *                                   Command Input

         REPORT AREA=CXX,TYPE=I,DBID=16
 /*

Sample Report

The following is an example of a sample report page. For an example report header, see Sample Report Headers.

Sample Report REPORT CXX - Impact Report 

                    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

This page of the report shows the following:

  • 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.

                                  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)

This page of the report shows the following:

  • BASE
    The DATACOM-ID of the database containing the area.
  • AREA
    The DATACOM-NAME of the area.
  • TABLE
    The table name.
  • ID
    The table ID.
  • DISPOSITION
    The reason is described in Processing a DDPROD Request.
    The TYPE=I report has been enhanced to provide information about cases in which the disposition 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. 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 r11, that is, tables whose disposition is LOADED have no need to also show the key-level status.
    The code is described in Processing a DDPROD Request.

Type K - Encryption Report

For information about the AREA=CXX,TYPE=K encryption information report, see ENCRYPT (Facilitate Data Encryption) .

Type P - PREINIT Report

Use REPORT AREA=CXX with TYPE=P when you want to request a Directory PREINIT Report.

The PREINIT list is reported using the DBUTLTY function REPORT with AREA=CXX,TYPE=P. It reports on all items in the PREINIT list. If the list is empty, it has nothing to report. The first page of the full CXX report (not TYPE=A) and the same report requested as TYPE=K provides PREINIT AREAS - NO or YES to alert users whether any PREINIT areas exist.

The PREINIT list is information from the DBUTLTY function PREINIT. The function is used as part of:

  • The ONLINE_AREA_MOVE (OAM) MUF command to move all data blocks from one area to a new area with a new set of extents.
  • The ONLINE_TABLE_MOVE (TM24) MUF command to move all data rows from one area into a new area with a new set of extents and in Native Sequence Key order.
  • The Block Size Alter (BA24) process to move all data rows from one area into a new area with a new set of extents and in Native Sequence Key order.
  • A new database planned to be added for the index area as part of the SQL statement CREATE DATABASE.
  • A new data area planned to be added as part of the SQL statement CREATE AREA.

In the normal flow of actions, the TYPE=P report will report a newly initialized dataset from the time of the PREINIT function until it is utilized in one of the above actions. Should an entry exist that it no longer needed, it is deleted with the CXXMAINT function of DBUTLTY with OPTION=DPREINIT.

Example JCL

The following example shows the command to generate a TYPE P (PREINIT) CXX Report.

Note: Use the following as a guide to prepare your JCL. The JCL statements are for example only. Lowercase letters in a statement indicate a value you must supply. Code all statements to your site and installation standards.

 //jobname    See the previous note and JCL Requirements.
 //       EXEC PGM=DBUTLTY,REGION=2M
 //STEPLIB    See the previous note and JCL Requirements.
 //CXX      DD DSN=cxx.data.set,DISP=SHR           Directory data set
 //SYSIN    DD *                                   Command Input
           REPORT AREA=CXX,TYPE=P
 /*

Sample Report

The following example is a sample report page. For an example report header, see Sample Report Headers.

Sample Report PREINIT 

The PREINIT list exists at the CXX level and is reported in a REPORT function requested with AREA=CXX,TYPE=P.

                    CONTROL CARD(S)
                    .........1.........2.........3.........4.........5.........6.........7.........8
                    REPORT AREA=CXX,TYPE=P
 
                    FUNCTION=REPORT
                       AREA=CXX
                       TYPE=P
                       

This page of the report shows the following:

  • 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.


  DBID AREA TYPE  BLKSIZE OLDEP  DATETIME             TRACKS  DSN                                   
                                                                                                         
   995 IXX INDEX    4,096    NO  20131106084732           15  SYS13310.T084731.RA000.DBDVLWXX.IXX997.H02  
   997 I11 INDEX    4,096   YES  20131106084731           15  SYS13310.T084731.RA000.DBDVLWXX.I11997.H02  
   998 I11 INDEX    4,096    NO  20131106084731           15  SYS13310.T084731.RA000.DBDVLWXX.I11997.H02   
   999 I11 INDEX    8,192   YES  20131106084731           15  SYS13310.T084731.RA000.DBDVLWXX.I11997.H02   
  1555 ABC  DATA    5,555   N/A  20131106084732           15  SYS13310.T084731.RA000.DBDVLWXX.ABC555.H02 
  3333 ABC  DATA    4,096   N/A  20130628091120           15  SYS13179.T091119.RA000.DBDVLWXX.ABC.H04  
  3333 IXX INDEX    4,096   YES  20130628091120           15  SYS13179.T091119.RA000.DBDVLWXX.IXX.H04  

The section from a full CXX Report that follows shows an entry for PREINIT AREAS at the bottom right. PREINIT AREAS - YES indicates that currently there are PREINIT areas, but PREINIT AREAS - NO indicates that there are currently no PREINIT areas.

CONTROL AREA DIRECTORY                                      CXX VERSION - 15.0 
DBCRBAS REQUIREMENT (ALL BASES OPEN)  -   105,616           CXX ENQ - SYSPLEX   
NUMBER OF DATA BASES -    45                                DATA HIGH USED MARK - YES   
DEVICE TYPE - 3390                                          DATASET EXTENT VALIDATION - YES  
DYNAMIC FILE ALLOCATION ALLOWED - YES                       DATA FAST SEARCH - YES       
SECURE USING JOBNAME - NO                                   CXX LEVEL -   1  
SECURE ALLOWING SINGLE USER - NO                            SINGLE USER ALLOWED - YES  
SQL MODE - SUPPORT ACTIVE - YES                             SIMPLIFY MODE - YES          
           DATADICTIONARY BASE -     2                                                                
           DATA DEFINITION DIRECTORY BASE -    15           PREINIT AREAS - YES                

Type Z - CXX Internal History Report

Use REPORT AREA=CXX with TYPE=Z when you want to request a CXX internal history Report. Entries will exist only after function CXXMAINT OPTION=ALTER,OPTION2=HIST0001 (through HIST0099) has been executed and later CXX alterations performed using DDUPDATE 1000 ALTER transaction or selected CXXMAINT OPTION=ALTER functions. A full list of alter functions tracked as CXX internal history is provided with CXXMAINT OPTION=ALTER,OPTION2=HIST00nn. New CXX internal history entries are built if one of the compared values changes such as a 4 to a 5. Excluded are changes with no changes such as a 4 to a 4. The number of maximum entries is set with the HIST00nn value where the 'nn' is the maximum. Entries are by base. Therefore, each database can have zero entries or up to the maximum entries. The CXX internal history entries are not part of a BACKUP AREA=CXX and are not part of a load. A BACKUP/LOAD or BACKUP/CXXCLONE empties the database of history entries. If the database is deleted or purged using CXXMAINT, the history is also removed with the database.

Note: If all current history needs to be cleared such as the start of a regression suite set HIST0000, then restore to HST0099 (for example).

Example JCL

The following example shows the command to generate a TYPE Z CXX internal history Report. This example does not have DBID= providing a single database ID or range of bases.

Note: Use the following as a guide to prepare your JCL. The JCL statements are for example only. Lowercase letters in a statement indicate a value that you must supply. Code all statements to your site and installation standards.

 //jobname    See the previous note and JCL Requirements.
 //       EXEC PGM=DBUTLTY,REGION=2M
 //STEPLIB    See the previous note and JCL Requirements.
 //CXX      DD DSN=cxx.data.set,DISP=SHR           Directory data set
 //SYSIN    DD *                                   Command Input
           REPORT AREA=CXX,TYPE=Z
 /*

Sample Report

The following example is a sample report page. For an example report header, see Sample Report Headers.

Sample Report CXX internal history

The CXX internal history entries are printed for all bases with no DBID= keyword or the bases selected with the DBID=. Within each base, entries are printed newest entry first through all entries for that base. Then the next base follows.

                    CONTROL CARD(S)
                    .........1.........2.........3.........4.........5.........6.........7.........8
                    REPORT AREA=CXX,TYPE=Z
 
                    FUNCTION=REPORT
                       AREA=CXX
                       TYPE=Z
                       

This page of the report shows the following:

  • 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.

DBID DATE       TIME     JOBNAME R.UNIT JOBID   STEP SYSTEM   USERID   PDT ARA TBL OPTIONAL INFORMATION                
                                                                                                                       
 597 2018/03/09 14.29.49 DBDVLBA4 75428 JOB28773   1 CA31     ABCDO02  DDU I01     BLKSIZE 12,222 TO 12,345            
 770 2018/02/23  7.15.55 DBDVLLD  74386 JOB35082   2 CA11     ABCDO02  DBU MIN     DSN                                 
                                                          DSN OEMD.CA7.CA7PA00.MIN770 TO LYNJO02.DCMDEV.DB.DBDVM0.MIN770
 797 2018/07/17 11.00.15 DBDVLTA  90945 JOB61888   3 CA32     ABCDO02  DDU     C01 TABLE                               
 997 2018/09/07  7.45.16 DBDVL    96161 JOB05834   1 CA32     ABCDO02  DBU A01     DSOP 0 TO 4                         
 997 2018/09/07  7.45.16 DBDVL    96161 JOB05834   1 CA32     ABCDO02  DBU A01     DSOP 4 TO 0                         
 997 2018/09/06 14.58.32 DBDVL    96153 JOB57971   4 CA32     ABCDO02  DBU     F03 LOGGING N TO Y                      
 997 2018/09/06 14.58.32 DBDVL    96153 JOB57971   4 CA32     ABCDO02  DBU     F03 LOGGING Y TO N                      
 997 2018/09/06 14.58.32 DBDVL    96153 JOB57971   4 CA32     ABCDO02  DBU         RESET_KEY_USES                      
 997 2018/09/06 14.58.31 DBDVL    96151 JOB57971   2 CA32     ABCDO02  DDU     F02 KEY USE TST08 A TO N                
 997 2018/09/06 14.58.31 DBDVL    96151 JOB57971   2 CA32     ABCDO02  DDU A01     AREA                                
 997 2018/09/06 14.58.31 DBDVL    96151 JOB57971   2 CA32     ABCDO02  DDU         DATABASE                            
1018 2018/03/28  9.15.41 DBDVL118 77704 JOB44455   2 CA11     ABCDO02  DBU STA     DSN                                 
                                                        DSN DCMDEV.DB.DBDVM0.STA1018 TO LYNJO02.DCMDEV.DB.DBDVM0.STA1018
                                                                                                                       
REQUEST COMPLETE                                                                                                       

This page of the report shows the following:

  • DBID
    The DATACOM-ID of the database
  • DATE
    The date in the format CCYY/MM/DD
  • TIME
    The time in format HH.MM.SS
  • JOBNAME
    The Job name of the Job causing the entry
  • R.UNIT
    The run unit number assigned to the Job
  • JOBID
    The z/OS Job ID of the Job
  • STEP
    The z/OS step number of the Job step
  • SYSTEM
    The name of the z/OS System where the Job executed
  • USERID
    The security user that submitted the Job
  • PDT
    The Product that was executing to create the entry. Either DDU for Datadictionary or DBU for Datacom/DB (Datacom/AD)
  • ARA
    The DATACOM-NAME of the area. Blanks if the entry is not data area specific.
  • TBL
    The DATACOM-NAME of the table. Blanks if the entry is not table specific. 
  • OPTIONAL INFORMATION
    Is specific to the entry. Below are all the current entries possible:
    • DATABASE

DDUPDATE program when using a transaction 1000 ALTER for DATABASE that currently includes any combination of the two 1500 items below 

-UPD DATABASE,TOBIE_DATABASE_997(PROD)   
1000 ALTER   

With one or more of the following:

    • 1500 DYNAMIC-EXTEND,Y   
    • 1500 DYN-EXT-TRACKS,9999
    • AREA (data area excluding block size change)

DDUPDATE program when using a transaction 1000 ALTER for AREA that currently includes any combination of the five 1500 items below   

-UPD AREA,TOBIE_AREA_997(PROD) 
1000 ALTER

With one or more of the following:

    • 1500 DYNAMIC-EXTEND,C   
    • 1500 DYN-EXT-TRACKS,9999   
    • 1500 SPACE-MNGMNT,4   
    • 1500 SLACK,0   
    • 1500 URI-REUSE,N
    • BLKSIZE 12,222 TO 12,345 (change to data area with block size change only) 

DDUPDATE program when using a transaction 1000 ALTER for AREA that currently includes only a block size change, see 1500 items below   

-UPD AREA,TOBIE_AREA_997(PROD)   
1000 ALTER 

With the following:

    • 1500 BLOCK-SIZE,4096
    • BLKSIZE+ 12,222 TO 12,345 (change to data area with block size change and one or more of the other items below) 

DDUPDATE program when using a transaction 1000 ALTER for AREA that currently includes block size change and any combination of the other five 1500 items below 

-UPD AREA,TOBIE_AREA_997(PROD)   
1000 ALTER   

With one or more of the following:

    • 1500 DYNAMIC-EXTEND,C  
    • 1500 DYN-EXT-TRACKS,9999  
    • 1500 BLOCK-SIZE,4096  
    • 1500 SPACE-MNGMNT,4  
    • 1500 SLACK,0  
    • 1500 URI-REUSE,N
    • TABLE

DDUPDATE program when using a transaction 1000 ALTER for TABLE that currently includes any combination of the 3 1500 items below

-UPD KEY,TOBIE_F02_997.TST08(PROD) 
1000 ALTER   

With one or more of the following:

      • 1500 COMPRESSION,&
      • 1500 COMPRESS-EXIT,&
      • 1500 ENCRYPTION-KEY,&     
    • KEY USE TST08 A TO N

DDUPDATE program when using a transaction 1000 ALTER for KEY that currently includes only key usage in the below 1500 item below

Provides the key name changed with the 'from' value to the 'to' value 

-UPD KEY,TOBIE_F02_997.TST08(PROD) 
1000 ALTER   

With one or more of the following:

      • 1500 KEY-USAGE,A                 
      • -END        
    • RESET_KEY_USES

DBUTLTY program function CXXMAINT with the below example

      • CXXMAINT OPTION=ALTER,DBID=0997,OPTION2=RESET_KEY_USES
    • LOGGING N TO Y

 DBUTLTY program function CXXMAINT with the below example where the table LOGGING setting is changed from a Yes to No or No to Yes

      • CXXMAINT OPTION=ALTER,TABLE=F03,DBID=0997,LOGGING=NO
    • DSOP 0 TO 4

DBUTLTY program function CXXMAINT with the below example where the area DSOP setting is changed from one number to another

      • CXXMAINT OPTION=ALTER,AREA=A01,DBID=0997,DSOP=4
    • DSN

DBUTLTY program function CXXMAINT with the below example where the area DSN value is changed from one value to another

      • CXXMAINT OPTION=ALTER,AREA=A01,DBID=0997,DSN=DCMDEV.DB.DBDVM0.A01997
      • In addition, when a DSN is changed a following line in the report will provide the DSN alter with 'DSN from-DSN TO to-DSN'. This information is right adjusted to end in column 121.  


Was this helpful?

Please log in to post comments.

  1. Owen Williams
    2019-03-08 09:32

    Bullet points AREA NAME CHANGED through to TO/FROM PARTITION should be indented, as they are all children of the TABLE LOADED NO condition.

  2. JOANNA KRUEGER
    2019-03-11 06:03

    Hi Owen -

    Correction has been made to 15.1 and 15.0! Thanks