OpenTP1 Version 7 Messages
status file error occurred during checkpoint dump processing. reason code=aa...aa
Reason code | Meaning | Countermeasure |
---|---|---|
40 | The key value already exists. | Check the status service the 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 | |
50 | Inter-process communication error | Check the execution state of the server with the command provided by OpenTP1. |
51 | Required size is invalid. | Contact maintenance personnel. |
52 | Swapping error | |
53 | Protocol version error | |
54 | The key value is already allocated with a different size. | |
91 | An error occurred in the file system. | Examine the cause of the error according to the KFCA02123-W message output to the log file, and then take corrective action. |
99 | A close request was issued for an available file. | Enter the jnlls command to check the state of the file. |
100 | A close request was issued for a file under I/O processing. | Enter the jnlls command to confirm that the newest checkpoint dump file has pointed to the current journal. Then reenter the command. |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.