, as the Reserve(s) would not have been converted - GRS caused
the problem.
Ron
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ted MacNEIL
Sent: Monday, 27 February 2006 8:00 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Share DASD and CA-MII
We
We have shared dasd between our Prod Test Lpars ever since we had Lpars
over 10 years ago. I have never seen a problem.
We have had our share of problems.
-
-teD
I’m an enthusiastic proselytiser of the universal panacea I believe in!
On Sun, 26 Feb 2006 21:09:15 -0600, Ed Gould [EMAIL PROTECTED] wrote:
On Feb 26, 2006, at 8:21 PM, Eric N. Bielefeld wrote:
We have shared dasd between our Prod Test Lpars ever since we had
Lpars over 10 years ago. I have never seen a problem. Now, most
of the stuff that is shared is load
You can always READ without any risk of corrupting data, so if you know that
data is being update only from say ONLY one sysplex, the risk of corruption
should be minimal. Just time when you read the data to ensure you get the
'latest' version.
There is an exposure even if you only do updates
In the VTOC, a DSCB may be rewritten to update the last reference date
even for a dataset opened only for INPUT.
I have firmly believed, for over 15 years, if you are sharing DASD you need GRS.
If you are sharing across PLEX's, you need MIM (not MII anymore).
Period. End of statement.
Many
on the
Prod lpar.
Eric Bielefeld
PH Mining Equipment (for a little while)
- Original Message -
From: Ted MacNEIL [EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Saturday, February 25, 2006 6:00 PM
Subject: Re: Share DASD and CA-MII
I have firmly believed
.
Ed
Eric Bielefeld
PH Mining Equipment (for a little while)
- Original Message - From: Ted MacNEIL
[EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Saturday, February 25, 2006 6:00 PM
Subject: Re: Share DASD and CA-MII
I have firmly believed, for over
Thanks all, conclusions:
To transfer file from one SYSPLEX to another SYSPLEX, we can use Flashcopy
or Shadowimage, so different SYSPLEX read/update different volumes. Yes,
it is safe, but we have to change our TWS application procedures to do
Flashcopy.
We must buy CA-MIM, or use GRS to
Hi Yadong,
Actually GRS can also be made to handle cross-sysplex DASD sharing, but
requires an installation exit ISGNQXIT, to ensure a HW Reserve is used for
the cross-sysplex shared volume.(price = performance for integerity)
You can always READ without any risk of corrupting data, so if you
Hi, all,
We have 2 questions:
1. Is there any other software besides CA-MII to manage data integrity
on share dasd between different SYSPLEX?
2. If we just use share DASD to do file transfer from one SYSPLEX to
another SYSPLEX, do we still need a software like CA-MII?
Any
-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Yadong Wu
Sent: Tuesday, 14 February 2006 8:49 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Share DASD and CA-MII
Hi, all,
We have 2 questions:
1. Is there any other software besides CA-MII to manage data
11 matches
Mail list logo
