OpenTP1 Version 7 Tester and UAP Trace User's Guide
(1) Syntax
(a) set format
[set uto_server_count=maximum no. of test user servers]
[set max_trace_file_size=maximum size of trace files]
[set max_message_file_size=maximum size of MCF send
message file]
[set watch_time=max reply wait time]
[set rpc_trace=Y|N]
[set rpc_trace_name="name of the file for collecting RPC
trace information"]
[set rpc_trace_size=size of the file for collecting RPC
trace information]
|
(b) Command format
{{[<INDEXWORD PRONOUNCE="utoterm" INDEXITEM="utoterm" PARENTPRONOUNCE="Tester Service Definition" PARENTITEM="Tester Service Definition">utoterm</INDEXWORD> [-p OSITP|other] logical-terminal-name]}}
|
(2) Function
Defines the environment for executing online tester services.
(3) Explanation
(a) set format
Operands
- uto_server_count ~<unsigned integer> ((0-240)) <<64>>
Specify the maximum number of user servers that can be activated for testing by the online tester.
- max_trace_file_size ~<unsigned integer> ((0-2000000)) <<64>> (unit: Kbytes)
Specify the maximum size of each trace file for storing UAP trace information. As the header (management information) in a trace file is 128 bytes, add 128 bytes to the value you wish to specify.
When zero is specified, the online tester does not collect UAP trace information.
Up to two trace files are created for each tester user ID. This prevents erasure of the trace information when a trace file becomes full.
Whenever a trace file becomes full, the trace information must be backed up, and then the full trace file is deleted. Prevent the trace file from becoming full by specifying sufficient size.
The maximum trace file size that can be specified for an OpenTP1system is given by the following equation:
- Maximum size of trace file =
- (value specified in max_trace_file_size operand) x 2 x (number of users) x 1,024 bytes
- max_message_file_size ~<unsigned integer> ((0-2000000)) <<64>> (unit: Kbytes)
Specify the maximum size of the MCF send message file for storing messages sent by the following functions when the online tester's MCF simulator is used:
- dc_mcf_send function
- dc_mcf_reply function
- dc_mcf_sendsync function
- dc_mcf_sendrecv function
- dc_mcf_execap function
As the management information data in each send message is 128 bytes, and the header (management information) in the MCF send message file is 128 bytes, add 128 bytes to the value you wish to specify.
When zero is specified, the online tester does not collect send messages.
An MCF send message file is created for each test user ID. The maximum size that can be specified for a MCF send message file in an OpenTP1 system is given by the following equation:
- Maximum size of MCF send message file =
- (value specified in max_message_file_size operand) x (number of users) x 1,024 bytes
- watch_time ~<unsigned integer> ((0-62535)) (unit: seconds)
When using remote procedure calls (RPCs) for inter-process communication, specify the maximum wait time for return of a service reply after a service request is sent.
OpenTP1 may suspend termination processing for the length of time specified in this operand. Therefore, if you specify a large value, the termination processing of OpenTP1 may take some time.
If no reply has been received when the specified time elapses, the RPC returns a send/receive timeout error.
When zero is specified, the system remains in wait state indefinitely.
When you specify zero, OpenTP1 may not terminate.
When specification is omitted, the value specified in the watch_time operand of the system common definition is assumed.
- rpc_trace=Y|N ~<<N>>
Specify whether to collect RPC traces.
- Y
- Collect RPC traces.
- N
- Do not collect RPC traces.
When specification is omitted, the value specified in the rpc_trace operand in the system common definition is assumed.
- rpc_trace_name ~<pathname> <<$DCDIR/spool/rpctr>>
Specify the pathname of the file for collecting RPC traces.
In the pathname, the maximum length of the name of the file for acquiring the RPC trace is 13 characters. The default file name is rpctr.
To specify an environment variable in a pathname, make sure that the pathname begins with the environment variable (example: $DCDIR/tmp/file-name).
When specification is omitted, the value specified in the rpc_trace_name operand in the system common definition is assumed.
- rpc_trace_size ~<unsigned integer> ((1024-2147483648)) <<4096>> (Unit: bytes)
Specify the size of the file for collecting RPC traces.
When specification is omitted, the value specified in the rpc_trace_size operand in the system common definition is assumed.
(b) Command format
See below.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.