All systems

AS/400 (IBM i)

IBM i physical files
Supported

Prepare

  1. Upload AS/400 data
Guide

IBM AS/400 (now IBM i) is a widely-used midrange computer system in enterprise environments. It features an integrated database (DB2 for i) and robust business application support.

What You Can Upload

  • Physical files (PF) - data exports
  • Save files (.SAVF)
  • Exported CSV or XML from IBM i
  • DDS source files (optional, for schema)
  • ZIP archive with complete file sets

What You Get Out

DataMeans extracts your data into multiple modern formats:

OutputDescription
csv/{TableName}.csvOne CSV file per table with all row data
xlsx/{TableName}.xlsxExcel workbook per table
xls/{TableName}.xlsLegacy Excel format per table
json/{TableName}.jsonJSON array of records per table
json/{TableName}.jsonlNewline-delimited JSON (streaming-friendly)
postgres.sqlPostgreSQL CREATE TABLE + INSERT statements
schema/schema-graph.jsonRelationship graph for visualization
schema/er-model.jsonER model for diagram tools
report.jsonStructured extraction report
report.mdHuman-readable extraction summary

How to Export / Obtain Files

  1. On IBM i, use CPYTOIMPF to export physical files to CSV/IFS
  2. Or use SAVOBJ to create save files (.SAVF)
  3. FTP the exported files to your local system
  4. Include DDS source if available for better schema mapping
  5. Create a ZIP with all files
  6. Upload the ZIP to DataMeans

Supported Features

  • Physical file (PF) data extraction
  • Logical file (LF) view definitions
  • DDS (Data Description Specifications) parsing
  • EBCDIC to ASCII conversion
  • Packed decimal and zoned decimal fields
  • Date and time format conversion
  • Multi-member file handling

Known Limitations

  • Requires exported files (not raw disk images)
  • Complex SQL stored procedures documented but not converted
  • Some proprietary IBM formats may need preprocessing

Troubleshooting

IssueSolution
Character encoding errorsVerify EBCDIC to ASCII conversion settings
Date format issuesCheck job date format (MDY, DMY, YMD)
Missing fieldsInclude DDS source for complete schema

Last updated: January 2026

Technical reference

Overview

AS/400 (now IBM i) is an integrated business computer system developed by IBM, featuring a built-in relational database called Db2 for i. The system uses a proprietary object-based architecture where all resources (files, programs, devices) are treated as objects. The database supports both traditional record-oriented access and modern SQL, with advanced features like journaling, commitment control, and referential integrity.

History and Background

  • 1988: AS/400 announced in June as successor to System/36 and System/38; first systems shipped in August with OS/400.
  • 1994: AS/400 Advanced Series models introduced; integrated database named DB2/400.
  • 1995: Product line moved to 64-bit PowerPC AS (RISC) processors.
  • 2000: Renamed to eServer iSeries as part of IBM's eServer branding initiative.
  • 2004: eServer i5 systems introduced with POWER5 processors; OS/400 renamed i5/OS.
  • 2006: Renamed to System i.
  • 2008: System i and System p merged into IBM Power Systems; i5/OS renamed IBM i with release 6.1.
  • 2019: IBM i 7.4 released, introducing Db2 Mirror for i.
  • 2022: IBM i 7.5 released with security enhancements and a BOOLEAN SQL data type.

File Format Specifications

Database Objects:

  • Physical files: Tables containing data records
  • Logical files: Views and indexes over physical files
  • Source physical files: Program source code storage
  • Display files: User interface definitions
  • Printer files: Report output specifications

File Structure:

  • Record format level identifiers for compatibility
  • Field-level descriptions with data types and attributes
  • Access paths defined through logical files
  • Member concept allows multiple data sets per file
  • Integrated file system (IFS) for stream files

Storage Architecture:

  • Single-level store architecture
  • Db2 for i integrated database
  • Object-based security model
  • Journaling for audit trails and recovery
  • Commitment control for transactions

Data Types and Structures

TypeSizeDescription
CHARFixedFixed-length character strings
VARCHARVariableVariable-length character strings
GRAPHICFixedFixed-length double-byte strings
VARGRAPHICVariableVariable-length double-byte strings
BINARYFixedFixed-length binary data
VARBINARYVariableVariable-length binary data
SMALLINT2 bytes16-bit signed integers
INTEGER4 bytes32-bit signed integers
BIGINT8 bytes64-bit signed integers
DECIMALVariablePacked decimal numbers
NUMERICVariableZoned decimal numbers
FLOAT4/8 bytesSingle/double precision floating point
DATE4 bytesDate values (YYYY-MM-DD)
TIME3 bytesTime values (HH:MM:SS)
TIMESTAMP7-13 bytesDate and time with fractional seconds
BLOBVariableBinary large objects
CLOBVariableCharacter large objects
DBCLOBVariableDouble-byte character large objects

Database Features:

  • Referential integrity constraints
  • Check constraints and triggers
  • User-defined functions and procedures
  • Materialized query tables
  • Row and column access control

Version Differences

VersionYearKey FeaturesOS Branding
V1R11988First release; integrated relational databaseOS/400
V3R11994Referential integrity, triggers; DB2/400 nameOS/400
V4R11997AS/400e series; e-business focusOS/400
V4R41999Logical partitioning (LPAR)OS/400
V5R12001Linux in secondary logical partitionsOS/400
V6R12008POWER6 processor supporti5/OS, renamed IBM i
7.12010XML data type; Technology Refresh modelIBM i
7.22014Row and column access control (RCAC)IBM i
7.32016Temporal tables, authority collectionIBM i
7.42019Db2 Mirror for iIBM i
7.52022Security enhancements, BOOLEAN typeIBM i

Compatibility Notes:

  • Record format levels ensure application compatibility
  • SQL access available alongside native I/O
  • Some features require minimum OS levels
  • Migration tools available for hardware upgrades
  • Backward compatibility maintained for business applications

Technical References


To learn how to use this format with DataMeans, see the User Guide.