Title

Notify Control-M That DB2 Is Up

Name

DSN9022I

Table

DB2

Message

DSN9022I DSNYASCP `verb' NORMAL COMPLETION

where verb is – START DB2.

Message Description

Synchronous processing for command – START DB2 ended without error. DB2 is up and ready. "–" is a one-character identifier that identifies the DB2 subsystem.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

This rule, triggered by the above message, sets the IOA conditions that indicate DB2's status (up or down). This way, jobs in Control-M that are waiting for DB2 to be up can be submitted and jobs that require DB2 to be down are not submitted.

Rule Actions

• Deletes condition or date CTO-DB2-DOWN STAT
• Adds condition or date CTO-DB2-UP STAT
• Deletes condition or date CTO-DB2-DOWN-smfid STAT
• Adds condition or date CTO-DB2-UP-smfid STAT

Note: smfid is the SMF ID of the CPU.

Activating the Rule

Once scheduled, the rule is triggered whenever the above message is issued by the DB2 subsystem.

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 the rule.

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

Customization

Each DB2 subsystem in the installation has a 1-character identifier and all commands that refer to this DB2 subsystem must start with this character. Adapt "–" in command –START DB2 (inside the rule definition) to identify the relevant (production) DB2 subsystem in your installation.

If a different mechanism to control DB2 status (utility IOACND, Control-M Event Manager, and so on) is already implemented, the mechanism must be removed before implementing this rule.

Change the condition names either in this rule or in the existing job scheduling definitions, if both of the following are true:

• The IOA environment already uses prerequisite conditions indicating that DB2 is up or down. For example, if such conditions are already referenced by Control-M job scheduling definitions.
• The prerequisite conditions have different names than the ones indicated in this rule.

Note: As noted earlier, IOA DB2 prerequisite conditions must also be updated at time of IPL to indicate that the various DB2 subsystems are down. For details, see SolveWare Initialization.

Title

Notify Control-M That DB2 Is Down

Name

DSN3100I

Table

DB2

Message

Any of the following messages:

DSN3100I csect SUBSYSTEM ssss READY FOR START COMMAND

DSN3104I csect - TERMINATION COMPLETE

DSN3106I csect SUBSYSTEM STOPPED. COMMAND cmd IGNORED

Message Description

DB2 subsystem is down. It can be started by issuing a start command.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

This rule, triggered by any of the above messages, sets the IOA conditions that indicate DB2's status (up or down). This way, jobs in Control-M that are waiting for DB2 to be down can be submitted and jobs that require DB2 to be up are not submitted.

Rule Actions

• Deletes condition or date CTO-DB2-UP STAT
• Adds condition or date CTO-DB2-DOWN STAT
• Deletes condition or date CTO-DB2-UP-smfid STAT
• Adds condition or date CTO-DB2-DOWN-smfid STAT

Note: smfid represents the SMF ID of the CPU.

Activating the Rule

Once scheduled, the rule is triggered whenever one of the above messages is issued by the DB2 subsystem.

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 the rule.

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

Customization

If a different mechanism to control DB2 status (utility IOACND, Control-M Event Manager, and so on) is already implemented, the mechanism must be removed before implementing this rule.

Change the condition names either in this rule or in the existing job scheduling definitions, if both of the following are true:

• The IOA environment already uses prerequisite conditions indicating that DB2 is up or down. For example, if such conditions are already referenced by Control-M job scheduling definitions.
• The prerequisite conditions have different names than the ones indicated in this rule.

Note: As noted earlier, IOA DB2 prerequisite conditions must also be updated at time of IPL to indicate that the various DB2 subsystems are down. For details, see SolveWare Initialization.