What is my lock request waiting for?
我的锁请求在等待什么？
Lock request time out period exceeded.
已超过了锁请求超时时段。
Start a child thread that evaluates the lock request.
启动一个对锁请求进行处理的子线程。
The output indicates that you are waiting on the lock on the row (0;A) from the db2pd output because the 'Sts' column, which provides the status of the lock request, shows a W for waiting.
输出表明等待的是db2pd 输出中的行（0；A）上的锁，因为提供锁请求状态的 ‘Sts’列显示W，表示等待。
In this situation, if no lock is available at the time of the request, the application immediately receives a -911.
在这种情形中，如果请求时没有可用的锁，那么应用程序立刻会接收到- 911。
In this situation, the application will wait for a lock (if one is not available at the time of the request) until either the lock is granted or until a deadlock occurs.
在这种情形中，应用程序将等待获取锁(如果请求时没有可用的锁)，一直到被授予了锁或出现死锁为止。
The shorter the time a thread holds a given lock, the lower the probability that another thread will request it while the first thread is holding it.
一个线程占用一个给定锁的时间越短，另一个线程在该线程仍占用锁时请求该锁的可能性就越小。
For example, if you are writing a Web server, and all your cached pages are stored in a HashMap, every request will want to acquire and hold the lock on that map, and it will become a bottleneck.
例如，如果您正在编写一个Web服务器，而且所有的高速缓存的页都存储在hashmap中，那么每个请求都将需要获得并占用那个map上的锁，这就将成为一个瓶颈。
Once the MBean server has been started, the JLAGui can request lock statistics from the running application by navigating though the server into the native library and then on into the running JVM.
启动MBean服务器之后，JLAGui可以通过将该服务器导航到本地库中，然后导航到运行的JVM中，从而请求运行的应用程序的锁统计信息。
Because the acquired lock does not persist across transaction boundaries, the import utility loses its IX table lock and must request another lock after each commit.
因为获得的锁不会跨事务边界存在，所以import工具将失去它的IX表锁，并且必须在每次提交之后请求另一个锁。
This causes t1 to request a lock on MCL2 and wait until that lock can be obtained.
这造成t1请求mcl2上的锁，并一直等候到可以得到锁为止。
The global I/O request lock in 2.4 has been removed.
中的全局I/O请求锁不再使用。
The implementation of the lock function has to assure that the result of the request (lock is granted or not granted) is immediately available to the caller.
lock函数的实现必须确保调用者能够立即得到请求的结果(授予锁还是不授予锁)。
If multiple arrows show a circular lock-request pattern — threads prevent each other from running because they are waiting for each other to release a lock — then you have a deadlock.
如果多个箭头显示一个环形的锁请求模式—由于它们正在相互等候其它线程释放锁，所以线程彼此阻止运行—结果就形成了一个死锁。
When a request comes from a user to dump the data, each thread takes a lock and dumps it to a central place.
当收到来自用户的转储数据的请求时，每个线程获得一个锁，并将其转储到中心位置。
I am often asked at what point should we lock down the requirements and subject our users to formal change request procedures.
我经常会被问及我们应当在哪个时间点上回顾需求，并且使我们的用户服从正式的变更需求程序。
To avoid situtations like this, DB2 V8.2 supports the so called lock-request-clause.
为了避免这样情况发生，DB2V8.2支持所谓的 lock-request-clause。
A non locker code got a request to reserve the lock for making global updates.
非锁定程序代码收到一个为全局更新保留锁定的请求。
A non locker code got a request to reserve the lock for making global updates.
非锁定程序代码收到一个为全局更新保留锁定的请求。
应用推荐