Additional CMF API considerations
The following sections provide additional information about CMF API routines:
- CMF APIs
- CMF APIs and SDSF
CMF APIs
IBM ships the ERB* API routines even if you do not license RMF; however, these API routines are disabled by way of the IFAPRD dynamic product enablement facility.
API names/aliases at issue are as follows:
CMF API name | RMF API name | CMF module |
|---|---|---|
CX10GVID | ERBSMFI | CX10GVID |
CX10XDGS | ERB2XDGS | CX10XDU0 |
CX10DSQY | ERBDSQRY | CX10XDU0 |
CX10DSRC | ERBDSREC | CX10XDU0 |
CX10XDRS | ERB3XDRS | CX10XDRS |
CX10XDGX | ERB2XSMF | CX10XDGX |
RMF APIs reside in SYS1.SERBLINK. Ensure that MVS rules of module search find the APIs in the hilevel.BBLINK library before SYS1.SERBLINK. If BBLINK is placed on the linklist, make sure that it is at the same level as the BBLINK that the CMF PAS is using. Running the CMF PAS with a different level of BBLINK (through STEPLIB) from the one on the linklist will result in unpredictable API behavior.
As an alternative to placing BBLINK on the linklist, the individual API modules and their aliases can be copied to an appropriate linklist data set (concatenated ahead of SYS1.SERBLINK).
If users of the APIs (such as SDSF) are behaving incorrectly, one method to determine if there might be a mismatch between the CMF PAS and the API modules is to have the API user (typically a TSO user) include the BBLINK that the CMF PAS is using as part of its STEPLIB. (When trying this procedure, make sure that all data sets in the STEPLIB concatenation are APF-authorized.) If the APIs behave correctly with the STEPLIB, it is likely that incompatible API modules are being fetched from the linklist.
Even if the CMF PAS is running by using BBLINK from the linklist, older copies of the API modules might be present in a linklist data set ahead of BBLINK (perhaps previously copied before BBLINK was added to the linklist). Such a situation will cause unpredictable API behavior. Be sure to examine each of the data sets concatenated ahead of BBLINK for possible API-module mismatch.
CMF APIs and SDSF
The IBM SDSF product uses the following APIs to get system- and job-related performance information:
- ERBSMFI — used to obtain data for the local system (used by DA subcommand)
- ERB2XDGS — used to obtain data from systems anywhere in the sysplex (used by DA subcommand)
- ERB3XDRS — used to obtain the job delay data (used by JY subcommand)
Installation requirements to use CMF APIs
Complete the following installation requirements to use CMF APIs:
- Ensure that the BBLINK data set is available in the linklist (see CMF APIs for additional considerations), or ensure that the BBLINK data set is available in the TSO logon procedure STEPLIB.
- Specify CPU sampling in the CMFCPMxx PARMLIB member.
- Ensure that the following additional requirements have been met for all systems:
- A CAS is running with SPCF active and in the same XCF group as the other CASs
- An MVS PAS with XDS active. (By default, XDS=00 is distributed in the MVSPAS product.)
- The MVS PASs must all have DC=START in effect.
- The MVS PASs must have CXEN=Y in effect.