Title

Set the Follow-me Quantitative Resource

Name

DB2UP

Table

DB2

Event

DB2UP

Event Description

This event rule sets the quantity of resource CTO-DB2-CPU-id (used by follow-me jobs) to 9999.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations

Global Variables

%%CPUSEQ_smfid
For each computer's SMF ID, a one-character identifier of the corresponding system.

For example:

%%CPUSEQ_SYS1 = 1

%%CPUSEQ_SYS2 = 2

Rule Logic

This rule is triggered when DB2 starts operating. The one-character identifier of the CPU is obtained from the SMF ID and the quantity of resource CTO-DB2-CPU-id for the current CPU is set to 9999.

Rule Actions

Sets Quantitative resource CTO-DB2-CPU-id to 9999.

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

For each CPU on which Control-O is active, define a Global variable in the Global Variable list. Each variable must be defined in the format %%CPUSEQ_smfid=c, where smfid is the SMF ID of the CPU and c is a unique, 1-character identifier of the CPU.

These variables can be defined manually by adding the variables to the Control-O $GLOBAL member and issuing operator command F CONTROLO, LOADGLOBAL, or they can be defined by adding corresponding DO SET statements to a rule in the INITSLV rule table (see STARTSYS).

Control-M job scheduling definitions and JCLs for follow-me jobs must be modified to enable Control-M to dynamically determine the job target computer. SOLVSCHD and SOLVJCL libraries contain, respectively, a sample job scheduling definition and a sample JCL that serve as examples for defining such jobs. These samples can be adapted to site conventions and requirements.

Title

Reset the Follow-me Quantitative Resource

Name

DB2DOWN

Table

DB2

Event

DB2DOWN

Event Description

This event rule resets the quantity of resource CTO-DB2-CPU-id (used by follow-me jobs) to 0000.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations

Global Variables

%%CPUSEQ_smfid
For each computer's SMF ID, a one-character identifier of the corresponding system.

For example:

%%CPUSEQ_SYS1 = 1

%%CPUSEQ_SYS2 = 2

Rule Logic

This rule is triggered when DB2 stops operating. The one-character identifier of the CPU is obtained from the SMF ID and the quantity of resource CTO-DB2-CPU-id for the current CPU is reset to 0000.

Rule Actions

Reset Quantitative resource CTO-DB2-CPU-id to 0000.

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

For each CPU on which Control-O is active, define a Global variable in the Global Variable list. Each variable must be defined in the format %%CPUSEQ_smfid=c, where smfid is the SMF ID of the CPU and c is a unique, 1-character identifier of the CPU.

These variables can be defined by manually by adding the variables to the Control-O $GLOBAL member and issuing operator command F CONTROLO,LOADGLOBAL, or by adding corresponding DO SET statements to a rule in the INITSLV rule table (see STARTSYS).

Control-M job scheduling definitions and JCLs for follow-me jobs must be modified to enable Control-M to dynamically determine the job target computer. SOLVSCHD and SOLVJCL libraries contain, respectively, a sample job scheduling definition and a sample JCL that serve as examples for defining such jobs. These samples can be adapted to site conventions and requirements.