(1)

Date and time the report was created.

(2)

Title.

(3)

Page number of the report.

(4)

System name of CA MIM image as defined by the DEFSYS statement.

(5)

Name of the CA MIM started task.

(6)

The CA MIM release number.

(7)

The CA MIM service level.

(8)

Date and timestamp of the earliest record in the reporting interval.

(9)

Summary level for the data line. In this example, each RECORD is displayed in the detail line. If each HOUR was specified, then the detail line would be a summary of the hour's activity.

(10)

Date and timestamp of the latest record in the recording interval.

(11)

Range of records included in the report.

INTERVAL START(12)

Start date and timestamp that the report line interval data covers.

CF CYCLES (13)

The total number of control file accesses made by CA MIM during the reporting interval.

ENGAGE TIME (14)

The average elapsed time, in seconds, during the reporting interval to obtain the control file RESERVE and read the first block from the control file. The first block contains the GMR (Global Master Record), the block allocation mask, and as many transactions as will fit in the remainder of the block. Once the control file RESERVE is obtained, CA MIM on the local system has exclusive ownership of its data structures in relation to the external systems.

SCANFILE TIME (15)

The average elapsed time, in seconds, during the reporting interval to examine transactions in the blocks read in for transactions not seen yet by the local system and to disburse those transactions to the various facilities, including the driver, on the local system. During this time, control blocks on the local system are altered (built, changed, or deleted) based on transactions from the external systems to reflect changes that have occurred on the external systems.

If the number of transactions has extended to multiple blocks, then any control file read or write I/O time related to examining and disbursing the transactions to the local system is included in this time. Usually, this time appears as 0.000 if, on the average, all CA MIM transactions are contained in the first block.

Important! Increases in this column may indicate that CA MIM is rereading transactions that have not been processed yet by other systems.

HEART TIME (16)

The average elapsed time, in seconds, during the reporting interval that the CA MIM driver and all active facilities spent in the performance of global activities on the local system. During this time, control blocks on the local system can be altered (built, changed, deleted) to reflect requested changes on the local system. Transactions detailing the applied data structure changes are added to the control file. This column shows the total, average, elapsed time for all processing and then breaks out the amount of time each facility used of the total, average, elapsed time.

DISENGAGE TIME (17)

The average elapsed time, in seconds, during the reporting interval required to write the final updated block, if any, to write the GMR record, and to release the control file RESERVE.

AFTER TIME (18)

The average elapsed time, in seconds, during the reporting interval, that the CA MIM driver and all active facilities spent in the performance of activities on the local system that were a result of the control file cycle that completed, but that do not require ownership of the control file for serialization of data structures. It is during this time that units of work in other address spaces on the local system that have been waiting on the CA MIM address space for service are notified to continue execution. This column shows the total average elapsed time for all processing and then breaks out the amount of time each facility used of the total elapsed time.

WAIT TIME (19)

The average elapsed time, in seconds, during the reporting interval that CA MIM remained dormant while waiting for an event to cause the need to access the control file.

BLOCKS IN (20)

The average number of control file blocks read per control file cycle during the reporting interval.

BLOCKS OUT (21)

The average number of control file blocks written per control file cycle during the reporting interval.

XACT IN (22)

The average number of transactions read per control file cycle. This column shows the total average number of transactions read for all processing and then breaks out the average number of transactions that can be attributed to a given facility. Note that only global facilities receive transactions.

XACT OUT (23)

The average number of transactions written per control file cycle. This column shows the total average number of transactions written for all processing and then breaks out the average number of transactions that can be attributed to a given facility. Note that only global facilities generate transactions.

XACT PROC (24)

The average number of transactions processed per control file cycle.