gtpc2mjsC/C++ Language Support User's Guide

GNTAGH Messages

All non-header file output from the GNTAGH program is sent to SYSPRINT (console in CMS or TSO) and is in the following format:

   GHTnnnnn  cccccc   Message text

where:

nnnnn =
A sequence number. Each message number has a unique sequence number associated with it, identifying the phase in which the error or information was generated.

cccccc =
Message class. There are three types of messages sent:

INFO
Information only

WARNING
Possible error condition

FATAL
An error condition from which recovery is not possible. If a FATAL message has been received, the program will exit with a return code equal to the message sequence number, closing all open files where possible.

Message text
Each message class field is followed by text that describes the condition.


00016

Severity: FATAL

Explanation: Unable to open assembly SYSADATA file. This message occurs when the GLOBALS SYSADATA file cannot be opened in read-only mode.


00017

Severity: FATAL

Explanation: Unable to allocate working storage. This message occurs when the GNTAGH program is unable to allocate working storage for its internal processing.


00018

Severity: FATAL

Explanation: Unable to create temporary working file. This message occurs when the GNTAGH program is unable to create a scratch file for its internal processing.


00020

Severity: FATAL

Explanation: Unable to open output file. This message occurs when the c$globz.h header file cannot be opened in write-only mode.


00021

Severity: FATAL

Explanation: Unrecognized COPY statement found before SYNLST. This message is received when another COPY statement precedes the COPY SYNLST statement in the SYSADATA file. This usually indicates that either the GLOBALS program has been altered or that the wrong SYSADATA file is being read.


00022

Severity: FATAL

Explanation: COPY SYNLST statement not found. This message is received when the GNTAGH program cannot locate the COPY SYNLST statement in the SYSADATA file. This usually indicates that either the GLOBALS program has been altered or that the wrong SYSADATA file is being read.


00024

Severity: FATAL

Explanation: Cannot find FLDCNT and/or RCDCNT in SYNLST. This message is received when the SYNLST macro expansion does not contain the assembler GBLA variables FLDCNT and/or RCDCNT, which define the number of synchronizable fields and record entries in the SIGT table. Check to see if SYNLST has been modified, and these variables removed.


00030

Severity: FATAL

Explanation: GLOBZ REGR or GLOBZ REGS statement not located or not in sequence. This message occurs when the SYSADATA file either does not contain the GLOBZ REGR= or GLOBZ REGS= statement, GLOBZ REGR= is not the first GLOBZ macro invoked, or GLOBZ REGS= is not the second GLOBZ macro invoked.


00040

Severity: FATAL

Explanation: Missing global block label. This message is received when one or more global block names, as defined in the "block" array in GNTAGH, have not been located among the SYSADATA SYMBOL records. Check to make sure that:

  1. There are no extraneous global block names defined in GNTAGH.
  2. The proper MACLIBs were used for assembly.


00050

Severity: FATAL

Explanation: Error writing to output file. This message is received when an attempt to write an output line to C$GLOBZ fails.


00098

Severity: WARNING

Explanation: Rejecting -- unable to locate block. This message is received when a global tagname has been encountered whose displacement does not fall into any of the specified global blocks/areas. Check to make sure that GNTAGH code has not been altered in such a way that it cannot handle certain references.


00099

Severity: WARNING

Explanation: Rejecting -- low definition line. This message is received when a global tagname has been encountered whose point of definition was not within the bounds established by the GLOBZ statements. The line number and tagname as received are displayed in the text of the message, and should be checked against the output shown in message 00200. When this message is received, check to make sure that the GNTAGH program has not been altered in such a way that it cannot reconcile certain line numbers.


00200

Severity: INFO

Explanation: This message identifies the assembly source lines where each of the required GLOBZ statements is located. It is needed only for diagnostic purposes and does not describe an error condition.


00300

Severity: INFO

Explanation: C$GLOBZ H complete. This message is received at end-of-job when no errors have been encountered. The text of this message contains a count of the number of tags successfully converted into C #define format.


00301

Severity: WARNING

Explanation: Errors encountered. This message is received when at least one symbol name in global tagname format did not qualify for inclusion in the output header file. This message is sent at end-of-job instead of message 300 when errors have been encountered. Check your GLOBALS listing against the C$GLOBZ file produced by this run to identify the error.


00302

Severity: INFO

Explanation: This message is a reminder that you must verify the keypointability attribute of all tagnames in the c$globz.h header file that are listed as keypointable.