This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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 mode. 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 -------------------------- https://www.ibm.com/support/knowledgecenter/SSAUUV_5.1.0/topics /inz_inout_consistencyconsid.html
LOCK 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. .... Tip 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.
Do not place IBM confidential, company confidential, or personal information into any field.