This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
MainView for CICS
MainView for CICS
When we install MAINVIEW PUT / Recommended Service Levels, it would be nice if we didn't have to recycle the CICS regions to pick up the new code applied to BBLINK. Can we define the MV for CICS BBLINK library as a LIBRARY resource to CICS? Then we could dynamically refresh it after applying the maintenance and restarting the PAS.
It is possible to define the BBLINK as a LIBRARY resource to CICS TS 3.2 and above. We have a number of customers doing it this way with no problem.
The manuals state that BMC BBLINK modules have to be in DFHRPL concatenation but it doesn't matter HOW they get there. CICS LIBRARY facility puts the modules into DFHRPL concatenation.
Things to be aware of when putting BBLINK in a LIBRARY resource:
- BBLINK should be completely removed from DFHRPL
- It should be in a library resource by itself so enabling and disabling this resource will not affect others.
- The ranking of the BBLINK library resource must be ahead of any other data sets containing member BALPUTLV if any.
- Define the BBLINK Library resource with the CRITICAL attribute if MVCICS starts in the PLTPI.
- The library resource has to be in ENABLED status.
MainView for CICS (MVCICS) V6.4 introduced the CLIBR family of views. Users can use the action commands available in the CLIBR view to manipulate the LIBRARY resources.
Example of how to switch to use BBLINK LIBRARY resource without a recycle of CICS:
1) Create and then install a Library resource for BBLINK with these attributes: Ranking(9), Criticalst(Critical) and Enablestatus(Enabled). The Ranking of 9 will put it ahead of DFHRPL incase another data set in the DFHRPL concatenation have member BALPUTLV in it. This will also prevent a need to recycle CICS when BBLINK is currently in DFHRPL.
2) Enter FST2 TERM and then FST2 INIT in this CICS to start using the BBLINK library resource.
3) Go to MVCICS window mode and enter CPROG for the same CICS and you should see all the MVCICS modules loaded from the BBLINK library resource (field name Library DDname). Note that unused BBK1* modules may still have Library DDname of DFHRPL, but that will change when the modules are loaded to process views that get data via CICS SPI. Views like CREGSYS, CTCPSRV, CWEBSRV, etc.
4) Remove BBLINK completely from DFHRPL in CICS JCL for next recycle of CICS..
Example of how to use CLIBR to refresh MVCICS BBLINK using the same BBLINK after moving BBLINK to a library resource
1) It is not a requirement but it is best to enter FST2 TERM to terminate MVCICS agents. This way users will not get an error when they enter a view request that requires loading of a module from the BBLINK library resource after step 2. Loading is only necessary for the first request of that view.
2) Go to MVCICS window mode and enter CLIBR for the same CICS and then enter the DIS line command to disable the BBLINK library resource.
3) Copy the new modules into BBLINK.
4) Go to MVCICS window mode and enter CLIBR for the same CICS and then enter the ENA line command to enable the BBLINK library resource.
5) Enter FST2 INIT on CICS to initialize the MVCICS agents with the new code. If you did not enter FST2 TERM in step 1 you will have to do it now before entering FST2 INIT.
Example of how to use CLIBR to refresh MVCICS BBLINK using a different BBLINK data set:
1) With BBLINK1 as the current library resource. Create and install a BBLINK2 with the same attributes except Dsname01 will have a new data set with the maintenance and Enablestatus(Disabled).
2) Enter FST2 TERM to terminate the MVCICS agents.
3) Go to MVCICS window mode and enter CLIBR for the same CICS and then enter the DIS line command to disable the BBLINK1 library resource and then the ENA line command to enable the BBLINK2 library resource.
4) Enter FST2 INIT on CICS to initialize the MVCICS agents with the new code