                                Add Robot

This dialog is used to add a robot to the device configuration.
The dialog can be accessed through the "Add Robot..." button in the "Robots"
menu on the menu bar.

At the bottom of the dialog there are four buttons.  The OK button will add the
robot and dismiss the dialog.  The Apply button will add the robot and will not
dismiss the dialog.  The Cancel button will dismiss the dialog without 
performing any other action.  The Help button will display this message.

Robot Type

Use the option menu to choose the type of robot you wish to add.

Robot Number

The Robot Number is a logical identification of a robotic library and should be 
used when entering the robot's media into the volume configuration.  The default 
value is the first unused number.

Robotic Control on this host/Robotic Control Host

For some robots, the actual control path may be on another machine.  If this is
the case, set this toggle to No and enter the host name in the Robotic Control
Host field.

ACSLS Host (ONLY for ACS robots)

For ACS robots, the host name of the Automated Cartridge System Library Software
(ACSLS) server should be entered. Requests from ACS robotic control are sent to 
this host, from which the ACS robot is controlled.

DAS Server (ONLY for TLM robots)

For TLM robots, the Distributed AML Server (DAS) host name should be entered.
Requests from TLM robotic control are sent to this host, from which the TLM robot
is controlled.

Robotic Device File

The device file for the robotic library's control must be entered if the robot
is on this host. The path for this file is a SCSI or RS-232 connection.

 Note - for each platform, there is an appendix in the release notes 
        regarding path names for robot configuration.


 Example device files:

  SUN (SunOS 4.x) - /dev/ttya for RS-232
                  - /dev/sg/c0t6d0s0 for SCSI

        The SG driver is included for SCSI robotic control on SunOS 4.x
        platforms.  Refer to the SunOS appendix in the release notes
        for further information about the SG driver.

  HP9000-700 - /dev/ptr_rs232_a for RS-232
             - /dev/scsi/4 for SCSI

  HP9000-800 - /dev/tty0p1 for RS-232
             - /dev/rdrv1 for SCSI

  SGI - /dev/ttyf2 for RS-232
      - /dev/scsi/sc0d6l0 for SCSI

  SUN (Solaris 2.x) - /dev/term/a for RS-232
                    - /dev/sg/c0t5l0 for SCSI

        The SG driver is included for SCSI robotic control on Solaris 2.x
        platforms.  Refer to the Solaris appendix in the release notes
        for further information about the SG driver.

  RS6000 - /dev/tty0 for RS-232
         - /dev/ovpass0 for SCSI

        The ovpass driver is included for SCSI robotic control on RS6000
        platforms.  Refer to the RS6000 appendix in the release notes
        for further information about the ovpass driver.

LMCP Device File (ONLY for TLH robots on RS6000)

The Library Manager Control Point (LMCP) device file is used for communication
between the TLH robotic control and the IBM Automated Tape Library (ATL) via
the LMCP daemon on the RS6000 platform.  An example LMCP device file name is 
   RS6000 - /etc/lmcp0.

Library Name (ONLY for TLH robots on Solaris)

The Library Name is used for communication between the TLH robotic control 
and the IBM Automated Tape Library (ATL) via the LMCP daemon on the Solaris 
platform.  Library names are configured in the /etc/ibmatl.conf configuration
file.  See IBM documentation for more information.
