Re: Promote programs into production -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On 29-Jul-2015 18:46 -0600, Justin Taylor wrote:

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?

The REPLACE(*YES) processing needs the same /exclusive lock/ as any other methods. Thus no matter whether the CRTxxxPGM REPLACE(*YES) is used, the RNMOBJ and optionally MOVOBJ is used, or the Rename and/or Move Object (QLIRNMO) API is used, the program object typically can be locked exclusively during that processing. The reason these operations typically function without a lock conflict, is because a called program is not allocated in order to have been activated; only an explicit lock [e.g. by the application] will prevent others from obtaining the lock required for the rename and move operations.

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.