DSXchange

SetNull() will only work if the target column is defined as Nullable. But SetNull() does not help in deciding whether the input column is null. SetNull() generates a representation of NULL (unknown value).

... and for a stage? Perhaps DSGetStageInfo() - I don't have access to DataStage at the moment, so can't be sure. Otherwise you can definitely get it using the DSGetLog... functions, seek out "active stage finishing" events. As a bonus, these events contain the link row counts for links connected to...

Read my previous post. You have at least one corrupted index on DS_STAGETYPES. The file D:/CAB_DW_PROD_10/I_DS_STAGETYPES/INDEX.001 (mentioned in the error message) is the first index defined for DS_STAGETYPES.

Rebuild at least the DS_STAGETYPES indexing.

Yes, but if you have DataStage 7.5x2, then you have UNIX on Windows (MKS Toolkit ships and installs with the product).

I've learned something today.

"" is not the same as NULL. This may be the root cause of your confusion. "" is a known value, NULL represents unknown value. So, if the value is "", then it is not null, and your logic behaves as you have described. If the data are coming from a file, rather than from a table, there will be a stage...

Welcome aboard. :D

This is not the first time this question has been asked, so it has been answered previously. Search the forum before posting questions; you will often get an answer faster than awaiting a reply.

Not so. The only difference for execution mode is that, for parallel mode, you must partition (and, ideally, sort) on all pivot key columns. For sequential mode, since all rows are in the same partition, this is not necessary, through sorting is still beneficial.

You can directly access Excel via ODBC. It's very easy on Windows platform. Search the forum for techniques.

Three hashed files.

The design canvas looks cleaner, and makes it more obvious what's happening. And you don't have to stuff around with artificial key columns and computing same.

Please read the chapter on Configuration Files in the Manager guide. This will aid your understanding, and give you examples.

I do not have access to DataStage until mid-May, so am unable to post any examples. Maybe someone else will post the default.apt file from a UNIX installation.

That's got the potential to be a major gotcha! Thanks for posting the solution. I wonder if the support analyst who solved it has any hair left?!

The hashed file needs only two columns (Account_Num and Account_ID), so it's not going to be that large even with a few million rows.

To counter, some databases expressly forbid cross joins (Cartesian products), or require you to change a setting in your environment.

You need to put Descartes before de horse.

Usually first line is column names is incompatible with fixed width format. Indeed, were you in a parallel job, the Sequential File stage would prohibit the combination. Please edit your post and check the Disable Smilies in this post option, so that 8) is not converted to a "cool" emoticon. You nee...