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.

Field Description<br />

Environments<br />

Archive library Specify the library to contain the archived versions of source/objects. Only<br />

required when archiving objects. You must specify a library name to add<br />

the number of versions in the Archive versions field.<br />

AS/SET definitions and generated traditional objects are managed<br />

independently and require separate archive locations for traditional objects<br />

and definitions.<br />

The value *CALC applies to primary release management environments.<br />

For details, see the <strong>MKS</strong> <strong>Implementer</strong> <strong>2006</strong> Release Management <strong>Guide</strong>.<br />

Create Request defaults<br />

The following fields define the default values when creating a promotion request for this environment.<br />

The Chg field defines whether the user can override the default value when creating a request.<br />

Compile required Specify whether to compile all source-based objects using the Compile<br />

Requests function before moving the objects into this environment. Ensure<br />

the objects compile with the correct library list.<br />

Y: Objects compile before the move.<br />

N: Bypasses the Compile Request function. After creating a request,<br />

you can move the objects into this environment using the Move<br />

Requests function. Use this option for AS/SET definitions and LANSA<br />

objects.<br />

Auto submit in<br />

create rqs<br />

Create Environment Field Descriptions: Panel 1<br />

Specify whether to automatically submit the promotion when creating a<br />

request.<br />

Y: Promotions automatically submit.<br />

N: Promotions are held. To promote the request use: Compile Request,<br />

Move Request, or Move Requests by System/Environment.<br />

Through step Specify how many steps of the promotion to perform when auto-submitted<br />

from Create Request. Each subsequent step includes the prior step, for<br />

example, compile includes model copy, distribute includes model copy and<br />

compile, and move includes model copy, compile, and distribute. If using<br />

promotion scheduling, it is performed for the last step specified as the<br />

submit through step.<br />

1=Export: Valid only for LANSA environments. Exports LANSA objects<br />

on the request to a save file. Verify successful completion of the process<br />

by manually reviewing the export reports generated by LANSA.<br />

2=Compile: Valid only when Compile required = Y.<br />

3=Distribute: Valid only for remote environments.<br />

4=Move: No special edits.<br />

85

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

Saved successfully!

Ooh no, something went wrong!