DSXchange

Can you get into the project from the Administrator client?

If so, it may be that the Repository needs to be re-indexed. You must have exclusive access to the project to attempt this.

SMP is irrelevant. Both work on a single CPU system.

Precisely how did you "create a new account"? Which client? It can't be done in Manager by any means of which I am aware (at least not without creating a routine). Precisely how did you create the hashed file? (Note, it's "hashed", not "hash" file.) What were the settings on the Stage tab of the Has...

Last time I wrote one of these (I think it was in the Mesozoic era) I used a flag variable (InQuotes) that indicates whether the current character is inside a set of quotes or not. It is set by the first quote character found and reset if it is set when the next occurrence of that quote character is...

chulett wrote:Or just ensure the load jobs abort in the event of a problem. No 'audit' required.

Tell that to the auditors.

Did you try the solution with echo (my initial response)?

To paraphrase, do not have DATE_CREATED in your DataStage job at all. Because it has a default value in the table, it will be assigned this default value by virtue of not being named in the LOAD statement.

Within the Columns grid in the Sequential File stage you can scroll right and find a place where you can set up a "missing value" rule. Try changing that rule for DEPT to Replace, so that the job does not fail. But, yes, you do need to check the file itself and verify whether there are too few delim...

What is your "lookup failed" rule in the Lookup stage? By default it's set to Fail, which causes your job to abort on the first occasion a lookup fails to return a row.

Look in the logs of the individual jobs and report back what you found there. In particular, did job 1 even attempt to start? What was its status?

Can you describe more exactly what you are trying to do, what actual steps you take, and what you expect to happen? I know English is not your first language, but I did not understand your use of the words "cut" and "directions" in terms of a Survive job. Can you please use QualityStage terminology?

You design extra jobs that delete or truncate as appopriate, and conditionally run these.

I have no idea why you particularly use it.

Unicode is an encoding strategy that claims to support every character known to commercial data processing.

Without Unicode, DataStage is limited to the encoding called ISO8859-1, sometimes erroneously referred to as "8 bit ASCII".

subhasini wrote:max of some 30

That's why I responded as I did.
Configure as many columns as your max.

You've been here long enough to know that we don't do "urgent". If it's urgent, sign up with your support provider for premium service, and learn the true cost of urgent.

Why not continue to use server routines? You can call these via Routine activities in job sequences.