There are instances when a system remains defined in the couple data set as “active” even though measures have been taken to remove the system from the sysplex. For example, the last system removed from a sysplex with a VARY command remains defined in the couple data set as an “active” system. Before that system can rejoin the sysplex, it must be determined whether the sysplex should be reinitialized (implying the cleanup of residual system information). The following applies:

• In native MVS™ mode, when the system attempts to rejoin the sysplex, XCF is able to determine that the system is a new instance of the “active” system that is defined in the couple data set. As such, it can reinitialize the couple data set without requiring operator intervention.
• In a VM guest environment, woth OW31481 or OW32876 installed, when the VM guest system attempts to rejoin the sysplex, XCF determines whether the system is a new instance of the “active” system defined in the couple data set by verifying that:
  • Both systems are VM guests.
  • Both systems have the same system name.
  • The system status of the system identified in the couple data set has not been updated in a reasonable time frame prior to the attempt to rejoin the sysplex.

  If these conditions exist, XCF will initialize the couple data set without requiring operator intervention.