Re: Program won't let go of QRPLOBJ

Comment in-line

On 1/11/2011 4:25 PM, 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 seems I've solved some confusing debugging by deleting the version in QRPLOBJ. This lets me keep working without signing off and on again. Now I'm in a fairly circumscribed environment - I'd usually be the only one using the program, or it's in use by the HTTP server and I'm pretty sure that I'm the only one really using it from the browser.

Definitely, in production, it would not be safe to do this, as this thread has shown me.

Being in a development box can really skew one's view of things - security and all this are very different for me here, and this has a great bearing on testing.

Just some idle comments at end of day!

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