Each tester file is written in a specific data format. However, the user can easily create the tester files by command input, using the online tester. This is called the tester file creation facility.

Table 2-1 lists the tester files that can be created with the tester file creation facility.

Table 2-1 Tester files created by tester file creation facility

Tester files		Creator	Simulator using the tester file
Service request data files	RPC request data file	User	Client UAP simulator
	XATMI request data file	User	Client UAP simulator
Service response data files	RPC response data file	User	Server UAP simulator
		Online tester	Client UAP simulator
	XATMI response data file	User	Server UAP simulator
		Online tester	Client UAP simulator
XATMI receive data file		User	Client UAP simulator
MCF receive message files	Asynchronous receive message file	User	MCF simulator
	Synchronous receive message file	User	MCF simulator
Operating command result data file		User	Operating command simulator

The tester file creation facility is used to create tester files with one of following two methods:

• Using the test data definition file
  Creation of a tester file can use data from the test data definition file created by the user. The user can create the test data definition file using a text editor. This file can contain data for multiple tester files.
  
• Using journal data
  Creation of a tester file can use record data from an unload journal file or trace data from an RPC trace file. To use journal data, extract it using an operating command.
  Commands for extracting data and data types depend on kinds of tester files to be created. Using journal data disallows creation of an operating command result data file. Table 2-2 lists the kinds of tester files to be created, corresponding data extraction commands, and available data.
  

  Table 2-2 Kinds of tester files to be created, available data extraction commands, and available data

  Tester file name	Data extraction command	Available data
  RPC request data file	rpcdump	First effective RPC request send data out of RPC trace data extracted by the rpcdump command.
  XATMI request data file	rpcdump	First effective tpcall or tpacall function data out of XATMI request/response request send data in RPC trace data extracted by the rpcdump command. First effective tpconnect function data out of XATMI interactive request send data in RPC trace data extracted by the rpcdump command.
  RPC response data file	rpcdump	First effective RPC request send data out of RPC trace data extracted by the rpcdump command.
  XATMI response data file	rpcdump	First effective tpreturn function data out of XATMI request/response and interactive request send data in RPC trace data extracted by the rpcdump command.
  XATMI receive data file	rpcdump	All tprecv function data out of XATMI interactive receive data in RPC trace data extracted by the rpcdump command.
  Asynchronous receive message file	jnlrput	ij record data and mj record input message data in unload journal files extracted by the jnlrput command. When two or more record data entries are available, the system accepts data entries whose order identifier begins with s or l.
  Synchronous receive message file	jnlrput	Input message data in mj records from unload journal files extracted by the jnlrput command.
  Operating command result data file	--	--

  Legend:

  --: No files are created from journal data or trace data.