DSXchange

Certainly there is, but it involves you writing your own encryption and decryption routines.

There is nothing available "out of the box" as far as I am aware.

Use a fork join design, with one stream going through an Aggregator that calculates the maximum value of Col2 in each Col1 group.

Make sure to hash partition on Col1.

My bad, then. Another User Variables stage weirdness - I don't think there's anywhere else the sharp signs are needed within an expression.

We still don't know whether it was a connection to Information Server database, to Information Analyzer database or to the DataStage project ANALYZERPROJECT. It's annoying, that is.

... but without the sharp signs

What results did you get when you performed your Search?

The dsenv file only sets environment variables. It does not create connections.

DataStage will insert hash partitioner and tsort operators for Join, Merge and certain other stage types, if (Auto) is selected and insertion is not prevented, and if there is no sorting specified on those input links . It doesn't matter that the data have already been sorted upstream; the stage its...

Try bin/dssh instead. Also verify that $DSHOME/errlog is writable.

Get yourself a copy of UltraEdit - it has the FTP capability built-in.

Mount points are not really relevant. The most important factor is that scratch disk is local to the node, and that there's plenty of it. The same is true to a lesser extent of resource disk; how much of that you need depends on to what degree you make use of persistent Data Sets, File Sets and Look...

Be very, very careful. Any of these might be a running job. Verify whether each has a PPID (parent process ID) - for a section leader process that would be the conductor process (if on the same machine) or the remote shell that it invoked.

In particular has any change been made to the DSParams file in the project?

You shouldn't need to re-start, but it won't hurt to do so.

dssh can be run satisfactorily in any project directory, as well as in $DSHOME - each project directory is an "account" for dssh. But it is vital that the dsenv script has been executed first - that's why (I believe) advice is usually given to execute in $DSHOME, the location of the dsenv...