z/OS MVS Programming: Sysplex Services Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Handling a Failed IXLCONN REBUILD Request

z/OS MVS Programming: Sysplex Services Guide
SA23-1400-00

When an IXLCONN REBUILD request for structure rebuild is not successful, the connector has three options:
  • Disconnect from the old structure and let the rebuild continue.
  • Reissue the IXLCONN REBUILD request with one or more changed parameters, based on the return and reason code returned by the failed attempt. Note, however, that the more times you reissue the IXLCONN REBUILD request, the longer you are holding up the entire rebuild cycle for all connectors involved.
  • Stop the rebuild process. Note that if you choose to stop the rebuild process, the system will generate a Rebuild Stop event to be delivered to the event exits of the structure's connectors. The Rebuild Stop event will supersede any Rebuild Connect event that has not yet been delivered and may occur either before or after the connector has issued IXLCONN REBUILD to connect to the new structure.
When an IXLCONN REBUILD request for duplexing rebuild is not successful, the following occurs:
  • If the connector is connected to the old structure but is unable to connect to the new structure because of lack of connectivity to that coupling facility, the system initiates a fall back to the old structure for all connectors. (Duplexing rebuild assumes LESSCONNACTION=TERMINATE.) If the IXLCONN REBUILD request to connect to the new structure fails for any other reason, it is the responsibility of the user to either stop the rebuild or disconnect.
  • The system will attempt to duplex the structure in a different coupling facility if the active CFRM policy specifies DUPLEX(ENABLED) for the structure.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014