DSXchange

Thanks for posting that!

Chastisement? Really?

Sorry, just being my normal anal self.

Clarify something for us - you need to get a link row count and then do what with it? Knowing that would help get you appropriate advice.

OK. When it "hangs" have you ever just let it go to see how long it takes? Have you involved your DBA and/or SysAdmin to monitor your resources while the job runs?

Not any kind of helpful, I know, but I find it amusing that you are using one ETL tool to feed another. Seems to me either one should be able to do the whole task. [shrug]

Any time I see symptoms like that - a random issue appears that does not repeat when the job is rerun on its own - it says "resource issue" to me. How many jobs are running each night? Knowing nothing else about your situation, first suggestion would be to scale back how many run at the sa...

Ray has posted it. Either trigger expressions or a NestedCondition can control the "branch around" B part and then a Sequencer set to Any joins things back before running C.

Isn't there some sort of installation log kept that would store the configuration information they are looking for?

I know what you mean! However moderators move posts like this one, I have no powers to alter the workings of the website itself.

Ok... have you checked out the Change Capture stage?

Just build the string 'around' the job parameters so they evaluate. Snippet:

Experiment! Try it and see. No-one can predict how it will all work out in your environment with your tables and your data. Do things like that and you'll start to get a better feel for when you should allow the database to do work like that and when DataStage should do it. Regardless of tool, I ten...

How will you know that "A" was changed to "C"? I don't see any relationship there that would allow that unless there are other columns that you didn't show that would control the order the rows should be compared. Right now, any change detection would think the 'A' row is missing...

I wonder how much of the issue is due to the fact than the "name change" is really just a change in case and it's not being recognized properly everywhere? As an experiment, in your shoes I would probably try a change from "commanjobs" to "COMMANJOBSX" and then as a sep...

Ah... interesting point about the DataStage Operations Console, wasn't aware of that.