MKS Implementer 2006 Administration Guide

Chapter 3: Implementer Administration
118
*REL processes related objects only. It updates the repository to show the environments
where related objects exist.
For more information on build types, see “Build List (IBLDMBOLST) Command Parameters”
on page 119.
The build generates the Environment Build Report, which provides member/object status
and information on errors and warnings that occurred during the build. You can use this
report in place of the job log or user message queue for troubleshooting errors with the build.
For details, see “Environment Build Report” on page 121.
Key Considerations
You must have authority to host environment maintenance to run the build for a host
environment, and authority to remote environment maintenance to run the build for a
remote environment. These authorities are defined in Work with Users.
The environment’s program library, file library, and source library must exist or the
build ends in error.
You can run the build from an option in Work with Environments or by using a
command interface.
In Work with Environments, the Build List field confirms the repository status for an
environment.
For each *PRD and *QAC environment in Work with Environments, specify to maintain
related object information and specify the source of information. This is not required for
development environments.
If you use related objects in check out or create request, you must run the build for each
new *PRD and *QAC environment to create the initial list of member/objects in the
environment.
Once you create the member/object list and the environment/libraries are handled by
Implementer, the member/object list is maintained dynamically. You can rebuild the list
for maintenance purposes at any time, for example, if you edit object codes that support
source and object with different names.
If multiple object codes exist with the same characteristics, the object code with the
lowest sequence number is selected by the build when the Retain Object Codes value is
set to *NO. This gives better control over which object code is selected for the
environment.
Changing the sequence number of an object code may change the compile sequence of
members/objects in Compile Request.
The build does not assign object codes used to change the characteristics or data of an
existing object. This applies to any object code defined with creation process M or a
special characteristic beginning with “*”. For example, the build does not assign the
object codes PFDTA, PFCHG, and MRGMSGF.