- Case-studies
- COBOL -> Java migration
case-studies
Case-studies
Idemitsu Kosan, Nissan, Japan Airlines, SoftBank, Kyocera, TOTO, Murata Manufacturing, Japan Petroleum Exploration(JAPEX), Unitika, Nitori, Toppan, Ricoh, Nitto Denko, Token, DAIDO LIFE INSURANCE, Mizuho Research & Technologies, Okasan Information Systems, Kanden Systems, JAL Information Technology(JIT), ITEC HANKYU HANSHIN, Nishitetsu Information System, KIRIN BUSINESS SYSTEM, JFE Systems, KOBELCO SYSTEMS, Toray Systems Center, Bridgestone Software, Tec Information Systems, NEC Group, NTT Group, T.D.I, PERSOL P&T, Unisystem, etc.
Customer Testimonial (presentations)
AI-based COBOL→Java migration becomes a mainstream
Automatic conversion
UI Migration
- Migration to GUI
-
- Improved operability for using mouse and buttons.
- Customize UI to the client’s standards.
- A little slower response speed than the current system due to web system.
- Migration to CUI
-
- No need for training users because of unchanged UI/UX.
- Quicker response speed than GUI screen.
System Reform Schedule
Migration Cases
Six systems of two IBM mainframes such as production, sales, and after-sales service in a certain manufacturing industry
- Development process
- Inventory, migration design, source code migration – system test, user acceptance test support, go-live
- System reform information
- COBOL → Java
COBOL → MF COBOL
NATURAL → Java
PL/I → MF PL/I
JCL → Java+XML file
ASM → MF COBOL
ADABAS → SQL Server
OS/390 V2 → Windows Server 2012 - Current system scale
- COBOL：2,487KL, JCL：545KL, NATURAL：429KL, PL/I：2,156KL, ASM：35KL, Form：781, Screen：1,572
- Development period
- 20 months(* Migration of each system was carried out in about one year.)
Manufacturing System
- Development process
- Inventory, migration design, specification documentation, UI design – migration test, system test & user acceptance test support
- System reform information
- COBOL → Java
PL/I → Java
JCL → Shell
VSAM → Oracle
host → Linux - Current system scale
- COBOL：141.5KL, PL/I：37.2KL, JCL：44.8KL
- Development period
- 13 months
New Core Accounting System *Migrate to cloud
- Development process
- Inventory, migration design, source code migration – migration test, functional modification, system test, user acceptance test support, go-live
- System reform information
- MED, PSAM → HTML5.0
COBOL → Java11
ASM, Utility → Java11
JCL, Macro, CLIST → Java11 & XML file
File(PS, DAM, PO) → Linux standard file
VSAM file → SQL Server 2019
XSP → Red Hat Enterprise Linux 8.4(AWS) - Current system scale
- MED, MAP：11.9KL, COBOL：1,934.2KL, JCL：751.3KL, ASM：3.8KL, CLIST：1.7KL, COPY：41.7KL, Utility：50, Macro：4KL
- Development period
- 30 months
Computer Aggregate Processing System
- Development process
- Inventory, migration design, source code migration – migration test, system test & user acceptance test support, go-live support
- System reform information
- IDLⅡ, COBOL, COBOLS, HPL → Java
JCL → Java & XML file
ADBS/RIQS → SQL Server 2016
ACOS4 → Windows Server 2016 - Current system scale
- IDLⅡ：775.9KL, COBOL：386.8KL, COBOLS：49KL, HPL：9.8KL, JCL：327.3KL
- Development period
- 36 months
Next Generation Core System
- Development process
- Inventory, migration design, source code migration – migration test, system test & user acceptance test support
- System reform information
- YPS COBOL → Java
ASM → Java
NDB & RDB & VSAM → Oracle 12c
Fujitsu host → RHEL6 - Current system scale
- COBOL：520KL, ASM：0.9KL, JCL：178.5KL
- Development period
- 11 months
Cost Management System
- Development process
- Inventory, migration design, specification documentation, source code migration – migration test, system test & user acceptance test support
- System reform information
- COBOL, COBOLS, COBOLX, IDLⅡ, RPG, Macro → Java
JCL → KShell
ADBS → Oracle
VSAS/RIQS → Oracle
ACOS4 → Linux - Current system scale
- COBOL：104.3KL, COBOLS：124.5KL, COBOLX：7.7KL、DATASSF：5.0KL, IDLⅡ：391.1KL, RPG：1.4KL, JCL：431.5KL, Macro：10KL
- Development period
- 20 months (* POC included)