Defining the OMEGAMON subsystem to z/OS

Edit online

Some OMEGAMON® monitoring agents depend on the OMEGAMON subsystem. Before starting a runtime environment that contains any of these monitoring agents, you must define the OMEGAMON subsystem to z/OS®.

Before you begin

Check whether the OMEGAMON subsystem has already been defined to z/OS.

For example, issue the following DISPLAY MVS™ system command to list subsystems:

D SSI

The default name of the OMEGAMON subsystem is CNDL.

About this task

IBM Z® Monitoring Configuration Manager does not depend on the OMEGAMON subsystem. Defining the OMEGAMON subsystem is not a prerequisite for using Monitoring Configuration Manager.

However, the OMEGAMON subsystem is a prerequisite for starting some of the runtime environments that you create with Monitoring Configuration Manager.

The following OMEGAMON monitoring agents depend on the OMEGAMON subsystem:

  • CICS® (optional)
  • Db2®
  • IMS
  • Storage
  • z/OS

You must define the OMEGAMON subsystem on each LPAR where you plan to start runtime environments that contain any of these monitoring agents.

When you create a runtime environment that contains one of these monitoring agents, the generated runtime members include a started task that starts the OMEGAMON subsystem.

Optionally, you can configure your LPAR to start the OMEGAMON subsystem whenever z/OS restarts (IPL).

Procedure

  1. Copy the OMEGAMON subsystem initialization module KCNDLINT from the target library TKANMOD to a library in the linklist.
    For example, SYS1.LINKLIB.
  2. Refresh the library lookaside (LLA) library directory indexes.

    Issue the following MODIFY MVS system command:

    F LLA,REFRESH
  3. Dynamically define the OMEGAMON subsystem to z/OS.

    Issue the following SETSSI MVS system command:

    SETSSI ADD,SUBNAME=CNDL,INITRTN=KCNDLINT,INITPARM='SSPROC=OMEGCN'

    where:

    • CNDL is the subsystem name.

      CNDL is the default value of the runtime environment parameter RTE_KCNSTR00_SSID.

      The values of SUBNAME and RTE_KCNSTR00_SSID must match.

    • OMEGCN, the name of the procedure that initializes the subsystem, is the value of the runtime environment parameter RTE_CANSCN_STC.

      The default value of RTE_CANSCN_STC consists of the value of the RTE_STC_PREFIX parameter followed by the suffix CN. The value of RTE_STC_PREFIX in the initial set of parameters created by Monitoring Configuration Manager is OMEG (an abbreviation of OMEGAMON).

      The SSPROC parameter of the SETSSI command and the runtime environment parameter RTE_CANSCN_STC must match.

    If you do not want the subsystem address space to be started immediately, omit INITPARM.

  4. Define the OMEGAMON subsystem in the IEFSSNxx member of the SYS1.PARMLIB library.

    For example:

    SUBSYS SUBNAME(CNDL) INITRTN(KCNDLINT) INITPARM('SSPROC=OMEGCN')

    The SETSSI command in the previous step dynamically defines the subsystem so that it is available immediately. Defining the subsystem in the IEFSSNxx member defines the subsystem during z/OS initialization (IPL), so that you do not have to reissue the SETSSI command after each IPL.

    If you do not want the subsystem address space to be started at IPL, omit INITPARM.