Strange behavior with VSAM

chandracdac · New User Joined: 15 Jun 2007 Posts: 92 Location: bangalore

Hi All ,

i am facing some strange behaviour with my VSAM files.

I have 4 VSAM files in program. when i run with some set of files it is working properly. To cover some of the test cases
i tried below things.
1.i hav copied one of the VSAM File and edited some filed. when i run with this new file and other 3 files my job is abending with return code 90 for other files..
2. i thought may my edited VSAM file is causing issue and i created one more VSAM file with the same data This time i didn't change anything in the file. i.e now i just changed the file name of one VSAM file everything is same. But still my job is abending with same error code.Only difference between the file names is Highlevel qualifier.

Could some one please help me on this..

Thanks,
Chandra.

Gnanas N · Posted: Fri Jul 06, 2012 10:37 am

chandracdac · New User Joined: 15 Jun 2007 Posts: 92 Location: bangalore

I am sorry i forgot to mention that.

when i tried opening the files.. all files are input only.

MF00FS:00
MF04FS:00
MF11FS:00
MF12FS:90
MF17FS:90
MF20FS:90
*********************************************
* US VSAM FILE OPEN ERROR *
* FILE STATUS CODE 90
* *
*********************************************
CEE3250C The system or user abend U 099 R=NULL was issued.

Thanks
Chandra.

Gnanas N · Posted: Fri Jul 06, 2012 11:16 am

Okay. Does job's JESMSGLG or JESYSMSG has any info regarding VSAM error?

You may need to try with extended VSAM Return-code to get more info.

Here is an example.
ibmmainframes.com/post-98817.html

sandip_mainframe · New User Joined: 20 Sep 2006 Posts: 63 Location: pune

Hi chandra,

Whenever you perform any operation on the file, display file status every time. Let's say if you open the file,
DISPLAY ' OPEN FILE STATUS : ' FILE-STATUS-VAR

When you edit or delete file display the status.
DISPLAY ' EDIT FILE STATUS : ' FILE-STATUS-VAR

By this way you can catch exactly where you are getting file-status 90.

Thanks,
Sandip Walsinge
Walsinge Technologies Pvt Ltd, Pune.

Bill Woodger · Posted: Wed Jul 11, 2012 4:24 pm

Sandip, the TS knows which file is failing.

Why do you not suggest the extended file status that is available for VSAM files? That might help in establishing what the 90 is...

Robert Sample · Posted: Wed Jul 11, 2012 4:30 pm

Is your TSO / ISPF edit session set to retain trailing blanks or not? If not, the record length would change after an edit since the trailing blanks would be removed.

But as others have said your should use the extended file status clause to get the extra data VSAM will give you.

Pete Wilson · Posted: Thu Jul 26, 2012 9:58 pm

When you renamed the VSAM file did you just rename the Cluster name or the Data and Index components as well?

RC=90 is usually something to do with a catalog error, but it would help if you included and IEC161I, IDC3090 or IEC3351I messages as well as the RETURN and REASON codes, and also a the full LISTCAT output for the file name (cluster) that is producing the error.

Bill O'Boyle · Posted: Thu Jul 26, 2012 10:05 pm

Bill Woodger said -