Thank you for clarifying your earlier post. My earlier point is that
zLinux/TSM can certainly share libraries with zOS, but as you correctly
point out, I would not suggest that Fibre or ESCON/FICON tape devices
can be shared with zOS.
However, its not well understood that libraries can indeed be shared
between zLinux and zOS. We already share zOS disk, so I think its worth
clarifying as you did that we do not share tape devices. (zLinux
minidisks exist on zOS hardware, not talking about datasharing.)
There are many Powerhorn libraries being shared by zOS and zVM that
currently have only ESCON and/FICON drives. As those libraries upgrade
their drives from 20GB drives to 200 GB drives or 500 GB drives, they
are dramatically freeing up library slot capacity. This capacity can be
backfilled by zLinuz/TSM FCP drives managed by zOS.
It means dedicated FCP drives for the TSM workload, but it means no new
libraries are required. New libraries do not have to be acquired to
support a zLinux/TSM when a zOS managed library exists. One additional
software piece called Lib Station needs to be added to interface to zOS
HSC. Otherwise, TSM in certified to talk to ACSLS library manager on
the non-zOS libraries.
Lee Reiersgord
Systems Engineer
Data Management Group
Sun Microsystems/STK
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
David Boyes
Sent: Saturday, January 07, 2006 5:47 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: z/Linux, TSM 5.3, and STK
> A zOS managed Powderhorn library may have Fibre drives along with
ESCON,
> FICON and SCSI.
True -- but a drive can be only one of the above at a time. A drive can
only support one type of attachment, and if it's FCP, it can't be
accessed by ESCON/FICON. If you don't install FCP devices, then the TSM
code can't use the drives in the Powderhorn. Doesn't matter a whit if
the guest can talk to the library manager, if it can't transfer data.
It's important to keep in mind that sharing devices between open systems
and mainframe systems is a relatively new thing, and the likelihood of
that configuration being in place is still quite low. That's changing,
but it's not very likely to be the case right now.
> The key is not to confuse control path with data path. Various
clients
> can talk to zOS via TCPIP while they talk to the drive via Fibre or
> SCSI.
Mounting tapes in drives that the OS can't access really doesn't help.
> Running zLinux on a zOS managed library is not a problem...
... if you have FCP drives installed in the library. If you don't, then
it *is* a problem.
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
