6.2 CUI debugger (UNIX only)
In a UNIX execution environment, you use commands to run the debugger. The following shows the command specification format for the CUI debugger:
0-command-name[1-option]...[1-option][1-operand]
-
First specify options, and then specify operands. Operands includes option names, option values, and any arguments that can be specified in the command. If an operand is specified before an option, the command assumes that all items specified are operands.
-
Specify an option in the format -option-name[1-value]. Multiple options can be specified in any order.
-
Options with no value can be specified consecutively (example: -a -b -c and -abc are treated as being the same). If you specify options consecutively, you can specify a value for the last option (example: in -abc xyz, xyz is the value of the -c option).
-
If an invalid option is specified or a specified value is outside the permitted range of values, an error results.
- Starting the debugger
-
You start the debugger by specifying the -d option and the path name of a job definition script file in the command for executing batch jobs (adshexec command).
The started debugger outputs a prompt character string (adshdb) and then goes onto input wait status. When the debugger accepts a command entered by the user, it executes that command's processing. When the command's processing terminates, the debugger outputs the prompt character string and again goes onto input wait status. The debugger repeats this process until the debugger is terminated.
The debugger also outputs a prompt character string (adshdb) when it goes back into input wait status after receiving a signal while in input wait status.
The format used to start the debugger is shown below. For details about the command for executing batch jobs, see adshexec command (executes a batch job) in 8.3 Shell operation commands.
adshexec -d path-name-of-job-definition-script-file
- Pausing a job definition script
-
You can pause a job definition script by entering the Ctrl + C keys. This method of stopping a job definition script is useful when the job definition script has entered an infinite loop.
- Notes:
-
-
If the Ctrl + C keys are used during execution of an extended script command, extended shell command, standard shell command, or reserved script command, execution stops before the next stoppable instruction after execution of the current command has been completed.
-
If the Ctrl + C keys are used while an external command is executing in the foreground, execution depends on the external command's processing.
-
- Organization of this section
-
-
6.2.7 Commands for restarting execution of the job definition script
-
6.2.8 Performing sequential execution (step and next commands)
-
6.2.13 Displaying breakpoint and watchpoint information (info breakpoints command)
-
6.2.14 Displaying coverage information (info coverage command)
-
6.2.15 Displaying function information (info functions command)
-
6.2.16 Displaying job step information (info jobsteps command)
-
6.2.19 Displaying shell variable information (info variables command)
-
6.2.20 Enabling and disabling the fault injection mode (joberrmode command)