Yes, DATABASE RETENTION: ON
I am sure I never set this, but the value came out when I dumped out a Sesame.ini file. So, I suppose this is the default. I will have to read up on this, and make sure I know if I want it ON/OFF.
From User Guide, page 548:
Quote:DATABASE RETENTION: Database retention determines if an application remains
loaded on the server even after there are no more clients accessing that application.
This allows an administrator to preload a set of databases, making subsequent loading
unneeded, both for normal use and for X-Commands. Valid settings are ON and OFF.
ON is the same as using the –keep startup switch.
Example: DATABASE RETENTION: ON
Default: OFF
Hmm, shows default = OFF, so I must have changed it. And now reading this again, it would seem that I do want the value of ON for faster loading. And it may also explain some of the "unknown" applications that I mentioned seeing on Sesame Server in another posting. I think the Server/Client/Standalone operations and settings are starting to come together now.
So many new tools with the INI capabilities, hard to remember them all, and since you look at them once, make the INI setting, it is easy to forget they exist. They are not like programming functions that are used every day. Thanks for reminding me about that one setting. Will need to keep looking at loaded applications.
Since I rename development versions File1, File2, File3, etc. and they all have the same Application name, that is why I may see the same application name in the Server list, they are the names of File1, and File2, still there after I have closed them, and why they are locked. So when they "mysteriously" unlocked later, it was probably because as Admin, I went in and removed the applications. Did not realized this was happening in Standalone mode, as well as Server/Client.
Thanks again.....guess we can mark this one SOLVED from my perspective, but this is not my original thread. But I am satisfied.