1 / 7

Future of Classic Software

Understand the risks of relying on aging classic software, like hardware age and OpenVMS end of support. Learn how to mitigate risks through redesigning functionality, exploring hardware alternatives, and considering new OpenVMS versions. Explore options like Munis, EFP, and human resource surveys to determine your path forward amidst limitations and challenges in the software landscape.

dglass
Download Presentation

Future of Classic Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Future of Classic Software

  2. Classic Software Risks • Hardware Age • OpenVMS End of Support • SSDT Limitations • Redesign Functionality

  3. Hardware Age • Classic Servers in some cases 15 to 30 years old • Replacement parts are rarely new • Replacement parts will become increasing difficult to source

  4. OpenVMS End of Support • December 31, 2020 – Not Fiscal Year End • HP Decision – November 2016 • This date is not changing

  5. SSDT Limitations • Limitations on simultaneous migrations • Limitations on software development

  6. Risk Mitigation • Alternatives hardware • “New” version of OpenVMS • State Software Use/License Fee • Determine Your Path • Redesign, Munis, EFP

  7. Human Resource Survey

More Related