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.