DSXchange

Fork join with one path through Aggregator to get the counts.
Capture any row with a count >= 2 using a Filter or Transformer stage. These are your duplicates.
Another link captures either all rows or only those with count = 1, depending on your requirements.

The detail records are a straightforward join with the header records, which can also be created with a Join. One arm of that join can be driven by a Row Generator that creates rows like
AA,001
BB,002
CC,003
for as many as necessary.

You can verify in the job log ("job starting" event) which parameter values were passed to the job.

Question: Sunil, are you marketing yourself as a DataStage practitioner? The technique here is "vertical pivot". Details may be found if you Search DSXchange. If you want folks to provide complete solutions, chances are that they'll want to be paid. Because they, not you, will have done th...

Have you checked their website? Education is typically under the services menu.

Search DSXchange for "failed to load". Discover the usual reasons that shared libraries fail to be found or fail to load. Work out which one is affecting you.

Upgrade to version 8.5, in which looping within the Transformer stage is possible.

The bad news is that version 8.5 has not yet been released.

Yes. The easiest way is to refer to the $JobStatus activity variable downstream of the Job activity in a sequence. Otherwise you can create a routine using the DataStage API and calling DSGetJobInfo() to obtain the required information. You will, in this case, need to have attached the job to the ro...

Check out the "MD" conversions for Iconv() and Oconv() in the DataStage BASIC manual. They can manage these kinds of conversion, though I might observe that having a "-" inside angle brackets is very unusual.

This message usually means that the token has been previously defined, perhaps in a different header file. You need either to search very carefully or to generate a cross reference listing when compiling.

Mail usually ends up in dead.letter when it fails to be delivered. Check your recipient address.

DataStage is not able to open the connection. Please double-check all of the connection parameters. Check too that a different client (or even the DS.CONNECT utility) can or cannot connect.

Why did you mark the job type as Server ?

Code 40019 is "write failure". Check permissions within your project directory, in particular to the DS_JOBOBJECTS directory and the files within it.

You could adapt Kim's script to choose the format statement based on a command line argument's value.

Multiple versions are provided because different customers use different versions of DB2. The symbolic link points to the appropriate one.