A fix is available
APAR status
Closed as new function.
Error description
new function
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: RMF users. * **************************************************************** * PROBLEM DESCRIPTION: RMF support for asynchronous * * system-managed duplexing of coupling * * facility lock structures. * * * * Following RMF reports are extended: * * - Postprocessor CF Activity report * * - Monitor III CFACT report * * * * Following SMF record is extended: * * - SMF 74 subtype 4. * **************************************************************** * RECOMMENDATION: * **************************************************************** This new function APAR provides RMF support for the gathering and reporting of performance measurements collected for asynchronously duplexed CF lock structures. To expoit asynchronous system-managed duplexing the coupling facility must be running at CFLEVEL 21 or higher. For a full exploitation of this new support in a sysplex environment it is necessary to install this APAR on all systems of the sysplex. +--------------------------------------------------------------+ >>> POSTPROCESSOR CF ACTIVITY REPORT <<< The Postprocessor CF Activity report is modified: - A new Asynchronous CF Duplexing Summary section is added to the Usage Summary data collection. Per coupling facility it lists the asynchronously duplexed secondary lock structures and provides data related to the performance of async duplex CF operations and suspended asynchronous duplex requests. - The layout of the CF to CF Activity report section is reworked to show channel path details (operating mode, latency ..) for a remote coupling facility's sender channel paths. Report fields in the added Asynchronous CF Duplexing Summary: Field Heading Meaning ASYNC DUPLEX CF OPERATIONS TOTAL Number of asynchronous duplex operations transmitted from the primary to the secondary structure that completed in the secondary structure. TRANSMIT TIME AVG Average asynchronous duplex operation trans- mission time for operations sent from the primary to the secondary structure, in micro- seconds TRANSMIT TIME STD_DEV Standard deviation of the average asynchronous duplex operation transmission time. ASYNC DUPLEX SYNC_UP REQUESTS TOTAL Total number of user requests that requested sync up with the primary structure. User requests are summed up over all systems that have a connector to the structure. #SUSPEND Number of user requests that were suspended waiting for asynchronous duplex operations to complete in the secondary structure. Suspend counts are summed up over all sytsems that have a connector to the structure. SUSPEND TIME AVG Average accumulated suspend time for suspended requests waiting for asynchronous duplex operations to complete in the secondary structure, in microseconds. TRANSMIT TIME STD_DEV Standard deviation of the average accumulated suspend time. In case no structure is asynchronously duplexed the Asynchronous CF Duplexing Summary includes an informational message 'NO ASYNCHRONOUS CF DUPLEXING DATA AVAILABLE'. Report fields that have changed in the CF to CF Activity section: Field Heading Meaning RECEIVER SENDER TYPE CF link type of receiver/sender channel path. USE The number of receiver(sender paths of named type used for coupling facility communication). Detail data on sender channel paths may be blank if you are using data from an old RMF gatherer or have preallocated data from a previous RMF release. #REQ The sum of the following signals which have been sent from the subject CF to the remote CF: - Number of halt execution signals. - Number of ready to complete signals. - Number of ready to execute signals. - Number of request suppression signals. - Number of request for suppression accepted signals. AVG/SEC Average number of signals/messages per second. SERVICE TIME AVG The average service time in microseconds for all kind of signals which have been sent from the subject CF to the remote CF, including redrives, excluding any delay time. R/S R Receiver channel path. S Sender channel path. +--------------------------------------------------------------+ >>> MONITOR III CFACT REPORT <<< The structure status indicator (column ST) displayed in the Monitor III CFACT report indicates whether this structure is the primary or secondary instance of an asynchronously duplexed structure: PA Structure is the rebuild-old (primary) structure in an asynchronous duplexing rebuild process. SA Structure is the rebuild-new (secondary) structure in an asynchronous duplexing rebuild process. +--------------------------------------------------------------+ >>>>> SMF RECORD TYPE 70 TO 79 - RMF PRODUCT SECTION <<<<< The SMF record level change number SMFxxSRL at offset 51 (x33) changes to 124 (x7C). >>>>> SMF RECORD TYPE 74 SUBTYPE 4 - CF ACTIVITY <<<<< The Header/Self-defining section is extended by new triplet fields (offset/length/number): OFFSET NAME LEN FORMAT DESCRIPTION ... 116 x74 SMF744AO 4 binary Offset to Asynchronous CF Duplexing data section 120 x78 SMF744AL 2 binary Length of Asynchronous CF Duplexing data section 122 x7A SMF744AN 2 binary Number of Asynchronous CF Duplexing data sections The Structure Data Section is changed. OFFSET NAME LEN FORMAT DESCRIPTION 29 x1D R744QFL1 1 binary Status Flag Bit Meaning when set 0 Duplexing is active using system-managed asynchronous duplexing 1-7 Reserved The Request Data Section is changed. OFFSET NAME LEN FORMAT DESCRIPTION 25 x19 R744SFLG 1 binary Status Flag Bit Meaning when set ... 2 Structure is capable to participate in asynchronous duplexing 3 Structure is in the duplexing active state 4 Structure is primary instance of an asynchronously duplexed structure 5 Structure is secondary instance of an asynchronously duplexed structure 6-7 Reserved 388 x184 R744SIAD 2 binary Index to Asynchronous CF Duplexing data section. This field is zero if there is no Asynchronous CF Duplexing data available. 390 x186 R744SADN 2 binary Number of Asynchronous CF Duplexing data sections. 392 x188 R744SIXC 4 binary Number of asynchronous duplex requests that requested sync up with the primary structure. (Valid if bit 1 of R744SXFL is set.) 396 x18C R744SXSC 4 binary Number of asynchronous duplex requests that were suspended waiting for the operations to complete in the secondary structure of the currently duplexing instance. (Valid if bit 1 of R744SXFL is set.) 400 x190 R744SXST 8 binary Summed suspend time, in microseconds, for suspended requests that were waiting for the asynchronous duplex operation to complete in the secondary structure of the currently duplexing instance. (Valid if bit 1 of R744SXFL is set.) 408 x198 R744SXSQ 8 binary Square of summed suspend time, in square of microseconds, for suspended requests that were waiting for the asynchronous duplex operation to complete in the secondary structure of the currently duplexing instance. (Valid if bit 1 of R744SXFL is set.) 416 x1A0 R744SADO 8 binary Number of asynchronous duplex operations that were delayed because the primary structure was unable to accept new requests either becauce it could not forward requests to the secondary CF or because the secondary CF could not process incoming requests.(Valid if bit 0 of R744SXFL is set.) 420 x1A4 R744SADR 8 binary Number of asynchronous duplex requests that experienced a delayed operation because the primary CF was unable to accept new requests. (Valid if bit 0 of R744SXFL is set.) 424 x1A8 R744SQCH 1 binary Asynchronous duplex operation queue characteristic. The number number of queue entries is the product of 4096*2**R744SQCH 425 x1A9 R744SXFL 1 binary Bit Meaning When set 0 Data for primary instance of asynchronous duplexed structure is valid 1 Data for secondary instance of asynchronous duplexed structure is valid 2-7 Reserved 426 x1AA 122 Reserved The Remote Data Section is changed. OFFSET NAME LEN FORMAT DESCRIPTION 48 x30 R744RPGS 1 binary Receiver path group size : The following field is available eight times for eigth possible receiver/peer channel paths. 104 x68 R744RTAP 5 EBCDIC Channel path type acronym. A CHPID type is provided for each active receiver/peer message path in the path group. The number of valid entries is equal to the receiver path group size. The following field is available eight times for eigth possible receiver/peer channel paths. 152 x98 R744RIDP 1 binary Channel path identifier for receiver/peer channel paths. The range of values is X'00' to X'FF'. : 162 xA2 R744RCPN 2 binary Number of channel path data sections for channel paths of type CIB, CFP or CS5 connected to this remote CF. This includes the receiver/peer channel paths over which signals may be sent from the subject CF to this remote CF and the sender/peer channel paths returning signals from this remote CF to the subject CF. The count matches the number of subsequent channel path data sections associated with this remote CF. 164 xA4 R744RSGS 1 binary Sender path group size. 165 xA5 3 Reserved The following field is available eight times for eigth possible sender/peer channel paths. 168 xA8 R744RSAP 5 EBCDIC Channel path type acronym. A CHPID type is provided for each active sender/peer message path in the path group. The number of valid entries is equal to the sender path group size. The following field is available eight times for eigth possible sender/peer channel paths. 208 xD0 R744RSID 1 binary Channel path identifier for sender/peer channel paths. The range of values is X'00' to X'FF'. 216 xD8 R744RSC 4 binary Number of subchannels associated with the remote CF. 220 xDC R744RAMC 4 binary Number of asynchronous messages that are sent to this remote CF. The count includes the number of asynchronous commands that are sent and excludes path management commands and redrives of asynchronous commands. 224 xE0 R744RAMST 8 binary Total amount of service time for asynchronous messages sent to this remote CF, in microseconds. 232 xE8 R744RAMSQ 8 binary Total amount of squares of service time for asynchronous messages sent to this remote CF, in square of microseconds. 240 xF0 R744RAMPB 4 binary Asynchronous message path busy count. 244 xF4 R744RAMNS 4 binary Asynchronous message no subchannel count. The Channel Path Data Section is changed. OFFSET NAME LEN FORMAT DESCRIPTION 11 xB R744HCHF 1 binary Status Flag Bit Meaning when set 0 ... 1 Channel path is a sender channel 2-7 Reserved The Asynchronous CF Duplexing Data Section is added. OFFSET NAME LEN FORMAT DESCRIPTION 0 x0 R744AFO 8 binary The most current failed operation sequence number. 8 x8 R744AHEO 8 binary Highest operation sequence number that can be executed and completed in the secondary CF. 16 x10 R744ALAOH 8 binary Highest sequence number of the operation that has been executed in the primary structure. (Valid if bit 4 of R744SFLG is set.) 24 x18 R744ALAOSH 8 binary Highest sequence number of the operation that has completed in the primary structure and has been recognized by the secondary structure. 32 x20 R744ALCOH 8 binary Highest sequence number of the operation that has completed in the secondary structure. (Valid if bit 5 of R744SFLG is set.) 40 x28 R744ALCOPH 8 binary Highest sequence number of the operation that has completed in the secondary structure and that has been recognized by the primary structure. 48 x30 R744ALAO 8 binary Number of asynchronous duplex operations that have been executed in the primary structure. (Valid if bit 4 of R744SFLG is set.) 56 x38 R744ALAOS 8 binary Number of asynchronous duplex operations that have executed in the primary and have been recognized in the secondary structure. 64 x40 R744ALCO 8 binary Number of asynchronous duplex operations transmitted from the primary to the secondary structure that completed in the secondary structure. (Valid if bit 5 of R744SFLG is set.) 72 x48 R744ALCOP 8 binary Number of asynchronous duplex operations that have been completed both in the primary and in the secondary structure which has been recognized by the primary structure. 80 x50 R744ATPOCT 8 binary Total number of asynchronous duplex operations that have been transmitted from the primary to the secondary structure. 88 x58 R744ATPOC 8 binary Number of asynchronous duplex operations transmitted from the primary to the secondary structure in this interval. 96 x60 R744ARCPOT 8 binary Total number of asynchronous duplex operations that have completed in the secondary and have been recognized as complete to the primary structure. 104 x68 R744ARCPO 8 binary Number of asynchronous duplex operations transmitted from the primary to the secondary structure and recognized as complete to the primary structure in this interval. 112 x70 R744ACQSC 8 binary Number of stalls in the processing of the secondary operation queue. 120 x78 R744APDT 8 binary Total amount of primary delay time for asynchronous duplex operations, in microseconds. The primary delay time is the elapsed time in the primary CF between the assignment of the operation to the queue buffer and the first attempt to send the operation to the secondary CF 128 x80 R744APDQ 8 binary Total amount of squares of primary delay time for asynchronous duplex operations in square of microseconds. 136 x88 R744AMDT 8 binary Total amount of message delay time for asynchronous duplex operations, in microseconds. The message delay time is the elapsed time from the first attempt to send the asynchronous duplex operation in the primary CF to the time that the secondary CF assigns the asynchronous duplex operation to a secondary queue entry. 144 x90 R744AMDQ 8 binary Total amount of squares of message delay time for asynchronous duplex operations, in square of microseconds. 152 x98 R744AQDT 8 binary Total amount of secondary queue delay time for asynchronous duplex operations in microseconds. The secondary queue delay time is the elapsed time from the time the asynchronous duplex operation is assigned to a secondary queue entry to the time of completion of the asynchronous duplex operation. 160 xA0 R744AQDQ 8 binary Total amount of squares of secondary queue delay time for asynchronous duplex operations in square of microseconds. 168 xA8 R744AQST 8 binary Total amount of secondary queue stall time for asynchronous duplex operations, in microseconds. 176 xB0 R744AQSQ 8 binary Total amount of squares of secondary queue stall time for asynchronous duplex operations in square of microseconds. 184 xB8 R744ACDT 8 binary Total amount of secondary reported completion delay time for asynchronous duplex operations, in microseconds. The secondary reported completion delay time is the elapsed time in the secondary CF, from the time the asynchronous duplex operation completes in the secondary to the time that the completion is reported to the primary. 192 xC0 R744ACDQ 8 binary Total amount of squares of secondary reported completion delay time for asynchronous duplex operations, in square of microseconds. 200 xC8 R744ARDT 8 binary Total amount of response delay time for asynchronous duplex operations, in microseconds. The response delay time is the elapsed time from the launch of the operation response in the secondary CF to the time that the primary CF recognizes the response. 208 xD0 R744ARDQ 8 binary Total amount of squares of response delay time for asynchronous duplex operations in square of microseconds. 216 xD8 R744AOTT 8 binary Total amount of operation transmission time for operations sent from the primary to the secondary structure, in microseconds. (Valid if bit 5 of R744SFLG is set.) 224 xE0 R744AOTQ 8 binary Total amount of squares of operation transmission time, in square of microseconds. (Valid if bit 5 of R744SFLG is set.) 232 xE8 R744ASTT 8 binary Total amount of service time to transfer the asynchronous duplex operations to the secondary structure and complete the operations in the secondary structure, in microseconds. (Valid if bit 5 of R744SFLG is set.) 240 xF0 R744ASTQ 8 binary Total amount of squares of service time to transfer the asynchronous duplex operations to the secondary structure and complete the operations in the secondary structure, in square of micro- seconds. (Valid if bit 5 of R744SFLG is set.)
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
OA49148
Reported component name
RMF
Reported component ID
566527404
Reported release
7A0
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2015-10-16
Closed date
2016-10-20
Last modified date
2017-07-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA83107 UA83108
Modules/Macros
ERBMFBSR ERBMFIZS ERBMFL3J ERBMFL3V ERBPCTBL ERBPPCOM ERBRMFPP ERBR744 ERBSCAN ERBSMFI ERBSMF74 ERB3GCFC ERB3GCFI ERB3GCFS ERB3GCTC ERB3GSMF ERB3GSMM ERB3RCFA ERB3RTBR ERB4CFA1 ERB4MAIN
SA380667XX | SC342665XX |
Fix information
Fixed component name
RMF
Fixed component ID
566527404
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7A0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7A0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
19 July 2017