DSXchange

The input is a string type with no length (precision). The output is a VarChar with a length (precision) of 1. These do not match. Make them match.

A couple of possibilities.
1. Your data file has an empty last line. If so, get rid of it.
2. The "optional" fields (EIMPLDGX-MERCHANT-DESC-F and EIMPLDGX-MERCHANT-DESC) have been left off by whoever created the file. ("Don't see it being used.")

You should be able to generalize what I wrote earlier. You may need to loop through all the records for a particular key, sorted in flag order (descending) and date order (ascending). Other than that, the logic will be very similar. Why not attempt it?

The sequential file stage will execute on one node. Another alternative, if you need to preserve order, is to partition on, say, row number and sort on that before finishing with a sort-merge collector. Or you could execute your four node job but constrain the Transformer stage to executing in a sin...

So, if I read this right, the active record is passed through unchanged, and the inactive record is split into two, with the end date of one being the start date of the active record, and the start date of the other being the end date of the active record. Is this the correct reading? If so, sort by...

This is very odd. What happens if you re-index the project?

Developer9 wrote:Job (B) is in Runnable status all the time

That may not be true if people even just open it to look at it, and save it without re-compiling. And that, I suspect, may be part of (all of?) the problem.

Note also that the correct spelling is "apostrophe".

Yes.

Does Create_Dt come from source or is it being generated in your job?

In the former case use a Transformer or Modify stage, in the latter case use a Transformer or Column Generator stage.

Allegedly MKS Toolkit is no longer used by DataStage itself, but is retained for backwards compatibility. If you have any job, routine or command that relies on "UNIX", then you'll have to keep it. Otherwise, theoretically, you ought to be able to uninstall it. To be cautious, get confirma...

I, too, have done this in the past, and I'm sure at least the basic ideas exist on DSXchange. On another occasion I used the content of the system tables to create SELECT and INSERT statements "on the fly" for each table. And don't forget that Modify specifications can be completely parame...

HOW did you "try to delete the project"? If you try and take a cat apart to see how it works, the first thing you have on your hands is a non-working cat. -- Douglas Adams Have you cleaned up both the DataStage engine tables and the XMETA tables that refer to this project? Involve support....

Use a Column Generator stage between the SCD stage and the stage that performs the update.

DataStage uses prepared execution. That is, the SQL is sent to the database only once, to be "prepared" (run through query optimizer, etc.). This happens before any rows are processed, and throws metadata mismatch and other warnings/errors if necessary. As rows are processed, DataStage sen...

Or simply look in the RT_SCn directory in the project, without all those other steps.