Naming convention for runtime environment data sets

Edit online

Before you begin configuring runtime environments, you should understand the convention for naming the data sets in the runtime libraries.

Each data set in a runtime library has a name composed of the following parts:

Table 1. Runtime environment data set naming convention
Part of the name	Length
High-level qualifier, VSAM or non-VSAM	26 bytes
Mid-level qualifier, which identifies the runtime environment	8 bytes
Low-level qualifier, which identifies the data set and usually matches the DDNAME	8 bytes

You set the high-level qualifiers for VSAM and non-VSAM data sets and the mid-level qualifier when you create a runtime environment. The low-level qualifier for each data set is provided by the configuration software and has the format

cKppffff

where

c is the data set class:
- D for installation distribution libraries (DLIBs).
- T for target libraries (TLIBs) that were installed by SMP/E.
- R for runtime libraries.
pp is the 2-character code for the product or component.
ffff identifies the function of the data set; U as the final character identifies the data set as a user library. (Examples: CMD or CMDU for a commands data set, PAR or PARU for a parameters data set, and SAM or SAMU for a samples data set.)

For example, the data set IBM.RHILEV1.RTENAME1.RKANPARU has the high-level qualifier IBM.RHILEV1, the mid-level qualifier RTENAME1, and the low-level qualifier RKANPARU (which identifies the data set as a user library containing parameters for the component AN, the conglomerate component for the entire combination of products and components in the runtime environment).