#Xml tools errors detected in content how to#
#Xml tools errors detected in content code#

The 'standalone' attribute in the XML declaration was not specified correctly. The parser found an invalid attribute instead of the optional standalone declaration in the XML declaration. The value did not begin with lowercase or uppercase A through Z, or 'encoding' was not followed by '=', or the value was missing or improperly delimited or it specified a bad character, or the start and end delimiters did not match, or the parser found an invalid character following the closing delimiter. The encoding declaration value in the XML declaration was missing or incorrect. The parser found an invalid attribute instead of the optional encoding declaration in the XML declaration. 'version' was not followed by '=', or the value was missing or improperly delimited, or the value specified a bad character, or the start and end delimiters did not match, or the parser found an invalid character following the version information value closing delimiter in the XML declaration. The 'version' in the XML declaration was not specified correctly. The version information was not present in the XML declaration. The parser found an invalid character following '&' in a character reference or entity reference. The first character of the processing instruction target name was not a letter, '_', or ':', or the parser found an invalid character in or following the processing instruction target name.Ī processing instruction was not terminated by the closing character sequence '?>'.

The parser found an invalid start of a comment or CDATA section in element content.Ī processing instruction target name was not specified correctly. The first character was not a letter, '_', or ':', or the tag was not terminated by '>'. The element end tag was not specified correctly. The first character of the attribute name was not a letter, '_', or ':', or a character other than '=' was found following the attribute name, or one of the delimiters of the value was not correct, or an invalid character was found in or following the name.Īn empty element tag was not terminated by a '>' following the '/'. The first character was not a letter, '_', or ':', or the parser found an invalid character either in or following the element name.Īn attribute was not specified correctly. The parser found a second document type declaration.Īn element name was not specified correctly. The parser found a possible invalid start of a document type declaration. The parser found an invalid character in an attribute value. The parser found an invalid character in an entity reference name. The parser found an invalid digit in a decimal character reference (of the form &#dddd ).Ī character reference did not refer to a legal XML character. The parser found an invalid digit in a hexadecimal character reference (of the form �, for example ັ). The parser found an invalid character in a processing instruction data segment.Ī processing instruction target name was 'xml' in lowercase, uppercase or mixed case. The parser found the markup character '' without the matching opening character sequence ''. The parser found a duplicate attribute name. The parser found an invalid start of a processing instruction, element, comment, or document type declaration outside element content. The parser found an invalid character while scanning white space outside element content. The following table shows the meaning of each parser error code:

#Xml tools errors detected in content code#

From the message, you can get the specific error code associated with the error, as well as the offset in the document where the error was discovered. If the XML parser detects an error in the XML document during parsing, message RNX0351 will be issued.

#Xml tools errors detected in content how to#

How to change CCSID in a RPGLE Program * Execute A Commandĭ s 1a = 'CHGATR OBJ(' + + %trim(filePath) + ') ATR(*CCSID) Parser Error Codes %trim($errorPath) + + to change CCSID in a CLP Program CHGATR OBJ(filePath) ATR(*CCSID) VALUE(1208) How to catch RNX0351 error during XML SAX parsing monitor

You can look at the ccsid=ucs2 feature to figure it out. This method worked for most of my XML files but not all. The CCSID of my XML file was 819 and I had to change that to 1208. After quite a bit of research found that you have modify the CCSID of the XML file in IFS. And when I tried to parse this using the RPGLE SAX parser the Buyer name element had some special character causing it to fail. Well in this case I received an XML from Amazon into the IFS. How to resolve XML parsing error RNX0351? While parsing an XML document for an RPG procedure, the parser detected an error at offset.