If PRIMARY stops updating its status, the following events occur, based on the policy.

• When the failure detection interval specified on the INTERVAL keyword in PRIMARY's COUPLExx parmlib member elapses, MVS™ on BACKUP1 detects a status update missing condition for PRIMARY.
• BACKUP1 waits 5 seconds. If the status update missing condition on PRIMARY is not resolved, BACKUP1 performs a system reset of PRIMARY.
• BACKUP1 notifies group members on remaining systems in the sysplex (only BACKUP1 in the example) that PRIMARY has failed and no longer has access to shared resources.
• Group members of the multisystem applications on BACKUP1 can now take over the workload of their group members on PRIMARY.
• BACKUP1 deactivates all other LPARs in its addressing range (only PRIMARY in this example) and then acquires both the central and expanded storage assigned to those LPARs (only PRIMARY in this example).
• BACKUP1 brings all processor storage in its addressing range online. The storage previously used by PRIMARY is now available to BACKUP1. Also, the shared central processors used by PRIMARY are available to BACKUP1.
• As a result of the SFM policy, there is enough processor storage available on BACKUP1 for group members of the multisystem applications on BACKUP1 to take over the workload of their group members on PRIMARY.

Note that CONNFAIL(NO) is specified on the policy statement because a coupling facility is not available.