ERREVT2 is reported when the received message was discarded for any of the following reasons. ERREVT2 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:

• An input queue error occurred.
• An application, service, or service group was blocked or is in secure state.
• MHP terminated abnormally before the first segment is received.
• There is no MHP service function corresponding to the application name.
• SPPs cannot be started by the MCF when the remote MCF service is used.
• Messages remain in the input queue due to schedule blocking of service groups at termination of OpenTP1.

With the MHP for ERREVT2, reference the contents of ERREVT2 and send the message posting that processing was not possible in the local node 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 ERREVT2.

Figure 3-22 Outline of ERREVT2

1. The received message was discarded from the input queue for some reason.
2. Control returns to MCF, ERREVT2 reports, and the MHP for ERREVT2 is scheduled.
3. The send-only message posting the message resend request and so forth is sent from the MHP for an MCF event to the other system which sent the message.