| 150 | Error | ANR2579 | Schedule schedule name in domain domain name for node node name failed (return code return code). | Explanation: This message is displayed when a client reports failure in executing a scheduled action. The return code reported by the client is displayed. |
| 54 | Error | ANE4042 | Object name ???filespace namepath-namefile-name??? contains one or more unrecognized characters and is not valid. | Explanation: The filename, directory name, or volume label syntax is incorrect. |
| 50 | Warning | ANR0480 | Session session number for node node name (client platform) terminated - connection with client severed. | Explanation: The specified client session is ended because the communications link has been closed by a network error or by the client program. |
| 21 | Warning | ANR0481 | Session session number for node node name (client platform) terminated - client did not respond within commtimeout seconds seconds. | Explanation: The server ends a client session because the client has been holding database locks (a transaction was in progress) and the client has not responded in the number of seconds specified by the COMMTIMEOUT parameter in the server options file. |
| 20 | Warning | ANR0484 | Session session number for node node name (client platform) terminated - protocol violation detected. | Explanation: The server ends the specified session because a communications protocol error by the client has been detected. |
| 20 | Warning | ANR0444 | Protocol error on session session number for node client node name (client platform) - out-of-sequence verb (type verb name) received. | Explanation: The server detects a protocol error on the specified session because a verb has been received that does not adhere to the client-server exchange sequence. |
| 18 | Warning | ANR0482 | Session session number for node node name (client platform) terminated - idle for more than idletimeout minutes minutes. | Explanation: The server ends a client session because it has been idle for more minutes than specified in the IDLETIMEOUT parameter in the server options file. The client program will automatically attempt to reconnect to the server when necessary. |
| 13 | Warning | ANR2997 | The server log is log full percentage percent full. The server will delay transactions by delay time milliseconds. | Explanation: The server log utilization is very high. In order to prevent the server log from becoming full, the server will begin delaying transactions by the specified amount of time. |
| 13 | Warning | ANR0483 | Session session number for node node name (client platform) terminated - forced by administrator. | Explanation: The server ends a client session in response to a CANCEL SESSION command issued by an authorized administrator. |
| 12 | Warning | ANR2576 | An attempt was made to update an event record for a scheduled operation which has already been executed - multiple client schedulers may be active for node node name. | Explanation: The server has attempted to update an event record for a scheduled operation for the specified client node. However, the existing event record shows that this scheduled operation has already been executed, either successfully or unsuccessfully. Two or more client schedulers may be running for this node. |
| 6 | Warning | ANR0524 | Transaction failed for session session number for node node name (client platform) - data transfer interrupted. | Explanation: The database transaction associated with session session number was aborted because data transfer to or from data storage was interrupted by an external event. |
| 6 | Warning | ANR8213 | Session open with node name timed out. | Explanation: The server attempts to contact the indicated node name. The attempt is unsuccessful. |
| 1 | Error | ANE4023 | Error processing ???filespace namepath-namefile-name???: file input/output error | Explanation: An error was found while reading from or writing to the file. |
| 1 | Error | ANE4021 | Error processing ???filespace namepath-namefile-name???: file system not ready | Explanation: The file system/drive was not ready for access. |
| 1 | Warning | ANR0536 | Transaction failed for session session number for node node name (client platform) - downlevel client does not support format of stored files. | Explanation: A client attempts to perform an operation involving files that are stored in a format that is not supported by that client level. |
| 1 | Error | ANR4724 | During the backup of node node (Node id) filespace filespace name (filespace id) a deletion activity occurred. | Explanation: During full or incremental backup processing, files were deleted from the file space. The files were not deleted by expiration, but by some other process. DELETE FILESPACE, DELETE VOLUME, AUDIT VOLUME, or some other administrator command can cause files to be deleted. The file space image on the server will not be consistent with the client until an incremental backup is completed for the node. |
| 1 | Warning | ANE4900 | Schedule ???schedule name??? has opened a new session with the server. | Explanation: A scheduled event ended due to a connection failure. The scheduled event had to be restarted outside of its normal start-up window to continue the operation. |