On Wed, 11 Sep 2013 19:08:19 +0000, Gibney, Dave <[email protected]> wrote:
>>
>> Neither. zFS can safely be shared R/O outside sysplex / GRS
>> boundaries. BTW, with PDSESHARING(NORMAL), PDSE can
>> be shared R/W outside the sysplex, but the boundaries must still
>> be within the GRSplex. However, they can't be shared R/W between
>> systems managed by MII (MIM) because the ENQs issued for
>> SYSZIGW0 and SYSZIGW1 are issued with RNL=NO. IIRC, this
>> wasn't always the case and IBM "broke this" for CA MIM
>> customers around DFSMS/MVS 1.5. Thank you IBM.
>>
>> Regards,
>I usually don't disagree with Mark, but my experience is that without the XCF
>communication Barbara mentioned (i.e. inside a sysplex), updating a PDS/E
>from one LPAR can cause abends of address spaces in another LPAR that are
>actively using the PDS/E.
>Specifically, when VPS from LRS shipped with all PDS/E including the CNTL
>libraries, I abended my production VPS by modifying shared printer
>definitions from the development LPAR.
XCF is not involved when PDSE is using PDSESHARING(NORMAL). Were
you using PDSESHARING(EXTENDED)? WAS PDSESHARING(NORMAL)
in effect on BOTH systems involved? Were your 2 systems involved
in the same GRS ring? With PDSESHARING(NORMAL) you would not
have even been able to update a member on one system if the other
system had the PDSE opened for update. The sharing is on a data set
level, not on a member level (sharing at the member level on the
same system does work).
Regards,
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:[email protected]
ITIL v3 Foundation Certified
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
