Framework log

If the compliance check maps are not providing the expected results, the primary problem determination tool is the framework log. This log is an XML-style log that is written to the map directory if certain severe errors occur, or if the trace input option is enabled. This log includes information about each step that was performed by the compliance check map. For large EDI interchanges, the framework log can become large.

To enable the trace option, set input card 9 to one of the following values:
  • T – Trace log is written to file edilog.xml.
  • TU – Trace log is written to a unique file, which is based on the unique id that is specified in input card 2. If no unique id is specified, an id is generated based on the current time stamp. The file name is in the format, edilog_uniqueid.xml
Note: If you specify the CardOutput element in your configuration, then the framework log is written to output card 12 instead of to the edilog.xml or edilog_uniqueid.xml file.

For example, to enable this trace you can specify the command line option:
-IE9 T

Note: Use caution when you use the TU option. The option can cause many log files to be generated, since a new log is created for each unique id.
This log is intended to be read by a person, and in most cases an editor or viewer that can interpret XML data is useful to help read the log. However, in some cases this log might not be strictly well-formed XML - particularly if the EDI data contains XML control characters, such as, <, >, and &. To reduce complexity and processing overhead, these characters are not escaped, so there might be cases where XML processes do not handle these logs.