Rules Structure

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

Table 125 NetView Subsystem Initialization StartedRule Structure

Item	Description
Title	NetView Subsystem Initialization Started
Name	IEF403I
Table	NETVIEW
Message	IEF403I jjj STARTED { - TIME=hh.mm.ss} when the message is issued from job NETVSSI.
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 the NetView subsystem is started, the IOA environment is informed that the NetView subsystem is no longer down.
Rule Actions	Deletes condition or date CTO-netvssiname-DOWN STAT, where netvssiname is the name of the NetView subsystem 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 NetView conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. 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 the NetView subsystem 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 assumes that the name of the production NetView subsystem environment is NETVSSI. This name may need to be changed (in the rule’s ON statement) to match site conventions.

Table 126 NetView Subsystem Initialization CompletedRule Structure

Item	Description
Title	NetView Subsystem Initialization Completed
Name	CNM541I
Table	NETVIEW
Message	CNM541I NETVIEW SUBSYSTEM INITIALIZED SUCCESSFULLY
Message Description	The NetView subsystem has completed initialization and is up.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%STATUS_netvssiname Status (UP or DOWN) of the NetView subsystem, where netvssiname is the name of the NetView subsystem job or started task.
Rule Logic	Intercepts a message that indicates the NetView subsystem has completed initialization, and informs the IOA environment that the NetView subsystem is up.
Rule Actions	Adds condition or date CTO-netvssiname-UP STAT (where netvssiname is the name of the NetView subsystem job or started task). Sets Global variable %%STATUS_netvssiname to UP.
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 NetView conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. 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 the NetView subsystem 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. Table 127 NetView Subsystem Termination Started Rule Structure
Item	Description
Title	NetView Subsystem Termination Started
Name	CNM580I
Table	NETVIEW
Message	CNM580I NETVIEW SUBSYSTEM ADDRESS SPACE IS TERMINATING
Message Description	The NetView subsystem address space has received an MVS STOP command and is terminating.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%STATUS_netvssiname Status (UP or DOWN) of the NetView subsystem, where netvssiname is the name of the NetView subsystem job or started task.
Rule Logic	Intercepts the NetView subsystem termination message and informs the IOA environment that the NetView subsystem is no longer up.
Rule Actions	Deletes condition or date CTO-netvssiname-UP STAT (where netvssiname is the name of the NetView subsystem job or started task). Sets Global variable %%STATUS_netvssiname to DOWN.
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 to control NetView conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. 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 the NetView subsystem 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. Table 128 NetView Subsystem Termination Completed Rule Structure
Item	Description
Title	NetView Subsystem Termination Completed
Name	IEF404I
Table	NETVIEW
Message	Either of the following messages: IEF404I jjj ENDED { - TIME=hh.mm.ss} IEF450I jjj {ppp} sss - ABEND {Scde\|Ucde} REASON=xxxxxxxx TIME=hh.mm.ss when the message is issued from job NETVSSI.
Message Description	Job jjj ended or step sss of job jjj abended.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%STATUS_netvssiname Status (UP or DOWN) of the NetView subsystem, where netvssiname is the name of the NetView subsystem job or started task.
Rule Logic	When the NetView subsystem job or started task ends, the IOA environment is informed that the NetView subsystem is down.
Rule Actions	Adds condition or date CTO-netvssiname-DOWN STAT (where netvssiname is the name of the NetView subsystem job or started task). Deletes condition or date CTO-netvssiname-UP STAT (where netvssiname is the name of the NetView subsystem job or started task). Sets Global variable %%STATUS_netvssiname to DOWN.
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 NetView conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. 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 NetView 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 assumes that the name of the production NetView subsystem environment is NETVSSI. This name may need to be changed (in the rule’s ON statement) to match site conventions.

Table 129 NetView Initialization Started Rule Structure

Item	Description
Title	NetView Initialization Started
Name	IEF403I
Table	NETVIEW
Message	IEF403I jjj STARTED { - TIME=hh.mm.ss} when the message is issued from job NETVIEW.
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 NetView is started, the IOA environment is informed that NetView is no longer down.
Rule Actions	Deletes condition or date CTO-netviewname-DOWN STAT (where netviewname is the name of the NetView 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 NetView conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. 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 NetView 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 assumes that the name of the production NetView environment is NETVIEW. This name may need to be changed (in the rule’s ON statement) to match site conventions.

Table 130 NetView Initialization CompletedRule Structure

Item	Description
Title	NetView Initialization Completed
Name	DSI112I
Table	NETVIEW
Message	DSI112I NCCF READY FOR LOGONS AND SYSTEM OPERATOR COMMANDS
Message Description	NetView completed initialization and is up.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%STATUS_netviewname Status (UP or DOWN) of the NetView subsystem (where netviewname is the name of the NetView subsystem job or started task).
Rule Logic	Intercepts a message indicating that NetView is ready for action and informs the IOA environment that NetView is up.
Rule Actions	Adds condition or date CTO-netviewname-UP STAT (where netviewname is the name of the NetView job or started task). Sets Global variable %%STATUS_netviewname to UP.
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 NetView conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. If the IOA environment already contains a prerequisite condition indicating that NetView is up or down (for example, if such a condition is already referenced by a Control-M job scheduling definition), and if the prerequisite condition has a name that differs from the name indicated in this rule, then change the name of the prerequisite condition indicated in this rule to match your previous definition.

Table 131 NetView Termination Completed Rule Structure

Item	Description
Title	NetView Termination Completed
Name	IEF404I
Table	NETVIEW
Message	Either of the following messages: IEF404I jjj ENDED { - TIME=hh.mm.ss} IEF450I jjj {ppp} sss - ABEND {Scde\|Ucde} REASON=xxxxxxxx TIME=hh.mm.ss when the message is issued from job NETVIEW.
Message Description	Job jjj ended or step sss of job jjj abended.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%STATUS_netviewname Status of the NetView job or started task, where netviewname is the name of the NetView job or started task. %%STATUS_NPDA Status of the NPDA. %%STATUS_NLDM Status of the NLDM. %%NCCF_REPLY_netviewname NCCF reply number, where netviewname is the name of the NetView job or started task.
Rule Logic	When NetView started task ends, the IOA environment is informed that NetView and its components are down.
Rule Actions	Adds condition or date CTO-netviewname-DOWN STAT, where netviewname is the name of the NetView job or started task. Deletes condition or date CTO-netviewname-UP STAT. Sets Global variable %%STATUS_netviewname to DOWN. Sets Global variable %%STATUS_NPDA to DOWN. Sets Global variable %%STATUS_NLDM to DOWN. Sets Global variable %%NCCF_REPLY_netviewname to %%UNDEF.
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 NetView conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. 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 NetView 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 assumes that the name of the production NetView environment is NETVIEW. This name may need to be changed (in the rule’s ON statement) to match site conventions.

Table 132 Suppress S NETVIEW if the NetView Subsystem is Active Rule Structure

Item	Description
Title	Suppress S NETVSSI if the NetView Subsystem Is Active
Name	S NETVSSI
Table	NETVIEW
Command	S NETVSSI
Command Description	This command starts the NetView subsystem (and the rule suppresses the command).
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	IN !CTO-netvssiname-DOWN STAT where netvssiname is the name of the NetView subsystem job or started task.
Global Variables	None.
Rule Logic	If command S NETVSSI is issued when the NetView subsystem is already up, the new started task is immediately shut down and normal termination messages are issued. These messages, however, give the appearance that the active NetView has gone down and this may incorrectly trigger other rules in this solution and cause erroneous updating of prerequisite conditions. This rule prevents the situation described above by suppressing the S NETVSSI command if the NetView subsystem 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 NetView subsystem environment in the site.
Rule Actions	Suppresses the command. Sends a message to user U-SHFTOPER indicating that command S NETVSSI was suppressed.
Activating the Rule	Once scheduled, the rule becomes active when prerequisite condition or date CTO-netvssiname-DOWN STAT is deleted.
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.

Table 133 Suppress S NETVIEW if NetView is Active Rule Structure

Item	Description
Title	Suppress S NETVIEW if NetView is Active
Name	S NETVIEW
Table	NETVIEW
Command	S NETVIEW
Command Description	This command starts NetView (and the rule suppresses the command).
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	IN !CTO-netviewname-DOWN STAT Where netviewname is the name of the NetView job or started task.
Global Variables	None.
Rule Logic	If command S NETVIEW is issued when NetView is already up, the new started task waits until the currently running task goes down and then starts automatically. This may affect other rules in this solution and cause erroneous updating of prerequisite conditions. This rule prevents the situation described above by suppressing the S NETVIEW command if the NetView subsystem is already up. In this way, the task does not start without a message being sent and rules are not incorrectly triggered. This rule serves as a sample rule. A similar rule must be created for each NetView subsystem environment in the site.
Rule Actions	Suppresses the command. Sends a message to user U-SHFTOPER indicating that command S NETVIEW was suppressed.
Activating the Rule	Once scheduled, the rule becomes active when prerequisite condition or date CTO-netviewname-DOWN STAT is deleted.
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 NetView 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 assumes that the name of the production NetView environment is NETVIEW. This name may need to be changed (in the rule’s ON statement and IN condition) to match site conventions. The rule must be duplicated for each NetView subsystem in the site. To adapt each rule, the NetView subsystem name in the rule’s ON statement and IN condition must be changed.

Table 134 Start NETVIEW and NETVSSIRule Structure

Item	Description
Title	Start NETVIEW and NETVSSI
Name	STRTNET
Table	NETVIEW
Command	STRTNET
Command Description	A user-defined command to start the NetView started tasks (NETVSSI and NETVIEW).
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%NETVSSI – Name of the NetView subsystem started task. %%NETVIEW = NETVIEW – Name of the NetView started task.
Rule Logic	Sets Global variables to fix the names of the NetView and NetView subsystem started tasks. Then issues START commands for the two started tasks whose names were specified above.
Rule Actions	Sets Global variable %%NETVSSI to NETVSSI. Sets Global variable %%NETVIEW to NETVIEW. Issues command S %%NETVSSI to start the NetView subsystem started task. Issues command S %%NETVIEW to start the NetView 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	The rule sets the names of the NetView environments to NETVIEW and NETVSSI. These names may need to be changed (in the rule’s DO SET statements) to match site conventions. The rule must be duplicated for each NetView. NetView started task name and NetView subsystem name in the rule’s DO SET statements must be changed, as well as the names of the global variables different name must be given to each rule.

Table 135 Stop NETVIEW and NETVSSI Rule Structure

Item	Description
Title	Stop NETVIEW and NETVSSI
Name	STOPNET
Table	NETVIEW
Command	STOPNET
Command Description	A user-defined command to stop the NetView started tasks (NETVSSI and NETVIEW).
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%NETVSSI Name of the NetView subsystem started task. %%NETVIEW Name of the NetView started task. %%NCCF_REPLY Reply ID for issuing a command to NetView. %%STATUS_NETVIEW Status of NetView (UP or DOWN). %%STATUS_NETVSSI Status of the NetView subsystem (UP or DOWN).
Rule Logic	Checks the status of the NetView started tasks. If they are UP, terminates them. If they are DOWN, issues a message to notify that NetView is not up.
Rule Actions	Checks the status of NetView. If it is active, issues a CLOSE IMMED command to it. Checks the status of the NetView subsystem. If it is active, issues an MVS STOP command to terminate it. If none of the NetView started tasks was active, issues a message to INCONTROL user U-SHFTOPER to notify that NetView is not up.
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	The rule must be duplicated for each NetView environment in the site. To adapt each rule, the names of the variables that contain the NetView started task and NetView subsystem names in the rule’s DO statements must be changed. A different name must be given to each rule.

Parent Topic

NetView Startup and Termination