Load program dialog box

Depending on the programming language and platform of the program you are debugging, select the appropriate tab for a description of the controls and control groups. The tabs cover the following categories of programming languages on various platforms:

The table below describes the push buttons that appear in the Load Program dialog box. The names of control groups and subgroups appear in italics, and control names appear in bold.

Push buttons
Load Loads the selected program and options into the Debugger, then closes the Load Program dialog box.
Cancel Cancels the load operation and closes the Load Program dialog box. All selections are discarded.
Help Displays this help panel.

ngwin.gif (301 bytes)ngaix.gif (307 bytes) Compiled tab

Compiled (Intel/AIX/Solaris) Use the Load Program dialog box to choose a program file to load into the Debugger. You can also define the initial Debugger environment using start-up options found in this dialog box.

Select this tab if you want to debug a program that is compiled into native executable code. This includes programs written in C++ or High Performance Compiled Java.

Specify the name of the program to debug This field incorporates a selection list containing the names of programs recently loaded into the Debugger. Select any name from this list to load that program into the Debugger.

To select a program not named in this list, do one of the following:

  • If you know the name and path of the program, type that name and path directly into this field, or,
  • Click Browse, then use the controls in the resulting file-selection window to find and select a program.
Specify the dominant language the debugger will use Select a language from the selection list. Terms used in Debugger menus and dialog boxes will adjust to suit the language terminology used by the selected language.
Advanced Click Advanced to invoke the Source Search Path dialog box. This dialog box tells the Debugger where to look for source files associated with the program you are debugging.
Enter any program parameters Enter into this text field any arguments you want to pass to the selected program. For example, if your program is designed to read a file name and the /xyz option from the parameter list in that order, enter:
filename /xyz
Select startup behavior You can choose to invoke any combination of the following start-up options when your program is loaded into the Debugger:
Use program profile Check this box if you want to use the breakpoint, monitor, and Application Preferences settings that were associated with your program during your last Debugger session. If you are debugging your program for the first time, the Debugger uses the default Application Preferences settings, with no initially set breakpoints.

Checking this box will also associate and save any changes you make to the monitors and breakpoints with your program when you end your Debugger session.

Attention: If you add or delete lines in your source file, recompile it, and then debug the program again with a saved program profile, line breakpoints may no longer match the code they were initially set for because line breakpoint information is saved by line number, not by the content of the line.

Debug program initialization Select this check box to debug code that executes before the main program entry point is called. You might do this if you are debugging C++ code and you need to debug the constructors for your globally declared C++ class objects (because such objects are constructed before main is entered).
Environment variables for the program to be debugged
Use invoking command window environment Select this option to use the environment of the command window.
Use this application's previous session environment Select this option to use the environment of the previous Debugger session for this application.
Use the initial Debugger (startup) environment Select this option to use the default Debugger environment. This option is the default selection of these three options.
Select local or remote execution of the program Select one of the following options to define the location in which the program being debugged will run.
Local If you select this check box, all program execution and debugging takes place on the local system.
TCP/IP Connection If you select this check box, program execution and I/O takes place on a remote system while debugging control and display remains on the local system. If you choose this option, you must have started a debug engine daemon on the remote system using the irmtdbgc command. You must also provide the following information regarding the remote system:
Host This field incorporates a selection list containing the names of remote hosts recently used by the Debugger. Select any remote host name from this list. If the remote host you want to use is not named in the list, type the name of that host into this field.
Port Enter the port number the remote debug engine daemon is listening on. If you do not specify a port, the default is port 8000.

Remote debugging imposes a limitation in that Browse will only display what is defined for the system that you are looking at. Examples include:

  • On a Windows workstation with no mapped drives, Browse will only display the local file system. If you have mapped a network drive, then Browse will display the local file system and the mapped network drive.
  • On Unix systems, the PATH environment will be used to locate the program.


ngwin.gif (301 bytes)ngaix.gif (307 bytes) Interpreted tab

Interpreted (Intel/AIX/Solaris) Use the Load Program dialog box to choose a program file to load into the Debugger. You can also define the initial Debugger environment using start-up options found in this dialog box.

Select this tab if you want to debug an interpreted program, for example, interpreted Java.
Enter the class name containing main to be invoked

This field incorporates a selection list containing the names of programs recently loaded into the Debugger. Select any name from this list to load that program into the Debugger.

To select a program not named in this list, do one of the following:

  • If you know the name and path of the program, type that name and path into this field.
  • Click Browse, then use the controls in the resulting class-selection window to find and select a class.
Dominant language the debugger will use Select a language from the selection list. Terms used in Debugger menus and dialog boxes will be appropriate for the language you select.

If only one interpreted language is supported for debugging, the selection list is disabled.

Advanced Click Advanced to open the Source Search Path dialog box. This dialog box tells the Debugger where to look for source files associated with the program you are debugging.
Enter any program parameters

Enter arguments you want to pass to the selected program into this text field. For example, if your program is designed to read a file name and the /xyz option from the parameter list in that order, enter:
filename /xyz
Enter any JVM Program Arguments Enter any supported advanced Java Virtual Machine (JVM) arguments that apply to the program being debugged. Using unsupported arguments will cause the Debugger to close.
Select startup behavior You can choose to invoke any combination of the following start-up options when your program is loaded into the Debugger:
Use program
profile
Check this box if you want to use the breakpoint, monitor, and Application Preferences settings that were associated with your program during your last Debugger session. If you are debugging your program for the first time, the Debugger uses the default Application Preferences settings, with no initially set breakpoints.

Checking this box will also associate and save any changes you make to the monitors and breakpoints with your program when you end your Debugger session.

Attention: If you add or delete lines in your source file, recompile it, and then debug the program again with a saved program profile, line breakpoints may no longer match the code they were initially set for because line breakpoint information is saved by line number, not by the content of the line.

Environment variables for the program to be debugged
Use invoking command window environment Select this option to use the environment of the command window.
Use this application's previous session environment Select this option to use the environment of the previous Debugger session for this application.
Use the initial Debugger (startup) environment Select this option to use the default Debugger environment. This option is the default selection of these three options.
Select local or remote execution of the program Select one of the following options to define the location in which the program being debugged will run.
Local If you select this check box, all program execution and debugging takes place on the local system.
TCP/IP Connection If you select this check box, program execution and I/O takes place on a remote system while debugging control and display remains on the local system. If you choose this option, you must have started a debug engine daemon on the remote system using the irmtdbgj command with engine_daemon_parameters. You must also provide the following information regarding the remote system:
Host This field provides a selection list containing the names of remote hosts recently used by the Debugger. Select any remote host name from this list. If the remote host you want to use is not named in the list, type the name of that host into this field.
Port Enter the port number the remote debug engine daemon is listening on. If you do not specify a port, the default is port 8000.

Remote debugging imposes the following limitations:

  • Halt is not supported when remote debugging.
  • Browse will only display local file systems.


ngos400.gif (278 bytes) AS/400 Use the Load program dialog box to load a program into the debugger.

Controls and control groups in this group are used as follows:

TCP/IP name of AS/400 host
Host

Specify the name of the AS/400 host on which you are debugging your applications. You can enter the host name in one of the following formats:

  • An IP address, such as 9.99.99.99
  • A hostname which is defined in your local host table or on a name server to which you link, such as name.name.name.com

Alternatively, you may select the name of the host from the Host field drop down list, which contains debug host names specified in previous debug sessions. Specifying a debug host is mandatory.

Note: To determine the AS/400 TCP/IP address, type GO CFGTCP on an AS/400 command line, and choose menu option 12 = Change local domain and host names. Be careful not to change the local domain name and hostname when you use this option.

Port Number You only need to specify a port if you want to connect to the AS/400 using a port other than the default port. By default, the port number is set to 3001.

Use this field to permanently specify the port used by the AS/400 debug server. Enter a value between 1 and 64,767 that matches the port number specified for the QDBGSVR entry on the AS/400.

Specify the name of the program to add to debug Specify the name of the program you want to start for your debugging session. You can enter the program name using the following formats:
  • Library/program -- The Debugger searches the specified library for the program. If the program is not found in the specified library, an error message is displayed.
  • Program.
  • Class name.
  • Partial path/class.

To locate a Java class that resides on IFS, you can map the IFS network drive to your workstation, and click Browse to select the class on the mapped network drive in the Open dialog box.

Enter any program parameters Enter arguments you want to pass to the selected program into this text field. For example, if your program is designed to read a file name and the /xyz option from the parameter list in that order, enter:
filename /xyz
Use program profile Check this box if you want to use the breakpoint, monitor, and Application Preferences settings that were associated with your program during your last Debugger session. If you are debugging your program for the first time, the Debugger uses the default Application Preferences settings, with no initially set breakpoints.

Checking this box will also associate and save any changes you make to the monitors and breakpoints with your program when you end your Debugger session.

Attention: If you add or delete lines in your source file, recompile it, and then debug the program again with a saved program profile, line breakpoints may no longer match the code they were initially set for because line breakpoint information is saved by line number, not by the content of the line.

Step Into If Step Into is selected, the debugger will stop at the first debuggable statement in your program. If Step Into is not selected, you will be able to browse your program source and set breakpoints. Once all breakpoints are set, pressing the Run push button will cause the debugger to stop at the first debuggable statement of your program.

If you wish to debug program initialization, do not select Step Into.

Debug Java Select this check box to create a JVM job on the AS/400 for the debug session.
Debugger Settings Click Debugger Settings to invoke the Debugger Settings dialog box. The Debugger Settings dialog box allows you to specify Debugger options, JVM creation settings and batch job creation settings.
Push buttons
Load Loads the program that was specified. Invocation options specified in the dialog box also load and the Load program dialog box closes.
Cancel Cancels the load operation and closes the Load program dialog box. All selections are discarded.
Help Displays this help panel.