Partitioning Process

Information in the SL Console partition workspace is committed to the library controller database only through the Commit (Step 4) screen. The information is lost if any one of the following occurs before you have committed your updates:

You actively log off the SL Console session.

The SL Console session times out or the connection to the library is lost.

You actively refresh the SL Console workspace from the current library controller database. This is done through the Refresh button on the Summary (Step 2) and Design (Step 3) screens.

Caution – For the following reasons, it is recommended that you make the library unavailable to other users before committing your partition workspace changes.

There is no real-time validation of partition boundaries against the library controller database; therefore if you do not make the library unavailable and other users are performing cartridge movements or library configuration changes, configuration conflicts may arise. See “Synchronizing the Display With the Controller Database” on page 31 for details.

The library temporarily drops all connections to HSC or ACSLS hosts when partition configurations changes are committed. The hosts will automatically reconnect, but multiple error messages will be displayed, and cartridge management tasks in progress may fail.

154 SL500 User’s Guide • July 2008

Revision: KA • 96116

Page 186
Image 186
Sun Microsystems manual 154 SL500 User’s Guide July Revision KA