IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual page 115

Initializing the Tivoli Monitoring Service Engine service:
Tivoli Monitoring Service Engine successful initialization is noted by message
KLVIN408 IBM OMEGAMON PLATFORM ENGINE VERSION 400 READY. There
are two classes of Tivoli Monitoring Service Engine initialization failures:
v Failures that result from unsupported Tivoli Monitoring Service Engine startup
parameters. For example: User abend U0012
v Failures that result from protocol initialization failures. For example: User abend
U0200
Repairing Tivoli Monitoring Services Engine initialization failures:
For U0012 Abends, incorrect Engine STARTUP parameters, examine and correct the
parameters pointed to by the RKLVIN DD statement of the started task JCL. Most
often, U0012 Abend failures can be resolved by backing out the last change made
to the Tivoli Monitoring Services Engine startup parameters. For U0200 Abends,
the root cause of the protocol failures must be remedied. These failures are covered
in "TCP/IP service initialization" and "SNA service initialization" on page 100.
RAS1 service initialization
The Reliability, Availability and Servicability (RAS1) service refers to the RAS1
building block (Basic Services component) used for diagnostic tracing. Nearly all
diagnostic information for IBM Tivoli Monitoring is delivered via the RAS1 (trace)
component. This component is configured in member KBBENV of RKANPAR
using the KBB_RAS1 environment variable. Often, customers redirect the
initialization member via CT/Engine INITLIST processing. INITLIST processing is
always echoed to the RKLVLOG with the KLVIN411 message. The following shows
an example of a typical KBBENV override to KDSENV
KLVIN410 INITLIST MEMBER KDSINIT BEING PROCESSED
KLVIN411 KLVINNAM=KDSINNAM
KLVIN411 KLVINTB=KDSINTB
KLVIN411 KLVINVLG=KDSINVLG
KLVIN411 KLVINNAF=KDSINNAF
KLVIN411 KLVINVPO=KDSINVPO
KLVIN411 KLVINSTG=KDSINSTG
KLVIN411 KLVINVAM=KDSINVAM
KLVIN411 KBBENV=KDSENV
In this instance, configuration of KBB_RAS1 must display in member KDSENV of
RKANPAR.
TCP/IP service initialization
TCP/IP service is Transmission Control Protocol. TCP/IP provides end-to-end
connectivity for application-layer codes such as telnet, FTP, Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server, and the Tivoli Enterprise
Monitoring agents.
Initializing the TCP/IP service:
TCP/IP services for this address space are available if any of the following
messages are present:
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.tcp
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.pipe
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.udp
These messages are only displayed when KDC_DEBUG=Y is active in the
environment; KDC_DEBUG=Y must be added to member KDSENV of RKANPAR
(or the appropriate initialization member) to obtain the level of tracing required to
have these messages echoed to the RAS1 log. IF KDC_DEBUG=Y is set and if none
of these messages are in the log, then initialization of the TCP/IP service failed.
Chapter 5. Installation and configuration troubleshooting
97