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 />

Clearing Remote QA Environments<br />

384<br />

When you promote from a host and a remote QA environment to a production environment<br />

on a single request, <strong>Implementer</strong> retains a copy of the source and objects in the remote QA<br />

environment. By default, <strong>Implementer</strong> does not delete items from remote environments.<br />

For situations when this is not the desired result, <strong>Implementer</strong> provides a feature that allows<br />

you to delete the items in a remote QA environment after successful promotion from the<br />

environment. This is beneficial when QA and production environments exist on both the host<br />

and remote systems, and you want to automatically delete source and objects from the<br />

remote QA environments. For example, a promotion request created on a host system targets<br />

both local and remote QA environments. After successful QA testing, a new request created<br />

from the host QA environment targets both host and remote production. As part of the final<br />

move processing for the request, a special command you define runs based on your<br />

specifications and deletes the source and objects from the remote QA environment.<br />

NOTE This feature is available for AllFusion 2E environments by setting up the<br />

special command as described in this section. You must also set the <strong>Implementer</strong><br />

data area values for IMDLTFRMUP and IMDLTFRMUS to ‘YES’. For details, see<br />

“<strong>Implementer</strong> Data Areas” on page 402.<br />

Key Considerations<br />

Define the remote QAC environment with the Remove obj in from lib/env field and the<br />

Remove src in from lib/env field set to 1 (Always). For details, see the environment field<br />

descriptions on page 131.<br />

Define a special command for the remote environment to run for all promotion requests<br />

that target the environment. The special command automatically runs after the move<br />

completes, when the source and objects are in the target libraries.<br />

Add the <strong>Implementer</strong> Receiver library to the library list of the remote environment to<br />

support processing the special command.<br />

Define the object codes, or enable environment object code overrides for the remote QA<br />

environments. For details, see “Removing Source and Objects After Promotion” on<br />

page 92.<br />

To define the special command<br />

1 From the Work with Environments panel, select the remote production environment<br />

with option 19=Special commands, and press ENTER.<br />

2 Press F6=Add.

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

Saved successfully!

Ooh no, something went wrong!