|
|
|
The following new elements have been added to the <log> <error> support:
Name |
Description |
RTG Error |
Accepted Values |
|---|---|---|---|
<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 |
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 file=mylog.txt>
<error>yes</error>
</log>
The following example enables the logging of end-of-file errors but not of record-not-found errors:
<log file=mylog.txt>
<error>
<atend>yes</atend>
<notfound>no</notfound>
</error>
</log>
Full details on log error attributes are available in the FairCom RTG guide: <error>
