DSXchange

I prefer "INT(In.NumberColumn/1000)*1000" to get 3 decimal positions.

asaf_arbely - he already did explain it. Go to the director and job view, then select the menu item Job -> Clear Log and in that menu you can override the Auto-Purge settings as you require.

How do you know that this isn't working? I suggest you read the data and then write it to another sequential file and compare the two. Note that the "view data" in the designer should never be used to check NLS data.

There is a Java transform stage which can be used to invoke java code.

I recommend using the NullToValue(), that way you only have to program one condition per column.

"resize" is a UNIX command, this is being used and won't work. If I recall correctly, the syntax of the $DSHOME/bin/resize command isn't documented, so you should stick to the DS shell (i.e. ADMIN tool) command "RESIZE {HashefileNAME} * * * 64BIT"

Does the error happen right at the start or after the job runs a while?

Can you do a DB2 CONNECT to the same DB2 instance from the command line? The error indicates that the environment cannot be reached.

It should be "* * *" and not "***"

DataStage will perform an implicit conversion, but it is much better to perform the conversion yourself explicitly, i.e. by convertig your decimal to an integer and then doing your join.

The Char() function lets you input an ASCII value and the function returns that character. Thus, "Char(9)" would give you a TAB character.

aninashh - this is now the 3rd thread you have posted the same problem! Please keep to one thread, and keep this one closed.

Having 2 distinct threads with the same problem is not good, plus you should have seen what happens when posters state that their problem is "urgent", that usually results in getting a slower response than wuold normally have happened. You need to post your error messages as well as the co...

Please cut-and-paste your complete error and post it here.

10Kb record size is not a problem for DataStage, each record can theoretically grow to close to the size of virtual memory space for that user. 1000 columns, while large and potentially inefficient, is not a problem, either.