Re: Compress Object command

In my previous job I used the CPROBJ command on a regular basis on all of 
the user libraries because I was short on disk space and there was no 
money for adding disks.  It worked very well for me.  I did use either 7 
or 14 for the DAYS parameter (it's been 9 years, so my memory is a little 
fuzzy).  That may be a little extreme for your situation, but I would 
suggest you consider something less that 90 days, maybe 30.  If you have 
the horsepower in your system, you will not notice any performance 
problems when a compressed object is used for the first time.

I did try using the OBJ(*ALL/*ALL) parameter once, and it appeared to be 
making a significant difference in disk utilization.  The problem with it 
is that it cannot compress any object that is in use and it waits for a 
time-out on every one of them before moving on.  It therefore is rather 
slow on the system libraries.

Thank you,
Ronald L. Zimmerman
I.T. Applications Manager
Swiss Valley Farms, Co.      http://www.swissvalley.com
"Farmer Owned with Pride"
Email: Ron-Zimmerman@xxxxxxxxxxxxxxx

midrange-l-bounces@xxxxxxxxxxxx wrote on 12/01/2006 09:34:22 AM:

Early this week I had asked about using the CHGPGM command to remove
observability and compress program sizes that all responders said to
forget about. One mentioned using the Compress Object CPROBJ command to
save on space usage and speed up backups. Is anyone using this command
on a regular basis to reduce the size of objects that can be compressed
that only get used infrequently like year-end processes? If you do run
it do you only compress your own objects or do you do a system wide
compress? 

I am considering running this CPROBJ OBJ(*ALLUSR/*ALL) OBJTYPE(*ALL)
DAYS(90) every week end when system use is low.  Or would CPROBJ
OBJ(*ALL/*ALL) OBJTYPE(*ALL) DAYS(90) be a better choice.

I did a test on our development library which has 2,915 objects. 2,901
were scanned by CPROBJ, 464 were able to be compressed and space usage
for the library went from 3,924,838,912 down to 3,833,350,656. Not a big
change.  But, of the 464 objects that were compressed space usage went
from 150,269,952 down to 58,781,696. Not bad. 

Mike Cunningham
CIO
Pennsylvania College of Technology
www.pct.edu
mcunning@xxxxxxx
-- 
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.