7 Reasons To Be Thankful For IBM i – IT Jungle

7 Reasons To Be Thankful For IBM i

November 16, 2022

Alex Woodie

Despite problems around the nation, Americans still have a lot to be thankful for. We have really good schools, a strong U.S. dollar, and a tech sector that’s the envy of the world. And while the IBM i server plays a smaller role in the day-to-day running of our country than it used to, there are still many reasons to be thankful for platform.

IT Jungle will take a break from publishing next week to rest, eat turkey, and think about what we’re thankful for, which definitely includes the IBM i. Thankfully, we have prepared a list ahead of time (much like that premade pie that your sister-in-law always brings).

Here are seven reasons to be thankful for IBM i in 2022:

The IBM i Installed Base

The IBM i installed base is smaller than it used to be. By some estimates, there were a quarter-million organizations running the AS/400, the legendary predecessor to the IBM i. The business pushed several billion dollars in annual spending, rivaling the S/390 mainframe in revenue (if not prestige).

Nowadays, it’s generally understood that there are less than 100,000 organizations in the world running IBM i. Yes, many organizations have moved off the platform and to industry standard platforms or the cloud. IBM i continues to be misunderstood by younger tech leaders, who take one look a greenscreen IBM i app and decide the whole platform is a liability.

No matter. The platform still demands loyalty among those who have stuck with it, who see it as the unrivaled IT asset that it truly is, rather than a liability. In head-to-head matchups, the IBM i trounces standards-based systems in total cost of ownership. When was the last time you saw a Windows Server user proudly proclaiming that her company runs on Windows? Answer: Never.

IBM i Professionals

IBM i pros are the hardworking men and women who make the world go ‘round for the companies that rely on the IBM i to run their businesses, day in and day out, rain and shine. The platform is legendary for its uptime and resilience, but it’s not doing anything without the talented humans who make it all work.

IBM i professionals are a unique lot in the IT world, as they bring a multi-threat capability to their daily game. They’re one part developer, one part business analyst, one part operator, and one part IT firefighter. They were “full-stack” before full-stack became the latest thing in the “look at me” mainstream IT world.

But human resources are also a big concern for the platform at the moment, as numerous IBM i shops report how difficult it is to find replacements for retiring professionals. They are a precious resource on the platform, and truly something to be thankful for.

IBM i User Groups

One of the strengths of the IBM i community is the multitude of user groups that help to keep IBM i professionals united. That includes the dozens of smaller local user groups scattered across the country, the larger regional groups like OCEAN, and well as the national groups, like COMMON and the Large User Group. Outside of the United States, groups like COMMON Europe and the Japanese IBM i user group (formerly known as iSuc) have kept the IBM i community together, through large events and monthly meetings.

These groups were tested during the COVID-19 pandemic, as in-person meetings and large events had to be cancelled. Many of these groups pivoted to virtual events, to varying degree of success. While Zoom meetings have some benefit, there is no way to replicate the full spectrum of benefits that come from a good in-person conference or meeting. Luckily, many of these groups survived the pandemic and have continued with in-person meetings, which is so crucial to maintaining the continuity of the community and the platform.

IBM i’s Deep Technical Roots

The IBM midrange server was once described as a “farmer’s box” by the CEO of a major ERP vendor. While it may have tickled the fancy of a farmer or two in the vast fields south of the IBM Laboratory in Rochester, Minnesota, the comment was not a compliment.

The truth is, the IBM i server can be as sophisticated or as rudimentary as you want it to be. Yes, you can treat it like rusting, 50-year-old plow if you’d like, and it will continue to run your business despite the abuse. But the platform can also run some of the most cutting-edge applications on the planet, if you give it the chance.

All the cool kids today are running containerized microservices in the cloud, which is supposedly “the future” of computing. Never mind that there is essentially no visibility into the interactions between these containerized microservices applications, the Docker container, and the Kubernetes scheduler. Just cross your fingers that you never have to troubleshoot those types of application performance issues – and thank your lucky stars that currently IBM has no plans to co-mingle IBM i and Kubernetes in any kind of direct way.

Instead, the old dog has a few nifty tricks left to teach the younger canines, as it turns out. IBM i has an exceptionally strong architecture, thanks in part to its single-level storage system. That apparently attracted the attention of some pretty high-level folks who asked the retired Dr. Frank Soltis back in 2020 for some direction on how to scale supercomputers and AI systems. Yes, there is a reason this architecture is still kicking in its sixth decade.

New Web and Mobile Applications

The investment protection in code is a double-edged sword for IBM and its midrange customers. On the one hand, code written 40 years ago can still run on the platform. But on the other hand, code written 40 years ago is still running on the platform. Every good deed, apparently, will be severely punished.

There is a lot of ancient code powering old applications on the IBM i server, which is a very bad thing. In fact, all that old code arguably is the main reason for the widespread perception that the IBM i server is a “legacy” box that should be left out in the field (maybe next to that rusting old plow).

This is why you we should all be thankful for new Web and mobile application development. IBM i shops that are embracing open source technologies such as PHP, Node.js, and Python to develop new Web and mobile applications are a true beacon of hope for the IBM i installed base.

While you can continue to run that old greenscreen RPGIII program until the cows come home, your users and customers would probably much rather work with an application that behaves like other modern apps they’re used to using. That alone should be worth the investment.

But here’s the kicker: Adopting these newer technologies will also make it easier to attract younger programmers to the platform, and give IBM i shops a shot at turning them into the multi-threat developer-analyst-ops people that will be so desperately needed in the next generation. That’s a triple-win across customers, employees, and owners.

The IBM i Vendor Community

Like the installed base, the IBM i independent software vendor (ISV) community has shrunk a bit over the past 10 to 15 years. The number of software houses developing and selling system utilities and business applications is not what it used to be.

But there remains a core group of ISVs that have stuck it out. They rolled with the punches and refused to quit during the Great Recession from 2008 to 2009 and COVID economic shutdown in 2020 and 2021. They stuck to their guns and continued developing good software and providing solid customer support.

While the ranks of the ISVs has dwindled due to consolidation, there is a new generation of leadership emerging in the vendor community. A computer platform is only as strong as its weakest link, but thanks to hard work of independent business owners, the ISV community is not it in the IBM i world.

IBM Itself

Few companies in the country have a corporate history as long and storied as that of International Business Machines. And no other company has had such a hand in guiding the IT business over the past 100 years as IBM.

However, these are not the best of times at the company with the iconic striped logo. While IBM’s cloud competitors soar to valuations in excess of $1 trillion (and over $2 trillion for a time for Microsoft), IBM has stayed stuck at around $129 billion.

Despite the competitive situation and the shift away from on-prem gear, the Armonk, New York company has persevered. It continues to develop cutting edge hardware, such as the Power10 processor, which sports the sort of memory bandwidth that X86 chip vendors can only dream of. IBM has led the world in the number of new patents issued for 29 straight years, and there’s little to believe it won’t lead in that category when the next list comes out, in January 2023.

Yes, IBM has made some questionable decisions when it comes to the IBM i platform from time to time. But as a whole, the work that it does to keep this platform going and make it viable is something to be honored and be thankful for.

Happy Thanksgiving, everyone.

6 Threats to the High Availability of Your Data (and How to Solve Them)

Achieving high availability for data is tough. The best-laid data infrastructures often go awry for a variety of reasons, and they bring data availability down with them.

What are those things that can go awry and prevent data high availability? And what can you do to stop or mitigate them?

Threats to high availability

Let’s take a look at some of the obvious and not-so-obvious high availability problems you may encounter with your data infrastructure.

1. Infrastructure failure

Let’s begin with what is probably the most obvious source of disruption to high availability for your data: Infrastructure failure. When part of your infrastructure goes down, you are likely to experience a disruption in service, and fail to achieve high availability.

Infrastructure failure can take many forms. It could mean a failed disk or a network switch that has become overloaded. It could involve virtual servers that crash because of problems with the hypervisor that powers them. It could be a bad memory stick that brings down a host server.

In practice, it’s pretty hard to know ahead of time which parts of your infrastructure are at risk of failing. For that reason, the best safeguard against this risk is to build redundancy and backups into your data infrastructure, and enable them via automated failover. Automated failover means (as the term implies) that the backup system takes over automatically when the main system goes down.

Read our guide

The Ultimate Buyers Guide to HA/DR Solutions

The demands for high availability are more stringent and the competition to put the most advanced technology on the market is more vigorous than ever. How can you be sure you’re choosing the best solution for your company? This white paper acts as the ultimate buyers guide to HA/DR solutions.

2. Infrastructure overload

Another common problem for high availability for data is infrastructure overload.

It’s possible for the load placed on your infrastructure to become so great that the infrastructure can no longer handle it, and service is disrupted as a result. This could happen if, for example, you attempt to process a sudden influx of new data without having set up new infrastructure to handle it.

The best defense against this risk (beyond not deliberately overloading your infrastructure, of course) is to build scalability into your data infrastructure. This includes not just ensuring that you can set up new infrastructure quickly when you need it, but also thinking about scalability from a big-picture perspective: Will your IT team be able to scale up, too, when it has more data infrastructure to manage?

3. Malicious activity

It may be obvious that there are bad people out there who want to disrupt your infrastructure’s high availability. Threats like DDoS attacks that originate on external networks can quickly bring your data and other services down.

But external attacks are not the only type of malicious threat. Your availability could also at risk from insider attacks carried out by, for example, a disgruntled employee.

There are some tools you can deploy, like anti-DDoS routers, to mitigate the risk of attacks. Since you can’t know exactly where an attack might originate, however, it is also important to have backups in place so that if data services are interrupted, or data is destroyed, you can restore it quickly from backups.

4. Data inconsistency

Data that is not available in the format that you need to work with it, and cannot be transformed quickly enough to that format, poses a problem for high availability. Technically, data that exists in the wrong format may still be available, but unless you can transform it as required, it may as well not be available at all.

The best solution to this challenge is to ensure that you have flexible, automated data transformation tools at your disposal. With those tools, you can transform data quickly when you need to move it from one format (like a cloud-based, block-level storage system) to another (like an on-premise file system).

5. Poor data quality

Data without data quality is not very useful. When your data sets are filled with inconsistencies, redundancies, inaccuracies or other issues, they prevent you from using data effectively, and undercut high availability.

Control this problem by leveraging data quality tools to clean up data sets, and building them into your data management processes. Data quality control shouldn’t be a one-off or periodic process; it should be part and parcel of the rest of your data management workflow.

6. Data access problems

Last but not least on our list of threats to high availability for data is data access. If the right users don’t have access to the right data, they won’t be able to do their jobs, and your data may as well not exist at all.

Ensuring that users who should have access to a given body of data while preventing unauthorized access requires careful planning, but it’s essential in order to achieve data security. Build access control into your data infrastructure from the beginning to help streamline your solution to this conundrum.

Precisely offers high availability solutions to help protect your IBM i infrastructure from outages. For more information, read our white paper: The Ultimate Buyers Guide to HA/DR Solutions.

The post 6 Threats to the High Availability of Your Data (and How to Solve Them) appeared first on Precisely.

Robot | Ten Job Scheduling Features Your IBM i Can’t Live Without

Interested in learning more about Robot Schedule? Request a demo here: https://www.helpsystems.com/products/job-scheduling-software-ibm-i/demo

Robot Schedule has hundreds of features that all play a huge role in automating and monitoring your IBM i batch workflows. But which ones are considered the most crucial to your IBM i‘s success and why?

Watch as your favorite Robot Schedule gurus Tom Huntington and Chuck Losinski reveal what features have made their top ten list. Chuck and Tom have over 60 years of experience with Robot Schedule; helping customers with complicated scheduling and industry needs around automation every day.

In this session they will cover why these features are so critical to a high performing IBM i and how they:

-Meet today’s automation challenges
-Help customers pass today’s regulations
-Provide the management reporting needed for decisions

Watch now!

Introduction to SR-IOV and vNIC for IBM i

 

This is the first in a series of articles on frequently overlooked Power systems features that highlight the value for IBM i customers, starting with sharing Ethernet adapters with SR-IOV, and the added benefits that can be achieved with vNIC technology on top of SR-IOV. 

Whether you have an existing system that is already capable of these features, or you are considering migrating to new hardware, you can only benefit from knowing what your options are.

What Is SR-IOV?

SR-IOV (Single Root Input/Output Virtualization) is a hardware specification that allows multiple operating systems to simultaneously use a single I/O adapter in a virtualized environment.  It is not unique to the Power Hypervisor (PHYP).  You can find SR-IOV being used heavily in x86 based virtualization, such as VMWare or Hyper-V – a fact that just serves to complicate searches for information related to IBM i.

More to the point for the IBM i administrator, it allows a single SR-IOV capable adapter to be shared by multiple LPARs.  You can split a single adapter with two ports, dedicating each port to a separate lpar, or you can go more granular and share different percentages of the bandwidth of a single physical port between multiple partitions.  When sharing a single physical port, you get to specify the minimum percentage of outgoing bandwidth each partition gets, allowing each partition to use available bandwidth to burst higher when necessary.  It is also possible to limit the maximum outgoing bandwidth a given partition will use, although this is only possible via the HMC CLI, not the HMC GUI.

What is vNIC?

vNIC is a Power virtualization technology built into PowerVM that leverages the combination of VIOS (Virtual I/O Server) virtualization with SR-IOV adapters to get the performance and flexibility of SR-IOV with the additional flexibility and redundancy of a fully virtualized solution.  I expect to expand on VIOS in much more detail in future article.  For now, I’ll just say that vNIC provides an automated active/passive failover ability and supports the use of Live Partition Mobility.  If you already use VIOS, you should strongly consider SR-IOV adapters with vNIC rather than Shared Ethernet Adapters (SEA) unless you need the active/active load sharing configuration that is only available with SEA.  If you don’t use VIOS, watch out for a future article for why you should.

Why SR-IOV?

          Better use of limited resources.  10G ethernet adapters have become common in enterprise configurations.  Most of these adapters have multiple ports.  Without SR-IOV, each adapter is usually dedicated to a single partition, often leaving the extra ports unused while additional adapters are dedicated to other partitions, leaving even more ports unused.  How many of these ports are utilized to their full capacity?  Not as many as you might think (seriously, collect some performance stats and see for yourself).  More adapters used at a fraction of their capacity means more cabling and more network switch ports, all used at a fraction of their capacity.  That gets costly, for both the server and network budgets, especially when working with 10G ports.

          More flexibility.  Once you have connected ports to network switches, you can add partitions that use those ports without any additional cabling or network configuration.  This is especially true if you configure those ports as trunks and use VLAN tagging at the IBM i TCP/IP configuration to access different networks and IP address ranges.

          Better Performance than other shared configurations.  Compared to traditional server-based networking configurations (VIOS Shared Ethernet Adapters or IBM i NWS Virtual Ethernet), SR-IOV connections perform much better.  Virtual ethernet connections have processor overhead, and many tuning parameters that limit performance.  SR-IOV establishes a hypervisor managed path to the hardware that is second only to a dedicated adapter.  In the real world, SR-IOV will perform effectively the same as a dedicated adapter, and better than any server virtualized adapter.

Who should use SR-IOV?

          Large Enterprises should consider SR-IOV and vNIC technology to achieve high bandwidth connectivity to enterprise scale 10G (and up) infrastructure .  Automatic failover (vNIC) to redundant connections ensures connectivity that leverages the highly redundant network infrastructures that exist in high-end enterprises.

          Small businesses should consider SR-IOV and vNIC technology to get the maximum capacity out of the investment in network connectivity.  Fewer adapters, less cabling and a smaller number of network ports is easier on the budget, while still providing the ability to adapt to changing business needs.  SR-IOV adapters provide the ability to share adapters between partitions without any server based virtualization, resulting in a simple to maintain shared configuration when other virtualization functions are not required.

What else do I need to know?

          For all of the following, see the SR-IOV FAQ for details.  It can be found at:  https://community.ibm.com/community/user/power/viewdocument/sr-iov-vnic-and-hnv-information

You must have an SR-IOV supported adapter, so make sure your IBM Sales Representative or Business Partner knows you want SR-IOV when ordering a new system.SR-IOV adapters must be placed in specific slots.  On Power 9 and Power 10 hardware, this includes most of the slots in the system.There are limits on the number of SR-IOV enabled adapters per system.  As of November 2022, the maximum number of SR-IOV shared adapters is lower of 32 or the number of SR-IOV slots in the system.  This is not really limiting for most customers.There are limits on how many shared (logical) ports can be assigned to a physical port, depending on the specific adapter (Ranging from 4 to 60)There are limits on how many shared (logical) ports can be assigned per adapter (ranging from 48 to 120)SR-IOV adapters in shared mode require Hypervisor memory (see FAQ)Pay particular attention to limitations for 1G ports on supported adapters, especially 1G SFP+ in 10G+ adapters as these may not be supported for SR-IOV.HMC is required for SR-IOV support. VIOS is required for vNIC.  VIOS is NOT required for SR-IOV.Sharing a Link Aggregation (e.g. LACP) of multiple ports is not allowed.  This is not as bad as it sounds as Link aggregation is effectively used as a redundancy measure in a VIOS SEA configuration rather than as a performance measure.  SEA simply does not have the capacity to use more than a single link’s bandwidth.  In practically all cases where Link Aggregation is used with VIOS, vNIC with failover is a better solution.  In the rare case that it is necessary, Link Aggregation can be managed at the IBM i O/S level with the CRTLINETH RSRCNAME(*AGG) command if the SR-IOV physical ports are 100% dedicated to a single partition.  See https://www.ibm.com/support/pages/configuring-ethernet-link-aggregationChanging the minimum capacity of a SR-IOV logical port is disruptive, so plan accordingly.  Remember that the value is a minimum, and all logical ports can burst higher.  This means that barring any specific continuous outgoing bandwidth requirements, you are better off estimating low.Bandwidth splitting on SR-IOV adapters is based on outgoing bandwidth only.  There is no way to split incoming bandwidth, so consideration should be given to anticipated incoming bandwidth when deciding on how many partitions can share a port.SR-IOV cards are not owned by any partition, so typically adapter firmware updates are included in System firmware updates.  If necessary, there is a separate procedure to install adapter firmware updates separately that you may need to use. 

How to configure an SR-IOV port on IBM i

Rather than including a bunch of HMC screenshots that duplicate existing resources, I’ll direct you to the excellent reference material in the “Selected References” below, especially the Redpaper.  These references will show you how to put an SR-IOV adapter in shared or hypervisor mode and how to configure a logical port for a partition.  There is no difference between doing this for AIX and IBM i.  The specific web interface may change a bit with each HMC release, but the concepts remain the same.

Once the resource is created, the easiest way to determine the resource name is to select the partition from the HMC and get the CMNxx resource name from the “Hardware Virtualized I/O” page for SR-IOV, or the “vNIC” page for a vNIC.  It will also show up along with all of the other resources in WRKHDWRSC *CMN, or STRSST.  Once the resource name is located, configure it exactly as you would any other Ethernet resource by creating a Line description, IP address, etc.

You can dynamically add and remove SR-IOV and vNIC resources to/from a running partition.  Make sure that if you remove one, there are not any configurations using that resource.

What if you need help implementing SR-IOV or vNIC on an IBM i?

Whether you have a large environment or small, implementing new technologies can be challenging.  If you need help beyond the available documentation, the IBM i Technology Services team (formerly known as Lab Services) is available to help with implementation planning, execution, and knowledge transfer.  See https://www.ibm.com/it-infrastructure/services/lab-servicesfor contact information or speak to your IBM Sales Representative or Business Partner.  If you are planning a new hardware purchase, you can include implementation services by the Technology Services team in your purchase.

Disclaimer

I am an employee of IBM on the IBM i Technology Services team (formerly known as Lab Services).  The opinions in this post are my own and don’t necessarily represent IBM’s positions, strategies, or opinions.

Selected References

I often find that researching topics related to Power Systems provides a wealth of information relating to AIX and VIOS, and substantially less that relates directly to IBM i.  Having spent a few years administering AIX systems, I am familiar with the many excellent AIX blogs that are available.  Many of these references are very AIX focused, but don’t let that dissuade you from reading them — they are also excellent resources for IBM i administrators.

IBM Power Systems SR-IOV Technical Overview and Introduction Redpaper https://www.redbooks.ibm.com/abstracts/redp5065.html

IBM Support: Configuring Ethernet Link Aggregation

https://www.ibm.com/support/pages/configuring-ethernet-link-aggregation

IBM Community: SR-IOV FAQ

https://community.ibm.com/community/user/power/viewdocument/sr-iov-vnic-and-hnv-information

AIX for System Administrators – SR-IOV & vNIC summary pages

http://aix4admins.blogspot.com/2016/01/sr-iov-vnic.html

http://aix4admins.blogspot.com/2017/03/vnic_20.html

YouTube – This is the replay from the May 28th, Power Systems Virtual User Group Webinar covering Single Root I/O Virtualization (SR-IOV) presented by expert Chuck Graham

https://youtu.be/1ANyxQaSXOI

TL;DR 

SR-IOV lets you share ethernet adapter cards across multiple IBM i partitions without using VIOS.  vNIC adds the ability to include automatic active/passive failover if you also use VIOS.

Verified by MonsterInsights