×
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.
-----Original Message-----
From: Mark Murphy/STAR BASE Consulting Inc. [mailto:mmurphy@xxxxxxxxxxxxxxx]
Sent: Thursday, March 02, 2017 8:35 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Percolating QC changes
In the Centralized CMS model typically used in the IBM i environment, you would check out the objects that needed changes, make the changes, and then promote the objects back to QC. If any of the objects that need changes are already checked out, the source for those changes must be saved out somewhere and the objects checked back in first. Then the conflicting development changes can be manually merged back in when the QC changes are completed. This is a common problem with centralized CMS systems like Aldon, Implimenter, and Turnover. This can sometimes be mitigated by each developer having his own development library. Then you only have to worry if the developer has the same object checked out for a different issue. That is easier to manage, but increases the storage requirements significantly.
Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx
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.
midrange.com
