DSXchange

U did not ask the question. U is one of our members. It's a Burmese name. The second person personal pronoun in English is spelled "you", not "u". Please use a professional standard of English on DSXchange, not least because "proper" English is hard enough for those who...

Corrupted repository? Have you used fixtool (or UVFIXFILE) in verify mode to look at DS_JOBS and DS_JOBOBJECTS tables? The string in your report is a DataStage-encrypted string. It does not belong in a File property.

No.

Standardize the format of your string (add leading zeroes to month and day) so that you only need one mask.

Search the forum for techniques.

The storage mechanism, which the OP stated does not exist, in fact does exist. It's a "state file" created (if needed), initialized and used by the Surrogate Key Generator stage and the GetSurrogateKey() function.

There are two different kinds of range lookup - one where the range is on the stream input, the other where the range is on the reference input. Be careful how you specify it.

My guess is that you've put a reference to an encrypted parameter into a filename field.

Parallel jobs do support before-job and after-job subroutines (which are executed by the Conductor process) but do not support before-stage or after-stage subroutines.

The before/after subroutines are server routines whose type is before/after subroutine.

Welcome aboard. This technique is called Vertical Pivot.

Search the forum for techniques - the main one uses Transformer stage with stage variables.

In a future release (8.2?) the Pivot stage will handle vertical pivot.

It appears not to have liked the backslash.

Look at the timestamps on the two posts. John has responded with a separate thread to ask a separate question, which is the way things should be.

There is no need to quote everything - it only wastes space.

Domain logto suggests that the user details supplied are not those of a user credentialled for DataStage in the named project, or that the named project is not a correct DataStage project name. Did you provide port numbers in the request?

Perhaps solved, but not an answer to the original question.

What Craig said, except for the "why not" part.

NEVER kill DataStage processes.

Don't hold your breath.

Welcome aboard.

There's nothing automatic, but you can design recovery.

As noted, designing recovery will require that you keep track of how far the job has got before it fails.