RE: IBM i Monitoring utility

Don Brown via MIDRANGE-L <[email protected]> Sun, 28 Jun 2026 00:11:27 +0000
Newsgroups gmane.comp.hardware.ibm.midrange
Message-ID <SYBP282MB35585566B421654057737DC6E9E92@SYBP282MB3558.AUSP282.PROD.OUTLOOK.COM>
   Hi,

   I can't see in the history what ODBC tools you are using to do the
   monitoring or how the monitor is checking the connection.

   But if that is proving unreliable or providing false positives sometimes
   perhaps you need to go the other way and have the LPAR provide a heartbeat
   on whatever frequency you are wanting to check. The heartbeat could be a
   timestamp written to a file either on the lpar or on an external device or
   a data queue or a web service call or whatever you like.

   But if the problem is the monitoring machine has a network problem and
   that is the only monitoring tool then that is a problem!

   Cheers
   Don

    

   Don Brown

   Senior Consultant
    
   [1]OneTeam IT Pty Ltd
   P: 1300 088 400

   -----Original Message-----
   From: MIDRANGE-L <[email protected]> On Behalf Of
   Laurence Chiu
   Sent: Saturday, 27 June 2026 8:46 PM
   To: Midrange Systems Technical Discussion <[email protected]>
   Subject: Re: IBM i Monitoring utility

   I am trying to distinguish between the host is down or lost the connection
   to the host. In the latter situation, our monitoring tool will post an
   alert the host is down, That eventually ends up as a SMS message to the
   help desk who call the techs. If they then logon and see the host is not
   down, they are not happy :-(

   I did some research on this and it seems we could use the HMC. It has a
   REST API which we can ingest from our monitoring tool and feed the data
   into the same date pipeline we now get from ingesting QSYSPOPR. It doesn't
   look too hard but this was not an options our team that manages our
   corporate wide monitoring infrastructure since they don't know anything
   about IBMi!

   On Fri, Jun 26, 2026 at 10:04 AM Laurence Chiu <[email protected]> wrote:

   > On a similar note does anybody have any thoughts on tools that can
   > monitor the health of an IBMi LPAR when the health monitoring is
   > performed from an external agent using ODBC? If the ODBC connection
   > fails, or the network connection fails, the tool cannot detect the
   > difference and will report host is down. This is not entirely
   > satisfactory since it can generate false alerts. One piece of advice
   > I saw was to leverage the HMC and use API calls to the HMC to detect
   > the host status which is likely to be more robust. Has anybody have an
   experience with this?
   >
   > On Fri, Jun 26, 2026 at 8:36 AM Bryan Dietz <[email protected]> wrote:
   >
   >> there are some example out on the IBM techdocs, and there are more in
   >> a source file in QMGTOOLS.
   >>
   >> passing along,
   >> Bryan
   >>
   >>
   >> --
   >> This is the Midrange Systems Technical Discussion (MIDRANGE-L)
   >> mailing list To post a message email: [email protected]
   >> To subscribe, unsubscribe, or change list options,
   >> visit: [2]https://lists.midrange.com/mailman/listinfo/midrange-l
   >> or email: [email protected]
   >> Before posting, please take a moment to review the archives at
   >> [3]https://archive.midrange.com/midrange-l.
   >>
   >> Please contact [email protected] for any subscription
   >> related questions.
   >>
   >>
   --
   This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
   list To post a message email: [email protected] To subscribe,
   unsubscribe, or change list options,
   visit: [4]https://lists.midrange.com/mailman/listinfo/midrange-l
   or email: [email protected]
   Before posting, please take a moment to review the archives at
   [5]https://archive.midrange.com/midrange-l.

   Please contact [email protected] for any subscription related
   questions.

   --
   Message protected by MailGuard: e-mail anti-virus, anti-spam and content
   filtering.
   [6]https://www.mailguard.com.au

References

   Visible links
   1. https://www.oneteamit.com.au/
   2. https://lists.midrange.com/mailman/listinfo/midrange-l
   3. https://archive.midrange.com/midrange-l.
   4. https://lists.midrange.com/mailman/listinfo/midrange-l
   5. https://archive.midrange.com/midrange-l.
   6. https://www.mailguard.com.au/
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: [email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact [email protected] for any subscription related questions.