BREAKS_DONE

DECIMAL(11,0)

No

Number of times the startup option BREAK occurred to cause a task to allow a task switch. It does not indicate if another task of equal or higher priority was ready to run and was dispatched.

DEFRAG_REDBR

INTEGER

No

Contains the count of the number of times backwards processing (such as LOCBR) interrupted an active DBUTLTY DEFRAG function.

INDEX_Q_CUR_ENTS

INTEGER

No

Current number of unprocessed entries in the index queue.

INDEX_Q_MAX_ENTS

INTEGER

No

Maximum number of unprocessed entries in the index queue for the life of this MUF.

INDEX_Q_CUR_DBIDS

SMALLINT

No

Contains the current number of unique DBIDs with unprocessed entries in the index queue.

INDEX_Q_MAX_DBIDS

SMALLINT

No

Contains the maximum number of unique DBIDs with unprocessed entries in the index queue for the life of this MUF.

IO_DASD_RETRY

INTEGER

No

Count of times the operating system required CA Datacom to reissue a physical I/O because of a "retry" return code.

IO_MEM_SHORT

INTEGER

No

Times I/O restricted in z/OS due to 24-bit memory shortage.

MRDF_IXX_DIRECT

DECIMAL(11,0)

No

Contains the count of times the MRDF facility referenced an IXX block directly, without moving it to an IXX buffer.

MUF_NAME

CHAR(8)

No

Name of the MUF specified in the MUF Multi-User startup option or the name of the MUF job name.

TIMES_READ_1

INTEGER

No

During sequential GETIT/GETPS, CBS, and ADDIT processing it is possible that CA Datacom/DB would choose to read multiple blocks with one EXCP. This counter reflects the number of times that only one block was read.

TIMES_READ_2_8

INTEGER

No

During sequential GETIT/GETPS, CBS, and ADDIT processing it is possible that CA Datacom/DB would choose to read multiple blocks with one EXCP. This counter reflects the number of times that two through eight blocks were read.

TIMES_READ_9_32

INTEGER

No

During sequential GETIT/GETPS, CBS, and ADDIT processing it is possible that CA Datacom/DB would choose to read multiple blocks with one EXCP. This counter reflects the number of times that 9 through 32 blocks were read.

TIMES_READ_33_99

INTEGER

No

During sequential GETIT/GETPS, CBS, and ADDIT processing it is possible that ,CA Datacom/DB would choose to read multiple blocks with one EXCP. This counter reflects the number of times that 33 or more blocks were read.

TIMES_WRITE_1

INTEGER

No

With pipelining, multiple blocks in an area frequently need to be written. If these blocks are physically close on DASD, CA Datacom/DB attempts to write more than one at a time. This count is the times a write was necessary to the index or data and only one block needed to be or could be written.

TIMES_WRITE_2_12

INTEGER

No

See previous description. This is a count of the times that 2 through 12 blocks could be written together in one EXCP.

TIMES_WRITE_13_24

INTEGER

No

See previous description. This is a count of the times that 13 through 24 blocks could be written together in one EXCP.

TIMES_WRITE_25_48

INTEGER

No

See previous description. This is a count of the times that 25 through 48 blocks could be written together in one EXCP.

XCF_ALL_PATHS_BUSY

INTEGER

No

Count of times an XCF message send failed because all XCF signaling paths were busy resulting in a retry.

XCF_MISC_ENV_ERROR

INTEGER

No

Count of times an XCF message send failed for environmental reasons other than paths busy or too few message buffers resulting in a retry.

XCF_REJECT_MSG_IN

INTEGER

No

Count of messages received by MUF with characteristics which made them unacceptable for processing.

XCF_RETRY_LIM_HIT

INTEGER

No

Count of the number of XCF messages for which the retry limit was exceeded and therefore had to be queried for action by a subtask.

XCF_SUBSYS_FAILURE

INTEGER

No

Count of times an XCF message send failed because the MVS XCF component failed.

XCF_TOO_FEW_MSGBUF

INTEGER

No

Count of times an XCF message send failed due to a shortage of XCF buffers resulting in a retry.