Ch 2. Messages Issued During Syntax Checking [ COBOL/HP-UX Error Messages for the Series 700 and 800 ] MPE/iX 5.0 Documentation
COBOL/HP-UX Error Messages for the Series 700 and 800
Chapter 2 Messages Issued During Syntax Checking
Introduction
The messages described in this chapter are produced when the COBOL system
checks the syntax of your COBOL programs prior to producing intermediate
code. They indicate that either your COBOL syntax is incorrect or there
are inconsistencies in your program. This chapter contains a list of
these messages in numerical order.
Error Messages
Your COBOL system displays these messages in the following format:
LINE OF COBOL CODE.
**nnnn-A**** (mmmm)**
**message here
where
nnnn is the message number
mmmm is the page on which the previous message occurred.
A is a one-letter identifier that shows the severity of the
message as follows:
U Unrecoverable. An unrecoverable fault causes your COBOL
system to stop. A message of this severity is actually
produced by the run-time system, and you should refer to
Chapter 4 , of Run-Time System Messages later in this
manual for details of such messages.
S Severe. When a severe fault is encountered,
intermediate code is not produced for the statement in
error. Consequently, you cannot use this intermediate
code to generate native code, and you will not be able
to run code containing severe faults. You can, however,
use the Animator software on intermediate code
containing severe faults if you set the E switch on.
See your COBOL System Reference for details. If you use
either of these methods to execute the intermediate code
produced, results are unpredictable.
Following an S-level error, the source code between the
word that caused the error and the next recognizable
verb or the beginning of the next sentence is ignored.
Consequently, when you correct the original error and
resubmit your program, more errors may be found.
E Error. Whenever an error fault occurs in your source
code, your COBOL system attempts to correct the error
and continues to check the syntax and produce
intermediate code. Your COBOL system makes assumptions
about what was intended, and if this varies from your
expectations, then you should correct the source code
that is in error. In any case, you may wish to correct
the source code so that you can produce intermediate
code with no errors.
You can animate intermediate code that contains errors,
and you can also produce generated code from it, or run
it, if you set the E switch on. See your COBOL System
Reference for details..
W Warning. A warning indicates that there may be an error
or inconsistency in the source code; the statement
might, however, be syntactically correct.
You can animate intermediate code that contains
warnings, and you can also produce generated code from
it, or run it.
I Information. An information message draws your
attention to something in the source code of which you
may need to be aware. This kind of message does not
imply there is a fault, nor are you required to take any
action.
You can animate intermediate code that contains
information messages, and you can also produce generated
code from it, or run it.
The same message can appear with a different severity in
different circumstances.
Note that error, warning, and information messages may or may
not be produced by your COBOL system, depending on the setting
of the WARNING directive. Refer to your COBOL System
Reference for details.
Many of the severe faults and errors have a cumulative effect.
Thus if a fault is reported at an early stage in your coding
it will probably have a 'knock on' effect and produce a series
of messages as your COBOL system goes through the rest of your
code. Often a simple mistake (such as failing to put a period
at an expected place) will cause a series of messages to be
given, all of which originate from the initial fault. In
cases such as this you will often find that one very simple
amendment to your code (such as inserting a period), could be
all that is needed to recover from a run of severe faults and
errors.
Flags
In addition to the various types of messages described here, your COBOL
system may produce flags. Your COBOL system displays these in a similar
format to the messages:
LINE OF COBOL CODE.
* * nnnn-flagtype * * * * * *
* * flag message here
where
nnnn is the flag number
flagtype shows the level of syntax, as described below.
When you use the FLAG directive, those areas of syntax not supported at
the level you choose are highlighted in this way. The flagtype shows the
lowest level at which this feature is supported, and can be any of:
LOW GSA low level
L-I GSA low intermediate level
H-I GSA high intermediate level
HIGH GSA high level
MF Micro Focus extension to ANSI COBOL standard X3.23
1974
OSVS IBM OS/VS COBOL
VSC2 IBM VS COBOL II
ANS74 ANSI COBOL standard X3.23 1974
ANS85 ANSI COBOL standard X3.23 1985
SAA Full implementation of IBM's System Application
Architecture definition of COBOL
depending on the options to the flag directives that are available to
you. Refer to your COBOL System Reference for details of the FLAG
directive. When you use the FLAGSTD directive, those areas of syntax not
supported by the ANSI '85 COBOL subset and/or optional modules selected
are highlighted by flags. The flagtype shows the lowest level at which
the feature is supported, and can be any of:
MIN Minimum level
INT Intermediate level
HIGH High level
MF Micro Focus extension to ANSI COBOL standard X3.23
1985
OSVS IBM OS/VS COBOL
VSC2 IBM VS COBOL II
SAA Full implementation of IBM's System Application
Architecture definition of COBOL.
The flags produced depend on the options supplied to the FLAGSTD
directive: refer to your COBOL System Reference for details of the
FLAGSTD directive.
Your COBOL system produces these flags only when the FLAG or FLAGSTD
directive is in effect. These flags are for your information, and
indicate those areas of potential incompatibility if you intend to use
your program in a different operating environment. Flags do not affect
the running of your program, nor do they prevent you from producing
generated code or from using the Animator debugging tool.
Flags in the range 404 to 451 are produced if the source program exceeds
the limits of the mainframe compiler implementation specified in the FLAG
directive. A full table of the limits for each mainframe dialect can be
found in Appendix A , Flagging of SAA, OSVS and VSC2 Implementation
Limits. The limits shown in the messages are those for the SAA
implementation where applicable.
Names in Messages
When displayed, some messages contain an actual name from your program.
In this manual, the place where the name will be inserted is shown by a
description of the type of name, in italics. For example, message 1146
is shown in this manual as:
1146 procedure-name-1 lies in more than one PERFORM THRU range
If the procedure-name concerned were CALCULATE-TAX, the actual
message displayed would be:
1146 CALCULATE-TAX lies in more than one PERFORM THRU range
MPE/iX 5.0 Documentation