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.