tpfsoftware.com
> products > TPF/GI
Overview
2.4.1: Linkmap window
The new Linkmap Window allows you to see the files and functions
that make up a program. It also allows you to easily lock control
files and navigate to the point in your code where a function is
located.
There are several ways to view a linkmap:
- Method 1: Select View>Linkmap... from the TPF/GI menubar. Type
a program name into the Enter a Program Name dialog box, and click
OK.
- Method 2: Select Trace>Debug Windows>Linkmap Window from the
TPF/GI menubar. Right click the Linkmap Window and select Add
Linkmap... from the local menu.
- Method 3: When you are stopped in Source View, click the new
View Active Linkmap button located near the bottom-left corner
of the Source View Window.
Once a linkmap is displayed, you can add a control file to Source
View or navigate to a control file quickly by double clicking the
name of the file in the Linkmap Window.
Similarly, you can navigate to a function in your code by double
clicking the name of the function in the Linkmap Window. The control
file in which the function resides will be added to the Source View
if necessary, and the beginning of the function will be highlighted
in the Source View Window.
Additional Features: The Linkmap Window can display more than
one linkmap at a time. You can remove one linkmap or clear the entire
Linkmap Window by right clicking the Linkmap Window and selecting
Remove Linkmap or Clear Linkmap Window from the local menu.
Note: Function information may not be available for all files
that appear in the Linkmap Window. Additionally, it may not be possible
to add all the files in the Linkmap window to Source View.
2.4.1: Local Variables
window
An advanced new Local Variables window allows you to watch and
edit local variables in their "natural" formats--for example, you
can view char arrays as strings, ints in decimal format, and doubles
in fixed point format. Variables such as structs, arrays, and pointers
can be expanded in a tree-like fashion to reveal more detail about
their contents. Variables can be expanded to an unlimited number
of levels, so that you can investigate arrays of arrays of arrays,
for example, or structs that contain other structs. The new Local
Variables window works with C and C++ programs compiled using the
C++ compiler.
To use the new Local Variables window, do the following:
- Add a Source View control file for a program compiled with the
TEST option of the compiler;
- Select Trace>Debug Windows>Local Variables from the TPF/GI menubar.
The Local Variables window will dock with the Source View window
by default. Please see the help file for more information.
2.4.1: Visual Log (audit
trail logging)
A new Visual Log allows you to document your work by allowing
you to
- Take snapshots of TPF/GI windows
- Log selected TPF/GI events such as ECB creation and GI Console
output
- Record your comments.
To start the Visual Log, select Log>Visual Log... from the TPF/GI
menubar.
To place a snapshot of a TPF/GI window into the log, do the following:
- Make sure that the target window has focus (click the window's
title bar);
- Click the Visual Log button or press Shift+Ctrl+S.
For more informaiton, please see the TPF/GI help file.
2.4.1: Scripting
You can now write scripts to control many important functions
in TPF/GI. Here are some of the things you can do:
- Send input through the terminals--including the GI Console,
PrimeCRAS, ALC1, ALC2, LOC1, and LOC2. You also have access to
the output of the command.
- Start and stop logging in terminals.
- Start and stop message capture (recording of input) in terminals.
- Show, hide, clear, and unlock terminals.
- Run Message Run files. Message Run files are the automated
input files that can be used with ALC1, ALC2, LOC1, LOC2, and
the PrimeCRAS.
- Add control files to the Source View window.
- Execute CMS commands without submitting them through the GI
Console. You also have access to the output of the command.
- Find out which systems are activated in TPF/GI and change the
active system.
- Find out which ECBs are active and place a new ECB "in context."
- Load TPF programs.
- Run fast, run slow, step into, step over, step out, etc.
Scripts can be written in the following languages:
- VBScript (Visual Basic Script). VBScript files should have
the extension .vbs.
- JScript (Javascript). JScript files should hve the extension
.js.
- Other languages for which a scripting engine is available that
works with Microsoft's ActiveScripting.
To start using scripts, do the following:
- Select File>Scripts from the TPF/GI menubar. The Scripts window
will appear.
- Select the New button to create a new script. The Notepad program
will open to allow you to edit your new script. Be sure to save
your script before you try to run it in TPF/GI.
- To run a script, select the script in the "Available Scripts"
list of the Scripts window and click the Run button.
- If a script seems to get stuck, click the Continue button to
unstick it.
- To cancel a script, click the Abort button. (Lengthy actions
that were already set in process by the aborted script--such as
the executing of a message run file--will have to be stopped individually).
- To turn a script into a tool button, select the script in the
"Available Scripts" list and click the Make Button... button.
You can have a script that executes automatically after TPF/GI
activates systems. Name the script $activate.* where "*" is replaced
by your script file extension. If more than one file is named $activate,
only the script that is first alphabetically will be executed.
To see sample scripts, read more about scripts, and learn the
commands that are available to you, please see the TPF/GI help file.
2.4.1: Program Flow
TPF/GI's Trace Output Viewer has added a new page--called the
"Program Flow" page--that helps you visualize the flow of nested
calls from one program to another within your applications.
Like the other Trace Output Viewer pages, the Program Flow page
responds to the trace output filters and updates "live" as your
test application runs in TPF/GI.
To see the Program Flow page in action, do the following:
- Select Trace>Output from the TPF/GI menubar to display the Trace
Output Viewer;
- Click the Program Flow tab of the Trace Output Viewer;
- Return to TPF/GI and set up a trace;
- Run a transaction using TPF/GI;
- Switch back to the Trace Output Viewer and watch the Program
Flow develop.
Although watching the live updates can be fun, the real usefulness
of Program Flow is to analyze what has happened in your application
after trace is complete.
2.4.1: Repeat Tool Productivity
Enhancer
This version of TPF/GI ships with a plug-in tool called the Repeat
Tool. The Repeat Tool is a window that remembers certain actions
you have taken in TPF/GI and allows you to repeat any single action
with a simple double click.
To open the Repeat Tool window, select Tools>Repeat from the TPF/GI
menubar. If Tools>Repeat is not on your menubar, then the Repeat
Tool has not yet been installed into your copy of TPF/GI.
To install the Repeat Tool into your copy of TPF/GI:
- Use Notepad to open the file named Tools.txt in your main TPFGI
folder.
- Add the following...
drepeat.dll
...on a line by itself at the bottom of the Tools.txt file.
- Save your changes to Tools.txt.
- Restart TPF/GI.
Once the Repeat Tool window is open, please press F1 for help
on using the Repeat Tool.
2.4.1: FTP file download
TPF/GI is now using an enhanced FTP dialog to handle file downloads.
To see the new dialog box in action, select File>Download to PC...
from the TPF/GI menubar.
2.4.1: Quicker Source View
Assembler Expression menu items
You can now view Assembler expressions and DSects without passing
through the Edit Expression dialog box. In the Source View window,
- Right click the expression you want to view; the local menu
will appear.
- To immediately view the expression under your text cursor, select
the menu item "View Expression " from the
local menu.
- To immediately view the DSect associated with the expression
under your cursor, select the menu item "View DSect "
from the local menu.
- If you want to edit the expression before viewing it, select
the "Edit Expression..." menu item from the local menu.
2.4.1: Line and Column
numbers available again for ALC Logs
ALC logging can now be set to include line and column numbers.
To include line and column numbers in the ALC log, do the following:
- Right click an ALC window and select Properties from the local
menu.
- The Environment Preferences dialog box will appear, and the
preferences page for the ALC will be showing.
- Place a checkmark in the "Line and Column Numbers" checkbox.
- Select the OK or Apply button.
2.4.1: Source View remembers
docking positions
To a great extent, the Source View window now remembers which
windows were docked to it and will attempt to redock them in approximately
the same positions when you reopen the Source View window.
2.4.1: Trace Options window
remembers address stops
The Trace Options window now remembers which address stops you
have used in the past. Each address stop is listed with a checkbox
beside it. To activate an address stop, place a checkmark in the
corresponding checkbox. Options are also available to check or clear
all checkboxes.
2.4.1: Right click to close
Source View debug windows
The debug windows that normally dock with the Source View window
(callstack, local variables, breakpoints, machine instructions)
can be closed individually now. Right click the tab of the docked
window that you want to close, then select Close from the popup
menu.
2.4.1: Drop down action
changed in GI Console, Prime CRAS
Now when you select an item from a retrieve list in the GI Console
and Prime CRAS windows, the item will immediately be sent to the
host. This saves you the trouble of pressing Enter or clicking the
exclamation point button after you select the drop down item.
To override this auto send new behavior, right click the GI Console
or Prime CRAS window and select Properties from the local menu,
then uncheck the "Auto Send on Select" checkbox.
To temporarily override the auto send behavior, hold down the
Ctrl key while you select an item from the GI Console or Prime CRAS
retrieve lists.
2.4.1: Retrieve lists can
be cleared and limited
The retrieve lists in the ALC, GI Console, and Prime CRAS windows
can now be cleared. In addition, you set the maximum number of items
that each retrieve list holds.
To clear a retrieve list, do the following:
- Right click an ALC, GI Console, or Prime CRAS window and select
Properties from the local menu.
- The Environment Preferences dialog box will appear, and the
preferences page for the terminal that you clicked will be showing.
- Select the Clear Now button. Close the Environment Preferences
dialog box.
To set the maximum number of items in a retrieve list, do the
following:
- Right click an ALC, GI Console, or Prime CRAS window and select
Properties from the local menu.
- The Environment Preferences dialog box will appear, and the
preferences page for the terminal that you clicked will be showing.
- Type a maximum number of items in the box labeled "Lines to
Keep".
- Select the OK or Apply button.
2.4.1: XCOR, XFIL work
on addresses that cross word boundaries
Now in the block editor windows you can perform XCORs and XFILs
on addresses that cross word boundaries. To do this,
- Select four bytes that cross a word boundary;
- Right click your mouse inside the selected area;
- Select XCOR or XFIL from the popup menu.
2.4.1: Trace Output Viewer
printing improved
The Trace Output Viewers no longer prints context information
with each item if you have context information display turned off.
2.4.1: Exiting TPF/GI is
confirmed when ECB active
To prevent closing TPF/GI accidentally, you are now asked to confirm
your decision to exit TPF/GI if an ECB is active when you click
the "X" at the top right corner of the TPF/GI main window.
You are not asked to confirm exiting TPF/GI if there is no ECB
active because the absence of an ECB probably indicates you are
done with testing anyway.
Also, you are not asked to confirm your actions if you select
File>Exit or File>Deactivate System from the TPF/GI menubar: it
is highly unlikely that you are selecting these items accidentally.
2.4.1: Closing Machine
Instructions window now turns off machine trace
Closing the Machine Instructions window now turns off machine
instruction trace for all Source View control files. This change
brings machine instruction trace behavior in line with user expectations.
The Machine Instructions window can be closed either by clicking
the "X" at the corner of the window or (if the window is docked)
by right clicking the Machine Instructions tab and selecting Close
from the popup menu.
2.4.1: Tool buttons can
be removed by right clicking
Tool buttons and other items on TPF/GI toolbars can now be removed
with a shortcut.
To quickly remove an item from a TPF/GI toolbar, do the following:
- Click the toolbar area with your right mouse button.
- Select Remove Item From Toolbar from the local menu.
For more information about customizing toolbars, please see the
TPF/GI help file.
2.4.1: Separators available
when customizing toolbars
Separator symbols can now be placed on the TPF/GI toolbars to
help you organize your tool buttons.
To place a separator on a toolbar, do the following:
- Click the toolbar area with your right mouse button.
- Select Customize from the local menu.
- The Customize window will appear. Select the Commands tab.
- In the Commands list, you will see an item labelled "| (separator)";
drag this item from the Commands list and drop it on any toolbar.
- Close the Customize window.
For more information about customizing toolbars, please see the
TPF/GI help file.
|
