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.

Appendix C: Converting DesignTracker Data to <strong>MKS</strong> Integrity<br />

438<br />

6 Resolve all errors reported in the conversion log file. For details, see “Conversion Log<br />

File” on page 435.<br />

7 Run the conversion by issuing the following command:<br />

ICVTDT MODE(*CONVERT) TYPE(*BOTH) DFTCRTUSR(CVTUSER)<br />

8 Review the conversion log file for errors and warnings. For details, see “Message and<br />

Error Handling” on page 435.<br />

9 If the alternate was used to handle undefined values, in <strong>MKS</strong> Integrity, query for issues<br />

that use the alternate values for fields and modify the values as needed.<br />

Convert DT to <strong>MKS</strong> Integrity (ICVTDT) Command<br />

The Convert DT to <strong>MKS</strong> Integrity (ICVTDT) command is the tool that allows you to generate<br />

an initial <strong>Implementer</strong> conversion properties file, validate the entries in the file, and convert<br />

existing DRs and SRs into <strong>MKS</strong> Integrity issues.<br />

The command uses the current DR and SR selection criteria that are applied when subsetting<br />

the Work with Design Requests or Work with Service Requests functions for the user that<br />

issues the command, or the selection criteria of the last report generated by the user<br />

(whichever is most current). This allows you to view and report on the information to<br />

convert. The conversion automatically excludes any items already converted.<br />

The command converts DRs and SRs based on the values defined in the implementerconversion.properties<br />

file that installs in the root directory where the <strong>Implementer</strong><br />

server is installed. Records convert based on the sort order determined by using the DR and<br />

SR summary report criteria. For information on the conversion properties file, see<br />

“Generating and Configuring the Conversion Properties File” on page 441.<br />

The command provides three operational modes, depending on the Conversion Mode<br />

parameter value specified.<br />

Command parameter Conversion properties file status / command action<br />

*EDIT or *CONVERT Creates file if it does not exist.<br />

*EDIT Edits existing file.<br />

*CONVERT Edits existing file. If no errors, converts data.<br />

Create an initial prototype of the conversion properties file by issuing the command with the<br />

*EDIT parameter value, which populates the file based on the data currently defined to<br />

DesignTracker. The property file can be edited using any ASCII text editor. You can issue the<br />

ICVTDT command with the *EDIT parameter value as often as needed to validate the<br />

conversion property file until no errors are reported. When you are ready to convert data,<br />

issue the command with the *CONVERT parameter value.

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

Saved successfully!

Ooh no, something went wrong!