Help for COBOL85 debugger

This debugger can debug the debug-object programs, that is, can check errors in a COBOL source program that is being executed.

The debugger can debug a COBOL source program by using a direct operation while the COBOL source program is being displayed.  A debug operation is made by executing a command on a menu or by selecting a button on a toolbar by using the keyboard or mouse.  A debug operation can also be made by entering a specific-rule-satisfying character string in the [Line command] window.  (This character string is called a line command.)

Pressing the F1 key displays the message explaining how to use the help function.

How to use debugger

-	Activating the debugger

-	Quitting the debugger

-	Basic operations of debugger

-	Debugging operation

-	Limitations

Reference information

-	Screen configuration

-	Menus

-	Toolbar

-	Line commands


Notes
Limitations

Observe the following when using the debugger:

-	This debugger can debug 32-bit application programs, but cannot debug 16-bit application programs.

-	A program whose total number of lines exceeds 65,535 after the library texts have been expanded cannot be debugged.

-	The debugger stops an application’s processing when it breaks execution.  In this status, the application window or icon is not redrawn even though windows on top of it are moved.  To see the contents of the application window, be sure to arrange windows so that the debugger and other program windows do not cover the application window.

-	The execution results of about the previous 5,000 lines are retained in the command line window.

-	When compiler option NUMBER is specified for a program, an editor line number or a relative line number can be specified as the statement identification number.  When compiler option NONUMBER is specified for a program, only a relative line number can be specified as the statement identification number.  Which information item from the editor line number and relative line number is to be used must be specified in the [Display] page in the [Environments] dialog box.

-	A breakpoint or a passage count point can be set in the EXEC SQL described in the PROCEDURE DIVISION.  A breakpoint or a passage count point cannot be set in the EXEC SQL pair that encloses a nonexecutable statement such as the WHENEVER statement.  In the SQL statement, a breakpoint or a passage count point cannot be directly set.

-	When a REPLACE statement or a COPY statement with the REPLACING, DISJOINING, or JOINING operand is written to a source program, the source program used before the character string is replaced is displayed.  When the position of a statement or procedure name is changed by the replacement, the program cannot be normally debugged.


Activating the debugger

The debugger can be started by using the following methods:

-	Select the [WINSVD [debug]] command from the [Tool] menu of P-STAFF.

-	Specify and execute WINSVD.EXE in accordance with the selected command formats.


Command formats

The following command formats can be used to start the debugger:

Format 1

WINSVD

When the debugger is started using format 1, the main window is displayed.  To start the debug operation, select the [Start Debugging] command on the [File] menu.  The [Start Debugging] dialog box is opened.  Specify required information and select the [OK] button.

Format 2

WINSVD	[start-parameters]executable-program[execution-time-option]

When the debugger is started using format 2, the main window is displayed and the [Start Debugging] dialog box is opened.  This [Start Debugging] dialog box already contains the command-specified start parameters, executable program name, and execution-time-option.  Required information can be added.  To start the debugging operation, select the [OK] button.

Start parameters

A start parameter must begin with a slash ( / ) or a hyphen ( - ).  The parameter name that follows the first character can be a string of upper-case or lower-case alphabetic characters.  No space must be placed between the parameter name and the subsequent character string.  Two or more start parameters can be specified by delimiting them with one or more spaces.  The program name, file name, or folder name in the start parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.

The following start parameters can be specified:

/Gstart-program-name 	Specifies the name of the program that is to be stopped at the entry after debugging starts.  When this parameter is omitted, the processing stops in the first executed program.

/Ssource-file-storage-folder-name 	Specifies a folder in which source files are contained.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified by delimiting them with one or more semicolons ( ; ).  Source files are retrieved sequentially from the leftmost-specified folder.

When this start parameter is omitted, it is assumed that the folder that contains applications is specified.

/Ccopy-library-storage-folder-name 	Specifies a folder in which copy library files are contained. The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified by delimiting them with one or more semicolons ( ; ).  Copy library files are retrieved sequentially from the leftmost-specified folder.

When this start parameter is omitted, it is assumed that the folder that contains applications is specified.

/Asubschema-descriptor-file-storage-folder-name

 	Specifies a folder in which subschema descriptor files are contained.  The folder name specified in this parameter  must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified by delimiting them with one or more semicolons ( ; ).  Subschema descriptor files are retrieved sequentially from the leftmost-specified folder.

When this start parameter is omitted, it is assumed that the folder that contains applications is specified.

/Mscreen-and-form-description-storage-folder-name

 	Specifies a folder in which screen and form descriptions are contained.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified by delimiting them with one or more semicolons ( ; ).  Screen and form descriptions are retrieved sequentially from the leftmost-specified folder.

When this start parameter is omitted, it is assumed that the folder that contains applications is specified.

/Escreen-and-form-description-extension 	Specifies the extension of a screen and form description.  When this start parameter is omitted, it is assumed that .PMD is specified.  When NONE is specified, no extension is added.

/Hfile-descriptor-storage-folder-name 	Specifies a folder in which file descriptors are contained.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified by delimiting them with one or more semicolons ( ; ).  File descriptors are retrieved sequentially from the leftmost-specified folder.

When this start parameter is omitted, it is assumed that the folder that contains applications is specified.

/Ofile-descriptor-extension 	Specifies the extension of a file descriptor.  When this start parameter is omitted, it is assumed that .FFD is specified.  When NONE is specified, no extension is added.

/Ddebug-information-file-storage-folder-name

 	Specifies a folder in which debug information files are contained.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified by delimiting them with one or more semicolons ( ; ).  Debug information files are retrieved sequentially from the leftmost-specified folder.

When this start parameter is omitted, it is assumed that the folder that contains applications is specified.

/Bcommand-file-name 	Specifies the name of a command file for batch debugging.  The file name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the file name is specified with a relative path, it is assumed that the file name is a relative file name from the current folder used at the debugger start.  When the extension is omitted, it is assumed that .LOG is specified.

When this start parameter is specified, start parameter /L must also be specified.

/Lhistory-file-name 	Specifies the name of a history file for batch debugging.  The file name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the file name is specified with a relative path, it is assumed that the file name is a relative file name from the current folder used at the debugger start.  When the extension is omitted, it is assumed that .LOG is specified.

/N	Starts debugging without opening the [Start Debugging] dialog box.

Explanation of executable program

Specify the file name of a program to be debugged.  When the file name is specified with a relative path, it is assumed that the file name is a relative file name from the current folder used at the debugger start.  When the extension is omitted, it is assumed that .EXE is specified.  The current folder used at executable program execution is used as a folder containing the files of the executable program.

Explanation of execution-time options

Specify an execution-time option to be passed to a program to be debugged.  This option must be specified after the file name of the executable program (one or more spaces must be placed between this option and the file name).

See Also:

-	Starting debugging


Quitting the debugger

To quit the debugger, select the [Exit] command from the [File] menu.

See Also:

-	QUIT command


Copying a character string

The character string that was selected using the [Source File] window or [Line Command] window can be copied to the clip board.  The character string can be copied by following the procedure given below:

1	Using the [Source File] window or [Line Command] window, select the character string to be copied.

2	Select the [Copy] command from the [Edit] menu.  Alternatively, press the [image] item on the toolbar.


Retrieving a character string

A character string in a source file can be retrieved by following the procedure given below:

1	Activate the [Source File] window displaying the program in which a character string will be retrieved.

2	Select the [Find] command from the [Search] menu.  The [Find] dialog box is opened.

3	Specify the required information in the [Find] dialog box, and select the [Find Next] button.

The character string in the source file can be selected prior to executing before Step 2 above.  In this case, when the [Find] dialog box is opened, the selected character string is used as the initial value of the character string to be retrieved.  When the character string is not selected in the above case, the character string that includes the current cursor position is used as the initial value.

The previously retrieved character string can be retrieved repeatedly.  To retrieve a character string in the forward direction relative to the cursor position, select the [Find Previous] command from the [Search] menu.  To retrieve a character string in the backward direction relative to the cursor position, select the [Find Next] command from the [Search] menu.


Positioning the cursor to a specified line

Position the cursor to a specified line in the [Source File] window by following the procedure given below:

1	Activate the [Source File] window displaying the program for cursor positioning.

2	Select the [Jump] command from the [Search] menu.  The [Jump] dialog box is opened.

3	Specify a line number in the [Jump] dialog box, and select the [OK] button.


Sounding

When program execution is stopped the user can specify whether an alarm is to be sounded.  This specification is available for batch debugging mode and other debugging modes.  Specify the sounding function by following the procedure given below:

1	Select the [Environments] command from the [Option] menu.  The [Environments] dialog box is opened.

2	Specify the required information in the [Sound] page in the [Environments] dialog box.  Then, select the [OK] or [Apply] button.


Displaying a source file

During program execution, the debugger automatically opens the [Source File] window as required, and displays the source file of a program to be debugged.

An arbitrary source file can be displayed by following the procedure given below:

1	Select the [Program List] command from the [Window] menu.  The [Program List] window is opened.

2	From the program list displayed in the [Program List] window, select the name of the program to be displayed.  (This selection can be made by double clicking the program name or by selecting the program name and pressing the ENTER key.)


Displaying a copy library file

During program execution, the debugger automatically opens the [Source File] window as required, and displays a copy library file.

An arbitrary copy library file can be displayed by following the procedure given below:

1	Use the right button of the mouse to click the COPY statement that copies the copy library file to be displayed.  The shortcut menu is displayed.

2	Select the [Open file name] command from the shortcut menu.


Displaying a subschema descriptor file

A subschema descriptor file can be displayed using the [Source File] window in the following procedure:

1	Use the right button of the mouse to click the SUBSCHEMA-NAME paragraph.  The shortcut menu is displayed.

2	Select the [Open file name] command from the shortcut menu.


Displaying a screen and form descriptor

A screen and form descriptor can be displayed using the [Source File] window in the following procedure:

1	Use the right button of the mouse to click the COPY statement that copies the screen and form descriptor to be displayed.  The shortcut menu is displayed.

2	Select the [Open file name] command from the shortcut menu.


Displaying a file descriptor

A file descriptor can be displayed using the [Source File] window in the following procedure:

1	Use the right button of the mouse to click the COPY statement that copies the file descriptor to be displayed.  The shortcut menu is displayed.

2	Select the [Open file name] command from the shortcut menu.


Displaying a program list

A list of the programs that are being loaded on memory can be displayed using the [Program List] window.

To open the [Program List] window, select the [Program List] command from the [Window] menu.


Debugging using line commands

To debug a program by using line commands, open the [Line Command] window.

To open the [Line Command] window, select the [Line Command] command from the [Window] menu.


Changing the font

The font to be used in the [Source File] window, [Watch Data] window, [Line Command] window, and [Program List] window can be specified in window units, as follows:

1	Activate the window for which a font is to be selected.

2	Select the [Font] command from the [View] menu.  The [Font] dialog box is opened.

3	Specify the required information in the [Font] dialog box, and select the [OK] button.

More than one [Source File] window and more than one [Watch Data] window can be opened.  However, only one font can be specified for these [Source File] windows or for these [Watch Data] windows.  That is, the font specified for a [Source File] window (or for a [Watch Data] window) is also applied to other [Source File] windows (or to other [Watch Data] windows.


Changing the colors

The colors of characters and background displayed during debugger processing can be changed by following the procedure given below:

1	Select the [Color] command from the [View] menu.  The [Color] dialog box is opened.

2	Specify the required information, and select the [OK] button.

With the [Color] dialog box, specify which part of the debugger display screen is to undergo color change.


Specifying the toolbar display

Toolbar display or no display can be selected.

Select the [Toolbar] command from the [View] menu.  The toolbar display not appearing on the screen is displayed when this command is selected.  Conversely, the toolbar display appearing on the screen ceases to do so when this command is selected.

When the toolbar is being displayed, a mark is displayed at the left of the [Toolbar] command.

The information on the toolbar display setup is saved at the end of the debugger.  If it was being displayed at the end of the previous debugging, the toolbar is displayed immediately after the start of the subsequent debugging.


Changing the toolbar position

The toolbar can be removed from the screen by dragging it.  The removed toolbar can be fixed again at the upper, lower, left, or right position or can be used in the removed state.

The toolbar position is saved at the end of the debugging.  Immediately after the debugger is started, the toolbar is displayed at the same position as that used at the previous debugging.


Specifying the status bar display

Status bar display or no display can be selected.

Select the [Status bar] command from the [View] menu.  The status bar display not appearing on the screen is displayed when this command is selected.  Conversely, the status bar display appearing on the screen ceases to do so when this command is selected.

When the status bar is being displayed, a mark is displayed to the left of the [Status bar] command.

The information on the status bar display setup is saved at the end of the debugging.  If the status bar was being displayed at the end of the previous debugging, the status bar is displayed immediately after the start of the subsequent debugging.


Activating another window or icon

When the [Source File] window, [Watch Data] window, [Line Command] window, or [Program List] window is covered with another window, the active window can be switched as explained below.  When the window selected is a minimized one, the window is opened and displayed.

Activating the [Program List] window

Select the [Program List] command from the [Window] menu.

Activating the [Line Command] window

Select the [Line Command] command from the [Window] menu.

Activating the [Source File] window

Select a source file name from the list located at the bottom on the [Window] menu.

Activating the [Watch Data] window

From the list located at the bottom on the [Window] menu, select the name of the data that is being monitored.

The displayed windows can be switched one by one as follows until the target window is found.  These operations are common to all of the windows.  However, in this case, the minimized window is subject to switching but is not opened automatically.

-	Select the [Next] command from the control menu of the current active window.

-	Press the CTRL+F6 keys or press the CTRL+TAB keys.  To switch in the opposite direction, press the CTRL+SHIFT+F6 keys or press the CTRL+SHIFT+TAB keys.


Rearranging the windows or icons

The [Source File] window, [Watch Data] window, [Line Command] window, [Program List] window, and minimized windows can be rearranged in various ways by selecting a command on the [Window] menu.

See Also:

-	[Cascade] command

-	[Tile Horizontally] command

-	[Tile Vertically] command

-	[Arrange Icons] command


Displaying two parts of the same program simultaneously

Two parts of the same program (e.g., the data division and procedure division or two programs written to the same COBOL source file) can be displayed simultaneously by dividing the [Source File] window vertically into two parts.

To divide the [Source File] window into two parts, double-click or drag the split box located at the upper part of the vertical scroll bar.  This displays a split bar for splitting the window.  The size of the window frame can be changed by dragging the split bar.

The screen split mode can be returned to the 1-screen mode by double-clicking the split bar or by dragging the split bar to the top or bottom of the screen.


Changing the data display format

In the [Data] dialog box or [Watch Data] window, data is displayed in automatic format or in hexadecimal format.  These formats can be switched by the using any of the methods given below:

Changing the data display format by using the [Data] dialog box

Select the required data display format by using the [Display format] in the [Data] dialog box.

Changing the data display format by using the [Watch Data] window

To use the automatic format, select the [Automatic Format] command from the [View] menu.  When the automatic format is set as the data display format, a mark is displayed to the left of this command.

To use the hexadecimal format, select the [Hexadecimal Format] command from the [View] menu.  When the hexadecimal format is set as the data display format, a mark is displayed to the left of this command.


Starting debugging

To start debugging, open the [Start Debugging] dialog box, select the required information, and select the [OK] button.  The [Start Debugging] dialog box can be opened by the using any of the methods given below:

-	Select the [Start Debugging] command from the [File] menu.

-	Select [image] from the toolbar.

-	From the application list on the [File] menu, select an application that is to be debugged.  This command is added when the debugger has been used in the past.

The above operations can also be executed when the debugger was started but debugging activity has not yet begun or when debugging has already started but debugging of another application is required.


Quitting debugging

To quit debugging, select the [Exit] command from the [File] menu.

No operation for quitting the current debugging is not required to debug another application after quitting the current debugging.  Execute only the operation for starting the next debugging.

See Also:

-	QUIT command


Executing a program unconditionally

To restart program execution from the current stop position, do one of the operations listed below.  These commands execute a program unconditionally.

-	Select the [Go] command from the [Continue] menu.

-	Select [image] on the toolbar.

See Also:

-	Executing only one statement

-	Executing up to cursor position

-	Executing up to the next program

-	Executing by specifying specific execution conditions

-	CONTINUE command


Setting a breakpoint

A breakpoint can be set by following either of the procedure given below:

1	Select the [Breakpoint] command from the [Debug] menu.  The [Breakpoint] dialog box is opened.

2	Specify the required information in the [Breakpoint] dialog box, and click the [Set] button.

A statement in which a breakpoint was set is indicated with the statement appearing in a specific color.

A breakpoint can also be directly set in the target statement by using the [Source File] window.  This can be done by using either of the methods given below.  In this case, the [Breakpoint] dialog box is not opened.

-	Position the cursor at the statement in which a breakpoint is to be set, and select [image] on the toolbar.

-	Use the right button of the mouse to click the statement in which a breakpoint is to be set.  Then, select the [Set Breakpoint] command from the shortcut menu.

See Also:

-	BREAK command


Canceling a breakpoint

A breakpoint can be canceled by following the procedure given below:

1	Select the [Breakpoint] command from the [Debug] menu.  The [Breakpoint] dialog box is opened.

2	Select the breakpoint to be canceled from the [List of breakpoints] in the [Breakpoint] dialog box.  Then, click the [Delete] button.

A breakpoint can also be directly canceled from the target statement by using the [Source File] window.  This can be done by using either of the methods given below.  In this case, the [Breakpoint] dialog box is not opened.

-	Position the cursor at the statement from which breakpoint is to be canceled, and select [image] on the toolbar.

-	Use the right button of the mouse to click the statement from which breakpoint is to be canceled.  Then, select the [Delete Breakpoint] command from the shortcut menu.

See Also:

-	DELETE command


Forcing Program Execution to Break

Program execution can be forcibly terminated by using any of the methods given below:

-	Select the [Break] command from the [Continue] menu.

-	Select [image] on the toolbar.

-	Activate the debugger window, and press the ESC key.


Tracing the processing flow during program execution

The processing flow of a program can be confirmed during its execution by using the either of the methods given below:

-	Select the [Animate] command from the [Continue] menu.

-	Select [image] on the toolbar.


Referencing and changing Data Values

Data values can be referenced and changed using the [Data] dialog box.  The [Data] dialog box can be opened by using either of the methods given below:

-	Select the [Data] command from the [Debug] menu.

-	Select [image] on the toolbar.

-	Use the right button of the mouse to click the [Source File] window.  Then, select the [Data] command from the shortcut menu.

See Also:

-	LIST command

-	SET command


Skipping unnecessary processing

A series of processing that will cause an error or an endless loop can be skipped during execution.  This can be done by following the procedure given below:

1	Execute the program up to the point immediately before the first statement of the processing series to be skipped.

2	Do one of the following on the [Source File] window:

-	Position the cursor at the position where the next processing is to be started.  Select the [Change Start Point to Cursor] command from the [Continue] menu.

-	Use the right button of the mouse to click the position where the next processing is to be started.  Then, select the [Change Start Point to Cursor] command from the shortcut menu.

See Also:

-	SKIP command


Stopping the program execution at data value changing

When watch data is performed by specifying the monitor attribute, a change of the data value stops the program execution.

Watch data for monitor can be set by following the procedure given below:

1	Open the [Watch Data] dialog box by using any of the methods given below:

-	Select the [Watch Data] command from the [Debug] menu.

-	Select [image] on the toolbar.

-	Use the right button of the mouse to click the [Source File] window, and select the   [Watch Data] command from the shortcut menu.

2	To newly start watch data, specify the required information and click the [Set] button.

3	From the [List of watch datas], select the processing to be the target of the monitor.  Click the [Monitor] button.

When the monitor attribute is already specified for other processing, the attribute is transferred from the old processing to the newly selected processing.

See Also:

-	DTRACE command

-	MONITOR command


Stopping the program execution at specific value setting

By performing watch conditional expression, program execution can be stopped when data is set to a specific value and the monitored conditional expression is satisfied.

This condition monitoring can be set by following the procedure given below:

1	Open the [Watch Conditional Expression] dialog box by using any of the methods given below:

-	Select the [Watch Conditional Expression] command from the [Debug] menu.

-	Select [image] on the toolbar.

-	Use the right button of the mouse to click the [Source File] window, and select the [Watch Conditional Expression] command from the shortcut menu.

2	To monitor a new conditional expression other than the current watch conditional expression, cancel the current watch conditional expression by clicking the [Delete] button.

3	Specify the required information such as the conditional expression to be monitored, and click the [Set] button.

See Also:

-	DATACHK command


Determining Where Execution Breaks

To find which program stopped at which position, select the [Where] command from the [Debug] menu.

Executing the [Debug] command activates the [Source File] window including the current breakpoint.  The cursor is positioned at the current breakpoint position.

See Also:

-	WHERE command


Viewing the Calling Path

To check a program calling path, use the [Call Stack] dialog box.  The [Call Stack] dialog box can be opened by using either of the methods given below:

-	Select the [Call Stack] command from the [Debug] menu.

-	Select [image] from the toolbar.

See Also:

-	CALLS command


Checking the statement exection count

How many times a statement was executed can be known by setting in advance a passage count point in the statement at program execution.

A passage count point can be set by using the methods given below:

-	Select the [Passage Count] command from the [Debug] menu to open the [Passage Count] dialog box.  Set the required information, and click the [Set] button.

-	Open the [Source File] window.  Use the right button of the mouse to click a statement in which a passage count point is to be set.  Then select the [Set Passage Count] command from the shortcut menu.

The passage count value of a statement in which a passage count point was set in advance can be known from the [List of passage counts] in the [Passage Count] dialog box.

The statement in which a passage count point was set in advance is indicated by coloring its statement.

Not-passed statements have a different in color from that of already-passed statements.  If only the program execution is made after a passage count point is set, the passage count point color is not updated.  To update the passage count point color, select the [Update Passage Count Display] command from the [Debug] menu.

A passage count point can be canceled by using either of the methods given below:

-	Select the [Passage Count] command from the [Debug] menu to open the [Passage Count] dialog box.  From the [List of passage counts], select the passage count point to be canceled.  Then select the [Delete] button.

-	Open the [Source File] window.  Use the right button of the mouse to click a statement of which passage count point is to be canceled. Then select the [Delete Passage Count] command from the shortcut menu.

See Also:

-	COUNT command

-	DELCOUNT command


Referencing the status of the currently used debug function

The current setup status of a debug function such as a breakpoint, passage count point, watch data, or watch conditional expression can be known.

Breakpoint

Use the [Breakpoint] dialog box to know whether there is a breakpoint or to know the status of a breakpoint that is being set.  To open the [Breakpoint] dialog box, select the [Breakpoint] command from the [Debug] menu.

Passage count point

Use the [Passage Count] dialog box to know whether there is a passage count point or to know the status of a passage count point that is being set.  To open the [Passage Count] dialog box, select the [Passage Count] command from the [Debug] menu.

Watch data

Use the [Watch Data] dialog box to know whether there is data of which value is being monitored or to know the name of the data that is being monitored.  The [Watch Data] dialog box can be opened by using any of the methods given below:

-	Select the [Watch Data] command from the [Debug] menu.

-	Select [image] from the toolbar.

-	Use the right button of the mouse to click the [Source File] window.  Select the [Watch Data] command from the shortcut menu.

During data monitoring, the [Watch Data] window is open.  The value change of the data that is being monitored can be checked by using this window.

Watch conditional expression

To know whether a watch conditional expression is being set or to know the status of the monitored conditional expression, use the [Watch Conditional Expression] dialog box.  The [Watch Conditional Expression] dialog box can be opened by using any of the methods given below:

-	Select the [Watch Conditional Expression] command from the [Debug] menu.

-	Select [image] from the toolbar.

-	Use the right button of the mouse to click the [Source File] window.  Select the [Watch Conditional Expression] command from the shortcut menu.

See Also:

-	STATUS command


Tracing the past execution path

By collecting the trace information in advance, the past processing flow can be checked by tracing the program execution path in a backwards direction.  The past execution path can be traced by following the procedure given below:

1	Select the [Trace] command from the [Debug] menu.  The trace information collection starts.

2	Execute the program.

3	Trace the processing by using the backward trace function.

The following explains the types and operation of backward tracing:

Backward tracing in statement units

Use one of the following methods:

-	Select the [Backward Trace] command from the [Debug] menu, then select the [Previous Statement] command.

-	Select [image] from the toolbar.

Forward tracing in statement units

Use one of the following methods:

-	Select the [Backward Trace] command from the [Debug] menu, then select the [Next Statement] command.

-	Select [image] from the toolbar.

Backward tracing in procedure units

Use one of the following methods:

-	Select the [Backward Trace] command from the [Debug] menu, then select the [Previous Procedure] command.

-	Select [image] from the toolbar.

Forward tracing in procedure units

Use one of the following methods:

-	Select the [Backward Trace] command from the [Debug] menu, then select the [Next Procedure] command.

-	Select [image] from the toolbar.

The path that was executed before trace information collection started cannot be traced.  When the trace information collection terminates, the subsequent execution path cannot be traced.


Automating Debugging

Debugging can be automatically executed by reading a line command from a command file.  Automatic debug operation can be set by using either of the methods given below:

Batch debugging

Specify a command file at the start of debugging.  All of the later debug operations are automatically executed.  When all the line commands contained in the command file are executed, the debugger terminates.  When a QUIT command is found in the command file, the debugging terminates at once and the debugger terminates.

For batch debugging, the history file for saving the debug results must be specified.

To start the batch debugging, open the [Batch Debugging] page from the [Start Debugging] dialog box.  Then specify a command file and a history file.

Automatic debugging

Specify a command file after debugging has started.  A series of debug operations are automatically executed.  When all of the line commands contained in the command file are executed, the debugger terminates at the position of the last line command termination.  When a QUIT command is found in the command file, the debugging terminates at once and the debugger terminates.

To start the automatic debugging, select the [Automatic Debugging] command from the [Option] menu.  Then specify a command file in the [Automatic Debugging] dialog box.

See Also:

-	Starting debugging

-	AUTORUN command


Restarting a program

A program that is terminated during debugging can be restarted for re-debugging.

For re-debugging, the user can specify whether the current setup status of the following functions is to be held or canceled:

-	Breakpoints

-	Passage count points

-	Watch data

-	Watch conditional expression

Re-debug the program by following the procedure given below:

1	Open the [Re-debug] dialog box by using either of the methods given below:

-	Select the [Re-debug] command from the [Continue] menu.

-	Select [image] from the toolbar.

2	Specify the required information in the [Re-debug] dialog box.  Click the [OK] button.

See Also:

-	RERUN command


Allocating a Data Area in the Linkage Section

If there is a parameter specification error in the calling program and the data area defined in the linkage section cannot be acquired, this data area can be allocated by following the procedure given:

1	Open the [Linkage] dialog box by the following methods:

-	Select the [Linkage] command from the [Debug] menu.

-	Use the right button of the mouse to click the [Source File] window.  Select the [Linkage] command from the shortcut menu.

2	Specify the data for which area is to be acquired.  Then, select the [OK] button.

See Also:

-	LINKAGE command


Viewing and Modifying the Debug Environment

The debug environment that is currently set can be viewed and modified using the [Environments] dialog box.

To open the [Environments] dialog box, select the [Environments] command from the [Option] menu.

The following items can be set as the debug environment items:

-	Animation speed

-	Whether the called program is also to be processed in backward tracing or animation processing

-	Level of PERFORM statement that is not to be processed in backward tracing or animation processing

-	Whether lower-case letters contained in data names or program names are to be handled as upper-case letters

-	Statement identification number mode

-	Replacement characters to be used at attribute error occurrence at data display

-	Whether the debugger is to be activated at processing execution stop

-	Type of window that is to be opened at batch debugging

-	Whether an alarm is to be sounded at processing execution stop

See Also:

-	ENV command


Saving the debugging operation results into file

Debugging operation information and its resultant records can be saved in the history file.  Debugging can be performed while creating a history file.  For this purpose, start debugging, select the [Output Log] command from the [Option] menu, and specify a history file in the [Output Log] dialog box.


Referencing a program list

A list of the debugged programs that are included in the debug-object programs loaded in the memory can be referenced.

To reference the program list, select the [Program List] command from the [Window] menu.  The [Program List] window is opened.


Executing only one statement

Only one statement of a program can be executed from the current processing stop position.  This execution can be made by using either of the two methods given below:

Step-in

When the program in step-in mode is executed from the statement that calls a subprogram, processing stops in the subprogram.  The step-in mode processing can be made by using either of the methods given below:

-	Select the [Step Into] command from the [Continue] menu.

-	Select [image] from the toolbar.

Step-over

When the program in step-over mode is executed from the statement that calls a subprogram, the subprogram is executed and processing stops in the next statement.  The step-over performed processing can be performed by using either of the methods given below:

-	Select the [Step Over] command from the [Continue] menu.

-	Select [image] from the toolbar.


Executing up to cursor position

A program can be executed from the current processing stop position to the cursor position in the [Source File] window.  This execution can be performed by using any of the methods given below:

-	Move the mouse cursor to the statement at which processing is to be stopped.  Then, select the [Run to Cursor] command from the [Continue] menu.

-	Move the cursor to the statement at which processing is to be stopped.  Then, select [image] from the toolbar.

-	Use the right button of the mouse to click the statement at which processing is to be stopped.  Then, select the [Run to Cursor] command from the shortcut menu.


Executing up to the next program

A program can be executed from the current processing stop position to the entry of the next program.  This execution can be performed by using either  of the methods given below:

-	Select the [Run to Next Program] command from the [Continue] menu.

-	Select [image] from the toolbar.


Executing by specifying specific execution conditions

The following conditions can be specified as specific execution conditions:

-	Executing up to statement of specified type

-	Executing up to specified position

-	Executing up to entry

-	Executing up to exit

-	Executing up to file access

A program with a specific execution condition can be executed by following the procedure given below:

1	Select the [Specific Execution Condition] command from the [Continue] menu.  The [Specific Execution Condition] dialog box is opened.

2	Specify the required information in the [Specific Execution Condition] dialog box, and select the [OK] button.

When the specific execution condition is already set, the [Specific Execution] command can be selected from the [Continue] menu.  By specifying this command, the execution under the same specific execution condition can be repeated.


Main window

The main window is as shown below.  When a part of the main window is selected, the name of the selected part is displayed.


Menus


Toolbar


[Source File] window


[Program List] window


[Watch Data] window


[Line Command] window


Status bar


[Source File] window

Displays the files and descriptors listed below.  The displayed file or descriptor cannot be edited.

-	Source files of debug-object programs

-	Copy library files

-	Subschema descriptor files

-	Screen and form descriptors

-	File descriptors

One [Source File] window is opened for one file or one descriptor.  Two or more windows can be opened at a time.

The [Source File] window is as shown below.  When a part of the [Source File] window is selected, the name of the selected part is displayed.

Line number area

An area for specifying a line number.  When the statement identification number mode is the editor line number mode, a sequence number is displayed in this area.  When the statement identification number mode is the relative line number mode, a relative line number is displayed in this area.  However, when the program is compiled with compilation option NONUM, the relative line number is always displayed without regard to the statement identification number mode specification.

Source file area

Area for displaying a source file.  That part of the source file which is not displayed in the window can be displayed using the scroll bar.  By dividing the screen by using a split bar, two different parts of one source file can be displayed at the same time.

When the [Source File] window is active, the shortcut menu can be displayed by using the right button of the mouse to click the inside of the window.

The following statements are distinguished from other statements by coloring the statement:

Currently stopped statement	The currently stopped statement is colored.  Unless the setup status is changed, the statement color is yellow.

Currently backward-traced statement	The currently backward-traced statement is colored.  Unless the setup status is changed, the statement color is blue.

Statement in which breakpoint is set	The statement in which breakpoint is set  is colored.  Unless the setup status is changed, the statement color is red.

Statement in which passage count point is set

The statement in which passage count point is set  is colored.  When the program is executed after the passage count point is set, the executed statements not have a color different from that of the already executed statements.  Unless the setup status is changed, the statement not passed is indicated in green, and the already-passed statement is indicated in dark green.


Line number area


Source file area


Split bar


[Watch Data] window

Displays the data being monitored.  When the data value is changed by executing a program, the value displayed in this window also changes.  Moreover, the data value can be changed using this window.

The title bar of this window indicates a serial number, data name, and the name of a program in which the data is being declared.  When the monitor attribute change-time stop attribute is set for the watch data, a dollar sign ( $ ) is indicated at the left side of the serial number.

The [Watch Data] window is as shown below.  When a part of the main window is selected, the name of the selected part is displayed.

Type

A category and an area length are displayed in this area.  When the data cannot be accessed, nothing is displayed.

Replace

When a code that cannot be displayed is detected in the monitored value, the character that is to be replaced with the code is displayed in this area.  A replacement character can be specified with the [Environments] dialog box.

Offset area

The offset from the head in the data area is indicated in units of bytes.  However, when an internal Boolean item is displayed in the automatic format, the offset is indicated in units of bits.

Value area

The monitored data value is displayed in this area.  The data value displayed in this area can be changed.  The changed value in this area can be reflected in memory by pressing the ENTER key.

To set the value display format to the automatic format, select the [Automatic Format] command from the [View] menu.  To set the value display format to the hexadecimal format, select the [Hexadecimal Format] command from the [View] menu.


Offset area


Value area


[Line Command] window

Used for a line command.

The [Line Command] window is as shown below.  When a part of the main window is selected, the name of the selected part is displayed.

Line command input area

In this area, enter a line command character string that instructs a debugging operation.  To execute the specified line command, click the [Enter] button or press the ENTER key.

[Enter] button

Executes the line command that was entered in the line command input area.

Line command output area

The execution result of a line command is output to this area.

One line that is selected from the line command output area can be copied to the line command input area.  To copy a line, double-click the line or select the line then press the ENTER key.

The input focus can be moved between the line command input area and the line command output area by pressing the TAB key.


Line command input area


[Enter] button


Line command output area


[Program List] window

Displays a program list.  All of the debugged programs contained in the debug-object programs loaded in at the memory are displayed in this list.  Once loaded programs are displayed, they continue to be displayed even if they are deleted.

The [Program List] window is as shown below.  When a part of the main window is selected, the name of the selected part is displayed.

Program name area

A debug-object program is displayed in this area by indicating the [image] or [image] item at the left side of the program name.   indicates that a debugged program contained in the debug-object programs is not being displayed.   indicates that a debugged program is being displayed.   is displayed at the left of the debugged program.

When a debugged program is selected and the ENTER key is pressed, the cursor moves to the start position of the selected program.

Whether debugged programs are to be displayed can be specified as follows:

-	Select [image] or [image], and press the ENTER key.

-	Double-click [image] or [image].

-	Select [image] and press the + key.

-	Select [image] and press the - key.

-	Click [image] or [image].

To move the selected item upwards in the same level, press the CTRL+UP ARROW keys. To move the selected item downwards in the same level, press the CTRL+DOWN ARROW keys.

To move the selected item to a higher level, press the LEFT ARROW key.  To move the selected item to a lower level, press the RIGHT ARROW key.


Program name area


Status bar

The status bar has six fields.  Clicking a field of the status bar displays, the explanation message for the field.


Psitioning the mouse cursor at a command in the menu or clicking a button on the toolbar displays, the explanation message for the command.


When program execution is stopped, the type of stop event is indicated.


While the [Source File] window is active, the current cursor position is displayed in the following format:

line-column

When this field is double-clicked, the [Jump] dialog box is opened.


When lower-case letters are handled as upper-case letters, "Equivalent" is displayed.  When lower-case letters are not handled as upper-case letters, "Not Equivalent" is displayed.

When this field is double-clicked, the [Input] page of the [Environments] dialog box is opened.


While trace information is being collected, "Trace" is displayed.

When this field is double-clicked, the [Trace] dialog box is opened.


While historical information is being collected, "History" is displayed.

When this field is double-clicked, the [Output Log] dialog box is opened.


Menus

Debugging can be performed by selecting a command provided as a menu.

-	[File] menu

-	[Edit] menu

-	[View] menu

-	[Search] menu

-	[Continue] menu

-	[Debug] menu

-	[Option] menu

-	[Window] menu

-	[Help] menu


Toolbar

The menu commands that may be used frequently are also prepared as buttons on the toolbar.  Debugging can also be executed by selecting these buttons.

[Start Debugging] button

[Copy] button

[Set/Delete Breakpoint] button

[Re-debug] button

[Go] button

[Animate] button

[Break] button

[Run to Cursor] button

[Step Into] button

[Step Over] button

[Run to Next Program] button

[Data] button

[Watch Data] button

[Watch Conditional Expression] button

[Call Stack] button

[Previous Statement] button

[Next Statement] button

[Previous Procedure] button

[Next Procedure] button

[Help] button


Shortcut menu

A shortcut menu is displayed at the position that is clicked by using the right button of the mouse.  A shortcut menu can also be displayed by pressing the SHIFT+F10 keys.

This debugger supports a shortcut menu on the [Source File] window.

-	[Open Library]/[Open file name]

-	[Set Breakpoint]/[Delete Breakpoint]

-	[Set Passage Count]/[Delete Passage Count]

-	[Run to Cursor]

-	[Change Start Point to Cursor]

-	[Data]

-	[Watch Data]

-	[Linkage]

-	[Watch Conditional Expression]


 [Start Debugging]

This menu opens the [Start Debugging] dialog box.  Debugging starts in accordance with the information specified in this dialog box.


[Recent Debugging]

A list of programs that were debugged.  When a program is selected from this list, the [Start Debugging] dialog box is opened.  Debugging starts in accordance with the information specified in this dialog box.

The [Start Debugging] dialog box that was opened with this command is already initialized in accordance with the information used when the selected program debugging was started in the past.


[Exit]

Stops debugging and terminates the debugger.


 [Copy]

Copies the character string that was selected on the [Source File] or [Line Command] window to the clip board.


[Font]

Opens the [Font] dialog box.  When one of the [Source File] window, [Watch Data] window, [Line Command] window, and [Program List] window is active, the font to be used in the active window can be specified using this dialog box.

Two or more [Source File] windows or two or more [Watch Data] windows can be opened at the same time.  However, only one font can be specified for these [Source file] windows or for these [Watch data] windows.  That is, the font specified for a [Source file] window (or for a [Watch data] window) is also applied to other [Source file] windows (or to other [Watch data] windows.


[Color]

Opens the [Color] dialog box.  Using this dialog box, the colors of characters and background displayed during debugging can be specified.


[Automatic Format]

Displays data in the automatic format in the [Watch Data] window.

While data is being displayed in the automatic format, a mark is displayed to the left of this command.


[Hexadecimal Format]

Displays data in the hexadecimal format in the [Watch Data] window.

While data is being displayed in the hexadecimal format, a mark is displayed to the left of this command.


[Toolbar]

Displays the toolbar or suppresses the toolbar display.

While the toolbar is being displayed, a mark is displayed to the left of this command.


[Status bar]

Displays the status bar or suppresses the status bar display.

While the status bar is being displayed, a mark is displayed to the left of this command.


[Find]

Opens the [Find] dialog box.  When the [Find] dialog box is already opened, this command activates the dialog box.  The character string specified in this dialog box is retrieved from the source file displayed in the [Source File] window.


[Find Previous]

Retrieves that character string in a source file which is specified in the [Find] dialog box.  This retrieval is executed in the forward direction from the cursor position in the source file.


[Find Next]

Retrieves that character string in a source file which is specified in the [Find] dialog box.  This retrieval is executed in the backward direction from the cursor position in the source file.


[Jump]

Opens the [Jump] dialog box.  The cursor is positioned at the specified position in the source file.


 [Re-debug]

Used to open the [Re-debug] box.  Re-debugging is executed in accordance with the information specified in this dialog box.


 [Go]

Executes a program.


 [Animate]

Executes a program.  The execution path can be confirmed because the breakpoint-indicating statement color moves during the execution.


 [Break]

Forcibly stops the following operations:

-	Program execution

-	Data value display when data monitoring function is set

-	Data value display when monitor display (change-time stop attribute) is set or canceled in watch data

-	Historical information output when [Output Log] button is clicked in [Passage Count] dialog box.

-	Historical information output when [Output Log] button is clicked in [Data] dialog box

-	Data value display at DTRACE command execution

-	Data value display at LIST command execution

-	Data value display at MONITOR command execution

-	Status display at STATUS command execution


[Change Start Point to Cursor]

Changes the processing stop position from the current breakpoint to the cursor position displayed in the [Source File] window.  After this, the program can be restarted from the new stop position.


 [Run to Cursor]

Executes a program up to the cursor position displayed in the [Source File] window.


 [Step Into]

Executes only one statement in a program.  When this command is selected from a statement that calls a subprogram, processing stops in the called subprogram.


 [Step Over]

Executes only one statement in a program.  When this command is selected from a statement that calls a subprogram, processing stops in the next statement that appears after the called subprogram is executed.


 [Run to Next Program]

Executes processing up to the entry of the next program.


[Specific Execution]

Executes a program in accordance with the condition specified in the [Specific Execution Condition] dialog box.  This command can be used only when a specific execution condition is set.


[Specific Execution Condition]

Opens the [Specific Execution Condition] dialog box.  A condition for stopping program execution can be specified in this dialog box.  Program execution continues until the specified condition is satisfied.


[Where]

Activates the [Source File] window that displays the current breakpoint.  The cursor is positioned at the breakpoint.


 [Call Stack]

Opens the [Call Stack] dialog box, and displays the program call path.


[Breakpoint]

Opens the [Breakpoint] dialog box.  A breakpoint can be set or canceled using this dialog box.


[Passage Count]

Opens the [Passage Count] dialog box.  A passage count point can be set or canceled using this dialog box.


[Update Passage Count Display]

The statement in which a passage count point is set using the [Source File] window is colored.  A statement not passed and an already passed statement can be distinguished by different color.  This display color can be updated in accordance with the latest information.


 [Data]

Opens the [Data] dialog box.  The value of the specified data can be referenced or updated using this dialog box.


[Data Name List]

Opens the [Data Name List] dialog box to display a list of data names used in a presentation file or network database.


 [Watch Data]

Opens the [Watch Data] dialog box.  The watch data function (Watch Data function) can be set or canceled using this dialog box.


[Linkage]

Opens the [Linkage] dialog box.  The data area of a linkage section can be acquired using this dialog box.


 [Watch Conditional Expression]

Opens the [Watch Conditional Expression] dialog box.  A watch conditional expression can be set or canceled using this dialog box.


[Trace]

Starts or terminates trace information collection.

While trace information is being collected, a mark is indicated to the left of this command.


 [Backward Trace]-[Previous Statement]

Moves in units expressed in statements the backward-trace-position-indicating mark in the reverse direction of the program execution direction.

This command can be used only when trace information is being collected.


 [Backward Trace]-[Next Statement]

Moves in unit expressed in statement the backward-trace-position-indicating mark in the program execution direction.

This command can be used only when trace information is being collected.


 [Backward Trace]-[Previous Procedure]

Moves in units expressed in procedures the backward-trace-position-indicating mark in the reverse direction of the program execution direction.

This command can be used only when trace information is being collected.


 [Backward Trace]-[Next Procedure]

Moves in units expressed in procedures the backward-trace-position-indicating mark in the program execution direction.

This command can be used only when trace information is being collected.


[Environments]

Opens the [Environments] dialog box.  The current debug environment can be referenced or changed using this dialog box.


[Automatic Debugging]

Opens the [Automatic Debugging] dialog box.  Automatic debugging is executed by reading a line command from the command file specified using this dialog box.


[Output Log]

Opens the [Output Log] dialog box.  Debugging operation information and the result of such debugging are output to the history file specified using this dialog box.


[Cascade]

Displays opened windows by stacking them so that their title bars can be displayed completely.


[Tile Horizontally]

Rearranges opened windows so that they do not overlap with each other.  When there are three or less open windows, these windows are arranged vertically.  When there are four or more open windows, they are arranged vertically and horizontally and equally spaced.


[Tile Vertically]

Rearranges open windows so that they do not overlap with each other.  When there are three or less open windows, these windows are arranged horizontally.  When there are four or more opened windows, they are arranged horizontally and vertically and equally spaced.


[Arrange Icons]

Arranges icons at the left bottom of the main window when windows are minimized.


[Close All]

Closes all of the windows currently opened such as the [Source File] window, [Watch Data] window, [Line Command] window, and [Program List] window.


[Program List]

Opens the [Program List] window.  If the [Program List] window is already opened when this command is executed, the [Program List] window is activated.

When the [Program List] window is active, a mark is displayed at the left side of this command.


[Line Command]

Opens the [Line Command] window.  If the [Line Command] window is already opened when this command is executed, the [Line Command] window is activated.

When the [Line Command] window is active, a mark is displayed at the left side of this command.


[Window Names]

A list of names of currently open [Source File] windows and [Watch Data] windows.  One window can be activated by selecting it from this list.

When ten or more windows ([Source File] windows + [Watch Data] windows) are open, the [Other Windows] command is added at the bottom of the list.  When the [Other Windows] command is selected, the [Select Window] dialog box is opened.  An arbitrary window listed in this dialog box can be activated by selecting it from the dialog box.


[Help Topics]

Displays help information on the COBOL85 debugger.


[About]

Opens the [About] dialog box, and displays the version and copyright information on the COBOL85 debugger.


[Open Library]/[Open file name]

When the cursor is positioned at a COPY statement, this command opens the [Source File] window and displays a fetched copy library file, screen and form descriptor, or file descriptor.

When the cursor is positioned at a SUBSCHEMA-NAME paragraph, this command opens the [Source File] window and displays a subschema definition file.

"file name" indicates the corresponding file name or descriptor file name.


[Set Breakpoint]/[Delete Breakpoint]

When a breakpoint is not set in the statement where the cursor is positioned, the [Set Breakpoint] command sets a breakpoint in this statement.

When a breakpoint is already set in the statement where the cursor is positioned, the [Delete Breakpoint] command deletes the breakpoint from this statement.


[Set Passage Count]/[Delete Passage Count]

When a passage count point is not set in the statement where the cursor is positioned, the [Set Passage Count] command sets a passage count point in this statement.

When a passage count point is already set in the statement where the cursor is positioned, the [Delete Passage Count] command deletes the passage count point from this statement.


 [Help]

When this button is clicked, the cursor changes into [image].  When the menu command or toolbar button is clicked using this new cursor, the help message concerned with the selected command or button is displayed.


Conventions for line command format
Font and Symbols describing line command format

The following characters and symbols are used to explain the line command coding format:

Fonts and symbol	Meaning

ABC	A variable character string in a specified format is shown in boldface.  The variable character string is replaced with an actual character string.

Example: BREAK breakpoint-position

         >>	BREAK 100

{AB | CDE}	A set of character strings enclosed by { and } and separated by | indicates that one of the character strings must be selected.

Example: STATUS {BREAK | COUNT | DTRACE |DATACHK | SCOPE}

         >>	STATUS BREAK,

         	STATUS COUNT,

         	STATUS DTRACE,

         	STATUS DATACHK or

         	STATUS SCOPE

[ABC]	A character string enclosed by [ and ] is optional.

AB...	A character string just before ... can be specified repeatedly.


AUTORUN command

Starts automatic debugging.  During automatic debugging, the menu cannot be operated, no command can be entered in the line command input area, and the [Enter] button cannot be selected.  When the last line command in the file is executed, command execution using the line command input area can be validated again.  If a QUIT command appears in the file, the subsequent line commands are not processed but the debugger terminates.

To stop command execution using the command file, select the [Break] command from the [Continue] menu when the debugger window is active.  When an AUTORUN command appears in the command file, this command is ignored.

Command format

AUTORUN command-file-name

AUTO can be written as the abbreviated code of AUTORUN.

Meaning of operands

command-file-name	Specifies the name of a command file for automatic debugging input.  The file name specified in this parameter must not contain quotation marks ('), double quotation marks ("), commas (,), semicolons (;), spaces, or parentheses.  When the file name is specified with a relative path, the current folder name used at debugger start is added to the file name.  When no extension is specified, .LOG is used as the extension.


BREAK command

Sets breakpoints at specified positions.  A breakpoint can only be set to statements for which object code has been generated.

Command format

BREAK	{breakpoint-position [IN(program-modifier)] [COND(conditional-expression)] [CYCLE(n)]  |
ENTRY [PROC(program-name-scope)] [COND(conditional-expression)] [CYCLE(n)]  |
EXIT [PROC(program-name-scope)] [COND(conditional-expression)] [CYCLE(n)]  |
STMT(statement-keyword) [PROC(program-name-scope)] [COND(conditional-expression)] [CYCLE(n)]}

BREAK can be abbreviated as B.

Meaning of operands:

breakpoint-position	Sets a breakpoint at a position specified by a statement identification number

ENTRY	Sets a breakpoint at a program entry.
ENTRY can be abbreviated as ENT.

EXIT	Sets a breakpoint at a program exit.
EXIT can be  abbreviated as EX.

STMT(statement-keyword)	Sets a breakpoint at the statement that contains the specified statement keyword.  Two or more statement keywords can be specified by delimiting them with commas.
STMT can be abbreviated as STM.

IN(program-modifier)	Specifies the program containing the specified line as a program modifier when the breakpoint-position is specified by a statement identification number.  If this operand is omitted, the program modifier defaults to the implicit program name

PROC(program-name-scope)	Specifies the target program as a program name scope when the breakpoint is set by specifying an entry, exit, or statement keyword.  Two or more program name scopes can be specified by delimiting them with blanks.  If this operand is omitted, all programs are affected.  When the COND operand is also specified, only one program can be specified in this operand.
PROC can be abbreviated as P.

COND(conditional-expression)
Specifies interrupting execution at the breakpoint only when the conditional expression specified is satisfied.
COND can be abbreviated as CO.

CYCLE(n)	Breaks execution at the nth execution of the breakpoint.  “n” is an integer.
CYCLE can be abbreviated as CY.

If both the COND and CYCLE operands are specified, execution is interrupted when either condition is satisfied.


CALLS command

Displays the program names on the calling path in order starting with the nearest to the halted program and moving to the farthest.  Sequence numbers from 0 are displayed to the left of the program names.

Command format

CALLS


CONTINUE command

Restarts program execution from the position where execution was halted.

Command format

CONTINUE

CONTINUE can be abbreviated as CONT or C.

See Also:

-	Explanation of signals


COUNT command

Counts the number of times statements are executed, referred to as “passage counts”.  A passage count point can only be set for statements whose objects have been generated.

Command format

COUNT	{passage-count-position [IN(program-modifier)]  |
ENTRY [PROC(program-name-scope)]  |
EXIT [PROC(program-name-scope)]  |
STMT(statement-keyword) [PROC(program-name-scope)] }

COUNT can be abbreviated as CO.

Meaning of operands

passage-count-position	Sets a passage count at the position specified by a statement identification number.

ENTRY	Sets a passage count at a program entry.
ENTRY can be abbreviated as ENT.

EXIT	Sets a passage count at a program exit.
EXIT can be abbreviated as EX.

STMT(statement-keyword)	Sets a passage count at a statement that has the specified statement keyword.  Two or more statement keywords can be specified by delimiting them with commas.
STMT can be abbreviated as STM.

IN(program-modifier)	Specifies the program containing the specified line as a program modifier when the passage-count-position is specified by a statement identification number.  If this operand is omitted, the program modifier defaults to the implicit program name.

PROC(program-name-scope)	Specifies the target program as a program name scope when the passage count is set by specifying an entry, exit, or statement keyword.  Two or more program name scopes can be specified by delimiting them with blanks.  If this operand is omitted, all programs are affected.
PROC can be abbreviated as P.


DATACHK command

Sets the watch conditional expression.  If the conditional expression is satisfied, program execution is interrupted.  Only one expression can be monitored.  To monitor another expression, use the DELDCHK command to end monitoring of the current expression and enter a new DATACHK command.

Command format

DATACHK	monitoring-conditional-expression [IN(program-modifier)]

DATACHK can be abbreviated as DCHK.

Meaning of operands

monitoring-conditional-expression
Specifies the conditional expression to be monitored.

IN(program-modifier)	Specifies the program containing the data described in monitoring-conditional-expression as a program modifier If this operand is omitted, the program modifier defaults to the implicit program name.


DELCOUNT command

Cancels or resets passage count points.

Command format

DELCOUNT	{passage-count-position [IN(program-modifier)] [CLEAR]  |
ENTRY [PROC(program-name-scope)] [CLEAR]  |
EXIT [PROC(program-name-scope)] [CLEAR]  |
STMT(statement-keyword) [PROC(program-name-scope)] [CLEAR]  |
* [PROC(program-name-scope)] [CLEAR] }

DELCOUNT can be abbreviated as DCO.

Meaning of operands

passage-count-position	Cancels the passage count specified by a statement identification number.

ENTRY	Cancels the passage count at a program entry.
ENTRY can be abbreviated as ENT.

EXIT	Cancels the passage count at a program exit.
EXIT can be abbreviated as EX.

STMT(statement-keyword)	Cancels the passage count at a statement that has the specified statement keyword.  Two or more statement keywords can be specified by delimiting them with commas.
STMT can be abbreviated as STM.

*	Cancels all set passage counts.

IN(program-modifier)	Specifies the program containing the specified line as a program modifier when the passage-count-position is specified by a statement identification number.  If this operand is omitted, the program modifier defaults to the implicit program name.

PROC(program-name-scope)	Specifies the target program as a program name scope when the passage count is canceled by specifying an entry, exit, or statement keyword, or all statements.  Two or more program name scopes can be specified by delimiting them with blanks.  If this operand is omitted, all programs are affected.
PROC can be abbreviated as P.

CLEAR	Resets a passage count without canceling it.
CLEAR can be abbreviated as C.


DELDCHK command

Cancels the watch conditional expression.

Command format

DELDCHK

DELDCHK can be abbreviated as DDCHK.


DELDTR command

Cancels the watch data operation (data monitoring operation).

Command format

DELDTR	{ serial-no | *}

DDTR can be written as the abbreviated code of DELDTR.

Meaning of operands

serial-no	Specifies the serial-no of the watch data operation that is to be canceled.  The watch data operation set using a MONITOR command can also be canceled using this operand.

*	Cancels all of the watch data operations.  The data monitoring operation set using a MONITOR command is also canceled.


DELETE command

Cancels set breakpoints.

Command format

DELETE	{breakpoint-position [IN(program-modifier)] [ {EFFECT | NOEFFECT} ]  |
ENTRY [PROC(program-name-scope)] [ {EFFECT | NOEFFECT} ]  |
EXIT [PROC(program-name-scope)] [ {EFFECT | NOEFFECT} ]  |
STMT(statement-keyword) [PROC(program-name-scope)] [ {EFFECT | NOEFFECT} ]  |
* [PROC(program-name-scope)] [ {EFFECT | NOEFFECT} ] }

DELETE can be abbreviated as D.

Meaning of operands

breakpoint-position	Cancels the breakpoint at a position specified by a statement identification number.

ENTRY	Cancels the breakpoint at a program entry.
ENTRY can be abbreviated as ENT.

EXIT	Cancels the breakpoint at a program exit.
EXIT can be abbreviated as EX.

STMT(statement-keyword)	Cancels the breakpoint at a statement that has the specified statement keyword.  Two or more statement keywords can be specified by delimiting them with commas.
STMT can be abbreviated as STM.

*	Cancels all breakpoints.

IN(program-modifier)	Specifies the program containing the specified line as a program modifier when the breakpoint-position is specified by a statement identification number.  If this operand is omitted, the program modifier defaults to the implicit program name.

PROC(program-name-scope)	Specifies the target program as a program name scope when the breakpoint is canceled by specifying an entry, exit, or statement keyword, or all statements.  Two or more program name scopes can be specified by delimiting them with blanks.  If this operand is omitted, all programs are affected.
PROC can be abbreviated as P.

{EFFECT | NOEFFECT}	NOEFFECT temporarily disables a breakpoint.  EFFECT enables a temporarily disabled breakpoint.
NOEFFECT can be abbreviated as NOE
EFFECT can be abbreviated as E.


DELMON command

Cancels the watch data operation having the monitor. attribute

Command format

DELMON

DM can be written as the abbreviated code of DELMON.


DTRACE command

Sets the watch data operation.

Command format

DTRACE	{ data-name [IN(program-modifier)] [FORMAT( {A | H} )] | serial-no }

DTR can be written as the abbreviated code of DTRACE.

Meaning of operands

data-name	Specifies the data to be monitored as a data name.

IN(program-modifier)	The "program-modifier " specifies the program that contains the data to be monitored.  When this operand is omitted, it is assumed that the implicit program name is specified as the program modifier.

FORMAT( {A | H} )	Specifies display format "A" or "H."  "A" specifies the automatic format.  "H" specifies the hexadecimal format.  When this operand is omitted, FORMAT(A) is assumed.  "F" can be written as the abbreviated code of FORMAT.

serial-no	Specifies the serial-no of the watch data operation of which attribute is to be changed from the monitor attribute into the ordinary attribute.

Data value display can be stopped by pressing the ESC key while the debugger window is active.

See Also:

-	MONITOR command


ENV command

Modifies the debug environment according to the specified operand.  The environmental factors corresponding to unspecified operands are not changed.  If no operand is specified, the status of the current debug environment is displayed.

Command format

ENV	[ABEND(replacement-character)] [ {NUM | SEQ} ] [ {DBTR(history-file-name) | NODBTR} ] [ {DIFF | SAME} ]

Meaning of operands

ABEND(replacement-character)
Specifies the replacement character.  A 1-byte character except single and double quotation marks, a blank, and a parenthesis can be specified.
The question mark is the substitute character when the debugger is activated.
ABEND can be abbreviated as AB.

{NUM | SEQ}	statement identification number mode
SEQ specifies relative line number mode.  NUM specifies editor line number mode.  The statement identification number mode is automatically set when program execution is interrupted.  If execution is interrupted in a program compiled with the NUMBER compiler option, NUM is set.  If execution is interrupted in a program compiled with the NONUMBER compiler option, SEQ is set.

{DBTR(history-file-name) | NODBTR}
Specifies whether to record the operation log, called history, in a file.  Specify DBTR(history-file-name) to start recording.  If a relative path name is used to specify the file name, the current directory name when the debugger is activated is prefixed to the path name.  The extension defaults to .LOG.  Specify NODBTR to end recording.  Since history can only be recorded in one file, to record history in another file, specify NODBTR to end history collection.  Recording then starts in the new file.

{DIFF | SAME}:	Specifies whether lowercase and uppercase letters in program names and data names specified in commands are to be case-sensitive.  DIFF specifies that they are case-sensitive.  SAME specifies that they are not case-sensitive.  SAME is set when the debugger is activated.


LINKAGE command

Allocates a data area defined in the linkage section of the halted program.  Since the number or size of the parameters passed by the calling program may be incorrect, this function can be used to continue debugging without correcting or recompiling the calling program.

Command format

LINKAGE	data-name

LINKAGE can be abbreviated as LINK.

Meaning of operands

data-name	Specifies the data to be allocated as a data name.


LIST command

Displays data values.

Command format

LIST	data-name [IN(program-modifier)] [FORMAT( {A | H} )]

LIST can be abbreviated as L.

Meaning of operands

data-name	Specifies the data to be referenced as a data name.

IN(program-modifier)	Specifies the program containing the data name as a program modifier.  If this operand is omitted, the program modifier defaults to the implicit program name.

FORMAT({A | H})	Specifies the display format.  A specifies automatic format, and H specifies the hexadecimal format.  Automatic format means that the debugger will display the data in the most meaningful way for the picture description of the data item.  The default is FORMAT(A).  FORMAT can be abbreviated as F.

Press the ESC key when the debugger window is active to interrupt the LIST display.


MONITOR command

Sets the watch data operation having the monitor attribute.

When the watch data operation having the monitor attribute is already being executed for the specified data, the monitor attribute is canceled.

Command format

MONITOR	{ data-name[IN(program-modifier)][ FORMAT({A | H})]|serial-no }

M can be written as the abbreviated code of MONITOR.

Meaning of operands

data-name	Specifies the data to be monitored as a data name.

IN(program-modifier)	The "program-modifier " specifies the program that contains the data to be monitored.  When this operand is omitted, it is assumed that the implicit program name is being specified as the program modifier.

FORMAT( {A | H} )	Specifies display format "A" or "H."  "A" specifies the automatic format.  "H" specifies the hexadecimal format.  When this operand is omitted, FORMAT(A) is assumed.  "F" can be written as the abbreviated code of FORMAT.

serial-no	Specifies the serial-no of the watch data operation for which the monitor attribute is to be set.

Only one watch data operation can have the monitor operation.  If the monitor attribute is already set in another watch data operation when this command is executed, the current monitor attribute is canceled.  Instead, the monitor attribute is set in the newly specified watch data operation.

The value display can be stopped by pressing the ESC key while the debugger window is active.

See Also:

-	DTRACE command


QUIT command

Quits the debugger.

Command format

QUIT

QUIT can be abbreviated as Q.


RERUN command

Forcibly terminates the program being debugged and restarts debugging from the beginning.  Whether the current settings for breakpoints, passage counts, monitoring condition, and monitoring data should be retained can be specified as options in RERUN command.  The following settings are retained unconditionally:

-	Debug environment

-	Debug starting program name

Command format

RERUN	[BREAK( {KEEP | CANCEL} )] [COUNT( {KEEP | CANCEL} )] [DTRACE( {KEEP | CANCEL} )] [DATACHK( {KEEP | CANCEL} )]

Meaning of operands

BREAK({KEEP | CANCEL}):	Retaining breakpoints
KEEP specifies retaining the current breakpoints.  CANCEL specifies canceling the settings.  The default is BREAK(KEEP).
BREAK can be abbreviated as B.

COUNT({KEEP | CANCEL}):	Retaining passage counts
KEEP specifies retaining the current passage counts.  CANCEL specifies canceling the settings.  The default is COUNT(KEEP).
 When KEEP is specified, the counters of the passage counts are initialized to zero.
COUNT can be abbreviated as CO.

DTRACE({KEEP | CANCEL}):	Retaining data monitoring
KEEP specifies retaining the current monitoring data.  CANCEL specifies canceling the setting.  The default is DTRACE(KEEP).
DTRACE can be abbreviated as DTR.

DATACHK({KEEP | CANCEL}):	Retaining the monitoring condition
KEEP specifies retaining the current monitoring condition.  CANCEL specifies canceling the setting.  The default is DATACHK(KEEP).
DATACHK can be abbreviated as DCHK.

Use of the RERUN command may cause a different compilation unit to be loaded.  If this occurs, all breakpoints, passage counts, monitoring data, and monitoring condition set for the compilation unit are canceled.


RUNTO command

Executes the program from the current position to the position specified by the RUNTO operands.

Command format

RUNTO	[{NEXT[(number-of-statements)] [ {GLOBAL | LOCAL} ]  |
STMT(statement-keyword)  |
FILE(file-name) [IN(program-modifier)]  |
breaking-position [IN(program-modifier)]  |
ENTRY [PROC(program-name-scope)]  |
EXIT [PROC(program-name-scope)]  |
#}]

RUNTO can be abbreviated as R.  If no operand is specified, NEXT is assumed.

Meaning of operands

NEXT(number-of-statements)	Executes the specified number of statements.  If NEXT is specified without a number of statements, only one statement is executed before execution is halted.
NEXT can be abbreviated as N.

{GLOBAL | LOCAL}	Specifies whether to include statements in called programs when the number of executed statements is counted.  GLOBAL specifies counting in called programs.  LOCAL specifies that there is no counting in called programs.  The default is GLOBAL.
GLOBAL can be abbreviated as G
LOCAL can be abbreviated as L.

STMT(statement-keyword)	Executes the program up to a statement that has the specified statement keyword.  Two or more statement keywords can be specified by delimiting them with commas.  Note that execution can be interrupted only at statements whose objects have been generated.
STMT can be abbreviated as STM.

FILE(file-name)	Specifies as a file-name.Executes the program up to a statement that uses the specified file-name.

break-position	Specifies as a statement identification number the position of the statement where execution is to be interrupted.  Only statements whose objects have been generated can be specified.

ENTRY	Executes up to a program entry.
ENTRY can be abbreviated as ENT.

EXIT	Executes up to a program exit.
EXIT can be abbreviated as EX.

IN(program-modifier)	Specifies the program containing the file or execution break statement as a program modifier.  If this operand is omitted, the program modifier defaults to the implicit program name.

PROC(program-name-scope)	Specifies as a program name scope the name of the program whose execution is to be interrupted at an entry or exit.  Two or more program name scopes can be specified by delimiting them with blanks.  If this operand is omitted, all programs are affected.
PROC can be abbreviated as P.

#	Executes the program up to the position specified by the last RUNTO command (for all operands except NEXT).

See Also:

-	Explanation of signals


SCOPE command

Changes the implicit program name.

Command format

SCOPE	[program-modifier]

SCOPE can be abbreviated as SC.

Meaning of operands

program-modifier	Specifies the program name to be set as the implicit program name as a program modifier.  The default is the name of the halted program.


SET command

Updates data values.

Command format

SET	assignment-expression [IN(program-modifier)]

Meaning of operands

assignment-expression	Specifies the assignment expression to be executed.

IN(program-modifier)	Specifies the program containing the data described in the assignment expression as a program modifier If this operand is omitted, the program modifier defaults to the implicit program name


SKIP command

Changes the position at which program execution is to be restarted.

Command format

SKIP	break-position

Meaning of operands

break-position	Specifies as a statement identification number the position at which execution is to be restarted.  Only statements whose objects have been generated can be specified.


STATUS command

Displays debugging status values.

Command format

STATUS	{BREAK | COUNT | DTRACE | DATACHK | SCOPE}

STATUS can be abbreviated as ST.

Meaning of operands

BREAK	Displays the status of breakpoint settings.
BREAK can be abbreviated as B.

COUNT	Displays the status of passage count settings.
COUNT can be abbreviated as CO.

DTRACE	Displays the currently monitored data name.
DTRACE can be abbreviated as DTR.

DATACHK	Displays the currently monitored condition.
DATACHK can be abbreviated as DCHK.

SCOPE	Displays the implicit program name.
SCOPE can be abbreviated as SC.

Press the ESC key when the debugger window is active to interrupt the STATUS display.


WHERE command

Reports the position at which program execution was interrupted or halted.

Command format

WHERE

WHERE can be abbreviated as W.


Explanation of signals

Code	Explanation

EXCEPTION_ACCESS_VIOLATION	The program lacked proper access when it attempted to read or write data at a virtual address.

EXCEPTION_FLT_DENORMAL_OPERAND	One operand in a floating-point operation is not correct.  This value is too small and cannot be represented as a standard floating-point value.

EXCEPTION_FLT_DIVIDE_BY_ZERO	The program divided a floating-point value by floating-point value 0.

EXCEPTION_FLT_INEXACT_RESULT	The result of a floating-point operation cannot be represented as an accurate decimal.

EXCEPTION_FLT_INVALID_OPERATION	This exception indicates a floating-point exception not included in this list.

EXCEPTION_FLT_OVERFLOW	The characteristic value of a floating-point operation exceeds the upper limit of the corresponding type.

EXCEPTION_FLT_STACK_CHECK	As a result of a floating-point operation, a stack overflow or underflow occurred.

EXCEPTION_FLT_UNDERFLOW	The characteristic value of a floating-point operation exceeds the lower limit of the corresponding type.

EXCEPTION_INT_DIVIDE_BY_ZERO	The program divided an integer by zero.

EXCEPTION_INT_OVERFLOW	As a result of an integer operation, an overflow of the highest-order bit occurred.

EXCEPTION_PRIV_INSTRUCTION	The program attempted to execute a statement for an operation that was not allowed in the current machine mode.

UNDEFINED_EXCEPTION(exception-code)	Another signal was generated.


[Start Debugging] dialog box

Specifies the information required to start debugging.

The [Start Debugging] dialog box has the following pages:

-	[Application] page

-	[Source] page

-	[Descriptor] page

-	[Debugging Information] page

-	[Batch Debugging] page


[Application] page

 [Application]

Specifies the file name of an executable program that is to be debugged.  The file name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the file name is specified with a relative path, it is assumed that the file name is a relative file name from the current folder used at the debugger start.

This parameter cannot be omitted.  When no extension is specified, .EXE is used as the extension.

[Browse] button

Opens the [File Reference] dialog box.  Using this dialog box, the file specified in the [Application] can be referenced.

[Execution-time-option]

Specifies the execution-time option that is to be passed to the executable program.

This parameter can be omitted.

[Start program]

Specifies the name of a program from which debugging is to be started (name of debugged program).  The program name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.

When this parameter is omitted, it is assumed that the first program found is specified.

[OK] button

Closes the [Start Debugging] dialog box, and starts the debugging.

[Cancel] button

Closes the [Start Debugging] dialog box.  The debugging does not start.

See Also:

-	[Source] page

-	[Descriptor] page

-	[Debugging Information] page

-	[Batch Debugging] page


[Source] page

 [Source file storage folders]

Specifies a folder in which source files are stored.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified as required by delimiting them with a semicolon ( ; ).  Source files are retrieved sequentially from the leftmost-specified folder.

When this parameter is omitted, it is assumed that the folder in which the applications are stored is specified.

[Browse] button

The [Browse] button located at the right side of the [Source file storage folders] is used to open the [Folder Reference] dialog box.  Using this dialog box, the folder to be specified in the [Source file storage folders] can be referenced.

[Copy library storage folders]

Specifies a folder in which copy library files are stored.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified as required by delimiting them with a semicolon ( ; ).  Copy library files are retrieved sequentially from the leftmost-specified folder.

When this item is omitted, it is assumed that the folder in which the applications are stored is specified.

[Browse] button

The [Browse] button located at the right side of the [Copy library storage folders] is used to open the [Folder Reference] dialog box.  Using this dialog box, the folder to be specified in the [Copy library storage folders] can be referenced.

[Subschema descriptor file storage folders]

Specifies a folder in which subschema descriptor files are stored.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified as required by delimiting them with a semicolon ( ; ).  Subschema descriptor files are retrieved sequentially from the leftmost-specified folder.

When this item is omitted, it is assumed that the folder in which the applications are stored is specified.

[Browse] button

The [Browse] button located at the right side of the [Subschema descriptor file storage folders] is used to open the [Folder Reference] dialog box.  Using this dialog box, the folder to be specified in the [Subschema descriptor file storage folders] can be referenced.

[OK] button

Closes the [Start Debugging] dialog box, and starts the debugging.

[Cancel] button

Closes the [Start Debugging] dialog box.  The debugging does not start.

See Also:

-	[Application] page

-	[Descriptor] page

-	[Debugging Information] page

-	[Batch Debugging] page


[Descriptor] page

Screen and form descriptor

[Folder]

Specifies a folder in which screen and form descriptor files are stored.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified as required by delimiting them with a semicolon ( ; ).  Screen and form descriptor files are retrieved sequentially from the leftmost-specified folder.

When this parameter is omitted, it is assumed that the folder in which the applications are stored is specified.

[Browse] button

Opens the [Folder Reference] dialog box.  Using this dialog box, the folder in which the screen and form descriptors are stored can be referenced.

[Extension]

Specifies the extension of the screen and form descriptor.  The initial value is PMD.  When no extension is required, select "None".

File descriptor

[Folder]

Specifies a folder in which file descriptors are stored.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified as required by delimiting them with a semicolon ( ; ).  File descriptors are retrieved sequentially from the leftmost-specified folder.

When this parameter is omitted, it is assumed that the folder in which the applications are stored is specified.

[Browse] button

Opens the [Folder Reference] dialog box.  Using this dialog box, the folder in which the file descriptors are stored can be referenced.

[Extension]

Specifies the extension of the file descriptor.  The initial value is FFD.  When no extension is required, select "None".

[OK] button

Closes the [Start Debugging] dialog box, and starts the debugging.

[Cancel] button

Closes the [Start Debugging] dialog box.  The debugging does not start.

See Also:

-	[Application] page

-	[Source] page

-	[Debugging Information] page

-	[Batch Debugging] page


[Debugging Information] page

 [Debugging information file storage folders]

Specifies a folder in which debugging information files are stored.  The folder name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When the folder name is specified with a relative path, it is assumed that the folder name is a relative folder name from the current folder used at the debugger start.  Two or more folder names can be specified as required by delimiting them with a semicolon ( ; ).  Debugging information files are retrieved sequentially from the leftmost-specified folder.

When this parameter is omitted, it is assumed that the folder in which the applications are stored is specified.

[Browse] button

Opens the [Folder Reference] dialog box.  Using this dialog box, the folders that are to be specified as the [Debugging information file storage folders] can be referenced.

[OK] button

Closes the [Start Debugging] dialog box, and starts the debugging.

[Cancel] button

Closes the [Start Debugging] dialog box.  The debugging does not start.

See Also:

-	[Application] page

-	[Source] page

-	[Descriptor] page

-	[Batch Debugging] page


[Batch Debugging] page

 [Command file]

Specifies the name of a command file.  The file name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.  When a command file is specified, the debugger executes batch debugging.

When the file name is specified with a relative path, it is assumed that the file name is a relative file name from the current folder used at the debugger start.  When the extension is omitted, .LOG is used as the extension.

[Browse] button

The [Browse] button located at the right side of the [Command file] is used to open the [File Reference] dialog box.  Using this dialog box, the file to be specified in the [Command file] can be referenced.

[History file]

Specifies a file in which the historical information on the debugging operation and the result of its execution is to be stored.  When the file name is specified with a relative path, it is assumed that the file name is a relative file name from the current folder used at the debugger start.  When the extension is omitted, .LOG is used as the extension.

To execute batch debugging, this parameter cannot be omitted.

[Browse] button

The [Browse] button located at the right side of the [History file] is used to open the [File Reference] dialog box.  Using this dialog box, the file to be specified in the [History file] can be referenced.

[OK] button

Closes the [Start Debugging] dialog box, and starts the debugging.

[Cancel] button

Closes the [Start Debugging] dialog box.  The debugging does not start.

See Also:

-	[Application] page

-	[Source] page

-	[Descriptor] page

-	[Debugging Information] page


[File Reference]Dialog Box

The file reference dialog box helps you select required files.

File Name

Displays the selected file name or the types of file being listed (e.g. *.EXE).

You can enter the file name directly in the text box or select it from the file list.

Alternatively, enter a file name in the text box.  Add a directory name and drive name as required.

Directories

Select the directory with the desired file.  When a directory is selected, the files in it are displayed in the file list.

If the desired directory is not found in the list, select another drive from the drive list.

List Files of Type

Open a drop-down list to select the type of files to be displayed in the file list.

Drives

Open a drop-down list to select the drive with the desired file.  If the drive is changed, the directories on it are displayed in the directory list.

[OK] button

Selects a specified file, and closes the dialog box.

[Cancel] button

Closes the dialog box.  No file is selected.

[Network] Button

Displays the dialog box for connecting to shared network directories.


[Folder Reference] dialog box

Selects a target folder.

[Folder]

Selects a target folder.  If the target folder is not shown in the list, select another drive from the list of drives in [Drive].

[Files of type]

Opens a drop-down file list.  From this list, the type of the files to be displayed in the file list can be selected.

[Drive]

Opens a drop-down drive list.  From this list, the drive that has a target folder can be selected.  When the drive is changed, the folders on the new drive are shown in the folder list.

[OK] button

Selects a specified folder, and closes the dialog box.

[Cancel] button

Closes the dialog box.  No folder is selected.

[Network] button

Opens the [Assign Network Drive] dialog box for connection to the shared folder of the network.


[Folder Specification] dialog box

Specifies a folder in which a specified file is to be stored if an access to the file fails.

[Folder]

Specifies the folder in which the corresponding file is being stored.  The folder name specified in this parameter must not contain quotation marks ('), double quotation marks ("), commas (,), semicolons (;), spaces, or parentheses.

[Browse] button

Opens the [Folder Reference] dialog box.  Using this dialog box, a folder can be referenced.

[OK] button

Closes the dialog box, and restarts the access to the file contained in the specified folder.

[Cancel] button

Closes the dialog box.  Processing is continued by ignoring the access-failed file.


[Font] dialog box

Specifies the font that is to be used in the [Source File] window, [Watch Data] window, [Line Command] window, or [Program List] window.

[Font]

Selects a font from the list.

[Size]

Selects a font size from the list.  The larger the size-indicating number is, the larger the size of the displayed characters is.

[Sample]

Displays the characters that use the font (selected with [Font]) and font size (selected with [Size]).

[OK] button

Closes the dialog box, and changes the font of the active window into the selected font.

[Cancel] button

Closes the dialog box.  The font is not changed.


[Color] dialog box

Specifies the colors that can be used by the debugger.

[Item]

Displays the list of items for which colors can be specified.  Select an item of which color is to be changed.

[Preview]

Displays characters and symbols in the colors selected with [Foreground] and [Background].

[Foreground]

Selects, from the color list, the character color that is to be used in the currently selected item.  When the color of the item is changed, the color selected from the color list is used as the new color of the item.

To select a system color, select the [Standard] button.  This button is valid only when the item has a corresponding system color.

[Background]

Selects, from the color list, the background color that is to be used in the currently selected item.  When the color of the item is changed, the color selected from the color list is used as the new color of the item.

To select a system color, select the [Standard] button.  This button is valid only when the item has a corresponding system color.

[OK] button

Closes the dialog box, and changes the color of the selected item into the specified color.

[Cancel] button

Closes the dialog box.  The color is not changed.

[Reset] button

Resets the specified colors of all of the items for which colors are specifiable to the initial state that was set at shipping.


[Find] dialog box

Retrieves a character string from a source file.

[Find What]

Specifies a character string that is to be retrieved.

[Match Whole Word Only]

Retrieves a character string in word units.  When this item is selected, the system retrieves only the pattern in which one word consists of only the specified character string.

[Match case]

Specifies whether upper-case letters are to be distinguished from lower-case letters at the retrieval of a character string that contains alphabetic characters.

[Direction]

Specifies the retrieval direction from the cursor position (forward direction or backward direction).

[Find Next] button

Retrieves the specified character string from the source file.  Even if this button is clicked, the dialog box is not closed.

[Cancel] button

Closes the dialog box.  The character string is not retrieved.


[Jump] dialog box

Positions the cursor on a specified line in the source file.

[Line number]

Specifies the line on which the cursor is to be positioned.  The specified line number is interpreted in accordance with the statement identification number mode that is valid at present in the [Source File] window.  Immediately after the dialog box is opened, the system sets the number representing the line on which the cursor in the [Source File] window is positioned.

[OK] button

Closes the dialog box, and positions the cursor at the head of the specified line.

[Cancel] button

Closes the dialog box.  The cursor is not positioned on the specified line.


[Re-debug] dialog box

Specifies the conditions required for re-debugging.

[Clear all breakpoints]

When this check box is marked, all of the currently set breakpoints are cleared.

[Clear all watch datas]

When this check box is marked, all of the currently set watch data monitoring operations are cleared.

[Clear watch conditional expression]

When this check box is marked, all of the currently set watch conditional expression operations are cleared.

[Clear all passage counts]

When this check box is marked, all of the currently set passage count points are cleared.

[OK] button

Closes the dialog box, and executes the debugging again.

[Cancel] button

Closes the dialog box.  The debugging is not executed again.


[Specific Execution Condition] dialog box

Executes a program up to a specified position.

[Case]

Selects the condition that causes the program execution stop.

[Line number]

Specifies the statement identification number of the line on which the program execution is to stop.  This item is valid when [Specified position] is selected in [Case].  The line number is interpreted in accordance with the statement identification number mode.

[File name]

Specifies a target file name when [Position where specified file is accessed] is selected in [Case].

[Program name]

When [Specified position] or [Position where specified file is accessed] is selected in [Case], [Program name] must be used to specify the program modifier of the program whose execution is to stop.

When [Entry] or [Exit] is selected in [Case], [Program name] must be used to specify the program name scope.

When [Program name] is omitted, it is assumed that the currently stopped program is specified.

[Verb]

When [Specified verb] is selected in [Case], [Verb] is used to select from the list the type of statement for stop.  Select the check box of the object verb, and mark it.

[OK] button

Closes the dialog box, and executes the program up to the specified position.

[Cancel] button

Closes the dialog box.  The program is not executed.


[Call Stack] dialog box

Displays a program calling path.

[Program name]

Displays the name of a program located on a calling path.  The top program is the currently stopped program.  The calling programs are listed sequentially.

When a program name is double-clicked or when the [Go To] button is selected, the cursor is positioned at the program.

[Go To] button

When the name of a program on a calling path is selected and the [Go To] button is clicked, the dialog box is closed. The cursor is positioned at the source file of the selected program.

[Cancel] button

Closes the dialog box.


[Breakpoint] dialog box

Sets or cancels a breakpoint, or changes the setup conditions of a breakpoint.  A breakpoint cannot be set in a statement in which no objects are created.

[Case]

Selects the condition for breakpoint setup.

[Line number]

Specifies the statement identification number of the statement in which a breakpoint is to be set.  This item is valid when [Set position] is selected in [Case].  The line number is interpreted in accordance with the statement identification number mode.

[Program name]

Specifies the name of a program that contains the position at which a breakpoint is to be set.

When [Set position] is selected in [Case], specify the program modifier of the program in [Program name].  In other cases, specify a program name scope in [Program name].

When [Program name] is omitted, it is assumed that the currently stopped program is specified.

[Conditional expression]

Specifies a conditional expression.  The program execution is stopped only when this conditional expression is satisfied when processing reached the breakpoint.

When no conditional expression is specified for a breakpoint, the program execution is stopped each time processing reaches this breakpoint.

[Cycles]

Specifies a statement passing count.  The program execution is stopped only when the statement passing count is satisfied when processing reached the breakpoint.

When no conditional expression is specified for a breakpoint, the program execution is stopped each time processing reaches this breakpoint.

[List of breakpoints]

Displays a list of information on the currently set breakpoints.  The statement identification numbers are displayed in statement identification number mode.

When one line is selected from this list, the setup contents of the selected breakpoint are copied to the [Line number], [Program name], [Conditional expression], and [Cycles] fields.  When a suspended breakpoint is selected, the contents of these fields are cleared.

Double-clicking one line, deletes the breakpoint on the selected line.  This double-clicking cannot delete a suspended breakpoint.

[Set] button

Sets a breakpoint at the specified position.

[Close] button

Closes the dialog box.

[Delete] button

Deletes the breakpoint that was selected from [List of breakpoints].

[Delete All] button

Deletes all of the currently set breakpoints.

[Enable/Disable] button

Changes the status of the breakpoint that was selected from [List of breakpoints].  If the breakpoint is valid when this button is selected, the breakpoint is invalidated.  If the breakpoint is invalid when this button is selected, the breakpoint is validated.

[Go To] button

Closes the dialog box, and moves the cursor to the position of the breakpoint selected from [List of breakpoints].


[Passage Count] dialog box

Sets or cancels a passage count point, or changes the setup conditions of a passage count point.  A passage count point cannot be set in a statement by which no objects are created.

[Case]

Selects the condition for passage count point setup.

[Line number]

Specifies the statement identification number of the statement in which a passage count point is to be set.  This item is valid when [Set position] is selected in [Case].  The line number is interpreted in accordance with the statement identification number mode.

[Program name]

Specifies the name of a program that contains the position at which a passage count point is to be set.

When [Set position] is selected in [Case], [Program name] must specify the program modifier of the program.  In other cases, [Program name] must specify a program name scope.

When [Program name] is omitted, it is assumed that the currently stopped program is specified.

[List of passage counts]

Displays a list of information on the currently set passage count points.  The statement identification numbers are displayed in statement identification number mode.

When one line is selected from this list, the setup contents of the selected passage count point are copied to the [Line number] and [Program name] fields.  When a suspended passage count point is selected, the contents of these fields are cleared.

Double-clicking one line with the mouse button, deletes the passage count point on the selected line.  This double-clicking cannot delete a suspended passage count point.

[Set] button

Sets a passage count point at the specified position.

[Close] button

Closes the dialog box.

[Delete] button

Deletes the passage count point that was selected from [List of passage counts].

[Delete All] button

Deletes all of the currently set passage count points.

[Reset] button

Resets, to 0, the passage count value of the passage count point selected from [List of passage counts].

[Reset All] button

Resets, to 0, the passage count value of all of the currently set passage count points.

[Output Log] command

Outputs a list of passage count points to the [Line Command] window and the history file.

[Go To] button

Closes the dialog box, and moves the cursor to the position of the passage count point selected from the list.


[Data] dialog box

Displays or changes a data value.

[Data name]

Specifies the data of which value is to be displayed as a data name.

[Program name]

Specifies the program modifier of the program in which the data specified with [Data name] was declared.

When [Program name] is omitted, it is assumed that the currently stopped program is specified.

[Type]

Displays the category and area length of the data.

[Replace]

Displays the character that is to be replaced with a display-disabled code contained in a value.  The replacement character can be specified with the [Environments] dialog box.

[Value]

Consists of an offset area and a data value area.

The offset area indicates the offset from the head of the data area, in units of bytes.  When an internal Boolean item is displayed in automatic format, the offset is indicated in units of bits.

The data value area indicates a data value.  The data value displayed in the data value area can be changed.

[Display format]

Selects a data display format.

When [Automatic] is selected, a data value is displayed in the format that satisfies the rules of the item.

When [Hexadecimal] is selected, a data value is always displayed in hexadecimal format without regard to its category.

[Display] button

Displays the value of the data specified with [Data name].

[Close] button

Closes the dialog box.

[Modify] button

Posts, to the application memory, the value that was modified in the data value area.

[Watch] button

Applies the watch data function to the displayed data.

[Output Log] button

Outputs a data value to the [Line Command] window and history file.


[Data Name List] dialog box

Displays the name of data related to the network database function or presentation file function.  When a network database function statement or a presentation file function statement is executed, the debugger automatically stops the program execution, and displays this dialog box.

[Data name]

Displays a tree-format list of the names of the data related to the network database or presentation file.  At the root of the tree, a subschema name or a presentation file name is displayed.

The mark located at the left side of each item indicates whether the item is expandable in display.   means no expansion display.  means expansion display.

The expansion display or no-expansion display can be selected by using the following methods:

-	Select the [image] item and press the + key.

-	Select the [image] item and press the - key.

-	Select [image] or [image] by clicking it.

The selected item can be moved upwards in the same level, by pressing the CTRL+UP ARROW keys.  The selected item can be moved downwards in the same level, by pressing the CTRL+DOWN ARROW keys.

The selected item can be moved to a higher level, by pressing the LEFT ARROW key.  The selected item can be moved to a lower level, by pressing the RIGHT ARROW key.

[Display/Modify] button

Opens the [Data] dialog box.  The [Data] dialog box can also be opened by using the following methods:

-	Select the file management information or item name from the [Data name] list, and press the ENTER key.

-	Select the file management information or item name from the [Data name] list, by double-clicking it with the mouse button.

[Cancel] button

Closes the dialog box.


[Watch Data] dialog box

Sets or cancels a watch data operation.

[Data name]

Specifies the data to be monitored as a data name.

[Program name]

Specifies the program modifier of the program in which the data to be monitored was declared.  When the [Program name] is omitted, it is assumed that the currently stopped program is specified.

[List of watch datas]

Displays a list of information on the currently set watch data operations.  When the monitor attribute is set for a line, the dollar sign ( $ ) is indicated at the left side of the serial number of the line.

When one line is selected from this list, the setup contents of the selected watch data operation are copied to the [Data name] and [Program name] fields.  When one line is selected by double-clicking it with the mouse button, the watch data monitoring operation is canceled.

[Set] button

Starts the specified watch data operation.

[Close] button

Closes the dialog box.

[Monitor] button

Assigns the monitor attribute to the watch data operation that was selected from [List of watch datas].  Only one watch data operation can have the monitor attribute.  If the monitor stop attribute is already set in another watch data operation when this command is executed, the current monitor attribute is canceled.  Instead, the monitor attribute is set in the newly specified watch data operation.

Selecting the watch data operation for which the monitor attribute is already set and clicking this button cancels the monitor attribute.

[Delete] button

Deletes the watch data operation that was selected from [List of watch datas].

[Delete All] button

Deletes all of the currently set watch data operations.


[Linkage] dialog box

Acquires the data area that was defined with the linkage section of the currently stopped program.

[Current program]

Displays the currently stopped program.

[Data name]

Specifies the name of the data area that is to be acquired for the linkage section.

[OK] button

Closes the dialog box, and acquires the data area specified with [Data name].

[Cancel] button

Closes the dialog box.  The data area is not acquired.


[Watch Conditional Expression] dialog box

Sets or cancels a watch conditional expression operation.

[Current status]

Displays the conditional expression that is being monitored, and displays the program in which the data contained in the conditional expression was declared.  While the watch conditional expression is not being executed, "None" is displayed instead of the conditional expression and program name.

[Conditional expression]

Specifies the conditional expression that is to be monitored.

[Program name]

Specifies the program modifier of the program in which the data contained in the conditional expression to be monitored was declared.  When [Program name] is omitted, it is assumed that the currently stopped program is specified.

[Set] button

Starts the monitoring of the specified conditional expression.

[Delete] button

Cancels the current watch conditional expression operation.

[Close] button

Closes the dialog box.


[Trace] dialog box

Starts or terminates trace information collection.

[Collect trace information]

To start trace information collection, select this check box to insert a mark in it.  To terminate trace information collection, select this check box again to delete the mark.

[OK] button

Closes the dialog box.  Trace information collection is started or terminated in accordance with the specification of the [Collect trace information] check box.

[Cancel] button

Closes the dialog box.  The setup status is not changed.


[Environments] dialog box

Sets the environment for debugging.

The [Environments] dialog box has the following pages:

-	[Operation] page

-	[Input] page

-	[Display] page

-	[Window] page

-	[Sound] page


[Operation] page

Immediately after debugging starts, [Operation page] shows the information that was set at the previous debugging.  The standard value is the initial value required when the debugger is used for the first time.

[Animation speed]

Specifies the execution speed of animation.

A speed of 10 levels can be specified.  When the slowest speed is 0 and the fastest speed is 9, the standard speed is 5.

[Display text of subprograms]

Specifies whether the called programs are to be processed in the animation or backward tracing.

When this check box is selected to insert a mark in it, also the called programs are processed.  When the mark is deleted, the called programs are not processed.  When the standard value is used, the called programs are also processed.

[Display PERFORM nest]

Specifies the nest level of the PERFORM operations that are not to be processed in the animation or backward tracing.  In animation, the PERFORM operations within the specified nest level are animated.  The PERFORM operations with a deeper nest level are executed without animation.  In backward tracing, statements are traced by skipping the statements that are contained in the PERFORM operations with the specified nest level or deeper nest level.

A value from 0 to 99 can be specified as the nest level.  When 0 is specified, all of the nest levels are processed.  The standard value is 0.

[OK] button

Closes the [Environments] dialog box, and updates the environment setup status.

[Cancel] button

Closes the [Environments] dialog box.

[Apply] button

Updates the environment to the [Operation] page setup status without closing the [Environments] dialog box.

Even if this button is not clicked, the environment is updated when another page is opened.

See Also:

-	[Input] page

-	[Display] page

-	[Window] page

-	[Sound] page


[Input] page

Immediately after debugging started, the [Input] page always indicates the standard value.

[Match case]

Specifies whether lower-case letters are to be distinguished from upper-case letters at the retrieval of a data name or program name that contains alphabetic characters.

When this check box is selected to insert a mark in it, lower-case letters are distinguished from upper-case letters.  Therefore, specify lower-case letters and upper-case letters correctly.  When the mark is deleted from this check box, lower-case letters are handled as upper-case letters.  In this case, lower-case letters need not be distinguished from upper-case letters in the specification.  When the standard value is used, lower-case letters are handled as upper-case letters.

[OK] button

Closes the [Environments] dialog box, and updates the environment setup status.

[Cancel] button

Closes the [Environments] dialog box.

[Apply] button

Updates the environment to the [Input] page setup status without closing the [Environments] dialog box.

Even if this button is not clicked, the environment is updated when another page is opened.

See Also:

-	[Operation] page

-	[Display] page

-	[Window] page

-	[Sound] page


[Display] page

Immediately after debugging starts, the [Display] page always indicates the standard value.

[Statement identification number mode]

Specifies the statement identification number mode.  The line number in the [Source File] window is displayed in accordance with this mode.  The statement identification number is interpreted in accordance with this mode.

The statement identification number mode is updated automatically each time the program execution stops.

[Data value]

Specifies a replacement character.  The standard value of the replacement character is a question mark ( ? ).

[OK] button

Closes the [Environments] dialog box, and updates the environment setup status.

[Cancel] button

Closes the [Environments] dialog box.

[Apply] button

Updates the environment to the [Display] page setup status without closing the [Environments] dialog box.

Even if this button is not selected, the environment is updated when another page is opened.

See Also:

-	[Operation] page

-	[Input] page

-	[Window] page

-	[Sound] page


[Window] page

Immediately after debugging starts, the [Window] page indicates the information that was specified in the previous debugging.  The standard value is the initial value required when the debugger is used for the first time.

[Activate the debugger when execution breaks]

Specifies whether the debugger window is to be activated when the program execution stops.

When this check box is selected to insert a mark in it, the debugger is activated at execution stop.  When the mark is deleted, the debugger is not activated at execution stop.  When the standard value is used, the debugger is activated at execution stop.

This function is valid in other than batch debugging.  When program execution stops in batch debugging, the debugger window is not automatically activated.

When program execution is stopped during debugger processing, the information that was displayed by the program is not redisplayed.  Therefore, if this displayed information is overlaid with the debugger main window at execution stop, this information cannot be referenced.  To prevent this, delete the mark from the check box.  This enables the redisplay of the information that was displayed by the program.

[Batch debugging]

Specifies whether the [Source File] window, [Watch Data] window, [Line Command] window, and [Program List] window are to be opened at batch debugging.

When the check box is selected to insert a mark on a window, the window is opened.  When the mark is deleted, the corresponding window is not opened.  When the standard value is used, only the [Line Command] window is opened.

[OK] button

Closes the [Environments] dialog box, and updates the environment setup status.

[Cancel] button

Closes the [Environments] dialog box.

[Apply] button

Updates the environment to the [Window] page setup status without closing the [Environments] dialog box.

Even if this button is not clicked, the environment is updated when another page is opened.

See Also:

-	[Operation] page

-	[Input] page

-	[Display] page

-	[Sound] page


[Sound] page

Immediately after debugging starts, the [Sound] page indicates the information that was specified in the previous debugging.  The standard value is the initial value required when the debugger is used for the first time.

[Sound a beep then execution breaks]

Specifies whether a beep is to be issued when the program execution stops.

When this check box is selected to insert a mark in it, a beep is issued at program execution stop.  When the mark is deleted, a beep is not issued.  When the standard value is used, a beep is issued.

This function is valid in other than batch debugging.

[Sound a beep when execution breaks while batch debugging]

Specifies whether a beep is to be issued when the program execution stops during batch debugging.

When this check box is selected to insert a mark in it, a beep is issued at program execution stop.  When the mark is deleted, a beep is not issued.  When the standard value is used, a beep is not issued.

[OK] button

Closes the [Environments] dialog box, and updates the environment setup status.

[Cancel] button

Closes the [Environments] dialog box.

[Apply] button

Updates the environment to the [Sound] page setup status without closing the [Environments] dialog box.

Even if this button is not clicked, the environment is updated when another page is opened.

See Also:

-	[Operation] page

-	[Input] page

-	[Display] page

-	[Window] page


[Automatic Debugging] dialog box

Starts automatic debugging.

[Command file]

Specifies a command file.  The file name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.

[Browse] button

Opens the [File Reference] dialog box.  Using this dialog box, the file to be specified in [Command file] can be referenced.

[OK] button

Closes the dialog box, and starts the automatic debugging.

[Cancel] button

Closes the dialog box.  Automatic debugging is not executed.


[Output Log] dialog box

Starts or terminates historical information collection.  Historical information is output to a history file.

[Current status]

Displays "During execution" while historical information is being output or displays "Stop" while historical information is not being output.

[History file]

Specifies a history file.  The file name specified in this parameter must not contain quotation marks ( ' ), double quotation marks ( " ), commas ( , ), semicolons ( ; ), spaces, or parentheses.

[Browse] button

Opens the [File Reference] dialog box.  Using this dialog box, the file to be specified in [History file] can be referenced.

[Start] button

Starts historical information output to the history file.

[End] button

Terminates historical information output to the history file.

[Close] button

Closes the dialog box.


[Select Window] dialog box

Selects a [Source File] or [Watch Data] window that is to be activated.

[Windows]

Selects, from the window list, a window that is to be activated.

[OK] button

Closes the dialog box, and activates the selected window.

[Cancel] button

Closes the window.  The selected window is not activated.


[About] dialog box

Displays the version information and copyright information on the COBOL85 debugger.

[OK] button

Closes the dialog box.


Statement identification number

A statement identification number identifies a particular statement or location within a program.  There are several formats and these are shown below.

The position of the statement indicated by the statement identification number sometimes cannot be determined in the search range for the program modifier.  If this occurs, the position of the first statement that appears in the search range of the program modifier is selected.

Statement format

{*section-name  |
*paragraph-name [ {IN | OF} section-name]  |
[ {copy-modifier- | copy-specification/...} ]  line-number[.statement-number] }

Meaning of specification

*section-name	Indicates the first statement in the section section-name.

*paragraph-name [ {IN | OF} section-name]
Indicates the first statement in the paragraph paragraph-name.  If a section name is not specified, the section that contains the current execution position is searched first.  Then, the whole program is searched from the beginning.
If a section name is specified, the specified section is searched.
If the section contains two or more paragraphs of the same name, the first found paragraph is selected.

[ {copy-modifier- | copy-specification/...} ]line-number[.statement-number]
Indicates a statement by line number and statement number A copy modifier and copy specification are used to indicate the position of the statement in a source included from the copy library.


Data name

Specify one of the following as the data name:

-	Identifier

-	Condition-name

-	Index-name

-	Special register

-	Symbolic-constant

-	Functions

If specifying a blank in a data name, enclose the data name with parentheses.  An example is given below.

LIST (DATA01 OF DATA02)


Identifiers

An identifier, excluding a subscript and reference modification, must conform to the COBOL language specifications.

A subscript must be specified in the following format:

Subscript:	{ integer | identifier [ {+|-} integer ] | index-name [ {+|-}integer ] | symbolic-constant [ {+|-} integer ] }

Reference modification must be specified in the following format:

Reference modification:

high-order-end : [ length ]

where, high-order-end/length:

{ integer | identifier [ {+|-} integer ] | symbolic-constant [ {+|-} integer ] }


Condition names

A condition name, excluding a subscript, must conform to the COBOL language specifications.

A subscript must be specified in the following format:

Subscript:	{ integer | identifier [ {+|-} integer ] | index-name [ {+|-} integer ] | symbolic-constant [ {+|-} integer ] }


Index-name

The format of index-names conforms to the COBOL language specifications.


Special registers

Special registers can be specified in accordance with the COBOL language specifications excluding the following:

-	SHIFT-IN

-	SHIFT-OUT

-	ADDRESS OF


Symbolic-constant

The format of symbolic-constants conforms to the COBOL language specifications.


Functions

A function can be specified in the following format:

Function:	{ addr-function | leng-function }

where, addr-function:	FUNCTION ADDR( argument )

leng-function:	FUNCTION LENG( argument )

The argument of the addr-function must be an identifier other than an internal Boolean item.

The argument of the leng-function must be an identifier other than an internal Boolean item, nonnumeric literal, or hexadecimal nonnumeric literal.


Assignment expression

An assignment expression can be specified in the following format:

assignment expression:
{ identifier assignment expression | index-name assignment expression }

identifier assignment expression:
identifier = { identifier | literal | arithmetic expression | index-name | addr-function }

index-name assignment expression:
index-name = { identifier | integer | index-name }

where, addr-function:	FUNCTION ADDR( argument )

Do not insert a blank before and after the equal sign.

The argument of the addr-function must be an identifier other than an internal Boolean item.

Assignment rules conform to the COBOL language specifications.  However, when a hexadecimal constant is assigned to a numeric item, the specified constant must match the number of bytes occupied by the numeric item in memory.  The specified hexadecimal constant is stored in memory as is from the lowest address upward.

When specifying a blank in an assignment expression, enclose the expression with parentheses.  An example is given below.

SET (DATA01 OF DATA02 = "ABC")


Conditional expressions
Conditional expression

A conditional expression can be specified in the following format:

Conditional expression:
or-condition-of-compound-conditions

where, or-condition-of-compound-conditions:
{ and-condition-of-compound-conditions | or-condition-of-compound-conditions OR and-condition-of-compound-conditions }

where, and-condition-of-compound-conditions:
{ relation-condition-of-simple-conditions | and-condition-of-compound-conditions AND relation-condition-of-simple-conditions }

where, relation-condition-of-simple-conditions:
{ identifier | literal | arithmetic-expression | index-name | addr-function } relational-operator  {  identifier | literal | arithmetic-expression | index-name | addr-function }

where, relational-operator:

{[IS][NOT] GREATER [THAN]|

 [IS][NOT] LESS [THAN]|

 [IS][NOT] EQUAL [TO]|

 [IS][NOT] > |

 [IS][NOT] < |

 [IS][NOT] = |

 [IS] GREATER [THAN] OR EQUAL [TO]|

 [IS] >= |

 [IS] LESS [THAN] OR EQUAL [TO]|

 [IS] <= }

addr-function:	FUNCTION ADDR ( argument )

Literals must not be specified at both of the left side and right side of a conditional expression.

One or more spaces must be placed before and after the reserved word that constitutes relational and logical operators OR and AND.  No spaces need be placed before and after the relational operators >, <, =, >=, and <=.

When the conditional expression is for the relational condition for Boolean objects or for the relational condition for point data (including ADDR function), "[IS]{NOT}EQUAL[TO]" or "[IS][NOT]=" must be used.

The argument of the ADDR function must be an identifier other than an internal Boolean item.

The WHEN-COMPILED special register cannot be specified in a conditional expression.

To specify spaces in a conditional expression, the conditional expression must be enclosed in parentheses as shown in the following example:

DATACHK (DATA01 OF DATA02 = "ABC")


Program modifier

Specifies the program that contains either the statement indicated by a statement identification number or the data indicated by a data name.

Specification format

{ external-program  |
[ external-program].internal-program }

Meaning of specification

external-program	Specifies an external program.

[external-program].internal-program
Specifies an internal program.
If specification of an external program is omitted, the external program for the implicit program name is used.


Program name scope

A program name scope specifies the program processed by a command.

Specification format

{{ external-program  |
external-program.internal-program  |
external-program.*  |
external-program.internal-program.* }...|
* |
& }

Meaning of specifications

external-program	Specifies a specific external program.

external-program.internal-program
Specifies a specific internal program.

external-program.*	Specifies a specific external program and all internal programs included in the external program.

external-program.internal-program.*
Specifies a specific internal program and all internal programs included in the internal program.

*	Specifies all programs.

&	Specifies the program being halted.


Arithmetic expressions

An arithmetic expression can be specified in the following format:

Arithmetic expression:
{ primary-expression | +primary-expression | -primary-expression }

where, primary-expression:
{ identifier | literal | ( arithmetic-expression ) | leng-function }

where, leng-function:	FUNCTION LENG ( argument )

The identifier must be a numeric item.

The literal must be a numeric literal or figurative constant ZERO, ZEROS, or ZEROES.

The argument of the leng-function must be an identifier other than an internal Boolean item, nonnumeric literal, or hexadecimal nonnumeric literal.


implicit program name

The program modifier assumed to be specified when the IN operand is omitted is called the implicit program name.

The implicit program name is automatically set when program execution is interrupted.

If execution is interrupted in a debuggable program, the halted program is used.

If execution is interrupted in a program that is not debuggable, the nearest debugged program on the calling path is used.

If no debuggable programs are running when execution is interrupted, no implicit program name is set.  In this case, the IN operand cannot be omitted.

A debuggable program is one in which the program has been compiled for debugging and has a debugging information file available to the debugger.

Use the SCOPE command to change the implicit program name.


Line numbers

A line number is an identifier of a line in a COBOL source program.  A line number is interpreted as an editor line number or a relative line number in accordance with the statement identification number mode.


Editor line numbers

An editor line number is written to the sequence number area in a COBOL source program


Relative line numbers

A relative line number begins with the first line in a file and increases by one with each successive line.


statement number

This is the number that identifies each of the statements on one line.  The number 1 is assigned to the first statement, and the number is incremented by 1 for each statement.


copy modifier

The copy modifier is the number assigned to each library text included by the compiler.  This number is prefixed to the line number that specifies a statement in the included library text.

Example:

Set a breakpoint at the statement on line 6800 in the library text for the fifth included library:

BREAK 5-6800


copy specification

A copy specification indicates the line number of a COPY statement.  It indicates the line number of the COPY statement that included the text and, if necessary, can include the statement number (within that line).

Specification format

line-number[.statement-number]

Example

Set a breakpoint at the statement on line 7000 in the library text included by the COPY statement on line 6000.  The COPY statement is also in the library text included by the COPY statement on line 5000.

BREAK 5000/6000/7000


Statement keyword

A statement keyword specifies the type of statement.  The following types can be specified:

-	Conditional statement (excluding EVALUATE statement in which conditional expression is not written)

-	Unconditional statements other than the following statements:

-	ENTRY statement

-	PERFORM statement of format 1

-	PERFORM statement with NO LIMIT specification

-	END-PERFORM statement (of format 1, excluding PEFORM statement)

-	WHEN specification in EVALUATE statement (excluding WHEN OTHER specification and WHEN ANY specification)

-	NEXT SENTENCE specification

-	Program end header (END PROGRAM)


statement identification number mode

Holds information about whether a statement identification number is to be interpreted as an editor line number or relative line number  The mode is automatically set when program execution is interrupted.

If execution is interrupted in a program compiled with the NUMBER option, the mode is set for interpretation as editor line numbers.

If execution is interrupted in a program compiled with the NONUMBER option, the mode is set for interpretation as relative line numbers.


Batch debugging

In batch debugging mode, all debugging operations are executed automatically by specifying a command file and a history file at debugging start.


Automatic debugging

In automatic debugging mode, after debugging starts, a series of debugging operations are automatically executed by specifying a command file.


Command file

A command file contains a series of line commands.  This file is read by the debugger at batch debugging or automatic debugging.

A command file can be created using a text editor.  The history file that was created in the past debugging can also be used as a command file.

The AUTORUN command that is specified in a command file is invalid.


History file

A history file is a file in which debugging operation information and the result of its execution can be saved.  A history file can also be used as a command file in automatic debugging or batch debugging.


Replacement character

When a data value cannot be displayed in the [Data] dialog box, [Watch Data] window, or [Line Command] window, a replacement character can be displayed instead of the code of the data value.  A one-byte character except for a quotation mark ( ' ), double quotation mark ( " ), parenthesis, and space can be specified as a replacement character.


Debug-object programs

Executable programs (EXE) or a dynamic link library called from an executable program can be debugged.


Debugged programs

A COBOL source program that is included in debug-object programs and can be actually debugged is called a debugged program.  The debugger requires a debug information file to debug a program to be debugged.  See the related user's guide for explanations of specifications at compile time and linkage time for debugging information file creation.


debugging information file

This is the file the debugger reads to debug debugged programs.  The debugging information file is created by the compiler and contains information such as statement expansion positions and data assignment positions.


File name

A file name defined in a file description entry or a report-name defined in a report group description entry.


Re-debugging

Program debugging can be forcibly terminated, and the same program can be redebugged from the beginning.


Breakpoint

When program execution reaches a statement in which a breakpoint is set, the stop condition is checked.  When the stop condition is satisfied, the program execution stops.


Watch Data

Function for monitoring specified data.  The value of the data that is being monitored is always displayed in the [Watch Data] window.  When the data value is changed, the data value displayed in the window is also updated automatically.


Monitor

Function for monitoring data value change.  When a specified data value is changed, the program execution is stopped.


Serial-no

A serial number is assigned to a watch data operation that is set.  A serial number is used to identify a watch data operation.


Watch conditional expression

Function for monitoring a conditional expression.  When a specified conditional expression is satisfied, the program execution is stopped.


Passage count point

A passage count point can be set in a statement in a program.  When the program is executed, the system counts how many times the statement was executed.


Historical information collection

Function for collecting and saving as historical information the debugging operation information and the result of such debugging


[File] menu

-	[Start Debugging]

-	[Recent Debugging]

-	[Exit]


[Edit] menu

-	[Copy]


[View] menu

-	[Font]

-	[Color]

-	[Automatic Format]

-	[Hexadecimal Format]

-	[Toolbar]

-	[Status bar]


[Search] menu

-	[Find]

-	[Find Previous]

-	[Find Next]

-	[Jump]


[Continue] menu

-	[Re-debug]

-	[Go]

-	[Animate]

-	[Break]

-	[Change Start Point to Cursor]

-	[Run to Cursor]

-	[Step Into]

-	[Step Over]

-	[Run to Next Program]

-	[Specific Execution]

-	[Specific Execution Condition]


[Debug] menu

-	[Where]

-	[Call Stack]

-	[Breakpoint]

-	[Passage Count]

-	[Update Passage Count Display]

-	[Data]

-	[Data Name List]

-	[Watch Data]

-	[Linkage]

-	[Watch Conditional Expression]

-	[Trace]

-	[Backward Trace]-[Previous Statement]

-	[Backward Trace]-[Next Statement]

-	[Backward Trace]-[Previous Procedure]

-	[Backward Trace]-[Next Procedure]


[Option] menu

-	[Environments]

-	[Automatic Debugging]

-	[Output Log]


[Window] menu

-	[Cascade]

-	[Tile Horizontally]

-	[Tile Vertically]

-	[Arrange Icons]

-	[Close All]

-	[Program List]

-	[Line Command]

-	[Window names]


[Help] menu

-	[Help Topics]

-	[About]


Basic operations of debugger

-	Copying a character string

-	Retrieving a character string

-	Positioning the cursor to a specified line

-	Sounding

-	Displaying a source file

-	Displaying a copy library file

-	Displaying a subschema descriptor file

-	Displaying a screen and form descriptor

-	Displaying a file descriptor

-	Displays a program list

-	Debugging using line commands

-	Changing the display format


Changing the display format

-	Changing the font

-	Changing the colors

-	Specifying the toolbar display

-	Changing the toolbar position

-	Specifying the status bar display

-	Activating another window or icon

-	Rearranging the windows or icons

-	Displaying two parts of the same program simultaneously

-	Changing the data display format


Debugging operation

-	Starting debugging

-	Quitting debugging

-	Executing a program unconditionally

-	Setting a breakpoint

-	Canceling a breakpoint

-	Forcing Program Execution to Break

-	Tracing the processing flow during program execution

-	Referencing and changing Data Values

-	Skipping the unnecessary processing

-	Stopping the program execution at data value changing

-	Stopping the program execution at specific value setting

-	Determining Where Execution Breaks

-	Viewing the Calling Path

-	Checking the statement exection count

-	Referencing the status of the currently used debug function

-	Tracing the past execution path

-	Automating Debugging

-	Restarting a program

-	Allocating a Data Area in the Linkage Section

-	Viewing and Modifying the Debug Environment

-	Saving the debugging operation results into file

-	Referencing a program list

-	Executing a program up to a target position


Executing a program up to a target position

-	Executing only one statement

-	Executing up to cursor position

-	Executing up to the next program

-	Executing by specifying specific execution conditions

See Also:

-	RUNTO command


Screen configuration

-	Main window

-	[Source File] window

-	[Watch Data] window

-	[Line Command] window

-	[Program List] window

-	Status bar

-	Menus

-	Toolbar

-	Shortcut menu


Line commands

Debugging can be executed by entering a line command from the [Line Command] window.  Each line command must be specified in accordance with its coding format.

-	AUTORUN command

-	BREAK command

-	CALLS command

-	CONTINUE command

-	COUNT command

-	DATACHK command

-	DELCOUNT command

-	DELDCHK command

-	DELDTR command

-	DELETE command

-	DELMON command

-	DTRACE command

-	ENV command

-	LINKAGE command

-	LIST command

-	MONITOR command

-	QUIT command

-	RERUN command

-	RUNTO command

-	SCOPE command

-	SET command

-	SKIP command

-	STATUS command

-	WHERE command

See Also:

-	Font and Symbols describing line command format


Toolbar

Displays the buttons required for command execution.  Each button name can be displayed by positioning the pointer on the button.  The toolbar display mode or the no-display mode can be selected using the [Toolbar] command in the [View] menu.  The toolbar can be removed by dragging it.


When the mouse cursor is positioned at a command displayed in a menu or when a button displayed in the toolbar is clicked, the explanation message of the command is displayed.


When the program execution is stopped, the type of the event that caused the program stop is displayed.


While the [Source File] window is active, the current cursor position is displayed in the "line-column" format.

The [Jump] dialog box can be opened by double-clicking this field with the mouse button.


When lower-case letters are to be handled as upper-case letters, "Equivalent" is displayed.  When lower-case letters are not to be handled as upper-case letter, "Not equivalent" is displayed.

The [Input] page of the [Environments] dialog box can be opened by double-clicking this field with the mouse button.


While trace information is being collected, "Trace" is displayed.

The [Trace] dialog box can be opened by double-clicking this field with the mouse button.


While historical information is being collected, "Log" is displayed.

The [Output Log] dialog box can be opened by double-clicking this field with the mouse button.


[Start Debugging] command

Starts debugging newly.


[Recent Debugging] command

Displays the programs that were debugged recently, and starts the debugging of a program selected from these displayed programs.


[Exit] command

Stops the debugging operation, and terminates the debugger.


[Copy] command

Copies selected data from the [Source File] or [Line Command] window to the clipboard.


[Font] command

Specifies a font that is to be used in each window.


[Color] command

Specifies the colors of characters, background, etc.


[Automatic Format] command

Displays data in the [Watch Data] window, using the automatic format.


[Hexadecimal Format] command

Displays data in the [Watch Data] window, using the hexadecimal format.


[Toolbar] command

Specifies the toolbar display mode or no-display mode.


[Status bar] command

Specifies the status bar display mode or no-display mode.


[Find] command

Retrieves a specified character string from the active [Source File] window.


[Find Previous] command

Retrieves a specified character string in the backward direction from the cursor position.


[Find Next] command

Retrieves a specified character string in the forward direction from the cursor position.


[Jump] command

Positions the cursor at a specified position in a source file.


[Re-debug] command

Forcibly terminates the current program debugging, and redebugs the same program from the beginning.


[Go] command

Executes a program.


[Animate] command

Executes a program while executing animation.


[Break] command

Forcibly terminates the current program execution.


[Change Start Point to Cursor] command

Changes the processing stop position from the current breakpoint to the cursor point.


[Run to Cursor] command

Executes a program up to the current cursor position.


[Step Into] command

Executes only one statement in a program.  When this command is executed in a statement that calls a subprogram, processing stops inside the called subprogram.


[Step Over] command

Executes only one statement in a program.  When this command is executed in a statement that calls a subprogram, the called subprogram is executed then processing stops at the next statement.


[Run to Next Program] command

Executes a program up to the entry of the next program.


[Specific Execution] command

Executes a program in accordance with the condition specified in the [Specific Execution Condition] dialog box.  This command can be specified only when a specific execution condition is being set.


[Specific Execution Condition] command

Executes a program until a specified program-execution-stopping condition is satisfied.


[Where] command

Positions the cursor at the current breakpoint.


[Call Stack] command

Displays a program calling path.


[Breakpoint] command

Sets or cancels a breakpoint or changes the breakpoint setup status.


[Passage Count] command

Sets or cancels a passage count point or changes the passage-count-point setup status.


[Update Passage Count Display] command

Distinguishes statements not passed from already-passed statements in accordance with the latest information, by assigning two different colors to these statements.


[Data] command

Displays or changes a data value.


[Data Name List] command

Displays a list of the names of the data related to the presentation file or network database.


[Watch Data] command

Sets or cancels a data monitoring operation.


[Linkage] command

Acquires the data area of a linkage section.


[Watch Conditional Expression] command

Sets or cancels a watch conditional expression operation.


[Trace] command

Starts or terminates a trace information collection operation.


[Backward Trace]-[Previous Statement] command

Traces a program in units expressed in statements in the reverse direction of the program execution direction.  This command can be used only while trace information is being collected.


[Backward Trace]-[Next Statement] command

Traces a program in units expressed in statements in the program execution direction.  This command can be used only while trace information is being collected.


[Backward Trace]-[Previous Procedure] command

Traces a program in units expressed in procedures in the reverse direction of the program execution direction.  This command can be used only while trace information is being collected.


[Backward Trace]-[Next Procedure] command

Traces a program in units expressed in procedures in the program execution direction.  This command can be used only while trace information is being collected.


[Environments] command

Displays or changes a debugging environment.


[Automatic Debugging] command

Starts an automatic debugging operation.


[Output Log] command

Starts or terminates a historical information output operation.


[Cascade] command

Displays opened windows by overlapping them so that each title bar is visible.


[Tile Horizontally] command

Rearranges opened windows so that all of these windows do not overlap with each other.


[Tile Vertically] command

Rearranges opened windows so that all of these windows do not overlap with each other.


[Arrange Icons] command

Arranges icons at the left bottom of the main window when windows are minimized.


[Close All] command

Closes all of the currently opened windows.


[Program List] command

Opens the [Program List] window.  If the [Program List] window is already opened when this command is executed, the [Program List] window is activated.


[Line Command] command

Opens the [Line Command] window.  If the [Line Command] window is already opened when this command is executed, the [Line Command] window is activated.


[Window Names] command

Displays a list of the names of the [Source File] windows and [Watch Data] windows.  An arbitrary window contained in this list can be activated by selecting it.


[Help Topics] command

Displays the help information on the COBOL85 debugger.


[About] command

Displays the version and copyright information on the COBOL85 debugger.


[Open Library]/[Open file name] command

Displays a copy library file, screen and form descriptor, or file descriptor in the [Source File] window or displays a subschema definition file in the [Source File] window.


[Set Breakpoint]/[Delete Breakpoint] command

Sets a breakpoint in the statement having the cursor.  When a breakpoint is already set in the statement having the cursor, the breakpoint is deleted from this statement.


[Set Passage Count]/[Delete Passage Count] command

Sets a passage count point in the statement having the cursor.  When a passage count point is already set in the statement having the cursor, the passage count point is deleted from this statement.


Title bar

A window or a dialog box can be moved by dragging the title bar with the mouse.  A window can be maximized or can be returned to the previous size and position by double-clicking the title bar with the mouse.


Scroll bar

Scroll bars are displayed at the right edge and at the bottom of a window.  The contents of the window can be scrolled by dragging the scroll box with the mouse or by clicking the scroll arrow.


Split box

A small box located at the top of the vertical scroll bar of a [Source File] window.  Two different parts of one source file can be displayed simultaneously by dragging the split box to the split position.  To cancel the split state, double-click the split bar with the mouse button.


Split bar

A boundary line displayed when one [Source File] window is divided into two parts.  The size of each part of the split window can be changed by dragging the split bar to the change position.  To cancel the split state, double-click the split bar with the mouse button.


Maximize button

A window can be maximized by clicking the [image] button located in the upper right-hand corner of the window.  The window can be returned to the previous size and position by double-clicking the title bar with the mouse button.


Maximize button

A window can be maximized by clicking the [image] button located in the upper right-hand corner of the window with the mouse button.  The window can be returned to the previous size and position by double-clicking the title bar with the mouse button.


[Maximize] command

A window can be maximized by selecting [Maximize] by clicking the mouse button.  The window can be returned to the previous size and position by double-clicking the title bar.


[Maximize] command

A window can be maximized by selecting [Maximize] by clicking the mouse button.  The window can be returned to the previous size and position by double-clicking the title bar.


Minimize button

A window can be minimized by clicking the [image] button located in the upper right-hand corner of the window.  The window can be returned to the previous size and position by double-clicking the icon.


Minimize button

A window can be minimized by clicking the [image] button located in the upper right-hand corner of the window.  The window can be returned to the previous size and position by double-clicking the icon.


[Minimize] command

A window can be minimized by selecting [Minimize] by clicking the mouse button.  The window can be returned to the previous size and position by double-clicking the icon.


[Minimize] command

A window can be minimized by selecting [Minimize] by clicking the mouse button.  The window can be returned to the previous size and position by double-clicking the icon.


Close button

An application or a window can be closed by clicking the [image] button located in the upper right-hand corner of the window.


[Close] command

An application or a window can be closed by clicking [Close].


Restore button

A window can be returned to the previous size and window by clicking the [image] button located in the upper right-hand corner of the window.


Restore button

A window can be returned to the previous size and window by clicking the [image] button located in the upper right-hand corner of the window and by clicking the mouse button.


[Restore] command

A window can be returned to the previous size and window by clicking [Restore].


Frame of window

A frame line around a window.  The shape or size of a window can be changed by dragging the frame line.  The size of a window can be changed in both the vertical and horizontal directions simultaneously by dragging the corner of the window.


[Move] command

A window can be moved using arrow keys of the keyboard by selecting [Move] by clicking the mouse button.


[Size] command

The size of a window can be changed using arrow keys of the keyboard by selecting [Size] by clicking the mouse button.


[Next] command

Processing can be moved to the next window by selecting [Next] by clicking the mouse button.


[Next] command

Processing can be moved to the next window by selecting [Next] by clicking the mouse button.


[Switch To] command

An application can be switched into another application by selecting [Switch To] by clicking the mouse button.