The Debugging Collector window allows you to debug Collectors written in the Novell proprietary language. The left column on the debugger displays the commands for the current script state. The highlighted command is being executed.
The right column on the debugger displays the script’s variables and their current value. The variable list expands as all the script’s variables are used. The variables are color-coded to show new variables in blue, changed variables in red, and variables whose value has not changed since the last step as black.
Figure 16 Debug Collector Window
The
tab displays the events generated using this Collector, and the / tab allows you to upload/download another Collector script file to make modifications.The debugger has the following four controls:
Table 6 Debugger Icons
Icon |
Action |
Description |
---|---|---|
![]() |
|
Runs the script until the next breakpoint is encountered. |
![]() |
|
Proceeds one instruction at a time. |
![]() |
|
Pauses the running script. |
![]() |
|
Stops the script. |
The
list and the list are not displayed in the debugger when the script is running. To see the list and the list, the debugger must be Stepping, Paused, or Stopped.You can view events as well as upload and download the Collector’s script from the
tab and the / tab.Multiple Sentinel Control Center users might connect to the same debugging session. For this reason, a Collector remains in Debug mode until one of the users specifically clicks the debugger’s
button.To debug a Collector:
In the main ESM display, locate the Collector that you want to debug.
Right-click the Collector and select
.In the Debug Collector window, select a variable from the list of variables in the right pane, then click the
button.After debugging all the variables, close the Debug window.
Start the Collector to generate the events.
For trademark and copyright information, see Legal Notices.