AUTOOPS

Purpose

The AUTOOPS control file entry applies to IP management and AON functions.

The AUTOOPS control file entries define NetView® operator IDs that function as automation operators. Automation operators are NetView tasks that respond to network messages without requiring operator intervention. Each automation operator initiates actions through procedures defined in the control file. Automation operators are assigned specific messages to act upon. Messages are assigned on the MSG parameter of the AUTOOPS entry.

The NetView program defines multiple automation operators. Each operator processes as a separate task within the NetView program. This task design permits the NetView program to distribute its workload among the automation operators, thereby improving system performance.

Syntax

AUTOOPS

operid

Defines a name for the automation operator. Each automation operator relates to a specific NetView operator ID by using the AUTOOPS ID parameter.

NetView command lists use the automation operator name to route commands from one automation operator to another. During processing, the associated NetView operator ID is substituted. This technique enables the command list coding to be independent of the NetView operator IDs, which might be unique in each installation. The value specified for the automation operator name creates a NetView common global (CGLOBAL). The NetView operator ID is stored in this common global (CGLOBAL).

Each AUTOOPS entry creates at least two common global variables:

automation operator name
automation operator name with the number 2 appended at the end

Examples of automation operator names are MSGOPER and MSGOPER2. If only one ID is defined, both common global variables contain the same name and ID.

The following automation operator names are provided:

AIPOPER (AON): Sets and resets the AIP (Automation In Progress) operator status bit in RODM. This bit causes a display pattern to be placed on the object in NetView management console. RODM AIP operators issue the commands necessary to update resource objects in RODM views with the AIP operator status. These operators are also used in the management of the OIV processing.
ALRTOPER (AON, IPMGT): Sends alerts and resolutions to NetView over an LU 6.2 session.
BASEOPER (AON, IPMGT): Provides backup for other automation operators.
CONNOPER (AON): The automation operator used for active connection monitoring.
DVIPOPER: Used for DVIPA polling processes.
GATOPER (AON): The outbound gateway operator for automation notification forwarding.
INFOPER (AON): Serializes the updates to the inform log.
MSGOPER (AON, IPMGT): Formats and issues notifications and DDF updates.
NETOPER (AON/SNA): Initiates routines based on the NetView automation table and AON/SNA generic failure and recovery routines.
OIVOPER (AON): An optional operator task used by the Operation Intervention View (OIV) function. When enabled, automatically deletes resources from the OIV at specified intervals. Only resources with the display status of satisfactory (129) are removed.
TCPOPER (AON/TCP, IPMGT): Used for TCP/IP automation
TRAPOPER (AON): Used for trap automation processes
WKSTOPER (AON/TCP): Sends and receives commands and responses between AON and a workstation with the interface installed.
X25OPER: Used by X25 automation processes (AON/SNA only)

User-defined automation operator names can be added by defining a 1 - 10 character name, without embedded blanks, commas, single quotations, or periods, and cannot begin with a number.

ID

Defines a NetView operator ID used for an automation operator. Each operator ID must be defined to the NetView program in the DSIOPF member. The primary NetView operator ID receives all the incoming messages assigned to this automation operator. The secondary operator is defined for backup or off-load purposes only.

The NetView program only supports offloading work of NETOPER, MSGOPER, TCPOPER, and AIPOPER. Provide at least two IDs for the automation operator definitions. Code a root autotask name to be used along with a number to identify how many autotasks are needed. For example, to define five AIPOPER autotasks (AUTAIP1 through AUTAIP5), code the following command:

AUTOOPS AIPOPER,ID=(AUTAIP,5)

This creates five common global variables: AIPOPER, AIPOPER2, AIPOPER3, AIPOPER4, and AIPOPER5.

Note: When coding any AUTOOPS definitions, follow the syntax provided in the sample policy definitions shipped with the NetView program.

The outbound gateway operator is defined as a NetView operator. The default naming convention for the operator ID is the three letter prefix GAT, followed by the domain-ID.

You can change the autotask names as needed for your installation.

SEC

Specifies one or more NetView operator IDs to receive a copy of the messages defined for this automation operator. Messages that are sent to these operator IDs are not subject to automation. .

You can also specify a valid NetView operator group. All operators in this list receive the message if they are logged on and at least one operator in the ID list or one group ID is logged on. By defining a group name, you can send a secondary message to all operators belonging to the group. Define groups in the CNMSTUSR or CxxSTGEN member by using the ASSIGN.groupname.GROUP statement. For information about changing CNMSTYLE statements, see IBM® Tivoli® NetView for z/OS® Installation: Getting Started.

MSG

Specifies the messages to be routed to this automation operator. The NetView ASSIGN statement is used to route these messages. You can use a prefix and an asterisk (*) to specify groups. For example, to specify all messages beginning with DSI, use DSI*. To specify all messages, use just an asterisk (*). Do not assign messages to BASEOPER and GATOPER parameters.

Note: SNA Automation requires specific VTAM® messages to be assigned.

Usage notes

The AUTOOPS statement requires that the IPMGT tower or the AON tower be enabled.
NetView message assignment statements are issued based on the order of the automation operators in the control file. The assignment statements must not overlap and must be placed in order from most specific to least specific.
Define at least one automation operator, referred to as the base operator (BASEOPER), with an AUTOOPS entry. Several automation operators are provided for optimum operation. Define additional automation operators when developing your own extensions to the automation process.
The primary operator assigned in the AUTOOPS ID statement is the first receiver of an assigned message. If the primary operator is logged off or abnormally ends, the secondary operator receives the message. If a secondary operator is not defined or is not logged on, the automation operator (BASEOPER) receives the message. This sequence is designed to provide a level of redundancy to ensure that automation continues if one or two automation operators were logged off or not functioning. The command list must be run to the secondary operator. Load balancing is not dynamic.
If you change the primary assignments provided with the NetView program, results are unpredictable.
In situations where a command list runs for a long time period, define a secondary operator. The secondary operator can process the command list, freeing up the primary operator to handle incoming messages.
When using Resource Access and Control Facility (RACF®), it is not necessary to define the automated NetView operator IDs (host). The access checking of RACF is performed only when an operator (host) or another NetView system attempts a logon (NNT). The checking is bypassed if an automation operator is started through the AUTOTASK command. Therefore, when a NetView automation operator ID is not defined to RACF, an operator is not authorized to use that ID.
Gateway operators defined by GATOPER must be defined to RACF. GATOPERs on the focal point must be defined to RACF. If your installation is controlled by ACF2, define automation operators to ACF2, but not to RACF.
If an automation operator is not active (indicated by DSI008I message), the NetView program restarts the task. The NetView program builds and initiates the AUTOTASK command based on the DSI008I message.

Examples

The following examples of AUTOOPS control file entries are SNA examples.

The following example shows an automation operator assignment by the AUTOOPS entry:
```
AUTOOPS GATOPER,ID=GATCNM01
```
In this example, the name of the automation operator is GATOPER. The NetView operator ID, defined in the DSIOPF member, is GATCNM01. The ID is not enclosed in parentheses because only a single NetView operator ID is defined. GATOPER has no messages assigned to it. GATOPER is an outbound gateway operator that establishes and maintains the connections to other domains to enable automation notification forwarding.
The following examples are of additional automation operator definitions by AUTOOPS:
```
AUTOOPS BASEOPER,ID=AONBASE
AUTOOPS MSGOPER,ID=(AONMSG,2),MSG=EZL*
```
In the following example, secondary automation operators are added using the AUTOOPS entry:
```
AUTOOPS NETOPER,ID=(AONNET,5),
        SEC=(+OURGRP,OPER6),
        MSG=(CNM*,DSI*,EMS*,BNJ*)
```
In this example, the system programmer adds all operators to the group +OURGRP, which must be created by a user program that issues the ASSIGN command, and specifies that OPER6 get copies of all messages assigned to NETOPER. These copies are not subject to automation.
In the following example, nine automation operators are defined for AON messaging:
```
AUTOOPS MSGOPER,ID=(AONMSG,9),
        MSG=(EZL*)
```
In this example, the system programmer increases the AON default of two MSGOPER autotasks to nine. The autotask names used are AONMSG1 through AONMSG9. AON contains 10 MSGOPER autotasks which are defined in EZLOPF. If the system programmer chooses to define 15 MSGOPER autotasks, EZLOPF must be modified to add the additional autotask definitions.
In the following example, the operator ID that is used for automatic deletion of resources from the Operator Intervention network View (OIV) is defined:
```
AUTOOPS OIVOPER,ID=AUTOIV1
```
A TIMER statement is required to activate the automatic deletion.