The transaction logs for non-ODBC users are stored in fixed-length files in the directory where the executable is installed, in a file named translog.out for outbound processing and in a file named translog.in for inbound processing. Each time ECRTP is executed, the program appends new information to the transaction log files. Since these files can become very large, the user must institute a procedure to control their size by periodically deleting information.
Non-ODBC users have three choices for the creation of the transaction log:
No Log
Non-Expanded Text Transaction Log
Expanded Text Transaction Log
If the transaction log is written in the expanded format (-xl switch), additional fields are included and the sizes of three fields are expanded to include eight-digit dates, six-digit times, and the complete text of all error messages. The non-expanded format has fewer fields and includes only six-digit dates, four-digit times, and truncated versions of the error messages. See “Expanded format” for the layout of the non-ODBC expanded text transaction log.)
The trace files for non-ODBC users are stored in fixed-length files in the map/generated files directory, in outgoing.err for outbound processing and incoming.err for inbound processing.