Limited support

   

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for CMF 6.3.

Field descriptions of the Structure Activity Section

The following figure shows an example of the Structure Activity Section of the Coupling Facility Activity Report.
PRODUCED BY CMF ANALYZER (v.r.mm  RSL yymm )       COUPLING FACILITY ACTIVITY REPORT                    RPTSEQ     3 PAGE     17
BMC SOFTWARE, INC.                                           XYZ COMPANY                                REPORT DATE: dd mmm yy 16.06
ACTL dd mmm yy 11.45.00  dd mmm yy 14.30.00                  HQ LOCATION                                SYSTEM ID: ESAJ     Z v.rr.n


BASED ON REC TYPE/# RECS/# SAMPLES/REC HOURS:  74-4/130/11.6K/16.13
COUPLING FACILITY = CF16      ---------------------  STRUCTURE ACTIVITY SECTION  ---------------------------------------------------
-------------------------------------------------- STRUCTURE = DFHCFLS_DFHRSTAT  ---------------------------------------------------
 TYPE = LIST    SIZE = 96291K     ENCRYPTED = NO
 SYSTEM  ------------------ REQUESTS -------------------       -------------- QUEUED REQUESTS ---------------
   NAME    TYPE    PER     COUNT    % OF  -SERVICE TIME--       DELAY        #      %  ----- DELAY TIME ------
                   SEC              ALL     AVG   STD DEV       REASON       REQ   REQ   /REQ    S DEV    /ALL
 -------- ------- ------- --------- ----- ------- -------       -------- ------- ----- ------- ------- -------
 SJSC     ALL           0         0     0       0       0       NO SCH         0     0       0       0       0
            SYNC        0         0     0       0       0
            ASYNC       0         0     0       0       0
            CNVAS       0         0     0                       DUMP           0     0       0       0       0
            SUPPR       0         0     0

 -------- ------- ------- --------- ----- ------- -------       -------- ------- ----- ------- ------- -------
 SUMMARY  ALL           0         0     0       0       0       NO SCH         0     0       0       0       0
            SYNC        0         0     0       0       0
            ASYNC       0         0     0       0       0
            CNVAS       0         0     0                       DUMP           0     0       0       0       0
            SUPPR       0         0     0

The following table describes each field on the Structure Activity Section of the Coupling Facility Activity Report.

Field

Description

STRUCTURE

Name of the structure, up to 16 characters long

Note

When there are multiple instances of the same structure, the activity data of all instances is combined.

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 there is no activity against a structure from any connected system, its type is listed as UNK (for unknown).

SIZE

Structure size in either K or M, if the size in K is a multiple of 1024 or greater than 99999

ENCRYPTED (PTF BQM1388 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 if they are used only by low-level systems in the Parallel Sysplex that do not support encrypting CF structures.
  • NA—The CF structure does not support encrypting lock structures.

SYSTEM NAME

Name of the system that is originating the requests against this structure

REQUESTS - TYPE

Type of requests: synchronous (SYNC), asynchronous (ASYNC), originated as synchronous but converted to asynchronous (CNVAS), suppressed (SUPPR)

ALL is the total for all request types.

REQUESTS - PER SEC

Rate per second of requests that originated from a system against this structure, viewed by request type

REQUESTS - COUNT

Number of requests that originated from a system against this structure, viewed by request type

REQUESTS - % OF ALL

Percentage of requests of a type that originated from a system, compared with the total number of requests from all systems against this structure

REQUESTS - SERVICE TIME - AVG, STD DEV

Average number of microseconds that are required to complete a request (excluding queue time) and its standard deviation

The service time of synchronous-converted-to-asynchronous (CNVAS) requests is included in that of asynchronous (ASYNC) requests.

QUEUED REQUESTS - DELAY REASON

Reason that a request gets queued

Possible values for this field are as follows:

  • NO SCH No coupling facility subchannel available
  • DUMP Structure being dumped
  • PR WT— Duplexed request was holding a subchannel while waiting for a peer request to be started
  • PR CMP— One of the two duplexed operations is completed, but the completed subchannel remains unavailable for use until the peer operation is completed

QUEUED REQUESTS - # REQ

Total number of requests to this structure that are delayed in this interval

QUEUED REQUESTS - % REQ

Percentage of requests to this structure that are 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 structure in microseconds

This number indicates how delays are affecting overall request activity to the structure.

EXTERNAL CONTENTION - REQ TOTAL

Total number of requests to the structure 1

EXTERNAL CONTENTION - DEFERRED

Number of requests to the structure that were unable to be completed within the request issuers thread 1

EXTERNAL CONTENTION - TOTAL

Number of requests to the structure that were delayed due to lock contention 2

This number is a subset of DEFERRED.

EXTERNAL CONTENTION - FALSE

Number of requests to the structure that were delayed due to false lock contention 2

False lock contention occurs when a user-supplied hash value is used to map a lock request to a lock entry and multiple unique lock requests hash to a single lock table entry. This number is a subset of the total lock contention count.

Note

A high false lock contention count indicates either a poor hashing algorithm or an inadequate number of lock table entries.

DATA ACCESS - READS

Total number of read hits for a cache structure read request for the interval 3

DATA ACCESS - WRITES

Total number of write hits for a cache structure write request for the interval 3

DATA ACCESS - CASTOUTS

Total number of castouts for a cache structure for the interval 3

Castouts occur when changed data is written to DASD. The castout count can indicate the volume of changed data being removed from a store-in cache structure, such as the IBM Db2 global buffer pool structures.

DATA ACCESS - XI’s

Number of times that a data item residing in a local buffer pool was marked invalid by the coupling facility 3

The XI count indicates the amount of data sharing among the users of the cache structure and the amount of write or update activity against the cache data.

1 This field is applicable only to serialized list or lock structures.

2 This field is applicable only to lock structures.

3 This field is applicable only to cache structures.

Was this page helpful? Yes No Submitting... Thank you

Comments