DSXchange

Exactly, you need something else to check and thus only run your job if the file is found. Easiest way is the Sequence and WFF way, but there are others.

And you are 'stopping' them how? Where does the 'using scripts' part come into the picture exactly?

So... again... based on conditions, you want to update different combinations of columns? Will you always execute all four or always just one of the four or something in-between?

And what have you tried? Are you getting any particular errors or problem?

As noted, it is unusual as you would typically load the base tables directly. Why the perceived need to target a view?

For "long filenames" with embedded spaces you need to quote the entire thing. That or switch back to the 8.3 "short name" which more than likely is:

//dsserver/etl/FtpFil~1/dummy.txt

Sorry, but what exactly do you mean by "4 update SQLs on the same table"?

Which 'this' has been resolved? This this or the other this?

Then the next thing you know, Douglas Adams fans will counsel the use of an Infinite Improbability Drive to accomplish the same, leading to the extremely possible possibility of Spontaneous Massive Existence Failure or perhaps just... no tea.

Those seem like... generic instructions and not specific to any particular patch, and as noted are for server side patches. If you truly received a client side 'Designer patch' I don't see how these apply, they should have given you specific instructions for this. And Ray, someone else piped in with...

And how many of the 45 invocations of the job are you running at the same time? Have you grep'd the process id list to see what, if anything, shows up out there for them?

Can you post the instructions you received? I don't see any 'Designer' fix would be run on the server...

You don't use both, you use one or the other. Perhaps that's contributing to it. Try removing the "-wait" and see, as the "-jobstatus" also waits.

Is there any way you can look at the script itself for that message and see if you can tell what bits it is checking for?

As noted, it's not really a solution, per se... still best to see if you can track down the root cause.