Epic: whole-migration harness: data, job streams, interfaces, performance, security, cutover
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- backend
Research direction
Start by reading this epic and the related issues #3803, #4493, #4508, and #4050 to understand the existing scan and coverage work. The issue asks for each migration area to be filed as its own issue when work starts; there is no specific file or test to begin with. Done means the separate work is scoped and its evidence can report into the #4493 coverage page.
Written by the indexing model from the issue text.
Description
Why. Program-logic equivalence is only part of a migration. Each part below fits the same scan, generate or capture, compare, evidence, ratchet pattern, and should report into the #4493 coverage page.
Parts (suggested order):
- Data migration (VSAM, EBCDIC): convert each dataset, then round-trip it and compare byte for byte. Also reconcile counts, check key integrity, check EBCDIC/packed-decimal conversion field by field, and generate edge records (high-values, low-values, bad signs). Reuses the scan's layouts.
- JCL job streams: #4508.
- Interface contracts: inventory every file, queue (MQ), CICS link, DB2 table and transfer at the estate boundary, then record or generate traffic at each boundary and compare old versus new.
- The answer key on z/OS: #4050.
- Performance budgets: the same workloads old versus new (throughput, latency, the batch window), measured against a z/OS baseline (SMF). Budgets and regression gates, not byte equality.
- Security (RACF): extract transaction/dataset access per program, map RACF profiles to the new model, and test the same allow/deny decisions.
- Cutover by parallel run: shadow-mode production traffic through both systems with live comparison. The go/no-go stays human, fed by the evidence.
File each part as its own issue when it starts. Related: #3803, #4493.
- Dominant language
- Python
- Stars
- 57
- Forks
- 11
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 975
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from squid-protocol/gitgalaxy
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
squid-protocol/gitgalaxy#7827 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:frontier
Difficulty 5/5 Over a week Newbie friendliness 18/100
squid-protocol/gitgalaxy#7900 ·
Maintainers usually reply within 1 day
-
core-engine scope:infra testing
Difficulty 4/5 3-5 days Newbie friendliness 54/100
squid-protocol/gitgalaxy#7863 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
squid-protocol/gitgalaxy#7834 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
squid-protocol/gitgalaxy#7828 · 1 comment ·
Maintainers usually reply within 1 day
All issues in squid-protocol/gitgalaxy
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
graphql-python/graphql-core#304 ·
Maintainers usually reply within 1 day
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Gathin23/cleanyourtv#3464 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day