AREA_NAME

CHAR(3)

No

The name of the area (CXX, IXX, or data area).

BLOCK_LENGTH

SMALLINT

No

The length of each block in this area.

DATASET_NAME

CHAR(44)

Yes

This field is null if the data set name is not known. This can occur for new databases before the areas are initialized, or the database loaded from a Directory (CXX) backup and the database is new, or for areas which have not been initialized for several versions of CA Datacom/DB. Otherwise, the data set name is present.

This field contains *virtual* if this database is defined as virtual.

DBID

SMALLINT

No

The database identifier (ID) containing this area. For the Directory (CXX) row, this field is zero.

DEVICE

CHAR(6)

Yes

This field is null if the area has not been initialized since a catalog of a new database, or the load of a new database from a CXX backup. Otherwise, it contains a name representing the type of device CA Datacom/DB is using to determine device geometries, that is, records per track and tracks per cylinder.

Note: The virtual areas are treated as if they reside on 3380 devices. For example, an actual physical Index Area (IXX) might be on a 3390 device. However, CA Datacom/DB treats it as if it resides on a 3380 device during the run of the MUF and reports it that way in the DIR_DATASET (DRZ) Dynamic System Table.

DIR_NAME

CHAR(8)

No

Name of the Directory being used by this MUF.

GENERATION

SMALLINT

No

Value returned is 1 for generation 1.

IN_USE_BLOCKS

INTEGER

No

Can be zero if the area is not initialized. Contains a count of the number of blocks that contains active information. If a system failure has occurred during maintenance processing, this number can be inaccurate. In CA Datacom/DB reporting, IN_USE_BLOCKS and TOTAL_BLOCKS are used to calculate percent full.

MAX_USED_BLOCKS

INTEGER

No

This field can be zero if the area has not been initialized. Otherwise, this is a high water mark as to how full the area has been. In CA Datacom/DB reporting, MAX_USED_BLOCKS and TOTAL_BLOCKS are used to calculate maximum percent full.

PARTIAL_BLOCKS

INTEGER

No

This field is zero in the rows for the Directory (CXX) and Index Area (IXX), if the area is not initialized, or if space option 0 (no reclamation) is selected. Otherwise, this field contains the number of blocks that probably have space to add one or more records. In compressed tables and areas with multiple tables of different lengths, for a specific add, space may not exist. In support of transaction backout, some space is not actually available until a transaction commit. If a system failure has occurred during maintenance processing, this number can be inaccurate.

SECONDARY_CYLS

SMALLINT

Yes

The secondary allocation is only reported in cylinders. The number reported is a maximum size of 64k-1 (65535). This number reflects size 65535 and all larger sizes.

The size reported was the last time the area was opened when the base 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 size is subject to a CXX BACKUP function and restored with the base restore. The information is not disabled if input into a back level of CA Datacom and then subject to a backup there and restored into a 15.0 CXX. If the information is not currently correct, then it is corrected the next open for update of the data set.

If the allocation was done in average block then 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 then the secondary size from the JCL is converted into cylinders (rounding down). Therefore, a value reported as 0 might mean no secondary or a secondary of a size less than a full cylinder.

This field may be null if:

• The data set has not been opened in the past with 15.0 code installed.
• It 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 (DSN starting with &&).

TOTAL_BLOCKS

INTEGER

No

This field may be zero if the area has not been initialized. Otherwise, it contains the total number of blocks in the area.

TOTAL_TRACKS

INTEGER

No

This field may contain zeros for an area not initialized. Otherwise, it contains the number of tracks allocated and accepted by CA Datacom/DB for use.