The first column of the standard report has the heading "TY". Its value is the record type, taken from the following list:
ST Start Transaction CB Commit Begin CE Commit End RO Rollback Transaction DE Delete (record) RW Rewrite WR Write OP Open (Opens an existing file ) MA Make (Creates or Recreates a file during an OPEN operation) CL Close CP Copy RN Rename RM Remove (file)
The other columns are as follows:
PID ID of process which wrote the record
Term Name of terminal used by the runtime
User User name of owner of the runtime
Client Host name of machine running the runtime, the client machine when
using AcuServer
Date/Time Date and Time the event occurred
File ID Unique identifier of the file
File Name Name of file being opened, created, recreated, deleted, renamed,
or copied
If the "-l" option is used:
Location Byte offset of the record in the log file Length Length of the log record
-v Option
If the "-v" option is used, record images are displayed in a format similar to the following:
Record Image:
0015 0001 2ce2 dffc 0000 55dd0000 646f ...,.....U...do 7669 6400 6163 7563 6f62 6f6c 00 vid.acucobol.
-i Option
logutil may be used to monitor transaction log activity. If you run it with only the "-i" option, or with no options, it sends a summary report to standard output. This report contains statistics, version information, and warning messages. One or both of the two warning messages below may appear, as shown in the following report:
logutil corruptlog
Log File : corruptlog WARNING: INCOMPLETE TRANSACTION AT END. WARNING: 2 ACTIVE TRANSACTIONS. Total Size : 2366 bytes Number of Records : 79 Mean Record Size : 29 bytes Number of Transactions : 17 Mean Transaction Size : 139 bytes Record Version(s) : 1
The warning "COMMIT BEGIN WITHOUT MATCHING COMMIT END" means that the last record in the log file is not a type CE (Commit End) record. This means that, during a commit:
the log file was being updated at the time logutil was run
or a process was killed with an uncatchable signal
or a system failure occurred
In the case of a killed process with an uncatchable signal, or a system failure, the next START TRANSACTION using the corrupted log file will return TRANSACTION-STATUS 12.
The warning "2 START TRANSACTIONS WITHOUT MATCHING ROLLBACKS OR COMMITS" means that there are two transactions that have yet to be committed or rolled back. This could indicate a problem if there are no runtime processes currently using the log file.