02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 3: <strong>Implementer</strong> <strong>Administration</strong><br />

74<br />

Field Description<br />

Create User Profile Field Descriptions: Panel 1<br />

User Profile Specify the name and a description for the user profile. You can edit a<br />

name only when enrolling a new profile. You cannot rename existing user<br />

profiles.<br />

<strong>MKS</strong> Integrity User ID Specify the name this user logs on with to access the <strong>MKS</strong> Integrity<br />

Server. Field is valid only when <strong>MKS</strong> Integrity is used for issue tracking or<br />

<strong>MKS</strong> Source is used for source archiving. For details, see “User Profile<br />

Setup” on page 235, and “<strong>Implementer</strong> and <strong>MKS</strong> Source Integration” on<br />

page 259.<br />

*USRPRF: The <strong>MKS</strong> Integrity user ID defaults from the user’s iSeries<br />

user profile. This is the default value.<br />

Name: Specify the valid <strong>MKS</strong> Integrity user ID. The value *NONE is not<br />

authorized to access <strong>MKS</strong> Integrity.<br />

Programmer/env admin options<br />

The following fields, in conjunction with user capabilities by environment on page 109, define the<br />

user’s access to functions used on a daily and emergency basis.<br />

Check out Specify if this user has authority to use the Check Out option on the menu<br />

or command interface. Developers usually use the Check Out function.<br />

The default value is Y.<br />

Create request Specify if this user has authority to use the Create Request option on the<br />

menu or command interface. Developers usually use the Create Request<br />

function. The default value is Y.<br />

Compile requests Specify if this user has authority to use the Compile Requests option on<br />

the menu or command interface. Developers usually use the Compile<br />

Requests function. The default value is Y.<br />

Project maintenance Specify if this user has authority to use the Projects option on the menu.<br />

Project leaders usually use this function. The default value is N.<br />

Emergency check out Specify if this user has authority to use the Emergency Check Out<br />

function on the menu. The default value is N.<br />

Emergency create<br />

request<br />

Specify if this user has authority to use the Emergency Create Request<br />

function on the menu. The default value is N.<br />

Move requests Specify if this user has authority to use the Move Requests option on the<br />

menu or command interface. Project leaders usually use this function.<br />

The default value is N.<br />

Setup options<br />

The following fields define the user’s access to functions such as data maintenance and system and<br />

environment configuration defaults. The default value for each of these options is N (not allowed).<br />

User profile<br />

maintenance<br />

Specify if this user has authority to change user profile information in<br />

Work with Users.<br />

Host env maintenance Specify if this user has authority to change environment information in<br />

Work with Environments.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!