z/OS MVS Setting Up a Sysplex
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Scenario

z/OS MVS Setting Up a Sysplex
SA23-1399-00

  • Connectivity failure

    The policy specifies one heavily weighted system, SYSA. The policy also specifies two lesser weighted systems, SYSC and SYSD. Two systems, SYSB and SYSE, will use the system default weight of 1, since they do not have a system statement and weight is not specified in the policy default statement. (For a description of how SFM uses weights to make isolation decisions, see Handling signaling connectivity failures.)

  • System failure

    If SYSA stops updating its status, the operator will be prompted, and no automated action will take place. Because SYSB and SYSE do not have a system statement and the system statements for SYSC and SYSD do not specify an action for a status update missing condition, if SYSB, SYSC, SYSD, or SYSE enters a status update missing condition, the policy default action will be used, and a system isolation will be attempted with no delay.

  • Reconfiguration

    If SYSE is removed from the sysplex for any reason, and SYSD is active, then SYSD will acquire both the central and expanded storage assigned to SYSE.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014