Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!pyrltd!tetrauk!nick
From: nick@tetrauk.UUCP (Nick Rumble)
Newsgroups: comp.databases
Subject: Re: XA Compliant RDBMSs
Keywords: TUXEDO XA OLTP DTP
Message-ID: <1125@tetrauk.UUCP>
Date: 3 Apr 91 11:25:56 GMT
References: <1120@tetrauk.UUCP> <2060010@hpcuhc.cup.hp.com>
Reply-To: nick@tetrauk.UUCP (Nick Rumble)
Organization: Tetra Ltd., Maidenhead, UK
Lines: 22


In article <2060010@hpcuhc.cup.hp.com> Dan Hepner writes :-

>The Developer's Specification of XA, as yet unpublished by
>    X/Open.

In fact, the Developer's Specification of XA is now available 
through X/Open.

Dan goes on to say :-

>It's also quite possible to make use of Tuxedo/T - DBMS
>combinations which have no utilization of the XA interface at all.

True. But - and this is a *big* but, should one or more elements
within a distributed TP application fail for some reason, remote
transactions belonging to non-compliant DBMSs would remain in a
pre-committed state. Having no control over them, the TP monitor
could not instigate the necessary recovery (commit or abort)
procedures, leaving the DTP application in an inconsistent state.

Nick Rumble