The common definition defines essential environment information common to each MCF communication service. Common definition commands are used, but specified values of identifiers and other parameters must be unique. Create a separate common definition resource file for each communication service. Each type of communication service has specific options. For details, see the applicable OpenTP1 Protocol manual.

The data communication definition defines the environment information native to each MCF communication service. Definition commands native to the communication service are used. There are two types of definitions depending on the nature of the communication service: protocol native definition and application startup definition.

Use the protocol native definition to prepare an MCF communication configuration definition for an external communication service (MCF communication process). For details on the commands, see the applicable OpenTP1 Protocol manual.

Use the application startup definition to prepare an MCF communication configuration definition for communication within a node (application startup process).

Some definition commands are common to both types of definitions, but there are slight differences in the options. For details, see the definition command for the appropriate communication service.

The file structure of this definition is shown in Figure 5-2.

Figure 5-2 MCF communication configuration definition file structure

The specification sequence of the common definition commands is shown in Figure 5-3.

Figure 5-3 Common definition commands specification sequence

#: An application startup process does not use the buffers defined by this mcftbuf command. Do not specify this command in the corresponding MCF communication configuration definition.

The specification sequence for the application startup definition commands is shown in Figure 5-4.

Figure 5-4 Specification sequence of application startup definition command