Monitor IBM i systems (AS400)
Monitor an IBM i (AS400) live: CPU, disks, jobs waiting for a reply, subsystems, operator messages, backups, PTFs, security, and its security events in the SIEM.
In Infrastructure → IBM i systems you monitor your IBM i (AS400) systems live, without installing a ARGUNIS agent on them: ARGUNIS reads the system's own read-only views every few minutes.
Before you begin
On the IBM i, install the Mapepire server (IBM open source, IBM i 7.4 or later) and create the read-only profile: on this page, Read-only user script provides the commands.
Allow port 8076 only from the host that will run the checks (the ARGUNIS cloud, the link, an agent, or a monitoring probe).
Create the profile's credential in Settings → Credentials (type "Database", engine "IBM i").
If you can't install Mapepire, ARGUNIS uses the JTOpen fallback (IBM's Java driver) through the IBM i database server (port 8471). In the cloud and on the probe it is already included; on an agent, the administrator installs it with argunis-agent install-jtopen (it requires Java 11 or later). The page tells you when it connected through the fallback.
Add a system
Click Add IBM i system.
Enter the name, the IBM i address and, if it isn't 8076, the Mapepire port.
Choose the credential, where it's checked from, the interval, and the group.
Adjust the thresholds (CPU, ASP space, job queues, backup) and what to alert on.
Click Add and check.
Each system counts as one server in your plan.
What the page shows
Section | What you see | Alarm |
|---|---|---|
CPU and jobs | CPU, active jobs, and jobs in the system | CPU above the threshold |
ASP (disks) | Used space of each ASP | Space above the threshold (IBM i stops if the ASP fills up) |
Jobs in MSGW | Jobs waiting for a reply to a message | Jobs in MSGW in two consecutive readings |
Subsystems | Status of each subsystem | QBATCH, QINTER, QCMN, QSPL, QUSRWRK, QSERVER, QSYSWRK, or QHTTPSVR stopped (critical) |
Job queues | Held queues or queues with waiting jobs | Held queue with jobs or with more than the threshold waiting |
Operator messages | Unanswered QSYSOPR inquiries and messages with severity 80 or higher (24 h) | There is at least one unattended |
PTFs and backups | PTF groups and their status; libraries never backed up | Groups with problems or pending; last backup older than the threshold |
Security | Security level (QSECURITY) and profiles with *ALLOBJ | QSECURITY lower than 40 |
Security events in the SIEM
Each reading brings to the SIEM what is new in the audit journal (QAUDJRN: failed sign-ons, profile changes, authority failures and changes, system value changes) and in the system history. They arrive as the source "IBM i · system name", included from the start. For the audit journal, the profile needs the *AUDIT special authority and auditing enabled on the system (the script explains it).