DSXchange

In neither case will the Remove Duplicates have any tsort operator included, because there is an explicit sort on the input link (in this case a Sort stage).

Partitioning and sorting are separate from each other.

In the controlling sequence you can use Date() always uses the current date. If you prefer, use system variable @DATE instead, which is set to the job start date.

Welcome aboard. You can't do that in a single job. You need one job to read and store the value (perhaps in its user status area) and the controlling sequence can pass the value to a job parameter in the second job. The Sequential File stage's File property is set to a reference to that job parameter.

As you provided it the DELETE would delete all categories. Presumably there was a later command to synchronize the project from the common metadata repository.

Generate a constant that identifies one source as "A" and the other as "B". This will be used downstream to indicate which output column to populate in the Transformer stage.

A Column Generator stage would be ideal for this purpose.

You can only choose which sort process to use by placing an explicit Sort stage on the input links to the Join stage.

You are correct that DataStage will insert a tsort operator by default if you have not otherwise specified sorting on the input links.

You may have Unicode/UTF-8 enable in Sybase, which is why it is reporting a size of 4 for this field.

It's still a join. Between source and join generate a column that identifies the source. Perform the join. Downstream of the join use a Transformer stage to generate two output links, and bring those together using a Funnel stage.

(Auto) is guaranteed always to work (to deliver correct results, all else being equal).

(Auto) is not guaranteed to be optimally efficient in all cases. This is where someone with some knowledge can get a job to perform better (finish faster).

(Auto) uses hash partitioning on stages that designate Keys except as follows. (Auto) uses DB2 partitioning for DB2 Connector stage. (Auto) uses Entire partitioning for reference input to Lookup stage. (Auto) uses Same partitioning for adjacent stages executing in parallel using the same node pool. ...

Almost certainly this is an issue of running out of memory on the client.

For a Join stage DataStage will always (under (Auto)) use hash partitioning on the Join Keys, and sort on the Join keys unless there is sorting specified either on, or immediately upstream on, the input link. It may be more efficient to partition on the leading subset of the Join Keys, but this inte...

Because there is no trailing semi-colon, the SELECT verb is being used to generate a Select List (an in-memory list of key values that will be consumed by the next command). Backslash is a quote character. Three dots is a wildcard. Ordinarily the SELECT verb requires WITH to introduce a filter phras...

adityavarma's entry shows as premium member. I would expect manteena's to be processed shortly, given that the administrators have just had the Thanksgiving holiday.