Integrity Exposure Issues

Advanced Topics › Global Data Set Integrity Facility › PDSE Type Data Set Considerations › Integrity Exposure Issues

Integrity Exposure Issues

For CA MII customers who are sharing PDSEs in a MIMplex that does not equal a single sysplex, integrity exposures can occur between the sysplex systems and the systems or sysplexes outside the local sysplex. Because the SYSZIGW0 and SYSZIGW1 ENQs are issued with RNL=NO, CA MII bypasses those ENQs and passes them on to GRS. All of the systems in the originating sysplex are aware of these ENQs because GRS propagates them to the systems in the local sysplex. However, because CA MII bypasses these requests, the systems outside the originating sysplex are unaware of these ENQs.

The following table illustrates in what environments it is safe to share PDSEs across all systems in the MIMPLEX:

DASD Sharing Environment	PDSESHARING Mode

DASD Sharing Environment	Normal	Extended
Non-sysplex systems	Yes	n/a
Single sysplex systems	Yes	Yes
Single sysplex plus non-sysplex systems	No (see Notes)	No
Multiple sysplexes plus non-sysplex systems	No (see Notes)	No
Multiple sysplexes	No (see Notes)	No

Notes:

To share PDSEs in non-sysplex environment, do one of the following:
- Specify GDIINIT PROCESS=ALLSYSTEMS
- Specify the following statements in the MIMQNAME member:
```
SYSZIGW0 SCOPE=SYSTEMS ECMF=NO GDIF=YES EXEMPT=NO       
SYSZIGW1 SCOPE=SYSTEMS ECMF=NO GDIF=YES EXEMPT=NO     
```
PDSE sharing in mixed sysplex environments is not safe, due directly to the inappropriate use of RNL=NO on the SYSZIGW0 and SYSZIGW1 ENQs. See the IBM APAR OW30729 for clarification of this issue.

At the present time, we recommend that you not manage PDSEs with EDIF.