Security parameter library
The BBSECURE security parameter library always contains the following members:
Member | Description |
|---|---|
BBMTRN nn | Resource definitions for Plex Manager |
BBMTSP nn | Class definitions for each known resource class |
BBMTSS nn | Parameter definitions that specify the ESM and its attributes |
BBMZRN nn | Resource definitions for resources that are common to all BMC AMI Ops products |
The nn variable is the two-character member name suffix. The default suffix is 00. The suffix enables you to create different versions of each member. The suffixes for the parameter, class, and common resource definition members are associated to a CAS in the CASDEF view. The member suffix for product resource definitions is associated to a PAS in the TGTDEFD view.
Depending on which BMC AMI Ops products are installed, the BBSECURE security parameter library might also contain one or more of the following resource definition members:
Member | Product |
|---|---|
AAOTRN nn | BMC AMI Ops Automation |
ASTTRN nn | BMC AMI Ops SYSPROG Services |
BBDTRN nn | BMC AMI Ops Monitor for CMF and BMC AMI Ops Monitor for z/OS |
BBFTRN nn | BMC AMI Ops Monitor for IMS Online and BMC AMI Ops Monitor for DBCTL |
BBHTRN nn | Alarm Management |
BBJTRN nn | MainView VistaPoint |
BBKTRN nn | BMC AMI Ops Monitor for CICS |
BBPTRN nn | BMC AMI Ops Monitor for Db2 |
BBSTRN nn | BMC AMI Ops Monitor for MQ |
BBUTRN nn | BMC AMI Ops Monitor for UNIX System Services |
BBWTRN nn | MainView Explorer |
DYCTRN nn | BMC AMI Ops Automation for Capping (iCap) |
MAMTRN nn | Total Object Manager |
MTMTRN nn | MainView Transaction Analyzer |
SOPTRN nn | MainView for VTAM |
SV0TRN nn | BMC AMI Storage |
TACTRN nn | BMC AMI Ops Monitor for IP |
Share a security parameter library between CASs
If you have a shared DASD environment, CASs that have the same security requirements can share a security parameter library by referencing the same library on the BBSECURE DD statement in each CAS started task procedure.
This option eliminates the need to create or maintain separate security parameter libraries for each CAS.
If your CASs have different security requirements, you can still share a security parameter library; however, you must:
- Create the appropriate security parameter, class, and resource definition members with different member name suffixes
- Use the CASDEF view to associate each CAS to the appropriate member suffixes