You have several options for customizing your session. For example, you can resize and rearrange windows, close selected windows, change session parameters, and change session panel colors. This section explains how to customize your session using these options.
The window acted upon as you customize your session is determined by one of several factors. If you specify a window name (for example, WINDOW OPEN MONITOR to open the Monitor window), that window is acted upon. If the command is cursor-oriented, such as the WINDOW SIZE command, the window containing the cursor is acted upon. If you do not specify a window name and the cursor is not in any of the windows, the window acted upon is determined by the setting of Default window under the Profile Settings panel.
Refer to the following topics for more information related to the material discussed in this topic.
To define your PF keys, use the SET PFKEY command. For example, to define the PF8 key as SCROLL DOWN PAGE, enter the following command:
SET PF8 "Down" = SCROLL DOWN PAGE ;
Use quotation marks (") for C and C++. You can use either apostrophes (') or quotation marks (") for assembler, COBOL, disassembly, and PL/I. The string set apart by the quotation marks or apostrophes (Down in this example) is the label that appears next to PF8 when you SET KEYS ON and your PF key definitions are displayed at the bottom of your screen.
Refer to the following topics for more information related to the material discussed in this topic.
You can define a symbol to represent a long character string. For example, if you have a long command that you do not want to retype several times, you can use the SET EQUATE command to equate the command to a short symbol. Afterward, Debug Tool treats the symbol as though it were the command. The following examples show various settings for using EQUATEs:
If a symbol created by a SET EQUATE command is the same as a keyword or keyword abbreviation in an HLL, the symbol takes precedence. If the symbol is already defined, the new definition replaces the old. Operands of certain commands are for environments other than the standard Debug Tool environment, and are not scanned for symbol substitution.
To change the relative layout of the physical windows, use the PANEL LAYOUT command (the PANEL keyword is optional). You can display either the Memory window or the Log window in one physical window, but you can not display both windows at the same time in separate physical windows.
The PANEL LAYOUT command displays the panel below, showing the six possible physical window layouts.
Window Layout Selection Panel
Command ===>
1 2 3
1 .-----------. 2 .-----------. 3 .-----------. Legend:
| M | | _ | _ | | _ |
|-----------| | | | | | L - Log
| S | |-----------| |-----------| M - Monitor
|-----------| | _ | | _ | _ | S - Source
| L | | | | | | E - Memory
'-----------' '-----------' '-----------' To reassign the
Source, Monitor,
4 5 6 Log, and Memory
4 .-----------. 5 .-----------. 6 .-----------. windows, type
| _ | _ | _ | | _ | _ | | _ | _ | over the current
| | | | | | | | | | settings or
| | | | |-----| | | |-----| underscores with
| | | | | _ | | | | _ | S, M, L, or E.
| | | | | | | | | |
'-----------' '-----------' '-----------'
Enter END/QUIT to return with current settings saved.
CANCEL to return without current settings saved.
Initially, the session panel uses the default window layout 1 .
Follow the instructions on the screen, then press the END PF key to save your changes and return to the main session panel in the new layout.
Refer to the following topics for more information related to the material discussed in this topic.
To close a physical window, do one of the following tasks:
When you close a physical window, the remaining windows occupy the full area of the screen.
To open a physical window, enter one of the following commands:
If you want to monitor the values of selected variables as they change during your Debug Tool session, you must display the Monitor window in a physical window. If it is not being displayed in a physical window, open a physical window as described above. The Monitor window occupies the available space according to your selected physical window layout.
If you open a physical window and the contents assigned to it are not available, the physical window is empty.
To resize physical windows, do one of the following tasks:
WINDOW SIZE 12 SOURCE
For the Memory window and the Monitor window, if you make a physical window too narrow to properly display the contents of that window, Debug Tool does not allow you to edit (by typing over) the contents of the window. If this happens, make the physical window wider.
To restore physical window sizes to their default values for the current physical window layout, enter the PANEL LAYOUT RESET command.
To toggle a window to full screen (temporarily not displaying the others), move the cursor into that window and press PF10 (ZOOM). Press PF10 to toggle back.
PF11 (ZOOM LOG) toggles the Log window in the same way, without the cursor needing to be in the Log window.
You can change the color and highlighting on your session panel to distinguish the fields on the panel. Consider highlighting such areas as the current line in the Source window, the prefix area, and the statement identifiers where breakpoints have been set.
To change the color, intensity, or highlighting of various fields of the session panel on a color terminal, use the PANEL COLORS command. When you issue this command, the panel shown below appears.
Color Selection Panel
Command ===>
Color Highlight Intensity
Title : field headers TURQ NONE HIGH
output fields GREEN NONE LOW Valid Color:
Monitor: contents TURQ REVERSE LOW White Yellow Blue
line numbers TURQ REVERSE LOW Turq Green Pink Red
Source : listing area WHITE REVERSE LOW
prefix area TURQ REVERSE LOW Valid Intensity:
suffix area YELLOW REVERSE LOW High Low
current line RED REVERSE HIGH
breakpoints GREEN NONE LOW Valid Highlight:
Log : program output TURQ NONE HIGH None Reverse
test input YELLOW NONE LOW Underline Blink
test output GREEN NONE HIGH
line numbers BLUE REVERSE HIGH Color and Highlight
Memory : information GREEN NONE LOW are valid only with
offset column WHITE NONE LOW color terminals.
address column YELLOW NONE LOW
hex data GREEN NONE LOW
character data BLUE NONE LOW
Command line WHITE NONE HIGH
Window headers GREEN REVERSE HIGH
Tofeof delimiter BLUE REVERSE HIGH
Search target RED NONE HIGH
Enter END/QUIT to return with current settings saved.
CANCEL to return without current settings saved.
PF 1:? 2:STEP 3:QUIT 4:LIST 5:FIND 6:AT/CLEAR
PF 7:UP 8:DOWN 9:GO 10:ZOOM 11:ZOOM LOG 12:RETRIEVE
Initially, the session panel areas and fields have the default color and attribute values shown above.
The usable color attributes are determined by the type of terminal you are using. If you have a monochrome terminal, you can still use highlighting and intensity attributes to distinguish fields.
To change the color and attribute settings for your Debug Tool session, enter the desired colors or attributes over the existing values of the fields you want to change. The changes you make are saved when you enter QUIT.
You can also change the colors or intensity of selected areas by issuing the equivalent SET COLOR command from the command line. Either specify the fields explicitly, or use the cursor to indicate what you want to change. Changing a color or highlight with the equivalent SET command changes the value on the Color Selection Panel.
Settings remain in effect for the entire debug session.
Refer to the following topics for more information related to the material discussed in this topic.
The PANEL PROFILE command displays the Profile Settings Panel, which contains profile settings that affect the way Debug Tool runs. This panel is shown below with the IBM-supplied initial settings.
Profile Settings Panel
Command ===>
Current Setting
---------------
Change Test Granularity STATEMENT (All,Blk,Line,Path,Stmt)
DBCS characters NO (Yes or No)
Default Listing PDS name
Default scroll amount PAGE (Page,Half,Max,Csr,Data,int)
Default window SOURCE (Log,Monitor,Source, Memory)
Execute commands YES (Yes or No)
History YES (Yes or No)
History size 100 (nonnegative integer)
Logging YES (Yes or No)
Pace of visual trace 2 (steps per second)
Refresh screen NO (Yes or No)
Rewrite interval 50 (number of output lines)
Session log size 1000 (number of retained lines)
Show log line numbers YES (Yes or No)
Show message ID numbers NO (Yes or No)
Show monitor line numbers YES (Yes or No)
Show scroll field YES (Yes or No)
Show source/listing suffix YES (Yes or No)
Show warning messages YES (Yes or No)
Test level ALL (All,Error,None)
Enter END/QUIT to return with current settings saved.
CANCEL to return without current settings saved.
You can change the settings either by typing your desired values over them, or by issuing the appropriate SET command at the command line or from within a commands file.
The profile parameters, their descriptions, and the equivalent SET commands are as follows:
A field indicating scrolling values is shown only if the screen is not large enough to show all the profile parameters at once. This field is not shown in the example panel above.
You can change the settings of these profile parameters at any time during your session. For example, you can increase the delay that occurs between the execution of each statement when you issue the STEP command by modifying the amount specified in the Pace of visual trace field at any time during your session.
To modify the profile settings for your session, enter a new value over the old value in the field you want to change. Equivalent SET commands are issued when you QUIT from the panel.
Entering the equivalent SET command changes the value on the Profile Settings panel as well.
Settings remain in effect for the entire debug session.
Refer to the following topics for more information related to the material discussed in this topic.
You can place a set of commands into a data set, called a preferences file, and then indicate that file should be used by providing its name in the preferences_file suboption of the TEST run-time string. Debug Tool reads these commands at initialization and sets up the session appropriately.
Below is an example preferences file.
SET TEST ERROR; SET DEFAULT SCROLL CSR; SET HISTORY OFF; SET MSGID ON; DESCRIBE CUS;
All of the customizations described in Customizing your full-screen session can be preserved between Debug Tool sessions by using the save and restore settings feature. See Recording how many times each source line runs for instructions.