CF Data Sharing attributes

Use the CF Data Sharing attributes to create table views, charts, and situations that monitor coupling facility characteristics for VSAM cache structures and OSAM cache structures.

Actual Structure Size The current size of a structure allocated in the Coupling Facility. This actual structure size, which you define in the CFRM policy, is allowed to grow to the Maximum Structure Size. Valid format is an integer.

CF Request Count The number of active Coupling Facility requests that are possibilities for Fence processing. Valid format is an integer.

CF Structure Fence and Waiter Queue The FW Queue that is established if an error occurs. Coupling Facility requests are placed on the Fence/Waiter Queue until the error is resolved. Valid format is an integer.

Connection Name The name of the connection between an IMS coupling facility and an MVS address space. Valid format consists of up to 16 alphanumeric characters. Example: IRLM1$$$ARLM001.

Data Sharing Status The status of the Coupling Facility structure. Data Sharing Status is active unless an error exists, in which case, data sharing stops. Otherwise, the valid format consists of up to 30 alphanumeric characters.

Data Sharing Type Identifies a structure as either an OSAM or VSAM cache structure.

Global Buffer Count The number of database buffers (or blocks) for which data sharing is implemented. For each block of shared data read by any IMS connected to the Coupling Facility, an entry is made in the corresponding VSAM or OSAM buffer invalidate structure. This field is the count of such directory entries for the cache structure. Valid format is an integer.

IMSID The IMS Subsystem identifier. Valid format consists of up to four alphanumeric characters. Example: I61A.

Mapping Version An internal column used to indicate the mapping version of the data row. Valid format is an integer.

Maximum Structure Size The maximum size of the structure expressed in kilobytes. The size of the VSAM and OSAM structures required depends on the number of database buffers that are used in data sharing. To determine the actual structure size required, count the number of data sharing buffers for both VSAM and OSAM and enter these numbers in the TDEC field of the MVS cache structure size formula. Define the Maximum Structure Size to be larger than the actual current structure size allocated, in order to allow for future expansion.Valid format is an integer.

MVS System The MVS System Management Facility (SMF) identifier. Valid format consists of up to four alphanumeric characters. Example: SP11.

Originating System Identifier Fully identifies the originating IMS subsystem. Valid format consists of up to 32 alphanumeric characters. Example: I91A:SP22:IMS

Sequential Buffering Global Buffering CT The total number of OSAM database buffers that are cached in the Coupling Facility. In addition to buffer invalidation, IMS employs the Coupling Facility to cache the buffers for IMS OSAM Sequential Buffering databases. This is known as OSAM data caching. This field contains the total number of 2K coupling facility elements required to hold all cached OSAM buffers. More information related to OSAM data caching is on the next view. Valid format is an integer.

SES Lock Table Name The name of the lock table that IMS uses to implement sysplex data sharing. Valid format consists of up to 16 alphanumeric characters.

SES Structure Name Defined in the CFNAMES control Statement in the IMS proclib member DFSVSMxx. This name must match the name in the CFRM policy for each MVS image connecting to the Coupling Facility. This may indicate the reason a connection to a structure failed. Valid format consists of up to 16 alphanumeric characters.

Sysplex Identifier Indicates the originating sysplex for this request. Valid format consists of up to eight alphanumeric characters.

Timestamp The date and time when the monitoring agent retrieved the data. This attribute is intended for logging and reporting data collection times rather than for creating situations. To specify a time of day for monitoring, use attributes from the Universal Time or Local Time groups. See the Tivoli Enterprise Portal help for instructions on specifying timestamp attributes in situations and queries.