IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

HPU should has issued LOCK TABLE statement in SQL mode.

Db2 High Performance Unload for z/OS V5.1 documentation says that
when we specify LOCK YES, the table can be accessed only in read-only
But according to PMR: 00483,6V5,760, HPU can not issue LOCK TABLE in the
case of SQL mode.

<>Db2 High Performance Unload for z/OS V5.1 documentation
  Consistency considerations                                           
   To prevent concurrent access for updates, set the LOCK keyword       
   to YES. This setting is useful for both direct and SQL access modes.
   When you specify LOCK YES, the table can be accessed only in         
   read-only mode while Db2 HPU is unloading data from the table.       
   YES is required when any access mode is selected.                    
   To ensure data consistency, consider specifying QUIESCE YES and      
   LOCK YES. The DB2 FORCE and LOCK YES combination also ensures        
   data consistency, but reduces performance.

It has been clearly different between the actual design and the above description.
We request code change for this problem that HPU issues LOCK TABLE statement in SQL mode.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 28 2019
  • Delivered
Who would benefit from this IDEA? As a customer using HPU.
How should it work?

If HPU issues LOCK TABLE,  we present guarantee consistency by using HPU.

Idea Priority Urgent
Priority Justification Our customers develop their system for their service-in planned on this fall. We want to give this solution ASAP.If we cannot present guarantee consistency by using HPU to our customers, it will affects a trust to our product.
  • Attach files

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 "anonymous@euprivacy.out" 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