DSXchange

Use a connector with two input links and combine the two inputs into a single transaction within the stage. This can also be done with the older ODBC stage.

Use the (free) IBM Concierge service to help you to plan your upgrade. They will produce a checklist to make sure you don't miss anything.

Use this one.

When you import the table definition for the sequential file specify 001 (three digit decimal ASCII code) as the delimiter.

Use either of those stages. DataStage is simply another client as far as SQL Server is concerned, so you configure the client software or ODBC driver just as you would for any other client.

Your single node configuration lacks a default node pool name ("").

Welcome aboard. You don't have the required C++ compiler installed/licensed.

As Craig noted, you don't need to re-sort (unless you want to run the Aggregator stage in Sort mode). What IS important is that the data are partitioned using a key-based algorithm on the grouping column(s).

You didn't miss much, so I've unpremiumed it.

It does seem to be inaccessible at the moment. Wait for Kim to get back from vacation. Watch this space.

Have you tried re-compiling the sequence?

If your developers have followed recommended practice of using ".ds" as the suffix for Data Set descriptor files then, yes, the search is easy. Don't forget that the data files live elsewhere, so you must use orchadmin command to remove the Data Sets.

There is a function for this - something like GetEnvironment() or GetEnvVar() - but I'm recovering from NYE drinkies and can't recall exact details. It'll be in online help and the manuals somewhere.

You understood correctly. These files are not referred to by the software once installation/upgrade has been completed.

Is "PAR" really a hostname, or have you mis-spelled "RAP" in the one node configuration?