Issuing the function dc_mcf_tactcn() requests the MCF communication process to establish a connection with the remote system.

Depending on the protocol used, an MCF event is reported to the UAP when a connection to the remote system is established or when connection establishment fails. The figure below shows the flow for establishing a connection, using an example in which the function dc_mcf_tactcn() is used on TP1/NET/TCP/IP.

Figure 3-1 Example of establishing a connection using the function dc_mcf_tactcn()

Issuing the function dc_mcf_tdctcn() requests the MCF communication process to release the connection with the remote system.

Depending on the protocol used, an MCF event is reported to the UAP when the connection is released. The figure below shows the flow for releasing a connection, using an example in which the function dc_mcf_tdctcn() is used on TP1/NET/TCP/IP.

Figure 3-2 Example of releasing a connection using the function dc_mcf_tdctcn()

The table below shows the functional differences between the functions and the operation commands used for establishing or releasing a connection.

Table 3-2 Functional differences between functions and operation commands (connection establishment and release)

Function name	Operation command	Functional differences
dc_mcf_tactcn	mcftactcn	Requests establishment of a single connection. Multiple or batch specification of connections is not allowed. A request to establish a connection group is not allowed. Subconnections cannot be specified. A connected XP service cannot be specified.
dc_mcf_tdctcn	mcftdctcn	Requests release of a single connection. Multiple or batch specification of connections is not allowed. A request to release a connection group is not allowed. Subconnections cannot be specified.
dc_mcf_tlscn	mcftlscn	Acquires the status of a single connection. Multiple or batch specification of connections is not allowed. The status of a connection group cannot be acquired. Only the protocol type and connection status can be acquired. Other additional information or protocol-specific information cannot be acquired.