Turning on the audit journal and reading it with SQL
QAUDJRN is not on by default and cannot be enabled retroactively. The command to turn it on, the functions to query it, and the library they live in.
QAUDJRN is not on by default and cannot be enabled retroactively. The command to turn it on, the functions to query it, and the library they live in.
IBM has published an open source bridge between AI agents and Db2 for i. What it actually does, what it takes to run, and what authority it works with.
On IBM i there is no such thing as a project: there are libraries, full stop. Project4i adds one on top of Code for IBM i — free, MIT, inside VS Code. I looked at it closely and it won me over.
No revolution, but three or four things that take manual work off whoever administers the system. And one that concerns anybody sending mail from it.
The seven objections you hear in the meeting room, what is true in each, and where this platform is still the best choice. Including where it is not.
"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.