Document Controls

  • View a Print Friendly version of this document

    Print
  • Toggle highlighting of search terms in this document

  • Text Size: 

    • A (normal)
    • A (larger)
    • A (largest)

For Application Development & Delivery Professionals

Primary Analyst Photo Document Information Rate this Document

October 28, 2009

Modernization Decisions: Should Client Leave Adabas When It Leaves The Mainframe Platform?

by Phil Murphy

with Mike Gilpin, David D'Silva

Average:
(2 ratings)

This is an excerpt

Executive Summary

Applications professionals at a government agency had been operating a suite of custom Adabas applications for decades. The agency was facing mounting economic pressures, it was seeking avenues for cost reduction, and the large bill for the agency's shared-services computing environment was a tempting target. To this end, the agency decided to migrate these applications off the mainframe to a different platform where it expected to achieve lower costs. But it faced another decision as well: Should it also migrate from Adabas to a new database management system (DBMS)?

Keywords

TABLE OF CONTENTS

  • Should A Platform Migration Also Include Adabas Replacement?
  • Moving
  • Beyond Scoring: Factor The Vendor Relationship Into Your Migration Decision
  • The Net Result For The Agency Was A Counterintuitive Decision

RECOMMENDATIONS

  • Consider Conventional Wisdom, But Base Decisions On Your Context
  • Related Research Documents

This is an excerpt

Buy Risk-Free

Price: US $2495

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.

Add to cart

Save and Share

Document Tools

Spread the word: