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.

Environments<br />

3 Complete the fields as described in the following tables of Create Environment Field<br />

Descriptions. Press PAGE DOWN to access the additional panels.<br />

4 When finished, press ENTER to add or update the environment.<br />

Field Description<br />

Create Environment Field Descriptions: Panel 1<br />

Environment Specify the name of the environment. You can enter a name only when<br />

creating a new environment. You cannot change the name of an existing<br />

environment.<br />

Description Type a brief description for the environment.<br />

Administrator Specify a user profile that has authority to Move Requests for this<br />

environment. To the right of this field is the description of the administrator.<br />

Env type Specify whether the environment is Production (*PRD), Quality Assurance<br />

(*QAC), or Test (*TST) environment.<br />

*PRD: You can check out from and promote to a *PRD environment. You<br />

cannot check out to a *PRD environment or to a library defined to a<br />

*PRD environment, or promote from a *PRD environment.<br />

*QAC: You can promote to and from a *QAC environment. You cannot<br />

check out to a *QAC environment or to a library defined to a *QAC<br />

environment.<br />

*TST: You can check out to a *TST environment or to a library not<br />

defined to any environment. You can promote from a *TST environment.<br />

You cannot check out to libraries that are defined in *PRD or *QAC<br />

environments, or promote to *TST environments. A *TST environment is<br />

considered a developer’s set of libraries.<br />

83

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

Saved successfully!

Ooh no, something went wrong!