Title

Handling Exceeded DB2 Thresholds

Name

DSNC011I

Table

DB2

Message

Either of the following messages:

DSNC011I xxxx TRANSACTION ABENDED BECAUSE THREADS ARE UNAVAILABLE

DSNU086I csect ttttt I/O ERRORS ON SPACE=dddddddd. DATASET NUMBER=nnn. I/O ERROR PAGE RANGE=aaaaaa,bbbbbb

Message Description

Messages handled by other rules comprising the DB2 solutions.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations

Global Variables

None.

Rule Logic

To avoid message overload situations, this rule deactivates DB2 rules whose messages have exceeded a predetermined number of appearances in a period of time.

These threshold values are defined for every message included in this rule in the threshold parameter APPEARED ### TIMES IN #### MINUTES. (The default is 5 times in 720 minutes.)

To synchronize threshold handling correctly, this rule is assigned a higher PRIORITY value than the message rules that it monitors, and has a CONTINUE SEARCH value of Y (Yes).

Deactivation of a message rule is achieved by adding the inverse IN prerequisite condition that is defined for the rule.

To reactivate the deactivated message rule, the threshold conditions must be deleted. This can be done either manually or automatically by Control-O (see the following section).

Threshold conditions must be specified in the IGNORE list of the Control-M CONTDAY procedure (see SolveWare Implementation Considerations).

Rule Actions

• Notifies user U-SYSDBA that the message that has exceeded its threshold is no longer handled by Control-O.
• Sets the appropriate IN condition to deactivate the rule. The format of this condition is:
• CTO-msgid-THRESH
  where msgid is the message ID of the specific message.

Activating the Rule

Once scheduled, the rule is triggered whenever one of the above messages exceeds its threshold.

Recommended Mode or Category

During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for this rule.

The SolveWare category for this rule is 2—some customization is required before implementation.

Customization

Review each DB2 message monitored by this rule and determine appropriate threshold values.

For each message included in this rule, adapt to site requirements the APPEARED ### TIMES IN #### MINUTES value, which specifies a number of appearances in a time period.

Title

Resetting DB2 Rule Threshold Conditions

Name

RESDB2

Table

DB2

Event

RESDB2

Event Description

This Event rule deletes all threshold conditions for all DB2 rules.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations

Global Variables

None.

Rule Logic

Using the INTERVAL parameter, this rule periodically deletes the threshold conditions of all DB2 rules in order to reactivate DB2 rules that exceeded their thresholds. For more information regarding the resetting of threshold conditions, see Customization in this table.

Rule Actions

• Deletes condition or date CTO-DSNC011I-THRESH STAT
• Deletes condition or date CTO-DSNU086I-THRESH STAT

Activating the Rule

Once scheduled, the rule is triggered periodically according to the INTERVAL parameter specification.

Recommended Mode or Category

During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for this rule.

The SolveWare category for this rule is —some customization is required before implementation.

Customization

Adapt the INTERVAL parameter to site requirements:

If you use the INTERVAL parameter without the TIME FROM parameter, the threshold conditions are deleted when the rule is ordered.

Note: Threshold conditions must also be deleted at time of IPL (see SolveWare Initialization).

Threshold conditions must be specified in the IGNORE list of the Control-M CONTDAY procedure (see SolveWare Implementation Considerations ).