
 Robot Configuration

 This menu allows robotic libraries to be configured, deleted or
 updated.

 When adding a robot, the type of robot must be entered first.  A
 prompt for the robot number will then be displayed.  The robot
 number must be unique in the volume configuration.  You may use the
 default value (which is only guaranteed to be unique for this host)
 or select any number not already in use.  This is a logical 
 identification of a robotic library and should be used when entering
 the robot's media into the volume configuration (see the vmadm/xvmadm 
 man page). 

 The path to the robotic library must be entered.  This path is either
 an RS-232 connection or a SCSI connection.

 Note - for each platform, detailed configuration information
        appears in the Media Manager Device Configuration Guide.

 Examples are:

  SUN (SunOS 4.x) - /dev/ttya for RS-232
                  - /dev/sg/c0t6d0s0 for SCSI attached to a Sun host.
                  - /dev/asc38 for SCSI attached to an Auspex Storage
                    Processor (SP).

        The SG driver is included for SCSI robotic control on SunOS 4.x
        platforms.  Refer to the SunOS chapter in the Media Manager
        Device Configuration Guide for further information about the 
        SG driver.

  HP9000-700 - /dev/ptr_rs232_a for RS-232
	     - /dev/scsi/c0t4l0 for SCSI (except for TS8 on HP-UX 9.x)

  HP9000-800 - /dev/tty0p1 for RS-232
             - /dev/rdrv1 for SCSI on HP-UX 9.x
             - /dev/spt/c1t3d0 for SCSI on HP-UX 10.x (spt driver)
             - /dev/spt/c1t3l0 for SCSI on HP-UX 10.x (sctl driver)

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

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

        The SG driver is included for SCSI robotic control on Solaris 2.x
        platforms.  Refer to the Solaris chapter in the Media Manager 
        Device Configuration Guide for further information about the 
        SG driver.

  RS6000 - /dev/tty0 for RS-232
         - /dev/ovpass0 for SCSI via ovpass (most robot types)
         - /dev/rmt4.1 for SCSI via Atape driver (eg. for IBM 3590 B11)

        The ovpass driver is included for SCSI robotic control on RS6000
        platforms.  Refer to the RS6000 chapter in the Media Manager Device
        Configuration Guide for further information about the ovpass driver.

	The Atape driver is supplied by IBM.

  DEC ALPHA - /dev/tty00 for RS-232
            - /dev/tldc0t4l0 for SCSI (with TLD robots)

 For some robots, the actual control path may be on another machine.  If
 this is the case, enter the host name of the machine instead of a path.
 NOTE - When entering a robot that is controlled by another machine, the
        logical robot number MUST be the same on both machines.

 Typically, robots are defined first and then the drives in the robot
 are added via the Drive Configuration menu.  However, it is possible
 to define the drives first, then define a robotic library, and finally,
 add the drives to the robot via the Drive Configuration update option.
