Title

ADABAS MPMxx Initialization Started

Name

IEF403I

Table

ADABAS

Message

IEF403I jjj STARTED { - TIME=hh.mm.ss}

when the message is issued from job MPM*.

Message Description

Job jjj starts.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

As soon as ADABAS is started, the IOA environment is informed that ADABAS is no longer down.

Rule Actions

Deletes condition or date CTO-adabasname-DOWN STAT, where adabasname is the name of the ADABAS job or started task.

Activating the Rule

Once scheduled, the rule remains active until deleted from Control-O.

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 that controls ADABAS conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule.

Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true:

• The IOA environment already contains a prerequisite condition indicating that ADABAS is up or down.
  For example, if such a condition is already referenced by a Control-M job scheduling definition.
• The prerequisite condition has a different name than the one indicated in this rule.

The rule assumes that the name of the production ADABAS environments starts with MPM. This prefix may need to be changed (in the rule’s ON statement) in order to match site conventions.

Title

ADABAS Initialization Completed

Name

ADAN01

Table

ADABAS

Message

ADAN01 adabasname time ADABAS IS ACTIVE

Message Description

ADABAS has completed initialization and is up.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

As soon as ADABAS initialization has been completed, the IOA environment is informed that ADABAS is up.

Rule Actions

Adds condition or date CTO-adabasname-UP STAT,
where adabasname is the name of the ADABAS job or started task.

Activating the Rule

Once scheduled, the rule remains active until deleted from Control-O.

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 that controls ADABAS conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule.

Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true:

• The IOA environment already contains a prerequisite condition indicating that ADABAS is up or down.
  For example, if such a condition is already referenced by a Control-M job scheduling definition.
• The prerequisite condition has a different name than the one indicated in this rule.

  Table 114 ADABAS Termination Started Rule Structure

Title

ADABAS Termination Started

Name

ADAN51

Table

ADABAS

Message

ADAN51 adabasname OPER,TYPEIN:xxxxxx when xxxxxx is ABEND

Message Description

xxxxxx indicates the last operator command issued to ADABAS. When this command is ABEND, the message indicates that ADABAS termination started.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

ADABAS received an ABEND command from the operator and the IOA environment is informed that ADABAS is no longer up.

Rule Actions

Deletes condition or date CTO-adabasname-UP STAT,
where adabasname is the name of the ADABAS job or started task.

Activating the Rule

Once scheduled, the rule remains active until deleted from Control-O.

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 that controls ADABAS conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule.

Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true:

• The IOA environment already contains a prerequisite condition indicating that ADABAS is up or down.
  For example, if such a condition is already referenced by a Control-M job scheduling definition.
• The prerequisite condition has a different name than the one indicated in this rule.

  Table 115 ADABAS MPMxx Termination Completed Rule Structure

Title

ADABAS MPMxx Termination Completed

Name

IEF404I

Table

ADABAS

Message

IEF404I jjj ENDED { – TIME=hh.mm.ss}

when the message is issued from job MPM*.

Message Description

Job jjj ended.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

When ADABAS job ends, the IOA environment is informed that ADABAS is down.

Rule Actions

• Deletes condition or date CTO-adabasname-UP STAT,
  where adabasname is the name of the ADABAS job or started task.
• Adds condition or date CTO-adabasname-DOWN STAT,
  where adabasname is the name of the ADABAS job or started task.

Activating the Rule

Once scheduled, the rule remains active until deleted from Control-O.

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 that controls ADABAS conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule.

Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true:

• The IOA environment already contains a prerequisite condition indicating that ADABAS is up or down.
  For example, if such a condition is already referenced by a Control-M job scheduling definition.
• The prerequisite condition has a different name than the one indicated in this rule.

The rule assumes that the name of each production ADABAS environment starts with MPM. This prefix may need to be changed (in the rule’s ON statement) in order to match site conventions.

Title

Suppress S MPMxx if ADABAS Is Active

Name

S MPMxx

Table

ADABAS

Command

S MPMxx

Command Description

This command starts ADABAS (and the rule suppresses the command).

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

IN !CTO-adabasname-DOWN STAT

where adabasname is the name of the ADABAS job or started task

Global Variables

None.

Rule Logic

In general, if command S MPMxx is issued when ADABAS is already up, either the new started task is immediately shut down, or it waits until the currently running task goes down and then starts automatically. In either case, other rules in this solution can be triggered, causing erroneous updating of prerequisite conditions, thus incorrectly triggering jobs in Control-M.

This rule prevents the situations described above by suppressing the S MPMxx command if ADABAS is already up. In this way, issuance of the termination messages, or starting of the task without a message being sent, is prevented and rules are not incorrectly triggered.

This rule serves as a sample rule. A similar rule must be created for each ADABAS environment in the site.

Rule Actions

• Suppresses the command.
• Sends a message to user U-SHIFTOPER indicating that command S MPMxx was suppressed.

Activating the Rule

Once scheduled, the rule becomes active when prerequisite condition or date CTO-adabasname-DOWN STAT is deleted (where adabasname is the name of the ADABAS job or started task).

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

Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true:

• The IOA environment already contains a prerequisite condition indicating that ADABAS is up or down.
  For example, if such a condition is already referenced by a Control-M job scheduling definition.
• The prerequisite condition has a different name than the one indicated in this rule.

The rule must be duplicated for each ADABAS job or started task in the site. To adapt each rule, the ADABAS name in the rule’s ON statement and IN condition must be changed.