To create a launch configuration, do the following:
Select the What To Debug tab to bring it to the foreground. Unless otherwise specified, all fields in this tab must be completed before a debugging session can be started.
| Group | Settings |
|---|---|
| Connection | In this section you select the name of an existing Remote System connection from the pull down menu. This connection must be for the IBM® i server which contains the application that you wish to debug. If the connection has not yet been created, click New to launch a wizard which will allow you to create a new connection. |
| Programs or service programs to be debugged | In this section you enter information about the programs and service
programs that you will debug. You can specify multiple programs. Click Add to
add a program or service program to the list.
|
| Step into | If this check box is not selected, the debugger will stop at the first
encountered breakpoint. This could be a profile breakpoint (one that you set
in a previous debugging session) or a source breakpoint (one that you set
in the Debugger editor before starting to debug). If Step into is selected:
|
| Terminate debug session on program completion | If this check box is selected and a valid initial program (but not a service program) is specified in the Programs or service programs to be debugged group, the debugging session will end when the program runs to completion. |
| Update production files | If this check box is selected, the application under debug will be allowed to update database records in production libraries. |
Use this page to specify the IBM i command for starting the application to debug. Interactive applications are typically started via a CALL or user-defined command. They will execute in the interactive job associated with the selected Remote System connection. If no interactive job is associated with the connection, you will be asked to use the STRRSESVR command to associate the interactive job with the specified connection.
You can also click Prompt to invoke a prompt dialog for the specified command, if one is available.
If you completed the What to Debug tab with an initial program, or if you chose the application to debug from the Remote System Explorer or i Project Navigator, the command is automatically created for you.
| Group | Settings |
|---|---|
| Source Lookup Path | By default, the IBM i Default
and Debug engine source containers are listed. The IBM i Default source container allows the debugger to look for the source in the
location from which the program object is compiled. The Debug engine source
container provides the text for views other than *SOURCE view (for example,
*LISTING view or *STATEMENT view). You can specify your own source lookup
path:
|
| Search for duplicate source files on the path | If this check box is not selected, the debugger searches the specified paths in sequence and uses the first occurrence. If this check box is selected, the debugger searches the specified paths and lists all occurrences, allowing you to select one. |
Select the Common tab to bring it to the foreground and do the following: