For many years, IBM i has provided a means for the system to detect and report problems. What started as hardware problem detection and reporting via a product called Service Director (SD), has grown to include software problem reporting, with inventory and performance data sent using Electronic Service Agent (ESA), which is integrated into the operating system.
(more…)As a member of the PASE development team, inquiries from the IBM i community regarding PASE often come to me. In one such recent email, the following phrase caught my eye:
To most, including me, it (PASE) is just “the other side I rarely use.”
E-x-a-c-t-l-y!
(more…)A positive out-of-box experience for clients deploying IBM i has been a key point of emphasis from day one, and will continue to be in the future. Much is owed to the integration of the operating system with key functions, such as security and database, and with IBM middleware like WebSphere Application Server. We package and test everything together as a fully integrated stack to ensure the quick and easy deployment of an IBM i system or partition.
(more…)When the System/38 was being architected, it was recognized that underlying hardware technology was subject to unpredictable change. While it didn’t take a crystal ball to understand that change would be inevitable, having one to forecast the future of storage technology sure would have been nice. But as we all know, there is no crystal ball. This reality led to the development of Single Level Store. A key feature of Single Level Storage (SLS) architecture is that it insulates the upper-level code from the specifics of the storage technology it uses. Along with the Technology Independent Machine Interface, TIMI, SLS is a fundamental element of the design that has allowed IBM i to continue to take advantage of new capabilities seamlessly.
(more…)