Re: QRPLOBJ

Folks,

You have to remember WHY QRPLOBJ even exists. This is key to the whole
thing.

If you delete the program first then everyone who has ran it, and may call
it again, will abort with a nasty message. The job keeps a pointer to
that object. When the object is moved to QRPLOBJ then the pointer gets
changed to that object. If you just delete it you'll get some nasty
pointer not found type message.

What stops the pointer from going to QRPLOBJ? Well, restarting the job
for one.

You have to ask yourself what solution you're willing to take:
- accept the current security failures that the OP was trying to work
around.
- accept the nasty message which may occur when the object is deleted
- modify the security model to accept QRPLOBJ
- severely restrict implementing changes, even those which may fix
critical errors, to system outage times to avoid calls to QRPLOBJ and the
alternative nasty message.
- Rewrite the system that if the security model detects QRPLOBJ then the
called program, and the calling program, work out how to use the new model
(perhaps some combo of LR, etc?).



Rob Berendt