The following tables list the types and names of the tester files that the user must create in order to use the online tester.

For creating a test directory, see Subsection 3.4.1 Test directory.

Table 3-3 List of tester files to be created by the user

Tester file type		Use and contents	Time of creation	Deleted by	Time of deletion
Service request data files	RPC request data file	Stores request data passed to the server UAP when using the client UAP simulator with an RPC interface.	Before service request	User	Any
	XATMI request data file	Stores request data passed to the server UAP when using the client UAP simulator with an XATMI interface.	Before service request	User	Any
Service response data files	RPC response data file	Stores data returned as the service result when using the server UAP simulator with an RPC interface.	At activation of the simulate SPP	User	Any
	XATMI response data file	Stores data returned as the service result when using the server UAP simulator with an XATMI interface.	At activation of the simulate SPP	User	Any
XATMI receive data file		Stores data received by the tprecv function in the UAP when the conversational service paradigm is made via an XATMI interface.	Before service request or at activation of the simulate SPP#	User	Any
MCF receive message files	Asynchronous receive message file	Stores messages passed to the MHP by the dc_mcf_receive function when using the MCF simulator.	Before service request	User	Any
	Synchronous receive message file	Stores messages passed to the UAP by the dc_mcf_recvsync and dc_mcf_sendrecv functions when using the MCF simulator.	Before service request	User	Any
Operating command result data file		Stores data returned to the UAP as the execution result when using the operating command simulator.	Before service request	User	Any

Note

All user-created files for the offline tester can be used without modification, except the following:

XATMI receive data file

Synchronous receive message file

Operating command result data file

However, these three files can be used by the offline tester if you use the cat command to consolidate several offline tester data files into a single file.

#: The user creates an XATMI receive data file before a service request is made when using the client UAP simulator, or at activation of the simulate SPP when using the server UAP simulator.

Table 3-4 Names for user-created tester files

Tester file type		File name
Service request data files	RPC request data file	Any
	XATMI request data file
Service response data files	RPC response data file	$DCDIR/spool/uto/test-user-ID/ user-server-name/svc-service-name#1
	XATMI response data file	$DCDIR/spool/uto/test-user-ID/ user-server-name/xsv-service-name#1
XATMI receive data file		$DCDIR/spool/uto/test-user-ID/ user-server-name/xrv-service-name#1, #2, #3
MCF receive message files	Asynchronous receive message file	$DCDIR/spool/uto/test-user-ID/ xx....xx(xx....xx can be any name)
	Synchronous receive message file	$DCDIR/spool/uto/test-user-ID/ recv-logical-terminal-name#4 (Header segment file: $DCDIR/spool/uto /test-user-ID/recvh-logical-terminal-name)
Operating command result data files	For SPP service functions	$DCDIR/spool/uto/test-user-ID/ user-server-name/cmd-service-name#1
	For SUP and SPP main functions	$DCDIR/spool/uto/test-user-ID/ user-server-name/cmd

#1: When the service name exceeds 11 characters, the first five and last six characters are combined as the service name.

Example:Service name uapservice0001 uapsece0001

#2: When the service name exceeds 15 characters, the first five and the 10th to 15th characters are combined as the service name.

Example:Service name uapxatmiservice0001 uapxaervice

#3: Any name when using the client UAP simulator.

#4: Logical terminal name set as the argument of the dc_mcf_recvsync or dc_mcf_sendrecv function.

Organization of this section

3.3.1 Service request data files

3.3.2 Service response data files

3.3.3 XATMI receive data file

3.3.4 MCF receive message files

3.3.5 Operating command result data file