We are running VDF 17.0.28.0 and using it to access DB2 tables on our Mainframe using an ODBC connection.
Once we use VDF to access a list of tables on DB2, the locks are held against the VM DB2 catalog tables until
the application is terminated. This prevents other users from dropping and creating objects in DB2. For example,
this the screen I am on. Even while sitting here, locks are being held (see 2nd screen shot).
User Agent: 9 User-ID: VDFUSER SQL-ID: VDFUSER
is R/W APPL B986A
Agent is not processing and is in communication wait.
State started: 2012-03-28 12:56:39
Conversation started: 2012-03-28 12:52:29
LUWID: AC10098D.EBB2.120328175030.0001
EXTNAM: Studio.exe 27FC0000001"""""""""""""""
Requester: SQL09074 (DB2/NT64) at EWZELL7
Protocol: DRDA via TCP/IP
Package: NULLID.SYSSN200 Section: 4
Connection ID: 45
DBSPACE LOCK NUMBER
AGENT USER NUMBER TYPE IN SIX IS IX S U X Z WAITERS
9 VDFUSER DB 0 0 0 1 0 0 0 0 0
9 VDFUSER 1 DBSP 0 0 1 0 0 0 0 0 0
9 VDFUSER 1 IKEY 0 0 0 0 467 0 0 0 0 <-- Locks being held
9 VDFUSER 1 ROW 0 0 0 0 526 0 0 0 1 <-- Locks being held
9 VDFUSER 1 TABL 0 0 10 0 0 0 0 0 0
9 VDFUSER 2 DBSP 0 0 1 0 0 0 0 0 0
9 VDFUSER 2 TABL 0 0 0 0 1 0 0 0 0
9 VDFUSER 17 DBSP 0 0 0 1 0 0 0 0 0
9 VDFUSER 17 PAGE 0 0 0 0 0 0 2 0 0
9 VDFUSER 17 TABL 0 0 0 0 3 0 0 1 0
9 VDFUSER 295 DBSP 0 0 1 0 0 0 0 0 0
9 VDFUSER 295 TABL 0 0 1 0 0 0 0 0 0
9 VDFUSER 10041 INT 0 0 0 0 0 0 1 0 0
9 VDFUSER 10042 INT 0 0 0 0 0 0 0 1 0
9 VDFUSER 10043 INT 0 0 0 0 0 0 1 0 0
9 VDFUSER 10044 INT 0 0 0 0 0 0 0 1 0
9 VDFUSER 10045 INT 0 0 0 0 0 0 0 1 0
9 VDFUSER 10046 INT 0 0 0 0 0 0 0 1 0
9 VDFUSER 10047 INT 0 0 0 0 0 0 0 1 0
9 VDFUSER 10048 INT 0 0 0 0 0 0 1 0 0
9 VDFUSER 10049 INT 0 0 0 0 0 0 1 0 0
Ed Zell
Illinois Mutual Life
ewzell@illinoismutual.com
(309) 636-0107