PDSE sharing using CA MII - IEC143I 213-70

Products

• MIM Resource Sharing (MIM)
• MIM Data Sharing (MII)

Issue/Introduction

Two LPARS, DEVP and PROD, running CA MIM (MII) r12.5.

Both are in MONOPLEX mode with GRS=NONE and GRSRNL=EXCLUDE.

PDSESHARING = NORMAL. 

MII GDIF defined with PROCESS=ALLSYSTEMS and are using COMMUNICATIONS=DASDONLY 

Below QNAMES dynamically set as suggested in MIM Installation guide.

SYSZIGW0 SCOPE=SYSTEMS ECMF=NO GDIF=YES EXEMPT=NO
SYSZIGW1 SCOPE=SYSTEMS ECMF=NO GDIF=YES EXEMPT=NO

Getting IEC143I 213-70 error when attempted to create new member in a PDSE shared between out DEVP and PROD LPAR.

Any suggestion regarding CA MIM configuration to share PDSE between two MONOPLEX systems?

Environment

Release : 12.5
Component : MII

Resolution

MIMs only job is to propagate the SYSZIGW0/SYSZIGW1 enqs from one monoplex to the other.  So, if MIM is doing this properly the IEC143I message is something being generated by IBM and not MIM itself.

Based on a DISPLAY COUNTS information, MII GDIF is indeed processing the enqueue as expected.

RESOURCE TYPE  ------ ENQS ------   ----- RESERVES -----     GLOBAL   

 (QNAME)        ISSUED  PROCESSED      ISSUED   PROCESSED   CONFLICTS 

SYSZIGW0  S    137,989    137,989           0          0           7

SYSZIGW1  S          1          1           0          0           0

 

The IEC143I 213-70 is being generated by z/OS and not by GDIF. The S213-70 is how PDSE's are protected when PDSESHARING=NORMAL. The message/abend is how IBM maintains integrity.

 

As a reminder, PDSE Sharing in NORMAL Mode when the MIMplex=Sysplex is not managed. In this configuration, the resources are raised specifying RNL=NO - a condition MIM doesn't manage.

Additional Information

Review MIM documentation for information regarding PDSE Resource Sharing:

• PDSE Type Data Set Considerations
• MIM QNAME/EXEMPT Processing Flowchart

---

Articles from SHARE related to PDSE:

PDSE Performance Basics

PDSE Nuts and Bolts