Using ESCON attached 3590 for TSM 5.5 / Linux
One of our customers who does not follow this list asked me to post a question here. They are running SLES 10 SP1 in an instance on a FLEX-ES system. (Think of this as running in an LPAR on a normal system. That is, no zVM.) They have an ESCON connected 3590 that they can use from the Linux system with no problem, but apparently there is a 'special' device driver supplied for TSM 5.5 and when they install it, the driver apparently does not 'see' the tape device. They found a statement that TSM only supports Fiber attached tape devices, but we're not sure if Fiber in this context includes ESCON or not and I can't see why TSM should care as long as Linux is happy with the device. Does anyone else have any experience with this combination (TSM 5.5 on SLES 10 with ESCON 3590) or possibly have any suggestions?? Thanks Mike C. M. (Mike) Hammock Sr. Technical Support zFrame IBM zSeries Solutions (404) 643-3258 [EMAIL PROTECTED] __ This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. To reply to our email administrator directly, send an email to [EMAIL PROTECTED] -- 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
Re: Using ESCON attached 3590 for TSM 5.5 / Linux
Am Mittwoch, 16. Juli 2008 schrieb Mike Hammock: They are running SLES 10 SP1 in an instance on a FLEX-ES system. (Think of this as running in an LPAR on a normal system. That is, no zVM.) They have an ESCON connected 3590 that they can use from the Linux system with no problem, but apparently there is a 'special' device driver supplied for TSM 5.5 and when they install it, the driver apparently does not 'see' the tape device. They found a statement that TSM only supports Fiber attached tape devices, but we're not sure if Fiber in this context includes ESCON or not and I can't see why TSM should care as long as Linux is happy with the device. Does anyone else have any experience with this combination (TSM 5.5 on SLES 10 with ESCON 3590) or possibly have any suggestions?? As far as I know, TSM for Linux only supports FCP-attached (scsi) tapes. Channel attachement like FICON or ESCON are not supported. Christian -- 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
Re: Using ESCON attached 3590 for TSM 5.5 / Linux
Thanks Christian... That's what we were afraid of, but were not sure... They are trying to do a proof of concept with their existing equipment (ESCON 3590) and I don't believe there is any way to connect a true FCP or SCSI tape device to the Linux system on a FLEX-ES system, so I suspect they are out of luck for now... I assume that running zVM in the instance/LPAR and attaching the tape device to a Linux guest would not make any difference, correct? If anyone else has any ideas or suggestions, we'd be glad to listen.. Thanks C. M. (Mike) Hammock Sr. Technical Support zFrame IBM zSeries Solutions (404) 643-3258 [EMAIL PROTECTED] Christian Borntraeger [EMAIL PROTECTED] To bm.com LINUX-390@VM.MARIST.EDU Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: [LINUX-390] Using ESCON attached 3590 for TSM 5.5 / Linux 07/16/2008 07:54 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Am Mittwoch, 16. Juli 2008 schrieb Mike Hammock: They are running SLES 10 SP1 in an instance on a FLEX-ES system. (Think of this as running in an LPAR on a normal system. That is, no zVM.) They have an ESCON connected 3590 that they can use from the Linux system with no problem, but apparently there is a 'special' device driver supplied for TSM 5.5 and when they install it, the driver apparently does not 'see' the tape device. They found a statement that TSM only supports Fiber attached tape devices, but we're not sure if Fiber in this context includes ESCON or not and I can't see why TSM should care as long as Linux is happy with the device. Does anyone else have any experience with this combination (TSM 5.5 on SLES 10 with ESCON 3590) or possibly have any suggestions?? As far as I know, TSM for Linux only supports FCP-attached (scsi) tapes. Channel attachement like FICON or ESCON are not supported. Christian -- 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 __ This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. To reply to our email administrator directly, send an email to [EMAIL PROTECTED] -- 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
Re: Using ESCON attached 3590 for TSM 5.5 / Linux
the tape device. They found a statement that TSM only supports Fiber attached tape devices, but we're not sure if Fiber in this context includes ESCON or not It does not. TSM doesn't understand channel-attached tape on Linux at all. FCP-only. Your 3590 is useless for this purpose. Does anyone else have any experience with this combination (TSM 5.5 on SLES 10 with ESCON 3590) or possibly have any suggestions?? If you want a Linux-only solution, buy a FCP tape drive. Or install z/OS.e and use the z/OS TSM to drive your channel-attached tape. Those are the choices on offer from IBM. Since most people don't like those options much, you can also use the remote volume option of the VM TSM server to drive the actual tapes (since it DOES understand channel-attached tape), and configure the Linux TSM server to use the CMS server as the destination for the virtual volumes. Look at the docs for virtual volume support -- there are some limitations but you don't end up with an entire z/OS system just to do backups. -- 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
