HP 3000 Manuals HP 3000 Manuals
Messages 001-200
---------------------------------------------------------------------------------------
001 MESSAGE FLOATING POINT OVERFLOW (001)
CT CAUSE The absolute value of a real number is too large.
ACTION Check the permitted range of real/longreal values.
---------------------------------------------------------------------------------------
002 MESSAGE FLOATING POINT UNDERFLOW (002)
CT CAUSE The absolute value of a real number is non-zero and too small.
ACTION Check the permitted range of real/longreal values.
---------------------------------------------------------------------------------------
003 MESSAGE ERROR IN FLOATING POINT NUMBER REPRESENTATION (003)
CT CAUSE The real or longreal number must have a digit after the decimal
point.
ACTION Correct the constant to specify a fractional part.
---------------------------------------------------------------------------------------
004 MESSAGE AN EXPONENT IS REQUIRED HERE (004)
CT CAUSE The exponent for a real or longreal number is missing. A
number is required after the 'E' or 'L'.
ACTION Correct the constant to specify an exponent.
---------------------------------------------------------------------------------------
005 MESSAGE ILLEGAL CONTROL CHARACTER CONSTANT (005)
CT CAUSE The value of the constant following the sharp (#) is greater
than 255.
ACTION Check nonprinting character formation rules.
CAUSE The only nonnumeric characters that can follow a sharp (#) are
a letter, @, [, ], ||, ^, or _.
ACTION Check the permitted range of character values.
---------------------------------------------------------------------------------------
006 MESSAGE A QUOTE IS EXPECTED HERE (006)
CT CAUSE The end of line was found before the terminating quote. String
literals cannot span source lines.
ACTION Check string constant for missing closing quote or shorten
constant.
---------------------------------------------------------------------------------------
007 MESSAGE INTEGER OVERFLOW (007)
CT CAUSE The absolute value of the integer is greater than maxint.
ACTION Check the permitted range of integer values.
---------------------------------------------------------------------------------------
008 MESSAGE END OF FILE FOUND BEFORE EXPECTED (008)
CT CAUSE The compiler expects more source code. There may be an
unmatched BEGIN-END or an unclosed comment.
ACTION Check for missing END, semicolon, period, or incomplete
statement. Also check for an unclosed comment or $SKIP_TEXT
ON$.
---------------------------------------------------------------------------------------
009 MESSAGE UNRECOGNIZED CHARACTER (009)
CT CAUSE An illegal character was found in the source.
ACTION Check for unprintable characters and character validity in
context.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
010 MESSAGE 100 ERRORS--PROGRAM TERMINATED (010)
CT CAUSE Only 100 errors are allowed before the compiler stops.
ACTION Correct earlier errors so that compilation can continue.
---------------------------------------------------------------------------------------
011 MESSAGE A COMMA IS REQUIRED HERE (011)
CT CAUSE A comma is needed to separate procedure/function names in the
SUBPROGRAM compiler option.
ACTION Check syntax and insert a comma where necessary.
---------------------------------------------------------------------------------------
012 MESSAGE VARIABLE SPECIFICATION NOT ALLOWED HERE (012)
CT CAUSE Only SPL procedures are allowed to have a variable number of
parameters.
ACTION Remove the keyword VARIABLE or declare the routine SPL
VARIABLE.
---------------------------------------------------------------------------------------
013 MESSAGE IDENTIFIER DOUBLY DEFINED (013)
CT CAUSE An identifier in a parameter list is a duplicate of another
identifier.
The procedure/function name is defined earlier and is not a
FORWARD procedure/function.
The field name of a record is already declared.
The identifier is already declared in the current scope.
ACTION Delete duplicate declaration.
---------------------------------------------------------------------------------------
014 MESSAGE IDENTIFIER NOT DEFINED (014)
CT CAUSE The identifier is an undeclared variable, constant, procedure,
or function.
The type identifier is undeclared.
ACTION Add identifier to the declaration section.
---------------------------------------------------------------------------------------
015 MESSAGE INVALID VARIABLE USE (015)
CT CAUSE The control variable of a FOR loop is being modified in the
statement component of the FOR loop. For example:
* It is the control variable of a nested FOR loop.
* It appears on the left side of an assignment statement.
* It is being passed by reference to a user-defined or
standard procedure.
ACTION Remove assignment to loop control or conformant bound variable.
Do not pass this variable as a VAR, ANYVAR, or READONLY
parameter.
CAUSE The variable appears in the variable list of a WITH statement
but is not a record type.
ACTION Remove the variable from the WITH list.
CAUSE The identifier appears with subscripts, but it is not an array
or string.
ACTION Correct the array expression or remove the subscript.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
016 MESSAGE TYPE IDENTIFIER REQUIRED HERE (016)
CT CAUSE A constant or variable identifier has been used where a type
identifier is required.
ACTION Replace the constant or variable identifier with a type
identifier.
---------------------------------------------------------------------------------------
017 MESSAGE INVALID TYPE IDENTIFIER USE (017)
CT CAUSE A type identifier has been used where a constant or variable
identifier is required.
The construct in which the identifier occurs is not legal in
this context. This is often an array or record in executable
code.
ACTION Replace the type identifier with a constant or variable
identifier.
---------------------------------------------------------------------------------------
018 MESSAGE A CONSTANT EXPRESSION IS REQUIRED HERE (018)
CT CAUSE A variable occurs where a constant is required.
An expression with variables occurs where a constant expression
is required.
The expression contains an operator or a standard procedure or
function that is not legal in a constant expression.
The expression contains constant operands that are not legal;
for example, set or Boolean values.
ACTION Check the constant expression for a variable, or illegal type
of operand.
---------------------------------------------------------------------------------------
019 MESSAGE INVALID FORWARD TYPE IDENTIFIER DEFINITION (019)
CT CAUSE The identifier appeared in a forward pointer type definition
and is now being declared as something other than a type.
ACTION Check the FORWARD definition.
---------------------------------------------------------------------------------------
020 MESSAGE BOOLEAN EXPRESSION IS REQUIRED HERE (020)
CT CAUSE An expression with a Boolean result is required here.
ACTION Check the source and correct the expression.
---------------------------------------------------------------------------------------
021 MESSAGE AN ORDINAL EXPRESSION IS REQUIRED HERE (021)
CT CAUSE An expression with an ordinal result is required here.
ACTION Check the source and correct the expression.
---------------------------------------------------------------------------------------
022 MESSAGE INCOMPATIBLE SUBRANGE BOUNDS (022)
CT CAUSE The type of the lower bound is not compatible with the type of
the upper bound in a subrange.
ACTION Check the type of the lower and upper bounds and make them the
same.
---------------------------------------------------------------------------------------
023 MESSAGE AN INTEGER EXPRESSION IS REQUIRED HERE (023)
CT CAUSE An expression with an integer result is required for the repeat
factor in the 'OF' construct in an array constructor.
ACTION Check the source code and correct the expression.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
024 MESSAGE LOWER BOUND OF SUBRANGE IS GREATER THAN UPPER BOUND (024)
CT CAUSE The lower bound is greater than the upper bound in a subrange
type declaration.
ACTION Increase the upper bound, or decrease the lower bound.
---------------------------------------------------------------------------------------
025 MESSAGE FOUND UNEXPECTED "! " (025)
CT CAUSE The compiler was not expecting this token and it has been
discarded. The token is illegal here or a previous
undetectable error has caused the compiler to issue this
message; for example, a semicolon ( ; ) before ELSE.
ACTION Remove "! " or correct earlier error.
---------------------------------------------------------------------------------------
026 MESSAGE MISSING "! " (026)
CT CAUSE The compiler expected this token, but it was omitted or
misspelled. The correct token was inserted.
ACTION Insert "! "
---------------------------------------------------------------------------------------
027 MESSAGE "! " FOUND BEFORE EXPECTED. SOURCE MISSING. (027)
CT CAUSE The compiler found this token before it was expected. The
compiler was able to accept it by inserting dummy tokens.
ACTION Correct the syntax error and recompile.
---------------------------------------------------------------------------------------
028 MESSAGE MISUNDERSTOOD SOURCE BEFORE "! " (028)
CT CAUSE The compiler has discarded some previously accepted source code
preceding this token. Either the token is inappropriate, but
the compiler has been able to accept it by ignoring previous
code, or the token is correct and code must now be discarded.
ACTION Check the source code and fix the syntax.
---------------------------------------------------------------------------------------
029 MESSAGE " NOT ALLOWED AS A STRING LITERAL DELIMITER (029)
CT CAUSE A double quote cannot delimit a string literal.
ACTION Replace " with expected '.
---------------------------------------------------------------------------------------
030 MESSAGE OPEN FAILED ON FILE "! " (030)
CT CAUSE The compiler could not open the source file.
The compiler could not open the INCLUDE file.
The compiler could not open the SYSINTR or SPLINTR file.
ACTION Check for the correct file name spelling, file existence, and
any file equations.
---------------------------------------------------------------------------------------
031 MESSAGE READ FAILED ON SOURCE FILE (031)
CT CAUSE The compiler could not read the source file.
The compiler could not read the INCLUDE file.
ACTION Correct the condition causing the read to fail, such as a
corrupted file or any internal compiler errors.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
032 MESSAGE EMPTY SOURCE FILE (032)
CT CAUSE The source file is empty.
ACTION Check the file name.
---------------------------------------------------------------------------------------
033 MESSAGE MISSPELLED RESERVED WORD: "! " (033)
CT CAUSE The reserved word is misspelled.
ACTION Correct the spelling of the reserved word.
---------------------------------------------------------------------------------------
034 MESSAGE FORWARD TYPE "! " NOT FOUND (034)
CT CAUSE The identifier occurs in a pointer type definition but is not
subsequently defined.
ACTION Define the identifier.
---------------------------------------------------------------------------------------
035 MESSAGE FORWARD PROCEDURE "! " NOT DECLARED (035)
CT CAUSE A procedure declared with the FORWARD directive is not
subsequently defined. The definition may be missing, or the
name appearing in the definition may be misspelled.
ACTION Declare the procedure.
---------------------------------------------------------------------------------------
036 MESSAGE VIOLATION OF PASCAL SCOPING RULES (036)
CT CAUSE The scope of an HP Pascal identifier is the entire block in
which it is declared. It is not possible to use an identifier
from an enclosing level and then to redefine it at the new
level.
ACTION Use a separate identifier in this text.
---------------------------------------------------------------------------------------
037 MESSAGE INVALID USE OF "! " IN POINTER DEFINITION (037)
CT CAUSE A non-type identifier defined on a previous level was used in a
pointer type definition.
ACTION Replace the non-type identifier with a type identifier.
---------------------------------------------------------------------------------------
038 MESSAGE ILLEGAL PASCAL CONSTRUCT (038)
CT CAUSE The use of the FOR construct within strings is illegal.
ACTION Use another looping construct with strings.
---------------------------------------------------------------------------------------
039 MESSAGE "! " ACCESSED, BUT NOT INITIALIZED (039)
CT CAUSE A simple variable appears in an expression, as a value
parameter, or in some other accessing reference and it has
never appeared in an assigning reference, such as a reference
parameter, or on the left side of an assignment statement.
Some component of a structured variable appears in an accessing
reference but no component of that variable has yet appeared in
an assigning reference.
ACTION Initialize the variable before it is used.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
040 MESSAGE INVALID STRING TYPE USE (040)
CT CAUSE The standard type identifier string is not used to define a
string type.
ACTION Use the standard identifier string to define this type.
---------------------------------------------------------------------------------------
041 MESSAGE MISSING SEPARATOR BETWEEN NUMBER AND IDENTIFIER (041)
CT CAUSE A character was detected immediately following a number. HP
Pascal requires a separator, such as a space, comment, or
end-of-line between a number and an identifier or reserved
word.
ACTION Insert a separator between the number and the identifier.
---------------------------------------------------------------------------------------
042 MESSAGE ^STRING IS NOT ALLOWED IN TYPE DECLARATIONS (042)
CT CAUSE ^STRING was used in a pointer type declaration. A user
definition for STRING did not follow so an error was produced
when the compiler checked for unresolved forward pointer
declarations. The generic type STRING is only allowed for VAR
parameters.
ACTION Remove use of string in type declaration.
---------------------------------------------------------------------------------------
043 MESSAGE THIS FEATURE REQUIRES $OS ! (043)
CT CAUSE This feature is not available under the current OS level.
---------------------------------------------------------------------------------------
044 MESSAGE THIS FEATURE DOES NOT CONFORM WITH THE ANSI/ISO STANDARD (044)
CT CAUSE This feature is not available under the current STANDARD_LEVEL.
ACTION Remove this feature if ANSI/ISO conformance is desired.
Remove STANDARD_LEVEL compiler option if this feature is
desired.
Use the compiler option STDPASCAL_WARN if a warning message
rather than an error message is desired with the current
STANDARD_LEVEL that is set.
---------------------------------------------------------------------------------------
045 MESSAGE ONLY COMMENTS AND COMPILER OPTIONS ARE ALLOWED IN '!' (045)
CT CAUSE Text which is neither a comment nor a compiler option was
detected in the system-wide option file.
ACTION Remove any text which is neither a comment nor a compiler
option from the system-wide option file. Because this file is
write-protected, your system administrator should be notified.
---------------------------------------------------------------------------------------
060 MESSAGE OPERAND NOT OF TYPE BOOLEAN (060)
CT CAUSE A non-Boolean operand appears with the operator NOT, OR, or
AND.
ACTION Change the operator to a Boolean type.
---------------------------------------------------------------------------------------
061 MESSAGE WRONG TYPE OF OPERAND FOR ARITHMETIC OPERATOR (061)
CT CAUSE A nonnumeric operand appears with an arithmetic operator.
ACTION Check and correct the operand or operator.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
062 MESSAGE TYPE OF OPERAND NOT ALLOWED WITH OPERATOR (062)
CT CAUSE An operand of this type cannot be used with this operator.
ACTION Check and correct the operand or operator.
---------------------------------------------------------------------------------------
063 MESSAGE BASE TYPE OF OPERAND AND SET DO NOT AGREE (063)
CT CAUSE The operand on the left of an IN operator is not type
compatible with the set on the right.
ACTION Check the operands to ensure compatible types.
---------------------------------------------------------------------------------------
064 MESSAGE TYPES OF OPERANDS DO NOT AGREE (064)
CT CAUSE The operands can be used separately but not with the operator.
For example, <Boolean> = <integer>.
ACTION Check and correct one of the two operands.
---------------------------------------------------------------------------------------
065 MESSAGE ASSIGNMENTS CANNOT BE MADE TO FILES (065)
CT CAUSE An assignment cannot be made to a file or a structured variable
with a file type component.
Structured constants cannot contain files. Building a
structured constant with a type that contains a file is
illegal.
Variables which contain files cannot be passed as value
parameters.
ACTION Remove the file assignment.
---------------------------------------------------------------------------------------
066 MESSAGE ASSIGNMENT TYPE CONFLICT (066)
CT CAUSE The expression on the right side of an assignment statement is
not assignment compatible with the receiving entity on the
left.
A constant in a constructor is not assignment compatible with
the component to which it is being assigned. The subrange type
of the expression being assigned does not intersect the type of
the receiving entity.
ACTION Check the assignment compatibility rules.
---------------------------------------------------------------------------------------
067 MESSAGE TYPE OF EXPRESSION NOT ALLOWED IN SUBRANGE (067)
CT CAUSE The expression defining a subrange bound is not an ordinal
expression.
ACTION Replace the expression with an ordinal expression.
---------------------------------------------------------------------------------------
068 MESSAGE ILLEGAL ASSIGNMENT TARGET (068)
CT CAUSE An assignment was made to an identifier that is not a non-file
variable or a function result; for example, a declared
constant, a set, or string type identifier.
ACTION Correct the left-hand side of the assignment.
---------------------------------------------------------------------------------------
069 MESSAGE INVALID CONSTANT EXPRESSION (069)
CT CAUSE This expression is not legal in a CONST declaration. It is not
a constant expression, or it is a constant expression and the
results of the arithmetic would be out of range of
minint..maxint.
ACTION Correct the expression.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
070 MESSAGE ILLEGAL TO ASSIGN TO (070)
CT CAUSE The identifier denotes an entity that cannot appear on the
right side of an assignment statement; for example, a set or
string type identifier.
ACTION Correct the right-hand side of the assignment.
---------------------------------------------------------------------------------------
072 MESSAGE REAL CONSTANT FOLDING NOT AVAILABLE IN $HP3000_16$ (072)
CT CAUSE Temporary restriction on real constant folding in $HP3000_16$.
This is transparent, except when an integer value is specified
for a real field in a structured constant declaration. This
also occurs if a real constant is specified for a longreal
constant .
ACTION Change the integer constant to a real one by appending ".0", or
add "L0" to the real number.
---------------------------------------------------------------------------------------
080 MESSAGE ARRAY INDEX TYPES NOT COMPATIBLE (080)
CT CAUSE The subscript in an array reference is not compatible with the
type of the index in the array declaration.
ACTION Change the array subscript to be compatible with the type of
the index.
---------------------------------------------------------------------------------------
081 MESSAGE ARRAY ELEMENT TYPES NOT EQUIVALENT (081)
CT CAUSE PACK and UNPACK array parameters must have identical component
types.
ACTION Use identical component types.
---------------------------------------------------------------------------------------
082 MESSAGE INVALID ARRAY SIZE (082)
CT CAUSE The size of the array is too big for the compiler.
In PACK or UNPACK the destination array is not large enough.
ACTION Use a smaller array size.
---------------------------------------------------------------------------------------
083 MESSAGE WRONG NUMBER OF ELEMENTS FOR ARRAY OR STRING CONSTANT (083)
CT CAUSE While building an array or string constant, more components
were specified than declared.
Not all the components were specified while building an array
constant.
ACTION Use the correct number of components that need to be specified.
---------------------------------------------------------------------------------------
084 MESSAGE INVALID INDEX TYPE (084)
CT CAUSE Index type is not an ordinal type.
ACTION Use an ordinal type.
---------------------------------------------------------------------------------------
085 MESSAGE REFERENCE TYPE MUST BE STRING OR ARRAY (085)
CT CAUSE Tried to index a structure that is not an array or string.
ACTION Use an array or string in this context.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
086 MESSAGE MAXIMUM STRING LENGTH MUST BE BETWEEN 1 AND ! (086)
CT CAUSE Tried to declare string with a maximum length < 1 or > the
limit mentioned in the message.
ACTION Correct the string maximum length specification so it is in the
permitted range.
---------------------------------------------------------------------------------------
087 MESSAGE EXPRESSION FOR MAXIMUM LENGTH MUST BE TYPE INTEGER (087)
CT CAUSE Tried to declare a string with a noninteger constant expression
for the maximum length.
ACTION Use an integer constant in this context.
---------------------------------------------------------------------------------------
088 MESSAGE INCORRECT NUMBER OF INDICES FOR STRING DECLARATION (088)
CT CAUSE A string can only have one index in a declaration.
No index was supplied in a string declaration.
ACTION Use only one index in a string declaration.
---------------------------------------------------------------------------------------
089 MESSAGE TOO MANY SUBSCRIPTS IN STRING OR ARRAY REFERENCE (089)
CT CAUSE The number of subscripts in the reference exceeds the number of
subscripts in the declaration of the array or string.
ACTION Correct the number of subscripts.
---------------------------------------------------------------------------------------
090 MESSAGE ILLEGAL CONSTRUCT FOR AN ARRAY OR STRING INDEX (090)
CT CAUSE A subrange construct was used as an array or string index.
ACTION Correct the subrange construct.
---------------------------------------------------------------------------------------
100 MESSAGE INVALID RECORD REFERENCE (100)
CT CAUSE Record field referenced without specifying a record variable,
constant, or function call that returns a record.
ACTION Qualify the name completely (i.e., specify which record
variable this is a field of).
---------------------------------------------------------------------------------------
101 MESSAGE INVALID FIELD IDENTIFIER (101)
CT CAUSE The identifier is not one of the fields of the record used in
the reference.
ACTION Check the field name and the record type definition.
---------------------------------------------------------------------------------------
102 MESSAGE INVALID TAG TYPE (102)
CT CAUSE The tag in a NEW or DISPOSE procedure call is not a tag value
of the specified record.
ACTION Correct or remove the non-tag value.
---------------------------------------------------------------------------------------
103 MESSAGE POINTER OR FILE REQUIRED FOR DEREFERENCE (103)
CT CAUSE A pointer or file is required in a dereference.
ACTION Remove up-arrow or change preceding expression to be of type
pointer or file.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
104 MESSAGE POINTER VARIABLE IS REQUIRED HERE (104)
CT CAUSE NEW, DISPOSE, MARK, and RELEASE all require a pointer variable
as the first parameter.
ACTION Declare and supply a pointer variable.
---------------------------------------------------------------------------------------
106 MESSAGE MISSING TAG VALUES FOR TAG TYPE (106)
CT CAUSE Not all tag values for a tag type in the record are specified.
ACTION Add empty variant declarations for the missing tag values.
---------------------------------------------------------------------------------------
120 MESSAGE INVALID BASE TYPE FOR SET (120)
CT CAUSE The base type of a set is not an ordinal type.
ACTION Check usage in the source program.
---------------------------------------------------------------------------------------
121 MESSAGE ITEM NOT A LEGAL SET ELEMENT (121)
CT CAUSE Element of a set is not an ordinal type.
ACTION Replace item with a valid element for this set.
---------------------------------------------------------------------------------------
122 MESSAGE OPERAND NOT A SET (122)
CT CAUSE Right operand for an IN operator is not a set.
ACTION Change expression to set type.
---------------------------------------------------------------------------------------
123 MESSAGE SET ELEMENTS NOT TYPE COMPATIBLE WITH EACH OTHER (123)
CT CAUSE In an untyped set constructor, this element is not compatible
with the first element in the set.
ACTION Change types so they are compatible.
---------------------------------------------------------------------------------------
124 MESSAGE SET ELEMENT NOT COMPATIBLE WITH SET TYPE (124)
CT CAUSE In a typed set constructor, the set element is not assignment
compatible with the base type of the set.
ACTION Replace element with a valid element for this set.
---------------------------------------------------------------------------------------
125 MESSAGE SET OF THIS SIZE CANNOT BE CONSTRUCTED (125)
CT CAUSE To construct this set would require more bytes than can be
specified for this implementation.
ACTION Define/declare set to have fewer elements.
---------------------------------------------------------------------------------------
140 MESSAGE BUILDING OF STRUCTURED CONSTANTS NOT ALLOWED HERE (140)
CT CAUSE A constructor that is not a set constructor occurs outside of a
CONST declaration section.
ACTION Create a named constant in the CONST section and use its name
here.
CAUSE A constructor occurs as an element of a set or string
constructor.
ACTION Remove the constructor from the set or string.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
141 MESSAGE RECORD CONSTANT HAS MISSING FIELD(S) (141)
CT CAUSE One or more fields missing in a record constructor.
The name of a field is misspelled.
ACTION Correct erroneous field name. Add the missing fields.
---------------------------------------------------------------------------------------
142 MESSAGE DUPLICATE FIELD NAME (142)
CT CAUSE This field has already been defined in the constructor.
ACTION Delete the duplicate declaration.
---------------------------------------------------------------------------------------
143 MESSAGE FIELD NAME DESIGNATOR NOT ALLOWED HERE (143)
CT CAUSE The constructor is not a record constructor.
This construction <field name>:<expression> appears outside of
a record constructor.
ACTION Remove the field name designator from the code.
---------------------------------------------------------------------------------------
144 MESSAGE MISSING FIELD NAME DESIGNATOR (144)
CT CAUSE The construction <field name>:<expression> is required in a
record constructor.
ACTION Add a field name designator to the code.
---------------------------------------------------------------------------------------
145 MESSAGE TYPE IDENTIFIER REQUIRED HERE (145)
CT CAUSE The identifier preceding the left square bracket of a
constructor is not a type identifier.
ACTION Check the syntax of structured constants.
CAUSE The identifier in the bounds construct of a conformant array
parameter is not a type identifier.
ACTION Change either the declaration or the usage of the identifier to
make sure they are consistent.
---------------------------------------------------------------------------------------
146 MESSAGE CONSTRUCT ONLY ALLOWED FOR ARRAYS AND STRINGS (146)
CT CAUSE <Count> OF <expression> occurs when the constructor is not an
array or string constructor.
ACTION List each element individually and specify its value.
---------------------------------------------------------------------------------------
147 MESSAGE CONSTRUCT ONLY ALLOWED IN CONSTRUCTORS (147)
CT CAUSE <Count> OF <expression> is used outside of a constructor.
ACTION Remove the <count> OF <expression> from the code.
---------------------------------------------------------------------------------------
148 MESSAGE SUBRANGE CONSTRUCT ILLEGAL EXCEPT IN SET CONSTRUCTORS (148)
CT CAUSE A subrange construct was used in a string declaration or a non
set structured constant.
ACTION Remove the subrange construct from the code.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
149 MESSAGE TOO BIG STRUCTURED CONSTANT (149)
CT CAUSE The compiler's structured constant table has overflowed.
ACTION If there are one or more structured constants larger than the
table size, break them up into smaller constants, if possible.
If the total size of all the structured constants exceeds the
limit, break your compilation unit into smaller pieces and
spread the constants over them.
Note: The first action may cause the second condition to
arise!
---------------------------------------------------------------------------------------
150 MESSAGE EXPANDED STRING LITERAL IS TOO BIG (150)
CT CAUSE The compiler's identifier table has overflowed.
ACTION Break your compilation unit into smaller pieces and spread your
string literals over them.
Read in the string literals from a message catalog.
If the same quoted string is used over and over in the code,
declare it as a constant in one place and use the named
constant instead.
---------------------------------------------------------------------------------------
151 MESSAGE TYPE OF CONFORMANT ARRAY BOUNDS MUST BE SCALAR (151)
CT CAUSE The type identifier in the index specification for a conformant
array parameter does not designate a scalar type.
ACTION Change index to scalar or subrange.
---------------------------------------------------------------------------------------
152 MESSAGE PARAMETER DOUBLY DEFINED (152)
CT CAUSE In the index specification of a conformant array parameter the
upper bound identifier has the same spelling as the lower bound
identifier.
In an index specification of a conformant array parameter a
bounds identifier has the same spelling as another parameter or
as another bounds identifier in the parameter list of the
current procedure header.
ACTION Rename one of the duplicate identifiers.
---------------------------------------------------------------------------------------
153 MESSAGE NOT ALLOWED AS AN ANYVAR PARAMETER (153)
CT CAUSE A parameter can not be an AnyVar parameter and a conformant
array parameter.
ACTION Change the formal parameter specifier to VAR or omit it.
---------------------------------------------------------------------------------------
154 MESSAGE NON CONFORMANT BASE TYPE (154)
CT CAUSE The base type of an array being passed as an actual conformant
array parameter must be identical to the base type of the
formal conformant array parameter.
ACTION Change either the actual array's index type or the formal
conformant array's index type so the two are compatible.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
155 MESSAGE NON CONFORMANT ACTUAL PARAMETER (155)
CT CAUSE The parameter being passed as an actual conformant array
parameter does not have an array type.
ACTION Check the parameter and make sure it has an array type.
CAUSE The parameter being passed as an actual conformant array
parameter does not have the same packing as the formal
parameter.
ACTION Check that the packing of both parameters are the same and
correct if necessary.
---------------------------------------------------------------------------------------
156 MESSAGE NON CONFORMANT ARRAY INDEX (156)
CT CAUSE The index type of the actual conformant array parameter is out
of range of the type of the index type of the formal parameter.
ACTION Change either the actual array's bounds or the formal
conformant array's bounds so the actual bounds lie within the
formal bounds.
---------------------------------------------------------------------------------------
157 MESSAGE NON IDENTICAL TYPE FOR PARAMETER IN CONFORMANT PARAMETER LIST
(157)
CT CAUSE In a parameter declaration of the form:
p1, p2...pn: <conformant array declaration>, the actual
parameters passed must have identical types.
ACTION Check the type declarations of the actual parameters, and
ensure that they have the same type.
Break up the formal parameter specifications i.e., make
separate and complete declarations of each of p1, p2...pn.
---------------------------------------------------------------------------------------
158 MESSAGE CRUNCHED CONFORMANT ARRAYS ARE NOT ALLOWED (158)
CT CAUSE Conformant array parameters cannot be CRUNCHED.
ACTION Remove CRUNCHED, or change to PACKED.
---------------------------------------------------------------------------------------
159 MESSAGE NO PACKED CONFORMANT ARRAYS OF CONFORMANT ARRAYS (159)
CT CAUSE Packed conformant arrays cannot have, as their elements,
conformant arrays.
ACTION Add PACKED to the inner type. Remove PACKED from the outer
type.
---------------------------------------------------------------------------------------
160 MESSAGE INVALID BASE TYPE FOR FILE (160)
CT CAUSE The component type of a file may not be a file or a structure
with a file type component.
ACTION Remove/change the file being referenced or the declaration of
the file.
---------------------------------------------------------------------------------------
161 MESSAGE TEXTFILE VARIABLE IS REQUIRED HERE (161)
CT CAUSE The predefined procedure or function in question may only be
used with a file of type text.
ACTION Remove/change the file being referenced or the routine being
used.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
162 MESSAGE TEXTFILE NOT ALLOWED HERE (162)
CT CAUSE The standard procedure or function in question may not be used
with a file of type text.
ACTION Remove/change the file being referenced or the routine being
used.
---------------------------------------------------------------------------------------
163 MESSAGE INVALID TYPE FOR A PROGRAM PARAMETER (163)
CT CAUSE An identifier in the program parameter list has not been
declared as a file variable, or a variable of type PAC, string,
or integer.
ACTION Correct the actual declaration to be a file declaration or
remove the identifier from the program statement.
---------------------------------------------------------------------------------------
164 MESSAGE VARIABLE IS REQUIRED HERE (164)
CT CAUSE A variable is required as the target for reading from a file or
a string.
ACTION Supply a variable in the code.
---------------------------------------------------------------------------------------
165 MESSAGE DEFAULT FILE INPUT MUST BE IN PROGRAM PARAMETER LIST (165)
CT CAUSE The file variable in a standard procedure or function call was
defaulted to INPUT, but INPUT was not declared in the program
parameter list.
ACTION Either add 'INPUT' to the program heading or remove the
redefinition of 'INPUT', if one was made.
---------------------------------------------------------------------------------------
166 MESSAGE DEFAULT FILE OUTPUT MUST BE IN PROGRAM PARAMETER LIST (166)
CT CAUSE The file variable in a standard procedure or function call was
defaulted to OUTPUT, but OUTPUT did not appear in the program
parameter list.
ACTION Add 'OUTPUT' to the program heading or remove the redefinition
of 'OUTPUT', if one was made.
---------------------------------------------------------------------------------------
167 MESSAGE FORMAT EXPRESSION ALLOWED ONLY FOR TEXTFILES (167)
CT CAUSE A formatted output expression may only occur when writing to a
textfile or a string.
ACTION Remove the formatted expression from the code.
---------------------------------------------------------------------------------------
168 MESSAGE INTEGER VALUE IS REQUIRED HERE (168)
CT CAUSE The expressions specifying the field width and the number of
decimal digits for an output expression are not type integer or
a subrange of integer.
ACTION Replace with an integer expression.
---------------------------------------------------------------------------------------
169 MESSAGE SECOND FORMAT VALUE ALLOWED ONLY FOR REAL OR LONGREAL (169)
CT CAUSE The format value that specifies the number of decimal digits in
an output expression is only legal for output values of type
real or longreal.
ACTION Check type of parameter or remove decimal position specifier.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
190 MESSAGE THIS PROGRAM PARAMETER WAS UNDECLARED: "! " (190)
CT CAUSE The identifier appeared in the program parameter list but was
never declared.
ACTION Add the identifier declaration.
---------------------------------------------------------------------------------------
191 MESSAGE DUPLICATE PROGRAM PARAMETER (191)
CT CAUSE There is more than one PARM parameter or more than one INFO
parameter in a program parameter list.
ACTION Remove duplicate declarations.
---------------------------------------------------------------------------------------
192 MESSAGE PARAMETER "! " DOES NOT MATCH POSSIBLE SPL TYPES (192)
CT CAUSE The HP Pascal type of the parameter does not correspond to an
acceptable SPL type.
ACTION Change the parameter definition to a type that will correspond
to the SPL type.
---------------------------------------------------------------------------------------
193 MESSAGE PARAMETER "! " DOES NOT MATCH INTRINSIC PARM TYPE (193)
CT CAUSE The HP Pascal type of the parameter does not match the
parameter type required by the INTRINSIC.
ACTION Change the parameter definition to a type that will correspond
to the intrinsic type.
---------------------------------------------------------------------------------------
194 MESSAGE MISSING FUNCTION RETURN SPECIFICATION (194)
CT CAUSE The return type is not specified in the function heading.
ACTION Insert the result type declaration.
---------------------------------------------------------------------------------------
195 MESSAGE INVALID PARAMETER TO HALT (195)
CT CAUSE The optional parameter to HALT is not type integer or an
integer subrange.
ACTION Change the parameter to type integer or supply no parameter.
---------------------------------------------------------------------------------------
196 MESSAGE THIS INTRINSIC MAY NOT BE USED AS A FUNCTION (196)
CT CAUSE The specified intrinsic does not return a result and cannot be
declared as a function.
ACTION Redeclare the intrinsic as a procedure.
---------------------------------------------------------------------------------------
197 MESSAGE ELEMENTS OF PACKED OR CRUNCHED STRUCTURES CANNOT BE PASSED BY
VAR (197)
CT CAUSE Elements of packed arrays or records may not be passed to a
routine expecting a reference parameter.
ACTION Redeclare the intrinsic as a procedure.
---------------------------------------------------------------------------------------
198 MESSAGE EMPTY PARAMETER MAY NOT BE USED HERE (198)
CT CAUSE Actual parameters may only be omitted for EXTERNAL SPL VARIABLE
procedures or for intrinsics that are extensible and/or have
default parameters.
ACTION Supply a value for the parameter in question.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
199 MESSAGE PROCEDURE NOT DECLARED (199)
CT CAUSE The identifier used in the procedure call either has not been
declared, or it is not a procedure name.
ACTION Check the spelling of the procedure and make sure it is
declared.
---------------------------------------------------------------------------------------
200 MESSAGE PARAMETER "! " MUST BE VAR PARAMETER. (200)
CT CAUSE The parameter in the intrinsic declaration was specified as a
value parameter, but the intrinsic requires a reference
parameter.
ACTION Change the intrinsic declaration so that it specifies the
parameter in question as a VAR parameter.