Subject: RE: IOCP Question for 3490E C22 drive
From: Mead, Jerry (JMead@kable.com)
Date: Thu Jun 26 2008 - 10:33:21 EDT
We have stk tape drives (3490e) where each one has it's own channel.
example
* --------------------------------------------------------------------
* VSE CHANNEL E DEFINITIONS
* E00-E0D 3490E STK TIMBERLINE TAPE DRIVES
* EACH UNIT HAS A UNIQUE ESCON CHANNEL (CHPID)
* SEE STORAGETEK TIMBERLINE CONFIGURATION AND
* ADDRESSING GUIDE FOR IBM IOCDS CONFIGURATION
* DIFFERENCES OR CALL STK.
* --------------------------------------------------------------------
* E00-E0D 3490E CONTROLLERS AND DRIVES
CNTLUNIT CUNUMBR=E00,PATH=(98),UNIT=3490,UNITADD=((00,01))
CNTLUNIT CUNUMBR=E01,PATH=(85),UNIT=3490,UNITADD=((00,01))
CNTLUNIT CUNUMBR=E02,PATH=(89),UNIT=3490,UNITADD=((00,01))
etc
________________________________
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Ray Waters
Sent: Tuesday, June 24, 2008 8:44 AM
To: VSE Discussion List
Subject: RE: IOCP Question for 3490E C22 drive
Here is our 3490E IOCP:
CNTLUNIT CUNUMBR=0610,PATH=(42,43,44,45,46,47,48,49),UNIT=3490, X
UNITADD=((00,16)),CUADD=0
IODEVICE ADDRESS=(0610,16),CUNUMBR=(0610),UNIT=3490, X
UNITADD=00
z/VM 520
Z9 BC machine
Ray Waters
________________________________
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Chip Bryant
Sent: Tuesday, June 24, 2008 8:31 AM
To: VSE Discussion List
Subject: IOCP Question for 3490E C22 drive
Hi,
I have an older mainframe (7060-H55), running an older version of Z/VM
(4.3) with several very old, unsupported VSE/ESA guest machines (2.3.1).
I have successfully implemented a Virtual Tape system thus eliminating
almost all the tape drives except for a few used for archive tape usage
and to generate off-site tapes. We would like to get rid of the
remaining old 3480 drives and replace it with a 3490E C22 rack mount
unit since it uses less space and can read the old 3480 cartridges. I
am planning on getting the channel attached unit (not the ESCON).
Several years ago, an IBM Level II Tech told me that VM does not really
care anything about what is specified in the IOCP for a device except
for the address. They told me that VM actually goes out and queries
each device and builds it's tables from that and not from what is in the
IOCP. Based on that information, can I leave my IOCP alone and use the
definition from the old 3480 drives since I want to use the same
addresses? here is what I have defined for the old 3480 tape drives in
the IOCP:
CNTLUNIT CUNUMBR=590,
PATH=E0,UNIT=3480,PROTOCL=S4,SHARED=N,UNITADD=((90,16))
IODEVICE CUNUMBER=590,ADDRESS=(590,16),UNIT=3480,STADET=N
What worries me is the UNITADD at 90. The IOCP manual says that for a
3490E that the UNITADD must be 00. However, it says that for ESCON but
makes no mention for a parallel channel hook up. If I have the 3490E
installed at address 590, will the above definition work OK? I know
there are only two addresses for the 3490E and the above states 16 but I
take it VM will ignore this when it queries the device? I don't really
want to have to gen a new IOCP as it is a big ordeal to shutdown
everything to load a new one. I would appreciate any input anyone has
on this so I know if I can leave everything alone or if I need to "bit
the bullet" and figure on generating a new IOCP. Thanks for your input,
Chip Bryant
This message and any files transmitted with it are the property of
Sigma-Aldrich Corporation, are confidential, and are intended solely for
the use of the person or entity to whom this e-mail is addressed. If you
are not one of the named recipient(s) or otherwise have reason to
believe that you have received this message in error, please contact the
sender and delete this message immediately from your computer. Any other
use, retention, dissemination, forwarding, printing, or copying of this
e-mail is strictly prohibited.
________________________________
NOTICE:
This e-mail is intended solely for the use of the individual to whom it
is addressed and may contain information that is privileged,
confidential or otherwise exempt from disclosure. If the reader of this
e-mail is not the intended recipient or the employee or agent
responsible for delivering the message to the intended recipient, you
are hereby notified that any dissemination, distribution, or copying of
this communication is strictly prohibited. If you have received this
communication in error, please immediately notify us by replying to the
original message at the listed email address. Thank You.
This archive was generated by hypermail 2b25 : Mon Jun 30 2008 - 23:50:13 EDT