Manual customization
This topic describes how to complete the manual customization process that you began in Overview of MainView Customization
.
The following tasks are unique to the CMF MONITOR product:
- Specifying Extractor operating environment
- Copying sample parameter and JCL members
- Copying sample online screen definitions
- Creating the CLIST for invoking the CMFMON Online Facility
(If you used the Installation System to configure CMF MONITOR, you have already completed this task and can skip it.) - Creating JCL for starting CMFMON Write Facility
- Assembling and linking the JES3 mapping CSECT
- Copying CMF API modules to the output load library
(If you used the Installation System to configure CMF MONITOR, you have already completed this task and can skip it.)
Specifying Extractor operating environment
You must specify the correct Extractor operating environment for the combination of BMC products that you have installed in your system. In this procedure, you select a sample member containing the minimum set of Extractor control statements for the combination of products at your site.
The following BMC products use the Extractor:
- MainView for z/OS
- CMF MONITOR
Each product or combination of products requires specific Extractor control statements to collect the necessary data for product views, displays, and reports. Samples of the different Extractor control statement sets for each product mix are shipped in BBSAMP.
To specify the Extractor operating environment for your BMC Software product mix
- Create two members in hilevel.UBBSAMP with the names CMFCPM00 and CMFIPM00.
- Go to Sample members to copy into CMFCPM00 and locate the row that contains + (plus) marks for the combination of Extractor products you have. Note the BBSAMP member name on that row.
- Copy the correct sample member from BBSAMP to the CMFCPM00 member in hilevel.UBBSAMP.
- Go to Sample members to copy into CMFIPM00 and locate the row that contains + (plus) marks for the combination of Extractor products you have. Note the BBSAMP member name on that row.
- Copy the correct sample member from BBSAMP to the CMFIPM00 member in hilevel.UBBSAMP.
To allocate CPM output data sets and optionally allocate IPM output data sets for CMF MONITOR, use hilevel.UBBSAMP member:
- CMFJBSAM for BSAM data sets
- CMFJVSAM for VSAM data sets
Sample members to copy into CMFCPM00
If you are customizing
CMF MONITOR
MainView for z/OS
Copy BBSAMP member
+
CMFCC
+
+
CMFCCR
+
CMFCR
Sample members to copy into CMFIPM00
If you are customizing
CMF MONITOR
MainView for z/OS
Copy BBSAMP member
+
CMFIC
+
+
CMFICR
+
CMFIR
Copying sample parameter and JCL members
All sample JCL members for use with CMF MONITOR are distributed in hilevel.BBSAMP. These members are then copied (and in some cases, renamed) to hilevel.UBBPARM.
A description of each of these members is in Sample members available for customization in UBBSAMP.
In this step, you copy sample JCL members for CMF MONITOR from BBSAMP to your own hilevel.UBBSAMP, and you copy default control statement members from BBPARM to your own hilevel.BBPARM libraries. From then on, all modifications should be made in UBBSAMP and UBBPARM, leaving the originals untouched in BBSAMP and BBPARM. By performing this step, you prevent the modifications you make for your site from being overwritten when new product FMIDs are added or when maintenance is applied.
To create copies of the sample members in hilevel.UBBPARM and in hilevel.UBBSAMP
- Copy hilevel.BBSAMP member CMFCPARM to your private JCL library.
- Modify the JCL by following the directions at the top of the member.
- Submit the JCL.
After the sample JCL members and control statement members have been copied, you can use them to begin executing CMF MONITOR. Instructions for using each of these samples is provided within the member itself.
You can also modify these samples to meet the specific needs of your site. For additional information about modifying either Analyzer or Extractor control statements, see Defining-Extractor-control-statements.
The following table contains a description of all sample members copied from BBSAMP to UBBSAMP. Sample control statement members available for customization in UBBPARM contains sample control statements copied from BBPARM to UBBPARM.
Sample members available for customization in UBBSAMP
Member name | Description |
---|---|
@BBXINIT | JCL to initialize BBXS |
CMFJMONB | Sample JCL for running CMFMON type 79 batch reports. See Using-CMF-MONITOR-CMFMON for information about using this member. |
CMFJANL | JCL to run the CMF MONITOR Analyzer. See Defining-Extractor-control-statements for information about using this member. |
CMFJBSAM | JCL for creating BSAM Extractor output data sets. |
CMFJVSAM | JCL for creating VSAM Extractor output data sets. |
CMFJCLRB | JCL used for clearing CMF MONITOR output data sets as a batch job. If you record CMF MONITOR data to SMF, you do not need to use this member. |
CMFJCLRS | JCL used for clearing CMF MONITOR output data sets as a Started Task. If you record CMF MONITOR data to SMF, you do not need to use this member. |
CMFJCVBS | JCL to run the COPYVBS ( CX10CVBS) utility |
CSMAPSAS | Sample SAS routine to produce a common storage report that uses CMF type 29 records. |
CX98REPG | JCL to create a sample report for testing the CMF MONITOR Analyzer Spreadsheet Converter. See Defining-Extractor-control-statements for more information about using the Spreadsheet Converter program. |
CMFERBCP | JCL to copy CMF API modules and their RMF aliases to the output data set. |
Sample control statement members available for customization in UBBPARM
Member name | Description |
---|---|
ANLYSAMP | CMF MONITOR Analyzer control statements to produce most of the batch reports . |
CMFANLTR | CMF MONITOR Analyzer control statements to produce trace reports from the SMF type 76 trace records . |
CMFMNB00 | Sample control statements for producing CMFMON batch reports. See Using-CMF-MONITOR-CMFMON for information about using this member. |
CMFCPM00 | Sample Extractor CPM control statements as described in Defining-Extractor-control-statements. |
CMFIPM00 | Sample Extractor IPM control statements as described in Defining-Extractor-control-statements. |
CMFMON00 | Sample control statements for running the CMFMON component of CMF MONITOR, as described in Using-CMF-MONITOR-CMFMON. |
CMFCPM01, CMFCPM08, CMFCPM15 | Sample Extractor control statements for each of the possible combinations of products that use the Extractor CPM mode. |
CMFIPM01, CMFIPM04, CMFIPM07 | Sample Extractor control statements for each of the possible combinations of products that use the Extractor IPM mode. |
CMFXDS00 | Sample XDS control statements for starting the collection of cross-system data for use by SDSF. The distributed MainView for z/OS PAS PROC points to this member. For more information about using this member, see Administering. |
CMFXDS01 | Sample XDS control statements to start buffering CMF type records (excluding type 79). For more information about using this member, see Administering. |
CMFXDS02 | Sample XDS control statements to start buffering all CMF type records including type 79 For more information about using this member, see Administering. |
Copying sample online screen definitions
The online component of CMF MONITOR presents information about your system through online views.
You can display multiple views with one command by combining them into screen definitions. Four samples of screens definitions, each containing multiple views, have been created for your use. This step copies those sample screen definitions from BBSAMP to your own sitewide library, hilevel. SBBSDEF.
To copy the sample screen definitions
- Copy hilevel . BBSAMP member CMFCSDEF to your private JCL library.
- Modify the JCL by following the directions at the top of the member.
- Submit the JCL.
For information about using the sample screen definitions or creating your own screen definitions, see Using-screen-definitions-to-solve-problems.
Creating the CLIST for invoking the CMFMON Online Facility
This task creates the CLIST for starting the CMFMON Online Facility. The CMFMON Online Facility displays job- and system-related data from an ISPF application. The data is presented in a format similar to that of RMF MONITOR II (RMFMON).
The CMFMON CLIST is used to invoke the CMFMON Online Facility. The CLIST performs all necessary data set allocations and then displays the CMFMON menu from your TSO ISPF session.
To create the CMFMON CLIST
- Copy BBSAMP member CMFMON to your private CLIST library. Make sure that the CLIST library is in the SYSPROC concatenation of your TSO logon procedure.
- Modify the CLIST by following the directions at the top of the member.
- Save the CLIST.
For more information about using the CMFMON Online Facility, see Using-CMF-MONITOR-CMFMON.
Creating JCL for starting CMFMON Write Facility
This step creates JCL that allows you to invoke the CMFMON Write Facility as a batch job and as a started procedure.
By invoking the CMFMON Write Facility, you can write type 79 records either to the SMF data set or to an output data set of your choice. If you choose to write type 79 records to an output data set (not to SMF), this step also provides instructions for allocating that output data set.
Creating an output data set for type 79 records
To create an output data set for type 79 records
- Copy BBSAMP member CMFJBSAM to your private JCL library.
Modify the JCL by following the directions at the top of the member.
- Submit the JCL.
Creating a batch job for starting CMFMON
To create a batch job for starting CMFMON
- Copy BBSAMP member CMONJCL to your private JCL library.
- Modify the JCL by following the directions at the top of the member.
- Save this member to use when you want to start CMFMON as a batch job.
Creating a started procedure for starting CMFMON
The following procedure describes how to create a started procedure for starting CMFMON.
To create a started procedure for starting CMFMON
- Copy BBSAMP member CMONSTC to a system procedure library.
- Modify the JCL by following the directions at the top of the member.
- Save this member so that you can invoke CMFMON as a Started Task from the console.
For information about using the CMFMON Write Facility, see Using-the-CMFMON-write-facility.
Assembling and linking the JES3 mapping CSECT
Use this step only if your system runs a JES3 subsystem; do not perform this step if your system runs a JES2 subsystem.
The JES sampler, which is controlled by the EXTSUM Extractor control statement, needs to know the correct offsets for your version of JES3 so that it can use the proper CSECT mapping when gathering data. This step creates a job that assembles and links the mapping CSECT and provides the appropriate JES3 offsets to the EXTSUM sampler.
To assemble and link the JES3 mapping CSECT
- Copy hilevel . BBSAMP member CMFCJES3 to your private JCL library.
- Modify the JCL by following the directions at the top of the member.
- Submit the JCL.
For information about using the EXTSUM Extractor control statement, see EXTSUM.
Copying CMF API modules to the output load library
This optional step copies the CMF API load modules and their RMF aliases from the installation library to the specified output load library.
This step is not required if the BBLINK will be on the Link List. If copied, place the output load library on the Link List ahead of the SERBLINK library.
To copy CMF API modules to the output load library
- Copy hilevel.UBBSAMP member CMFERBCP to your private JCL library.
- Modify the JCL by following the directions at the top of the member.
- Submit the JCL.
You have now completed the manual customization procedure for CMF MONITOR.
Where to go from here: