WRKACTJOB is DSPACTJOB on steroids Every process that runs on an IBM i System is a #JOB. Using the WRKACTJOB command is pretty intuitive, since you are working with all the active jobs on the system you are literally asking your IBM i to show you all the active processes and allow you to view, […]
When Does a User Profile Become a Bottleneck?
A user profile can become a major system bottleneck for two reasons: performance issues, or availability issues. Dawn May explains here.
Common: COMING April 13: The Latest with the IBM i Platform
The IBM i team is always hard at work continuously enhancing the platform with requests and feedback from our amazing community. The team this year is focusing on hybrid cloud, security, high availability and disaster recovery, and even more open source options for developers. On Tuesday, April 13th, join COMMON and IBM i Chief Architect to learn about the latest with the IBM i platform. Steve will update the community on recent enhancements made to the platform and where we are at in the roadmap.
This webinar will be available on this page from 9:00 AM CDT on April 13, 2021
This content will not be available until 04/13/2021 at 4:00 PM (CEST)
(2) IBM FlashSystem HyperSwap Failover Live Demo
IBM i – Where business applications runs best
For a long period of time, many saw IBM i and its predecessors as old fashioned systems. The number one reason for this was the old school 5250/Green Screen user interface. Number two on that list was monolithic applications written in old school RPG language . I have some thoughts about this later in the article..
What is very modern though is such things as:
- In memory technologies (since 1970-s on IBM i)
- Object based operating system (Unique implementation in IBM i)
- Reliability, Availability, Security, Scalability, Serviceability – (It’s all there in IBM Power which is the server IBM i runs on)
- Isolation of programs (no, you don’t need containers for this. Similar functions built into IBM i since the time of AS/400)
- Operating system that was aimed for multiple users at the same time (IBM i was, Windows and Linux wasn’t)
- Branching instead of time sharing operating system (Unique to IBM i and why 80% of all customer are using just 1 or 2 CPU/Cores)
- Highly integrated relational database into the Operating System, not an application on top of it.. (Unique to IBM i)
- Single level storage… (The data is there for you, when you need it. No need to search for it..)
- Openness (IBM i is one of the most open system available on the market today)
Coming back to the reasons why IBM i is seen as un-modern. To start with, 5250 (Green Screens) is not always bad. They are sometimes actually very good. Not as primary way to interact with a business application, for sure. But just like with Windows or Linux, you need something more efficient than a GUI when it comes to do things “under the hood”. And compared to windows and linux terminal, 5250 kicks ass.
Secondly, monolithic applications is not the hottest thing these days. Sure, there are some draw backs with them. But there was also a reason why they were written like that a long time ago. Performance…
The good news though is that you can migrate your monolithic into REST based web services and still stay on the platform. And if you still are stuck with old school RPG, there are convert tools out there to make the code look just like Java or .NET for example..
Sure, there is still the thing called vendor locked in choosing IBM i. But you don’t get away from that which path you choose you follow. The only thing I can promise that this vendor is one you want to be locked in with..
The good thing though, is that IBM i allows you to create smaller chunks of programs just like on any other platforms. Rest based web services works very well today.
