The Status window displays status information.
It is one of the four primary windows. The other primary windows are Source,
Log, and Command. By default, the Status window is displayed on the top line
without a border. Like all the other primary windows, the Command window is
always open, even when it is obscured by an overlaid window.
The Status window displays information about the current
status of your debugging session. This information is displayed in the following
fields:
-
Help:
-
identifies the PF key that is assigned as
the help key. Pressing the help key opens the Help window to display cards
from the help system. You can use the Keys window to change the help key assignment.
-
reason for entering the debugger
-
is displayed in the second field from the
left. In the above display,
Step
is displayed
because control was transferred from the executing program to the debugger
as the result of a debugger step
command.
-
run scope
-
is displayed in the third field from the
left. In Status Window the run scope is located at the entry hook for the READIN function. This is
also shown by the highlighted line in the Source window. Run scope is the
location in your code at which control was transferred to the debugger. Run
scope is identified by function name and either line number, or, in the case
of function calls, the side of the call on which the run scope is located:
calls, entry, or return.
-
command scope
-
is displayed in the fourth field from the
left. In Status Window the command scope is located in line 24 of the
main
function. Certain
commands, such as break
,
goto
, and runto
, use command scope to determine default function and
section names. Command scope is identified in the same manner as run scope.
Changing command scope The
scope
command can be used to change command scope. However,
if you have more than one function in your calling sequence, you can move
the cursor into the Status window and use the PF19 or PF20 keys to change
command scope. The window scroll < > up
or window scroll < > down
commands are assigned
to these keys by default. The PF19 key causes the run scope to move up in
the calling sequence, and the PF20 key causes the run scope to move down in
the calling sequence.