Re: I4GL Error - no number - lock table

It is error -524; see also errors -255 and -327. I'd guess that the 4.11 database is unlogged and SE, and the 6.00 database is OnLine and logged. With a logged database, you can only issue LOCK TABLE statements within the scope of a transaction, and you cannot issue UNLOCK TABLE statements. COMMIT WORK release all locks and closes all non-HOLD cursors. With an unlogged database, you have to manually issue UNLOCK TABLE statements, and of course BEGIN WORK and friends do not work. You have to design programs carefully if they are to run unchanged in both logged and unlogged environments. You have to be even more careful if they are to work with both unlogged databases and MODE ANSI databases. And only with extreme difficulty can they be made to have the same error recovery characteristics under logged and unlogged databases. In fact, I'd suspect that the error recovery characteristics cannot be identical and that you could, with care, prove it. You have to consider transaction logging carefully when designing database programs. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> }Date: Wed, 5 Jul 1995 14:57:39 -0500 }From: DONALD_BOOTHBY_at_ISDLAN@ima.isd.state.in.us (DONALD BOOTHBY) }X-Informix-List-Id: <list.6812> } }The message appears: "Lock table can only be used within a }transaction" when I'm trying to create a new program, or trying to }modify an existing program in I-4GL 4.11 for Informix 6.00.UE1. } }The error message doesn't have a number. } }I would contact Informix's customer service, but we are currently }ordering the product and the evaluation period has ended and so }Informix wants us to send a letter of intent which the State can't }legally do, blah, blah, blah. } }Appreciate any or all assistance. }Anyone got a job that you can just go out and buy what you need rather than }justify it to death. } }donald_boothby_at_isdlan@ima.isd.state.in.us }State of Indiana - Information Services Division }Indianapolis, IN 46204