Troubleshooting | ODBCLink/SE Reference Manual |
Error Messages
Errors in ODBCLink/SE can come from several sources; all messages have a prefix which indicates the source of the error, as follows:
[ODBCLN32] | Generated by the |
[WINSOCK] | Comes from the Winsock driver. |
[ALLBASE] | Generated by the ALLBASE/SQL command interpreter. |
The first action you should take in case of a problem is to attempt to execute the command manually, e.g. try to login using a terminal emulator, or else try issuing the SQL statement that causes a problem in ODBCUTSE or ISQL. If you do not know the command causing the error (because you are using Microsoft Access for instance), turn on host logging and examine your ODBCLOG file.
Errors from ALLBASE/SQL or IMAGE/SQL are followed by DBERR or DBWARN and a number. These error messages are documented in the ALLBASE/SQL Message Manual or in the IMAGE/SQL Administration Guide.
Error messages are returned by ODBCLink/SE to the application. Each message is followed by a CAUSE which gives information as to why the warning or error occurred. This is followed by an ACTION which gives information on how to resolve the problem.
Note: For all other errors, refer to the appropriate documentation or manuals.
| ODBCLink/SE |
66 | ©M.B. Foster Associates Limited |
