DSXchange

So you don't have a problem resetting the job, that sounds like it is happening just fine. The fact that it logs errors during the reset is of no consequence and is normal in cases like this. What's typically happening is the errors that caused the job to abort in the first place are being picked up...

Only call the routine in the Initial Value of the Stage Variable and don't put anything in the derivation field of the Transformer entry. Only called once and then can be referenced as much as you like.

saadmirza wrote:I am looking for such kind of functionality like a director on Web...

I think it's been mentioned as coming with Hawk.

Sounds more like you are looking for an RTI/SOA solution, not a web user triggered batch job.

Otherwise, it's the standard 'dsjob' command that you're looking for... and I see Arnd has already mentioned that.

As for disappearing specifications, you appear to have a bug in the client. Or perhaps you're not entering 1, 2, 3 in order. The latter, sorta. It happens when you put in a Sort Order and don't put in a Sort sequence number. Once you move off the row the gui removes the sort order since that field ...

Now you knows I meants the data Mr Ray, the dang data.

You need to match reality, otherwise the stage doesn't know and it has to do its own 'sorting'.

No, it should stick around. Did you fill out the Sort field first with a number to show which is 1, 2, etc?

Please don't post the same question in both forums unless you are specifically looking for both a Server and a PX answer. This forum is meant for questions on the EE/PX product where the answer to your question would be:

a) Totally different and
b) Unusable in a Server job

Thanks.

You may have hit one of the Aggregators problem thresholds, like the number of records it can handle. Any chance you were sending it a very large number of (or some rather 'fat') records? At some point it will just fall over unless you sort your incoming data and assert that in the stage.

In other words, use ExecDOS in the before or after job areas, or use DSExecute within a routine called from a Command Execution stage in a Sequencer job.

You can also use Char(10) in place of the \r.

Keep in mind the fact that, if it's not sorted over all of the grouping columns in the same order as they are grouped, you might as well not bother to sort at all.

ps. Nothing in a database table is stored 'sorted'.

Welcome. Or perhaps welcome back. :D If you still have support for the product, you can register at Ascential Developer Net and get access to their Library. One of the things you'll find there is the What's New document for 7.5. While it won't go back as far as 5.x, it will show what is new in 7.x (...

I've seen this before and have no idea why it would be happening. Two or three times in the last year one seemingly random job out of the hundreds that run at night would crater with this error. Nothing 'special' about the jobs, just standard insert or update actions on a table via the OCI9 stage. A...