D
dbeavon
Guest
Do you use the -q option to cache your r-code in memory? This is probably what is "holding onto" previous versions of your r-code. If you remove the "-q" then it should automatically pick up changes in your programs, once you've deployed them. In practice I always rely on "-q" , even in development. That is primarily because much of our PROPATH resides on network-attached file server and, without -q, the AVM will spam the network with lots of hits on the underlying program files. As an alternative approach, I rely on a short (10-20 second) PAS timeout to trim out my unused multi-session agent after a brief moment of inactivity. Then I can be sure that PAS will pick up new r-code. See here for more details on those timeout variables: community.progress.com/.../36188 Here are other options for clearing out your r-code: ================ * QUIT statement - in a given pacific appserver session, this should flush the entire AVM session. Beware it may erase the work that you've done in your session startup event procedure. * "r-code trick" - in any session that this is trick is done, it will flush your saved r-code. knowledgebase.progress.com/.../P130577 Hope these ideas are helpful.
Continue reading...
Continue reading...