# Record-oriented filesystem

> file system where data is stored as collections of records

**Wikidata**: [Q7302818](https://www.wikidata.org/wiki/Q7302818)  
**Wikipedia**: [English](https://en.wikipedia.org/wiki/Record-oriented_filesystem)  
**Source**: https://4ort.xyz/entity/record-oriented-filesystem

## Summary
A record-oriented filesystem is a type of file system that stores data as collections of records, often used in mainframe and legacy systems. Unlike modern byte-stream filesystems, it organizes data into structured records, which can be accessed directly by applications. This approach is common in older operating systems like IBM VM/CMS and OpenVMS.

## Key Facts
- **Subclass of**: File system, specifically designed for structured data storage.
- **Related systems**: Includes the CMS file system (IBM VM/CMS) and Files-11 (OpenVMS/RSX-11).
- **Aliases**: Known as "レコード・オリエンテッド・ファイルシステム" in Japanese.
- **Wikidata description**: "File system where data is stored as collections of records."
- **Wikipedia coverage**: Available in English, Japanese, and Russian (3 languages).
- **Sitelink count**: 3 (limited online presence compared to general file systems).
- **Facet of**: Operating system design, emphasizing record-based data management.
- **Microsoft Academic ID (discontinued)**: 140045502.

## FAQs
### Q: How does a record-oriented filesystem differ from modern filesystems?
A: It stores data as structured records rather than unstructured byte streams, optimizing access for specific applications like databases or transactional systems.

### Q: What are examples of record-oriented filesystems?
A: Notable examples include the CMS file system (IBM mainframes) and Files-11 (used in OpenVMS and RSX-11 operating systems).

### Q: Why are record-oriented filesystems less common today?
A: Modern systems favor byte-stream flexibility for general-purpose use, while record-oriented designs are niche, suited for legacy or specialized applications requiring rigid data structures.

## Why It Matters
Record-oriented filesystems played a critical role in early computing, particularly in mainframe environments where structured data handling was essential for efficiency. By organizing data into fixed or variable-length records, these systems streamlined access for applications like banking or inventory management, reducing processing overhead. While largely supplanted by more flexible byte-stream filesystems in modern operating systems, their design influenced data management strategies in databases and transactional software. Understanding these filesystems provides insight into the evolution of data storage solutions and the trade-offs between structure and flexibility in system design.

## Notable For
- **Mainframe legacy**: Central to IBM VM/CMS and OpenVMS, iconic operating systems in enterprise computing.
- **Fixed-length records**: Often uses uniform record sizes for predictable access patterns.
- **Integration with hardware**: Optimized for tape or early disk storage systems common in mid-20th-century computing.
- **Specialized use cases**: Effective for batch processing, transaction logging, and structured datasets.
- **Multilingual recognition**: Documented in Japanese ("レコード・オリエンテッド・ファイルシステム"), reflecting its historical global use.

## Body
### Definition and Purpose
A record-oriented filesystem organizes data into discrete records, each representing a self-contained unit of information (e.g., a bank transaction). This structure enables efficient random access and batch processing, critical for early computing tasks.

### Historical Context
- **1960s–1980s**: Prominent in mainframe systems like IBM VM/CMS, where storage efficiency and direct record access were prioritized.
- **Decline**: Gradually replaced by hierarchical filesystems (e.g., Unix File System) that offered greater flexibility for diverse data types.

### Technical Characteristics
- **Record formats**: May use fixed-length (uniform size) or variable-length (delimited) records.
- **Access methods**: Supports sequential or direct access, depending on implementation.
- **Metadata**: Stores minimal metadata compared to modern filesystems, focusing on record identity and location.

### Examples and Legacy
- **CMS file system**: Native to IBM VM/CMS, emphasizing simplicity and integration with virtual machine environments.
- **Files-11**: Developed for DEC’s OpenVMS, supporting advanced features like record locking and transactional integrity.
- **Modern relevance**: Survives in niche applications (e.g., embedded systems, legacy enterprise software) requiring structured data handling.