MKS Implementer 2006 Administration Guide

Key Considerations
Purging Environment History
To purge host environments, you must have authority to environment maintenance and
move authority for the environment. To purge remote environments, you must have
authority to remote environment maintenance and move authority for the environment.
Authority to host and remote environment maintenance is defined in Work with Users.
Move authority is defined in Work with Environments, User Capabilities.
When purging history for all environments (F19=Purge All History), users cannot access
or use Implementer while the purge is running (requires a dedicated database). When
purging specific environments, users cannot access the selected environment while the
purge is running.
Purging completed requests removes requests that completed on or before the purge
date you specify. It removes the entire promotion request if the request is from the
purged environment, or if the request targets a single environment and that
environment is purged. If a request targets multiple environments and the secondary
target environment is purged, it removes the purged primary environment from the
request and the second environment becomes the primary environment on the request.
In addition, Implementer adds a comment to the request, for example, “The primary
target environment ‘name’ was purged on date by ‘user’.” When removing
a purged secondary environment from the request, Implementer also adds a comment to
the request, for example, “The target environment ‘name’ was purged on date
by ‘user’.”
You can optionally purge closed locks and object status history for production
environments by specifying *ALL for the purge to date. If a lock is from or to the purged
environment, it removes the lock and all related history. If a lock was copied from a
purged environment, it removes any references to the environment from the lock and
related history. If the history of a lock includes passing through a purged environment,
the portion of history related to the purged environment.
CAUTION Use this option cautiously—it purges the Implementer database of
historical data, thereby removing audit trail information from production
environments.
Only requests that are non-release management packages can be removed. For details on
purging release management environments, see the MKS Implementer 2006 Release
Management Guide.
MKS recommends you print the Activity Report, option 31 on the Implementer Menu,
prior to running Purge History. This report is useful for analyzing the status of all
environments and projects.
375