![[Contents]](FIGURE/CONTENT.GIF)
OpenTP1 Version 7 Messages
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
cannot execute aaaaaaaa command because of bbbb-cc.
| Reason code | Meaning | Operator's action | OpenTP1 administrator's action |
|---|---|---|---|
| 101 | Memory is insufficient. | Wait for the running process to end and then re-execute the command. If a system call message precedes, take action according to it. | Re-estimate memory. |
| 102 | Shared memory library service cannot be provided because the number of segments in shared memory attached to the read process exceeds the limit specified for the system. | Take action according to the preceding system call message if any. | Re-estimate shared memory. |
| 103 | A network failure occurred. Possible causes are:
|
Examine the cause 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. |
-- |
| 104 | Journal service is not online, or necessary information in shared memory cannot be referenced. | Check the execution state of journal service with the command provided by OpenTP1. After journal service becomes online, re-execute the command. | -- |
| 105 | Timeout was detected during command execution. | Find the cause of the command timeout using output messages, then re-execute the command if necessary. | -- |
| 106 | Shared memory cannot be used. | Take action according to the preceding system call error message. | -- |
| 107 | A system call error occurred. | Examine the cause according to the preceding system call error message. | -- |
| 108 | An invalid option is specified for a nonduplicated system. | Re-execute the command with only options that can be specified for a nonduplicated system. | -- |
| 110 | The command cannot be specified in the execution environment of the system. | For a command that specifies the file type, check the options of the command. Check also the execution environment of the system. | -- |
| 111 | The program products required for command execution are not installed. | Check if the program products required for command execution are installed. | -- |
| 201 | The file name is incorrect. | Re-execute the command with the correct file name. | -- |
| 202 | The specified special file name is not of character type, or no device is associated with the special file. | Check the specified special file name and then re-execute the command. | -- |
| 203 | The device specified with path is not initialized for the OpenTP1 file system. | Check the file name. If it is correct, initialize the device for the OpenTP1 file system. | -- |
| 204 | The file already exists. | Check the file name. If it is correct, remove the file with the jnlrm command and then re-execute the jnlinit command. | -- |
| 205 | The area for file creation cannot be allocated. | Change the device in which a file is to be created; or, remove unnecessary files; or, back up the file, re-create an OpenTP1 file with the filmkfs command and then restore that file. | Re-estimate the file. |
| 206 | The number of files exceeded the upper limit specified at file system initialization. | ||
| 207 | The upper limit was exceeded when opening a character-type special file. | Re-execute the command without opening unnecessary files in the process. | -- |
| 208 | There is no authority for access to the specified special file. | Check for access authority with the fills command. | -- |
| 209 | An I/O error occurred upon access to a journal file created on the OpenTP1 file system. | Examine the cause of the I/O error and take corrective action; or, re-create the OpenTP1 file system on another disk drive or partition. | -- |
| 210 | The OpenTP1 file system version is inconsistent. | Re-create the OpenTP1 file system. | -- |
| 211 | There is no authority for access to the specified file. | Check for access authority with the fills command. | -- |
| 212 | The file is not found. | Re-execute the command with the correct file name. | -- |
| 216 | The specified file name is neither jnl nor cpd. | -- | |
| 221 | Lock segment shortage occurred. | -- | Check the number of record lock segments specified when configuring the operating system. |
| 222 | The journal file is being used by another process. | Check if the file specified in the command is being used by another process. If necessary, re-execute the command. | -- |
| 224 | The specified file is waiting for being unloaded. | Check the file name. If it is correct, unload the file with the julunlfg or jnlchgfg command or re-execute jnlrm with the -u option specified. | -- |
| 301 | The file already exists. | Check the file with the command provided by the operating system (OS) and then re-execute the desired command with the correct file name. | -- |
| 302 | The specified file name is a directory. | -- | |
| 303 | An error occurred when opening the unload journal file created on the OS file. | Examine the cause according to the preceding open system call error message. | -- |
| 304 | An error occurred when closing the unload journal file created on the OS file. | Examine the cause according to the preceding close system call error message. | -- |
| 306 | There is no access authority regarding the point information file. | Examine the I/O error for its cause, take corrective action, and execute the command again. | -- |
| 403 | An error occurred when opening the definition file. | Examine the cause according to the preceding definition file opening error message. | -- |
| 404 | An error occurred when opening the analysis file. | Examine the cause according to the preceding analysis file opening error message. | -- |
| 405 | An error was detected during definition analysis processing. | Examine the cause according to the preceding analysis error message. | -- |
| 406 | A specification error exists in the jnldfsv definition command for journal service definition. | -- | Check the jnldfsv definition command for journal service definition. |
| 417 | An error occurred during name service definition analysis. | Check the specification of the name service definition. | -- |
| 521 | The journal service is not being restarted. | -- | -- |
| 701 | The file group is not found. | Check the state of the file group with the jnlls command, and then re-execute the command if necessary. If a definition file analysis error precedes, examine the cause according to the definition analysis error message. | -- |
| 702 | Opening the file group failed. | Examine the cause of the failure and take action according to the reason code in the KFCA01200-E or KFCA01201-E message output to the log file. | -- |
| 703 | Closing the file group failed. | -- | |
| 704 | The file group is already open. | Check the state of the file group with the jnlls command and then re-execute the command with the correct file group name. | -- |
| 705 | The file group is already closed. | -- | |
| 706 | The file group cannot be closed. | -- | |
| 707 | The file group is being used for system recovery processing or with the jnlunlfg or jnlchgfg command. | -- | |
| 708 | The file group cannot be closed because there is no other overwritable file group. | -- | -- |
| 709 | File opening was canceled because there was another file group in the same generation. | Remove the physical file of the file group with the jnlrm command and then re-create it with jnlinit. | -- |
| 710 | Specified file group is current. | Check the state of the file group with the jnlls command, then re-execute the command if necessary. | -- |
| 1101 | Opening every target physical file failed. | Follow the KFCA01240-E message output to the log file. | -- |
| 1301 | Specified resource group name is not found. | Using the jnlls command, check the resource group name. | -- |
| 1401 | The specified node is not connected to the specified archive resource group. | Specify a node that is connected to a specified archive resource group. | -- |
| 1501 | The error occurred when assignment for the unload journal file was attempted. | Remove the cause according to the previous error message and execute the command again. | -- |
| 1502 | The error occurred when attempting to open the unload journal file. | -- | |
| 1503 | The error occurred when attempting to close the unload journal file. | -- | |
| 1504 | The error occurred when attempting to gain access to the unload journal file. | Remove the cause according to the previous error message and execute the command again. | -- |
| 1505 | A time that cannot be converted in the system was specified. | Check the specified time, and then re-execute the command. | -- |
| 1601 | There is no journal file that can be unloaded or whose status can be changed. The element files that make up the file group are too few. | Check the specified file group name. | -- |
| 1602 | Block omission was detected in the journal file. | The journal file may be damaged. Cancel unloading the file group and then contact the OpenTP1 administrator. | Contact maintenance personnel. |
| 1603 | The file group has been unloaded. Or with the multinode function in use, it has been moved into the archive journal file to enable overwriting. | Check the specified file group name. | -- |
| 1604 | The value specified for the -n option of the jnlinit command is out of the range from 12 to 524287. | Re-execute the jnlinit command with the -n option specified within the range from 12 to 524287. | -- |
| 1607 | The file group is not used for online processing. | Check the specified file group name. | -- |
| 1609 | There is no file group to be unloaded. | -- | -- |
| 1610 | The specified run ID does not match the file group's run ID. | Use the jnlls command to identify the file group's run ID and execute the command again. | -- |
| 1611 | A file group to be unloaded has been overwritten while unloading. | -- | -- |
| 1612 | The failure occurred during access to the journal file. | Take corrective action according to the previous system call error message or KFCA04191-E message. | -- |
| 1621 | The specified command cannot be executed in an execution environment that does not use the automatic unload function. | Check the options of the command. Also check the execution environment of the system. | -- |
| 1622 | The command cannot be executed because the automatic unload function has already started or stopped. | Use the Jnlatunl command with the -i option to check the operating status of the automatic unload function. If necessary, start or stop the automatic unload function. | -- |
| 1623 | The jnlatunl command timed out while the system was waiting for termination of automatic unload processing. | Execute the automatic unload processing again. Alternatively, use the jnlunlfg command to unload the file. | -- |
| 1703 | The error occurred during analysis of the point information file. | Examine the point information file for the cause of the analysis error and execute the command again. | -- |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.