HP3000-L Archives

November 1996, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
K N Kumar <[log in to unmask]>
Reply To:
K N Kumar <[log in to unmask]>
Date:
Sat, 2 Nov 1996 19:35:02 IST
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Gavin wrote:

>
> > > > Q3.  As I understand it a DBXUNDO applies to all DB calls across
> multiple
> > > > databases. Do I have this right?
> >
> > As of MPE/iX 5.5, DBXUNDO can be used for transactions spanning multiple
> > databases.
>
> My recollection is that DBXUNDO will only affect a single database unless
> you specified multiple databases in your DBXBEGIN call which is a different
> mode similar (or identical to?) the old multi-database DBBEGIN.  As I
> recall, support for multi-database DBX transactions has been there for
> some time (I believe Image/SQL has always required it), but may not have
> been documented or implemented in a fully general fashion until more
> recently.

Support for static multi-database transactions (MDBX) has been there for
some time. The Dynamic intrinsics (DBXBEGIN, DBXEND, DBXUNDO) can now be
used for multi-database transactions (DMDBX) using a mode identical to its
static counterpart. While MDBX defines modes 3 and 4, DMDBX defines mode 3
only.

Regards,

Kumar
CSY, Bangalore

ATOM RSS1 RSS2