Is that really true? When checking just now I found that the 'Planning
and Administration' manual also says so, but I'm 99% sure (allowing
1% for memory deterioration) that I shared a 20 cyl. RACF database
between two separate VM XA systems and it worked perfectly well.
While the rest of the
Subject:Re: Installing RACFVM - Questions
Yes, this is true. RACF manages the updates to the shared database
using the reserve/release functions of the DASD control unit. So, a
reserve issued by RACF must flow to the real control unit, so that any
reserve issued by another system would be rejected until a release is
done. And, CP only
Yes, I knew about the basic operation, I just don't see why the logic
should be restricted to full pack minidisks (except maybe to prevent
potential problems when somebody defines multiple MWV minidisks
on the same pack ..).
But thanks for confirming the documented operation!
Eginhard Jaeger
On
On Wednesday, 07/28/2010 at 10:03 EDT, Eginhard Jaeger
e.jae...@ch.inter.net wrote:
Is that really true? When checking just now I found that the 'Planning
and Administration' manual also says so, but I'm 99% sure (allowing
1% for memory deterioration) that I shared a 20 cyl. RACF database
I dare to disagree a bit:
- MWV is required to get Virtual Reserve/Release, that is sharing inside
z/VM.
- SET SHARED ON and FULLPACK Mdisk is for Real Reserve/Release
They are different beasts:
The Real R/R is a function of the dasd controller: when one system sends a
Reserve, it halts the IOs
On Wednesday, 07/28/2010 at 02:38 EDT, Kris Buelens
kris.buel...@gmail.com wrote:
I dare to disagree a bit:
- MWV is required to get Virtual Reserve/Release, that is sharing inside
z/VM.
- SET SHARED ON and FULLPACK Mdisk is for Real Reserve/Release
They are different beasts:
The Real R/R
: Wednesday, July 28, 2010 2:39 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] Installing RACFVM - Questions
On Wednesday, 07/28/2010 at 02:38 EDT, Kris Buelens
kris.buel...@gmail.com wrote:
I dare to disagree a bit:
- MWV is required to get Virtual Reserve/Release, that is sharing inside
z/VM
That will not work. The database must be on full pack minidisks,
which means the minidisk must start at cylinder 0 and go to the end of
the volume. (DEVNO minidisks can also be used.) So, your directory
entries must be:
MDISK 200 3390 0 END VMRACP MWV READ WRITE MULT
MDISK 300 3390 0 END
