IBM Support

II05151: RMF CHANNEL PATH ACTIVITY REPORT: DASHES AND ZERO VALUES FOR PATH UTILIZATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • RMF Channel Path reports, Utilization values:
    When RMF cannot collect channel path data, it reports dashes
    for these paths. The channel paths in question are listed below.
    
         Channel Path |
         Acronym      | Description
        --------------+----------------------------
         BYTE         | Parallel Byte Multiplex
         CBY          | ESCON Path to a Byte Converter
         ISD          | Internal System Device
         DSD          | Direct System Device
         EIO          | Emulated I/O
         CFS          | Coupling Facility Sender
         CFR          | Coupling Facility Receiver
         CBS          | Cluster Bus Sender
         CBR          | Cluster Bus Receiver
         ICS          | Internal Coupling Sender
         ICR          | Internal Coupling Receiver
         CBP          | Integrated Cluster Bus Peer
         CFP          | Coupling Facility Peer
         CIB          | Coupling links using InfiniBand
         ICP          | Internal Coupling Peer
    
    To collect Channel Path data, RMF inspects SRM maintained
    control blocks at the end of each measurement interval.
    Due to hardware restrictions (which are processor type
    dependent), these data may be not, or only partially,
    available to SRM.
    
    When the data is not available for a Coupling Facility Path,
    the average utilization for the set of CF links from a system
    to a CF may be calculated with the data in the RMF Coupling
    Facility Report, Subchannel Activity Section.
    
                      ((SYNC #REQ * SYNC service time) +
                       (ASYNC #REQ * ASYNC service time))
    Utilization % = --------------------------------------- * 100
                     Interval time  *  #subchannels in use
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II05151

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1991-06-18

  • Closed date

    1993-10-22

  • Last modified date

    2008-10-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
13 December 2020