Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Workspace IBM i
Categories System Management
Created by Guest
Created on Sep 18, 2026

Add Scriptable NTP Client Health Check Command Status for IBM i

IBM i currently provides commands and logs to configure and troubleshoot NTP, but it does not provide a simple, scriptable method to verify NTP client health and synchronization status.

Customers increasingly rely on automated monitoring platforms and health-check processes to validate system services. For NTP, administrators need a supported method to programmatically determine whether the NTP client is operational and successfully communicating with its configured servers without enabling logging or modifying the current NTP configuration.

Today, administrators must review NTP log files, traces, or job status information, which is difficult to consume from monitoring tools and does not provide a simple equivalent to commonly available commands on other operating systems.

Requested Enhancement

Provide a command, SQL service, or other scriptable interface that can be used to:

  • Verify that the NTP client is active.
  • Verify successful communication with configured NTP server(s).
  • Report the currently selected synchronization source/server.
  • Return the timestamp of the last successful synchronization.
  • Report synchronization state (synchronized, unsynchronized, unreachable, error, etc.).
  • Return a machine-readable status code suitable for automation and monitoring platforms.
  • Query NTP reachability without changing the system clock or existing CHGNTPA settings.
  • Report if the systems current time is within required time range of source NTP server.

Business Justification

This enhancement would simplify integration with enterprise monitoring and observability tools, reduce the need for log parsing, and provide IBM i administrators with a supported, low-overhead method to verify accurate time synchronization. Accurate NTP operation is critical for auditing, security, logging correlation, HA/DR environments, and distributed application workloads.

A capability comparable to the Linux command:

ntpdate -q <server>

or a query-only status interface similar to those available on other operating systems would significantly improve operational monitoring and automation on IBM i.

Example Use Cases

  • ScienceLogic and other monitoring platform integration.
  • Automated health checks and compliance validation.
  • Early detection of NTP server connectivity issues.
  • Verification of time synchronization after system IPLs, network changes, or maintenance activities.
  • Monitoring environments where NTP logging is intentionally disabled to avoid ongoing log growth and administrative overhead.
Idea priority Low