DSXchange

The "NuTCRACKER" failure is a strange one, it would seem that you have installed MKS Toolkit on your client machine as well. Did you re-install the clients?

It is impossible to guarantee that there will be no impact, but the "." (dot) releases of DataStage are generally backward compatible; so you should see no issues or problems when upgrading from 7.5.1a to 7.5.3

It might sound like the old Doctor adage "take 2 aspirin and call me in the morning", but try re-installing the client software. This will force overwrite the .dlls and other files that might have been overwritten by other applications.

Normally all you need it conectivity between your windows machine and the DataStage server machine, if a firewall is involved you will need to open up ports but normally if the machines can see each other all you need to do is install the correct client version and enter the server name, userid and ...

Most likely this path is in the parameters and is defaulted incorrectly when scheduled.

did you try to connect to "servername:9080"?

I concur with lstsaur; the UNIX installation guides are more like rough guidelines and they assume that the installer understands the commands used and their implications. You will almost always get some sort of error or message and realize "Oh, I did that as root, I will need to chmod and chown tho...

This warning should disappear when you code an explicit null handling into the transform or modify stage. Are you certain the warning did not go away when you tried this?

The same key using the same hashing algorithm with the same APT_CONFIG file will go to the same partition number on both files.

Ray,

that is why I stated "generally"; but since the lookup that the OP is referring to is unclear I didn't want to confuse the issue.

That error message doesn't help much, it is like getting a windows popup stating "Your job has aborted.". What other information and error messages or warnings do you get? Does this abort right away or after a while? Does it happen each and every run in the same way? What has changed in the system b...

I am not sure what "V LOOKUP" means, but generally lookups are case sensitive.

In Server jobs the dates/timestamps are strings, so a "LEFT(In.TimestampCol,10)" or "In.TimestampCol[1,10]" will do this for you.

Your design has a join with only one input, that was probably an oversight. The "tsort" files are from that stage.

If you change your query to "select CUSTOMERMETER_WID from MLSDWPROD.PB_MWEB_CUST_METER_D" with just one column defined and do a "view data" does it work?