openFT writes trace data to files with the following format:
'<openft qualifier>.<inst>.Smddhhmm.Sssccc.I000.FTTF'
(Control process)'<openft qualifier>.<inst>.Smddhhmm.Sssccc.Iiii.FTTF'
(Server process for inbound and asynchronous outbound requests, i= 001,002, ...)'<openft qualifier>.<inst>.Ymddhhmm.Sssccc.Pnnnnnnn.FTTF'
(Process for synchronous outbound requests)
Here, the first two name parts are replaced by OPENFT QUALIFIER and the name of the instance.
mddhhmm.Sssccc specifies the creation time of the trace file. Here, m indicates the month (1 = January, 2 = February, ... A= October, B=November, C = December), dd the day, hhmm the time in hours (hh) and minutes (mm), ssccc the time in seconds (ss) and milliseconds (ccc). nnnnnnn means the process ID of the process for synchronous outbound requests.
Please note that the trace file name may be shortened if the OPENFT QUALIFIER does not consist solely of a "first level qualifier", i.e. it contains a period. For example, ssccc may replaced by sss or may be omitted completely.
Trace files in the event of errors
If a trace file cannot be written without errors due to a memory bottleneck, a DLOG record and a console message are output.
If a record of the trace file cannot be written as a result of an infringement of the maximum record length, the trace file is closed and the subsequent records are written to a new continuation file with the additional suffix.Liii, e.g.:
’<openft qualifier>.<inst>.S8101010.S33222.I001.FTTF’ (first trace file)
’<openft qualifier>.<inst>.S8101010.S33222.I001.L001.FTTF’ (continuation file)