Service request data files

An RPC request data file stores the data passed to the service function for a service requested when using the client UAP simulator with an RPC interface. A single file contains one set of data.

(a) File structure

[Figure]

(b) File contents

Item	Position	Length (bytes)	Contents
Data length	0	4	Length of the data to be passed to the service function. (0 - specified value of DCRPC_MAX_MESSAGE_SIZE)
Response area length	4	4	Length of the response area to be passed to the service function. (1 - specified value of DCRPC_MAX_MESSAGE_SIZE)
Data	8	n	Data to be passed to the service function.

(c) Notes

The items in the RPC request data file are related to the service function arguments as follows:
1. Data
2. Data length
3. Response area length
An RPC request data file for the online tester can also be used.
Do not use a plus sign (+) in the file name. Also, do not use ps or end as the file name.
An error occurs when the specified data is less than the specified data length. Data that exceeds the data length is truncated.

(2) XATMI request data file

An XATMI request data file stores the data passed to the service function for a requested service when using the client UAP simulator with an XATMI interface. A single file contains one set of data.

(a) File structure

[Figure]

(b) File contents

Item	Position	Length (bytes)	Contents
Call type	0	8	Type of function calling a service: call call from tpcall function acall call from tpacall function connect call from tpconnect function
Buffer type	8	8	Buffer type, specified as one of the following character strings: X_OCTET X_COMMON X_C_TYPE
Buffer subtype	16	16	Buffer subtype, specified as a string of up to 16 characters. Specify a null character when specifying X_OCTET as the buffer type.
Flags	32	4	Flags to be passed to the service function, specified as a hexadecimal. 0x00000000L 0 0x00000004L TPNOREPLY 0x00000008L TPNOTRAN 0x00000100L TPNOCHANGE 0x00000800L TPSENDONLY 0x00001000L TPRECVONLY
Data length	36	4	Length of the data to be passed to the service function (0-524288). Specify zero when no data is passed. The buffer type and subtype specifications are ignored when zero is specified.
Data	40	n	Data to be passed to the service function

(c) Notes

The items in the XATMI request data file are related to the service function arguments as follows:

void tpservice(svcinf)
     TPSVCINFO *svcinf;
 
     struct TPSVCINFO {
               char name[32];  ......1.
               char *data;     ......2.
               long len;       ......3.
               long flags;     ......4.
               int cd;         ......5.
            }

Service name
Address at which the data mapped to buff_type and sub_type is stored
Length of the data shown by data
Flags (specified flags stored in bit strings)
Interactive descriptor (stores zero)

An XATMI request data file for the online tester can also be used.
Do not use a plus sign (+) in the file name. Also, do not use ps or end as the file name.
An error occurs when the specified data is less than the specified data length. Data that exceeds the data length is truncated.
The response data area is reallocated according to the buffer type and buffer subtype in the response data.
When the buffer type and subtype are specified, the values specified for the data length and data must be the same as the data structure value defined for the stubs.
Boundary alignment is performed for the data structure specified for the stubs (the total length is an integer multiple of 4). For this reason, the user must consider the alignment portion when creating an XATMI request data file.

(3) TxRPC request data file

A TxRPC request data file stores the data passed to the service function for a requested service when using the client UAP simulator with a TxRPC interface. A single file contains one set of data.

(a) File structure

[Figure]

(b) File contents

Item	Position	Length (bytes)	Contents
Major version	0	2	Major version number specified in the interface definition of the txidl command. Specify zero to omit this specification.
Minor version	2	2	Minor version number specified in the interface definition of the txidl command. Specify zero to omit this specification.
Data length	4	4	Length of the data to be specified for a data part (0 to specified value of DCRPC_MAX_MESSAGE_SIZE - 16).
Data	8	n	Argument data to be passed to the service function. When setting an address in the argument, set the contents of the area indicated by the address. Set character string #NULL## if the address is null.

(c) Notes

The following shows data contents of the TxRPC request data file and how the service function arguments are related to the data received by the arguments.
Do not use a plus sign (+) in the file name. Also, do not use ps or end as the file name.
An error occurs when the specified data is less than the specified data length. Data that exceeds the data length is truncated.
UAP operations are not guaranteed when the data contains an error.

11.2.1 Service request data files

(1) RPC request data file

(a) File structure

(b) File contents

(c) Notes

(2) XATMI request data file

(a) File structure

(b) File contents

(c) Notes

(3) TxRPC request data file

(a) File structure

(b) File contents

(c) Notes