internal lock

[xixi]

can someone explain to me what is internal p lock, internal s lock,
internal v lock? when i have IS lock or IX lock , i always have these
internal locks together for the application handle

Application handle = 261
Application ID =
AC100482.GD3A.00F85FE51898
Sequence number = 0006
Application name = db2jccmain
Authorization ID = WCADMIN
Application status = UOW Waiting
Status change time = Not Collected
Application code page = 1208
Locks held = 1
Total wait time (ms) = Not Collected

List Of Locks
Lock Name = 0x5359534C564C303153304E4441
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal P Lock
Mode = S

[Fan Ruo Xin]

They are used by IBM developer or support people. You don't need worry
about them.

xixi wrote:

can someone explain to me what is internal p lock, internal s lock,
internal v lock? when i have IS lock or IX lock , i always have these
internal locks together for the application handle

Application handle = 261
Application ID =
AC100482.GD3A.00F85FE51898
Sequence number = 0006
Application name = db2jccmain
Authorization ID = WCADMIN
Application status = UOW Waiting
Status change time = Not Collected
Application code page = 1208
Locks held = 1
Total wait time (ms) = Not Collected

List Of Locks
Lock Name = 0x5359534C564C303153304E4441
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal P Lock
Mode = S

[Bob [IBM]]

Actually these locks are part of the general execution of DB2.

A p-lock is a lock on the package cache:
Any execution of SQL, whether static or dynamic, must be done while holding a 'package lock'. This ensures that no-one can drop the package that is being executed.

A v-lock is a variation lock :
Any execution of dynamic SQL is done via an entry in the SQL cache known as a variation. In order to ensure that the variation remains valid during the execution, V locks are acquired on behalf of the entry.

An s-lock is a sequence lock:
Not sure if I am allowed to tell you what it is used for :)

--

Bob
Consulting I/T Specialist
IBM Toronto Lab
IBM Software Services for Data Management
[My comments are solely my own and are not meant to represent an official IBM position - ask my cat!]
"Fan Ruo Xin" <fa*****@sbcglobal.net> wrote in message news:3F**************@sbcglobal.net...
They are used by IBM developer or support people. You don't need worry
about them.

xixi wrote:

can someone explain to me what is internal p lock, internal s lock,
internal v lock? when i have IS lock or IX lock , i always have these
internal locks together for the application handle

Application handle = 261
Application ID =
AC100482.GD3A.00F85FE51898
Sequence number = 0006
Application name = db2jccmain
Authorization ID = WCADMIN
Application status = UOW Waiting
Status change time = Not Collected
Application code page = 1208
Locks held = 1
Total wait time (ms) = Not Collected

List Of Locks
Lock Name = 0x5359534C564C303153304E4441
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal P Lock
Mode = S

[holmskov]

Hi Bob

Just wondering - is there ANYTHING that I can do to lower the amount of Internal P Locks I find in a system?

I found a place where it states:
"Internal P locks are package locks. An application will have an S (shared lock) lock whenever that application is using the package. A rebind can not be done while the package is in use, so at that time a rebind will wait to acquire an X (exclusive) lock.".
and
"These locks are freed when the SQL statement is committed. "

I am not doing any binding/rebinding on the system. I tend to have a couple of packagecache overflows. Do not know if these are related? Or is it just the frequency of which these transactions are initiated that causes the P locking?

Thanks for any insight on how to avoid this.

Best regards - Ole

Actually these locks are part of the general execution of DB2.

A p-lock is a lock on the package cache:
Any execution of SQL, whether static or dynamic, must be done while holding a 'package lock'. This ensures that no-one can drop the package that is being executed.

A v-lock is a variation lock :
Any execution of dynamic SQL is done via an entry in the SQL cache known as a variation. In order to ensure that the variation remains valid during the execution, V locks are acquired on behalf of the entry.

An s-lock is a sequence lock:
Not sure if I am allowed to tell you what it is used for :)

--

Bob
Consulting I/T Specialist
IBM Toronto Lab
IBM Software Services for Data Management
[My comments are solely my own and are not meant to represent an official IBM position - ask my cat!]
"Fan Ruo Xin" <[e-mail]> wrote in message news:[e-mail]...
They are used by IBM developer or support people. You don't need worry
about them.

xixi wrote:
[color=blue]
> can someone explain to me what is internal p lock, internal s lock,
> internal v lock? when i have IS lock or IX lock , i always have these
> internal locks together for the application handle
>
> Application handle = 261
> Application ID =
> AC100482.GD3A.00F85FE51898
> Sequence number = 0006
> Application name = db2jccmain
> Authorization ID = WCADMIN
> Application status = UOW Waiting
> Status change time = Not Collected
> Application code page = 1208
> Locks held = 1
> Total wait time (ms) = Not Collected
>
> List Of Locks
> Lock Name = 0x5359534C564C303153304E4441
> Lock Attributes = 0x00000000
> Release Flags = 0x40000000
> Lock Count = 1
> Hold Count = 0
> Lock Object Name = 0
> Object Type = Internal P Lock
> Mode = S[/color]