Mainframe Migration Toolkit
Python tools and runtime support for specification-led COBOL and JCL migrations to PySpark.
Installation
Install the complete runtime:
python -m pip install "mainframe-migration-toolkit[all]"
Python 3.10 or newer is required. Java 17 is required for the bundled dataset validator and is recommended when running PySpark pipelines.
Quick start
Initialize a migration workspace from its parent directory:
python -m mainframe_toolkit init-workspace .
The command creates an isolated migration/ Git repository and preserves existing source, input, and golden-dataset directories outside that repository.
Inspect the initialized workspace:
python -m mainframe_toolkit inspect migration --strict
Claude Code can run the orchestrated multi-agent workflow from migration/:
claude --agent mainframe-migration-supervisor
In Devin, invoke migrate-mainframe-job. The toolkit installs the native entry skill in .devin/skills/ and worker agents in .devin/agents/; the principal session coordinates them sequentially. If delegation is unavailable, it continues the work itself. No ACP setup is required. Existing customized assets are preserved and reported as conflicts by init-workspace; review old .agents/skills/ migration definitions before removing them. While these legacy definitions remain, installation of native Devin assets is deferred to avoid competing instructions; Claude assets can still be updated.
Other commands parse JCL and copybooks, convert sequential datasets, scaffold PySpark jobs, analyze source similarity, and validate output against golden datasets. Run python -m mainframe_toolkit --help for the complete command list.
Generated programs expose pure DataFrame functions. The caller wires FunctionStep,
InputBinding and OutputBinding; optional OutputSink exports an output while
the next program receives its canonical DataFrame in memory. Readers, raw
contracts, to_canonical mappers and canonical contracts remain separate.
Contract checks inspect structure/schema only; conversion errors arise from
native Spark expressions on normal actions. CSV and Parquet readers/writers
are provided; custom sources, mappers and sinks use explicit callables.
PipelineProgram/ProgramStep remain compatible with previously generated jobs.
Use python -m mainframe_toolkit references --path for runnable examples.
Metadata
Release files for mainframe-migration-toolkit 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mainframe_migration_toolkit-0.5.0.tar.gz | 102.1 kB | Without provenance | Details for mainframe_migration_toolkit-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mainframe_migration_toolkit-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for mainframe_migration_toolkit-0.5.0-py3-none-any.whl |
Total release size: 241.8 kB
Release files / mainframe_migration_toolkit-0.5.0.tar.gz
| Download URL | mainframe_migration_toolkit-0.5.0.tar.gz |
|---|---|
| Size | 102.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3fd557112469488a20d34804a037f717cdc92228d45b4878993822bec881cacc
|
|
BLAKE2b-256 checksum How to use checksums |
048042790b6de5b7d7a7351ebf3e98b49bf50cd47e7d1859e79b0ea054a6b161
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / mainframe_migration_toolkit-0.5.0-py3-none-any.whl
| Download URL | mainframe_migration_toolkit-0.5.0-py3-none-any.whl |
|---|---|
| Size | 139.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6bc750c126d54561a87d3473c25c8e782e361df885bcbea7825756011dcad5c5
|
|
BLAKE2b-256 checksum How to use checksums |
ac8abc95c0353262a280776408b174f6a979874ec24267c8b734dc589de94f8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for mainframe-migration-toolkit 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.