See Debugging a job for information about the launch configuration.
| Control | Settings |
|---|---|
| Source Lookup Path | By default, the debugger looks for the source in the location from
which the program object is compiled. 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. |
The debugger searches for a program to be debugged on the IBM® i server in the following locations, depending on the format you use to specify the program name in the launch configuration:
| Library/program | The debugger searches the specified library for the program. If it does not find the program in the specified library, an error message is displayed. |
| *LIBL/program | The debugger searches all of the libraries in the library list until it finds the first match for the specified program name. If it does not find the program in the library list, an error message is displayed. |
| *CURLIB/program | The debugger uses the current library to locate the program. If you do not have a library designated as the current library, an error message is displayed. |
| Program | When only the program name is specified, the search path used is the same as that used for *LIBL/program. |
For batch or multithreaded debugging, the library list used is the library list of the connection in the Remote System Explorer from where the debugger is started.
For interactive debugging, the library list consists of all the libraries in the library list of the interactive 5250 job plus the libraries specified in the Remote System Explorer connection properties.
For attaching to a running job, the library list of that job will be used.