GENERATE
The GENERATE action generates runtime members for a runtime environment from a set of configured parameters.
Before you begin
Before performing a GENERATE action for an existing runtime environment, stop the started tasks for that runtime environment. Started tasks can lock runtime members, such as persistent data store data sets. Locked runtime members can cause the GENERATE action to fail.
About this task
With the GENERATE action, you can generate the runtime members and started tasks for your runtime environment.
- The GENERATE action generates runtime members from the parameters in the runtime environment definition library, rte_plib_hilev.RTEDEF. The GENERATE action builds the set of parameters that is used by concatenating the corresponding RTEDEF library members.
- Run the GENERATE action on the LPAR where you will start the runtime environment. For example, if your site uses JES2, insert a SYSAFF job parameter after the JOB statement to ensure that the job runs on that LPAR.
- If the RTEDEF library contains LPAR-specific members, then the
GENERATE action uses the LPAR-specific members for the LPAR where the
GENERATE action is running. For example, consider the RTEDEF
library that contains the following members:
- KDS$PARM
- KDS$ZOS1
- KDS$ZOS2
If you run the GENERATE action on LPAR ZOS1, then the GENERATE action uses the non-LPAR-specific member KDS$PARM and the LPAR-specific member KDS$ZOS1, but not the LPAR-specific member KDS$ZOS2.
- Specify KFJ_LOCAL_PLIB_HILEV in the KCIVARS
DD, along with KFJ_SYSNAME, if you want to generate a runtime
environment that will be deployed using a different local high-level qualifier. If you decide to use different settings for the local generation of the runtime environment, there are certain limitations in terms of parameters that can be customized. The following parameters are not allowed in the respective RTEDEF members:
- KYN_XAI0_SUBAGENT_PRODHOME
- KQI_HFS_HFSROOT_DIR1
- KS3_APP_ZFS_DIR
- KM2_HIST_DSTOR_RKM2EDS_DSNx (where x is 1 to 7)
- GBL_USER_JCL
- KD2_OMPE_DSHLQ
- KD2_OMPE_VSAM_DSHLQ
If any of these parameters are explicitly specified in the RTEDEF members, message KFJ00213E is returned in KCIPRINT and the workflow stops. To continue, remove these parameters from the RTEDEF data set members and re-run the GENERATE action.
- You can use the OPTION parameter for the GENERATE action to control certain processing. For information about the available options, see GENERATE options.
- After you run the GENERATE action, you can review a list of the members that
were not replaced when the work (WK*) libraries were copied to the runtime
(RK*) libraries due to having been defined in an exclude list. The list of
members is provided in the exclude report, which is identified by the EXCLRPT
DD statement. The exclude report is generated only for the GENERATE action
without any options specified, or with only OPTION NOUSS or OPTION
QUICKCONFIG specified.
For more information, see Members excluded during GENERATE action.
Procedure
Example
The following JCL generates runtime members for the runtime environment that is defined by members of the TSOUID.MONSUITE.RTEDEF library, including RTE1 and LPAR-specific configuration profile members such as Kpp$ZOS1.
Note the JES2 SYSAFF parameter that causes the job to run on LPAR ZOS1.