Partition Design and Commit Screens

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.

Caution – Information in the SL Console partition workspace is saved to the library controller database only through the Commit (Step 4) screen. If your SL Console session ends or you refresh the workspace data before you have committed your updates through the Commit (Step 4) screen, you will lose any partition changes you have made through the Summary (Step 2) and Design (Step 3) screens and all associated popups.

Caution – It is recommended that you follow the Resolve Orphaned Cartridges procedure before using this screen.

Caution – This screen updates the library controller database with all partition configuration changes you have made during this SL Console session. Failure to use this screen before logging out of the current SL Console session will cause all your library configuration changes to be lost.

Screen Fields

None

Buttons

Apply

Click to update the library controller database with the current settings from the SL Console partition workspace. The Tools > Partitions—Commit

(Step 4)—Confirm Apply popup appears, indicating whether there are any orphaned cartridges or other errors in the current partition configuration.

Note – This button is grayed out if you have not made any changes to the SL Console partition workspace since the last commit.

? (Help)

Click to display online help for the screen.

See Also

Partitions—Summary (Step 2)

Partitions—Design (Step 3)

Partitions—Design (Step 3)—Verify Results

Partitions—Commit (Step 4)—Confirm Apply

96116 • Revision: KA

Chapter 6 Library Partitioning 221

Page 253
Image 253
Sun Microsystems SL500 manual Apply, ? Help