CFEE entry for coupling facility connection event exit

Entry:
CFEE
VIT option:
CFS
Event:
Event Exit Driven for a Connection to a Coupling Facility Structure
VIT processing module:
ISTRACCF
Control is returned to:
ISTFSXEV
This trace record is written when any of the following actions occurs:
  • A new connection is established to the coupling facility structure.
  • A connection to the coupling facility structure is terminated.
  • A connector loses read/write access to the coupling facility structure.
  • A state change occurs for the coupling facility structure.
  • A user sync point is set by a connector to the coupling facility structure.
  • A user sync point has been confirmed by all connectors to the coupling facility structure.
REQTEXT
Byte (hex)
Contents
00–03
Record ID: C"CFEE"
04
ID is the primary address space ID (ASID). This field is 0 if the ASID is greater than X'FF'.
05
0
06
Event identifier (see the mapping of IXLYEEPL in z/OS MVS Data Areas at z/OS® Internet Library for an explanation of this code.)
07
The event identifier in byte 06 determines the meaning of this field.
Event flags:
  • If byte 06 indicates a loss of connectivity event, use the following flags:
    Bit
    Meaning
    1... ....
    The rebuild process is in progress for the structure.
    .1.. ....
    The rebuild stop process is in progress for the structure.
    ..1. ....
    This event applies to the rebuild version of the structure.
    ...1 ....
    No action will be taken. MVS™ will determine action based on policy information.
    .... xxxx
    0
  • If byte 06 indicates an existing connection event, use the following flags:
    Bit
    Meaning
    1... ....
    The rebuild process is in progress for the structure.
    .1.. ....
    The rebuild stop process is in progress for the structure.
    ..1. ....
    This event does not pertain to a real connection but indicates that all existing connection events have been received.
    ...1 ....
    The connection identified is active.
    .... 1...
    The connection identified does not have access to the structure.
    .... .xxx
    0
  • If byte 06 indicates a disconnected or failed event, use the following flags:
    Bit
    Meaning
    1... ....
    The rebuild process is in progress for the structure.
    .1.. ....
    The rebuild stop process is in progress for the structure.
    ..1. ....
    This event applies to the rebuild version of the structure.
    ...1 ....
    The connection disconnected abnormally.
    .... xxxx
    0
  • If byte 06 indicates a rebuild existing connection event, use the following flags:
    Bit
    Meaning
    1... ....
    The rebuild process is in progress for the structure.
    .1.. ....
    The rebuild stop process is in progress for the structure.
    ..1. ....
    This event does not pertain to a real connection but indicates that all rebuild existing connection events have been received.
    ...1 ....
    The connection identified is active.
    .... xxxx
    0
  • If byte 06 indicates structure alter begin event, use the following flags:
    Bit
    Meaning
    1... ....
    The rebuild process is in progress for the structure.
    .1.. ....
    The rebuild stop process is in progress for the structure.
    ..1. ....
    Structure size will be altered.
    ...1 ....
    Entry-to-element ratio will be altered.
    .... xxxx
    0
  • If byte 06 indicates structure alter end event, use the following flags:
    Bit
    Meaning
    1... ....
    The rebuild process is in progress for the structure.
    .1.. ....
    The rebuild stop process is in progress for the structure.
    ..1. ....
    Attempt to alter structure size.
    ...1 ....
    Attempt to alter entry-to-element ratio.
    .... 1...
    Alter request able to meet all specified targets.
    .... .1..
    Alter request able to meet only some specified targets.
    .... ..xx
    0
  • If byte 06 indicates a recommended action, use the following flags:
    Bit
    Meaning
    1... ....
    The rebuild process is in progress for the structure.
    .1.. ....
    The rebuild stop process is in progress for the structure.
    ..1. ....
    Policy is available to determine action.
    ...1 ....
    Action is disconnect.
    .... xxxx
    0
  • For all other events, use the following flags:
    Bit
    Meaning
    1... ....
    The rebuild process is in progress for the structure.
    .1.. ....
    The rebuild stop process is in progress for the structure.
    ..1. ....
    VTAM® ignored this event.
    ...x xxxx
    0
08–0B
Structure object (CFSSTR) address
0C–0F
Event sequence number. Each event is assigned a unique sequence number.
10
The connection identifier for the subject of this event
11
Connection FSM State. Connection states are listed in the VTAM data map ISTCFCON.
12
Reason for starting rebuild (see the mapping of IXLYEEPL in z/OS MVS Data Areas at z/OS Internet Library for an explanation of this code).
13
Reason for stopping rebuild (see the mapping of IXLYEEPL in z/OS MVS Data Areas at z/OS Internet Library for an explanation of this code).
  • If byte 06 indicates a rebuild event, then this field contains the reason for stopping rebuild (see the mapping of IXLYEEPL in z/OS MVS Data Areas at z/OS Internet Library for an explanation of this code).
  • If byte 06 indicates structure alter end event, use the following flags:
    Bit
    Meaning
    1... ....
    Alter request failed because of structure failure.
    .1.. ....
    Alter request failed because of loss of connectivity.
    ..1. ....
    Alter request failed because of rebuild started.
    ...1 ....
    Alter request failed because ratios specified on alter request are not consistent with structure attributes.
    .... xxxx
    0
14–17
User Data 1

The contents of this field depend upon the event received and the state of the structure when the event was received.

If this event pertains to a user sync point, this field contains the connector-defined event for the user sync point set if a user sync point has been set.

If this event pertains to a disconnect or failed connection event, then this field contains the first 4 bytes of the connector-defined data specified in IXLDISC.

If this event pertains to a rebuild connects complete event, then this field contains the number of active connectors to the original structure.

If this event pertains to a rebuild event, other than rebuild connects complete, then this field contains the connector-defined reason for starting rebuild, if a connector-specified reason was given.

If this event pertains to alter begin event, then the first 2 bytes contain the target entry portion of the entry-to-element ratio. The second 2 bytes contain the target element portion of the entry-to-element ratio.

If this event pertains to an alter end event and the ratio was changed, then this field contains the current number of entries.

If this event indicates a structure state change, the first 2 bytes of this field contain a validity flag. The validity flag byte 14 contains:
Bit
Meaning
1... ....
Coupling facility operational level of the coupling facility in which the structure resides is valid. If this bit has been set, User Data 2 contains the coupling facility operational level for the coupling facility in which the structure resides.

Otherwise, this field contains all zeros.

18–1B
User Data 2

The contents of this field depend upon the event received and the state of the structure when the event was received.

If this event pertains to a user sync point, this field contains the connector-defined event for the user sync point confirmed if a user sync point has been confirmed.

If this event pertains to a disconnect or failed connection event, then this field contains the last 4 bytes of the connector-defined data specified in IXLDISC.

If this event pertains to a rebuild stop event, then this field contains the connector-defined reason for stopping the rebuild, if a connector-specified reason was given.

If this event pertains to a rebuild connects complete event, then this field contains the number of connectors that successfully connected to the rebuild structure.

If this event pertains to an alter begin event, then this field contains the target structure size.

If this event pertains to an alter end event and the ratio was changed, then this field contains the current number of elements. If the structure size was changed then this field contains the current structure size. If both ratio and size are changed, this field contains the current number of elements.

If this event indicates a structure state change and byte 14 (first byte of User Data 1 field) contains a value of X'80', this field contains the coupling facility operational level. This is the operational level of the coupling facility in which the structure resides.

Otherwise, this field contains all zeros.

1C–1F
Request parameter header (RPH) address