Microsoft Knowledge Base Email Alertz

(249167) - The Microsoft OLEDB Provider for AS/400 and VSAM (SNAOLEDB) does not support pessimistic locking. In the Microsoft SNA SDK documentation under the ADO Recordset Object in the OLE DB Provider for AS/400 and VSAM topic, it is mentioned under LockType...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 249167 - Last Review: November 24, 2004 - Revision: 2.1

BUG: SNAOLEDB Does Not Support Pessimistic Locking

This article was previously published under Q249167

SYMPTOMS

The Microsoft OLEDB Provider for AS/400 and VSAM (SNAOLEDB) does not support pessimistic locking.

In the Microsoft SNA SDK documentation under the "ADO Recordset Object in the OLE DB Provider for AS/400 and VSAM" topic, it is mentioned under LockType that SNAOLEDB supports all four lock types. Namely adLockReadOnly, adLockOptimistic, adLockPessimistic, and adLockBatchOptimistic. The preceding statement is not true and SNAOLEDB does not currently support adLockPessimistic from an ADO recordset object.

The ADO Client side cursor does not support "pessimistic" locking. ADO server side cursor support "pessimistic" locking if the corresponding provider supports this property. SNAOLEDB does not support "pessimistic" locking. If an unsupported value is set, then no error occurs and the closest supported LockType is used instead. If from an ADO program you set the LockType property to adLockPessimistic, when you open an updateable recordset with server side cursor it automatically maps to either adLockOptimistic or adLockBatchOptimistic.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft SNA Server version 4.0 Service Pack 2 (SP2) and Service Pack 3 (SP3) SDK documentation.

MORE INFORMATION

The OLEDB Provider for AS/400 and VSAM (SNAOLEDB) comes with SNA Server/Client version 4.0 SP2 or SP3. It uses the DDM RLIO protocol to provide OLEDB consumers with access to VSAM and AS/400 record-level data. This provider complies with Level 4 of the IBM Distributed Data Management (DDM) architecture and the OLE DB architecture. It uses SNA Server, the reliable platform for host integration as the networking bridge between the SNA host and the Windows NT operating systems.

The Microsoft OLE DB Provider for AS/400 and VSAM supports the following features:
  • Set attributes and a record description of a host file (column information).
  • Position to the beginning record or the ending record in a file.
  • Navigate to the previous or next record in a file.
  • Seek to a record based on an index.
  • Lock records.
  • Change records in a file.
  • Insert new records and delete records in a file.
  • Preserve file and record attributes.
SNAOLEDB does not support "pessimistic" locking.

REFERENCES

For more information, please refer to the following article in the Microsoft Knowledge Base:
190625  (http://kbalertz.com/Feedback.aspx?kbNumber=190625/EN-US/ ) FIX: ADO Client Cursors Report LockType = adLockPessimistic
SNA SDK Documentation

APPLIES TO
  • Microsoft OLE DB Provider for AS/400 and VSAM 4.0 SP2
  • Microsoft OLE DB Provider for AS/400 and VSAM 4.0 SP3
Keywords: 
kbbug kbpending KB249167
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate