Naming Conventions
BMC Software, Inc., Confidential and Proprietary Information
Chapter 3 Performing Additional Installation Tasks 3-25
Table 3-10 indicates what the variables represent, and Table 3-11 shows
examples of plan names.
Note: The access type for CATALOG MANAGER 3.3 or later must be
direct (D). CATALOG MANAGER 3.3 or later is designed to use a
single DOPTs module for both direct and indirect access. Because
the plan names are communicated to the products through the
DOPTs module, CATALOG MANAGER is the only Administrative
Product that requires only a single set of plans for both direct access
and indirect access.
Collection Names
Collection names have the following conventions:
• prdvrmc_y_MAIN (ALTER and CHANGE MANAGER)
• prdvrm_y_#_MAIN (CATALOG MANAGER)
• prdvrm_y_MAIN (DASD MANAGER PLUS)
Table 3-10 Plan Name Variables
Variable Represents
prd or pp
product code
vrm
version/release/maintenance level
c
indicates the exploited DB2 version
(B=3.1, C=4.1, D=5.1, and E=6.1 or later)
y
access type (D=direct, I=indirect)
z
plans function
Table 3-11 Examples of Plan Names
Example Description
AL621EDF ALTER 6.2.01 DB2 Version 6 direct access Front End plan
AL621EIF ALTER 6.2.01 DB2 Version 6 indirect access Front End
plan
ASU613DD DASD MANAGER PLUS 6.1.03 direct access Object
Definition plan
