DSXchange

I have explained the technique in the past on DSXchange. If there's enough interest, I could reprise that explanation.

Does the four join query work executed from some client other than DataStage? How long does it take to return any rows?

What is the stage type downstream of the ODBC Connector stage in your job?

(1) Enclose the argument in the call in parentheses, or
(2) In the routine copy the argument variable into a local variable and assign only to the local variable.

I would not expect any output from this command and therefore would not be worried about the logged event.

Compare your script with the one supplied with DataStage, to determine whether there are any differences.

(What did you use for the email server name and sender and recipient addresses?)

SharePoint's security model can be, shall we say, awkward?

Theoretically, within DataStage there is no limit. Practically, of course, there will be, not least because the joins are performed pairwise left-to-right and the intermediate result sets have to be stored somewhere. If you're relying on inserted tsort operators, then you must also factor in the tot...

I would have expected to see modulus 2 (rather than modulus 1) in the WHERE clause. Modulus 1 can only ever be 0. This looks like a bug.

Sequences generate DataStage BASIC code, not osh script. A sequence is a special case of a server job. Now to your actual question. The internal identifier numbers simply specify the order in which the objects were created. In dev, VIdent1 was created before Ident2. In prod, purely because of the or...

Each partition is sorted separately. That's why you need to partition the data based on at least the first sort key, to get correct results. A Sort Merge collector will preserve sorted order without the need to re-sort. But do you really need to present the entire set sorted in a single partition? O...

Welcome aboard.

The usual solution is to record the creation and modification date/time in each record.

Retrieving them then becomes a simple WHERE clause.

It is, but it's neither maximally efficient nor maximally flexible.

Separately.