Chapter 6 HPSS Configuration388 September 2002 HPSS Installation GuideRelease 4.5, Revision 26.8.13.2.4 Vendor Information1. 3584 UltraScalable Tape Library Planning and Operator Guide GA32-0408-012. IBM Ultrium Device Drivers Installation and User's Guide GA32-0430-00.13. IBM Ultrium Device Drivers Programming Reference WB1304-014. 3580 Ultrium Tape Drive Setup, Operator and Service Guide GA32-0415-005. 3584 UltraScalable Tape Library SCSI Reference WB1108-006.8.13.3 IBM 3494/3495 PVR Information6.8.13.3.1 Vendor Software RequirementsHPSS is designed to work with IBM 3494/3495 robots attached to an HPSS server with either RS-232, Ethernet, or Block Multiplexer (BMUX) control connections. Data paths to the drives will beSCSI-2 with RS-232 and Ethernet control paths, or BMUX if BMUX control paths are used. TheHPSS PVR must run on a machine with the appropriate version of Library Manager Control Point(LMCP) device drivers installed.6.8.13.3.2 Configuration RequirementsWhen configuring an HPSS PVR to manage an IBM robot, the Drive Address configuration entriescorrespond to the device number of the drive. Determine the device number by running the HPSStool GetESANumbers for each tape drive in the robot.The HPSS PVR requires one or two LMCP device special files to access the robot. For AIX systems,these files are usually named /dev/lmcpX and can be created using the System ManagementInterface Tool (SMIT). For a BMUX connected robot, the files can be defined to be a Command Portor an Asynchronous (Async) Port. The HPSS PVR requires both. By default, the PVR will expect theCommand and Async ports to be named /dev/lmcp0 and /dev/lmcp1 respectively. Controlconnections must be made prior to configuration of the /dev/lmcpx devices or undefined errorsmay result. For Solaris systems, the symbolic library name defined in /etc/ibmatl.conf (e.g., 3494a)should be used.For RS-232 and Ethernet connected robots, the device special files support both command andasync capabilities. If only one device special file is created, the environment variables orconfiguration should be set so that both the command and async ports point to that one special file.It is also possible to create two device special files and arbitrarily select one to be the command portand the other to be the async port. The PVR can then be configured to recognize the ports asdescribed above in the BMUX case.HPSS can share an IBM robot with other tape management systems. If a robot is shared, care mustbe taken to make sure that a drive is not used by any other tape management system while thatdrive is configured as unlocked in the HPSS PVL. This is important because HPSS periodically pollsall of its unlocked drives even if they are not currently mounted. The two LMCP device special files(or possibly one file in the case of an RS-232 or Ethernet controlled robot) are not available to othertape management programs. Additional device special files may be created for other programs.
