![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Debugger-Toolbar.webp\")
\n\t\t<\/p>\n
\n<\/p>\n
The \u201cTurboDebugger.bat\u201d TI process DOS version
\nof a debugger has finally been replaced by the new IBM Planning Analytics
\nWorkspace (PAW) debugger. The first
\nrelease of the new functionality is included in PAW version 2.084 releases and
\nabove. In this article we will dive into
\nthe features of the new TI Process Debugger within PAW and how it can help you
\ntroubleshoot issues faster in your Turbo Integrator processes.<\/p>\n
<\/p>\n
Enable the TI Process Debugger:<\/b><\/p>\n
The TI process debug mode can be enabled within PAW Workbench while editing any process. In the top right corner of the process window, the debug button is on the far-right corner of the menu bar. Click this button to display the debug window.<\/p>\n
\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t<\/p>\n
After clicking the debug button, the debug window will display.<\/p>\n
\t\t\t\t\t\t\t\t\t\t\t\t![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Debugger-Slider.webp\")
\n\t\t<\/p>\n
To turn the process debugger on click on the Debugger<\/b> toggle switch highlighted above. Once the debugger is enabled this changes the \u201cRun\u201d button above the debugger button into the \u201cDebug\u201d button.<\/p>\n
\t\t\t\t\t\t\t\t\t\t\t\t![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Debug-button.webp\")
\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n
<\/p>\n
Debug Mode \u2013 Process Execution<\/b><\/p>\n
Before running the process in debug mode, set any breakpoints in the process where you want to pause the process to see the variable definitions.<\/p>\n
\t\t\t\t\t\t\t\t\t\t\t\t![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Script.webp\")
\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n
<\/p>\n
Click the Debug button and define any process parameters required for the TI process.<\/p>\n
\t\t\t\t\t\t\t\t\t\t\t\t![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Parameters.webp\")
\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n
<\/p>\n
Click the Debug button and define any process parameters required for the TI process.<\/p>\n
<\/p>\n
Debugger Window<\/b><\/p>\n
\t\t\t\t\t\t\t\t\t\t\t\t![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Panel.webp\")
\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t<\/p>\n
Debugger Toolbar<\/b><\/p>\n
\t\t\t\t\t\t\t\t\t\t\t\t![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Stepping-Controls.webp\")
\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n
Continue <\/b>\u2013 button runs through process until it reaches the next breakpoint.<\/p>\n
Step over<\/b> \u2013 button will execute current highlighted line of the process. This will allow you to execute a process line-by-line and will execute a line of code that executes a process normally.<\/p>\n
Step in<\/b> \u2013 button is like \u201cStep Over\u201d but running a line of code that executes a process will open sub process in debug mode to continue debugging in that process.<\/p>\n
Step out<\/b> \u2013 button is only used after \u201cStep In\u201d to enter debug mode in a sub process, \u201cStep Out\u201d will finish the execution of the sub process and return to debugging the original process that called it.<\/p>\n
Continue to end<\/b> \u2013 button will continue execution of the TI process and ignore any breakpoints.<\/p>\n
Stop execution<\/strong> \u2013 button will immediately end the execution of the TI process debugging.<\/p>\n Remove all breakpoints<\/strong> \u2013 button removes all breakpoints from the TI process.<\/p>\n Breakpoints<\/strong><\/p>\n The TI process debugger allows you to select any line of code to pause before executing the line of code.<\/p>\n You can set a conditional breakpoint by entering expressions. The expression must evaluate to true or false and can contain references to any variables, parameters and use TI process functions. Potential expression errors can be corrected at run time.<\/p>\n To enter the expression, click the Expression field for the selected breakpoint, and type the expression.<\/p>\n <\/p>\n In the following example, the expression \t\t\t\t\t\t\t\t\t\t\t\t Variables<\/b><\/p>\n When the debugger pauses, the Variables<\/b> section shows the current process variables and their values.<\/p>\n \t\t\t\t\t\t\t\t\t\t\t\t \u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 System Variables<\/b><\/p>\n Select the \u201cSystem variables\u201d toggle button to show the TI process system variables.<\/p>\n \t\t\t\t\t\t\t\t\t\t\t\t Locks<\/b><\/p>\n The debugger provides a window to display lock information during the process execution in debug mode. This provides useful information to determine potential lock contention during the execution of the process.<\/p>\n \t\t\t\t\t\t\t\t\t\t\t\t <\/p>\n The new IBM Planning Analytics Workspace Turbo Integrator process debugger allows developers to debug with the process now versus creating log files with ASCIIOUTPUT functions and analyze and hope you define all the outputs needed to troubleshoot.\u00a0 Developers will become more efficient troubleshooting and resolving problems now once they learn how to properly use the debugger.<\/p>\n\n
pPeriod@='01'<\/code> is entered for the line Prolog(86) breakpoint to stop debugging when the input data is for period \u201806\u2019.<\/p>\n![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Breakpoints.webp\")
\n\t\t<\/p>\n![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Variables.webp\")
\n\t\t<\/p>\n![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Variable-Values.webp\")
\n\t\t<\/p>\n![\"IBM](\"https:\/\/forquestsolutions.com\/staging\/7345\/wp-content\/uploads\/2023\/07\/Locks.webp\")
\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/p>\n