Scripting Guide - SAS

56 Scripting Tools Chapter 4
Debug Scripts
Show the Log in the Script Window
You can view the log inside the script window by right-clicking and selecting Show Embedded Log. This
option makes it easy to edit and run a script, quickly see the results of your changes, and then continue to
develop the script.
The embedded log always appears in the Scripting Index script window but is not available in Application
Builder and the Debugger.
Save the Log
You can also save logs as text files, which can be viewed with any text editor. Double-clicking a log text file
opens it in your default text editor, not in JMP.
1. Make the log window active (click the Log window to make it the front-most window).
2. From the File menu, select Save or Save As.
3. Specify a filename, including the extension .txt on Windows.
4. Click Save.
Debug Scripts
The JSL Debugger helps identify the point at which a script causes an error or fails. Rather than
commenting out portions of the script or adding Print() expressions, you can use the Debugger to find
the problem.
In an open script, click the Debug Script button (or select Edit > Debug Script) to show the script in the
JSL Debugger window. You can also use a keyboard shortcut:
• Press CTRL + SHIFT + R (Windows).
• Press SHIFT + COMMAND + R (Macintosh).
Debugger Window
The Debugger opens in a new instance of JMP (Figure 4.9). The original instance is inoperable until the
script produces something that requires interaction. At that point, the Debugger window becomes
inoperable until you perform whatever action is required. Then control is returned to the Debugger. Close
the Debugger to work again in the original instance of JMP.