![]() |
![]() |
In the following example, an IBM 3494 library containing two drives is attached to the server system.
You must first set up the 349X library on the server system. This involves the following tasks:
define library 3494lib libtype=349x
define path server1 3494lib srctype=server desttype=library device=/dev/lmcp0,/dev/lmcp1
The DEVICE parameter specifies the device special files for the LMCP.
See Defining Libraries and SCSI Libraries. For more information about paths, see Defining Paths.
define drive 3494lib drive01 define drive 3494lib drive02
Both drives belong to the 3494LIB library.
See Defining Drives.
define path server1 drive01 srctype=server desttype=drive library=3494lib device=/dev/rmt0 define path server1 drive02 srctype=server desttype=drive library=3494lib device=/dev/rmt1
The DEVICE parameter gives the device special file for the drive. In this example, each drive is given a device special file name by Tivoli Storage Manager that is unique to the device special file. For more about device names, see Determining Device Special File Names. For more information about paths, see Defining Paths.
define devclass 3494_class library=3494lib devtype=3590 format=drive
query library query drive query path query devclass
See Requesting Information About Libraries, Requesting Information about Drives, Requesting Information about a Device Class, and Requesting Information About Paths.
define stgpool 3494_pool 3494_class maxscratch=20
Key choices:
For more information, see Defining or Updating Primary Storage Pools.
The 349X library manager tracks the category number of each volume in the library. A single category number identifies all volumes used for the same purpose or application. These category numbers are useful when multiple systems share the resources of a single library.
Attention: If other systems or other Tivoli Storage Manager servers connect to the same 349X library, each must use a unique set of category numbers. Otherwise, two or more systems may try to use the same volume, and cause a corruption or loss of data.
Typically, a software application that uses a 349X library device uses volumes in one or more categories that are reserved for that application. To avoid loss of data, each application sharing the library must have unique categories. When you define a 349X library to the server, you can use the PRIVATECATEGORY and SCRATCHCATEGORY parameters to specify the category numbers for private and scratch Tivoli Storage Manager volumes in that library. See Tivoli Storage Manager Volumes for more information on private and scratch volumes.
When a volume is first inserted into the library, either manually or automatically at the convenience I/O station, the volume is assigned to the insert category (X'FF00'). A software application, such as Tivoli Storage Manager, can contact the library manager to change a volume's category number. For Tivoli Storage Manager, you would use the CHECKIN LIBVOLUME command (see Checking New Volumes into a Library).
The number of categories that the server requires depends on whether you have enabled support for 3590 drives. If support is not enabled for 3590 drives, the server reserves two category numbers in each 349X library that it accesses: one for private volumes and one for scratch volumes. If you enable 3590 support, the server reserves three categories in the 349X library: private, scratch for 3490 drives, and scratch for 3590 drives.
The default values for the PRIVATECATEGORY and SCRATCHCATEGORY parameters are the same as when 3590 support is not enabled. However, the server automatically creates the scratch category for 3590 drives, by adding the number 1 to the SCRATCHCATEGORY value you specify. For example, suppose you enter the following command:
define library my3494 libtype=349x privatecategory=400 scratchcategory=401
Tivoli Storage Manager uses the following categories in the library:
To avoid overlapping categories, ensure that the value specifies for the private category is not equal to the scratch category value plus 1.
Attention: The default values for the categories may be acceptable in most cases. However, if you connect other systems or Tivoli Storage Manager servers to a single 349X library, ensure that each uses unique category numbers. Otherwise, two or more systems may try to use the same volume, and cause a corruption or loss of data.
Also, if you share a 349X library with other Tivoli Storage Manager servers or other applications or systems, be careful when enabling 3590 support to prevent loss of data. See Enabling Support for IBM 3590 Drives in Existing 349X Libraries. For a discussion regarding the interaction between library clients and the library manager in processing Tivoli Storage Manager operations, see Performing Operations with Shared Libraries.
The new category that the server creates for 3590 scratch volumes can duplicate a category already assigned to another application and cause loss of data. If you are currently sharing a 349X library with other Tivoli Storage Manager servers or other applications or systems and you enable support for 3590 drives, you need to be careful. The server automatically creates a third category for 3590 scratch volumes by adding one to the existing scratch category for any 349X libraries defined to Tivoli Storage Manager.
To prevent loss of data, do one of the following before enabling 3590 support:
Check in the Tivoli Storage Manager volumes that you put in the insert category in step 1.
For more information about checking in volumes, see Checking New Volumes into a Library.
After taking steps to prevent data loss, enable 3590 support by adding the following line to the server options file (dsmserv.opt):
ENABLE3590LIBRARY YES
Stop and start the server to make this change effective.
Ensure that enough volumes are available to the server in the library. Keep enough labeled volumes on hand so that you do not run out during an operation such as client backup.
checkin libvolume 3494lib search=yes status=scratch checklabel=no
label libvolume 3494lib search=yes checkin=scratch
After you have attached and defined your devices, you can store client data in two ways: