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 7: Administrative Utilities<br />

374<br />

When promoting to a Windows NT Server, IFS objects inherit the authorities of the<br />

target directory, regardless of authorities defined to the environment or existing on the<br />

from object. The object owner is user SDMAUTUSR (or the user profile defined to<br />

<strong>Implementer</strong> data area SDMAUTUSR). Unlike traditional objects, the object owner is not<br />

set by the Reset Authorities function.<br />

NOTE The Reset Authorities function does not change the authorities or owners of<br />

IFS objects in environments on a mounted drive.<br />

To reset authorities<br />

Common Questions<br />

1 From Work with Environments, select the environment with option 31, Reset<br />

Authorities, and press ENTER. A message displays confirming the action you are about to<br />

perform. (If you need to cancel without running the job, press F3=Exit or F12=Cancel.)<br />

2 Press F9=Submit to submit the reset authority job. The Work with Environments panel<br />

redisplays.<br />

What conditions warrant running Reset Authorities (other than when initially setting up the<br />

environment)?<br />

It may be necessary to run this function after initial setup if the libraries within the<br />

environments become corrupt external to <strong>Implementer</strong> use. You should restrict external<br />

access to the libraries you have under <strong>Implementer</strong>’s controlled.<br />

When is it necessary to rerun Reset Authorities and overwrite the authorities that exist?<br />

Use this function if users have either too much or not enough authority to an environment.<br />

Purging Environment History<br />

The Purge History function purges the <strong>Implementer</strong> database of completed promotion<br />

requests for a specific environment or globally for all environments. The function is available<br />

on both the host and remote system. On the host system, you can optionally purge lock status<br />

and history, object status history, and concurrent development activity.<br />

The function purges information from the <strong>Implementer</strong> database. It does not delete system<br />

objects or information. After purging, you can delete the environment if necessary.<br />

For details on deleting environments, see page 96.

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

Saved successfully!

Ooh no, something went wrong!