Re: WARNING! problems with Transactions and kill command on SE

Ing. Melvin Perez Cedano wrote: > Hi all: > I'm surprised because a thing that supposed to work, doesn't. I will > explain you using an example: [SNIP] > If I run this program on a unix session, and after the delete statement > I kill such process using the unix kill -9 command, what should happened > with the data affected? > I don't know if I'm wrong, but I think that the data should stay as it > was before execute the program. > On SCO OpenServer and INFORMIX-SE 7.14 the data is removed!!! > Is that correct? if so, How could you check the consistency here? On a guess, did you create the database with logging? If the database has no logging you can neither COMMIT not ROLLBACK and the transaction is permanent if the statement succeeds. Indeed the BEGIN WORK statement is probably generating an error and this simple test program is not checking the error condition after the BEGIN WORK. You can write code that is independent of logging status by checking the logging status of the database in the sqlca.sqlwarn string immediately after the DATABASE statement. Check out the 4GL manual for details. Art S. Kagel