HP 3000 Manuals HP 3000 Manuals
User Errors (UE399 - UE416) (contd.)
---------------------------------------------------------------
UE400 MESSAGE CHARACTER CONSTANT IS MISSING ENDING
CAUSE Token parsed as a character constant is missing a
trailing single quotation mark ('). This applies
to a single quotation mark followed by a single
character or equivalent, backslash sequence.
ACTION Re-enter the command enclosing the character
constant in single quotation marks (').
---------------------------------------------------------------
UE401 MESSAGE STRING CONSTANT IS MISSING ENDING "
CAUSE Token parsed as a string constant was missing a
trailing double quotation mark before the end of
the command line.
ACTION Re-enter the string with a beginning and ending
double quotation marks.
---------------------------------------------------------------
UE402 MESSAGE MACROS NESTED TOO DEEPLY
CAUSE A user specified macro has caused the evaluation of
over 20 macro definitions during its evaluation.
The debugger cannot evaluate macros nested this
deep. This error can also be caused by a recursive
macro definition.
ACTION Redefine the macro using fewer than 20 macro
definitions, or remove the recursive definition.
---------------------------------------------------------------
UE403 MESSAGE MACROS PROCESSING OVERFLOW
CAUSE While evaluating a userh specified macro, the
buffer used to hold the resulting definition
for this macro was about to overflow, and
the processing for this macro terminated
unsuccessfully.
ACTION Undefine the unnecessary macros and redefine the
macro.
---------------------------------------------------------------
UE404 MESSAGE SORRY, YOU CAN'T ACCESS A NAKED FIELD
CAUSE An attempt was made to refer to a field by name
without specifying the qualifying structure (for
example, union, record, pointer, etc.).
ACTION Use the \t display format for more information.
---------------------------------------------------------------
UE405 MESSAGE TOO MANY SUBSCRIPTS
CAUSE An attempt was made to dereference an array with
more dimensions than it was declared to have.
However, HP C does allow you to dereference
pointers in this manner.
ACTION Use the \t display format for more information.
---------------------------------------------------------------
UE407 MESSAGE INVALID FIELD ACCESS: "NAME"
CAUSE An attempt was made to do a field dereference of an
object (NAME) that was not a structure or union.
ACTION Use the \t display format to determine the
characteristics of the object (NAME).
---------------------------------------------------------------
UE408 MESSAGE NO SUCH FIELD NAME "NAME" FOR THAT RECORD
NO SUCH FIELD NAME "NAME" FOR THAT STRUCT
NO SUCH FIELD NAME "NAME" FOR THAT UNION
CAUSE Struct (union, record) did not contain a field of
that NAME.
ACTION Use the \t display format for more information.
---------------------------------------------------------------
UE411 MESSAGE OPERAND STACK OVERFLOW
CAUSE An expression was too complicated for the
expression handler to parse. A combination of more
than 15 nested parentheses and/or pending operators
may be the cause.
ACTION Re-enter the expression, using less than 15 nested
parentheses.
---------------------------------------------------------------
UE412 MESSAGE CAN'T EXECUTE CHILD PROGRAM
CAUSE The debugger could not execute the object file
given.
ACTION Check to see that the file is executable.
---------------------------------------------------------------
UE413 MESSAGE WINDOW MODE REQUIRED FOR THIS COMMAND
CAUSE The debugger was probably invoked with the -L
option.
ACTION Verify that you are using an HP terminal and rerun
the debugger without the -L option.
---------------------------------------------------------------
UE415 MESSAGE NO SUCH FIELD: "NAME"
CAUSE The simple field NAME or field list specified does
not exist.
ACTION Check the declaration for the correct field name or
field list.
---------------------------------------------------------------
UE416 MESSAGE NON-UNIQUE FIELD LIST
CAUSE The field name or field list specified does not
uniquely identify a single field.
ACTION Use a more complex field list to ensure it
identifies a single field.
---------------------------------------------------------------
UE418 MESSAGE CAN'T MIX . AND OF OPERATORS
CAUSE The field list includes both the . and of
operators.
ACTION Use only the . or of operator.
---------------------------------------------------------------
UE419 MESSAGE ONE ARRAY SUBSCRIPT EXPECTED
CAUSE The field specified is a table or one of the
field's ancestors is a table, but no array
subscript was given.
ACTION Determine which field is a table, and use the
appropriate subscript.
---------------------------------------------------------------
UE420 MESSAGE LIST OF <NUMBER> ARRAY SUBSCRIPTS EXPECTED
CAUSE The field specified is a table and/or one or more
of the field's ancestors is a table; <number>
subscripts are required, but no array subscripts
were given.
ACTION Determine which fields are tables, and use the
appropriate <number> of subscripts.
---------------------------------------------------------------
UE421 MESSAGE NOT ENOUGH ARRAY SUBSCRIPTS, EXPECTED <NUMBER>
CAUSE There are more tables among the field and its
ancestors than there were subscripts given.
ACTION Determine which fields are tables, and supply
<number> subscripts.
---------------------------------------------------------------
UE422 MESSAGE UNEXPECTED ARRAY SUBSCRIPT LIST
CAUSE Neither the field specified nor any of its
ancestors are tables, but one or more subscripts
was given.
ACTION Do not give a list of subscripts.
---------------------------------------------------------------
UE423 MESSAGE CAN'T MOVE TO A CONSTANT
CAUSE The item which is the destination of the move is a
constant.
ACTION Do not attempt to store into a constant, or look at
the declarations to determine the correct field
name.
---------------------------------------------------------------
UE424 MESSAGE CAN'T MOVE TO THAT DESTINATION
CAUSE The item which is the destination of the move is of
a type into which the debugger can not store.
ACTION Do not attempt to store into that item, or look at
the declarations to determine the correct field
name.
---------------------------------------------------------------
UE425 MESSAGE CAN'T HANDLE EDITED FIELDS AS DESTINATION
CAUSE The item which is the destination of the move is an
edited field.
ACTION None, the debugger can not currently handle edited
fields as the source or destination of a mov (move)
command.
---------------------------------------------------------------
UE426 MESSAGE CAN'T HANDLE EDITED FIELDS AS SOURCE
CAUSE The item which is the source of the move is an
edited field.
ACTION None, the debugger can not currently handle edited
fields as the source or destination of a mov (move)
command.
---------------------------------------------------------------
UE427 MESSAGE CAN'T MOVE NUMERIC FIELD TO ALPHABETIC FIELD
CAUSE The source of the move is a numeric field, while
the destination field is alphabetic.
ACTION None, moving a numeric field to an alphabetic field
is illegal.
---------------------------------------------------------------
UE428 MESSAGE CAN'T MOVE NUMERIC FIELD WITH A FRACTION TO
ALPHANUMERIC FIELD
CAUSE The source of the move is a numeric field which has
a fraction, while the destination field is
alphanumeric.
ACTION None, moving a numeric field with a fraction to an
alphanumeric field is illegal.
---------------------------------------------------------------
UE429 MESSAGE CAN'T MOVE ALPHABETIC FIELD TO NUMERIC FIELD
CAUSE The source of the move is an alphabetic field,
while the destination field is numeric.
ACTION None, moving an alphabetic field to a numeric field
is illegal.
---------------------------------------------------------------
UE430 MESSAGE CAN'T MOVE ALPHANUMERIC FIELD CONTAINING
NON-DIGIT TO NUMERIC FIELD
CAUSE The source of the move is an alphanumeric field
containing a non-digit, while the destination is
numeric.
ACTION None, moving an alphanumeric field containing a
non-digit to a numeric field is illegal.
---------------------------------------------------------------
UE431 MESSAGE INVALID SIGN IN PACKED DECIMAL NUMBER
CAUSE The packed decimal field that is either being
displayed or being used as the source of a move
contains an invalid sign field.
ACTION Use either a data field that redefines the packed
decimal field, or use the group field that contains
the packed decimal data field.
---------------------------------------------------------------
UE432 MESSAGE INVALID DIGIT IN PACKED DECIMAL NUMBER
CAUSE The packed decimal field that is either being
displayed or being used as the source of a move
contains an invalid digit.
ACTION Use either a data field that redefines the packed
decimal field, or use the group field that contains
the packed decimal data field.
---------------------------------------------------------------
UE433 MESSAGE INVALID SIGN OVERPUNCH IN DISPLAY NUMBER
CAUSE The display field that is either being displayed or
being used as the source of a move contains an
invalid sign overpunch.
ACTION Use either a data field that redefines the display
field, or use the group field that contains the
display field.
---------------------------------------------------------------
UE434 MESSAGE INVALID SEPARATE SIGN IN DISPLAY NUMBER
CAUSE The display field that is either being displayed or
being used as the source of a move contains an
invalid separate sign.
ACTION Use either a data field that redefines the display
field, or use the group field that contains the
display data field.
---------------------------------------------------------------
UE435 MESSAGE TOO MANY ARRAY SUBSCRIPTS, EXPECTED <NUMBER>
CAUSE There are less tables among the field and its
ancestors than there were subscripts.
ACTION Determine which fields are tables, and supply
<number> subscripts.
---------------------------------------------------------------
UE436 MESSAGE SUBSCRIPT NUMBER <SUBSCRIPT> OUTSIDE RANGE <LOW>
TO <HIGH>.
CAUSE Subscript number <subscript> was outside the valid
range of <low> to <high>.
ACTION Supply a value between <low> and <high>.
---------------------------------------------------------------