[[{“value”:”Founders of smaller IBM i and System z software vendors who are looking to sell their companies before they retire may want to check out a new venture called Izzi Software. In an interview with IT Jungle, the executives heading the startup explain that it has a mandate to spend millions of private equity dollars on acquiring midrange and mainframe ISVs that have solid products and businesses, but may not be big enough to attract M&A attention from bigger firms.
It’s no secret that the IBM i and System z communities tend toward the older side of the age …
The post Izzi Throws Retiring IBM i Software Company Founders A Lifeline appeared first on IT Jungle.”}]] Read More
Once upon a time : Silverlake Common Europe Luxembourg
[[{“value”:”During the Fort Knox project, a skunkworks project was started at IBM Rochester by engineers who believed that Fort Knox’s failure was inevitable. These engineers developed code which allowed System/36 applications to run on top of the System/38, and when Fort Knox was cancelled, this skunkworks project evolved into an official project to replace both the System/36 and System/38 with a single new hardware platform. The project became known as Silverlake (named for Silver Lake in Rochester, Minnesota) and officially began in December 1985. The Silverlake hardware was essentially an evolution of the System/38 which reused some of the technology developed for the Fort Knox project.
Silverlake’s goal was to deliver a replacement for the System/36 and System/38 in as short of a timeframe as possible, as the Fort Knox project had stalled new product development at Rochester, leaving IBM without a competitive midrange system. On its launch in 1986, the System/370-compatible IBM 9370 was positioned as IBM’s preferred midrange platform, but failed to achieve the commercial success IBM hoped it would have. Much like Silverlake, the 9370 also reused the co-processor developed during the Fort Knox project as its main processor, and the same SPD I/O bus which was derived from the Series/1 bus.
Source : Wikipedia …”}]] Read More
Talsco Weekly: Bridging the IBM i Skills Gap patrick staudacher
[[{“value”:”Welcome to another edition of Talsco Weekly IBM i Brief: 🔄 IBM i platform poised for major identity refresh. 🔨 Power9 support ends as Power11 era approaches. AI: 🌐From AI to GAI: How do we get from here to there. Career: 💼 Job seekers face evolving market challenges in 2025. Development: 🔄 RPG and Node.js
The post Talsco Weekly: Bridging the IBM i Skills Gap appeared first on IBM i (AS/400, RPG) Recruiting, Staffing & Consulting.”}]] Read More
Getting Started with VS Code for i: Install, Connect, Edit, Compile Seiden Group
IBM Champion Patrick Behr helps RDi and SEU users get started with the lightweight yet powerful VS Code for IBM i. In this video, he demonstrates how to install VS Code and its IBM i Development pack, connect to your IBM i server, and begin working with your RPG physical files. For more educational resources on VS Code for IBM i, visit https://www.seidengroup.com/2022/04/22/visual-studio-code-for-ibm-i-a-resource-guide/.From: Seiden Group Read More
View rendered display file in VS Code garciawork
[[{“value”:”I KNOW I had this working a while back, but it has been a while. I have the IBM i Renderer extension installed, and I have used it, but I cannot for the life of me remember HOW I got the rendered version of the display file to display. Does anyone know?
submitted by /u/garciawork[link][comments]”}]] Read More
