Product Documentation

FairCom RTG V2 Update Guide

Previous Topic

Next Topic

Improved log output with file names on ERROR entries

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

TOCIndex