DSXchange

I'm curious about the "look for a file residing on a remote machine". If that's a one-time look and process if found, then I've done much the same in the past that Franklin has noted to pull remote files locally for processing. As mentioned, the sticky bit can be getting all of the securit...

Not to be confused with iStool. And yes, it's perfectly safe to click on the link. I swear.

The 'new' utility in the 8.x world is istool. Andy posted a nice overview of the syntax here.

Still suggest you bring your SysAdmin into the conversation, if you haven't yet.

Unless something has changed, you only needed to give the gateway on a Windows server... for UNIX it can be left empty. Assuming we're talking about the Notification Activity stage here.

That's all handled by the O/S, talk to your System Administrator.

And it's a custom routine (hence the DSU prefix) which means someone there wrote it.

Problems along those lines always say 'resource issue' to me. The rub is nailing down what is actually going on, what resource is being affected / exhausted at that moment in time.

Use a message handler to 'demote' the message.

I was making the same assumption, forgot to mention the FD part.

That would be a job for the Complex Flat File stage. Have you tried that using that stage yet?

Neither are we. Not sure what other advice anyone could give. If the problem is the return in one of the parameters, where does it come from? How are you passing / generating / fetching the parameter values to use? Look closely there. Try something other than @FM in your Convert() function - CHAR(10...

It's pretty simple - the frequency of one versus the other. Go with the one with the most chance of happening first.

I'll repeat... have you engaged your DBA? They can check and see if the index is actually being used. And please, post the entire error message if you want help with it. If so, clarify what "parallel mode" means - running the job on more than one node or using parallel / partitioned writes...

Doesn't sound like a DataStage problem but rather a database one. From your description, it sounds like full table scans are happening because you don't have an index over the column(s) in your where clause. Have you engaged your DBA, had them monitor the session, make suggestions? Also, "abort...