DUMPDS

DUMPDS solutions are designed to automate management of system dump datasets. Various components of the MVS environment produce dumps that include diagnostic information regarding a problem. These dumps are kept in the dump dataset SYS1.DUMPxx.

A common way of managing the dump files is to ensure that there are always several empty dump files to which new dumps can be written. This solution implements this method of work.

All messages (DO SHOUT actions) in the DUMPDS rules are sent to an INCONTROL user named U-SYSADMIN. A user with this name must be defined in the IOA Dynamic Destination table (CTMDEST). For more information, see the Dynamic Destination Table chapter of the INCONTROL for z/OS Administrator Guide.

In many cases, rules definitions make use of the inverse IN Condition feature. This feature activates rules only if the specified IN conditions are not set. For more information about using inverse IN conditions, see Inverse IN Conditions.

Solutions Provided

SolveWare subject DUMPDS contains the following solutions:

Copy and Clean SYS1.DUMPxx
For situations where an insufficient number of SYS1.DUMP files are available. A copy and clean job is automatically sent to prevent loss of system information.
DUMPDS Rule Thresholds
Handles exceeded thresholds of all other DUMPDS rules.

Copy and Clean SYS1.DUMPxx

In an MVS environment, a predefined number of dump datasets is defined and allocated. These files are named SYS1.DUMPxx. Whenever any system component produces a dump, it is directed to one of the empty (available) dump files.

If all dump files are full, the current dump cannot be produced and important information may be lost.

This solution is designed to ensure that a pre-specified number of empty dump datasets is always available for new dumps. The solution responds to MVS messages that indicate that no dump datasets are available, and after a dump has been produced, it checks that there is still a sufficient number of empty dump datasets.

Rules

The Copy and Clean SYS1.DUMPxx solution includes the Complete or Partial Dump Produced, All Dump Datasets Full rule.

Rules Structure

The following tables describe the structures of the Complete or Partial Dump Produced, All Dump Datasets Full solution rules.

Table 69 Complete or Partial Dump Produced, All Dump Datasets Are Full Rule Structure

Item	Description
Title	Complete or Partial Dump Produced, All Dump Datasets Full
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	IEA911E – An SVC dump was written to a SYS1.DUMP dataset. IEA994A, IEA994E – All SYS1.DUMP datasets are full. The current dump, and subsequent dumps, cannot be produced. IEE711I – An SVC dump cannot be produced.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations
Global Variables	%%DUMP_AVAIL The number of empty dump datasets that must be available for new dumps at any time. %%CLEAR_DUMPxx Flag indicating whether to clear dump dataset SYS1.DUMPxx. This variable is set for every dump dataset in the system. Valid values are: YES NO
Rule Logic	This rule is triggered when a dump is produced, or when no empty dump dataset is found. Either situation normally requires a user response. The user must check if a sufficient number of empty dump datasets is available, and if not, the user must clear dump datasets using command DUMPDS, or utility IEBGENER, or using IPCS. The rule issues command DISPLAY DUMP to obtain SYS1.DUMP dataset information that it uses to determine the number of dump datasets currently available. The rule then checks if this number is sufficient according to the value specified by the user in Global AutoEdit variable %%DUMP_AVAIL, which that reflects the number of empty dump datasets that are available for new dumps at any time. If enough datasets are empty, the rule ends and no actions are performed. If there is a need to empty dump files, then for each SYS1.DUMP dataset, the rule sets a flag indicating whether to clear the dataset. The flags are set in Global AutoEdit variables referenced by the job JCL. The rule adds prerequisite condition or date CTO-CLRDUMP-GO 0101, which triggers a pre-scheduled job in Control-M to clear the dump datasets. (For further details on the job scheduling definition, see Customization in this table.) Once the rule has been triggered, it is temporarily deactivated by setting its own inverse IN condition. This prevents multiple triggering of the rule caused by additional appearances of the above messages before the job has finished cleaning the specified SYS1.DUMPxx datasets. Once the job has successfully executed, condition CTO-IEA911E-HANDLED is deleted to reactivate the rule. Condition CTO-CLRDUMP-GO, which triggered the pre-scheduled job, is deleted upon completion of the job.
Rule Actions	Sets Global AutoEdit variable %%DUMP_AVAIL to 1. This variable reflects the number of empty dump datasets that must be available at any time (see Rule Logic in this table). The default value of 1 can be changed by the user—see Customization in this table. Sets condition CTO-IEA911E-HANDLED to deactivate the rule temporarily (see Rule Logic in this table). Sets variable %%RESPMSG to IEE852I. Issues operator command DISPLAY DUMP. Analyzes response message IEE852I to determine the number of currently available dump datasets. Sets Global AutoEdit variable %%CLEAR_DUMPxx to YES or NO to indicate which datasets to empty. Issues a command instructing Control-O to write Global AutoEdit variables. Sets prerequisite condition CTO-CLRDUMP-GO to start a job in Control-M to clear flagged dump datasets.
Activating the Rule	Once ordered, the rule remains active until one of the messages IEA911E, IEA994A, IEA994E, or IEE711I exceeds a pre-defined threshold. (For more information regarding threshold handling, see DUMPDS Rule Thresholds.) The rule is also temporarily deactivated when it is triggered and reactivated after the copy and/or clean job finishes OK (see Rule Logic in this table).
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 the rule. The SolveWare category for this rule is 2—some customization is required before implementation.
Customization	If a different automatic mechanism to clean SYS1.DUMPxx is already implemented, the mechanism must be removed before testing this rule. A job scheduling definition and JCL member for the SYS1.DUMPxx copy and or clean job must be created. SOLVSCHD and SOLVJCL Libraries contain a sample scheduling definition and JCL to copy and or clean SYS1.DUMPxx. This sample can be adapted to site conventions and requirements. The supplied sample job executes program utility IPCS, which prints and clears the dump datasets. This job can be modified to use a different method to clear the dump files such as the DUMPDS command.
Customization (continued)	The supplied sample job includes %%LIBSYM and %%MEMSYM AutoEdit control statements, which reference the Control-O $GLOBAL member. SYS1.DUMP flags (AutoEdit variables that indicate whether to clear specific datasets) must be included in this member. The job must be defined as a cyclic job or cyclic started task (STC) with a MAXWAIT value of 99. It then only needs to be ordered once, but must not be removed manually from the Control-M Active Jobs file. The MAXWAIT value of 99 ensures that the job is never removed from the Active Jobs file by the Control-M New Day procedure. The cyclic job is always ready for submission. It is triggered by adding the prerequisite condition or date CTO-CLRDUMP-GO 0101. When an execution of the job is completed, this condition is deleted. This prevents cyclic re-invoking of the job and ensures that the job is only invoked again if the rule is triggered again. If there is a need to empty dump files, then for each SYS1.DUMP dataset, the rule sets a flag indicating whether to clear the dataset. The flags are set in Global AutoEdit variables referenced by the job JCL. This is done by including the Control-O $GLOBAL member in the job JCL and defining %%LIBSYM and %%MEMSYM AutoEdit control statements. In the rule definition, the default value supplied for Global AutoEdit variable %%DUMP_AVAIL is 1, meaning that at least one dump dataset must be left empty at all times. This value must be adapted to site requirements. Prerequisite condition or date CTO-IEA911E-HANDLED STAT must be deleted at time of IPL to make sure the rule is active after system startup. For more information, see SolveWare Initialization.

DUMPDS Rule Thresholds

This solution handles message overload – situations in which a message appears on the console more times than is desirable. If a SYS1.DUMP related message appears too often on the system console, threshold rules deactivate the relevant DUMPDS rule until the source of the problem is found and the problem corrected.

For more information on threshold handling, see Rule Thresholds.

Rules

The DUMPDS Rule Thresholds solution includes the following rules:

Handling Exceeded DUMPDS Thresholds
Resetting DUMPDS Rule Threshold Conditions

Rules Structure

The following tables describe the structures of the DUMPDS Rule Thresholds solution rules.

Table 70 Handling Exceeded DUMPDS Thresholds Rule Structure

Item	Description
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.

Table 71 Resetting DUMPDS Rule Threshold Conditions Rule Structure

Item	Description
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. 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.