Table of Contents
Advertisement
7
L o g f i l e s
Log files
FrameMaker log files give you information used to identify and correct errors in your
application.
Generating log files
FrameMaker can produce a log file of errors and warnings for each file it processes. If it
runs without encountering errors or other conditions requiring messages, it does not create
a log file. The one exception to this is that the UNIX batch utilities always produce a log file
so that you know what files were processed.
FrameMaker generates messages for conditions such as:
•
Markup syntax errors
•
Read/write rule syntax errors
•
Missing or otherwise unavailable files
•
Missing entities
•
Inconsistencies between read/write rules and the relevant EDD or DTD
Messages in a log file
Messages written to the log file include warnings, errors, and fatal errors.
Warnings are notifications of potential problems; a warning does not necessarily mean
something is wrong with the input. For example, when the software creates an EDD from a
DTD, it issues a warning if it encounters an element rule in a read/write rules document
for a generic identifier that doesn't exist in the DTD. This situation is legal, but the software
warns you in case you have misspelled the generic identifier in the rules document. For all
warnings, the software writes a message and continues processing.
Errors indicate actual problems in the processing. For example, when FrameMaker updates
an existing EDD, it reports an error for a FrameMaker element definition that has no
counterpart in the DTD. For most errors, the software writes a message and continues
processing.
The third category of message indicates fatal errors. These errors cause processing to stop.
For example, if FrameMaker encounters a syntax error in a rules document, it stops
processing.
To aid in debugging your structure application, FrameMaker provides a facility for locating
certain problems. Choose Check Read/Write Rules from the Developer Tools menu.
FrameMaker uses the current application to check the validity of the rules document in that
application. The command can find many potential problems and most fatal errors.
Structure Application Developer's Guide
71
Advertisement
Table of Contents
