MKS Implementer 2006 Administration Guide

Chapter 7: Administrative Utilities
376
To purge environment history
1 From the Implementer Menu, type option 42, Environments, and press ENTER.
From the Implementer Receiver menu, type option 8, Environments, and press ENTER.
On the remote system you also have the option to use the Purge History (IDBPRG)
command. Type IDBPRG and press ENTER to display the Purge History window. The
Purge History command is valid only on the Implementer Receiver.
2 Select the environment to purge with option 32, Purge History. To purge history for all
environments, press F19=Purge All History. The Purge History panel displays.
3 Complete the fields as described in the following table of “Purge History Field
Descriptions”.
4 Press F9=Submit to submit the job (or press F3=Exit to cancel the purge function).
NOTE For information on overriding the default job queue and submission method
on the host system, see “Submitting Job Overrides” on page 372. On the remote
system, data area IRJOBQ stores the remote job queue, and data area IRSBMMTD
stores the submission method. For details, see “Implementer Data Areas” on
page 402.
Field Description
Repository Maintenance
Purge History Field Descriptions
Environment Name If purging a single environment, this field defaults to the
environment selected on the Work with Environments panel. If you
selected to purge all environments, the field defaults to *ALL.
Purge to date Specify the ending date to purge all completed requests. For
promotion requests, this is the completion date of each request. For
locks and object history, it is the date the lock was released on the
host system. Specify *ALL to purge up to the current date.
Purge lock/obj status history Specify whether to purge lock and object status history. This option
is valid only for host production environments. Status history is not
purged for locks released on the specified purge to date, or for
existing locks with active concurrent development.
Y: Purges lock and object status history.
N: Does not purge lock and object status history. This is the
default value.
Implementer’s member/object repository is the source for items that display in Object
Inquiry and Work with Objects. Repository Maintenance allows you to modify the object
codes associated with traditional member/objects and IFS objects within the repository for an
environment.