DSXchange

First and obvious question - what's different about the dev environment that it works there and not in the other environments? That you have a zero length string (presumably in a VarChar column) is almost certainly the sourced of your problems. Is this supposed to represent NULL? If you go the fixed...

What happens if your expression is ( A / 30.0 ) * B ?

collabxchange wrote:I need the surrogate key to be generated sequentially

Why?

A surrogate key guarantees uniqueness - nothing else. A bigger block size would be my main recommendation.

What it really should have said was "too many right parentheses".

This is cool. Must keep an eye on your blog page. Or maybe you just change your DSXchange signature when a new blog appears!

Craig only speaks 'murrican.

Because the file contains accented characters, it cannot be plain ASCII, it must be encoded somehow. Perhaps it is encoded using ISO-8859-1, perhaps using a different encoding. You also need to ascertain what the mapping used in the DB2 table is, for the same reason.

How is the file encoded, and what NLS map are you using in the DataStage job? The two need to be compatible, if not identical.

Have you changed the memory offsets used by DataStage engine?

What Craig is trying to say is that the entry in the value file should be of the form First line is column names should be False.

Legally, no.

The DataStage BASIC encryption algorithm can be found if one searches hard enough. However there is no guarantee that the same algorithm will be used in future versions.

Use status view in Director, disable display of Categories, and sort by Status.
Aborted will sort to the top of the list.

From memory (not in a position to check at the moment), the command may also provide this value.

Generate the parameter value in the Job activity using an expression, for example

You missed the quoted comma as the second argument of the Field() function.