![[Contents]](FIGURE/CONTENT.GIF)
OpenTP1 Version 7 Operation
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
The following table lists the error events and their possible causes.
Table 10-1 Error events and causes
| Event | Cause | Reference section for remedy |
|---|---|---|
| UAP cannot be started. | System definitions are invalid. | 10.5 UAP errors |
| Memory is inadequate. | ||
| UAP does not terminate its processing. | Error in UAP. | |
| UAP terminates abnormally. | Error in UAP or OpenTP1. | |
| UAP linkage is invalid. | ||
| UAP deadlock occurs. | Looping of a lock request has occurred between UAPs. | |
| OpenTP1 cannot be started. | OpenTP1 has not been correctly installed or set up. | 10.6 OpenTP1 errors |
| OpenTP1 system definitions are invalid. | ||
| Memory or disk space is inadequate. | ||
| File required in order to start OpenTP1 is missing. | ||
| OS configuration is inappropriate to OpenTP1 execution environment. | ||
| TCP/IP environment has not been set up. | ||
| Hardware error (disk or LAN). | ||
| A user initialization command is invalid. | ||
| Process service processing is interrupted. | ||
| Entering dcstop command does not terminate OpenTP1. | UAP processing takes too long, or there is an error in the UAP processing, and the UAP does not terminate its processing. | |
| At the time of normal termination, messages accumulated in the output queue are not output due to a communication error, etc. | ||
| The OpenTP1 at the archive-journal node does not terminate because the connected journal service does not terminate. | ||
| The OpenTP1 at the archive-journal source node does not terminate because the connection to the global archive journal cannot be released. | ||
| OpenTP1 terminates abnormally. | OpenTP1 system service or user server was terminated by the kill command. | 10.2 OpenTP1 file errors |
| Error in OpenTP1. | ||
| Journal file group to be swapped in is missing. | ||
| There is no spare status file for A or B system. | ||
| Current status file for A or B system cannot be read. | ||
| Error occurred in MCF definition file. | ||
| Error occurred in MCF queue file. | ||
| Error in the user exit routine. | ||
| Error in the UAP. | ||
| OpenTP1 operation command does not terminate normally. | Specification of an option or command argument is invalid. | 10.6 OpenTP1 errors |
| Environment required in order to execute the operation command has not been set up. | ||
| User is not authorized to execute the operation command. | ||
| Response-wait overtime occurs for an OpenTP1 operation command. | Processing is not completed within the response wait time, because the OS workload is high. | |
| File I/O error occurs. | Error has occurred in the file. | 10.2 OpenTP1 file errors and 10.3 File errors |
| File error message is output. | ||
| Communication error message is output. | Error has occurred in the protocol. | 10.4 Communication errors |
| Error has occurred on the LAN. |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.