XML Parse with COBOL and XML System Service - better design to avoid truncated XML element content

Current situation:
------------------
Extra COBOL program logic for every XML element content is necessary to check for split content and to concatenate pieces of content for this case.

Enterprise COBOL V5 is running with z/OS XML System Service to parse XML data (XML PARSE ?).
For the XML events ATTRIBUTE-CHARACTERS and CONTENT-CHARACTERS the XML-TEXT contains the character content of the XML element. This can be the whole content of the element but unfortunately also only a substring of the content.
For every XML PARSE the programmer has to add additional coding to check for splits and to concatenate pieces of content if a split is detected.
This has to be done by checking the COBOL special register XML-INFORMATION (implemented with APAR PM85035).

Even with an XML content of 12 bytes we recognized such a truncation.
We analyzed this case in PMR 79415,035,724. The truncation occurs due to z/OS XML code reaching the end of an LE HEAP element of almost 200K that could not hold the complete string of 12 bytes any more.
Instead of obtaining a new piece of storage, only a substring of the XML content was returned.

Suggested improvement:
----------------------
It would be a much better design in our view if COBOL/XML System Service handled this case in a transparent way and returned the complete XML content to the COBOL program.