ERREVT3 is reported in the following case. ERREVT3 is also reported when a communication event for which errevt=yes (report error event at communication event failure) is specified in the -n option of the application attribute definition mcfaalcap encounters a failure for any of the following reasons:

• MHP terminated abnormally after the first segment was received with the function dc_mcf_receive().
• A failure occurred at termination of an application.

This event is reported when DCMCFNRTN is set for the flag of the function dc_mcf_rollback() called by the MHP.

With the MHP for ERREVT3, reference the contents of ERREVT3 and send the message posting that the UAP of the local node terminated abnormally, using the application name as the key, or take similar measures. At this time, send a response message or send-only message from the MHP for an MCF event depending on the type of the logical terminal or UAP.

The figure below shows the outline of ERREVT3.

Figure 3-23 Outline of ERREVT3

1. When retry is not set for rollback, if an error occurs in the processing with the MHP which received the message, control returns to MCF via the output queue.
2. ERREVT3 reports based on the information sent from the MHP which caused the error.
3. ERREVT3 schedules the MHP for an MCF event via the input queue. This MHP sends the message posting that an error occurred in the UAP of the another system, to the other system which sent the message.