HP Archive Backup System for OpenVMS Guide to Operations

Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X
B.2 SLS/MDMS V2.x to ABS/MDMS V4.x Migration
It is also equally valid to name the drive after the OpenVMS device name as long as it is unique
within the domain. Specify nodes for drives using the NODES or GROUPS attributes. You must
specify all nodes or groups that have direct access to the drive.
Note
Do not specify a node or group name in the drive name or the OpenVMS device name.
Consider two drives named “$1$MUA500”, one on cluster “BOSTON” and the other on cluster
“HUSTON”, and you want to use a single MDMS domain. You can set up the drives as follows:
$ MDMS CREATE DRIVE BOS_MUA500/DEVICE=$1$MUA500/GROUP=BOSTON
$ MDMS CREATE DRIVE HUS_MUA500/DEVICE=$1$MUA500/GROUP=HUSTON
B.2.3.6
Jukeboxes
The new ACCESS attribute can limit use of the drive to be either local or remote access. Local
access is defined as access by any of the nodes in the NODES attribute or any of the nodes
defined in the group object (in the GROUP attributes). Remote access is defined as access from
any other node. By default, both local and remote accesses are allowed.
With MDMS V3, drives can be defined as being jukebox controlled, stacker controlled or standalone.
• Jukebox Controlled: A drive is jukebox controlled when it resides in a jukebox, and you
want random-access loads/unloads of any volume in the jukebox. Define a jukebox name,
control mechanism (MRD or DCSC), and drive number for a MRD jukebox. The drive
number is the number MRD uses to refer to the drive and starts from zero.
• Stacker Controlled: A drive can be defined as a stacker when it resides in a jukebox and you
want sequential loading of volumes, or if the drive supports a stacker loading system. In
such cases, do not define a jukebox name but set the “STACKER” attribute.
• Stand-alone: If the drive is stand-alone (loadable only by an operator), do not define a jukebox
and also clear the “STACKER” attribute.
Set the “AUTOMATIC_REPLY” attribute if you want Opcom requests on the drive to be completed
without operator intervention. It enables a polling scheme that automatically cancels the
request when the requested condition is satisfied.
In MDMS V2, jukeboxes were differentiated as libraries, loaders and ACS devices, each with
their own commands and functions. With MDMS V3, all automatic loading devices are grouped
under the jukebox object.
Jukeboxes can be controlled by one of the following two subsystems. They can also have unique
names comprising a maximum of 31 characters:
• MRD used for most of the SCSI jukeboxes including some StorageTek silos
• DCSC used for most of the existing and older StorageTek silos
The new “ACCESS” attribute can limit use of the jukebox to be either local or remote access.
Local access is defined as access by any of the nodes in the “NODES” attribute or any of the
nodes defined in the group object (in the GROUP attributes). Remote access is access from any
other node. By default, both local and remote accesses are allowed.
For MRD jukeboxes, the robot name is the name of the device that MRD accesses for jukebox
control. It is equivalent to the device name that is listed first in the old TAPE_JUKEBOXES definition
in the TAPESTART.COM (but without the node name). As with drives, nodes for the
jukebox must be specified using the “NODES” or the “GROUPS” attributes.
B–12 Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X