FairCom RTG COBOL Edition User's Guide

Configurable Log Output

The output of the FairCom RTG log includes a file name with the log messages. Warning and error log messages are formatted with the file name appended at the end of the message. The file name is preceded by the instance name, when specified in ctree.conf with the <instance name> attribute, or by the instance number and file number to uniquely identify the file as follows:

instance_number#file_number:file_name.

The file name is logged for START, READ, NEXT, PREVIOUS, WRITE, REWRITE, DELETE, and UNLOCK operations.

In addition, every entry in the log is pre-pended with a thread ID to uniquely identify the process/thread that made the log entry. The thread ID is made of 8 hexadecimal digits followed by a “>” sign.

Example:

00002D40> 20140915T141358 core:3494:cts_rewdel ERROR 5:42:0 record is locked 0#0:arc1.dat

Substitution Specifiers

The following substitution specifiers can be used in the name attribute of the <instance> and its variant elements:

%t to print the thread ID in unsigned decimal format
%p to print the process ID in unsigned decimal format
%i to print the instance number in unsigned decimal format

These specifiers can optionally contain embedded format specifiers with the following prototype:

%[0][width][x|X]specifier

[0] left-pads the number with zeroes (0) instead of spaces when width is specified
[width] minimum number of characters to be printed. If the value to be printed is shorter than this number, the result is padded with blank spaces. The value is not truncated even if the result is larger.
[x] (lower case) number is as unsigned hexadecimal integer
[X] (upper case) number is as unsigned hexadecimal integer

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