RE: QRPLOBJ

["Reger, Bill" <breger@xxxxxxxxxx>]

The only reason I can think of that might cause a programmer to move the old
objects to QRPLOBJ when new objects are promoted to production is for object
archival reasons.  Since you said you are archiving the previous source
members, there really is no particular reason to archive the old objects
also.  You can always recompile from the old source members if a "backout"
situation arises.  The only "real" use for QRPLOBJ is where an object is "in
use" and OS/400 handles this situation for you.
 
William K. Reger
Senior Project Manager
Levitz Furniture Corporation
Phone:  (561) 994-5114
E-mail:  breger@levitz.com <mailto:breger@levitz.com> 

                -----Original Message-----
                From:   Allen Overeem [mailto:AOvereem@stvgb.org]
                Sent:   Wednesday, January 19, 2000 8:05 AM
                To:     MIDRANGE-L@midrange.com
                Subject:        Re: QRPLOBJ

                Laurin,
                Test and production  are on one and the same machine;
production is a library; pgmrs have test libraries; V4R4.  
                The move process (which is only done when all users are off
and all other production jobs are ended) moves the program object and source
code from the test lib to production lib; if the pgm exists in production,
it is forced to QRPLOBJ; the old source is also moved to Archive lib at this
time.  
                 pgm obj in use appears to be one in production (even in
wrkactjob-call stack) but in fact is not?  The old program object exists
nowhere else but in QRPLOBJ lib and seems to be the object running!  We have
only noticed this strange behavior since upgrading to v4r4 just a week
before y2k.  Could the force to QRPLOBJ be causing this?
                 The programmer who created the move process is long gone so
I cannot ask him why he included the force to QRPLOBJ- it seems to me that I
could remove that logic without a hitch, but it is difficult to test in test
area.  Why might this logic have been included?
                Thanks!

                Allen L. Overeem
                Information Services
                St.  Vincent  Hospital
                Phone: (920) 431-3111
                E-mail: aovereem@stvgb.org

                +---
                | This is the Midrange System Mailing List!
                | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
                | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
                | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
                | Questions should be directed to the list owner/operator:
david@midrange.com
                +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---