TTGEN groups the problems it detects from a configuration
file into four categories:
- TTGEN SUMMARY MESSAGE:
TTGEN summary message.
Displayed after TTGEN is run regardless of TTGEN run options.
- DISASTER:
Very serious problem.
TTGEN will stop immediately when it is detected. No output
file or listing will be produced.
- Example:
Problem in opening or reading the source configuration
file.
- ERROR:
Critical problem in system configuration or definition.
TTGEN detects some problems or inconsistencies with the
configuration. By skipping or ignoring some statements,
it manages to continue the compilation. But the resulting memory
file would be invalid. Hence no output file or listing will be produced.
- Example:
Multiple interface cards with the same bus and slot.
- WARNING:
Minor configuration problem
TTGEN detects some non-critical configuration problems with
the configuration file. This may cause unexpected results or unavailable
functions during normal runtime operations. However, the system should
otherwise operate normally without encountering a fatal error. If
only warnings are detected, a ZCOM memory file and listing (if requested)
will be produced. After the memory image file has been created,
you may use it to initialize and startup the ZCOM runtime subsystem
using zmasterd.
- Example:
A long system name is specified, causing some trailing
characters to be truncated or some ports of an ACC card are not
defined.
Any file handling errors that occur while running TTGEN are
reported by HP-UX. For further explanation of any file handling
errors, refer to the Hewlett-Packard HP-UX Reference
Manual, under PERROR(3) and ERRNO(3).
See the "TTGEN Error Messages" chapter in
the ACC Error Guide for lists of errors and
other messages which may be produced by TTGEN. The severity code
indicates whether that problem is a Disaster (value 3 or above),
an Error (value 2), or a Warning (value 1).
When specified, the "%s"(%d) field
in the Disasters, Errors, and Warnings indicate the source file
name and the line number where the problem occurs. Other instances
of %s indicate strings, %d indicate signed integers, and %u indicate
unsigned integers, filled in at TTGEN runtime with an appropriate
value and printed out with those values.
Printable version
