Product Documentation

BTRV Edition User's Guide

Previous Topic

Next Topic

Driver Error Codes

The table below lists the logical error codes logged by the driver in the log file and returned by ctutil. These errors are generated internally by the driver and are converted into an error to be returned to the application. They do not match any standard Btrieve error codes.

The error codes logged by the driver in the log file are formatted as follows:


THREAD> DATE T TIME SRC:LINE:FUNCTION TYPE E1:E2:E3 MESSAGE

For example:


00002038> 20150506T105656 api:5248:ctl_regins ERROR 19:133:0 INTISAMX(1280,32,64,1280,1,,(not displayed),FAIRCOMS)

The first part of the message is the thread ID. The next part is a date-time stamp. DATE is formatted as yyyymmdd followed by T and then the TIME formatted as hhmmss:

20140312T081659 = March 12, 2014 at 8:16:59 AM.

The next part of the message (SRC:LINE:FUNCTION) indicates the source module, line number, and function returning the error, which may be required by FairCom Support:

  • SRC: Columns 16-20 acronym for source module where the error is logged (usually add ctcb in front to get the actual source module name)
  • LINE: Columns 22-25 line number where the error has been logged (usually just after it is generated)
  • FUNCTION: Columns 27-36 function name where the error has been logged

For example:

api:4397:ctl_regins

Columns 38-42 indicate the event type: ERROR, WARNG, INFO, PROFL, DEBUG.

Following the ERROR event type, you will see three numbers delimited by colons (":"). These numbers indicate the following in the order listed:

For example, ERROR 19:133:0 indicates COBOL error 19 (CTE_INTERFACE), FairCom DB error 133 (ASKY_ERR), and sysiocod 0.

The final part of the message is internal information (the failing function and the function arguments), for example:

INTISAMX(1280,32,64,1280,1,a)

Below are examples of other event types:


20140725T165133 api:0436:ctl_init INFO configuration file: ctree.conf

20140725T165133 api:0437:ctl_init INFO client version:10.5.0.28751-140717 id:34

20140725T165133 api:4706:ctl_setins INFO server version:10.5.0.28751-140717 id:34


20140725T165908 core:0611:cts_make DEBUG FILE created: custmast

20140725T165908 api:5492:ctl_conffi DEBUG FILE "custmast" matches <file> #0

20140725T165908 fsi:0576:ct_make2 PROFL 079310 counts on file:custmast


20140725T170057 api:1926:ctl_open2 WARNG transaction configuration mismatch: <transaction>no</transaction> but file is ctPREIMG

In This Section

FairCom RTG Error Codes

Previous Topic

Next Topic

FairCom RTG Error Codes

Symbolic

Error Code

Description

CTE_NO_ERROR

0

Operation completed successfully

CTE_SYS_ERR

1

System error

CTE_PARAM_ERR

2

Parameter not correct

CTE_TOO_MANY_FILES

3

Too many files open. Check the FILES keyword in the configuration file

CTE_MODE_CLASH

4

File is open read-only

CTE_REC_LOCKED

5

Record locked by another user

CTE_BROKEN

6

File is corrupt. Rebuild it or restore it from a backup

CTE_DUPLICATE

7

Duplicate record not allowed

CTE_NOT_FOUND

8

Record not found

CTE_UNDEF_RECORD

9

Record position not set

CTE_DISK_FULL

10

Write error

CTE_FILE_LOCKED

11

File locked by another user

CTE_MISMATCH

13

File definition mismatch

CTE_NO_MEMORY

14

Out of memory error

CTE_MISSING_FILE

15

File not found

CTE_PERMISSION

16

User does not have appropriate access permission

CTE_NO_SUPPORT

17

Unsupported functionality

CTE_INTERFACE

19

Interface error, check FairCom DB error code (you may need to activate the error logging in ctree.conf and view the error log)

CTE_MODE_CLASH_W

23

File is open write-only

CTE_MODE_CLASH_RW

24

File is not open for read and write

CTE_AT_END

25

End of file

CTE_SYNTAX_ERR

31

Configuration syntax error

CTE_CONFIG_ERR

32

Configuration error

CTE_ENCRYPTED

33

Operation not allowed. File is encrypted

CTE_REDIRINST

34

Unexpected reference to redir instance

CTE_NOT_SQL

35

Server/database is not SQL

CTE_MISSING_TABLE

36

SQL table not found

CTE_INCOMPATIBLE

37

Client/server incompatibility

CTE_FILE_EXISTS

38

File already exists

CTE_NO_TRANSACTION

39

No active transaction

CTE_NOT_MODIFIABLE

40

Key is not modifiable

CTE_NOT_CTREE_FILE

41

Unknown file format

CTE_TRAN_EXIST

42

Transaction already active

CTE_XDD_RULE_ERR

43

XDD rule error

Previous Topic

Next Topic

FairCom RTG SQL Access Errors

The FairCom RTG solution is enabled through a server-side callback module, which implements c-treeDB callback routines. Errors that occur within these routines generate a standard c-treeDB error code that is context sensitive to this implementation. Here is a list of possible return codes from this module, and their meaning in FairCom RTG XDD handling.

Symbolic

Error Code

Description

CTDBRET_CALLBACK_1

4109

Could not find schema in XDD

CTDBRET_CALLBACK_2

4110

Record length does not match extended data definitions

CTDBRET_CALLBACK_3

4111

Invalid or corrupted XDD resource

CTDBRET_CALLBACK_4

4112

Syntax error parsing extended data definitions

CTDBRET_CALLBACK_5

4113

Internal error

CTDBRET_CALLBACK_6

4114

Could not find field in XDD

CTDBRET_CALLBACK_7

4115

Could not find filter in XDD

CTDBRET_CALLBACK_8

4116

Too many schemas in XDD

CTDBRET_CALLBACK_9

4117

Error setting filter condition on schema

CTDBRET_CALLBACK_10

4118

Field value conversion error

CTDBRET_CALLBACK_11

4119

Unsupported CLOB/BLOB definition in XDD

CTDBRET_CALLBACK_12

4120

Index not supported on field type

CTDBRET_CALLBACK_13

4121

Missing or bad dbtype information in XDD

CTDBRET_CALLBACK_14

4122

Invalid filter key settings in XDD

CTDBRET_CALLBACK_15

4123

"Regular" field found after virtual fields in the XDD <schema> (in earlier releases: Invalid field default settings in XML definitions)

CTDBRET_CALLBACK_16

4124

Not used

CTDBRET_CALLBACK_17

4125

Key definition does not match XDD information

CTDBRET_CALLBACK_18

4126

Missing or bad value in XDD

CTDBRET_CALLBACK_19

4127

Internal error (unexpected field type)

CTDBRET_CALLBACK_20

 

Not used

TOCIndex