MKS Implementer 2006 Administration Guide

Implementer and MKS Integrity Integration
3 In the MKS Integrity User ID field, specify the name this user logs on with to access
MKS Integrity. This user ID is also used for source archiving in MKS Source when
MKS Source archiving is enabled. The user ID must be set up in MKS Integrity and/or
MKS Source before defining it here. The field entry is case sensitive. Valid entries are as
follows:
*USRPRF: The iSeries user profile defaults as the MKS Integrity user. This is the
default value. iSeries user profiles are specified in all upper case. If the name
specified in MKS Integrity is not all upper case, retype the name using the exact case
as that used in MKS Integrity.
Name: Specify the valid MKS Integrity user ID.
*NONE: The user is not authorized to access MKS Integrity.
4 In the MKS Integrity emergency update field, specify if this user has authority to activate
and de-activate the MKS Integrity emergency update mode and perform emergency
updates. Allows the user to change the value of the MKS Integrity Emergency Update
Active field on the Change User defaults panel, which is accessible from Work with
Users using option 20=User Defaults and from the Workbench using F18=User Defaults.
Y: The user has authority to activate the emergency update mode.
N: The user does not have authority to activate the emergency update mode.
5 Press ENTER to update the user profile.
NOTE When activating emergency mode as described in “Emergency Update
Mode” on page 255, the authorized user must sign off the iSeries and sign on again.
When the authorized user accesses Implementer, a message displays at the bottom
of the menu to confirm the emergency update mode is active.
Environment Setup
If the environments for this integration already exist and you have already configured the
state setup, depending on your workflow you may not need to perform the following
additional environment setup tasks.
Implementer allows you to control whether an issue is required when checking out from
a production environment. This allows you to enforce rules that define how a member
that is checked out from the environment can subsequently be rejected and promoted
throughout the development cycle.
237