IBM Tivoli OMEGAMON XE V3.1 Deep Dive on z/OS

120 IBM Tivoli OMEGAMON XE V3.1 – Deep Dive on z/OS

Figure 4-5 RAS1 banner

Successful initialization of RAS1 service with the presence of the RAS1 banner

in Figure 4-5 is a necessary but not sufficient condition to diagnose failures in

OMEGAMON address space. You also need to have the configuration of

KBB_RAS1 to any value that is not NONE. In Figure 4-5, KBB_RAS1 is set to

ERROR. This shows that all messages with the severity of error and above will

be written out. This provides the necessary and sufficient level of RAS1 tracing to

diagnose the majority of OMEGAMON address space startup issues.

You might also include the KDC_DEBUG=N parameter in the configuration.

4.3.2 ITMS:Engine service

The ITMS:Engine is a collection of basic z/OS and communication service

routines built specifically for the z/OS environment. Most OMEGAMON address

spaces load and employ the services of ITMS:Engine, except OMEGAMON

classic components.

The ITMS:Engine successful initialization is noted by the KLVIN408 message as

shown in Example 4-1.

Example 4-1 ITMS:Engine initialization

KLVIN408 CANDLE ENGINE VERSION 180 READY ON SC52(0A6A3A208

There are two possible ITMS:Engine initialization failures:

򐂰

Invalid ITMS:Engine startup parameters. Indicated by user abend code U0012.

For U0012 abends, the startup parameter is referred by the RKLVIN DD

statement of the started task JCL. Most often, U0012 abend can be remedied

by backing out the last change made to the ITMS:Engine startup parameters.

You also should check whether all STEPLIB datasets are APF authorized.

========================> Candle CT/RAS1 Service Log +=====================

System Name: SC69 Process ID: 93

User Name: STC Job Name: CANSDSST

System Type: OS/390;SP7.0.6 MAC1_ENV Macro: 0x1995

Start Date: 2005/11/16 Start Time: 13: 9:13

KBB_RAS1: ERROR

KBB_ENVPATH: KBBENV

============================================================================