Successful Completion of a Connection

IXLCONN returns the following information in the ANSAREA area:

CONACONTOKEN

Token that uniquely identifies the connection within the sysplex. You must specify the CONACONTOKEN value returned by IXLCONN as input to other structure requests such as IXLCACHE, IXLLIST, or IXLLOCK.

Whenever the following events occur, the system invalidates your CONACONTOKEN:

If the structure is in certain phases of the user-managed rebuild or duplexing processes. (Note that the CONTOKEN is not invalidated during system-managed processes.)
If your connection disconnects or fails.
If a structure fails, or a failure of the coupling facility occurs.
If you lose connectivity to a structure.

You cannot access the structure when the CONACONTOKEN is invalidated.

CONACONNAME

Name that uniquely identifies the connection to the structure. If you do not specify a name on IXLCONN, the system generates a unique name.

CONACONID

A connection identifier to identify this active connection. If the active connection becomes failed-persistent, the connection retains the same connection identifier. If the failed persistent connection is able to reconnect, the CONACONID remains the same.

CONASTRUCTUREATTRIBUTES

Structure specific attributes. You must verify that the attributes for the structure are acceptable. If the attributes are not acceptable, you can release your connection by issuing IXLDISC or you can attempt to rebuild the structure.

If the connector caused the structure to be allocated, the CONACONALLOC bit will be on in CONASTRUCTUREATTRFLAGS.

See Verifying Structure Attributes for the type of attribute information the system returns for a cache, list, and lock structure.

Byte 2 of CONASTRUCTUREATTRIBUTES contains system-managed duplexing information, indicating whether the structure is being duplexed by system-managed duplexing rebuild, and if so, whether the primary structure is failure-isolated from the secondary structure.

CONAFLAGS

Connection status flags that indicate whether the structure is in a special state. The special states include:

Rebuild (CONAREBUILD)
Rebuild stop (CONAREBUILDSTOP)
User sync point event (CONAUSYNCEVENTSET)
Alter in progress (CONAALTERINPROGRESS)
Whether the connection is new or has been reconnected (CONARECONNECTED).

When connecting during a user-managed structure rebuild process or when a user sync point is set, you are expected to participate in the process indicated by the CONAFLAGS and respond to the event. The connect answer area contains the information that you would have received in the event exit if you had been connected to the structure at the time of the event.

If you connect to a structure that is in the process of being altered, the CONAALTERINFO area contains information about changes being made to the structure.

CONAREBUILDFLAGS

Flags for a connection that occurs during user-managed duplexing rebuild processing. Information includes:

Duplexing rebuild in progress (CONAREBUILDDUPLEX)
Duplexing rebuild switch in progress (CONAREBUILDDUPLEXSWITCH)

CONACONNECTIONVERSION

Connection version number. Each time you connect to a version of the structure, your connection version number increases. For example, if a failed-persistent connection reconnects to a structure, the connection version number is incremented and is greater than the connection version number of the original connection. However, if you connect with the REBUILD option, the connection version number is the same as the original connection version number. The rebuild connect request does not define a new connection; at rebuild connect time the original connection must be active.

CONASTRUCTUREVERSION or CONAPHYSICALSTRUCTUREVERSION

Physical structure version number. Connectors that specified or defaulted to IXLCONN ALLOWAUTO=NO use this field to uniquely identify a physical instance of a structure. Connectors that specified IXLCONN ALLOWAUTO=YES must use this field, along with CONAPHYSICALSTRUCTUREVERSION2, to identify a physical instance of the structure. Each time a structure is allocated for the same structure name, the version number for the structure increases. For example, when a new structure is allocated during rebuild, the structure version number of the new structure is greater than the structure version number of the original structure. See Understanding the Structure Version Numbers.

CONAPHYSICALSTRUCTUREVERSION2

Second physical structure version number. Applicable only for connectors that specified IXLCONN ALLOWAUTO=YES. This field, along with CONAPHYSICALSTRUCTUREVERSION, uniquely identifies a physical instance of the structure. See Understanding the Structure Version Numbers.

CONALOGICALSTRUCTUREVERSION

Used for diagnostic purposes.

CONAFPCONNSNOTINPOLICY

Information about failed-persistent connections, specifically the number of failed-persistent connections that are defined in the structure, but which could not be reconciled into the policy because the number of CONNECT records in the CFRM active policy is too small. This situation occurs only when all systems fail and the first system is re-IPLed into the sysplex with a CFRM policy that supports a smaller number of CONNECT records. The system issues warning message IXC502I.

CONAUSERSYNCPOINTEVENT

A user sync point event if one was defined by an existing connector using the IXLUSYNC macro. You are expected to perform the processing required for the event and then provide a confirmation using the IXLUSYNC macro. See Using IXLUSYNC to Coordinate Processing of Events.

CONAREBUILDINFO

Information for a connection that connects during user-managed structure rebuild process. You are expected to participate in the processing by responding to events. Further, for user-managed duplexing rebuild, once the structure is in the Duplex Established phase, you are expected to maintain the synchronization of the data in the duplexed structure. of duplexed structure data. See Structure Rebuild Processing.

CONAALTERINFO

Information for a connection that connects during structure alter. The information is valid when the alter flag in CONAFLAGS (CONAALTERINPROGRESS) is set.

CONAFACILITYARRAY

If this connection allocated the structure (CONACONNALLOC is set), the connect answer area contains information about each coupling facility in which the system attempted to allocate the structure in order to explain why the structure was allocated in the coupling facility that it was. If the connect request failed because no suitable coupling facility was found in the preference list (reason code IXLRSNCODENOFAC and CONACONNALLOC not set), this array indicates which coupling facilities were attempted and describes why each was not suitable. A reason code (CONAFACILITYRSNCODE) is provided for each coupling facility in which the system could not allocate the structure, which explains why the structure was not allocated in that coupling facility.

CONACFACILITYINFO

Current information about the coupling facility in which the structure is allocated. The information includes the operational level of the coupling facility, space utilization, and model-dependent limits.

CONAESTIMATEDMAXENTRIES

Estimated maximum number of entries supported by the structure. Using both real storage and storage-class memory, you can allocate at most this number of entries to the structure. This count is only an estimate and therefore only substantially accurate. Connectors must not rely on the availability of exactly this number of entries for use. The number is zero when storage-class memory is not associated with the structure. End of change

CONAESTIMATEDMAXELEMENTS

Estimated maximum number of elements supported by the structure. Using both real storage and storage-class memory, you can allocate at most this number of elements to the structure. This count is only an estimate and therefore only substantially accurate. Connectors must not rely on the availability of exactly this number of elements for use. The number is zero when storage-class memory is not associated with the structure. End of change