MPE/iX Intrinsics Reference Manual (32650-90875)
Chapter 8 431
Command Definitions (HPMERGEEND-LOGSTATUS)
HPSETDUMP
HPSETDUMP
NM callable only.
Arms the system debugger call from a process abort.
Syntax
I32 CA
HPSETDUMP(
status,cmdstr
);
Parameters
status
32-bit signed integer (optional)
Returns the status of the HPSETDUMP call. If no errors or warnings are
encountered,
status
returns 32 bits of zero. If errors or warnings are
encountered,
status
is interpreted as two 16-bit fields.
Bits (0:16) comprise
status.info
. A negative value indicates an error
condition, and a positive value indicates a warning condition. Refer to the
MPE/iX Error Message Manual Volumes 1, 2 and 3 for a description of its
value.
Bits (16:16) comprise
status.subsys
. The value represented by these bits
defines the subsystem that set the status information. The subsystem
identifier for HPSETDUMP is 165.
cmdstr
character array (optional)
An array of characters of up to 255 characters containing the system
debugger commands. The first character in the buffer is recognized as the
delimiter. The last character in the command string must be immediately
followed by that same delimiter.
Operation Notes
The process enabling the system debugger can be the current process or any child of the
current process created after the intrinsic call. The commands are contained in a character
array, left-justified, with a delimiting character as the first and last character of the
command string.
Before a process aborts, Debug is called to execute the commands in
cmdstr
. Any
command that attempts to obtain user input causes an error when executed by Debug. If
the process that aborts is being run from a job, the process terminates after executing the
command string. If the process is being run from a session, then after the specified
command string has been executed, Debug stops to accept interactive commands with I/O
performed at the user terminal if the following conditions are met: the abort did not occur
while in system code; and the process entered the abort code through a native mode
interrupt (typically caused by arithmetic and code related traps).
Once Debug accepts interactive input, the user is free to enter any DEBUG command. The