DSXchange

Off the top of my head, a routine to read those values in and a Nested Condition stage to split the flow from there to the right Job Activity. Perhaps all in a looping structure supported by a UserVariables Activity stage.

Search the forums for USERSTATUS, it's all out there including some code that may come in handy.

You need some way for the job to stash / land that data in such a way that the Sequence job can pick up and pass along. For a Server job I'd suggest USERSTATUS, however either job type can write data to a flat file and a Sequence routine can pick them up and pass them as job parameters to downstream...

No, a dblink is - in this particular case - a specific Oracle object, allowing a query to reference a 'remote' table as if it was local to the current instance. I would think other databases have a similar concept.

Thanks for the info, I'll check. Probably have the Apache tool here somewhere, not sure about the Oracle one. And I'll bump up the Wait Delay as well. This is good timing as I just found out it's time for another 'load test' in the QA environment tonight. Any idea what a reasonable value to raise th...

Search the forums. The cause and solution have been discussed here before.

Looking for some Words of Wisdom as I am getting beaten up black and blue over 'RTI performance' or lack thereof. I said "Part 1" as I thought I'd start with the simplest case and, if time allows, follow up with the more complex ones. Please see this post which explains our topology. I have four ser...

Excellent, please mark the topic as Resolved in that case.

I did a mixture of both of your suggestions. I used EOR (End of Record, I presume) characters in which I was able to retrieve a couple of the commands to perform that from a previous post titled, "writing multiple lines from 1 source row", from roy. p.s.- I looked for the FAQ mentioned by Chulett o...

First suggestion would be to re-post your problem over in the Parallel Extender forum. This one is for QualityStage questions. Before that, I'd suggest availing yourself of the Search functionality to see if your topic has been discussed before. (hint: it has)

There are probably other ways, but I'd bring it in as a string, remove all the 'punctionation' and then divide by 100:

Then you need to search more better. It has been discussed here quite a number of times. First clue is that all that running a query in a tool like SQL Developer or Toad just tells you is that it is syntactically correct. It doesn't provide any clue how appropriate it may (or may not) be for use in ...

Never tried this, but the docs say you need to use UtilityGetRunJobInfo afterwards to find out what happened. One of the possible actions is JobCompletionStatus, which sounds like the one you need.

Something like this, perhaps?

http://www.dsxchange.com/viewtopic.php?t=119624

Or via a routine using the Routine Activity stage.