338 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
LNKLST or concatenation order, you may be running with fewer entries defined.
In a later chapter covering the Tivoli NetView for z/OS data source integration,
we will verify the actual REXX environment utilization.
10.1.5 Source/390 security
The user ID that the Source/390 started tasks run under must have ALTER
authority to the object server log data sets as well as READ access to the
remaining Source/390 data sets.
If using the RACF class OPERCMDS, then the MVS.MONITOR resource must
be defined and the ID that the GTMPUMP started task runs under must have
READ access to it. Use the following command:
permit mvs.monitor class(opercmds) id(STC) access(read)
10.2 Setting up Tivoli NetView for z/OS
Many of the data sources use IBM Tivoli NetView for z/OS as the interface to get
the feed into IBM Tivoli Business Systems Manager. This is because IBM Tivoli
NetView for z/OS provides a programmable interface with an automation
capability that is needed to perform monitoring and management.
The data sources that use IBM Tivoli NetView for z/OS are:
? System Automation for OS/390 Version 2.1
? CICSPlex
? DB2
? IMS
? RODM
This section describes the common configuration steps for IBM Tivoli NetView for
z/OS. The configuration for IBM Tivoli NetView for z/OS is mostly independent
from the feeds it manages. Specific configuration steps are provided related to
the feeds itself in Chapter 11, “z/OS data feeds and discovery” on page 347.
The tasks that are needed to customize IBM Tivoli NetView for z/OS are:
? 10.2.1, “Modify the NetView started task procedure” on page 339
? 10.2.2, “Modify the DSIPARM members” on page 339
? 10.2.3, “Enable the PPI connection” on page 339
? 10.2.4, “Enable NETCONV connection” on page 340
? 10.2.6, “Tuning considerations” on page 341
Chapter 10. z/OS installation and configuration 339
10.2.1 Modify the NetView started task procedure
Modify the IBM Tivoli NetView for z/OS startup procedure to concatenate the IBM
Tivoli Business Systems Manager libraries as shown in Table 10-2.
Table 10-2 Modification to IBM Tivoli NetView for z/OS startup procedure
10.2.2 Modify the DSIPARM members
This section describes the required modification of the NetView DSIPARM
members.
? Modify hlq.SGTMSAMP(IHS$MAT) to comment out the unused interfaces and
include this member at the top of the current message table. Typically add in
the DSITBL01 a line such as
%INCLUDE IHS$MAT
? Add an include statement in DSICMD for IHS$CMD, such as
%INCLUDE IHS$CMD
? Modify hlq.SGTMSAMP(IHS$OPF) to comment out the unused interface(s).
Add an include statement in DSIOPF for IHS$OPF, such as:
%INCLUDE IHS$OPF
? Modify hlq.SGTMSAMP(IHS$CAT2) to comment out the unused interface(s)
and include this member in CNMSCAT2 or your local command authorization
table.
? Ensure that your local version of CNMSCAT2 permits the groups NVOPS1
and NVOPS2 to the MVS and EXCMD commands.
10.2.3 Enable the PPI connection
Uncomment the statement in the object pump parameter member to enable the
program-to-program interface (PPI) to IBM Tivoli NetView for z/OS as shown in
Example 10-8 on page 340.
DD name TBSM library Notes
STEPLIB hlq.SGTMMODS TBSM modules
DSICLD hlq.SGTMEXEC REXX programs
DSIPARM hlq.SGTMSAMP sample members
DSIMSG hlq.SGTMMSGS message files
340 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
Example 10-8 Enabling PPI for TBSM
* To activate the NetView PPI interface uncomment
* the following line *
PPI=YES
The result from the DISPPI command issued in NetView indicates that the default
PPI receiver name, NETVAOP, is active, as shown in Example 10-9. Note that the
name NETVAOP is reserved.
Example 10-9 DISPPI output
DISPPI
RECEIVER RECEIVER BUFFER QUEUED TOTAL STORAGE RCVR
IDENTITY STATUS LIMIT BUFFERS BUFFERS ALLOCATED ASID
-------- -------- ---------- ---------- ---------- ---------- ----
NETVALRT ACTIVE 1000 0 3 0 005F
ISTMTRCV ACTIVE 500 0 38 0 001A
DSIMCAT ACTIVE 25 0 0 0 005F
SC69NSCO ACTIVE 1000 0 0 0 005F
SC69NHTM ACTIVE 1000 0 0 0 005F
NETVRCV ACTIVE 500 0 103 0 005F
DSIQTSK ACTIVE 100 0 0 0 005F
NETVAOP ACTIVE 1000 0 405 0 0071
IHSATEC ACTIVE 5000 0 21 0 006D
END OF DISPLAY
10.2.4 Enable NETCONV connection
A NETCONV connection between the IBM Tivoli Business Systems Manager
task server and the NetView for z/OS focal point enables commands to be issued
from the IBM Tivoli Business Systems Manager console, executed in NetView,
and the response returned to a command response window on the IBM Tivoli
Business Systems Manager console. The steps to configure a NETCONV
session from NetView for z/OS are:
1. Verify that the DUIFPMEM member in DSIPARM contains the following
parameters:
TCPANAME The name of the local TCP/IP stack.
USETCP/IP Must be YES.
SOCKETS Specifies the number of supported connections.
PORT Listening port number, typically 4020. This number
must match the tserver_390 parm on the task server.
2. Verify that the DUIIGHB member in DSIPARM contains the parameter
TCPANAME that identify the name of the local TCP/IP stack.
Chapter 10. z/OS installation and configuration 341
Start the NETCONV session to the task server after the workstation steps have
been completed for NETCONV communication. The format of this command and
the response are shown in Example 10-10. The IP address is for the host running
the task server, typically the database server.
Example 10-10 NETCONV connection
NETCONV ACTION=START,IP=ibmtiv5.itsc.austin.ibm.com
DUI401I NETCONV COMMAND PROCESSED SUCCESSFULLY. COMMUNICATION TO IP
ibmtiv5:4020 (9.3.4.55:4020) STARTED.
This NETCONV connection must be available continuously for IBM Tivoli
Business Systems Manager to send commands to the z/OS system, so it must
be issued from an AUTOTASK. We use AUTO2 to keep this connection, using the
EXCMD command to let the NETCONV command be executed by AUTO2.
10.2.5 Enabling communication between NetView systems
For commands to be available to all z/OS systems, these systems must be
running IBM Tivoli NetView for z/OS. The system may be running a procedural
version of IBM Tivoli NetView for z/OS instead of the enterprise version that is
required for the focal point.
IBM Tivoli NetView for z/OS uses the RMTCMD mechanism to ship commands
to remote nodes. This connection requires that NetView can authenticate the
operator and to have knowledge of the remote nodes.
10.2.6 Tuning considerations
These are the recommended tuning considerations:
? REGION size
Changing the region size to 0 enables the IBM Tivoli NetView for z/OS
program to allocate the storage it needs.
? DSISVRT VSAM files
IMS data source integration uses the save/restore VSAM files. Review and
modify size if necessary.
? IRXANCHR
Issuing the IHS$DBUG ENVIRO command from IBM Tivoli NetView for z/OS
shows the number of REXX environments in use.
? DSICTMOD
Issue QRYGLOBL COMMON from IBM Tivoli NetView for z/OS, and increase
the number of common global variables if necessary using CNMS0055.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.