MKS Implementer change management question about losing source code

["Stone, Joel" <StoneJ@xxxxxxxxxxxxxxxx>]

Title: MKS Implementer change management question about losing source code

We lose source code using Implementer, and MKS tells me that it is due to our unique configuration.  To me the config doesn't seem unique at all, but rather the norm.

We have a development box, and several production boxes.  When a program is promoted, only the object is promoted to the production environments, not the source.

Each time a remote operator pulls in his changed objects,  the test source matching that object is written over the master source.

If there are 10 remote environments, the master source is overlayed 10 times, once for each promotion to production at each remote.

A problem occurs when a remote operator pulls in changes out of sequence.  For example,  PGMA ver 1 is promoted, and a week later PGMA ver 2 is promoted.

The remote operator at one division was on vacation that week, and let promotions slip.  When he returns, he accidentally pulls PGMA ver 2 in first.  The next object he pulls in is then PGMA ver 1.

His was the last division to pull in PGMA changes, and the PGMA source on the development box is now one version old, at PGMA ver 1.

The problem may not be discovered for months or years, when the PGMA ver 2 source code is long gone, and no longer matches the object running in 9 out of 10 production environments.

Has anyone else experienced this problem??

Do other AS/400 change management packages allow a remote operator to control source code integrity?