DSXchange

Would have gone that route except for the time component to the scheduling. Hence the suggestion to have the Sequence job that runs last at 6:45am first check the status of the other four to see if (when it runs) if it needs to actually do anything or just shut down and wait for next time. Me, I'd p...

A custom routine in #5 can use the API to "get job info" to check the last run status for the previous four and pass back the result. A trigger can then decide if the fifth one should do anything or not.

Not really a "workaround" IMHO... all they've posted is a change they made. Won't know for some time if it has the desired effect or not.

Which is also why I noted that it is another solution.

Those are valid options for Parallel jobs with the Lookup stage. In Server, you need to check the success or failure of the lookup after it happens and then programmatically decide what needs to happen. That involves either checking the NOTFOUND link variable or checking if the key field(s) come bac...

... off you go to your own topic.

Or EXECUTE or OPEN?

What release are you on? Up to date on fixpacks?

Hard to say. Sounds more like a lock than a "slow down" unless you've let it run to completion and it has completed after some number of hours? Do you have any idea at what stage it is when it gets stuck, what it is doing? Writing to the hashed file? The target? As you said, in your shoes ...

A little late but assuming the Director - just unschedule it. All you are doing is removing an entry from cron (or at) which will not affect anything currently running. If this is a "run every" schedule, you'll need to add it back when it's time to get back on schedule.

No, I think you're still referring to the tangential conversation about aborted jobs being handled by Job Activity stages inside a Sequence job. The question was for the Sequence itself - if that outer-most Sequence job is aborted it will need to be manually reset before it can be rerun. Taking chec...

A derivation is an expression who's derived value is automatically assigned to its associated variable. You cannot do direct assignments in any derivation.

Now, I'm thinking that the above only resets the specific Job Activity and not the status of the sequence as a whole. Is that correct? Yes. Is there no way to simply have the sequence reset without putting a wrapper around it? No. Something must reset it when appropriate as checkpointed runs compli...

Just a guess but have you tried quoting the table name when dropping it?

As noted, it would seem you have different ODBC drivers in production or they are configured differently.