RE: CLRLIB QRPLOBJ?? (was Re: IPL regains storage.......but)

Forget about interactive jobs, it's the server jobs you have to worry about.
Those are the ones you don't know if they crash.

Christopher K. Bipes      mailto:ChrisB@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                  http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

-----Original Message-----
From: Walden H. Leverich [mailto:WaldenL@TechSoftInc.com]
Sent: Monday, August 27, 2001 10:16 AM
To: 'midrange-l@midrange.com'
Subject: RE: CLRLIB QRPLOBJ?? (was Re: IPL regains storage.......but)


Actually, I've had an interesting thought on this subject.

Let's say you have a user that is running some job that uses the IBM program
QAWXXPGM (I made the name up.) Now, I go and install a PTF that replaces
QAWXXPGM. To do the replacement it renames QAWXXPGM to QPZ0001 and puts the
new QAWXXPGM into QSYS. Now that user still has the _original_ program in
his stack and if you look you'll see QPZ0001 in the call stack. Now let's
say I then apply that PTF perm. Won't that delete QPZ0001 since it's no
longer needed? What will happen to that user that has it in their stack?
Boom? Maybe that is why objects are moved into QRPLOBJ on an apply perm.
These objects (at least programs) may still be needed by an active job.
However, at IPL it's safe to say they're no longer needed.

As to when it's safe to clear QRPLOBJ, if you clear it at times other than
IPL you may run the risk of blowing up active jobs. If you _know_ that no
one is using those programs, great, but are you sure?