IT modernization is the process of extending the value of aging platforms and systems into the future by adopting modern, efficient technologies.
Editor's note: This article introduces the white paper "The Essential Guide to IBM i Database Modernization," available free from the MC White Paper Center.
Those within the IBM i community love the platform for its reliability, scalability, and ability to deliver tremendous business value with unusually low operational costs. So why is the system perceived as being "legacy"? Many point to the green-screen user interface or a lack of effort to publicize the value proposition of the IBM i. Nonetheless, based on extensive research by IBM and others, we strongly believe that the lack of application agility is the primary factor limiting the growth and acceptance of this remarkable platform. In fact, the biggest constraint of application agility is neither the user interface nor the RPG-written applications; it's the fact that we're not using the SQL capabilities in the DB2 for i database.
This whitepaper will explain:
- Why companies should consider modernizing their application's database
- The database modernization challenges companies have faced in the past
- The benefits of migrating legacy or heritage database objects
- The new technology advancements that can be leveraged after database modernization has taken place
First and foremost, it's important to ask the following:
- What is the cumulative value of the intellectual capital invested in your applications?
- What competitive advantage do your current application systems provide?
Without a doubt, there's significant value in your "legacy" or "heritage" applications, and this value can be leveraged relatively easily for dramatic results and benefit to your company. It's entirely feasible (rather simple, actually) to extend the life of these applications while remaining competitive. Our goal is to build a case for database modernization that supports your business goals by defining the value in your heritage application system.
Modernize Your IBM i
IT modernization is the process of extending the value of aging platforms and systems into the future by adopting modern, efficient technologies. This can be accomplished whilst removing the operational constraints that inhibit growth and agile response to changes in the business environment. However, what should be thought of as an ongoing process of IT system improvement is perceived as a large and daunting project because incremental improvements to monolithic code often exhibit "gotchas" along the way. As a result, the importance of system improvement is often forgotten as IT personnel are consistently challenged to "do more with less."
Interestingly, modernization has continued to be a top priority for CIOs. The results of a survey conducted by Gartner of over 2,300 CIOs indicates "Legacy Modernization" as being one of the top 10 CIO business and technology priorities for 2012.
Why Is the IBM i Perceived as Legacy?
- User Interface/User Experience (UI/UX)—Younger CIOs and CFOs see the default interface of the IBM i and are often quick to pigeonhole the entire platform as legacy. In addition, younger programmers and users cannot relate to the 6 – 8 character field names and the 6 – 10 character file names of DB2 for i, which older programmers have historically employed to name database constructs and elements.
- Old-Style Monolithic Code—In previous years, developers created huge "structured" monolithic programs, as that was the programming model of the time. Often, 80% of the lines of code in these monoliths dealt with database relationships and database validations.
Additionally, there was little or no separation of function, which made maintenance problematic. This presented massive maintenance backlogs and frustrated users.
Some companies seldom (or maybe never) improved applications by introducing newer coding techniques; leveraging new enhancements to the language, operating system, and database; or improving the maintainability of the applications because the system just kept on running. Now, IBM shops strive to remain competitive but are facing challenges: skyrocketing costs constrain IT budgets; the intellectual property invested in heritage systems needs to be retained and leveraged; and major advances in analytics, cloud, mobile, and database engine technologies must be utilized. Fortunately, this problem is solved through database modernization.
Understanding Database Modernization
Companies must think strategically to correct the fundamental challenge brought on by lack of application agility, which is retained by old code and an inflexible database structure. Often, companies start by modernizing the UI because it's the most visible part of the application. The most important piece should be in modernizing the database and eliminating monolithic code so that discrete functions of core applications can be leveraged for a variety of benefits.
To create application agility, applications designed on old standards have to be fundamentally re-constructed in order to unlock their massive value, retain the competitive advantage facilitated by those applications, and recover the business rules in re-usable components.
All modernization has to start at the database engine layer, as most of the advances introduced to the platform since 2000 pre-supposes the use of an SQL database engine. In fact, in our experience, if the SQL engine is leveraged, your code base can be reduced by approximately 80% by simply moving database functions historically coded in RPG (or other HLLs) down into the database engine. It's possible to implement a solution with minimum disruption using a low-risk, gradual, iterative process to ensure no loss of business continuity and to support parallel databases during the process.
This automatic, gradual, and non-disruptive process doesn't require manual program recompilation during the initial phase of the migration. Subsequent refactoring or reengineering of the code at both a code and database level will require recompilation of the objects.
Want to Know More?
Download "The Essential Guide to IBM i Database Modernization," available free from the MC White Paper Center.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online