Modernize COBOL with AI agents without breaking the business.
AI agents can read and rewrite COBOL faster than any team could before. The migrations that fail do not fail on the rewrite. They fail on what a changed field quietly breaks three programs away. gitta reads your COBOL, copybooks and JCL structurally, names every program that still depends on a change, and stops the merge before it reaches your build.
1205 CA-REQUEST-SPECIFIC PIC X(32482).
1305 CA-POSTCODE PIC X(8).
1305 CA-POSTCODE PIC X(10).
gittaSix programs read CA-POSTCODE. LGTESTC1 and LGUCDB01 still move it into an eight character field and would cut the new postcode short. Merge stopped before the build.
A COBOL migration breaks where no one is looking.
A plain text merge sees lines. The risk lives between programs, in the layouts they share and the fields they pass, and it reads as correct right up to the day it does not.
Shared copybooks
One record layout is copied into dozens of programs. Widen a field in the copybook and every program that moves it somewhere smaller is now wrong, silently.
Programs calling programs
A change to what one program sends reaches every program that reads the other end. A diff shows neither side the whole picture.
Tests that never ran
Much mainframe code has no automated test. An agent can pass the tests that exist and still break a path nothing covers.
See the blast radius of one field.
Change CA-POSTCODE, and gitta names every program whose code still reads it, through a move, a redefine or a direct reference, and shows which ones no longer fit.
- LGTESTC1moves it into an eight character fieldwould truncate
- LGUCDB01moves it into an eight character fieldwould truncate
- LGACUS01reads the fieldfits
- LGACDB01reads the fieldfits
- LGIPDB01redefines the recordfits
- LGUPVS01passes it to another programfits
- LGSTSQdoes not touch the fielduntouched
gitta reads the mainframe the way it is written.
Not a translation layer and not another agent. gitta reads the structure each program uses, under whichever agent your team already chose.
- COBOL and copybooks
- The layouts many programs share, down to every field, level and status value, so a change to one is traced to all of them.
- JCL and night jobs
- Each job step and the program it runs, so a change that moves a step or a program is checked like any other.
- Where-used across the base
- Every program that reads a changed field or record, named on the change, before the merge, not after a batch window fails.
- Under any agent
- watsonx Code Assistant for Z, Claude Code or Cursor. gitta reads the change the same way whoever wrote it.
Runs on z/OS, in your own shop.
gitta is a native IBM Z program and runs on z/OS itself, so your DBB pipeline checks every agent change on the mainframe before the build starts, with no container in the way. Your programs, data sets and build process stay exactly as they are, and your source never leaves your company. Prefer a container? gitta also runs in zCX, loaded into z/OS, so the check runs inside z/OS before the IBM DBB build step.
Read about gitta on IBM ZGive your COBOL agents a safety net.
Tell us about your base and the agents your team runs, and we will show you gitta on your own code. For SAP shops, gitta reads ABAP the same way, and the mainframe overview has the full picture.
