Rich,

With respect to the code levels you are at on the DMX's:
Both the DMX2 at 5671.60.xx and DMX3 5771.94.xx are at levels that incorporate MIDAW minimum uCode levels. With that said, you may want to review the release notes for 5671.65.69, 5771.94.103 and 5771.99.108 with respect to your environment for any applicable fixes.
These are accessible via Powerlink - 'Products' > 'Hardware/Platforms' > 'Symmetrix' > 'release notes' under each Symmetrix category.

Other reading on the subject in the Knowledge Base is Article 'emc139565'.

Best regards,

Michael

Michael,

I'll check out the release notes, we have already reviewed the Knowledge Base article.

Thank you.

Rich

Rich,

Thanks for the information. Good to hear it¿s working well for you. We¿re still talking about turning MIDAW on. One more question if I may. When you activated MIDAW, how did you go about it? EMC is recommending we activate it on all the DMX¿s with the bin file change, then, we¿re ready, turn it on to the various LPAR¿s, through z/OS. We have three plexes, a system programmer (sandbox) plex, a development plex, then a production plex. I was planning on starting with the sandbox, then moving up to development, then production.

Thanks again,

Rich

Rich,

You are correct.
EMC enables it (MIDAW handling and flow) in the DMX and in turn, you have control at the LPAR via z/OS.

Michael

Thanks Michael,

Regards,

Rich

Hi,
As I understood, by default MIDAW is off on DMX-3 ?
To turn on I need to ask EMC support. Is it true? Is it dynamic process? Have you any suggestion about settings in z/OS environment when EMC turn MIDAW on ?
Should I SETIOS MIDAW=NO before changing on EMC boxes or it doesn¿t matter.

Thanks for any comments and suggestions

Hi,

We did this a couple months ago. Environment is DMX2's and a DMX3, z/OS 1.8. The steps were 1) MIDAW was set off in parmlib, 2) EMC Customer Engineer activated MIDAW to the DMX2's and 3 via a bin file change. Once the bin file change was made, we used the SETIOS command to activate MIDAW under z/OS and updated parmlib.

It was a dynamic change for us. We have z9's and a z890, the z890 does not support MIDAW.

Also our system programmers checked for any PTF's for z/OS before MIDAW was activated.

It was uneventful and painless.

Hope this helps.

Regards,

Rich

Hi Guys,

Thanks Rich!!

Just to clarify. The MIDAW flag in the bin file is safe to enable ONLINE at any time. Once it is enabled it just means we are "MIDAW capable" when the host decides to utilize the feature. So obviously best not to enable the feature on the host before the bin flags are set but there are no harm in enabling the bin flags say at installation time (just in case MIDAW is needed later).

Regards,
Michael.

Hi,

Your welcome Michael. One more item to add.

You can check if the hardware is enabled for MIDAW by using the command below (z/OS). Might be a faster way to check, then asking your CE to check for you.

DS QD,6500,RDC
IEE459I 08.34.07 DEVSERV QDASD 388,
UNIT VOLSER SCUTYPE DEVTYPE CYL SSID SCU-SERIAL DEV-SERIAL EF-CHK,
6500 PIM800 2105F20 2105 10017 6005 XX07-02479 XX07-02479 **OK**,
READ DEVICE CHARACTERISTIC,
2105E833900C5EA0 BF9720322721000F E000E5A205940222 130906742721002D,
2727000F274B002D 32321B02DFEE0001 0677080F007F4800 0035000000000000,
**** 1 DEVICE(S) MET THE SELECTION CRITERIA,
**** 0 DEVICE(S) FAILED EXTENDED FUNCTION CHECKING,

The A0 bolded in the sense information indicates MIDAW is enabled to the hardware. I believe it's a 80 if MIDAW is not enabled, however, I can't check this, since all our SYMM's are now enabled to MIDAW.

Regards,

Rich