Using the log for testing and debugging

Each script has an associated script log. If you run an event or a script, Automator updates the script log with information from that run. It contains error and warning messages, as well as informational messages about exactly which files were populated or backed up to which databases, which data sources were deleted, and so on.

Use the script log with Preview Mode for testing and debugging events and scripts. When you use Preview Mode, Automator goes through the specified events without affecting the database. It writes the information as though it was a real run.

Note

See also Running events and scripts using preview mode.

You can use the script log to view, trace, and correct problems in the script. To open the event dialog box where you defined the event, double-click the lines where the problems occur. Modify the event to correct the problem.

When you use either the Manager Scheduler from the TrueSight Capacity Optimization or the Task Scheduler on Microsoft Windows to run a script, Automator produces a text log which contains the same information, warning, and error messages as the script log. For more information, see Saving-a-script-log-as-a-text-file.

This section describes the following information:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*