HP 3000 Manuals HP 3000 Manuals
HPDEBUG (NM) (new) The HPDEBUG intrinsic is the counterpart to the MPE V/E DEBUG intrinsic. It calls the MPE XL system debugger. You can use an optional parameter to pass debug commands you want to be automatically executed when the debugger is entered. When the HPDEBUG calls the debugger, the debugger pushes your commands onto its command stack and executes them. You pass a character array of up to 1024 characters in the cmdstr parameter. 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. For processes in jobs, process execution is resumed when the command string is exhausted. Processes run from a job will not be allowed to stop in the system debugger. If the command string does cause control to return to the calling procedure, any remaining commands are left pending on the debugger command stack to be executed the next time the debugger is called. For processes in sessions, control remains in the debugger unless you pass a CONTINUE command. If no command in the command string causes control to be returned to the calling procedure, the user will be left in the debugger as long as the process is being run from a session environment. You may have output sent to any writable ASCII file you specify. By default, output is sent to the terminal LDEV for sessions and $STDLIST for jobs. The status parameter, a 32-bit signed integer passed by reference is optional, but recommended. It indicates status in two fields. One reports the presence of errors and warnings, and the other indicates their source. If an error or warning condition is encountered, and you did not specify the status parameter, HPDEBUG causes the calling process to abort. Using the status parameter in MPE XL is analogous to using condition codes in MPE V/E. You can translate returned values with the MPE XL Intrinsics Reference Manual (32650-90028).