DSXchange

Hmmm... what happens when you try just a plain "Execute_Command_1.$CommandOutput = 0" condition?

Do you have any better idea? Can we leverage the constraint setting in the transformer stage? Yes. As noted, you can setup a specific reject row link and constrain it so that only 'database issues' are sent down it using the Output Link Variable of REJECTEDCODE. Set that constraint to 'Abort after ...

Welcome! :D

I've got no answer for you, being strictly (so far anyway) a UNIX 'DataStager' but thought you might want to add some specifics to your post. What is your exact version of both DataStage and Windows? May make a difference in the answer you get...

There's a little bit more to it than that. Yes, zero means 'all or nothing' and is needed in order to rollback an entire transaction if there are problems. However, in order to trigger the rollback, the job must abort - not finish in any fashion, including 'with warnings'. Accomplish this by various...

You can't or you would violate the constraint, as you've seen. But you can do a couple of different things with the second occurance of the primary key - 1) Update rather than insert or 2) throw the record away. That's something you would have to decide. I am assuming that you are doing a hashed loo...

Because the moment you reimported your changed source and recompiled it, those pesky lines were added right back in. You need to copy/paste the code into the Job Control page of a regular Server job - i.e. not use a Sequencer job type - and then you are free to hack away at it. Of course, then the m...

What shows in the job's log? How far is it gettting, what is it logging before the 'hang'?

Thanks, Arnd. Never got enough time (or energy) yesterday to come back and see what happened with this thread.

kumar_s wrote:But winky man gets me to login page, probably while capturing link, page might have timed out --->:cry:

That's generally a cookie problem when you logon doesn't 'stick'...

If it works for other people on other machines, but not for you on your machine, the first thing to try would be a reinstall of the client software on your machine. Reinstall it right over the top of your existing installation and let us know if that fixes it.

Client - sure. PX Server - no. You'd need a very specific version of DSEE (as just noted in another thread) 7.5.X2 I believe, in order to run PX jobs on a Windows box. Off the top of my head, the Client supports Win XP Pro, 2000 and 2003 while from what I recall the 'PX Server running on Windows' bi...

Well, there is a specific version of DataStage EE that allows you to run PX jobs on Windows - 7.5.X2 - from what I recall.

Check his delete statement, it's doing a WHERE clause with a range, it's not expecting a streaming of values to feed a DELETE cursor. That method would work if a single row, single column of data was fed to the ODBC stage using custom SQL to just perform the delete. Another stream would then send t...

Or perhaps via a second link - which should be the first link sent to the stage when checking row order. Constrain it to only send one row (if appropriate) and you may need to commit the deletes before you do the insert to avoid locking yourself.

Keep in mind the fact that 0 is the same as 'false' or equivalent to the @FALSE system variable while 1 (actually any non-zero value) is 'true' or equivalent to the @TRUE system variable. Check the online help for reject row handling as it goes through all this. REJECTEDCODE is non-zero (or @TRUE) w...