Field descriptions of the Subchannel Activity Section

The following figure shows an example of the Subchannel Activity Section of the Coupling Facility Activity Report.

PRODUCED BY CMF ANALYZER (v.r.mm RSL yymm )       COUPLING FACILITY ACTIVITY REPORT                    RPTSEQ     3 PAGE     18
BMC SOFTWARE, INC.                                           XYZ COMPANY                                REPORT DATE: DD MMM YY 1.47
ACTL 10 AUG 14 14.16.19 11 AUG 14 01.30.00                  HQ LOCATION                                SYSTEM ID: SJSD     Z v.rr.n


BASED ON REC TYPE/# RECS/# SAMPLES/REC HOURS: 74-4/90/1,345/11.23
COUPLING FACILITY = CF16      --------------------- SUBCHANNEL ACTIVITY SECTION --------------------------------------------------

SYSTEM ------------------ REQUESTS ------------------- %    -------------- QUEUED REQUESTS --------------- REJECTED -- CONFIG --
  NAME    TYPE    PER      COUNT   % OF -SERVICE TIME-- LINK   TYPE     #      %    ----- DELAY TIME ------ REQUESTS RESOURCE CNT
                  SEC              ALL     AVG   STD DEV UTIL            REQ    REQ    /REQ   S DEV    /ALL RES CNT
-------- ------- ------- --------- ----- ------- ------- ----- -------- ------- ----- ------- ------- ------- ---- ---- -------- ---
ADDM     *** NO DATA ***

SJSB     *** NO DATA ***

SJSC     *** NO DATA ***

SJSD     ALL       210.2   8497713 100.0    28.9   141.0     0                                                PATH    0 PATH       4
           SYNC     42.1   1700345 20.0     7.9    10.9     0 SYNC           0     0       0       0       0 SCH     0 SCH GEN   28
           ASYNC    67.4   2724759 32.1    42.0   178.3     0 ASYNC        139     0     731     501       0           SCH USE   28
           CNVAS       0         0     0                       TOTAL        139     0                                   SCH OPT   28
           UNSUC       0         0     0       0       0                                                                CHP TYPE ICP

SJSE     *** NO DATA ***

SJSH     *** NO DATA ***

-------- ------- ------- --------- ----- ------- ------- ----- -------- ------- ----- ------- ------- ------- ---- ----
SUMMARY ALL       210.2   8497713 100.0    28.9   141.0                                                      PATH    0
           SYNC     42.1   1700345 20.0     7.9    10.9       SYNC           0     0       0       0       0 SCH     0
           ASYNC    67.4   2724759 32.1    42.0   178.3       ASYNC        139     0     731     501       0
           CNVAS       0         0     0                       TOTAL        139     0
           UNSUC       0         0     0       0       0

------------------------------------------------- CHANNEL PATH DETAILS ------------------------------------------------
SYSTEM CPID TYPE   ---OPERATION MODE--- DEGRADED DISTANCE PCHID HCA ID HCA PORT -------- I/O PROC IDS --------
SJSD      23   CIB    12x B/W IFB3 HCA3-0      NO          N/A   0702   000C      02     01
SJSD      24   CIB    12x B/W IFB3 HCA3-0      NO          N/A   0703   001C      02     04

The following table describes each field on Subchannel Activity section of the Coupling Facility Activity Report.

Field	Description
SYSTEM NAME	Name of the system connected to the coupling facility Note If no records from a system are found in the input data, * NO DATA * is printed after the system name.
REQUESTS - TYPE	Type of requests Possible values for this field are as follows: SYNC—synchronous requests directed to structures ASYNC—asynchronous requests directed to structures CNVAS—requests directed to structures that originated as synchronous but converted to asynchronous A synchronous request is converted to asynchronous if the buffer size is greater than 4-K bytes or if multiple buffers are passed. UNSUC—not completed due to hardware problems ALL—total of all request types The ALL field value can exceed the sum of the values for SYNC, ASYNC, CNVS, and UNSUC because it also includes coupling-facility-managing requests and requests directed to structures that are no longer active at the end of the interval.
REQUESTS - PER SEC	Rate per second of requests that originated from the system, viewed by request type Note The rate and count of requests from all systems in the SUMMARY section exceeds the TOTAL rate and count in the Structure Summary section, because the former include unsuccessful requests and coupling-facility-managing requests.
REQUESTS - COUNT	Number of requests that originated from a system
REQUESTS - % OF ALL	Percentage of requests of a type that originated from a system, compared with the total number of requests from all systems
REQUESTS - SERVICE TIME - AVG, STD DEV	Average number of microseconds that are required to complete a request (excluding queue time) and its standard deviation Service time of synchronous-converted-to-asynchronous (CNVAS) requests is included in that of asynchronous (ASYNC) requests. The service time of coupling-facility-managing (GLOBL) requests is not available.
% LINK UTIL	Coupling Link Utilization Percent is shown for SYNC requests, ASYNC requests, and the total of the two. It is calculated as follows: [(RC * AST) / (IT * 1,000,000 * NSU)] * 100 where RC = Request Count AST = Average Service Time (in microseconds) IT = Interval Time (in seconds) NSU = Number of Subchannels in Use Note The value shown is the average for the set of CHPIDs used by the system which is specified to communicate with the CF. If multiple SYSPLEXes are sharing the set of CHPIDs, add the values for all of the SYSPLEXes to determine the link’s overall utilization.
QUEUED REQUESTS - # REQ	Total number of requests to this coupling facility that were delayed in this interval
QUEUED REQUESTS - % REQ	Percentage of requests to this coupling facility that were delayed in this interval
DELAY TIME / REQ	Average delay time for each delayed request in microseconds
DELAY TIME S DEV	Standard deviation of the average delay time for delayed requests
DELAY TIME / ALL	Average delay time for all requests to the coupling facility in microseconds This number helps indicate how delays are affecting overall request activity to the coupling facility.
REJECTED REQUESTS - RES, CNT	Number of requests that were rejected due to a temporary lack of resource: path (PATH) or subchannel (SCH)
CONFIG - RESOURCE, CNT	Number of paths or coupling facility subchannels for each of the following resources: PATH—number of paths connecting the system and the coupling facility SCH GEN—number of GENed coupling facility subchannels SCH USE—number of coupling facility subchannels that are currently in use SCH OPT—number of coupling facility subchannels that this system can optimally use to satisfy its requests
Channel Path Details subsection
SYSTEM	Name of the system connected to the coupling facility
CPID	Channel path ID of a channel attached to this coupling facilityThere can be up to eight channel paths connected from an LPAR to a coupling facility.
TYPE	Channel path type
OPERATION MODE	Channel path operation mode Indicates the following: Data rates for CFP channel paths: 1GBIT - 1.0625 Gbit/sec 2GBIT - 2.125 Gbit/sec Bandwidth for CIB channel paths: 1X - single bandwidth 12X - 12-fold bandwidth Protocol for CIB channel paths: IFB IFB3 Adapter types for CIB channel paths: HCA-O HCA-O LR HCA3-O LR HCA3-O LR Bandwidth for CS5 channel paths: 8X - 8-fold bandwidth Protocol for CS5 channel paths: PCIe Gen3 Adapter types for CS5 channel paths: PCIe-O SR An unknown operation mode (UNKNOWN)
DEGRADED	Indicates whether the channel path is either operating at a reduced capacity or is not operating at all
DISTANCE	Estimated channel path distance in kilometers, calculated as follows average round trip path time in microseconds / 10 microseconds per kilometer
PCHID	Physical channel identifier
HCA ID	Host channel adapter identifier
HCA PORT	Host channel adapter port
I/O PROC IDS	Identifiers for the I/O processors (System Assist Processors) that are accessible by the channel path

Field descriptions of the Subchannel Activity Section

On this page