0

NO_ERROR

Successful operation.

2

KDUP_ERR

Key value already exists in index.

You are trying to add a record to a table that has a unique index and matches an existing record.

3

KMAT_ERR

Could not delete target key value since recbyt does not match associated data record position in index.

You can get this trying to delete a record not in the database.

4

KDEL_ERR

Could not find target key value in index. No deletion performed. May indicate improper use of buffers during ReWriteRecord().

Consider rebuilding the database.

5

KBLD_ERR

Cannot call DeleteKeyBlind() with an index that supports duplicate keys.

6

BJMP_ERR

ctree() function jump table error.

7

TUSR_ERR

Terminate user.

-8

FCNF_COD

This is a sysiocod value when FNOP_ERR (error 12) was caused by conflicting open requests (Server).

ctdbAlterTable() can return this if you are doing a Hot Alter Table and the server can't get an exclusive lock on the file.

-9

FDEV_COD

This is a sysiocod value when FNOP_ERR (error 12), DCRAT_ERR (error 17), or KCRAT_ERR (error 16) were caused by device access error

10

SPAC_ERR

InitCTree() parameters require too much space.

11

SPRM_ERR

Bad parameter(s): either bufs < 3, idxs <0, sect <1, or dats < 0.

12

FNOP_ERR

Could not open file. Either file does not exist, filnam points to incorrect file name, or file is locked by another process. Check sysiocod for the system-level error. For ISAM functions, check isam_fil for the specific file number.

For a file that does not exist, the file open function returns FNOP_ERR with system error code (sysiocod) ERROR_FILE_NOT_FOUND on Windows and ENOENT on Unix. Applications should always check sysiocod for full context.

For the client/server model only, if a file open returns FNOP_ERR, check sysiocod (which is the runtime errno value). If sysiocod = FCNF_COD, (-8), the file exists but there is a file mode conflict preventing the file from being opened. For example, requesting an ctEXCLUSIVE open when the file is already open ctSHARED.

The failure to open the file with sysiocod 32 could happen due to third-party backup software having the file open even if it does not lock regions of the file.

Troubleshooting:

Was the server file opened by another client in a non-shared mode?

Was the file opened by another client in exclusive mode?

13

FUNK_ERR

OpenIFile() cannot determine type of file. c-tree files < V6 must be rebuilt before they can be used. There is a file compatibility between c-tree V4 and V6 (there was no c-tree V5). c-tree V6 was released in 1992.

The Replication Agent will throw this error if you are trying to replicate tables that are incompatible versions. Best practice is to match the Replication Agent with the FairCom DB versions in use.

14

FCRP_ERR

File appears corrupt at open. This occurs if a file is updated and the disk protocol is set at NOTFORCE and CloseIFile() is not executed.

Files have been updated but not properly closed; they were not processed by automatic recovery so they are in an unknown (inconsistent) state.

If your transaction logs are corrupted, preventing automatic recovery from occurring, you can either:

• Restore from a backup and reapply changes if available (e.g., from application log or forward roll of good transaction logs you have saved).

  or

• Rebuild the files, which will clear the error 14 but will still leave the files in a possibly inconsistent state. In this situation the files will not be guaranteed to be consistent as of any point in time; they can contain a mixture of old/new data, and the data files may not match the index files, due to caching.

15

FCMP_ERR

Data file has been compacted, but not rebuilt. Rebuild data file, but do not force rebuild.

16

KCRAT_ERR

Could not create index file. Either no space is available on disk or filnam points to improper name.

17

DCRAT_ERR

Could not create data file. Either no space is available on disk or filnam points to improper name.

FairCom DB was unable to create a new database file. Another file with the same name could already be in the folder.

If you are working with c-treeDB, make sure you have created the necessary folders on the server to match the path you are using. The server won't create folders for you.

18

KOPN_ERR

Tried to create existing index file.

19

DOPN_ERR

Tried to create existing data file.

20

KMIN_ERR

Key length too large for node size. There must be room for at least 3 key values per node. The node size is given by sect * 128 where sect is 3rd parameter.

21

DREC_ERR

If you get this error creating a file, check that the record length is 5 or larger for standard files and 9 or larger for hugefile support.

If you get this error from an index rebuild, check that IFIL->dreclen is set the same as reclen in the file header. These two must match.

22

FNUM_ERR

filno out of range: 0 <= filno < fils, where fils is 2nd parameter. This error may occur if FairCom DB has not been initialized.

Either your InitISAM or the Session you opened has too low of a maximum files limit. There are probably many log files in your database because you crashed with a transaction open, and the total files exceeded the limit. Figure out which limit you hit and raise it to a larger number.

A Replication Agent can get this error as a known bug that has been fixed.

23

KMEM_ERR

Illegal index member number.

24

FCLS_ERR

Could not close file. Usually indicates that memory is clobbered.

25

KLNK_ERR

Bad link in deleted node list. Rebuild file.

26

FACS_ERR

File number (datno, keyno, or filno) is not in use.

You have attempted to interact with a file number that does not correspond with an open file. Your file number may be wrong or the file may have been closed by another connection.

27

LBOF_ERR

Data record position before 1st actual data record

28

ZDRN_ERR

AddKey() called with recbyt = 0.

29

ZREC_ERR

Data file routine called with recbyt = 0.

30

LEOF_ERR

recbyt exceeds logical end of file. If recbyt is correct, then data file header record may be incorrect. If so, rebuild data file.

You can get this if you are trying to modify a record low-level using an offset that is past the last FairCom DB record in the file even though you are still within the physical file length. You have to add the records before you access them!

31

DELFLG_ERR

Next record in delete chain of a fixed-length data file does not have 1st byte set to 0xff. Data file header record may be corrupt; if so, rebuild data file. Or C255 constant is incorrect: see ctcmpl.h.

32

DDRN_ERR

Attempt to delete data record twice in a row.

33

DNUL_ERR

recptr is NULL.

34

PRDS_ERR

Could not find correct predecessor node. Should not show up in a single user system. Indicates that an index insertion was interrupted before completion. Rebuild index.

35

SEEK_ERR

Seek error: check sysiocod error.

lseek() failed in function ctio() (ctclib.c). Possible causes are: out of disk space, corrupted record position in file, or corrupted file descriptor.

Something is wrong with the local drive, such as permissions, disk full, or a corrupt drive.

36

READ_ERR

Read error: check sysiocod error.

Read failed in function ctio() (ctclib.c). Possible cause: corrupted data record position in file.

Something is wrong with the local drive, such as permissions, disk full, or a corrupt drive.

A bug in V11.5 (corrected in V11.6) would cause ctrdmp to fail undoing transactions with error 36.

37

WRITE_ERR

Write failed in function ctio(). See 35 above.

Write error: check sysiocod error.

Something is wrong with the local drive, such as permissions, disk full, or a corrupt drive.

Check disk space on server. Chances are the server is low on disk space.

38

VRTO_ERR

Could not convert a virtually opened file to an actually opened file. This might occur if your application uses up some file descriptors after a virtual file has been automatically closed. You can protect against this by lowering the MAXVFIL parameter in ctoptn.h.

39

FULL_ERR

No more records available.

The 4-byte data record position (or node position) address space has been exhausted.

You have filled up a non-large file table. You have to convert it to a large file to add more records.

40

KSIZ_ERR

Index node size too large.

The index node size was larger when the index was created. For client/server applications, check your PAGE_SIZE setting in ctsrvr.cfg. For stand-alone applications, check your sect setting (recall that PAGE_SIZE = sect * 128, where sect is the third InitCTree() parameter).

At least one of the indexes has an index node size larger than your FairCom DB connection parameters currently are. If you need to do this you will need to rebuild the indexes with a smaller node size.

41

UDLK_ERR

Could not unlock data record. If dummy lock file is in use, be sure it has a file mode of 3.

42

DLOK_ERR

Could not obtain data record lock.

Locked record or table.

Replication: The record on the target is already locked by another client. Check to see if a "rogue" replication is accidentally running in background. See Troubleshooting Replication in the replication guide.

43

FVER_ERR

File Version Error. Version incompatibility.

Current configuration parameters are inconsistent with the configuration parameters at the time of file creation.

You can get this error trying to rebuild or compact a database with a Full Text Index. The bug was fixed in 11.6.

You can also get this error by calling functions that require structures with versions, such as GetFileRegions(). These versions must match the versions written into the file in question. If they don't, you might get this error back from the function call.

44

OSRL_ERR

Data file serial number overflow.

45

KLEN_ERR

Index key length exceeds MAXLEN parameter. Change MAXLEN in ctoptn.h and recompile FairCom DB.

46

FUSE_ERR

File number is already in use.

If possible, increase the FILES setting in the server (or the fils parameter of INITISAM() for standalone). In releases after V10.3, the default for MAX_FILES_PER_USER has been increased from 2048 to 32767 to avoid file opens failing due to the lower limit.

You may have hit your FILES limit. Edit ctsrvr.cfg to have a bigger number.

If you get this error from PermIIndex() (PRMIIDX()), you may have opened a file after the one you are trying to modify. This function requires a file number sequentially after the host index file number for each item you are adding.

47

FINT_ERR

FairCom DB has not been initialized.

You have to call InitISAM() or one of it's variants before using the database.

48

FMOD_ERR

Operation incompatible with type of file.

A function has been called for the wrong type of file: e.g., a variable-length function is called for a fixed-length data file.

You can get this error from ctdbLastRecord() if you call it on a file without an index available. ctdbFirstRecord(), ctdbNextRecord() can both operate without an index. ctdbLastRecord() needs an index.

49

FSAV_ERR

Could not write file directory updates to disk during file extension.

50

LNOD_ERR

Could not lock index file node.

51

UNOD_ERR

Could not unlock index file node. If a dummy lock file is in use, be sure it has a file mode of 3.

52

KTYP_ERR

Variable-length and/or floating point keys disabled in ctoptn.h.

Invalid key type.

53

FTYP_ERR

The file’s file mode is inconsistent with the compile time options selected in ctoptn.h.

54

REDF_ERR

Attempt to write a read only file.

55

DLTF_ERR

File deletion failed.

56

DLTP_ERR

File must be opened exclusive for delete.

57

DADV_ERR

Proper lock is not held (ctCHECKLOCK/READ).

In normal ISAM situations, this error means you tried to save a record without having locked it.

In c-treeRTG (the COBOL database driver), the RTG system opens the files with ctCHECKLOCK or'ed in to the file mode, which means you have to lock records before updating them and also you have to get a lock to write a record. If you don't, you will get an error 57 back from the save or from the add record. Although c-treeRTG manages that locking behavior internally, a bug could sometimes cause record saves to fail and return error 57.

58

KLOD_ERR

LoadKey() called with incorrect key number. You cannot continue.

59

KLOR_ERR

LoadKey() called with key out of order. You may skip this key and continue.

60

KFRC_ERR

Percent out of range.

61

CTNL_ERR

NULL file control block detected during I/O.

62

LERR_ERR

File must be opened exclusively.

63

RSER_ERR

Start file/log file serial number error.

64

RLEN_ERR

Checkpoint past end of log file (a checkpoint file is pointing to a region beyond the end of the transaction log).

A serious hardware failure can cause the final entries of the transaction log to not be written to disk, causing this error.

Try restarting the server with the following keyword in place:
CHECKPOINT_PREVIOUS YES

Log files don't match database. Check to see if some, but not all, log files were thrown out.

65

RMEM_ERR

Not enough memory during transaction processing.

App needs more memory to perform an auto recover.

66

RCHK_ERR

Log file entry failed to find checkpoint.

Prior to V11.6.1, checkpoints that were larger than 16MB were considered bad and this error was thrown. A very large forward roll could create a checkpoint with a very large redo list causing it to be too large. One customer had a 300MB checkpoint. V11.6.1 raised the size check to 2GB.

67

RENF_ERR

Could not rename file.

In V9 and earlier, there were issues rebuilding on a drive other than the startup drive. You can get this error trying to rebuild on a drive other than the system drive. Copy to the system drive and try again.

68

LALC_ERR

Could not allocate memory for control list.

69

BNOD_ERR

Node does not belong to index.

This could indicate index corruption caused by things like a server and a single-user library modifying the same tables simultaneously.

70

TEXS_ERR

Transaction already pending.

This error can occur when 2 people are looking at the same info.

A call to PUTHDR() with a mode of ctTIMEIDhdr or ctUNIQIDhdr for a transaction-controlled file that has been updated (LOG_FILE_ID_CHANGE YES) in the current transaction fails with this error.

71

TNON_ERR

No active transaction.

You are trying to modify a record in a transaction-controlled table without having a transaction open.

72

TSHD_ERR

No space for shadow buffer.

73

TLOG_ERR

ctLOGFIL encountered during shadow only.

This error is trying to catch writing to a transaction log when the transaction mode does not include writing to the log. It was triggered on PREIMG files when an index buffer was re-used that had previously been used with a TRNLOG file. This was a false positive and was fixed in builds around V11.5.

74

TRAC_ERR

Recovery: two active transactions for user.

A V11.5 bug could cause this error to be logged talking about a failure to read next change from transaction log. Fixed in V11.6.

75

TROW_ERR

Recovery: bad transaction owner.

A V11.5 bug could cause this error to be logged talking about a failure to read next change from transaction log. Fixed in V11.6.

76

TBAD_ERR

Recovery: bad transaction type.

A V11.5 bug could cause this error to be logged talking about a failure to read next change from transaction log. Fixed in 11.6.

77

TRNM_ERR

Recovery: file name too long.

78

TABN_ERR

Transaction abandoned: Too many log extents or dynamic dump wait exhausted.

Transaction is too large. Do it in smaller parts.

79

FLOG_ERR

Could not log file opn/cre/cls/del.

80

BKEY_ERR

NULL target or bad keyno.

81

ATRN_ERR

Transaction allocation error.

82

UALC_ERR

User allocation error.

Parameters passed to a function required memory allocation that failed. The parameters may be wrong. It is also possible the machine is out of memory.

83

IALC_ERR

ISAM allocation error.

84

MUSR_ERR

Maximum users exceeded.

85

LUPD_ERR

Attempt to reduce write lock to read lock after update.

86

DEAD_ERR

Dead lock detected.

87

QIET_ERR

System is busy: files in use.

88

LMEM_ERR

Linked list memory allocation error.

89

TMEM_ERR

Memory allocation during transaction processing.

90

NQUE_ERR

Could not create queue.

91

QWRT_ERR

Queue write error.

92

QMRT_ERR

Queue memory error during write.

93

QRED_ERR

Queue read error.

94

PNDG_ERR

Pending error: Cannot save or commit transaction.

This error can be returned from CommitTransaction() if you did a save in a transaction, the save returned an error like Keydup, you ignored the error, and then tried to commit the transaction. You can also get this from SetSavePoint().

If you have a 2-phase commit source/target replicated server, you can get this if you are trying to connect to a target server as if it were the master. Check to see if you reversed the target and master IP numbers.

95

STSK_ERR

Could not start task.

96

LOPN_ERR

Start-file/log open error.

FairCom DB is having trouble opening a needed log file probably for auto recover. The log could be missing or it could be locked by another process. Two processes trying to open the same single-user database exclusive can get this.

If replication is getting error 96, it may have gotten so far behind that the max logs was hit and the needed log was deleted. Re-sync database.

If the Deferred Indexer is logging this error, probably the logs were cleared out but the DFRKSTATEDT.FCS and DFRKSTATEIX.FCS were not deleted and it's still trying to process an old log that is gone.

97

SUSR_ERR

Bad user handle.

98

BTMD_ERR

Bad transaction mode.

99

TTYP_ERR

Transaction type / mode conflict.

Normal ISAM systems: This is what you get if you try to save a new record, or delete an existing record outside of a transaction.

100

ICUR_ERR

No current ISAM record for data file isam_fil.

In DirectSQL, this is what you get when the current cursor is out of records. Similar to error 101.

101

INOT_ERR

Could not satisfy ISAM search request for index isam_fil.

Key does not match any record.

The following items are the most probable causes of the INOT_ERR (101):

• Passing GetRecord() a duplicate allowed index number (keyno). GetRecord() does not support duplicate allowed indexes.
• Improper target padding. Review “Key Segment Modes” in the FairCom DB documentation.
• Not calling TransformKey() on target. Refer to “TransformKey” in the FairCom DB documentation.
• Passing ctDeleteSequence() a sequence name that does not exist
• Improper segment mode. Review “Key Segment Modes” in the FairCom DB documentation.

102

INOD_ERR

ISAM parameter file does not exist. Be sure that filnam parameter points to correct name. isam_fil value is undefined.

103

IGIN_ERR

Could not read ISAM parameter file Initialization record. isam_fil is undefined. Be sure that parameter file is not empty, and that the correct short integer input conversion character has been specified in ctoptn.h.

104

IFIL_ERR

Number of files opened exceeds fils parameter at initialization. Increase fils. Optionally change ctMAXFIL in ctoptn.h. isam_fil is undefined.

105

IUND_ERR

Could not undo a rejected ISAM update. Data file must be rebuilt. (During the rebuild, look for records with rejected duplicate key values.)

106

IDRI_ERR

Could not read ISAM parameter file Data File Description record for isam_fil. Be sure parameter file is consistent with RTREE setting in ctoptn.h.

107

IDRK_ERR

Too many indexes for data file number isam_fil in ISAM parameter file. Change MAX_DAT_KEY in ctoptn.h.

108

IMKY_ERR

keyno for index file member out of sequence. keyno must equal host index file keyno plus member number.

109

IKRS_ERR

Too many key segments defined in ISAM parameter file for index number isam_fil. Change MAX_KEY_SEG in ctoptn.h. Be sure that parameter file is consistent with RTREE setting in ctoptn.h.

110

ISRC_ERR

Could not read ISAM parameter file Key Segment Description record for index number isam_fil.

111

IKRI_ERR

Could not read ISAM parameter file Index File Description record. isam_fil indicates the relative index number for an unspecified data file.

112

IPND_ERR

(ctENABLE) found pending locks.

113

INOL_ERR

No space left in the FairCom DB internal lock list.

114

IRED_ERR

1st byte of fixed-length data record found by ISAM routine equals delete flag.

This can happen if you are trying to delete a record in a fixed-length record that is already deleted, or if a fixed-length record has binary data in the first byte that mimics the deleted mark.

115

ISLN_ERR

Sum of key segment lengths does not match key length for index number isam_fil.

116

IMOD_ERR

Bad mode parameter.

117

IMRI_ERR

Could not read ISAM parameter file Index Member record.

118

SKEY_ERR

NextInSet or PreviousInSet called with a keyno that does not match keyno in last call to FirstInSet.

119

SKTY_ERR

FirstInSet called for numeric key type.

120

RRLN_ERR

Not enough dynamic memory for record buffer.

121

KBUF_ERR

Tried to update data with ctISAMKBUFhdr on.

122

RMOD_ERR

Attempt to change between fixed and variable-length records during rebuild. Once a data file is created, its record length characteristic cannot be changed.

123

RVHD_ERR

A variable-length data record is not preceded by a valid record mark. The file is apparently corrupted.

The fixed-length portion length you gave to FairCom DB is wrong. Check the IFIL Minimum Record Length field. It needs to be the offset of the beginning of the vFields field.

This can also be corruption in the data file.

Basically we were traversing your file and there was other data where a record should have started. This is most often a section of the file that is corrupted.

A rebuild will often fix this, however the intelligence that determines how much data to remove from the data file may cause large numbers of good records to be eliminated.

Earlier versions of the rebuild would do this automatically. Newer versions ask.

Always rebuild on a copy and compare the record count before and after.

124

INIX_ERR

Number of indexes in index file does not match IFIL structure in call to OpenIFile() or the parameter file specified.

125

IINT_ERR

FairCom DB is already initialized via a previous call.

126

ABDR_ERR

Bad directory path get.

127

ARQS_ERR

Could not send request.

Something happened to the server or the network that prevented the client from receiving info from the server.

See “Client/Server ctntio Communication Errors (Formerly VDP Errors)” in the FairCom DB documentation for more information.

128

ARSP_ERR

Could not receive answer.

Something happened to the server or the network that prevented the client from receiving info from the server.

See “Client/Server ctntio Communication Errors (Formerly VDP Errors)” for more information.

129

NINT_ERR

FairCom DB not initialized.

130

AFNM_ERR

NULL file name pointer. Empty file name on call to open or create.

131

AFLN_ERR

File name length exceeds message size.

132

ASPC_ERR

No room for application message buffer.

133

ASKY_ERR

Could not identify Server.

Client was not able to locate the server. Check to see that the server is working OK and the client connection IP is correct.

134

ASID_ERR

Could not get Servers message ID.

135

AAID_ERR

Could not allocate application ID.

136

AMST_ERR

Could not get application message status.

137

AMQZ_ERR

Could not set application message size.

138

AMRD_ERR

Could not get rid of application message.

139

ABNM_ERR

Badly formed file name.

140

VMAX_ERR

Variable record length exceeds 65,529 bytes.

141

AMSG_ERR

Required message size exceeds maximum.

142

SMXL_ERR

Application MAXLEN > Server’s MAXLEN ctoptn.h.

143

SHND_ERR

Communications handler not installed.

144

QMEM_ERR

Application could not ID output queue.

145

ALOG_ERR

No message space. Was login ok?

146

VDLK_ERR

Could not update available space information in variable-length data file.

Try rebuilding indexes.

147

VDLFLG_ERR

Space to be reused is not marked deleted.

Record pointed to by available space information is not marked deleted in variable-length data file.

FairCom DB reports this as a diagnostic code; notify FairCom and ignore.

148

VLEN_ERR

Attempt to write a variable-length record into a file position which is too small for the record.

149

VRLN_ERR

Variable-length passed to AddVRecord() is less than minimum record length established at file creation.

Most often caused by a DODA that is not correct.

150

SHUT_ERR

Server is shutting down.

151

STRN_ERR

Could not shut down; transactions pending.

152

LEXT_ERR

Could not extend logfile.

153

VBSZ_ERR

Buffer in call to ReReadVRecord() is too small for the variable-length record.

154

VRCL_ERR

Attempt to read (R) a zero length record from a variable-length data file.

155

SYST_ERR

Native system failure.

156

NTIM_ERR

Timeout error.

158

VFLG_ERR

ReReadVRecord() record not marked active.

159

VPNT_ERR

Zero data record position in variable-length function.

160

ITIM_ERR

Multi-user interference: key value changed between index search and subsequent data record read.

Error 160 basically means the index node for a record didn't match the record. It can happen if you look up a record and another user deletes that record then you try to do something with it. Or if you look up a record, another user edits the record making it larger causing it to be moved to a different spot on the disk, then you try to do something with it. Your cached index entry no longer points to the record. In both of these cases, catching the error and re-reading the record will resolve the issue as you will get the corrected offset.

You can also get this error if you have an out-of-date index that contains entries for records that no longer exist in the database. Rebuild in this case will clear the bad index entries.

161

SINA_ERR

User appears inactive.

162

SGON_ERR

Server has gone away.

This can mean you were connected and the connection went away, but it can also be returned instead of a 133, i.e., trying to connect to a server that isn't there can return a 162.

163

SFRE_ERR

No more room in Server lock table - free up memory.

164

SFIL_ERR

File number out of range.

165

SNFB_ERR

No FairCom DB file control block. Try increasing the FILES limit in ctsrvr.cfg and restarting FairCom Server. (In standalone mode, limit is set by InitISAM fils parameter.)

Up the FILES in the config file on the server.

166

SNMC_ERR

No more FairCom DB file control blocks in Server. Try increasing the FILES limit in ctsrvr.cfg and restarting FairCom Server. (In standalone mode, limit is set by InitISAM fils parameter.)

Up the number of files in the server config file.

167

SRQS_ERR

Could not read request.

168

SRSP_ERR

Could not send answer.

169

TCRE_ERR

Create file already opened (in recovery).

170

SFUN_ERR

Bad function number at Server.

171

SMSG_ERR

Application message size exceeds Server size.

172

SSPC_ERR

Could not allocate Server message buffer.

173

SSKY_ERR

Could not identify Server.

174

SSID_ERR

Could not get Server message ID.

175

SAMS_ERR

Server could not allocate user message area

176

SMST_ERR

Could not get Server message status

177

SMQZ_ERR

Could not set message Server message size

178

SINM_ERR

Unexpected file number assigned to [si] in recovery.

179

SOUT_ERR

Server is at full user capacity.

FairCom DB server is reporting you went over the user limit. Reboot and inform FairCom: It's not supposed to ever do this.

180

IKRU_ERR

Could not read r-tree symbolic index name.

181

IKMU_ERR

Could not get dynamic memory for r-tree symbolic index name.

182

IKSR_ERR

Cannot accommodate temporary r-tree files. Increase ctMAXFIL.

183

IDRU_ERR

Could not read r-tree data field symbolic names.

184

ISDP_ERR

Multiple set buffer space already allocated.

185

ISAL_ERR

Not enough dynamic memory for multiple sets.

186

ISNM_ERR

Set number out of range in .

187

IRBF_ERR

Null buffer pointer in r-tree.

188

ITBF_ERR

Null target buffer pointer in r-tree.

189

IJSK_ERR

JOINS_TO skip condition in r-tree.

190

IJER_ERR

JOINS_TO error condition in r-tree.

191

IJNL_ERR

JOINS_TO null fill condition in r-tree.

192

IDSK_ERR

IS_DETAIL_FOR skip condition in r-tree.

193

IDER_ERR

IS_DETAIL_FOR error condition in r-tree.

194

IDNL_ERR

IS_DETAIL_FOR null fill condition in r-tree.

195

IDMU_ERR

Could not get dynamic memory for r-tree data field symbolic names.

196

ITML_ERR

Exceeded RETRY_LIMIT on error 160 in r-tree.

197

IMEM_ERR

Could not get memory for IFIL block.

198

BIFL_ERR

Improper IFIL block.

199

NSCH_ERR

Key segment refers to schema but no schema is defined.