The following table is designed as a replacement table for MUF_SYSTEM_STATS (MFS). It has many columns with a larger capacity than the old table and removes obsolete columns that are in other dynamic systems tables or provide no value. We recommend that you start using this table to collect systems statistics even though the MFS table still exists.
Note: Columns whose lengths are different between the two tables are in italics. Otherwise, all column characteristics are the same as the old table.
|
Column Name |
SQL Data Type |
Nullable |
Description |
|---|---|---|---|
|
BEGIN_TIME
|
TIMESTAMP |
No |
Date and time the MUF was enabled. This timestamp would need to be the same if this record was read at two points in time and the difference was being computed to see activity during a time period. (If the timestamp is different on the second reading of the record, the MUF has been recycled.) |
|
CURRENT_CPU
|
INTEGER |
No |
Number of CPU seconds used by the MUF address space since startup. |
|
CURRENT_DATETIME
|
TIMESTAMP |
No |
Current date and timestamp from the MUF. |
|
DATA_MGR_REQUESTS
|
DECIMAL(13,0) |
No |
Specifies the number of calls to the low-level CA Datacom/DB processor. Each request to the MUF that involves a CA Datacom/DB RAAT or SAAT type command generates one data manager request. Each request involving an SQL request generates as many data manager requests as necessary to process the SQL request. |
|
DATA_SEQUENCE
|
DECIMAL(13,0) |
No |
Number of times a data buffer was referenced. |
|
DATA_USED_1
|
DECIMAL(13,0) |
No |
Number of times a data buffer was referenced the first time after the buffer was read from DASD or copied from MRDF. |
|
DATA_USED_2
|
DECIMAL(11,0) |
No |
Number of times a data buffer was referenced a second time after the buffer was read from DASD or copied from MRDF. |
|
DATA_USED_3
|
DECIMAL(11,0) |
No |
Number of times a data buffer was referenced a third time after the buffer was read from DASD or copied from MRDF. |
|
DATA_USED_4
|
DECIMAL(11,0) |
No |
Number of times a data buffer was referenced a fourth time after the buffer was read from DASD or copied from MRDF. |
|
DATA_USED_5
|
DECIMAL(13,0) |
No |
Number of times a data buffer was referenced five times (and six times, and seven times, and so forth) after the buffer was read from DASD or copied from MRDF. |
|
DATA2_USED_1
|
INTEGER |
No |
Number of times a data2 buffer (large-size data buffer) was referenced once after the buffer was read from DASD or copied from MRDF. |
|
DATA2_USED_2
|
INTEGER |
No |
Number of times a data2 buffer (large-size data buffer) was referenced twice after the buffer was read from DASD or copied from MRDF. |
|
DATA2_USED_3
|
INTEGER |
No |
Number of times a data2 buffer (large-size data buffer) was referenced three times after the buffer was read from DASD or copied from MRDF. |
|
DATA2_USED_4
|
INTEGER |
No |
Number of times a data2 buffer (large-size data buffer) was referenced four times after the buffer was read from DASD or copied from MRDF. |
|
DATA2_USED_5
|
DECIMAL(11,0) |
No |
Number of times a data2 buffer (large-size data buffer) was referenced five times (and six times, and seven times, and so forth) after the buffer was read from DASD or copied from MRDF. |
|
DB_REQUESTS
|
DECIMAL(13,0) |
No |
Number of calls from an application program either directly or through another tool (such as SQL) which was shipped to the MUF. Blocked GETIT/GETPS requests are counted here as one request per block. Block SQL requests are the same, one request per block. |
|
DELETED_BLOCKS
|
INTEGER |
No |
Number of times the last entry in an index block was deleted. |
|
DXX_SEQUENCE
|
DECIMAL(13,0) |
No |
Number of times a DXX buffer was referenced. |
|
DXX_USED_1
|
DECIMAL(11,0) |
No |
Number of times a DXX buffer was referenced once after the buffer was read from DASD or copied from MRDF. |
|
DXX_USED_2
|
DECIMAL(11,0) |
No |
Number of times a DXX buffer was referenced twice after the buffer was read from DASD or copied from MRDF. |
|
DXX_USED_3
|
DECIMAL(11,0) |
No |
Number of times a DXX buffer was referenced three times after the buffer was read from DASD or copied from MRDF. |
|
DXX_USED_4
|
DECIMAL(11,0) |
No |
Number of times a DXX buffer was referenced four times after the buffer was read from DASD or copied from MRDF. |
|
DXX_USED_5
|
DECIMAL(13,0) |
No |
Number of times a DXX buffer was referenced five times (and six times, and seven times, and so forth) after the buffer was read from DASD or copied from MRDF. |
|
INDEX_Q_PROCESSED
|
INTEGER |
No |
The number of index queue entries processed. Queue processing includes:
This statistic is useful primarily to CA Support for debugging purposes. |
|
IXX_SEQUENCE
|
DECIMAL(13,0) |
No |
Number of times an IXX buffer was referenced. |
|
IXX_USED_1
|
DECIMAL(11.0) |
No |
Number of times an IXX buffer was referenced once after the buffer was read from DASD or copied from MRDF. |
|
IXX_USED_2
|
DECIMAL(11,0) |
No |
Number of times an IXX buffer was referenced twice after the buffer was read from DASD or copied from MRDF. |
|
IXX_USED_3
|
DECIMAL(11,0) |
No |
Number of times an IXX buffer was referenced three times after the buffer was read from DASD or copied from MRDF. |
|
IXX_USED_4
|
DECIMAL(11,0) |
No |
Number of times an IXX buffer was referenced four times after the buffer was read from DASD or copied from MRDF. |
|
IXX_USED_5
|
DECIMAL(13,0) |
No |
Number of times an IXX buffer was referenced five times (and six times, and seven times, and so forth) after the buffer was read from DASD or copied from MRDF. |
|
LOG_PERCENT_FULL
|
INTEGER |
No |
The highest percent full the Log Area reached. |
|
LOG_WRITE_COMMAND
|
INTEGER |
No |
The number of times the Log buffer containing logged data was written because of a command. Commands which cause transaction boundaries (COMIT, LOGCP, LOGCR, ROLBK, CLOSE) are always written. The ADDIT, DELET, and UPDAT maintenance commands are only written if the table definition indicates writes, the URT indicates writes, or the Multi-User startup option LOGPEND indicates no pipelining. Commands which are optional are LOGIT and LOGDW. Some internal system commands can also write the Log block prior to full. Comparing the ratios of COMMAND WRITE to BUFFER FULL WRITE I/O can be used to attempt tuning by reducing the number of LXX writes. The number of writes to the Log Area may not equal these detail counts due to multitasking events. |
|
LOG_WRITE_CONTROL
|
INTEGER |
No |
The number of times the Log control block was written. The control block information is required for the restart process during MUF. This counter is part of the information to provide details about the LXX I/O. The number of writes to the Log Area may not equal the detail counts due to multitasking events. |
|
LOG_WRITE_FULL
|
INTEGER |
No |
The number of times the log buffer containing logged data was written when it was considered to be full. This count is the number of Log Area (LXX) blocks used. LXX block size tuning is reflected here. The number of writes to the Log Area may not equal these detail counts due to multitasking events. |
|
LOG_WRITE_OTHER
|
INTEGER |
No |
Indicates the number of times a non-full Log block had to be written to support RESTART when an index or data block had to be written. The number of writes to the Log Area may not equal these detail counts due to multitasking events. |
|
LOG_WRITE_TXB
|
INTEGER |
No |
Indicates the number of times a Log block was written during transaction or request backout. |
|
LOG_WRITE_2_PHASE |
INTEGER |
No |
The number of I/Os done to the log Area in support of the CA Datacom STAR 2 phase commit processing. This is also used in special cases without CA Datacom STAR in the system. |
|
LOGPEND_WRITES
|
INTEGER |
No |
Number of writes to an index or data buffer due to the setting of the Multi-User startup option LOGPEND. |
|
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. |
|
NO_TXB_BUFFER
|
INTEGER |
No |
Specifies the number of times a task was in transaction or request backout, but all LOGPOOL buffers were not available. |
|
PHYSICAL_READS
|
DECIMAL(11,0) |
No |
Specifies the number of physical I/Os (EXCPs) that have been done to read data from DASD. |
|
PHYSICAL_WRITES
|
DECIMAL(11,0) |
No |
Specifies the number of physical I/Os (EXCPs) that have been done to write memory data to DASD. |
|
RECORD_LOCKS
|
DECIMAL(11,0) |
No |
Specifies the number of times a record was locked. Includes exclusive control locks and, for SQL, share locks. |
|
RQ_PENDING_1_10
|
DECIMAL(11,0) |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already nine or less tasks waiting on resources. |
|
RQ_PENDING_11_20
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 10 through 19 tasks waiting. |
|
RQ_PENDING_21_30
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 20 through 29 tasks waiting. |
|
RQ_PENDING_31_40
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 30 through 39 tasks waiting. |
|
RQ_PENDING_41_50
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 40 through 49 tasks waiting. |
|
RQ_PENDING_51_60
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 50 through 59 tasks waiting. |
|
RQ_PENDING_61_70
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 60 through 69 tasks waiting. |
|
RQ_PENDING_71_80
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 70 through 79 tasks waiting. |
|
RQ_PENDING_81_90
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 80 through 89 tasks waiting. |
|
RQ_PENDING_91_100
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already 90 through 99 tasks waiting. |
|
RQ_PENDING_GT_100
|
INTEGER |
No |
Specifies the number of times tasks waited on resources other than I/O and there were already more than 99 other tasks waiting on resources. |
|
SECONDARY_CONFLICT
|
INTEGER |
No |
Specifies the number of times a record lock was attempted where it was not currently available because the record was subject to transaction backout. |
|
SEQ_READ_AHEAD
|
INTEGER |
No |
Specifies the number of times a read-ahead I/O was done in support of the GETIT or GETPS command. |
|
SPLIT_DXX
|
INTEGER |
No |
Specifies the number of times that a DXX-level index block was split. This indicates growth of an index. |
|
SPLIT_IXX
|
INTEGER |
No |
Specifies the number of times that an IXX-level index block was split. |
|
SQL_REQUESTS
|
INTEGER |
No |
Specifies the number of requests issued to the MUF of the SQL style. |
|
WAIT_ACCOUNTING
|
INTEGER |
No |
Specifies the number of times a task had to wait when adding a record to an Accounting buffer because the Accounting buffer was full. |
|
WAIT_LOCK
|
INTEGER |
No |
Specifies the number of times a task requested a record-level lock that was not available. |
|
WAIT_REQUEST
|
INTEGER |
No |
Specifies the number of times that a task had to wait on an active request of another task. This involves internal CA Datacom/DB processing and currently can occur during a Log Area full condition and during close processing. |
|
WAIT_SPILL
|
INTEGER |
No |
Specifies the number of times that a task had to wait on the completion of a spill. This occurs when the Log has no space to add records until a spill is completed and space made available. |
|
WAIT_TASK
|
INTEGER |
No |
Specifies the number of times that a task had to wait on the completion of another task. This is done when a secondary conflict exists and the task needs to wait for the commit or rollback of the task last maintaining a data record. |
|
Copyright © 2014 CA.
All rights reserved.
|
|