General naming conventions used in beta release

We use naming conventions for FMIDs, SYSMOD, PTF, product distribution files, runtime libraries, and PSI deployments.

Use this topic to understand the basic naming conventions. 


Related topics

Getting-started

FMIDs

For function modification identifiers (FMIDs), we use the following naming convention:

Zpppvrx

Digit

Explanation

Z

Indicates BMC Software

ppp

Product or component identifier

vr

Version and release of a product or component

Numbers 00 to 09 are represented as 0 to 9, and numbers 10 to 35 are represented as A to Z.

For example, 1B indicates version 1 and release 11.

x

Unique identifier for products or components that use multiple FMIDs

SYSMOD, PTF, and APAR

We classify system modifications (SYSMODs) by product line and type. Each SYSMOD name uses the format BTPFV or BTPnnnn:

Digit

Explanation

B

Indicates BMC Software (for APARs and PTFs)

T

SYSMOD type:

  • A or C indicates an APAR.
    For example, BAB0001 or BCI0002.
  • P or Q indicates a PTF.
    For example, BPB0123 or BQI0456. 

P

An identifier that groups products by product line

F

A two-character identifier that is used only for a function SYSMOD

V

A two-digit version number that is used only for a function SYSMOD

N

An APAR or PTF number within a product line

Product distribution files

We use naming conventions for product distribution files to prevent conflicts between system and product data sets.

The following naming conventions apply to the installation data sets:

Name variable for a product data set

Description

Example

targetLibraryName

Target library ddname or DDDEF name

BMC.V2400.ESD6.DBLINK

distributionLibraryName

Distribution or maintenance library ddname or DDDEF name

BMC.V2400.ESD6.ADBLINK

runtimeLibraryName

Runtime library data set name

BMC.V2400.RTE6.BMCLINK

function

Function name

ZAUP221

prdRelease

Three-letter product code and release number

SPD2200

Important

Release numbers can include a combination of one-digit or two-digit version, release, and modification levels. For example, 2200 means version 2.2.00 (version 2, release 2, no maintenance).

Runtime libraries

The following types of libraries are created:

Library type

Description

Runtime libraries

Runtime libraries use one of the following conventions that you specify:

  • BMC*

    All LLQs begin with BMC, followed by the type of library (such as LINK, SAMP, or PLIB). This is the recommended default naming convention.

  • Product-line designators

    LLQs begin with one of the following designators, followed by the library type:

    • BB for BMC AMI Ops and some performance products
    • DB for BMC products for IBM Db2
    • IM for BMC products for IBM IMS
    • XX for Infrastructure components
  • LLQs that you specify 

User libraries
(User libraries use a qualifier of UBMC)

User libraries contain configuration information.

Software instances and deployments 

We recommend the following naming conventions for software instances and deployments:

Product family 

Example

Description

BMC AMI Ops



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*