An IDMS Production CV abended with message IEC143I 213-FD
CCSR010E RHDCOS00 S213 AT 000096C8 LMOD IDMSDC CSECT RHDCOMOC +0026C8
CCSR021I OWNER = CA IDMS R18.5
CCSR022I MODULE = RHDCOMOC FMID = CAGJI50 RMID = RO60748
CCSR062I ILC: 02 INTERRUPT CODE: 0D
CCSR067I COMPLETION CODE S213 REASON CODE 000000FD
Above abend occurred while a batch UCF job was attempting to vary an application DDLDML dictionary area from retrieval to update. The same area was also in retrieval mode in another CV on a different z/OS partition.
What is the 213-FD and how to avoid this abend??
From the IBM Z/OS System Message Guide, the IEC143I error message states:
An error occurred during the processing of an OPEN macro instruction for a
data set on a direct access device. This is probably a user error.
An attempt was made to open a physical sequential data set for output with
DISP=SHR when the data set was already opened for output processing and
enhanced data integrity MODE(ENFORCE) was active.
For return code FD, opening a PS data set for output while it is already open
for output is not allowed by the enhanced data integrity function. Correct the
application, have the system programmer add this data set name to the exclude
list in the PARMLIB member IFGPSEDI, or bypass enhanced data integrity
processing by setting the DCBEEXPS bit on in the DCBE or by specifying the
"bypass data set integrity" option in the program properties table or the
dynamic allocations options. For information about specifying the "bypass data
set integrity" option, see z/OS MVS Initialization and Tuning Reference
IDMS provides area security, by returning an error when 2 systems try to access an area in update mode, by looking at the area SMP lock. This is after the OPEN. The error S213-FD is occurring when the area/file is being opened. This is IBM's way of securing 2 areas/files from simultaneous updates.
You'll have to put the dictionary DDLDML and the DDLDCLOD areas into the exclusion list, informing IBM that these areas will be secured by IDMS.
On the question whether it is possible for IDMS to trap and handle this specific abend so as to avoid the IDMS CV from crashing; currently we don't know if IDMS can tell IBM before the open, that we want control back, and that there's some sort of return code we can interpret, and put out a warning. Create an IDEA/Enhancement to request handling of this error at a future incremental IDMS Release.
IBM Z/OS V2R1 System Messages Guide