Runtime members
The GENERATE action generates runtime members in locations (MVS™ data set names and z/OS® UNIX® System Services paths) that are specified by parameters.
Runtime member locations
MVS data sets:
- rte_hilev.rte_name.RK*
- rte_hilev.rte_name.ssid.RK*
- rte_vsam_hilev.rte_name.RK*
- rte_vsam_hilev.rte_name.ssid.RK*
- gbl_dsn_sys1_proclib
- gbl_dsn_sys1_vtamlib
- gbl_dsn_sys1_vtamlst
z/OS UNIX directory paths:
- rte_uss_dir/rte_name/*
where:
- ssid is the identifier of a subsystem to be monitored, such as a Db2® subsystem or an IMS subsystem
- Other identifiers in italics represent parameter values
Parameters that specify runtime member locations
- RTE_HILEV
- High-level qualifiers of non-VSAM data sets.
- RTE_VSAM_HILEV
- High-level qualifiers of VSAM data sets.
RTE_HILEV and RTE_VSAM_HILEV have the same default value: rte_plib_hilev
- GBL_DSN_SYS1_PROCLIB
- GBL_DSN_SYS1_VTAMLIB
- GBL_DSN_SYS1_VTAMLST
- The data set names where the GENERATE action writes members intended for your
system libraries.
Default values:
- rte_hilev.SYS1.PROCLIB
- rte_hilev.SYS1.VTAMLIB
- rte_hilev.SYS1.VTAMLST
You must use your own site-specific procedures to copy the members from these locations to your actual PROCLIB, VTAMLIB, and VTAMLST system libraries.
- RTE_USS_RTEDIR
- z/OS UNIX directory. Default value: /var/rtehome
- RTE_NAME
- The runtime environment name is appended to RTE_HILEV and RTE_VSAM_HILEV as a low-level qualifier and to RTE_USS_RTEDIR as a directory name.
The following diagram illustrates the relationships between parameters and runtime member locations:
Tip: Monitoring Configuration Manager writes concise started tasks to:
- rte_hilev.SYS1.PROCLIB
and versions with verbose comments to the same location used by PARMGEN:
- rte_plib_hilev.rte_name.RKANSAMU
- rte_plib_hilev.rte_name.RKD2SAM (for Db2)