Task 4 Implementing the PARMLIB
Task 4.1 Implement the PARMLIB
BMC mainframe products, including Session Monitor, use parameter libraries (PARMLIBs) with the Common Mainframe Services Controller (CMSC) to configure each product and common components. The CMSC is installed as part of the BMC AMI Enterprise Common Components installation.
This task is required for both a new installation and an upgrade of Session Monitor.
Task 4.1.1 Create the Default Member
Choose one of the following sample sources of PARMLIB member HSCM:
Library | Member name | Contents |
---|---|---|
Target library | HSCM00 | Sample Session Monitor parameter member with only core parameters that you must be set to enable Session Monitor to function. |
Target library | HSCMALL | Sample Session Monitor PARMLIB parameter member with every product parameter and descriptions of either coding values. |
Configuration library | HSCM00 | Initially, this is a copy of member HSCM00 from the SQQFSAMP target library. After running Task 3.6 Perform PARMLIB Gen (for new installations) or Tracking-the-manual-tasks (for upgrades,) it contains a sample PARMLIB member with values collected during import and configuration set as appropriate parameter values. |
Alternatively, you can choose either of the other samples as a starting point to create your own member and set parameter values as needed.
For an upgrade, you might already have an HSCM00 in your PARMLIB. You can simply edit that member, changing parameter settings as needed. Use the generated .INSTALL member HSCM00 as a guide to setting parameter values and identifying any new parameters added to the product since your existing member was created.
Task 4.1.2 Update the CMSC with your PARMLIB members
Use the z/OS MODIFY (F) command to update the CMSC with the PARMLIB member that you created.
To refresh all PARMLIB members use,
To refresh a single parameter member use,
F cmscname,PARMLIB REFRESH member_name
During the refresh process, parameter values are validated. If they are found to be invalid, an error message is written to the FDBDLOG SYSOUT data set associated with the ECC CMSC instance in which the member is being refreshed. If an error is detected, the contents of the in-core member are not refreshed. You must correct the error and refresh the member before attempting to use it.