When PTF is applied - say a program object is replaced - the old object is
moved to QRPLOBJ.
In this way jobs which were using old program will continue to use it.
Deleting a program when some job is executing instructions from this
program, will cause the job to fail.
This is why PTF process uses QRPLOBJ.
It is safe to clear QRPLOBJ at IPL time, because there are no jobs using
any object from QRPLOBJ.

Earlier in this thread Tom Liotta said that you should be careful what you
remove from QRPLOBJ - very true.

Best regards
    Alexei Pytel

"The better is the worst enemy of the good"





                    "Walden H.
                    Leverich"                 To:     "'midrange-l@midrange.com 
'"
                    <WaldenL@TechSoftIn        <midrange-l@midrange.com>
                    c.com>                    cc:
                    Sent by:                  Subject:     RE: CLRLIB QRPLOBJ?? 
(was Re: IPL
                    midrange-l-admin@mi        regains storage.......but)
                    drange.com


                    08/25/2001 04:58 PM
                    Please respond to
                    midrange-l





Neil,

Are you saying that the objects needed for RMVPTF are stored in QRPLOBJ? If
so I don't believe that is correct for two reasons.

First, if you look very early in the SCPF job joblog you'll see message
CPC2199 from QLICLLIB stating that "Library QRPLOBJ Cleared." This message
is from the CLRLIB command (well, ok from the CPP). I doubt the CLRLIB
command skips the PTF objects in QRPLOBJ. Secondly, I believe all PTF
objects are renamed to QPZA* in QSYS, take a look, you probably have a ton
of them.

-Walden

-----Original Message-----
From: neilp@dpslink.com
To: midrange-l@midrange.com
Sent: 8/24/2001 11:38 PM
Subject: RE: CLRLIB QRPLOBJ?? (was Re: IPL regains storage.......but)

What you are seeing are the objects that would be used if you ran
RMVPTF.
As you are permanently applying the PTF's these objects are no longer
needed, and can be cleared.

...Neil





"Chuck Lewis" <clewis@iquest.net>
Sent by: midrange-l-admin@midrange.com
2001/08/24 22:08
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Subject:        RE: CLRLIB QRPLOBJ?? (was Re: IPL regains
storage.......but)


I would definitely agree with this statement Tom.

With my perm applying PTF's to free up disk space and prep for an OS
upgrade, I saw MANY PTF related objects created in QRPLOBJ and I would
be
very leery of blowing these away...

I had never noticed this in QRPLOBJ before but had noticed the usual
program
or display file objects due to compiling stuff in use at the time...

JMHO,

Chuck

Tom wrote:

<As has been mentioned elsewhere on this list, a CLRLIB of QRPLOBJ can
be
trouble. Objects should not be removed from QRPLOBJ unless you know what
they are. The system does some of its own work through this library and
can
be disrupted if some of its objects disappear.

On most days at most sites, there's probably no problem. But blanket
CLRLIB
should be avoided.

Tom Liotta>




_______________________________________________
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
_______________________________________________
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







As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.