ODBC Driver Error Messages
An error reported on the BASIS ODBC Driver has the following format:
[BASIS] [BASIS ODBC Driver] error message
Some ODBC error messages include a value for the fserr and fserrs parameters in the error text.
-
The fserr value minus 1 is equivalent to the same PRO/5 error number. For example, fserr=13 would indicate a PRO/5 !ERROR12 (Missing or Duplicate File).
-
A positive fserrs value indicates that no host error occurred.
-
A negative fserrs value indicates an underlying host error occurred. Use the absolute value of the fserrs value to determine the system error from the operating system. For example, fserrs= -92 would indicate a host error 92.
Following is a list of PRO/5 error numbers and their descriptions that may be returned by fserr:
Error |
Description |
---|---|
File/Record/Device Busy or Inaccessible |
|
End of Record |
|
End of File |
|
Disk Read/Write Error |
|
Disk Not Ready |
|
Peripheral Data Transfer Error |
|
Invalid Disk Directory |
|
Pointer Out of Range |
|
Disk Write Error/Data Miscompare |
|
Illegal File Name |
|
Missing or Duplicate Key |
|
Missing or Duplicate File |
|
Improper File/Device Address |
|
Improper File/Device Usage |
|
Disk Full |
|
Directory or Table Overflow |
|
Invalid Parameter |
|
Illegal Control Operation/Permissions Error |
|
String/Number Mismatch |
|
Workspace Memory Overflow |
|
Hardware Stack Overflow |
|
System Memory Overflow |
|
Buffer Overflow |
|
Numeric Overflow |
|
Invalid Integer |
|
Nonexistent Numeric Subscript |
|
Format Mask Overflow |
|
Invalid String Size |
|
Substring Out of Range |
|
Open of File With Invalid Header |
|
General I/O Error |
|
User limits have been exceeded |
|
Network User Error |
|
Network Error |
|
Network Gone |
|
Disk Read/Write Error occurred during a critical operation |
|
Disk Not Ready Error occurred during a critical operation |
|
Disk Pointer Out of Range occurred during a critical operation |