02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 5: <strong>MKS</strong> Integrity Integration<br />

284<br />

Only one version per product can be set to *HEADREV. When multiple versions exist,<br />

you must set all previous versions to *VERSION before you can set a new version to<br />

*HEADREV.<br />

The product version must not have open releases when creating the development path.<br />

A message notifies you if open releases exist.<br />

Before creating a new release of a product, you must close the current release.<br />

To work with product versions and set the <strong>MKS</strong> Source development path for a version<br />

1 From the <strong>Implementer</strong> Menu, type option 51, Products, and press ENTER. The Work with<br />

Products panel displays.<br />

2 Select the product with option 10=Work with Versions, and press ENTER. The Work with<br />

Product Versions panel displays.<br />

3 Do one of the following to display the Product Version Maintenance window:<br />

Type 1=Create on the first option line, and press ENTER.<br />

Select an existing version with option 2=Change, and press ENTER.<br />

Select an existing version with option 3=Copy, and press ENTER.<br />

NOTE If <strong>Implementer</strong> or the product are not set up for <strong>MKS</strong> Source archiving, the<br />

<strong>MKS</strong> Source Devpath field is view-only, and function key F6=Create Development<br />

Path does not display. For details, see “Product Setup and Source Archiving” on<br />

page 280, and “Defining <strong>MKS</strong> Source Values in <strong>Implementer</strong>” on page 275.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!