HP 3000 Manuals HP 3000 Manuals
Symbolic Debug Function Key Loop
A two set function key loop is available whenever you run a program with
Symbolic Debug:
Debug Edit Set
ShoDebug Listing Edit NextKeys Resume Refresh Help MainKeys
Debug Utility Set
Trace Retrace Calls NextKeys Resume At Next Clear End Run
When in the Debug function key loop, you can return to the Main function
key loop by pressing f8 in the Debug Edit Set. You can then re-enter the
Debug loop by pressing the Debug key in Main Program Set 2 (Displayed in
Symbolic Debug only).
When your program completes execution or is terminated by the END RUN
command, you will be taken from the Debug loop to the Main function key
loop.
To see all the TOOLSET/XL function key sets, turn to Chapter 2 of this
Reference Manual.
Control Y
Entering [[CONTROL]]Y when programming in COBOL returns control to
TOOLSET/XL, unless you code [[CONTROL]]Y to perform a different function.
In that case, the coded function takes priority.
For Pascal and FORTRAN programs, [[CONTROL]]Y has no effect if you are in
a construct, such as a FOR loop, that does not call a procedure or
function or hit a label of your program. Once such a call or label is
encountered, [[CONTROL]]Y returns control to TOOLSET/XL.
Process Handling
Symbolic Debug handles up to three processes simultaneously when process
handling is employed. If three processes are using Symbolic Debug, any
other processes created are run without Symbolic Debug, regardless of how
they are compiled and prepared. The user is responsible for the timing
and the interaction of his program.
MPE V based systems also have the restriction that a user process being
handled by Symbolic Debug cannot do a create process on itself (a
recursive RUN). This restriction is not true for MPE XL based systems.
Xtraps
TOOLSET/XL arms XCODETRAP, XLIBTRAP, and XSYSTRAP for user programs. If
your program terminates abnormally because of the code exception or run
time error detected in the compiler software library or system intrinsic
calls, control is returned to Symbolic Debug. An abort error message is
displayed at this time along with the currently executing calls. The
DISPLAY, RETRACE, LISTING, or CALLS command can be entered to find the
reason for a program abort. Because the state of the program is
unpredictable, a RESUME command is not allowed at this point.
If you choose to arm XCODETRAP, XLIBTRAP, or XSYSTRAP with your own trap
handlers to perform a different function, that function has priority.