File status 44 during writting records into alt index file

mainframekk · New User Joined: 11 Jul 2005 Posts: 8

From IBM manual
'A boundary violation exists because an attempt was made to rewrite a
record to a file and the record was not the same size as the record being
replaced, or an attempt was made to write or rewrite a record that was
larger than the largest or smaller than the smallest record allowed by the
RECORD IS VARYING clause of the associated file-name."

is it normal if the max number of duplicates of alt index key is reached?

parikshit123 · Active User Joined: 01 Jul 2005 Posts: 269 Location: India

Hi,

File status 44 for VSAM dataset is basically due to

A BOUNADRY VIOLATION DUE TO ATTEMPT TO WRITE A RECORD OF IMPROPER LENGTH

Further,

A boundary violation exists because an attempt was made to rewrite a record to a file and the record was not the same size as the record being replaced, or an attempt was made to write or rewrite a record that was larger than the largest or smaller than the smallest record allowed by the RECORD IS VARYING clause of the associated file-name.

It has nothing to do with 'MAXIMUM NUMBER OF DUPLICATE ALT KEYS'

Please check your REWRITE statement and prior READ statements

Thank you,
Parikshit.

Samvel · New User Joined: 19 Jul 2005 Posts: 1

Hi,
Are you dealing with variable length record? -If yes, have you correctly defined the LRECL compared with the longest record length?

mainframekk · New User Joined: 11 Jul 2005 Posts: 8

My case is..
The base file is a KSDS in variable length (keylength=31)
For the alt index file, the alt keylength is 17 and record length of alt index file is defined as 22,32572 using formula (5 + alt keylength + base keylength x number of duplicates)

where
32572 = 5 + 17 + 31n
n = 1050

When writting the 1051 duplicated record into alt index file, it returns 44.

Prasanthhere · Active User Joined: 03 Aug 2005 Posts: 306

hi

Tried to REWRITE a record of a different length.Check the record length