|
Make sure this is current
Information collected . . . . . . . . . : 04/07/16 04:00:00
Have you tried
PRTDSKINF RPTTYPE(*LIB) OBJ(*ALL) MINSIZE(99999)
Post all of this
% of Size in
Description Disk 1,000,000 bytes
User libraries 13.44 60136.54
User directories 15.81 70717.18
Folders and documents .00 .11
QSYS 2.46 10987.12
Other IBM libraries 2.68 11993.19
Licensed Internal Code 1.56 6958.15
Temporary space 3.08 13783.64
Unused space 60.85 272254.30
System internal objects .07 302.03
Objects not in a library .00 .00
TOTAL 99.95 447132.26
As you can see here I should be spending more time in "User directories"
than in "User libraries". (Domino lpar)
This lpars biggest libraries and objects are:
Library/ % of Size in Last
Object Type Owner Library 1000 bytes Change
QPFRDATA *LIB QSYS 36005826.6 04/07/16
Q095000021 *MGTCOL QCOLSRV 18.17 6543913.0 04/04/16
Q094000021 *MGTCOL QCOLSRV 18.13 6527135.7 04/03/16
Q096000021 *MGTCOL QCOLSRV 18.03 6493581.3 04/05/16
Q097000021 *MGTCOL QCOLSRV 18.03 6493581.3 04/06/16
Q093000021 *MGTCOL QCOLSRV 17.99 6476804.1 04/02/16
QAPMJOBMI *FILE QCOLSRV 4.01 1442500.6 04/07/16
...
QSYS *LIB QSYS 10968910.3
Q890F10068 *JRNRCV QSYS 14.03 1539407.9
Q890F10063 *JRNRCV QSYS 14.02 1538359.3
Q890F10065 *JRNRCV QSYS 14.02 1538359.3
Q890F10067 *JRNRCV QSYS 14.02 1538359.3
Q890F10069 *JRNRCV QSYS 10.71 1175228.4
Q890F10064 *JRNRCV QSYS 8.42 923570.2
Q890F10066 *JRNRCV QSYS 4.59 503681.0
ROUTINES *LIB ROB 9852145.7
...
QAEZD0008O *FILE SSA 2.69 265367.6
QAEZD0009O *FILE SSA 2.69 265367.6
QAEZD0010O *FILE SSA 2.69 265367.6
QAEZD0011O *FILE SSA 2.69 265367.6
Basically all systems stuff.
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 03:24 PM
Subject: Re: QRPLOBJ Clean Library.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
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>remove,
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
don't you think?simple
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
want to remove the ones that were put into QRPLOBJ from our dev and qano
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 arounding
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
withobject 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 namethe
ORD500FM. Leave it open. From another job modify both the screen and
program. The "old" versions should be in QRPLOBJ. See if the job
isthe open ORD500FM screen has a lock on it. You want the lock as that
riskyyour safety check to see if it's safe to delete it. If the programnever
locks it but just uses it then I hope you can see how it might be
to<midrange-l@xxxxxxxxxxxx>
clear that library out. If, however, it leaves a lock on it then youwithout
should be able to safely clear out all the objects in that library
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
thinkingDate: 04/11/2016 02:09 PMcould
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
ask for it to IPL every weekend. But short of doing that I was
ofthe
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
dateobject description field
3. If library is one of our development libraries and the last used
listiswithin
more than a day ago delete the object from QRPLOBJ.
Our QRPLOBJ is quite large mainly from the recompiles and promotes
our development libraries and Q/A environments.list
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
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
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.