Predefining and managing OMEGAMON started tasks

If you are using System Automation for NetView®, make sure the automation rules are defined to start and manage the OMEGAMON® started tasks. System Automation comes with an OMEGAMON policy that predefines these rules.

See the System Automation publications for information about the OMEGAMON policy.

The following table lists the OMEGAMON started tasks (default names have been used) and associated automation dependencies.
Note: The CUA-related started tasks are applicable to only OMEGAMON family V5.3.0 and earlier versions. PARMGEN 3Q17 IF PTF will no longer generate these started tasks if later versions are installed in the CSI that the PARMGEN environment points to.
Table 1. OMEGAMON started tasks and automation dependencies
PARMGEN Configuration Parameter Default started task name Description
Dependency on VTAM

VTAM must be running and the major node must be active.

KM2_CLASSIC_STC IBMM2RC IBM® OMEGAMON for z/OS® (3270)
KM2_CUA_STC IBMM2 IBM OMEGAMON for z/OS (3270)
KC2_CCnn_CLASSIC_STC IBMOCx

(where x = 0, 1, 2, 3..15)

IBM Z® OMEGAMON for CICS

(where nn = 01, 02, 03..; 1 per 3270 Classic started task that can monitor multiple CICS regions per STC)

KI2_I1nn_CLASSIC_STC IBMOIx

(where x = 0, 1, 2, 3..99)

IBM OMEGAMON for IMS on z/OS

(where nn = 01, 02, 03..; 1 per 3270 Classic STC that monitors 1 IMS subsystem per STC)

KI2_CUA_STC IBMI2 IBM OMEGAMON for IMS on z/OS (3270)
GBL_DB2_KD2_CLASSIC_STC IBMO2 IBM OMEGAMON for Db2® Performance Expert/Performance Monitor on z/OS (3270)
KDS_TEMS_STC IBMDS Tivoli Enterprise Monitoring Server
RTE_CANSETE_STC IBMETE OMEGAMON End-to-End
KM2_EPILOG_COLLECTOR_STC IBMM2HI IBM OMEGAMON for z/OS (3270) Historical Collector (Epilog)
KM2_EPILOG_ZOOM_STC IBMM2EZ IBM OMEGAMON for z/OS (3270) Epilog Zoom
KDF_CUA_STC IBMDF IBM OMEGAMON for Storage on z/OS (3270)
KMV_CUA_STC IBMMV IBM OMEGAMON DE on z/OS OMEGAVIEW (Agent)
KON_CUA_STC IBMON IBM OMEGAMON for Networks on z/OS (3270)
Dependency on TCP/IP

TCP/IP must be started, ready to accept binds, and able to resolve DNS names; this automation usually requires OMPROUTE.

KDS_TEMS_STC IBMDS Tivoli Enterprise Monitoring Server
KM2_CUA_STC IBMM2 IBM OMEGAMON for z/OS (3270)
KC5_AGT_STC IBMC5 IBM Z OMEGAMON for CICS (Agent)
KD5_AGT_STC IBMD5 IBM OMEGAMON for Db2 Performance Expert/Performance Monitor on z/OS (Agent)
KI5_AGT_STC IBMI5 IBM OMEGAMON for IMS on z/OS (Agent)
KN3_AGT_STC IBMN3 IBM OMEGAMON for Networks on z/OS (Agent)
KMQ_AGT_STC IBMMQ IBM OMEGAMON for Messaging- MQ(Agent)
KMC_AGT_STC IBMMC IBM OMEGAMON for Messaging- MQ Configuration (Agent)
KQI_AGT_STC IBMQI IBM OMEGAMON for Messaging- Integration Bus (Agent)
KYN_AGT_STC IBMYN ITCAM for Application Diagnostics on z/OS (Agent)
KOB_TOM_STC IBMTOM IBM OMEGAMON enhanced 3270 user interface
KGW_AGT_STC IBMGW IBM Z OMEGAMON for CICS TG (Agent)
Dependency on Tivoli Enterprise Monitoring Server (IBMDS)

These tasks retry if they do not succeed in connecting to IBMDS. The dependency is optional.

KC5_AGT_STC IBMC5 IBM Z OMEGAMON for CICS (Agent)
KD5_AGT_STC IBMD5 IBM OMEGAMON for Db2 Performance Expert/Performance Monitor on z/OS (Agent)
KI5_AGT_STC IBMI5 IBM OMEGAMON for IMS on z/OS (Agent)
KM2_EPILOG_COLLECTOR_STC IBMM2HI IBM OMEGAMON on z/OS (3270) Historical Collector (Epilog)
KDF_CUA_STC IBMDF IBM OMEGAMON for Storage on z/OS (3270)
KMQ_AGT_STC IBMMQ IBM OMEGAMON for Messaging- MQ (Agent)
KMC_AGT_STC IBMMC IBM OMEGAMON for Messaging- MQ Configuration (Agent)
KQI_AGT_STC IBMQI IBM OMEGAMON for Messaging- Integration Bus (Agent)
KYN_AGT_STC IBMYN ITCAM for Application Diagnostics on z/OS (Agent)
KM2_CUA_STC IBMM2 IBM OMEGAMON for z/OS (3270)
KN3_AGT_STC IBMN3 IBM OMEGAMON for Networks on z/OS (Agent)
KOB_TOM_STC IBMTOM IBM OMEGAMON enhanced 3270 user interface
KGW_AGT_STC IBMGW IBM Z OMEGAMON for CICS TG (Agent)
No dependencies
RTE_CANSCN_STC IBMCN OMEGAMON Subsystem
KM2_CSA_ANALYZER_STC IBMM2CS IBM OMEGAMON for z/OS (3270) Common Storage Area Analyzer
Note: IBMOCx must come up before the CICS regions, or the OMEG INIT fails.