HP 3000 Manuals HP 3000 Manuals
Messages 528-814
---------------------------------------------------------------------------------------
528 MESSAGE PREVIOUS VERSION OF '!' INACTIVATED (528)
W CAUSE A procedure or function by the same name already exists in the
USL file and has been inactivated.
CAUSE If PRIVATE_PROC was ON, then two level 1 procedure or function
names are not unique within the first 15 characters, or a copy
from a previous compilation is being replaced.
CAUSE If PRIVATE_PROC was OFF, then either duplicate non-level 1
procedure or function names exist (they are not unique within
15 characters) or duplicate procedure or function names have
been introduced due to separate compilation of procedures or
functions wi th names which are identical within the first 15
characters.
---------------------------------------------------------------------------------------
530 MESSAGE EXPRESSION WILL CAUSE A RUN-TIME SET RANGE ERROR (530)
W CAUSE Evaluation of a set construction in which an element of the set
list will necessarily fall outside the bounds of the set
construction will cause this error.
ACTION Check the source code and fix the expression.
---------------------------------------------------------------------------------------
532 MESSAGE THE SPECIFIED WORKSPACE FOR TOOLSET IS INVALID (532)
W CAUSE The file is not a valid TSAM root file or the file cannot be
opened.
ACTION Determine why the file is invalid.
---------------------------------------------------------------------------------------
533 MESSAGE BAD FONT OPTION GIVEN (533)
W CAUSE The call to FDeviceControl returned an error condition.
ACTION Ensure that the font number specified exists in the font file
specified in the file equation for PASLIST.
---------------------------------------------------------------------------------------
534 MESSAGE CONTROL VARIABLE HAS BEEN ASSIGNED TO NON-LOCALLY (534)
W CAUSE The control variable may be modified by a non-local reference
from a routine invoked in the body of the FOR loop.
ACTION Make sure that there are no non-local references to the control
variable.
---------------------------------------------------------------------------------------
535 MESSAGE "! " ACCESSED, BUT NOT INITIALIZED (535)
W 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, 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 Make sure the variable is initialized.
---------------------------------------------------------------------------------------
536 MESSAGE LABEL "! " DECLARED, BUT NOT USED TO MARK ANY STATEMENT (536)
W CAUSE The label appears in a LABEL declaration, but is not used to
mark any statement.
ACTION Remove label from LABEL declaration.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
537 MESSAGE THIS PREVIOUSLY UNIMPLEMENTED FEATURE IS NOW IMPLEMENTED (537)
W CAUSE New functionality has been added of which the user should be
aware.
ACTION None.
---------------------------------------------------------------------------------------
538 MESSAGE THIS FEATURE REQUIRES $OS "! " (538)
W CAUSE The current $OS is not one that allows the feature.
ACTION Use the $OS specified in the message or remove the feature.
---------------------------------------------------------------------------------------
539 MESSAGE THIS FEATURE REQUIRES $ STANDARD_LEVEL "! " (539)
W CAUSE The current standard_level is lower than that required for this
feature.
ACTION Use the standard_level in the message or remove the feature.
---------------------------------------------------------------------------------------
540 MESSAGE THIS FEATURE REQUIRES $STANDARD_LEVEL$ "! " AND
$OS "! " (540)
W CAUSE The current standard_level is lower than that required for this
feature and the $OS specified is wrong.
ACTION Use the standard_level and $OS specified in the message or
remove the feature.
---------------------------------------------------------------------------------------
541 MESSAGE FURTHER MESSAGES SUPPRESSED FOR THIS LINE (541)
W CAUSE Only 5 messages will be printed for any single input source
line. If more than 5 messages are issued, then this will be
the sixth and last message.
ACTION Remove the causes of the first 5 messages on this line, so that
the next message can be printed.
---------------------------------------------------------------------------------------
549 MESSAGE MISSING SEPARATOR, TEXT IGNORED UNTIL NEXT SEPARATOR (549)
W CAUSE When two or more compiler options are on the same line, the
options must be separated by a semicolon or comma.
ACTION Add a separator if there are two or more compiler options.
---------------------------------------------------------------------------------------
550 MESSAGE LOWER BOUND GREATER THAN UPPER, FOLDED TO EMPTY SUBRANGE (550)
W CAUSE Assigning or comparing a constant subrange with the lower bound
greater than the upper bound results in an assignment or
comparison of an empty set.
ACTION Correct the bounds.
---------------------------------------------------------------------------------------
551 MESSAGE OBSOLETE !, USE '!' (551)
W CAUSE A feature supported by a previous release is now obsolete.
ACTION Change the source to use the recommended features and
recompile.
---------------------------------------------------------------------------------------
552 MESSAGE SYSTEMS LANGUAGE VARIABLE NOT SET (552)
W CAUSE JCW 'NLUSERLANG' or environment variable 'LANG' not set.
ACTION Set the system variable to the desired language (-LANG on
HP-UX, NLUSERLANG on MPE/iX.)
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
553 MESSAGE '!' and '!' ARE INCOMPATIBLE COMPILER OPTIONS (553)
W CAUSE These options are not compatible. The second was ignored.
ACTION Delete one of the options.
---------------------------------------------------------------------------------------
554 MESSAGE DUPLICATE $SET FOR '!'; ITS VALUE IS NOW '!' (554)
W CAUSE This identifier was previously set by a $SET (or, on HP-UX, a
-D on the command line). The value last seen takes effect.
ACTION Decide which value you want this identifier to have and remove
all other $SETs (or, on HP-UX, remove the -D option on the
command line if it is in error).
---------------------------------------------------------------------------------------
555 MESSAGE VOLATILE VARIABLE PASSED BY REFERENCE (555)
W CAUSE A variable declared as volatile was used as an actual parameter
in a routine call for which the formal parameter was a
reference parameter.
ACTION The compiler cannot guarantee that the parameter will be
properly updated, so you must ensure that it is.
---------------------------------------------------------------------------------------
556 MESSAGE DEFAULT_PARM VALUES DO NOT MATCH THOSE IN FORWARD DECLARATION
(556)
W CAUSE The values of constants for OPTION DEFAULT_PARMS do not match
the corresponding values declared in a previous FORWARD
declaration. The values used are those that were specified in
the FORWARD declaration.
ACTION Ensure that the values are the same or leave off the formal
parameter list from the routine heading when the routine is
defined.
---------------------------------------------------------------------------------------
557 MESSAGE PARAMETER TO PROCEDURE "NEW"MAY CAUSE A RUN-TIME ERROR (557)
W CAUSE The pointer argument to NEW is not aligned on a four-byte
boundary. If the type of a pointer was defined with the
ALIGNMENT compiler option and a component of a structured type
contains this pointer type, a variable declared with this
structured type may cause the pointer to be aligned improperly.
ACTION Create the variable so that the component used as an argument
to NEW is four-byte aligned. This can be done by removing the
ALIGNMENT option from the type declaration for the pointer or
by rearranging the fields of the record containing the pointer.
---------------------------------------------------------------------------------------
558 MESSAGE FILES APPEAR IN THE VARIANT PART OF A RECORD (558)
W CAUSE Fields of a file type or a structure containing a file type
appear in the variant part of a record. When this variant
becomes inactive, all fields in that variant are undefined.
Furthermore, files corresponding to such fields are not
guaranteed to be closed when the variant becomes inactive.
ACTION Make sure that such files are closed before deactivating the
variant.
---------------------------------------------------------------------------------------
559 MESSAGE INVALID $SHLIB_VERSION DATE STRING (559)
W CAUSE The date string passed to the $SHLIB_VERSION compiler option is
invalid.
ACTION The date string should be in the form: month/year. The year
may be a 2 or 4 digit value. A month/year value representing a
date earlier than January 1990 is invalid.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
560 MESSAGE $HP_DESTINATION'ARCHITECTURE'$ IGNORED; FIRST SEEN TAKES EFFECT
(560)
W CAUSE The compiler encountered more than one
$HP_DESTINATION'ARCHITECTURE' option; only the first one seen
will take effect.
ACTION Remove extra $HP_DESTINATION'ARCHITECTURE'$ options from the
source file.
ACTION If you are specifying the +DA option to the pc command, remove
the compiler option $HP_DESTINATION'ARCHITECTURE'$ from your
source file.
---------------------------------------------------------------------------------------
561 MESSAGE $HP_DESTINATION'SCHEDULER'$ IGNORED; FIRST SEEN TAKES EFFECT
(561)
W CAUSE The compiler encountered more than one
$HP_DESTINATION'SCHEDULER' option; only the first one seen will
take effect.
ACTION Remove extra $HP_DESTINATION'SCHEDULER'$ options from the
source file.
ACTION If you are specifying the +DS option to the pc command, remove
the compiler option $HP_DESTINATION'SCHEDULER'$ from your
source file.
---------------------------------------------------------------------------------------
562 MESSAGE $OPTIMIZE 'BASIC_BLOCKS num'$: num was omitted; using zero.
(562)
W CAUSE You inadvertently omitted the number which specifies the
threshold of basic blocks in a procedure which you want
optimized at level 2. Zero was inserted by the compiler, which
effectively disables the basic blocks feature; every procedure
is optimized at level 2.
ACTION Specify the num in the $OPTIMIZE 'BASIC_BLOCKS num'$ directive.
ACTION On HP-UX, specify the num on the command-line with +Obbnum.
ACTION On HP-UX, specify 0 as num to guarantee the "old" -0 behavior
(that is, not ever dropping down to level 1 optimization).
---------------------------------------------------------------------------------------
568 MESSAGE '+' IS NOT ALLOWED HERE (568)
W CAUSE A '+' was specified as part of a $SEARCH compiler option, but
it did not precede all the file names in the search list.
ACTION Correct the compiler option.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
569 MESSAGE NO ASSEMBLY FILE FOUND. LIST_CODE NOT PERFORMED (569)
W CAUSE The compiler could not find the file with the assembly listing
(usually "???.s" on HP-UX or "PASASSM" on MPE/iX). On MPE/XL;,
this usually happens because the PASASSM file is too small to
hold the assembly output (the default size is 40,000 records).
Another possible reason is that you have hit some file system
limit like total file space or number of files.
ACTION If you have run against a system limit, get around it and
recompile.
On MPE/iX, if you can determine that you have not run afoul
of a system limit, try the following file equation:
FILE PASASSM;DISC=100000
Modify the parameter of the "DISC=" option according to how
big you think your compilation unit is.
---------------------------------------------------------------------------------------
570 MESSAGE PARAMETER TYPE NOT SUPPORTED BY EXTERNAL LANGUAGE (570)
W CAUSE An ANYVAR or READONLY parameter is used with an EXTERNAL C or
EXTERNAL FTN77 directive. These types of parameters are not
supported by these languages.
ACTION Remove parameter or change TYPE to VAR.
---------------------------------------------------------------------------------------
571 MESSAGE INCOMPATIBLE COMPILER OPTIONS PFA AND OPTIMIZE (571)
W CAUSE Both OPTIMIZE and PFA options are present. The options are
mutually exclusive.
ACTION (1) If PFA is desired, remove OPTIMIZE.
(2) If OPTIMIZE is desired, remove PFA.
---------------------------------------------------------------------------------------
572 MESSAGE INCOMPATIBLE COMPILER OPTIONS OPTIMIZE AND SYMDEBUG (572)
W CAUSE Both OPTIMIZE and SYMDEBUG 'XDB' options are present. The
options are mutually exclusive.
ACTION (1) If SYMDEBUG 'XDB' is desired, remove OPTIMIZE.
(2) If OPTIMIZE is desired, remove SYMDEBUG 'XDB'.
---------------------------------------------------------------------------------------
573 MESSAGE INCOMPATIBLE COMPILER OPTIONS SYMDEBUG AND OPTIMIZE (572)
W CAUSE Both OPTIMIZE and SYMDEBUG 'TOOLSET' options are present. The
options are mutually exclusive.
ACTION (1) If SYMDEBUG 'TOOLSET' is desired, remove OPTIMIZE.
(2) If OPTIMIZE is desired, remove SYMDEBUG 'TOOLSET'.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
575 MESSAGE VALUE OF ESCAPECODE IS QUESTIONABLE HERE (575)
W CAUSE The value returned by ESCAPECODE outside a RECOVER construct is
undefined.
ACTION Store off escape code into a local variable from inside the
RECOVER construct, and use the local variable outside it.
---------------------------------------------------------------------------------------
576 MESSAGE POINTER FIELD IN OTHER VARIANT NOW UNDEFINED (576)
W CAUSE An integer field overlaying a pointer field has been assigned
to making the pointer undefined.
ACTION None - informational message only.
---------------------------------------------------------------------------------------
577 MESSAGE ASSUME "! " IS NOT VALID, REMOVE $ASSUME$ (577)
W CAUSE A construct is used that invalidates the given assumption which
the compiler ignores.
ACTION Remove the $ASSUME$ option that is invalid.
---------------------------------------------------------------------------------------
582 MESSAGE $HP3000_32$ NOT RECOGNIZED, OPTION IGNORED (582)
W CAUSE $HP3000_32$ is not recognized because $HP30000_16$ has not been
set.
ACTION Remove $HP3000_32$
---------------------------------------------------------------------------------------
584 MESSAGE INVALID MODULE LIBRARY NAME SPECIFIED (584)
W CAUSE Specified a module library which cannot be opened by the
system.
ACTION Check the name of the module library.
---------------------------------------------------------------------------------------
586 MESSAGE INVALID ALIGNMENT VALUE, OPTION IGNORED (586)
W CAUSE The alignment specified was not one of 1, 2, 4, 8, 16, 32, 64,
or 2048 bytes.
ACTION Correct the alignment value.
---------------------------------------------------------------------------------------
587 MESSAGE UNSUPPORTED VARIABLE ALIGNMENT REQUESTED (587)
W CAUSE The type declaration specified an alignment value that is not
supported for static variables.
ACTION Correct the alignment value.
---------------------------------------------------------------------------------------
588 MESSAGE POSSIBLE USE OF UNINITIALIZED FIELD '!' OF '!' (588)
W CAUSE The field of the local variable mentioned in the message may be
uninitialized when used in this procedure or function.
ACTION Ensure that the field is initialized before use.
---------------------------------------------------------------------------------------
590 MESSAGE IDENTIFIER `!' OVERLOADED BY IMPORTED MODULE(S) (590)
W CAUSE An identifier with the same spelling is exported by an earlier
imported module.
ACTION Rename one of the identifiers. If you do not rename an
identifier, the identifier in the last imported module will be
used.
---------------------------------------------------------------------------------------
591 MESSAGE COUNT IS NEGATIVE; NO DATA WILL BE MOVED (591)
W CAUSE The move count parameter to a MOVE procedure will always be
negative, thus no data will be moved.
ACTION Make sure that the count is supposed to be negative.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
592 MESSAGE LONG TO SHORT POINTER CONVERSION EMITTED IN STATEMENT "! "
(592)
W CAUSE A 64 bit address was converted to a 32 bit address. Only
addresses that are in space registers 4 through 7 can be
converted without an error.
ACTION A run-time trap will occur if the address is not valid.
ACTION On MPE/iX, make sure short addresses in SR4 are not passed to
an executable library (XL). They may not trap until
dereferenced.
---------------------------------------------------------------------------------------
593 MESSAGE TYPE COERCION ALTERS NUMBER OF STORAGE UNITS (593)
W CAUSE Source and target types require a different number of storage
units; thus, code generated as a result of this type coercion
may not behave as expected.
ACTION Remove the type coercion expression or define the TYPE_COERCION
level to be 'NONCOMPATIBLE'.
---------------------------------------------------------------------------------------
594 MESSAGE IMPLEMENT MISSING FOR MODULE "! " (594)
W CAUSE No IMPLEMENT appeared in the given MODULE.
ACTION Supply an IMPLEMENT section.
---------------------------------------------------------------------------------------
595 MESSAGE EXPORT QUALIFICATIONS NOT IMPLEMENTED (595)
W CAUSE EXPORT qualifiers currently have no effect.
ACTION No action is required.
---------------------------------------------------------------------------------------
596 MESSAGE DUPLICATE IMPORTED MODULE (596)
W CAUSE <IDENT1> ! <IDENT2> is the same as <IDENT2>.
ACTION Rename one of the modules.
---------------------------------------------------------------------------------------
597 MESSAGE POSSIBLE USE OF UNINITIALIZED VARIABLE '!' (597)
W CAUSE The local variable mentioned in the message may be
uninitialized when used in this procedure or function.
ACTION Ensure that the variable is initialized before use.
---------------------------------------------------------------------------------------
598 MESSAGE RESULTS OF $GLOBAL/$RLFILE/$SUBPROGRAM IS DIFFERENT ON MPE V
(598)
W CAUSE If a compilation has $GLOBAL, $RLFILE, and $SUBPROGRAM set, the
result of the compile will be different than if it was done on
MPE V (no outer block information is output).
ACTION Remove either $GLOBAL or $SUBPROGRAM.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
599 MESSAGE POSSIBLE PARAMETER ADDRESS ALIGNMENT MISMATCH (599)
W CAUSE A VAR parameter of unknown alignment is being passed as a
reference parameter to an INTRINSIC which has a strict
alignment requirement for that parameter. If the actual
parameter has a less restrictive alignment than that required
by the intrinsic, an AD DRESS ALIGNMENT error will occur.
ACTION Ensure that the actual parameter has the alignment required by
the INTRINSIC.
---------------------------------------------------------------------------------------
600 MESSAGE INSUFFICIENT HEAP AREA TO ALLOCATE VARIABLE (PASCERR 600)
RT CAUSE The heap is full.
ACTION Increase the amount of heap space for the program or decrease
the storage used by the program.
---------------------------------------------------------------------------------------
601 MESSAGE INVALID DISPOSE PARAMETER (PASCERR 601)
RT CAUSE The pointer parameter to DISPOSE is NIL.
The pointer parameter to DISPOSE does not identify any area
allocated by NEW.
ACTION Initialize the pointer with NEW before disposing.
CAUSE The pointer parameter to DISPOSE identifies an area previously
deallocated by release.
ACTION Do not DISPOSE a pointer that has been released.
---------------------------------------------------------------------------------------
602 MESSAGE REPEATED USE OF DISPOSE ON GIVEN PARAMETER (PASCERR 602)
RT CAUSE The pointer parameter to dispose identifies an area previously
deallocated by dispose.
ACTION Do not DISPOSE a pointer that has been released.
---------------------------------------------------------------------------------------
603 MESSAGE DISPOSE PARAMETER ALLOCATED AS DIFFERENT VARIANT (PASCERR 603)
RT CAUSE The pointer parameter to dispose identifies an area allocated
by new with a different sequence of case constants.
CAUSE The pointer parameter to dispose includes case constants, but
it identifies an area allocated by new without any case
constants.
CAUSE The pointer parameter to dispose does not include case
constants, but it identifies an area allocated by new with case
constants.
ACTION Make sure that any tags associated with DISPOSE match the tags
on NEW. Also check for heap corruption.
---------------------------------------------------------------------------------------
604 MESSAGE DISPOSE PARAMETER CONTAINS AN OPEN SCOPE (PASCERR 604)
RT CAUSE The pointer parameter to dispose identifies an area containing
an actual variable parameter, an element of the record variable
list of a WITH statement, or both.
ACTION Make sure that the identifier does not reference such an area.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
605 MESSAGE INVALID RELEASE PARAMETER (PASCERR 605)
RT CAUSE The parameter to RELEASE was not set by a previous call to
MARK.
ACTION Initialize the parameter with MARK.
CAUSE The parameter to RELEASE was set by a call to MARK, but a
previous call to RELEASE has been made with this parameter.
ACTION Get rid of one of the uses of MARK.
CAUSE The parameter to RELEASE was set by a call to MARK, but that
call to MARK was preceded by a call to MARK with a different
parameter that has already been used as a parameter to RELEASE.
ACTION Don't use RELEASE on already released space.
---------------------------------------------------------------------------------------
606 MESSAGE RELEASE PARAMETER ENCLOSES AN OPEN SCOPE (PASCERR 606)
RT CAUSE The parameter to release identifies an area containing an
actual variable parameter, an element of the record variable
list of a WITH statement, or both.
ACTION Make sure that the identifier does not reference such an area.
---------------------------------------------------------------------------------------
607 MESSAGE RELEASE PARAMETER ENCLOSES GETHEAP AREA(S) (PASCERR 607)
RT CAUSE The parameter to release identifies an area containing areas
the user allocated with GETHEAP procedure, but which have not
yet been deallocated with the RTNHEAP procedure.
ACTION RTNHEAP must be used to release areas allocated by GETHEAP.
---------------------------------------------------------------------------------------
608 MESSAGE HEAP INTEGRITY LOST / HEAP DATA LOST (PASCERR 608)
RT CAUSE The internal data structures of the heap have become
inconsistent. The most likely causes are:
1. A field has been assigned to in a variant different than
the one specified in a call to new.
2. A pointer to a disposed area (for example, a dangling
pointer) has been dereferenced in an assignment.
3. An SPL routine has directly accessed the DL-DB area
outside of a region allocated by the GETHEAP procedure.
4. The DLSIZE intrinsic has been called.
5. The RTNHEAP procedure was unable to return an area.
ACTION Verify that none of the likely causes have occurred.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
609 MESSAGE BAD ALIGNMENT (PASCERR 609)
RT CAUSE A call to new or dispose passed a bad value for the alignment
parameter; for example, the type to which the pointer points
has an alignment which is not recognized by NEW or DISPOSE. The
only legal values for the alignment are 1, 2, 4, 8, 16, and
2048.
ACTION Ensure that the type to which the pointer points has an
alignment which is one of the above.
CAUSE A call to P_GetHeap or P_RtnHeap passed a bad value for the
alignment parameter.
ACTION Give a correct alignment value.
---------------------------------------------------------------------------------------
610 MESSAGE BAD SIZE (PASCERR 610)
RT CAUSE A call to new or dispose passed a bad value for the size of the
area.
ACTION None. Usually an internal error.
CAUSE A call to GetHeap or RtnHeap passed a bad value for the size of
the area.
ACTION Change the size parameter.
---------------------------------------------------------------------------------------
611 MESSAGE HEAP INTEGRITY LOST / HEAP DATA LOST (PASCERR 608)
RT CAUSE The internal data structures of the heap have become
inconsistent. The most likely causes are:
1. A field has been assigned to in a variant different than
the one specified in a call to new.
2. A pointer to a disposed area, such as a dangling
pointer, has been dereferenced in an assignment.
3. There is a mismatch of data types. Check to see that
the routine calling NEW or GETHEAP uses the same
declaration for the pointer as the routine which makes
an assignment through it (for separate compilations).
ACTION According to above causes.
---------------------------------------------------------------------------------------
620 MESSAGE VALUE NOT WITHIN SUBRANGE (PASCERR 620)
RT CAUSES The value of an ordinal expression is outside of the subrange
of the target of an assignment statement.
The value of an ordinal expression appearing as an actual
parameter is outside the subrange of the formal value
parameter.
The value of an ordinal expression appearing in an array
selector is outside of the subrange of the index type.
ACTION Ensure that the value is within the subrange.
---------------------------------------------------------------------------------------
621 MESSAGE NO CASE LABEL FOR SELECTOR VALUE (PASCERR 621)
RT CAUSE The value of the CASE select expression does not match any of
the specified CASE constants and no OTHERWISE clause appears.
ACTION Add a CASE to handle the value that caused the error, or add an
OTHERWISE clause to handle the value, or change the program
logic so the value of the selector corresponds with one of the
CASE labels.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
622 MESSAGE INVALID POINTER (PASCERR 622)
RT CAUSE A pointer with the value of NIL was dereferenced.
A pointer with an undefined value was dereferenced.
A pointer set by MARK was dereferenced.
A pointer identifying an area previously deallocated was
dereferenced.
ACTION Correct the program logic.
---------------------------------------------------------------------------------------
623 MESSAGE VALUE OF PRED UNDEFINED (PASCERR 623)
RT CAUSE The minimum value of an ordinal type or subrange was the
parameter to PRED. The result is undefined.
ACTION Do not call PRED with the lowest value of an ordinal type.
---------------------------------------------------------------------------------------
624 MESSAGE VALUE OF SUCC UNDEFINED (PASCERR 624)
RT CAUSE The maximum value of an ordinal type or subrange was the
parameter to SUCC. The result is undefined.
ACTION Do not call SUCC with the highest value of an ordinal type.
---------------------------------------------------------------------------------------
625 MESSAGE SET RANGE ERROR (PASCERR 625)
RT CAUSE An attempt was made to assign a set to a set variable when the
set contains an element not within the set range of the
variable.
An attempt was made to pass a set to a formal parameter when
the set contains an element not within the set range of the
parameter.
ACTION Correct the program logic.
---------------------------------------------------------------------------------------
626 MESSAGE ATTEMPT TO DO MOD BY A VALUE LESS THAN OR EQUAL TO ZERO
(PASCERR 626)
RT CAUSE An attempt was made to perform the MOD operation when the right
operand is zero or negative.
ACTION Correct the program logic error that has caused the invalid
value to be used. Note that MOD is not the remainder operator.
---------------------------------------------------------------------------------------
627 MESSAGE SQRT CALLED WITH NEGATIVE ACTUAL PARAMETER (PASCERR 627)
RT CAUSE The value passed to the SQRT function is less than zero.
ACTION Only call SQRT with non-negative values.
---------------------------------------------------------------------------------------
628 MESSAGE LN CALLED WITH NON-POSITIVE ACTUAL PARAMETER (PASCERR 628)
RT CAUSE The value passed to the LN function is less than or equal to
zero.
ACTION Only call LN with positive values.
---------------------------------------------------------------------------------------
640 MESSAGE BAD PROCEDURAL PARAMETER (PASCERR 640)
RT CAUSE A nonlevel 1 procedure or function was passed as a procedural
or functional parameter to an external, non-HP Pascal routine.
ACTION Only level 1 procedures/functions can be passed.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
650 MESSAGE STRING OVERFLOW (PASCERR 650)
RT CAUSE An attempt was made to index beyond the maximum length of the
string.
ACTION Correct the string operation, standard procedure or function
call arguments, or the program logic.
---------------------------------------------------------------------------------------
651 MESSAGE STRING INDEX EXCEEDS CURRENT LENGTH (PASCERR 651)
RT CAUSE An attempt was made to index beyond the current length of the
string.
ACTION Correct the argument or the program logic.
---------------------------------------------------------------------------------------
652 MESSAGE DESIGNATED CHARACTER POSITION(S) OUTSIDE STRING (PASCERR 652)
RT CAUSE The specified offset is greater than the current length of the
string, or less than 1.
ACTION Correct either the argument or the program logic.
---------------------------------------------------------------------------------------
653 MESSAGE DESIGNATED CHARACTER POSITION(S) OUTSIDE PAC (PASCERR 653)
RT CAUSE The specified offset is greater than the upper bound of the
PAC.
ACTION Correct the program logic that has caused the invalid value to
be used; change the value that has caused the error to a
legitimate value. Also check the type definition.
---------------------------------------------------------------------------------------
654 MESSAGE ATTEMPT TO READ PAST END OF STRING (PASCERR 654)
RT CAUSE Attempt was made to read beyond the maximum length of the
string.
ACTION Correct the problem that is causing the read past the end of
the string.
---------------------------------------------------------------------------------------
655 MESSAGE INVALID NUMBER OF CHARACTERS SPECIFIED (PASCERR 655)
RT CAUSE The number of characters to be copied, moved, or deleted in the
predefined string procedure STRMOVE is less than zero.
ACTION Correct the problem that is generating the negative count.
---------------------------------------------------------------------------------------
670 MESSAGE INVALID CHARACTER FOR HEX DIGIT (PASCERR 670)
RT CAUSE The character was not in the set 0..9, A..F, or a..f.
ACTION Correct the argument to the numeric conversion function to
contain only valid characters in the particular base.
---------------------------------------------------------------------------------------
671 MESSAGE INVALID CHARACTER FOR OCTAL DIGIT (PASCERR 671)
RT CAUSE The character was not in the set 0..7.
ACTION Correct the argument to the numeric conversion function to
contain only valid characters in the particular base.
---------------------------------------------------------------------------------------
672 MESSAGE INVALID CHARACTER FOR BINARY DIGIT (PASCERR 672)
RT CAUSE The character was not in the set 0..1.
ACTION Correct the argument to the numeric conversion function to
contain only valid characters in the particular base.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
673 MESSAGE NUMBER OF SIGNIFICANT DIGITS CAUSED OVERFLOW (PASCERR 673)
RT CAUSE The number of significant digits was more than 32 for the
standard function BINARY, 11 for the function OCTAL, or 8 for
the function HEX.
ACTION Correct the argument to the numeric conversion function to be a
representable value.
---------------------------------------------------------------------------------------
690 MESSAGE OPEN ERROR: PHYSICAL FILE COULD NOT BE CLOSED (PASCERR 690)
RT CAUSE An attempt was made to open a file, but the logical file was
already associated with a physical file and this physical file
could not be closed prior to opening another physical file.
ACTION Find out why the file could not be closed.
---------------------------------------------------------------------------------------
691 MESSAGE OPEN ERROR: MISMATCH OF LOGICAL/PHYSICAL FILES (PASCERR 691)
RT CAUSE The characteristics of the logical file are not compatible with
those of the associated physical file. For example, a physical
file with variable length records may not be opened for direct
access.
ACTION Check to make sure that the file characteristics are
compatible.
---------------------------------------------------------------------------------------
692 MESSAGE FILE OPEN ERROR (PASCERR 692)
RT CAUSE An unsuccessful attempt was made to open a file. The file was
absent or exclusively accessed, or you did not have permission
to access the file.
ACTION Check for file's presence and its access protections, and also
the state of the file when the open is attempted.
---------------------------------------------------------------------------------------
693 MESSAGE ERROR OCCURRED WHILE READING FROM FILE (PASCERR 693)
RT CAUSE File system failure or corrupted Pascal FILE variable.
ACTION Correct the file system problem, or correct program error that
corrupted Pascal FILE variable, such as array reference out of
bounds with RANGE OFF or dereferencing an invalid pointer.
---------------------------------------------------------------------------------------
694 MESSAGE ATTEMPT TO READ PAST EOF (PASCERR 694)
RT CAUSE The current position is past the last component of the file.
ACTION Correct the program logic to check EOF before reading file data
or checking EOLN status. For a direct access file, check that
disk record to be read is not greater than MAXPOS.
---------------------------------------------------------------------------------------
695 MESSAGE ERROR OCCURRED WHILE WRITING TO FILE (PASCERR 695)
RT CAUSE A Pascal FILE variable has been corrupted.
ACTION Correct the file system problem or program error that is
corrupting the HP Pascal file such as an array out of bounds
with RANGE OFF or dereferencing an invalid pointer.
CAUSE An attempt is made to write past the physical unit of the file.
ACTION Increase the file's physical limit.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
696 MESSAGE WRITE ON READ-ONLY FILE (PASCERR 696)
RT CAUSE An attempt was made to perform an output operation on a file
opened for input access only.
ACTION Correct the program logic so it doesn't write to the file or
open the file in a way that permits writing (such as REWRITE,
APPEND, or OPEN.) Scratch files can only be created by opening
them in a way that permits writing.
---------------------------------------------------------------------------------------
697 MESSAGE OPEN ERROR: UNABLE TO INITIALIZE POSITION (PASCERR 697)
RT CAUSE A request was made to open a logical file already associated
with the physical file. However, the file pointer was unable
to be repositioned at the beginning of the physical file.
ACTION See if program logic is corrupting the Pascal FILE variable.
---------------------------------------------------------------------------------------
698 MESSAGE OPEN ERROR: UNABLE TO EMPTY FILE (PASCERR 698)
RT CAUSE REWRITE was unable to empty the file of its previous contents.
ACTION Check if program logic is corrupting the Pascal FILE variable.
Otherwise, it is a file system problem.
---------------------------------------------------------------------------------------
699 MESSAGE UNABLE TO CLOSE FILE (PASCERR 699)
RT CAUSE The file could not be closed as requested.
ACTION Check if you have save permission on your system or make sure
you have used the CLOSE command to close the file.
---------------------------------------------------------------------------------------
700 MESSAGE ERROR OCCURRED DURING DIRECT ACCESS I/O (PASCERR 700)
RT CAUSE An error occurred during a file operation on a direct access
file.
ACTION Check if you are specifying a record beyond the file's physical
limit.
---------------------------------------------------------------------------------------
701 MESSAGE ILLEGAL CHARACTER IN NUMBER (PASCERR 701)
RT CAUSE An attempt was made to read a number from a text file, but an
illegal character was found before a valid number.
ACTION Correct the input.
---------------------------------------------------------------------------------------
702 MESSAGE INPUT VALUE OVERFLOW (PASCERR 702)
RT CAUSE The numeric value read is too large for the type of the
variable.
ACTION Correct the input.
---------------------------------------------------------------------------------------
703 MESSAGE ATTEMPT TO WRITE PAST PHYSICAL BOUNDS OF FILE (PASCERR 703)
RT CAUSE The current record position is past the physical limit of the
file.
ACTION Create a larger size file and re-run the program.
---------------------------------------------------------------------------------------
704 MESSAGE READ ATTEMPTED FROM OUTPUT FILE (PASCERR 704)
RT CAUSE An attempt was made to perform an input operation on a file
opened only for output.
ACTION Correct the program logic so it doesn't read from the file or
open the file in a way that permits reading (such as RESET or
OPEN.)
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
705 MESSAGE FILE NOT OPENED FOR DIRECT ACCESS (PASCERR 705)
RT CAUSE An attempt was made to perform a direct access file operation
on a file not opened for direct access with the OPEN procedure.
ACTION A nontext file must be opened for direct access with OPEN to
use SEEK, READDIR, WRITEDIR, or POSITION.
---------------------------------------------------------------------------------------
706 MESSAGE FILE NOT OPENED (PASCERR 706)
RT CAUSE An attempt was made to access an unopened file.
ACTION Correct the program logic so it doesn't read from the file or
open the file in a way that permits reading (such as RESET or
OPEN.)
---------------------------------------------------------------------------------------
707 MESSAGE INVALID OPEN OPTION (PASCERR 707)
RT CAUSE An invalid option was found in the third parameter to one of
the file opening procedures.
ACTION Correct the option.
---------------------------------------------------------------------------------------
708 MESSAGE COULD NOT OPEN FILE FOR APPEND ACCESS (PASCERR 708)
RT CAUSE A file system failure or corrupted Pascal FILE variable
prevented opening a variable length record file for append
access.
ACTION Either correct the file system problem or correct the program
error that corrupted the Pascal FILE variable (such as array
reference out of bounds with RANGE OFF or dereferencing an
invalid pointer.)
---------------------------------------------------------------------------------------
709 MESSAGE FIELD WIDTH LESS THAN ZERO (PASCERR 709)
RT CAUSE The field width in a formatted write of a nonnumeric expression
was less than zero.
ACTION Correct the program logic so it doesn't use negative values for
the field width or decimal position.
---------------------------------------------------------------------------------------
710 MESSAGE FIELD WIDTH LESS THAN 1 (PASCERR 710)
RT CAUSE The field width in the formatted write of a numeric expression
was less than 1.
ACTION Correct the width specified.
---------------------------------------------------------------------------------------
711 MESSAGE NO DIGITS AFTER DECIMAL POINT (PASCERR 711)
RT CAUSE No digits occur after the decimal point in a formatted write of
a real or longreal expression.
ACTION Correct the input.
---------------------------------------------------------------------------------------
712 MESSAGE INPUT VALUE UNDERFLOW (PASCERR 712)
RT CAUSE The value read is too small to be represented in the variable.
ACTION Correct the input.
---------------------------------------------------------------------------------------
713 MESSAGE FIELD TOO SMALL TO PRINT NUMBER (PASCERR 713)
RT CAUSE This is an internal HP PASCAL error.
ACTION Contact Hewlett-Packard.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
714 MESSAGE INVALID CLOSE OPTION (PASCERR 714)
RT CAUSE An invalid disposition option was found in the second parameter
to CLOSE.
ACTION Correct the option.
---------------------------------------------------------------------------------------
715 MESSAGE INVALID ENUMERATED IDENTIFIER FOR INPUT (PASCERR 715)
RT CAUSE An attempt was made to read an enumerated identifier from a
textfile, but either a valid HP Pascal identifier was not found
or the identifier found was not an identifier of that
enumerated type.
ACTION Correct the input.
---------------------------------------------------------------------------------------
716 MESSAGE CANNOT WRITE ENUMERATED VALUE (PASCERR 716)
RT CAUSE An attempt was made to write an enumerated variable to a
textfile, but the current ordinal value of the variable is not
within the range of the enumerated type.
ACTION Check the program's logic.
---------------------------------------------------------------------------------------
717 MESSAGE INVALID BOOLEAN READ (PASCERR 717)
RT CAUSE An attempt was made to read a Boolean value from a textfile,
but a non-boolean value was found.
ACTION Correct the input.
---------------------------------------------------------------------------------------
718 MESSAGE INVALID FLOATING POINT NUMBER REPRESENTATION (PASCERR 718)
RT CAUSE An attempt was made to read a real or longreal number from a
textfile, but an invalid floating point number was found.
ACTION Correct the program's logic to read the real or longreal from
the correct place in the file or string, verify that the
correct file or string is being accessed, or correct the
corrupted file or string.
---------------------------------------------------------------------------------------
719 MESSAGE INVALID CALL TO EOLN (PASCERR 719)
RT CAUSE The EOLN function was called for a file positioned at
end-of-file. An end-of-line marker precedes the end-of-file in
every text file, but this final end-of-line marker had already
been read past.
ACTION Check for end-of-file before calling EOLN.
---------------------------------------------------------------------------------------
720 MESSAGE UNABLE TO LOCK FILE (PASCERR 720)
RT CAUSE An attempt was made to lock a file without specifying the lock
option in the call to open. This error should never occur
since in HP Pascal the only way to lock a file is by specifying
this lock option.
ACTION None
---------------------------------------------------------------------------------------
721 MESSAGE WRITE FIELD WIDTH TOO LARGE (PASCERR 721)
RT CAUSE Either an attempt was made to write a number with a field width
greater than 254 characters, or an attempt was made to write a
longreal in fixed point format which would result in an
excessive number of digits being printed.
ACTION Reduce the field width if it is greater than 254 characters.
Write large longreals in floating point format.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
722 MESSAGE CANNOT "ASSOCIATE" FILE OPENED BY A PASCAL ROUTINE (PASCERR
722)
RT CAUSE An attempt was made to associate a file that was not opened
with a system provided open routine. Instead, the file was
opened with a PASCAL open routine.
ACTION Open the file with a system provided open routine such as
MPE/iX "FOPEN" or HP-UX "OPEN" before using "associate."
---------------------------------------------------------------------------------------
723 MESSAGE MISSING OPTIONS TO "ASSOCIATE" (PASCERR 723)
RT CAUSE The option string passed to the associate routine was empty.
ACTION Pass the appropriate options to the associate routine.
---------------------------------------------------------------------------------------
724 MESSAGE INVALID OPTIONS TO "ASSOCIATE" (PASCERR 724)
RT CAUSE An illegal combination of options were passed to "associate."
ACTION Pass a legal set of options to "associate."
---------------------------------------------------------------------------------------
725 MESSAGE LOGICAL FILE PREVIOUSLY ASSOCIATED OR OPENED (PASCERR 725)
RT CAUSE An attempt was made to associate a logical file name to a
physical file number. However, the file name is already on the
Pascal open file list. It was placed on the list during a
previous "associate" or "open." If the file is not
disassociated or close d, any subsequent attempt to associate
it will fail.
ACTION Close the file using the Pascal "close" routine or disassociate
the file using the Pascal "disassociate" routine.
---------------------------------------------------------------------------------------
799 MESSAGE INVALID OPERATING SYSTEM I/O (PASCERR 799)
RT CAUSE An attempt was made to perform some kind of I/O which is
illegal on this Operating System. This error will never occur
for normal users.
ACTION Contact Hewlett-Packard.
---------------------------------------------------------------------------------------
808 MESSAGE COERCION REQUIRES $TYPE_COERCION 'STRUCTURAL'$ (808)
CT CAUSE The current $TYPE_COERCION 'string'$ is insufficient to permit
this type coercion.
ACTION Set the type_coercion level to that given in the message.
---------------------------------------------------------------------------------------
809 MESSAGE COERCION REQUIRES $TYPE_COERCION 'REPRESENTATION'$ (809)
CT CAUSE The current $TYPE_COERCION 'string'$ is insufficient to permit
this type coercion.
ACTION Set the type_coercion level to that given in the message.
---------------------------------------------------------------------------------------
810 MESSAGE COERCION REQUIRES $TYPE_COERCION 'STORAGE'$ (810)
CT CAUSE The current $TYPE_COERCION 'string'$ is insufficient to permit
this type coercion.
ACTION Set the type_coercion level to that given in the message.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
811 MESSAGE COERCION REQUIRES $TYPE_COERCION 'NONCOMPATIBLE'$ (811)
CT CAUSE The current $TYPE_COERCION 'string'$ is insufficient to permit
this type coercion.
ACTION Set the type_coercion level to that given in the message. This
is very dangerous coding practice.
---------------------------------------------------------------------------------------
813 MESSAGE MULTIPLE DEFINITIONS FOR THIS MODULE (813)
CT CAUSE A definition for this module identifier has already been
compiled within this compilation unit.
ACTION Delete extra module definition from the compilation unit.
---------------------------------------------------------------------------------------
814 MESSAGE MISSING EXPORT SECTION (814)
CT CAUSE A module must have an EXPORT section.
ACTION Define an EXPORT section for this module.