Trend Watch: Cloud Computing
This is the first in a multi-part series with a focus on trends that are interesting and important, from cloud computing to digital transformation, all with a clear focus on enterprise computing. In this post, I jump into cloud computing and discuss the subject at this point-in-time.
AIX and NTP
By default AIX uses NTPv3. This probably works fine for an internal-only situation (I hope), but for a server that also talks with the "outside," I recall that NTP shows up fairly frequently in CVE messages.
Open Source on i: Introduction and Thoughts
The Open Your i blog explores the thrilling journey of the growth of open source on IBM i.
February 2017 IBM i Announcements
Once again it is announcement time, with IBM i 7.3 Technology Refresh 2 and IBM i 7.2 Technology Refresh 6 being announced. As is somewhat typical for these Technology Refresh announcements, the content for both releases is quite similar. Steve Will’s blog “Announcing IBM i 7.3 TR2 & 7.2 TR6”
reviews the announcement overall. I want to focus on a few enhancements that will make an IBM i administrator’s life a little easier.
The Year Ahead
In our previous blog, we talked about the things that we regarded as the highlights of 2016. As you might expect, since Application Development (AD) is our primary focus, the majority of things on our prediction/wish list for 2017 are also firmly rooted in that area.
Announcing IBM i 7.3 TR2 & 7.2 TR6
This might come as a bit of a surprise, but it’s announce day again. I know, I know–it doesn’t seem all that long ago that we announced IBM i 7.3 Technology Refresh 1. And it wasn’t! But this year’s “spring” announcement of IBM i 7.3 TR2 (and the accompanying 7.2 TR6) comes a little earlier than spring. (Maybe we’re all just hoping for a short winter!) Whatever the reason, it’s time again for me to give you an overview of the announcement.
DB2 12 Plan Stability with APREUSESOURCE
During a migration, DB2 12 will automatically rebind any package bound in DB2 9 and earlier versions. The automatic rebind results in a new package, while the previous package copy is automatically discarded. However, to ensure plan stability, a BIND should be done manually, because auto rebind won't copy the original package to the previous one. So if a regression in access path occurs, the REBIND SWITCH option is not available.
New Servers Designed for Smaller Environments
In my consulting work, I see a number of customers with small machines running critical workloads that don't incorporate virtualization. Because these workloads aren't necessarily memory- or CPU-intensive, these customers see no need to set up multiple LPARs. They just want a stand-alone system.