DSXchange

Right, my bad acronym... some kind of "Type 3 SCF" then.

That Administrator setting is a default, something that only new jobs inherit at creation time. It doesn't affect existing jobs.

I'm assuming this is a Type 3 SCD, current and previous values being stored.

Then you don't need "two streams". And it's just a simple hashed file check and some derivation song and dance for the update stream.

I too assumed that was not really the case.

For the 'unchanged value in the lookup' condition, do you really need to do anything or can that record just be discarded?

What stage are you using? What settings / properties are set in the stage?

So, does the Server job run correctly? Is the process failure noted in the Server job's log or the Sequence job's log? Any idea where in the flow that pid is failing or what the pid is associated with? Perhaps you could ready a telnet windows on the server for something simple like "ps -ef |gre...

No, you need the credentials, either directly at the command line or you can look into the -file option.

No, it simply means that no commits are done until the job completes normally, if the job aborts all work will be rolled back. Which is exactly what you wanted, I assume.

More information is trickling in and clarifying the situation. We can all connect from the Designer client but not the Director or the Manager.

Curiouser and curiouser...

Here's an interesting bit of additional news. I had assumed the problem was affecting everyone but that's not the case. Some people can connect to the project and some cannot.

What would cause something like that?

No, re-read my message, 7.5x2 is the only version (before 8) that will run PX jobs on Windows. Just wanted to make sure there was a point to all this.

Unless this is specifically the 7.5x2 version (note the 'x') you'll never get it running jobs on Windows. Never mind the fact that XP is not a supported O/S.

Set the interval to zero, as long as it is a count and not elapsed time.