Because a large amount of Event data can be captured, it is important to understand how to maintain this data either automatically or manually. Because of the potentially short-term lifespan of Capture Event data sets, it is a good practice to allocate the Event data sets on WORK volumes.
We recommend the following methods for specifying a retention period for captured events to control how long those events are saved:
Lets you specify and associate a retention period with each captured event in the CAPTURE parmlib member, or in each CAPLIB member.
Contains data set retention information. If you use this feature for setting retention periods, the process continues to function properly.
Deletes and uncatalogs expired data sets on an interval basis. Use this facility to control the amount of data retained. If a data set is manually deleted, the supplied Index Maintenance function CAPMAINT cleans up any outstanding data.
If you do not use a retention period to remove Event data sets automatically, then those data sets exist forever unless manually deleted.
Copyright © 2014 CA.
All rights reserved.
|
|