DSXchange

The xmlOutputStage only makes sense as a destination if it is running sequentially, so that it can put all the nodes back together... I'd have to test it further to determine exactly what it is doing, but I'm not surprised that the data isn't as you expect if it runs in parallel and is also the targ...

Make sure that "you" are entering the messages into the queue when doing such validation. Use DataStage, or amqsput (MQ command line utility -- do some searches --- you'll find the syntax)... Put "Hello World" into a message. Be sure that it is a simple datagram message --- pure ...

I would do a couple of things: a) put in a bogus queue manager name. and a bogus queue name. Be sure you get clean MQ failure messages in the log. This would at least absolutly ensure that you are "talking" with the MQ API properly. 2035 errors and such happen when queue details are wrong....

I thought we were talking about XMLInput Stage to break up the parsing of a document into more processes. I read the first entry too briefly. You could use XMLOutput in parallel, but you have to do the final construction of the resulting document yourself. You could, if it makes sense, use parallel ...

Hard to say then...indeed the validation should go down the reject path, and you can indicate what kinds of errors to be captured and what should happen. You might want to play with the various options (warning, fatal, etc.) and the column datatype for the column on that particular link that you are...

Support. There have been a variety of patches to validation. I haven't heard of one blowing up exactly this, but it's certainly possible, and you've narrowed things down. I will assume it works perfect when you uncheck the box.

Ernie

Check a couple of things....first, how is the XML Schema identified in the document? There should be an attribute in the header called something like schemalocation or sometimes NoNameSpaceSchemaLocation. This points to the xsd. To be safe, do your testing with this pointing to a 100% local and full...

Are you searching this forum and looking for any and every entry with "xml" ? ; ) Dig deeper. Look for entries with text(). You will be able to find additional commentary that will be useful in understanding this. In the meantime, you need the string "text()" at the end of your x...

Not at all...you can certainly use XMLInput in parallel...but think about what you are parallelizing..... XMLInput reads either "a chunk of content"....or a url to go and "get" an xml document. What source are you coming from? Was it running in parallel? ...or at the very least, ...

Not sure what option you are speaking of....but earlier, if you were getting zero rows, it is 99% of the time due to incorrect xpath. Do some searches thru the forum...there are lots of basic entries on using xmlInput Stage. In brief, keep using the Folder Stage to send your document or the filename...

....I am assuming in your first post that "what you are getting" and "what you want" are solely from the output of the XMLOutput Stage. ....they aren't even close, which means that the xpaths aren't right, or something else is strange. ...and if, in fact, it's something only when...

You have a lot of work to do, learning the XMLOutput Stage and exactly how it builds xml documents. Start by sending your output link from that Stage to a flat file...use a single column on the output link (call it something like mySOAPbody and make it varchar with a long length), and then in the se...

Can you also outline exactly what your symptoms are.... is your job aborting? Is it getting errors (what errors?)... Is it getting zero rows but ends successfully? Something else?

Ernie

Auditing, compliance, fear of not being able to prove compliance.....definitely things that are driving the need for better metadata and especially better lineage...

Ernie

...with the MQ Plugin, about the only way it could easily be done is with a value in the payload..... put a special value in the first couple of bytes to identify each "group" of logical messages.

Ernie