Error messages like the following might be generated when you read XML files using the XMLV2 LIBNAME engine:

These errors occur when there are characters within the XML file which cannot be rendered correctly using the current session encoding.

To read the XML file correctly and prevent the error, modify the session encoding to the correct encoding, which renders the characters successfully.  

An alternative to the above circumvention is to use the COMPAT=YES LIBNAME statement option when you use the XMLV2 engine. This option treats the characters the same as the default behavior of the XML engine and simply ignores the character that it cannot render.  The sample code below illustrates this:

Operating System and Release Information