Why modernize your RPG and COBOL code now?

• Lower operational risk: reduce dependencies on opaque modules and tacit knowledge.
• Agility: more frequent deployments, automated testing and better traceability.
• Security: detection of vulnerabilities and embedded secrets.
• Talent attraction: facilitate the entry of profiles that do not know RPG/COBOL in depth.

What does IBM's Project Bob contribute to this process?

Project Bob is an environment with AI assistance aimed at teams working with RPG on IBM i i COBOL on System z. The goal is accelerate modernization and improve code quality with:

• Analysis and recommendations within the IDE: refactor suggestions, readability improvements, and security checks.
• Contextual assistance: proposals for changes with explanations, so as not to "play blindly".
• Bridge to modern architectures: support for modularization, exposure APIs, encapsulate data access and prepare dev/test automated.

Recommended roadmap (step by step)

1. X-ray of the code
   Inventory programs, dependencies (RPG, CL, embedded SQL), critical points and security risks.
2. Modernization objectives
   Define whether you are looking for stability, technical debt reduction, API exposure or progressive migration to services.
3. Fast and safe refactors
   • Fragment programs that are too large.
   • Separate business logic from data access.
   • Enter flower pots basic for regressions.
4. Automate quality
   Integrate code review, static analysis, and security checks into the pipeline.
5. Expose data and functionalities
   Publish APIs where it makes sense, to pave the way for modern frontends and integrations.
6. Iterate with metrics
   Measure deployment time, error rate and test coverage to justify investment and adjust the plan.

Specific best practices for RPG on IBM i

• ILE and modularity: takes advantage of modules and services to reduce interdependencies.
• Modern SQL: replace old data access with SQL optimized and parameterized.
• Error management clear**:** encodes consistent and traceable responses.

Best practices for COBOL on System z

• Size limit and responsibilities: avoids “monolithic” programs that are difficult to test.
• Well-encapsulated data: documents schemes and contracts to facilitate evolution.
• Automate testing: even minimal tests act as a safety net for each change.

Frequently Asked Questions (FAQ)

Do I need to rewrite everything?
Not necessarily. It's often better modernize in layers: encapsulate data, expose APIs and refactor critical points.

What ROI can I expect?
It depends on the size and status of the code. The first iterations (security, tests, APIs) already provide tangible value in weeks.

Does Project Bob replace other tools?
It is a AI assistance compendium for RPG/COBOL; can coexist with pipelines and QA/security tools you already have.

L'entrada Modernització d’RPG i COBOL: guia pràctica per transformar el “codi vell” amb Project Bob d’IBM ha aparegut primer a Andorsoft, S.A..