Because HPU is not an application program and not a 'true Utility', it does not check all instances of other Utilities for incompatibility. Users will run HPU and other Utilities will that try to start may not see that HPU is running and there could be abends or inconsistent results. Adding an implied QUIESCE when running with LOCK YES. will add logic for Db2 Utilities to avoid each other. This is a feature with another vendor. Per development, this would most likely be a installation parm.
At the very least, if LOCK YES is coded and QUIESCE YES is NOT coded, include an information message stating this.
|Who would benefit from this IDEA?||All customers using HPU and running other Utilities to try to avoid Utilities conflicting with each other. Customers potentially migrating from other vendors who have this logic aready.|
How should it work?
Because HPU is not an application program and not a 'true Utility', it does not check all instances of other Utilities for incompatibility. When LOCK YES is issued, it should imply QUIESCE YES. This would add logic to HPU so that it could avoid conflicts with other Db2 Utilities that try to run while HPU is already running.
|Priority Justification||Customer is migrating from another vendor in which this feature already exists.|
|Customer Name||Customer wishes to remain anonymous. Please contact IBM account team.|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions