MKS Implementer 2006 Administration Guide

Appendix B: Environment Examples
424
The following table describes how to define an environment for remote production.
Field Description
Environment Specify the environment name. It is helpful to design a recognizable
naming convention, for example, RMTSYS1.
Description Specify a brief description of the environment, for example, Remote
Production # 1.
Administrator Specify the Implementer administrator.
Env type Specify the type of environment, *PRD (production), *QAC (quality
assurance), or *TST (development).
Library defaults
Specify the program library, files library, source library, and archive library names.
Library Owner,
Object Owner
Applies to new objects created in Implementer, when you run Reset
Authorities for an environment.
Archive Versions Specify the number of archive versions to keep (up to 99 versions).
Create request defaults: CHG field
Yes. The Chg field parallel to the next four fields controls whether you can change the corresponding
field values when working in this environment.
Compile required No.
Auto submit in create rqs Yes. Allows automatic promotion of a promotion request to 1 of 4
levels: compile, distribute and move, or export if a LANSA
environment.
Submit through step 4 (automatically promotes through the Move step).
Add related objects to rqs Yes. Automatically adds related objects to a promotion request.