Database Analysis situations

Warning threshold exceeded for DB2 maximum threads.

It is not detrimental to reach a high percentage of the maximum active thread limit. However, when the ratio frequently nears 100%, increase the value specified in the THRDA keyword of the DSNCRCT macro used to define the CICS® DB2 Resource Control Table for the transaction. You can also increase it dynamically using the MODIFY option of the DSNC transaction. Increasing the number of threads increases the overhead of the z/OS® dispatcher scanning the TCB chain.

Formula: If the value of Maximum_Active_Threads is greater than 20 and the value of Maximum_Active_Threads is less than or equal to 54 then situation CICSplex_DB2MaxThreads_Warning is true.

Critical threshold exceeded for DB2 maximum threads.

It is not detrimental to reach a high percentage of the maximum active thread limit. However, when the ratio frequently nears 100%, increase the value specified in the THRDA keyword of the DSNCRCT macro used to define the CICS DB2 Resource Control for the transaction. You can also increase it dynamically using the MODIFY option of the DSNC transaction. Increasing the number of threads increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Maximum_Active_Threads is greater than 54 then situation CICSplex_DB2MaxThreads_Critical is true.

Warning threshold exceeded for DB2 abort percent.

Consider changing the WAIT parameter in the DSNCRCT table to specify WAIT=YES or WAIT=POOL for this transaction. WAIT=YES allows a task to be queued when no threads are available; WAIT=POOL allows a task to use a pool thread. Increase the value specified in the THRDA keyword of the DSNCRCT macro used to define the CICS DB2 Resource Control for the transaction, or increase it dynamically using the MODIFY option of the DSNC transaction. Increasing the number of threads increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Abort_Percent is greater than 40 and the value of Abort_Percent is less than or equal to 65 then situation CICSplex_DB2Abort_Warning is true.

Critical threshold exceeded for DB2 abort percent.

Consider changing the TWAIT parameter in the DSNCRCT table to specify WAIT=YES or WAIT=POOL for this transaction. WAIT=YES allows a task to be queued when no threads are available; WAIT=POOL allows a task to use a pool thread. Increase the value specified in the THRDA keyword of the DSNCRCT macro used to define the CICS DB2 Resource Control for the transaction, or increase it dynamically using the MODIFY option of the DSNC transaction. Increasing the number of threads increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Abort_Percent is greater than 65 then situation CICSplex_DB2Abort_Critical is true.

Warning threshold exceeded for DB2 wait percent.

To reduce the percentage of waits, you can increase the maximum number of active threads for this transaction temporarily using either the MODIFY option of the DSNC transaction, or permanently by changing the THRDA parameter in the DSNCRCT. Increasing the number of threads, however, increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Wait_Percent is greater than 40 and the value of Wait_Percent is less than or equal to 65 then situation CICSplex_DB2Wait_Warning is true.

Critical threshold exceeded for DB2 wait percentage.

To reduce the percentage of waits, increase the maximum number of active threads for this transaction temporarily using either the MODIFY option of the DSNC transaction, or permanently by changing the THRDA parameter in the DSNCRCT. Increasing the number of threads, however, increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Wait_Percent is greater than 65 then situation CICSplex_DB2Wait_Critical is true.

Warning threshold exceeded for DB2 thread HWM.

If the problem is intermittent, increase the maximum number of active tasks for this transaction temporarily with the MODIFY option of the DSNC transaction. If the threshold is exceeded frequently, consider raising the maximum number of active threads by changing the THRDA parameter in the DSNCRCT. Increasing the number of threads, however, increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Threads_in_Use_Percent_HWM is greater than 70 and the value of Threads_in_Use_Percent_HWM is less than or equal to 90 then situation CICSplex_DB2ThreadHWM_Warning is true.

Critical threshold exceeded for DB2 thread HWM.

If the problem is intermittent, increase the maximum number of active tasks for this transaction temporarily with the MODIFY option of the DSNC transaction. If the threshold is exceeded frequently, consider raising the maximum number of active threads by changing the THRDA parameter in the DSNCRCT. Increasing the number of threads, however, increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Threads_in_Use_Percent_HWM is greater than 90 then situation CICSplex_DB2ThreadHWM_Critical is true.

Warning threshold exceeded for DB2 thread use.

If the problem is intermittent, increase the maximum number of active tasks for this transaction temporarily with the MODIFY option of the DSNC transaction. If the threshold is exceeded frequently, consider raising the maximum number of active threads by changing the THRDA parameter in the DSNCRCT. Increasing the number of threads, however, increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Threads_in_Use_Percent is greater than 70 and the value of Threads_in_Use_Percent is less than or equal to 90 then situation CICSplex_DB2ThreadUse_Warning is true.

Critical threshold exceeded for DB2 thread use.

If the problem is intermittent, increase the maximum number of active tasks for this transaction temporarily with the MODIFY option of the DSNC transaction. If the threshold is exceeded frequently, consider raising the maximum number of active threads by changing the THRDA parameter in the DSNCRCT. Increasing the number of threads, however, increases the overhead of the z/OS dispatcher scanning the TCB chain.

Formula: If the value of Threads_in_Use_Percent is greater than 90 then situation CICSplex_DB2ThreadUse_Critical is true.

Warning threshold exceeded for DB2 attach status.

Verify that DB2 is required for this CICS region. If DB2 is needed, attach DB2 for this region using DSNC STRTc, wherec is the appropriate RCT suffix. Include the DB2 startup program in the CICS startup PLT.

Formula: If the value of CICSplex_DB2_Summary.Attached_to_DB2 equals No then situation CICSplex_DB2Attached_Warning is true.

Critical threshold exceeded for DB2 attach status.

Verify that DB2 is required for this CICS region. If DB2 is needed, attach DB2 for this region using DSNC STRTc, wherec is the appropriate RCT suffix. Include the DB2 startup program in the CICS startup PLT.

Formula: If the value of CICSplex_DB2_Summary.Attached_to_DB2 equals No then situation CICSplex_DB2Attached_Critical is true.

Warning threshold exceeded for DBCTL active status.

Use the CICS transaction CDBC to connect CICS to DBCTL.

Formula: If the value of CICSplex_DBCTL_Summary.DBCTL_Active equals No then situation CICSplex_DBCTLAct_Warning is true.

Critical threshold exceeded for DBCTL active status.

Use the CICS transaction CDBC to connect CICS to DBCTL.

Formula: If the value of CICSplex_DBCTL_Summary.DBCTL_Active equals No then situation CICSplex_DBCTLAct_Critical is true.