What to Debug tab
About this task
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 that contains the job that you want to debug. If the connection has not yet been created, click New to launch a wizard that will allow you to create a new connection. |
| Key | In this field you enter a unique key string, which is used to search the job information on the dynamic debugging data queue on the IBM i host. The syntax of the key must be the same as the one which is written to the data queue for the corresponding job. The wildcard character ('*') is not supported. Key: Enter the key string. The maximum length of the key is 64 bytes. |
| Command to resume application | In this field you enter the command which resumes the application you want to debug. This command will be invoked by the Integrated IBM i Debugger after the debugger attaches to your application. This field is only required if your application is halted in order to specify the debugger invocation and start the debugger. Otherwise, leave this field blank. Command to resume application: Enter the command that will resume your application. After you typed the command, you can click the Prompt button to prompt for the command parameters. |
| Launch timeout (in seconds) | In this field you enter the maximum time in seconds that the debugger launch process should wait for the job information to become available on the dynamic debugging data queue. The debugger launch process ends automatically if no job information matching the specified key is found when the timeout value is reached. Launch timeout: Enter the seconds for the timeout value. If nothing is specified, the value is retrieved from the debugger preference setting for Launch timeout. |
| 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. To debug a running application and stop at the next executable
statement, make sure there is no program or service program specified
in this section.
|
| 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 is selected and a valid program (but not a service program) is specified as the initial program in the Programs or service programs to be debugged table, the debugging session ends when the program runs to completion. |
| Update production files | If the Update production files check box is selected, the application under debug will be allowed to update database records in production libraries. |