DSXchange

That is not the error. It is merely an alert and ought not to prevent compilation.

Please post the entire error message.

Change your "real" dot to something else, such as ~; effect the removal, then convert all tilde characters back to dots.

There are no changes in functions. Only new functions.

Everything in 7.5 will work in 8.0, according to everything we've had from IBM.

Depends which five. You have to build that intelligence in to your code.

No script is required. In the job activity there is a drop-down list with the caption "Execution action". Open this list and you will see the option that I mentioned earlier. Behind the scenes, or if you want to do it yourself, all of the functionality is in a single function call, DSPrepareJob(). T...

Not true (about limiting to sequential). You can build in as much parallelism as you desire, and you can start parallel jobs from a batch or a job control routine.

After all, a job sequence is only a GUI that generates a job control routine.

Interesting question. I wonder what the demand would be.

Yes it's a big task. Big, not difficult, just tedious. You can get MetaStage to do it automatically, but at a (monetary) price. At least it would be properly licensed. Apart from that, the API is there and documented, and you can examine the source code of ETLStats to see how one person has done it.

Time dimension table with multiple-row return enabled from the lookup, or via an inner join on the year-and-month.


Tip: "Numeric date" fields yyyymmdd and yyyymm are very useful in time dimensions.

It's entirely appropriate to server (on UNIX).

I prefer to use a Routine activity as a sink, so as to log an entry reporting that the job sequence reached that point.

You could use UtilityMessageToLog as the routine. I don't, because it returns 1 - I use a clone of it that always returns 0.

If you can't change the job then you are going to have to use something that polls the jobs and gets their row counts.

Take a look at ETLStats from Kim Duke. That will do most, if not all, of what you need.

Welcome aboard. :D

In the job activities in your job sequence, change the run rule from "Run" to "Reset if required, then Run". Then re-compile the job sequence.

That is the easiest way to automatically reset aborted jobs that are run from a job sequence.

By planning ahead, and having had all 100 jobs write their counts into the table.

Or by retro-fitting the above solution.

Typically that is ALL that a factless fact table contains. A set of foreign keys to dimensions; the combination of those foreign keys effectively forms the primary key of the fact table. A factless fact table records that some combination of dimension values occurred. There are no measures. For exam...