(a) Syntax

{SPP|MHP}={service-group-name|service-name}
           execution-format-program-name
           user-service-definition-file-name
           [T]
           [{F|D debugger-name|[N][D debugger-name]}]{,|;}

(b) Function

Defines the following items for the UAP to be tested by the offline tester:

• UAP type (SPP or MHP)
• Service group name
• Name of the execution format program for the service group
• Name of the user service definition file for the service group
• Whether to use the server UAP simulator
• Whether to connect a debugger

A UAP definition can only be written for an SPP or MHP. SUPs cannot be tested by the offline tester.

(c) Operands

• SPP|MHP
  Specify the type of service group as the definition name, as follows:
  

  SPP

  SPP service group

  MHP

  MHP service group

• service-group-name
  Specify the service group name. To use the UAP simulator with a TxRPC interface, specify the interface name that is specified in the IDL file.
  
• service-name
  Specify the service name to use the server UAP simulator with an XATMI interface.
  
• execution-format-program-name
  Specify the name of the UAP (execution format program) that executes the service group. A non-existent name can be specified when simulating service functions.
  
• user-service-definition-file-name
  Specify the name of the user service definition file that contains the environment definition for executing the service group. To use the UAP simulator with a TxRPC interface, specify the name of the user service definition file created by the txidl command. A non-existent name can be specified when simulating service functions.
  
• T
  Specify this operand to use the UAP simulator with a TxRPC interface. This operand can be specified only when SPP is specified for the service group type. If MHP is specified, specifying this option causes an error.
  
• F
  Specify this operand to use the server UAP simulator. If specification is omitted, the service group is activated at offline tester startup.
  
• D debugger-name[debugger-argument]
  Specify this operand to run the UAP under debugger control. Either of the following debugger names can be specified, but no name check is performed:
  

  dbx

  To use the dbx debugger

  cbltd

  To use the COBOL85/TD debugger

  The argument to be passed to the debugger can also be specified. When no argument is specified, the name specified in execution-format-program-name becomes the argument.
  As the argument, specify the executable file name, using the same name as specified in execution-format-program-name. No error occurs if the names differ, but the specified executable file name is passed to the debugger, while the offline tester uses the execution format program name to control the debugger.
  
• N
  Specify this operand to suppress activation of the service group (UAP) at offline tester startup and to activate the service group by start subcommand after the offline tester starts.
  When specification is omitted, the service group (UAP) is activated at offline tester startup.
  

(d) Note

A service group name can only be specified once. If duplicated, the first definition is valid. In the following example, spp1 is specified twice and the definition of the second line causes an error.

Example:

SPP = spp1 spp1.load spp1usr, SPP = spp1 spp2.load spp2usr, Error occurs.

(e) Definition example

# UAP definition
SPP = spp1 spp1.out spp1usr,
SPP = spp2 DUMMY    DUMMY   F,
SPP = spp3 spp3.out spp3usr D dbx,
SPP = spp4 spp4.out spp4usr,
SPP = spp5 spp5.out spp5usr N D dbx -I /betran/utf/uap/src
      spp5.out,
MHP = mhp1 mhp1.out mhp1usr;
#

(a) Syntax

rpc_message = directory-name-of-RPC-request-data-file{,|;}

(b) Function

Defines the name of the directory that contains the RPC request data file. If the name is specified more than once, the last definition is valid.

(c) Operands

• rpc_message
  Write rpc_message as the definition name.
  
• directory-name-of-RPC-request-data-file
  Specify the pathname of the directory that contains the RPC request data file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for RPC request data file
rpc_message = /betran/utf/rpcmsg;
#

(a) Syntax

tp_message = directory-of-XATMI-request-data-file{,|;}

(b) Function

Defines the name of the directory that contains the XATMI request data file. If the name is specified more than once, the last definition is valid.

(c) Operands

• tp_message
  Write tp_message as the definition name.
  
• directory-name-of-XATMI-request-data-file
  Specify the pathname of the directory that contains the XATMI request data file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for XATMI request data file
tp_message = /betran/utf/xatmimsg;
#

(a) Syntax

txrpc_message = directory-name-of-TxRPC-request-data-file{,|;}

(b) Function

Defines the name of the directory that contains the TxRPC request data file. If the name is specified more than once, the last definition is valid.

(c) Operands

• txrpc_message
  Write txrpc_message as the definition name.
  
• directory-name-of-TxRPC-request-data-file
  Specify the pathname of the directory that contains the TxRPC request data file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for TxRPC request data file
txrpc_message = /betran/utf/txrpcmsg;
#

(a) Syntax

rpc_return_data = directory-name-of-RPC-response-data-file{,|;}

(b) Function

Defines the name of the directory that contains the RPC response data file. If the name is specified more than once, the last definition is valid.

(c) Operands

• rpc_return_data
  Write rpc_return_data as the definition name.
  
• directory-name-of-RPC-response-data-file
  Specify the pathname of the directory that contains the RPC response data file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for RPC response data file
rpc_return_data = /betran/utf/rpc_return;
#

(a) Syntax

tp_return_data = directory-name-of-XATMI-response-data-file{,|;}

(b) Function

Defines the name of the directory that contains the XATMI response data file. If the name is specified more than once, the last definition is valid.

(c) Operands

• tp_return_data
  Write tp_return_data as the definition name.
  
• directory-name-of-XATMI-response-data-file
  Specify the pathname of the directory that contains the XATMI response data file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for XATMI response data file
tp_return_data = /betran/utf/tp_return;
#

(a) Syntax

txrpc_return_data = directory-name-of-TxRPC-response-data-file{,|;}

(b) Function

Defines the name of the directory that contains the TxRPC response data file. If the name is specified more than once, the last definition is valid.

(c) Operands

• txrpc_return_data
  Write txrpc_return_data as the definition name.
  
• directory-name-of-TxRPC-response-data-file
  Specify the pathname of the directory that contains the TxRPC response data file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for TxRPC response data file
txrpc_return_data = /betran/utf/tx_return;
#

(a) Syntax

tp_converse = directory-name-of-XATMI-send/receive-data-file{,|;}

(b) Function

Defines the name of the directory that contains the XATMI send/receive data file. If the name is specified more than once, the last definition is valid.

(c) Operands

• tp_converse
  Write tp_converse as the definition name.
  
• directory-name-of-XATMI-send/receive-data-file
  Specify the pathname of the directory that contains the XATMI send data file and XATMI receive data file. Add the directory name for the files if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for XATMI send/receive data file
tp_converse = /betran/utf/tp_converse;
#

(a) Syntax

mcf_message = directory-name-of-MCF-receive-message-file{,|;}

(b) Function

Defines the name of the directory that contains the MCF receive message file. If the name is specified more than once, the last definition is valid.

(c) Operands

• mcf_message
  Write mcf_message as the definition name.
  
• directory-name-of-MCF-receive-message-file
  Specify the pathname of the directory that contains the MCF receive message file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for MCF receive message file
mcf_message = /betran/utf/mcfmsg;
#

(a) Syntax

adm_call_cmd = directory-name-of-operating-command-result-data-file{,|;}

(b) Function

Defines the name of the directory that contains the operating command result data file. If the name is specified more than once, the last definition is valid.

(c) Operands

• adm_call_cmd
  Write adm_call_cmd as the definition name.
  
• directory-name-of-operating-command-result-data-file
  Specify the pathname of the directory that contains the operating command result data file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for operating command result data file
adm_call_cmd = /betran/utf/etc/call_cmd_val;
#

(a) Syntax

cmdfile = directory-name-of-continuous-execution-command-file{,|;}

(b) Function

Defines the name of the directory that contains the continuous execution command file. If the name is specified more than once, the last definition is valid.

(c) Operands

• cmdfile
  Write cmdfile as the definition name.
  
• directory-name-of-continuous-execution-command-file
  Specify the pathname of the directory that contains the continuous execution command file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# directory definition for continuous execution command file
cmdfile = /betran/utf/etc;
#

(a) Syntax

damfile = logical-file-name physical-file-name [N]{,|;}

(b) Function

Associates a logical file name with a physical file name for simulating the DAM service.

Definitions must be written for all the DAM files accessed by the UAP.

(c) Operands

• damfile
  Write damfile as the definition name.
  
• logical-file-name
  Specify the logical file name.
  
• physical-file-name
  Specify the name of the DAM file to be used by the offline tester. Add the directory name if different from the directory in which the offline tester is currently executing.
  
• N
  Specify to disable lock, regardless of any function specification.
  

(d) Definition example

# DAM file definitions
damfile = damfile1 /betran/utf/dam/damfile1,
damfile = damfile2 /betran/utf/dam/damfile2 N;
#

(a) Syntax

tamtable = TAM-table-name TAM-file-name [N]{,|;}

(b) Function

Associates TAM table names with TAM file names for simulating the TAM service.

Definitions must be written for all the TAM files accessed by the UAP.

(c) Operands

• tamtable
  Write tamtable as the definition name.
  
• TAM-table-name
  Specify the TAM table name (name used by TAM service functions).
  
• TAM-file-name
  Specify the name of the TAM file to be used by the offline tester. Add the directory name if different from the directory in which the offline tester is currently executing.
  
• N
  Specify to disable lock, regardless of any function specifications. This operand must be specified for a UAP written in COBOL that accesses TAM files.
  

(d) Definition example

# TAM file definitions
tamtable = tamtable1 /betran/utf/tam/tamfile1,
tamtable = tamtable2 /betran/utf/tam/tamfile2 N;
#

(e) Note

• Each TAM file and TAM table name can only be specified once. If duplicated, the first definition is valid.

(a) Syntax

isttable = IST-table-name record-length record-count{,|;}

(b) Function

Specifies an internode shared table used for the IST service simulation using a set of the internode shared table name, record length, and record count.

Define all internode shared tables accessed by the UAP. Up to 64 internode shared tables can be defined.

(c) Operands

• isttable
  Write isttable as a definition name.
  
• IST-table-name
  Specify the internode shared table name. It is used for the IST service function.
  
• record-length
  Specify the record length in the internode shared table in bytes.
  
• record-count
  Specify the number of records in the internode shared table.
  

(d) Definition example

# IST table definition
isttable = isttbl1 8 12,
isttable = isttbl2 10 20;
#

(a) Syntax

func_value_file = function-return-values-file-name{,|;}

(b) Function

Defines the name of the file in which function return values are set. If the name is specified more than once, the last definition is valid.

(c) Operands

• func_value_file
  Write func_value_file as the definition name.
  
• function-return-values-file-name
  Specify the name of the function return values file. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# definition of function return values file
func_value_file = /betran/utf/etc/return_val;
#

(a) Syntax

tracefile = trace-file-name{,|;}

(b) Function

Defines the name of the file for storing offline tester trace information. If the name is specified more than once, the last definition is valid.

(c) Operands

• tracefile
  Write tracefile as the definition name.
  
• trace-file-name
  Specify the trace file name. Add the directory name if different from the directory in which the offline tester is currently executing.
  

(d) Definition example

# trace file definition
tracefile = /betran/utf/log/trace;
#

(a) Syntax

protocol = protocol-name{,|;}

(b) Function

Defines MCF protocol. This definition is valid only when testing a UAP written in COBOL or DML. Omit the definition for protocols other than OSI TP.

If the protocol is specified more than once, the last definition is valid.

(c) Operands

• protocol
  Write protocol as the definition name.
  
• protocol-name
  Specify the protocol name, as follows:
  

  OSI/TP

  OSI TP protocol is used.

  An error occurs if a protocol other than OSI TP is specified.
  

(d) Definition example

# protocol definition
protocol = OSI/TP;
#