DSXchange

If the metadata are different for each file create ten separate jobs to do the validation. Take OK triggers from each job activity into a Sequencer set to fire only if All of its inputs have fired. Make sure there is an alternative exit from the job sequence, for example non-OK triggers or automatic...

You can. You still need to set the environment variable in Administrator, and you still need to create a job parameter of this environment variable. What you then do is set the default value of the job parameter to the special token $ENV which instructs DataStage to read the value from the underlyin...

This can also happen if you leave the "Precision" field empty, which is treated as the same as 0 by DataStage.

Yeah, it should be called the "Not Found" link. They got it right with Transformer, and it's "Otherwise/Log" link, but that's purely serendipitous; it's only because the Transformer also supports a reject link for handling rows that raise exceptions.

That definitely sounds like a bug. Have you reported it through your support provider? Clearly you can generate a reproducible case. When you say "SQL Server stage" I presume you mean "SQL Server Enterprise stage"? Are you selecting from the same table that you are updating?

... and don't try to boil water in a toaster or cook bread in a kettle!

Search the forum. This has been asked and answered many times.

The current case is, of course, marked as a server job, but the input from VCinDSX may yet prove valuable.

If the abort was raised in a stage chances are that your after-job subroutine never even got executed. Certainly it's not the culprit, and therefore you don't have an "after job routine issue".

"Replace existing rows completely" performs a DELETE then an INSERT on each row processed. It does not clear the table.

In MVS edition you don't really have an alternative, unless you want to create a routine to delete all rows from the table.

It only exists in server jobs or DataStage BASIC.

If the metadata are different for each file create ten separate jobs to do the validation. Take OK triggers from each job activity into a Sequencer set to fire only if All of its inputs have fired. Make sure there is an alternative exit from the job sequence, for example non-OK triggers or automatic...

Insert a Sample stage with a Skip of 30000000.

You also get one process per player (operator). How many stages are in these jobs? Can you be sure no-one else is also running jobs on this server? How can you be sure?

From memory it's a lot more. I think pricing is available on their web site.