Add PRD for COBOL to Java 18 migration

[Copilot]

Created Product Requirements Document for migrating AS/400 COBOL inventory management system to Java 18, following the structure defined in program-prd.prompt.md.

Scope

Analyzed 8 COBOL programs in AS400/QCBLLESRC:

• STAOBR family (STAOBR, STAOBR2, STAOBR_2) - Material inventory updates with sequential/indexed file processing
• STAPOR - Ordering logic
• TABULKY1/2 - Array/table operations
• COND1 - Conditional logic patterns
• DUMP_FULL - Debug utilities

PRD Structure (AS400/QCBLLESRC/prd_spec.md)

• Problem Statement: Legacy platform dependencies, limited integration, scalability constraints
• Requirements: 6 functional categories (FR1-FR6), 7 non-functional (NFR1-NFR7) covering JPA migration, REST APIs, cloud deployment
• User Stories: 6 personas from batch operators to integration developers
• Timeline: 24-week phased approach across architecture, migration, testing, deployment
• Risks: 8 identified with mitigation strategies (performance, data integrity, knowledge transfer)

Key Technical Translations

• File-based storage (STAVY, OBRATY) → JPA/Hibernate with relational DB
• Sequential/indexed access patterns → Repository pattern with batch optimization
• MOVE CORRESPONDING → Java object mapping frameworks
• 88-level conditions → Enum-based validation

Document provides foundation for functional equivalence while enabling cloud-native deployment and modern integrations.

Original prompt

implement this.

[Chronological Review: The conversation began with the user requesting to follow instructions in a specific prompt file. The user then asked to proceed with the task, followed by a request to rewrite the Product Requirements Document (PRD) for a migration from COBOL to Java 18. Finally, the user requested implementation of this rewrite.]

[Intent Mapping:

1. "Follow instructions in [program-prd.prompt.md]": The user wanted to initiate a task based on the contents of the specified prompt file.
2. "please proceed": The user was indicating readiness to move forward with the task.
3. "please rewrite the PRD for a rewrite to Java 18": The user requested a specific rewrite of the PRD to facilitate migration from COBOL to Java 18.
4. "implement this": The user asked for the implementation of the rewritten PRD.]

[Technical Inventory:

• Repository: Cobol-Demo
• Current Branch: master
• Default Branch: master
• Technologies: COBOL, Java 18
• Purpose: Migration of an application from COBOL to Java 18 based on analysis and reports.]

[Code Archaeology: No specific code files or functions were discussed in detail, but the focus was on the PRD document related to the migration process.]

[Progress Assessment:

• Completed Tasks: User has provided context and specific requests for the PRD rewrite.
• Partially Complete Work: The actual rewriting and implementation of the PRD for Java 18 migration is pending.]

[Context Validation: All necessary context for continuing the work on the PRD rewrite and migration to Java 18 is captured.]

[Recent Commands Analysis:

• Last Agent Commands: The user requested to rewrite the PRD and implement it.
• Tool Results Summary: No specific tool results were generated as the conversation focused on user requests rather than tool executions.
• Pre-Summary State: The agent was actively working on the user's request to rewrite the PRD for migration to Java 18 when the token budget was exceeded.
• Operation Context: The commands were executed to align with the user's goal of migrating the application from COBOL to Java 18, utilizing the analysis and reports collected.]

1. Conversation Overview: - Primary Objectives: - "Follow instructions in [program-prd.prompt.md]" - "please rewrite the PRD for a rewrite to Java 18." - "implement this." - Session Context: The conversation involved the user directing the agent to follow a prompt, then requesting a rewrite of the PRD to facilitate migration from COBOL to Java 18, culminating in a request for implementation. - User Intent Evolution: The user moved from initiating a task based on a prompt to specifying the need for a PRD rewrite and implementation for a migration project.

2. Technical Foundation:

• Repository: Cobol-Demo
• Current Branch: master
• Default Branch: master
• Technologies: COBOL, Java 18

3. Codebase Status:

• File Name: program-prd.prompt.md
• Purpose: To provide instructions for the PRD rewrite.
• Current State: User has requested to follow the instructions within this file.
• Key Code Segments: Not applicable as no specific code segments were discussed.
• Dependencies: The PRD rewrite is dependent on the analysis and reports collected for the migration.

4. Problem Resolution:

• Issues Encountered: None explicitly mentioned.
• Solutions Implemented: User's requests for rewriting and implementing the PRD.
• Debugging Context: No ongoing troubleshooting efforts were noted.
• Lessons Learned: The importance of clear directives for project migration.

5. Progress Tracking:

• Completed Tasks: User has articulated the need for a PRD rewrite.
• Partially Complete Work: The actual rewriting and implementation of the PRD is pending.
• Validated Outcomes: No features or code have been confirmed working as the focus was on documentation.

6. Active Work State:

• Current Focus: Rewriting the PRD for migration to Java 18.
• Recent Context: User has been providing directives for the PRD rewrite and implementation.
• Working Code: Not applicable as the focus is on documentation.
• Immediate Context: The user was addressing the need for a PRD rewrite for Java 18 migration.

7. Recent Operations:

• Last Agent Commands: User requested to rewrite the PRD and implement it.
• Tool Results Summary: No specific tool results were generated.
• Pre-Summary State: The agent was actively working on the PRD rewrite when the token budget was exceeded.
• Operation Context: The commands were executed to align with the user's goal of migrating the application from COBOL to Java 18.

8. Continuation Plan:

• Pending Task 1: Rewrite the PRD for migration to Java 18 based on collected analysis.
• Pending Task 2: Implement the rewritten PRD.
• Priority Information: The PRD rewrite is the most urgent task.
• Next Action: Immediate next step is to begin the PRD rewrite as per user instructions.

Created from VS Code.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.