OpenTP1 Version 7 Programming Guide

[Contents][Index][Back][Next]

3.10.5 MCF event that reports discarding of an unprocessed send message (ERREVTA)

ERREVTA is reported in the following cases:

Organization of this subsection
(1) Flow up to ERREVTA

(1) Flow up to ERREVTA

When MHP terminates normally, the messages sent to the output queue are output. When OpenTP1 is to be terminated normally in transmission wait state, MCF waits for the termination until the send messages in the output queue have been sent. At this time, if the messages cannot be sent due to a failure in the destination system, timeout occurs and the send messages are discarded. ERREVTA reports to post that the messages have been discarded. The period of time causing timeout is specified for the mtim operand of the timer definition mcfttim of the MCF communication configuration definition. Timer monitoring is performed based on this operand value.

Note that the timer start request message issued by the function dc_mcf_execap() is not included in the monitoring of the remaining time for unprocessed send messages. Consequently, when the normal termination command (dcstop command) for OpenTP1 is executed, the timer start request message is discarded immediately and ERREVTA is reported.

The figure below shows the outline of ERREVTA.

Figure 3-25 Outline of ERREVTA

[Figure]

  1. The normal termination command (dcstop command) for OpenTP1 is executed. Any timer start request message remaining at this time is discarded, and MCF reports ERREVTA.
  2. The message that was processed normally by MHP is stored in the output queue.
  3. Output messages are discarded because timeout occurred for the send messages in the output queue.
  4. ERREVTA reports from MCF.
  5. The MHP for ERREVTA is scheduled.
  6. The message information is saved in a user file or the like.