Solution found.
Apparently, it was the creation of the problem XML file. The process used to create the file include running separate SQL queries using the FOR XML clause and then pasting the results into the file. The file passed XML validation in several of the XML parsers (XML Spy, SAS XML Mapper, etc). But the XML92 engine in Base SAS was unable to read the data.
The file was recreated whole and now Base SAS can read the data from the XML file. No changes were made to the map file nor the SAS program I had developed. Important to note: the XML92 engine does not pass an error message to the log.
As of this morning, I still do not know what prevented the engine from reading the data. But I did receive the SAS Note email this morning which had this reference:
http://support.sas.com/kb/41/067.html
********
Problem Note 41067: Using the XML92 engine might generate an error or shut down SAS when the data contains specific characters
Using the XML92 LIBNAME engine might generate errors and shut down SAS if the data contains specific characters. The characters that potentially could cause the problem are characters that require escaping, such as the following: & < > "
The XML92 LIBNAME engine can overwrite memory when it escapes these characters, which causes the problem.
A hot fix is planned for this issue.
*******
This may have been the issue. I had found “&” within a data field, but when I had replaced it with an appropriate fix, the XML file was still not read correctly. Maybe there was an errant “ (double quote) somewhere in the file that I did not find.
Thanks for all assistance…