Martha,
Maybe minidisk cache is active on one of the systems.  Did you define the DASD 
as Shared?

                                                                                
                                           Dennis

18 Jan 1911, one hundred years ago today, Eugene Ely makes the first successful 
airplane landing on a warship, landing on the armored cruiser USS Pennsylvania 
in San Francisco Bay.



-----Original Message-----
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf 
Of Martha McConaghy
Sent: Monday, January 17, 2011 09:16
To: IBMVM@LISTSERV.UARK.EDU
Subject: [IBMVM] 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

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the 
intended recipient(s) and may contain information that is privileged, 
confidential or proprietary. If you are not an intended recipient, please 
notify the sender, and then please delete and destroy all copies and 
attachments, and be advised that any review or dissemination of, or the taking 
of any action in reliance on, the information contained in or attached to this 
message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a 
solicitation of any investment products or other financial product or service, 
an official confirmation of any transaction, or an official statement of 
Sender. Subject to applicable law, Sender may intercept, monitor, review and 
retain e-communications (EC) traveling through its networks/systems and may 
produce any such EC to regulators, law enforcement, in litigation and as 
required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, 
and EC may be archived, supervised and produced in countries other than the 
country in which you are located. This message cannot be guaranteed to be 
secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America 
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
Government Agency. Attachments that are part of this EC may have additional 
important disclosures and disclaimers, which you should read. This message is 
subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you 
consent to the foregoing.

Reply via email to