Sun Microsystems SL8500 manual Monitoring Library Events

Automated Mode of Operation

5.The library operator uses the SLConsole to unlock the CAP.

6.The library operator opens the CAP, verifies that it is empty, and then closes the CAP.

■The library locks the CAP and audits it to verify that it is empty.

■The library releases the CAP reservation. The CAP is available to all partitions.

7.Partition 2, Host 2 must resubmit the enter request.

■CAP A is reserved to Partition 2, Host 2.

Monitoring Library Events

Library operations are continually monitored by the HBC controller. All events associated with these operations are logged by the HBC card and can be retrieved by operators and service representative for examination.

Library events are accessible from the StreamLine Library Console (see “Event Monitors” on page 103). Events are represented by the following codes:

■Action codes (what command was issued, such as “load drive”)

■Result codes (what was the result of the action requested)

■Known service plan (KSP) diagnosis (what mechanism or component is responsible for the task or fault)

See “Working with the Search Utility” on page 106 to lookup on a result code.

Events are stored under three headings:

■Communication events (host-to-library, library-to-library, and library-to-drive). Data for these events include:

■Date/time stamp

■Library identifier

■Drive identifier

■Requestor

■Interface protocol

■Communication type

■Error events, which include:

■Date/time stamp

■Drive identifier

■Operation type

■Four-digit (hexadecimal) Action Code

■Interrupt level (generated by the hardware or software)

■VOLID for media-related events

■Warning events, which indicate a loss of performance or events that may be indicative of future, fatal errors. The data for these are the same as in error events.

Note – Using the Library Console you an spool event data being monitored to a file.

96154 • Revision K Chapter 4 Library Operation 57