Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

det: batch file I/O holes in estates without an application JCL job (no CobolFiles), and WRITE ... ADVANCING

Cerrado
  • ¿Algo no está bien?
#6,065 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #6111 de @squid-protocol — fusionado

Evaluación

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

Línea de trabajo

Start with cobol_to_java_batch_forge.py and det/program.py to trace when batch runtime files and unscheduled main programs are generated, then inspect det/stmt.py around _write() for the trailing phrase handling. Use unit and synthetic COBOL programs to check WRITE ... ADVANCING against the IBM reference, and verify the named holes distinguish unsupported phrases. Done means the specified batch regression checks pass and the translation only survey reports before and after counts.

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

Descripción

bug claim:melek priority: high scope:core

Why

The 2026-10-22 non-burned translation-only survey (#6064 comment) has two gaps that cover about two-thirds of the hole statements in the local non-burned corpora (dsf, zopeneditor-sample: 124 hole statements over 10 programs):

hole reason statements
<OPEN/READ/WRITE/CLOSE> <file>: the generated project has no batch package (CobolFiles) to run files through ~50
WRITE ADVANCING / other phrases 33

Both are generic batch COBOL, not estate quirks, so they are likely to recur on any unseen batch estate.

1. No batch package unless the estate has an application JCL job

cobol_to_java_batch_forge.py BatchForge.sources() returns {} when self.applications is empty, so the batch runtime (CobolFiles, Sysout, CobolAbend, …) is generated only when the estate holds at least one application JCL job. det/program.py:has_batch() then finds no batch/CobolFiles.java, and every FD gets fd.why = "the generated project has no batch package…" (program.py ~L1029). Every file I/O statement becomes a hole.

dsf has no JCL at all. The unscheduled main-program path (the CardDemo CBTRN01C case: a main program with files, no USING, no COMMAREA) only counts when self.applications is already non-empty (bool(self.applications) and key in self.unscheduled, ~L343/L348).

Fix: emit the batch runtime when the estate has any batch program: an application job or an unscheduled main program with files. Treat a no-JCL estate's file-owning main programs as unscheduled batch steps, as CardDemo's CBTRN01C already is. A CICS-only estate (no FDs in a main program) must still get no batch package, as today.

2. WRITE … ADVANCING

det/stmt.py _write() (~L1000) holes anything after WRITE rec [FROM x]: "WRITE ADVANCING / other phrases". Model BEFORE/AFTER ADVANCING n LINE(S) | mnemonic | PAGE (IBM Enterprise COBOL Language Reference, WRITE statement, sequential files) for line-sequential and printer files: carriage control as IBM defines it for the record (ASA control byte when the file is ADV; the line/page skip otherwise). Refuse by name any phrase still not modelled (AT END-OF-PAGE/EOP with LINAGE, mnemonic names not in SPECIAL-NAMES), as a named hole, never a guess.

Sweep the class in the same PR: _write currently holes every trailing phrase, so check which others the surveys hit (INVALID KEY / NOT INVALID KEY on indexed/relative WRITE, END-WRITE) and model or name them separately, so the hole reason says which phrase.

Evidence constraints

  • No burned estate uses ADVANCING (grep over the 6 burned corpora: 0 files). Part 2 therefore can't reach L2+ on a burned estate: test it with unit and synthetic programs (language-crucible) against the IBM reference, and report it as translation-only until a burned program uses it. Don't build cases on dsf/zopeneditor/census repos (burned-only rule).
  • Part 1 regression: CardDemo/CBSA/GenApp batch must be unchanged (byte-identical generated estate where they have application jobs); the async credit-card estate (CICS-only, 0 JCL) must still get no batch package.
  • Afterwards: re-run the non-burned translation-only survey (det_survey.py --no-compile over dsf, zopeneditor-sample) and post the before/after counts here. Baseline: dsf 0 / 7 whole, 231 / 318 statements; zopeneditor-sample 2 / 5 whole, 595 / 632.
Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 20 min
PR fusionados (30 d)
985

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.