MKS Implementer 2006 Administration Guide

Chapter 6: Third Party Integrations
306
Type/Name order. If a match is found in the target model, the program tries to make the
object PRD (if it is not already). If any other version in the group is PRD, the attempt
fails, the information is written to a report, and processing continues. The result is the
first version in a group, alphabetically, set to PRD.
If the wrong version is flagged as the production version, you have to make manual
changes. Use the Associate Production Model Report to identify which objects to correct.
For each object, change the version that was set by the YASCPRDMDL command to
DEV, and set the version to production. The Work with Versions (YWRKVSN) and
Change Model Object (YCHGMDLOBJ) commands can be useful for this.
Example 2
You have a development model and traditional production library, and you want to
implement change control and establish a production model.
1 If the production library in your existing system was generated from your development
model, you have two options. You can define a separate environment for the existing
3GL production library, or you can create a new model library and define its generation
library as the existing 3GL production library. Either solution works, but the first
solution has overhead of both extra promotion steps and extra disk space requirements.
2 For either situation, you must identify the objects in development that constitute the
objects in production. If you already have Implementer as your change control system,
this is not necessary since the production version types are already set.
To identify the production objects in your existing development model, either:
Use the Start Change Control (YSTRCHGCTL) command, particularly if your
existing promotion system places permanent locks on those objects promoted to
production (set the version type to *BYLOCK).
Alternately, follow these steps if the production flags have not been established:
Issue the YBLDMDLLST command to create a model list of all the non
versionable objects in the model, in other words, exclude functions and
messages. Do not include Implementer-supplied objects.
Issue the Execute Model Object List (YEXCMDLLST) command to call change
model object (YCHGMDLOBJ) for each list entry, and change the version type
of the objects to production (*PRD).
Create a model list of all functions and messages, excluding those supplied by
AllFusion 2E (versionable objects). For each object, include only the version in
production. Do not include more than one version for a group, as it causes an
error in the next step.
Generate the YEXCMDLLST command as before for the non versionable
objects. An error occurs if you attempt to set more than one version in a group
to production.