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


The Quiesced State

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

Only members with permanent status recording can become quiesced. A member in the quiesced state is disassociated from XCF services, but XCF still maintains a record of the member's existence. The IXCQUIES macro places a member in the quiesced state. The following are true for a quiesced member:
  • The quiesced member can no longer send or receive messages, and XCF stops scheduling the member's message user routine.
  • The quiesced member can no longer have its status monitored by XCF, and XCF stops scheduling the member's status user routine.
  • The quiesced member can no longer be notified by XCF of status changes to other members of the group (XCF stops scheduling the member's group user routine).
  • XCF no longer associates the quiesced member with a task, job step task, address space, or system, although XCF maintains a record of the system that the member was associated with when it was last active.
  • A quiesced member can become active with permanent status recording once again through IXCJOIN. When this happens, the member is treated as a new member because XCF:
  • A quiesced member can have its user state value changed by another active member of the same group through IXCSETUS.

A member might choose the quiesced state to avoid unnecessary recovery action. When a member becomes quiesced, other members can infer that the member cleaned up its own resources (closed any open data sets, released all serialization on shared data sets, etc.) before terminating.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014