The OPNOF REXX program controls the functions that the NOF performs and how it executes those functions. To call the OPNOF program, use the following REXX code:
OPNOF SET ALRTMLWTO ON|OFF SET ECHOVTAM WTO|MLWTO|NONE SET ECHOSTAT ON|OFF SET ALRTOPSGLV ON|OFF SET OPSID opsid1 (opsid2...opsidn) SHOW STAT|STATS
In calling OPNOF, you can specify any of these parameters:
Tells the NOF what to do when it receives a network alert. If you specify ON, the NOF sends the alert as a multi-line WTO message to the console, where your operators and CA OPS/MVS will see it. If you specify OFF, the NOF does not send alerts to the console.
If your main reason for sending alerts to the console is to allow CA OPS/MVS to see them, you may want to use the SET ALRTOPSGLV parameter instead.
Tells the NOF what to do when it receives an unsolicited VTAM message. When NetView is active, unsolicited VTAM messages no longer flow to the console. SET ECHOVTAM gives you the option of echoing such messages to the console. If you use the PPOLOG option of VTAM (for example, F VTAM,PPOLOG=YES), the SET ECHOVTAM parameter also controls solicited command responses.
Possible subparameters for SET ECHOVTAM are:
Tells the NOF what to do when it receives a NetView status monitor update. The NetView status monitor receives such updates directly from VTAM over a proprietary interface and gives you the option of generating message CNM094I when one of these updates occurs.
If you specify SET ECHOSTAT ON, the NOF echoes these CNM094I messages to the console where CA OPS/MVS can see them. If you specify SET ECHOSTAT OFF, the NOF ignores status monitor updates.
Tells the NOF whether to generate a CA OPS/MVS global variable called GLOBAL.OPNF.ALERT when it receives a NetView alert. This variable, generated if you specify SET ALRTOPSGLV ON, is generated in automatable format so that you can write global variable rules against it. This has the benefit of keeping alert information off the console if you only want to automate the response to the alert.
A sample rule called OPNFPALR processes the contents of the GLOBAL.OPNF.ALERT variable. If you specify SET ALRTOPSGLV OFF, the NOF generates no variable.
Tells the NOF which CA OPS/MVS subsystems to send the global variable to. This command is meaningful only if you are sending alerts to CA OPS/MVS global variables. You can specify up to five CA OPS/MVS subsystems. For example, to generate global variables for alert in the CA OPS/MVS copy running under subsystem OPSS, you would specify the following command:
NOF SET OPSID OPSS
Displays the values of the NOF parameters.
Displays the number of messages and alerts that the NOF has processed.
Because NOF parameters do not survive restarts of NetView, you should modify the initial CLIST that is invoked when NetView starts up so that the CLIST calls the sample NOF initialization routine. This routine, located in member OPNFINIT in the OPS.CCLXCLS0 data set, issues NOF SET commands for the default parameters.
To find your initial CLIST, look at the NCCFIC parameter in the DSIDMN member of the NetView parameter data set.
Copyright © 2014 CA.
All rights reserved.
|
|