Wednesday, March 14, 2012

Moving BI off the Mainframe

When IT professionals use the acronym "MF" in the near future, they may no longer be referring to "Mainframe" as they have for decades. Instead, that term may soon stand for "Micro Focus."

So how could a UK-based software vendor replace the Big Blue Mainframe?

Well, I am seeing it first-hand with a client that is swapping their IBM MVS/TSO platform for Red HatEnterprise Linux. All applications and data move off the mainframe and are exchanged for Micro Focus substitutes.

The magic sauce to mainframe modernization comes in the form of the Micro Focus Enterprise Server, which basically provides a mainframe replica on a cheaper box. One major benefit is that mainframe Job Control Language (JCL) batch processes can be ported as-is to a mid-range computer. Differences between the mainframe and the new platform are hidden under the covers.

For example, the mainframe dataset names (including PDS libraries, GDGs, etc.) are kept in the legacy JCL code. Even though the job now runs on completely different technology, it continues to use mainframe terminology. This is possible because Micro Focus handles an underlying cross-referencing via a system catalog connecting mainframe names with their real physical file correspondents.

Within Enterprise Server, Micro Focus provides a full application development and deployment environment for COBOL and PL/1 technologies. Also, common IBM utilities used within JCL code have Micro Focus replicas.

Micro Focus stresses the importance of modernization while minimizing risk. Their technology enables companies to leverage existing (and often substantial) investments in applications while running them in newer, less expensive environments. The vendor makes the following points about using their mainframe re-hosting technologies:
  1. Moving application development off the mainframe to a cheaper platform (e.g., Windows, Unix, or Linux) can provide additional CPU capacity for each developer, eliminate resource contention, and improve delivery times
  2. Moving testing off the mainframe can overcome capacity barriers and help developers meet schedules on time and on budget
  3. Moving workload off the mainframe can provide rapid cost savings in mainframe MIPS and software costs


On their website, Micro Focus tells how several customers have saved large amounts of money moving off the mainframe. For example, Tulane University in New Orleans, LA, saved a quarter million dollars each year, achieved three- to four-fold improvements in their batch processing times, and achieved ROI within one year by moving to Micro Focus.

Munich-based Stahlgruber GmbH migrated from the mainframe to Linux, saving 70% of the costs and achieving ROI in less than two years. In addition, Stahlgruber saw a dramatic improvement in computing performance. One program that took forty-five minutes to run on their mainframe zipped along on a four-processor Linux box finishing in only four minutes.

Other Micro Focus success stories include Tesco, the leading UK food retailer; the City of Inglewood government in the US State of California; and the Kansas City Southern Lines railroad (which cut annual mainframe maintenance costs by 90%).  

At my particular client, our team is responsible for moving legacy FOCUS 4GL applications to a WebFOCUS Linux environment. Our first objective is to port existing batch jobs off of the expensive platform to achieve cost reductions. Once that has been done, the client will then take advantage of new BI features available in the WebFOCUS product.

To reduce time, cost, and risk of porting FOCUS to WebFOCUS, we also leverage Partner Intelligence's BI Modernization Workbench to simplify the up-front analysis work and to automate any manual code conversion work.

No comments:

About Me

My Photo
Helping companies make better decisions via Business Intelligence. INTP working on the E&J. Traveler, reader, family guy, coffee drinker.