My CICS program is abending to corrupt alternate index of a file. How do I find out if the index of a file is corrupt?
If your CIS transaction is abending because it is attempting to read a VSAM KSDS record via an alternate index, then it's the AIX that is the problem. You MUST investigate WHY this is becoming corrupt.
If the AIX is simply out of date (for example, you have deleted the base record and the AIX is not defined as upgradeable), then your application is at fault if it has not been coded to support this simple error case.
I don't think you can do any sort of operation within the CICS environment to detect a corrupt or damaged AIX save doing a browse on all the records in the AIX (and so reading them all) which will be a long job and have access considerations during the browse.
Have a look in the VSAM manuals for AIX processing and use of the VERIFY (amongst others) AMS command.
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
Related Q&A from Robert Crawford
For better mainframe capacity planning, how do I convert CPU hours to MIPS? And is there a way to calculate the relationship between MIPS and MSUs? Continue Reading
I have two years of experience in mainframe technology, currently working as a mainframe developer. I want to change to Java technology. Continue Reading
I want to replicate DB2 from the mainframe to an AIX box since it's cheaper and the copy can be used for testing. Is this possible? Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.