Field descriptions of the CF to CF Activity Section
The following figure shows an example of the CF to CF Activity section of the Coupling Facility Activity Report.
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 = IMSLCFCC ------------------------- CF TO CF ACTIVITY --------------------------------------------------------
----------- REQUESTS ----------- -------------- QUEUED REQUESTS ---------------
PEER -RECEIVER- -SENDER- --SERVICE TIME-- # % -- DELAY TIME -----
CF TYPE USE TYPE USE PER SEC COUNT AVG STD DEV REQ REQ /REQ STD DEV /ALL
-------- ----- --- ----- --- ------- ------- ------- -------- ------- ----- ------- ------- -------
IMSLCF02 ICP 1 ICP 1 0 0 0 0 SYNC 0 0 0 0 0
------------------- CHANNEL PATH DETAILS -------------------
SYSTEM CPID TYPE ---OPERATION MODE--- DEGRADED DISTANCE
CF13 23 CIB 12x B/W IFB3 HCA3-0 NO N/A
CF13 24 CIB 12x B/W IFB3 HCA3-0 NO N/A
The following table describes each field in the CF to CF Activity section.
Field | Description |
|---|---|
PEER CF | Remote coupling facility name |
RECEIVER (PTF BQM1361, BQM1362, BQM1363, BQM1379, BQY1369, or BQY1371 applied) | TYPE—type of CF-to-CF receiver link USE—number of receiver links used for coupling facility communications |
SENDER (PTF BQM1361, BQM1362, BQM1363, BQM1379, BQY1369, or BQY1371 applied) | TYPE—type of CF-to-CF sender link USE—number of sender links used for coupling facility communications Information about sender links is available only if input SMF records were produced on IBM z/OS 2.2 systems with support for asynchronous duplexing. |
REQUESTS - PER SEC | Average number of requests per second This value is the sum of the signal counters that the subject CF has sent to the remote CF. This calculation uses the following signal counters:
|
REQUESTS - COUNT | Total number of requests in the interval |
REQUESTS - SERVICE TIME | AVG—average service time in microseconds STD DEV—standard deviation to the average service time |
QUEUED REQUESTS | Queued requests are synchronous |
QUEUED REQUESTS - # REQ | Number of signals of all types that have experienced a delay in being sent from the subject CF to this remote CF |
QUEUED REQUESTS - % REQ | Percentage of requests that are delayed |
QUEUED REQUESTS - DELAY TIME | /REQ—the average delay time in microseconds over all delayed requests S DEV—standard deviation of the average delay time /ALL—average delay time in microseconds for all requests, both delayed and not delayed |
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 facility Up to eight channel paths can be connected from an LPAR to a coupling facility. |
TYPE | Channel path type |
OPERATION MODE | Channel path operation mode This field indicates the following information:
|
DEGRADED | 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 |
Related topic