Receiving Answer Area Information from IXLCONN REBUILD

At the completion of its processing, IXLCONN REBUILD returns the following information in the connect answer area, mapped by IXLYCONA.

CONACONTOKEN

Connect token that uniquely identifies the connection to a new structure within the sysplex. This CONTOKEN is temporary and is not the same CONTOKEN value that IXLCONN returned for the original structure.

During the rebuilding process, use the temporary CONTOKEN only when using mainline services IXLCACHE, IXLLIST, IXLLOCK, IXLRT, IXLSYNCH, or IXLFCOMP to the new structure.

For all other coupling facility requests (IXLDISC, IXLEERSP, and IXLREBLD), use the CONTOKEN returned from IXLCONN for the original structure. When the system reports that the rebuilding process is complete (Rebuild Complete event), discard the temporary connect token and use the CONTOKEN returned from IXLCONN for the original structure to access the new structure.

For successful IXLCONN REBUILD requests for cache and list structures, the system revalidates the CONTOKEN returned from IXLCONN for the original structure. At this stage, users can make IXLCACHE or IXLLIST structure requests. Accessing the original cache or list structure allows users to move data between the original and new structures. Lock users cannot use the CONTOKEN for the original structure to access the original structure during rebuild.

CONACONID

A connection identifier. The connection identifier is the same as that for the original structure.

CONAFLAGS

Connection status flags.

CONASTRUCTUREATTRFLAGS

Structure type attributes. Users must verify that the attributes for the structure are acceptable. Otherwise, they should disconnect or stop the structure rebuild.

CONASTRUCTUREVERSION

Structure version number. The structure version number will be greater than the structure version number of the old structure.

CONACONNECTIONVERSION

Connection version number. The connection version number will be equivalent to the connection version number of the original connection.

CONAVECTORTOKEN and CONAVECTORLEN

For TYPE=CACHE or TYPE=LIST with list monitoring structures, a vector token and vector length used to identify the user's local vector. Use the new vector token from IXLCONN REBUILD after the rebuild process is complete. However, if the rebuild process is stopped, use the vector token returned on the original IXLCONN request.

See the IXLYCONA macro in z/OS® MVS™ Data Areas in the z/OS Internet library.

The connector that allocates the new structure receives an indication in the IXLCONN answer area (CONACONNALLOC field). Subsequent connectors receive an indication that they are connected to the new structure through the CONAREBUILD field of the answer area.

The event exit for the connector might receive Rebuild Existing Connection events before the IXLCONN REBUILD request for the new connection completes.

For cache or unserialized list structures, the event exit for existing connectors might receive Rebuild New Connection events after the IXLCONN REBUILD request for the new connection completes. Users of cache and unserialized list structures can rebuild information into the new structures as soon as the IXLCONN REBUILD request completes. Thus, list and cache users are able to access the original and new structure before they receive the Rebuild Connects Complete event in their event exits. (The Rebuild Connects Complete event indicates that all users have issued IXLCONN REBUILD for a structure rebuild. The Rebuild Connects Complete event is not presented to users who have issued IXLCONN REBUILD for a duplexing rebuild.)

List and cache users can perform copy or read operations for cache or list data in the original structure to help with rebuilding; however, IBM® recommends that you do not change data in the original structure during the rebuilding process. In the event of a REBUILD STOP request, you will need to use the original structure once again.