Critical Event Monitoring
Purpose
Critical Event Monitoring handles specific critical events that may occur during normal day-to-day running of DB2®. These include:
| Message | Description |
|---|---|
| DSNB250E, DSNB311I, DSNB312I, DSNB320I, DSNB321I, DSNB322I, DSNB323I, DSNB350I, DSNB351I | Recover failed dataspace (for data sharing only) |
| DSNJ002I | Switch active log data sets |
| DSNR004I | RESTART...UR STATUS COUNTS |
| DSNP007I | Data set could not be extended |
| DSNJ110E | Last active log data set is % full |
| DSNJ111E | All active log data sets full |
| DSNJ115I | Archive data set could not be allocated |
| DSNT500I/DSNT501I | Resource unavailable |
Recovery commands that are required should be defined for the message in the automation's MESSAGES/USER DATA policy item for any DB2 subsystem that requires DB2 critical event message recovery.
If the DB2 subsystem is known to SA z/OS as an application of type DB2, event message recovery can be controlled by parameters entered via the DB2 CONTROL policy item for the subsystem.
Restrictions
Critical event monitoring is only done if the DB2 subsystem is defined to SA z/OS and if recovery is enabled for the invoking message ID minor resource.
For some recovery actions SYSOPR needs SYSCTRL authority.
Usage
For each of the Event Monitoring processes, the input parameters are validated for accuracy and any errors that are found are logged and the process is terminated. The requested subsystem is then checked to determine if automation is enabled for the major resource, and also that recovery is enabled for the invoking message ID minor resource. Once these preliminary checks have been successfully completed, the requested recovery action is performed.
DSNB250E, DSNB311I, DSNB312I, DSNB320I, DSNB321I, DSNB322I, DSNB323I, DSNB350I, DSNB351I: Recover Failed Dataspace
Description: You may want to start table spaces in response to these messages. To do this, specify the start command in the MESSAGES/USER DATA policy item for these messages in your automation policy as follows: INGDB2 TABLE &SUBSAPPL START
DSNJ002I: Switch Active Log Data Sets
Description: If commands are defined in the automation policy item MESSAGES/USER DATA for this message to an application of type DB2, these commands are only issued when the triggering message is for the log data set that is specified by the "Active log data set name" in the DB2 CONTROL policy item.
If the application is not of type DB2, the defined commands are issued unconditionally.
DSNR004I: RESTART...UR STATUS COUNTS
Description: If the message reports an INDOUBT counter greater than zero at the end of a DB2 restart process, ISSUEACT is called to issue commands that are defined in the automation policy item MESSAGES/USER DATA of the DB2 application for this message.
DSNP007I: Data Set Could Not Be Extended
Description: The created automation table statement calls ISSUEACT with its code specifications as the parameters. The code values are extracted from the message text. The data set name is passed as the CODE1 value, the return code is passed as the CODE2 value, and the connection ID is passed as the CODE3 value. If a code match is found with the ID of the triggering message in policy item MESSAGES/USER DATA, the value that is returned is used to select and issue the related commands as defined in the automation policy.
DSNJ110E: Last Active Log Data Set Is % Full
Description: If commands are defined in the automation policy item MESSAGES/USER DATA for this message to an application of type DB2, these commands are only issued when the message reports a percentage full figure that is equal to or greater than the critical threshold that is defined in the "Log full threshold" field of the DB2 CONTROL policy item.
If the application is not of type DB2, the defined commands are issued unconditionally.
DSNJ111E: All Active Log Data Sets Full
Description: If commands are defined in the automation policy item MESSAGES/USER DATA for this message to an application of type DB2, these commands are only issued when the number of received messages within a time period exceeds a given threshold. The time period and the threshold can be entered via the DB2 CONTROL policy item in the "Active log alerts" field and the related "Threshold" field.
If the application is not of type DB2, the defined commands are issued unconditionally.
DSNJ115I: Archive Data Set Could Not Be Allocated
Description: If commands are defined in the MESSAGES/USER DATA automation policy item for this message for an application of type DB2, these commands are only issued when the elapsed time since they were triggered by this message is greater than a given time interval, as specified in the Log offload interval field in the DB2 CONTROL policy item.
If the application is not of type DB2, the defined commands are issued unconditionally.
DSNT500I/501I: Generate DSNT500I/DSNT501I Alert
Description: The created automation table statement calls ISSUEACT with its code specifications as the parameters. The code values are extracted from the message text. The name is passed as CODE1, the reason is passed as CODE2 and the type is passed as CODE3. If a code match is found with the ID of the triggering message in policy item MESSAGES/USER DATA, the value that is returned is used to select and issue the related commands as defined in the automation policy.