Re: transaction return codes

christrier wrote: > I am working with an Informix Dynamic Server, I am not sure about the > version. > The system is transaction based and I have to turn the transaction off > for a few operations. Are you sure? Why? > I did it with "ondblog nolog". That's a heavy-duty tool - not for casual use. > I then started a script which inserts some stuff into a DB and is > parallel! > After a few minutes I get a message in my logfiles with > "ondblog complete, returning 18 (0x12)" > and the script runs through ... > Can someone tell what this means? > I would appreciate your advice Normally, you could try any of a variety of tricks - such as using a RAW table or a temp table WITH NO LOG - to avoid the transactions. It also is not clear to me why that would be desirable; the whole point of a transaction is to ensure the integrity of the system. You might, perhaps, be overlooking deferring or disabling constraints. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.01 -- http://dbi.perl.org/