Based on the available docs and forum content, there is no explicit guidance on: - Using

com.ibm.as400.access.AS400JDBCDriver

with the existing IBM Db2 source connector, or - Officially supporting DB2 on AS400 / IBM i via that driver. The IBM Db2 connector is documented as using the IBM Data Server Driver for JDBC and SQLJ (

com.ibm.db2:jcc

), i.e., the standard Db2 Type 4 JDBC driver, not the AS400-specific driver. [[Db2 source](https://docs.airbyte.com/integrations/sources/db2)] There is also an unanswered community question asking whether Airbyte can connect to “IBM DB2 as400,” with no confirmation or example of doing so. [[Forum 2947](https://discuss.airbyte.io/t/2947)] You can modify connectors for your own usage by forking the repo, changing code and dependencies (e.g., switching the JDBC driver in a Java connector), building the image locally, and then using it as a custom connector in Airbyte. [[Custom connectors](https://docs.airbyte.com/integrations/custom-connectors); [Developing locally 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#connector-contributions)] For Java JDBC-based sources, support has suggested starting from an existing JDBC-based connector (like Postgres) when building new sources. [[Custom Java source](https://discuss.airbyte.io/t/192)] However, the knowledge sources do not provide step‑by‑step instructions or confirmation that replacing the Db2 driver with

AS400JDBCDriver

will work, so I cannot state it is supported. From the docs I can only say: - Technically you can fork and modify the Db2 connector to use another JDBC driver and run it as a custom connector. [[Custom connectors](https://docs.airbyte.com/integrations/custom-connectors); [Developing locally 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#connector-contributions)] - There is no documented guarantee that this will successfully support AS400 Db2 with

com.ibm.as400.access.AS400JDBCDriver

.