Previously working RPGLE applications that use XML-INTO fail with message RNX0353 with reason code 1 after installing PTFs.
Resolving the problem
Previously working RPGLE applications that use XML-INTO fail with message RNX0353 with reason code 1 after installing PTFs:
RNX0353 Escape 50 mm/dd/yy hh:mm:ss.ffffff QRNXUTIL QSYS *STMT PGMNAME PGMLIB *STMT
From module . . . . . . . . : QRNXXML
From procedure . . . . . . : _QRNX_XML_INTO
Statement . . . . . . . . . : 105
To module . . . . . . . . . : Modname
To procedure . . . . . . . : Procedure
Statement . . . . . . . . . : Statement Number
Message . . . . : The XML document does not match the RPG variable; reason code 1.
Cause . . . . . : While parsing an XML document, the parser found that the XML document does not correspond to RPG variable response and the options do not allow for this. The reason code is 1. The exact subfield for which the error was detected is response. The options are <options>. The XML document name is <document name>; *N indicates that the XML document was not an external file. Recovery . . . : Contact the person responsible for program maintenance to determine the cause of the problem. Technical description . . . . . . . . : Reason codes and their meanings are as follows: 1. The specified path to the XML element was not found in the XML document. 2. The XML document contains too few array elements for array subfields of a data structure. 3. The XML document contains too many array elements for array subfields of a data structure. 4.
The XML document is missing XML attributes or elements to match subfields. 5. The XML document contains extra XML attributes or elements that do not match subfields. 6. The XML document contains text content within the
content for the subfields of a data structure. 7. The XML document contains unexpected attributes or child elements for XML elements that match RPG scalar fields, subfields or array elements. 8. The XML document contains data that cannot be successfully assigned to the RPG variable. The RPG status code associated with the failure is 0. 9. The XML document contains a special attribute (such as fmt or adjust) that is not relevant or does not have a valid value.
Previously, there was a bug in XML-INTO where even if the path specified in XML-INTO did not exist, it would not fail. It was documented in the ILE RPG reference that it an error would be received; however, no error was shown. The following PTFs fixed this problem:
V5R4 - SI43659
V6R1 - SI43158
V7R1 - SI43159
For more information, see APAR SE47330 at the following URL:
The resolution is to change the code so that XML-INTO references a valid path in the XML file.