Re: sqlturbo processes don't go away

In article <3159C114.9B4@csg.mot.com>, Robert Scott <Robert_scott@csg.mot.com> says: > >I have a question..... > >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." > >If I have a simple program like the following, I get no sqlturbo. >MAIN > WHILE TRUE > DISPLAY "HELLO WORLD" > SLEEP 1 > END WHILE >END MAIN > >If I add a database to this, I get the sqlturbo until the program stops. >DATABASE TEST >MAIN > WHILE TRUE > DISPLAY "HELLO WORLD" > SLEEP 1 > END WHILE >CLOSE DATABASE >END MAIN > >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 > >Does anyone know what would cause this? Do I really have a problem or >am I missing something? This all seems quite normal to me, or rather it is what all our systems do. I don't see how this can be a problem. In client server applications the sqlturbo can sometimes persist for some time after the client program that caused it has gone away. This too does not seem to be a problem usually.