Title

IPL – Reset SolveWare Prerequisite Conditions

Name

CTO147I

Table

INITSLV

Message

CTO147I CONTROL-O INITIALIZATION COMPLETE.
TYPE=type,SUB=subsystem,RUN#=nnnn

Message Description

This rule is triggered immediately following the startup of the Control-O monitor during IPL. It performs actions needed to initialize other SolveWare rules. This initialization process consists of adding or deleting prerequisite conditions for other rules that must be added or deleted at time of IPL.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

This rule is automatically triggered immediately following startup of Control-O during IPL, before any other SolveWare rules are scheduled.

This rule adds or deletes prerequisite conditions required by other rules. To determine which prerequisite conditions this rule must add or delete, refer to the description of each SolveWare rule in this guide.

Rule Actions

Adds or deletes prerequisite conditions required by other rules.

Activating the Rule

The rule is triggered immediately following the startup of the Control-O monitor during IPL.

Recommended Mode or Category

During the testing period, the rule is activated in LOG mode. Once you are satisfied with the results of the rule, change this 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

The rule adds or deletes conditions for all SolveWare rules included in this guide. Decide which SolveWare subjects (and rules) you intend to implement and then remove the conditions for those rules you do not intend to implement.

Start the Control-O monitor at the beginning of IPL. This is achieved by placing the following command as one of the first commands in member COMMNDnn in SYS1.PARMLIB:

COM='S CONTROLO,SUB=MSTR,OUTPUT=DUMMY,

ORDER=IPLRULES,TYPE=IPL'

Rule list member IPLRULES contains table INITSLV. Optionally, it can contain system startup rules (table STARTSYS) and started task monitoring rules.

For example, tables CICS and DB2.

Title

Define Site Configuration Global Variables

Name

JES2GLBL

Table

INITSLV2

Event

JES2GLBL

Event Description

This Event rule is triggered immediately following the startup of the Control-O monitor during IPL. It initializes site configuration Global variables that define the MVS multi-system configuration to Control-O. The Global variables defined by this rule are necessary for the implementation of other SolveWare rules at your site.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

• %%ID_sfmid

Character used by Control-M as a system identifier (set in AutoEdit System variable %%$SIGN) in a multi-system environment, where smfid is the SMF ID of the CPU.

For example:
%%ID_SYS1=A
%%ID_ESA1=B

• %%JES2_ROUTE_smf

Multi-access spool member, multi-access spool member node, or node member used to send a command over the network to the specified system. smf is the SMF ID of the CPU.

For example:

%%JES2_ROUTE_ESA1=$M2 %%JES2_ROUTE_ESA2=$N2M3

• %%CPU_SMFx

SMF ID of the CPU, indexed by a sequence number.

For example:

%%CPU_SMF0=SYS1
%%CPU_SMF1=SYS2

Rule Logic

This Event rule is executed at start of Control-O to initialize JES2 Global variables that define the MVS multi-system configuration to Control-O. These variables are used by other SolveWare rules.

Rule Actions

Initialize Global variables %%ID_smfid, %%JES2_ROUTE_smf and %%CPU_SMFx for each MVS system handled by 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 MVS system handled by Control-O, a set of Global variables must be defined in the rule as follows:

• %%ID_smfid
  Character used by Control-M as a system identifier (set in AutoEdit System variable %%$SIGN) in a multi-system environment).
• %%JES2_ROUTE_smf
  Multi-access spool member, multi-access spool member node, or node member used to send a command over the network to the specified system. smf is the SMF ID
  of the CPU.
  For example:
  %%JES2_ROUTE_ESA1=$M2 %%JES2_ROUTE_ESA2=$N2M3
• %%CPU_SMFx
  SMF ID of the CPU, indexed by a sequence number.