The BBXS Subsystem is automatically initialized by the first BMC product that needs to use it. There is no requirement to initialize it or even define it in the IEFSSNxx PARMLIB member. All other address space that make use of the BBXS Subsystem will then use the one created automatically.
If you need to reinitialize the BBXS Subsystem (after applying maintenance or on the recommendation of BMC Support) the BBXSINIT program has been provided.
BMC ships a sample started task procedure for BBXS initialization in the prefix.BBSAMP data set.
During customization, the @BBXINIT member is copied to a library that you specify and renamed to BBXSINIT. This procedure runs the BBXSINIT program that initializes or reinitializes the BBXS subsystem.
BMC recommends that you use the BBXSINIT procedure early in the IPL process or after applying maintenance to BBXS.
Except in places where the @BBXINIT procedure is specifically mentioned, the remainder of this appendix uses the term BBXSINIT interchangeably to refer to both the program and the procedure that executes the program. After BBXS is initialized, routines and shared data areas loaded into CSA memory remain there until the next IPL.
The BBXSINIT program, as the name implies, creates new copies of the BBXS modules and data areas in CSA and initializes all ongoing BBXS processes, such as channel and device data collection. Any new product startups or product restarts use the new BBXS code and data areas. CSA used by a previous initialization of BBXS is not released until an IPL occurs.
Do not run the BBXSINIT program as part of another startup procedure. If the other procedure needs to run more than once between IPLs, BBXS is reinitialized and claims more valuable CSA space.
Reinitialization of BBXS is required so that changes to CSA-resident BBXS modules become effective and dynamically loaded modules match the version of the CSA-resident modules. The reinitialized version of BBXS works with all versions of BMC products because BBXS is downwardly compatible.
BMC recommends that you recycle all products that use BBXS after the BBXS subsystem is reinitialized so that the new BBXS code is used by all applications.
The COMMON STORAGE MONITOR component of MainView for z/OS allows the user to collect data on the allocations and use of common storage (CSA). This component can be activated or not activated. BMC recommends starting this monitor as soon as possible in order to track all CSA allocations directly after IPL.