DSXchange

I think you need to enable the "Add checkpoints so sequence is restartable on failure" option, but I'm not really sure.

You could always code something up in BASIC to read the input and write the output to different filenames... or you could use the Folder stage.

Read the Server Job Developer's Guide section on it to see how it can dynamically write to many files in a directory.

Yes, we do. I'm interested in Ray's statement re: two syntaxes... I see no evidence of the ability of being able to sleep until a particular clock time. Where would that be documented? I went thru some gyrations to compute the next time to sleep to and how many seconds from now that was, hence the i...

linit wrote:I am back with some other issue.

Next time, when you come back with some other issue - start some other thread. Please.

You can't "call the function" without using a SELECT statement - that's how they work, they must be selected.

And wrapping the select of the function into a stored procedure just seems... silly. But hey, if that's what your Oracle team wants you to do, knock yourself out.

Then you just need a smarter sleeper. I wasn't going to add all the gory details, just put forth the general (very) high level concept. As an example, I just built one that needs to run over the course of the day and run a series of jobs 'every five minutes'. At the end of each run, regardless of ru...

You could build a Sequence job with the Loop stages that runs your job and sleeps for X inside each iteration.

Tell us what they are, what the hex values are that you are seeing.

Dollars to Doughnuts that 'square' is a DOS End-Of-File marker, a Ctrl-Z. As long as there's only one that is, and it's at the end of the file.

Otherwise, you'll need to take a peek at it with a Hex Editor or viewer of some sort.

Since this is a Parallel job question, please mark it as such.

So why is this marked as a 'Server' question?

Now we just need some sort of Challenge mechanism.

Yes, it does - but what shows in the Monitor can be confusing and can make it look like 'nothing is running'. BTW, the OP has never explained exactly what this means or how they are measuring this 'delay': The problem is, job A is not getting triggered immediatley after the tool triggers seqA job. S...

Great... how is this a 'workaround'?

How about coming back here and explaining whatever issue or issues you still have with this and let's get them straightened out.