Space errors are the family of failures where VSAM or allocation services cannot obtain enough tracks or control structures to satisfy a PUT, a CA split, or an extend. They differ from catalog errors because the name usually resolves correctly—the system simply cannot grow the footprint under current rules. Beginners should avoid the trap of staring only at DASD free percentages in ISPF. The meaningful story lives in LISTCAT: primary and secondary quantities, extent counts, volume lists, SMS data class ceilings, and the relationship between high-used and high-allocated RBA. This page buckets common causes, suggests an interview script for storage teams, and reminds you to correlate technical ceilings with business calendars so you do not fight ghosts every quarter.
| Class | Symptom | Direction |
|---|---|---|
| Zero secondary | Cluster cannot extend when primary fills | DEFINE larger or ALTER per policy; REPRO |
| Wrong volume list | Allocation cannot find eligible volume | Correct volume list; SMS ACS |
| Extent limit | Messages referencing max extents | Larger primary/secondary; fewer fragments |
Sometimes the VSAM file is an application log that grew faster than forecasts. Capacity can add space, but product owners should also rotate or archive logical data. Purely technical fixes without governance refill disks in weeks.
Monthly automated LISTCAT extracts for top N largest clusters catch slope changes early. Pair with business owners for seasonal forecasts. Prevention is cheaper than heroic 2 a.m. extends during freeze windows.
Compressed or extended-format VSAM datasets still obey allocation ceilings. Sometimes administrators see larger logical capacity assumptions in documentation than the physical tracks available after compression savings reverse during incompressible data phases. Trend actual high-used growth, not only marketing charts about compression ratios.
When FTP or replication tools move VSAM exports between systems, space errors can appear on the target if block sizes or SMS classes differ. Build a target-side checklist that mirrors the source LISTCAT allocation summary so IMPORT or REPRO targets have headroom before cutover windows begin.
Space errors sometimes reflect pool policy: test volumes cannot absorb production-sized extends even though a nearby pool has terabytes free. Navigating those policies requires the storage service catalog and sometimes a finance code to move a dataset class. Document which pool each critical VSAM file is supposed to live in before cutover weekend fatigue makes everyone accept risky temporary pools.
Space errors mean your toy box cannot grow wider even though the room has floor space: maybe the lid is nailed shut (extent rules), maybe the box is only allowed on one shelf (volume list), or maybe you already borrowed all extra boxes allowed this week (secondary zero). Ask the grownup with the hammer policy (storage) which rule applies.
1. What should you inspect when inserts fail near month-end?
2. Why might free space on volume A not help a cluster constrained to volume B?
3. True or false: High-used RBA near high-allocated always means safe room for huge inserts.