MKS Implementer 2006 Administration Guide

Submit
Specify *YES to submit the job to batch processing, or *NO to run interactively.
Job queue/Library
Environment Repository Build
Specify the job queue and library for the build list. The value *PRODUCT uses the default
output queue and library specified in System Control Maintenance.
Hold on job queue
Specify whether to hold the build list job on the job queue.
*JOBD Uses the value specified in the job description of the user submitting the
job. This is the default value.
*NO The job is not held on the job queue.
*YES The job is held on the job queue.
Common Questions
When do you need to run the build list?
Run the build list for each newly created environment, or if you add source or objects to the
environment library outside of Implementer.
If you create a new member using Implementer, is it necessary to rerun the build list?
No. Implementer automatically updates the list. When you check out a new member with an
action code of 2, Implementer creates a new member.
Environment Build Report
The Environment Build Report generates automatically for the build types *ALL and *IFS.
The report does not generate for the build type *REL. This report is helpful for problem
resolution if errors or unexpected results occur during a build, as it replaces having to use the
job log or user message queue for troubleshooting errors with the build.
The report includes the following information:
general environment information
list of all source members and objects in the environment libraries not added to the
repository, with specific messages for each source member and object
optionally, a list of all source, objects, and object codes loaded into the repository
list of objects in the environment libraries not added to the repository
list of source members in the environment libraries not added to the repository
warnings that occurred during the build for specific related objects
121