DSXchange

No even without an experiment. Key-based partitioning is driven by VALUES in the data fields, not the names of the data fields. Non-key partitioning is driven simply by the order of rows in the data - again not the name(s) of anything.

There is not enough information to answer the question. How many nodes are in your configuration file? What partitioning algorithms are used on each link in your job design? Do all nine source records have a matching key in the reference data?

Only by taking the class, I'm afraid.

Maybe, in future, it will be made available through DSXchange Learning Center, but those arrangements are not yet in place.

I believe U would prefer to use DataStage BASIC, since U is currently working at a server-only shop in Singapore (or was, last time I looked).

Good. Your point #2 remains incorrect. 2. When the Job is aborted and the abort condition is handled in the Trigger section, the check point is added. No it isn't. Only non-failure completion will add a checkpoint. That is why, if all activities complete successfully, you get an event logged indicat...

... and Arnd is asking you to PROVIDE that clear understanding of each step, since you are advocating this approach.

You might also like to educate him about whatever it is you mean by "internal implication".

The "MC0X" conversion returns the code for each byte as two hexadecimal digits. For example "A" (whose ASCII code is 65) will be converted to "41".

I think you've now hijacked the thread - your current rumination has nothing to do with the topic of the thread "best way to abort a job".

Not at all. AGE might be an integer, but - for a person - you'd expect to reject negative values and "too large" values (over 120, say).

There are many environment variables that affect these behaviours. I do not propose to canvass them all here. They are to be found in the manuals, in IBM's Advanced DataStage class, or in my Advanced Parallel Job Techniques class.

Customized VEMAIL, as noted in your other thread.

The Soundex and NYSIIS functions are available to you, though you may (will) need to customize the Pattern Action Language (PAL) for the Rule Set.

Maybe someone has already done that and will post here in the near future.

MetaStage, ETLStats or by writing your own equivalent. The inbuilt reporting utilities operate at one level only.

That is so totally wrong, ag_ram.

A checkpoint is only added if the activity completes successfully, and then only if "do not checkpoint run" is cleared for that activity.

It is the presence of a checkpoint that allows an activity to be skipped on re-start.

You are the only one who thinks it is strange.

If I have to leave my desk to deal with some other emergency, and my session to the database times out (or even if I just switch off my client), any uncommitted transaction will (eventually, in some cases) be rolled back.