> Support to share IBM tape drives (that is Ficon/Escon attached) as a > native device. These drives will be shared with the 390 side.
That's one to address to IBM, not Novell. > We need to > know when we hit EOV for multivolume tapes and have a method of unloading > and calling for the next mount. Ditto. Although the CMS-based tape daemon Adam wrote a while back provides a reasonable alternative for now. > Support to share the IBM VTS (Virtual Tape System), which is a tape based > virtual system. See above. > Support to run the IBM 3494 robotic system. REALLY see above. > How about a device driver, that makes the FICON/Escon attached tape drive, > look, and addressed like a SCSI attached drive? Keep in mind that if you can get a FCP port, a FCP to SCSI converter and SCSI-based tape drives are acceptably cheap substitutes, but it's still annoying as hell though that I can't use the equipment I already paid for, and that VM can share just fine. A useful compromise would be a Linux device driver that spoke to the VSE shared tape server routines already in DFSMS/VM, or better yet, an iSCSI server for VM, VSE and z/OS that understood how to map channel-attached tape devices to iSCSI LUNs. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
