Calling the Message Notify User Routine

XCF presents the collection of responses to the message notify user routine of the originating member, in the message notification parameter list (MNPL).

MNPL maps a table that contains information about the response, if any, that was collected from each target member. When more than one target member exists, the entries in the table are in one-to-one correspondence with the entries in the table of targets specified (with the TARGETS= parameter, members=all or members=others) when the original broadcast message was sent. The one-to-one correspondence applies to all entries in the table of targets, including any entries containing a null member token. If any target table entry contains a null member token, the corresponding entry in the MNPL identifies that state with one of the following flags:

MNPLTOSENDSKIPPED
MNPLTRSENDSKIPPED

When either of these flags is set to B'1', the corresponding target member token is hexadecimal zero, indicating that the sender wanted to skip an entry in the message-out target table.

If no response was received, XCF provides a code in the table. (The MNPLTRRESPCODE field indicates why the expected response was not received.) Note that failure to receive a response does not imply that the target member did not receive its copy of the message. Some reasons why an expected response might not be received are:

The send of the message-out request has yet to be initiated.
The target member is not coded to support XCF-managed response collection.
The target member is not running on a system that supports XCF-managed response collection.
The system on which the target member resides was removed from the sysplex before the response was sent.
The target member became inactive before it could send the response.
The message was not sent because the target member is not active.

If a response was received, use the XCF Message In service (IXCMSGIX) to retrieve the data or the XCF Message Control service (IXCMSGC) to save or discard the data. Note that IXCMSGIX and IXCMSGC must be invoked from within the message notify user routine.

Response collection is considered complete when all the expected responses have arrived, when IXCMSGC is used to force completion, or when the timeout value expires, whichever occurs first. (See Specifying a Timeout Value for Message Completion for a description of the timeout value.)