|The Windowing Interface|
During a debugging session, you can control the windowing interface by
|Opening and Closing Windows|
Most windows can
be opened with the
window open command and
closed with the
window close command. You cannot
use these commands to open and close the four primary windows, Message windows,
or Pop-up windows.
To be more precise,
close are actually subcommands of the
window command. The
command is used to issue a number of subcommands, all of which control the
windowing interface. Most of these subcommands can be issued from either the
Command window or a configuration file. Refer to Setting Up a Configuration File for more information about using a configuration
file to customize the windowing interface. Also see Command Directory for more information about
window command and its subcommands.
The general form for using the
window command to open a window is as
In either case, WINDOW-NAME identifies the window to be opened and can be any of the following:
|Moving, Resizing, and Zooming Windows|
With the exception of Message and Pop-up windows, all
windows can be moved with the
window move command,
resized with the
window resize command, and
zoomed with the
window zoom command. These
commands can be executed from the Command window; however, the easiest way
to accomplish these tasks is to use PF keys. By default, the following commands
are assigned to PF keys:
To move a window, perform the following steps:
To resize a window, perform the following steps:
When you zoom a window, it fills the entire display area. Other windows are hidden behind the zoomed window. To zoom a window, perform the following steps:
|Directing Commands to a Window|
Usually any output that is
generated by debugger commands is
displayed in the Log window. For example, you can use the
to the Dump window, and the
keys command to
the Keys window by using the following command prefixes:
|redirect command (>)||opens a new Print, Dump, or Keys window and directs output to it. Only the Keys window can be opened.|
|redirect command (>>)||directs output to a previously opened Print, Dump, or Keys window. If the window has not been opened, this prefix command opens a new window exactly as the > prefix does.|
The > and >> symbols are prefixed to either the
keys command. The syntax for the command does not
For example, either of the following commands directs a variable named my_variable to the Print window:
The first command opens a new Print window, and the second command reuses an open Print window.
You can open several Print or Dump windows with the
> command prefix; however, only one Keys window can be opened. Both the >
and >> command prefixes have the same effect on the
command if a Keys window is already opened: the existing window is reused.
Anytime a dedicated window is either opened or reused, it automatically becomes the top window. That is, the physical cursor is placed inside the window, which is then placed on top of the stack of windows that are currently open.
|Changing the Window Configuration|
The size, position, and display
attributes of debugger windows
can be controlled with the Config window. You can open the Config window with
window open config command and change the
display characteristics for any window at any point in your debug session.
These changes can be saved to your configuration file if you want to make
them permanent. The Config window allows you to customize the following parameters
that affect the configuration of the debugger:
Certain types of windows, such as the Print window, allow you to open several windows of that type simultaneously. However, other types of windows, such as the Log window, allow only one instance at a time. You cannot have two Log windows open simultaneously.
For windows that allow only one instance, changing configuration parameters results in that window being closed and reopened. If the change results in borders being added, the reopen fails if the resources required to display the window exceed the capabilities of the debugger. This can happen when a large number of windows are open. See Number of Open Windows for a discussion of this limitation. However, failure to reopen one of the four basic windows is severe enough for the debugger to reopen the window without a border.
For windows that allow several instances to be displayed simultaneously, such as the Print window, changing configuration parameters has no effect on windows of that type that are already open. New instances of that type of window are displayed using the new parameters.
You can use the config window to change the size or position of a window. However, information in the window may move, or the moved or resized window may appear on top of the Config window. Therefore, using PF keys is the preferred way to move or resize windows.
To save your current configuration to a file, specify the file name and type in Y after the Save: prompt on the first line of the Config window. window has complete details on the various customization parameters that are saved when the current configuration is written to a file. Those that may be set in the Config window are only a subset of those that are saved.
|Using PF Keys|
PF keys offer the fastest and easiest way to issue some
of the debugger commands in a full-screen session.(footnote 1) The default PF key command assignments are adequate for most debugging
tasks; however, you can reassign debugger commands to PF keys by using either
keys command or the Keys window.
The debugger maintains two sets of tables for key assignments, the current set and the default set. On start-up, both sets of tables are identical to the command assignments that are shown in Default PF Key Commands.
||open Help Window|
||move current window|
||dump memory contents pointed to by expression under cursor|
||none (may be used in a future release)|
||none (may be used in a future release)|
||scroll Source window up|
||scroll Source window down|
||jump to next window in stack|
||resume execution and break at next line-number hook without stepping into functions|
||resume execution and break at next hook|
||zoom current window|
||resize current window|
||close current window|
||display value of variable under cursor|
||find in the current window|
||none (may be used in a future release)|
||scroll current window up|
||scroll current window down|
||jump to previous window|
||scroll current window left|
||scroll current window right|
||jump to Command window|
You can use a configuration file to modify the command assignments to both sets of tables. After the configuration file is executed, both sets of tables are identical and contain the default assignments you have specified. See Setting Up a Configuration File for more information.
You can also change the command assignment for a PF
key outside the configuration file (sometime after starting your debugging
session). These changes affect only your current session unless you choose
to save the new configuration with the
Any of the following
commands can be used to list or modify PF key assignments. You can issue these
commands either in the configuration file or from the Command window.
keys list *.
keys list *
keys default *
keys definen "text"
You can also use the Keys window to display and change current
PF key assignments. Open the Keys window either by issuing a
window open keys command or by redirecting any of the
keys commands to a
window. This is done by prefixing the command
> or a
(See Directing Commands to a Window.)
The Keys window, shown in
The Keys Window, comprises four fields: a protected field
that identifies the keys, and three unprotected fields. The Help Key field is used to assign a key to the
help <> command, and the key
definition field is used to
assign debugger commands to the other keys. The ISPF
field is used only when running the debugger under ISPF, as described in Appendix
4, "Debugger ISPF Interface."
The Keys Window
If the height of the window is smaller than
to display all of the PF key definitions, you can view information that is
not visible by scrolling vertically using the the
window scroll down commands.
The PF19 and PF20 keys are assigned to these commands by default. You can
also use the
window zoom command, the effect
of which is shown in The Keys Window.
PF key definitions can be changed by typing over the
current definition. Blanking out (erasing) the field gives the default definition.
(When erasing a field, make sure that the field has been scrolled all the
way to the left.) Each key definition can be up to 80 characters long. The
definition field may be scrolled horizontally, using the
scroll left and
window scroll right
You can easily customize a keyboard by
creating a configuration
file that contains
keys define n "text" commands. However,
note that customized PF key definitions work only in full-screen mode. Refer
to Setting Up a Configuration File for more information about using a configuration file.
|Switching Between Full-Screen Mode and Line Mode|
At any time during a debugging session, you can switch between
full-screen mode and line mode using the
window on commands.
Top of Page
Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.