Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 18 Processing in Debug Mode : Using the Rule Debugger

Using the Rule Debugger
Processing Rules in Debug Mode
Using the Rule Debugger, you can process your rules in debug mode. In debug mode, you can view and modify the execution state of a rules program. You can choose particular events, called break events, that are of interest to you and have the Debugger suspend the execution of the rules program when these events occur. When execution is suspended, you can issue commands to examine the state of execution or change the values of:
and then instruct the Debugger to resume the execution of the rule.
How to Invoke and Navigate the Rule Debugger
Invoke the Debugger from one of the following places:
DB debug rule ==> rulename<Enter>
If you do not specify a rule, the Object Manager screen for the Debugger appears. Refer to Chapter 16, Processing in Standard Execution Mode for more information about using the Object Manager.
EX execute rule ==> Debug(rulename)<Enter>
COMMAND ==> DB rulename<Enter>
Using the line command G within the Object Manager screen of the Rule Editor or the Rule Executor.
Main Screen of the Rule Debugger
Any of those methods display the following screen:

 
COMMAND ===>
-------------------------------Debug Information------------------------------
Starting TRANSFERCALL to rule EMPLOYEES_RAISE
--------------------------- Breakevent Control-------------------------------
Break Event Object name
 
PFKEYS: 1=HELP 3=SAVE BREAKS 6=DBGCOM 12=EXIT 14=EXPAND 15=GO 22=REMOVE BREAK

 
Layout of the Rule Debugger Screen
The Rule Debugger screen is divided into three sections:
PF Keys and Commands for the Rule Debugger Screen
The following PF keys and primary commands are available from within the Debugger screen:
Exit the application and return to the starting point for the debugging session (for example, workbench, Object Manager for the Rule Editor).
Stop the debugging process and let the application finish processing.
Save the current break events that are defined and exit one transaction level of the application that is being debugged.
Go to the Debugger Command Editor screen. The cursor must be positioned on a break event. Refer to How to Examine and Modify the Execution State for more information.
Exit the Debugger. Changes made since you last pressed PF4 persist until you exit your TIBCO Object Service Broker session.
Expand the rule that is currently being executed by the Debugger. The action statement that is about to be performed is highlighted.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved