Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!pacbell!pbhyf!jwas From: jwas@PacBell.COM (Joe Wasik) Newsgroups: comp.databases Subject: Re: INFORMIX bug? Keywords: informix bug 4gl Message-ID: <8335@pbhyf.PacBell.COM> Date: 21 Nov 90 21:49:08 GMT References: <8330@pbhyf.PacBell.COM> <1990Nov20.221658.19496@informix.com> Reply-To: jwas@PacBell.COM (Joe Wasik) Organization: Pacific * Bell, San Ramon, CA Lines: 36 In article <1990Nov20.221658.19496@informix.com> markj@informix.com (Mark Jeske(Chicago Consultan)t) writes: >>In our case, since the Informix-4GL application starts up >>other background jobs, the sqlexec program hangs around until those other jobs >>are finished and it then interferes with the logoff process. >I would try the following in your code before you exit. > > close database > call sqlexit() While I admit I hadn't even considered doing a close, it's now been tried and unfortunately it doesn't work. In fact, the sqlexit() function also appears to wait. It seems to be waiting for confirmation that sqlexec back-end has died. It doesn't get it, so the program hangs at the sqlexit() function. An interrupt allows it to continue, but without killing the sqlexec back-end. Thanks to all those who send advice. Nope, signals 1,2,3,13,15 don't work either. Signal 9 does, but is obviously undesirable. Signal 16 works. Does anyone in Informix-Land know whether the sqlexec back-end does an orderly exit upon getting signal 16? Thanks. -- Joe Wasik - PacBell, 2600 Camino Ramon, 4e750, San Ramon, CA 94583 415-823-2422 jcwasik@clib.pacbell.com or {att,bellcore,sun,ames,pyramid}!pacbell!clib!jcwasik iraq += kuwait; numcountries--; price_oil *= 2; us_public = screwed; -- Joe Wasik - PacBell, 2600 Camino Ramon, 4e750, San Ramon, CA 94583 415-823-2422 jcwasik@clib.pacbell.com or {att,bellcore,sun,ames,pyramid}!pacbell!clib!jcwasik iraq += kuwait; numcountries--; price_oil *= 2; us_public = screwed;