6.1.1 Debugging with the GUI (Windows only)
You can use GUI operations from the JP1/Advanced Shell Editor to debug job definition script files.
The following figure provides an overview of debugging.
|
|
![[Figure]](GRAPHICS/MU050200.GIF)
-
Debugging of a job definition script from the editor is started.
-
A breakpoint is set.
-
When the job definition script is run, it stops at the breakpoint.
-
Debugging stops.
- Organization of this subsection
(1) Output
To run job definition scripts interactively, JP1/Advanced Shell displays the standard output and standard error output on the console at suitable times during debugging execution, unlike during normal execution where the standard output and standard error output are output after execution has completed. However, error messages are also displayed in the Error List window. For details about the Error List window, see 4.7.4 Error List window. The files for the standard output and the standard error output are not created in the spool job directory.
During normal execution, job execution logs are output to the standard error output after job definition scripts have been completed. During debugging, information equivalent to the job execution logs is output to the standard error output.
(2) Initialization of information
When a job definition script is run after already having been run once, information about the shell variables and environment variables that were specified during the previous execution is initialized.
(3) Spool
Each time debug execution is performed on a job definition script, JP1/Advanced Shell creates a spool job folder and stores the following files:
-
Script image: Contents of the script that was run
-
Job execution logs: JP1/Advanced Shell messages
-
Output files: Files created by executing the #-adsh_spoolfile command
-
sysout management file (.sysout)
(4) Notes
If [[conditional-expression]] is used for conditional, the E-Time entry in an execution result message might be the debugger's processing time.