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


After the Duplex Established Phase

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

  • If a loss of connectivity occurs to the old structure, MVS™ does not present the LOSSCONN event. Once the switch has completed, the old structure will be deallocated and the former new structure will not have experienced a loss of connectivity. If appropriate, another duplexing rebuild might occur.
  • If a loss of connectivity occurs to the new structure after a switch has been requested, MVS defers presenting the LOSSCONN event until after the switch to the new structure is complete. At that time, the policy will determine whether another duplexing rebuild should be attempted.

    If another duplexing rebuild is not automatically initiated, the deferred LOSSCONN event might indicate to delay action, and if so, MVS will later present either an XES Recommended Action event or, for an MVS-initiated structure rebuild based on REBUILDPERCENT, a Rebuild Quiesce event.

    If another duplexing rebuild is automatically initiated, the deferred LOSSCONN event will be presented after the Rebuild Process Complete event, followed by a Rebuild Quiesce event indicating that MVS is initiating a duplexing rebuild. Those connectors who had lost connectivity to the former new structure are not able to participate in the duplexing and will receive a LOSSCONN event. The system delivers the Lossconn Percentage Notification event indicating the percentage loss of connectivity, to all active connectors. The connectors' protocol determines how the percentage is handled.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014