Martha,

Could MDCACHE be getting in the way?

When I share minidisks between z/VM systems in different LPARS  or on 
different CECs, I run an EXEC to ensure that the following commands are 
entered before to access the disk updated on the "other" system, from the 
system where it had not been updated:

 'PIPE CP DETACH' vdev' 
 'CP LINK' owner vdev vdev 'RR' 
 'CP SET MDCACHE FLUSH' vdev 
 'ACCESS' vdev fmode

Update those as required, test, rinse, lather, repeat, and let us know if 
that takes care of it.

Mike Walter
Aon Corporation
The opinions expressed herein are mine alone, not my employer's. 





"Martha McConaghy" <[email protected]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
01/17/2011 11:16 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
CMS disk weirdness between processors






I'm in the process of migrating our production LPARs from a z9 to a z10 
and
I've found a bit of weirdness.  Since the z10 has been around awhile, I
assume this isn't anything new, but I wonder why it is happening.

I've found that a CMS minidisk that is created while on the z9, is 
readable
by a VM system on the z10.  However, if (from the z10) a fle is modified,
that file is no longer readable by the CMS system on the z9.
I get a DMSXIN104S error
code 3 when trying to read the file.  Moreover, if (from the z9), I try to
write a new file to the disk, I get a different error, and CMS crashes.
(All of these z/VM systems are the same by the way, z/VM 5.4.0 RSU 1001.)

I've always been able to share disks between systems on different 
processors
before, so I wonder what is different now?  I've got a z990 that I still
have to maintain and this is going to make life more difficult.

Martha






The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 

Reply via email to