FairCom RTG V2 Update Guide

<log><error> types added: <locked>, <missingfile>, and <undefined>

This modification introduces <log><error> configuration keywords to mask three new error types in addition to the existing <atend>, <duplicate>, and <notfound>. This 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. The following new types are now supported:

• <locked> to mask record locked errors
• <missingfile> to mask file not found errors
• <undefined> to mask no current record position errors

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

The complete list of FairCom RTG errors that can be masked now contains the following:

Keyword RTG Error

<atend> 25

<duplicate> 7

<locked> 5

<missingfile> 15

<notfound> 8

<undefined> 9