DSXchange

Only worry about it on your machine. Hard to say what's wrong.....that's not a terribly large amount...search the threads here...maybe you are already specifying "too" much. Put in a min and a max and try different increasing amounts for the max. Unfortunately it's a bit of a trial and err...

Ditto to everything above.....another thing to consider is to not let the XMLOutput Stage do the actual i/o ....if the xml documents aren't extrememely large, put an output link on the xmlOutput Stage with a single column....called it something like "myXMLoutput" with a longvarchar datatyp...

Default namespaces can be a pain to work with. As Craig suggests, put a snippet of xml here so we can see..just need the first couple of elements and attributes near the top along with the all-important header..... share your xpath also (the Description property of your xmlInput Stage's output link)...

Right mouse click on the WSTransformer.....enter "grid style"...in there you will see a property for "jvm options" or something like that.... in there you can set increase the heap size. I can't remember the exact syntax (search the web for java heap size, and look in other threa...

client mode or server mode?

(thank you Andy ; ) )

My blog covers the "concept" of RTI and ISD, but syntactically talks mostly about ISD, which is the 8.x "generation" of the original RTI technology. I will assume that you have the RTI console installed, and that your DataStage Server is fully authorized to support RTI Jobs.........

Absolutely....but as I said, be careful...you are going to end up with all kinds of table definitions, depending on the creativity of the author of your xhtml document. Every repeating list or other item within the "body" might need its own link and its own repeating element. Could get ugl...

No....and in fact, trying to read xml with Seq Stage will potentially get you in trouble. Look thru the forum and check out my blog below for techniques on reading XML as a source. Provided that the xml documents aren't "huge" you can just load them directly into MQ without any need for th...

I'm not entirely sure I understand what you are trying to do, but it sounds like "duplication of some rows" may be necessary to accomplish your goal. I would probably try to figure out exactly what order of rows (and how many of them) would I need to "easily" build the xml desire...

Hmm. That's a new one. MQ sites say that it has something to do with a parameter called EXTSH (or similar). Haven't seen it, but a few of the MQ sites I was browsing seem to imply that it existed in prior releases....did they make any changes to the queue manager configuration?

Ernie

The Repetition element is "one per output link"....so you should definitely be able to improve on your current scenario dramatically. One link for each detailed repeating node scenario.

Ernie

How "complex" is each complex element? Does each of the "100" have it's own inner repeating nodes? Or is each of the 100 just a single set of additional elements that occurs one time? (or perhaps some of them have multiples while others do not).... The XMLInput Stage can do all o...

From everything I can tell by looking at samples on the web, it's nothing but pure XML.....the tags are very html-like, meaning that they don't convey "metadata," they convey formatting......but you should very definitely be able to pull out the bits and pieces that you want. The real prob...

My bet is that this is simply an initialization issue. You are saying that it takes that long even if the source file is completely empty? Sorry I missed that point earlier. There are a ton of processes being started here. Hopefully you are using a single node config file, but even if not, you seem ...