• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • To 2032 . . . And Beyond!

    December 7, 2020 Timothy Prickett Morgan

    As you sit here in 2020, can you even imagine 2032? Can you imagine beyond that? Oddly enough, I can imagine three or four decades out from here a lot more easily than I can do a dozen years, even though I know the error bars get longer and the probabilistic clouds get fuzzier the further into the future you wander with your mind. So what does it mean, really, when Big Blue commits to support the IBM i platform at least until 2032, a mere dozen years away in a platform that, depending on how you want to cut it, dates back to 1969 with the System/3 or 1978 with the System/38?

    In some ways, the support for the software is much more important than revolutions on the hardware crank every three or four years, which we detailed two weeks ago. But that cranking of Power hardware – from Power4 way back in 2001 when IBM converged its AS/400 and RS/6000 Power chip development and literally got its act together, to the expected delivery of Power10 in late 2021 in high-end machines and early 2022 in low-end machines and the Power11 chip in maybe 2025 and support for that chip at least for four years if not longer – give customers and partners the confidence that IBM is investing in the hardware and that implies that it will be investing in the software stack in a real and substantial way, not just fixing bugs and rolling in some new database features or open source packages in PASE or in Linux.

    Therefore, we can see visibility, more or less, in Power hardware that will provide ample enough compute power for the vast majority of IBM i, AIX, and Linux customers that Big Blue has through 2030. And if you look at the various IBM i roadmaps, which are published in presentations and strategy documents, we can see the support to go out even longer. Here is the IBM i roadmap from 2019, to which I have made some modifications to update it:

    First, I extended the light blue line for IBM i 7.1 to reflect the extended extended support that Big Blue added to this release back in October of this year, stretching its extended support by two years until the end of April 2023. That will make IBM i 7.1 the longest supported release in the history of the IBM midrange since 1969. IBM is clearly not afraid of longevity, and customers have some issues as well as some comfort. The red bars have been added to show three years of extended support after normal support is removed. So, you can see that with iNext or IBM i Next, which should coincide with the Power10 launch next year and into 2021, regular support runs to about 2030 by that roadmap from 2019 and then you can assume 2033 given extended support (which has its limits, as we have discussed often). For IBM i Next +1, which we presume coincides with Power11, it looks like extended support runs until late 2036 or early 2037, if history is any guide.

    Now, to stay on that IBM i support schedule, you will have to be on reasonably current hardware, generally two generations back. So IBM i Next will require at least a Power8 system and IBM i Next +1 will require at least a Power9 processor. But IBM i 7.4 will very likely also be supported on Power10 and Power11 iron as well. But that will be the end of the road there, and IBM i 7.3 will probably only get to Power10. Again, if history is any guide.

    And that is the thing. History is a guide, but not a guarantee, and IBM will tell you. The IBM i roadmap below, which was shown by Steve Sibley, vice president and offering manager for the Cognitive Systems division at IBM, at the Common Europe Online vCEC 2020 event a few weeks ago, is less precise in the dates covered but does come with some disclaimers. Take a look:

    Let’s repeat in print what IBM says above so the search engines see it and old eyes with decades of looking at screens see it:

    ** All statements regarding IBM’s future direction and intent are subject to change or withdrawal without notice and represent goals and objectives only.
    ** Arrows indicate "ongoing status" and do not imply specific dates.

    A roadmap, no matter who is drawing it, is only as good as the terrain you actually end up driving through, the vehicle that you take, and the fares that the riders on the platform bus are willing to pay to go where you say we all should be going. You need all three of these to actually get to where you are going.

    It is important not to mix up intent with contractual agreement. A roadmap is not a promise, it is an intent, and while IBM has been very good in making good on its intentions, conditions change and so do regimes at major IT vendors. There is never a guarantee of anything, really. Just ask the 20,000-plus employees in Europe of IBM’s NewCo spinoff of its outsourcing and hosting business who are rumored to be soon handed pink slips – or rather, be given the sack if we are talking colloquially in England or renvoyé de son travail in France or essere licenziata in Italy or gefeuert zu warden in Germany, and so on. That’s around 22 percent of the 90,000-strong NewCo workforce. Conditions change, indeed.

    Now, back to IBM i.

    The good news is that a lot of Power Systems customers don’t need for IBM i to be doing a lot more than it is already doing. Adding support for new hardware features – we find the memory clustering technology in Power10 particularly intriguing – will be key, as will the addition of new languages and programming frameworks as time passes. We expect to see more tight integration with AI software stacks and features in IBM i that let it be more easily deployed on the public cloud and have its pricing metered more like a cloud subscription. The database and various kinds of resiliency and high availability clustering will also see improvements. But generally, IBM i Next and IBM i Next +1 will look a lot like IBM i 7.4. We are talking about fairly modest changes, at least compared to the early and middle years of OS/400, when so many things were changing.

    Think about it. How much of the OS/400 stack was changed to make it suitable to host Internet protocols and workloads? Do we think there is a substantial, big change on that level coming to corporate computing? I don’t. And that means change will be less and less jarring even if it is a fairly regular pain in the neck and always carries a certain amount of risk that something can go wrong as systems software is upgraded and updated. The trick is to not get your applications trapped on an old release of IBM i. Far too many companies have done this, for a multitude of reasons, and this is why Big Blue keeps extending IBM i 7.1 out and out and even went so far as to support IBM i 7.1 on Power9 hardware only a few weeks ago in some kind of degraded mode.

    We have been advocating for just this approach for many, many years, and we think IBM should go all the way back to IBM i 6.1, i/OS 5.4, and OS/400 V5R3 if necessary to get every customer on current Power9 iron. Why not? Charge for the software support and create an organization to support old releases. A lot of them. Stretch those light blue and red bars out to infinity and beyond! And charge a fair price for supporting so many releases. These customers have stable workloads, so it should be fairly easy compared to a Linux platform running AI software that changes every freaking day.

    It’s a far better model than encouraging customers to move to Windows Server or Linux with Microsoft or Oracle databases running on X86 iron. IBM only sells the Linux part of that switch, and it is far less lucrative than supporting customers where they are and moving them ahead on hardware. Who cares if it takes more cycles to do this? IBM i shops and most AIX shops will have more cycles than what they want anyway in a Power9, Power10, or Power11 system.

    And if IBM doesn’t want to support these heritage releases, then farm it out to a bunch of techies who know how to do it and will do it if Big Blue turns them on inside of the PowerVM hypervisor.

    I’m just interested in results. There are many ways to achieve them.

    RELATED STORIES

    Resilience In The Platform, Resilience In The Business

    IBM Reveals Power10 Rollout Plan, Begins Power11

    IBM’s Possible Designs For Power10 Systems

    Drilling Down Into The Power10 Chip Architecture

    Power To The Tenth Power

    IBM i Roadmap Promises A Long Ride, Few Bumps

    The IBM i Roadmap Leads To A Familiar Place

    IBM i Strategy And Roadmap Loses Business Focus

    Power Systems Slump Is Not As Bad As It Looks

    The Path Truly Opens To Alternate Power CPUs, But Is It Enough?

    Powers Of Ten

    IBM Gives A Peek Of The Future At POWERUp 2019

    What Open Sourcing Power’s ISA Means For IBM i Shops

    IBM’s Plan For Etching Power10 And Later Chips

    The Road Ahead For Power Is Paved With Bandwidth

    IBM Puts Future Power Chip Stakes In The Ground

    What Will IBM i Do With A Power10 Processor?

    Samsung Joins The OpenPower Consortium Party

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Tags: Tags: AIX, AS/400, i/OS 5.4, IBM i, IBM i 6.1, IBM i 7.1, Linux, NewCo, OS/400, OS/400 V5R3, PASE, Power10, Power11, Power8, Power9, PowerVM, RS/6000, System/3, System/38, X86

    Sponsored by
    UCG Technologies

    Best Practices for Doing IBM i Cloud Backup & DRaaS Right

    In the technology business for 30+ years including more than a decade in cloud backup and disaster recovery, we’ve learned a few things along the way. Here are best practices to follow – and land mines to avoid.

    1. RELIABILITY. Up to 71% of restores from tape contain failures.
    • BEST PRACTICE: Use disk-to-disk technology for backups.

    With disk-to-disk technology, your backup data resides on disk drives, proven to be far more reliable than tapes. When your backup completes, you know the data is secure and accessible on the disk drive. With tapes you never really know if your data is usable until you try to restore it, at which point it’s too late.

    1. BREADTH OF OFFERING. Choice in product and service offerings meet your business’ needs.
    • BEST PRACTICE: Don’t settle for less than what you need.

    Vendor offerings vary widely. Some are designed primarily for consumers and others for enterprise data centers. Choose a solution that scales and offers the features you need to provide the level of service you expect. De-duplication and delta-block technologies will improve performance, reduce your data footprint and save you money. Find out if their de-duplication offering is at the file level or the block level. Make sure the solution can back up servers, PCs, and laptops as well your applications.

    1. SECURITY. 60% of organizations using tapes don’t encrypt their backups.
    • BEST PRACTICE: End-to-end encryption with no “back door.”

    Using encryption with tape makes backups run slowly and often takes too long to fit within a backup window. As a result, most people simply turn encryption off, creating a security risk. Even with the physical safety of disk-to-disk backup, encryption is essential. Look for 256-bit AES. Find a solution that encrypts your data during transmission and storage. Make certain there isn’t a “back door” that would let someone else view your data.

    1. ACCESSIBILITY. Companies waste thousands of hours waiting on tapes.
    • BEST PRACTICE: Ensure that you can get your data back with minimal delay.

    You should have direct access to your backups, with no time spent on physical transport (no trucks, no warehouses). Restores should take minutes, not hours or days. Set yourself up to work with your data, not wait for it. Make sure your solution provider can meet your Return-to-Operations (RTO) and Recovery Point Objectives (RPO) which determine how quickly you can recover your data and maintain business continuity. Inquire about onsite and offsite replication that provide both improved performance and a solid disaster recovery strategy.

    1. CYBER SECURITY. More than 80 percent of U.S. companies have been successfully hacked, according to a Duke University/CFO Magazine Global Business Outlook Survey.
    • BEST PRACTICE: Regular cyber security training and phishing tests for all employees using company email are essential to your organization.

    Your end-users are the weak link in your network security. Today, your employees are frequently exposed to advanced phishing attacks. Trend Micro reported that 91% of successful data breaches started with a spear-phishing attack. Be sure your vendor of choice includes cyber security training as part of their backup and DR package.

    1. SCALABILITY. Some backup systems can’t scale readily.
    • BEST PRACTICE: Invest in a data protection architecture that can grow with your business.

    You should be able to back up your data no matter how large it grows. Starting small? Look for an option that handles your backups automatically. Then, as you grow, gives you tools to manage complex environments. Look for “changes-only” and compression technologies to speed backups and save space. And insist on bandwidth throttling to balance traffic and ensure network availability for your other business applications. Make sure that their solution offerings rely on common technology to scale easily as your business––and data––grow.

    1. COST-EFFECTIVENESS
    • BEST PRACTICE: Calculate the true total cost of tape-based back up.

    A 2019 Server OS Reliability Survey found that one hour of downtime costs at least $100K for 98% of companies to over $5 million for 34% of surveyed companies. When you do the math, the dollars make sense: Go with disk-to-disk. Unlike tape, there are close to zero handling costs—no rush deliveries, loading, accessing, locating, or repeated steps. And there’s one benefit you can’t factor directly: Reputation. Reliability and security can make an incalculable difference with just one avoided breach or failure.

    1. COMPLIANCE. Most companies have problems satisfying privacy, security, and data retention regulations.
    • BEST PRACTICE: Choose a data protection partner who has deep know-how about compliance, and the technology to ensure it.
    1. Disaster Recovery. Most companies lack a comprehensive, tested plan for disasters.
    • BEST PRACTICE: Find a vendor that delivers a complete DR solution.

    You can’t say your data protection is complete until you have a disaster recovery plan that is itself complete and tested. Your backup vendor should have both the product mix and professional services team to help you prepare for a worst-case scenario. Make sure they can help configure your backups so you rebound quickly. Best bet: A vendor who can train you to deal with disasters confidently, based on your company’s actual configuration.

    1. EASE OF USE. Some companies don’t —or can’t—manage their backups from one place.
    • BEST PRACTICE: Get control and reporting you can use anywhere, with ease. Managing your backup environment should be simple, and the software you use should eliminate any guesswork that could lead to lost data. You should know at all times if your data is protected across your entire network—including remote offices—by simply looking at a dashboard. The software should be simple to configure using wizards, yet powerful enough to meet your specific needs with customizable views, job propagation, and roles-based security.
    1. OPERATING SYSTEM AND PLATFORM SUPPORT. Most backup vendors support a limited range of OS, server types, and applications.
    • BEST PRACTICE: Look for broad and deep technology that supports your complete environment. Your backup solution should accommodate your environment, not vice versa.
    1. CUSTOMER SUPPORT. Backup vendors’ product support varies widely.
    • BEST PRACTICE: Find a vendor whose support is passionate, maybe even slightly obsessed. Customer support should be one of your vendor’s main selling points. You shouldn’t have to wonder if they’ll be there to help when you need them most. Do they offer phone support or email only, and who exactly are you talking to when you call that 800 number? Find a vendor that will treat your data as if it were their own.
    1. REPUTATION. Does your backup vendor have a quality reputation and the financial resources to stay in business for the long haul?
    • BEST PRACTICE: Find a vendor with strong financial backing and customer references. There are a lot of vendors that have come and gone. When you consider a service provider, look for one that has strong financial backing, a solid business plan and the ability to be in business as long as your data needs to be stored. Ask for customer references and case studies as their customers are the best validation you can get.

     

    Visit VAULT400.com/proposal to receive a FREE analysis and proposal

    DOWNLOAD SOLUTIONS BRIEF:
    Best Practices for IBM i Cloud Backup & Recovery

    DURING THIS UNPRECEDENTED TIME, DON’T WAIT FOR YOUR BUSINESS
    TO SUFFER A DISASTER TO TAKE ACTION.

    Serving the US, Canada, & Latin America

    VAULT400 Cloud Backup & DRaaS is an IBM Server Proven Solution.

    800.211.8798 | info@ucgtechnologies.com| ucgtechnologies.com/cloud

    To the First Responders serving on the front-lines during the COVID-19 pandemic,
    we extend our heartfelt gratitude.

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Thoroughly Modern: What’s New With PHP On IBM i? IBM i PTF Guide, Volume 22, Number 49

    Leave a Reply Cancel reply

TFH Volume: 30 Issue: 78

This Issue Sponsored By

  • UCG Technologies
  • Fresche Solutions
  • ARCAD Software
  • Computer Keyes
  • Manta Technologies

Table of Contents

  • To 2032 . . . And Beyond!
  • Thoroughly Modern: What’s New With PHP On IBM i?
  • Guru: Fall Brings New RPG Features
  • As I See It: Disruption Revisited
  • MariaDB Now Available Via RPM

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • IBM i Software And Power Systems Upgrades Keep Rolling Forward
  • Preparing For What’s Next In A Thoughtful, Structured Way
  • Guru: Fall Brings New RPG Features, Part 3
  • ARCAD Plugs IBM i DevOps Suite Into Microsoft Azure
  • Park Place Buys Curvature To Become Maintenance Goliath
  • 2021 Predictions for IBM i, Part 1
  • West Four Stands Out With On Demand Color Label Printing
  • HelpSystems Acquires Data Security, File Transfer Companies
  • Four Hundred Monitor, January 13
  • IBM i PTF Guide, Volume 23, Number 2

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2021 IT Jungle

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.