8.6

Table Of Contents
l Click on Skip to ignore the next task or branch and go to the next one. The job file is not
modified in any way.
l Click on View as Text in the Data group of the Debug tab to view the current job file
using a text editor (Notepad by default).
l Click on View as PDFto view the current job file in Adobe Acrobat if it is present (this will
work only for PDFjob files).
l Click on View Metadata to open the data selector and see the current state of the
process' Metadata.
l Click on View as Hex to view the current job file in the internal Hex editor.
l Click on the Stop button to stop the debugging process. If you use Run, Step or Skip
after stopping the process, debugging starts over from the top.
l Use the Set Breakpoint button to tag the currently selected task, branch or condition as a
breakpoint. When you click Run in your process, the process will execute every task until
it reaches a breakpoint and will stop just before the task that is set as a breakpoint.
l Use the Ignore button to disable the task, branch or condition that is currently selected. If
you disable a branch or condition, all tasks inside that branch or condition are ignored
including the output. Note that if you set a task, branch or condition to be ignored, it will
also be ignored at run-time, providing you sent the configuration to the service.
l
Look at the Messages Area pane to see any message generated by the tasks that run
(See " The Message Area Pane" on page673).
l
Use the Debug Information pane to see the current value of any variable in your process
or globally, or to evaluate custom expression. See "The Debug Information Pane" on
page672.
Debugging and Emulation changes
One of the most useful case where debugging is crucial is whenever the job file is converted to
another type of emulation, or if a new data file of a different emulation is used within the
process. For example, if a process starts with a Line Printer data file and the converts it into a
PDF, it is not possible to do any data selection on the PDFbecause the Line Printer emulation
is active by default. The debugging features can easily resolve this limitation.
The first method is used if your process has all the required tasks, but data selections after an
emulation change are necessary.
l Step through the process until you have reached the point after the emulation or data
change.
Page 62