P
Peter Judge
Guest
PL’s are a good approach in general. If you want to hotfix you could think about dropping the affected rcode into propath ahead of the PLs; there are some threads on Communities about approaches for that (ie folders named for hotfixes etc). If the question is about removing r-code that is memory-resident (ie persistently running or loaded via -q) then you have other things to think about. - For the -q case, you can force r-code to reload using a ASSIGN CURRENT-LANGUAGE = CURRENT-LANGUAGE. statement in ABL. - For the persistent-procedure case, you can read the session’s procedure chain and delete/reload the rcode. - For OOABL and static members, it depends on what’s held and how it was loaded in the first place. In general terms it’s probably better (for the last 2 cases) to start new sessions (and/or agents in AppServer terms). That way you know you had a clean session start (and not a hinky-dinky manual process).
Continue reading...
Continue reading...