Re: Program won't let go of QRPLOBJ

As I now understand QRPLOBJ, all programs are placed there when recompiled. (I used to think just programs actually in use were placed there-- but I was wrong)

If you delete the program from QRPLOBJ, I agree that you'll get that "I would have sworn that this pointer pointed to a real program" error.

But if you perform the same trick with a subsystem's routing program, the subsystem -will- re-resolve the link on the fly!

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx



At 5:25 PM -0500 1/11/11, Jon Paris wrote:

On Jan 11, 2011, at 1:57 PM, midrange-l-request@xxxxxxxxxxxx wrote:

Is it safe in a production setting to delete the moved old object in
QRPLOBJ? I suppose if it is actively in use, no, it'd crash. But if it
is idle, say, with a CGI server job, will the job pick up the new object?

"Safe"? No - the job will crash I suspect because otherwise why would the system have put it in QRPLOBJ in the first place? It is placed there so that any currently resolved pointers to it remain valid. Remember its address doesn't change when it "moves" from its original library - its description is simply moved to a different library. More to the point, deleting it won't cure anything so why would you bother?

It is not actually coded this way but it helps to think that the generated code in your program has a test in front of each call to check if the target pointer has previously been initialized. If it has not then the program pointer is resolved. If the pointer has been resolved then there is nothing (short of reinitializing the program) that will cause it to re-resolve the pointer.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com