Getting VSAM code 44?

Virtual Storage Access method - ESDS, KSDS, RRDS & LDS. Basic direct access method, Basic sequential -, Queued sequential -, Basic partitioned -, Indexed sequential -, Object - access method.
Post Reply
Anil
Registered Member
Posts: 70
Joined: Sun Jun 16, 2013 12:41 am

Getting VSAM code 44?

Post by Anil »

Hi,

I am getting VSAM Status 44. When I looked for it's explnation it shows:

Code: Select all

A BOUNADRY VIOLATION DUE TO ATTEMPT TO WRITE A RECORD OF IMPROPER LENGTH 
What is the meaning of that, how to solve it ? Please help me.
Thanks,
Anil
enrico-sorichetti
Global Moderator
Global Moderator
Posts: 826
Joined: Wed Sep 11, 2013 3:57 pm

Re: Getting VSAM code 44?

Post by enrico-sorichetti »

the length of record that You are trying to write does not agree with the record length of the vsam cluster
speck To your support to find out the characteristics of the VSAM cluster and WHY there is a mismatch between the COPYBOOK and the same
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort 8-)
User avatar
Robert Sample
Global Moderator
Global Moderator
Posts: 1891
Joined: Fri Jun 28, 2013 1:22 am
Location: Dubuque Iowa
United States of America

Re: Getting VSAM code 44?

Post by Robert Sample »

The COBOL FD for the VSAM data set needs to match the physical attributes the data set has; each WRITE or REWRITE also needs to match the COBOL FD. A file status 44 means the program is attempting to write a record larger (or smaller) than the FD specified, or a REWRITE is being attempted where the record length is not the same as the record that was read.

This information is EASILY available in the Enterprise COBOL Language Reference manual -- why did you not read that first?
Anil
Registered Member
Posts: 70
Joined: Sun Jun 16, 2013 12:41 am

Re: Getting VSAM code 44?

Post by Anil »

Thanks Robert. I was able to find what it meant from the manual but making it work in my program was challenging. After some effort I could get it. I took a wrong file as input. :|
Thanks,
Anil
Post Reply

Create an account or sign in to join the discussion

You need to be a member in order to post a reply

Create an account

Not a member? register to join our community
Members can start their own topics & subscribe to topics
It’s free and only takes a minute

Register

Sign in

Return to “SMS & VSAM and BDAM, BSAM, QSAM, BPAM, ISAM, OAM.”