IBM i is not an obsolete system: the objections one by one
The seven objections you actually hear in the meeting room, what is true in each, and the cases where this platform is still the best choice. Including the ones where it is not.
The seven objections you actually hear in the meeting room, what is true in each, and the cases where this platform is still the best choice. Including the ones where it is not.
How software is written, compiled and kept alive on this platform. For anyone arriving from other languages, and for anyone who has worked here for years without ever seeing the reasons written down.
How an IBM i is put together and why: objects, libraries, jobs, subsystems, security, spool, backups. The guide for anyone handed the machine without having seen one before.
"It will not print" is the most frequent report and the one with the fewest things to check: queue, writer, printer. In that order, and it takes two minutes.
The journal records every change to your data, with the time and the name of who made it. It exists for recovery, but day to day it mostly answers one question: who changed this record?
Calling an external API from an RPG program needs no extra software and no rewrite: it can be done in SQL, in a few lines. The available routes, and when each one makes sense.
Many installations run on users who hold *ALLOBJ because "otherwise it does not work". How you end up there, and how to get out without stopping anybody's work.
ACS is far more than a 5250 emulator, but most people who use it only ever open that one window. How to set it up properly, and what is behind the menu entries nobody clicks.
Saving is the easy part. This guide starts from the question that actually matters: if the machine does not come back tomorrow morning, what do you restart from, and how long does it take?