I have encountered the following.
A VSAM KSDS is defined with, say, 200 cylinders and then loaded with some data. This data occupies the first 150 cylinders, so the Highest CA is at the 75% mark, as is the HARBA. Both CI and CA Freespace are non-zero. When SHR is NOT 4, CI and CA splits can occur within the first allocation until it is full. Then they can continue to expand into such secondary allocation as is defined. Also records with a higher key that the current high-key can be added to the file without any problems (space permitting, of course) When SHR IS 4 CI splits can occur within any or all of the CAs, so long as it does not lead to a CA split which, as I cited from the manual, is not allowed. The High-key is not allowed to change either, so you cannot add data to the end of the current set. So you can wind up (and I did!) with a situation where a file is only 75% full (HURBA/HARBA) but the addition of extra records yields an error (VSAM FDBK code 0x1C). The situation is even more bizarre if the file has 0% CA Freespace when loaded, since the first CI Split after initial load will lead to a CA split (which is, by definition, disallowed). REORGing the file will result in the records a of course put the records back exactly where they were and so the problem will persist. In these cases, I have loaded the file with non-zero CI and CA freespace (this allows some room or the insertion/expansion of data) and the ALTERed the CA FSPC back to 0. Mike Kerford-Byrnes ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
