Re: Help with invalid XML code issue

2017-06-14 Thread Jantje.
On Sat, 10 Jun 2017 14:26:32 -0700, Lizette Koehler wrote: > >I was supplied with an xml file to use to install a product. When it runs it >fails with the following error message. This is done on the mainframe in the >OMVS function. Try uploading it in binary mode (no conversion to EBCDIC).

Re: Help with invalid XML code issue

2017-06-11 Thread Elardus Engelbrecht
Lizette Koehler wrote: >Thanks. I removed the encoding section and it worked. I have been banging my >head for 3 weeks on this issue. Excellent! Thanks John McKown for your kind and amazing help to Lizette Koehler! You're one in a thousand! I am also interested in this, just in case I get a

Re: Help with invalid XML code issue

2017-06-10 Thread Paul Gilmartin
On Sat, 10 Jun 2017 16:48:06 -0500, John McKown wrote: >> >​Hum, 0x4c in UTF-8 is an "L". In EBCDIC CP-037 (et al.) it is a "<". If >you look at the first line: >​ > > >the phrase: encoding="UTF-8" says that the rest of the data is in UTF-8. >But it's actually in EBCDIC. So the XML parser "sees" th

Re: Help with invalid XML code issue

2017-06-10 Thread Lizette Koehler
t; > >-Original Message- >>From: John McKown >>Sent: Jun 10, 2017 2:48 PM >>To: IBM-MAIN@LISTSERV.UA.EDU >>Subject: Re: Help with invalid XML code issue >> >>On Sat, Jun 10, 2017 at 4:26 PM, Lizette Koehler >>wrote: >> >>> I

Re: Help with invalid XML code issue

2017-06-10 Thread Lizette Koehler
IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: Help with invalid XML code issue > >On Sat, Jun 10, 2017 at 4:26 PM, Lizette Koehler >wrote: > >> I am not unix or xml savvy. So any guidance will be appreciated. >> >> I was supplied with an xml file to use to install a p

Re: Help with invalid XML code issue

2017-06-10 Thread John McKown
On Sat, Jun 10, 2017 at 4:26 PM, Lizette Koehler wrote: > I am not unix or xml savvy. So any guidance will be appreciated. > > I was supplied with an xml file to use to install a product. When it runs > it fails with the following error message. This is done on the mainframe > in the OMVS func