Knowledge Base

INF: “Key Not Found” Accessing VSAM KSDS on IBM OS/390

Article ID: 191452

Article Last Modified on 11/24/2004

Microsoft OLE DB Provider for AS/400 and VSAM 1.0, when used with:
- Microsoft SNA Server 4.0

This article was previously published under Q191452

SYMPTOMS

HRESULT 80004005, (Key not found.) is returned to a consumer program attempting to open a VSAM KSDS on an OS/390 mainframe.

RESOLUTION

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.

Keywords: kbprb KB191452