Why is there no activity data displayed for ICP channel types in the channel activity report or in the CPALL view?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView for z/OS


    APPLIES TO:

    MainView for z/OS CMF MONITOR



    PROBLEM:

    Why is there no activity data displayed for Internal Coupling Peer (ICP) channel types in the channel activity report or in the CPALL view?     


    SOLUTION:

    While the ICP channels are "channels", they are not used for "I/O". 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. CPALL and any other Channel related view in MAINVIEW will not show an CF to CF activity. This activity is not I/O that z/OS is performing so MainView for z/OS would not see that activity.

    Activity on 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.
     


    Article Number:

    000120220


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles