Ch 43. CM Debugger [ MPE/iX Error Messages Manual Volume III ] MPE/iX 5.0 Documentation
MPE/iX Error Messages Manual Volume III
Chapter 43 CM Debugger
(Subsystem 169)
--------------------------------------------------------------
---------------------------------------------------------------
25000 MESSAGE An internal error occurred in DEBUG/STACKDUMP
intrinsics.
CAUSE An unexpected error was encountered while
processing the command/intrinsic.
ACTION Retry the command/intrinsic. If the error
persists, record any error information that
is printed and call your Hewlett-Packard
Representative.
---------------------------------------------------------------
25001 MESSAGE The address for the STATUS parameter is invalid
or inaccessable.
CAUSE The status parameter references an undefined
address or an address to which the callers do not
have write access.
ACTION Make sure the variable was defined as a 4-byte
value, and make sure the pointer dereferences
reference valid data.
---------------------------------------------------------------
25002 MESSAGE The address for the CMDSTR parameter is invalid
or inaccessible.
CAUSE The command string parameter references an
undefined address or an address to which the
callers do not have write access.
ACTION Make sure pointer dereferences reference valid
data.
---------------------------------------------------------------
25003 MESSAGE No closing delimter was found in the CMDSTR
parameter.
CAUSE The first and last characters in the command string
are not the same.
ACTION Make sure the first and last characters are the
same. Furthermore, that character should not
appear within the body of the command string. Make
sure the string of characters is > = the maximum
size allowed.
---------------------------------------------------------------
25004 MESSAGE The address for the FILENAME parameter is invalid
or inaccessible.
CAUSE The file name parameter references an undefined
address or an address to which the callers do not
have write access.
ACTION Make sure pointer dereferences reference valid
data.
---------------------------------------------------------------
25005 MESSAGE An error was encountered when closing the file.
CAUSE FCLOSE reported an error while trying to close the
file.
ACTION Ensure the caller has file CREATE/SAVE
capabilities.
---------------------------------------------------------------
25006 MESSAGE An error was encountered when opening the file.
CAUSE FOPEN reported an error while trying to open the
passed file name. The file is exclusively opened
for writing as a FIXED, 132-byte, ASCII file with
CCTL.
ACTION Ensure that the indicated file does not already
exist; ensure there is free disk space; ensure the
caller has file CREATE/SAVE capabilities.
---------------------------------------------------------------
25007 MESSAGE The file number passed is invalid or
inaccessible.
CAUSE The file number does not correspond to an opened
file. The file number corresponds to STDIN or one
of the file numbers reserved for use by MPE/iX.
ACTION Make sure the file number corresponds to an opened
file.
---------------------------------------------------------------
25008 MESSAGE The file has the incorrect record size.
CAUSE The record size is not in the required range (for
example, from 64 to 512 bytes).
ACTION Specify a file that has a valid record size.
Remember to check for file equations that may alter
the value specified in source code.
---------------------------------------------------------------
25009 MESSAGE The file type is binary; it must be ASCII.
CAUSE The file system reported that the file was opened
as a binary file.
ACTION Open the file as an ASCII file. Be sure to check
for file equations with the same name as the file
being opened.
---------------------------------------------------------------
25010 MESSAGE Insufficient access rights; write access to the
file is required.
CAUSE The file system reported that the caller did not
have write access to the file. Either the file was
not opened for write access, or the particular
caller was not granted write access to the file.
ACTION Make sure the file was opened for write access. Be
sure to check for file equations with the same name
as the file being opened. You may have to change
file and/or group/account security or "release" the
file.
---------------------------------------------------------------
25011 MESSAGE Missing or unknown keyvalue for HPDEBUG keyword
option.
CAUSE An odd number of itemnum/item were passed. Each
itemnum must have a corresponding item.
ACTION Check the calling code to ensure that each itemnum
is paired with an item.
---------------------------------------------------------------
25012 MESSAGE Unknown HPDEBUG keyword option selector.
CAUSE One of the itemnum selectors was not recognized as
a supported itemnum.
ACTION Verify the use of correct itemnums. Make sure that
the itemnum/items are correctly paired.
---------------------------------------------------------------
25020 MESSAGE You must have PM capability to debug program
files with PM capability.
CAUSE An attempt was made to enter DEBUG for a program
that was linked/prepped with PM capability by a
user who does not have PM capability.
ACTION Link/prep the program without PM capability or
grant the user PM capability.
---------------------------------------------------------------
25021 MESSAGE You must have READ/WRITE access to a program file
to debug it.
CAUSE An attempt was made to enter DEBUG for a program
file to which the user does not have write access.
Write access validation is performed by the file
system.
ACTION Alter the file and/or group/account security so
that the user has write access to the program file.
---------------------------------------------------------------
25022 MESSAGE DEBUG could not be initialized. The debugger
request has been ignored.
CAUSE The internal DEBUG data structures could not be
allocated and/or initialized. This could be due to
a lack of disk space or a lack of some other system
resources (including DEBUGGER table space).
ACTION Verify there is sufficient free disk space for
virtual memory. Wait for the machine to become
less loaded and try again. If the error persists,
record any error information that is printed and
call your Hewlett-Packard Representative.
---------------------------------------------------------------
25023 MESSAGE Could not capture process state. The debugger
request has been ignored.
CAUSE DEBUG was unable to obtain all of the required
information about a process which is necessary to
debug it.
ACTION Retry the command/intrinsic. If the error
persists, record any error information that
is printed and call your Hewlett-Packard
Representative.
---------------------------------------------------------------
25024 MESSAGE Unknown ESCAPE while entering DEBUG. The
debugger request has been ignored.
CAUSE An unexpected error was detected by DEBUG while
trying to enter the main command processing code.
ACTION Retry the command/intrinsic. If the error
persists, record any error information that
is printed and call your Hewlett-Packard
Representative.
---------------------------------------------------------------
MPE/iX 5.0 Documentation