PARMLIB Members
Related topics
BMC mainframe products use parameter libraries, or PARMLIBs, to configure each product and common components. BMC Product PARMLIB Member Parameters lists the Release 17.02 PARMLIB Members for all BMC mainframe products and common components. Your product requires a PARMLIB where its members are provided such that you can modify them to fit your site’s requirements.
BMC recommends 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 BMC Mainframe Services Controller (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.
General Guidelines for PARMLIB Members
Parameters used by your BMC mainframe product or component are read from the BMC PARMLIB data set. Edit the sample parameters to your site’s requirements.
General Guidelines
PARM Name | Values | Samples |
---|---|---|
Data columns | 1 to 71 | N/A |
Symbol separator | Underscore | "A_LONG_SYMBOL" |
Continuation | Check for “+” character in Column 72. | + |
Comments | “*” in column 1. | * is a comment |
- If the PARMLIB member includes multiple groups of parameters, for example for the definition of multiple Db2 Subsystem, 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 the following General Guidelines).
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.
General Guidelines for PARMLIB Data set
- The data set can be blocked.
- The data set can have multiple extents.
- The data set must be on a single volume.
- The CMSC must have READ access.
BMC Product PARMLIB Member Parameters
Product PARMLIB | Product |
---|---|
AABD | Abend-AID BDCAS |
AADC | Abend-AID DCAS |
AAFA | Abend-AID Fault Analytics |
AATD | Abend-AID TDCAS |
AAVW | Abend-AID Viewer |
CMSC | BMC AMI Common Mainframe Services Controller |
FACM | File-AID Common Component |
FADA | File-AID/Data Solutions |
FADE | File-AID for Db2 Environment Information |
FAFD | File-AID for Db2 |
FAFR | File-AID/RDX |
FAIE | File-AID for IMS Environment Information |
FAIX | File-AID for IMS |
FAMV | File-AID/MVS |
HCI | BMC AMI Host Communications Interface |
HSCM | Performance Test |
LMCL | BMC AMI License Management Client (LMSINIT) |
LMSV | BMC AMI License Management Server (LMZINIT) |
STR | Strobe |
XCHG | Xchange |
XD$$ | Code Debug CICS Index Member |
XDDB | Code Debug CICS System Facilities and Code Coverage Test components |
XDGB | Code Debug CICS Global components |
XTSO | Code Debug TSO |
XVGB | Code Coverage CICS components |