XPost: comp.databases.ibm-db2   
   From: srielau@ca.ibm.com   
      
   OK, here is the deal:   
   When you execute a dynamic statement which depends on table T.   
   DB2 will hold a usage lock on T until the end of the transaction.   
   So noone will be able to alter T (in a non-trivial way) until this   
   transaction is over.   
   An alternate design would be to release the lock after usage.   
   However in the interest of keeping the cache fast the capturing of locks   
   needs to be minimized. Schema evolution is considered a much rarer (more   
   rare??) event than cache-hits   
      
   Does that answer the comment?   
      
   Cheers   
   Serge   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)