DSXchange

We only have one remaining issue-the same co-worker has discovered that if a job fails, and you set the email function, the sequencer will send the email but continues to run. I haven't seen the job, they say they have tested, but I'm assuming that they didn't have the sequencer set to stop after e...

Where in the heck did you get that approach? The projects need to remain in place so they can be properly upgraded when the new Server version is installed. If you remove the old Server installation, then you should have imported all of your 'old' jobs from an export and that process will upgrade ev...

Nothing has changed with scheduling via the Director, it still leverages cron/at on UNIX and at on Windows. You may be thinking of Sequence jobs which get more and more capability as you go up the 7.x release versions and reduce the need for custom job control.

How ironical... a double post.

Edited to add: I guess it must be nice to have super powers. There *were* two posts when I posted this but now there's only the one. Poof!

We send an email and a page as well. This 'page' is just another email sent to either a true pager or our cell phones.

All of us chickens talking amongst ourselves about how unfair life in the coop is won't really change anything. Did we end up with an 'official' webmaster replacement after Walter left? Perhaps I'll forward a link to this thread to both official Contacts and see if anything comes of it...

Cleaning up logs won't help the initial display of Director in the Status view. When you check specific logs, sure, but it has nothing to do with how long it takes to just display the status of all jobs. As Arnd notes, it's all about using Categories well and the number of jobs in whatever Category ...

In other words, all recovery comes from a backup. How you use that backup is what Ray is writing about.

Specificall, this 'reverse pivot' to search for would be a vertical pivot. You'll have to do it manually as the Pivot stage only does a 'horizontal' pivot or columns to rows.

You can use 'cut' to get the pieces and then put them together any way you want. Best to ask a colleague for scripting help, quicker that way.

Last question first - it doesn't reset because it wasn't "required", the job was in a Restartable state. If it was just Aborted then it would have reset it. When the job in S2 fails, you need to ensure that S2 itself aborts which it sounds like you are doing. Then, you need to ensure that MS notices...

I've seen this behaviour when there are multi-byte values in the data.

Post your XPath Expressions, please.

Help / About is certainly one of the correct places to go and will show you both the 'Client' version at the top and what Server version you are connected to at the bottom. Not sure why you are not "getting the info".