DSXchange

ok. So that worked. Aggregation is behaving as it should for this particular column. 3 rows...3 instances. In your original post, it was the same tree....but broken into two different highest level nodes. Now it is not. If you remove fred/sally/alice (take them out one at a time), do you still get a...

You can't. If you want always on...use the ISDInput....if you want "start on demand" (meaning ...start the job, for EACH request coming in, and only when the request arrives), then use some other Stage as the starting point. ....in that case, where do you get the data from? Well, it can co...

Well... there are two topics of discussion going on here then. From the original post, it looked like you had two rows of data, one single column, and trying to make sure they both get into the inner most element as a repeating group. Now we're looking at three entirely independent nodes at a higher...

hard to say. Let's look at your xpath for the entire input link.

Some other thoughts... a) make certain that you do NOT have validation selected in the Composer step b) do tests with 100% character string data (varchar, char on the links), and find (for testing) an xsd that uses only xs:string elements. Also...what are the sequence of Steps in your Assembly? Are ...

The majority of new Stages are produced on or for the Parallel Canvas. that being said, there are exceptions, the xml Stage being one of them, although it is not as fully functional as it is in Parallel Jobs. Server Jobs have a place....there are a variety of times when they are preferred (beyond ju...

At the moment, I can't imagine. Never seen it do that. ...unless there is other logic in your Assembly, like a pivot or an aggregator or a switch, etc. that is causing it to drop. Put a transformer in front of the xml and send the rows to another sequential file. Be sure your first row (let's stop c...

Maybe I confused you in my suggestion above. I want you to add three entirely bogus columns...each at the SAME level as the repeating element that wasn't working in your very first post: fred sally alice those are the actual column names. In an upstream transformer, give them a counter value....perh...

Well...it's probably pushing on some limits or boundaries somewhere. Formally, the Stage does not support more than one input link a Server Job, or more than one output link.....so it might be related in some way...... if you are really doing two entirely independent streams, just make it two separa...

Hard to say exactly, but I've seen things like this before when there is only one or two columns (up to 4) being aggregated. As a test, try adding another field to the input link (or perhaps 3 more). In an upstream transformer, create a counter that increments uniquely, and then add that to the xml ...

You say "header"..... but do you really mean "the first row"? Often a header means a row that is in some different type of format. If we assume that you simply have three TOTAL rows, then perhaps your schema has other validating criteria. Are the datatypes correct? are there any ...

The data in the resulting xml document appears to all be related to each other....meaning that program "appears" to belong to customer and company......Assuming you are using the xmlOutput Stage, do whatever you have to PRIOR to the xmlOutput Stage to get those all onto the same link.........

It's not exactly clear to me what you "want" to get, or what the exact issue is. Can you provide a bit more detail and explanation?

Thanks.

Ernie

and note which column is checked as the "key" (repetition element).

Ernie

Yes...you tell it to look for "this" value in the formal MQ Message Type...set that at the source stage, using a long 6 digit integer value. Another Job (or "any" application) can populate the "stop" message with that value.

Ernie