DSXchange

I have it running against 'DB2 v9.5.400.576' here if that is any help.

Are either your database or DataStage using a locale which might use ',' as the decimal delimiter?

pingu - this is a global forum, it would help if you were to specify exactly where you are. The market in the UK is weak(ish) but picking up, Australia seems to be actively looking for people again, Germany and France are going strong and desperately looking for consultants. I haven't been following...

Perhaps the character is being translated incorrectly from DB2 to DataStage. Isolate the characte and use the SEQ() function to determine which ASCII value arrives in DataStage.

Are you certain that the config file you posted is what is actually being used (check the 2nd entry in the director log for the run to confirm), since the dpr_aos_dev directory is not contained in the config file EBI_TwoNode.apt.

What stage is node_db2node3 that is triggering the warning?

I have to admit that I can't recall what I did (after all, it was 6 years ago and a couple of projects ago). Things have probably changed at Version 8 in any case. I don't have a DB2 to check against here, but I would be surprised if it were a limitation. If you simply read with DB2 partitioning and...

How many clients do you have licenses for - and do you come close to that amount? Is the network stable? (as you can see, I have no idea what the cause might be, I'm just rooting around)

Hashed files don't suffer from fragmentation in that manner; but the default settings of 20% merge 80% split can cause overhead if you go past those limits. The hashed file uses a hashing algorithm on the key to decide into which group a record is placed, the number of groups is also seen as the MOD...

While pure inserts are more efficient than delete/update on an existing table, the performance difference on a well hashed file (dynamic files are well-hashed) isn't great.

Umm, you mean when the scheduled job tries to run? If so, please post the complete message. Or do you mean when you try to add a job to the scheduler?

Just in case Craig left any doubts open - never use kill -9.

Your DB2 stage needs to reflect the character set that the data is stored in the database, after that stage, i.e. when writing output, you can revert to your project's preferred NLS settings.

What is your server hardware platform? Also, does this occur with just designer sessions or also with director windows?

I can think of no project-level method of doing this; you will get a generic warning stating that truncation may occur, but without explicitly coding for truncation you won't get the warnings the way you would like.

Is the DB2 database partitioned and, if so, are you using the DB2 partitioning in your database and subsequent stages?