DSXchange

Look up a list of UNIX signals to find out what signal 15 is (a mnemonic beginning with SIG but appropriate searching will find an explanation as well). This will probably help you to resolve what the particular issue is.

1. The hang is awaiting a "go ahead" to be able to write to the log, which it's never going to get if the log is corrupt. (It is.)

2. Clearing the log is one way to clear the corruption.

Yes you can do that also. It uses the same functions under the covers.

In DSParams check RTLogging versus ORLogging.

Why not simply use a Surrogate Key Generator stage, in which you can set the block size property? This stage can access your database sequence, or it can use a state file that you can initialize from the database.

That's not a file, that's a command.

What is mtt (a project or job name, perhaps a script)?

An aborted job can't reset itself either, because it's aborted (no longer executing). And, if it's not aborted, why do you want to reset it?

If you're not going to use a sequence then you need a separate job, perhaps one that contains only job control code.

dsrules wrote:Requirement is not to use sequencers.

Resist stupid requirements.

In any case, a sequencer would not help. A sequence may, however.

Resist stupid requirements.

Has the Lookup Failed rule changed between the two jobs?

DataStage does not perform implicit conversion from string to date (because not every string can be guaranteed to be a valid date). Make sure, before entering the Change Capture stage, that the data types are compatible on the two inputs.

This might be urgent, if the interview is soon.

dsjob -jobinfo commands through Execute Command activities will capture the information - you will have to parse it.

Or you could use a routine invoking DSGetJobInfo() calls, invoked via Routine activity.

Probably not enough time to do that before the interview.

SGE is a TLA

Not sure how it is used with IIS (another TLA from IBM) - I have not encountered it. SGM is Sun grid manager, if that helps.