Creating Parameters Files for Network-Attached Automated Libraries

You must create a parameters file for each network-attached library to be included in your environment.

How to Create a Parameters File for Network-Attached Automated Libraries

1. Change to the /etc/opt/SUNWsamfs directory.

   Although the parameters file can be written to any directory, the most common location is /etc/opt/SUNWsamfs.

   ---

   Note - When you created your mcf file, you included the full path name to the parameters files. Ensure that the mcf file points to the correct location for the parameters files that you create.

   ---

2. Create a new file with a name that corresponds to the library that you are configuring.

   For example, for a Sony network-attached library, you might name the file sonyparams.

3. Type a list of parameter entries in the file.

   See the sections in this chapter for details about the parameter entries that should be included for specific library types.

Configuring a StorageTek ACSLS-Attached Automated Library Parameters File

In many respects, the way in which SAM-QFS systems interoperate with StorageTek ACSLS-attached automated libraries is very similar to the way in which they interoperate with direct-attached automated libraries. However, the installation and configuration procedure of a StorageTek ACSLS-attached automated library requires additional steps.

The StorageTek ACSLS software package controls the automated library. Daemon software controls the StorageTek automated library through the ACSAPI interface.

Before you begin, ensure that the following are true and that the StorageTek ACSLS-attached automated library is prepared for inclusion in a SAM-QFS environment:

• The StorageTek ACSLS automated library is operational.

• The StorageTek ACSLS software package is installed and working.

For instructions describing how to create an empty parameters file, see How to Create a Parameters File for Network-Attached Automated Libraries.

Type a list of parameter entries in the StorageTek parameters file.

The following table shows the keywords to use.

The following example shows a parameters file for a StorageTek ACSLS-attached automated library:

#
#  This is file: /etc/opt/SUNWsamfs/stk50
#
hostname = baggins
portnum = 50014
access = some_user  # No white space allowed in user_id
ssi_inet_port = 0
csi_hostport = 0
capid = (acs=0, lsm=1, cap=0)
/dev/rmt/0cbn = (acs=0, lsm=1, panel=0, drive=1) shared
/dev/rmt/1cbn = (acs=0, lsm=1, panel=0, drive=2)

Configuring an ADIC/Grau Automated Library Parameters File

The ADIC/Grau automated library operates within SAM-QFS environments through the grauaci interface. This interface uses the DAS/ACI 3.12 interface that is supplied by ADIC/Grau. For more information about the DAS/ACI interface, see your ADIC/Grau documentation.

Before you begin, ensure that the following are true and that the ADIC/Grau automated library is prepared for inclusion in a SAM-QFS environment:

• The ADIC/Grau automated library is operational.

• The ADIC/Grau library is operating on the Distributed AML Server (DAS).

• Both the avc (avoid volume contention) and the dismount parameters are set to true in the DAS configuration file for this client.

For instructions describing how to create an empty parameters file, see How to Create a Parameters File for Network-Attached Automated Libraries.

Type a list of parameter entries in the ADIC/Grau parameters file.

The parameters are specified as name-value pairs, such as keyword=value. The various parameters identify the ADIC/Grau automated libraries, the drives associated with the libraries, and the server name. All parameter entries are case-sensitive, so enter them exactly as specified in the DAS configuration file and in the mcf file.

The following table shows the parameters that must appear in the ADIC/Grau parameters file.

Comments can appear anywhere on any line, and they must begin with a hash character (#). The system ignores characters to the right of the hash.

If the ADIC/Grau library contains various media types, a media changer exists for each media type. Each media changer has a unique client name in the DAS configuration, a unique library catalog, and a unique parameters file.

The following sample ADIC/Grau parameters file defines one ADIC/Grau automated library that supports DLT tape and one ADIC/Grau automated library that supports a Hewlett-Packard optical drive.

# This is file: /etc/opt/SUNWsamfs/grau50
#
client = DASclient
server = DAS-server
#
# the name "drive1" is from the DAS configuration file
#
acidrive drive1 = /dev/rmt/0cbn
#
# the name "drive2" is from the DAS configuration file
#
acidrive drive2 = /dev/rmt/1cbn

The /var/opt/SUNWsamfs/.grau directory contains diagnostic information that can be useful for troubleshooting.

The system creates files in this directory that are named graulog- eq, where eq is the Equipment Ordinal as defined in the mcf file. For more information, see grauaci(7) in Sun QFS and Sun Storage Archive Manager Reference Manual and mcf(4) in Sun QFS and Sun Storage Archive Manager Reference Manual.

Configuring an IBM 3494 Automated Library Parameters File

The IBM 3494 automated tape library operates in SAM-QFS environments with the assistance of the IBM lmcpd daemon package. You can obtain the IBM lmcpd daemon package from IBM.

Before you begin, ensure that the following are true and the IBM 3494 automated library is prepared for inclusion in a SAM-QFS environment:

• The IBM 3494 automated library is operational.

• The IBM lmcpd daemon package is installed and working.

• The /etc/ibmatl.conf file is configured and working.

• The IBM 3494 automated library can be used as a single physical library or as multiple logical libraries. If you divide this library into multiple logical libraries, create a parameters file for each logical library.

For instructions describing how to create an empty parameters file, see How to Create a Parameters File for Network-Attached Automated Libraries.

Type a list of parameter entries (keyword = value and pathname = value) in the IBM 3494 parameters file.

All arguments are case sensitive. The following table shows how to specify the parameters.

Comments can appear anywhere on any line and must begin with a hash character (#). The system ignores characters to the right of the hash sign.

The following sample /etc/ibmatl.conf file uses information obtained from the mtlib utility supplied by IBM.

#
# This is file: /etc/ibmatl.conf
# Set this file up according the documentation supplied by IBM.
3493a   198.174.196.50  test1

After the lmcpd daemon is running, use the IBM mtlib utility to obtain the device numbers. The following example shows output from mtlib.

# mtlib -l 3493a -D
0, 00145340 003590B1A00
1, 00145350 003590B1A01

The following sample parameters file is for an IBM 3494 library.

#
# This is file: /etc/opt/SUNWsamfs/ibm50
#
name = 3493a    # From /etc/ibmatl.conf
/dev/rmt/1bn = 00145340     # From mtlib output
/dev/rmt/2bn = 00145350     # From mtlib output
access=private
category = 5

Configuring a Sony Network-Attached Automated Library Parameters File

The Sony network-attached automated library operates within the SAM-QFS environment through the DZC-8000S Application Interface Library package. This software package provides the application programming interface (API) to the PetaSite Controller (PSC). For more information about the DZC-8000S interface, see the Sony PetaSite Application Interface Library DZC-8000S, which is available from Sony.

Before you begin, ensure that the following are true and that the Sony network-attached automated library is prepared for inclusion in a SAM-QFS environment:

• The Sony network attached automated library is operational.

• The Sony PSC configuration file is installed and working.

Type a list of parameter entries in the Sony parameters file.

For instructions describing how to create an empty parameters file, see How to Create a Parameters File for Network-Attached Automated Libraries.

The various parameter values identify the Sony automated libraries, the drives associated with the libraries, and the host name. All parameter and value entries are case-sensitive, so type them exactly as they are specified in the configuration file and in the mcf file.

The following table shows the parameters that must appear in the Sony parameters file. All parameters are required.

Comments can appear anywhere on any line, but they must begin with a hash character (#). The system ignores characters to the right of the hash sign.

The following example shows a parameters file for a Sony network-attached automated library.

#
# This is file: /etc/opt/SUNWsamfs/sonyfile
#
# The userid identifies the user during initialization of
# the PetaSite library functions
#
userid = 65533
#
# europa is the hostname for the server running
# the DZC-8000S server code.
#
server = europa
#
# The bin numbers 1001 and 1002 are from the PSC
# configuration file.
#
sonydrive 1001 = /dev/rmt/1cbn
sonydrive 1002 = /dev/rmt/2cbn

About Shared Drives

Typically, the SAM-QFS processes have exclusive control over a library's drives as declared in the host system's mcf file. In many cases, however, drives are defined in individual mcf files that are used by independent copies of SAM-QFS processes. If a process is not using a drive, the drive remains idle.

The shared-drives capability enables two or more mcf files to define the same drive, which makes the drive available to multiple SAM-QFS processes. However, these multiple processes cannot share media. Each SAM-QFS process must still maintain its own set of VSNs.

The shared-drives feature can be useful, for example, when a library is attached to more than one host system in a SAM-QFS environment. The SAM-QFS processes coordinate the use of a drive and keep the drives in a library busy.

You can configure some network-attached libraries to share one or all of the media drives between multiple SAM-QFS processes on multiple host systems. All of the StorageTek ACSLS-attached libraries support shared drives in SAM-QFS environments.

To implement one or more shared drives, specify the shared keyword in the parameters file for each drive that is to be shared. The placement of the shared keyword is specific to each manufacturer's library, so see the vendor-specific sections for more information.