I second that emotion :-) SETROPTS SHAREDB(YES) or some such incantation... RACF could go into 'read only' mode if it finds things amiss.
Scott Rohling On Tue, Jan 18, 2011 at 4:12 PM, Alan Altmark <alan_altm...@us.ibm.com>wrote: > On Tuesday, 01/18/2011 at 04:51 EST, Scott Rohling > <scott.rohl...@gmail.com> wrote: > > The DASD is defined as shared - but if you're really sharing this RACF > database > > - the 200 and 300 minidisks need to be fullpack minidisks. Cylinder 0 > to END. > > (DEVNO disks are recommended) > > > > I'm not saying this is the cause of the problem you are seeing .. but > > RESERVE/RELEASE protection of the database between your z/VM systems > isn't > > happening the way you have it defined - and I thought I should point > that out. > > Some day I'd like to see the sysprog's *intent* expressed in SETROPTS and > for RACF to ask CP whether or not the proper sacrifices have been made on > behalf of the volumes containing the databases. > > Alan Altmark > > z/VM and Linux on System z Consultant > IBM System Lab Services and Training > ibm.com/systems/services/labservices > office: 607.429.3323 > alan_altm...@us.ibm.com > IBM Endicott >
