Re: Help with XML-INTO

Just a basic thing - case does not match - now there is an option in the XML-INTO opcode that can deal with that - we need to see what you are using in that opcode.

Also, the XML nowhere has an element called RESULTS - I think you want to start with OUTPUT - the <?xml at the top is not part of the data.

Someone else can confirm or deny my feeble attempt!!

Cheers
Vern

On 7/12/2019 11:07 AM, Marvin Radding wrote:

I hope someone has some experience with the XML-INTO op-code.

I am trying to construct the data structure for this XML
-------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<Output>
<SearchResults>
<SearchResult>
<OTObject DisplayName="OTObject">810132</OTObject>
</SearchResult>
</SearchResults>
</Output>
-------------------------------------------------

I am getting this error: The XML document does not match the RPG variable; reason code 1.

This is the data structure I am trying to use to read the XML
----------------------------------------------------------
EVAL results
RESULTS.XML.VERSION = ' '
RESULTS.XML.ENCODING = ' '
RESULTS.OUTPUT.SEARCHRESULTS.SEARCHRESULT.OTOBJECT.DISPLAYNAME =
' '
RESULTS.OUTPUT.SEARCHRESULTS.SEARCHRESULT.OTOBJECT.OTOBJECT =
' '
----------------------------------------------------------

I can provide the RPG code to create this. I hope this is sufficient.

I have no idea what is wrong. It looks good to me.

If I can understand how to use XML-INTO for this xml, I am working to using it for a much longer and more complicated XML if which this is just a small sample.

Thanks,

Marvin
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced, traumatized, triggered, and crying for their safe spaces.

Notice: This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. This message may also contain Protected Health Information (PHI) and must be treated confidentially and handled in accordance with HIPAA and other federal and state privacy laws. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately and delete this e-mail (and any accompanying attachments).