Use this syntax to define a manual library.
Privilege
class
To issue this command, you
must have system privilege or unrestricted storage privilege.
Syntax
>>-DEFine LIBRary--library_name--LIBType--=--MANUAL------------->
.-RESETDrives--=--Yes-----.
>--+-------------------------+---------------------------------->
'-RESETDrives--=--+-Yes-+-'
'-No--'
.-AUTOLabel--=--Yes-----------.
>--+-----------------------------+-----------------------------><
'-AUTOLabel--=--+-No--------+-'
+-Yes-------+
'-OVERWRITE-'
Parameters
- library_name (Required)
- Specifies the name of the library to be defined. The maximum length
of this name is 30 characters.
- LIBType=MANUAL (Required)
- Specifies that the library is not automated. When volumes must
be mounted on drives in this type of library, messages are sent to
operators. This type of library is used with stand-alone drives.
- AUTOLabel
- Specifies
whether the server attempts to automatically label tape
volumes. This parameter is optional. The default is YES.
To use
this option, you need to 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.
- 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, for example,
a storage agent becomes unavailable but is still holding the path
to a drive, persistent reserve allows the server to break the storage
agent’s reservation and access the drive.
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.
- Yes
- Specifies that drive preemption through persistent reserve or
target reset are used. YES is the default for a library that is defined
with SHARED=YES.
- No
- Specifies that drive preemption through persistent reserve or
target reset are not used. NO is the default for a library that is
defined with SHARED=NO. 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. YES is the default for a library that is defined with SHARED=YES.
- No
- Specifies that drive preemption through persistent reserve is
not used. NO is the default for a library that is defined with SHARED=NO.
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.
Example: Define
a manual library
Define a library
named
MANUALMOUNT with the library type of MANUAL.
define library manualmount libtype=manual