Re: sqlturbo processes don't go away

You were reading the I-Net/I-Star book, which is talking in terms of remote database access therefore. When you close a remote database, the engine should disconnect for you. If you are accessing a local database (as in your sample code), then the engine does not go away. There is an ESQL/C function sqlexit() which can be used to get rid of the engine altogether. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> PS: Thanks for including the detailed version info... }From: Robert Scott <Robert_scott@csg.mot.com> }Date: Wed, 27 Mar 1996 14:29:09 -0800 }X-Informix-List-Id: <news.22551> } }It appears that I have many sqlturbo process running which should not }be. I was reading about how when running INFORMIX-OnLine, an sqlturbo }process will be spawned to work with my application process. I }understand this, but something doesn't seem right. } }I read the following in the "INFORMIX-NET/INFORMIX-STAR User Guide" } }"The database engine process is active for the duration of the }connection. You terminate the sqlexec or sqlturbo process when you }finish running your application or when you issue a CLOSE DATABASE }statement. Each request from a client receives its own database }engine process." } }[...] } }With the following I would expect the sqlturbo to start and end when I }issue the CLOSE DATABASE - but it doesn't. The sqlturbo stays until the }application program is terminated. } }DATABASE TEST }MAIN }CLOSE DATABASE } WHILE TRUE } DISPLAY "HELLO WORLD" } SLEEP 1 } END WHILE }END MAIN } }[...more info, including detailed version info...]