MKS Implementer 2006 Administration Guide

Implementer Software Owner MWIPROD
Environment Repository Build
Implementer includes the user profile MWIPROD. This user profile has security
administrator rights to set up Implementer and owns most of the objects in Implementer.
MWIPROD typically does not have capabilities to the environments in Implementer. MKS
recommends you define a user profile other than MWIPROD to serve as the administrator;
however, this profile should not have specific authorities to the environments.
NOTE MKS recommends you set the MWIPROD profile to bypass expiring the
password. To do this, issue the CHGUSRPRF command with parameter value
PWDEXPITV(*NOMAX).
Security Officer
MKS recommends you use the default user profile in the event that access is accidentally
denied to other users in the system. The IBM-shipped security officer user profile QSECOFR
has security administrator rights to administer Implementer.
The security officer typically does not have capabilities to the environments in Implementer.
MKS recommends you define a user profile other than QSECOFR to serve as the
administrator. Again, this profile should not have specific authorities to the environments.
NOTE Any of these user profiles can be group profiles; however, if a specific user is
a member of a group but not enrolled under a separate OS/400 profile, the user has
the same rights as those defined for the group profile.
Environment Repository Build
The Build List function, also called the “build”, loads source and object, and object code
information from an environment’s set of libraries into Implementer’s environment
repository. The repository provides a productivity aid that allows you to select members and
objects from lists rather than having to manually type each name in the check out and create
request functions. In addition, Implementer uses the repository for impact analysis to
determine the source of related objects across environments.
You can create the environment repository by using any of the following build types:
*ALL processes all member/object types including related objects. By using additional
parameters you can control whether to show build objects in the report, retain existing
valid object codes, add new member/objects, remove records for items that no longer
exist in the environment libraries, or completely clear the repository and rebuild it from
start.
*IFS processes IFS object only. This is useful when an environment has been actively
managing traditional member/objects, and you add new IFS objects.
117