Your site can have several parameter libraries, including a distributed version and one or more site-customized versions.
Multiple parameter library data sets can be concatenated together. For example, a site parameter library can be created and a data set that is customized for each PAS can be concatenated before the site library.
Some parameter library members support the substitution of system variables.
During the installation and customization process, you select whether to use runtime libraries or SMP/E libraries. If you use runtime libraries, your customized library names will start with BMC. If you use SMP/E libraries, your customized library names will start with BB, UBB, or TOSZ. A few library names start with IBB or SBB for runtime or SMP/E libraries.
Throughout the MainView documentation, the BB*, UBB*, and TOSZ* data set names are used even if the actual library names start with BMC*.
For more information, see the following sections in this topic:
BBPARM is a distributed target library that is created during product installation.
This version of the parameter library should never be modified. Subsequent SMP maintenance will overwrite any changes that you make. The distributed name is used in this guide for reference only.
UBBPARM contains copies of members from the BBPARM distributed parameter library. This customized library is created automatically by MainView Customization, or you can create it manually.
Use the UBBPARM data set to make any parameter library changes that are described in this guide.
MainView Customization creates a UBBPARM data set as hlq.image.UBBPARM (for example, hlq.IMAGSYSD.UBBPARM). This method allows each system image to have its own BBPARM data set for unique parameters.
A single UBBPARM data set, however, can be shared among multiple systems. BMC recommends sharing a single UBBPARM when unique parameters are not required.
Customized IMS parameters
You can define unique parameters for individual IMS systems, either by copying and renaming specific members and including them in UBBPARM or by creating user-defined parameter data sets (referred to as IBBPARM data sets).
This topic applies to the following products only:
MainView AutoOPERATOR for IMS
MainView for DBCTL
MainView for IMS Online
MainView for IMS Offline
For more information about customizing parameters for individual IMS systems, see the product-specific customization guides.
Customized IMFSYS00, IMFECP00, and AAOPRM00 members
In the UBBPARM data set, you can include a copied, renamed version of IMFSYS00 to customize the system parameters for an IMS system, including the SUBSYS parameter, which establishes communication between the IMS system and the BBI-SS PAS. The name of an IMS-specific system parameter member must be in the following format:
imsidSYS (where imsid is the four-character IMS system identifier)
You can also include a copied, renamed version of IMFECP00 to customize the Event Collector parameters for an IMS system. The name of an IMS-specific Event Collector parameter member must be in the following format:
You can include an AAOPRMxx member by using the AAOPRM parameter in the IMFSYS00 (or imsidSYS) member to specify the suffix.
If you do not need to customize other UBBPARM members for an IMS system, you do not need to create and allocate a separate IBBPARM parameter data set for that system.
User-defined parameter data set
You can allocate an IBBPARM parameter data set to contain any members that you want to make unique to an IMS system.
If you do not need to customize any parameter members other than IMFSYS00, IMFECP00, or AAOPRM00 for an IMS system, an IBBPARM data set is not required. Instead, you can include renamed versions of the members in UBBPARM, as described in Customized IMFSYS00, IMFECP00, and AAOPRM00 members.