How to: Clone customized data from an existing RTE

If you have cloned an existing runtime environment (RTE) or upgraded an RTE by pointing to new libraries, you might have customized data that you want to copy to the new RTE. For example, you might have customized data such as monitoring situations stored in VSAM data sets; OMEGAMON workspace definitions, profiles, and thresholds; or Enhanced 3270 user interface workspace definitions and profiles. This topic explains how to perform this task using PARMGEN.

Before you begin

The following parameters must be customized in the RTE configuration profile before the KCIJPCLN job is submitted:
  • RTE_CLONE_FROM_HLQRTE
  • RTE_CLONE_FROM_VSAM_HLQRTE
If these parameters are not already set to the appropriate values, modify the RTE configuration profile, then resubmit the $PARSESM job before you submit the KCIJPCLN job.

About this task

The KCIJPCLN job copies the following elements from the RTEs identified by the CLONE_FROM parameters:
  • any customized non-VSAM data such as profiles, workspaces, or screenspaces
  • any customized VSAM data such as situations, SDA status data, and managed objects
  • customized globals
  • customized security modules and exits
  • sequential data
Run this job before you bring up your started tasks.

Procedure

  1. Enter UTIL on the command line of the Workflow panel.
    The Utilities panel is displayed.
  2. Select Clone customized data from another RTE. (option 29).
    The KCIJPCLN JCL is displayed.
  3. Edit the job for other RTEs as needed and review the job for certain product restrictions.
  4. Submit the job.
  5. Bring up your started tasks.