MVSFORUMS.com

abracadabra · Posted: Fri Sep 10, 2004 7:55 am Post subject: VSAM Code 44

Hi What could be the possible reason for a VSAM Status 44. It says A BOUNADRY VIOLATION DUE TO ATTEMPT TO WRITE A RECORD OF IMPROPER LENGTH

Thanks
_________________
Cheers!

Manas Biswal · Posted: Fri Sep 10, 2004 9:36 am Post subject:

I think you are trying to REWRITE a record with a different length than the original record length.
Please post details - Online or batch and code snippets.

Regards,
Manas

abracadabra · Posted: Fri Sep 10, 2004 9:40 am Post subject:

Its a fixed lenght file, so no question of variable record lengths. Its in batch
_________________
Cheers!

abracadabra · Posted: Fri Sep 10, 2004 12:26 pm Post subject:

Has anybody ever faced a VSAM status 44 before? Basically I am running it in batch and trying to write into the file. Even the key is different for the record that I am writing. All records are being written from a copybook into the output file. This record which is having an error is the last of a similar set of records. Then more records are written. When processed separately, the record is getting processed. Any help is welcome
_________________
Cheers!

abracadabra · Posted: Fri Sep 10, 2004 12:37 pm Post subject:

Just to add, the VSAM KSDS has an alternate index defined with duplicates
_________________
Cheers!

MikeBaker · Beginner Joined: 04 May 2004 Posts: 96 Topics: 9

VSAM returns two difference status codes. If you want to debug this, then you can have a look at the second RC being returned. Have a look at the "Programming Guide" for COBOL. It says... (see below) and shows how to code it etc.

FILE STATUS IS data-name-1 data-name-8
The variable data-name-1 specifies the two-character COBOL file status key. The
variable data-name-8 specifies a 6-byte data item that contains the VSAM return
code when the COBOL file status key is not 0.

kolusu · Posted: Sun Sep 12, 2004 7:49 pm Post subject:

abracadabra,

Vsam file status code of 44 is similar to status code 24 , which may occur when you run out of extents. May be your vsam file reached the 4GB limit. Check this link which discusses the same issue.

http://www.mvsforums.com/helpboards/viewtopic.php?t=2073&highlight=4gb

Hope this helps...

Cheers

Kolusu
_________________
Kolusu - DFSORT Development Team (IBM)
DFSORT is on the Web at:
www.ibm.com/storage/dfsort

www.linkedin.com/in/kolusu