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.
Thanks Janet & team, we understand now the reasons explained. The idea then must change to a way of suspending the utility completely (releasing drains or waits), but letting re-intent after a few seconds or minutes. This is a completely different focus.
Our main scenario is an Incremental-COPY-change executed twice a day for all Db2-objects , and a QUIESCE of 1 Tablespace executed inside a Business JOB. The Business JOB fails inmediately, and could be smart or cool if QUIESCE could re-intent after a period of time.
In summary, RE-INTENT after n TIME. Could be possible?
Dear Maria, Thank you for submitting this enhancement request. Our Db2 utilities development team reviewed it and provided the following feedback:
Unlike DML, utility execution generally runs much longer, and it's not uncommon for an exclusive utility like LOAD/REORG/RECOVER to run for minutes, hours or even days. Also, incompatible utilities need to wait for each other to finish completely, not until its next commit point like drain/wait processing does with DML.
For this reason, it is not really conceivable to implement a wait/retry processing between utility executions, knowing that it is likely to timeout if the wait is short, or cause other system resources issues like SYSUTILX contention if the wait is long. Over the years development team is focused on letting potential compatible utilities to run concurrently instead (like REORG SHRLEVEL CHANGE and COPY SHRLEVEL CHANGE on the same object). Therefore, we are not considering this idea.
We appreciate your input to the Db2 Utilities development team. And we hope that you will continue to submit enhancement suggestions for improvements as customer feedback is a key component to shaping the future direction of Db2 Utilities.
Sincerely,
Db2 Utilities Team