|
What about moving objects to MYRPLOBJ instead (a user library you would create)? You would have total control over that library and be assured OS/400 won't interfere with it. Your move/compile program then can make decisions about the objects there. You might want to alter your startup program to CLRLIB MYRPLOBJ. Loyd > -----Original Message----- > From: Allen Overeem [SMTP:AOvereem@stvgb.org] > Sent: Friday, 28 January, 2000 2:15 PM > To: MIDRANGE-L@midrange.com > Subject: RE: QRPLOBJ Library > > Lurton wrote: > ____________________________________________________________ > If you compile an object (pgm) with replace yes, it will create a > duplicate > of the object in QRPLOBJ with a strange name like Q34578ikl. The original > object name will be in the text. So, if a program is running and you > recompile, the old program will still be in the job stack until the user > ends the program. The next instances will always get the new program > because the rename process prevents them from calling the old. > __________________________________________________________ > > Thanks but this is totally unrelated to the situation I am describing. > First of all, the program to be moved or recompiled is NOT running! > Second, we are forcing the object into qrplobj with a cl movobj command > within our inhouse software program that we use to do moves and > recompiles. The name is not being changed, there is no Q appended by the > system-this is inhouse software forcing the "move" of the existing object > with the same name to qrplobj just before moving the new object into > production. What I need to know is what the OS might do with the object > because of this force?? Is it possible that there is a change in the OS > between release 2 and 4 (which we upgraded to just before seeing this > strange behavior) that might cause problems resolving to the "correct" > object?? Thanks anyway. > > +--- > | 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.