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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.