HP 3000 Manuals HP 3000 Manuals
User Errors (UE300 - UE416) (contd)
---------------------------------------------------------------
UE350 MESSAGE CAN'T OPEN "FILE" AS RECORD FILE
CAUSE The system failed to open the specified record
file.
ACTION Check the file path and permissions.
---------------------------------------------------------------
UE351 MESSAGE OPERATOR STACK OVERFLOW
CAUSE The 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.
---------------------------------------------------------------
UE352 MESSAGE OPERATOR STACK UNDERFLOW
CAUSE The expression handler failed. This may have been
caused by a corrupt environment or a parsing
problem.
ACTION Re-enter the expression in an alternate form, if
possible.
---------------------------------------------------------------
UE353 MESSAGE DATA TOO BIG TO PUT IN THE CHILD PROCESS
CAUSE A string constant or other data was larger than the
total size of the buffer in xdbend.lib.sys
ACTION Re-enter a smaller string constant or data item, if
applicable.
---------------------------------------------------------------
UE354 MESSAGE CAN'T STORE INTO A CONSTANT
CAUSE The left side of an assignment statement was found
to be a constant; it cannot be modified.
ACTION Use the \t display format for information on the
assigned variable.
---------------------------------------------------------------
UE355 MESSAGE CAN'T SET ANY REGISTERS
CAUSE Setting registers incorrectly is inherently
dangerous and can lead to complete lockup of the
operating system.
ACTION Only use the g (goto) command to make limited, safe
changes to the program counter ($pc). Avoid
changing register values directly.
---------------------------------------------------------------
UE356 MESSAGE STRING TOO LONG FOR ASSIGNMENT
CAUSE An attempt was made to assign a string over 1024
bytes to an HP FORTRAN 77 CHAR*, HP Pascal string,
or HP Pascal packed array of char.
ACTION Use the \t display format for type information of
the string assigning to, and re-enter the command
with an appropriately sized string.
---------------------------------------------------------------
UE357 MESSAGE INCOMPATIBLE OPERANDS FOR STRING ASSIGNMENT
CAUSE An attempt was made to assign to an HP FORTRAN 77
CHAR*, HP Pascal string, or HP Pascal packed array
of char, something other than an HP FORTRAN 77
CHAR*, HP Pascal string, HP Pascal packed array of
char, a string constant, or a character constant.
ACTION Re-enter the command with a proper assignment.
---------------------------------------------------------------
UE358 MESSAGE CAN'T DEREFERENCE A CONSTANT
CAUSE An attempt was made to dereference a constant.
ACTION Use the \t format to find the type of the object to
be displayed.
---------------------------------------------------------------
UE359 MESSAGE CAN'T TAKE THE ADDRESS OF A CONSTANT
CAN'T TAKE THE ADDRESS OF A REGISTER
CAUSE Operand of &, $addr, or addr operator is marked as
a constant or register type.
ACTION Use the \t display format to find the type of the
object being displayed.
---------------------------------------------------------------
UE360 MESSAGE POSTFIX "++" NOT SUPPORTED
POSTFIX "--" NOT SUPPORTED
PREFIX "++" NOT SUPPORTED
PREFIX "--" NOT SUPPORTED
CAUSE An attempt was made to use an unsupported operator.
For example, ++n, --n, n++, n--.
ACTION Make sure a space is used between a + or - operator
and a unary sign (for example 2- -5). +=1 or -=1
can be used to increment or decrement,
respectively.
---------------------------------------------------------------
UE361 MESSAGE INVALID COMBINATION OF OPERATOR AND OPERANDS
CAUSE The debugger tried to perform a numeric operation
on one or more non-numeric operands.
ACTION Re-enter the command with a valid expression.
---------------------------------------------------------------
UE362 MESSAGE UNKNOWN OPERATOR (NUM)
CAUSE An unsupported operator, with internal value NUM,
was pushed on the operator stack.
ACTION Re-enter the command using an operator known to the
current language or reset $lang to the language in
which the operator is valid.
---------------------------------------------------------------
UE363 MESSAGE MISFORMED EXPRESSION
CAUSE An expression was entered incorrectly. The
debugger attempts to show you where the error was
detected in the command line. The error token
might be one token beyond the actual error.
ACTION Re-enter the expression using operators and
operands known to the current language or reset
$lang to the language in which the operator or
operand is valid.
---------------------------------------------------------------
UE364 MESSAGE TWO OPERATORS IN A ROW
CAUSE The expression handler detected an improper
construct in an expression.
ACTION Re-enter the command with a valid expression.
---------------------------------------------------------------
UE365 MESSAGE FORTRAN VARIABLE NOT PURE ARRAY
CAUSE An attempt was made to dereference an array that
had pointer or function qualifiers, while the
current language was set to FORTRAN, which does not
support them.
ACTION Try again with $lang set to a different language.
---------------------------------------------------------------
UE366 MESSAGE INVALID REAL NUMBER
CAUSE The specified numeric expression was not a real
number.
ACTION See the appropriate language reference manual, or
Table 4-3 in this manual, for the format of real
numbers.
---------------------------------------------------------------
UE367 MESSAGE MISFORMED GLOBAL NAME
CAUSE Colon ( : ) must be followed by a variable name
(string).
ACTION Refer to the "Entering Variable Names" section in
the HP Symbolic Debugger User's Reference Manual
(31508-90003) to see how to specify global
variables.
---------------------------------------------------------------
UE368 MESSAGE UNKNOWN GLOBAL
CAUSE The variable specified with :var was not a
recognized global variable name.
ACTION Use the lg (list globals) command to list all known
global variables.
---------------------------------------------------------------
UE369 MESSAGE NEED A ":" AFTER THE NUMBER
CAUSE Proc:depth:var was entered incompletely (:var was
missing).
ACTION Refer to the l (list) command listing in the HP
Symbolic Debugger User's Reference Manual
(31508-90003) to see a list of variables.
---------------------------------------------------------------
UE370 MESSAGE INVALID LOCAL NAME
CAUSE Proc[:depth]:var was entered incorrectly. Var must
be a valid variable name in the specified
procedure, at the specified depth.
---------------------------------------------------------------
UE371 MESSAGE UNKNOWN LOCAL
CAUSE The variable specified with proc[:depth]:var was
not a recognized local variable of proc.
ACTION Use the l (list) command to list all known local
variables of the current proc, or use the T (Trace)
command to list the locals, variables, and
procedures on the stack.
---------------------------------------------------------------
UE372 MESSAGE PROCEDURE "PROC" NOT FOUND AT STACK DEPTH NUM
CAUSE In proc:depth, the procedure PROC was not on the
child process stack at depth NUM. Either the stack
was not that deep, or the procedure at that depth
was not PROC.
ACTION Use the t (trace) command to list the stack.
---------------------------------------------------------------
UE373 MESSAGE UNKNOWN LANGUAGE
CAUSE An attempt was made to modify the current language
by assigning an invalid language designator to the
special variable $lang. The valid language
designators are COBOL, Pascal, FORTRAN, C, and
default.
ACTION Re-enter the command with COBOL, Pascal, FORTRAN,
C, or default as the designator.
---------------------------------------------------------------
UE374 MESSAGE LOCAL IS NOT ACTIVE
CAUSE A local variable name was recognized but the
procedure it belongs to was not currently active on
the child process stack.
ACTION Re-enter the command after its procedure has been
called.
---------------------------------------------------------------
UE375 MESSAGE TWO OPERANDS IN A ROW
CAUSE The expression handler detected an improper
construct in an expression.
ACTION Refer to the "Entering Expressions" section in the
HP Symbolic Debugger User's Reference Manual
(31508-90003).
---------------------------------------------------------------
UE376 MESSAGE NO SOURCE FILE FOR CURRENT ADDRESS
CAUSE The given child process address did not map to a
known, debuggable source file.
ACTION Use the lf (list files) command to view the files
the debugger recognizes, and re-enter the command
with an appropriate address expression.
---------------------------------------------------------------
UE377 MESSAGE NO SEARCH PATTERN
CAUSE The search command (/, ?, n (next), or N (Next))
was given without a search pattern (in the case of
n (next) and N (Next), the previous search command
/ or ? was provided without a pattern).
ACTION Refer to the individual command listings in the HP
Symbolic Debugger User's Reference Manual
(31508-90003) for more information about search
commands.
---------------------------------------------------------------
UE378 MESSAGE NO MATCH FOR "TEXT"
CAUSE The search pattern (TEXT) for the /, ?, n, (next)
or N (Next) command was not found in the current
viewing file. Note that the pattern is a literal,
not a regular expression.
ACTION Try another pattern or view another file and search
for the pattern.
---------------------------------------------------------------
UE379 MESSAGE INVALID DISPLAY FORMAT "TEXT"
CAUSE Given the data display format, or a portion of it,
the TEXT contained invalid syntax.
ACTION Refer to Table 4-3 in the HP Symbolic Debugger
User's Reference Manual (31508-90003) to see valid
data viewing formats.
---------------------------------------------------------------
UE381 MESSAGE LENGTH NOT ALLOWED WITH "TEXT" FORMAT
CAUSE Given the data display format, the TEXT did not
allow the data length specification because it is
irrelevant or implicit in the format.
ACTION Refer to the HP Symbolic Debugger User's Reference
Manual (31508-90003) to see valid data viewing
formats.
---------------------------------------------------------------
UE382 MESSAGE THIS DOES NOT APPEAR TO BE A STRUCT OR UNION
THIS DOES NOT APPEAR TO BE A RECORD OR UNION
CAUSE The debugger tried and failed to dump the contents
of a data object that was not a struct, union, or
record.
ACTION Use the \t display format for more information.
---------------------------------------------------------------
UE385 MESSAGE NO CURRENT PROCEDURE
CAUSE The debugger tried to list locals for the current
viewing procedure when the procedure was undefined.
ACTION Use the lp (list procedures) command to list all
the debuggable procedures.
---------------------------------------------------------------
UE386 MESSAGE NO SUCH PROCEDURE "PROC"
CAUSE An attempt to list locals of a non-existent, or
non-debuggable procedure PROC was made.
ACTION Use the lp (list procedures) command to list all
known debuggable procedures.
---------------------------------------------------------------
UE387 MESSAGE UNRECOGNIZED "l" COMMAND
CAUSE The l (list) command was given with a second part
that was neither a known procedure name, nor a
valid option.
ACTION Refer to the l (list) command listing in the HP
Symbolic Debugger User's Reference Manual
(31508-90003) for more information.
---------------------------------------------------------------
UE388 MESSAGE ":" MUST BE FOLLOWED BY A DEPTH
CAUSE Proc:depth was entered incorrectly.
ACTION Refer to the individual command listings in the HP
Symbolic Debugger User's Reference Manual
(31508-90003) for more information.
---------------------------------------------------------------
UE390 MESSAGE EXITING COMMAND LINE PROCEDURE CALL
CAUSE The command line procedure call environment
terminated for an unusual reason, such as a break
was encountered during program execution, or an
error was reached before the procedure was called.
ACTION Check the procedure call for errors and re-enter
the command line procedure call.
---------------------------------------------------------------
UE391 MESSAGE CAN'T PASS MORE THAN NUM ARGUMENTS TO CALLED
PROCEDURE
CAUSE A large limit (NUM) exists on how many parameters
can be passed to a procedure called from the
command line.
ACTION Check the number of parameters for the procedure
you are attemping to call. If the limit (NUM) is
less than the number of parameters in the
procedure, that procedure cannot be called from the
command line.
---------------------------------------------------------------
UE392 MESSAGE ARGUMENT LIST TOO LONG
CAUSE Arguments to the run command exceeded 1024 bytes.
ACTION Re-enter the run command with fewer arguments.
---------------------------------------------------------------
UE393 MESSAGE CAN'T GOTO A LINE OUTSIDE OF THE CURRENT
PROCEDURE
CAUSE The line number given to the g (goto) command was
not an executable source line in the top procedure
or paragraph on the child process stack. This is
not always the same as the current viewing
procedure.
ACTION Re-enter the g (goto) command with a line number
within the procedure or paragraph on the top of the
child process stack.
---------------------------------------------------------------
UE396 MESSAGE UNKNOWN NAME
CAUSE An unrecognized string (procedure or variable name)
was encountered in an expression.
ACTION Use the lp (list procedures), lg (list globals), l
(list), lc (list commons), or ll (list labels)
command to list all known procedures, globals,
locals, commons, or labels.
---------------------------------------------------------------
UE398 MESSAGE MISFORMED HEX NUMBER
CAUSE 0x or 0X was given without digits following.
ACTION Re-enter the command with a valid hexadecimal
number.
---------------------------------------------------------------
UE399 MESSAGE MISFORMED OCTAL NUMBER
CAUSE An octal number starting with 0 contains an 8 or 9.
ACTION Re-enter the command with the correct octal number.
---------------------------------------------------------------