OpenTP1 Version 7 Tester and UAP Trace User's Guide
Table 6-1 lists the types of errors that may occur with the online tester and their probable causes.
Table 6-1 Online tester errors and causes
Error | Cause | Manual reference |
---|---|---|
Online tester command does not terminate normally. | No online tester definition in system definition. | 6.1.2 (1) |
Incorrect option or command argument. | ||
File for command execution cannot be accessed. | ||
UAP trace information not collected. | No test target specified in system definition. | 6.1.2 (2) |
Zero specified in max_trace_file_size operand in the system definition. | ||
Zero specified in UAP_trace_max operand in the system definition. | ||
Send messages not collected. | No test target specified in system definition. | 6.1.2 (3) |
Zero specified in max_message_file_size operand in the system definition. | ||
Number of send messages exceeds the upper limit. | ||
No send data collected for interactive service requests. | Output of send data not defined in the system definition. | 6.1.2 (4) |
Test UAP does not start. | Test user ID not set. | 6.1.4 (1) |
No test target specified in system definition. | ||
UAP does not start in non-test mode. | Specified as a test UAP in the system definition. | 6.1.4 (2) |
dc_rpc_open function in a test UAP returns an error. | No online tester definition in the system definition. | 6.1.4 (3) |
Test UAP restarted with _uto as the test user ID. | Conflict in UAP status control between the OpenTP1 system and the online tester. | 6.1.4 (4) |
Test UAP does not recover after abnormal termination. | Test UAP interlocked to the debugger. | 6.1.4 (5) |
Debugger-interlocked UAP frequently causes a time-out error. | Incorrect value specified for the monitoring time in the user service definition. | 6.1.4 (6) |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.