Long-term Infor LX (BPCS) data archival on cloud object storage. Queryable Parquet, EBCDIC-faithful, COMP-3-precise, hash-signed audit evidence preserved for SOX, IRS and FDA 21 CFR Part 11. Tier to cold storage at $1–4 per TB per month versus $200–800 per TB per month for an active IBM i.
Once BPCS is no longer the system of record, every dollar spent on IBM i Power hardware, IBM Software Maintenance, Infor LX support and RPG / AS/400 operator staffing is overhead. An Infor LX (BPCS) data archival removes the overhead while preserving the data and the audit trail.
Many BPCS customers find themselves in the same position: the live operational use case has moved to a modern ERP — Oracle Fusion, NetSuite, SAP S/4HANA or another platform — but BPCS is kept alive on the IBM i because finance, tax or compliance still needs to query 10–20 years of historical GL transactions, work-order batch records or supplier invoices. The cost of keeping that dormant BPCS alive is rarely tracked properly: an IBM i Power9 / Power10 LPAR with the licences and IBM Software Maintenance contract, an Infor LX support agreement, AS/400 operator and RPG developer salaries to keep the lights on, plus the security and patching overhead of running an aging IBM i in a modern security posture.
An Infor LX (BPCS) data archival replaces all of that with structured, queryable, tamper-evident Parquet on cloud object storage. Every BPCS file in scope (GLM, GLT, APH, RAH, IIM, IIH, MHM, ECH and the audit-trail and journal files) is extracted once, hash-signed, normalised to UTF-8 with COMP-3 unpacking, and stored in tiered cloud storage. The IBM i Power LPAR is then powered down. Auditors, finance analysts and tax queries hit the archive directly via SQL — no AS/400 expert required, no Infor LX licence renewal needed.
The economics are typically dramatic. A 5 TB BPCS database that costs $50K–$200K per year to keep alive on a Power LPAR with IBM Software Maintenance can be archived to S3 Glacier Deep Archive for $200–800 per year (a 50–500× reduction). The savings compound across the 7–30+ year retention window and typically pay back the Infor LX (BPCS) data archival project in under 12 months.
Compliance, finance and tax teams sign off because the evidence pack is constructed to their standard.
Every Parquet file in the archive is SHA-256 hashed and the hash is recorded in a signed manifest. Any tampering — accidental or malicious — is immediately detectable on next access.
BPCS audit-trail files (GLAT, APAT, RAAT, IIAT, MHAT) captured in their original form alongside the converted form. Auditors can drill from any GL journal line back to the originating RPG program execution decades later.
QSQJRN database journals captured for every period in retention. Every insert / update / delete with user, terminal and timestamp preserved. Reconstruction of any transaction at the database-write level possible decades later.
Data stored as UTF-8 Parquet for queryability, but the original EBCDIC field plus source CCSID is preserved as metadata. Any field can be re-rendered in its original BPCS form on demand for audit walkthrough.
Archives can be locked to S3 Object Lock / Azure Blob Immutability in compliance mode — write-once-read-many for the full retention period. SOX / FDA reviewer-approved configuration.
Pre-built semantic layer hides BPCS field-naming quirks (GLT, GLM, IIM become Finance.JournalLine, Finance.Account, Item.Master). Self-serve SQL / BI for finance, audit, tax without IT involvement.
A repeatable, governed workflow built for clean AS/400 decommissioning. Typical timeline: 8–14 weeks for a 5–20 TB BPCS instance.
Inventory BPCS libraries (LXFILES, LXMODOBJ, custom libraries), identify every file in retention scope, establish per-domain retention policy (SOX 7yr, IRS 4–7yr, FDA 30+yr, state-specific), confirm WORM lockability requirement with compliance / legal.
Cloud storage target chosen (S3 / GCS / Azure Blob), tiering policy designed (Hot → Cool → Cold lifecycle), KMS key management defined, IAM access policy for read-only analyst access drafted, audit-log SIEM integration designed.
DB2 for i extractor pulls every BPCS file in scope to UTF-8 Parquet with COMP-3 unpacking, EBCDIC round-trip metadata, and hash-signed manifests. IBM i database journals captured in parallel. Multi-TB GLT and ITH extracts scheduled to off-peak.
Signed evidence pack constructed: manifest, hash signatures, audit-trail captures, IBM i journal captures, chain-of-custody log, optional RPG source-code snapshot for FDA 21 CFR Part 11 customers. Evidence pack signed with customer-controlled KMS key.
Pre-built semantic layer deployed (Athena views / BigQuery views / Snowflake / Trino) hiding BPCS field-naming quirks. Read-only IAM access provisioned for finance, audit, tax analysts. Sample queries validated against IBM i source results.
Final delta capture from IBM i journal, archive locked to WORM if required, IBM i Power LPAR moved to read-only and ultimately powered down. Infor LX licence non-renewal, IBM Software Maintenance contract termination, AS/400 operator role transitioned.
What customers actually save when they replace a dormant IBM i with cloud archive storage.
IBM Power9 / Power10 LPAR refresh avoidance ($50K–$200K capex per refresh cycle), IBM Software Maintenance termination ($20K–$80K per year), Infor LX support contract termination ($30K–$150K per year).
AS/400 operator role transitions (1 FTE typical), RPG developer / contractor spend ends (often 0.5–2 FTE equivalent in retained engagements), IBM i security / patching overhead absorbed.
5 TB BPCS archive at S3 Glacier Deep Archive: ~$5/month. 50 TB: ~$50/month. Add ~10% for query / restore activity on demand. Total typically <$2K/year for the largest customer archives.
Power consumption avoidance (an IBM Power LPAR typically draws 1–5 kW continuous), data-centre rack space, cooling, fire suppression — particularly material for on-prem AS/400 customers.
Most Infor LX (BPCS) data archival projects pay back in 8–14 months from the IBM i decommissioning date. Beyond payback the savings compound across the full SOX / FDA retention window — typically 7–30 years.
Aging IBM i hardware failure risk eliminated. RPG / AS/400 skills cliff irrelevant. IBM i security patching cycle no longer required. Compliance posture upgraded to modern cloud baseline.
Infor LX (BPCS) data archival is the long-term preservation of BPCS transactional and master data in a queryable, signed and tamper-evident form — typically because you are retiring the IBM i hardware and the BPCS application but still need to satisfy SOX (7 years), IRS (4–7 years), FDA 21 CFR Part 11 (pharma, often 30+ years for regulated batch records) or audit requirements. A backup is an opaque blob that requires the original BPCS application and an IBM i LPAR to make readable; an Infor LX (BPCS) data archival is structured, queryable Parquet or columnar storage that any analyst can query with SQL without ever touching the AS/400 again. Syntra ETL's archive preserves the full audit chain — BPCS audit-trail files (GLAT, APAT, RAAT, IIAT, MHAT) plus IBM i database journals — so auditors can drill from a GL journal line back to the originating RPG program execution, even decades later.
Infor LX (BPCS) data archival becomes the right move when the cost of keeping BPCS live (IBM i hardware refresh, Power-server licence, IBM Software Maintenance, Infor LX support contract, RPG developer salaries, AS/400 operator staffing) exceeds the business value the live system delivers. Typical triggers: the active operational use case has already moved (you cut over to Oracle Fusion, NetSuite or another modern ERP and BPCS is only kept alive for retro-reporting), the IBM i is heading for a hardware refresh and finance is questioning the spend, or an M&A divestiture leaves an orphan BPCS instance with no operational future. In all three cases, Infor LX (BPCS) data archival lets you retire the AS/400 and the Infor LX licence while keeping the data queryable for compliance and audit.
The full BPCS footprint can be archived. Financials: GL master (GLM), GL transactions (GLT) — typically 7–20+ years, GL audit trail (GLAT), AP files (APH/APT/APO/APAT), AR files (RAH/RAT/RAO/RAAT), Fixed Assets (FAM/FAT). Manufacturing: BOMs (PSM/PSC) with effectivity-date history, routings (RTM/RTO), work-order history (MHM/MHD/MHAT), shop-floor hours (HRM) — critical for FDA 21 CFR Part 11 batch traceability. Inventory: item master (IIM), item-balance history (IIH), inventory transactions (ITH) — multi-decade for some industries. Order Management: sales order history (ECH/ECL), shipment history (SHP). Procurement: PO history (HPO/HPL). Plus the IBM i database journals at QSQJRN level capturing every insert / update / delete with user, terminal and timestamp.
Faithfully. The archive stores data in UTF-8 Parquet (standardised, queryable in every modern tool) but the original EBCDIC field plus the source CCSID is captured as metadata so the round-trip is provable for audit. COMP-3 packed-decimal and zoned-decimal numerics are unpacked to decimal with full precision preserved (no float rounding) and the source field-definition is captured as metadata. CYYMMDD zoned-decimal dates (BPCS's signature date format) are normalised to ISO 8601 with the original CYYMMDD form preserved for retro-reporting reproducibility. Any field can be re-rendered in its original BPCS form on demand for audit walkthrough.
Every archive ingest produces a tamper-evident evidence pack: SHA-256 hash signature of every Parquet file, signed JSON manifest with record counts and sum totals per partition, source BPCS audit-trail capture (GLAT, APAT, RAAT, IIAT, MHAT files in their original form alongside the converted form), IBM i database journal capture for the same period (so auditors can reconstruct any transaction at the database-write level), and a chain-of-custody log capturing the extractor user, IBM i source LPAR, SQL queries executed and target storage bucket. The evidence pack is signed with a customer-controlled KMS key and can be locked to write-once-read-many (WORM) S3 / Azure Blob immutability storage for SOX or FDA compliance.
Storage tiers handle the long retention requirement economically. Hot tier (queryable in seconds, typical for current FY + prior FY) sits on S3 Standard / Azure Hot. Warm tier (queryable in minutes, typical for years 2–7) auto-transitions to S3 IA / Azure Cool. Cold tier (queryable in hours via restore, typical for FDA 21 CFR Part 11 batch records held for 10–30+ years) sits on S3 Glacier Deep Archive / Azure Archive — costing $1–4 per TB per month versus the $200–800 per TB per month an active IBM i Power LPAR costs to host the same data. Lifecycle policies automate the tier transitions so retention cost drops 95–99% over the life of the archive.
Yes — that's the point. The archive is structured Parquet on cloud object storage with a standard SQL query layer (Athena, BigQuery, Snowflake or Trino / Presto depending on your cloud) so finance, audit, tax and compliance analysts query directly with standard SQL or BI tools (Tableau, Power BI, Looker, Oracle OAS). A pre-built read-only Infor LX (BPCS) data archival semantic layer hides the BPCS field-naming quirks (file names like GLT, GLM, IIM, ECH become Finance.JournalLine, Finance.Account, Item.Master, Order.Header for self-serve analysts) so business users don't need to know what GLAT or QSQJRN means. Every query is logged for SOX / FDA evidence of access.
RPG IV / III, COBOL, CL and DDS display files are IBM i platform-bound and don't carry forward. For Infor LX (BPCS) data archival (as opposed to live migration), the goal is read-only analytical and audit access, not re-execution of business logic — so the RPG / COBOL code itself does not need to be preserved beyond a source-code snapshot kept for audit reference. What is preserved is the result of every RPG program execution: the actual data writes captured in the GLAT / APAT / RAAT / IIAT / MHAT audit-trail files and in the IBM i database journals. Auditors can see exactly what every RPG program did to the data, even decades after the program itself stopped running. Pharma customers under FDA 21 CFR Part 11 typically also snapshot the RPG source code into the evidence pack for completeness.
30-minute call. Walk through your BPCS volumes, retention requirements (SOX / IRS / FDA), IBM i landscape and target cloud platform — leave with a concrete Infor LX (BPCS) data archival plan and a credible business case for AS/400 decommissioning.