Enable override embed members when creating an RTE

Use this procedure to enable override embed members when creating a runtime environment (RTE).

Before you begin

Read Using override embed members in Configuration Manager.

This task applies to creating an RTE using the Monitoring Configuration Manager CREATE or MIGRATE action. For more information, see Creating your first, minimal runtime environment.

About this task

Override embed members can be used to specify user-defined parameters and values that might otherwise be overwritten by the GENERATE action when maintenance or upgrades are performed, or to override existing values. Using override embed members for your runtime environment requires a data set (the embeds data set) that contains the override embed parameters and values.

You can enable the use of override embed members when creating your RTE by including the KFJ_USE_EMBEDS parameter set to Y in the KCIVARS DD statement for the CREATE or MIGRATE actions. With the inclusion of this setting, Monitoring Configuration Manager creates the embeds data set, populates the override embed parameters and values, and defines the data set to the RTE using the RTE_X_OVERRIDE_EMBEDS_LIB parameter.

For the CREATE action, by default, the embeds data set is populated with the override embed parameters and values for the products that are installed in the respective CSI used to build the RTE. For the MIGRATE action, this library will contain the embed parameters and values from the source PARMGEN installation (as specified by parameter KFJ_MIGRATE_WCONFIG).

The default embeds data set name is rte_plib_hilev.rte_name.EMBEDS. Optionally, you can include the KFJ_EMBEDS_LIB parameter to use a custom data set name rather than the default name. Use of this parameter allows you to use the same embeds data set and settings for multiple RTEs.
Note: If you specify the name of an existing data set using parameter KFJ_EMBEDS_LIB, its contents will not be overwritten.

Procedure

  1. As part of the process to create an RTE, submit a job that performs the CREATE action or MIGRATE action with KFJ_USE_EMBEDS set to Y and, optionally, KFJ_EMBEDS_LIB set to a custom data set name.

    Example JCL:

    Figure 1. Example JCL to enable override embed members for a new RTE. 
    //UID#ZMCM JOB ,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
/*JOBPARM SYSAFF=<lpar>
//S1       EXEC PGM=KCIOMEGA,REGION=0M,DYNAMNBR=256
//STEPLIB  DD DISP=SHR,DSN=<tlib_hlq>.TKANMOD
//KCIFLOW  DD DISP=SHR,DSN=<tlib_hlq>.TKANCUS(KFJOMEGA)
//KCIVARS  DD *                                        
ACTION            CREATE | MIGRATE
RTE_NAME          <rte_name>
RTE_PLIB_HILEV    <rte_plib_hilev>
...
KFJ_USE_EMBEDS    Y                         * Y|N valid values
KFJ_EMBEDS_LIB    <embeds_data_set_name>    * override default EMBEDs library
/*

    Where <rte_name> and <rte_plib_hilev> specify the RTE, and <embeds_data_set_name> is the optional custom embeds data set name.

  2. Complete the creation of the RTE. For more information, see Creating or updating a runtime environment.
  3. Update the override embed members as needed.

Results

Monitoring Configuration Manager sets up the embeds data set, populates it with supported override embed parameters (if applicable), and defines it to the RTE using the RTE_X_OVERRIDE_EMBEDS_LIB parameter.