PARMLIB members

BMC AMI mainframe products use parameter libraries, or PARMLIBs, to configure each product and common components. For a list of the PARMLIB members for all BMC AMI mainframe products and common components in release 17.02, see BMC AMI product PARMLIB member parameters. Your product requires a PARMLIB where its members are provided such that you can modify them to fit your site's requirements, as described in Task 3.2: Implement the BMC PARMLIB.

We recommend using one common data set, but can be concatenation of data set names to store your site's PARMLIB (if applicable) members in a common library. A copy of your product's parameter files must reside in the //CWPARM DD Concatenation of the BMC AMI Common Mainframe Services Controller (CMSC).

The CMSC address space is a centralized facility providing the common parameter library services. It provides two basic functions in relation to parameters: storage and retrieval. The following is a guideline for some of the usage and features of the CMSC:

• Users will modify a human readable PARMLIB member and issue a modify command to the CMSC to store this new set of parameters into a common memory object.
• This common memory object is accessible even if the CMSC is inactive.
• When the CMSC is initialized, all PARMLIB members are loaded into a common memory object.
• The default suffix is 00, but this can be changed in the CMSCnnnn PARMLIB member.

The following topis will give provide information about the general guidelines of PRAMLIB:

General guidelines for PARMLIB members

Parameters used by your BMC AMI mainframe product or component are read from the BMC PARMLIB data set. Edit the sample parameters to your site's requirements.

General guidelines

• If the PARMLIB member includes multiple groups of parameters, for example for the definition of multiple Db2 Subsystems, then only one occurrence of each of the parameters within each group is allowed.
• Line level comments are supported using the /* to start a comment and */ to end the comment. Embedded comments are supported.

System symbolics

The CMSC resolves system symbolics as product parameters which are saved into storage, potentially allowing a single parameter member to be used across multiple LPARs. These symbols are defined by your installation in IEASYMxx. Issue the following display command to display the current symbols:

PARMLIB member naming convention

PPPPnnnn

• PPPP is the product prefix (see BMC AMI product PARMLIB member parameters).
• nnnn is the 1 to 4-character PARMLIB suffix, for example 00.

The PARMLIB member name for each product or product component must start with the product prefix, for example FACM for File-AID Common Components. The 1- to 4-character suffixes can be used to replace the default name (FACM00). If the parameter for a given product is omitted, the default suffix will be 00.

Changing the default PARMLIB member

In the CMSC startup parameters, specify the product parameter, followed by the equal sign, and the 1- to 4-character suffix (for example: FACM=01, which points to PARMLIB member FACM01). If you changed your PARMLIB member name from the default FACM00 to FACM0005, for example, update your CMSC PARMLIB member to point to the new PARMLIB member, FACM=0005.

General guidelines for PARMLIB data set

• The data set can be blocked.
• The data set must be defined as Fixed Block.
• The data set can have multiple extents.
• The data set must be on a single volume.
• The CMSC must have READ access.

BMC AMI product PARMLIB member parameters