Siblings of #6839: COBOL -> lowered-HLASM boundary (linked coverage, START target, code page)

Chiusa
  • Qualcosa non va?
#7,011 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, testing

Direzione di ricerca

Read det/hlasm.py, the test_hlasm_estate_census_5859 coverage, and the linked #6839/#5859 work first. The issue lists several possible follow-ups, including measuring linked coverage and parity on lowered HLASM, adding a COBOL START case for ZECSNC, and code-page conversion; determine which item is in scope before changing code. Done means the selected gap has a case or measurement that addresses it.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

scope:sweep testing

Siblings of #6839 (from PR #7009, row H: ZECS001 LINKs the lowered HLASM ZECS002).

Class: a burned CICS program's LINK / XCTL / START to a program the forge does not generate (HLASM, lowered by det/hlasm.py). test_hlasm_estate_census_5859 pins the burned assembler set. PR #7009 covers ZECS001 -> ZECS002 (LINK); main-program HLASM (zecs-zecs002, zecs-zecsnc) was already handled in #5859.

Duplicate search: open issues with HLASM in the title are #4510 / #4515 (frontier harness support), neither covers these.

  • Linked coverage + parity for a lowered HLASM target. The det coverage ledger records linked.ZECS002 as 0/0 paragraphs/branches under zecs-zecs001, and det_parity warns "ZECS002: methods 40 vs 21 expected from 0 in the COBOL", because both read the .asm as COBOL. Measure on the lowered program instead. No proof depends on it (ZECS002 is proved in its own case), so the warnings are noise today.
  • ZECSNC as a START target from a COBOL case. ZECSNC is started (RUN TRANSID / START), not LINKed. Only worth a case if a burned program starts it with observable data.
  • ZECS001 1610 line 854 false arm (the ZC01SD scan running to SD-INDEX 20): needs a ZC01SD template with 20+ entries.
  • Code-page conversion for a re-hosted HLASM program (frontier, mapped only): a production port receives Unicode headers and an EBCDIC-table ZECS002 would mis-decode them. A migration gap, not an equivalence one; recorded as residual risk in hlasm_cics_design.md assumption 3.

Siblings: #6839, #5859

Lingua principale
Python
Stelle
57
Fork
11
Merge medio
1h 21m
PR unite (30g)
971

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di squid-protocol/gitgalaxy

Tutte le issue di squid-protocol/gitgalaxy

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.