MKS Implementer 2006 Administration Guide

Local Quality Assurance
The following table describes how to define an environment for local quality assurance.
Field Description
Environment Specify the environment name. It is helpful to design a recognizable
naming convention, for example, AR_QAC.
Description Specify a brief description of the environment, for example, Quality
Assurance Env.
Administrator Specify the Implementer administrator user profile.
Env type Specify the type of environment, *TST (development), *QAC (quality
assurance), or *PRD (production).
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 Yes. Members are usually compiled before promoting to a test
environment.
Auto submit in create rqs Yes. Allows automatic promotion of a request to 1 of 4 levels: compile,
distribute and move, or export (if a LANSA environment).
Submit through step 2 (automatically promotes through the compile step).
Add related objects to rqs Yes. Automatically adds related objects to a promotion request.
Check out required Yes. Members/objects require check out before adding them to a
promotion request. You must also check out newly created members/
objects.
Allow authority overrides No. Not allowed to change object authority on a promotion request.
421