NETVIEW OPEN ACCESS

NETVIEW solutions are designed to automate several management aspects of NetView and to provide a bidirectional interface between Control-O. The interaction and exchange between NetView and Control-O enhances the power of both and saves the high costs of implementing console automation using NetView alone.

Some messages (DO SHOUT actions) in the NETVIEW rules are sent to an INCONTROL user (U-SHFTOPER). A user with that name must be defined in the IOA Dynamic Destination table (CTMDEST). For details, see considerations chapter of the INCONTROL for z/OS Installation Guide.

Some rule definitions make use of the inverse IN condition feature. This feature activates rules only if the specified IN conditions are not set. For more information about using inverse IN conditions, see Inverse IN Conditions.

Solutions Provided

SolveWare subject NETVIEW contains the following solutions:

NetView Startup and Termination
Provides an easy procedure of starting and stopping the NetView started tasks. Monitors the NetView startup and termination processes, intercepts related messages and updates the appropriate IOA prerequisite conditions and global variables.
Direct Access to NetView
Provides a set of basic intercommunication facilities between Control-O and NetView, which include exchange of variables and information, triggering of automation processes in both products and alert management.

NetView Startup and Termination

This solution handles NetView startup and termination and provides simple procedures for starting and stopping NetView. At sites operating both Control-O and NetView, the status of NetView (up or down) impacts automation tasks and capabilities. Therefore, the site must maintain two prerequisite conditions for each task started by NetView, which indicate NetView status:

CTO-netview-UP 0101 and CTO-netview-DOWN STAT
CTO-netvssi-UP 0101 and CTO-netvssi-DOWN STAT

These conditions are updated by Control-O according to the NetView started task initialization and termination messages and can be used as prerequisite conditions for Control-O rules that use or control NetView resources.

This solution also maintains a set of global variables that indicate the availability of different NetView resources:

Copy

%%STATUS_netview
%%STATUS_netvssi
%%STATUS_NPDA
%%STATUS_NLDM

While startup or termination is in process—but not yet completed—the IOA environment considers NetView or the NetView subsystem as both "not up" and "not down." Therefore, NetView not being up is not necessarily the same as NetView being down, and vice versa.

Rules

The NetView Startup and Termination solution includes the following rules:

NetView Subsystem Initialization Started
NetView Subsystem Initialization Completed
NetView Subsystem Termination Started
NetView Subsystem Termination Completed
NetView Initialization Started
NetView Initialization Completed
NetView Termination Completed
Suppress S NETVSSI if NetView Subsystem is Active
Suppress S NETVIEW if NetView Is Active
Start NETVIEW and NETVSSI
Stop NETVIEW and NETVSSI

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.

Direct Access to NetView

This solution handles intercommunication between Control-O and NetView. At sites operating both NetView and Control-O, integration between those two products is very important. It allows the automation procedures implemented with Control-O to use any information available to NetView, without losing any automation benefits already acquired using NetView alone.

This solution provides rules and KOA scripts that enable transferring of Global variables and messages between NetView and Control-O, issuing NetView commands from the IOA environment and handling of NPDA alerts.

Rules

The Direct Access to NetView solution includes the following rules:

Save Reply ID of NCCF
Send a Command to NCCF
Set a Global Variable in NetView
Get the Value of a Global Variable From NetView
Set a Global Variable in Control-O
Record NPDA Alerts to the IOA Log
Send Alert to NPDA

Rules Structure

The following tables describe the structures of the Direct Access to NetView solution rules, as well as the following KOA scripts:

Manage a Preset NetView Environment
Log On to NetView
Get Value of NetView Variable
Set Value of NetView Variable
Enter NCCF Command and Get Response
Enter a GENALERT Command to NetView
Calculate Line Length in a NetView Screen
Perform NetView GETSCREEN Commands

Table 136 Save Reply ID of NCCFRule Structure

Item	Description
Title	Save Reply ID of NCCF
Name	DSI802I
Table	NETVIEW
Message	Either of the following messages: DSI802I domainid REPLY WITH VALID NCCF SYSTEM OPERATOR COMMAND DSI803I domainid REPLY INVALID. REPLY WITH VALID NCCF TERMINAL OPERATOR COMMAND
Message Description	A constant operator reply that prompts for a NetView command.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%NCCF_REPLY_netviewname NCCF reply number, where netviewname is the name of the NetView job or started task.
Rule Logic	When one of the above messages appears on the console, the message reply number is updated in a Control-O Global variable. This variable is later accessed by another Control-O rule that issues reply commands to NetView.
Rule Actions	Assigns the message reply number (system variable %%REPLY) to Global variable %%NCCF_REPLY_netviewname.
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 1—little or no customization is required.

Table 137 Send a Command to NCCF Rule Structure

Item	Description

Title	Send a Command to NCCF
Name	NCCFCMD
Table	NETVIEW
Command	NCCFCMD
Command Description	A user-defined command to issue a NetView command through the NetView open reply message (WTOR).
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%NCCF_REPLY_netviewname NCCF reply number, where netviewname is the name of the NetView job or started task.
Rule Logic	This command uses the NetView reply number, which is stored in a Global variable, to issue a NetView command. It waits for a reply from NetView and notifies the operator in case of an invalid command. The command is especially useful when a NetView command is to be issued from a source other than the console itself. For example, batch jobs, started tasks or CLISTs can use this command to issue NetView commands without having to determine the currently open NetView reply number.
Rule Actions	Using the NetView reply number (Global variable %%NCCF_REPLY_netviewname), issues the appropriate reply command. Waits for NetView’s reply and, if it announces an invalid command, notifies user U-SHFTOPER.
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 1—little or no customization is required.

Table 138 Set a Global Variable in NetView Rule Structure

Item	Description
Title	Set a Global Variable in NetView
Name	SETNTVAR
Table	NETVIEW
Command	SETNTVAR variable-name variable-value
Command Description	A user-defined command to set a Global variable in NetView.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	This command invokes KOA script SETNVAR that sets a NetView Global variable. The command is very useful for integrating procedures of NetView and of Control-O.
Rule Actions	Invokes KOA SETNVAR with the same parameters as the command. Issues messages to INCONTROL user U-SHFTOPER according to the KOA’s return code.
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 1—little or no customization is required.

Table 139 Get the Value of a Global Variable From NetView Rule Structure

Item	Description
Title	Get the Value of a Global Variable From NetView
Name	GETNTVAR
Table	NETVIEW
Command	GETNTVAR netview-variable Control-O-variable
Command Description	A user-defined command to get the value of a Global variable from NetView.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	The Global variable name is specified as the third word of the command.
Rule Logic	This command invokes KOA script GETNVAR that extracts the value of a NetView Global variable and assigns it to a Global variable in Control-O. The command is very useful for integrating procedures between NetView and Control-O.
Rule Actions	Parses command text to extract required data. Performs KOA script GETNVAR that uses the same variables as the command. Issues messages to INCONTROL user U-SHFTOPER according to the KOA’s return code.
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 1—little or no customization is required.

Table 140 Set a Global Variable in Control-O Rule Structure

Item	Description
Title	Set a Global Variable in Control-O
Name	SETGLVAR
Table	NETVIEW
Command	SETGLVAR variable-name variable-value
Command Description	A user-defined command to set a Global variable in Control-O.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	The Global variable name is passed as the second word of the command.
Rule Logic	This command sets a Global variable whose name is given by the first parameter and assigns the second parameter as its value. The command is very useful for integrating NetView with Control-O. It enables NetView CLISTs or NetView exits to set Global variables in Control-O using a simple operator command.
Rule Actions	Assigns the value of the second command parameter to a Global variable named by the first command parameter.
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 1—little or no customization is required.

Table 141 Record NPDA Alerts to the IOA Log Rule Structure

Item	Description
Title	Record NPDA Alerts to the IOA Log
Name	BNJ030I
Table	NETVIEW
Message	BNJ030I operatorid time type ALERT RECEIVED FROM THE FOLLOWING RESOURCE: resource
Message Description	An alert was generated in NetView.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	As soon as an alert is generated in NetView, a message is issued to the console. This message triggers this rule that sends it to IOA.
Rule Actions	Sends a message to user U-NETVALRT with the text of the alert.
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 1—little or no customization is required.
Customization	CLIST CTONVINI (supplied in the SOLVKOA library) issues a series of NPDA Set Recording Filter (SRFILTER) commands to enable alert generation and to allow Control-O to receive NetView alert information. The CLIST must be adapted to site conventions and copied to one of the libraries specified in DD statement DSICLD of the NetView procedure. The NetView startup CLIST used at the site must be modified to issue command CTONVINI that sets the NPDA SRF filters.

Table 142 Send Alert to NPDA Rule Structure

Item	Description
Title	Send Alert to NPDA
Name	IEF450I
Table	NETVIEW
Message	IEF450I jjj {ppp} sss - ABEND {Scde\|Ucde} REASON=xxxxxxxx TIME=hh.mm.ss
Message Description	Step sss of job jjj abended.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	%%NETVIEW_ALERT_JOB_jobname where jobname is the name of the abending job. Such a variable must be defined for each job that must be monitored by this rule.
Rule Logic	When a job abend message is intercepted, the rule checks if the job name appears in a predefined list of jobs. If the job’s name appears on the list, an alert is sent to NetView about the abend.
Rule Actions	Checks if there exists a Global variable called %%NETVIEW_ALERT_JOB_jobname. If such a variable exists, KOA script GENALRT is invoked to generate an alert in NetView.
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 looks for a Global variable called %%NETVIEW_ALERT_JOB_jobname. To maintain a list of jobs that require generating an alert in NetView when they abend, the appropriate Global variables must be set by a rule that is activated during system or NetView startup. For additional information, see the Customization item in Table 148 Enter a GENALERT Command to NetView Script Structure.

Table 143 Manage a Preset NetView Environment Script Structure

Item	Description
Title	Manage a Preset NetView Environment
Name	NETVUE
KOA Script Description	This script manages the preset NetView environment that is used by the other KOA scripts and Control-O rules in this solution.
Activating the KOA Script	Script NETVUE is activated automatically by a Control-O server in response to requests for the preset NetView environment.
Parameters	Functions: INIT, TERM, RESET.
Global Variables	None.
KOA Script Logic	When the function is INIT, the KOA logs on to NETVIEW, types the userid and password and receives the main entry panel. The NetView screens are received by KOA script SCRNWAIT, which handles the special way in which NetView sends its screens (each part of the screen is sent separately). When the function is RESET, the KOA returns to the main NetView entry panel. When the function is TERM, the KOA logs off from NetView.
Recommended Category	The SolveWare category for this KOA script is 3—the script is provided as an example. Some customization is needed if the script is to be implemented.
Customization	The user ID, password and NetView VTAM application ID entered by this script must be modified according to site requirements. An alternative is to keep the user ID and password in a protected dataset and to extract them by using KOA file functions ALLOC, OPENFILE and GETFILE.

Table 144 Log On to NetView Script Structure

Item	Description
Title	Log On to NetView
Name	LOGNET
KOA Script Description	This script is called by other scripts in order to log on to handle the online session with NetView. The script performs logon and logoff actions.
Activating the KOA Script	The KOA script is called using a CALLMEM statement from other KOA scripts (GETNTVAR, SETNTVAR, GENALERT).
Parameters	Functions: INIT, TERM, RESET
Global Variables	None.
KOA Script Logic	When the function is INIT, the KOA logs on to NETVIEW, types the userid and password and receives the main entry panel. The NetView screens are received by KOA script SCRNWAIT, which handles the special way in which NetView sends its screens (each part of the screen is sent separately). When the function is RESET, the KOA returns to the main NetView entry panel. When the function is TERM, the KOA logs off from NetView.
Recommended Category	The SolveWare category for this KIOA script is 3—the script is provided as an example. Some customization is needed if the script is to be implemented.
Customization	The user ID, password, and NetView VTAM application ID entered by this script must be modified according to site requirements. An alternative is to keep the user ID and password in a protected dataset and to extract them by using KOA file functions ALLOC, OPENFILE, and GETFILE.

Table 145 Get Value of a NetView Variable Script Structure

Item	Description
Title	Get Value of a NetView Variable
Name	GETNVAR
KOA Script Description	This KOA script retrieves the value of a given NetView variable and sets a Control-O Global variable to the obtained value.
Activating the KOA Script	The KOA script is activated by rule GETNTVAR in this solution.
Parameters	netview-variable Control-O-variable.
Global Variables	Control-O-variable specifies the name of the Global variable.
KOA Script Logic	The KOA script enters the NCCF facility and issues the supplied NetView CLIST GETCG using script NCCFCMD to display the value of the Netview variable. The Control-O Global variable is set to the obtained value.
Recommended Category	The SolveWare category for this KOA script is 3—the script is provided as an example. Some customization is needed if the script is to be implemented.
Customization	CLIST GETCG (provided in the SOLVKOA library) must be copied to one of the NetView CLIST libraries specified in the DD statement DSICLD in the NetView procedure.

Table 146 Set Value of a NetView Variable Script Structure

Item	Description
Title	Set Value of a NetView Variable
Name	SETNVAR
KOA Script Description	This KOA script sets the value of a given NetView variable to the desired value.
Activating the KOA Script	The KOA script is activated by rule SETNTVAR in this solution.
Parameters	%A1 NetView variable to be set by the script %A2 New value for the NetView variable
Global Variables	None.
KOA Script Logic	The KOA script enters the NCCF facility and issues the NetView command SETCGLOB using script NCCFCMD to set the value of the Netview variable.
Recommended Category	The SolveWare category for this KOA script is 1—little or no customization is needed.

Table 147 Enter NCCF Command and Get Response Script Structure

Item	Description
Title	Enter NCCF Command and Get Response
Name	NCCFCMD
KOA Script Description	This KOA script enters a given NCCF command and loads the response into Control-O AutoEdit variables.
Activating the KOA Script	The KOA script is called using CALLMEM statements by other scripts in this solution.
Parameters	nccf-command.
Global Variables	None.
KOA Script Logic	The KOA script enters the NCCF facility, and issues command nccf-command, which is passed as a parameter. The responses are analyzed using script NEXTLINE and stored in Control-O AutoEdit variables %%LINE1, %%LINE2,.....%%LINEn.
Recommended Category	The SolveWare category for this KOA script is 1—little or no customization is needed.

Table 148 Enter a GENALERT Command to NetView Script Structure

Item	Description
Title	Enter a GENALERT Command to NetView
Name	GENALRT
KOA Script Description	This KOA script enters an alert to NetView using command GENALERT.
Activating the KOA Script	The KOA script is invoked by rule IEF450I in this solution.
Parameters	%A1 System ID %A2 Job name
Global Variables	None.
KOA Script Logic	The KOA script enters the NCCF facility and issues NetView command GENALERT to enter an alert to Netview.
Recommended Category	The SolveWare category for this KOA script is 3—the script is provided as an example. Some customization is needed if the script is to be implemented.
Customization	The resource hierarchy specified in the GENALERT command can be adapted to site conventions. The supplied hierarchy is CPU (smf ID), PROD (CTO) and PROG (jobname). CLIST CTONVINI (supplied in the SOLVKOA Library) issues a series of NPDA set recording filter (SRFILTER) commands to allow alert generation and to allow Control-O to receive NetView alert information. The CLIST must be adapted to site conventions and copied to one of the libraries specified in DD statement DSICLD of the NetView procedure. The NetView startup CLIST used at the site must be modified to issue command CTONVINI, which sets the NPDA SRF filters.

Table 149 Calculate Line Length in a NetView Screen Script Structure

Item	Description
Title	Calculate Line Length in a NetView Screen
Name	NEXTLINE
KOA Script Description	This KOA script returns the number of the next line containing information on the NetView screen.
Activating the KOA Script	This script is activated automatically by another script that receives the NetView screen.
Parameters	%A1 The number of the current line. %A2 The number of the first line containing information on the NetView screen. %A3 The number of the last line on the screen that contains information.
Global Variables	None.
KOA Script Logic	The next line to be processed is returned to the script that invoked script NEXTLINE using variable %%nextline.
Recommended Category	SolveWare Category for this script is 1—minimal or no customization is required.

Table 150 Perform NetView GETSREEN Commands Script Structure

Item	Description
Title	Perform NetView GETSREEN Commands
Name	SCRNWAIT
KOA Script Description	Handles receipt of screens from NetView.
Activating the KOA Script	This script is called by other scripts that require access to a NetView screen.
Parameters	%A1 Maximum number of seconds to attempt to receive the screen. %A2 Number of seconds after which, if the screen did not change, to consider the screen complete.
Global Variables	None.
KOA Script Logic	NetView screens are normally sent in several pieces. Script SCRNWAIT performs a NetView GETSCREEN command once per second and determines that the screen is complete when either no new screen data is received for a specified number of seconds (variable %A2), or a maximum number of seconds elapsed (variable %A1). One of the following return codes is returned by the script: 0 – A complete screen was received. 4 – Nothing was received. 8 – A VTAM error occurred.
Recommended Category	SolveWare Category for this script is 1—minimal or no customization is required.