MKS Implementer 2006 Administration Guide

Rules and Actions
2 Plan and perform any required training (pilot installations can be used for this purpose).
3 Configure MKS Integrity for any remaining changes:
a) Workflow, fields, and types.
b) Enroll users (non pilot users).
4 Perform the conversion.
a) Secure a backup of the Implementer and MKS Integrity databases.
b) Issue the Convert DT to MKS Integrity (ICVTDT) command for each group of DRs
and SRs requiring conversion.
c) Perform any additional MKS Integrity setup changes.
d) Verify the set up by using the Implementer and MKS Integrity functions for check
out and promotion.
e) Begin using the new features.
Example of a Basic Conversion
The following tasks illustrate the steps required to perform and complete a typical data
conversion.
1 Issue the following command to run the conversion and generate the initial conversion
properties file:
ICVTDT MODE(*EDIT) TYPE(*BOTH) DFTCRTUSR(CVTUSER)
A message confirms the file was generated and the location of the file.
NOTE To generate a new conversion properties file, delete or rename the existing file.
2 Define the mappings from DesignTracker values to MKS Integrity fields and values.
In the conversion properties file, modify the field and value settings using any
desktop ASCII editor, such as Notepad. For details, see “Generating and Configuring the
Conversion Properties File” on page 441.
3 In MKS Integrity, set up any new types, fields, or field values that will be used for
DesignTracker DRs or SRs.
4 From the Work with Design Requests and/or Work with Service Requests functions, use
F17 to subset the list of requests to convert.
5 Edit the conversion settings by issuing the following command:
ICVTDT MODE(*EDIT) TYPE(*BOTH) DFTCRTUSR(CVTUSER)
437