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 on page 43).
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 below).
Rule Actions	Issues the following command S CICS. 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).

Parent Topic

System Startup