The VSAM Connector Built for Mainframe Data Extraction
Extract VSAM files from z/OS, including KSDS, ESDS, and RRDS, and archive decades of mainframe data into open, queryable format, eliminating the need for COBOL scripts or manual layout translation.
🌟 Featured in Gartner® Hype Cycle™ for Data Management
Connectors
Data Governance
Enterprise Clients
Talk to a Connector Expert
VSAM Data Archiving, Done Right
Archon’s VSAM Connector reads VSAM datasets directly from z/OS using copybook-based record layout definitions, converting binary EBCDIC data, including packed decimal (COMP-3), binary (COMP), and zoned decimal fields, into structured, queryable records in ADS. The connector eliminates the need for custom COBOL extraction programs, handling all three VSAM organization types natively: key-sequenced (KSDS), entry-sequenced (ESDS), and relative record (RRDS).
VSAM remains the native file system for IBM z/OS mainframes across banking, insurance, government, and retail sectors, holding decades of master records, transaction files, and batch output accumulated in these organizations’ most critical operational systems. Mainframe modernization projects routinely identify VSAM data as the hardest extraction challenge, and Archon addresses this through direct processing of VSAM datasets.
- KSDS, ESDS, RRDS, and VRRDS VSAM organization types all supported
- COBOL copybook-based field definition with automatic packed decimal handling
- EBCDIC-to-UTF-8 conversion with CCSID codepage mapping
- Packed decimal (COMP-3), binary (COMP), and zoned decimal field types handled natively
- z/OS FTP, IBM Connect:Direct, and DFSORT/IDCAMS export paths supported
Capabilities
Everything You Need for VSAM Data Operations
Copybook-Based Record Layout Parsing
Archon uses COBOL copybook definitions to interpret VSAM record layouts, resolving COMP-3 packed decimal fields, COMP binary fields, and EBCDIC alphanumeric data without manual field mapping. Multiple record types in the same VSAM file are handled through copybook conditional logic.
EBCDIC to UTF-8 at Scale
All VSAM data is automatically converted from EBCDIC to UTF-8 with full CCSID codepage mapping. Packed decimal fields are converted to standard numeric with precision preservation. Binary integers are normalized to big-endian standard equivalents.
Mainframe Banking and Government Compliance
Every extracted VSAM record is cryptographically hashed, timestamped, and WORM-compliant at ingestion. Supports OCC, Federal Reserve, and FDIC banking record retention; NARA federal records retention schedules; state insurance commissioner requirements; and HIPAA minimum retention periods.
Mainframe Data Made Searchable
Archived VSAM records are immediately searchable via Archon Analyzer, including account master files, transaction records, policy files, citizen records, removing the need for a live z/OS environment, COBOL runtime, or mainframe access credentials.
Use Cases
How Enterprises Use the VSAM Connector
01 Mainframe Decommissioning
VSAM is invariably one of the last items addressed in a mainframe decommissioning project. Archon extracts VSAM master files and transaction datasets before z/OS hardware shutdown, converting decades of EBCDIC data into open-format queryable records in ADS, eliminating the mainframe dependency.
02 Core Banking Modernization
Community banks and savings institutions running core banking applications that use VSAM for account master and transaction files must archive this data before migrating to modern core banking platforms. Archon extracts VSAM account and transaction files with OCC-compliant immutability controls.
03 Insurance Policy and Claims Archive
Insurance companies with VSAM-hosted policy administration systems, including policy master files, premium transaction ESDS, claims KSDS, require long-term access for policy reinstatement, claims re-opening, and state regulator examination. Archon archives the complete VSAM record set with state insurance commissioner retention compliance.
04 Government Records Preservation
Federal and state government agencies running z/OS systems accumulate citizen records, tax data, and benefit payment files in VSAM across decades. Archon archives these with NARA-aligned retention schedules, making records retrievable for FOIA requests and GAO audits without live mainframe access.
Technical Specifications
| Connection Method | Connection via copybook and datafile |
|---|---|
| VSAM Types | KSDS, ESDS, RRDS, VRRDS |
| Record Layout | COBOL copybook-based field definition with automatic packed decimal handling |
| Character Sets | EBCDIC to UTF-8 conversion with codepage mapping (CCSID) |
| Data Types | Packed decimal (COMP-3), binary (COMP), zoned decimal, alphanumeric |
| Output Format | Parquet, Avro, XML, CSV, TXT, TSV, CSV, Excel |
| Transformation Rules | VSAM-specific field handling, copybook parsing |
| Retention Management | Policy-based retention with legal hold and WORM controls |
| Deployment | On-premises · Cloud (AWS) · Hybrid |
| Security & Compliance | TLS 1.3 in transit · AES-256 at rest · OCC · NARA · HIPAA · FDIC |
How It Works
Up and Running in 4 Steps
01
Connect to z/OS
Establish z/OS connectivity via FTP, IBM Connect:Direct, or DFSORT/IDCAMS export. Archon inventories VSAM dataset catalogue, record organization types, and available copybook definitions. 02
Map & Configure
Upload COBOL copybook definitions for each VSAM dataset. Archon parses copybooks automatically, configuring COMP-3, COMP, and EBCDIC field handling per record type. 03
Validate & Preview
Run a dry-run against sample VSAM records. The quality report validates copybook parsing accuracy, packed decimal conversion, and EBCDIC translation before full extraction. 04
Archive & Monitor
Execute the full VSAM extraction. Cryptographic hashes applied per record. Mainframe data immediately searchable via Archon Analyzer on arrival in ADS.FAQ
Common Questions About the VSAM Connector
- 1. Does Archon require COBOL copybooks for every VSAM dataset, or can it infer record layouts?
Archon can infer record layouts where possible, at the same time supports copybooks for precise mapping when needed.
- 2. How does Archon handle VSAM files with multiple record types (multi-format ESDS)?
Archon identifies and maps multiple record formats, preserving structure and relationships.
- 3. Can Archon extract VSAM files without impacting z/OS production batch performance?
Yes, Archon uses optimized, low-impact methods to avoid disruption to batch workloads.
- 4. How does Archon ensure VSAM banking records meet OCC record retention requirements?
Archon ensures compliance by enforcing retention policies, immutability, and full audit trails.
- 5. What z/OS connectivity options does Archon support for VSAM extraction?
Archon supports multiple options including direct connectors, APIs, and secure data transfer methods.
Ready to archive your VSAM data and retire the dependency?
Talk to an Archon integration specialist at archondatastore.com. Free consultation, no commitment, reply within 24 hours.
