COBOL

COBOL

COBOL

COBOL is responsible for the efficient, reliable, secure, and unseen day-to-day operations of the world's economy.

 View Only
Expand all | Collapse all

Suggestions on troubleshooting OSR / VALIDATING WITH FILE

  • 1.  Suggestions on troubleshooting OSR / VALIDATING WITH FILE

    Posted Mon October 01, 2018 05:56 AM

    Greetings,

     

    We are attempting to run a cobol xml parse, validating with file. We have succesfully generated an OSR but when running the program in question it fails with with the following code.

    8404 XRSN_DEM_INVCHARINPROLOG
    An invalid XML character was found in the prolog of a document.
    Action: Change the document or schema to correct and retry.

     

    Can anyone help with how to troubleshoot this ? We are running this from JCL. The XSD is uploaded to USS by means of FTP where we request a binary upload. So we are expecting to see UTF8 there. The XML itself is generated by means of a cobol xml generate with encoding 1208. The failure occurs during the start-of-document event. How should we go about troubleshooting this in Cobol ? There isn't much in terms of experience with OSR in our organisation (it could very well be a basic error) and manuals seem to focus a lot on C with which I myself am unfamiliar. Any insights would be greatly appreciated.

     

    Best regards,

    Frankbd

    Frankbd


  • 2.  Re: Suggestions on troubleshooting OSR / VALIDATING WITH FILE

    Posted Wed October 17, 2018 01:09 PM

    You mention that you ftp'd the XSD file to USS, but did you then run the xsdosrg command on USS?

     

    Have you checked out this link in the Enterprise COBOL Programming Guide?

    https://www.ibm.com/support/knowledgecenter/SS6SG3_6.2.0/com.ibm.cobol62.ent.doc/PGandLR/tasks/tpxml35.html

     

    If you are still having issues, let me know.

     

     

    DavidHT


  • 3.  Re: Suggestions on troubleshooting OSR / VALIDATING WITH FILE

    Posted Thu October 18, 2018 04:12 AM

    Hello David,

     

    Thanks for replying. I must admit, I forgot about this thread. Pretty much because we solved the issue. It ultimately came down to errors in the cobol code in question. The whole thing ran perfectly and the samples used to describe this are spot on.

     

    Best regards,

    Frankbd

    Frankbd