Topic: ibm-i
-
IBM i for a Linux/Windows agent: objects and libraries instead of files and paths
IBM i does not store a database file, a program and a menu as bytes in a directory tree; it stores typed objects inside libraries, found through a per-job library list, with CL commands built from a stable verb+noun pattern. This article maps those ideas onto what a Linux- or Windows-trained agent already knows.
-
IBM i jobs, subsystems, and job logs: WRKACTJOB, WRKSBS, DSPJOBLOG, and ending a job safely
IBM i work management organizes all activity into jobs running inside subsystems; WRKACTJOB, WRKSBS, DSPJOBLOG, and DSPMSG QSYSOPR are the read-only commands an agent reaches for first, and ENDJOB's *CNTRLD versus *IMMED option decides whether a job gets a chance to clean up before it dies.
-
IBM i security basics for administration: special authorities, object authority, QSECURITY, and QAUDJRN
IBM i access control rests on special authorities such as *ALLOBJ and *SECADM granted per user profile, object-level authorities checked with DSPOBJAUT/EDTOBJAUT, the QSECURITY system value that sets the enforcement level, and the QAUDJRN audit journal that records what happened — all administration and auditing, no exploitation.
-
Running IBM i CL commands from an SSH/PASE shell: system, qsh, and CCSID pitfalls
From an SSH session into IBM i PASE, the PASE-for-i system utility and the QSH/Qshell environment are the two supported ways to run CL commands and capture their output. Both convert between the job's CCSID and PASE's own encoding, which is where most first-time integration bugs come from.
-
IBM i backups: SAVLIB, SAVOBJ, SAVSYS, save files, and the GO SAVE menu
IBM i backups revolve around SAVLIB/SAVOBJ/SAVSYS writing to tape or to a save file created with CRTSAVF, and the GO SAVE menu options that wrap them into repeatable, optionally unattended, full or partial system saves.
-
Open source on IBM i: yum, bash as the default shell, and starting the SSH daemon
IBM's supported open-source stack for IBM i (Node.js, Python, git, bash, and more) installs as RPMs into /QOpenSys/pkgs through yum, ships bash as the recommended interactive shell, and depends on the SSH daemon being started explicitly with STRTCPSVR *SSHD before any of it is reachable remotely.
Machine-readable: JSON