Exception Messages

OMEGAMON for Db2 PE displays the ARCM exception when a thread is waiting for a tape mount. Db2 requires the archive tape mount during abort processing to backout changes made in the current unit of recovery. The thread does not do any processing until the tape is mounted, and holds Db2 resources until the abort request is complete.

ARCM is a member of the thread (TH) exception group. This exception monitors an action, not a value; its threshold is always N/A. The default state for ARCM is ON. If State is ON and a Db2 thread is waiting for a tape mount of an archive log, OMEGAMON for Db2 PE displays the exception.

A tape mount is necessary if Db2 recovery log archiving is to tape. Log data set archiving is an automatic feature of the Db2 log manager. Log archiving is initiated internally by Db2 when an active log is full. It runs as a subtask within the Db2 subsystem, and as a result, no job or started task is initiated.

ARCV is a member of the Db2 system (SY) exception group. This exception monitors an action, not a value; its threshold is always N/A. The default state for ARCV is ON. If State is ON and an archive is waiting for a tape mount, OMEGAMON for Db2 PE displays the exception.

When the percentage is below 90%, you get the basic exception message, assuming that you have set the threshold at 90% or lower. This message simply reports the percentage of use for any buffer pool that has reached the threshold value.

When the buffer pool used percentage is between 90% and 94.9%, inclusive, the exception message will include the information that the buffer pool has reached the Sequential Prefetch threshold (SPTH).

When the buffer pool used percentage is between 95% and 97.5%, inclusive, the exception message will include the information that the buffer pool has reached the Data Manager threshold (DMTH).

When the buffer pool used percentage exceeds 97.5%, the exception message will include the information that the buffer pool has reached the Immediate Write threshold (IWTH).

BMTH is a member of the system (SY) exception group. The default threshold is 90%.

CICT is a member of the CICS (CI) exception group. The default threshold for CICT is 80% of the THRDMAX value in the Resource Control Table (RCT). The threshold can be any value from 1% through 100%. If the ratio of active CICS threads to the THRDMAX value exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

OMEGAMON for Db2 PE displays the COMT exception when the number of system page updates per Commit exceeds the installation-defined threshold.

The update count used in the rate calculation is incremented each time a row in a page is updated.

COMT is a member of the thread (TH) exception group. Default threshold for COMT is 100 page updates to 1 commit. The threshold can be any value from 1 through 10,000. If the ratio of updates to commits exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

This is caused when the system maximum thread limit is reached (CTHREAD parameter). CTHD is a member of the thread (TH) exception group. This exception monitors an action, not a value; its threshold is always N/A. If State is ON and a user is waiting for thread creation, OMEGAMON for Db2 PE displays the exception.

OMEGAMON for Db2 PE displays the DDFS exception when it detects that the Distributed Database Facility (DDF) is not active in the Db2 subsystem being monitored. This might be because DSNZPARM specifies that DDF must be started manually; it might also reflect an abnormal termination of the distributed database facility.

DDFS is a member of the system (SY) exception group. This exception monitors an action, not a value; its threshold is always N/A.

OMEGAMON for Db2 PE displays the DRCV exception when the DDF VTAM receive data rate exceeds the exception threshold.

DRCV is a member of the system (SY) exception group. The exception threshold rate is expressed as KB per second. The default threshold for DRCV is 1000 KB per second.

OMEGAMON for Db2 PE displays the DSND exception when the DDF VTAM APPC send data rate exceeds the exception threshold.

DSND is a member of the system (SY) exception group. The exception threshold rate is expressed as KB per second. The default threshold for DSND is 1000 KB per second.

OMEGAMON for Db2 PE displays the DWAT exception when it detects that a distributed allied thread has been waiting for a response to a remote SQL request for a period of time greater than the exception threshold

DWAT is a member of the thread (TH) exception group. The exception threshold is expressed as an integer, that is, the number of seconds that can elapse before the exception will trip. The default threshold for DWAT is 120 seconds.

ENTO does not analyze ENTRY definitions with a THRDA value of zero because these threads automatically use the buffer pool and are considered legitimate POOL thread users.

ENTO analyzes all ENTRY thread definitions with TWAIT=POOL and THRDA>0 specified. As a result, it can trip and display multiple times on one OMEGAMON for Db2 PE cycle for the same CICS region. The Plan=cccccccc displays the Db2 plan name assigned to the entry threads. If the Db2 plan name is ********, the entry definition is using the CICS dynamic plan exit. The variable aaaa is the first CICS transaction defined to the plan. The CICS transaction ID is needed because the same Db2 plan can be defined to multiple ENTRY definitions. A CICS transaction can only be defined to a single Db2 plan. Therefore, the transaction ID in the exception output provides a unique identifier of which ENTRY definition is overflowing if the Db2 plan is defined to multiple ENTRY definitions.

ENTO is a member of the CICS (CI) exception group. The default threshold for ENTO is three transactions. The threshold can be any value from 1 through 100 transactions. If the number of transactions using a POOL thread due to an overflow exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

The definition of ENTRY threads (in the RCT) is optional. The definition and use of ENTRY threads enables the Db2 user to assign one or more Db2 threads to a single Db2 plan. You can also define one or more transactions that might use the plan.

ENTU analyzes all ENTRY thread definitions. As a result, it can trip and display multiple times on one OMEGAMON for Db2 PE cycle for the same CICS region. The Plan=cccccccc is the Db2 plan name assigned to the entry threads. If the Db2 plan name is ********, the entry definition is using the CICS dynamic plan exit. The variable aaaa is the first CICS transaction defined to the plan. The CICS transaction ID is needed because the same Db2 plan can be defined to multiple ENTRY definitions. A CICS transaction can only be defined to a single Db2 plan. The transaction ID in the exception output provides a unique identifier of which ENTRY definition is incurring the thread use reported by the exception.

ENTU ignores all ENTRY definitions with a THRDA value of zero and TWAIT=POOL. It also ignores any ENTRY definitions in which THRDA is set to one, regardless of the TWAIT operand in use.

ENTU is a member of the CICS (CI) exception group. The default threshold for ENTU is 95% of the THRDA value. The threshold can be any value from 1% through 100%. If the ratio of active threads originating from an ENTRY definition to the ENTRY definition's THRDA value exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

The definition of ENTRY threads (in the RCT) is optional. By using ENTRY threads, you can assign one or more Db2 threads to a single Db2 plan. You can also define one or more transactions which might use the plan. Other options are available when defining ENTRY threads, one of it is TWAIT. TWAIT is used to govern the required processing when all Db2 threads associated with an ENTRY definition (plan) are in use. If TWAIT is YES is specified and no ENTRY thread is available, the request is queued and waits for a thread assigned to the ENTRY definition to become available. This exception is tripped and displayed when the number of transactions waiting for an ENTRY thread exceeds the exception threshold.

The exception routine analyzes all ENTRY thread definitions with TWAIT is YES specified. As a result, the exception can trip and display multiple times on one OMEGAMON for Db2 PE cycle for the same CICS region. The Plan=cccccccc is the Db2 plan name assigned to the ENTRY threads. The variable aaaa is the first CICS transaction defined to the plan. The CICS transaction ID is needed because the same Db2 plan can be defined to multiple ENTRY definitions. A CICS transaction can only be defined to a single Db2 plan. The transaction ID in the exception output provides a unique identifier of which ENTRY definition is incurring the waits if the Db2 plan is defined to multiple ENTRY definitions.

ENTW is a member of the CICS (CI) exception group. The default threshold for ENTW is two transactions. The threshold can be any value between 1 and 100 transactions. If the number of transactions waiting for an ENTRY thread exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

ETIM displays the wall clock time that the plan has been actively holding thread resources. This might indicate that service level commitments have been exceeded.

ETIM is a member of the thread (TH) exception group. The default threshold for ETIM is 600 seconds. The threshold can be any value between 1 and 999999.99 seconds. If the thread elapsed time exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

The counters which Db2 maintains for this activity are updated throughout the life of the thread, and are reset when Db2 signon occurs.

GETP is a member of the thread (TH) exception group. The default threshold for GETP is 15 (1.5 Getpages to Read I/Os). The threshold can be any value between 0 and 100. Specify the threshold as an integer, where 1 equals 0.1 Getpages to Read I/Os. For example, OMEGAMON for Db2 PE sets a threshold specified as 20 equal to a ratio of 2.0 Getpages to Read I/Os. If the ratio of the Getpage rate to Read I/Os falls below the threshold, OMEGAMON for Db2 PE displays the exception.

GTRC is a member of the Db2 system (SY) exception group. This exception monitors an action, not a value; its threshold is always N/A. If State is ON and the global trace is active, OMEGAMON for Db2 PE displays the exception.

IDBC is a member of the thread (TH) exception group. The default threshold for IDBC is.7 seconds. The threshold can be any value between 0.00 and 999999.99 seconds. The threshold is specified in 100ths of seconds. For example, to set a threshold of.7, specify a value of 70. If the total In-Db2 CPU time exceeds the threshold value, OMEGAMON for Db2 PE displays the exception.

IDBK is a member of the Db2 system (SY) exception group. The default threshold for IDBK is 90% of the IDBACK installation parameter. The threshold can be any value between 1% and 100%. If the ratio of active background connections to the IDBACK value in use exceeds the threshold value, OMEGAMON for Db2 PE displays the exception.

IDBT is a member of the thread (TH) exception group. The default threshold for IDBT is 5 seconds. The threshold can be any value between 1 and 999999.99 seconds. If the total In-Db2 time exceeds the threshold value, OMEGAMON for Db2 PE displays the exception.

IDFR is a member of the Db2 system (SY) exception group. The default threshold for IDFR is 85% of the IDFORE installation parameter. The threshold can be any value between 1% and 100%. If the ratio of active foreground connections to the IDFORE value in use exceeds the threshold value, OMEGAMON for Db2 PE displays the exception.

IMCN is a member of the IMS (IM) exception group. This exception monitors an action, not a value; its threshold is always N/A. If State is ON and a region is defined but not connected to Db2, OMEGAMON for Db2 PE displays the exception.

IMND is a member of the IMS (IM) exception group. This exception monitors an action, not a value; its threshold is always N/A. If State=ON and no dependent region is defined to Db2, OMEGAMON for Db2 PE displays the exception.

These threads might cause Db2 resources to be unavailable to other active threads until either restart or RECOVER INDOUBT processing occurs.

INDB is a member of the thread (TH) exception group. This exception monitors an action, not a value; its threshold is always N/A. If State=ON and a thread is in doubt, OMEGAMON for Db2 PE displays the exception.

INDT is a member of the Db2 system (SY) exception group. The default threshold for INDT is one indoubt thread. The threshold is a value between 1 and 100 threads. If the number of indoubt threads exceeds the threshold value, OMEGAMON for Db2 PE displays the exception.

LKUS is a member of the thread (TH) exception group. The default threshold for LKUS is 80% of the NUMLKUS parameter defined by the installation. The threshold can be any value between 1% and 100%. If an active thread exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

Active log data sets are allocated to Db2 during startup processing. When an active log data set is full, it is automatically archived by Db2 to an archive log. When an active log is successfully archived, it is available for reuse. The availability of active logs is critical to the functioning of Db2. If no active log is available, the Db2 subsystem will hang until one becomes available. The lack of an active log could be caused by an insufficient number of logs defined when Db2 was installed, too small log data set size, or possibly due to problems encountered during the archive process.

LOGN is a member of the Db2 system (SY) exception group. The default threshold for LOGN is two available logs. The threshold is a value between 1 and 100 logs. If the number of available primary active logs is less than or equal to the threshold value, OMEGAMON for Db2 PE displays the exception.

OMEGAMON for Db2 PE displays the MCNV exception when the number of conversations in use constitutes a specified percentage of the preset maximum for a given logmode. In addition, when the percentage reaches 100%, the exception displays the number of threads waiting because the preset maximum was exceeded.

MCNV is a member of the system (SY) exception group. The exception threshold is expressed as a percentage (0-100). For example, if you want OMEGAMON for Db2 PE to notify you when any logmode has started 80% of its allotment of conversations, set the threshold to 80. The default threshold for MCNV is 80%.

OMEGAMON for Db2 PE displays the MDBT exception when the number of distributed database access threads in use constitutes a specified percentage of the preset maximum. The maximum is set in DSNZPARM by the MAXDBAT parameter.

MDBT is a member of the system (SY) exception group. The exception threshold is expressed as a percentage (0-100). For example, if you want OMEGAMON for Db2 PE to notify you when an application has used 80% of its allotment of database access threads, set the threshold to 80. The default threshold for MDBT is 85%.

OMEGAMON for Db2 PE displays the MDBW exception when the number of distributed database access threads waiting because the maximum has been reached exceeds the exception threshold. The maximum is set in DSNZPARM by the MAXDBAT parameter.

MDBW is a member of the system (SY) exception group. The exception threshold is expressed as an integer, that is, the number of threads waiting because MAXDBAT was reached. The default threshold for MDBW is 2.

OMEGAMON for Db2 PE displays the Db2 and IRLM messages that have been written to the system log since the last OMEGAMON for Db2 PE cycle, or as many of the messages as the LROWS parameter for the terminal allows, whichever is less.

MSGE is a member of the Db2 system (SY) exception group. The default threshold for MSGE is N/A. If State is ON and new messages exist, OMEGAMON for Db2 PE displays the messages.

The update count reflected in this exception is incremented each time a row in a page is updated. Updated pages are not necessarily written at commit, but rather later, asynchronously as determined by the Db2 Deferred Write algorithm. There is no direct immediate relationship between page updates and page writes.

The counters which Db2 maintains for this activity are updated throughout the life of the thread, and are reset at Db2 signon if the thread is reused.

PGUP is a member of the thread (TH) exception group. The default threshold for PGUP is 10 updates per second. The threshold can be any value between 1 and 1000 updates per second. If the active thread exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

POLU is a member of the CICS (CI) exception group. The default threshold for POLU is 90% of the total number of POOL threads allowed. The threshold can be any value between 1% and 100%. If the percentage of POOL threads exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

POLW is a member of the CICS (CI) exception group. The default threshold for POLW is two transactions. The threshold can be any value between 1 and 99 transactions. If the number of transactions waiting for a POOL thread exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

Unlike normal Read I/O, Sequential Prefetch Read I/O is performed asynchronously with the user's request. It provides a read-ahead capability. A single Sequential Prefetch I/O results in multiple pages being read. Threads with excessive sequential prefetch rates might cause reduced overall Db2 performance.

The counters which Db2 maintains for this activity are updated throughout the life of the thread, and are reset during Db2 signon if the thread is reused.

PREF is a member of the thread (TH) exception group. The default threshold for PREF is 10 Prefetch requests per second. The threshold can be any value between 1 and 100 Sequential Prefetch requests per second. If the prefetch rate exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

This exception analyzes the ratio of the resource limit high-water mark (CPU seconds) to the current resource limit.

RELM is a member of the thread (TH) exception group. The default threshold for RELM is 85 percent of the resource high-water mark (CPU seconds). The threshold can be any value between 1 and 100 percent of the resource limit. If the resource limit exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

Generally, this exception indicates excessive physical Read I/O on behalf of a thread. Although a single SELECT might return a limited number of rows, the pages searched might be enormous. I/O might be caused by access path selection changes which occurred due to object changes (indexes dropped or no longer clustered), or by inadvertent use of stage 2 (non-sargable) predicates. It might simply result from the fact that the SQL is a set-oriented language, which operates on sets of data, rather than on individual rows (records).

The counters which Db2 maintains for this activity are updated throughout the life of the thread, and are reset during Db2 signon if the thread is reused.

RIO is a member of the thread (TH) exception group. The default threshold for RIO is 10 Read requests per second. The threshold can be any value between 1 and 1000 synchronous Read requests per second. If the Read I/O rate per second exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

SUSL is a member of the Db2 system (SY) exception group. The default threshold for SUSL is five suspended threads. The threshold can be any value between 1 and 100 suspended threads. If the number of lock suspensions exceeds the threshold value, OMEGAMON for Db2 PE displays the exception.

For non-CICS threads, this is the CPU rate of the address space from which the thread originates. It includes both TCB and SRB time. For CICS threads, this is the CPU rate attributable to the thread originating from the CICS connection. It includes only TCB time incurred by the thread.

This exception limits its analysis of CPU use to Db2 connections that contain active threads. This exception does not report CPU use for connections with no active threads.

TCPU is a member of the thread (TH) exception group. The default threshold for TCPU is 20% of total processor utilization. The threshold can be any value between 1% and 100%. If CPU utilization exceeds the threshold value, OMEGAMON for Db2 PE displays the exception.

OMEGAMON for Db2 PE displays this exception when the number of users queued and waiting for create-thread processing exceeds the exception threshold.

This exception might indicate that Db2 reached the CTHREAD value that controls the number of active threads.

THDQ is a member of the Db2 system (SY) exception group. The default threshold for THDQ is 2. The threshold is a value between 1 and 100 requests. If the number of requests queued and waiting for Create Thread processing exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

Db2 thread concurrency can be controlled by the CTHREAD value. CTHREAD defines the maximum number of concurrent threads allowed.

TMAX is a member of the Db2 system (SY) exception group. The default threshold for TMAX is 85% of the CTHREAD installation parameter. The threshold can be any value between 1 and 100%. If the ratio of active threads to the CTHREAD parameter exceeds the threshold, OMEGAMON for Db2 PE displays the exception.

OMEGAMON for Db2 PE displays the TRCV exception when it detects that a distributed thread has received an amount of data greater than the exception threshold.

TRCV is a member of the thread (TH) exception group. The exception threshold is expressed in KB. The default threshold for TRCV is 1000 KB.

OMEGAMON for Db2 PE displays the TSND exception when it detects that a distributed thread has sent an amount of data greater than the exception threshold.

TSND is a member of the thread (TH) exception group. The exception threshold is expressed in KB. The default threshold for TSND is 1000 KB.

UTIS is a member of the system (SY) exception group. The default state for UTIS is OFF. If State is ON and a Db2 utility has been started but has not yet completed running due to abnormal termination, OMEGAMON for Db2 PE displays the exception.