If a report is done without a DBID, the first page of the CXX report (not TYPE=A) has information about the full CXX. In the following example, a full CXX Report report (without a DBID specified) displays the Version 12.0 enhancements in the report. It shows previous and new (for Version 12.0) field values by displaying the new field values on the right side of the example.
CONTROL AREA DIRECTORY DBCRBAS REQUIREMENT (ALL BASES OPEN) - 63,232 CXX ENQ - SYSPLEX NUMBER OF DATA BASES - 34 DATA HIGH USED MARK - NO DEVICE TYPE - 3390 DATASET EXTENT VALIDATION - NO DYNAMIC FILE ALLOCATION ALLOWED - YES DATA FAST SEARCH - NO SECURE USING JOBNAME - NO CXX LEVEL - 1 SECURE ALLOWING SINGLE USER - YES SINGLE USER ALLOWED - NO SQL MODE - SUPPORT ACTIVE - YES
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.
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,DBID=999 FUNCTION=REPORT AREA=CXX DBID=00999 Ž
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 Base: 999 ******************************************************************************** Directory: PRODCXX 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--5/08/2009, TIME-07.35.25 } LAST RESTARTED - DATE--5/08/2009, TIME-07.35.24 } Ž LAST MAINTAINED - DATE--9/05/2008, TIME-06.42.18 } REPLICATED BASE - NO BASE FORMAT - 2 } PARTITIONED BASE - NO } UPDATE USERS - 0 } READ ONLY USERS - 0 } OCCURRENCE - TOBIE_DATABASE_PTNP001 ‘ 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 } BLOCKS UNUSED - 57 } TOTAL BLOCKS - 60 } TOTAL TRACKS - 5 } PERCENT FULL - 5 } DATA SET NAME - JBND007.IXX5000 } INDEX DTF/DDNAME - IXX5000 VOLUMES - WRKD26 }
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:
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.
Date and time of the last RESET CXX for this database.
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 may 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 replicated or partitioned. (See the CA Datacom STAR Administrator Guide for details on partitioning and replication.)
BASE FORMAT can be 1 or 2. FORMAT 1 restricts features of Version 12.0 that are not compatible with the previous release. FORMAT 2 allows all Version 12.0 functionality. For details about base format, see the information about upgrading the CXX in the chapter about creating and maintaining the Directory (CXX) in the CA Datacom/DB Database and System Administration Guide.
UPDATE USERS reports the number of tables open for update times the number of User Requirements Tables open for update that contain the tables. (This count is not always maintained accurately on DASD.)
READ ONLY USERS reports the number of tables open for read only times the number of User Requirements Tables open for read-only that contain the tables.
OCCURRENCE is the entity-occurrence name for the database, and the status/version in CA Datacom/DB.
SQL SECURITY indicates whether SQL Security has been selected for the tables in this database. See the CA Datacom/DB Database and System Administration Guide 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 the CA Datacom/DB Database and System Administration Guide for information about the CA Datacom/DB Index structure.
(page 2 continued)
Date: mm/dd/ccyy ******************************************************************************** Page: 2 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn Base: 999 ******************************************************************************** Directory: PRODCXX 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--5/08/2009, TIME-07.35.25 } LAST RESTARTED - DATE--5/08/2009, TIME-07.35.24 } LAST MAINTAINED - DATE--9/05/2008, TIME-06.42.18 } REPLICATED BASE - NO BASE FORMAT - 2 } PARTITIONED BASE - NO } UPDATE USERS - 0 } READ ONLY USERS - 0 } OCCURRENCE - TOBIE_DATABASE_PTNP001 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 } BLOCKS UNUSED - 57 } TOTAL BLOCKS - 60 } Œ TOTAL TRACKS - 5 } PERCENT FULL - 5 } DATA SET NAME - JBND007.IXX5000 } INDEX DTF/DDNAME - IXX5000 ’ VOLUMES - WRKD26 }
These lines report the space utilization for this Index Area:
Number of Index blocks per track.
For FBA devices, this is the number of physical blocks in one logical block.
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.
Count of the completely empty blocks in the Index. If a system failure has occurred during processing, this number can be inaccurate.
Total blocks used by the Index.
Total tracks used by the Index.
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 from CA Dynam/D for z/VSE if it is present and if the data set is catalogued.
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.
OLDEP refers to old entry points. When OLDEP=NO is specified, the DBNTRY entry point is the only entry point supported. See the INIT function in the CA Datacom/DB DBUTLTY Reference Guide for information on the OLDEP= keyword.
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.
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.
Date: mm/dd/ccyy ******************************************************************************** Page: 3 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn Base: 999 ******************************************************************************** Directory: PRODCXX TABLE NAME - K12 PARTITION - K01 2/3 } AREA NAME - P02 } OCCURRENCE - TOBIE_K12 P001 } Œ OCCURRENCE - TOBIE_AREA_PTN_P02 P001 } TABLE ID - 111 } AREA SQLNAME - TOBIE_AREA_PTN_P02 } RECORD LENGTH - 84 / 96 } BLOCK LENGTH - 4,096 SLACK - 0 } RECORDS IN TABLE - 0 } OVERFLOWS IN AREA - 0 } LENGTH OF KEY/ELEMENTS - 1,088 } Ž BLOCKS IN USE - 2 } NUMBER OF KEYS - 9 } BLOCKS UNUSED - 58 } NUMBER OF ELEMENTS - 1 } TOTAL BLOCKS - 60 CXXMAINT LINK - YES } CHANGE MASTER KEY - YES } TOTAL TRACKS - 5 DYNAMIC EXTEND - YES } DUPLICATE MASTER KEY - YES } PERCENT FULL - 3 DYN.EXT.TRACKS - 15 } RECOVER - YES } ‘ DEVICE TYPE - 3390 LOGGING - YES } BLOCKS/TRACK - 12 PIPELINE - YES ’ DSOP MODE - NO RECLAMATION “ DB COMPRESSION - NO } ” TABLE LOADED - YES, DATE--5/08/2009, TIME-07.35.24 } • 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 } 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 - } DATA DTF/DDNAME - P025000 } KEY - NAME ID LENGTH MASTER NATIVE UNIQUE DIRECT KEY INC CBS USE OCCURRENCE / KEY SQLNAME STATUS } * TST01 0001 8 YES YES NO NO YES YES TST01P001 LD } TOBIE_K01_PTN_TST01 }
Table Information
Identifies the table:
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.
CA Datacom/DB entity-occurrence name for the table and its status/version.
Internal table identifier.
Identifies the area containing the previously identified table:
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.
CA Datacom/DB entity-occurrence name for the area and its status/version.
Blank if table is not accessible by SQL, or if the database has not been cataloged with r9 or later.
Reports information about the contents of this table:
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).
Number of records in the table. If a system failure has occurred during add/delete processing, this number can be inaccurate.
Amount of storage needed by the Multi-User Facility to hold the CXX control blocks that contain each key, element, or special field definitions for the given table.
Number of keys defined for this table.
Number of elements defined for this table.
Reports physical details about this data area:
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.
The n specifies the slack size defined for the table in its definition.
Number of records added to the area since the last area load.
Number of blocks in the data area that currently contain data. If a system failure has occurred during processing, this number can be inaccurate.
Number of blocks that currently are completely empty. If a system failure has occurred during processing, this number can be inaccurate.
Total blocks in this area.
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 allocated to the area.
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.
Type of device containing this area.
Note: When the Index Area or data area has not been INITed, the DEVICE is blanks.
Data blocks per track in this area.
Specifies whether dynamic extends are in effect for this data 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.
CHANGE MASTER KEY and DUPLICATE MASTER KEY reports whether the Master Key value can be changed during update processing and whether duplicate Master Key values are allowed.
RECOVER and LOGGING reports whether CA Datacom/DB recovery is activated for this table and whether logging is active for this table.
PIPELINE indicates whether the Pipeline maintenance option is active for this table.
DSOP MODE reports the data area space reclamation option for this table.
DB COMPRESSION and USER COMPRESSION indicates 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.
These fields indicate whether the table and index are loaded.
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.
Specifies that the table is loaded and the date and time of the last load are displayed.
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.
Indicates that the index is loaded with all data indexed.
(page 3 continued)
Date: mm/dd/ccyy ******************************************************************************** Page: 3 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn Base: 999 ******************************************************************************** Directory: PRODCXX TABLE NAME - K12 PARTITION - K01 2/3 } AREA NAME - P02 } OCCURRENCE - TOBIE_K12 P001 } OCCURRENCE - TOBIE_AREA_PTN_P02 P001 } TABLE ID - 111 } AREA SQLNAME - TOBIE_AREA_PTN_P02 } RECORD LENGTH - 84 / 96 } BLOCK LENGTH - 4,096 SLACK - 0 } RECORDS IN TABLE - 0 } OVERFLOWS IN AREA - 0 } LENGTH OF KEY/ELEMENTS - 1,088 } BLOCKS IN USE - 2 } NUMBER OF KEYS - 9 } BLOCKS UNUSED - 58 } NUMBER OF ELEMENTS - 1 } TOTAL BLOCKS - 60 CXXMAINT LINK - YES } CHANGE MASTER KEY - YES } TOTAL TRACKS - 5 DYNAMIC EXTEND - YES } DUPLICATE MASTER KEY - YES } PERCENT FULL - 3 DYN.EXT.TRACKS - 15 } RECOVER - YES } DEVICE TYPE - 3390 LOGGING - YES } BLOCKS/TRACK - 12 PIPELINE - YES DSOP MODE - NO RECLAMATION DB COMPRESSION - NO } TABLE LOADED - YES, DATE--5/08/2009, TIME-07.35.24 } 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 } 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 - } • DATA DTF/DDNAME - P025000 } KEY - NAME ID LENGTH MASTER NATIVE UNIQUE DIRECT KEY INC CBS USE OCCURRENCE / KEY SQLNAME STATUS } * TST01 0001 8 YES YES NO NO YES YES TST01P001 LD } TOBIE_K01_PTN_TST01 }
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/DB 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/DB 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/DB 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.
These fields indicate which type of constraints apply for this table.
Indicates that CA Datacom/DB domain constraints are in effect for this table.
Indicates that CA Datacom DL1 Transparency constraints are in effect for this table. See the CA Datacom DL1 Transparency User Guide for more information.
Indicates if the table is constrained by SQL.
These fields provide referential integrity information for this table.
Indicates whether this table is referenced by another table or is the object in a relationship with another table.
Indicates whether this table references another table or is subject in a relationship with another table.
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.
Indicates the history of the table regarding referential integrity.
Indicates the function that was being performed when the check pending was issued.
Indicates whether a DBUTLTY CONFIRM function was executed using the FORCE parameter.
Indicates whether data in the row or rows violated an integrity constraint or constraints.
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 data set name, if it is known.
At the bottom of this report are all keys and their pertinent attributes defined for this table.
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 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.
Date: mm/dd/ccyy ******************************************************************************** Page: 4 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn Base: 999 ******************************************************************************** Directory: PRODCXX 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 }
Report of all columns (fields) defined for this key.
Indicates the sequence (ascending or descending) of field data in the index.
Indicates if the field is data type sensitive.
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.
Date: mm/dd/ccyy ******************************************************************************** Page: 5 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn Base: 999 ******************************************************************************** Directory: PRODCXX 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 }
Partitioning Information
Table partitioning information.
Shows that K01 is the name of the Full Parent table in this database, in this example.
Shows that KA1 is the name of the Any Parent table in this database, in this example.
Shows that SYSUSR is the table SQL authorization ID for both the Full Parent and the Any Parent table, in this example.
Shows that the table SQL name of the Full Parent table is K01, in this example.
Shows that the table SQL name of the Any Parent table is KA1, in this example.
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.
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.
Indicates the occurrence name of the field making up the partition key.
Indicates whether the field is data type sensitive.
Shows the starting position of this field in the data record.
Shows the length of the field in the data record.
Shows the high value of this partition. If this field contains unprintable characters, it will also be printed in hexadecimal format.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|