BXBEGIN-DBXEND:

Is a controlling a transaction with transaction recovery, rollback. This
works with XM. Also, careful of some limits.

In IMAGE/SQL, the rollback capability is supported by enclosing every
transaction with a pair of DBXBEGIN and DBXEND calls. By doing this, the
user can roll back a transaction if needed. However, the problem with the
rollback capability is the limit placed on the rollback log buffer size. The
transaction manager limits the buffer size to 4 MB, so if a user wants to
commit a transaction that is greater than 4 MB, the transaction can't be
completed. In TurboIMAGE, the user can override the rollback capability by
not enclosing a transaction with a pair of DBXBEGIN and DBXEND calls; this
is not the case for gateway access through IMAGE/SQL.


-----Original Message-----
From: Ted Ashton [mailto:[log in to unmask]]
Sent: Monday, November 22, 1999 12:07 PM
To: [log in to unmask]
Subject: Re: DBBEGIN versus DBXBEGIN


John Saylor explains about DBBEGIN vs. DBXBEGIN
>
> DBBEGIN-DBEND are reserved for the start and end of a program and it
treats
> the whole program operation as a single transaction . . .
>
> DBXBEGIN-DBXEND are reserved for the grouping of specific transaction in a
> program . . .
>

Furthermore, DBXBEGIN allows the use of DBXUNDO.

Ted
--
Ted Ashton ([log in to unmask]), Info Serv, Southern Adventist University
          ==========================================================
It is the merest truism, evident at once to unsophisticated observation,
that mathematics is a human invention.
                                         -- Bridgman, P. W.