OpenTP1 Version 7 Programming Guide

[Contents][Index][Back][Next]

3.6.1 Message communication modes

Organization of this subsection
(1) Message communication modes available with MHPs
(2) Communication modes of MHPs and message communication facilities available to SPPs
(3) Message communication modes and application type
(4) Communication protocol products and functions available in communication modes

(1) Message communication modes available with MHPs

Message communication modes which can be used with MHPs are shown below. Available message modes vary depending on the communication protocol.

The figure below shows the message communication modes.

Figure 3-6 Message communication modes

[Figure]

(2) Communication modes of MHPs and message communication facilities available to SPPs

The message communication facilities which are available to MHPs and SPPs are as follows:

To use the function dc_mcf_send() with an SPP, the SPP processing must be operating as a transaction.

(3) Message communication modes and application type

For an MHP using message exchange facilities, specify the type of application according to the message communication mode to be used. Specify the type of application for the type operand of the MCF application definition or the application attribute definition (mcfaalcap). There are the following three types of application:

Specify noans for the mode in which a message, received with the function dc_mcf_receive(), is sent to the logical terminal of the input source by using the function dc_mcf_send().

For MHPs, specify the type of application according to the message handling mode. This specification is not required for SPPs.

If the specified type of application conflicts with the message handling mode, a message exchange function returns with an error or the MHP processing is rolled back. The type conflicts with the mode in the following cases:

The application type of the MCF event handling MHP is determined by the reported MCF event. See 3.10 MCF events for details.

The table below shows the correspondence between the types of application and message exchange functions.

Table 3-9 Correspondence between the types of application and message exchange functions

Message Mode Types of Application Functions for Message Processing
receive send reply send
recv
recv
sync
send
sync
tempput, tempget contend
Inquiry-response mode ans M Y M N N N N
Noninquiry-response mode (receive-only mode) noans M#1 Y N N#2 N#2 N#2 N
Continuous-inquiry-response mode cont M Y M N N N Y

Legend:
M: Must be used.
Y: Can be used.
N: Cannot be used.

Note
The type of the logical terminal depends on the protocol. See the applicable OpenTP1 Protocol manual.

#1
The function dc_mcf_receive() cannot be used by SPPs.

#2
Can be called when TP1/NET/OSI-TP is used.

(4) Communication protocol products and functions available in communication modes

The following tables indicate what functions are available in each of the communication modes used by OpenTP1-provided products conforming to different communication protocols.

Table 3-10 Functions available in communication modes used by communication protocol products (1/5)

Function name Communication protocol product used and application type
TP1/NET/User Agent TP1/NET/OSI-TP TP1/NET/TCP/IP
noans type ans type cont type noans type ans type cont type noans type ans type cont type
dc_mcf_commit Y N -- Y -- -- Y -- --
dc_mcf_receive# Y Y -- Y -- -- Y -- --
dc_mcf_execap Y Y -- N -- -- Y -- --
dc_mcf_reply# N Y -- N -- -- N -- --
dc_mcf_rollback Y Y -- Y -- -- Y -- --
dc_mcf_send# Y Y -- N -- -- Y -- --
dc_mcf_resend# Y Y -- N -- -- Y -- --
dc_mcf_sendrecv# Y Y -- Y -- -- Y -- --
dc_mcf_sendsync# N N -- Y -- -- Y -- --
dc_mcf_recvsync# U U -- Y -- -- N -- --
dc_mcf_contend N N -- N -- -- N -- --
dc_mcf_tempget N N -- N -- -- N -- --
dc_mcf_tempput N N -- N -- -- N -- --

Legend:
Y: Available with the communication protocol product
N: Unavailable
U: This communication mode is used with the communication protocol product in a unique way.
--: This communication mode cannot be used with the communication protocol product.

#
The method of using the function might vary depending on the communication protocol product. For details, see the applicable OpenTP1 Protocol manual.

Table 3-11 Functions available in communication modes used by communication protocol products (2/5)

Function name Communication protocol product used and application type
TP1/NET/XMAP3 TP1/NET/HNA-560/20 TP1/NET/HNA-560/20 DTS
noans type ans type cont type noans type ans type cont type noans type ans type cont type
dc_mcf_commit Y N N Y N N Y N N
dc_mcf_receive# Y Y Y Y Y Y Y Y Y
dc_mcf_execap Y Y Y Y Y Y Y Y Y
dc_mcf_reply# N Y Y N Y Y N Y Y
dc_mcf_rollback Y Y Y Y Y Y Y Y Y
dc_mcf_send# Y Y Y Y Y Y Y Y Y
dc_mcf_resend# Y Y Y Y Y Y Y Y Y
dc_mcf_sendrecv# N N N N N N N N N
dc_mcf_sendsync# N N N N N N N N N
dc_mcf_recvsync# N N N N N N N N N
dc_mcf_contend N N Y N N Y N N Y
dc_mcf_tempget N N Y N N Y N N Y
dc_mcf_tempput N N Y N N Y N N Y

Legend:
Y: Available with the communication protocol product
N: Unavailable

#
The method of using the function might vary depending on the communication protocol product. For details, see the applicable OpenTP1 Protocol manual.

Table 3-12 Functions available in communication modes used by communication protocol products (3/5)

Function name Communication protocol product used and application type
TP1/NET/OSAS-NIF TP1/NET/HNA-NIF TP1/NET/HSC(1) TP1/NET/HSC(2)
n typ a typ c typ n typ a typ c typ n typ a typ c typ n typ a typ c typ
dc_mcf_commit Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_receive# Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_execap Y Y -- Y -- -- Y -- -- N -- --
dc_mcf_reply# N Y -- N -- -- N -- -- N -- --
dc_mcf_rollback Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_send# Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_resend# Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_sendrecv# Y Y -- N -- -- N -- -- N -- --
dc_mcf_sendsync# N N -- N -- -- N -- -- Y -- --
dc_mcf_recvsync# U U -- N -- -- N -- -- Y -- --
dc_mcf_contend N N -- N -- -- N -- -- N -- --
dc_mcf_tempget N N -- N -- -- N -- -- N -- --
dc_mcf_tempput N N -- N -- -- N -- -- N -- --

Legend:
n typ: noans type
a typ: ans type
c typ: cont type
Y: Available with the communication protocol product
N: Unavailable
U: This communication mode is used with the communication protocol product in a unique way.
--: This communication mode cannot be used with the communication protocol product.

#
The method of using the function might vary with the communication protocol product. For details, see the applicable OpenTP1 Protocol manual.

Table 3-13 Functions available in communication modes used by communication protocol products (4/5)

Function name Communication protocol product used and application type
TP1/NET/HDLC TP1/NET/X25 TP1/NET/X25-Extended
noans type ans type cont type noans type ans type cont type noans type ans type cont type
dc_mcf_commit Y -- -- Y -- -- Y -- --
dc_mcf_receive# Y -- -- Y -- -- Y -- --
dc_mcf_execap Y -- -- Y -- -- Y -- --
dc_mcf_reply# N -- -- N -- -- N -- --
dc_mcf_rollback Y -- -- Y -- -- Y -- --
dc_mcf_send# Y -- -- Y -- -- Y -- --
dc_mcf_resend# Y -- -- Y -- -- Y -- --
dc_mcf_sendrecv# N -- -- N -- -- N -- --
dc_mcf_sendsync# N -- -- N -- -- N -- --
dc_mcf_recvsync# N -- -- N -- -- N -- --
dc_mcf_contend N -- -- N -- -- N -- --
dc_mcf_tempget N -- -- N -- -- N -- --
dc_mcf_tempput N -- -- N -- -- N -- --

Legend:
Y: Available with the communication protocol product
N: Unavailable
--: This communication mode cannot be used with the communication protocol product.

#
The method of using the function might vary depending on the communication protocol product. For details, see the applicable OpenTP1 Protocol manual.

Table 3-14 Functions available in communication modes used by communication protocol products (5/5)

Function name Communication protocol product used and application type
TP1/NET/SLU - TypeP1 TP1/NET/SLU - TypeP2 TP1/NET/NCSB TP1/NET/UDP
n typ a typ c typ n typ a typ c typ n typ a typ c typ n typ a typ c typ
dc_mcf_commit Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_receive# Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_execap Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_reply# N Y -- N -- -- N -- -- N -- --
dc_mcf_rollback Y Y -- Y -- -- Y -- -- Y -- --
dc_mcf_send# Y N -- Y -- -- Y -- -- Y -- --
dc_mcf_resend# Y N -- Y -- -- Y -- -- Y -- --
dc_mcf_sendrecv# N N -- Y -- -- N -- -- N -- --
dc_mcf_sendsync# N N -- N -- -- N -- -- Y -- --
dc_mcf_recvsync# N N -- U -- -- N -- -- N -- --
dc_mcf_contend N N -- N -- -- N -- -- N -- --
dc_mcf_tempget N N -- N -- -- N -- -- N -- --
dc_mcf_tempput N N -- N -- -- N -- -- N -- --

Legend:
n typ: noans type
a typ: ans type
c typ: cont type
Y: Available with the communication protocol product
N: Unavailable
U: This communication mode is used with the communication protocol product in a unique way.
--: This communication mode cannot be used with the communication protocol product.

#
The method of using the function might vary depending on the communication protocol product. For details, see the applicable OpenTP1 Protocol manual.