Rational Developer for System z
Enterprise PL/I for z/OS, Version 4.2, Programming Guide

GONUMBER

The GONUMBER option specifies that the compiler produces additional information that allows line numbers from the source program to be included in runtime messages.

Read syntax diagramSkip visual syntax diagram   .-NOGONUMBER---------------------.
   |              .-NOSEPARATE-.    |
>>-+-GONUMBER--(--+-SEPARATE---+--)-+--------------------------><
 

ABBREVIATIONS: GN, NGN

SEPARATE
Places the generated statement number table in the separate debug file if the TEST(SEPARATE) option is specified. When you use GONUMBER(SEPARATE), the statement numbers are not available for inclusion in runtime messages.
NOSEPARATE
Places the generated statement number table in the object deck.

Alternatively, the line numbers can be derived by using the offset address, which is always included in runtime messages, and either the table produced by the OFFSET option or the assembler listing produced by the LIST option.

GONUMBER is forced by the ALL and STMT suboptions of the TEST option.

Note that the GOSTMT option does not exist. The only option that produces information at run time identifying where an error has occurred is the GONUMBER option. When the GONUMBER option is used, the term statement in the runtime error messages refers to the line numbers as used by the NUMBER compiler option, even if the STMT option is in effect.

If the GONUMBER(SEPARATE) option is specified without TEST(SEPARATE), it is changed to GONUMBER(NOSEPARATE).

If both TEST and NOGONUMBER are specified, the NOGONUMBER option is changed to GONUMBER(NOSEPARATE).

The default is NOGONUMBER.

For compatibility, when the GONUMBER option is specified, the default suboption is SEPARATE.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)