Re: VSAM write error: file status key = 24

2021-02-09 Thread Joel C. Ewing
Perhaps because if you reorg the file with adequate CI/CA free space internally, the record you are trying to insert or extend might be able to find enough CI/CA internal free space without requiring a split that would violate the restrictions of SHR(,4)   The restrictions of that SHAREOPTION

Re: VSAM write error: file status key = 24

2021-02-09 Thread Joe Monk
what does any of that have to do with file status 24 on a write? A file status of 24 means the file needs a REORG. Joe On Tue, Feb 9, 2021 at 5:46 AM Mike Kerford-Byrnes wrote: > From page 15 of "OS/VS VSAM Data Set Sharing" GG22-9043:- > > > > Cross-region or Cross-System

VSAM write error: file status key = 24

2021-02-09 Thread Mike Kerford-Byrnes
>From page 15 of "OS/VS VSAM Data Set Sharing" GG22-9043:- Cross-region or Cross-System SHAREOPTION 4 - .VSAM takes three other special actions as the data set is being processed: * A change of High Used RBA is prevented. For a KSDS, this means no CA splits, no adds of new Cas

Re: VSAM write error: file status key = 24

2021-02-08 Thread Farley, Peter x23353
DU Subject: VSAM write error: file status key = 24 Greetings, After REPRO-ing a VSAM KSDS file defined with shareoptions (4,3) to a file defined with shareoptions (4,4), we started receiving the following error on a write attempt (COBOL program): Status key=24 Meaning: An attempt was made to wr

VSAM write error: file status key = 24

2021-02-08 Thread Steff Gladstone
Greetings, After REPRO-ing a VSAM KSDS file defined with shareoptions (4,3) to a file defined with shareoptions (4,4), we started receiving the following error on a write attempt (COBOL program): Status key=24 Meaning: An attempt was made to write beyond the externally defined boundaries of a