Saving Event Monitor Data To A File; Displaying Result Code Definitions; Event Monitor Types - Oracle StorageTek SL3000 Manual

Monitoring Library Events
Use the Monitor menu to pause, resume, stop, or clear the event monitor. Use the
4.
Spool File menu to save the event monitor to a file (see
Data to a File"

Saving Event Monitor Data to a File

You may need to send the file to your Oracle support representative to assist in
diagnosing problems.
Open an event monitor (see
1.
In the event monitor window, select Spool File > Start Spooling.
2.
Select a directory and file name. Click Save.
3.
To stop spooling, select Monitor > Stop Spooling.
4.

Displaying Result Code Definitions

Result codes identify the library event type (result codes are the same as library
EventIds).
In SLC, select Tools > Diagnostics. Select the Library in the device tree.
1.
Click the Search tab.
2.
In the Search Type list, select Result Code.
3.
To search for a specific result code, enter the complete code (wildcards or partial
4.
codes are invalid)
To list all result codes, select List All.
Click Search.
5.

Event Monitor Types

There are four types of event monitors: All, Error Warn Info, Error and Warnings, and
Errors. Each monitor type logs events based on the severity of the event. For example,
the Errors monitor only logs error events (see
types).
Each event logged in the event monitor contains the following information:
Time
Identifies when the event occurred.
Device ID
Identifies the library address of the device corresponding to the event.
User
Identifies the user that originated the event. This is "root" for HLI or SCSI host
activities.
I / F
Identifies the interface type of the requester. The interface can be hli, scsi, or default
(for SLC or CLI requests).
15-4 StorageTek SL3000 Library Guide
on page 15-4).
To arrange multiple event monitors on one screen, use the
Note:
Window menu in the upper right corner.
"Starting an Event Monitor"
Severity for a description of the event
"Saving Event Monitor
on page 15-3).