BTRV Edition User's Guide

<error>

The error log option instructs the FairCom RTG to log file error events.

Accepted Values

Value	Effect	Synonyms
yes	This value turns on the error logging.	y, true, on, 1
no	This value turns off the error logging.	n, false, off, 0

The error log option also accepts the following Boolean (yes or no) sub-options to include or exclude certain type of errors from the log file.

Children elements

Name	Description	RTG Error	Accepted Values
<atend>	This value turns on logging of end-of-file errors. This option is disabled by default.	25	yes and no
<notfound>	This value turns on logging of record-not-found errors. This option is disabled by default.	8	yes and no
<duplicate>	This value turns on logging of duplicate-key errors. This option is disabled by default.	7	yes and no
<locked>	This value masks record-locked errors. *See Note below.	5	yes and no
<missingfile>	This value masks file-not-found errors.*See Note below.	15	yes and no
<undefined>	This value masks no-current-record-position errors.*See Note below.	9	yes and no

By default, the entries associated with <atend>, <notfound>, and <duplicate> are not logged unless they are explicitly enabled. <locked>, <missingfile> and <undefined> remain logged by default.

* Note:

These masks can be useful if you encounter a large number of error 9:0 (undefined record position) in your FairCom RTG logs and need a way to mask them.

In the FairCom RTG log file, these errors can be identified by the first of the three colon-separated error values:

RTG Error : Underlying c-tree API Error : Operating System Error

For example, a record locked error will display the following (notice 42 is the c-tree error for record locked):

ERROR 5:42:0

Examples

The following example enables the logging of errors only:

</log>

The following example enables the logging of end-of-file errors but not of record-not-found errors:

<error>

</error>

</log>