UPDATE LIBRARY (Update a 349X library)

Privilege class

To issue this command, you must have system privilege or unrestricted storage privilege.

Parameters

library_name (Required)

Specifies the name of the library to be updated.

SHAREd

Specifies that this library is shared with other servers in a storage area network (SAN). You must issue this command from the server defined as the primary library manager for the shared library. This parameter is required for libraries defined to a library manager and for libraries used for NDMP operations. Specify SHARED=YES to update a library that is not currently shared.

Important: If a library has a path from a data mover (such as a NAS file server) but no connection to the server, the library cannot be shared with another server.

AUTOLabel

Specifies whether the server attempts to automatically label tape volumes. This parameter is optional.

To use this option, you must check in the tapes with CHECKLABEL=BARCODE on the CHECKIN LIBVOLUME command.

No

Specifies that the server does not attempt to label any volumes.

Yes

Specifies that the server only labels unlabeled volumes.

OVERWRITE

Specifies that the server attempts to overwrite an existing label. The server overwrites existing labels only if both the existing label and the bar code label are not already defined in any server storage pool or volume history list.

WORMSCRatchcategory

Specifies the category number to be used for WORM scratch volumes in the library. This parameter is required if you use WORM volumes. You can specify a number from 1 to 65279. This number must be unique. It cannot be shared with other applications or defined libraries, and it must be different from the other category numbers in this library. This parameter is only valid when 3592 WORM volumes are used.

Restriction: This parameter can only be updated if the device class WORM parameter is set to YES and the WORMSCRATCHCATEGORY currently has no defined value.

RESETDrives

Specifies whether the server preempts a drive reservation with persistent reserve when the server is restarted or when a library client or storage agent reconnection is established.

If persistent reserve is not supported, the server completes a reset of the path to the target device.

If persistent reserve is not supported, the server is not able to reset the path to the target device.

Support for persistent reservation has the following limitations:

• If you are using the Tivoli® Storage Manager device driver, persistent reserve is only supported on some tape drives. See Technote 1470319 for details.
• If you are using the IBM® device driver, persistent reserve must be enabled at the device driver level. See the IBM Tape Device Drivers Installation and User's Guide for information about driver configuration.
• If you are using a virtual tape library that is emulating a supported drive, it might not support persistent reserve.

The following table describes the three possible configurations for drives that are attached to NAS devices.

Table 1. Configurations for drives that are attached to NAS devices.

Library device configuration	The behavior for persistent reserve
The library device is attached to the Tivoli Storage Manager server, and the tape drives are shared by the server and the NAS device.	Drive reservation preemption is supported when the NAS device supports persistent reserve and it is enabled. For more information about setting persistent reserve, see the documentation for your NAS device.
The library device is attached to the Tivoli Storage Manager server and the tape drives are accessed only from the NAS device.	Drive reservation preemption is not supported. If you enable persistent reserve on the NAS device for these drives and a reservation is set by the NAS device but never cleared, you must use another method to clear the reservation.

Yes

Specifies that drive preemption through persistent reserve or target reset are used.

No

Specifies that drive preemption through persistent reserve or target reset are not used. The RESETDRIVES parameter must be set to YES in a clustered environment when SHARED=NO.

Yes

Specifies that drive preemption through persistent reserve is used.

No

Specifies that drive preemption through persistent preserve is not used.

Note: A library manager will not be able to break a drive reservation if the system that has the drive reservation is not configured to use persistent reservation.