DSXchange

I will limit my explanation of that expression to two simple points; it's woefully cumbersome (compare the other suggestions) and it's wrong (which was also already pointed out - it removes all zeroes, including any within the number).

DataStage 390 was renamed DataStage EE MVS and was then renamed IBM Websphere DataStage EE MVS Edition

One physical machine but two separate machines as far as the rest of the world is concerned. Don't really understand the need for two copies of the same version either - using multiple projects would seem to do it for me. Maybe they want one with NLS and one without?

If you initialize a stage variable it doesn't actually need a derivation. If there is no derivation, the initial value remains accessible.

Then you need and If..Then..Else, with one branch handling IsNull(column)

They're not "trash" - they're messages (metadata) indicating that the column is not indexed.
And it's probably that you have not created all the hashed files you need in the new environment.
Back to you.

It's probably the MKS Toolkit telnet that's occupying port number 23. This starts before the DataStage Telnet Service. Change the DataStage Telnet Service to Manual, and just don't start it. You can get there via the MKS Toolkit telnet if you need to. Alternately, cripple the MKS Toolkit telnet, the...

The default maximum column retrievable by the ODBC stage is 400, so that's not the problem. This can be increased by MAXFETCHCOLS in the uvodbc.config file. Are you using generated SQL or user-defined SQL in the ODBC stage? Are there 58 columns defined on the Columns grid? Do all the data types matc...

Please be more specific about what you mean by "performance". Hashed files (note, not "hash" files) are the fastest possible mechanism for performing a key-based lookup, particularly if cached in memory.

If the condition is a value, use a Switch stage. If the condition must be an expression (akin to a WHERE clause in SQL) use a Filter stage.

If you have days and months with arbitrarily one or two digits, then Left(x,10) may not be a reliable function to use. Get that piece right (or just lose it is probably OK) then try again with the remainder.

I believe Pavan originally stated that an awk script he wrote was slow and that awk was too slow and that he wanted to code this in Datastage because it is faster? No, I've re-read the original post. He only asked whether it is possible in DataStage. He did claim that awk was too slow, but made no ...

You can also click the Verify button in the Configuration File editor (found under the Tools menu in Manager).

Try logging in with fully qualified names, for example Machine1\Bob.

As many as you like. You can create configuration files for one processing node (for small jobs) through to 16 or even more processing nodes (for large jobs). Depending on how your file systems are laid out, you can specify disk and scratch disk resources to spread the I/O around as much as possible...