Build 50712: Find Feature Extended to XML Terminal
Previously the user could not search for text in the XML Terminal windows by pressing Ctrl+F. This feature has now been extended to these windows.
Build 50712: XML Terminal Output Viewing
Users can now use their web browsers (or other external applications) to view the XML output that returns from the host. When the user indicates that XML output is to be viewed, the output is extracted from the XML output log that the terminal displays and is written to a temporary XML file. Then TPF/GI requests that Windows open the XML file in the default application for displaying XML. The following changes have been made:
A "Last Output" button has been added to the XML terminal window. The user can click this button to view the XML output that has arrived at the terminal most recently.
To view output other than the very last that has arrived, users can right-click the output in the XML terminal and select "View Output Message" from the popup menu.
Users can now specify an "XML Support Folder." This is the folder on their workstations where they keep their XML support files (such as schemas or style sheets) that are necessary for their XML output to display properly. It is also the folder where the temporary XML files are created to display the XML output. This folder can be specified in the TPF/GI XML preferences (right click the XML terminal and select "Properties").
An "Auto View Output" option has been added to XML preferences. If this option is set, the XML output is automatically displayed in the user's browser or other external application when the output arrives from the host.
A new preferences option allows users to specify whether temporary XML output files should overwrite each other, or whether unique file names should be used.
A new preferences option allows users to specify whether temporary XML output files should be deleted by TPF/GI when it is shutting down.
The appearance of the XML terminal window has been simplified slightly by moving some existing options to the TPF/GI XML preferences (right click the XML terminal and select "Properties").
TPF/GI product administrators can set the XML support folder and other new preference options at install time by changing the Windows Registry. For details, please see this administrator FAQ.
Build 50616
Build 50616: Find Feature Extended to Message Log & Message Capture Windows
Previously the user could not search for text in the Message Log and Message Capture windows by pressing Ctrl+F. This feature has now been extended to these windows.
Build 50616: Block Editor Windows Now Remember Positions By Block Type
The tactic for setting block editor window positions has now changed. Block editor windows will now remember their positions by block type. This includes XCOR, XCRW, XAUT, and other similar windows. There is one position remembered per "type" of window. For example, all XCOR windows share the same position, all XCRW windows share the same position, etc. The last window of a given type that is closed is the one that has its position remembered..
Build 50615
Build 50616: Trace Output Viewer Compatible with CITRIX
The trace output viewer now creates its INI file in a folder location compatible with CITRIX.
Build 50509
Build 50509: Customizable Script and EXEC for Loading Programs in TPF/GI
TPF Software has developed a PC script (written in VBScript) and a corresponding VM EXEC that can load programs in TPF/GI. The script and EXEC can be customized by each installation. They are being used by two customers already and are freely available to other customers. To receive these scripts, please contact Thiru at
.
Build 50316
Build 50316: Binary Message Support Added to Consumer Finance Terminal
Message run for the Consumer Finance Terminal emulator now supports the CMSTPFMI binary message format.
Build 50106
Build 50106: Consumer Finance Terminal Added
A Consumer Finance Terminal emulator has been added for financial customers who require that support.
Build 50106: VM Command Support Added to Consumer Finance Terminal
Message run for the Consumer Finance Terminal emulator now supports commands (prefixed with "CMSTCMD") that are sent directly to VM.
Build 50505
Build 50505: Option to Suppress "Done" Dialog Box in Message Run
Previously, when a Message Run was completed, a dialog box would always appear informing the user that the Message Run was done. This dialog box can now be suppressed in TPF/GI preferences by selecting the "Running" category and setting the "End Message Run" option.
Build 40817
Build 40817: Logs Now Simultaneously Accessible in Other Viewers
Message Run logs can now be viewed in other viewers (such as Notepad) even while they are open in TPF/GI.
Build 40705
Build 40705: Enhanced Overlay Panel Caching
Users can now specify which overlay panels are downloaded and cached by TPF/GI at startup. This allows the panels that users need most often to be immediately available.
TPF Applications that use too many resources degrade system performance.
But it is difficult to find and fix this kind of problem. Fortunately,
TRex, a new feature of TPF/GI, gives you the power you need.
It allows programmers to immediately identify which transaction,
which ECB, and even which program or function is using the most
resources.
TRex analyzes performance at several levels: the transaction level,
the ECB level, and the individual program/function level. TRex
provides a comprehensive level of information: CPU usage, memory
usage, I/O usage, tape records, pool records, program usage, core
blocks, heap space, system work blocks.
And TRex is easy to use because it's a graphical tool, with pie
charts, bar charts, and tables. Usually, you can just click part
of the picture to see more detail.
To start TRex, select Log>Transaction Recording
& Examination>User from the TPF/GI
menu bar. Once you have done that, data is being collected for
TRex. Now run the transactions necessary to collect your data.
When you are ready to analyze your data, select Log>Transaction
Recording & Examination>View from the TPF/GI menu
bar. The TRex Viewer will open.
From the TRex viewer, you can see things such as the top ECBs
used by a transaction, the top programs/functions used by an ECB,
the amount of heap used by an ECB, ECB heap usage by transaction,
and much more. Som TRex screen shots are below.
Build 40428: ScriptDialogs
Enhancements
The following enhancements have been made to the dialog boxes
that can be used with scripting.
The Dialog Object now by default focuses the first control
in the dialog box. So if the first control is (for example) a
text input, that text input will have focus.
The Dialog Object has a new FocusControl property. This will
allow you to designate a control other than the first in the
dialog box to have focus. Read
FocusControl Help .
The ProgressDialog Object now has a MsgBox method that you
can use to show message boxes that will not be covered by the
ProgressDialog. Read
ProgressDialog.MsgBox Help .
The ProgressDialog Object now has a StayOnTop property. You
can set this to True or False. You may not need to use this property
if you are content with using the ProgressDialog.MsgBox method
described above. Read
StayOnTop Help .
Build 31215
Build 31215: Unlimited
Source View Line Length
Source View will now display lines of any length.
Previously, the viewable line length was limited.
Users may now add files of type .C, .CPP, .ASSEMBLE, and .SABRE
directly to Source View. Previously, users had to add files of
type .CMSTPFCT (control files) only. The syntax highlighting used
for these and other file types is determined by new settings in
your TPF/GI Environment Preferences. See the "New Syntax Coloring
Preferences in Source View" item below.
Build 31215: Algorithm
for Matching Control and Symbol Files to Source Files
When you add a source file (e.g. "MYFILE CPP A" or "MYFILE ASSEMBLE
A") to Source View, TPF/GI needs to locate and "lock" the corresponding
control file (e.g. "MYFILE CMSTPFCT J"). To locate the control
file, TPF/GI searches your mini-disks for all files that
have the same filename as your source file but have the type "CMSTPFCT".
If only one suitable source file is found, TPF/GI will use it.
If
more
than
one suitable
control
file is found, TPF/GI will display a list of those control files
and ask you to select the one you want to use.
Similar considerations apply to "symbol" files (file extension
CMSTPFSF). TPF/GI tries to find a suitable symbol file when the
source file is of type SABR or ASSEMBLE. The same algorithm is
used as for control files. If a symbol file cannot be found, the
SABR or ASSEMBLE file can still be traced, but the Assembler expression
facility will not work.
Build 31215: New Control
File Age Warning
If TPF/GI finds itself using a control file that is older than
the source file in Source View, it will warn you with a message
box.
You can turn off this warning using a new preference. To reach
this
preference,
right-click the Source View window and select Properties; on the
General page, check or uncheck the box which reads "Warn if source
files are newer than control files."
This preference also control whether you are warned when a symbol
file (CMSTPFSF) is newer than the corresponding source file.
Build 31215: .H, .HPP,
and Other Text Files May Be Added to Source View
Any type of file containing text may now be added to Source View
for syntax-highlighted viewing. To do this, select Trace>Add Source
View Files from the TPF/GI menubar, then select
files of type.H,
.HPP, or other types. The files you selected will then appear in
Source View. The syntax highlighting used for the files is determined
by new settings in your TPF/GI Environment Preferences. See the "New
Syntax Coloring Preferences in Source View" item below.
Build 31215: Scripting
Updated to Add Source Files to Source View
The SView object in TPF/GI scripting can now be used to add source
files (e.g. "MYFILE CPP A") to Source View as well as control files
(e.g. "MYFILE CMSTPFCT A"). The two methods with the ability to
do this are SView.AddCtlFile and SView.AddSourceFile. To learn
more about these methods, do the following:
Select
Help>Scripting Help from the TPF/GI menu bar;
Click the link
"all the objects
available for scripts to use in controlling TPF/GI";
Click the "SView Object" link;
Scroll to the bottom of that topic and click the AddCtlFile
link and read that topic;
Scroll to the bottom and click the AddSourceFile link and
read that topic.
Build 31215: New Syntax
Coloring Preferences in Source
View
You can now select which file types are associated with which
types of syntax highlighting. By default, files of type .C, .CPP,
.H, and .HPP are displayed with the C/C++ Syntax Highlighter. Similarly,
.ASSEMBLE files are displayed with the Assembler Syntax highlighter,
and .SABRE files are displayed with the SabreTalk Syntax Highlighter.
You can add more file types or change syntax highlighting for types
with new preferences in TPF/GI. To reach these preferences, select
Preferences>Environment... from the TPF/GI menu bar, then select
the Source View category and the new Extensions page. Double click
a Syntax Type (Assember, C/C++, or SabreTalk) to edit the list
of file types associated with it.
Users who trace C/C++ files in Source View can now place the mouse
cursor over C/C++ expressions in their source code
to get a tooltip (hint) that displays the value of the
expression. If necessary, this-> is automatically
prepended to expressions to get them to evaluate
properly;
this
is often necessary
for member variables referenced in member functions. When an expression
evaluates to a struct or class, the value of each member of the
struct or class is displayed in the tooltip (up to one level deep).
When an expression evaluates to an array, the value of each element
in the array (up to 50) is displayed in the tooltip.
Where the mouse cursor is placed over an expression determines
what part of an expression is evaluated and its value displayed.
The
table
below
gives examples.
Placing the Mouse Here...
Displays the Value of...
(**ppstruct).arrayField[index]
^
**ppstruct
(**ppstruct).arrayField[index]
^
(**ppstruct).arrayField
(**ppstruct).arrayField[index] ^ or ^
(**ppstruct).arrayField[index]
(**ppstruct).arrayField[index]
^
index
Preferences are
available to disable tooltip expression evaluation and to change
the delay before an expression is evaluated. To reach these preferences,
right click
the Source View window and select Properties.
Build 31215: Source View
Add to Watch Feature Improved
The feature in Source View that allows variables and expressions
to be right-clicked and added to the Watch window has been enhanced.
The feature is now much smarter about determining what is and is
not a C++ expression. In addition, member variables within method
calls are now be prefixed with this-> if necessary
to get them to evaluate. Which part of an expression is right clicked
determines what is added to the Watch window. The rules for adding
expressions to the Watch window are the same as for tooltip expression
evaluation. See the table above for examples.
Build 31215: Source View,
Message Run, GIConsole, Etc. Use Mouse Wheel
Many controls in TPF/GI which formerly did not respond to the
mouse wheel now do so. Updated controls include Source View, Message
Run, the GI Console, the PrimeCRAS console, and Machine Instructions.
Build 31215: Host Open
Dialog Box Resizeable
The Host Open Dialog Box, which is used to select files on the
host for Source View and other purposes, is now resizeable. In
addition, between sessions of TPF/GI, the dialog box now remembers
its size, position, and whether it was last left in View or Detail
mode.
TPF/GI now gives better feedback that the Message Log or Message
Capture features are active. The text "(Logging)" and/or "(Capturing)"
now appears in the title bars of terminal emulator windows when
Message Log or Message Capture is turned on for those windows.
Affected windows include LOC1, LOC2, ALC1, ALC2, GI Console, and
PrimeCRAS.
In addition, Message Run, Message Log, and Message Capture now
appear on the right click menus of ALC1, ALC2, LOC1, and LOC2.
Build 31215: Delete on
Right Click Menu for Trace Program Options
After adding programs to the exclude or include sections of the
Trace Options dialog box, users can now multiselect program items
and delete them either by pressing the Delete key on the keyboard
or by right clicking and selecting the Delete menu item.
Build 31215: XML Formatted
in XML Terminals
Previously, XML input and output was not formatted for display
in the XML terminals. That meant, for example, that lengthy XML
outputs without carriage returns appeared on one line and the display
was sometimes corrupted.
With version 2.7.1, XML in the terminals is now displayed with
formatting: line breaks are inserted before and after XML tags,
and lines are indented to accentuate the XML structure. New preferences
allow this formatting to be turned on and off, and allow the amount
of indenting to be adjusted. To reach these preferences, right
click the XML1 or XML2 terminals and select Properties... from
the menu.
Build 31215: Input Lock
in XML Terminals
The XML1 and XML2 terminals now "lock" once input is sent in.
No further input can be sent in until output returns from the host.
This lock can be overridden by clicking the red lock light in the
lower left hand corner of the terminal window.
Build 31215: New "Save
Trace Output to File" Warning
If you have unchecked the option "Save Trace Output to File" in
the Environment Preferences dialog box, TPF/GI will now warn you
when you use the Trace Options dialog box to
set trace options. This is to save you from assuming that trace
is being saved to a file when it is not.
. 
