DSXchange

Split the data into two streams, one where the value is "ABC", the other where it isn't. Process the two streams appropriately. If necessary (and only if necessary) bring the two streams back together using a Funnel stage.

I think this is entirely within the client. Can you reproduce the problem from a different Designer client (that is, one on a different machine)?

I've seen it with shared containers, even before version 8. I imagine that something similar happens with connectors - only one person can have it open at a time. The compiled job, on the other hand, uses a reference to the shared container (or connector) so that as many jobs as need to use the logi...

This is fixed-width data. The field width is 12. Therefore the implied data type is Char(12). Whatever you specify to represent null in this field must contain exactly 12 characters. In the Columns grid of the Sequential File stage scroll right until you find NULL Value and supply values there that ...

Only by rewriting dsjob. Source code is in the Developer's manuals.

Would that be 2008, 2009 and 2010 then?

Command output probably has linefeed(s). You need to convert these to "" in addition to anything else you want to do.

In which column in the Columns grid did you specify the 150? This error usually arises from having a VarChar column with its Precision left empty.

Even easier, when you have this page open in Designer, click on the Help button. Then click on the check boxes in the help screen and all will be revealed!

They've put a lot of work into DataStage help over the years, it's only right that we should use it from time to time.

I'd prefer to use a master sequence rather than a script to do this.

Add an Exception Handler and Terminator to your job sequence. The Terminator will look after issuing the stop requests.

(Slightly off topic)
Sequential File stage can run in parallel, except under very specific circumstances. These include writing to one file and reading from one file with number of readers per node set to 1.

According to IBM the only versions supported for XMETA are DB2 version 9, Oracle version 10g or Microsoft SQL Server 2003.

Looks like you're getting the individual partition (instance) row counts via DSJ.INSTROWCOUNT - which returns a delimited list of row counts. If you just want the total rows across all partitions, prefer DSJ.LINKROWCOUNT as the fourth argument to DSGetLinkInfo().