Disasters

Disaster 02: Problem in running C Pre-processor. (Severity 3)

Explanation

TTGEN uses the C-Pre-processor (/opt/langtools/lbin/cpp) to pre-process the TTGEN configuration file.

This error means that TTGEN cannot find cpp, or cpp returns an error (e.g., bad "#" statements, or can't create temp files, etc.)

Action:

Try correcting the problem with cpp (e.g., run cpp on the configuration file without using TTGEN), or using the TTGEN "-n" option to by-pass cpp.

Disaster 03: Can't open file "%s": %s (Severity 3)

Explanation

Can't open TTGEN configuration file or temp file generated from cpp. Problem with the input file or the file system.

Action:

Make sure file and directory are properly set up and access permissions are correct.

Disaster 04: Can't open output "%s": %s (Severity 3)

Explanation

Can't open TTGEN binary file. This may occur, for example, if the binary output file exists without write permission, or if the current directory does not have write permission and thus cannot create the binary output file.

Action:

Make sure file and directory are ok and access permissions are correct. Or specify "-o" option to overwrite existing output file.

Disaster 05: "%s"(%d): Unexpected end of file (Severity 3)

Explanation

Missing "END$" to signify end of TTGEN definitions

Action:

Add "END$" to the end of the configuration file.

Disaster 06: "%s"(%d): Read error: %s (Severity 3)

Explanation

File read error (e.g., data corruption) of configuration file.

Action:

Make sure file and directory are properly set up and access permission is correct.

Disaster 07: "%s"(%d): Comment closing pattern not found (Severity 3)

Explanation

File has incomplete comments (i.e., /* without closing */).

Action:

Check and rectify file for incomplete comments.

Disaster 08: "%s"(%d): Problem in parsing, status = %d (Severity 3)

Explanation

The TTGEN's parsing routine detects a strange internal error.

Action:

None. Inform HP support center.

Disaster 09: "%s"(%d): Write error: %s (Severity 3)

Explanation

Error in writing to output memory file (e.g., data corruption, or file system problems).

Action:

Rectify problem with the output file or file system.

Disaster 10: "%s"(%d): Must begin with "%s" (Severity 3)

Explanation

TTGEN configuration file must begin with the (case-insensitive) word, "TTGEN" (#include, #define, and C-style comments may precede this).

Action:

Check start of file for no nulls, lower-case ttgen or other violations.

Disaster 11: "%s"(%d): "%s" section expected (Severity 3)

Explanation

Configuration or other section expected, as indicated. First section after "TTGEN" control line must be "CONFIGURATION".

Action:

Add or re-arrange the CONFIGURATION section immediately after the "TTGEN" line.

Disaster 12: "%s"(%d): "%s" section in wrong sequence (Severity 3)

Explanation

Error in configuration file section sequence. The mentioned section should not be in here. END$ expected.

Action:

Remove or re-arrange the misplaced section.

Disaster 13: "%s"(%d): Can't allocate memory of %d bytes (Severity 3)

Explanation

TTGEN allocates virtual dynamic memory (through malloc) during compilation. Depending on the size of the defined network, the amount of required memory could range from 1 to 30 Mbytes. This error means the system rejects the "malloc" request (e.g., not enough main memory and swap space, or memory limit reached).

Action:

Discuss this problem with the system administrator (for possible operating system configuration problems) or define a smaller network.

Disaster 14: "%s"(%d): Can't get ZCOM device: %s (Severity 3)

Explanation

Can't get device table. (ZCOM device file is /opt/acc/cfg/zcomdevice) Problem in accessing the ZCOMDEVICE definition file. This file is used to interpret the device names used in "Terminal-Definition".

Action:

Make sure the device file (/opt/acc/cfg/zcomdevice) is accessible, or is generated from its source file (/opt/acc/cfg/zcomdevice.txt) using ZDGEN.

Disaster 15: "%s"(%d): Too many errors, compilation stopped (Severity 3)

Explanation

More than 99 errors encountered. When TTGEN detects too many errors in the configuration file, it gives up compilation.

Action:

Correct the TTGEN compilation errors and try again.