DSXchange

Search the forum for the following topics. You will need them all.
UV.ACCOUNT
VERIFY.SQL
SET.INDEX
DS.REINDEX

Welcome aboard.

Research the dsjob command ("command line interface") in the Parallel Job Advanced Developer's Guide or Server Job Developer's Guide (both of which are installed with your DataStage client software).

DataStage parallel jobs ALWAYS display decimal numbers with a decimal placeholder and leading and trailing nonsignificant zeroes, both so that you know that the value is decimal and not integer, and also so that you can verify that precision and scale are correct. It is not an error and it is not a ...

Execute in sequential mode (or use a server job). Sort in descending order. Count the rows. Pass only the fifth row.

Try it first to answer your first question.

If what you want to happen actually happens, then you will have nothing else to do.

Otherwise you may have a minor parsing task to undertake.

Either way, it can be done.

The Exception Handler has its own activity variables which you could include in the logged message. But you should be able to identify the culprit - that it, the activity that failed and thereby caused the Exception Handler to be triggered - from the job sequence's job log. Exception Handler activit...

I don't know. You will have to wait until next time U logs in. And even then, U may not be able to give a clear description. The problem is in how your job sequence is executing. You must determine what caused the Routine activity that invokes UtilityAbortToLog() to be executed - presumably a trigge...

If you search the forum you will find that this question has been answered before. Searching means that you can get your answer faster than posting and waiting for someone to answer.

Search the forum for this message and also for "packed decimal". You should find your answer.

What caused your job sequence (note, it's not "sequencer") to execute a routine activity that invoked UtilityAbortToLog?

Only you can determine this, as none of us can see your job sequence design.

Please use a professional standard of written English in DSXchange.

"R u" isn't.

You can't put an expression on the test grid. It won't be evaluated.

Create your own routine that accepts the three separate values, assembles the key, calls UtilityHashLookup, and reports the result.

Who said it is? The main reason, I guess, is that the default in Designer is to run with unlimited warnings. You can override this on the Limits tab, but you have to remember to do so. In Director the default default is to abort after 50 warnings have been generated. You can change the default in th...

Recompile is about your only hope to get this job back to a runnable state.

But you also need to investigate (and fix) the link that generated the error. Stage name and link name are part of the error message.