Override embed members

A PARMGEN configuration creates a set of files that get embedded in a number of the most commonly updated runtime members in the user libraries. These embed files can be used to add new user-defined parameters that might otherwise be overwritten when maintenance or upgrades are performed, or to override existing values.

The embed files include the following members:

  • Kpp$C*,
  • Kpp$P* and Kpp@P*
  • Kpp$S*
  • KCI$XW2R

where * represents either ENV, SYSIN, or started_task_name. The embed members are copied from the IK* interim staging libraries to the corresponding WCONFIG PARMLIB control library by the KCIJPUP1 (Refresh IK* templates/WCONFIG *$IBM profiles) job, or the KCIJPPRF profile refresh job which is equivalent to the KCIJPUP1 job except the user LPAR RTE profile is refreshed automatically. These members are then embedded into the appropriate members (such as started tasks and profiles) by the $PARSE or $PARSESV job. For a list of embed files, the library in which the affected member is located, and the purpose of the embed file, see Customizing the override embed members.

To enable the embed parameters, complete the following steps.
  • For an existing Run Time Environment (RTE):
    1. Edit %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(&imbed_name) referenced by the enabling product PTF or new product version. Modify the parameter accordingly before rerunning the WCONFIG($PARSE) job.
      Note: The new default parameter is typically introduced in a PARMGEN APAR maintenance. For existing RTEs created before the PARMGEN APAR that introduced the new parameter, the WCONFIG(&imbed_name) already exists. To enable the function, add the new override parameter to WCONFIG(&imbed_name).
    2. Submit WCONFIG($PARSEPR) job to recreate the RTE's %RTE_PLIB_HILEV%.%RTE_NAME%.WKANPARU(&runtime_member) where the &imbed_name is imbedded.
    3. Submit WKANSAMU(KCIJPW2R) job to refresh the &runtime_member from the PARMGEN work dataset (WKANPARU for example) to the corresponding product execution user library (RKANPARU for example) when you are ready to stage your runtime member updates.
    4. Recycle the product started task.
    5. Repeat step 1 to step 4 for additional RTEs that will enable the function.
  • For a new Run Time Environment (RTE):
    1. Follow the preferred RTE Implementation Scenario documented in Implementation scenarios.
    2. As part of the "Customizing the configuration profiles" step, edit %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(&imbed_name) that will override the WKANPARU(&runtime_member). Modify the parameter accordingly before rerunning the WCONFIG($PARSE) job.
    3. Complete the remaining steps as documented in the RTE Implementation Scenario.

To preserve these customizations, embed files are not overlaid during maintenance or upgrades. To refresh the files, you must rename them. Then, after the new files have been created, you can merge back in any customizations you have made from the backed up version.

Edit the embed files before you run the $PARSE (or $PARSESV) job. You can edit the files using the PARMGEN Workflow interface. Select option 4 on the Customize PARMGEN Profile Members panel, or enter UTIL on the command line of any Workflow panel to access the Utilities panel and select the WCONFIG library (option 7). After you customize the files, you can copy the tailored versions from one runtime environment to another. You can use the KCIJPCCF utility job to copy them.

The OLDWCNFG DDNAME in the KCIJPCCF job can be edited to copy the imbeds from either another RTE's WCONFIG dataset, or the PARMGEN IK* template datasets. Consider the following conditions before submitting the $PARSE job.
  • WCONFIG override imbeds are preserved. When a PARMGEN Interim Feature (IF) PTF updates an imbed, the PTF calls what has changed via the Updated WCONFIG(Kpp$*) Override Imbeds section in the attachment of the What's New in PARMGEN IF in the PARMGEN technote.
  • Review the deltas and implement the changes accordingly if you want to exploit the changes. You can rename the WCONFIG(Kpp$*) imbed prior to resubmitting the KCIJPPRF or KCIJPUP1 job if you want to refresh your copy. Note that these members are typically preserved so KCIJPPRF or KCIJPUP1 job will not update your WCONFIG(Kpp$*) user copy if the imbed already exists in WCONFIG library. Merge back your original customizations accordingly into the refreshed WCONFIG override imbed.
  • Kpp$* refresh considerations:
    • KCIJPPRF profile refresh job is rebuilt by the KCIJPCFG if you provide a backup LPAR RTE profile name.
    • The quickest way to find deltas is to compare your original WCONFIG imbed (backup copy) with the refreshed version or with the copy in the respective PARMGEN IK* library. For example, if an imbed is called WCONFIG(Kpp$PENV), this imbed is processed by the $PARSE job into the WKANPARU(KppENV) runtime member. It means that the IBM default version of Kpp$PENV is in the PARMGEN IKANPARU library. The preserved user copy is in your WCONFIG(Kpp$PENV).
    • If you want to move the Kpp$* imbeds out of the WCONFIG dataset into a new backup dataset, you can use the KCIRMVCP macro. See KCIRMVCP move/copy/allocate macro and KCIPCPY* panels help topic for more information. Once the imbeds are removed from the WCONFIG dataset, the KCIJPUP1 or KCIJPPRF job will copy the latest versions of the imbeds from the PARMGEN IK* template datasets to the RTE's WCONFIG dataset.

Individual products may include their own embed members. See the product configuration documentation for more information.