> 1. What is the difference between ServerAutoCommit and AutoCommit. Im not
> using either, as Im trying to maintain control of my own transaction.

ServerAutoCommit is used to guarantee that a job request that runs on the
server will commit upon completion without waiting for the client to request
the commit subsequent to the return of the job. What this accomplishes is
you remove a point of potential failure to ensure a commit will happen for
each successful invocation of a job. e.g. If you kick off a proc and the
network goes down the job will run to completion on the server but have no
way to become committed since the client isn't there any longer to do it.
This avoids that POF.

> 2. What would you use the sweepinterval for? Is that something that I

should

> use? Isnt sweeping quite resource intensive?

This is best left at 20,000 and left alone.

> 3. If I wait for transactions, would it wait forever or would it

eventually

> timeout. (using the ibo params)??

It would possibly wait forever but in most cases it will only wait while the
conflicting resource is in an uncommitted state. If two things are somehow
waiting for one another this is a core level deadlock that will put you in
the forever deadly embrace. App termination would be the only way out of
that.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com