Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Two questions about MIDAW

35 views
Skip to first unread message

R.S.

unread,
Feb 1, 2008, 9:17:12 AM2/1/08
to
The following scenario: z9, z/OS 1.7 with up-to-date service. FICON
connections.

1. What steps should be done to enable MIDAW on non-IBM storage?
The box is EMC DMX3 with proper microcode level. AFAIK MIDAW support has
to be enabled by EMC CE.
I wonder about activities on host side.


2. z9, z/OS 1.7 (with service), Shark ESS 800 with Microcode 2.4.4.112.

D IOS,MIDAW
IOS097I 10.41.07 MIDAW FACILITY 542
MIDAW FACILITY IS ENABLED

MVS command:
D M=DEV(8D10)
…
SCP TOKEN NED = 002105.000.IBM.75.0000000xxxxx.0D00
SCP DEVICE NED = 002105.000.IBM.75.0000000xxxxx.0D10
PAV BASE AND ALIASES 4
FUNCTIONS ENABLED = MIDAW

shows that MIDAV is enabled

But another Command show that is still *unavailable*:

DS,QD,8D10,RDC
UNIT VOLSER SCUTYPE DEVTYPE CYL SSID SCU-SERIAL DEV-SERIAL EF-CHK
8D10 ZXXXXX 2105800 2105000 3339 8D00 0175-XXXXX 0175-XXXXX **OK**
READ DEVICE CHARACTERISTIC
2105E833900A5E80 BFF720240D0B000F E000E5A205940222 1309067400000000
0000000000000000 24241B02DFEE0001 0677080F007F4800 0035000000000000

X'80' means (in ...A5E80) means that MIDAW is disabled.
Q2: Is the microcode level correct for MIDAW?
Q3: If yes, what should be done to enable this function?


Regards
--
Radoslaw Skorupka
Lodz, Poland


--
BRE Bank SA
ul. Senatorska 18
00-950 Warszawa
www.brebank.pl

Sąd Rejonowy dla m. st. Warszawy
XII Wydział Gospodarczy Krajowego Rejestru Sądowego,
nr rejestru przedsiębiorców KRS 0000025237
NIP: 526-021-50-88
Według stanu na dzień 01.01.2007 r. kapitał zakładowy BRE Banku SA (w całości opłacony) wynosi 118.064.140 zł. W związku z realizacją warunkowego podwyższenia kapitału zakładowego, na podstawie uchwał XVI WZ z dnia 21.05.2003 r., kapitał zakładowy BRE Banku SA może ulec podwyższeniu do kwoty 118.760.528 zł. Akcje w podwyższonym kapitale zakładowym będą w całości opłacone.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Wayne Driscoll

unread,
Feb 1, 2008, 9:35:07 AM2/1/08
to
Radoslaw,
I'm not an EMC CE, but since it appears that the DS,QD,xxxx,RDC appears to be asking the device what it supports, this is the indicator that MIDAW is disabled on the hardware side, so you probably need to contact your EMC support folks.

Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my own.

Chris Burgess

unread,
Feb 1, 2008, 9:36:57 AM2/1/08
to
Songs you know by heart.


Thanks,
Chris Burgess
EMC²
where information lives

Phone: 1-800-445-2588 x42149
1-508-249-2149
Pager: 1-877-443-8447
Fax: 1-508-544-2076
Email: burgess_c...@emc.com

Dean Montevago

unread,
Feb 1, 2008, 9:39:43 AM2/1/08
to
I thought if the box had FICON and the system was IPL'd with the default MIDAW=YES then it would take affect immediately. We had to upgrade the microcode on our EMC box to support MIDAW, even though we're ESCON and will be IPL'ng MIDAW=NO. No one ever mentioned anything about a CE being involved ?

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@BAMA.UA.EDU] On Behalf Of Wayne Driscoll
Sent: Friday, February 01, 2008 9:34 AM
To: IBM-...@BAMA.UA.EDU
Subject: Re: Two questions about MIDAW

Radoslaw,
I'm not an EMC CE, but since it appears that the DS,QD,xxxx,RDC appears to be asking the device what it supports, this is the indicator that MIDAW is disabled on the hardware side, so you probably need to contact your EMC support folks.

Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my own.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@BAMA.UA.EDU] On Behalf Of R.S.
Sent: Friday, February 01, 2008 8:17 AM
To: IBM-...@BAMA.UA.EDU
Subject: Two questions about MIDAW

The following scenario: z9, z/OS 1.7 with up-to-date service. FICON
connections.

1. What steps should be done to enable MIDAW on non-IBM storage? The box is EMC DMX3 with proper microcode level. AFAIK MIDAW support has
to be enabled by EMC CE.
I wonder about activities on host side.


2. z9, z/OS 1.7 (with service), Shark ESS 800 with Microcode 2.4.4.112.

D IOS,MIDAW
IOS097I 10.41.07 MIDAW FACILITY 542
MIDAW FACILITY IS ENABLED

MVS command:
D M=DEV(8D10)
...

shai hess

unread,
Feb 1, 2008, 9:44:32 AM2/1/08
to
HI,

Where can I find the description of the RDC which set the PAV and MIDAW?

Thanks,
Shai

R.S.

unread,
Feb 1, 2008, 9:53:10 AM2/1/08
to
Wayne Driscoll wrote:
> Radoslaw,
> I'm not an EMC CE, but since it appears that the DS,QD,xxxx,RDC appears to be asking the device what it supports, this is the indicator that MIDAW is disabled on the hardware side, so you probably need to contact your EMC support folks.

Wayne,
The second issue is related to ESS Shark.

However the difference for EMC is the command D M=DEV(EMC_device) does
not mention MIDAW status at all.

Mark Zelden

unread,
Feb 1, 2008, 10:05:14 AM2/1/08
to
On Fri, 1 Feb 2008 09:33:48 -0500, Wayne Driscoll
<wdri...@JMESOFTWARE.COM> wrote:

>Radoslaw,
>I'm not an EMC CE, but since it appears that the DS,QD,xxxx,RDC appears to
be asking the device what it supports, this is the indicator that MIDAW is
disabled on the hardware side, so you probably need to contact your EMC
support folks.
>

Agree. Initially there was EMC MCL that disabled it from the HW side regardless
of the setting in z/OS.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark....@zurichna.com
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

Jim Mulder

unread,
Feb 1, 2008, 1:32:13 PM2/1/08
to
IBM Mainframe Discussion List <IBM-...@BAMA.UA.EDU> wrote on 02/01/2008
09:16:32 AM:

> 2. z9, z/OS 1.7 (with service), Shark ESS 800 with Microcode 2.4.4.112.
>
> D IOS,MIDAW
> IOS097I 10.41.07 MIDAW FACILITY 542
> MIDAW FACILITY IS ENABLED
>
> MVS command:
> D M=DEV(8D10)

> ? ?


> SCP TOKEN NED = 002105.000.IBM.75.0000000xxxxx.0D00
> SCP DEVICE NED = 002105.000.IBM.75.0000000xxxxx.0D10
> PAV BASE AND ALIASES 4
> FUNCTIONS ENABLED = MIDAW
>
> shows that MIDAV is enabled
>
> But another Command show that is still *unavailable*:
>
> DS,QD,8D10,RDC
> UNIT VOLSER SCUTYPE DEVTYPE CYL SSID SCU-SERIAL DEV-SERIAL EF-CHK
> 8D10 ZXXXXX 2105800 2105000 3339 8D00 0175-XXXXX 0175-XXXXX **OK**
> READ DEVICE CHARACTERISTIC
> 2105E833900A5E80 BFF720240D0B000F E000E5A205940222 1309067400000000
> 0000000000000000 24241B02DFEE0001 0677080F007F4800 0035000000000000
>
> X'80' means (in ...A5E80) means that MIDAW is disabled.
> Q2: Is the microcode level correct for MIDAW?
> Q3: If yes, what should be done to enable this function?

When MIDAW was being designed, it was thought that it would
work with all DASD controllers with no changes required to
the DASD. When it was subsequently discovered that MIDAW did
not work correctly with some non-IBM DASD, the solution was to
define the bit in Read Device Characteristics so that the DASD
controller could indicate if it supported MIDAW. But since all
IBM DASD already did work with MIDAW, the MVS code first checks to
see if the manufacturer field in the NED is 'IBM', and if so,
MVS assumes that the device supports MIDAW. This avoided the need
to update IBM DASD simply to turn on the Read Device Characteristics
bit. If the manufacturer is not 'IBM', then the Read Device
Characteristics bit is used to determine if the device supports MIDAW.

Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY

0 new messages