Chapter 4. System Automation for z/OS working with End-to-end Automation 85
Yo u
must define the automated operator function EVTOPER. It is used to forward
events to the End-to-end Automation Adapter. If not defined, the initialization of
the End-to-end Automation Adapter fails.
We use the customization dialogs to define the automated operator functions for
the End-to-end Automation Adapter in entry type Auto Operators of the System
Automation for z/OS V3.1 policy database.
Note that the names of the Automation Operators must match those defined in
the DSIPARM data set. The following operator group had to be selected to our
z/OS systems SC63 and SC66:
EVT_PUBLISHER: Event publisher
E2E_AUTOOPS: Automated functions for End-to-end Automation Adapter
Figure 4-7 shows the output of the DISPAOPS command from system SC63N
showing the defined automated operator functions.
Figure 4-7 DISPAOPS result
4.4.3 Enabling the Event Automation Service
The Event Automation Service (EAS) can be started either with a job from an
MVS system console, or from a UNIX System Service command shell. In our
case study scenario, we automate the EAS start on our IBM Tivoli System
Automation for z/OS V3.1. Our EAS resource name is called E2E_EAS and the
MVS job name is called AOFAEVNT.
You can find a sample for starting EAS as a job located in SCNMUXMS as the
member IHSAEVNT. The initialization files are assumed to be located in a data
set allocated to DD name IHSSMP3. We follow the description within the
member for configuration.
AOFK2SO SA z/OS - Command Dialogs Line 27 of 51
Domain ID = SC63N ---------- DISPAOPS ---------- Date = 10/05/06
Operator ID = TIVO03 Time = 15:09:55
Automated
System Function Primary Status Secondary Status
-------- ---------- ------- ------ --------- ------
SC63 EVTOPER AUTEVT1 ACTIV AUTEVT2 ACTIV
SC63 E2EOPER AUTE2E ACTIV
SC63 E2EOPR01 AUTE2E01 ACTIV
SC63 E2EOPR02 AUTE2E02 ACTIV
SC63 E2EOPR03 AUTE2E03 ACTIV
86 IBM Tivoli System Automation for z/OS Enterprise Automation
Perform the following updates to the sample IHSAEVNT for our AOFAEVNT
started task:
If you do not hardcode the default name IHSAINIT for the global initialization
file, pass the name of your file using the parameter INITFILE.
If you do not hardcode the default name IHSAMCFG for the message adapter
configuration file, pass the name of your file using the parameter MSGCFG.
Modify the DD statements to specify the data set names in your installation.
The startup parameters have to be provided in the form of initialization files, and
we discuss configuration in the following sections:
“Configure the Global Initialization File” on page 86
“Configure the NetView message adapter service” on page 87
Configure the Global Initialization File
The default member name for the global initialization file is IHSAINIT. This is
found in the IBM-supplied dataset SCNMUXMS. This member was copied into
our user data set name NETVUSER.SCNMUXMS using System Automation for
z/OS V3.1 job AOFAEVNT. We follow the description within the member for
configuration.
Make sure that the NetView message adapter service is also started when
starting EAS. This is done by commenting out the following statement:
* NOSTART TASK=MESSAGEA
Specify the Program to Program Interface (PPI) called INGEV2E2 for the
receiver:
PPI=INGEVE2E
We change the IHSAINIT initialization file so that only the necessary tasks for our
environment are started at initialization time. Example 4-1 shows the
configuration in the NETVUSER.SCNMUXCL(IHSAINIT) member. We show here
only the lines that are relevant to our scenario. All the other lines are commented
out.
Example 4-1 Message adapter task
# PPI Receiver ID
PPI=INGEVE2E
# Tasks not started at initialization
NOSTART TASK=ALERTA
#NOSTART TASK=MESSAGEA
NOSTART TASK=EVENTRCV
NOSTART TASK=ALRTTRAP
Chapter 4. System Automation for z/OS working with End-to-end Automation 87
NOSTART TASK=TRAPALRT
Configure the NetView message adapter service
The default member name for the message adapter service is IHSAMCFG in
SCNMUXMS. We copy this member into our data set name
NETVUSER.SCNMUXMS. We change this IHSAMCFG for the following:
We specify the address 127.0.0.1 as the server host name.
We keep the port number on which the End-to-end Automation Adapter
listens as the default of 5529.
Set the connection mode in connection_oriented. This allows the connection
to be established at initialization time and closed at End-to-end Automation
Adapter termination time.
We keep the default value of 4096 for the maximum event size.
We specify the name of the NetView message adapter format file as
INGMFMTE. The version of the file that is to be used by end-to-end
automation is delivered in ING.SINGSAMP(INGMFMTE). No configuration is
required.
The resulting IHSAMCFG in our environment is shown in Example 4-2.
Example 4-2 Sample IHSAMCFG
ServerLocation=127.0.0.1
ServerPort=5529
ConnectionMode=connection_oriented
BufferEvents=yes
BufferEventsLimit=0
BufferFlushRate=0
BufEvtPath=/etc/Tivoli/tec/cache_nv390msg
BufEvtMaxSize=64
BufEvtShrinkSize=8
BufEvtRdBlkLen=64
EventMaxSize=4096
AdapterFmtFile=INGMFMTE
FilterMode=out
Note: Port 5529 is typically used for the Tivoli Enterprise Console®
incoming event port, which is the port that the Event Automation server
uses.

Get IBM Tivoli System Automation for z/OS Enterprise Automation now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.