DSXchange

Is the behaviour consistent? That is, is it always the same jobs/queries that hang? Have you tried executing the same queries using a client other than DataStage, but from the DataStage server machine? Have you employed the test/diagnostic tools that are in the branded_odbc directory?

What are the data sources containing these values? Whatever the case, you are going to need to write some code, since you are on version 6.

But please begin with an English language specification of the expected output from this processing.

Wasn't Mr Smee Captain Hook's offsider?

You need at least a format string.

The stage variable could have been more simply derived as Source.Rng >= LookupData.Rng1 And Source.Rng <= LookupData.Rng2 If expression Then @TRUE Else @FALSE is redundant because expression itself must return a true/false result. In DataStage BASIC, 0 or "" (or anything that is equivalent) is regar...

Since you have not asked a question I will assume that you have a solution to the situation you describe. Can I therefore ask you to post that solution?

If you don't have a solution, can you post a question?

The status of a job captured within a job will always be "Running". This does not contribute much to your understanding of what is happening. In an after-job subroutine you can capture the interim status (what the status will be once the subroutine finishes) but this is not available until all rows ...

Try disabling the job monitor (APT_NO_JOBMON) to see whether it's the source of the signals.

...anyone being paid by the hour!

There's nothing out of the box, but it would be a fairly straightforward parallel routine to write. Consider your business rules, though. InitCap might also need to occur after certain other characters, like O'Brien or Sarbanes-Oxley. Then there are the exceptions, such as fforbes-Hamilton, MacDonal...

eCollectAny has no effect when the receiving stage operates in parallel mode.

The first format is easiest; the routine reads a line at a time and returns a comma-delimited list. You then use the result of the function as your "list of things" in a StartLoop activity in a job sequence.

Note that ELSE IF is two words - there is no ELSEIF or ELIF operator. Note also that this is a value-generating expression, not a statement in a function, so that assigment operators and statement terminators are inappropriate.

Useful knowledge. Thank you.