MKS Implementer 2006 Administration Guide

Implementer and MKS Source Integration
4 Complete the fields as required. For MKS Source integration, the relevant fields are
Version, Version Description, Based on Product, Based on Version, Based on Release,
and MKS Source Devpath. For details on this panel, see the MKS Implementer 2006 Release
Management Guide.
Do one of the following:
a) If this is the current version, in the MKS Source Devpath field, type *HEADREV (this is
the starting point for the version, which is used to create the next current release),
and press ENTER.
b) If this is a previous version (not the current version) in the MKS Source Devpath
field type *VERSION.
NOTE The next two steps only apply to the *VERSION development path. The
*HEADREV development path automatically assigns revisions from the main trunk;
therefore, it does not require a development path assigned.
5 To create the *VERSION development path in MKS Source, press F6=Create
Development Path in MKS Source. A message displays requiring you to confirm your
request to create the MKS Source development path for the selected Implementer
product version.
6 To continue, type Y, and press ENTER.
A series of validations ensure you have the required permissions and the development
path can be created. A message displays if the product development path already exists
or if the product version has an open release. Once all validations successfully pass, the
product project is checkpointed in MKS Source with a checkpoint name equal to the
version name, and a development path is created on the checkpoint.
7 Repeat steps 2–6 for each version of the product that requires a development path in
MKS Source.
To create archives for existing previous versions of iSeries source
1 Activate archiving for the product.
2 Activate archiving for the oldest version you want to archive in MKS Source. Specify the
development path *HEADREV.
3 Activate archiving for each environment within the version.
4 Change the version to use development path *VERSION, and create the development
path.
5 Activate archiving for the next oldest version you want to archive in MKS Source.
Specify the development path *HEADREV.
6 Activate archiving for each environment within that version.
285