Member Termination

A member is terminated (put in a failed or not-defined state) when the task, job step task, address space, or system that the member is associated with ends. If the member does not explicitly disassociate from XCF, the resulting member state depends on whether the member has permanent status recording. The member with permanent status recording becomes failed. The member without permanent status recording becomes not-defined. In either case, XCF notifies the group user routines of the other active members of the group about the member state change. Another member of the group or authorized routine can then provide recovery (cleanup of resources) for the member.

XCF considers the member as terminated under any of the following conditions:

The member is task associated and the task, the active job step task, address space, or system ends
The member is job step task associated and the job step task, address space, or system ends.
The member is only address space associated (not task or job step task) and its address space or system ends.

Also, consider the following conditions about termination of the member:

The value of the TERMLEVEL keyword for IXCTERM when the member invoked IXCJOIN to become an active member of the group affects termination. For example, if TERMLEVEL=ADDRSPACE when it joined the group, the member's address space will be terminated and every XCF group member associated with that address space including any other group will be terminated. If TERMLEVEL=SYSTEM, the system on which the target member resides will be removed from the sysplex.
If the system that is to terminate the member is being initialized (that is, it is running during NIP), the system will be removed from the sysplex.

Note: See Member Association for more information on member association as it relates to member termination.

For abnormal task termination, members can use MVS™ recovery services (ESTAEs, FRRs, ARRs, etc.) to retry or perform cleanup of resources. For normal or abnormal task or address space termination, members can also provide resource manager routines to get control. Resource manager routines cannot retry, but can perform cleanup of resources. See z/OS MVS Programming: Authorized Assembler Services Guide for information about using resource managers.