You specify the properties for TLOG files using the following environment variables:
The actual TLOG file or files used to recover an IMS database depends on whether or not Forward recovery is enabled or disabled.
With the exception of the IMSDB.TLOG file created and used when Forward recovery is disabled, Enterprise Server generates and renames TLOG files using this naming convention:
serverName-YYMMDDhhmmssmm.TLOG
Where serverName is the name of the server on which the database is stored, and YYMMDDhhmmssmm represents two digits for each: year, month, day, hour, minute, second, and millisecond.
Depending on the size of the database and the volume of transactions, recovery log files can become quite large. To better manage large-volume logs, Enterprise Server occasionally creates extension logs. The name of an extension log file is the same as the originating log file, plus an appended extension number such as 001, 002, etc.
During a recovery process, Enterprise Server uses log file time stamps to determine which log file or files are required for the restoration, and excludes out-of-date log files from the recovery. This minimizes the time required to complete the recovery.
You can view the contents of a TLOG file using the cobfhtlog utility as follows:
cobfhtlog filenameWhere filename is the name of a TLOG file.
The contents of the file are written to the screen. The following example represents a snippet of the contents of a TLOG file:
rollfwd data data len: 00019 data : 100000006 00000006 ….. commit prep session: 0000000002 sequence no: 00000000000000000006 date time: 17081415252517 ….. commit begun session: 0000000002 sequence no: 00000000000000000007 date time: 17081415252523 ….. commit comp session: 0000000002 sequence no: 00000000000000000008 date time: 17081415252523