Title

Handling Exceeded DUMPDS Thresholds

Name

IEA911E

Table

DUMPDS

Message

Any of the following messages:

IEA911E { COMPLETE | PARTIAL } DUMP ON SYS1.DUMPxx FOR ASID asn

IEA994A ALL DUMP DATASETS ARE FULL AND NO SVC DUMPS CAN BE PRODUCED

IEA994E ALL ALLOCATED SYS1.DUMP DATASETS ARE FULL

IEE711I { SYSTEM UNABLE TO DUMP | SYSTEM DUMP NOT PRODUCED reason-text }

Message Description

All messages handled by rules comprising the DUMPDS 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 DUMPDS rules whose messages have exceeded a pre-determined number of appearances in a period of time.

These threshold values are defined for every message included in this rule in the threshold parameters APPEARED ### TIMES IN #### 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 DUMPDS rule is achieved by adding the appropriate (inverse) IN prerequisite condition that is defined for the rule.

To reactivate a deactivated rule, the threshold conditions must be deleted. This can be done either manually or automatically by Control-O.

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

Rule Actions

• Notifies user U-SYSADMIN 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, the rule must be activated 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 DUMPDS message monitored by this rule and determine threshold parameters. Take into consideration the total number of dump datasets in your site, the frequency of producing dumps, and so on.

For every message included in this rule, adapt APPEARED ### TIMES IN #### MINUTES values, which specify a number of appearances in a time period, to site requirements.

Title

Resetting DUMPDS Rule Threshold Conditions

Name

RESDUMP

Table

DUMPDS

Event

RESDUMP

Event Description

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

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations

Global Variables

None.

Rule Logic

Using the parameters INTERVAL and TIME FROM, this rule periodically deletes the threshold conditions of all DUMPDS rules in order to reactivate DUMPDS rules that exceeded their thresholds. (For more information about resetting threshold conditions, see Customization in this table.)

Rule Actions

• Deletes condition or date CTO-IEA911E-THRESH STAT
• Deletes condition or date CTO-IEA994A-THRESH STAT
• Deletes condition or date CTO-IEA994E-THRESH STAT
• Deletes condition or date CTO-IEE711I-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, the rule must be activated 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

Adapt the INTERVAL parameter to site requirements:

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

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

Threshold conditions must be specified in the IGNORE list of the Control-M CONTDAY procedure. For more information, see SolveWare Implementation Considerations.