What's New in TPF/GI 2.6.1

Version 2.6.1

Overview of Build 30807: Performance Enhancements

Although build 30807 contains many bug fixes and enhancements, its main improvements come in the area of performance. By reducing the amount of call stack information sent to the client machine, Build 30807 sends significantly less data to the workstation during a run to breakpoint in Source View trace. Even more significantly, the server now compresses all large messages before transmitting them to the workstation. As a result, users should see a significant performance enhancement when using this build of TPF/GI.

2.6.1 build 30807: Added Message Compression

TPF/GI now compresses data transmitted from the server to your workstation. Messages from the server are compressed if they exceed a certain size. In practice, you should see a 5-to-1 or greater reduction in the amount of data transmitted, along with a corresponding performance boost, as you use TPF/GI.

2.6.1 build 30807: Enhanced Callstack Message Efficiency

In previous builds of TPF/GI, some users who debugged C++ programs using Source View trace encountered "pacing" delays. This happened primarily when sections of user code executed a large number call-returns. The server-based part of TPF/GI was notifying the workstation of every call and return, transmitting such a large amount of data that the server needed to be "paced" (or have its rate of processing regulated). This made tracing take longer than necessary.

Build 30807 drastically reduces the number of call-return messages sent to the workstation when you "run fast" to a breakpoint in TPF/GI Source View trace. The improvement is so great that "pacing" problems should be eliminated when running fast to a breakpoint.

2.6.1 build 30807: Improved GI/FTP Reliability

In the past, TPF/GI users experienced some problems when using GI/FTP to download files from the host. However, the compatibility between GI/FTP and TPF/GI has now been vastly improved.

To access GI/FTP from TPF/GI, select File>Download to PC... from the TPF/GI menu bar.

You can also browse and download host files by selecting File>Host Files from the TPF/GI menu bar. However, this command is limited to CMS mini-disk files, whereas GI/FTP can download any file reachable by FTP.

2.6.1 build 30807: New Trace Output Viewer "Show Only Matching" Tool Button

The Trace Output Viewer contains filters that limit which trace output items are displayed. You can elect either to view all items (with a checkmark beside matching items) or to view only matching items (so that all non-matching items are hidden). A new tool button allows this view choice to be made from the toolbar as well as from the menu bar.

2.6.1 build 30807: XML Terminal Help and Display Preferences

A full help topic has been added to the TPF/GI help file for the XML terminals. To access this help file, open an XML terminal and hit the F1 key on your keyboard.

In addition, the ability to control XML terminal font size and colors through preferences has been added. The XML Terminal topic in the TPF/GI help file describes how to set these preferences.

2.6.1 build 30807: XML Terminals Now "Scriptable"

The XML Terminals in TPF/GI can now be controlled through scripting. Two new scripting objects have been added, XML1 and XML2. Using these objects, the XML terminals can be opened, hidden, connected, and disconnected; in addition, messages can be sent and received, and a list of daemons can be acquired. To learn how to use these scripting objects, see the "XML1, XML2 Objects" topic in the TPF/GI help file.

2.6.1 build 30807: Improved Timeout Processing

When the host takes a long time to respond to a message from the client, a timeout can occur. This is a more common occurance for users working from home. TPF/GI timeout processing has been modified so that no information is lost even though the timeout occurs. If a timeout occurs and you choose to wait until the host does respond, you should be able to proceed normally.

The timeout processing was also changed so that TPF/GI is smarter about deciding that a timeout has occurred. If the host is in the process of responding, a timeout will not be called.

In addition, the information given about timeouts has improved: now, when a timeout does occur, the number of seconds the timeout has lasted is displayed in the TPF/GI status line. This display is updated every five seconds until the host responds.

2.6.1 build 30807: Citrix Compatibility Improved

In order to be compatible with Citrix, TPF/GI was changed to use dynamic rather than hard-coded ports.

In addition, a problem was resolved that kept TPF/GI from appearing in the task bar or Task Manager under Citrix.

2.6.1 build 30807: Find Feature Works with Message Run

When users have a file open in the Message Run window, they can now use Ctrl+F to search the contents of that file.

2.6.1 build 30807: Easy to Open Saved Data with Trace Output Viewer

The Trace Output Viewer now makes it easy for users to reopen trace files that they have saved using File>Save A Copy.

Two changes were made:

1. When the user selects File>Open... from the Trace Output Viewer menu bar, the Open dialog box now opens to the directory last used by the program.
2. The File menu now has a list of most recently used files. Select one of these files to reopen it easily.

2.6.1 build 30807: Windows Open In View After Resolution Change

Occasionally, users will use TPF/GI with a large screen resolution, shut TPF/GI down, change to a smaller screen resolution, then reopen TPF/GI. In the past, this has meant that some TPF/GI windows appeared out of sight to the right or the bottom of the visible area of the screen.

TPF/GI windows now appear in the visible area of the screen when opened.

2.6.1 build 30807: Progress Dialog Box Available for Scripting

Scripts written for TPF/GI can now display a dialog box with a progress meter or a "busy" animation, along with a text message. Scripts can update the progress meter and the text message as they progress through the steps of a process. To read about this new ProgressDialog, select Help>Script Dialogs from the TPF/GI menu bar.

2.6.1 build 30807: Source View Problems Corrected

Miscellaneous Source View problems corrected include

• Bit fields that are one bit wide were displayed with a negative value;
• Source View occasionaly flickered excessively during scrolling and returned unexpectedly to the top of the file;
• The most recently built Source View file was not used if it took less than one minute to recompile;
• A step on a BACKC after running fast executed a run fast instead of a step;
• The Pause button was not enabled during a Run-No-Trace.

These and other problems have been fixed.

2.6.1 build 30205: "Make a Suggestion" feature

A new menu item under the Help menu allows users to suggest enhancements to TPF/GI. To reach the menu item, select Help>Make a Suggestion from the TPF/GI menubar.

2.6.1: Added new XML terminal Type for testing TCP/IP transactions

Two new terminals now allow programmers to test TCP/IP transactions by sending XML messages into TPF and receiving XML output. XML terminals are available only if your installation has configured TCP/IP for use in TPF. Please see your administrator to find out if XML is configured at your shop and what advanced options may be available to you.

2.6.1: Added ability to print Trace Statistics

Programmers can now print the the contents of the trace statistics window. The currently selected tab is printed, and macro and instruction tabs are printed in html table format.

2.6.1: Added Heap Display to the ECB

The graphical ECB window now has a Heap page that allows programmers to browse through the currently allocated heap items for that ECB. For each heap block item, the Heap page shows

• the program (module),
• the program member (file),
• the block address,
• the allocated size, and
• the value of the first eight bytes in the block.

Displaying the program and program member for each item are recent enhancements.

If programmers leave the Heap page showing while they step through code, the page will not only show which heap blocks are allocated, it will also keep programmers informed of

• which allocations are new since the last time they stepped,
• which blocks have been recently released.

For more information, see the Ecb Heap Page topic in the TPF/GI help.

2.6.1: Added VTAPE Mount support to Tape Mount Dialog

TPF/GI now supports virtual tapes as part of the mounting process. A customizable $GIVTAPE EXEC allows the user to return a list of available VTAPE VOLSERS to the user for selection. When mounting scratch tapes, users can enter additional VTAPE command parameters as necessary.

Please see the Mount Tape Dialog Box topic in the TPF/GI help file for help on mounting virtual tapes.

2.6.1: Added TPF/DF macros to the Macro Groups in the Trace Options Dialog

A new checkbox on the Macro Options page of the Trace Options dialog box now allows users to select all TPF/DF macros as a group.

2.6.1: New CINFC table menu item

A new menu item makes it easy to view and edit the CINFC table from TPF/GI. Select View>Tables>CINFC Table from the TPF/GI menubar.

2.6.1: Saving Information During Catastrophic Situations

When the host goes catastrophic, all log and capture windows now save their contents to the user's Work directory. Message boxes inform the user of where the files have been saved. In addition, the Catastrophic dialog box now has a "Save..." button so that users can save the entire contents of the GI Console even if they haven't been logging.

2.6.1: Input Substitution During Message Run

The GI/Substitution feature has been added to Message Run in TPF/GI. This feature parses any file comments in VISTA and INPUT files, searching for substitution values. It then substitutes the values into the input before sending the input to the host. Substitutable values include dates and times.

A new tool button on the Message Run window displays the Message Substitution Dialog Box.

A help file is available at http://www.tpfsoftware.com/webhelp/products/gisubstitute/GISubstitute.htm.

2.6.1: New Program Status dialog box

A new Program Status dialog box allows users to view and edit the properties of TPF programs. This new dialog box can be reached by right clicking a program name and selecting Program Status from the local menu. Program names can be right clicked in most places that they appear in TPF/GI. This includes block editor windows, ECB windows (including the program nesting area), the Linkmap window, machine trace windows, and program database windows.

Alternatively, users can select VIew>Program>Status... from the TPF/GI menu bar.

Access to the XPGM feature for program editing has also been included on many more right click menus.

2.6.1: Kanji support added to the ALC

The ALC terminal windows can now display Kanji characters.

2.6.1: Multi-selection in Trace Output Viewer

Items in the Trace Output Viewer can now be multi-selected and copied to the Windows Clipboard.

2.6.1: Dimensions of LOC (3270 terminal) can be "unconstrained"

Normally, the LOC (and ALC) terminals can assume only those dimensions that leave the least blank space around the text in the terminal area. A new preference allows the LOC window to be any size. This preference is on the General page of the LOC (3270) category in the Environment Preferences Dialog Box.

2.6.1: ALC font can be set

We are testing how to allow the font used by the ALC terminals to be set. Currently, there are two test methods of doing this. First, a new Environment preference allows the font to be set for the ALC terminals. The new preference is on the Display Fonts page page of the Fonts category in the Envrionment Preferences Dialog Box. Second, the ALC terminal can be right clicked and a Select Font... item can be chosen from the local menu.

In the future, one or both of these font-setting methods may be modified or removed.

This change is being tested primarily as a way to allow customers who use Kanji to select a better font for Kanji display. If possible, select a TrueType font (such as Courier New); this will allow the most variety of window sizes.

2.6.1: Current heap statistics displayed

Statistics on the current heap usage can now be viewed by selecting Trace>View Statistics and selecting the Memory/Heap Usage page.

2.6.1: Horizontal scrollbar added to the Trace Output viewer

The Trace Output viewer now displays a horizontal scrollbar when necessary.

2.6.1: TPF PUT level displayed

After connecting to a system, you can view the current TPF PUT level in the TPF/GI About box.

2.6.1: Data event control block (DECB) area shown only if supported

The DECB area of the ECB window is now shown only if the current TPF PUT level supports DECBs.

2.6.1: Data event control block (DECB) support changes

There have been changes to DECB support, so if you have not read this item recently, please read it again.

The data entry control block (DECB) feature, new in version 2.6.1, allows programmers to view, edit, create, and delete DECBs.

Access to DECBs is provided through the graphical page of TPF/GI’s ECB window, which has been redesigned. Manipulations of DECB levels are carried out through user-friendly, drag-and-drop or right-click actions.

By default, users must click the new View DECB area button (described below) to display or hide the DECB area of the ECB window. However, a new preference option does exist that will cause the DECB area to be automatically displayed whenever DECBs are present and hidden whenever DECBs are not present. To change this preference, right click the ECB window, select Properties from the local menu, then check or uncheck the box labeled "Automatically show DECB area if DECBs are present."

The new View DECB Area tool button is at the bottom of the DECB window. Depress this button to display the DECB area. Undepress this button to hide the DECB area. This new tool button also indicates whether DECBs are present.

The View DECB Area Button
Appearance	Meaning
	DECBs are not present.
	DECBs are present.

If your preferences are to automatically show the DECB area and DECBs are present, the View DECB Area tool button will be disabled.

Data entry control block support is available only if you are running with TPF DECB support enabled. This requires TPF PUT 13 and higher, and also requires the use of C++ rather than C. To read more about TPF/GI's DECB feature, read the newsletter article on the TPF Software web site. To read more about IBM's DECB feature, see an IBM presentation on the web.

2.6.1: New preference for ECB Data Level and DECB hints

By default, a detailed hint is shown whenever the mouse cursor hovers over a data level or DECB in an ECB window. This hint can be turned off by unchecking a preference checkbox. Right click the ECB window, select Properties, then uncheck the box labeled, "Descriptive hints for data levels and DECBs."

2.6.1: New button to hide ECB trace information area

A new tool button, ,at the bottom of the ECB window allows the ECB trace information section to be hidden or displayed.

2.6.1: New button to hide ECB data levels

A new tool button,, at the bottom of the ECB window allows the ECB data level area to be hidden or displayed.

2.6.1: Version 2.6.1 best with host version 1.2.1 and higher

TPF/GI 2.6.1 contains enhancements which make it best when run with host version 1.2.1 and higher.

2.6.1: New Watch Expressions Window displays ALL variables!

The Watch Expression window, new in version 2.6.1, allows C and C++ programmers to view and edit expressions involving all variables, including non-local variables. This means that now all variables in C and C++ programs can be examined and modified using TPF/GI. This includes all extern and static variables.

The Watch Expression window boasts all the human-friendly features of the Variables window, but it adds the ability to watch individual elements in an array and individual members in struct or class. For more information, see the TPF/GI help file and the newsletter article on the TPF Software web site.

2.6.1: Local Variables window enhanced, now named "Variables"

The window formerly known as the "Local Variables Window" has been enhanced and renamed the "Variables Window." The Variables Window has two pages. The "Locals" page displays all local variables. The "this" page displays the value of the hidden this variable when it is available.

2.6.1: New Trace Statistics Window shows charts, stats, graphs

The Trace Statistics window, new in version 2.6.1, allows users to see charts, graphs, and statistics detailing information about program and file I/O, pool usage, memory and heap usage, macros, and instructions.

To use the Trace Statistics window, first set up trace options, then run a transacation. When you select Trace>View Statistics from the TPF/GI menubar, information generated by the transaction and trace options will be available.

To update the Trace Statistics window, close the window and reopen it.

For more information, consult the TPF/GI help file and a newsletter article on the TPF Software web site.

2.6.1: New XCOR scripting objects

A new XCOR object allows user scripts to get and set core on the host. A versatile new data object allows for easy handling of core and other data. To learn about the XCOR object, do the following:

1. Select Help>Scripting Help from the TPF/GI menu bar;
2. The TPF/GI help file window will appear; click the hyperlinked text which reads "...all the objects available...";
3. A new page containing a table of available scripting objects will appear; links to both the XCOR object and the data object are available here.
   

2.6.1: Microsoft Script Debugger now automatically enabled

Scripts that you write for TPF/GI can be debugged using the Microsoft Script Debugger. Some recent versions of the Script Debugger have been designed by Microsoft so that the debugger window does not automatically appear when there is a script problem (a registry setting controls this behavior). To change this behavior, every time TPF/GI 2.6.1 starts up it will now override this Microsoft registry setting so that you can debug your scripts using the Script Debugger.

For information about how to determine whether the Script Debugger is installed on your machine and how to use it, please see http://www.tpfsoftware.com/support/scriptdbg.phtml.

If you don't want TPF/GI to enable the Script Debugger every time it starts up, you can set the value of the following registry entry to '0': HKEY_CURRENT_USER\Software\TPF Software\TPFGI\Preferences\Scripts\EnableScriptDebugger.

If you want to restore the Microsoft registry setting for the Script Debugger to its default value of 0, change the following setting: HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings\JITDebug.

2.6.1: Users can now supply script templates

Users can now supply their own script templates to be used when they create new scripts from within TPF/GI. Users can supply one template per script extension.

To supply a template for a script extension, do the following:

1. Create a text file that contains the initial script code you want to use;
2. Name the text file $template.xxx, where xxx is the extension of the script type that you want to supply a template for;
3. Place the file in the TPF/GI scripts folder.

For example, to provide a template for scripts written in VBScript, create a text file named $template.vbs and place it in the TPF/GI scripts folder. To provide a template for scripts written in JScript, create a text file named $template.js and place it in the TPF/GI scripts folder.

The TPF/GI scripts folder can be accessed by selecting File>Scripts from the TPF/GI menu bar. You can drag files from Windows Explorer and drop them in the file window on the TPF/GI scripts window.

2.6.1: Trace Output view search filter items now sorted

The TPF/GI Trace Output viewer has a search filter that contains the names of all programs and all ECB IDs that were encountered during the trace. The program names and ECB IDs in this filter are now automatically sorted in alphabetical order.

2.6.1: Visual Logs can now be appended to

Users can now reopen previously saved Visual logs and append new log information to them.

2.6.1: View Fixed Files dialog box enhanced

The View Fixed Files dialog box now accepts either equate names or record IDs.

Version 2.5.1

2.5.1: Terminal input and output in Visual Log uses fixed font

The Visual Log now records terminal input and output messages in a fixed (monospaced) font. The fixed font will make character columns align with each other in the Visual Log the way that they do in the TPF/GI terminal emulators.

2.5.1: Global panels downloaded

TPF/GI now downloads globals panels at startup if the globals panels have changed on the server.

2.5.1: Script dialog boxes

TPF Software has launched a new product, ScriptDialogs, to provide dialog boxes for user scripts in TPF/GI and other TPF Software products. ScriptDialogs ships with TPF/GI version 2.5.1, and can also be downloaded to work with version 2.4.1. For more information, please see the ScriptDialogs web page.

2.5.1: Scripts can send attention identifiers to 3270

User scripts can now send attention identifiers (AIDs) to the 3270 terminal emulators.

The Input method of the LOC1 and LOC2 objects has been extended to accept AID codes in one of two ways: either as an optional third argument or as single argument.

To send input to the LOC1 or LOC2 objects with an AID other than Enter, please let the following VBScript example be your guide.

  ' Send in "ZDSYS" with an AID of F1
  ' "error_return" is a variable for returning
  ' any errors to the caller
  Loc1.Input "zdsys", error_return, &HF1

To send in an AID such as PA1, PA2, PA3, or Clear, use the following example as your guide.

  ' Send in a PA1 to the LOC2
  ' Note that 0x6C is the AID for PA1
  Loc2.Input &H6C

Note: Rather than using the Input method to send in a Clear AID, use the Clear method instead.

For further details about this enhancement please see the Using Scripts section of the TPF/GI help file. Search the TPF/GI help file for the text "Attention Identifier" or "AID."

2.5.1: Two scripting objects have briefer aliases

Users can now use briefer aliases for the PrimeCRAS and GIConsole objects in their scripts. The PrimeCRAS object may be abbreviated "PRC"; the GIConsole object may be abbreviated "GIC."

2.5.1: Input method is now default for terminal scripting objects

The terminal objects in TPF/GI scripting now have the Input method as their default method. This means that users may now optionally omit the word "Input" the dot that precedes it. Terminal scripting objects include ALC1, ALC2, LOC1, LOC2, GIConsole, and PrimeCRAS.

For example, scripts may send input to the ALC1 object by either of the following:

ALC1.Input "ZDSYS"
ALC1 "ZDSYS"

2.5.1: GI/FTP and SFS

GI/FTP, the TPF Software module for downloading files using the FTP protocol, now reads and writes SFS subdirectories.

2.5.1: LOC colors can be set

The colors used by the local 3270 terminal emulators can now be set by the user. This new feature has been added so that users with special vision needs can set the colors they desire; but setting selected background colors to hues other than black will help all programmers see exactly where protected and unprotected fields begin and end.

To set the LOC colors, do the following:

1. Right click the LOC terminal and select Properties.
2. Place a check in the checkbox labeled "Use user-defined colors."
3. Click the Edit User Colors button.
4. On the LOC colors page, select the element you would like to color, then use the left and right mouse buttons to set the foreground and background colors for the element by clicking the color boxes. For the extended color attributes, only foreground colors can be set.
5. Click OK or Apply to accept the changes you have made

2.5.1: More windows can print

The ability to print has been added to many more windows, including Tape Status, Hold Table, MECB, Trace Options, Event Status, and the Local Database Status. To print one of these windows, first click the title bar of the window to give it focus, then select File>Print from the TPF/GI menubar.

2.5.1: Right click to print from block editor windows

Users have always had the ability to print the contents of block editor windows by selecting File>Print from the TPF/GI menubar. Now users can right click block editor windows and select "Print" from the popup menu.

Block editor windows include the XCOR, XFIL, XCRW, XREG, XREC, XAUT, and Globals windows.

2.5.1: Printer font can be set

Users can now select the font and the font size for printing the contents of TPF/GI windows. To specify this information, select Preferences>Environment from the TPF/GI menubar, then select the Font page.

There are two types of printer fonts: fixed (or monospace) and proportional. Terminal windows, Source View, and block editor windows such as XCOR use the fixed font to print. List windows such as Tapes and Local Database use the proportional font to print.

2.5.1: XCRW on right click of ECB register

Right clicking an ECB register now allows you to do an XCRW if the register is being used to address a data level. The XCRW window will open at the correct displacement, allowing you to view and edit the data level immediately.

2.5.1: XCOR on right click of local variable

Users can now do an XCOR on the address of a local variable. Right click a local variable in the Source View Local Variables window and select "XCOR on ..." to do the XCOR.

2.5.1: GIConsole and PrimeCRAS can be cleared

The GIConsole and PrimeCRAS terminals can now be cleared. Right click either terminal and select "Clear" from the popup menu to clear them.

2.5.1: Now handles large volumes of incoming data

TPF/GI now handles large volumes of incoming data from the host. Great amounts of data can be generated by tracing. TPF/GI can now "pace" the flow of data so that it can be handled.

When too much data is generated by the host, TPF/GI displays an error message, then immediately prompts the host to begin sending data again. The result is that all the incoming data is handled without requiring users to click an OK button on a dialog box.

To stop the flow of data, users should press the Pause button on the TPF/GI toolbar. If the Pause button is unresponsive, users should try closing (not minimizing) the Trace Output Window to see if the situation improves.

2.5.1: New Source View C/C++ Debugging Preference

When users right click the Source View window, a local menu is displayed with commands that let users view and edit variables. These commands fall into two groups: the "old" group, representing the old-style way of debugging C/C++ variables; and the "new" group. The old-style group consists of commands such as Add a Watch, Edit Variable, Edit as Pointer, Static Variables, and Parm Variables. The new-style group currently consists of the command Local Variables. A new preference item helps users select the new-style C/C++ debugging by disabling the old-style commands. To change this preference, right click the Source View window and select Properties, then look for the combo box under the "C/C++ Debugging" heading.

Version 2.4.1

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:

1. Add a Source View control file for a program compiled with the TEST option of the compiler;
2. 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:

1. Make sure that the target window has focus (click the window's title bar);
2. 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:

1. Select File>Scripts from the TPF/GI menubar. The Scripts window will appear.
2. 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.
3. To run a script, select the script in the "Available Scripts" list of the Scripts window and click the Run button.
4. If a script seems to get stuck, click the Continue button to unstick it.
5. 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).
6. 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:

1. Select Trace>Output from the TPF/GI menubar to display the Trace Output Viewer;
2. Click the Program Flow tab of the Trace Output Viewer;
3. Return to TPF/GI and set up a trace;
4. Run a transaction using TPF/GI;
5. 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:

1. Use Notepad to open the file named Tools.txt in your main TPFGI folder.
2. Add the following...
drepeat.dll
...on a line by itself at the bottom of the Tools.txt file.

3. Save your changes to Tools.txt.
4. 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,

1. Right click the expression you want to view; the local menu will appear.
2. To immediately view the expression under your text cursor, select the menu item "View Expression " from the local menu.
3. To immediately view the DSect associated with the expression under your cursor, select the menu item "View DSect " from the local menu.
4. 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:

1. Right click an ALC window and select Properties from the local menu.
2. The Environment Preferences dialog box will appear, and the preferences page for the ALC will be showing.
3. Place a checkmark in the "Line and Column Numbers" checkbox.
4. 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:

1. Right click an ALC, GI Console, or Prime CRAS window and select Properties from the local menu.
2. The Environment Preferences dialog box will appear, and the preferences page for the terminal that you clicked will be showing.
3. 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:

1. Right click an ALC, GI Console, or Prime CRAS window and select Properties from the local menu.
2. The Environment Preferences dialog box will appear, and the preferences page for the terminal that you clicked will be showing.
3. Type a maximum number of items in the box labeled "Lines to Keep".
4. 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,

1. Select four bytes that cross a word boundary;
2. Right click your mouse inside the selected area;
3. 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:

1. Click the toolbar area with your right mouse button.
2. 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:

1. Click the toolbar area with your right mouse button.
2. Select Customize from the local menu.
3. The Customize window will appear. Select the Commands tab.
4. In the Commands list, you will see an item labelled "| (separator)"; drag this item from the Commands list and drop it on any toolbar.
5. Close the Customize window.

For more information about customizing toolbars, please see the TPF/GI help file.

Version 2.3.1

2.3.1: Programs can be excluded from trace

The program selection for macro and instruction trace has been completely redesigned to allow the programmer to specify not only programs to include in testing, but also programs to exclude from testing.

You can find these improvements in the Trace Options Window: select Trace>Programs from the TPF/GI menubar.

The Programs area of the Trace Options Window now has two main "tabs" that look like buttons: one tab is labelled "Include" and the other "Exclude." Clicking the Include tab will reveal the program include list as well as buttons that allow you to modify the include list. Clicking the Exclude tab will reveal the program exclude list as well as buttons that allow you to modify the exclude list.

To add programs to either list, you can click the Add Programs button. To remove programs from either list, you can highlight the program entry and press the Delete key, or you can click the Clear List or None buttons, depending on which list you are modifying.

For example, suppose you want to trace all programs that begin with "C", but exclude programs that begin with "CV". To do this, take the following steps:

1. Click the Include tab in the Programs area of the Trace Options Window.
2. Click the Add Programs button.
3. In the Add Programs dialog box, type the text "C***" and press OK.
4. Click the Exclude tab in the Programs area of the Trace Options Window.
5. Click the Add Programs button.
6. In the Add Programs dialog box, type the text "CV**" and press OK.
7. Click the OK or the Apply button in the Trace Options Window.

For more detailed instructions, open the Trace Options Window and press F1 for context-sensitive help.

2.3.1: Step Count and Step Set Count Commands

The new Step Count command allows you to step ahead a given number of instructions or macros. For this command to operate properly, you must be stopped in non-Source View trace, and either your macro trace or your instruction trace must be set with the RUN option. Once you select the Step Count command, TPF/GI will run until the specified number of instructions or macros have been executed, or until the trace stops for another reason.

For example, if you are tracing all instructions with the RUN option and all macros with the NORUN option, selecting the Step Count command will step forward the given number of instructions or until the first macro executes. Trace data about the instructions and macros that executed will appear in the machine instructions panel of the ECB window. Information for up to 500 trace entries can appear in the ECB machine instructions window. If you stepped ahead more than 500 entries, use the Trace>Output command to view the additional trace information.

The Step Set Count command first displays a dialog box that allows you to set the number of instructions or macros to step foward before you step. On the other hand, the Step Count command does not show you a dialog box; instead, it steps forward immediately, using for its count the last value that you typed in when you used the Step Set Count command.

From the menubar, to use the Step Count command: select Run>Step Count>Step N Times.

From the menubar, to use the Step Set Count command: select Run>Step Count>Step Set Count....

From the toolbar, to use the Step Count command: click the left part of the following button:

From the toolbar, to use the Step Set Count command: click the right part of the following button:

2.3.1: Visible Carriage Returns in ALC

The ALC terminal emulator now has the ability to display visible carriage returns. In addition, you can select the display character and colors that represent the carriage return.

To turn carriage returns on, take the following steps:

1. Click the ALC terminal with your right mouse button;
2. Select the Properties menu item;
3. The Environment preferences dialog box will appear; select a display character in the Display Character drop-down box;
4. Select the Ok or Apply button.

To set the carriage return color, take the following steps:

1. Click the ALC terminal with your right mouse button;
2. Select the Properties menu item;
3. The Environment preferences dialog box will appear; go to the Other Colors category;
4. Click the Terminal Control Characters element;
5. Left- and right-click the color boxes to select a foreground and background color;
6. Check and uncheck the Text Style check boxes to select a text style.
7. Select the Ok or Apply button.

To turn carriage returns off, take the following steps:

1. Click the ALC terminal with your right mouse button;
2. Select the Properties menu item;
3. The Environment preferences dialog box will appear; select "None" in the Display Character drop-down box;
4. Select the Ok or Apply button.

2.3.1: 3270 Extended Attributes

The LOC 3270 emulator now supports extended attributes. The enhancements include support for the Start Field Extended (SFE), Modify Field (MF), and Set Attribute (SA) orders.

At this time, extended attribute support includes foreground and background colors and underlining. Reverse video and blink are not yet supported.

As a result of these recent enhancements, the LOC terminal colors currently cannot be adjusted from the Environment Preferences dialog box. A future version of TPF/GI may add this feature.

2.3.1: Password Security Enhancements

To increase security, password support in TPF/GI is now handled by a centralized password object located in the APPMAN DLL. Users' ID's and passwords can still be modified from TPF/GI.

2.3.1: ALC Terminal Log Format is Briefer

The ALC terminal now logs I/O in a brief format. Previously, the entire input and output screens were logged; now only the new input and new output is placed in the logs.

Version 2.2.1

2.2.1: New, improved help file

The TPF/GI help file has been completely rewritten. It now includes a detailed help topic for every command and for nearly every window in the application. The new help file is based on the new Microsoft HTML Help system, which is friendlier than the old WinHelp system, and which offers increased opportunities for help over the Web.

2.2.1: Press F1 for context-sensitive help from most windows; press Ctrl+F1 from ALC, LOC

Most TPF/GI windows now feature "context-sensitive" help. From most windows, simply press F1 (the PF1 key) and a help topic will appear that explains the window that has focus. Because the ALC and LOC windows may remap the F1 key, from the ALC and LOC windows press Ctrl+F1 for context-sensitive help.

If you use Internet Explorer 3.x, you may find that TPF/GI's new help file uses a new window each time it is opened. Upgrade to IE4 or IE5 to solve this problem, or close the help file windows each time you are done with them to work around the problem.

2.2.1: Assembler Expression Facility available for SABRE-Talk

Thanks in great part to support code written by Jeff Longwell, we have been able to extend the "assembler" expression facility so that it can be used from SABRE-Talk programs at Worldspan. To learn more about the assembler expression facility, read the "Assembler expressions can be edited" topic in this file, and select Help>Contents from the TPF/GI menubar and read the Assembler Expression Facility Overview topic in the TPF/GI help file.

2.2.1: Source View right mouse button handling improved

In the Source View Window, it used to take two mouse clicks to place the text cursor on a word and cause a local menu to pop up: first, to place the text cursor on a word, you had to click the left mouse button on the word; then, to cause the local menu to pop up, you had to click the right mouse button anywhere on the control file.

Now you can simply click the right mouse button on the word: the text cursor will move to that spot and the local menu will pop up at the same time.

The exception to this behavior happens when you have text selected and you click the right mouse button inside the selection: the local menu will still pop up, but the text cursor will not move. This behavior has been designed so that you can select an assembler expression that you want to edit and then click the expression with the right mouse button without unselecting the text.

If you select text and then click the right mouse button outside the selection, the selection will be removed, the text cursor will be placed at the clicked spot, and the local menu will pop up. This behavior is also by conscious design.

2.2.1: Block editor bookmarks can be saved, reloaded, printed

The bookmark feature available in the block editor windows (windows such as XVAR, XREC, XFIL, XREG, and so forth) has been improved. Bookmarks can now be saved to a file and reloaded from the file, and bookmarks are now printed when you print a block editor block. With these improvements, bookmarks offer real opportunities for enhanced documentation and marking of bugs.

To learn more about bookmarks, read the Using Bookmarks topic in the new TPF/GI help file.

2.2.1: Network trace can be activated from Help menu

Sometimes you need to gather information about the operation of TPF/GI in order to report a possible bug. In this case, your administrator may ask you to repeat the steps that created the bug while running a "network trace." A "network trace" records messages sent between TPF/GI and the host. Information about these messages is placed in two files; when these two files are sent to TPF Software, we can study them to help discover the problem.

To begin running a network trace, select Help>Network Trace from the TPF/GI menubar. The GIConnex network trace window will appear and TPF/GI will begin recording all subsequent messages to two files-one file with an MLG extension and one file with an IDX extension.

The network trace ends when you uncheck the Enable Network Trace checkbox on the network trace window or when you shut down TPF/GI. When a network trace ends, a dialog box will appear offering you a chance to copy or delete the files that were created by the network trace. This is also a good opportunity to note what the filenames are in case you need to send them to your administrator.

2.2.1: System activation message can be customized

A new button in the Activate Systems dialog allows users to customize the message that is sent to the host to activate a system. Normally, the single word Activate is sent to the host; now, using this new button, you can send additional options after the word Activate.

CMSTPF Administrator Notes:

This feature has been added to allow a programmer to concatenate a (project) local database, prior to the activation of CMSTPF. Whatever text is specified in the customize button, is sent to the CMSTPFGI Exec (for the Activate option), as optional parameters. The Administrator can update the CMSTPFGI Exec to examine the options (Customized data), and link/concatenate a database, prior to activating CMSTPFGI.

For programmers (end users) to include additional activation options, follow the steps below.

1. Run TPF/GI without any systems activated. If you have TPF/GI set up to automatically activate systems when you run it, you will need to cancel system activation the first time you run it and then run TPF/GI again.
2. Select File>Activate Sytems... from the TPF/GI menubar.
3. In the Activate Systems dialog box, put a checkmark in the Activate checkbox that is associated with the system you want to activate.
4. The Customize button will appear to the right of the Activate checkbox; click the customize button.
5. A dialog box entitled Customize the Activate Command will appear. In this dialog, type the options you want and click OK.
6. Back in the Activate Systems dialog box, the options you typed will appear to the right of the Customize button.
7. Click OK in the Activate Systems dialog box to activate the system.

Any options you type will be placed after the word Activate, a space, an open parenthesis, and another space. For example, if the option text you type is "concatenate J," the following activation message will be sent to the host:

ACTIVATE ( concatenate J

Please note: if you activate multiple systems, only the first system activated will receive additional options.

2.2.1: "More" button in About box aids bug reporting

A new button in the TPF/GI About box helps users discover and report important information about their copy of TPF/GI. To reach this button, select Help>About from the TPF/GI menubar, then click the new More button. A second dialog box will pop up, displaying detailed information about the program. From this second dialog box, users can print the information, copy it to the clipboard, or save it to a file.

Version 2.2.0

2.2.0: Assembler expressions can be edited

TPFGI now lets you watch and edit assembler expressions while you debug in Source View.

To use this powerful new facility, follow these steps:

1. Begin tracing an assembler control file in source view.
2. While you are stopped in the control file, use the left mouse button to click a DSECT field name or an assembler expression.
3. Now use the right mouse button to click anywhere in the Source View window.
4. A local menu will pop up; select the "Edit Expression" item from this local menu.
5. The "Edit Assembler Expression" dialog will appear showing the assembler expression you have selected; fine-tune the assembler expression by editing its text.
6. Once you have the assembler expression to your liking, click the Edit Expression button to view and edit the value of the expression.
7. Alternatively, if the assembler expression contains a field name, you can also view and edit the entire DSECT by clicking the Edit button.

Here are some examples of expressions that the "Edit Assembler Expression" dialog understands:

1. A field name by itself: EBW001
2. A field name plus or minus a displacement: EBW001+3 or EBW001-3
3. A field name with a length override: EBW001(16)
4. A field name with an additional register displacement: EBW001(R13) or EBW001(,R13)
5. A combination of 1 through 4 above: EBW001+3(16,R13) or EBW(16,R13) or EBW001+3(16)
6. A combination of 1 through 4 above, with a literal displacement replacing the field name: 8 or 8(16) or 8(R13) or 8(16,R13)
7. A DSECT name by itself: EB0EB
8. A register name by itself: R13 or RG13 or REG13 or RLD
9. The name of an EQUATE that is known to the control file: CXSGHE

Assembler expressions must be in scope in order to be evaluated. "In scope" means that any DSECT or field involved in the expression is valid at the line in the control file where you are stopped.

2.2.0: Trace Store now supported graphically

You can now control the Trace Store facility through the graphical user interface. To set and review Trace Store options graphically, select Trace>Trace Store from the TPFGI menubar.

2.2.0: Trace options now easy to save and restore

Two new menu items let you save your trace options and restore them again easily. To save your trace options, select Trace>Save from the TPFGI menubar. You can now safely make minor (or major) changes to the options. To restore your trace options to the last saved state, simply select Trace>Restore from the TPFGI menubar. Restoring trace options will cause the Trace Options dialog to display.

2.2.0: ENTNC Program Facility

You can now issue the ENTNC command in order to enter-no-return to a program. To issue the command, select Run>ENTNC from the TPFGI menubar. A dialog will appear requesting the program name.

2.2.0: MECB window easier to use

The MECB window now contains two separate buttons for the suspend and resume functions. This use of two buttons avoids the confusion of a single button toggling between "Suspend" and "Resume."

2.2.0: ENTER key applies block editor changes

Hitting the ENTER key will now apply any changes you have made after editing an ECB window or one of the other block editor windows such as XCOR and XFIL. The changes will be applied only for the overlay panel that has focus.

Version 2.1.0

2.1.0: Systems can be activated and initialized in one step

The Activate and Initialize Systems dialog boxes have been combined. This means that you now can activate and initialize multiple systems in one step. To reach this newly combined dialog box, select File>Activate Systems from the TPF/GI menu bar.

Configuration of the local database can also be done from this Activate Systems dialog box-or from a new Configure Local Databases dialog box (see below).

2.1.0: Local databases can be configured from a new dialog box

To reach the new Configure Local Databases dialog, select Preferences>Configure Local Databases from the TPF/GI menubar. Please note that the configuration done in this dialog is "off-line"; this means that the changes you make to a database configuration do not take effect until the next time you initialize/activate that system.

2.1.0: Systems can be activated automatically when TPF/GI starts

You can choose to have TPF/GI activate and initialize systems automatically when it starts up. This can be done in either of two places

• In the Activate Systems dialog box
• In the Program Options dialog box.

To use the Activate Systems dialog box, select File>Activate Systems from the TPF/GI menubar, then put a check in the box labelled "Perform these actions every time TPF/GI starts."

To use the Program Options dialog box, select Preferences>Program from the menubar, then click the "Other" tab, and put a check in the box labelled "Automatically activate when TPF/GI starts."

2.1.0: Message Run scripts can run in "no-display" mode

You can now run a message run script without having input or output appear in the terminal window. In addition to slightly faster running times, this new "no-display" mode allows input messages of any size to be given to the ALC window without wrap-around problems.

To reach no-display mode for a terminal, do the following:

1. Open Message Run by clicking the message-run button in the terminal.
2. In the Message Run window, drop down the mode list and select "No-Display Mode."

2.1.0: Informative communication status colors reinstated

You can now keep informed of TPF/GI's communication status by watching the leftmost status panel at the bottom of the main form. When this panel is blue, TPF/GI is ready to receive your input. When this panel is red, TPF/GI is contacting the host. When this panel is green, TPF/GI is executing a TPF transaction, and can be interrupted, by depressing the Pause button.

Note: A very long period of red may mean that your connection has been broken or some other serious error has occurred.

2.1.0: The Trace Output window has been enhanced

The Trace Output window has been moved to a separate application and improved. The window now consumes fewer resources, lets you browse through larger Trace Output, and offers enhanced view options and search abilities. You can still reach this window by selecting Trace>Output from the TPFGI menubar.

2.1.0: A new preferences page lets you control Trace Output

TPFGI now gives you greater control over your Trace Output files. To find the new Trace Output file options, select Preferences>Environment from the TPFGI menubar, then scroll down to the "Trace" page. Here you can choose whether to save Trace Output to a file, indicate the maximum size for the Trace Output file, and clear the Trace Output file.

2.1.0: The Record Hold Table can be monitored and edited

To monitor the record hold table, select View>Tables>Record Hold Table from the TPFGI menubar. From the resulting MHold window, you can hold records, release records, and edit the associated ECB for a file address being held.

2.1.0: The Event Table can be monitored and edited

To monitor the event table, select View>Tables>Event Table from the TPFGI menubar. From the resulting MEvent window, you can timeout events, post events, dequeue events, and edit the ECB associated with an event.

2.1.0: General Data Sets can be viewed and edited

To display, mount and unload General Data Sets, select View>General Data Sets from the TPF/GI menubar.

2.1.0: The Trace Store command can be issued

To issue the trace store command, select Trace>Store from the TPFGI menubar.

2.1.0: A new preferences page lets you change your ID and password

To change your VM User ID and password, select Preferences>Environment from the TPFGI menubar. Changes made to the VM User Id and password do not take effect until the next activation of TPFGI.

This feature enables programmers to change the User Id or Password directly from the TPF/GI preference menu.

2.1.0: The installation protects passwords and reuses directories

The install program now hides passwords while they are being entered. In addition, if a previous version of TPFGI is already installed, previously defined directories will be reused, and the User Id won't be requested again.

First time installers will be requested to enter their VM User Id and password.

2.1.0: Database initialization messages can be viewed

A new window now displays the unsolicited messages that the host sends to TPFGI to report on the success or failure of database initialization and other issues. You can view this window at any time by selecting View>Unsolicited Message Log from the TPFGI menubar. These messages are also saved to a text file named UNSOLMSG.LOG in your GIUSER folder.

Version 2.0.1

2.0.1: Toolbars can be customized and undocked

You can now change which buttons appear on TPF/GI toolbars. You can also cause the toolbars to float in empty space or "dock" on the TPF/GI main window (docked is the default state). Since this feature is so new, brief examples are included below.

Toolbar Example 1. How to add a Help Contents button to a toolbar:

1. Select Preferences>Toolbars from the TPF/GI menu bar.
2. The Customize dialog box will appear. Click the Commands tab on the Customize dialog.
3. Click the "Help" category in the left-hand list of the Customize dialog.
4. Drag the "Contents" item from the Commands list of the Customize dialog to any existing toolbar.

Toolbar Example 2. How to remove a button from a toolbar.

1. Select Preferences>Toolbars from the TPF/GI menu bar.
2. The Customize dialog box will appear. You are now in "customize-the-toolbar" mode.
3. Move your mouse to any existing toolbar (in other words, do not move your mouse to the Customize dialog box; instead, move your mouse directly to an existing toolbar that already has buttons).
4. Drag a tool button from the toolbar and drop it into empty space.

Toolbar Example 3. How to create a new toolbar.

1. Select Preferences>Toolbars from the menu bar.
2. The Customize dialog box will appear. Click the "New" button on the customize dialog.
3. Type a name for the new toolbar and press Enter. The new toolbar will appear at a small size and floating in space.
4. Populate the new toolbar with buttons by following Toolbar Example 1 above.

Toolbar Example 4. How to undock a toolbar (make it float).

1. Place the mouse cursor over the handle at the left-hand end of the docked toolbar.
2. Depress and hold down the left mouse button and move the mouse cursor downward off the TPF/GI main window.
3. Release the left mouse button.

Toolbar Example 5. How to dock a toolbar (stop it from floating).

1. Place the mouse cursor over the handle at the left-hand end of the floating toolbar.
2. Depress and hold down the left mouse button and move the mouse cursor over the TPF/GI main window.
3. Release the left mouse button.

2.0.1: Debug windows can dock with Source View

The Machine Instructions, Breakpoints, Call Stack, and Watch windows all can dock in tabbed form at the bottom of the Source View window. They can also be dragged away to float separately. They can also be docked with each other separately from Source View.

New preference checkboxes help control the docking behavior of these debug windows. To reach these checkboxes, right click the Source View window and select preferences.

2.0.1: Block editor windows can dock together

In order to save screen space, block editor windows of the same general type now dock together automatically using tabs. For example, XCOR windows dock with other XCOR windows, and XFIL windows dock with other XFIL windows. To undock a block editor window, grab its tab and drag it away to a new screen position.

2.0.1: Several windows are more space efficient

The block editor, PrimeCRAS and GI Console windows now use space more efficiently, allowing you to see more data and less empty gray space. For the block editor windows, the OK, Apply, and Cancel buttons have been shrunk down and moved to the left-hand bottom corner of the window. If you prefer to use the keyboard, you can still press Enter to OK changes to the window and Escape to cancel changes.

2.0.1: Block editor windows offer new chaining options

A new button on most block editor windows allows you to customize the way the window chains forward and backward. You can find this button on most block editor windows at the top of the scrollbar, between the forward- and backward-chain buttons. Depress this button to cause any forward or backward chains to appear in new windows. Un-depress this button cause any forward or backward chains to appear in the same window, replacing the data that was previously there.

2.0.1: Block editor windows can be split into two editable views

A new button near the bottom left corner of block editor windows allows them to be split into two editable views of the same data. For example, you can edit the top and bottom of a core block at the same time, or drag data from one position to another easily.

2.0.1: An optional file mask dialog fine tunes the file open dialog

An optional file mask dialog allows you to preselect the range of files that the TPF/GI host open dialog will display. This dialog can be turned off by unchecking a checkbox on the file mask dialog itself or by unchecking a checkbox in the Host Communications preferences dialog. To reach this second checkbox, select Preferences>Program from the TPF/GI menu bar, then click the Options tab.

2.0.1: Globals Areas can be displayed and edited

To display globals areas, select View>Globals from the TPF/GI menubar, then select Globals Area 1 through 4.

Home   |   Products   |   Support   |   Services   |   Training   |   News   |   About Us   |   Contact Us   |   Search

Copyright © TPF Software Inc.