DSXchange

You can't. Blank is not a legal value for decimal and integer data types.

You might try changing the data type to Char.

Provide a sufficiently large precision value for the Decimal data type.

Check and double check the user name/password combination specified in the Connector or its associated Data Connection.

Thank you for posting the solution. I was thinking along the same lines while reading the original problem (did not "do" DSXchange over the weekend).

Do you get three rows into the Transformer stage?

What would you expect the result to be?

The correct test for a failed lookup would be IsNull(col2).

That's not the URL for version 8.7 (though it was for earlier versions).

Try http://machinename:9080/ibm/iis/console

Actually it's neither of the things you envisage. Was this job exported from a system on which NLS is enabled and imported to this system on which NLS is not enabled? The request for the NLS locale setting has come with the job, but the locale is not available on a system on which NLS is not install...

Have you started ASB Node Agent and Logging Agent?

You could write your own Job Control routine. This is the old-fashioned way, and requires some skill with DataStage BASIC code, but may solve your particular problem.

By far the easiest way to accomplish this task is to use "text formatting", to do which you need to use the Fmt() function in a BASIC Transformer stage (or in a server job). The derivation expression is Field(Fmt(InLink.TheString,"40T"),@TM,1,1) The Fmt() function with "T&qu...

Stable sort does require rather more memory. Do you really need a stable sort? That is, is it really part of your requirement that the original order of records is preserved for each value of sort key? In my experience it rarely is. So I'd first look at disabling stable sort. I'd also look at cleani...

The solution is to have your metadata match what's really out there.

I always do, so I've never encountered that particular message.

DataStage issues the alert when any difference occurs in the map name; it is not the responsibility of DataStage to be aware that one map name is an alias for another one.

The error message indicates that you (the user name under which connection is made) do not have write permission to the hashed file.

DS_CONNECT is executed within the dssh environment, possibly from the Administrator client Command window, possibly by logging in on the engine machine. DS_CONNECT <<DSN>> You are prompted for a user name and password for the data source, and then connection succeeds or fails. If connection succeeds...