Stay Ahead in Mainframe Tech

Read the latest trends in COBOL migration and mainframe security best practices from industry leaders

Full

Enhanced Definition

In the context of mainframe systems, "Full" describes a state where a storage resource (such as a dataset, DASD volume, or buffer) or a processing queue has reached its maximum allocated capacity, preventing any further data from being written, stored, or processed until space is made available or capacity is increased.

Key Characteristics

- Resource Exhaustion: Signifies that a specific allocated resource has no remaining available space, extents, or slots.
- Operational Impact: Can lead to program ABENDs (e.g., B37, D37, E37 for datasets), job failures, system slowdowns, or unavailability of critical services.
- Capacity Management: Often managed through JCL space parameters (SPACE), SMS policies, system-defined limits for buffers and queues, or application-specific configurations.
- Error Conditions: Typically results in specific error messages, ABEND codes, or return codes that indicate the type of resource that has become full.
- Dynamic vs. Static: Some resources (like VSAM datasets) can be dynamically extended if configured, while others require manual intervention, job re-execution with increased allocation, or data offloading.