Field descriptions of the summary sections of the Coupling Facility Activity Report

The following table describes each field on the summary sections of the Coupling Facility Activity Report.

Field	Description
COUPLING FACILITY	Coupling facility name Warning Note This field is displayed in the first section header on every page of this report.
PROCESSOR SUMMARY SECTION
CPU MODEL	CPU model
VERSION	Hardware model identifier
PLANT	Manufacturer plant code
SEQUENCE #	Sequence number
CF LEVEL	Coupling facility function level
# LOGICAL PROCESSORS	Number of logical processors if the coupling facility is a partition in a PR/SM environment, or the number of physical processors if the coupling facility is stand-alone
# SHARED PROCESSORS	Number of shared logical processors¹
AVG WEIGHT	Average weight of the shared processors, up to 999¹
DYNAMIC DISPATCHING	The dynamic dispatching status for the coupling facility:¹ OFF—Coupling facility will continuously poll for work The CPU for the coupling facility, when dispatched, will always appear to be 100% busy. ON—When out of work, the coupling facility will quiesce and then actively look for work on a timer basis THIN—Thin interrupts are enabled
# PROCESSORS EFFECTIVE	Number of available logical processors, effectively, if the coupling facility is a partition in a PR/SM environment This value is a ratio of the total LPAR dispatch time (sum of CFCC execute time and wait time for all processors) over the interval duration. For a coupling facility that is ICMF LPAR, refer to CPU-Utilization-Report.
AVERAGE UTILIZATION	Average CPU utilization of the coupling facility
MAXIMUM UTILIZATION, PROCESSOR NUMBER, FROM, TO	Maximum utilization of any processor during all recording intervals PROCESSOR NUMBER identifies the processor, and FROM and TO identify the recording interval.
MODEL	Coupling facility type
VERSION	Coupling facility model
CFLEVEL	Coupling facility microcode level
PLANT	Two-character Manufacturer Plant Code; field will be blank for z/OS systems earlier than 1.8
SEQUENCE #	12-character Manufacturer Sequence Number; field will be blank for z/OS systems earlier than 1.8
STORAGE SUMMARY SECTION
STORAGE ALLOCATION	STRUCTURES—Storage allocated and partitioned into structures The amount of storage allocated to structures reported here can exceed the TOTAL SIZE of all structures in the STRUCTURE SUMMARY SECTION because some amount of overhead is not attributable to any structure. DUMP—Storage reserved for dumping data AUGMENTED—Storage allocated as augmented space AVAILABLE—Storage not allocated to structures, dump, or augmented space TOTAL—Total storage of the coupling facility
SIZE	AMOUNT— Storage in the coupling facility is allocated in blocks of 4-K bytes² % OF CF— Percentage of the total coupling facility storage allocated to structures, dump space, or available
% OF DUMP	USED— Percentage of dump space in use, observed at end of interval MAX REQ — Percentage of the largest amount of dump space requested, compared with the dump space size This largest requested amount is a high water mark since coupling facility initialization or dump space reinitialization. If this value exceeds 100, at least 1 dump has been lost or truncated. The recommended size of dump space equals that of the largest structure or 5% of the coupling facility storage, whichever is larger.
STORAGE ORGANIZATION	Structure and dump storage in the coupling facility occupies both Control and DATA area
DEFINED	SIZE—For control area, the maximum amount it can occupy Data area, on the other hand, is not restricted to this size. When exhausted, data storage can be allocated from control area. The control area can be defined as equaling the total coupling facility storage. In other words, there is no restriction on the size of the control area; the entire coupling facility is shared between control and data areas. In this case, NOT DEFINED SEPARATELY FROM Control is printed on the DATA line. % OF CF — Percentage of coupling facility storage allocated to control or data area
ALLOCATED	SIZE—Amount of control or data area allocated to structures or dump The allocated size of data area can exceed the defined size (% OF DEFINED then exceeds 100), indicating that the data storage has been exhausted and data has been allocated from the control area. % OF DEFINED — Percentage of defined control or data area allocated to structures or dump
Total CF SCM	Assigned— Amount of SCM that can be concurrently used as structure extensions (assigned in 4-KB increments) %InUse — Percentage of SCM in use by all structures of the coupling facility SumMaxSCM — Sum of the maximum SCM defined for all structures of the coupling facility
CONNECTIVITY SUMMARY SECTION
SYSTEM NAME	Name of the system connected to the coupling facility If no records from a system are found in the input data, * NO DATA * is printed after the system name.
DURATION	Total recording intervals of records produced on system
START TIME	Start date and time of the first record
END TIME	End date and time of the last record
STRUCTURE SUMMARY SECTION
TYPE	First user connecting to a structure specifies its type Possible values for this field are as follows: LIST—Allows users to share data organized as entries in a set of lists CACHE—Allows sharing of frequently referenced data LOCK—Allows serializing on shared resources, including list and cache structures If no activity occurs against a structure from any connected system, its type is listed as UNK (for unknown).
NAME	Name of the structure, up to 16 characters long A structure and its attributes (maximum size for example), are specified in the coupling facility resource management (CFRM) policy. The first subsystem or application that connects to the structure allocates it in the coupling facility. When you have multiple instances of the same structure, each instance is considered unique and is listed separately in the Structure Summary section. The Structure Activity section combines the activity data of all instances of a structure.
STATUS	Status of the structure, observed at end of interval Possible values for this field are as follows: ACTIVE — At the end of at least one interval, at least one system is connected to the structure; the ACTIVE values in the Status field can include either the PRIM or SEC qualifier PRIM — Rebuilt-old (primary) structure in a duplexing rebuild process; it is the first structure of the duplexed pair to be allocated SEC — Rebuilt-new (secondary) structure in a duplexing rebuild process; it is the second structure of the duplexed pair to be allocated INACTV — Structure is allocated in the coupling facility but is not connected to any system at the end of any interval UNALLO — No system is connected to the structure at the end of interval and the structure is no longer allocated in the coupling facility; the existence of the structure is known because it was active earlier in the recording interval If the structure becomes active during the report interval, an asterisk is also printed.
ENC *(PTF ??? applied)*	Whether the CF structure is encrypted Possible values are: YES— The structure is encrypted. NO— The structure is not encrypted and cannot be encrypted. You cannot encrypt CF structures that are used only by down-level systems in the Parellel Sysplex that don't support encryption of CF structures. NA— The encryption of lock structures is not supported.
SIZE	AMOUNT—Size of the structure, allocated in blocks of 4-K bytes² The structure size is either the value specified in the coupling facility resource management (CFRM) policy or the value specified at allocation time, whichever is greater. % OF CF—Percentage of total coupling facility storage that is allocated to the structure
CPU % OF CF	Percentage of coupling facility’s CPU busy time that is attributable to this structure Warning Note This percentage reflects the CPU consumption of requests that originated from all z/OS systems that are connected to the coupling facility. However, the metrics related to requests in this section cover only the systems that are included in the input SMF records. Some of the CPU busy time is not attributable to any structure, so the sum of this column on the SUMMARY line is less than 100%. This field is applicable only for coupling facility level 15 and higher.
REQUESTS	PER SEC—Rate per second of completed requests that are directed to the structure Graph is scaled such that the bar of the structure having the highest rate occupies the full width of the column. COUNT—Number of completed requests that are directed to the structure % OF CF—Percentage of completed requests against the structure, compared with the total number of requests against all structures SERVICE TIME—Average number of microseconds that are required to complete a request (excluding queue time) Graph is scaled such that the bar of the structure having the longest service time occupies the full width of the column.
LST/DIR ENTRIES TOT/CUR	Pair of numbers that provide information about list entries or cache directory entries For list or lock structures, the first number is the total number of list entries in the structure. For cache structures, the first number is the total number of directory entries in the structure. For list or lock structures, the second number is the average number of list entries in use at the end of the interval. For cache structures, the second number is the average number of directory entries in use at the end of the interval.³
DATA ELEMENT - TOT/CUR	Pair of numbers that provide information about list and cache data elements For list or lock structures, the first number is the total number of list elements in the structure. For cache structures, the first number is the total number of data elements in the structure. For list or lock structures, the second number is the average number of list elements in use at the end of the interval. For cache structures, the second number is the average number of data elements in use at the end of the interval.³
LOCK ENTRIES - TOT/CUR	Pair of numbers that provide information about lock table entries for lock structures or serialized list structures The first number is the total number of lock table entries for the structure. The second number is the average non-zero lock table entry count at the end of the interval.³
DIRECTORY RECLAIMS	Number that provides the average number of directory reclaims for a cache structure Directory reclaim activity indicates a shortage of directory entries. A shortage of directory entries causes the coupling facility to reclaim already used directory entries that are associated with unchanged data. As a result, the copy of the data in the coupling facility is invalidated, and must be reread from DASD and registered to the coupling facility again.³
SUMMARY	Values on this line are either the total or the average of values of all instances of all structures If different structure instances exist at different ends of interval, totaling their sizes and percentages of coupling facility storage is meaningless. In this case, N/A is printed.
SCM STRUCTURE SUMMARY
TYPE	First user connecting to an SCM structure specifies its type Possible values for this field are as follows: LIST—Allows users to share data organized as entries in a set of lists CACHE—Allows sharing of frequently referenced data LOCK—Allows serializing on shared resources, including list and cache structures If there is no activity against a structure from any connected system, its type is listed as UNK (for unknown).
STRUCTURE NAME	Name of the structure, up to 16 characters long A structure, and its attributes (maximum size, for example), is specified in the coupling facility resource management (CFRM) policy. The first subsystem or application that connects to the structure allocates it in the coupling facility. When there are multiple instances of the same structure, each instance is considered unique and listed separately in the Structure Summary section. In the Structure Activity section, the activity data of all instances of a structure is combined.
ALGORITHM	Type of algorithm used by the coupling facility to control the movement of structure objects between real storage and SCM: KeyPrty1: KeyPriority1 Unknown
SCM	MAX—Maximum amount of SCM that this structure can use, in bytes %USED—Percentage of the maximum amount of SCM in use by this structure
AUGMENTED	EST.MAX—Estimated maximum amount of coupling facility space that can be assigned as augmented space for this structure, in bytes %USED—Percentage of the estimated maximum augmented space in use by this structure
LST ENTRY	EST.MAX—Estimated maximum number of list entries that can reside in SCM for this structure CURRENT—Number of existing structure list entries that reside in SCM
LST ELEM	EST.MAX—Estimated maximum number of list elements that can reside in SCM for this structure CURRENT—Number of existing structure list elements that reside in SCM
SCM READ – CNT	CNT—Number of read operations against SCM, initiated either: By a reference to list structure objects residing in SCM As a prefetch operation to retrieve list structure objects in SCM that are expected to be referenced BYTE X'FERRED—Number of SCM read bytes transferred from SCM to the coupling facility AVG ST—Average service time per SCM read operation to SCM, in microseconds STD_DEV—Standard deviation of the service time for SCM read operations to SCM, in microseconds
SCM WRITE	CNT— Number of list write operations to SCM BYTE X'FERRED— Number of SCM write bytes transferred from coupling facility storage to SCM AVG ST— Average service time per SCM write operation to SCM, in microseconds STD_DEV— Standard deviation of the service time for SCM write operations to SCM, in microseconds
SCM AUX ENABLED	CMD—Number of commands that required coupling facility auxiliary frames %ALL—Percentage of SCM auxiliary enabled commands out of all requests for this structure
DELAYED FAULTS	CNT—Number of commands (and for multiple list-entry commands, the number of list item references) that were delayed due to a fault condition, resulting in required access to SCM %ALL—Percentage of delayed faults out of all requests for this structure
ASYNCHRONOUSLY DUPLEXED STRUCTURES—SECONDARY (PTF BQM1361, BQM1362, BQM1363, BQM1379, BQY1369, or BQY1371 applied)
TYPE	Type of structure
STRUCTURE NAME	Name of the structure
ASYNC DUPLEX CF OPERATIONS	PER SEC—Number (per second) of asynchronous duplex operations transmitted from the primary to the secondary structure, and completed in the secondary structure COUNT— Number of asynchronous duplex operations transmitted from the primary to the secondary structure, and completed in the secondary structure TRANSMIT TIME AVG—Average transmission time from the primary to the secondary structure, in microseconds STD DEV—Standard deviation of the transmission time from the primary to the secondary structure, in microseconds SERVICE TIME AVG— Average service time, in microseconds The service time is the sum of transmission time and the time to complete the operation in the secondary structure. STD DEV— Standard deviation of the service time from the primary to the secondary structure, in microseconds
ASYNC DUPLEX SYNC-UP REQUESTS	Sync-up requests are submitted to ensure that updates are completed in the secondary structure. Requests from all systems connected to the structure are included. PER SEC—Number (per second) of sync-up requests COUNT—Number of sync-up requests SUSPEND PER SEC— Number (per second) of sync-up requests that were suspended while waiting for operations to complete in the secondary structure. This number includes requests from all systems that are connected to the structure. COUNT— Number of sync-up requests that were suspended while waiting for operations to complete in the secondary structure. AVG— Average suspend time, in microseconds STD DEV— Standard deviation of suspend time

^{1 This field is applicable only for coupling facility level 15 and higher.}

^{2 The unit is in kilobytes (K), or in megabytes (M) if the size is a multiple of 1024 kilobytes or greater than 99999.}

^{3 If a field contains N/A, the data is not applicable to this structure type.}

Field descriptions of the summary sections of the Coupling Facility Activity Report

CMF MONITOR 6.1

On this page