Chapter 2. Components and functions 53
2.4 Mainframe (z/OS) resource feeds
Mainframe component connectivity is shown in Figure 2-10.
Figure 2-10 z/OS components and feeds
zOS
TBSM SOURCE/390
SOURCE/390
Object Pump
WebSphere
for OS/390
DFSMShsm
SMS
XRC
MVS
Console
Messages
and
Commands
CICSPlex System
Manager for OS/390
Resource Management
Facility
OMEGAMON
CICS Transient Data
Tivoli Workload
Scheduler
CICSPlex
IMS
DB2
System Automation for
OS/390 V2R1
Tivoli NetView
for z/OS
CPSM API
GPMSERVE
3270 screen
External Data
Interface (EDI)
Program-to-
program
Interface (PPI)
SOURCE/390 Dataspace
SOURCE/390 Object Server
SA/390 V1R3 and other
automation tools
Automation EDI interface
TBSM Servers
Host
integration
Server
Database
Server
Event Server
Task Server
NETCONV
SNATCP/IP
GTMAOPE0
MVS IP
Listener
RODM
EKGNotify
54 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
We will discuss this connectivity in the following sections:
? 2.4.1, “OS/390 components” on page 54
? 2.4.2, “Windows servers connection” on page 57
? 2.4.3, “Object registration process” on page 60
? 2.4.4, “Bulk discovery” on page 62
? 2.4.5, “Command support” on page 68
2.4.1 OS/390 components
Source/390, which resides on a z/OS system, enables the monitoring and
management of OS/390 and z/OS systems. Source/390 components are:
? Source/390 Object Pump
? Source/390 Object Server
? Source/390 Data Space
The Source/390 object pump collects event and performance data and places it
in the Source/390 data space. The Source/390 object server then picks up the
data and exceptions and passes them to the IBM Tivoli Business Systems
Manager servers for subsequent processing and storing in the database.
The object pump uses several mechanisms to get the feeds:
? NetView program-to-program interface (PPI): The object pump registers itself
as the PPI listener called NETVAOP. NetView automation can write to the PPI
interface and send events to IBM Tivoli Business Systems Manager. This
mechanism is used for z/OS subsystems such as CICS, IMS, DB2, and
System Automation/390 V2.
? The external data interface (EDI) uses cross-memory services to pass
messages and exceptions that reside on the same MVS host to IBM Tivoli
Business Systems Manager. Messages and exceptions are passed by EDI
directly to the Source/390 object pump and are not displayed on the system
console. This interface is used by the CICS transient data monitor, Tivoli
Workload Scheduler for z/OS batch information, System Automation for
OS/390 v1.3, and other automation products.
? Most of the z/OS subsystems—such as storage information (DFSMS),
extended recovery (XRC), and WebSphere information—as well as general
JES and z/OS information, are read through the extended MCS console
interface.
Chapter 2. Components and functions 55
? Several feeds have a specialized interface, such as:
– Resource Object Data Manager (RODM): The object pump subscribes to
the RODM change notification (EKGNotify) so that any RODM object
changes will be notified to IBM Tivoli Business Systems Manager.
– CICSPlex System Manager (CPSM): The object pump actively queries the
CPSM using the CPSM API interface.
– Resource Monitoring Facility (RMF™): The object pump uses the
GPMSERVE process to get RMF metrics for z/OS resources.
– Omegamon II: The object pump interfaces with Omegamon’s 3270
exception screen and monitors the exceptions that occur.
This is the start-up sequence for the address spaces of Source/390:
1. First, the dataspace is started. It must show the GTM5010I message before
we can proceed. The startup log for the data server is shown in Figure 2-11.
Figure 2-11 TBSM data server startup log
2. The object server is started and connected to the data server, as seen in
message GTM4041I in Figure 2-12 on page 56. It then allocates LU 6.2
sessions or a TCP/IP session.
– An LU 6.2 session is indicated by message GTM7406I, and the
transaction programs are initialized as indicated by the GTM7424I
messages.
– An IP session is indicated by messages GTM8205I and GTM8252I, as
shown in Figure 2-12 on page 56.
GTM5000I TBSM DATASPACE INITIALIZATION STARTING
GTM4600I EXTENDED RECOVERY ENVIRONMENT ESTABLISHED
GTM4110I GTMDSPC , USING ID 01
GTM5002I PROCESSING PARMLIB MEMBER: PDSC6900
GTM5101I TBSM DATASPACE CREATED, SIZE= 42467328, ORIGIN=00000000
GTM5030I MODIFY INTERFACE ESTABLISHED, CONSOLE COMMUNICATION AVAILABLE
GTM5010I TBSM DATASPACE INITIALIZATION COMPLETE
56 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
Figure 2-12 TBSM object server startup log
3. The object pump is started and, as indicated by the log in Figure 2-13 on
page 57, it performs the following:
– Issues the MONITOR command.
– Allocates an MCS console, as indicated by IEA630I.
– Connects to the object server, as indicated by GTM1620I.
– Starts the registration process, as indicated by GTM1770I and GTM1780I.
GTM7500I INITIALIZATION IN PROGRESS
GTM4600I EXTENDED RECOVERY ENVIRONMENT ESTABLISHED
GTM4110I GTMSRVR , USING ID 01
GTM7508I TBSM SERVER DETECTED, JOBNAME=GTMDSPC
GTM4403I Q WARM STARTED, QADDR=00001000, ALET=01FF001B, SIZE=100 PAGES,
ID=GTMSRVR
GTM8205I GTMIPSND : READY TO TRANSMIT TO 9.3.5.11 PORT(1022)
GTM8252I GTMIPRCV : LISTENING ON PORT 1024
GTM4403I Q WARM STARTED, QADDR=00071000, ALET=01FF001B, SIZE=50 PAGES,
ID=GTMLOG
GTM4200I ALLOCATION SUCCESSFUL, DDNAME=ACC1LOG , S99ERROR=0000,
S99INFO=0000, DSNAME=GTMV2R1.SC69N.SRVR.LOG1
GTM4010I TBSM INITIALIZATION COMPLETED
Chapter 2. Components and functions 57
Figure 2-13 TBSM object pump startup log
– The object registration handshake is explained from the Windows side
in 2.4.3, “Object registration process” on page 60.
2.4.2 Windows servers connection
The connection to IBM Tivoli Business Systems Manager servers is shown in
Figure 2-14 on page 58.
GTM7500I INITIALIZATION IN PROGRESS
GTM4600I EXTENDED RECOVERY ENVIRONMENT ESTABLISHED
GTM4110I GTMPUMP , USING ID 01
GTM7508I TBSM SERVER DETECTED, JOBNAME=GTMDSPC
GTM4403I Q WARM STARTED, QADDR=00066000, ALET=01FF0010, SIZE=10 PAGES,
ID=GTMPUMP
GTM7801I STORAGE ALLOCATED FOR 10,016 TRAPS
GTM7524I VTAM 3270 SERVICES ARE NOT AVAILABLE
MN JOBNAMES,T
MONITOR SESS,T
IEA630I OPERATOR TM39069 NOW ACTIVE, SYSTEM=SC69 , LU=TM39069
GTM7545I TM69 : SUBSYSTEM INITIALIZED
GTM7815I TBSM HAS CONNECTED TO RODM : RODM
GTM7890I PPI RECEIVER IS ACTIVE
GTM7501I RUNNING INITIAL REXX EXEC : GTMRX004
GTM0001I TBSM INITIALIZATION STARTED - 4 Dec 2002 11:05:29
GTM0002I SYSTEM WAS IPL'D ON 10/23/2002 (102302) AT 16:52:42
GTM0003I TBSM IS RUNNING ON SYSTEM SC69
GTM2101I LOG PROCESSING IS AVAILABLE. DDNAME = ACC1LOG
GTM2102I DSNAME = SYSOUT(A)
GTM2104I THE LOG WILL BE CLOSED AND OPENED ON THE FOLLOWING INTERVAL:
04:00:00
GTM1620I OBJECT PUMP TO OBJECT SERVER HANDSHAKE STARTED
GTM0220I TBSM LOGON PROCESSING INITIALIZATION STARTED ...
GTM1001I TBSM EVENT MANAGER INITIALIZATION STARTED ...
GTM9520I TBSM COMMAND PROCESSOR INSTALLED
GTM0990I TBSM INITIALIZATION COMPLETED
GTM1770I ALL REQUIRED SHARED VARIABLES HAVE BEEN REGISTERED, PROCESSING
CONTINUES
GTM1780I OBJECT PUMP/OBJECT SERVER IS REQUESTING OBJECTS
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.