Question & Answer
Question
What does Message IEC143I RC 213-74 signify?
Answer
DESCRIPTION
Message IEC143I RC 213-74 is issued for an error that occurred during OPEN processing for a data set on DASD. Reason code of 74 indicates that the OPEN detected a MEMBER share conflict for a PDSE data set.
RESOLUTION
IEC143I 213-74 is issued to preserve the integrity of a PDSE and to prevent simultaneous updates to a PDSE member. This error message indicates that a sharing violation occurred for a PDSE member.
In a PDSE Extended Sharing Multi-System environment, if one sharing system is performing a PDSE member update in place, then access to the PDSE data set is denied to other system. Access on the other sharing systems is blocked regardless of the processing intent of the OPEN.
Section 8.5.1, titled, 'Scenarios for PDSE Extended Sharing Across Systems' in the 'Partitioned Data Set Extended Usage Guide' (SG24-6106-01) states:
Table 8.7 titled "PDSE SYSPLEX Level Sharing" from the same manual supports this statement.
Circumvention by holding a PDSE data set EXCLUSIVE is possible, but not recommended. Specifying DCB=OLD in the JCL allows the data set specified in the DD statement to be held exclusive. As this would circumvent the possibility of receiving IEC143I 213-74, it would also effectively 'invalidate' sharing of this PDSE with others.
Message IEC143I RC 213-74 is issued for an error that occurred during OPEN processing for a data set on DASD. Reason code of 74 indicates that the OPEN detected a MEMBER share conflict for a PDSE data set.
RESOLUTION
IEC143I 213-74 is issued to preserve the integrity of a PDSE and to prevent simultaneous updates to a PDSE member. This error message indicates that a sharing violation occurred for a PDSE member.
In a PDSE Extended Sharing Multi-System environment, if one sharing system is performing a PDSE member update in place, then access to the PDSE data set is denied to other system. Access on the other sharing systems is blocked regardless of the processing intent of the OPEN.
Section 8.5.1, titled, 'Scenarios for PDSE Extended Sharing Across Systems' in the 'Partitioned Data Set Extended Usage Guide' (SG24-6106-01) states:
A sharer of a PDSE can read existing members and create new members (or copies of existing members) concurrently with other sharers on the same or other systems. But shared access to a PDSE, when update-in-place of a member is being done, is restricted to a single system. The update-in-place access restriction exists from the time the update program is positioned to the member (through FIND or POINT macros) to the time the update program positions the directory or closes the PDSE. |
Table 8.7 titled "PDSE SYSPLEX Level Sharing" from the same manual supports this statement.
|
This table describes the results for different scenarios for an OPEN when two systems are sharing a PDSE.
Circumvention by holding a PDSE data set EXCLUSIVE is possible, but not recommended. Specifying DCB=OLD in the JCL allows the data set specified in the DD statement to be held exclusive. As this would circumvent the possibility of receiving IEC143I 213-74, it would also effectively 'invalidate' sharing of this PDSE with others.
A software symptom record is written when a member sharing violation is detected. The primary symptom string for the Software Symptom LOGREC entry includes the following data:
The IGWLGLCN RC8 RSN3FFF software symptom record is written on the LPAR that holds the connection that results in the sharing conflict. Therefore it might be necessary to review LOGREC data from all LPARs within the SYSPLEX to identify the holding job and the LPAR.
SYMPTOM | SYMPTOM DATA | EXPLANATION |
PIDS/5695DF115 | 5695DF115 | COMPONENT IDENTIFIER |
RIDS/IGWLGLCN | IGWLGLCN | ROUTINE IDENTIFIER |
PRCS/00000008 | 00000008 | RETURN CODE |
PRCS/00003FFF | 00003FFF | RETURN CODE |
The IGWLGLCN RC8 RSN3FFF software symptom record is written on the LPAR that holds the connection that results in the sharing conflict. Therefore it might be necessary to review LOGREC data from all LPARs within the SYSPLEX to identify the holding job and the LPAR.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG90","label":"z\/OS"},"Component":"5695DF115;PDSE","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"2.2;2.3;2.4","Edition":"","Line of Business":{"code":"LOB56","label":"Z HW"}}]
Was this topic helpful?
Document Information
Modified date:
03 September 2021
UID
isg3T1010622