RE: Promote programs into production

I think the only option you have is to get all users to stop using that program and then do the replace. And I would not do the replace and instead move the current production object to another library in case something goes wrong and you have to move it back. We also just do a compile to production when we want to implement any change that only affects the program. (if you need to also change anything in an "F" spec you will need to wait until all users are out of that program. Way I ask why you want to stop the current process of just doing a compile?

Mike Cunningham

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Wednesday, July 29, 2015 8:47 PM
To: MIDRANGE-L (midrange-l@xxxxxxxxxxxx) <midrange-l@xxxxxxxxxxxx>
Subject: Promote programs into production

Currently, we update production programs by simply compiling from source into the production library. I'd like to move the object from the test library instead. The trouble is, I need an exclusive lock on the production object to accomplish this. We run a 24/6 shop, and I can't wait until Sunday to promote an update. Our current compile method doesn't suffer from this problem (the current object is moved to QRPLOBJ and users are pointed there). Is there some way to replace the production object without the exclusive lock?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.