DSXchange

Then I would assume you've got at least 5 dead / zombie ones. No clue how that all changed in the 8.x release, however.

Another example:

http://www.dsxchange.com/viewtopic.php?t=85743

Searching for "errorlevel" may turn more up as that is how you check execution status in a DOS batch file.

You'll need to add some level of error checking, this example has none - zip, zilch, nada.

Most here are for UNIX but found this, it might help:

http://www.dsxchange.com/viewtopic.php?t=107766

Take out the bits you don't need and ain't much left, however.

Please don't quote everything every time you post. There's a lovely Reply to Topic button you can use below the current post that doesn't clutter things up quite so much.

OK. Is your job sourcing from this file? If so, then what you have should work provided the sql is syntactically correct by passing it as another field on the link. If not, explain your job design so we have some clue what you've built and where things are coming from. Bottom line - you always need ...

Ah... there is is:

$DSHOME/.dsadmin

Cat that and see what it says. Mine:

What? That's an important piece of information you left out. Which "it" does not belong? First figure out what the SQL needs to look like outside of any tool before we worry about DataStage.

What happened when you tried?

Just like you are doing is fine. Or perhaps use a job parameter if the value can change run to run.

And what happened when you tried?

Now your SQL is fine but you've blown a Foreign Key constraint. Completely different problem. Talk to your DBA if Referential Integrity is a new subject for you.

Besides, advising anyone to "kill -9" anything is not the best thing to be doing. Maybe a "kill -15", but best to stick with established interfaces so everything is done correctly.

In other words:

rupesh.datastage wrote:is it a right thing to do ??

No.

The Contact link at the top of every page. There's no phone number that I'm aware of.