DSXchange

Why are you reading DSParams? If the environment variable is set, you can simply obtain its value from the environment!

Or you can write the same C code in a Build stage, which is my original suggestion.

Has your licence expired? If not, it appears that the server installation has become corrupted, and you may need to re-install.

The "replace existing rows completely" option deletes the row whose key is supplied from DataStage then inserts a new row with this key.

At row #1 it's unlikely to be a space issue. Code -100 is often used to signal "end of data". Are you trying to sort an empty file?

Not in a server job you haven't!

What is this fascination that people have developed with having jobs abort? Never design to abort, say I.

Permissions on $DSHOME/bin/uv are incorrect. Not only must this (and a number of other executables) be owned by root, they must have the setuid bit set. There is a script in the scripts directory for resetting the permissions, or you can involve your support provider. You should also track down whom...

Note also that there is no single UTF-8 encoding. Unicode may be encoded in any eight-bit strategy; there are several around. That is, there are many variations on UTF-8 (Unicode Transformation Format, eight bit); you may be using incompatible ones. You have not even specified what NLS maps you are ...

If that's true you've discovered a bug in the parallel function, which you should report to your support provider.

You need to recompile the job in the new environment. You will have to recompile again when you move to version 8.0.

Nothing difficult really. Simply export as an IMF file and import on the other server. The same requirements to deploy jobs before running still apply.

Don't do it that way at all. Use a Wait For File activity in a job sequence. You can have one output from this when the file exists (or comes into existence within the required time period) that then executes your job. You have another output that is taken when the timeout expires without the file a...

Ignoring the TX job type for the moment, the language resource file is either DS_RESENU or DS_RESJPN, a hashed file containing decodes for encoded text strings generated within DataStage. It may be that the hashed file could not be created (permissions?) or that the data source file from which to lo...