File I/O and IPC Error Codes
This topic describes the error codes that may be returned to the SETTING variable during the execution of a file I/O or interprocess communication (IPC) DataBasic statement.
File I/O Error Codes
After each execution of one of the DataBasic file I/O statements, if the SETTING clause is included, the SETTING variable is assigned a value.
-
If the statement executes successfully, the SETTING variable is set to zero (or in some cases a particular value related to statement execution) and the THEN clause of the statement (if any) is executed.
-
If execution of the statement fails, the SETTING variable is assigned an error code corresponding to the type of error and the ON ERROR or ELSE clause of the statement (if any) is executed. The tables below specify the possible error codes for a failure in the statements listed.
Statement Failed |
Possible Error Codes |
Error Message |
---|---|---|
201 |
'file' IS NOT A FILE NAME |
|
202 |
'item' NOT ON FILE |
|
202 |
'item' NOT ON FILE |
|
202 |
'item' NOT ON FILE |
|
302 |
UPDATE OPERATION FAILED |
|
202 |
item' NOT ON FILE |
Note
Error B44 occurs if the file has been opened with the OPENSEQ statement, instead of the OPEN statement.
IPC Error Codes
If an inter process communication (IPC) statement executes successfully, the SETTING variable is set to zero (or in some cases a particular value related to statement execution) and the THEN clause of the statement (if any) is executed.
If an IPC error is detected while executing an IPC statement, the SETTING variable is set to one of the network error codes listed in the table below.
Code |
Error Message |
---|---|
4224 |
No process available |
4225 |
Timeout error |
4226 |
Session Manager not running |
4227 |
Port not available |
4228 |
Invalid account or password |
4229 |
Error in device definition item |
4230 |
Invalid system name |
4231 |
Invalid server name |
4232 |
Protocol error |
4233 |
Controller I/O failure |
4234 |
Qualifier or data too long |
4235 |
Circuit disconnected |
4236 |
Circuit aborted |
4237 |
Device not ready |
4238 |
Data not yet available |
4239 |
Invalid device name |
4240 |
Device active |
4241 |
Device not active |
4242 |
Virtual port not available |
4243 |
Protocol not supported |
4244 |
Connection refused |
4245 |
Too many indirect links |
4246 |
Error in route definition |
4247 |
Connection type requested is not available |
4248 |
Too many devices |
4249 |
Line status change |
4250 |
Break received |
4251 |
Unable to log to a remote account from a linked port |
4253 |
Invalid port number |
4255 |
No supervisor running for this device |
4258 |
Connection Rejected |