In article <MPG.dd137667df27c90989680@news.corp>,
Maestro@post1.com (Maestro) wrote:
> I'm attempting to reduce the number of OnLine sessions in a 100-user
>database application, would like to hear from you on one area which I'm not
>able to figure out.
>
> I have a 4GL program(A) which serves as a main menu. This program(A)
>has a db connection for performing simple read and will run other database
>programs as required by users. In an attempt to reduce the concurrent
>sessions, I tried issuing a CLOSE DATABASE statement in program(A) but this
>particular session still appear in onstat -g ses output. ??
>
> Anyone has any idea why is that so? Is there any other way to close the
>session?
>
It appears that only a DISCONNECT will free a session (Try it out in
dbaccess). Unfortunately DISCONNECT returns a syntax error in 4GL
(because its v6, I suppose). Further, DISCONNECT cannot be PREPAREd, unlike
statements like SET OPTIMIZATION which are not recognized by 4GL but
can be PREPAREd and EXECUTEd.
It does look like it works under ESQL (Why this discrimination?), so
maybe your menu program has to be written in C.
Let me know if you find a 4GL solution to this problem which I face
as well.
-----------------------
Rudy Fernandes
GIC, Kuwait
OL 7.20UC4, 4GL 6.04UC1
-----------------------