Best Practice Implementation › How to Perform the Best Practice Implementation › BPI Software Inventory Lifecycle › Data Set Naming Conventions

Data Set Naming Conventions

Having standard naming conventions within various components of CA Endevor SCM makes the product easier to support. The Best Practices Implementation (BPI) method includes standard data set naming conventions.

Previously if you were not using the BPI method, CA Endevor SCM used two sets of high and second level qualifiers for data set naming (iprfx.iqual and uprfx.uqual). The first set was reserved for the CA Endevor SCM installation runtime data sets. These data sets were prompted for during the installation process (job BC1JJB03). The second set was used as the prefix for all the CA Endevor SCM data sets that were created (element catalog, MCFs, package file, base and delta files, processor output libraries, and so on).

When you configure CA Endevor SCM using the BPI, you must specify four high level qualifiers for the CA Endevor SCM data sets. The installation runtime qualifier (iprfx.iqual) remains the same. The remaining three high level qualifiers are specified in the BPI Option member. Having these multiple high level qualifiers makes it easier for administrators to establish and maintain security rules, as well as provide a visual distinction between the data sets. The three prefixes are as follows:

• SiteHighLevelQual for all CA Endevor SCM site-wide data sets. This includes element catalog and index, ACM root and cross reference files, package file and Master Control files.
• AdminHighLevelQual for all CA Endevor SCM ADMIN environment data sets. This includes all allocations for the ADMIN environment.
• ApplHighLevelQual for all CA Endevor SCM application data sets. This includes the base and delta files for each of the standard application system, subsystem, and type combinations.

The maximum size for a data set name cannot exceed 44 characters, thus the maximum sizes allowed for the three high-level qualifiers will depend on the system and subsystem names. You can use multiple nodes within each high-level qualifier. The number of nodes is not important. However, the CA Endevor SCM data set names use a standard format consisting of the following, where the maximum number of characters allowed are shown in parenthesis: system (8), subsystem (8), subset of the environment name (3), stage number (1) and type (8). Using this standard, if you use the maximum amount of characters for system, subsystem, and so on, then only 12 characters are left for the high-level qualifier nodes. We recommend that the prefix nodes be 12 characters or fewer, if possible. This is to avoid data set length problems in the future if additional systems, subsystems, and types are created.