HP 3000 Manuals HP 3000 Manuals
Messages 201-527
---------------------------------------------------------------------------------------
201 MESSAGE PARAMETER "! " MUST BE VALUE PARAMETER (201)
CT CAUSE The parameter in the intrinsic declaration was specified as a
reference parameter, but the intrinsic requires a value
parameter.
ACTION Change the intrinsic declaration to specify the parameter in
question as a value parameter.
---------------------------------------------------------------------------------------
202 MESSAGE INVALID USE OF PROCEDURE OR FUNCTION IDENTIFIER (202)
CT CAUSE A procedure identifier appears as a function call.
A function identifier appears as a procedure call.
A valid identifier mistakenly appears as a function or
procedure identifier.
ACTION Change either the declaration or the usage of the identifier to
make sure they are consistent.
---------------------------------------------------------------------------------------
203 MESSAGE INCONSISTENT DEFINITION OF FORWARD PROCEDURE OR FUNCTION (203)
CT CAUSE The definition of a procedure declared FORWARD is a function.
The definition of a function declared FORWARD is a procedure.
ACTION Change either the declaration or the usage of the identifier to
make sure they are consistent.
CAUSE The ALIAS in the definition differs from the ALIAS in the
FORWARD declaration of a procedure or function.
ACTION Make ALIAS names identical or only use ALIAS in the FORWARD
declaration.
CAUSE A FORWARD declaration is already provided for a function or
procedure now declared FORWARD, EXTERNAL, or INTRINSIC.
ACTION Remove all but one of the declarations.
CAUSE The definition is missing a routine option or compiler option
which was specified in the FORWARD declaration.
ACTION Make sure all routine options or compiler options are repeated
in the definition of the procedure or function.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
204 MESSAGE INVALID DIRECTIVE (204)
CT CAUSE EXTERNAL, EXTERNAL SPL, EXTERNAL SPL VARIABLE, EXTERNAL
FORTRAN, EXTERNAL FTN77, EXTERNAL C, EXTERNAL COBOL, FORWARD,
and INTRINSIC are the only legal directives.
ACTION Remove the directive from the code or correct the spelling.
---------------------------------------------------------------------------------------
205 MESSAGE INVALID LANGUAGE SPECIFICATION (205)
CT CAUSE The language specified was not FORTRAN, SPL, COBOL, FTN77, or
C.
A language cannot be specified with the FORWARD or INTRINSIC
directives.
ACTION Remove or correct the language specification.
---------------------------------------------------------------------------------------
206 MESSAGE INCORRECT NUMBER OF PARAMETERS (206)
CT CAUSE The number of actual parameters given is either too few or too
many for the procedure or function.
ACTION Check consistency between the procedure call and procedure
declaration.
---------------------------------------------------------------------------------------
207 MESSAGE UNMATCHED PARAMETERS IN FORWARD (207)
CT CAUSE Parameters in the definition of a procedure or function
declared FORWARD do not match the parameters of the original
heading.
ACTION Check whether the FORWARD routine declaration and the routine
declaration are consistent.
---------------------------------------------------------------------------------------
208 MESSAGE ACTUAL PARAMETER NOT COMPATIBLE WITH FORMAL PARAMETER (208)
CT CAUSE This actual reference parameter is not type identical with the
formal reference parameter in a user-defined function or
procedure.
This actual value parameter is not assignment compatible with
the formal value parameter in a user-defined function or
procedure.
ACTION Check the types of the actual and formal parameters.
CAUSE This actual reference parameter to a standard function or
procedure is not type identical with the formal reference
parameter.
This actual value parameter to a standard function or procedure
is not assignment compatible with the required type.
ACTION Check the types of the actual parameter and the parameter
accepted by the predefined routine.
CAUSE This actual parameter is not intrinsic compatible with the
intrinsic parameter.
ACTION Check the types of the actual parameter and the intrinsic
parameter.
CAUSE The parameter of the standard SQR function is an integer
subrange type with a lower bound greater than the square root
of maxint, or an upper bound less than the negation of the
square root of maxint. In either case, an integer overflow is
possible at run time.
ACTION Do not call SQR.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
209 MESSAGE NO FURTHER CASE CONSTANT PARAMETERS ALLOWED TO NEW (209)
CT CAUSE The pointer parameter to NEW points to a record that has no
additional nested variant parts.
The pointer parameter to NEW points to a record that does not
have a variant part.
The pointer parameter to NEW points to a structure that is not
a record.
ACTION Check the record type definition for the correct variant record
or remove the extra variant labels from the call.
---------------------------------------------------------------------------------------
210 MESSAGE NO FURTHER CASE CONSTANT PARAMETERS ALLOWED TO DISPOSE (210)
CT CAUSE The pointer parameter to DISPOSE points to a record that has no
additional nested variant parts.
The pointer parameter to DISPOSE points to a record that does
not have a variant part.
The pointer parameter to DISPOSE points to a structure that is
not a record.
ACTION Check the record type definition for the correct variant or
remove the extra variant labels from the call.
---------------------------------------------------------------------------------------
211 MESSAGE NO FURTHER PARAMETERS ALLOWED TO MARK (211)
CT CAUSE More than one pointer parameter in a call to MARK.
ACTION Remove the extra parameter.
---------------------------------------------------------------------------------------
212 MESSAGE NO FURTHER PARAMETERS ALLOWED TO RELEASE (212)
CT CAUSE More than one pointer parameter in a call to RELEASE.
ACTION Remove the extra parameter.
---------------------------------------------------------------------------------------
213 MESSAGE VALUE PARAMETER MAY NOT CONTAIN FILE COMPONENT (213)
CT CAUSE This value formal parameter is a file or a structured type with
a file type component. This is equivalent to assigning to a
file.
ACTION Remove the file component from the source code.
---------------------------------------------------------------------------------------
214 MESSAGE FUNCTION TYPE MAY NOT CONTAIN FILE COMPONENT (214)
CT CAUSE This function return type is a file or a structured type that
contains a file type component. This is equivalent to
assigning to a file.
ACTION Remove the file component from the source code.
---------------------------------------------------------------------------------------
215 MESSAGE COMPILER LEVEL WRONG--PROBABLY UNMATCHED "END" (215)
CT CAUSE This occurrence of END cannot match a BEGIN because all
compound statements have been terminated. The compiler
disregards the extraneous END.
ACTION Ensure all BEGINs and ENDs match along with ENDs for CASEs.
Make sure a BEGIN has not been commented out or fix any syntax
errors.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
216 MESSAGE BAD CONSTANT PARAMETER (216)
CT CAUSE This string constant parameter to BINARY, OCTAL, or HEX either
contains an invalid character or represents a value outside the
range minint..maxint.
ACTION Fix the character construct.
CAUSE This parameter to SUCC is a constant value equal to the maximum
value of an ordinal type.
This parameter to PRED is a constant value equal to the minimum
value of an ordinal type.
ACTION Fix the constant value.
---------------------------------------------------------------------------------------
217 MESSAGE PROCEDURE OR FUNCTION NOT IN INTRINSIC FILE (217)
CT CAUSE An incorrect intrinsic file was specified prior to the
declaration of the procedure or function.
ACTION Check the name of the SYSINTR file.
CAUSE The INTRINSIC name differs slightly from the procedure or
function name declared INTRINSIC.
ACTION Either use the ALIAS option or correct the spelling of the
ALIAS parameter.
CAUSE The procedure has never been put into the intrinsic file.
ACTION Either check the spelling or list the intrinsic file (or
rebuild the intrinsic file if it is not the standard intrinsic
file.)
---------------------------------------------------------------------------------------
218 MESSAGE INTRINSIC FILE NOT CHECKED (218)
CT CAUSE Due to a prior error, the intrinsic file was never opened.
Thus, no attempt was made to look up this procedure or
function.
ACTION Fix the previous error and try again.
---------------------------------------------------------------------------------------
219 MESSAGE "STRING" IS NOT ALLOWED AS A VALUE PARAMETER (219)
CT CAUSE A string formal value parameter must have a specified maximum
length.
ACTION Make the declaration a VAR parameter or make the type a
specific string type.
---------------------------------------------------------------------------------------
220 MESSAGE FUNCTION "! " NOT ASSIGNED TO (220)
CT CAUSE A function of a simple type has no assignment to the result in
the function body.
A function of a structured type has no assignment to any
component of the result in the function body.
ACTION Make an assignment to the function result.
---------------------------------------------------------------------------------------
221 MESSAGE DECLARED FUNCTION TYPE DOES NOT MATCH INTRINSIC TYPE (221)
CT CAUSE The HP Pascal type of the return of a function declared
INTRINSIC does not match the type of the value returned by the
intrinsic.
ACTION Change the type so it matches the value of the intrinsic type.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
222 MESSAGE VARIABLE PARAMETER REQUIRED HERE (222)
CT CAUSE An expression appears as an actual reference parameter instead
of a variable.
A constant appears as an actual reference parameter instead of
a variable.
A component of a structured constant appears as an actual
reference parameter instead of a variable.
ACTION Check the parameter; it must be a variable and not an
expression or constant.
---------------------------------------------------------------------------------------
223 MESSAGE ILLEGAL PARAMETER FORM (223)
CT CAUSE The integer parameter to a string procedure/function is not
compatible with a 32 bit integer.
The actual parameter is a procedure or function identifier, but
the corresponding formal parameter is not a procedure or
function heading.
The parameters of the actual procedural or functional parameter
are not congruent with the parameters of the formal procedural
or functional parameter.
The parameter of a call to WADDRESS or SIZEOF is a component of
a packed structure.
The parameter of a call to BADDRESS is a component of a packed
structure other than a PAC.
Either the third parameter of a call to ASSERT is not a
procedure identifier or the parameter of such a procedure is
not an integer value parameter.
ACTION Check the types of the actual and formal parameters.
---------------------------------------------------------------------------------------
224 MESSAGE SYSTEM ADDRESSING LIMIT EXCEEDED (224)
CT CAUSE The storage limit for variables at run time is exceeded.
ACTION Reduce the number of variables or make the structured
variables, such as arrays or strings, smaller.
---------------------------------------------------------------------------------------
225 MESSAGE INCONSISTENT ALIAS IN FORWARD PROCEDURE OR FUNCTION (225)
CT CAUSE The ALIAS in the definition differs from the ALIAS in the
FORWARD declaration of a procedure or function.
ACTION Use the same ALIAS in both the declarations.
---------------------------------------------------------------------------------------
226 MESSAGE INCONSISTENT OPTIONS IN FORWARD PROCEDURE OR FUNCTION (226)
CT CAUSE The routine options specified in the definition differs from
the one in the FORWARD declaration of the procedure or
function.
ACTION Use the same routine options in both declarations.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
227 MESSAGE INCONSISTENT COMPILER OPTIONS IN FORWARD PROCEDURE OR FUNCTION
(227)
CT CAUSE The compiler options specified in the definition differ from
the one in the FORWARD declaration of the procedure or
function.
ACTION Use the same compiler options in both declarations.
---------------------------------------------------------------------------------------
228 MESSAGE VARIABLE OR EXPRESSION NOT WITHIN STRING LIMITS (228)
CT CAUSE The bounds of a subrange variable used as a string index do not
overlap the bounds of the string type.
ACTION Use a variable of the proper type.
CAUSE The constant expression used as a string index lies outside the
bounds of the string type.
ACTION Use a constant expression within the string bounds.
---------------------------------------------------------------------------------------
229 MESSAGE INCONGRUENT FORMAL PARAMETER SECTIONS (229)
CAUSE The formal parameter sections of the actual routine being
passed as a parameter are not congruent with the formal
parameter sections of the procedural or functional parameter of
the called routine.
ACTION Alter one of the formal parameter sections so that it is
congruent with the other.
Raise the STANDARD_LEVEL to HP_PASCAL.
---------------------------------------------------------------------------------------
230 MESSAGE INVALID CONTROL VARIABLE IN FOR STATEMENT (230)
CT CAUSE The control variable of the FOR loop is a record field.
The control variable of the FOR loop is defined in a scope
containing the current scope.
The control variable of the FOR loop is a formal parameter of a
procedure or function containing the FOR statement.
The identifier used as the control variable of the FOR is not a
variable.
ACTION Use a local ordinal variable for the loop control variable.
---------------------------------------------------------------------------------------
231 MESSAGE CONTROL VARIABLE NOT AN ORDINAL TYPE (231)
CT CAUSE The control variable of the FOR loop is not an ordinal type.
ACTION Use a local ordinal variable for the loop control variable.
---------------------------------------------------------------------------------------
232 MESSAGE EXPRESSION NOT COMPATIBLE WITH CONTROL VARIABLE (232)
CT CAUSE The expressions for the initial and final values are not type
compatible with the control variable of a FOR loop.
ACTION Check expressions and make sure the types are compatible.
---------------------------------------------------------------------------------------
233 MESSAGE INITIAL AND FINAL EXPRESSIONS NOT COMPATIBLE (233)
CT CAUSE The types of the expressions for the initial and final values
of the FOR loop are not type compatible.
ACTION Change the types of the initial and final value expressions or
of the loop control variable as appropriate.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
240 MESSAGE MULTIPLE MODULE IMPLEMENTATIONS NOT PERMITTED (240)
CT CAUSE Only one MODULE is permitted for each module.
ACTION Remove duplicate MODULE.
---------------------------------------------------------------------------------------
241 MESSAGE MISSING EXPORT SECTION FOR THIS MODULE (241)
CT CAUSE Every module must have at least one EXPORT.
ACTION Declare or define at least one 'object' in the EXPORT section.
---------------------------------------------------------------------------------------
242 MESSAGE INVALID IMPORT MODULE IDENTIFIER (242)
CT CAUSE The given identifier is not defined.
The given identifier is not the name of a module in the current
$SEARCH$ list.
ACTION Check the name of the IMPORT module identifier. If the PASLIB
file in which the module is defined is not in the current
search list, add the file to it.
---------------------------------------------------------------------------------------
243 MESSAGE NOT AN IMPORTED MODULE (243)
CT CAUSE The identifier is not the name of an import module or the
module currently being defined
ACTION If the name is misspelled, correct the spelling. Otherwise,
import the module in question.
---------------------------------------------------------------------------------------
250 MESSAGE DUPLICATE CASE LABEL (250)
CT CAUSE The CASE label is the same as a CASE label that appeared
previously in the same construct.
The CASE label is contained in a previous CASE label subrange
in the same construct.
The CASE label subrange contains at least one CASE label that
appeared previously in the same construct.
ACTION Remove the duplicate label from the code.
---------------------------------------------------------------------------------------
251 MESSAGE CASE LABEL OF INCORRECT TYPE (251)
CT CAUSE The type of the CASE label is not the same as the type of the
tag or the select expression.
ACTION Change the label or selecting expression as appropriate.
---------------------------------------------------------------------------------------
252 MESSAGE CASE LABEL TYPE NOT SAME AS PREVIOUS CASE LABEL (252)
CT CAUSE There was a detected error in the tag type or select
expression, so the CASE labels are checked against each other.
The type of the current CASE label does not match the type of
previous CASE labels.
ACTION Make sure that all case labels in a CASE statement are of the
same type.
---------------------------------------------------------------------------------------
270 MESSAGE INVALID LABEL - MUST BE AN INTEGER BETWEEN 0 AND 9999 (270)
CT CAUSE This label is not an integer.
A colon ( : ) appears or was inserted by the compiler where
no label was desired.
ACTION Check to ensure that the label is an integer between 0 and
9999.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
271 MESSAGE LABEL HAS NOT BEEN DECLARED (271)
CT CAUSE This label marks a statement, but never appeared in a LABEL
declaration for this block.
ACTION Declare the label.
---------------------------------------------------------------------------------------
272 MESSAGE LABEL DECLARED MORE THAN ONCE (272)
CT CAUSE This label already appeared in this LABEL section or in a LABEL
section in an enclosing scope.
ACTION Delete the duplicate label declaration.
---------------------------------------------------------------------------------------
273 MESSAGE SAME LABEL NOT ALLOWED ON MORE THAN ONE STATEMENT (273)
CT CAUSE This label has already marked a statement.
ACTION Remove/correct the duplicate definition.
---------------------------------------------------------------------------------------
274 MESSAGE LABEL `!` NOT USED (274)
CAUSE The label is referenced in a GOTO statement, but is not used to
mark a statement.
ACTION Mark a target statement with the label.
---------------------------------------------------------------------------------------
275 MESSAGE LABEL REFERENCED BY GOTO OUTSIDE STRUCTURED STATEMENT (275)
CT CAUSE This label appears in a component statement of a structured
statement and was previously referenced by a GOTO statement:
(a) preceding the structured statement.
(b) in a preceding component statement of the same structured
statement.
(c) contained in an inner procedure or function.
ACTION Remove either the label or the GOTO from the code.
---------------------------------------------------------------------------------------
276 MESSAGE GOTO REFERENCES LABEL INSIDE STRUCTURED STATEMENT (276)
CT CAUSE The label referenced in a GOTO statement appears in a component
statement of a structured statement and the GOTO statement
appears:
(a) after the structured statement.
(b) in a later component statement of the same structured
statement.
ACTION Remove either the label or the GOTO from the code.
---------------------------------------------------------------------------------------
293 MESSAGE TSAM INTRINSIC ERROR "! " (293)
CT CAUSE An error was encountered when reading a TSAM (toolset format)
file.
ACTION The error number replacing "! " refers to Toolset error
messages if 900 or above. Look them up in a Toolset manual.
Please report other numbers to your local HP representative.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
294 MESSAGE $ INCLUDE NOT ALLOWED HERE WHEN SYMBOLIC DEBUG IS ENABLED (294)
CT CAUSE $INCLUDE of a file in executable code must be on a Pascal
statement boundary if symbolic debug is enabled.
---------------------------------------------------------------------------------------
370 MESSAGE IMPORTED MODULE `!` WAS NOT REFERENCED (370)
N CAUSE The specified module was imported and no references to it were
found.
ACTION Either remove the module from the IMPORT statement or cause the
module to be referenced.
---------------------------------------------------------------------------------------
371 MESSAGE USE OF AN INLINED ROUTINE (371)
N CAUSE An inlined routine has been expanded in the current statement.
ACTION No action required. This message is for your information only.
---------------------------------------------------------------------------------------
373 MESSAGE ASSUME "! " IS VALID, USE $ASSUME$ (373)
N CAUSE The given optimizer assumption is valid, and should be used in
the routine's declaration to get the most out of optimization.
ACTION Use the $ASSUME$ compiler option.
---------------------------------------------------------------------------------------
374 MESSAGE BIT32 Type CONVERTED TO LONG INTEGER (374)
N CAUSE Using bit32 requires that it be converted to a long integer.
ACTION Use type coercion to obtain a signed or unsigned 32 bit
operation.
---------------------------------------------------------------------------------------
377 MESSAGE CODE GENERATED TO VERIFY CORRECT POINTER ALIGNMENT (377)
N CAUSE Checking code will be generated to ensure that the pointer
being coerced has an alignment that allows it to be used as the
coerced pointer type.
ACTION Use $RANGE OFF$ to eliminate the extra code.
---------------------------------------------------------------------------------------
378 MESSAGE WHICH IS A COMPONENT OF ' ! '(378)
N CAUSE This message accompanies message #379.
ACTION See message 379.
---------------------------------------------------------------------------------------
379 MESSAGE THE FIELD / AN ELEMENT OF ' ! ', CROSSES A WORD BOUNDARY (379)
N CAUSE Accesses of ordinal data items split across word boundaries are
relatively inefficient.
ACTION Use $ALIGNMENT$ to start ordinal data items on word boundaries.
---------------------------------------------------------------------------------------
380 MESSAGE TYPE COERCION MAY ACCESS INVALID DATA (380)
N CAUSE Informational message - the referenced type-coercion may cause
uninitialized/invalid data to become accessible.
ACTION Ensure that the data referenced is valid.
---------------------------------------------------------------------------------------
381 MESSAGE MACHINE DEPENDENT REPRESENTATION USED IS NOT CONSISTENT WITH
PACKING(381)
N CAUSE A real type, such as a real or longreal, is used with
$HP3000_16$.
ACTION Don't mix $HP3000_16$ and $HP3000_32$ modes in data
declarations.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
382 MESSAGE SIZE OF MACHINE DEPENDENT TYPE IS NOT CONSISTENT WITH PACKING
(382)
N CAUSE A machine dependent type such as a pointer, string, or file, is
used with $HP3000_16$.
ACTION Don't mix $HP3000_16$ and $HP3000_32$ modes in data
declarations.
---------------------------------------------------------------------------------------
383 MESSAGE FEATURE MAY NOT BE SUPPORTED FOR OTHER TARGET MACHINES (383)
N CAUSE Informational message - the referenced feature may not be
supported on other machines.
ACTION No action is required.
---------------------------------------------------------------------------------------
384 MESSAGE MOVE PROCEDURE IN STATEMENT "! " USES A SIMULATED FOR LOOP
(384)
N CAUSE The MOVE predefined procedure is implemented with a FOR loop to
move the elements.
ACTION No action is required.
---------------------------------------------------------------------------------------
385 MESSAGE POSSIBLE NON-ALIGNED OVERLAPPING SOURCE/TARGET IN STATEMENT !
(385)
N CAUSE The source and target of the MOVE predefined procedure may
overlap and generate scrambled results.
ACTION You may need to use MOVE_R_TO_L or MOVE_L_TO_R.
---------------------------------------------------------------------------------------
400 MESSAGE INVALID FILENAME (400)
CT CAUSE The filename given in the INCLUDE, SYSINTR, or SPLINTR option
is not a legal filename.
ACTION Correct the filename to conform to the format required by the
operating system.
---------------------------------------------------------------------------------------
401 MESSAGE ILLEGAL NAME IN ALIAS OR SUBPROGRAM OPTION (401)
CT CAUSE The procedure or function name in an ALIAS option is not a
valid identifier.
The procedure or function name in a SUBPROGRAM option is not a
valid HP Pascal identifier.
ACTION Make sure the name is a valid HP Pascal identifier.
---------------------------------------------------------------------------------------
402 MESSAGE NOT A LEGAL LOCALITY NAME (402)
CT CAUSE The name for a locality is illegal.
ACTION Check the name and make sure it is legal.
---------------------------------------------------------------------------------------
403 MESSAGE $IF$ EXPRESSION CAN NOT BE EVALUATED (403)
CT CAUSE The expression in an $IF$ has a syntax error in it.
ACTION Check the source code and fix the syntax error.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
404 MESSAGE UNMATCHED $ENDIF$ FOUND (404)
CT CAUSE An $ENDIF$ compiler option was found without a preceding $IF$
option. This may happen if either the compiler rejects an $IF$
because it was out of place, or the $IF$ is not in the code.
ACTION Check for a missing or commented $IF$.
---------------------------------------------------------------------------------------
405 MESSAGE A BOOLEAN EXPRESSION IS REQUIRED INSIDE STRING (405)
CT CAUSE A blank string was found as part of an $IF$.
ACTION Remove the $IF$ or add a string.
---------------------------------------------------------------------------------------
406 MESSAGE EXPECTED TRUE/FALSE AFTER "= " (406)
CT CAUSE Misspelled true/false after "= " in $SET$
ACTION Correct spelling.
CAUSE Missing true/false after "= " in $SET$
ACTION Add TRUE or FALSE.
---------------------------------------------------------------------------------------
408 MESSAGE UNMATCHED $ENDIF$ OR $ELSE$ FOUND (408)
CT CAUSE $ENDIF$/$ELSE$ compiler option was found without a preceding
$IF$ option. This may happen either if the compiler rejects an
$IF$ because it was out of place, or if the $IF$ is not in the
code.
ACTION Check for a missing or misplaced $IF$.
---------------------------------------------------------------------------------------
409 MESSAGE EXCEEDED MAXIMUM NESTING LEVEL FOR $IF$ (409)
CT CAUSE The nesting of $IF$ exceeded the maximum allowable nesting
level.
ACTION Remove the offending $IF$ from the code.
---------------------------------------------------------------------------------------
410 MESSAGE ILLEGAL IDENTIFIER IN $SET$ or $IF$ (410)
CT CAUSE An identifier is misspelled.
Expected an identifier and one was not found.
ACTION Provide a legal identifier or correct the spelling of the
identifier.
---------------------------------------------------------------------------------------
411 MESSAGE $PUSH$ NESTING TOO DEEP, OPTIONS NOT SAVED (411)
CT CAUSE Too many $PUSH$ compiler options encountered.
ACTION Remove the offending $PUSH$ option.
---------------------------------------------------------------------------------------
412 MESSAGE NOTHING TO $POP$, OPTIONS NOT CHANGED (412)
CT CAUSE Too many $POP$ compiler options for the number of preceding
$PUSH$ options.
ACTION Remove $POP$ options so that those remaining have matching
$PUSH$ options.
---------------------------------------------------------------------------------------
413 MESSAGE INVALID INTRINSIC FILE (413)
CT CAUSE The file specified in the intrinsic option is not a valid
SYSINTR file.
ACTION Check the name and make sure the file is an intrinsic file and
has not been corrupted.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
414 MESSAGE NLS NOT INSTALLED OR SYSTEM VARIABLE NOT SET (414)
CT CAUSE NLS (Native Language Support) is not installed or the JCW
'GETUSERLANG" is not set (MPE/iX) or the environment variable
'LANG' is not set (HP-UX).
ACTION Determine which of the above applies and correct the situation.
---------------------------------------------------------------------------------------
415 MESSAGE $INCLUDE FILENAME IS NULL (415)
CT CAUSE The file specified in the include option is empty.
ACTION Place a valid file name in the quotes.
---------------------------------------------------------------------------------------
425 MESSAGE COMPILER ERROR "! " COMPILE TERMINATED (425)
CT CAUSE (1..999) A run-time error was detected by the run-time support
library during compiler execution.
(1000..1031) A run-time error was detected in an arithmetic
operation during compiler execution.
(2000..2999) A run-time error was detected by a system
intrinsic during compiler execution.
ACTION Check that there is no previous syntax error. If there is one,
fix the error and recompile. Otherwise, report this as a bug.
(3000..3999) A run-time code trap (an addressing exception or
an illegal instruction, for example) occurred during compiler
execution.
(5000..5999) A user of internal code generation error.
(6000..6999) An optimizer error.
(7000..7999) A user or internal code generation error.
---------------------------------------------------------------------------------------
426 MESSAGE SYSTEM RESOURCE EXHAUSTED "! " COMPILE TERMINATED (426)
CT CAUSE The compiler ran out of space in the heap.
ACTION Break the code into smaller compilation units.
CAUSE The compiler ran out of space in one of its data areas or the
compiler could not acquire one of its data areas (especially if
the parameter is 2).
ACTION Reduce the size or the number of structured constants or number
of identifiers or increase the size of data areas. In the
following examples, the parameter is the number of pages:
On MPE/iX:
SETJCW PASXDATA 200
On HP-UX:
export PASXDATA=200 for ksh
PASXDATA=200; export PASXDATA for sh or ksh
setenv PASXDATA 200 for csh
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
461 MESSAGE PARSER STACK OVERFLOW - TOO MANY NESTED CONSTRUCTS (461)
CT CAUSE An internal compiler limit on nested structures has been
reached. A common cause is a long list of ELSE-IFs.
ACTION Break up a nested structure. Use a balanced IF-THEN-ELSE
structure.
---------------------------------------------------------------------------------------
500 MESSAGE OPTION NOT YET IMPLEMENTED (500)
W CAUSE This compiler option is not yet implemented.
ACTION Remove any references to this compiler option from the source
code.
---------------------------------------------------------------------------------------
501 MESSAGE UNRECOGNIZED COMPILER OPTION (501)
W CAUSE A compiler option with this name is not recognized.
ACTION Check the spelling of this option.
---------------------------------------------------------------------------------------
502 MESSAGE THIS OPTION IS NOT ALLOWED HERE (502)
W CAUSE The option appears in an illegal location in the source code.
For example, the GLOBAL option appears anywhere except before
the PROGRAM heading.
ACTION Remove the option from an illegal location in the source code
and place it in a legal location.
---------------------------------------------------------------------------------------
503 MESSAGE TEXT AFTER INCLUDE OR SKIP TEXT IGNORED (503)
W CAUSE Anything on the source line after INCLUDE was ignored.
Anything on the source line after a $SKIP_TEXT ON$ is treated
as a comment. Anything on the source line after an $IF$ that
evaluates to FALSE is ignored.
ACTION Remove the extra text.
---------------------------------------------------------------------------------------
504 MESSAGE INTEGER OUT OF RANGE, VALUE NOT CHANGED (504)
W CAUSE LINES requires an integer greater than 20
WIDTH requires an integer in the range 10..132.
$CHECK_ACTUAL_PARM$ and $CHECK_FORMAL_PARM$ require an integer
in the range 0..3.
ACTION Correct the option argument; check the compiler option syntax.
---------------------------------------------------------------------------------------
505 MESSAGE STRING PARAMETER IS REQUIRED, OPTION IGNORED (505)
W CAUSE This option requires information in a string literal parameter.
ACTION Check the option argument; check the compiler option syntax.
---------------------------------------------------------------------------------------
506 MESSAGE I/O FAILED ON FILE !, ! (506)
CAUSE I/O on a file failed. The compiler feature that uses that file
has been disabled for the remainder of the compilation.
ACTION Check the named file for invalid file equations, links, size
restrictions, and locking by other processes. Also check for
disk space.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
507 MESSAGE BOTH $GLOBAL$ AND $EXTERNAL$ NOT ALLOWED (507)
W CAUSE The option $GLOBAL$ occurred after the option $EXTERNAL$ was
specified. Since only one is allowed, $GLOBAL$ was ignored.
The option $EXTERNAL$ occurred after the option $GLOBAL$ was
specified. Since only one is allowed, $EXTERNAL$ was ignored.
ACTION Remove $GLOBAL$ or $EXTERNAL$, whichever is appropriate.
---------------------------------------------------------------------------------------
508 MESSAGE A "$ " IS REQUIRED HERE - ONE INSERTED (508)
W CAUSE Compiler option doesn't end with a $ on the same line.
ACTION Add a "$ " to the code.
---------------------------------------------------------------------------------------
509 MESSAGE EXPRESSION WILL CAUSE A RUN-TIME OVERFLOW (509)
W CAUSE The result of an expression will exceed maxint at run time.
This is detected for:
(a) +, -, * when the types of the operands are such that the
expression overflows. For example:
VAR
A: maxint-10..maxint;
Then the expression A + A would never be less than 2 * maxint -
10, which is greater than maxint.
(b) -minint
(c) the addition, subtraction, or multiplication of two
constants resulting in an overflow.
ACTION Correct the expression.
---------------------------------------------------------------------------------------
510 MESSAGE EXPRESSION WILL CAUSE A RUN-TIME UNDERFLOW (510)
W CAUSE The result of an expression will be less than minint at run
time. This is detected for:
(a) +, -, * when the types of the operands are such that the
expression underflows. For example:
VAR
A: maxint - 10..maxint;
B: minint..minint + 10
Then the expression B - A would be less than minint + 10 -
maxint, which is less than minint.
(b) the addition, subtraction, or multiplication of two
constants resulting in an underflow.
ACTION Correct the expression.
---------------------------------------------------------------------------------------
511 MESSAGE MOD DIVISOR WILL CAUSE A RUN-TIME ERROR (511)
W CAUSE In an expression A MOD B, B will be <= 0 at run time.
In a constant expression A MOD B, B is <= 0.
ACTION Correct the expression.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
512 MESSAGE RUN TIME DIVISION BY ZERO (512)
W CAUSE In an expression A DIV B, B = 0.
In a constant expression A DIV B, B = 0.
ACTION Correct the expression.
---------------------------------------------------------------------------------------
513 MESSAGE EMPTY INCLUDE FILE (513)
W CAUSE The INCLUDE file had no text in it.
ACTION Verify that the filename is correct.
---------------------------------------------------------------------------------------
514 MESSAGE $ NOT ALLOWED IN INFO PARAMETER (514)
W CAUSE The INFO parameter of a :PASXL, :PASXLLK, or :PASXLGO command
is interpreted as a compiler option with the $ assumed as the
leading and trailing character. The $ cannot appear in the
INFO string itself.
ACTION Do not supply '$' in the INFO string.
---------------------------------------------------------------------------------------
515 MESSAGE NO DISC SPACE FOR XREF (515)
W CAUSE A file error occurred trying to open the file needed to do the
cross reference. This could be any file error, but OUT OF DISK
SPACE is the most likely. A temporary file with the name
PASXRFdd, where d is a digit, is another possible cause.
ACTION Check for a duplicate file name and for enough file disk space.
---------------------------------------------------------------------------------------
516 MESSAGE NO VARIANT FOR TAG VALUE (516)
W CAUSE A NEW was called specifying a tag constant that did not appear
in the case list in the variant part. The maximum space for
the record is allocated.
ACTION Remove the variant identifier from the source code or correct
its spelling.
---------------------------------------------------------------------------------------
519 MESSAGE BOOLEAN EXPRESSION FOLDED TO '!' (519)
W CAUSE The compiler has folded an expression with IN, AND, or OR and
constant operands or, in the case of IN, with a left operand
that is a constant appearing in the set list.
The compiler has folded an expression with =, <>, <=, >=, or >
and operands that are non-set constants.
With $PARTIAL_EVAL ON$, the compiler has folded an expression
with OR when TRUE is an operand, or an expression with AND when
FALSE is an operand.
ACTION Check the operands to ensure that they are correct.
---------------------------------------------------------------------------------------
520 MESSAGE NON-OVERLAPPING TYPES - EXPRESSION FOLDED (520)
W CAUSE Two sets with ranges that do not overlap were intersected. The
compiler folded the expression to the empty set.
An arithmetic comparison was done with operands of types with
ranges that do not overlap. The compiler folded the
expression. For example, if A: 0..3 and B: 5..7, then A = B is
folded to false.
ACTION Check the operands to ensure that they are correct.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
521 MESSAGE BODY OF FOR LOOP WILL NEVER EXECUTE (521)
W CAUSE Values of the initial and final expressions will prevent the
body of the FOR loop from ever executing.
Non-overlapping subranges for the types of the initial and
final expressions prevent the body of the FOR loop from ever
executing.
ACTION Check the values and types for the initial and final
expressions.
---------------------------------------------------------------------------------------
522 MESSAGE CASE LABEL NOT WITHIN TAG OR SELECT EXPRESSION RANGE (522)
W CAUSE The CASE label value or subrange is not within the range of the
tag type and can never be specified in a call to NEW or
assigned to the tag field.
The CASE label value or subrange is not within the range of the
select expression and can never be selected.
ACTION Check the possible values of the CASE selection expression and
the values of the CASE labels.
---------------------------------------------------------------------------------------
523 MESSAGE INTEGER CONSTANT IS REQUIRED - OPTION IGNORED (523)
W CAUSE This compiler option requires an integer parameter; such as
WIDTH. The compiler has ignored this option.
ACTION Check the syntax and insert an integer where necessary.
---------------------------------------------------------------------------------------
524 MESSAGE SUBPROGRAM "! " SPECIFIED, BUT NOT FOUND (524)
W CAUSE A procedure or function name specified in the SUBPROGRAM option
was not found in the source.
ACTION Check the spelling of the procedure or function.
---------------------------------------------------------------------------------------
525 MESSAGE ANY EXTERNAL GOTO TO THIS LABEL IS AN ERROR (525)
W CAUSE This label marks a component statement of a structured
statement. This label cannot be referenced by a GOTO statement
contained in an external procedure or function, but that error
will not be detected until the program is prepared or executed.
ACTION Make sure no nonlocal GOTOs branch to this label.
---------------------------------------------------------------------------------------
526 MESSAGE EXPRESSION FOLDED TO THE EMPTY SET (526)
W CAUSE The compiler has determined that a set expression results in an
empty set and folded that expression to empty. This warning
appears in case the user expected side effects or made some
kind of error that caused the folding. Folding occurs when an
intersection is performed with the empty set, the empty set
occurs on the left side of the set difference operator, or two
empty sets appear in a set operation.
ACTION Check to see if expression should fold to the empty set.
---------------------------------------------------------------------------------------
527 MESSAGE 'ON' OR 'OFF' IS REQUIRED HERE (527)
W CAUSE The word ON or OFF is required after this compiler option name;
for example, $LIST$.
ACTION Correct the option argument and the compiler option syntax.
---------------------------------------------------------------------------------------