DSXchange

:) ...been watching. I haven't seen java stack errors on an import. My only initial guess would be to check for things like: a) names of objects... table names, anything strange b) is it repeatable? you said it works sometimes and sometimes not....but..for the "same" database does it alway...

hmm. At the moment, I'm not sure.....but are you certain that it's saying it can't find "this" file, or is it looking for an xsd? Also, play more with a Job that just uses the External Source to a Sequential Stage. Make sure you can get any file listing from any subdirectory successfully. ...

Not sure how you imported your metadata, but ultimately, on the output link of your xmlInput Link, scroll to the right and look at your column Desscriptions. The answer for something like this is usually in there. You will want to see something like (for each column in the grid): Customer /.../.../C...

That's the complete quote I was looking for in the 1000 dollar question ; ) "All the world's a Stage and the men and women merely players " ...but you have to say "What is?". :) But we'll give you the 1000....... Ernie PS. That's the quote that came to me when I wrote this redicu...

Hard to say, but what happens if you do everything with a single node config?

Ernie

Correct answers are quotes from the famous playwright, using hints from DataStage... ; ) (Anyone catch Watson on Jeopardy this week? Pretty cool, eh? Perhaps it will start answering our DataStage questions! --- sorry all --- am jetlagged in another time zone and my brain is tired from working on xml...

Can you explain your problem in more detail? It's not exactly clear what the issue is......

We assume that the xml you pasted is what you "want"..... please paste what you are getting that needs to be different.

Thanks.

Ernie

At quick glance, it looks identical at the bottom, where it counts for the repetition element. I might have missed it on a quick look, but everything above it (the lower attribute nodes) appears to be unique, so the behavior should remain the same. I won't have time to try your larger example for a ...

It also takes up less space. I've seen REDICULOUSLY large xml documents that were reduced by a third in size just by removing blanks and carriage return line feeds. Important when you are shipping them all over the place in transactional packets.

Ernie

You've done a great job so far.....the likely problem is that the second pivot should be independent of the first. Meaning --- split the data appropriately via copy or transformer... pivot your addresses on one path, and build that chunk of xml....then on the other path, pivot your contact methods a...

Give it a try and let us know how it goes.... ......although this is something I've been doing since 7.0.0. Provided a node really only occurs one time, I've always been able to include it as part of the current "row" (meaning --- specify the repeating element in any of those sub-nodes bec...

It shouldn't be this difficult...... build some simple jobs to test the technique. It's perfectly fine to test a column returned from a lookup (usually with IsNull() in a downstream transformer), and if it is null, set a "user message" as desired to be returned to your calling web service ...

....the most elegant (and most performant, least intrusive) way is to use InfoSphere CDC, which monitors the rdbms log directly --- sending details to DataStage as soon as they are committed..... This is the integration with what used to be "Data Mirror"..... in 8.5 the integration became ...

I don't have access to DataStage right now, so I can't tell you exactly what it says, but the input arguments are specified within the Stage itself. It should be fairly clear from the GUI --- you can hard code the values or use Job Parameters....it's on one of the tabs.

Ernie

Not sure if there is an issue? .....sounds like it is working great... ...but of course, for a real time job like this, you should have a single node configuration. Then, if you browse, you will get only one copy of the message, not multiples. There are only very rare cases when a real time job need...