A member can become not active unexpectedly as the result of a failure. A member also can become not active voluntarily by invoking the XCF Leave service (IXCLEAVE) or the XCF Quiesce service (IXCQUIES). This topic describes how XCF handles messages that might still be associated with the member that is terminating.

When a member becomes not active, XCF ensures that it deletes any member message data space. XCF also discards any messages that could not be presented to the member. The discarded messages include those saved by the member, those pending delivery to a message user routine, and completed message-out requests pending presentation to a message notify user routine. Incomplete message-out requests are declared to be complete when the sending member becomes not active, and are then discarded (without notification).

If XCF has initiated a send for a message-out request, XCF continues to attempt delivery of the message. XCF does not guarantee that the message will be delivered, even if it has already initiated the send, because a system can be removed from the sysplex before a message is transferred to its target system. Despite the potential for non-delivery, a member might want to take steps to ensure that XCF has initiated the send of its messages before it becomes (voluntarily) not active.