Apply mainframe dependency transformations to COBOL code using a pre-generated transformation guide. Converts CICS/VSAM constructs to standard COBOL.
Scanned 6/5/2026
Install via CLI
openskills install OpenHands/extensions---
name: mainframe-removal
description: Apply mainframe dependency transformations to COBOL code using a pre-generated transformation guide. Converts CICS/VSAM constructs to standard COBOL.
license: MIT
compatibility: Requires GnuCOBOL (cobc) for verification
triggers:
- remove mainframe
- cobol transformation
- cics removal
- standard cobol
---
Apply the transformations from a transformation guide to convert mainframe-specific COBOL to standard COBOL.
**Prerequisite**: A transformation guide must exist (see `cobol-mainframe-planning` skill).
## Transformation Requirements
### Data Operations
- Replace each CICS/VSAM construct with its standard COBOL equivalent per the plan
- Add FILE STATUS checks after EVERY file operation:
- Check for success (00) before proceeding
- Handle "not found" (23) distinctly from I/O errors (3x)
- Handle "file not exists" (35) at OPEN time
- Add explicit CLOSE statements in all code paths (including error paths)
### UI/Terminal Operations (BMS maps, SEND/RECEIVE)
- Replace with simple stubs or ACCEPT/DISPLAY statements
- Do NOT spend time replicating screen layouts
- Focus on preserving data flow, not UI fidelity
### Error Handling
- Replace CICS RESP/RESP2 checks with equivalent FILE STATUS logic
- Replace HANDLE CONDITION with explicit status checking after operations
- Ensure error paths don't leave files open
See [references/cics-transformation-examples.md](references/cics-transformation-examples.md) for before/after code examples.
## Verification
After transformation:
- Code MUST compile without errors
- Test with valid input → should execute core business logic
- Test with missing/invalid files → should fail gracefully, not crash
## Preserve
- All original business logic
- Data transformations and calculations
- Validation rules
## Checklist
- [ ] All EXEC CICS commands replaced
- [ ] FILE STATUS declared for all files
- [ ] FILE STATUS checked after every I/O operation
- [ ] CLOSE statements in all code paths
- [ ] Code compiles successfully
- [ ] Basic test execution passes
No comments yet. Be the first to comment!
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
克劳德代码会话的正式评估框架,实施评估驱动开发(EDD)原则
Go测试模式包括表格驱动测试、子测试、基准测试、模糊测试和测试覆盖率。遵循TDD方法论,采用地道的Go实践。
使用pytest、TDD方法、夹具、模拟、参数化和覆盖率要求的Python测试策略。
在编写新功能、修复错误或重构代码时使用此技能。强制执行测试驱动开发,包含单元测试、集成测试和端到端测试,覆盖率超过80%。