Correct me if I am wrong, but isn't error 24 just "I ran out of space", like an x37 abend for a sequential file that ran out of extents due to too-small primary/secondary allocations?
How much primary and secondary space was specified for the data component of the (4, 4) copy? How much space does the data component of the (4,3) version use today? Are the index component allocations the same in both versions? Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Steff Gladstone Sent: Monday, February 8, 2021 12:20 PM To: [email protected] 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 write beyond the externally defined boundaries of a relative or indexed file. The (4,4) file is identical to the (4,3) file in all respects except for the shareoptions. The error never occurs for the (4,3) file and occurs intermittently for the (4,4) file. Can anyone suggest what the problem might be? Thanks, Steff Gladstone -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
