ED300
ED300 - Purge Event History

Use ED300 to purge event history. Event history should be purched regularly tokeep the EDEVENT (Unix/Windows) or DBEDEDE (System i) and EDEVENTDTL (Unix/Windows) or DBEDEDT (System i) database tables down to a reasonable size. To purge event history 1. Access Purge Event History (ED300). 2. Assign a job name. 3. Specify the number of days of event history that you want to keep. 4. Add the job and click Submit. ED300 will write the purged data to these locations: LAWDIR/applicationproductline/edi/purged/EDEVENT.ccyymmddhhmmss -or- LAWDIR/applicationproductline/edi/EDEVENTDTL.ccyymnddhhmmss. These are comma-delimited files that can be backed off onto other media and can be reloaded into EDEVENT (Unix/Windows) or DBEDEDE (System i) and EDEVENTDTL (Unix/Windows) or DBEDEDT (System i) if they should ever be needed again.

Updated Files
CKPOINT - No Description Available.
EDEVENT - No Description Available.
EDEVENTDTL - No Description Available.



Referenced Files
None.







File created: Thu Jun 09 11:12:45 2016

Nogalis, inc.
Contact Us

All trademarks and registered trademarks are the property of their respective owners.