KKH Statutory Health Insurance Fund
Until recently, the copy process was conducted leveraging snapshots and solutions that had been developed in-house. However, this task increasingly required the team to drill more deeply into the Db2 system’s structures, especially after each Db2 version change. Successfully cloning Db2 objects required a two-step process: first, the team copied the data in “snapshots,” then made the data available again in the Db2 target system.
- Eliminated 40 man-hours of manual cloning per quarter
- Extended availability of consolidation system for test purposes by three days, minimizing the risk of failure
- Enhanced staff productivity resulted in better customer response times and a more competitive set of applications
- IBM Db2® for z/OS®
Want to learn more?
Our work involved in cloning the Db2 database has been reduced by more than half...The quicker we are in delivering better and faster applications, the more productive and competitive the whole of KKH is as a result.