DSXchange

Are you sure it's a VARCHAR not a CHAR in the database? If it were CHAR then the database itself might pad with space characters.

How about being just slightly more specific with your mask? "0N'.'0N1A0N" in conjunction with the MatchField() function should work with a full (five piece) scientific notation number. If the number is 1.234e10 then: MatchField(InLink.TheNumber, "0N'.'0N1A0N",1) returns "1&q...

You asked it to preserve blanks and it did so. What's the problem?

Upgrade to the current version and use a range lookup.

Otherwise do a sparse lookup as indicated, looking for the largest date smaller than your lookup date for that particular key value.

You can use orchadmin to dump the records and a redirection operator ( > )to write them into a file.

Have you specified one or more sort keys in the Funnel stage? That is, columns that have to have their sorted order preserved? Note too that the funnel stage does not sort - it expects the data to be correctly sorted (and partitioned) on all inputs.

Welcome aboard. This is not new. You can only load environment variables as job parameters if those environment variables are defined at project level. There may be one exception to this, if the special token $ENV is used as the default value. In this case, you are instructing DataStage to seek the ...

Ah. Consultant, derived from "con" and "insult".

It's always a compromise. Data Sets don't need to invoke import operator; they work with copy. I believe Lookup File Sets do need the overhead of import (for the data, not the index). So, with Data Sets you need to build the index, with Lookup File Sets you have to translate the data. Arnd's results...

Sorry, that was a misdirection (from a different product). In 8.7 I have no issue displaying the debug bar.

Seems to me that column1 is defined as not nullable and you've used an IsNull() function on it. DataStage has objected to this.

Have you compiled in debug mode?

When you use a Lookup stage the reference input is loaded into memory and an index is created on its defined key on the fly. Except that, if a Lookup File Set is used, it has the index created within its structure at the time that it is created/populated. That means that the cost of creating the ind...

I believe that, if environment variable DSHOME is set, the scripts prefer that value to anything specified in /.dshome.

That said, I also believe that IBM explicitly forbids any other 8.x version being installed alongside 8.5.

The job isn't actually getting to start, so there's no surprise that there are no target transactions. Is your (DataStage engine) system too heavily loaded?