Re: FW: defunct sqlexecd

Mitchell If you'd like to get in touch with me, I'll see what I can do to help. I'm sorry you've had some problems with support for SQL-Retriever. Perhaps you could tell me whom you contacted for support previously to no avail so that it doesn't happen again. I work in the UK support operation (what used to be VisionWare!) and specialise in SQL-Retriever. ----------------------------------------------------------------------- Allan Gould EMAIL : allang@sco.com Technical Support Engineer SCO Ltd SUPPORT PHONE : +44 (0)113 251 2222 Vision House, Waterside, SUPPORT FAX : +44 (0)113 251 2223 Kirkstall Rd, Leeds LS4 2QB MAIN PHONE: : +44 (0)113 251 2000 England MAIN FAX: : +44 (0)113 251 2001 ----------------------------------------------------------------------- Juergen Ostrinski wrote: > Nelson, > > Your problem does indeed sound similiar to mine. Since I can't seem to > get answers from either Intersolv or Informix I have little choice but > to try either Intersolv's 32-bit ODBC drivers or another vendors. > > Thanks, > Juergen > > Nelson, Mitchell wrote: > > > > Juergen, > > > > I have the same problem with Visionware's 16 bit ODBC drivers. I and my > > colleagues called up their Technical Support and they could not find why > > it happens. I think it is because the request terminates(normally? or > > abnormally? - cannot tell!) before ending the (Visionware's) server > > process. (The server process spawns the sqlexec process). This only > > happens MOST of the time, not ALL of the time. The only thing I could do, > > is to periodically check for the Visionware server process and have my SA > > do a kill -9 on them. > > > > Since, I am getting pretty sick of doing this and SCO (they own > > Visionware SQL-Retriever) does not want to help us, I will be moving > > Openlink's ODBC drivers. During my testing of Openlink ODBC drivers it > > appears that orphaned processes do not happen! > >