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
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.
|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.
|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.|
|Customer Name||TOKYO GAS SYSTEM|
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