Service request data files

An RPC request data file stores the data passed to the service function for the service specified by the utosppsvc command 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. (1 to 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 to 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 offline tester can also be used.
An error occurs when the specified data is less than the specified data length. Data that exceeds the data length is ignored.

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 and restricted by the specified call type: 0x00000000 0 (for call and acall only) 0x00000004 TPNOREPLY (for acall only) 0x00000008 TPNOTRAN 0x00000100 TPNOCHANGE (for call and acall only) 0x00000800 TPSENDONLY (for connect only) 0x00001000 TPRECVONLY (for connect only) TPNOTIME and TPSIGRSTRT are always set at service requests. TPNOBLOCK is not set.
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];
               char *data;         1.
               long len;           2.
               long flags;
               int cd;
            }

Address at which the data mapped to the buffer type and subtype is stored
Length of the data shown by data

The items in the XATMI request data file are related to the XATMI functions issued by the utoxsppsvc command as follows.

idata=tpalloc(type,subtype,ilen);
               2.      3.      4.
 tpcall(svc, idata,ilen,odata,olen,flags);
    1.                4.                5.
 tpacall(svc, idata,ilen,flags);
    1.                 4.     5.
 tpconnect(svc, idata,ilen,flags);
    1.                   4.     5.

XATMI function corresponding to the call type
Buffer type name
Buffer subtype name
Data length
Flags (specified as the actual flag values of the specified flags)

An XATMI request data file for the offline tester can also be used.
An error occurs when the specified data is less than the specified data length. Data that exceeds the data length is ignored.
When the subtype name is less than 16 characters, add null characters to the end of the name.
For buffer types other than X_OCTET, the data in the XATMI request data file is illegal when the subtype data length specified in the file differs from the subtype data length specified in the utoxsppsvc command.
TPNOCHANGE can be specified in flag, but the specification is ignored.
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 defined 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.
Check boundary alignment details in the stub source created by the stbmake command and an output result created by the stbmake command with the -p option specified.

3.3.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