Skip to Content

Additional CMF API considerations

The following sections provide additional information about 

BMC AMI Ops Monitor for 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 the IFAPRD dynamic product enablement facility.

The API names or aliases with issues are as follows:

BMC AMI Ops Monitor for CMF API name

RMF API name

BMC AMI Ops Monitor for 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. Make sure that MVS rules of module search find the APIs in the hilevel.BBLINK library before SYS1.SERBLINK. If BBLINK is placed on the Link List, 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 Link List results in unpredictable API behavior.

As an alternative to placing BBLINK on the Link List, you can copy the individual API modules and their aliases to an appropriate Link List data set (concatenated ahead of SYS1.SERBLINK).

Warning

Important

A configuration step for CMF copies the CMF API load modules and their RMF aliases to the output library. If you do not use the configuration step and want to copy the CMF API load modules manually, you can perform the copy by using hilevel.UBBSAMP(CMFERBCP).

Error
Warning

When you copy these modules, you must copy both the primary names and the aliases together. Because most Link List data sets are LLA-managed, you cannot successfully perform this copy procedure by using the ISPF 3.3 Copy function. You should perform this procedure by using IEBCOPY or some other equivalent.

The API modules must be from the same BBLINK used by the CMF PAS. Also, when service is applied to any CMF API modules, they will need to be recopied (with their aliases).

If users of the APIs (such as SDSF) are behaving incorrectly, to determine if there might be a mismatch between the CMF PAS and the API module stub, the API user (typically a TSO user) should 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 Link List.

Even if the CMF PAS is running by using BBLINK from the Link List, older copies of the API modules might be present in a Link List data set ahead of BBLINK (perhaps previously copied before BBLINK was added to the Link List). This situation causes 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)
Warning

Important

Users requesting data from the remote system when using the CMF API from SDSF are validated on each of the remote systems for both validity and access to resources. If asymmetric security definitions are used on different systems within the sysplex, various authorization errors occur.

Installation requirements to use CMF APIs

Complete the following installation requirements to use CMF APIs:

  1. Make sure that the BBLINK data set is available in the Link List (see CMF APIsfor additional considerations), or that the BBLINK data set is available in the TSO logon procedure STEPLIB.
  2. Specify CPU sampling in the CMFCPMxx PARMLIB member.
  3. Make sure 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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Monitor for CMF 6.3