DL/I Call Counts situations

You can monitor the database activity in a dependent region.

IMS_DepRegDLETCallHigh

Monitors the count of DLI Database DLET calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 DLET calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_DLET_Calls GT 100

IMS_DepRegDLICallHigh

Monitors the count of DB calls for a dependent region, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 1000 DLI calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_DLET_Calls GT 100

IMS_DepRegDLICallsPerTransHigh

Monitors the total DL/I database activity per transaction, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 DL/I calls per transaction.

The formula is: Dependent_Regions_Statistics.Total_Database_Per_Transaction GT 100

IMS_DepRegGHNCallHigh

Monitors the count of DLI Database GHN calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 GHN calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_GHN_Calls GT 100

IMS_DepRegGHNPCallHigh

Monitors the count of DLI Database GHNP calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 GHNP calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_GHNP_Calls GT 100

IMS_DepRegGHUCallHigh

Monitors the count of DLI Database GHU calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 GHU calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_GHU_Calls GT 100

IMS_DepRegGNCallHigh

Monitors the count of DLI Database GN calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 GN calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_GN_Calls GT 100

IMS_DepRegGNPCallHigh

Monitors the count of DLI Database GNP calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 GNP calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_GNP_Calls GT 100

IMS_DepRegGUCallHigh

Monitors the count of DLI Database GU calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 GU calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_GU_Calls GT 100

IMS_DepRegISRTCallHigh

Monitors the count of DLI Database ISRT calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 ISRT calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_ISRT_Calls GT 100

IMS_DepRegMsgGNCallHigh

Monitors the count of DLI Message GN calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 10 Message GN calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Message_GN_Calls GT 10

IMS_DepRegMsgGUCallHigh

Monitors the count of DLI Message GU calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 10 Message GU calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Message_GU_Calls GT 10

IMS_DepRegMsgISRTCallHigh

Monitors the count of DLI Message ISRT calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 10 Message ISRT calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Message_ISRT_Calls GT 10

IMS_DepRegMsgPURGCallHigh

Monitors the count of DLI Message PURG calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 10 Message PURG calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Message_PURG_Calls GT 10

IMS_DepRegMsgTotalCallHigh

Monitors the count of DLI Message Total calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 10 Message Total calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Message_Total_Calls GT 10

IMS_DepRegREPLCallHigh

Monitors the count of DLI Database REPL calls, and automatically generates an exception when the count exceeds the threshold. This dependent region has been identified as having done more than 100 REPL calls. This might indicate a looping transaction.

The formula is: Dependent_Regions_Statistics.Database_REPL_Calls GT 100