System Status Situations

Use the series of predefined situations associated with the System Status workspace to begin monitoring your system immediately or as templates for creating your own situations.

The names, descriptions, logic, and threshold values for the situations follow.

KD5_LPAR_CPU_Warning monitors the processor consumption for the LPAR that is being monitored. A warning condition is detected when the consumption reaches 70% of the capacity of the processor. The situation's formula is:

ZOS_System_Statistics.CPU_Utilization_LPAR GTE 70

KDP_ARCV_Critical monitors the status of a DB2 recovery log archive. A critical condition is detected when an active DB2 log is full and must be archived, and a tape mount is outstanding for the archive log. The situation's formula is:

KDP_System_States.Waiting_On_Tape_Mount EQ TRUE

KDP_ARCV_Warning monitors the status of a DB2 recovery log archive. A warning condition is detected when an active DB2 log is full and must be archived, and a tape mount is outstanding for the archive log. The situation's formula is:

KDP_System_States.Waiting_On_Tape_Mount EQ TRUE

KDP_DDFS_Critical monitors the status of the distributed database facility (DDF), detecting a critical condition when the DDF is inactive. This condition could indicate that the DDF terminated abnormally or that it was not started. The situation's formula is:

KDP_System_States.Dist_DB_Inactive EQ TRUE

KDP_DDFS_Warning monitors the status of the distributed database facility (DDF), detecting a warning condition when the DDF is inactive. This condition could indicate that the DDF terminated abnormally or that it was not started. The situation's formula is:

KDP_System_States.Dist_DB_Inactive EQ TRUE

KDP_DRCV_Critical monitors the rate of data received by a requestor (local) or server (remote) DB2 subsystem in response to SQL requests. A critical condition is detected when the rate reaches 1000 kilobytes/second. The situation's formula is:

KDP_System_States.Dist_Receive_Rate GE 1000.0

KDP_DRCV_Warning monitors the rate of data received by a requestor (local) or server (remote) DB2 subsystem in response to SQL requests. A warning condition is detected when the rate is in the range of 800 to 1000 kilobytes/second. The situation's formula is:

KDP_System_States.Dist_Receive_Rate GE 800.0

AND

KDP_System_States.Dist_Receive_Rate LT 1000.0

KDP_DSND_Critical monitors the amount of data sent to a requestor (local) or server (remote) DB2 subsystem. A critical condition is detected when the rate reaches 1000 kilobytes/second. The situation's formula is:

KDP_System_States.Dist_Send_Rate GE 1000.0

KDP_DSND_Warning monitors the amount of data sent to a requestor (local) or server (remote) DB2 subsystem. A warning condition is detected when the rate is in the range of 800 to 1000 kilobytes/second. The situation's formula is:

KDP_System_States.Dist_Send_Rate GE 800.0

AND

KDP_System_States.Dist_Send_Rate LT 1000.0

KDP_EDMU_Critical:

For DB2 9 or below: KDP_EDMU_Critical monitors the usage of environmental descriptor manager (EDM) pool pages. DB2 uses the EDM pool to manage and contain cursor tables (CTs) and package tables (PTs).
For DB2 10 or later: KDP_EDMU_Critical monitors the usage of database descriptor (DBD) pool pages. DB2 uses the DBD pool to manage and contain database descriptors (DBDs).

A critical condition is detected when the percentage in use based on the total pool size reaches 90%. The situation's formula is:

KDP_System_States.EDM_Utilization GE 90.0

For DB2 9 or below: KDP_EDMU_Critical monitors the usage of environmental descriptor manager (EDM) pool pages. DB2 uses the EDM pool to manage and contain cursor tables (CTs) and package tables (PTs).
For DB2 10 or later: KDP_EDMU_Critical monitors the usage of database descriptor (DBD) pool pages. DB2 uses the DBD pool to manage and contain database descriptors (DBDs).

A warning condition is detected when the percentage in use based on the total pool size is in the range of 72% to 90%. The situation's formula is:

KDP_System_States.EDM_Utilization GE 72.0
AND

KDP_System_States.EDM_Utilization LT 90.0

KDP_EDMU_Warning monitors the usage of environmental descriptor manager (EDM) pool pages. DB2 uses the EDM pool to manage and contain database descriptors (DBDs), cursor tables (CTs), skeleton cursor tables (SKCTs), package tables (PTs), skeleton package tables (SKPTs), and dynamic SQL caches (DSCs). A warning condition is detected when the percentage in use based on the total pool size is in the range of 72% to 90%. The situation's formula is:

KDP_System_States.EDM_Utilization GE 72.0

AND

KDP_System_States.EDM_Utilization LT 90.0

KDP_GTRC_Critical monitors the status of the DB2 global trace. It should not be active unless there is a specific purpose, such as diagnostic testing. The DB2 global trace can increase performance overhead. A critical condition is detected when the DB2 global trace is active. The situation's formula is:

KDP_System_States.Global_Trace_Active EQ TRUE

KDP_GTRC_Warning monitors the status of the DB2 global trace. It should not be active unless there is a specific purpose, such as diagnostic testing. The DB2 global trace can increase performance overhead. A warning condition is detected when the DB2 global trace is active. The situation's formula is:

KDP_System_States.Global_Trace_Active EQ TRUE

KDP_INDT_Critical monitors the number of in doubt threads in the DB2 system. A critical condition is detected when the number of terminated threads that are in doubt reaches two. The situation's formula is:

KDP_System_States. Indoubt_Threads GE 2

KDP_INDT_Warning monitors the number of in doubt threads in the DB2 system. A warning condition is detected when the number of terminated threads that are in doubt reaches two. The situation's formula is:

KDP_System_States. Indoubt_Threads GE 2

KDP_MDBT_Critical monitors the percentage of maximum allowed database access threads that are in use. The maximum is set in DSNZPARM by the MAXDBAT parameter. When the MAXDBAT limit is reached, conversations are queued (waiting on DBAT allocation), which can greatly increase response time. A critical condition is detected when the number of distributed database access threads in use reaches 85% of the preset maximum. The situation's formula is:

KDP_System_States.DB_Wait_Percent GE 85.0

KDP_MDBT_Warning monitors the percentage of maximum allowed database access threads that are in use. The maximum is set in DSNZPARM by the MAXDBAT parameter. When the MAXDBAT limit is reached, conversations are queued (waiting on DBAT allocation), which can greatly increase response time. A warning condition is detected when the number of distributed database access threads in use is in the range of 68% to 85% of the preset maximum. The situation's formula is:

KDP_System_States.DB_Wait_Percent GE 68.0

AND

KDP_System_States.DB_Wait_Percent LT 85.0

KDP_MDBW_Critical monitors the number of database access threads that are waiting because MAXDBAT was reached. Queuing of conversations when the MAXDBAT limit is reached can greatly impact response time. A critical condition is detected when the number of database access threads that are waiting reaches two. The situation's formula is:

KDP_System_States.Thread_Wait_Limit GE 2

KDP_MDBW_Warning monitors the number of database access threads that are waiting because MAXDBAT was reached. Queuing of conversations when the MAXDBAT limit is reached can greatly impact response time. A warning condition is detected when the number of database access threads that are waiting is in the range of one to two. The situation's formula is:

KDP_System_States.Thread_Wait_Limit GE 1

AND KDP_System_States.Thread_Wait_Limit LT 2

KDP_SPAC_Critical monitors the number of ASIDs executing stored procedures. Stored procedures can be executed in a DB2 stored procedure address space and in any WLM-managed stored procedure address space. The threshold is a count of address spaces capable of executing stored procedures. A critical condition is detected when the count reaches five. The situation's formula is:

KDP_System_States.ASIDs_Stored_Procedures GE 5

KDP_SPAC_Warning monitors the number of ASIDs executing stored procedures. Stored procedures can be executed in a DB2 stored procedure address space and in any WLM-managed stored procedure address space. The threshold is a count of address spaces capable of executing stored procedures. A warning condition is detected when the count is in the range of two to five. The situation's formula is:

KDP_System_States.ASIDs_Stored_Procedures GE 2

AND

KDP_System_States.ASIDs_Stored_Procedures LT 5

KDP_STPE_Critical monitors the number of stored procedures executing. The threshold is expressed as a count of stored procedures currently executing. A critical condition is detected when the count reaches 20. The situation's formula is:

KDP_System_States.Active_Stored_Procedures GE 20

KDP_STPE_Warning monitors the number of stored procedures executing. The threshold is expressed as a count of stored procedures currently executing. A warning condition is detected when the count is in the range of 10 to 20. The situation's formula is:

KDP_System_States.Active_Stored_Procedures GE 10

AND

KDP_System_States.Active_Stored_Procedures LT 20

KDP_SUSL_Critical monitors the number of threads that are unable to continue execution because the number of lock waits exceeds the specified threshold. A critical condition is detected when the count reaches five suspended threads. The situation's formula is:

KDP_System_States.Thread_Wait_Lock GE 5

KDP_SUSL_Warning monitors the number of threads that are unable to continue execution because the number of lock waits exceeds the specified threshold. A critical condition is detected when the count is in the range of four to five suspended threads. The situation's formula is:

KDP_System_States.Thread_Wait_Lock GE 4

AND

KDP_System_States.Thread_Wait_Lock LT 5

KDP_THDQ_Critical detects users waiting for thread creation to occur. This exception may indicate that DB2 reached the CTHREAD value that controls the number of active threads. A critical condition is detected when the number of users waiting for create thread processing reaches two. The situation's formula is:

KDP_System_States.User_Waiting_Threads GE 2

KDP_THDQ_Warning detects users waiting for thread creation to occur. This exception may indicate that DB2 reached the CTHREAD value that controls the number of active threads. A warning condition is detected when the number of users waiting for create thread processing is in the range of one to two. The situation's formula is:

KDP_System_States.User_Waiting_Threads GE 1

AND

KDP_System_States.User_Waiting_Threads LT 2

KDP_TMAX_Critical monitors the percentage of active threads, by indicating when the number of active threads approaches the maximum number allowed. DB2 thread concurrency can be controlled by the CTHREAD value. CTHREAD defines the maximum number of concurrent threads allowed. A critical condition is detected when the percentage of active threads to the specified maximum reaches 85%. The situation's formula is:

DB2_SRM_Subsystem.Thread_Utilization GE 85

KDP_TMAX_Warning monitors the percentage of active threads, by indicating when the number of active threads approaches the maximum number allowed. DB2 thread concurrency can be controlled by the CTHREAD value. CTHREAD defines the maximum number of concurrent threads allowed. A warning condition is detected when the percentage of active threads to the specified maximum is in the range of 68% to 85%. The situation's formula is:

DB2_SRM_Subsystem.Thread_Utilization GE 68

AND

DB2_SRM_Subsystem.Thread_Utilization LT 85

KDP_TRGD_Critical monitors the depth of the largest trigger stack. A critical condition is detected when the number of triggers in the largest trigger stack reaches two. The situation's formula is:

KDP_System_States.Trigger_Depth GE 2

KDP_TRGD_Warning monitors the depth of the largest trigger stack. A warning condition is detected when the number of triggers in the largest trigger stack is in the range of one to two. The situation's formula is:

KDP_System_States.Trigger_Depth GE 1

AND

KDP_System_States.Trigger_Depth LT 2

KDP_TRGE_Critical monitors the number of triggers. A critical condition is detected when the number of active triggers reaches 20. The situation's formula is:

KDP_System_States.Active_Triggers GE 20

KDP_TRGE_Warning monitors the number of triggers. A warning condition is detected when the number of active triggers is in the range of 10 to 20. The situation's formula is:

KDP_System_States.Active_Triggers GE 10

AND

KDP_System_States.Active_Triggers LT 20

KDP_UDFE_Critical monitors the number of user-defined functions executing. A critical condition is detected when the number of user-defined functions reaches 20. The situation's formula is:

KDP_System_States.Active_User_Functions GE 20

KDP_UDFE_Warning monitors the number of user-defined functions executing. A warning condition is detected when the number of user-defined functions is in the range of 10 to 20. The situation's formula is:

KDP_System_States.Active_User_Functions GE 10

AND

KDP_System_States.Active_User_Functions LT 20

KDP_UFAC_Critical monitors the number of ASIDs executing user functions. A critical condition is detected when a count of address spaces capable of executing user-defined functions reaches five. User-defined functions can be executed only from WLM-managed stored procedure address spaces. The situation's formula is:

KDP_System_States.ASIDs_User_Functions GE 5

KDP_UFAC_Warning monitors the number of ASIDs executing user functions. A warning condition is detected when a count of address spaces capable of executing user-defined functions is in the range of two to five. User-defined functions can be executed only from WLM-managed stored procedure address spaces. The situation's formula is:

KDP_System_States.ASIDs_User_Functions GE 2

AND

KDP_System_States.ASIDs_User_Functions LT 5