Category:Debugger Release Notes

From m204wiki
Revision as of 14:17, 1 June 2023 by Ekern (talk | contribs)
Jump to navigation Jump to search

This section contains brief descriptions of the features added in each "build" of the Debugger Client. You can determine the current build number by selecting the About option of the Help menu.

Build: 69  (April 2022)

TN3270 Debugger:

When used with Model 204 version 7.7 or higher, support the TN3270 DEBUG WAIT command via:

  • Execution>Connect to online... menu item and dialog

Subroutine/method context for source lines and variable value traces is available:

  • Requires M204 version 7.8 or higher
  • When execution stops for a breakpoint, runtime error, return from daemon, $WEB_FORM_DONE, "until value =" satisfied, or completion of READ SCREEN, additional information is displayed in the status area: The routine or method being executed is identified, along with its type (subroutine, method, local function, etc)
  • When you right click on a program line, the context menu item "Procedure Information" has been renamed to "Line Information". If "Line Information" is selected, the display now identifies which routine or method contains the  line.  The same change has been made to the context menu in the Execution Trace display
  • When a value trace is run, each line of the value trace (in the Execution Tab) identifies the subroutine or method that changed the value  
  • Added routineName.%var syntax to Value button/valueDisplay command to view variables along a call stack (by context).

Execution Trace improvements:

  • Added 'Show In Source Context' menu to Execution Trace lines to show them in source context

HELP command options were added:

  • help connecting
  • help workers
  • help list

Client commands were added:

  • shell runs a program or opens a DOS box

Debugger macro &&functions were added:

Debugger macro improvements:

  • Allow &&functions to be used as arguments to other &&functions.
  • Allow &&functions to be used as arguments to evaluate

Audit trail control:

Added <auditLines> to debuggerConfig.xml to control number of audit lines kept in the audit tab.

Build: 68  (November 2018) 

This build was strictly bug fixes, and logging improvements.  No new functionality was added.

Build: 67  (05 July 2017) 

Naming and limiting the number of daily Client log files (see step 6) In the Client configuration file, in addition to invoking automatic creation of a new log file on a daily basis, you can now specify how many days worth of previous logs to retain. The new daily log is always named log.txt; the names of previous daily logs include their creation dates.

Configuring the location for the Debugger documentation files You can relocate and optionally rename the installed defaults of the Debugger Client Help file, its PDF representation, or both.

Build: 66  (03 April 2017)  

In the Client configuration, you can specify automatic creation (see step 6) of a new log file on a daily basis to control growth of the log. You can also turn logging off.

Build: 65  (01 September 2016)  

Added &&buildNumber function.

Made errors that might occur in connecting to server more visible via a message box.

Improves error reporting on MINDEBCL violations from the mainframe.

Build: 64  (07 October 2015) 

Added "jandeb_" prefix to all generated JavaScript function names in generated Proxy Auto Config (PAC) files.

Support Microsoft IPV6 extensions in existing PAC files (FindProxyForURLEx function).

Send Client version information to the mainframe: the build and tag number are reported in the MSIR.1077 message.


Build: 63  (06 July 2015) 

Support procedures running on daemons for Run Until and White or Black List processing.

Support object expansion for JSON class objects.

The Preferences window IE Mode options (newPac and mergedPac) are enhanced to support HTTP URLs as well as file URLs. The options invoke automatic creation and maintenance of Proxy Auto Config (PAC) files, which designate the only host URLs that the Debugger Client will handle requests for as a proxy server for the IE and Chrome browsers.

The Client may now use HTTP to upload generated PAC files to the HTTP server specified in the Client's configuration file.

Added the httpPacURL element to the debuggerConfig.xml file to identify the HTTP server configured to accept and serve PAC files.  

Macro and command changes:

  • Updated setIEMode command with option http to support HTTP PAC files.
  • Updated showIE command to display URL information for HTTP PAC files.
  • Added retryHttpPac command to simplify testing and setting up of HTTP PAC files.
  • Added &&currentPacFile function to return the URL of the current PAC file in use.
  • Removed the superseded ieAuto option from setPreference command.

Other changes:

  • The Sirius Debugger product name is changed to TN3270 Debugger.

Build: 62  (10 December 2013) 

These are the principal changes to the Debugger Client since the previous build:

Physical changes and additions to the Client user interface:

The new IE Options area and IE Mode drop down menu replace the former Web Browser Options area and Automatically Maintain IE proxy settings option. In addition, IE Mode options are available to invoke automatic creation and maintenance of Proxy Auto Config (PAC) files, which designate the only host URLs the Debugger Client will handle requests for as a proxy server.  

  • The Proc Selection page now has Black List filtering to accompany the already existing White List filtering, and your filtering selection now persists over runs of the Client.

Macro and command changes:

New commands:

  • generatePac command restricts the Debugger Client's role as proxy server to handling only Internet Explorer requests for hosts (onlines) specified in debuggerConfig.xml.
  • setBlackList and setWhiteList commands let you temporarily override (but not change) the contents of an existing Black List or White List file.
  • setIEMode controls whether, and the host URLs for which, the Debugger will serve as the proxy server for users of the Internet Explorer browser.
  • showIE displays the current IE browser operating mode (the setIEMode setting that is in effect) and displays the current values of IE settings that pertain to the Debugger Client.

Changed commands:

New Client functions:

  • &&exists tests if a macro variable is defined.
  • &&blackOrWhiteList tests whether black list filtering, white list filtering, or neither is in effect.
  • &&ieMode returns the setting of the IE Mode option in the Client's Preferences window.

Other changes:


Build: 61  (31 November 2012) 

These are the principal changes to the Debugger Client since the previous build:

Macro and command changes:

  • nsLookup command added to aid in debugging setup problems
  • Assorted bug fixes.


Build: 60  (31 October 2012) 

These are the principal changes to the Debugger Client since the previous build:

Physical changes and additions to the Client user interface:

  • Status message improvements:
    • Added a display of the value (if ten characters or less) to the message received after a successful "run until variable = value" execution.
    • The macroTrace, mapButton, mapKey, clearButton, and setPreference commands now report after a successful operation (in the Status bar, Console, and Client log).

Macro and command changes:

  • New ignoredFileTypeList option of the setPreference command allows on off toggling of file type filtering.

New Client functions:

  • &&exists tests if a macro variable is defined.
  • &&preference returns the current value of a specified Client preference.


Build: 59  (17 August 2012) 

These are the principal changes to the Debugger Client since the previous build:

Physical changes and additions to the Client user interface:

  • Help menu Commands option now displays individual command syntax
  • Command line tool now maintains persistent history of commands, reviewable via the keyboard up/down arrow keys
  • macroTrace processing log now shows syntax help if commands have syntax errors
  • Watch Window color panel option (Out of Scope) for Watch Window items not in code in currently active tab (Source Code or Daemon).
  • Selecting Add Watch (from context menu for a Source Code line) automatically opens external Watch Window if Client in "Hide Lower" mode
  • Support master thread and daemon thread interaction (ReturnToDaemon method/Continue method)

Macro and command changes:

  • <> ("not equal" operator) added to assert command
  • Argument added to help command to display help for a specific command or function


Build: 58  (30 April 2012) 

These are the principal changes to the Debugger Client since the previous build:

Physical changes and additions to the Client user interface:

  • Search and Watch Window controls display at bottom of main window when in "Hide Lower" mode

Macro and command changes:

  • New option (valueDisplayOnConsole) of setPreference command to control whether value displays appear in a separate Value window when the Console window is open
  • &&arg function now restricted to commands within macros (in previous builds, &&arg could be used outside of a macro, but its results were unpredictable and unreliable)


Build: 57  (31 January 2011) 

These are the principal changes to the Debugger Client since the previous build:

Physical changes and additions to the Client user interface:

  • A Step out, Step over, or trace followed by pressing the Enter key launches another step out, step over, or trace if program execution has not completed
  • Named buttons may be replaced by separators for visual separation between buttons
  • Pinned external windows:
    • Context menu options simplify pinning and unpinning  
    • Pin icon in title bar
  • Additional StringTokenizer class variables are viewable: CurrentQuoted, CurrentToken, String, and StringLength

Macro and command changes:

  • New option (main) of extraButtonBar command to combine the main and second button bars
  • New option (ieAuto) of setPreference command to control automatic proxy maintenance for the Internet Explorer browser
  • Button mapping keyword (separator) for mapButton command or mapping file mapping element converts a button to a visual separator


Build: 56  (22 August 2011) 

These are the principal changes to the Debugger Client since the previous build:

Physical changes and additions to the Client user interface:

  • New Preferences window section Open at Startup with checkboxes for button bars:
    • External main button bar  
    • Extra button bar

Macro and command changes:

  • Addition to buttonBar command:  new option show  
  • New mapButton command assigns button mappings without requiring a mapping file or Client restart
  • The descriptions of the "macro only" commands (continueIf, include, macroTrace, noSpan, setM204Data, and span) are moved to the Client command reference  


Build: 55  (15 May 2011) 

These are the principal changes to the Debugger Client since the previous build:

Physical changes and additions to the Client user interface:

  • Three additional Client buttons (bringing total to fifteen) for mapping Client commands
  • New Proc Selection tab checkboxes turn on or off the inspection of lists of procedures/routines to exclude or include in source code displays in the Client

Macro and command changes:

  • "[in window] command" format applies the searching commands to most any Client window (main, external, or work), as follows:
In

window

Is one of:

about 
auditTrail
commands 
console 
executionHistory 
executionTrace 
keyboardShortcuts
source  
textviewer  
value 
watchWindow 
webBuffer 

command

Is one of:

bottom 
searchDown
searchFromBottom
searchFromTop 
searchUp 
top 

  • setPreference command added for turning on and off the various code exclude/include options

Other changes:

  • Number of code blocks you can exclude/include from or in debugging in a single request increased to 300  


Build: 54  (28 February 2011) 

These are the principal changes to the Debugger Client since the previous build:

  • Requirement is removed to have button mappings for the step, run and cancel commands  
  • Physical changes and additions to the Client user interface:


Build: 53  (30 November 2010) 

These are the principal changes to the Debugger Client since the previous build:

  • Physical changes and additions to the Client user interface:
    • Button bar moved above main window, and Status area moved to strip at bottom of main window
    • Font size in most Client windows is now scalable
    • Two additional Client buttons (bringing the total to twelve) now available for mapping Client commands
    • Editor for client side editing can now be set in the debuggerConfig.xml file  (an alternative to Notepad)
    • READ SCREEN information now displayed in the Client's Audit Trail tab
    • Mouse double click now opens external windows
    • Removed label Variable or Field for text box above Watch Window; changed Trace Changes button label to Trace; changed the former Trace button label to Trace All; changed the former Add Watch button label to Watch.
  • Macro and command changes:
    • Macro command line tool is renamed to Command Line and now accepts all commands
    • New macro related commands:
  • createMacro mimics the action of the Macros menu New Macro option
  • runMacroFromUISelection mimics the action of the Macros menu Run Macro option
    • New command and method options for sending user interface commands to the Client:
  • DebuggerTools class additions:
    • New ClientCommand method
    • New StatusMessage method
    • New parameter (to execute Client command) for Break method
    • New parameter (to execute Client command) for Command method
    • The "macro only" restriction for some commands (echo, toggle, varDump, and windowToTop) is removed, and their descriptions are moved to the Client command reference  


Build: 52  (9 August 2010) 

These are the principal changes to the Debugger Client since the previous build:

  • Bug fixes only.


Build: 51  (15 July 2010) 

These are the principal changes to the Debugger Client since the previous build:

  • New Preferences (File > Preferences) option (Use existing IE proxy for URLs not to be debugged) for troubleshooting IE proxy server issues
  • Some mapping errors in the ui.xml and uimore.xml files will now invalidate only the individual item and not the entire file


Build: 50  (31 March 2010) 

These are the principal changes to the Debugger Client since the previous build:

  • Audit Trail, Web Buffer and Execution Trace windows may now be moved to separate external windows
  • Client Window menu lists and tracks new Client external windows
  • Multiple issues fixed concerning Client operation on Windows 7, thereby making build 50 the preferred build for Windows 7 users
  • Client's display and watch facilities now work for Janus SOAP Arraylist objects the  same as they do for $lists or Stringlists
  • New macro only commands:
    • macroTrace traces all macro statements in the debugging session
    • setM204Data sets a Model 204 %variable or global variable  
    • windowToTop brings specified window to top of window stack
  • New Client functions (&&assertFailureCount, &&assertSuccessCount, &&assertStatus) report macro assert command results
  • New showCommands mappable command displays all the Client commands in alphabetical order
  • Boolean enumeration variables (for example, %bool1 is enumeration Boolean) may now be set (only to True or False)
  • Single quotes now allowed on string literal values in macros, wherever string literals may appear (for example with &&prompt)
  • Search path for PDF copy of product User Guide (View PDF Manual option, Client Help menu) now first tries the product installation folder, then the Doc subfolder
  • PDF version of Debugger User Guide is installed in the target installation folder instead of in a Doc subfolder.


Build: 49  (31 December 2009)

These are the principal changes to the Debugger Client since the previous build:

  • The assert command now accepts a Client function as a target (left side)


Build: 48  (31 October 2009)

These are the principal changes to the Debugger Client since the previous build:

  • Added Proc Selection tab buttons for creating and editing Exclude and Include lists for selectively excluding from debugging the code for particular methods and User Language subroutines
  • Binary view of a variable's value now also shows printable characters


Build: 47  (30 September 2009)

These are the principal changes to the Debugger Client since the previous build:

  • New Client menu option (Toggle Init Exclude) and command (toggleInitExclude) control whether to invert the way exclude mode operates: initially excluding code instead of initially including code (until an explicit directive)


Build: 46  (15 September 2009) 

These are the principal changes to the Debugger Client since the previous build:

  • Debugger commands and macros may now be mapped to numeric keys as well as to alphabetic and function keys
  • Multiple commands added for Client tab selection and navigation:
    • selectAuditTab
    • selectSourceTab
    • selectWebBufferTab
    • selectExecutionTraceTab
    • selectProcSelectionTab
    • selectNextTab
  • Additional text items available for user specified coloring in the Client windows:
    • User Language TEXT and HTML statement blocks  
    • User Language Macro Facility statements
  • Add Watch and Display right click options for lines within HTML or TEXT blocks now detect Model 204 field name expressions
  • Added the Value class variable to the expansion of a ScreenField object


Build: 45  (30 July 2009) 

These are the principal changes to the Debugger Client since the previous build:

  • Additional class variables are viewable:  
    • Record class: RecordNumber and FileName variables
    • RecordsetCursor class: RecordNumber, FileName, LoopLockStrength, and State variables
    • FastUnloadTask class: State variable
    • StringTokenizer class: AtEnd and NotAtEnd variables
    • UserStatistics class: LoginToString, RequestToString, and ToString variables
    • CharacterMap class
    • RandomNumberGenerator class
  • Support added for viewing fields that belong to Model 204 field groups


Build: 44  (09 July 2009)

These are the principal changes to the Debugger Client since the previous build:

  • Fixes for some cases where string data was erroneously shown in binary/hex notation (X'aabbcc' format)
  • FloatNamedArrayList class variables now viewable


Build: 43  (30 June 2009) 

These are the principal changes to the Debugger Client since the previous build:

  • $STATUS and $STATUSD calls can now be quickly evaluated/watched by right clicking their program line and selecting Add Watch or Display from the context menu
Otherwise, the overall size and position of the Client window as well as the dimensions of its internal windows is stored when the Client closes and reused when the Client is next opened.
  • New Macros menu items (Run and Edit) identify the most recently run macro and enable quick execution or editing of that macro
  • New mappable command (clearWebBuffer) and Window menu item (Clear Web Buffer) that clear the contents of the Web Buffer tab.
  • New mappable commands that help to debug requests that contain objects, lists, or Stringlists. Probably better suited for macros, the commands may also be mapped to buttons or keys:
  • expandObject displays a list of object variable names and values for its object instance argument
  • expandList displays the list items in the $list or Stringlist referenced by the variable specified as the command argument
  • getVariablesForClass displays a list of the names of the variable members in the class specified as the command argument
  • New mappable command (valueDisplay) that, like the Value button, displays in a separate window the value of the item currently in the Variable or Field area
  • New mappable command (showShortcuts) that displays the Client's current (default as well as mapped) keyboard shortcuts
  • Class variable members in system exception classes are now viewable
  • Increased drop down history of search terms, procedure names, and variables from ten to twenty
  • Multiple bug fixes (listed in Client's Help menu, About option).


Build: 42  (27 March 2009) 

These are the principal changes to the Debugger Client since the previous build:

  • Independent coloring for Source Code comments


Build: 41  (30 January 2009) 

These are the principal changes to the Debugger Client since the previous build:

  • Debugger Client now always becomes the topmost window when a breakpoint is reached
  • The Add Watch button now works properly with %variables whose names also have an embedded per cent (%x) character or whose names are enclosed in curly braces {%x}.


Build: 40  (8 December 2008) 

These are the principal changes since the previous build:

  • debugTrace tag added to debuggerConfig.xml file for additional diagnostic Client logging


Build: 39  (15 October 2008) 

These are the principal changes since the previous build:

  • Bug fixes only.


Build: 38  (30 September 2008) 

These are the principal changes since the previous build:

  • The Dataset object is added to the list of viewable classes.


Build: 37  (31 August 2008) 

These are the principal changes since the previous build:

  • New Clear Execution Trace menu item and clearExecutionTrace command for clearing the contents of the Execution Trace tab
  • Clear button added to Execution History and Macro Console windows.
  • New optional attribute, startUpMacro, for the mappings element in a ui.xml file mapping of alternative Client buttons, hot keys, and macros


Build: 36  (31 July 2008) 

These are the principal changes since the previous build:


Build: 35  (11 July 2008) 

These are the principal changes since the previous build:


Build: 34  (20 June 2008) 

These are the principal changes since the previous build:


Build: 33  (30 April 2008) 

These are the principal changes since the previous build:

  • User items specified during Client session now are preserved in the next session:
    • Previous search strings are accessible in a Search box drop down list.
    • Previous variables specified are accessible in a Variable or Field box drop down list.
    • Watch Window contents are redisplayed by default.
    • Resizing of the Client window is preserved.
  • Watch Window operations are no longer prevented when no program is being debugged
  • New DebuggerTools class method, Command, runs TN3270 DEBUG commands within a request


Build: 32  (18 February 2008) 

These are the principal changes to the Debugger Client since the previous build:

  • A fix for a rare case where the Watch Window failed to display certain variables in a program involving a persistent session


Build: 31  (08 February 2008) 

These are the principal changes since the previous build:

  • Enhancements to Source Preview feature:
    • A Step or Search command is allowed and causes a download of the entire source program
    • A Run command runs the program without a code download
  • A fix for the case where the Client was failing to display a compilation error message (M204.1265) for which a Model 204 MSGCTL was being issued


Build: 30  (28 January 2008) 

These are the principal changes since the previous build:

  • Array item references that have spaces between the array name and the left parenthesis are now recognized properly by all the Client features


Build: 29  (09 December 2007) 

These are the principal changes since the previous build:

  • Displaying in the Audit Trail tab the names of procedures excluded from debugging by the White List processing feature
  • A command for interrupting White List or Run Until processing
  • Changes to the Search feature to enable keyboard invoked consecutive searches for a given string:
    • The default response to pressing the Enter key while the Search text box has focus is changed from "search from the top" to "search from current line." This lets you press Enter repeatedly to find subsequent occurrences of a search string. Formerly, pressing Enter again found the same occurrence as the first time because it repeated the search from the top.
      Note: This introduces a small upward incompatibility.
    • New focusToSearchBox command gives the input focus to the Search string text area. The CTRL-F key combination is changed to perform the same function by default.


Build: 28  (09 November 2007) 

These are the principal changes since the previous build:

  • Echo command output goes to console if console is open
  • A macro running indicator to be displayed on the Client's title bar
  • New menu item (Execution > Run Until Proc) for Run Until processing, and the runUntil command is now mappable
  • Lines located via a Search button are now highlighted and displayed in the center of the page


Build: 27  (27 September 2007) 

These are the principal changes since the previous build:]

  • New Client macro related command (echo)
  • Search buttons now located below the text box for search strings


Build: 26  (17 August 2007) 

These are the principal changes to the Debugger Client since the previous build:


Build: 25  (13 July 2007) 

These are the principal changes since the previous build:

  • Support for additional level of Client menu and keyboard reconfiguration via the uimore.xml file


Build: 24  (29 June 2007) 

These are the principal changes since the previous build:

* help and manual programmable commands simplify access to product documentation


Build: 23  (27 June 2007)

These are the principal changes since the previous build:

  • Debugger now recognizes %variable names that include question marks (?) and single quotation marks (')
  • Screen and ScreenField objects are added to the list of viewable classes


Build: 22  (20 June 2007) 

hese are the principal changes since the previous build:

  • NamedArraylist objects are added to the list of viewable classes


Build: 21  (13 June 2007) 

These are the principal changes since the previous build:

  • Help menu Keyboard Shortcuts display can be printed and saved  


Build: 20  (08 June 2007)

These are the principal changes since the previous build:

  • New DebuggerTools method (DebugOff) mimics SIRUS DEBUG OFF command


Build: 19  (26 April 2007) 

These are the principal changes to the Debugger Client since the previous build:

* Fix provided for problem with requests longer than 64, 000 lines


Build: 18  (20 April 2007) 

These are the principal changes since the previous build:


Build: 17  (30 March 2007) 

These are the principal changes since the previous build:

  • Settable buttons and hot keys
You may reconfigure any of the ten contiguous buttons below the main window to invoke a different feature than its default. You also may create your own keyboard shortcuts for commonly used features.
  • Enter key is alternative to the Set button in the Set dialog box for changing a variable's value
  • Cosmetic changes to buttons
The button widths are now uniform, their labels have a smaller font, and disabled buttons are more obviously so.


Build: 16  (05 March 2007) 

These are the principal changes since the previous build:]

  • Workstation IP number displays on startup
The Audit Trail page initially displays a line like the following:

Local IP address 198.242.244.234  


Build: 15  (22 February 2007) 

These are the principal changes since the previous build:

  • Pressing Enter key repeats last GUI action
Pressing the Enter key has the same effect as clicking the button that is currently highlighted. For example, when a request is first presented in the Source Code tab, the Step button is highlighted. You can step through the program simply by pressing Enter repeatedly.  


Build: 14  (19 February 2007)

These are the principal changes since the previous build:

In this context, subscripts are allowed for $list identifiers. For example:

list %alpha(%i)


Build: 13  (09 February 2007) 

These are the principal changes since the previous build:

Two command parameters are settable in the User 0 stream.
  • Options to set multiple breakpoints at once on all lines that match a search string or regex, or on executable statements that follow comment lines that begin with *break
  • Breakpoint maximum increased from 40 to 1000 per User Language request


Build: 12  (22 January 2007) 

These are the principal changes since the previous build:

You can now right click the variable's name in the Watch Window display.
You can press the CTRL-C keyboard key combination to copy the contents of the active (topmost) tab to the Windows clipboard.
  • Additional "trace until" option
The Run To Change button continues request execution until the value of a selected variable changes. The new variation to this feature (press Alt key while clicking Run To Change) continues execution unless or until a selected variable's value becomes equal to a value you specify.
  • Length limit increased to 255 for %variables whose value you set


Build: 11  (09 January 2007) 

These are the principal changes since the previous build:

  • STATUS option for TN3270 DEBUG command
Using the STATUS option produces a simple status report of the Debugger worker threads.
  • White List processing enhancements
Processing is moved to the mainframe to eliminate code transfer and provide response time benefit. Also, trailing wild cards are now allowed in the White List.
  • Step Out option
By pressing the Alt key and clicking the Client GUI Step Over button, you can immediately discontinue the Debugger processing of a called subroutine, method, or daemon and continue processing at the statement after the call to the subroutine, method, or daemon. This action is called a "Step Out".
  • Skipping over Daemon code
By pressing the Alt key and clicking the Client GUI Run button, you can discontinue the interactive debugging of the Daemon object calls in your program. The Daemon code executes but is not displayed in the Debugger Client.
  • Assembler language replaces User Language for Debugger internals
    • Downloading a User Language dump file (SIRDEBUG) to install the Debugger Server is no longer necessary.
    • The Windows Installer program (setup.exe) for the Debugger workstation client is downloadable from the web site for Debugger customers.
  • Removal of requirements to license Janus SOAP and Janus Sockets to use the Debugger.
A new Debugger Server port type (DEBUGGERSERVER) replaces the SRVSOCK type that is required for earlier versions, and a new port type (DEBUGGERCLIENT) replaces the CLSOCK type that is required for the TN3270 Debugger for earlier versions.
  • New File > Preferences option lets you break Debugger execution after READ SCREEN/MENU statements
New message (Full Screen Read Pending) prompts TN3270 Debugger Client users when READ SCREEN is active. Formerly, the message was Waiting for Online.
  • Breakpoint maximum increased from 20 to 40 per User Language request
  • After failed compilation, F11 and F10 keys allow navigation to next and previous statement, respectively, that did not compile


Build: 10  (04 December 2006) 

These are the principal changes to the Debugger Client since the previous build:

  • Option to restart the Debugger Client
From the file menu, the Restart option shuts down the Debugger Client. The Client then restarts, doing the same processing as if you started it by clicking its desktop icon.
  • Main working area is resizable  
You can now drag the black bar just above the page navigation buttons to resize the main working window in the Client.
  • Improvements to $list and Stringlist viewing
For a float variable $list handle or for a Stringlist object variable, you can now request a display of its elements, which will be presented in a data viewer similar to the way XML documents are displayed.


Build: 9  (17 November 2006) 

These are the principal changes since the previous build:

  • Run Until spans debug sessions
The Run Until spans HTTP requests option is renamed to Run Until spans debug sessions, and it is generalized to work with the TN3270 Debugger as well as with the Janus Debugger. With this option turned on, Run Until continues searching through the source program until it finds the specified procedure, even if the debugging session is interrupted by a loss of the connection to the Online or the TN3270 Debugger is toggled off and on again. When the session resumes, the Client keeps searching for the target procedure.
  • Performance statistics kept in log file are enhanced to report the number of bytes received per message incoming to the Debugger Client.


Build: 8  (13 November 2006) 

These are the principal changes since the previous build:

  • Right clicking Source Code lines lets you display variable values

As described in Displaying the value of a program data item, this approach lets you display a variable’s value just as if you entered the variable name in the Variable or Field input area, then clicked the Value button.


Build: 7  (5 November 2006) 

These are the principal changes since the previous build:

  • The installation kit now installs a required file (gdiplus.dll) to the installation target folder instead of to the system root folder, avoiding any security issues concerning folder write permissions.
  • Minor memory use and performance improvements for both source code loading and variable watching.


Build: 6  (25 October 2006) 

These are the principal changes since the previous build:

  • Save and restore proxy settings for Microsoft Internet Explorer
The automatic maintenance of proxy settings for Janus Debugger IE users that was added in Build 5 did not save and restore all proxy related settings. It now does.
  • Performance improvements for watching variables
The display of the values of watched variables is slightly accelerated.


Build: 5  (18 October 2006) 

These are the principal changes since the previous build:

  • Better proxy control for Internet Explorer
For those Janus Debugger users whose browser is Microsoft Internet Explorer, the task of defining the Debugger Client as the proxy server can be handled automatically by the Client when it starts up (and undone when the Client shuts down).
  • Improved source line scrolling
To avoid having the current execution position in a source tab be the last line on the page (obscuring the next line of code), the display of the highlighted current position now includes the next two lines.


Build: 4  (2 October 2006)

These are the principal changes since the previous build:

  • Performance improvements for very long programs
Elapsed time for transferring and displaying programs with thousands of lines of code has been reduced by 90%. In addition, a new configuration file setting lets you trace the time the Client spends handling program code (see Tracking Client performance).


Build: 3  (27 September 2006) 

These are the principal changes since the previous build:

  • Run Until Procedure processing can ignore the end of an HTTP request
This feature is designed to make it easier to debug HTML frame based web applications, since the Client by default terminates the search for a designated Run Until procedure at the end of an HTTP request. Thus, a procedure search stops by default after each SOUL produced frame in a single HTML frameset statement.
The File > Preferences menu option displays a checkbox that lets you direct the Client to continue across multiple HTTP requests until the specified Run Until procedure name or pattern is satisfied. See Precedence and scope for Run Until.
  • Selecting which of multiple web servers are eligible for debugging

After selecting the File > Preferences menu option, you can choose which of the Onlines specified in the Client configuration file (debuggerconfig.xml) are to have their web requests debugged. For more information, see Debugging multiple Web Servers.  

  • New hot key combination for Preferences option
The CTRL-P key combination now invokes the Preferences option of the File menu.


Build: 2  (4 September 2006)

These are the principal changes since the previous build:

  • Simplified editing and reloading of a White List
You can now edit or create a white list file (whitelist.txt) with the Windows Notepad editor by selecting Edit White List from the Debugger Client File menu. In addition, instead of restarting the Client to reload the list when done editing, you simply click the Reload White List button on the Proc Selection tab.
White list processing is described in Running only to listed procedures.
  • Enhanced status reporting
    • An hourglass cursor displays whenever the Client is waiting for processing to complete on the Online.
    • Additional status area message values indicate that the GUI is waiting for the Online to respond:
  • Waiting for Online is displayed when source code is being sent from the Online to the Client workstation, or when the Online is processing the Client's Step, Run, Run Until, or Trace command. The Waiting for Online message is also displayed in TN3270 Debugger sessions whenever the Client awaits a new request from the Online.
  • Receiving/Forwarding Web Page is displayed by the Janus Debugger Client when a Web Server's HTTP response to a web request is being read by the Client and forwarded to the web browser.
  • Persistent Session Suspended (see Debugging Web Server persistent sessions) is changed to Session awaits browser.
    • When White List processing is toggled on or off from the Proc Selection tab, White list is active or White list turned off is displayed as appropriate.
  • New hot key combination for Search command
The CTRL-F key combination now performs the same function as the Search button (see The navigation and execution buttons).
  • A summary of the changes since the last build
As described in Versions and builds, you can view a list of the changes in the current build of the Client by selecting About from the Debugger Client File menu.

This category currently contains no pages or media.