DSXchange

Your support provider will advise. They, in turn, will need to investigate whether it's a known bug or a new one and, if the former, whether there exists a patch. We (the posters at DSXchange) do not have the resources to do those things.

Yes. Never react to a single sample. Monitor over time - maybe four weekly samples.

Look at the source code for this routine (in the SDK branch) and identify the situations under which it might return -1. Apply detective skills to determine which of these is happening in your case.

It is not possible in parallel jobs in version 7.

It is possible in server jobs, using two hashed file stages connected to the same Transformer stage and which refer to the same hashed file. Search for more information; it has been discussed more than once, and recently.

Like, wow! (Maynard G Krebs)

Try StringToDecimal() with the scale set to 0.

No, there's nothing the way you're thinking. However, there's nothing to stop you updating/rewriting the value file itself, perhaps in a before-job subroutine or in an upstream job, routine or command activity in the job sequence. Values files for parameter sets are stored in a directory named for t...

Shared containers don't get executed separately, so the answer is "no".

Components within the shared container should be able to be monitored as if they were components in the parent job itself.

Welcome aboard.

Start by disabling operator combination. Until you've done that you have no idea which stage (operator) is generating the problem.

There is a document prepared by IBM support on configuring access from DataStage to remote DB2. It can be had for the asking from your support provider.

Check your assumptions. You don't get this message unless more than one row is returned. This might be because you are doing a lookup on a partial key or non-key column, or it might be that there are indeed duplicates in the reference table.

Without the STATISTICS keyword, ANALYZE.FILE reports only the tuning settings (the parameters that can be set when the hashed file is created). There is no way to tell from that whether the hashed file is well tuned. Add this keyword to have sizing information reported. ANALYZE.FILE myhashedfile STA...

Lose the semi-colons.

If two jobs are accessing the same sequence ("qwerty") then you will get a deadlock situation, as the first one in holds the lock until it (the job) completes. Prefer KeyMgtGetNextValueConcurrent() in these circumstances.

We probably expect you to post next that jobs won't run because the log tables can't be opened.