STARTSYS

SolveWare subject STARTSYS automates the initialization of SolveWare rules that handle the startup of various system components after IPL.

Solutions Provided

SolveWare subject STARTSYS contains the following solutions:

SolveWare initialization – This solution contains rules that initialize prerequisite conditions and Global variables required by other SolveWare rules at time of IPL.
System startup – This solution contains sample rules for automated system startup.

SolveWare Initialization

This solution automates SolveWare rule initialization by adding or deleting those prerequisite conditions that must be added or deleted at time of IPL and by setting certain Global variables to values required by SolveWare rules.

The SolveWare Initialization solution is implemented as a prerequisite to the implementation of all other SolveWare solutions. For special administrative considerations regarding SolveWare initialization, see the customization instructions for rule CTO147I, in Table 5 IPL – Reset Prerequisite Conditions Rule Structure in Rules Structure.

Rules

The SolveWare Initialization solution includes the following rules:

IPL – Reset SolveWare Prerequisite Conditions
Define Site Configuration Global Variables

Rules Structure

The following tables describe the structures of the SolveWare Initialization solution rules.

Table 5 IPL – Reset Prerequisite Conditions Rule Structure

Item	Description
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.

Table 6 Define Site Configuration Global Variables Rule Structure

Item	Description
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. %JES2_ROUTE_ESA1=$M2%%JES2_ROUTE_ESA2=$N2M3 %%CPU_SMFx SMF ID of the CPU, indexed by a sequence number. %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. %%JES2_ROUTE_ESA1=$M2%%JES2_ROUTE_ESA2=$N2M3 %%CPU_SMFx %%CPU_SMFx SMF ID of the CPU, indexed by a sequence number.

System Startup

This solution contains sample rules for automated system startup using Control-O. The startup process is initiated automatically after IPL. A statement in member COMMNDnn in the SYS1.PARMLIB library starts the IPL CONTROL-O. STARTSYS rules start the various system components in the required sequence (for example, start TSO and CICS only after VTAM node initialization is completed) and reply to the appropriate JES2 startup messages.

Solution "System Startup" does not contain a rule to start JES2 because it assumes that JES2 is started automatically after IPL. If desired, you can define a rule to start JES2, but first, prevent automatic startup of JES2 outside of Control-O.

Initialize (delete) all prerequisite conditions defined in this solution before the rules of this solution are ordered. For special considerations regarding prerequisite condition initialization, see SolveWare Initialization.

Deactivate any existing startup mechanisms that parallel the rules in this solution.

This solution handles startup of JES2 environments. However, the solution can be easily adapted to handle startup in a JES3 environment.

Rules

The System Startup solution includes the following rules:

JES2–Specify Options
Start VTAM
TSO VTAM Node Is Active
CICS VTAM Node Is Active
Start New Control-O Under JES2
Start Control-M
Start Control-D Monitor and Subsystem
Order Non-IPL Rules

Rules Structure

The following tables describe the structures of the System Startup solution rules.

Table 7 JES2–Specify Options Rule Structure

Item	Description
Title	JES2–Specify Options
Name	$HASP426
Table	STARTSYS
Message	$HASP426 SPECIFY OPTIONS - subsystem
Message Description	JES2 requests that the operator specify initialization options.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule notifies the operator that after a predefined delay, Control-O automatically replies NOREQ to the message. The operator can override the anticipated NOREQ option by replying to the message during the delay period.
Rule Actions	Notifies the operator that reply NOREQ is issued after a delay. After the delay, issues the following command: R %%REPLY,NOREQ
Activating the Rule	Once ordered, the rule remains active until deleted from Control-O.
Recommended Mode or Category	Activate the rule in LOG mode during the testing period. 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 3—the rule is provided as an example. Implementation of this rule requires some customization.
Customization	STARTSYS rules are provided as guidelines for automated system startup. Examine and adapt each rule to site requirements. The rule is defined with a 20-second delay period. This delay period (defined in parameter WAIT of statement DO COMMAND) can be adapted to site requirements. The reply string, originally defined as NOREQ, can be adapted to site standards.

Table 8 Start VTAM Rule Structure

Item	Description
Title	Start VTAM
Name	SVTAM
Table	STARTSYS
Event	SVTAM
Event Description	This Event rule starts VTAM.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	This rule issues a START command to start VTAM. VTAM remains in status STARTING until JES is up, at which point VTAM starts executing.
Rule Actions	Issues the following command S VTAM
Activating the Rule	The rule is activated immediately, once it has been ordered.
Recommended Mode or Category	Activate the rule in LOG mode during the testing period. 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 3—the rule is provided as an example. Implementation of this rule requires some customization.
Customization	STARTSYS rules are provided as guidelines for automated system startup. Examine and adapt each rule to site requirements. Change the VTAM procedure name specified in the rule (VTAM) to the actual name of the VTAM procedure at the site.

Table 9 TSO VTAM Node Is Active Rule Structure

Item	Description
Title	TSO VTAM Node Is Active
Name	IST093I
Table	STARTSYS
Message	IST093I nodename ACTIVE where nodename is TSOM.
Message Description	The VTAM node specified in the message was successfully activated.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	Once the TSO VTAM node is successfully activated, TSO can be started. The rule immediately issues command S TSO to start TSO. Prerequisite condition or date CTO-STRT-TSO-ISSUED 0101 is added. This condition is defined as an IN condition for rule ORDERALL (see Table 14 Order Non-IPL Rules Rule Structure).
Rule Actions	Issues the following command: S TSO Adds prerequisite condition or date CTO-STRT-TSO-ISSUED STAT
Activating the Rule	Once ordered, the rule remains active until deleted from Control-O.
Recommended Mode or Category	Activate the rule in LOG mode during the testing period. 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 3—the rule is provided as an example. Implementation of this rule requires some customization.
Customization	STARTSYS rules are provided as guidelines for automated system startup. Examine and adapt each rule to site requirements. Adapt the TSO VTAM node name specified in the rule (TSOM) to actual site VTAM definitions.

Table 10 CICS VTAM Node Is Active Rule Structure

Item	Description
Title	CICS VTAM Node Is Active
Name	IST093I
Table	STARTSYS
Message	IST093I nodename ACTIVE where nodename is CICS.
Message Description	The VTAM node specified in the message was successfully activated.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	Once the CICS VTAM node is successfully activated, CICS can be started. The rule immediately issues command S CICS to start CICS. Prerequisite condition or date CTO-STRT-CICS-ISSUED 0101 is added. This condition is defined as an IN condition for rule ORDERALL (see Table 14 Order Non-IPL Rules Rule Structure below).
Rule Actions	Issues the following command S CIS Adds prerequisite condition or date CTO-STRT-CICS-ISSUED STAT
Activating the Rule	Once ordered, the rule remains active until deleted from Control-O.
Recommended Mode or Category	Activate the rule in LOG mode during the testing period. 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 3—the rule is provided as an example. Implementation of this rule requires some customization.
Customization	STARTSYS rules are provided as guidelines for automated system startup. Examine and adapt each rule to site requirements. Adapt the CICS VTAM node name specified in the rule (CICS) to actual site VTAM definitions.

Table 11 Start New Control-O Under JES2 Rule Structure

Item	Description
Title	Start New Control-O Under JES2
Name	SCTO
Table	STARTSYS
Event	SCTO
Event Description	This Event rule starts Control-O under JES2.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule issues a START command to start a new Control-O monitor. The new Control-O monitor remains in status STARTING until JES is up, at which point it starts executing and replaces the active Control-O monitor. Control-O is started under JES to enable it to write to SYSOUT files.
Rule Actions	Issues the following command S %%CONTROLO.
Activating the Rule	The rule is activated immediately, once it has been ordered.
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 3—the rule is provided as an example. Implementation of this rule requires some customization.
Customization	STARTSYS rules are provided as guidelines for automated system startup. Examine and adapt each rule to site requirements.

Table 12 Start Control-M Rule Structure

Item	Description
Title	Start Control-M
Name	SCTM
Table	STARTSYS
Event	SCTM
Event Description	This Event rule starts Control-M under JES2.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule issues a START command to start Control-M. Control-M remains in status STARTING until JES is up, at which point Control-M starts executing.
Rule Actions	Issues the following command: S CONTROLM
Activating the Rule	The rule is activated immediately, once it has been ordered.
Recommended Mode or Category	Activate the rule in LOG mode during the testing period. 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 3—the rule is provided as an example. Implementation of this rule requires some customization.
Customization	STARTSYS rules are provided as guidelines for automated system startup. Examine and adapt each rule to site requirements. Change the Control-M procedure name specified in the rule (CONTROLM) to the actual name of the Control-M procedure at the site.

Table 13 Start Control-D Monitor and Subsystem Rule Structure

Item	Description
Title	Start Control-D Monitor and Subsystem
Name	SCTD
Table	STARTSYS
Event	SCTD
Event Description	This event rule starts Control-D under JES2.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule issues a START command to start the Control-D monitor and subsystem. Control-D remains in status STARTING until JES is up, at which point Control-D starts executing.
Rule Actions	Issues the following commands: S CONTROLD S IOAINIT, OPTIONS=D
Activating the Rule	The rule is activated immediately, once it has been ordered.
Recommended Mode or Category	Activate the rule in LOG mode during the testing period. 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 3—the rule is provided as an example. Implementation of this rule requires some customization.
Customization	STARTSYS rules are provided as guidelines for automated system startup. Examine and adapt each rule to site requirements. Change the Control-D procedure name specified in the rule (CONTROLD) to the actual name of the Control-D procedure at the site.

Table 14 Order Non-IPL Rules Rule Structure

Item	Description
Title	Order Non-IPL Rules
Name	ORDERALL
Table	STARTSYS
Event	ORDERALL
Event Description	This Event rule orders non-IPL rules.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	IN CTO-STRT-TSO-ISSUED STAT IN CTO-STRT-CICS-ISSUED STAT
Global Variables	None.
Rule Logic	This rule is triggered after Control-O has started TSO and CICS. TSO and CICS startup are the last actions performed by IPL rules, at which point IPL rules can be replaced with the New Day (non-IPL) rules. This rule issues a command to rebuild Control-O rules.
Rule Actions	Issues the following command F %%CONTROLO,O=ALL,REBUILD
Activating the Rule	Once ordered, the rule remains active until deleted from Control-O.
Recommended Mode or Category	Activate the rule in LOG mode during the testing period. 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 3—the rule is provided as an example. Implementation of this rule requires some customization.
Customization	STARTSYS rules are provided as guidelines for automated system startup. Examine and adapt each rule to site requirements. Prerequisite conditions referenced by this rule must be deleted at time of IPL (see SolveWare Initialization).