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 would seem to severely limit what kind of updates could be safely made to the data set. Basically, you could update existing records with records of the same length or delete records; but adding arbitrary new records or increasing the length of a arbitrary record carries a much higher risk of failure than when using a SHAREOPTION that allows the High-Used RBA to be extended. Joel C Ewing On 2/9/21 6:04 AM, Joe Monk wrote: > 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 <[email protected]> > wrote: > >> 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 to the end of the dataset, and consequently >> no new extents. For an ESDS or an RRDS, it means no Cis can be added to >> the >> end of the dataset. >> * A change of High-key RBA is prevented (KSDS only). This means that >> the high-key CI cannot be split and that new Cis cannot be added logically >> to the end of the data set. However, free space imbedded within the file >> can be used. >> * Data and sequence set buffers are refreshed for direct processing. >> (more stuff that does not relate to the problem you describe). >> >> >> >> The manual was written in 1980! I am not aware of any changes since then, >> but it is an area of VSAM with which I did not have much involvement - most >> users avoided SHR(,4) like the plague! >> >> >> >> Mike Kerford-Byrnes >> >> >> >> >> ... -- Joel C. Ewing ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
