Dear UniVerse Gurus,
Our UniVerse system (10.1, Win2K3) is set up without any Transaction
Logging parameters set in the UV Config.
I.E. TXMODE = 0, and all the other related configration parameters are
set to defaults.
Transactions do however, still work from UniBasic or from UniObjects,
even without TXMODE set - the UniAdmin documentation says "A value of
zero allows transactions to execute but not be logged ...".
So we can use UV Transactions to get all-or-none of a set of updates
applied, i.e. ensure atomicity of operation, but not for roll-forward
recovery from a crash.
OK, so far so good ...
But, where is the information needed to roll a transaction forward
("Commit") or back ("Rollback") stored in that situation?
All the documentation in the PDF is about transaction logging, i.e. it
assumes TXMODE = 1
Are there any configuration parameters which we ought to set, and if so,
how could we determine the optimal values? TXMEM, for example.
Thanks
Mike
The information contained in this Internet Email message is intended
for the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence Force.
If you are not the intended recipient you must not use, disclose, copy or
distribute this message or the information in it.
If you have received this message in error, please Email or telephone
the sender immediately.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
