Checking for Status Update Resumed
Once XCF schedules the status user routine to check for status
update resumed, the routine must again set a return code to let XCF
know whether it wants other members to be notified of a status change.
The status user routine should set the return code as follows:
- A return code of SEUPDRES indicates that the member is operating
normally, even if it did not resume updating its status field. In
this case:
- The return code matches the value in SEPLSTCH, causing XCF to schedule the group user routines to notify the other members that the member's status update resumed (event type = GEMNOSUM, where GEMNOSUM is a system-defined constant).
- The status user routine can place user data in GPR 0 to be passed to the group user routines in the parameter list (GEPLUDAT field mapped by the IXCYGEPL mapping macro).
- XCF continues to monitor the status field in case the member misses another update.
- A return code of SEUPDMIS indicates that the member is not operating
normally, even though it might have resumed updating its status field.
In this case:
- The return code does not match the value in SEPLSTCH, so XCF will not schedule the group user routines.
- The status user routine should not place user data in GPR 0 because XCF will not be scheduling the group user routines.
- XCF continues to monitor the status field, and continues scheduling
the status user routine:
- As long as the status user routine runs successfully
- Until the status user routine confirms a status update resumed
- Until the member becomes inactive.
Note: XCF reports the status update missing condition to the group user routines only once per occurrence, rather than continuously informing the group user routines that the status update is still missing.
Figure 1. XCF Status Monitoring
Service Normal Processing (Part 1 of 2)

Figure 2. XCF Status
Monitoring Service Normal Processing (Part 2 of 2)
