AS400 monitoring means monitoring IBM i systems, which XorMon lists as IBM i (AS400). XorMon, open source under GPL v3, runs a C-language OS agent on each IBM i partition that collects CPU, jobs, memory pools, ASP storage, disk and LAN data every minute and sends it to the XorMon server.

What does XorMon monitor on IBM i (AS400)?

XorMon graphs CPU usage, the top jobs by CPU and IO, disks, jobs and threads, memory pools with their faults and pages, ASP capacity and performance, LAN traffic and multipath status.

Each metric is graphed per system, per memory pool or per ASP. Per system: CPU %, CPU cores and IO/sec of the top jobs, disk busy % and disk IO/sec, jobs, active jobs and active threads, LAN MB/sec, packets/sec and discarded packets/sec, and multipath status, which needs no configuration on IBM i. Per pool: pool size, current threads, DB and non-DB faults/sec, and DB and non-DB pages/sec. Per ASP: free, used and used % capacity, data throughput and IO/sec. ASP total latency, service time and wait time cover all ASPs, iASPs included, in the Enterprise edition (see ASP latency monitoring). LPAR2RRD and STOR2RRD are legacy tools. XorMon is their full-stack successor, and all new development goes into XorMon. Per the Migration page, LPAR2RRD and STOR2RRD can run alongside XorMon on the same devices during the move, device definitions can be imported, and the XorMon license is covered, at no extra fee, by the existing support contract of enterprise edition customers of those tools for the same environment size. Performance history is not migrated.

Sources: Feature matrix, ASP latency monitoring, updated 2026-05-04, Multipath, updated 2026-10-22, About Xorux, and Migration, updated 2026-07-26.

Which IBM i commands do the XorMon graphs match?

Most graphs are mapped to the native IBM i command that shows the same data: WRKACTJOB for job CPU % and IO, WRKSYSSTS for jobs, pool size, faults and pages, WRKDSKSTS for ASP throughput and IO/sec, and DSPASPBRM for ASP capacity.

The WRKACTJOB graph uses the percent metric of the default WRKACTJOB screen: 100% equals the CPU entitlement of the LPAR, and the value can go above 100% when the number of configured logical processors is higher than the entitlement. Instead of graphing every running process, the agent selects the 10 processes with the highest CPU usage in each sampling period. CPUTOP shows the CPU time of these jobs converted to CPU cores, IOTOP shows their IO/sec, and a click on the color square of a job opens a graph of that job alone.

Sources: WRKACTJOB implementation, updated 2026-06-19, and Feature matrix.

How does the XorMon agent collect data from IBM i?

The agent is installed from a save file on IBM i V6R1 or later, runs under a dedicated LPAR2RRD user profile and sends its data over TCP to the XorMon server on port 8162. Connections are initiated from the IBM i side.

The save file LPAR2RRD.savf is transferred by FTP and restored with RSTLIB. A separate agent version is provided for releases older than V7R3. The LPAR2RRD user needs *USE authority on the QSYS/QPMLPMGT service program and, on V7R6 and higher, the QIBM_IOSYSCFG_VIEW function usage. The agent starts as the RTV_SYSSTS command or as an autostart job entry in the LPAR2RRD subsystem, and its job log shows "connection Established" once data has been sent to the XorMon server.

Source: IBM i agent, updated 2026-09-24.

How does XorMon alert on IBM i problems?

Performance alerts with a threshold can be set on any metric the tool collects, and the IBM i OS agent is also supported by ping alerting.

In XorMon, event alerting sends an alert when a device turns red in the global health status dashboard, and a clear alert when it turns green again. Prediction alerting warns when a metric is predicted to reach its threshold within a set number of days. Alerts are sent by email, SNMP trap or one of the other alerting integrations.

Sources: Alerting, updated 2026-10-13, Ping alerting, updated 2026-09-17, and Alerting integrations, updated 2026-10-22.

Key points

• Monitors IBM i (AS400) with a C-language OS agent for IBM i V6R1 and later.
• Collects data every minute and sends it to the XorMon server over TCP port 8162.
• Graphs CPU, top 10 jobs by CPU, disks, jobs and LAN per system, memory pools per pool, and capacity and IO per ASP.
• Graphs match the IBM i commands WRKACTJOB, WRKSYSSTS, WRKDSKSTS and DSPASPBRM.
• Threshold alerts on collected metrics, ping alerting, free open source license (GPL v3).

To compare XorMon with Site24x7 for IBM i and AS400 monitoring, read the Site24x7 comparison.

IBM i agent and monitoring scope

The OS agent is written in the C language.
It is running on IBM i operating system where it regularly (every minute) collects performance data and transfers it every 20 minutes to the XorMon server where data is saved and graphically presented.

Monitoring scope

New to the terms used on this page? See the glossary entry for IBM i (AS400).

Last updated: 2026-11-07