Setting send/receive procedures

Send/receive procedures must be set when using the conversational service paradigm with a simulated UAP that uses the XATMI interface. Send/receive procedures are stored in a send/receive control file (any file name).

In the send/receive control file, define a send statement for sending data to the test SPP and a recv statement for receiving data from the test SPP.

Always create a send/receive control file when using the conversational service paradigm, even if no data is actually sent or received.

Organization of this subsection: (1) Syntax; (2) Operands; (3) Definition example; (4) Notes

(1) Syntax

(a) send statement

zueng020.tif0send [zueng020.tif1XATMI-receive-data-file-name]

Legend:

₀: One or more spaces or tab codes (or none)

₁: One or more spaces or tab codes

(b) recv statement

₀recv

₁type

₁subtype or buffer-length [ [Figure]

₁flag [,flag...]]

Legend:

₀: One or more spaces or tab codes (or none)

₁: One or more spaces or tab codes

(2) Operands

(a) send statement

send
Specify the send keyword as the definition name.
XATMI-receive-data-file-name ~<pathname>
Specify the name of the XATMI receive data file containing the data received by the test SPP.
When specification is omitted, the data in the XATMI receive data file specified in the preceding send statement is used. An error occurs if specification is omitted for the first send statement.

(b) recv statement

recv
Specify the recv keyword as the definition name.
type ~<8 upper-case alphabetics>
Specify one of the following receive buffer types:
- X_OCTET
- X_COMMON
- X_C_TYPE
subtype ~<1-31 alphanumerics>
Specify the receive buffer subtype when specifying X_COMMON or X_C_TYPE in type.
buffer-length ~<decimal digit>
Specify the receive buffer length when specifying X_OCTET in type.
flag
Specify one or more of the following flags set for a receive request (tprecv function):
- TPNOCHANGE
- TPNOBLOCK
- TPNOTIME
- TPSIGRSTRT
Do not specify a flag unless required.
When setting multiple flags, delimit each flag with a comma (,). Do not insert a space or tab code before or after the comma.

(3) Definition example

# send/receive procedure definition
# interactive service name: service01
send sendfile1
recv X_OCTET 128 TPNOCHANGE
send sendfile2
recv X_COMMON subtype1 TPNOTIME,TPSIGRSTRT
#

(4) Notes

A line can be up to 512 bytes in length, including the line feed code.
Write # at the start of a comment. Only a space or tab code may be written before #.
Do not write a comment at the end of the send/receive procedure definition.
No error occurs if no send statement or receive statement is defined. However, processing is terminated if a connection is established during execution of the utoxsppsvc command.
During execution of the utoxsppsvc command, the tpsend and tprecv functions are issued for the conversational service paradigm according to the specifications in the send/receive control file. If a TPEV_SVCSUCC or TPEV_SVCFAIL event occurs, subsequent send and recv statements are ignored and the command terminates normally.
The definition in the recv statement is related to the XATMI functions issued by the utoxsppsvc command as follows.

Example:

If the recv statement is defined as: recv X_COMMON subtype1 TPNOCHANGE

Then:
1. type
2. subtype
3. flag

3.1.6 Setting send/receive procedures

(1) Syntax

(a) send statement

(b) recv statement

(2) Operands

(a) send statement

(b) recv statement

(3) Definition example

(4) Notes