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


Removing a coupling facility from the configuration

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

This topic has a procedure for removing a coupling facility (CF) from the configuration when all CF structures can be removed from the CF. If not all structures can be removed from the CF (for example, the Parallel Sysplex® configuration is a global resource serialization star complex with a single usable CF), then see Transitioning from a Parallel Sysplex to a base sysplex.

Take the following actions to delete a CF from the CFRM active policy:

  1. Define a new CFRM policy that does not include any reference to that CF - this includes the CF definition and the CF name in structure preference lists. When removing the CF from a preference list, ensure the preference list contains the CF into which the structure will be rebuilt (or duplexed).

    When the CF is being removed only temporarily, use a name for the new CFRM policy that is different from the name of the current CFRM policy so that the CF can be restored to the sysplex using the original/current policy.

  2. CHPIDs being used for connectivity between all systems and the CF should be recorded at this point. The CHPIDs used for connectivity between all systems and the CF can be obtained using the ROUTE *ALL,DISPLAY CF,CFNAME=cfname command.
    Information about CF connectivity to systems and CF characteristics is returned in message IXL150I. Record the following information that uniquely identifies the CF to each system:
    • NODE DESCRIPTOR (type.mfg.plant.sequence)
    • PARTITION
    • CPCID
    • CHPID's (listed under SENDER PATH heading)
  3. Activate the new policy with the SETXCF START,POLICY,TYPE=CFRM,POLNAME=polname2 system command.

    The policy changes to remove the CF definition and the policy changes to the preference list of allocated structures may become pending. Verify the deletion or pending deletion of the CF from the CFRM active policy can be verified with the DISPLAY XCF,CF,CFNAME=cfname system command.

  4. Remove all structures from the CF. See Removing structures from a coupling facility for shutdown for guidelines on removing all structures from a CF that is pending deletion from the CFRM active policy.

    Unless REALLOCATE is used, any change to the preference list of a structure that was not allocated in the CF being removed might remain pending.

    After all structures are removed from the CF, the CF will be deleted from the active policy. Deletion of the CF from the active policy can be verified with the DISPLAY XCF,CF,CFNAME=cfname system command .

  5. Using the CHPIDs from a preceding step, on all systems, place all paths to the CF offline with the CONFIG CHP(chpxx,chpyy...),OFFLINE system command.

    Verify the unavailability of the CF on all systems with the DISPLAY M=CHP(chpxx,chpyy...) system command.

  6. SHUTDOWN the CF.

The CF can be removed from the I/O configuration when preceding actions are complete.

If making changes to CF elements (CF control units or CF channel paths) in the I/O configuration, ensure that SOFT=VALIDATE is specified on the ACTIVATE system command. SOFT=VALIDATE is a requirement in all N-1 partitions when changes to CF elements are made.

See z/OS HCD Planning and z/OS HCD User's Guide for additional information on deleting a CF from an I/O configuration.

See Adding a Coupling Facility for a procedure to restore the CF to the sysplex.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014