Problem solve Get help with specific problems with your technologies, process and projects.

VSAM files and AIX

A VSAM file with an Alternate Index is updated online. Before doing the update, the alternate index is read through the path to see if it is a duplicate record. It is not getting the duplicate record error and the records are being written again. Could this be a buffer problem? We are running OS/390 2.10 and TS 1.3 and use LSRPOOLS for our VSAM files. The file is defined with SHR (2,3).

I assume you are reading the Alternate Index to see if there is the potential for a duplicate-record failure when you add the new record to the base cluster. And, that you are doing that because you do not allow duplicate keys in the Alternate Index. This technique will only work if you are using an Upgradeable Alternate Index so that the new alternate key is immediately available through the alternative access path.

Why not just rely on a VSAM update failure (with the upgradeable Alternate Index) if you attempt to add a record to the base cluster and thereby get a duplicate alternate key (when you do not permit duplicates via the AMS definition)?

Robert Harris
CICS Technical Strategist -- CICS expert at Search390.com

Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .VO7aaqqaAFk.0@/search390>discussion forums.


Dig Deeper on IBM system z and mainframe systems

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.