Closing OnLine session (2)

This is a follow up on the original thread related to closing dormant OL connections. I've attempted using some of the suggestions posted, but they don't work - I think this is because we only have RDS (no ESQL/C or C-compiler and thus, no access to the SQLEXIT() function). I am trying another approach which would be ridiculous as a generalised solution. However, it could just possibly be worth thinking about in sites which have, like mine, recently upgraded to v6 tools and v7 OL. That is, they still have the v4 tools and the v5 SE versions available. The logic : Under SE, the database connnection runs as a unix process (sqlexec). If it lies dormant, it gets swapped out and its memory utilization goes to 0. 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. I've have commenced implementing this starting today and I will be monitoring the daily statistics that we collect to evaluate the effect of this. I will get back to the group with the conclusions I draw. However, I'd be interested to hear comments on the theory behind this approach. TIA. ----------------------- Rudy Fernandes GIC, Kuwait OL 7.20UC4, 4GL 6.04UC1 -----------------------