An MCF communication process is used when the local OpenTP1 system communicates with the remote system. This process is used when a UAP communicates with the remote system by using the following functions:

• Receiving message (the function dc_mcf_receive())
• Sending message (the function dc_mcf_send())
• Sending response message (the function dc_mcf_reply())
• Receiving synchronous message (the function dc_mcf_recvsync())
• Sending synchronous message (the function dc_mcf_sendsync())
• Exchanging synchronous message (the function dc_mcf_sendrecv())
• Resending message (the function dc_mcf_resend())

Create an MCF communication process for each communication protocol supporting product. When one OpenTP1 system communicates with a remote system via multiple communication protocols, define an MCF communication process for each communication protocol supporting product.

This system process is used when the OpenTP1 system passes messages to an internal MHP.

The application startup process is used when the following facilities are executed:

• Starting application program (the function dc_mcf_execap())
• MHP rollback (the function dc_mcf_rollback()) with retry specification
• When reported MCF error events (ERREVTx) are used in a job.
• When an MHP is activated with the mcfuevt command.

The application startup process is not used to communicate with other systems (does not depend on the communication protocol). In general, define one application starting process for each node.