TPF Software Featuring zTPFGI for z/TPF (zTPF)
    Home    Products    Support    Services    Training    News    About Us  

Search

Advanced

 

Admin Support

  Admin Support

  Resolution/KB

  Login

  Downloads

 

End User Support

  End User Support

  Demos

 

Products

  CMSTPF

  CTFS

  GI/TERM

  Resolution/KB

  RTF

  ScriptDialogs

  SOURCE VIEW

  TPF/GI

  TPF/IDE

  T-REX

  TTFS

  zIDE

  zTPFGI

 
tpfsoftware.com > products > TPF/GI Overview

What's New in TPF/GI 2.5.1

See What's New for other versions

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.

 

 

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

Copyright © TPF Software Inc.