Administrator's Guide


Categories in 349X Automated Libraries

A 349X library has an intelligent control unit that tracks the inventory of all volumes in the library. The control unit tracks the category number of each volume. 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. Typically, a software application that uses a 349X library device uses volumes only in one or more categories that are reserved for that application. To avoid loss of data, ensure that each application sharing the library uses unique categories.

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 ADSM, can then interact with the library control unit to change a volume's category number to a different value. To do this for ADSM, use the CHECKIN LIBVOLUME command (see "Informing the Server about New Volumes in a Library").

The number of categories that ADSM requires depends on whether you have enabled support for 3590 drives by using the ENABLE3590LIBRARY parameter in the server options file.

Without 3590 Support Enabled

An ADSM server reserves two different category numbers in each 349X library that it accesses. One of these categories is used for private volumes that belong to ADSM, and the other is used for scratch volumes that belong to ADSM. See "Private and Scratch Volumes in Automated Libraries" for more information on private and scratch volumes.

When you define a 349X library, you can specify the category numbers for volumes that ADSM owns in that library by using the PRIVATECATEGORY and SCRATCHCATEGORY parameters. The default values for these parameters are acceptable in most situations.

Attention: If you connect other systems or ADSM servers to a single 349X library, ensure that each uses 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.

With 3590 Support Enabled

The ENABLE3590LIBRARY server option supports the use of 3590 tape drives within 349X libraries. If support for 3590 drives is enabled for the server, the server reserves three different categories in the 3494 library. The categories are: private, scratch for 3490 drives, and scratch for 3590 drives.

Attention: If you are currently sharing a 3494 library between ADSM and other applications or systems, be careful when enabling 3590 support to prevent loss of data. See "Enabling Support for IBM 3590 Drives in Existing 3494 Libraries".

When you define a 349X library, you can specify the category numbers for volumes that ADSM owns in that library by using the PRIVATECATEGORY and SCRATCHCATEGORY parameters. The default values for these parameters are the same as when 3590 support is not enabled. However, ADSM automatically creates a third category, a scratch category for 3590 drives, by adding one to the SCRATCHCATEGORY parameter you specify. For example, suppose you enter the following command:

define library my3494 libtype=349x device=3494a
privatecategory=400 scratchcategory=401

ADSM then uses the following categories in the new MY3494 library:

400 (X'190')
Private volumes (for both 3490 and 3590 drives)

401 (X'191')
Scratch volumes for 3490 drives

402 (X'192')
Scratch volumes for 3590 drives

As shown in this example, to avoid overlapping categories, the number you specify for the private category must not be equal to the scratch category plus 1.

Attention: The default values for the categories may be acceptable in most cases. However, if you connect other systems or ADSM 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.

For information on the ENABLE3590LIBRARY server option, see ADSM Administrator's Reference.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]