MKS Implementer 2006 Administration Guide

Implementer and MKS Source Integration
If a based on environment is specified, the based on product/version/release specified
in the associated product/version must have a product/version/environment with the
same environment name as the based on environment specified in the target
environment.
The based on product version environment must be archived in MKS Source to provide
the starting revisions for the new environment’s population.
You must enable environments in a specific order to ensure the production environment
is assigned lower revisions than those assigned to items in QA environments. First,
enable the production (*PRD) environment and then enable the quality assurance
environments (*QAC). If you have multiple *QAC environments, enable them in order
from production toward QA1, for example, QA4, QA3, QA2, QA1, where QA4 is the
environment closest to “going into” production.
The environment population uses Implementer’s repository entries and locks to control
when it assigns new revisions as follows:
When processing a production member, if a based on environment is not specified
or the member does not exist in the based on environment, Implementer performs
an MKS Source check in to assign the initial revision ID.
When a member exists in a based on environment, Implementer uses the based on
member’s revision to assign the new environment member revision.
When processing a member from QA and a lock does not exist, Implementer
searches the product/version environment list toward production and uses the
revision from the first environment where the member exists.
When processing a member from QA and a lock exists, Implementer performs an
MKS Source check in to generate a new revision ID.
The following table illustrates the results of processing a member.
Environment Sequence Number Lock Assigned Revision Assigned
PRD 10 N 1.1
QA4 20 N 1.1
QA3 30 Y 1.2
QA2 40 N 1.2
QA1 50 Y 1.3
287