DSXchange

You need both links in order for this to work correctly and yes, you picked the right "OK" one. Run both into a Sequencer set to Any and then on to the next activity if either one is valid for the next step.

Yes.

Can you clarify what exact it is you mean by "a user updates the DSParams via DS Administrator"? As noted, wondering if that could be part of the problem.

It also ships with a pdf document that walks you through everything you should need to know about it. The online help mirrors that pdf pretty closely.

Hmmm... I thought there was some kind of command line option for that. Ah well.

I don't recall... do you need to have buffering on for this stage? Does it help if you add another transformer between the collector and file stages?

That was my next question, but figured I'd let you ask that one Andy.

Or just exit the loop cleanly when your stop condition (whatever it is) is found. No need to do anything less graceful, really. IMHO.

It will "mostly" work but really is not recommended.

richdhan wrote:1. Pls check this link for a list of job status codes

Or just check the dsapi.h file as noted in the previous linked post for the complete list.

You should know if a job is multi-instance or not as that is a deliberate design decision someone had to make, plus that shows in the description.

All of that, including the filename where that is stored on your system, is in the post I linked.

In other words, post the actual syntax you are using along with a sample or two of your input data.

It's an artifact of the row buffering. What's your goal here, what purpose does the Link Collector serve?

That would be your "table_reference" table, I would assume.