Hey Stuart,
Guess what, it still happens in version 10.1.22 of universe.
I'm using UO and in a normal basic program we retrieve the contents of
system(9001) when an error occurs.
I believe this is a bug.
Regards,
Jeff Marcos
* Phone: +612 9335 0104
* Fax: +612 9335 0753
* Email: [EMAIL PROTECTED]
------------------------------
Date: Wed, 20 Dec 2006 22:49:25 +1100
From: "Boydell, Stuart" <[EMAIL PROTECTED]>
Subject: [U2] [UV] 10.0.7 - System(9001) and transactions
Not sure if anyone else has come across this but I just found out that
under certain circumstances, calling system(9001) will hang a process.
As it's almost time for the Feast of Saturnalia I thought I'd share.
I have a file that has a file trigger - this is just an audit stamp of
when, who and a system(9001) stack-trace that writes into an audit file.
This works fine for most circumstances except when it is updated from
(in our case) UniObjects. This is all complicated as the UO process runs
in an update transaction, which calls a trigger that also runs in an
update transaction so tracking it down was Fun.
I had to amend the audit trigger program to make it run without hanging
by adding the following exception...
*// EXCEPT uvcs - hangs transaction as at UV 10.0.7
if @tty # 'uvcs' then auditRec := @am:lower(system(9001))
I haven't had time to try this for any other circumstances or versions
of UV but hope it helps someone.
Merry King Cole to one and every.
Stuart
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
