This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
MainView for z/OS
MainView for z/OS CMF MONITOR
Are there any configuration / customisation requirements in MainView in order to monitor Infiniband coupling links?
Infiniband Coupling links are Coupling Facility channels and are reported on by the Coupling Facility API, which does not differentiate on channel types in the reporting it does. InfiniBand coupling links are CHPID type CIB, and there are no special configuration/customisation requirements in MainView in order to monitor them.
Some users have commented that they have seen no data for Infiniband links (type CIB) when looking at channel activity in the CPALL view. The result is to be expected. For more information on this, see KA 000120220 - "Why is there no activity data displayed for Internal Coupling Peer (ICP) channel types in the channel activity report or in the CPALL view?" This will also apply to CIB channel types.
The communication to the Coupling Facilities, both from z/OS and between Coupling Facilities, is done with special instructions. The channel subsystem does not report on this activity, which is not I/O that z/OS is performing, so MainView for z/OS would not see this.
To look at Infiniband activity, Coupling Facility (CF) usage is reported via the CF API (IXLMG), which is used to produce the 74-4 SMF records and data for the CFxxxxxx views. Individual channel usage is not captured, but subchannel and path busy is. The CFDATA extractor samples coupling facility activity and the CFACT Analyzer statement is used to produce the Coupling Facility Activity Report.