u/Striking_Smell6986

Serious question for people who actively work with COBOL.

If you had a magic button that could instantly solve ONE problem when maintaining or modifying a large COBOL application, what would it be?

Examples:

• Finding where business logic lives
• Understanding dependencies
• Impact analysis
• Tracing data flow
• Outdated documentation
• Knowledge trapped with a few senior developers
• Something else entirely

I'm curious whether the biggest challenges today are technical problems, documentation problems, or simply understanding systems that have evolved over decades.

Would love to hear what your "magic button" would solve.

I'm not a COBOL developer by profession, but I've been spending a lot of time trying to understand how large COBOL applications are maintained in the real world.

One thing I'm curious about:

Imagine someone drops a change request on your desk for a COBOL application you've never worked on before.

What does your process actually look like?

Do you start with:

• JCL?
• Program search?
• Copybooks?
• Existing documentation?
• Dependency analysis?
• Talking to someone who knows the system?

And what usually ends up consuming the most time?

I'm asking because from the outside it seems like the coding part might be easier than figuring out where the change needs to be made and what else it could affect.

Would love to hear real stories from people who work on these systems.