DSXchange

Join data must be sorted on the join key(s). If the data isn't sorted, DataStage will put in a tsort operator unless you explicitly turn this off using an environment parameter such as $APT_NO_SORT_INSERTION.

Why not use an inner join in a join stage or a lookup stage (choose either link as a master) and have both Col2's go to the output?

If the NLS is greyed out then you haven't installed DataStage with NLS. If all you want to do is move the data, then you don't need NLS and can just write out the data. It might not display (with "view data") correctly but will work without any problems.

Craig - I would be surprised if the installation is an NLS one from the type of post (the language quoted was German)

This is not a small change, but a very fundamental one. If you look at your online documentation you will see a National Language Support Guide which should get you started.

Yes you can process this data. DataStage supports Multibyte and NLS. Even without NLS enabled the LATIN-1 characters can be processed.

And your output is declared as Char(8) or Varchar(8), right? You can demote the warning mesage to informational, or declare the column as decimal or integer and in a later change convert from numeric to string.

What is the COBOL copybook definition for that column?

Have you hashed on all 3 keys in all of the links, i.e in the second and third joins?

It shouldn't be caused by too many stages. Can you do a "save as" with another name of the changed job?

Each project has a DSParams file in it's main directory.

I am reading the Excel file which is in Datastage server(Unix box)... As has been asked several times before - what format is this file in? If native Excel format then you cannot read it directly. You might be able to find a free ODBC UNIX driver (or buy ConnectDirect) and then use the ODBC connect...

What about when you remove the "WITH NONE" from the update statement - I haven't seen that used before.

It seems that at first it runs and then (once the workstation eats more memory) it suddenly displays incorrect icons. Perhaps closing such memory hogs as outlook.exe or iexplore.exe might help, or only opening one job at a time.

Can you take a sample record and manaully type in the custom sql from the command line to see if you get an error message?