Security parameter library
The default definitions are distributed as members in the BBACTDEF library. When you customize parameter, class and resource definitions, the customized definitions are saved in the security parameter library, which is referenced by the BBSECURE DD statement in the CAS and PAS started task procedures. BBSECURE members are read during CAS and PAS initialization to establish security.
The BBSECURE security parameter library is created for you during MainView Customization. If you did not use MainView Customization and want to customize security definitions, you must create a BBSECURE library and define it in the CAS and PAS started task procedures, as described in Customizing after installation.
The BBSECURE security parameter library always contains the following members:
Resource definitions for Plex Manager
Class definitions for each known resource class
Parameter definitions that specify the ESM and its attributes
Resource definitions for resources that are common to all MainView 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 MainView products are installed, the BBSECURE security parameter library might also contain one or more of the following resource definition members:
MainView SYSPROG Services
CMF MONITOR and MainView for z/OS
MainView for IMS Online and MainView for DBCTL
MainView Alarm Manager (version 2.1)
MainView for CICS
MainView for DB2
MainView for MQ
MainView for UNIX System Services
Intelligent Capping for zEnterprise (iCap)
MainView Total Object Manager
MainView for Linux - Servers
MainView Transaction Analyzer
MainView for WebSphere Application Server
MainView for VTAM
MainView Storage Resource Manager (SRM)
MainView 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