Hello, I think there could be two solutions for this problem.
1. As suggested by Ken, there could be a read/locate for high-values at every RNF condition (doing it at file open won't solve the RNF during program execution for obvious reasons) to refresh the index. However I am not too sure if such a read does cause a refresh of index. Somebody could throw some light on this? 2. Taking a backup of the file into a VSAM dataset and use it in the job. This temp dataset is shielded from the CICS updates. Delete the temp dataset at the end of batch. Let me know your views on this. Thank you, Saurabh -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ken Porowski Sent: Wednesday, April 23, 2008 7:39 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: VSAM random read error We had a similar issue with a file open for update in CICS and read in batch. Occasionally a record not found condition was hit but the record was in the file. We did not want to use SHRoption 4 due to the performance hit and we didn't have a product to allow file sharing (SHROPTION 5, SYSB-II, etc.). What the programmers did was insert a read/locate for a key of high values (not sure if this was done once at file open or after every RNF) then redo the read. This seemed to solve the issue. I assume a CI/CA split happens after batch file open and the record needed is moved (in one of the split CI/CA), the read to high values must have forced a refresh of the index to batch. Pardon my lack of a more technical answer I don't have time to track down the details. Ken -----Original Message----- Pandey_Saurabh Hello Stephen, Thanks for your response. The file is indeed open for update in CICS but the key for which the random read failed was added quite some time back. Thank you, Saurabh -----Original Message----- Stephen Mednick > -----Original Message----- > Saurabh Pandey > > Hello, > > We have a KSDS file being read randomly during daily batch process. > But the read fails with file-status 23 (record not found). On > analysing the abend, the record with the read-key is always found in > the file. This happens on a random basis - once or twice a month. > > The job gets through successfully if we resubmit the job (after the > abend:w/o making any changes!) or introduce another step to take a > backup of the file and then use it(the backup file) in the program. > > Initially I thought that the file was being updated by some other > program running concurrently. I checked the abended job's execution > time and found that no other program running parallely was even using > this file. > > I have seemingly exhausted any possibility I could think of. > Could it be related to the record being present in secondary extents? > I am getting wilder :) > > Does someone has an idea here? > > Thank you, > Saurabh > Are you sure that the file ***isn't*** open for update by another task such as CICS? Stephen Mednick Computer Supervisory Services Sydney, Australia ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
