ContentsIndexPreviousNext

10.2 Error Codes

AcuServer returns an error code whenever an AcuServer file access fails.

AcuServer error codes have the following format:

9D,xxx

"9D" indicates a server error and is returned in your file-status variable.

You can retrieve the extended code with the "-x" runtime switch, or by calling C$RERR. Note that you can pass two parameters to C$RERR to fetch interface errors. The first parameter retrieves the two- or three-digit extended error code. This parameter must be at least PICTURE X(5). The second parameter retrieves a message associated with the error condition and should be at least PICTURE X(80).

AcuServer errors

AcuServer errors have a three-digit extended code. These errors include:

Error Code
Description
9D,100
Invalid syntax for FILE-PREFIX. The correct syntax for FILE-PREFIX is: FILE-PREFIX @server-name:pathname
9D,101
The version of the server is not compatible.
9D,102
Invalid connection password specified by client.
9D,103
Connection to server refused, access denied.
9D,104
PC/TCP resident kernel is not loaded.
9D,105
User count exceeded.

An error 9D, 101 indicates that the version of the Acucobol runtime and the version of AcuServer are incompatible. Because of a change in networking technology, AcuServer 5.0 will not work with versions of the ACUCOBOL-GT runtime prior to Version 5.0, and earlier versions of AcuServer will not work with the Version 5.0 runtime. Connecting to the server has changed so dramatically that even if a previous version of AcuServer is running, a 5.0 runtime on the client won't detect it, and you will receive an error stating that the server is not running.

An error 9D,105 indicates that the number of users attempting to use AcuServer exceeds the number of users authorized by your license. To extend the number of authorized users, please call Acucorp Customer Service.

Client runtime errors

Whenever a client runtime passes a file handle to AcuServer with a request for file access, AcuServer validates the file handle before performing any I/O using that handle. If AcuServer determines that a file handle is not valid (e.g., if the file pointer is invalid or the file is not open), it returns an error to the client runtime.

Client runtime error codes have the following format:

30,xx

"30" indicates a system error. Client runtime errors include:

Error Code
Description
30,02
No such file or directory
30,09
Bad file number