Search results for query: *

Hi k5tm, thank you for your inputs. Yes I probaly have to take a deep breath and work with something else a few ;-) However I'm running the program as a CICS program, so there will be no job steps before the program is run. I receive the message on a MQ queue. However it isn't the XML...

Hej ziggetty, have you downloaded the Enterprise COBOL Programming Guide? Says here that an exception number 6 is: 6 The parser found an invalid character in element content. The parser continues detecting errors until it reaches the end of the document or encounters an error that does not...

Sorry missed this post from you k5tm No it doesn't support XSLT from what I have read. Doesn't even really support any validation except for what is validated through your XML event handler. Regards Jacob

Hi, first of all thank you all for your inputs - unfortunately it seems like we have all reached the same conclution. to Bob - yes I have read that part too ;-) I have practically been wearing bits of my COBOL programming guide.pdf in my search for answers concerning ATTRIBUTES and encoding...

Thank you guys for your answer - really nice to know that I'm not the only one here. An other question I have now is how do you define to the XML GENERATE that some of your Working Storage areas are ATTRIBUTES and their ATTRIBUTE NAMES along with ATTRIBUTE VALUE CHARACTERS? To me it seems like...

Hi there, as I can see in the old post thread209-1101822 this topic has been up before but no answers were given. I too have the same problem with the XML parser not being able to handle the encoding='UTF-16' IBM-1200 ibm-1200 etc. It always fails on the encoding part. Like mentioned in the...