DSXchange

Where did you come across that property. I remember seeing that property in DB2 LOAD stage. It is what it says. Its the restart count. If a load fails and commits 30,000 records. You will pass 30,000 as the restart count.

Did you try looking for those files in the lib path. The ones that I mentioned in bold. They wont be the exact but atleast similar.

Basically for restartablility. Generally, the loads are indepenedent. A failure in one load will not affect the other. Thats why its a best practice to run them in a sperate job so that if one fails, atleast the other wont be affected. In your case its the opposite, you want the failure in one to af...

Clear the scratch space, temp area. Run the job again. Is it only this job or other jobs as well. Run a sample job in prod to see. Also keep the two environments identical, to the extent of comments.

Your wish is, finally, granted.

Actually I presumed that you have all in one job. You are correct, its better to keep them seperate. But if you have a requirement of rolling back data from all three tables then I would say go for a single job. But you need to test it first. Test whatever I said in my first post. If you have four d...

Yea, My bad. Thats the Terminator Activity. Have'nt used sequence jobs in a while and hence my rustyness. I remember your previous post. As far as I remember, it was concluded that a stopped job needs to be reset before you can run it again. As Craig put it, it needs to Abort. In order to do that ru...

You need to enclose your password within quotes. Before that you need to apply a patch. Refer herefor an ECASE number.

In Exeption handler, there is an option to Abort without waiting for other jobs to stop. Did you try that option?

Have you tried with transaction size 0. You will have to test it out with four database stages in a single job. If any one of them fails an insert, it will generate a warning, keep your warning level at 1 so that the job is forced to abort. This way the transaction will be rolled back. The only thin...

It seems like the libraries could not be loaded. I am on HP-UX so I have liborchsorthpux.sl , liborchstatshpux.sl and liborchgeneralhpux.sl for orchsort, orchstat and orchgeneral respectively. These are present in $APT_ORCHHOME/lib folder. I think your issue might be related to these library files a...

Strange error. Seems like the engine is not able to fine the PXEngine path. Look in the dsenv script in $DSHOME and see if $APT_ORCHHOME is properly set. Is this the first time your getting the error with a parallel job? Is this a new installation?

narasimha, I think the OP is concerned more in finding the job in the designer in order to open/edit/run it. Analogous to finding a link on a website with 5000 links. A simple find and click. Unfortunately such a thing is not present in DataStage.

They are alphabetically placed. Go for a visual view. There is no find option.

I highly doubt it. You have to build a job as far as I know.