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

Cerrado
  • ¿Algo no está bien?
#7,011 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 21 min
PR fusionados (30 d)
965

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.