DSXchange

Are you trying to replace 8.1 with 8.7, or install them side by side?

If the former, delete MKS Toolkit and allow the install program to install the correct version.

Indeed, you may need to do this in the latter case too, and hope that 8.1 can work properly with the newer version of MKS Toolkit.

Is there an alias for this host somewhere in your repository?

You can export in XML format, edit the XML, and import (overwriting).

Do clear the log. It's just good practice to do so. However, the hashed file that has become corrupted is RT_STATUS1, not RT_LOG1. If you have administrative tools enabled in Director client, you can clear the job's status information from there. If you do not have these tools enabled, then execute ...

Welcome aboard.

Somewhere, on (at least) one of your links, there is a column defined as VarChar, with Unicode set, without a value for its Precision (maximum length). You have to find this.

You might try setting the environment variable OSH_SHOW_SCHEMAS as part of your investigation.

You might also consider reducing the 50+ non-key columns to one using a Column Output stage, which generates a delimited string. You should then be easily able to compare those delimited strings to fulfil your requirement.

Where do you get the column names (name, address) from in your design?

In addition to the responses Vincent posted, you can also form a list for multiple edit by using the Drafts folder (one of the three folders in the governance area, the others being Pending Approval and Approved). I sometimes find this the easiest place to effect bulk edits.

Dynamic array structures are natively supported in server jobs. I'd recommend looking at using an approach based on server jobs.

It's not required, but it IS recommended. It's a safety measure, to make sure that no job could possibly be attempting to write to a Data Set while Data Sets are being deleted.

If you're getting DSJE_BADPROJECT in the dsjob command, it is either that you are not specifying the project name correctly (it is case sensitive), or (less likely, since you can compile jobs) your project or engine installation has been damaged.

All DataStage command line executables are well-formed, in that they generate an exit status of 0 if successful, and a non-zero exit status otherwise.

The exit status can be captured through the shell variable $? if on UNIX or %ERRORLEVEL% if on Windows.

Why are you using different delimiter characters in the DCount() and Field() functions?

Have you tried using multiple readers?

The functionality is there, including in version 11.5. In the Columns grid (in the bottom right quadrant of the Transformer stage, or in the downstream Sequential File stage), select the Column name and then use your right mouse button to drag a column (up or down) to its new position. You can also ...