HP 3000 Manuals HP 3000 Manuals
Messages 816-7999
---------------------------------------------------------------------------------------
816 MESSAGE INVALID IMPORT MODULE SPECIFIED (816)
CT CAUSE The IMPORT module specified could not be found.
ACTION Check $SEARCH path for missing files or check the module name.
CAUSE The module name is a duplicate of an identifier previously
defined.
ACTION Rename either the module name or the identifier.
---------------------------------------------------------------------------------------
817 MESSAGE INVALID MODULE IDENTIFIER (817)
CT CAUSE The identifier is not a module identifier.
ACTION Check identifier for misspellings.
---------------------------------------------------------------------------------------
818 MESSAGE NOT EXPORTED BY THE QUALIFYING IMPORTED MODULE (818)
CT CAUSE The identifier was not exported by the qualifying imported
module or defined in the module currently being defined.
ACTION Check the identifier for misspellings.
---------------------------------------------------------------------------------------
819 MESSAGE TYPE COERCION PERMITTED FOR DATA ITEMS ONLY (819)
CT CAUSE There was an attempt to type coerce NIL.
There was an attempt to type coerce a procedure name.
ACTION Remove the type coercion.
---------------------------------------------------------------------------------------
820 MESSAGE BIAS IS LESS THAN MINIMUM ARRAY INDEX (820)
CT CAUSE The bias parameter to a MOVE procedure will always cause an
index range error before the move is completed.
ACTION Fix the bias parameter or count parameter.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
821 MESSAGE BIAS + COUNT IS GREATER THAN MAXIMUM ARRAY INDEX (821)
CT CAUSE The bias and move count parameters to a MOVE procedure will
always cause an index range error before the move is completed.
ACTION Fix the bias parameter or count parameter.
---------------------------------------------------------------------------------------
822 MESSAGE BIAS IS NOT ASSIGNMENT COMPATIBLE WITH ARRAY INDEX TYPE (822)
CT CAUSE A bias parameter of a type that is not assignment compatible to
the index type of an array parameter to a MOVE procedure was
specified.
ACTION Fix the bias parameter to be of the same type as the index of
the array.
---------------------------------------------------------------------------------------
823 MESSAGE TARGET ELEMENT TYPE DOES NOT MATCH SOURCE ELEMENT TYPE (823)
CT CAUSE Element type of the source and target parameters to a MOVE
procedure must be identical.
ACTION Use a different mechanism to move data.
---------------------------------------------------------------------------------------
824 MESSAGE ACTUAL PARAMETER MUST BE AN ARRAY (824)
CT CAUSE The source or target parameter to a MOVE procedure is not an
array type, which it must be.
ACTION Declare the type as an array or coerce the parameter to an
array type.
---------------------------------------------------------------------------------------
825 MESSAGE A CRUNCHED STRUCTURE IS REQUIRED HERE (825)
CT CAUSE Any structures nested within a crunched structure must also be
crunched.
ACTION Declare the inner structure "crunched".
---------------------------------------------------------------------------------------
826 MESSAGE INVALID TYPE FOR COMPONENT OF A CRUNCHED STRUCTURE (826)
CT CAUSE Crunched structures may only have components of certain types.
ACTION Consult the HP Pascal Reference Manual for details.
---------------------------------------------------------------------------------------
828 MESSAGE MISSING DEFAULT VALUE FOR "! " (828)
CT CAUSE This parameter requires a default value to be specified.
ACTION Supply a default value in the "default_parms" option.
---------------------------------------------------------------------------------------
831 MESSAGE ROUTINE OPTION NOT COMPATIBLE WITH PREVIOUS ONE(S) (831)
CT CAUSE A routine was declared with two routine options that are
incompatible.
ACTION Re-evaluate the requirements for the routine options.
---------------------------------------------------------------------------------------
832 MESSAGE PROCEDURE NESTING TOO GREAT FOR THIS ROUTINE OPTION (832)
CT CAUSE A level 2 or greater routine was declared with a routine option
that is illegal at a level greater than 1.
ACTION Either make the routine level 1 or remove the routine option.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
833 MESSAGE INVALID ROUTINE OPTION (833)
CT CAUSE A routine option was declared that is not a known routine
option.
ACTION Check the spelling.
---------------------------------------------------------------------------------------
834 MESSAGE INVALID EXTENSIBLE PARAMETER COUNT (834)
CT CAUSE The count value in an Extensible routine is either less than
"0" or greater than the number of parameters in the routine.
ACTION Provide a legitimate count.
---------------------------------------------------------------------------------------
835 MESSAGE THIS FORM PERMITTED ONLY IN ROUTINE OPTION (835)
CT CAUSE A keyword value assignment to a formal parameter was used
outside of a definition option.
ACTION Remove the keyword assignment and assign by position.
---------------------------------------------------------------------------------------
836 MESSAGE THIS FORM NOT PERMITTED IN ROUTINE OPTION (836)
CT CAUSE An empty parameter was specified in a routine option or the
parameter was an expression.
ACTION Either supply a value or replace the expression with a
constant.
---------------------------------------------------------------------------------------
837 MESSAGE INVALID FORMAL PARAMETER FOR THIS ROUTINE OPTION (837)
CT CAUSE A routine option specified a formal parameter that was not
declared in the formal parameter list.
ACTION Check the formal parameter list.
---------------------------------------------------------------------------------------
838 MESSAGE DUPLICATE FORMAL PARAMETER FOR THIS ROUTINE OPTION (838)
CT CAUSE A routine option specified a formal parameter twice.
ACTION Remove the duplicate specification.
---------------------------------------------------------------------------------------
839 MESSAGE ROUTINE OPTION AND FORMAL PARAMETER ORDERING MISMATCH (839)
CT CAUSE The order of parameters in a routine option does not match the
ordering of the formal parameters in the formal parameter list.
ACTION Fix the routine option or match the ordering.
---------------------------------------------------------------------------------------
841 MESSAGE DEFAULT VALUE FOR VARIABLE FORMAL PARAMETER IS NOT NIL (841)
CT CAUSE A VAR formal parameter was assigned a default value that is not
NIL.
ACTION Assign the value NIL to the VAR parameter.
---------------------------------------------------------------------------------------
842 MESSAGE DEFAULT VALUE NOT COMPATIBLE WITH FORMAL PARAMETER (842)
CT CAUSE A parameter was assigned a default value whose type does not
match the type of the formal parameter.
ACTION Fix the default value.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
844 MESSAGE ILLEGAL USE OF READONLY VARIABLE OR PARAMETER (844)
CT CAUSE A READONLY variable or parameter was used as the target of an
assignment statement or was passed as a VAR parameter.
ACTION Remove the offending use of the READONLY variable or parameter.
---------------------------------------------------------------------------------------
845 MESSAGE INVALID USE OF ROUTINE OPTION (845)
CT CAUSE The routine option is not allowed in this context.
ACTION Remove the routine option.
---------------------------------------------------------------------------------------
846 MESSAGE NOT A FORMAL PARAMETER (846)
CT CAUSE A formal parameter specified in a routine option is not
declared in the formal parameter list.
ACTION Check the spelling. Remove the parameter in the routine
option. Add the parameter to the formal parameter list.
---------------------------------------------------------------------------------------
847 MESSAGE NOT A VARIABLE DEFAULT FORMAL PARAMETER (847)
CT CAUSE A formal parameter to the Haveoptvarparm function is not a VAR
or ANYVAR parameter.
ACTION Check the formal parameter list. Remove this call to
Haveoptvarparm.
---------------------------------------------------------------------------------------
848 MESSAGE NOT AN EXTENSION FORMAL PARAMETER (848)
CT CAUSE A formal parameter to the Haveextparm function is not an
extensible parameter.
ACTION Remove this call or check the count on the Extensible routine
option.
---------------------------------------------------------------------------------------
849 MESSAGE THIS ROUTINE OPTION NOT VALID FOR FUNCTIONS (849)
CT CAUSE The specified routine option is not allowed for a function.
ACTION Remove this routine option.
---------------------------------------------------------------------------------------
850 MESSAGE RECURSIVE USE OF INLINE PROCEDURE/FUNCTION NOT ALLOWED (850)
CT CAUSE A routine declared OPTION INLINE directly or indirectly calls
itself recursively.
ACTION Remove the recursion or remove the OPTION INLINE.
---------------------------------------------------------------------------------------
851 MESSAGE THIS DIRECTIVE NOT ALLOWED WITH ROUTINE OPTIONS (851)
CT CAUSE A routine directive was declared for a routine that has
definition options.
ACTION Remove the directive or the option.
---------------------------------------------------------------------------------------
852 MESSAGE NOT A DEFAULT FORMAL PARAMETER (852)
CT CAUSE A formal parameter supplied to the Haveoptvarparm function is
not a default parameter.
ACTION Remove this call or check the list of default parameters.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
856 MESSAGE AN ADDRESS CAN NOT BE GENERATED FOR THIS VARIABLE (856)
CT CAUSE The parameter to ADDRESS, BADDRESS, or WADDRESS does not reside
on a storage unit boundary, so a legal address can not be
generated for it.
ACTION Do not take the address of this variable.
---------------------------------------------------------------------------------------
858 MESSAGE THIS FEATURE IS NO LONGER VALID (858)
CT CAUSE The designated feature has been removed from the language
definition.
ACTION Remove the feature from the source code.
---------------------------------------------------------------------------------------
859 MESSAGE ANYPTR MAY NOT BE DEREFERENCED (859)
CT CAUSE Pointers of type ANYPTR may not be dereferenced.
ACTION Assign or type coerce the pointer before dereferencing it.
---------------------------------------------------------------------------------------
860 MESSAGE ADDRESS ALIGNMENT INCOMPATIBLE WITH DESIRED USE (860)
CT CAUSE The alignment of the value of the pointer being coerced is
incompatible with the alignment implied by the type coercion.
ACTION Ensure that the target type's alignment is smaller than or
equal to that of the source type.
CAUSE The alignment of an actual parameter prohibits its use due to
the required alignment of the VAR or ANYVAR formal parameter.
ACTION Ensure that the actual parameter has an alignment larger than
or equal to that of the formal parameter.
---------------------------------------------------------------------------------------
861 MESSAGE INCOMPATIBLE SOURCE AND TARGET TYPES FOR COERCION (861)
CT CAUSE The subrange of values for the type of the parameter to the
type coercion does not overlap with the subrange of values for
the target type of the type coercion. (ordinal coercion only)
ACTION None: A subrange variable cannot be coerced to another
subrange type that does not have some overlap with its original
type.
---------------------------------------------------------------------------------------
862 MESSAGE THIS TYPE COERCION NOT PERMITTED AS REFERENCE PARAMETER (862)
CT CAUSE Ordinal type coercions that require type conversion are not
permitted as reference parameters.
Pointer type coercions that require type conversion such as
short-to-long or long-to-short pointer conversion are not
permitted as reference parameters.
ACTION Copy into a variable, and pass that as the reference parameter.
---------------------------------------------------------------------------------------
863 MESSAGE THIS FEATURE IS NOT IMPLEMENTED (863)
CT CAUSE The feature in use has not been implemented in the current
compiler.
ACTION Remove this feature from the source code.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
864 MESSAGE BYTE OFFSET NOT PERMITTED WITH PROCEDURE OR FUNCTION VAR (864)
CT CAUSE ADDR takes a second parameter only if the first parameter is
not a procedure or function variable.
ACTION Remove the second parameter.
---------------------------------------------------------------------------------------
866 MESSAGE NO ANYVAR FOUND IN FORMAL PARAMETER LIST (866)
CT CAUSE A procedure or function declared with OPTION UNCHECKABLE ANYVAR
must have an ANYVAR parameter in its formal parameter list.
ACTION Remove the option or supply an ANYVAR.
---------------------------------------------------------------------------------------
868 MESSAGE INTRINSIC MECHANISM ERROR "! ". (868)
CT CAUSE An error has occurred in accessing the intrinsic file.
ACTION [REV BEG]Check the status indicator returned from the Intrinsic
Mechanism Access Routines. If the status indicator is one of
the following values, correct the error.
Value Description
1 OpenFail The given IM could not be opened.
2 CloseFail The IM could not be closed.
3 RetrieveFail An access error occurred in attempting to
read from the IM.
4 ReplaceFail An access error occurred in attempting to
write from the IM.
5 SpaceExhausted Inadequate space remains in the IM to
perform requested action.
14 BadIntrinsicFileThe file being accessed is not an intrinsic
file.
If the status indicator is not one of the above values, report
the error to your HP Service Representative.[REV END]
---------------------------------------------------------------------------------------
869 MESSAGE ARRAY ELEMENT SIZE MUST BE >= ONE BYTE. (869)
CT CAUSE Array parameter to Move_Fast must have elements with sizes
greater than or equal to one byte.
ACTION Use another mechanism to perform the move.
---------------------------------------------------------------------------------------
870 MESSAGE ARRAY MUST BE ALIGNED ON A BYTE BOUNDARY. (870)
CT CAUSE Array parameter to Move_Fast must be aligned on a byte
boundary.
ACTION Use another mechanism to move the array.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
871 MESSAGE INVALID ARRAY PARAMETERS TO MOVE_FAST. (871)
CT CAUSE Both array parameters to Move_Fast must have elements with the
same sizes.
ACTION Use some other mechanism to move the array.
CAUSE If only one of the parameters is crunched, then the elements
must be packed in with no wasted space between elements.
ACTION Check the packing.
---------------------------------------------------------------------------------------
872 MESSAGE ARRAY ELEMENTS CANNOT BE CONFORMANT ARRAYS. (872)
CT CAUSE If an array parameter to one of the MOVE routines is a
conformant array, then its elements must not themselves be
conformant arrays. The size of the elements must be known at
compile time.
ACTION Use a different mechanism like a FOR or WHILE loop to move the
elements.
---------------------------------------------------------------------------------------
873 MESSAGE INVALID MODULE LIBRARY SPECIFIED (873)
CT CAUSE Either the file that is to be used for the search of a module
or the file that is the Module Library is not of the Module
Library format.
ACTION Ensure that the file that was previously created is in Module
Library format.
---------------------------------------------------------------------------------------
874 MESSAGE INVALID IMPORT MODULE ENVIRONMENT (874)
CT CAUSE Trying to import a module which was compiled under a different
compilation environment.
ACTION Recompile imported module on current machine.
---------------------------------------------------------------------------------------
875 MESSAGE INTRINSIC DECLARATION NOT ENTERED INTO INTRINSIC FILE (875)
CT CAUSE Due to a previous error the intrinsic declaration was not
entered into the intrinsic file.
ACTION Correct previous errors.
---------------------------------------------------------------------------------------
876 MESSAGE INTRINSIC FILE OVERFLOW (876)
CT CAUSE The physical limit of the intrinsic file has been exceeded.
ACTION Build a larger intrinsic file using BUILD or a file equation.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
877 MESSAGE INVALID DEREFERENCING OF AN IMPORTED POINTER (877)
CT CAUSE Trying to dereference an imported pointer whose type is not
defined.
ACTION Import the type that the pointer points to.
Do not dereference the pointer in this module.
---------------------------------------------------------------------------------------
878 MESSAGE INVALID USE OF AN INLINED ROUTINE (878)
CT CAUSE The address of an inlined routine is being requested. This
happens in the following cases:
* The procedure is passed as a parameter to WAddress,
BAddress, Addr or Assert (as the "assert procedure").
* The procedure is passed as the actual parm when the
formal parm is a procedural/functional type.
ACTION Don't use option inline if the procedure is being used in the
above contexts.
---------------------------------------------------------------------------------------
879 MESSAGE UNIMPLEMENTED USE OF AN INLINED ROUTINE "! " (879)
CT CAUSE An inline function appearing as an actual parameter to itself
is an unimplemented feature.
ACTION Assign the function result to a local variable and pass the
local variable as the parameter.
---------------------------------------------------------------------------------------
880 MESSAGE $ALIGNMENT$ CONFLICT (880)
CT CAUSE The $ALIGNMENT$ value on a record or array declaration is less
than the minimum alignment for the record or array (because of
the alignments of its fields/elements).
ACTION Specify an alignment for the record or array that is at least
as large as the maximum alignment of any of its
fields/elements.
CAUSE The type on the right hand side of a type declaration is a type
identifier which has already been defined with $ALIGNMENT$.
ACTION Remove the conflicting $ALIGNMENT$.
CAUSE $ALIGNMENT$ is not allowed on string and file types.
ACTION Don't use $ALIGNMENT$ on string and file types.
---------------------------------------------------------------------------------------
881 MESSAGE MIXED MODE OPERATIONS NOT ALLOWED (881)
CT CAUSE An expression which mixes $HP3000_16$ and $HP3000_32$ operands
is not allowed.
ACTION Don't mix modes in the expression.
CAUSE String parameters to predefined string procedures and functions
and strings used in string expressions require $HP3000_16$.
ACTION Don't use $HP3000_32$ strings as parameters to string
predefines or in string expressions.
CAUSE Real parameters to arithmetic functions require $HP3000_16$
reals.
ACTION Don't use $HP3000_32$ reals as parameters to arithmetic
predefines.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
882 MESSAGE MIXED MODE PACKING NOT ALLOWED (882)
CT CAUSE Mixing $HP3000_16$ and $HP3000_32$ in data type definitions is
not allowed.
ACTION Don't mix modes in data declarations.
---------------------------------------------------------------------------------------
883 MESSAGE COERCION REQUIRES $TYPE_COERCION 'CONVERSION'$ (883)
CT CAUSE The current $TYPE_COERCION$ level is insufficient to permit
this coercion.
ACTION Set the $TYPE_COERCION$ level to that given in the message.
---------------------------------------------------------------------------------------
884 MESSAGE INVALID TYPE FOR INTRINSIC FORMAL PARAMETER NUMBER ! (884)
CT CAUSE The data type for the formal parameter specified is not an
acceptable type for an intrinsic declaration (when building an
intrinsic file using $BUILDINT$).
ACTION Use an appropriate language-independent type for the intrinsic
parameter.
---------------------------------------------------------------------------------------
885 MESSAGE INVALID TYPE FOR INTRINSIC FUNCTION RETURN (885)
CT CAUSE The data type for the function return specified is not an
acceptable type for an intrinsic declaration.
ACTION Specify the correct type.
---------------------------------------------------------------------------------------
886 MESSAGE RECURSIVE INCLUDE OF FILE (886)
CT CAUSE The file just specified in an $INCLUDE$ directive is currently
being included (thus, this is an infinite recursion of
includes; a fatal error).
ACTION Remove the recursive include.
---------------------------------------------------------------------------------------
887 MESSAGE INVALID FORMAL PARAMETER TYPE (887)
CT CAUSE A data type which is a $HP3000_32$ type is not allowed as a
formal parameter when $HP3000_16$ is ON.
ACTION Declare the parameter to be of a $HP3000_16$ type.
---------------------------------------------------------------------------------------
888 MESSAGE STATEMENT ! INCOMPATIBLE WITH $ASSUME '!' (888)
CT CAUSE The code generated for the given statement conflicts with the
given assume option. The compiler has detected incorrect code
generation.
ACTION Use a correct ASSUME option or remove the $ASSUME option.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
889 MESSAGE CONFORMANT ARRAYS NOT ALLOWED WITH $HP3000_16$ (889)
CT CAUSE Conformant arrays are not implemented when using $HP3000_16$.
ACTION Do not use this feature with $HP3000_16$.
---------------------------------------------------------------------------------------
890 MESSAGE CANNOT EXPORT AN IMPORTED MODULE IN THE OUTER BLOCK (890)
CT CAUSE The word EXPORT was seen after the module name on an import
statement in the outer block.
ACTION Remove the word EXPORT.
---------------------------------------------------------------------------------------
891 MESSAGE LISTINTR FAILED TO COMPLETE SUCCESSFULLY (891)
CT CAUSE The listing of the intrinsic file terminated unexpectedly.
Possible reasons are that the listing file could not be opened,
or the file limit on the listing file was exceeded.
ACTION Make sure the intrinsic file is present and spelled correctly.
If the file limit on the listing file was exceeded, build a
larger file or use a file equation to specify a larger file.
---------------------------------------------------------------------------------------
892 MESSAGE UNABLE TO CLOSE FILE '!' (892)
CT CAUSE The compiler was unable to close the specified file. Possible
reasons are that system file space is exhausted, or that an
attempt is made to create a file across account boundaries
(which is not allowed on MPE/iX).
ACTION Create enough system file space or specify a file within the
account boundary.
---------------------------------------------------------------------------------------
893 MESSAGE I/O MODULE(S) NOT IMPORTED (893)
CT CAUSE A call to a standard procedure such as writeln, readln, write,
or read was made in the implement section of a module that did
not import the appropriate module STDINPUT or STDOUTPUT. As a
result, the default file symbols input and/or output are
unknown to the compilation unit.
ACTION Explicitly IMPORT the appropriate system-defined module
STDINPUT, STDOUTPUT, or both.
---------------------------------------------------------------------------------------
894 MESSAGE INVALID USE OF MODULE IDENTIFIER (894)
CT CAUSE Module identifier can only be used with IMPORT.
ACTION Rename the identifier or remove the module identifier.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
900 MESSAGE INCORRECT POINTER ALIGNMENT (900)
RT CAUSE Internal parameter to CHKA.
ACTION No action is required. Internal use only.
---------------------------------------------------------------------------------------
905 MESSAGE INVALID PROCEDURAL/FUNCTIONAL VALUE REFERENCED (905)
RT CAUSE The value does not denote any actual procedure or function.
The static nesting level of the value does not correspond to
the current state of the activation stack.
The value is NIL.
The procedure or function is uninitialized or contains a bad
value.
ACTION Make sure the procedure or function has been initialized
correctly.
---------------------------------------------------------------------------------------
908 MESSAGE MOVE PROCEDURE PARAMETERS OUT OF RANGE (908)
RT CAUSE The range of the move for either the source or target exceeds
the declared range of the source or target arrays.
ACTION Check that the expressions defining the start, offset, and
count are producing correct values.
---------------------------------------------------------------------------------------
909 MESSAGE ESCAPE PROCEDURE WITH NO ENCLOSING TRY-RECOVER (909)
RT CAUSE Escape was called by the user and no enclosing TRY-RECOVER was
declared.
ACTION Use TRY-RECOVER to catch the escape.
---------------------------------------------------------------------------------------
910 MESSAGE ESCAPE EXECUTED WITHOUT AN UNWIND DESCRIPTION FOR THE FRAME
(910)
RT CAUSE An escape was executed, but one or more of the procedures in
the program stack does not have an unwind descriptor.
ACTION Contact Hewlett-Packard.
---------------------------------------------------------------------------------------
911 MESSAGE ESCAPE EXECUTED BUT CANNOT UNWIND DESCRIPTOR FOR THE FRAME
(911)
RT CAUSE An Escape was executed, but one or more of the procedures in
the program stack has a frame that is not unwindable.
ACTION Contact Hewlett-Packard.
---------------------------------------------------------------------------------------
912 MESSAGE GOTO EXECUTED AND BOTTOM OF FRAME HIT; INTERNAL ERROR (912)
RT CAUSE Internal error occurred while executing a non-local GOTO
statement.
ACTION Contact Hewlett-Packard.
---------------------------------------------------------------------------------------
913 MESSAGE GOTO EXECUTED WITHOUT AN UNWIND DESCRIPTOR FOR THE FRAME (913)
RT CAUSE A non-local GOTO was executed, but one or more of the
procedures in the program stack does not have an unwind
descriptor.
ACTION Contact Hewlett-Packard.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
914 MESSAGE GOTO EXECUTED BUT CANNOT UNWIND DESCRIPTOR FOR THE FRAME (914)
RT CAUSE A non-local GOTO was executed, but one or more of the
procedures in the program stack has a frame that is not
unwindable.
ACTION Contact Hewlett-Packard.
---------------------------------------------------------------------------------------
5001 MESSAGE GOTO OUT OF BLOCK TO MULTIPLE ENTRY PT. (5001)
W CAUSE Goto out of block to procedure with multiple entry points.
ACTION Warning only. No action required.
---------------------------------------------------------------------------------------
5002 MESSAGE ! (5002)
W CAUSE FSerr for other messages (see following messages).
ACTION Warning only.
---------------------------------------------------------------------------------------
5004 MESSAGE UNINITIALIZED VARIABLE (SYMID = !) !. (5004)
W CAUSE Optimizer detected uninitialized variable, should have been
initialized before its use.
ACTION Warning only.
---------------------------------------------------------------------------------------
5080 MESSAGE PREVIOUS VERSION OF ENTRY ! WAS REPLACED (5080)
W CAUSE Code for the entry listed was replaced in the RL (iX only).
ACTION Warning only. No action required.
---------------------------------------------------------------------------------------
5104 to MESSAGE INTERNAL COMPILER ERROR.
5199
W CAUSE The compiler is in error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------
5200 MESSAGE INTERNAL REGISTER TABLE OVERFLOW; PROCEDURE TOO BIG (5200)
CT CAUSE Your procedure is too large for the compiler to handle at once.
ACTION Break your procedure into two or more pieces.
---------------------------------------------------------------------------------------
5202 MESSAGE MAXIMUM AMOUNT OF LOCAL DATA ALLOWED EXCEEDED (5202)
CT CAUSE The maximum amount of local storage allowed has been exceeded.
ACTION Break your procedure into two or more pieces.
---------------------------------------------------------------------------------------
5207 MESSAGE MULTIPLE PROGRAM ENTRY POINTS (5207)
CT CAUSE Possible multiple main programs.
ACTION Make sure only one main program exists in the compilation unit.
---------------------------------------------------------------------------------------
5208 MESSAGE TOO MANY NESTED TRYS IN PROCEDURE (5208)
CT CAUSE The maximum number of nested TRYs allowed in a procedure is
about thirty.
ACTION Break up your procedure by putting some of the inner TRY blocks
into a nested procedure.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5209 MESSAGE CANNOT OPEN OBJECT FILE (5209)
CT CAUSE The compiler cannot open the object file. This may be because:
(a) You do not have write permission in the group (on
MPE/iX) or directory (on HP-UX) that you are working in.
(b) You have exceeded some physical disk space limit.
ACTION
(a) Work in a group or directory in which you have write
permission or get write permission in the current group
or directory.
(b) Remove some unnecessary files to make room for your
object file.
---------------------------------------------------------------------------------------
5210 MESSAGE CANNOT CLOSE OBJECT FILE (5210)
CT CAUSE The compiler could not close the object file. This may be
because:
(a) You do not have write permission in the group (on
MPE/iX) or directory (on HP-UX) that you are working in.
(b) You have exceeded some physical disk space limit.
ACTION
(a) Work in a group or directory in which you have write
permission or get write permission in the current group
or directory.
(b) Remove some unnecessary files to make room for your
object file.
---------------------------------------------------------------------------------------
5211 MESSAGE INVALID FILE CODE FOR OBJECT FILE ! (5211)
CT CAUSE File code for object file is not NMOBJ or NMRL.
ACTION Change file code or use different object file.
---------------------------------------------------------------------------------------
5212 MESSAGE DUPLICATE LABELS ARE NOT ALLOWED (5212)
CT CAUSE A duplicate user or internal label exists.
ACTION Check for duplicate labels. If none are found, report this
error to your
HP Service Representative.
---------------------------------------------------------------------------------------
5213 MESSAGE CANNOT OPEN ASSEMBLY FILE (5213)
CT CAUSE The compiler could not open the assembly file. This may be
because:
(a) You do not have write permission in the group (on
MPE/iX) or directory (on HP-UX) that you are working in.
(b) You have exceeded some physical disk space limit.
ACTION
(a) Work in a group or directory in which you have write
permission, or obtain write permission in the current
group or directory.
(b) Remove some unnecessary files to make room for your
assembly file.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5214 MESSAGE CANNOT CLOSE ASSEMBLY FILE (5214)
CT CAUSE The compiler could not close the assembly file. This may be
because:
(a) You do not have write permission in the group (on
MPE/iX) or directory (on HP-UX) that you are working in.
(b) You have exceeded some physical disk space limit.
ACTION
(a) Work in a group or directory in which you have write
permission or obtain write permission in the current
group or directory.
(b) Remove some unnecessary files to make room for your
assembly file.
---------------------------------------------------------------------------------------
5380 MESSAGE ATTEMPT TO OPEN FILE ! FAILED (5380)
CT CAUSE File could not be opened by compiler.
ACTION Check capabilities, access rights, and permissions of file in
the group
(on MPE/iX) or directory (on HP-UX).
---------------------------------------------------------------------------------------
5381 MESSAGE FILE ! HAS INVALID FILE CODE; EXPECTED NMRL (5381)
CT CAUSE File code of object file should be NMRL.
ACTION Use different file for object, build file as NMRL, or do not
use RL compile option.
---------------------------------------------------------------------------------------
5382 MESSAGE ATTEMPT TO ADD MODULE(S) BEYOND MODULE LIMIT OF ! IN FILE !
(5382)
CT CAUSE Module cannot be added to named RL.
ACTION Clean up your RL or use a different file for the object.
---------------------------------------------------------------------------------------
5383 MESSAGE FILE ! HAS AN INVALID RECORD SIZE. EXPECTED 128W RECORDS.
(5383)
CT CAUSE The RL has an invalid record size.
ACTION Build a new RL file with a correct record size.
---------------------------------------------------------------------------------------
5400 to MESSAGE INTERNAL COMPILER ERROR.
5999
I CAUSE The compiler is in error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------
6055 MESSAGE OPTDRIVER: BAD OPTIMIZER OPTION; IGNORED. (6055)
W CAUSE Internal compiler error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------
6056 MESSAGE OPTDRIVER: CAN'T OPEN DEBUG FILE FOR OUTPUT; STDOUT USED.
(6056)
W CAUSE Internal compiler error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6057 MESSAGE OPTDRIVER: BAD OPTIMIZATION LEVEL SPECIFIED; DEFAULT OF 0 USED.
(6057)
W CAUSE Internal compiler error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------
6058 MESSAGE OPTDRIVER: BAD SCHEDULER ALGORITHM SPECIFIED, USED DEFAULT.
(6058)
W CAUSE Internal compiler error.
ACTION Check argument to +DS, then report error to your HP Service
Representative.
---------------------------------------------------------------------------------------
6059 MESSAGE OPTDRIVER: !1 BASIC BLOCKS; DROPPING TO LEVEL 1 OPTIMIZATION
FOR !2. (6059)
W CAUSE Procedure !2 contains more that 500 basic blocks and requires
an inordinate amount of compile-time resources. Therefore, the
optimizer will be run at level 1 for !2.
ACTION No action is necessary. However, on HP-UX, if level 2
optimization is desired in spite of a possibly lengthy compile
time, this limit can be overridden by the use of the +Obbnum
option, where num is at least as large as the number given in
this message.
ACTION Use the $OPTIMIZE 'BASIC_BLOCKS num$ compiler option.
---------------------------------------------------------------------------------------
6110 to MESSAGE INTERNAL OPTIMIZER ERROR.
6199
CT CAUSE The compiler is in error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------
6200 to MESSAGE ALIASER: OUT OF MEMORY.
6299
CT CAUSE The optimizer ran out of virtual memory.
ACTION The easiest workaround is to break your compilation unit into
two or more pieces.
On HP-UX, this error may also be produced if the system runs
out of swap space, so another possible work-around is to
increase the amount of swap space available to the system (see
your HP-UX system administrator about this). However, this
action should be taken only as a last-resort.
On MPE/iX, the compiler heap space can be increased by running
PASCALXL.PUB.SYS with a larger NMHEAP:
:RUN PASCALXL.PUB.SYS;NMHEAP=120000000 ...
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6305 MESSAGE RALLOC: OUT OF GENERAL REGISTERS. (6305)
CT CAUSE Possible overly complex expression.
ACTION Simplify large or complex expression.
---------------------------------------------------------------------------------------
6306 MESSAGE RALLOC: OUT OF CALLEE SPACE REGISTERS. (6306)
CT CAUSE Long pointer expression too complex.
ACTION Simplify long pointer expressions.
---------------------------------------------------------------------------------------
6307 MESSAGE RALLOC: OUT OF CALLER SPACE REGISTERS. (6307)
CT CAUSE Long pointer expression too complex.
ACTION Simplify long pointer expressions.
---------------------------------------------------------------------------------------
6308 MESSAGE RALLOC: OUT OF CALLEE FLOATING POINT REGISTERS. (6308)
CT CAUSE Floating point expression too complex.
ACTION Simplify floating point expressions.
---------------------------------------------------------------------------------------
6309 MESSAGE RALLOC: OUT OF CALLER FLOATING POINT REGISTERS. (6309)
CT CAUSE Floating point expression too complex.
ACTION Simplify floating point expressions.
---------------------------------------------------------------------------------------
6310 to MESSAGE OUT OF MEMORY
6365
CT CAUSE The optimizer ran out of virtual memory.
ACTION The easiest workaround is to break your compilation unit into
two or more pieces.
On HP-UX, this error may also be produced if the system runs
out of swap space, so another possible work-around is to
increase the amount of swap space available to the system (see
your HP-UX system administrator about this). However, this
action should be taken only as a last-resort.
On MPE/iX, the compiler heap space can be increased by running
PASCALXL.PUB.SYS with a larger NMHEAP:
:RUN PASCALXL.PUB.SYS;NMHEAP=120000000 ...
---------------------------------------------------------------------------------------
6400 to MESSAGE INTERNAL COMPILER ERROR.
6999
I CAUSE The compiler is in error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------
ON HP-UX, the following warnings are generated if you pass a model number
that is not found in the /usr/lib/sched.models file.
---------------------------------------------------------------------------------------
7000 MESSAGE MODEL NUMBER IS UNKNOWN; WILL DEFAULT TO arch-rev CODE
GENERATION. (7000)
W CAUSE The model number given on a +DA option is not known to the
compiler.
ACTION The default code generation is as specified in the warning. If
this is not the desired target architecture revision, the
version may be specified using an architecture revision (such
as 1.1) instead of a model number on the +DA option.
---------------------------------------------------------------------------------------
7001 MESSAGE MODEL NUMBER IS UNKNOWN; DEFAULT INSTRUCTION SCHEDULING IS
USED. (7001)
W CAUSE The model number given on a +DS option is not known to the
compiler.
ACTION The default instruction scheduling is based on the most recent
processor implementation known to the compiler. If this is not
what is desired, an alternate model number may be specified.
---------------------------------------------------------------------------------------
On HP-UX, the following warning will be generated if the file
/usr/lib/sched.models cannot be found.
---------------------------------------------------------------------------------------
7002 MESSAGE CANNOT OPEN /usr/lib/sched.models. (7002)
W CAUSE The file /usr/lib/sched.models does not exist or cannot be
opened for reading.
ACTION Check protections on /usr/lib/sched.models. If it does not
exist, contact your HP Service Representative.
---------------------------------------------------------------------------------------
On HP-UX, the following warning is generated if you pass arguments that
do not conform to the expected format.
---------------------------------------------------------------------------------------
7003 MESSAGE IMPROPER ARGUMENT TO +DA OR +DS OPTION. (7003)
W CAUSE An improper argument was given to the +DA or +DS option.
ACTION Check the reference manual for information on the correct form
of the option.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
7100 to MESSAGE INTERNAL COMPILER ERROR.
7109
I CAUSE The compiler is in error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------
7110 MESSAGE DEBUG INFORMATION MAY BE CORRUPT; "! " UNRESOLVABLE
REFERENCE(S). (7110)[REV BEG]
I CAUSE User errors.
ACTION Correct all user errors or remove -g or $SYMDEBUG options and
recompile.
If there are no user errors, report error to your HP Service
Representative.[REV END]
---------------------------------------------------------------------------------------
7200 MESSAGE INTERNAL TABLE OVERFLOW (7200)
CT CAUSE Source file too large.
ACTION Split program up into smaller files.
---------------------------------------------------------------------------------------
7201 MESSAGE NEW_SLC_BLOCK: OUT OF MEMORY. (7201)
CT CAUSE Compiler ran out of virtual memory.
ACTION See message 6200.
---------------------------------------------------------------------------------------
7202 MESSAGE INIT_LINK: OUT OF MEMORY. (7202)
CT CAUSE Compiler ran out of virtual memory.
ACTION See message 6200.
---------------------------------------------------------------------------------------
7203 MESSAGE ALLOCATE_BYTES: OUT OF MEMORY. (7203)
CT CAUSE Compiler ran out of virtual memory.
ACTION See message 6200.
---------------------------------------------------------------------------------------
7204 MESSAGE ERROR IN WRITING TO OUTPUT FILE. (7204)
CT CAUSE I/O error writing to object file.
ACTION Check for full file system (HP-UX, MPE/iX) or an object file
that too small (MPE/iX).
---------------------------------------------------------------------------------------
7205 MESSAGE UNABLE TO ALLOCATE SPACE FOR OBJECT IN RL. (7205)
CT CAUSE I/O error writing to RL.
ACTION Check for an RL file that is too small (MPE/iX).
---------------------------------------------------------------------------------------
7206 MESSAGE UNABLE TO ADD OBJECT TO RL. (7206)
CT CAUSE I/O error writing to RL.
ACTION Check for an RL file that is too small, write permission
(HP-UX), or capability (MPE/iX).
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
7207 MESSAGE OBJECT IS TOO BIG TO FIT INTO RL. (7207)
CT CAUSE Object size is too large for the RL requested.
ACTION Check for an RL file that is too small or split up object
(MPE/iX).
---------------------------------------------------------------------------------------
7400 to MESSAGE INTERNAL COMPILER ERROR.
7999
I CAUSE The compiler is in error.
ACTION Report error to your HP Service Representative.
---------------------------------------------------------------------------------------