Re: Closing OnLine session (2)

At 08:35 AM 5/14/97 -0700, you wrote: >>The Plan : >>My menu programs and database (which are the dormant processes that >>I have targeted) will be under SE, while the >>'action' programs which are activated (RUN 'fglgo ...') from >>the menu program will run under OL. > >Maybe you'd be better off using the 7.x OnLine; you'd then have 1 dormant >program (the menu program) and one dormant thread in the engine, instead of >two dormant programs (the menu program and the sqlexec). This should >reduce the total memory requirement on the system -- all other things being >equal, which they aren't. > Thanks for your reply. Actually, my problem is to do with the OL memory blocked by the dormant menu process. OL never releases this memory (around 150K per user) until the user exits the menu program (at the end of the day when s/he logs out). As expected, the unix sqlexec process (under SE) takes more system memory than the corresponding OL thread. However, the SE method may prove to be advantegeous if the majority of my users change their 'action' programs infrequently thus keeping the menu program dormant most of the time. This would swap out their sqlexec process, keeping the overall usage of memory lower. Obviously, this depends on the profile of my user's actions. I have a beady eye on them!. Bye, Rudy