Previous Topic

Next Topic

Book Contents

Book Index

Rules Structure

The following tables describe the structures of the IMS Startup and Termination solution rules.

Table 94 IMS Initialization Started Rule Structure

Item

Description

Title

IMS Initialization Started

Name

IEF403I

Table

IMS

Message

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

when the message is issued from job IMS* (* is the generic mask character).

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 IMS is started, the IOA environment is informed that IMS is no longer down.

Rule Actions

Deletes condition or date CTO-imsname-DOWN STAT (where imsname is the name of the IMS 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 IMS conditions (utility IOACND, Control-M Event Manager, and so on) is already implemented, the existing mechanism must be removed before implementing this rule.

Change the name of the prerequisite condition deleted by this rule to match your previous definition, if both of the following are true:

  • The IOA environment already contains a prerequisite condition indicating that IMS is 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.

If required, change the IMS job or started task name mask in field JNAME of the rule’s ON block to conform to local naming conventions. The default-defined value is IMS*.

Table 95 IMS Initialization Completed Rule Structure

Item

Description

Title

IMS Initialization Completed

Name

DFS994I

Table

IMS

Message

One of the following messages:

DFS994I rtype START COMPLETED

DFS994I rtype EMERGENCY START COMPLETED

DFS994I TAKEOVER COMPLETED

Message Description

IMS has completed initialization and is up.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

When IMS is completely up, the IOA environment is informed that IMS is up.

Rule Actions

  • Checks that the third word of the message is START (to distinguish between different meanings of message DFS994I).
  • Adds condition or date CTO-imsname-UP STAT
    where imsname is the name of the IMS 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 IMS conditions (utility IOACND, Control-M Event Manager, and so on) is already implemented, the existing mechanism must be removed before implementing this rule.

Change the name of the prerequisite condition added by this rule to match your previous definition, if both of the following are true:

  • The IOA environment already contains a prerequisite condition indicating that IMS is up. 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 96 IMS Termination Started Rule Structure

Item

Description

Title

IMS Termination Started

Name

DFS32571

Table

IMS

Message

DFS3257I ONLINE LOG CLOSED ON ddname

when the message contains string CLOSED in columns 21–26

Message Description

IMS shutdown has started and the Online Log Dataset (OLDS) is closed.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

When IMS termination has started, the IOA environment is informed that IMS is no longer up.

Rule Actions

Deletes condition or date CTO-imsname-UP STAT
where imsname is the name of the IMS 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 IMS conditions (utility IOACND, Control-M Event Manager, and so on) is already implemented, the existing mechanism must be removed before implementing this rule.

Change the name of the prerequisite condition deleted by this rule to match your previous definition, if both of the following are true:

  • The IOA environment already contains a prerequisite condition indicating that IMS is up. 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 97 IMS Termination Completed Rule Structure

Item

Description

Title

IMS Termination Completed

Name

IEF404I

Table

IMS

Message

Either of the following messages:

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

when the message is issued from job IMS* (* is the generic mask character).

DFS994I IMS SHUTDOWN COMPLETEDt

when the message contains string SHUTDOWN COMPLETED in columns 12–27.

Message Description

  • IEF404I – Job jjj ended
  • DFS994I – IMS has completed termination.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

When IMS termination is completed, the IOA environment is informed that IMS is down.

Rule Actions

  • Deletes condition or date CTO-imsname-UP STAT
    where imsname is the name of the IMS job or started task.
  • Adds condition or date CTO-imsname-DOWN STAT
    where imsname is the name of the IMS 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 IMS conditions (utility IOACND, Control-M Event Manager, and so on) is already implemented, the existing mechanism must be removed before implementing this rule.

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

  • The IOA environment already contains a prerequisite condition indicating that IMS is 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.

If required, change the IMS job or started task name mask in field JNAME of the rule’s ON block to conform to local naming conventions. The default-defined value is IMS*.

Table 98 IMS Severe Termination Rule Structure

Item

Description

Title

IMS Severe Termination

Name

$HASP310

Table

IMS

Message

$HASP310 jj TERMINATED AT END OF MEMORY

when the message contains string IMS in columns 10 – 12.

Message Description

Abend of job jjj was so severe that no Recovery Termination Manager (RTM) processing occurred.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

For severe IMS abends, the IOA environment is informed that IMS is no longer up and that IMS is down.

Rule Actions

  • Deletes condition or date CTO-imsname-UP STAT
    where imsname is the name of the IMS job or started task that abended.
  • Adds condition or date CTO-imsname-DOWN STAT
    where imsname is the name of the IMS job or started task that abended.

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 IMS conditions (utility IOACND, Control-M Event Manager, and so on) is already implemented, the existing mechanism must be removed before implementing this rule.

Change the names of the prerequisite conditions added or deleted by this rule to match your existing definitions if both of the following are true:

  • The IOA environment already contains prerequisite conditions indicating that IMS 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: This rule applies only at JES2 sites.

Table 99 Suppress S IMS if IMS Is Active Rule Structure

Item

Description

Title

Suppress S IMS if IMS Is Active

Name

S IMS

Table

IMS

Command

S IMS

Command Description

This command starts IMS (the rule suppresses the command).

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

IN !CTO-imsname-DOWN STAT

Global Variables

None.

Rule Logic

If command S IMS is issued when IMS is already up, the new started task is immediately shut down and normal termination messages are issued. These messages, however, give the appearance that IMS has gone down and therefore may incorrectly trigger rules.

This rule prevents this situation by suppressing the S IMS command if IMS is already up. In this way, issuance of the termination messages is prevented and rules are not incorrectly triggered.

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

Rule Actions

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

Activating the Rule

Once scheduled, the rule becomes active when prerequisite condition or date CTO-imsname-DOWN STAT is deleted (where imsname is the name of the IMS address space).

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 IMS 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 IMS in the site. To adapt each rule, the IMS name in the rule’s ON statement and IN condition must be changed.

Parent Topic

IMS Startup and Termination