


AcuServer returns an error code whenever an AcuServer file access fails.
An error code of "9B" indicates that the requested operation is not supported. Other 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,105 indicates that the number of users attempting to use AcuServer exceeds the number of users authorized by your license. For connections with the ACUCOBOL-GT Web Plug-in, it means that the number of plug-in users trying to use AcuServer exceeds the number of ACUCOBOL-GT runtime licenses on the server machine. If your COBOL program receives a file status code 9D,105 in connection with plug-in users, it should display a message box stating that the Web file server is busy, and to please retry later. 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 |