DSXchange

Or just use a Sequence job.

LOL... welcome to Larry's world.

As Ray notes, you need to build that functionality in. I always have some kind of "date/time/loop" check built in so it can gracefully stop on its own and add a polling step so I can touch a stop file into existence and it will notice and again do a graceful shutdown.

Unfortunately, it's a "catch all status" so it could mean any number of things that the other status codes don't catch.

Use a Sequence job. And incrementing a value for every row is as simple as "StartingValue + @OUTROWNUM".

So, are you allowed to login using a different account and then su to dsadm? That's a very typical solution from what I've seen.

Or just use the proper trigger conditions as posted earlier - Finished OK for the 0 link and Otherwise for the 1 link. It will then know that you are handling any errors and stop doing it itself.

Spell out your requirements in words, for some reason I can't make any sense out of your example. Also posting the Oracle SQL you mentioned should help as well.

As noted, handle it yourself and the automatically logged 'unhandled exception' message will go away.

Exactly... if you need to know what fields have changed values, you'll need to check each one individually. Those other methods just let you know that something changed in the record.

I would start here in your shoes, in particular the General RealTime Discussions section.

It looks like it successfully processed a whole lot of nothing to me.

Having never used this particular tool, I'll leave it to others to provide any continuing help.

There have been discussions here about ways to deliver the logs in such a manner as to allow people of lesser importance (i.e. developers) the ability to view them, but I don't know if you want to build something like that. There have been other discussions around permissions lock-downs such that on...

I have no way to check anything, so unless someone else can verify this for you, you'd need to do a couple of things. 1. Find out where this "cmd" lives. 2. Add it's home directory to the PATH environment variable in the dsenv file. Unless this is something you set up? It does say it is a ...

Hard to say from that message but the "not found" part means you have a PATH issue which typically means you have not sourced your dsenv file to prepare your environment. Try:
And then run the script. Note that the first four characters are dot-space-dot-slash.