Page 1 of 1

help for exception

PostPosted: Mon Jun 22, 2015 9:06 pm
by adelinar
Exception 000529668 whit statment XML PARSE ... validating WITH FILE

I have a cobol pgm with the statment

XML PARSE input VALIDATING WITH mySchema-id
PROCESSING PROCEDURE p

but at the first row of input file :

<?xml version="1.0" encoding="utf-8"?>

i have the error 000529668 (RC=08, REASON=X'1504')

thanks for the help

Re: help for exception

PostPosted: Mon Jun 22, 2015 9:14 pm
by enrico-sorichetti
what happened when You researched the cobol/xml manuals
for the meaning of the RC 08 REASON 1504
or when You googled with
cobol xml rc 08 reason 1504 ???

Re: help for exception

PostPosted: Mon Jun 22, 2015 9:18 pm
by adelinar
the error means

1504 XRSN_OSR_INVALID The data within the OSR is invalid

but i not use an OSR but i load the xsd schema with a file into a work of the pgm

Re: help for exception

PostPosted: Mon Jun 22, 2015 11:10 pm
by Robert Sample
If you are working on a mainframe, there is a problem. If the data is encoding UTF-8, you would not be able to read the first line -- a mainframe uses EBCDIC which is NOT UTF-8. How did the data get to the mainframe? If it was transferred as text, then encoding needs to be changed to a mainframe encoding.

Re: help for exception

PostPosted: Mon Jun 22, 2015 11:35 pm
by adelinar
Thanks,
The file input was transferred as text. How can i convert to a mainframe encoding ?

Re: help for exception

PostPosted: Tue Jun 23, 2015 3:43 am
by Robert Sample
You could try
<?xml version="1.0"?>
or perhaps
<?xml version="1.0" encoding="ebcdic"?>
EBCDIC may need to be IBM-037 or IBM-1047 depending upon your site, but try EBCDIC first (but only if leaving the encoding off doesn't work -- defaults are usually the best way to go).

Re: help for exception

PostPosted: Tue Jun 23, 2015 6:25 pm
by adelinar
thanks, I tried this but also if I removed the total header from XML file or without encoding=utf-8 i got the same error.

Re: help for exception

PostPosted: Thu Dec 10, 2015 6:55 am
by Regg001
I had similar issue - i solved it by uploading the file using binary to the unix shelf instead of text mode. Then i was able to run a xsdosrg command on the file and it worked.

I haven't found a ''decent'' way to translate everything in a unix session. Short cut i'm using, i do my mods on my laptop on the source - then re-upload the file in binary mode to the mainframe and it works.

Are you running your program part of a CICS region ? (parse with validation).. If so , how did you defined the OSR file to the CICS region to allow the program to use it as an input file to create your work area ?