Rules Structure

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

Table 76 CICS Initialization Started Rule Structure

Item	Description
Title	CICS Initialization Started
Name	IEF403I
Table	CICS
Message	IEF403I jjj STARTED {- TIME=hh.mm.ss} when the message is issued from job CICS*.
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 CICS is started, the IOA environment is informed that CICS is no longer down.
Rule Actions	Deletes condition or date CTO-cicsname-DOWN 0101 (where cicsname is the name of the CICS 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 CICS conditions (utility IOACND, Control-M Event Manager, and so on.) is already implemented, the 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 CICS 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. Table 77 CICS Initialization Completed Rule Structure
Item	Description
Title	CICS Initialization Completed
Name	*DFH1517**
Table	CICS
Message	DFHSI1517 aplid CONTROL IS BEING GIVEN TO CICS
Message Description	CICS 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 CICS is completely up, the IOA environment is informed that CICS is up.
Rule Actions	Adds condition or date CTO-cicsname-UP STAT (where cicsname is the name of the CICS 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 CICS conditions (utility IOACND, Control-M Event Manager, and so on.) is already implemented, the 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 CICS 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 78 CICIS Termination Started Rule Structure
Item	Description
Title	CICIS Termination Started
Name	*DFH1071**
Table	CICS
Message	One of the following messages: DFH1701 C.I.C.S IS BEING TERMINATED BY OPERATOR opid AT TERMINAL termid DFHTM1701 {C.I.C.S. \| CICS/ESA} IS BEING TERMINATED BY OPERATOR opid AT TERMINAL termid DFHTM1703 applid PRODUCT IS BEING TERMINATED BY USERID userid IN TRANSACTION tranid {AT NETNAME \| AT TERMINAL} terminal. DFHTM1715 applid PRODUCT IS BEING QUIESCED BY USERID userid in TRANSACTION tranid {AT NETNAME \| AT TERMINAL} terminal IEF404I jjj-ENDED(- TIME=hh.mm.ss) when the message is issued from job CICS*
Message Description	DFHTM1701, DFH1701, DFHTM1703, and DFHTM1715 – Operator opid issued a CICS shutdown request from terminal termid. IEF404I – Job jjj ended.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	When CICS termination has started, the IOA environment is informed that CICS is no longer up.
Rule Actions	Deletes condition or date CTO-cicsname-UP STAT, where cicsname is the name of the CICS 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 CICS conditions (utility IOACND, Control-M Event Manager, and so on.) is already implemented, the mechanism must be removed before implementing this rule. If the IOA environment already contains a prerequisite condition indicating that CICS is up (for example, if such a condition is already referenced by a Control-M job scheduling definition), and if the prerequisite condition has a different name than the prerequisite condition indicated in this rule, then change the name of the prerequisite condition deleted by this rule to match your previous definition.

Table 79 CICS Termination Completed Rule Structure

Item	Description
Title	CICS Termination Completed
Name	*DFH1799**
Table	CICS
Message	One of the following messages: DFH1799/DFHKE1799 aplid TERMINATION OF CICESA IS COMPLETE IEF404I jjj ENDED{ - TIME=hh.mm.ss} when the message is issued from job CICS*.
Message Description	DFH1799/DFHKE1799 – CICS has completed termination. IEF404I – Job jjj ended.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	When CICS termination is completed, the IOA environment is informed that CICS is down.
Rule Actions	Adds condition or date CTO-cicsname-DOWN STAT (where cicsname is the name of the CICS 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 CICS conditions (utility IOACND, Control-M Event Manager, and so on.) is already implemented, the 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 CICS 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. Table 80 CICS Severe Termination Rule Structure
Item	Description
Title	CICS Severe Termination
Name	$HASP310
Table	CICS
Message	$HASP310 jjj TERMINATED AT END OF MEMORY
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 CICS abends, the IOA environment is informed that CICS is no longer up and that CICS is down.
Rule Actions	Adds condition or date CTO-cicsname-DOWN STAT (where cicsname is the name of the CICS job or started task that abended). Deletes condition or date CTO-cicsname-UP STAT (where cicsname is the name of the CICS 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 CICS conditions (utility IOACND, Control-M Event Manager, and so on.) is already implemented, the mechanism must be removed before implementing this rule. Change the names of the prerequisite conditions added or deleted by this rule to match your previous definitions, if both of the following are true: The IOA environment already contains prerequisite conditions indicating that CICS 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 81 Suppress S CICS if CICS Is Active Rule Structure

Item	Description
Title	Suppress S CICS if CICS Is Active
Name	S CICS
Table	CICS
Command	S CICS
Command Description	This command starts CICS (the rule suppresses the command).
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	IN !CTO-cicsname-DOWN STAT
Global Variables	None.
Rule Logic	If command S CICS is issued when CICS is already up, the new started task is immediately shut down and normal termination messages are issued. These messages, however, give the appearance that CICS has gone down and therefore may incorrectly trigger rules. This rule prevents this situation by suppressing the S CICS command if CICS 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 CICS environment in the site.
Rule Actions	Suppresses the command. Sends a message to user U-SHFTOPER indicating that command S CICS was suppressed.
Activating the Rule	Once scheduled, the rule becomes active when prerequisite condition or date CTO-cicsname-DOWN STAT is deleted (where cicsname is the name of the CICS 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 CICS 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 CICS in the site. To adapt each rule, the CICS name in the rule’s ON statement and IN condition must be changed. Table 82 Startup Continuation Permission Rule Structure
Item	Description
Title	Startup Continuation Permission
Name	DFH1588
Table	CICS
Message	One of the following messages: DFH1588/DFHSI1588D IS STARTUP TO BE CONTINUED? REPLY GO OR CANCEL
Message Description	CICS is requesting permission to proceed after an error has occurred during initialization, or after an emergency restart has completed.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	The rule is triggered after an error has occurred during CICS initialization, or after an emergency restart has completed. CICS issues message DFH1588 and waits for the operator to reply whether startup is to be continued or cancelled. The rule replies to the message with GO, causing the startup operation to continue.
Rule Actions	Replies to the message with GO.
Activating the Rule	Once scheduled, the rule remains active until deleted from Control-O.
Recommended Mode or Category	During the testing period, the rule must be activated 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	Automatic reply to the message may be desirable only for certain CICS environments. For example, test environment only. If so, change the JNAME field in the ON statement of the rule definition to intercept messages only from the CICS address spaces of those environments.

Parent Topic

CICS Startup and Termination