Basic upgrade requirements

Before you begin to upgrade your OMEGAMON products, any Tivoli Enterprise Monitoring Server (hub, remote, backup, and Hot Standby) that a monitoring agent reports to must be running at the prerequisite level. In addition, any agent and the Tivoli Enterprise Monitoring Server that it reports to must be running with the same level of IBM Tivoli Monitoring maintenance. All products in a runtime environment must use the same configuration method. If you are configuring multiple products, some of which require PARMGEN, you must use PARMGEN for all of the products.

Whenever you upgrade an OMEGAMON product or install PTF maintenance, the runtime environment libraries must be loaded to the upgraded maintenance level, at a minimum (which means that the PARMGEN KCIJPLOD load job must be run).

• If you are upgrading to OMEGAMON XE for Db2 Performance Expert V5.4.0 or OMEGAMON XE for Db2 Performance Monitor V5.4.0 in an existing PARMGEN runtime environment, to enable support for Db2 V11, you must manually add the following two parameters to the rte_plib_hilev. rte_name.WCONFIG($GBL$USR) profile:
  • GBL_DSN_DB2_LOADLIB_V11
  • GBL_DSN_DB2_RUNLIB_V11
  To enable support for Db2 V12, you must manually add the following two parameters to the rte_plib_hilev. rte_name.WCONFIG($GBL$USR) profile:
  • GBL_DSN_DB2_LOADLIB_V12
  • GBL_DSN_DB2_RUNLIB_V12
• If you are upgrading to OMEGAMON for IMS V5.5.0, OMEGAMON for CICS V5.5.0, and OMEGAMON for z/OS V5.5.0, you must rerun the KCIJPSEC job as part of the upgrade.
  Note: Regarding OMEGAMON for IMS, before you rerun KCIJPSEC job, you must take steps to enable the IMS related modules. For detailed information, see Enabling the IMS version-related modules.
• New jobs are provided in OMEGAMON family version 5.5.0 to delete obsolete elements and runtime members. Consider running the following jobs based on your requirements.
  • The KCIJPW1R job. For staged upgrade planning, use the KCIJPW1R job to delete any obsolete runtime members that are no longer generated by the PARMGEN $PARSE* jobs for the product-specific deprecated functions (CUA-related product runtime members, Epilog-related product runtime members, and other obsolete functions) from the product-execution user libraries for each RTE to upgrade (RKANCMDU, RKANPARU, RKANSAMU, RKD2PAR, RKD2PRF and RKD2SAM), when the product started tasks are not in use.
    Note: You do not have to delete these obsolete runtime members from the product execution user libraries (RK* user) immediately after SMP/E upgrade and reconfiguration of the RTEs pointing to the upgraded SMP/E target datasets. The product started tasks upgraded and loaded with the latest OMEGAMON V5.5 code will continue to run and tolerate the obsolete runtime members. You can continue to use the KCIJPW2R "Copy runtime mbrs from WK*->RK* RW libraries" to refresh the RK* user libraries after an upgrade following either the SMPE04, SMPE05, or SMPE06 upgrade scenario.
  • The standalone KCIDELJB job. A new DELRUN2 step is added to delete obsolete modules from the xKANMOD* load libraries, obsolete Object Definition Information (ODI) files from the RTE's RKANDATV, obsolete panels from the read-only RKANWENU, and obsolete screen space from the read-only RKppPROC profile dataset, once PARMGEN detects that the minimum OMEGAMON version installed is V5.5.0/V7.5.0.

    The new handy standalone KCIDELJB job, which is the equivalent of the BUILDEX*/DELRUN* steps of the composite KCIJPLOD job, is available for staged upgrades. Submit the KCIDELJB standalone job, which deletes obsolete elements in read-only runtime dataset copies of the %GBL_TARGET_HILEV%.TK* SMP/E target datasets. Run this job when the started tasks are not running in order to do the clean-up.

• Some product components are not SDA enabled:
  • OMEGAVIEW for the Enterprise agents
  • Language packs
  • Tivoli Enterprise Portal desktop client.

  Application support for these components must be installed manually.

• The GBL_DSN_GLOBAL_SOURCE_LIB parameter provides the flexibility in accommodating a common dataset that PARMGEN allocates to house globals from products that support KppGLB* global data members. IBM recommends that you use the common globals dataset name. The current default is the RTE-specific %RTE_HILEV%.%RTE_NAME%.RKANPARU dataset for compatibility with OMEGAMON for CICS and OMEGAMON for IMS globals usage, but best practice is to use a common globals dataset that can be shared across different LPAR RTEs. The GBL_DSN_GLOBAL_SOURCE_LIB parameter is available for customization by adding the parameter in WCONFIG($GBL$USR), if your $GBL$USR member existed prior to PARMGEN 2Q15 Interim Feature (APAR OA46817). Otherwise, the parameter is available in both WCONFIG($GBL$IBM) IBM default global profile and in the WCONFIG($GBL$USR) user global profile. To specify a more common global dataset rather than the default dataset value of the RTE's RKANPARU dataset, override the GBL_DSN_GLOBAL_SOURCE_LIB parameter value in WCONFIG($GBL$USR).

• The GBL_USS_TKANJAR_PATH parameter is used to change the TKANJAR DDDEF installation z/OS® UNIX System Services directory. If your $GBL$USR member exists before PARMGEN 1Q16 Interim Feature (APAR OA48678), you must add the GBL_USS_TKANJAR_PATH parameter in WCONFIG($GBL$USR) before you can use it. If your $GBL$USR member is created after you apply PARMGEN 1Q16 Interim Feature (APAR OA48678) or later PARMGEN PTF maintenance, the parameter is available in both WCONFIG($GBL$IBM) IBM default global profile and in the WCONFIG($GBL$USR) user global profile.

  Customize the GBL_USS_TKANJAR_PATH parameter in WCONFIG($GBL$USR), then follow the SMPEnn maintenance scenario to reconfigure your RTE. For more information, see the Maintenance Scenarios (Scenario SMPEnn) on-line help on the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU or SMP/E maintenance and upgrade scenarios.

  If the products that have TKANJAR DDDEF requirement such as OMEGAMON for JVM (HKJJvvv FMID) or OMEGAMON for CICS TG (HKGWvvv FMID) is upgraded, or you are applying SMP/E maintenance to these products that updated the elements in the TKANJAR path, make sure that you rerun the PARMGEN KCIJPUSS job in the RTE_PLIB_HILEV.RTE_NAME.WKANSAMU or RTE_HILEV.RTE_NAME.RKANSAMU dataset. Or you can submit these jobs from the "SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP" KCIP@SUB panel to refresh RTE_USS_RTEDIR/RTE_NAME/kan/bin/IBM/*.jar.

  For more information about this parameter, see GBL_USS_TKANJAR_PATH.

• The KCIJPDLA autodiscovery job integrates with IBM Discovery Library Adapter for z/OS (DLA); DLA requires the SMP/E SMPTLOAD DDDEF statement.
  If you are upgrading from an older version of a product that does not support DLA, make sure that SMPTLOAD is defined in the CSI. Use the following sample job to define the SMPTLOAD DDDEF. Change all occurrences of the following lowercase variables to values suitable to your installation before submitting.

  #globalcsi - The dsname of your global CSI.
  #tzone - The name of the SMP/E target zone.
  #dzone - The name of the SMP/E distribution zone.
  //SMPTLOAD JOB 'ACCOUNT INFORMATION','SMPTLOAD',
  // CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID
  //
  // D e f i n e D D D E F E n t r i e s 
  //
  //SMPTLOAD EXEC PGM=GIMSMP,REGION=496K
  //SMPCSI DD DISP=OLD,DSN=#globalcsi
  //SMPCNTL DD 
  SET BDY(GLOBAL) .
  UCLIN .
  ADD DDDEF(SMPTLOAD) CYL SPACE(2,1) DIR(1)
  UNIT(SYSALLDA) .
  ENDUCL .
  SET BDY(#tzone) .
  UCLIN .
  ADD DDDEF(SMPTLOAD) CYL SPACE(2,1) DIR(1)
  UNIT(SYSALLDA) .
  ENDUCL .
  SET BDY(#dzone) .
  UCLIN .
  ADD DDDEF(SMPTLOAD) CYL SPACE(2,1) DIR(1)
  UNIT(SYSALLDA) .
  ENDUCL .
  /*