DSXchange

Multiply by -1 is definitely the easiest approach.

"Pre-defined" means that the values defined within the Parameter Set will be used. The only alternatives are the name of a values file defined for the Parameter Set, which will provide a potentially different set of values for the parameters in the Parameter Set. To troubleshoot the failur...

With ISM yes (as Vincent advised), without ISM no (unless you want a "do it yourself" approach exporting components and using the export files as the "source code" that is managed by ClearCase).

Welcome aboard.

Have you enabled the option in the Lookup stage that allows multiple rows to be returned from the reference input link?

In an ideal world, surrogate keys and measures.

That "cascading delete" does not look like an ETL task to me.

Hopefully they're monitoring this forum but, just in case, why not email editor and membership director again?

ODBC tends to prefer dates in YYYY-MM-DD format. Try reformatting the dates.

A DataStage macro can only be run from within a job.

However you can do this with a routine, using DataStage API calls (specifically DSAttachJob(), DSGetJobInfo() and DSDetachJob() functions), but you'd need to do this before starting the job itself.

You might also contemplate what you want to do if there are nulls in the data.

That's the point - you don't have to. However I am sure you could devise logic to add a field to the link that updates the dimension table if you really wanted to - or to a copy of that stream.

Welcome aboard.

How are you partitioning your data?

It does look like an Aggregator, in particular an Aggregator using Hash method for grouping. The problem is in the code that performs that little task, and can only be solved through your official support provider since IBM, for some strange reason ( ), do not release the source code.

Good point. The joys of copy-and-paste. It will work as a string, but require an unnecessary data type conversion. Better is: (NullToEmpty(Column_1)='0004400') And (NullToEmpty(column_2)='1221') And (Index(NullToEmpty(column_3),"NOG",1) <> 0) And even better is: (NullToEmpty(Column_1)='000...

You're correct - the only undesirable consequence is wasted space. Hashed files with either "bittage" will work fine - the hashing algorithm works in exactly the same way. All else being equal, though, a 64-bit hashed file will have slightly more groups than a 32-bit, because there is less...