Script Host Debugger Help
Welcome to BlueZone Script Host Debugger Help. The BlueZone Script Host Debugger is a language-independent host for ActiveX scripting engines on 32-bit Windows platforms. This tool will allow you to run Visual Basic Scripting Edition (VBScript) and JScript natively within the base operating system, either on Windows 9x or Windows NT/2000/XP, and will act as a host for other ActiveX-supported scripting languages such as Perl, Rexx, and Python. In addition, BlueZone Script Host & Debugger allows scripts to communicate with SEAGULL's BlueZone Display emulation software products. Using the scripting languages you already know, you can now write scripts to execute common tasks on IBM mainframe and midrange systems, automate user input, obtain data from host systems, initiate file transfers, and more.
BlueZone Script Host Debugger is a Component Object Model (COM) scripting host application that utilizes the capabilities of BlueZone's DDE (Dynamic Data Exchange) and HLLAPI (High-Level Language API) interfaces. In addition to the scripting engine's properties and methods, BlueZone Script Host & Debugger adds methods that enable scripts to interact with the BlueZone session and the IBM host system.
BlueZone Scripting Host & Debugger can be used to debug scripts, pause script execution, step through statements and subroutines, and evaluate expressions. The process of debugging scripts is a simple one and begins with the setting of one or more Debug Breakpoints.
NOTE The
Microsoft Machine Debug Manager
must be installed on your workstation to use the debugging features of
the BlueZone Script Host & Debugger. If
you do not have the Machine Debug Manager installed, BlueZone Script Host
& Debugger will detect this condition, and will automatically download
it.
Debug Breakpoints can be added and removed in two ways:
By (1)
left-clicking the mouse button while holding the mouse pointer over the
line number to toggle; or (2) placing the caret in the line to toggle
then selecting Debug:Toggle Breakpoint
from the MenuBar or clicking the
ToolBar 
icon.
After adding one or more breakpoints to the script the Debug MenuBar and ToolBar buttons can be used to control script execution while analyzing the script.
Go:
Starts
or continues script debugging by executing until the next Debug Breakpoint
is hit.
Stop
Debugging: Stops
script debugging.
Step
Into: Steps
into subroutine, function or procedure. Script
execution will halt on the next statement within the subroutine, function
or procedure.
Step
Over: Steps
over subroutine, function or procedure. Script
execution will halt on the next statement following the subroutine, function
or procedure.
Step
Out: Steps
out of subroutine, function or procedure. Script
execution will halt on the next statement following the subroutine, function
or procedure.
Run to
Cursor: Executes
script until the line number where the caret resides is hit.
Toggle
Breakpoints: Adds
or removes a Debug Breakpoint on the line where the caret resides.
Clear
All Breakpoints: Clears
all Debug Breakpoints.
Evaluate:
Invokes
the Evaluate Expression dialog. Enter
an expression to evaluate then press the Evaluate button.
The Debug Panes are used to provide script code and data information while debugging. The Debug Panes consist of three windows:
The Debug Process / Thread Window - Displays a list of processes and threads involved in debugging.
The Call Stack Window - Displays a list of nested subroutines, functions and procedures showing a path of execution to the current call stack.
The Variable Window - Displays a list of local variables of the current call stack and their values.
The Debug Panes can be shown or hidden by selecting View:Debug Panes from the MenuBar
or ToolBar 
icon.
Related Topics: