Debugging with OLAP Worksheet

How does OLAP Worksheet help you debug?

OLAP Worksheet allows you to use the TRACE or WATCH commands to interactively step through your program, pausing to examine the current values of OLAP DML objects and specifying how many program lines to execute. It also allows you to set watch points where execution will stop when data values meet certain conditions.

Starting the OLAP DML debugger

Access to the OLAP DML debugger is through the TRACE command, which controls the list of programs that are traced by the debugger. To use the TRACE command, you must be connected to OLAP Services using OLAP Worksheet.

To debug a single program, attach the analytic workspace in which the program resides, and use the TRACE command to add that program to the trace list.

execute 'trace quarter.rpt'

Procedure: Debugging a program located on the OLAP Services computer

To debug a program that is located on the same computer as that on which OLAP Services is running, take the following steps:

1. Choose Connect from the File menu to display the Login dialog box.

2. Specify the server name, password, and computer name in the Login dialog box. If necessary, enter a user name, domain name, and password in the appropriate boxes. For details, refer to the OLAP Worksheet Help system.

3. Choose OK.

4. Once you have connected to the OLAP Services instance, attach the analytic workspace that contains the program that you want to debug. To attach an analytic workspace, enter a DATABASE ATTACH command in the command input window in OLAP Worksheet.

   Example:

   database attach demo
   

5. Add your program to the trace list by entering the TRACE command in the command input window.

   Example:

   trace quarter.rpt
   

   For more information on the TRACE command, see "OLAP DML Debugger Commands".

6. Run your program by entering the program name in the command input window.

   Example:

   quarter.rpt
   

   When your program runs, the debugger suspends the program's execution according to the settings you have specified and displays the double-line arrow prompt in the output pane of the command input window.

7. Either select the debugger commands from the Debug menu or enter the debugger commands in the command input window to examine your program's execution. For more information on using the debugger commands, see "OLAP DML Debugger Commands".

8. Leave the debugging environment by issuing the GO debugger command without any argument to have the program complete execution. If necessary, type go again to leave the debugging environment. The prompt returns to its single-line form (->) in the output pane.