When messages are exchanged with OpenTP1, TP1/Message Control outputs the message which post various system information items of OpenTP1 to MHP. Such messages are called MCF events. If an error or failure reported during message exchange processing, what occurred in the system is indicated by an MCF event. There are two types of MCF events: error events such as errors and failures, and communication events dependent on the protocol such as establishment and release of a connection. The MHP which handles failures based on MCF events is called the MHP for an MCF event. Creating this MHP enables individual failure recovery processing.

An MCF event is passed to the input queue, and the MHP for an MCF event is started. At this time, the user exit routine that edits input message and determines application name is not used. An MCF event is never started as the result of a failure occurring in an MCF event.

The table below lists MCF events. Some MCF events which are not included in the table are reported as events specific to communication protocol supporting products. For MCF events specific to communication protocol supporting products, see the applicable OpenTP1 Protocol manual.

Table 3-16 MCF events

MCF event name	MCF event code	Cause of MCF event occurrence	Example of processing by MHP for an MCF event
MCF event that reports detection of an invalid application name	ERREVT1	The application name of the message was not found in the MCF application definition.	Posts that the application name was not found. For an inquiry message, a response message can be output.
MCF event that reports discarding of a message	ERREVT2	The message in the input queue received with MCF or the message input to the input queue as a result of immediate startup of an application was discarded for any of the following reasons: An error related to the input queue occurred. MHP service, service group, or application was shut down. MHP service, service group, or application is in secure state. MHP terminated abnormally before the segment was passed to the function dc_mcf_ receive() of MHP. There is no MHP service corresponding to the application name. When MCF cannot activate SPP. MHP is not running.	Posts that the message was discarded. For an inquiry message, a response message can be output.
MCF event that reports UAP abnormal termination	ERREVT3	MHP terminated abnormally or rolled back# after the segment was passed to the function dc_mcf_receive() invoked by MHP.	Reports that the UAP terminated abnormally or rolled back. For an inquiry message, a response message can be sent.
MCF event that reports discarding of a timer-start message	ERREVT4	The message input as a result of startup of the timer start application was discarded.	Posts that the message was discarded. In the case of an inquiry message, a response message can be output.
MCF event that reports discarding of an unprocessed send message	ERREVTA	The unprocessed message from a UAP was discarded for any of the following reasons: Timeout occurred in residence time monitoring for unprocessed send message when MCF terminated normally. The output queue was deleted by the mcftdlqle command or the function dc_mcf_tdlqle(). The dcstop command was executed while a timer start request remained.	Posts that the unprocessed message was discarded. The unprocessed send message is saved in a file.
MCF event that reports a send error	SERREVT	A communication protocol error occurred during sending of a message.	Posts that the message could not be sent due to a failure in the communication protocol.
MCF event that reports send completion	SCMPEVT	A message was sent normally to the remote system.	Posts that the message was sent normally to the remote system.
MCF event that reports an error	CERREVT (VERREVT)	A connection failure or logical terminal failure occurred with the communication management program. It does not report when automatic retry is specified.	Posts that a connection failure or logical terminal failure occurred.
MCF event that reports an status	COPNEVT (VOPNEVT)	Connection has been established.	Posts that connection has been established.
	CCLSEVT (VCLSEVT)	Connection has been released normally.	Posts that connection has been released.

Note

ERREVT1, ERREVT2, ERREVT3, ERREVT4, and ERREVTA represent error events.

SERREVT, SCMPEVT, CERREVT, COPNEVT, and CCLSEVT represent communication events.

#

Excludes cases in which r is specified for the recvmsg operand in the MCF application definition (mcfaalcap -g) or in which DCMCFRTRY or DCMCFRRTN is specified for action of the function dc_mcf_rollback().

• The application attribute of MHP for an MCF event
  The application attribute of the MHP for an MCF event is determined according to the cause of the MCF event occurrence. For the MHP for an MCF event, perform processing according to the determined application type.
  When starting the MHP for ERREVT1, ERREVT2, or ERREVT3, the application startup process is required. When this process is used, the MCF communication configuration definition needs to be created.
  If an MCF event occurs when two or more MHPs were started by the function dc_mcf_execap(), the type of the MHP for an MCF event is determined based on the type of the MHP that called the function dc_mcf_execap() first. When the function dc_mcf_execap() was called from SPP, the MCF event corresponding to the application startup process reports.
  The table below shows the relationship between the MHP for an MCF event and the application attribute.
  

  Table 3-17 Relationship between MHPs for an MCF event and application attributes

  Event code of MCF event	Application attribute of MHP for an MCF event
  ERREVT1	The attribute is set according to the terminal type of the request source logical terminal. reply-type logical terminals: ans Logical terminals that are not the reply type: noans
  ERREVT2	The application attribute of the MHP which caused MCFevent reporting is inherited as is.#
  ERREVT3
  ERREVT4
  ERREVTA	The nonresponse (noans) type is set.
  SERREVT
  SCMPEVT
  CERREVT
  VERREVT
  COPNEVT
  CCLSEVT
  VCLSEVT

  #

  If the MHP has the nontransaction attribute, the application attribute is not inherited even after abnormal termination; instead, the specification for the MHP for an MCF event is observed.

  
  
• Relationship between communication protocol products and reported MCF events
  The following tables show the relationships between communication protocol products and reported MCF events.
  

  Table 3-18 Relationship between communication protocol products and reported MCF events (1/5)

  MCF EVENT	Communication protocol product
  	TP1/NET/User Agent	TP1/NET/OSI-TP	TP1/NET/TCP/IP
  ERREVT1	Y	Y	Y
  ERREVT2	Y	Y	Y
  ERREVT3	Y	Y	Y
  ERREVT4	Y	Y	Y
  ERREVTA	Y	Y	Y
  SERREVT	N	N	N
  SCMPEVT	N	N	Y
  CERREVT	Y	Y	Y
  COPNEVT	Y	Y	Y
  CCLSEVT	Y	Y	Y
  VERREVT	N	N	N
  VOPNEVT	N	N	N
  VCLSEVT	N	N	N

  Legend:

  Y: The event is reported by the communication protocol product.

  N: The event is not reported by the communication protocol product.

  
  

  Table 3-19 Relationship between communication protocol products and reported MCF events (2/5)

  MCF EVENT	Communication protocol product
  	TP1/NET/XMAP3	TP1/NET/HNA-560/20	TP1/NET/HNA-560/20 DTS
  ERREVT1	Y	Y	Y
  ERREVT2	Y	Y	Y
  ERREVT3	Y	Y	Y
  ERREVT4	Y	Y	Y
  ERREVTA	Y	Y	Y
  SERREVT	Y#	N	N
  SCMPEVT	Y#	N	N
  CERREVT	N	Y	Y
  COPNEVT	N	Y	Y
  CCLSEVT	N	N	N
  VERREVT	Y	Y	Y
  VOPNEVT	Y	Y	Y
  VCLSEVT	Y	Y	N

  Legend:

  Y: The event is reported by the communication protocol product.

  N: The event is not reported by the communication protocol product.

  #

  SERREVT and SCMPEVT are reported only when the print facility is used.

  
  

  Table 3-20 Relationship between communication protocol products and reported MCF events (3/5)

  MCF EVENT	Communication protocol product
  	TP1/NET/OSAS-NIF	TP1/NET/HNA-NIF	TP1/NET/HSC (1)	TP1/NET/HSC (2)
  ERREVT1	Y	Y	Y	Y
  ERREVT2	Y	Y	Y	Y
  ERREVT3	Y	Y	Y	Y
  ERREVT4	N	N	Y	Y
  ERREVTA	Y	Y	Y	Y
  SERREVT	N	N	Y	Y#
  SCMPEVT	N	N	Y	Y#
  CERREVT	Y	Y	Y	Y
  COPNEVT	Y	Y	Y	Y
  CCLSEVT	Y	Y	Y	Y
  VERREVT	N	N	N	N
  VOPNEVT	N	N	N	N
  VCLSEVT	N	N	N	N

  Legend:

  Y: The event is reported by the communication protocol product.

  N: The event is not reported by the communication protocol product.

  #

  TP1/NET/HSC reports SERREVT and SCMPEVT only in the asynchronous mode.

  
  

  Table 3-21 Relationship between communication protocol products and reported MCF events (4/5)

  MCF EVENT	Communication protocol product
  	TP1/NET/HDLC	TP1/NET/X25	TP1/NET/X25-Extended
  ERREVT1	Y	Y	Y
  ERREVT2	Y	Y	Y
  ERREVT3	Y	Y	Y
  ERREVT4	Y	Y	Y
  ERREVTA	Y	Y	Y
  SERREVT	N	N	N
  SCMPEVT	Y	N	Y
  CERREVT	Y	Y	Y
  COPNEVT	Y	Y	Y
  CCLSEVT	Y	Y	Y
  VERREVT	N	N	N
  VOPNEVT	N	N	N
  VCLSEVT	N	N	N

  Legend:

  Y: The event is reported by the communication protocol product.

  N: The event is not reported by the communication protocol product.

  
  

  Table 3-22 Relationship between communication protocol products and reported MCF events (5/5)

  MCF EVENT	Communication protocol product
  	TP1/NET/SLU-TypeP1	TP1/NET/SLU-TypeP2	TP1/NET/NCSB	TP1/NET/UDP
  ERREVT1	Y	Y	Y	Y
  ERREVT2	Y	Y	Y	Y
  ERREVT3	Y	Y	Y	Y
  ERREVT4	Y	Y	Y	Y
  ERREVTA	Y	Y	Y	Y
  SERREVT	N	N	N	N
  SCMPEVT	N	N	N	N
  CERREVT	Y	Y	Y	Y
  COPNEVT	Y	Y	Y	Y
  CCLSEVT	Y	Y	Y	Y
  VERREVT	N	N	N	N
  VOPNEVT	N	N	N	N
  VCLSEVT	N	N	N	N

  Legend:

  Y: The event is reported by the communication protocol product.

  N: The event is not reported by the communication protocol product.

  
  

Organization of this section

3.10.1 MCF event that reports detection of an invalid application name (ERREVT1)

3.10.2 MCF event that reports discarding of a message (ERREVT2)

3.10.3 MCF event that reports UAP abnormal termination (ERREVT3)

3.10.4 MCF event that reports discarding of a timer-start message (ERREVT4)

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

3.10.6 MCF event that reports a send error (SERREVT)

3.10.7 MCF event that reports send completion (SCMPEVT)

3.10.8 MCF event that reports an error (CERREVT, VERREVT)

3.10.9 MCF event that reports establishing a connection (COPNEVT, VOPNEVT)

3.10.10 MCF event that reports releasing a connection (CCLSEVT, VCLSEVT)

3.10.11 Message format for MCF events