Re: QRPLOBJ Clean Library.

Thanks. I get it....

PRTDSKINF shows QRPLOBJ as 2.83% Third highest % on the system.



On Mon, Apr 11, 2016 at 2:56 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

<snip>
It does appear that 4.3 GB is large to me, but not to the system. Less
than 1% on ours.
</snip>

<snip>
I'd start with RTVDSKINF and PRTDSKINF.
</snip>


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Michael Schutte <mschutte369@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/11/2016 02:48 PM
Subject: Re: QRPLOBJ Clean Library.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Yes I understand. The program objects never get a lock on them. That's
why
IBM says to never touch them.

However, if everyone has signed off. These program objects that were
replaced from our development and Q/A libraries should be safe to remove,
don't you think?

It does appear that 4.3 GB is large to me, but not to the system. Less
than 1% on ours.

I don't like the idea of running CLRLIB. That seems dangerous. I simple
want to remove the ones that were put into QRPLOBJ from our dev and qa
libraries. A lot of the objects were promotes to QA, checked back out,
changed and promoted back to QA. Just seems like a waste. Difference
between 85% and 84% usage.

On Mon, Apr 11, 2016 at 2:26 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

"Large" is in the eye of the beholder. Some might consider 4GB a

rounding

error
System ASP . . . . . . : 3523 G
% system ASP used . . : 75.8769
This is just our development lpar.

I'd start with RTVDSKINF and PRTDSKINF.

However, in answer to your question, I would "guess" that if there's no
object on it you should be able to delete it. But you can test this.

Open

a program with a screen, let's call it ORD500 and the screen name
ORD500FM. Leave it open. From another job modify both the screen and

the

program. The "old" versions should be in QRPLOBJ. See if the job with
the open ORD500FM screen has a lock on it. You want the lock as that is
your safety check to see if it's safe to delete it. If the program

never

locks it but just uses it then I hope you can see how it might be risky

to

clear that library out. If, however, it leaves a lock on it then you
should be able to safely clear out all the objects in that library

without

a lock.
Understand?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Michael Schutte <mschutte369@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/11/2016 02:09 PM
Subject: QRPLOBJ Clean Library.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I know there's been discussions in the past. But I just wanted to get
verification that I'm good to do this.

Our development partition is used by maybe 10-15 people. We sign off
everyday. We rarely do we do an IPL. Rarely, do we work weekends. I

could

ask for it to IPL every weekend. But short of doing that I was thinking

of

creating a program.

1. Get a list of objects in QRPLOBJ, save to a file
2. Read the file, scanning for the library of the original object in the
object description field
3. If library is one of our development libraries and the last used date
is
more than a day ago delete the object from QRPLOBJ.


Our QRPLOBJ is quite large mainly from the recompiles and promotes

within

our development libraries and Q/A environments.

Looks like it's 4.3 Gigabytes.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.