Specifications
Message
56
57
58
Significance
The program name is expected in this field.
Too
many dimensions caused a table overflow.
The symbol table overflowed; compilation
terminates.
59
The statement label may not be zero.
~o
61
There is
no
apparent exit from this program.
Unclosed
DO-implied list
62
An
unformatted
WRITE
must have a list.
63
64
65
66
67
68
The name must be an integer variable or
integer constant.
The name
is
not implicitly an integer variable.
A
RETURN
statement may appear only in a
subroutine or function definition. A
STOP
statement is assumed.
Superflous information
in
this statement is
ignored.
This field
on
the
STOP
card must have an octal
number not greater than 77777.
STOP
is
assumed.
The field must be a positive integer.
69
The field must be an integer variable.
70
71
72
73
74
75
77
78
79
96769450
A
The field must be a statement label.
This form of the
ASSEM
argument cannot
reference elements in
COMMON,
EXTERNAL
names, or subprogram arguments.
This type of statement may not terminate a
DO
loop.
This statement terminates a
DO
loop
when
it
is not the last
DO
encountered.
This
GO
TO
jumps
to
itself.
A program consisting of only an
END
card
is
illegal.
Too
many
unique dummy parameter references
caused a compiler table overflow.
The label in a
DO
statement must reference a
statement following it.
The maximum allowable number of nested
DOs
was
exceeded. The
DO
loop may be implied
in
a
DO
list.
Message
80
81
82
83
84
85
87
88
89
90
91
92
100
101
103
110
111
Significance
Subroutine argument table overflow caused by
a large number of declared parameters and
unique references to these parameters.
This formal argument
was
previously specified
as another formal argument or the subprogram
name.
Too
many formal arguments caused a compiler
table overflow.
The above name is not a variable or an array
element.
Two
elements of the same array or common
block are assigned
to
the same storage unit.
Blank
common and formal arguments may not
be initialized with
DATA
statements.
An
array element in a
BYTE,
SIGNED
BYTE,
DATA,
or
EQUIVALENCE
statement
either
has the wrong number of subscripts or the
subscript is out of range.
Too
many
EQUIVALENCE
names caused a
compiler table overflow.
At least two elements must appear
in
an
EQUIVALENCE
statement.
The
preceding equivalenced symbols have
overflowed the origin of common.
The
DATA
statement
field is not an integer,
real, double precision, or literal constant.
Missing terminating asterisk or quote in a
literal string as appropriate.
Catastrophic table overflow; compilation is
abandoned.
If
the offending statement is
arithmetic or a logical IF, the statement
should be broken into two or more statements
and the program recompiled.
Two
PROGRAM,
FUNCTION,
SUBROUTINE,
or
BLOCK
DATA
statements in one program
unit; the second
is
ignored.
The
relative address argument in the
ASSEM
statement requires an asterisk
at
the end of
the preceding instruction.
An
overflow of the table used for symbol
references; subsequent references are not
listed
by
the option S processor.
The index used in this subscripted variable
is
in
conflict with the dimension declaration.
5-9