MKS Implementer 2006 Administration Guide

Appendix B: Environment Examples
Local Production
418
The following table describes how to define an environment for local production.
Field Description
Environment Specify the environment name. It is helpful to design a recognizable
naming convention, for example, AR_PRD.
Description Specify a brief description of the environment, for example, Demo 1
Production.
Administrator Specify the Implementer administrator profile.
Env type Specify the type of environment. Valid options are *PRD (production),
*QAC (quality assurance), and *TST (development).
Library defaults
Specify the program library, files library, source library, and archive library names. If the libraries do not
exist, Implementer automatically creates them when promoting a request to the environment. The
library owner is the user profile defined in the Lib owner fields.
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 fields
The Chg field, parallel to the next four fields, controls whether you can change (override) these values
when creating a promotion request that targets this environment. Specify Y to allow overrides.
Compile required Yes. Allows auto submit in create request.