OpenTP1 Version 7 Messages
stops command processing because of error. reason code=aa...aa
Reason code | Meaning | Countermeasure |
---|---|---|
2 | A parameter error occurred in a shared memory function. | Contact maintenance personnel. |
3 | Required segment size is larger than the entire pool size of shared memory. | Check the shared memory size specified in the definition. |
4 | An attempt to share a segment allocated by another process was made. However, the segment is not yet allocated by any other process. | Check the execution state of journal or checkpoint dump service with the command provided by OpenTP1, wait till the state becomes online, and then re-execute the command. |
5 | Function executed in incorrect order | |
6 | The capacity of shared memory pool is insufficient. | Check the shared memory size specified in the definition. |
7 | Failure in lock processing for shared memory pool | Contact maintenance personnel. |
11 | Invalid argument | |
12 | Function input in incorrect order | |
13 | A fatal or unexpected error occurred. | -- |
14 | Memory shortage | Check available memory size. |
15 | A network failure occurred. | Examine the cause of the error according to the following procedure, and then take corrective action. (1)Check the node connection state with the command provided by the operating system. (2)Check the execution state of each server with the command provided by OpenTP1. |
16 | Send/receive timeout | |
17 | The input parameter length exceeds the limit. | |
18 | The returned reply is too large to be contained in the caller's area. | |
19 | The service is not cataloged. | |
20 | The server is terminating. | |
21 | There is no process to provide the service. | |
22 25 |
An unexpected error occurred. | |
23 | RPC environment is not started. | |
26 | Name information retrieval error | Contact maintenance personnel. |
27 | Argument specification error | |
28 | Process-specific memory cannot be allocated. | Check available memory size. |
29 | The versions are inconsistent between the function and shared memory or daemon. | Examine the cause of the error according to the following procedure, and then take corrective action. (1)Check the node connection state with the command provided by the operating system. (2)Check the execution state of each server with the command provided by OpenTP1. |
31 | A function parameter error occurred. | |
32 | Function input in incorrect order | |
35 | Timeout | |
36 | A network failure occurred. | |
37 | Service information must be retrieved with nam daemon (for the server on the client machine), but nam daemon is starting, terminating, or suspended. | |
40 | The key value already exists. | Check the status service definitions or initialization. |
41 | I/O error | Examine the cause of the I/O error and then take corrective action. |
42 | The offset plus length is out of the range of allocation area. | Contact maintenance personnel. |
43 | Work area cannot be allocated. | Check available memory size. |
44 | Insufficient number of buffer areas | Check the status service definitions. |
45 | Records equivalent to required size cannot be allocated (insufficient status file capacity). | |
46 | No record corresponds to the key value. | Contact maintenance personnel. |
47 | Status server is not operating. | Check the execution state of the server with the command provided by OpenTP1. |
48 | The offset is out of the range of allocation area. | Contact maintenance personnel. |
49 | Incorrect parameter format | Contact maintenance personnel. |
50 | Inter-process communication error | Check the execution state of the server with the command provided by OpenTP1. |
51 | Required size is incorrect. | Contact maintenance personnel. |
52 | Swapping error | |
53 | Protocol version error | |
54 | The key value is already allocated with a different size. | Contact maintenance personnel. |
80 84 86 87 |
The value specified for array size exceeds the defined maximum value. | |
81 82 |
Area cannot be allocated. | Check available memory size. |
83 | An error occurred during data conversion. | Contact maintenance personnel. |
85 | The text received from the function cannot be resolved into arguments because it is short. | |
96 | Discrepancy in the program | |
97 | The file size is invalid. | Check the size of the checkpoint dump file. |
98 | CPD I/O error | Examine the cause of the error and then take corrective action. |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.