The Risk of Running an Old IBM i System

There’s no question, running a business-critical ERP (Enterprise Resource Planning) application on a 20-year-old server, with a 20-year-old operating system presents a risk to the business. Running very old systems in a company is often described as “technological debt,” as the cost to resolve that status tends to increase over time.  Some investment firms and private equity groups actually use technological debt as a metric in their list of business attributes to review and monitor.   

What are the areas of risk when running out of date software? 

Cyber Risks

The older an IBM i OS is, the more vulnerable it is to cyber intrusion. The often stated perceived “security” of the old OS refers to user access controls within an isolated office of the 1990s, not a server that today is accessible via a company network, let alone a network which is connected to the Internet.  As your company expands and more systems and applications are connected to the IBM i, cyber risks grow. 

Hardware Risks

Besides no longer being covered by IBM support, the hardware itself won’t last forever and replacement parts will eventually not be available for repairs.  As it is, replacement parts for older Power servers are taken from recycled inventory and other old Power servers.  Remember, some hardware failures just happen, without prior announcement, and take your server offline. Those old parts may take days to obtain. The service engineers who know the old servers may be busy working on other projects before they can get to you. Can you afford to have your ERP offline for 3 or more days?

Financial Risks

As time progresses, the complexity, cost, and effort to migrate or upgrade grows. Especially when the updates have been skipped for over 20 years, multiple OS and application upgrades steps may be required.   

With every version that hits end of support, your technological debt grows exponentially 

For instance, to update from V5R4, you need to first update the OS to the latest version that your server can run, for a Power 5 server, that’s V7.1 (see this chart to find where you are). Once there, you can then jump to Power 9. Once on Power 9, you can update the OS to IBM i OS 7.4 or 7.5. Of course, you’ll also need to update applications along the way.  

Disaster Recovery Risks

When running out of date software, vendors may be slow to provide a replacement license key should a need suddenly arise to move to a replacement server (e.g. Disaster Recovery total hardware failure or loss event). With older systems, vendors may flat out refuse to provide assistance if support windows have closed.

The bottom line is, the further level back the server and/or operating system are, the more likely the chances that upgrading can move from a one-step process to a many-step process and this translates into a lot of, time, cost, and complexity. While it’s ideal to upgrade to currently supported hardware and software, consider migrating at least to a “less old” and more recent version of IBM i OS. This action will help reduce your company’s risk while providing a cost-effective option while you evaluate longer-term solutions.     

 

A screen a story – What does “move active records” mean?

The latest Technology Refresh (TR) for IBM i 7.4 and 7.5 has something new within them for reorganizing a file. If you have lost count of the TR levels IBM i 7.4 is at TR7 and IBM i 7.5 is at TR1. Every time a new TR is announced it can be overwhelming with the amount of enhancements and by the time you have it installed on your IBM i Server, it is hard to remember all the good stuff coming along with it.

So please see this as a kind reminder and for me the opportunity to put one specific announcement in the spotlight, falling under the category “Db2 for i – Database Engineer Enhancements”, called “Online reorganize physical file member (RGZPFM) enhancement”. The good news is that this enhancement was made available for both IBM i 7.4 and 7.5, implemented in the same way. When you open up the link it will show you two screenshots:

And…

Apparently, the difference lies with the fact that with the latest TR reorganizing with Allow Cancel , ALWCANCEL(*YES) now moves the record instead of deleting then reinserting it.  

Before going into more details about what is happening now when you reorganize a file with the RGZPFM command, allow me to give you some background information about the Reorganize While Active.

This link RGZPFM – Basics on Reorganize While Active will help you in getting to know what is needed to perform a Reorganize while active. Today it is hard to determine in which release this option was made available as documentation for IBM i older than 7.1 is hard to find (please correct me if I’m wrong) but I think it was in IBM i 6.1.

As DDS is still around and used when creating a physical file so is the default of the Create Physical File (CRTPF) command. The default for the parameter “Reuse deleted records . . . . . REUSEDLT” is still set to *NO. When creating a table, the default is the other way around and the Reuse deleted records option is always set to *YES. This is for sure a disk space saver. When thinking about SQL performance you might have a look here A screen a story – SQL Performance – a Table Scan.

As you may know or not know a Table scan touches all the records in a file. If a file contains deleted records a scan will take longer because the process touches every record, including deleted records. The fact that the command RGZPFM requires down time, time when the file is not in use, prevents many shops from reorganizing files with deleted records on a regular basis.

The Reorganize while active requires journaling and even that is still not implemented everywhere because of the DDS heritage IBM i has. With the right settings and the 5770SS1 option 42 installed called  “HA Journal Performance ” the disk impact and performance impact of journaling is limited. As mentioned in my article A screen a story –  Db2 Symmetric Multiprocessing the HA journal Performance now also comes for free with your IBM i core license.

With the reuse deleted records option and the journaling in place you are ready to unleash the power of this new option to reorganize your files which contain deleted records. When doing so you will find for every record being moved it causes two entries to be written in the journal, one record for the delete action and another for the record being inserted. You now may think hang on a minute, but with this new TR the record was moved. The screens below will show you what is happening.

An example of a file with deleted records:

Starting the Reorganize while active:

Check the command used, by pressing the button “Show Command”:

Tip: Please do not run the command in an ACS SQL script because this requires you to leave RSS active. Run it by pressing the OK button in the background.

Follow it’s progress (please notice text in green):

When it’s done:

Check the journal to see what is being done under the covers:

With this new TR, now the records are moved resulting in pairs of DL and PX journal type entries. DL stands for “Record deleted”, PX for “Record added directly”. Also notice that each pair has exactly the same timestamp, the indication that the record was moved. Before this TR, there was a small time gap between every DL and PX entry, meaning that for a very short time the record was not there. This is now fixed which completely removes the need to plan down time when doing this.

When contacting IBM support to they explained to me that when using the option Allow Cancel (ALWCANCEL(*YES) this is the way it was implemented. If a new journal entry type “move” would have been added all software replication vendors would have had a problem. IBM i was designed to run your business and with the growing needs for 24/7 uptime, this is a huge step forward.

How to change someone’s PDM defaults

I have been asked this question twice this week:

Is there a way to change everyone’s PDM settings without them having to into their own settings and making the change themselves?

Both people want to change the “file” that contains these setting either with a SQL statement or they would write a program to do so.

I do not know where the PDM settings are stored. I assume they are in a file, or possibly even files. As the data is IBM’s data I would be very wary to change it as I have no idea of what the consequences are if I was to make a mistake.

Read more »

Rocket Software Names Puneet Kohli President of its Application … – Business Wire

WALTHAM, Mass.–(BUSINESS WIRE)–Rocket Software, a global technology leader that develops enterprise software for some of the world’s largest companies, today announced Puneet Kohli will serve as president of its application modernization business unit and Gary Gregory has been appointed as the company’s chief technology officer. Kohli and Gregory step into their new roles at Rocket Software as the company continues to innovate and invest in the technology necessary to support customers’ modernization efforts across infrastructure, data, and applications.

The Application Modernization business unit helps enterprises modernize their critical applications while increasing the value of their existing business logic and data. Kohli assumes the president role as the business unit is experiencing significant momentum, while Gregory steps into his new position as CTO. Kohli recently led the enhancements of Rocket® Modernization Suite for IBMi i, which empowers customers to extend and enhance the value of their IT systems. Reporting to Rocket Software’s President and CEO Milan Shetti, Kohli will work with the application team to further enable its customers to increase business agility and drive better customer engagement across applications. During Kohli’s 5-year tenure at Rocket Software, he has held multiple leadership roles leading the Quality, DevOps, and Product engineering teams and has been instrumental in standardizing Rocket Software’s Quality and DevOps toolchain.

“Rocket Software directly addresses the IT challenges mission-critical organizations face with solutions to help in their modernization journeys. Enabling our customers to better engage with and provide for their own customers is something I feel very passionate about,” said Kohli. “I am fortunate to be able to continue to build upon the success of the entire Applications business unit and advance our application modernization solutions.”

As Chief Technology Officer, Gregory will work closely with Shetti on the company’s strategic imperatives, ensuring Rocket Software continues to provide its customers with the holistic solutions to solve their most pressing IT challenges. Gregory will also look at opportunities to bridge the gap between the state of IT and how applications are written and maintained, driving innovations that reduce barriers to modernization by cutting costs and eliminating risk.

“The application market has exploded and evolved significantly in the decade since I joined Rocket Software and I’ve had the privilege of guiding many of our customers on their modernization journeys during that critical period,” said Gregory. “As I pass the baton to Puneet, I look forward to uncovering the next great technologies and opportunities to advance Rocket’s depth and breadth and continue to support our customers.”

“Both Puneet and Gary have been exemplary leaders and mentors to our Rocketeers, furthering the organization’s ethos: putting the people behind the software first,” said Shetti. “They each have played a significant role in the success of our application business unit and helping our customers build extraordinary applications. I look forward to seeing them both continue to exceed our business goals.”

For more information about Rocket Software’s leadership team, click here.

About Rocket Software

Rocket Software partners with the largest enterprises, in all industries, to solve their most complex IT challenges, across infrastructure, data, and applications — with solutions that simplify, not disrupt their modernization journey. Trusted by over 10,000 customers, Rocket Software helps enterprises modernize in place with a hybrid cloud strategy, so they don’t need to re-platform or build from the ground up. The company’s 2,600 global employees work with customers to accelerate and optimize their modernization journey while meeting evolving market needs. Rocket Software is a privately held U.S. corporation headquartered in the Boston area with centers of excellence strategically located throughout North America, Europe, Asia and Australia. Rocket Software is a portfolio company of Bain Capital Private Equity. Follow Rocket Software on LinkedIn and Twitter or visit www.RocketSoftware.com.

______________________

i IBM is a trademark of International Business Machines Corporation

Verified by MonsterInsights