- Migration Pattern
- RPG to Java
migration-pattern
Migration Pattern
RPG to Java Background
Limits of RPG
・Low development efficiency and long development duration.
・Few software and hardware (printer, etc.) available.
・Not web system. It’s hard to use with multi-devices.
・Unable to take advantage of the benefits of cloud services.
・The character code is EBCDIC, so it is not suitable for data analysis.
…
Hopeless Sustainability
・Fewer specialized technicians.
・Hard to improve in-house IT technology and individual’s IT skills.
Migrate from RPG to Java before it’s too late.
RPG to Java Kinds of Conversion Methods
- Straight conversion: Convert RPG commands one by one with Java grammar or functions.
※Migration method that has been used for a long time. - LLM (Generative AI model) : Convert with LLM, modify and Test manually
- AI-powered migration with tool: Understand the programming language and convert it to the
correct pure Java according to its meaning with
AI conversion tool.
Problem with Straight Conversion -Conversion
If directly convert RPG commands, the conversion effect won’t be good in some respects.
Examples of performance problems:
RPG programs directly access DB. Java programs access DB through I/F. So performance problems will happen when a lot of users access DB.
Problem in testing -Vendor test/User test
Most Vendors lack analyzing capability, business knowledge.
The test becomes a difficult job and responsibility of customer.
LLM (Popular general-purpose generative AI model) and issues
LLM Application
Use generative AI tools like ChatGPT to convert RPG to pure Java systems, C/S systems to WEB, etc.
LLM Limitation
1. It requires learning. No direct injection of knowledge.
・Extremely large amount of high-quality training data v.s. insufficient amount of RPG and
Java available for free.
・LLM evaluation requires extremely fast processing v.s. CPUs are too slow to meet the demand.
Difficult to evaluate by RPG/Java comparison tests.
2. Additional learning for each round of bug fixes changes conversion rules.
System test must be done all over again.
Low quality conversion that requires huge manual workload of debugging, adjustment and retesting.
System Reform Conversion: Language Conversion Using Knowledge-injected AI
QA of System Reform
Complete verification of all technical elements
Test with actual business data
Source Code Converted with System Reform Technology (Examples)
GUI/CUI migration (WEB)
Achieve High Value-Added with System Reform Technology (Cases)
Customer Testimonial (Presentations)
System Reform Schedule
Migration Cases
Business System
- Development process
- Inventory, migration design, UI design – migration test, system test & user acceptance test support
- System reform information
- RPG & RPGLE to VB.NET2013
RPG & RPGLE to PL/SQL
PRTF to PDF
DB2 for i to Oracle11g
OS400 to WindowsServer2012 - Current system scale
- RPG:1,500KL, Form:221
- Development period
- 15 months
Production & Sales Management System
- Development process
- Inventory, migration design, specification documentation, source code migration – migration test, system test & user acceptance test support
- System reform information
- RPG to Java(online)
RPG to T-SQL(batch)
CL to PowerShell
DB2 to SQL Server
AS/400 to WindowsServer2008 - Current system scale
- RPG:155KL, CL:15.1KL
- Development period
- 9 months
Sales Management System
- Development process
- Inventory, migration design, specification documentation, source code migration – system test, user acceptance test support, go-live
- System reform information
- RPG & CLP to Java
CL to Java & PowerShell
DB2 to Oracle11g
OS/400(V5R3M0) to WindowsServer2008 - Current system scale
- RPG:110KL
- Development period
- 8 months
Sales System
- Development process
- Inventory, migration design, specification documentation, source code migration – migration test, system test & user acceptance test support
- System reform information
- RPG & CL to Java
DB2 to SQL Server 2008
OS/400(V5R3M0) to WindowsServer2008 - Current system scale
- RPG:69.2KL, CL:14.7KL
- Development period
- 7 months
Production Management System
- Development process
- Inventory & slimming, migration design, UI design – system test, user acceptance test support
- System reform information
- RPG, RPGLE to Java
CL to Java/Shell
DB2/400 to PostgreSQL v10.0
IBM V7R2 to Linux7.2 - Current system scale
- RPG:46.4KL
- Development period
- 10 months