Question & Answer
Question
Why are my applications receiving a NOTFND condition when trying to retrieve VSAM records in CICS Transaction Server for z/OS? I am also unable to retrieve the VSAM records when running batch jobs. But, I can verify that the records exist in the VSAM files using File Manager.
I have also seen the following errors:
IDAI1001E PUT FAILED, ERROR FOUND WHILE
UPDATING THE INDEX
REASON: DUPLICATE INDEX POINTER
IDAI1001E PUT FAILED, ERROR FOUND WHILE
UPDATING THE INDEX
REASON: OUT OF SEQUENCE INDEX
VSAM DYNAMIC RPL DUMP - IDAM19R3+12C0 FEEDBACK CODE: 0108006D
Answer
You might have recently installed z/OS maintenance that included VSAM APAR OA49513 for VSAM hiperspace handling. This APAR provides PTFs UA80640 (RD10), UA80641 (R210), or UA80642 (R220) for VSAM depending on your version and release. The PTFs require an IPL of the LPAR so you might notice VSAM records problems right after an IPL.
HIPER DFSMS VSAM APAR OA50329 has been opened to address the IDAI1001E and NOTFND problem, but this APAR is still in OPEN status so the PTFs are not available yet. At this point, you can use one of the local fixes:
Remove the PTFs for OA49513 (UA80640 UA80641 UA80642) from your system
Remove hiperspace buffers from the applications that use VSAM LSR with hiperspace buffers. In CICS Transaction Server for z/OS (CICS TS), RDO parameters of HSDATA and HSINDEX are added to the LSRPOOL definition to specify Hiperspace buffers. See Using Hiperspace bufferes in the CICS TS V.41 documentation for more information.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
12 May 2016
UID
dwa1266450