Re: qdcpobj1 & 2

As far as I know, this decompression happens only after installation and
only if space available in system ASP is above certain limit.
This was done to avoid slow-downs when object is first touched - and you
guessed already that on a freshly-installed OS almost every object will
cause this delay.
After that you are free to control, what to compress/decompress
(CPROBJ/DCPOBJ commands).

    Alexei Pytel
speaking only for myself




                      "Leif Svalgaard"
                      <leif@leif.org>           To:       
<midrange-l@midrange.com>
                      Sent by:                  cc:
                      midrange-l-admin@m        Subject:  Re: qdcpobj1 & 2
                      idrange.com


                      02/25/2002 05:32
                      PM
                      Please respond to
                      midrange-l





To: <midrange-l@midrange.com>
>
> They're decompressing objects.  If your situation is like mine, it's
> happening after installing OS/400 -- apparently the objects are installed
in
> compressed format and these jobs decompress them for better response.
>

The "evil empire" strikes again :-) trying to sell more DASD, eh?
It used to be that objects were only uncompressed the
first time they were used. Very sensible, but maybe some
people complained about mysterious "slow downs" at
random times.




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