Re: 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?

Our current CMS moves the existing object to an archive library and then
installs the new object. That works for programs. Display files require a
more manual process. You could use the library thing that some others have
previously mentioned, but I don't know how you'd ever get rid of the
temporary copy if everyone is using it. An alternative to the second
library is to install a copy of the display file named differently, and at
the same time, install a version of the program that references the newly
named display file. After everyone has moved to the new version of the
program, you need to repeat the process of replacing the original display
file with the new version and updating the referencing program to match.
Finally, you can delete that temporarily installed display file. I use
calendar entries to remind me of the steps I need to perform, because you
can't do them all at one time if there are locking issues.