DSXchange

You add -wait or -jobstatus, not both. And have you noticed the "port" needed after the SERVER entry now? Post your current syntax so we have some idea what you are doing now.

I'm not sure it's supported but if it is, you'd need multiple input links to a single ODBC stage to enable it - is that what you tried?

This forum (that I just moved your post to since you marked the job type as Parallel) is the one to use for questions specific to Parallel jobs. There is also a dedicated Server forum and the General one is where "everything else" goes - client questions, sequence job issues, routine codin...

Please make sure you understand that having everything "in one single line" is the standard and perfectly normal. No system should need it to be formatted and I would challenge your statement that it actually needs to be pretty printed like that. However, I've already noted how to accompli...

... and then I'll move it.

That won't work, I'm afraid.

Another solution - research the use of the DateFromDaysSince function.

As I suspected. You'll either need to break it up somehow (if applicable) or deliver it in some other manner like FTP.

Welcome. Searching will reveal a ton of questions and information on this topic already here. However... why Java or VB? The API to retrieve any information of that nature is dsjob at the command line and its use has been discussed here many, many times. A 'simple' approach would be to leverage dsjo...

<moved here from the TX forum>

I understand all that. Why not present all of this to your offiicial support provider? Show them the nature of your bug and see if you can save someone else from your pain? I'm sure they'd like to know that something silly like this is going on...

Run both triggers to a Sequencer set to 'Any' and then go from there to the End Loop.

It's called a reserved word. So, it was exactly what I thought, it was confused and thought you were incorrectly referencing the new surrogate key function. Not quite sure what part of all this was "poop".

Sure, just link the job to the End Loop stage and the loop will continue for as long as it can based on your loop conditions. There's no such thing as an infinite loop, however. Hence my continued concern that this approach is not... appropriate.

No, there's no special configuration needed, it should "just work". Are you using a full path to the file? It seems to be finding it ok but just want to be sure. Is your attachment file "large"? Does it work for a small file?