D
dbeavon
Guest
The docs say that we can use the QUIT statement from within an ABL session in pasoe. OpenEdge 11.7 Documentation This is supposed to simulate the "classic" state-reset behavior. It is done in conjunction with the manipulation of "SESSION:SERVER-CONNECTION-BOUND", which set to true when a connection is made, and false during disconnection. I'd like to use QUIT in order to clear out any memory leakage that may be going on within the ABL session. However we are finding that the performance is awful when running ABL programs on a network file share. It subverts the purpose of the "-q" client session parameter and causes programs to get reloaded continuously (r-code is too large and there are 1,000's of individual programs). It is probably wishful thinking, but does anyone know a mechanism to do the equivalent of a QUIT, but *without* unloading all the cached programs from memory? I'd like it to clear out all persistent procedures, delete static objects, perform GC, and so on. (Or perhaps there is a way to enumerate and delete persistent procedures manually?) Thanks in advance.
Continue reading...
Continue reading...