Events Other than Normal Processing

Certain events cause XCF to do the following:

Assume a status update missing condition for a member, even when one is not confirmed by the status user routine (event type = GEMSUMDI).
Stop monitoring a member (event type = GEMONREM).

In both of these cases, XCF notifies the group user routines. In the case where XCF stops monitoring a member, XCF schedules the group user routine of the affected member as well as the other members.

Note: To reinstate monitoring after XCF stops monitoring a member, the member must issue IXCLEAVE or IXCQUIES, and then issue IXCJOIN once again with the STATEXIT, STATFLD, and INTERVAL parameters.

Table 1 summarizes the events that cause XCF to assume a status update missing condition for a member, or to stop monitoring the member:

Table 1. Status User Routine Events Other Than Normal Processing
Event	Assume Status Update Missing	Stop Monitoring Member
The member's status user routine did not execute in time (system-defined). Note: XCF does not schedule the status user routine if a schedule is already outstanding. If a status user routine becomes deadlocked or is in an infinite loop, XCF cannot schedule it again.	X
The member's status user routine terminated abnormally for the first time.	X
XCF rescheduled the member's status user routine and it terminated abnormally for the second time.		X
XCF tried to invoke the member's status user routine for the first time, but failed (for example, an error could occur trying to invoke the routine because of an incorrect address or the routine not being loaded.)	X
XCF tried to invoke the member's status user routine a second time, and failed again.		X
The member changed to a quiesced, failed, or not-defined state.		X
XCF could not access the member's status field.		X