Re: QRPLOBJ Library

Peter wrote:
If your process
moves the production object to QRPLOBJ, and recompiles the new version, the
recompilation would not move anything to QRPLOBJ because you already did. Is
that correct?
__________________________________________________________

No. The move process does move current object to qrplobj after deleting any 
object in that lib by that name.
The recompile process does the same.  Really, the only difference between our 
move process and our recompile process is that during a move, the test object 
is moved to production with the movobj command.  In the recompile process, the 
production source is recompiled using crtclpgm or crtcblpgm after the existing 
production object is put to qrplobj with the movobj command. 
I appreciate the response. I have since removed the move to qrplobj from both 
processes. It seems pointless to save the production object when the source is 
already saved. The guy who wrote the procedures was very good, however, and he 
must have had his reasons. I was hoping someone more knowledgeable than me 
could help me figure it out. I am also wondering if this change will solve the 
problem we have been having since the upgrade from V4R2 to V4R4. I cannot seem 
to convince list members that the production object is not running when the 
move takes place, which makes for wasted chatter. Our moves are done after the 
users have been removed from the system, the subsystems (including batch) have 
been taken down,  backup has been run, subsystems (not users) brought back up.
Thanks again. 


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