MVSFORUMS.com

kavi · Beginner Joined: 15 Sep 2006 Posts: 64 Topics: 22

Hi All,

I have a KSDS file with Alternate Index. Am trying to read alternate index(PATH) with a key, during this read am getting logical error 90 for this key, if i read another key i dont have any problem, when i manually checked this key in PATH, thru File manager, it got terminated, but the record is available in AIX and KSDS. I am using EZT for programming. The below is the error code. Any help on this would be appreciated.

kolusu · Posted: Thu Jun 02, 2011 8:49 am Post subject:

kavi,

Looks like you have a corrupted vsam file. The file status code 90 is returned when you encounter an invalid pointer (no associated base record) in an Alternate Index or a file status code 90 is returned when the file i-o result was that a bad open file error occurrerd. This could be caused by a number of reasons, the most likely is that the file was not properly closed to start with.

Run an idcams verify on the vsam file and re-run your ezt program.

Kolusu

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

kavi · Beginner Joined: 15 Sep 2006 Posts: 64 Topics: 22

Thanks Kolusu,
This was happend in production toady. When we analyzed, found that, yesterday reorg was done for this VSAM file. So this might cause the problem. Running verify will solve the problem, or it could be some thing else? Can you please explain how the verify will work on VSAM file.

Thanks, Kavi

kolusu · Posted: Thu Jun 02, 2011 9:14 am Post subject:

papadi · Supermod Joined: 20 Oct 2009 Posts: 594 Topics: 1

I suspect you mean an unload/reload of the data was done to accomplish the "re-org". This (run conrrectly) will not cause a file status code 90.

When you say this happened "in Production", the problem process is more likely the victim rather than the culprit. My guess is that "something else" damaged the file. And this needs to be determined / prevented from happening again.

Only running the verify may lead to worse problems later. . .
_________________
All the best,

di

kavi · Beginner Joined: 15 Sep 2006 Posts: 64 Topics: 22

Hi Kolusu,

unload, delete, define, repro we normally call this as reorg. Not sure if this is correct term.

Thanks for your help.

Kavi

warp5 · Posted: Fri Jun 03, 2011 12:57 am Post subject:

Did you build the aix new or how did you handle it / them?

kavi · Beginner Joined: 15 Sep 2006 Posts: 64 Topics: 22

Hi warp5,

Yes, I build the AIX new, actually my base cluster had 3 AIX, and for only one primary record the corresponding AIX records were missed in one AIX, other two AIX are perfect. When tried open the path for this AIX for the key, it got terminated. As per my understanding even if we delete the record in AIX, it also deletes base. If this is correct then, am really not sure how the VSAM corrupted.

Thanks, Kavi

dbzTHEdinosauer · Posted: Fri Jun 03, 2011 10:30 am Post subject:

i have never heard of an i/o that would have you delete the index and then expect the base to be deleted.

normally, you delete the base, and if the idcams idx and aix parms are correct, the indexes will also show the delete of the record.

don't remember if records in the base are physically deleted or logically deleted.
same for the indexes.
too lazy to look it up,
but, this fine manual VSAM Demystified will probably
answer all your questions.
_________________
Dick Brenholtz
American living in Varel, Germany