MKS Implementer 2006 Administration Guide

Chapter 3: Implementer Administration
86
Field Description
Add related objects
to rqs
Field Description
Specify whether to add related objects to a request before promotion.
Ensures objects are promoted without level checks in production. For
example, when promoting a physical file or display file, all programs that
reference the PF or any related LFs are added to the request before the
compile step with an action of 9 for Recompile. Implementer uses the
source in this environment to recompile the program against the changed
physical file, thus avoiding the possibility of a level check.
When a request targets multiple environments, the derived related objects
are based on the primary environment. If this environment is a secondary
environment for a request, the related objects are added based on the
value of this field in the primary environment, not this environment.
Y: Adds all related objects to the request. This is required to add related
objects from the development path without locking the objects. For
details, see page 72.
N: Bypasses related object processing. For physical files, Implementer
adds the logicals to the request even when N is specified.
Create Environment Field Descriptions: Panel 2
Create Request options
The following fields define additional defaults for the environment.
Check out required Specify if users must check out a member/object in this environment before
it can be placed on a promotion request.
Y: Check out is required.
N: Check out is not required.
Allow authority
overrides
Create Environment Field Descriptions: Panel 1
Specify if users can change the authority method of this environment when
creating a promotion request.
Y: Authority method can be changed.
N: Authority method cannot be changed. All moves into the environment
use the default authority method defined for the object code.