OpenTP1 Version 7 Tester and UAP Trace User's Guide
(1) Syntax
(a) set format
[set test_mode=target|usable|dmyspp|simmhp|no]
[set test_transaction_commit=Y|N]
[set test_adm_call_command=do|skip|file]
[set test_xatmi_send_file=Y|N]
[set test_debugger="{dbx|cbltd|cblcv}[command-argument]"]
[set test_data_trace=Y|N]
|
(b) Command format
None.
(2) Function
Enables execution of the online tester at the user server. Add the definitions to each service group in the OpenTP1 user service definition.
(3) Explanation
(a) set format
Operands
(b) Command format
None.
- When specifying simmhp in the test_mode operand, match all the other specifications in the user service definition with the SPP specifications.
- Example:
Also, specify queue in the receive_from operand.
- User service default definitions cannot be specified as online tester definitions in the user service definition. This prevents a real job UAP from being run in error in a test environment.
- When using the MCF simulator, specify Y in the atomic_update operand of the user service definition if a transaction MHP is to be executed.
- The schedule priority of a test UAP depends on value specified in the schedule_priority operand of the user service definition. When executing a test UAP concurrently with a real job UAP, consider the effect on the performance of the job UAP when specifying the priority of the test UAP.
- If zero is specified in the uap_trace_max operand of the user service definition (even if a value of 1 or higher is specified in the max_trace_file_size operand of the tester service definition), a warning message output, indicating that UAP trace information cannot be collected.
- When the online tester is not being used, the dc_rpc_open function returns an error code at activation of a UAP that has a value other than no specified in the test_mode operand. This prevents a test UAP from being run in error as a real job UAP.
- To interlock a UAP to the debugger, specify file or skip for the test_adm_call_command operand. When the UAP is interlocked to the debugger by specifying do for the test_adm_call_command operand, issuing the dc_adm_call_command function lets the UAP wait for a response, disabling debugger control. To solve this, issue the utodbgstop command to terminate the UAP, then terminate the debugger.
- Do not issue a fork system call or system(3C) function to a UAP interlocked with the debugger. Issuing these functions lets the UAP wait for a response, disabling debugger control. To solve this, issue the utodbgstop command to terminate the UAP, then terminate the debugger.
- Debugger interlocking is unavailable when running under the multi-node environment.
- If possible, avoid testing a UAP interlocked with the debugger under the OpenTP1 system where a real job UAP is active. This is to prevent a system failure caused by normal or abnormal termination of the UAP interlocked with the debugger under the OpenTP1 system where the UAP is operating.
- Consider debugger interlocking operations and operation times when specifying monitoring time values in the user service definition for the UAP interlocked with the debugger. A thoughtlessly specified value may frequently cause a time-out error.
- When do is specified for the test_adm_call_command operand for a UAP to start another UAP in the test mode using the dcsvstart command set in the argument of the dc_adm_call_command function, specify the environment variable DCUTOKEY in the user service definition of the UAP that issues the function.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.