Browse Prior Art Database

Dynamic Device Configuration

IP.com Disclosure Number: IPCOM000113786D
Original Publication Date: 1994-Oct-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 4 page(s) / 101K

Publishing Venue

IBM

Related People

Carlson, KK: AUTHOR [+2]

Abstract

Disclosed is a process for a server or an application running on a host, such as the AS/400* or ES/9000*, to communicate to a device through a library control path and to the same device on a 370/390 channel, for the purpose of controlling the library. The configuration is dynamically determined by the application, which in the first implementation is the Media Library Device Driver on the AS/400.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Dynamic Device Configuration

      Disclosed is a process for a server or an application running
on a host, such as the AS/400* or ES/9000*, to communicate to a
device through a library control path and to the same device on a
370/390 channel, for the purpose of controlling the library.  The
configuration is dynamically determined by the application, which in
the first implementation is the Media Library Device Driver on the
AS/400.

      The application (Media Library Device Driver) must know the
configuration of the Media Library Device in order to properly drive
each Media Library Device.  A mapping must be made between the naming
conventions from the host on the channel interface, the naming
convention used by the user in host application commands, and the
addressing/naming conventions used in the library control path
connection to the Library manager in the Media Library Device.

      For example, a host, such as the AS/400, could have 6 tape
devices.  TAP01 and TAP03 are in MLD01.  TAP02, TAP04 and TAP06 are
in MLD02.  TAP05 is not in a Media Library Device.  The application
would need to determine this configuration in order to determine
which Media Library Device to send library control commands to, and
what to call the device, so that it will be recognized by the Library
Manager.  Refer to Figs. 1 and 2.  Fig. 1 enables the user to type
MNTMEDMLD VOL(VOL001) DEV(TAP13) to cause volume VOL001 to be mounted
on drive 0 on control unit 0 in Library LMI.  Fig. 2 enables the user
to type MNTMEDMLD VOL(VOL001) DEV(TAP13) to cause volume VOL001 to be
mounted on drive 4 on control unit in Library LM2.

      The configuration is established by the Media Library Device
Driver via the following procedure:
  1.  Ask each device on the channel path (via Read Configuration
      Data on 3490) to uniquely identify itself.  (This is done
      by Issuing Display Hardware Resources (DSPHDWRSC) to the
     ...