Configuring Near-Term History with system variable support

You can configure Near-Term History in an RTE that is enabled for system variable support.

Before you begin

Before you begin, you need an RTE having OMEGAMON® for Db2 PE already configured and system variable support enabled.

Procedure

  1. Start the Configuration and Installation Tools user interface by issuing the command ex on the TKANCUS library in your SMP/E installation.
    ex ‘&trghlq.TKANCUS’
  2. Use option 3 Configuration Workflow to open the PARMGEN workflow user interface.
  3. Enable your existing RTE that has been already enabled for system variable support.
  4. Use option 2 to open the PARMGEN profile selection menu.
  5. Use option 1 to open the RTE LPAR configuration profile.
  6. Enable Near-Term History for those profiles that you use for monitoring your DB2 subsystems by setting parameter KD2_PFnn_HIS_START to Y. nn is the profile ID.
    Previously, with the Configuration Tool, you had to enable system variable support for Near-Term History separately on the panel KD261PI Global Control Parameters. This prevented the use of %DB% and %SY% in the Near-Term History data sets. This limitation no longer exists. In addition, you do not have to enable system variable support for Near-Term History separately.
  7. Use PF3 to get back to the main workflow panel KCIPQPGB.
  8. Use option 3 to open the $PARSE job panel KCIP@PR1.
  9. Use option 1 to open the composite $PARSE job and submit it. The expected return code is zero.
  10. Use PF3 twice to get back to the main workflow panel KCIPQPGB.
  11. Use option 4 to open the SUBMIT job panel KCIP@SUB.
  12. Use option 5 to open the KCIJVUPV job that regenerates the Near-Term History configuration and submit it.
    The expected return code is zero.
  13. Use option 12 to open the KCIJPW2R deployment job and submit it.
    The expected return code is zero.