OpenTP1 considers all MCF services as one service. However, each MCF service is structured from several processes as follows:

MCF manager process (one)

Initializes the shared memory, and manages and operates all MCF communication processes and application startup processes generated within one online system.

MCF communication processes (zero or more^#)

Controls messages that are protocol-dependent. Starts process(es) in accordance with the protocol.

Application startup process (zero or more^#)

Controls messages that are not protocol-dependent. Processes are started in the following cases:

• application startup function is being used,
• error event processing MHP is started, or
• a roll back request of the retry instruction is issued.

MCF online command process (one or none)

Processes online commands that are input from a 560 or XP terminal. The process is started up when using online commands.

#: An MCF service can consist of either only MCF processes or application startup processes.

Each definition is to be prepared in number as follows:

MCF manager definition

one for the MCF manager process

MCF communication configuration process

one for each MCF communication process, and one for each application startup process

MCF application definition

one for each or for several MCF communication process(es). Alternatively, one for each or for several application startup processes.

To start up the MCF communication process or application startup process, the applicable MCF communication configuration definition must be created.

Table 4-3 lists the network communication definitions and their output object file names.

Table 4-3 Network communication definitions and their output object file names

Definition name	Output object file name
MCF manager definition	MCF service name
MCF communication configuration definition	MCF communication service name Application startup process name