Cloning an SMP/E environment for a staged upgrade of existing runtime environments

Cloning an environment and installing new versions into the cloned environment makes it possible for you to stage your upgrade. You can continue to apply maintenance to and reconfigure runtime environments that have not yet been upgraded as you gradually upgrade others.

About this task

In this scenario, you use JOBGEN to install new versions into a new set of SMP/E libraries. Then, you upgrade runtime environments one by one by pointing them to the updated libraries in the cloned environment and making any configuration changes required to upgrade them.
Note: This scenario assumes a PARMGEN to PARMGEN upgrade.

Procedure

  1. Install the products into a new set of SMP/E target libraries using the Install Job Generator (JOBGEN).
    1. Launch the installation and configuration software in an existing installation: 
      EX '%GBL_TARGET_HILEV%.TKANCUS'
    2. On the Welcome page, select option 2 (SMP/E-install z/OS® products with Install Job Generator).
    3. Supply the values as prompted.
    4. Submit the file-tailored KCIJG* SMP/E jobs to complete the installation.
    5. Exit JOBGEN and then exit the software configuration software.
  2. Modify each runtime environment in the new CSI to point to the new target libraries and high-level qualifiers.
    1. Invoke the configuration software from TKANCUS of the new environment and select option 3 (Configuration Workflow).
    2. Set the GBL_USER_JCL and RTE_PLIB_HILEV fields to the new values for the cloned GBL_USER_JCL. For RTE_NAME, specify the name of the runtime environment you want to clone and upgrade, then press Enter.

      For RTE_PLIB_HILEV, use a different value for the high-level qualifier, not the one in production (for example, change OMEG623.%USER_ID% to OMEG630.%USER_ID%), so the new runtime environment uses a different set of PARMGEN IK*, WCONFIG, and WK* work libraries.

    3. Select option 1 (Set up PARMGEN work environment for an RTE).
      • On the first set-up panel, provide the library and LPAR profile member name for the runtime environment you are cloning (for example, OMEG623.%USER_ID%.PLBLPAR1.WCONFIG(PLBLPAR1).
      • On the second set-up panel, specify the new GBL_TARGET_HILEV.
      • On the third set-up panel, you should not need to make any changes if you want an exact clone of the existing environment. However, any changes you make on this panel will be reflected in the corresponding parameters in the RTE configuration profile.
      • On the fourth set-up panel, all the products installed in the new CSI are selected. The products already configured in the RTE that is being cloned are marked with an asterisk. Deselect any products that you do not want to configure in this RTE, then specify Y in the Confirm ==> field and press Enter. The latest versions of the products installed are configured into new runtime environment.
      • When prompted, provide a name for the backed up RTE profile and press Enter.
    4. Review and submit the KCIJPCFG job, then return to the main Workflow panel.

What to do next

Complete the remaining steps as appropriate for your upgrade scenario:
  • If the new FMIDs introduce no configuration changes, only the KCIJcLOD job is required, to copy the target libraries to the RK* runtime libraries.

    See Scenario SMPE04: Upgrading an existing runtime environment with no configuration changes for detailed instructions.

  • If the new FMID contain new components or configuration parameters and you want to implement the changes using IBM-supplied configuration defaults, the following jobs must be resubmitted:
    • The $PARSE or $PARSESV job to recreate the runtime members and jobs
    • The following jobs, as indicated:
      • KCIJPLOD to copy the target libraries to the RK* runtime libraries
      • KCIJPSEC (if upgrade introduces changes in security) to create security-related members (load modules, encryption key, and other elements) based on the product security requirements
      • KCIJPUSP and KCIJPUSS (if upgrade introduces changes in z/OS UNIX System Services requirements)
      • KCIJPSYS (if upgrade introduces new started tasks or nodes)
      • KCIJPCPR to backup RK* production user runtime libraries job
      • KCIJPW2R to copy the WK* work libraries to the RK* production libraries
    See Scenario SMPE05: Upgrading an existing runtime environment with configuration changes but using IBM-supplied configuration defaults for detailed instructions for submitting these jobs.
  • To customize new components or parameters, edit the configuration profiles, and then submit the jobs listed in the previous bullet.

    See Scenario SMPE06: Upgrading an existing runtime environment and overriding defaults for detailed instructions.