Re: Q: SE-5.x

>From: Billy Wheeler <billy@west.co.za> >Date: Fri, 18 Oct 1996 11:21:46 +0200 (GMT+0200) >X-Informix-List-Id: <list.11793> > >> I recently started working on SE-5.0 supported on IBM ( all my prio >> experience has been with Online 7.x ). >> I was wondering what command do i use to start and stop the engine >> in SE.5.0. > >You don't. There's nothing to start or stop... Sort of, maybe. Mainly yes, but I'm going to split hairs and argue that there is something to start and stop, but that it happens automatically OnLine 7.x has a set of daemon processes (oninit) which has to be started before anybody can access the database. OnLine 5.x has a similar process (tbinit), and when clients wish to talk to the database, they start up a private server, sqlturbo, which uses the system maintained by tbinit. SE, in all versions, does not have a daemon sitting around looking after the database. Instead, each user starts up sqlexec, a process similar to sqlturbo except that the Unix kernel controls all the interactions between the different sqlexecs running for different users, instead of the (non-existent) daemon. When a program is started, it normally opens a database; this automatically starts a connection to a database server. In 7.x, you have the CONNECT statement as an alternative -- in 5.x you don't. When you open the database, an sqlexec process is started for you. When you close the database, your sqlexec may (or may not) terminate too. If the database was on a remote machine, it will exit; if the database was local, it won't, just in case you want to start using a different database. You can force it to exit with the ESQL/C function sqlexit(). Yours verbosely and pedantically, Jonathan Leffler (johnl@informix.com) #include <witticism.h>