MKS Implementer 2006 Administration Guide

Change Controlled Models
AllFusion 2E Change Management Integration
The process for enabling a model for change control differs for pre-existing models as
opposed to newly created models. For newly created models, the process is as simple as
creating the model with the Create Model Library (YCRTMDLLIB) command, specifying the
Implementer product library (MKSIM or Y2SYCM) in the change control parameter
(CHGCTL). For established AllFusion 2E models, you have to initialize the version type of all
of the model objects.
To accomplish this, various tools are available for analysis and modification, such as the Start
Change Control (YSTRCHGCTL) and Associate Production Model (YASCPRDMDL)
commands. You must also define the model to Implementer as an AllFusion 2E environment.
Type a model library name on the AllFusion 2E options panel, accessible using option 10
from the Work with Environments panel.
The following examples help to clarify these concepts.
Example 1
You have existing development and production models and you want to implement change
control.
1 Start Change Control (YSTRCHGCTL) command
If your production model is closely synchronized to the changes in development, you
can achieve implementation most easily by using the YSTRCHGCTL command. You
need to specify the set version type (SETVSNTYP) parameter (the possible values are
available in the command help text). The most sophisticated value for this parameter is
*ASSOC, which invokes the Associate Production Model (YASCPRDMDL) command
described next.
2 Associate Production Model (YASCPRDMDL) command
The YASCPRDMDL command compares objects between two models. It matches objects
by Owner name/Object type/Copy name in the development (source) model with the
Owner name/Object type/Object name in the target model. If a match is found, the
object in the development model is set as a production version.
The production model provided to the YASCPRDMDL command should ideally be the
related production environment you define in the CM environment setup. If you do not
have a production model, you can use a QA model instead.
For this approach to be effective, you must achieve development cutoff of all changes,
both functional and database. If functional cutoff is not an option, database cutoff is a
minimum requirement to obtain a predictable result.
You should note how objects are identified between the two models. For non versionable
objects, matching is straightforward because of the one-to-one relationship. For
versionable objects such as the functions, a more arbitrary pairing method could cause
some unexpected results. The program reads the development model objects in Owner/
305