Know where to look.
Review system status, sampled jobs in message wait (MSGW) or lock wait (LCKW), and QSYSOPR operator messages. See the recorded evidence that needs an operator’s attention.
Sampled MSGW / LCKW · QSYSOPR · System health
PowerSight AI · For IBM i
A clearer view of
your IBM i operations.
PowerSight AI by Clearward A/i brings jobs, operator messages and capacity evidence into one focused workspace. Start your morning review with a clearer picture of what needs attention, backed by stored IBM i data.
● IBM i expertise / Read-only monitoring / Customer control
The redesigned PowerSight AI workspace · illustrative data
Click the preview to enlarge
Focused on IBM iSystem i heritage. A modern perspective.
Read-only by designObserve operations with confidence.
Built for customer controlDesigned for deployment inside your organisation.
Available in the working prototype
Less searching.
More understanding.
From the first morning review to an unexpected job wait, bring the evidence your IBM i team needs into one place.
See beyond one moment.
Review ASP utilisation, sampled disk status and stored capacity history. Collection timestamps help your team understand how recent the evidence is.
ASP utilisation · Disk usage · History
Start with what matters.
Use a rule-based daily brief to review storage thresholds, sampled job waits, operator inquiries and output-queue findings. Follow the evidence and decide what to investigate next.
Daily brief · Findings · Supporting evidence
Clear about coverage
IBM i detail.
Practical operational context.
The prototype supports periodic review. It is not yet a continuous alerting service: the current test collector runs every four hours, and several checks return capped samples.
Beyond the headline metrics.
The collector includes job and output queues, subsystem state, scheduled jobs, system history, network and database connections, journals and basic configuration inventories. Collection does not mean every category has a dedicated dashboard or alert.
Coverage varies with services and permissions
Deeper checks, clearer priorities.
Roadmap priorities include critical-job checks, held or backed-up job queues, expected subsystem and TCP server availability, stopped writers, spool and job-log growth, and deeper CPU and memory analysis.
Planned · Requires implementation and validation
A broader operational picture.
Areas for validation include backup and HA health, QSYSMSG hardware events, PTF and OS maintenance, certificate and licence expiry, damaged objects, temporary storage and security posture.
Proposed coverage · No release dates committed
PTF inventory checks are coded but cannot be fully validated with the current public test account. Inventory collection alone does not establish patch compliance or expiry monitoring.
Your environment. Your control.
Built around the way
IBM i teams work.
PowerSight is being developed for organisations that want deeper visibility while keeping control of their systems, access and operational data.
The current prototype focuses on read-only monitoring and stored evidence. Enterprise rollout is in development.
Connect with purpose.
Collect supported IBM i operational information using a read-only connection and an appropriately authorised profile.
Bring the evidence together.
Retain snapshots, track collection results and organise system findings into an accessible operational view.
Keep your team in control.
Review the evidence and decide what needs action. Your operators remain responsible for changes to the system.
In development / IBM i knowledge & AI
The next step:
evidence you can question.
We are building towards an IBM i operations assistant that brings together system evidence, approved IBM documentation, your own runbooks and previous incidents. The aim: explain likely causes in the context of your applications, with sources your team can check.
This knowledge-assistant capability is planned; it is not part of the current monitoring prototype.
“Which job is holding up dispatch,
and what does our runbook say?”Planned investigation using customer-defined application context.
and what does our runbook say?”Planned investigation using customer-defined application context.
A few useful answers
Built for your
IBM i environment.
Is this for IBM i, iSeries and System i teams?
Yes. Our focus is organisations running IBM i, including teams who know their environment as iSeries, System i or AS/400. The prototype has been tested against IBM i 7.5 on PUB400. A wider supported-version matrix and minimum production release are not yet published. Available checks depend on the IBM i release, PTF level, services and profile permissions.
Will it change anything on my IBM i system?
The current connector is read-only. It collects operational evidence for review and does not make configuration changes or execute corrective actions.
Where is the platform intended to run?
The enterprise design is for deployment inside the customer organisation, with customer-controlled access and data. Deployment requirements and governance are still being developed.
How does PowerSight fit alongside existing monitoring?
Our focus is the daily work of IBM i operators: jobs, queues, messages and operational evidence. The planned assistant adds customer runbooks and application context to that evidence. PowerSight is not presented as a replacement for a complete enterprise monitoring suite; integrations with existing tools remain a future consideration.
What is available today?
A working prototype provides scheduled collection, a system selector and system registration, dedicated jobs, messages, storage and history views, and deterministic operational summaries. New connections require network access and validation in the customer environment. The knowledge assistant and broader enterprise capabilities remain in development.
Clearer insight. Confident operations.
PowerSight AI — IBM i operational intelligence from Clearward A/i.