Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 191452 - Last Review: November 24, 2004 - Revision: 4.1
INF: “Key Not Found†Accessing VSAM KSDS on IBM OS/390
This article was previously published under Q191452
HRESULT 80004005, (Key not found.) is returned to a consumer program
attempting to open a VSAM KSDS on an OS/390 mainframe.
To prevent this problem, be sure to define the entire VSAM record key in
the Host Column Definition file (HCD). Naturally, this means that all the
VSAM record fields that precede the key in the VSAM file record layout must
also be defined in the HCD file.
APPLIES TO
- Microsoft OLE DB Provider for AS/400 and VSAM 1.0, when used with:
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