Naming conventions

BMC uses naming conventions that reflect product-line organization while allowing for future expansion. BMC also classifies machine-readable data that is used during installation as product installation or product-specific information. 

FMID naming conventions

BMC uses the following naming convention for function modification identifiers (FMIDs) of Zpppvrx. For example, ZPWD330 is the FMID for version 3.3 of the Product Authorization utility.

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, release 11; and A1 indicates version 10, release 1.

x

Unique identifier for products or components that use multiple FMIDs

SYSMOD, PTF, and APAR naming conventions

BMC classifies 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

Installation images naming conventions

For the installation images, BMC uses naming conventions that identify the product and version of the image.

Image type

Syntax

Variable

Description

Installation System and product

bmcprd-vnnnn-xxx-image.bin

Installation System images and product prd

Product code

nnnn

Version number

xxx

Image type

Enhanced HOLDDATA

bmcehd.timePeriod.bin

timePeriod

Time period that the Enhanced HOLDDATA encompasses

RSL

RSLyymmq

yy

Last two digits of the calendar year

mm

Month

q

Blank for a quarterly RSL

C for a cumulative RSL

Product distribution files naming conventions

BMC uses 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 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

Note: 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 naming conventions

The Installation System creates different runtime libraries based on the options you choose during installation. For a list of the libraries created by the Installation System, see Library names.

The Installation System can create the following types of libraries:

Library typeDescription

Runtime libraries

Runtime libraries use one of the following conventions as specified by you (for more information about LLQs, see Specifying runtime data set information:

  • 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 MainView and some performance products
    • DB for BMC products for IBM DB2
    • IM for BMC products for IBM IMS
    • XX for Infrastructure components
  • LLQs are specified by you

User libraries
(which use a qualifier of UBMC)
User libraries contain configuration information.




Was this page helpful? Yes No Submitting... Thank you

Comments