We are starting to implement use of XML PARSE and GENERATE statements and are having an issue with overflow conditions.
Previously, we had subroutines that encountered overflow conditions that were trapped (e.g via ON EXCEPTION, etc) but otherwise continued fine. Apparently this is because the 'program mask' has a flag set off, meaning that such events do not automatically cause an abend (SOC8).
We now find that once a module containing an XML statement has been called in the run unit, the 'program mask' has been updated with the flag set ON, meaning that existing code that worked before is now abending when encountering overflow conditions.
Needless to say, we have loads of existing code that worked before and would now fail if we continue to migrate to using XML. Our techies are working on more detail that I can post later, but I'd appreciate any comments from others who may have come across the same problem and, more importantly, solved it!
Previously, we had subroutines that encountered overflow conditions that were trapped (e.g via ON EXCEPTION, etc) but otherwise continued fine. Apparently this is because the 'program mask' has a flag set off, meaning that such events do not automatically cause an abend (SOC8).
We now find that once a module containing an XML statement has been called in the run unit, the 'program mask' has been updated with the flag set ON, meaning that existing code that worked before is now abending when encountering overflow conditions.
Needless to say, we have loads of existing code that worked before and would now fail if we continue to migrate to using XML. Our techies are working on more detail that I can post later, but I'd appreciate any comments from others who may have come across the same problem and, more importantly, solved it!