DSXchange

Well... I did tell you it wouldn't work that way. And once again your explanations of what you are doing are hard to follow. Sorry. :( What does it mean when you say you used the "actual source as lookup"? If you are trying to compare a hashed file lookup to any other kind, like say a dire...

SON OF A... why did it take me posting it here to notice the fricking problem? And why in the hell did it "work" on Linux? Obviously, it didn't but it also didn't complain about the syntax... and wasn't doing what I wanted it to do.

This is making me crazy. :x Have a script that runs just fine in any shell on my Linux box but when I send it off to HP-UX land, the user gets a syntax error. I'm not doing anything I haven't done after working on HP-UX systems for the last umpty years so at a loss to explain it at the moment. Not t...

FYI... this just saved my bacon as I had the issue after installing the 8.1 client - 7.5.2 gave me the same stupid message after switching back.

All better now! :D

(mmm... bacon)

So... your server is installed on a Windows XP box? Since the only 'supported' Windows O/S for IA is Server 2003 SP2, I wonder if that could be the problem? Or at least a problem.

Ah... didn't realize it actually (and officially) reported "Startup time" in the log, my bad. I wonder exactly what that all entails? It doesn't include anything 'before job', just checked and verified that. I wonder if it would help at all to dump the score? Also, does this job use a diff...

Here. If there were any. Other than this one. And Ray's relocation request.

You'd need to provide more information before anyone can help. Simply saying "it is causing issues" isn't really enough for anyone to go on.

And also define what you mean by "startup time". For the job to say that it is "started"? Or perhaps log the "Initiated" entry? For an initial query to start returing rows? What?

asorrell wrote:I'm thinking maybe using the decode stage or the external stage might be a solution that could call an SSH command in some sort of a script to stream the data into the job without landing it.

Not exactly all that PX-savvy yet but that does sound feasible to me.

OK... how are you generating this "temp_id" value currently? Investigate the use of the Surrogate Key Generator stage and the use of a "state file", that's the "official" way to handle stuff like this.

And I specifically meant your DataStage support people. Good to check with other resources, but I would have started there.

Right. Those 'rejects' will still cause db errors to be generated & logged, the link just allows you to capture them - it won't suppress anything. Best to prequalify your data to ensure it doesn't blow any constraints.

Well... not to become an accomplice in this hijacking, but keep in mind the fact that everyone has an Execute Command stage but Windows peoples get a 'Command' stage as well.

eostic wrote:not sure if the XML Stages support it, or if it even makes sense for them to do so...

I kind of fall into this camp.

throbinson wrote:still believe your best bet would be some kind of custom XSLT. That seems to me to be too much work for too little reward.

And this one.

As noted, they will all start at approximately the same time and run as if they were three separate jobs. However, a failure in one job stream could doom all of the others, depending on the timing. It could also complicate restarts. No advantage, really, that I can think of. I'll guess that the thou...