Ansicht
Dokumentation

RNX0353 - The XML document does not match the RPG variable; reason code &1. ( OS/400 )

RFUMSV00 - Advance Return for Tax on Sales/Purchases   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.


Message : RNX0353
The XML document does not match the RPG variable; reason code &1.

Message Long Text :

Cause . . . . . : While parsing an XML document, the parser found that the XML document does not correspond to RPG variable "&3" and the options do not allow for this. The reason code is &1. The exact subfield for which the error was detected is "&4". The options are "&5". The XML document name is &6; *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 &2.
9. The XML document contains a special attribute (such as fmt or adjust) that is not relevant or does not have a valid value.
10. An XML child element was found for a data structure having a subfield matching the datasubf option.
11. An XML attribute was found having the same name as the datasubf option.
12. An XML attribute or element was found having the same name as a subfield that is identified by the countprefix option. For example, if option "countprefix=n_" was specified, and there exist subfields "xyz" and "n_xyz", it is not valid to have an XML attribute or element with the name "n_xyz".
13. The countprefix and datasubf options identified the same subfield.

Message File : QRNXMSG
Library Message File : QSYS2924


Vendor Master (General Section)   BAL Application Log Documentation  
This documentation is copyright by IBM.

Length: 3275 Date: 20240420 Time: 174543     sap01-206 ( 3 ms )