Helper I+1 — and please scope this specifically to **Db2 for i (IBM i / AS-400)**, not just generic DB2. Db2 for i, LUW, and z/OS are different engines, and Db2 for i is the one with no native OneLake path today.
This is the ERP backend for a large JD Edwards / IBM i install base that's moving to Fabric. Today the only options are batch Copy pipelines (not real mirroring) or a paid third-party Open Mirroring tool. Native journal-based CDC mirroring (snapshot + continuous changes into OneLake Delta, via the on-prem data gateway) would remove that friction and drive real Fabric adoption in the IBM i segment. The source-side change stream already exists through Db2 for i journaling, so the capture pattern is proven — the native integration is what's missing. Happy to be a preview customer for the JDE-on-IBM i use case.
