Hello Carlos Bodra,
I would have to agree with Billy. z/VM 4.4.0 with the correct
PTF's will see the DS6800.
While I am not sure that VSE/ESA 2.3.1 will handle the DS6800
properly,
I would suspect that VSE/ESA will handle it well if you MDISK
everything.
We are on z/VM 5.3 and z/VSE 4.1.2, both show the 1750 device
type but the
QUERY DASD DETAILS 904 shows the DEVTYPE = 3390-0A.
>From our z/VM 5.3
CMS
q dasd details 904
0904 CUTYPE = 1750-E8, DEVTYPE = 3390-0A, VOLSER = DS6904, CYLS = 3339
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 04, DDC = --
DUPLEX DETAILS: --
CU DETAILS: SSID = 0002, CUNUM = 0230
Ready; T=0.01/0.01 14:28:06
And from z/VSE 4.1.2
VOLUME 904 XCM EDMA
14:28:41
AR 0015 CUU CODE DEV.-TYP VOLID USAGE SHARED STATUS CAPACITY
AR 0015 904 6E 1750-500 DS6904 USED SHARED
3339 CYL
AR 0015 1I40I READY
14:28:41
Ed Martin
Aultman Health Foundation
330-363-5050
ext 35050
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Carlos Bodra
Sent: Tuesday, May 18, 2010 1:29 PM
To: VSE Discussion List
Subject: Saga continues..
Hi...
After got fix from Ingolf Salm for VSE/ESA runs under z10 BC, saga
continues.
Customer has MP3000 7060-H50 with internal disks. They are formated as
3390-3 only.
Since DS6000 Interoperability matrix show that z/VM 4.4.0 is supported,
no problem
on zVM side.
My question now is:
Will VSE/ESA 2.3.1 support volumes defined on DS6800 (all 3390-3 - no
large volumes).
Any hint about?
Thanks in advance for comments.
Carlos Bodra
