Db2 and mainframe data to Databricks

fa source inspect db2
fa source plan db2 --variant db2_luw
fa source plan db2 --variant db2_zos --json

The mainframe archetype keeps platform differences explicit. Variants are Db2 LUW, Db2 for z/OS, and Db2 for IBM i. Inventory tables, packages, SQL PL, utilities, load jobs, CDC or log capture, JCL and batch dependencies, encodings, and consumers.

Airlift records a consistent unload or replication boundary, commit sequence, restart checkpoint, batch window, file manifest, and reconciliation evidence from the selected adapter. It routes z/OS utilities, JCL coupling, SQL PL packages, legacy encodings, and cross-platform transaction behavior into owned residue instead of hiding them in a SQL conversion percentage.

Validation profiles should include EBCDIC and code-page behavior, decimal and date semantics, package behavior, commit ordering, batch totals, restart, and representative window performance. Certification and cutover use the same signed evidence, separation of duties, frozen wave, and rollback model as other Airlift sources.

The public pack is cataloged; live platform access and certified extraction/cutover effectors are external evidence gates.

Complete developer command sequence

Generate this exact recipe from the installed CLI so the guide and executable surface stay in sync:

fa source recipe db2
fa source recipe db2 --variant db2_luw --json > .airlift/db2-recipe.json

The App is engagement-aware. IBM Db2 and mainframe data appears under Active sources only after the source estate is added to an active engagement. The menu is derived from governed engagement scope; installing Airlift does not expose unrelated source pages.

Every remote mutation below requires --host, --org, authenticated workspace identity, and a stable --idempotency-key. JSON request files contain identifiers, artifact references, and opaque credential references—never passwords, tokens, or connection strings. Run fa <resource> <operation> --help for the current schema and exit semantics.

0. Inspect the source contract

fa source inspect db2 --json > .airlift/db2-profile.json
fa source plan db2 --variant db2_luw --json > .airlift/db2-capability-plan.json

Expected artifacts:

• .airlift/db2-profile.json
• .airlift/db2-capability-plan.json

Open Engagements → active engagement in the App. This stage is visible at /engagements after replacing the placeholder ID with the governed engagement ID.

1. Create governed scope and connection references

fa engagement create --file engagement.json --idempotency-key migration-create-v1
fa estate register --file db2-estate.json --idempotency-key db2-estate-v1
fa connection register --file db2-connection.json --idempotency-key db2-connection-v1
fa engagement update --file db2-scope.json --idempotency-key db2-scope-v1
fa engagement preflight <engagement-id>

Expected artifacts:

• Governed engagement
• Source estate
• Opaque connection binding

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id> after replacing the placeholder ID with the governed engagement ID.

2. Assess and accept inventory

fa assessment start --file db2-assessment-start.json --idempotency-key db2-assessment-start-v1
fa assessment status <assessment-id> --json
fa assessment record --file db2-assessment-record.json --idempotency-key db2-assessment-record-v1
fa assessment accept --file db2-assessment-accept.json --idempotency-key db2-assessment-accept-v1
fa inventory list --estate-id <estate-id> --json

Expected artifacts:

• Assessment report reference
• Normalized inventory
• Dependency graph

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/sources/db2 after replacing the placeholder ID with the governed engagement ID.

3. Implement the admitted source adapter

No source-specific executable compiler exists in this release. Continue with assessment, governed work, and an admitted adapter; Airlift does not invent executable output.

Expected artifacts:

• Capability plan and adapter requirements only

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/artifacts after replacing the placeholder ID with the governed engagement ID.

This source is cataloged or assessable but has no source-specific executable compiler in the installed Airlift generation.

4. Convert, move, and remediate

fa plan generate --file db2-migration-plan.json --idempotency-key db2-plan-v1
fa conversion batch create --file db2-batch.json --idempotency-key db2-batch-v1
fa conversion batch start --file conversion-batch-start.json --idempotency-key conversion-start-v1
fa residue list --engagement-id <engagement-id>
fa transfer plan --file db2-transfer.json --idempotency-key db2-transfer-v1
fa transfer run <transfer-id> --idempotency-key transfer-run-v1
fa transfer reconcile <transfer-id> --idempotency-key transfer-reconcile-v1

Expected artifacts:

• Target artifacts
• Residue cases
• Transfer checkpoints
• Reconciliation evidence

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

5. Validate independently and inspect discrepancies

fa validation run --file db2-validation.json --idempotency-key db2-validation-v1
fa validation status <validation-execution-id> --json
fa discrepancy list --engagement-id <engagement-id>
fa artifact list --engagement-id <engagement-id>

Expected artifacts:

• Provider run references
• Readiness evidence
• Discrepancies

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

6. Certify, cut over, and export evidence

fa certificate list --object-id <object-id>
fa cutover status <wave-id> --json
fa evidence list --engagement-id <engagement-id>
fa evidence export --file db2-evidence-export.json --idempotency-key db2-evidence-export-v1

Expected artifacts:

• Migration certificates
• Cutover evidence
• Content-digested evidence export

Open Engagements → active engagement in the App. This stage is visible at /assurance after replacing the placeholder ID with the governed engagement ID.

Runway executes releases; Experiments owns validation verdicts; Airlift owns migration readiness and cutover policy.

What developers see in the App

The contextual source workspace shows the accepted estate and the factory stages for this engagement. Artifacts displays immutable references, content digests, media types, and provider lineage. Runs displays assessment, conversion, transfer, validation, and deployment executions without treating a provider's success as an Airlift verdict.

View full size

These are automated captures from public synthetic engagements. The source workspace is specific to IBM Db2 and mainframe data; no unrelated source is presented as its migration journey. For sources without an evidence-backed journey, the image demonstrates setup, navigation, and developer entry points only—not a live connection, converted output, or certified migration. No client data, credentials, workspace hostnames, or internal deployment identifiers are embedded in the images.