Reviewing runtime members and jobs

Complete this step only if you use PARMGEN; this task not required to use Configuration Manager. You want to use the Db2 subsystem definitions that are configured in a model RTE (KD2_OMPE_CHECKSYS is set to Y). In the model RTE, all the Db2 subsystems are configured that you want to monitor with the OMEGAMON Collector running on this RTE. All the configuration information that you need for the Db2 subsystem-related runtime members is created in the profile library RKD2PRF of the model RTE. By submitting the job CRTDB2* all runtime members needed for this are created on the basis of the RKD2PRF library of the model RTE.

Before you begin

Ensure that you provide ALTER privileges on::
  • rHilev.rte_name.RKD2SAM
  • rHilev.rte_name.RKD2PAR
Ensure that you provide READ privileges on:
  • rHilev.rte_name.RKD2PRF

You must also ensure that Model RTE used (Set KD2_OMPE_CHECKSYS to Y)

Procedure

  1. If you specified that your RTE uses the monitoring profiles and Db2 subsystem definitions of another RTE, then submit the appropriate $PARSE* jobs.
    For example, if you specified the following overrides:
    KD2_OMPE_USE_MODEL = Y
    KD2_OMPE_SHARED_PROFILE_LIB = IBM.DB2MODEL.LPARRTE2
    RTE_SYSV_SYSVAR_FLAG = Y

    then submit the following $PARSE* jobs that create Db2 runtime members and sample jobs required by OMEGAMON for DB2® Performance Expert.

    • rHilev.rte_name.WKD2SAM(CRTDB2) or
    • rHilev.rte_name.WKD2SAM(CRTDB2V) if enabled for System Variables
  2. Customize WCONFIG(DB2). For example:
    KD2_OMPE_USE_MODEL = N
    KD2_OMPE_SHARED_PROFILE_LIB
    RTE_SYSV_SYSVAR_FLAG = N
    If your RTE is not using Db2 monitoring profiles from another RTE, then submit $PARSE* jobs:
    • rHilev.rte_name.WKD2PRF(CRTDB2M) or
    • rHilev.rte_name.WKD2PRF(CRTDB2MV) if enabled for System Variables