DSXchange

What has changed between when it was running successfully and when it is not running successfully? I can not accept "nothing" - you have to find what has changed, even if it's the data.

The three sequencers achieve nothing, your job design would still have the originally-reported problem.

In the configuration of IA are you using a static DataStage credential user and, if so, might that user's password have expired or otherwise have become invalidated/locked?

Not me. But accessing Help from within the stage will probably provide you with some clues.

Excellent.

(My server job background came through for a bit, there.)

Something is clearly different. Find out what it is. It might be in the operating system, the database(s), the authentications, anything.

JobMonApp is a Java application. It should be started the same way on Windows as on UNIX (JobMonInit). See this DeveloperWorks article for example.

No. Only the parallel Transformer stage requires the C++ compiler. The server Transformer stage (and the BASIC Transformer stage) compile within the DataStage server engine environment. It is vital that the four environment variables APT_COMPILER, APT_COMPILE_OPTIONS, APT_LINKER and APT_LINKER_OPTIO...

Stuck at ready state is rarely related to the job monitor (which is an independent application) but is usually related to waiting for some resource, such as a large, sorted extraction query to complete or for a database or table lock to be released.

Transformer stage with two outputs followed by a Funnel stage. The key goes to both output links. The first three columns go to the first output link, the other three columns go to the second output link.

RANK is a display function, not a selection function. As a general rule it's not something I'd ask an ETL tool to do - it's something I'd ask a reporting (or business intelligence tool) to do.

While it can be done in ETL, you need to decide in advance how you're going to handle tied values.

Never running DS.REINDEX without exclusive access to the project would be favourite.

Cool Thanks Ray - I was thinking User Varibles - but this is much simplier - do you have examples of this type of coding? - I am guessing Innovocation ID and Job Status - as you said - check on the three possible streams after exiting the Any Sequencer - with a wait type loop on those jobs running ...

Ray - what about a sub sequence - that gets passed the current Nested Condition triggers - to run a Nest_Condition within the Sub sequence - when any or all jobs finish in the sub Sequence it returns to the calling Sequence - no routine necessary - will test and advise results I thought (briefly) a...