About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Dear Frank, Thank you for submitting this enhancement request. The development team reviewed it and provided this feedback for you:
During development of utility history, the development team had considered the cleanup support for these history catalog tables, but at the end decided to not pursue it. MODIFY RECOVERY is mainly tied to object recoveries so it is not appropriate as a cleanup agent for utility history. Also in discussion with various sponsor users, many have different criteria to determine what utility history events to keep and what to delete (e.g. some based on time, some based on specific utilities run, some based on specific objects...etc), so ultimately it would be preferable for user to determine their own cleanup strategy via SQL DELETE, or utilize a more robust tooling solution (like via IBM Admin tool or equivalent product) to perform the customized utility history table cleanup.
Therefore, we are not considering this idea. Please do continue to submit enhancement requests to us for consideration, as your input greatly helps shape the future functions and features of our offerings.
Sincerely,
The Db2 z/OS Development team