Automatically Restart Failed Monitors

IT Infrastructure - Other
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

iSeries Navigator provides iSeries users with a broad suite of functions. In V5R2, iSeries Navigator includes a new feature that automatically restarts your failed monitors. In this article, I'll explain how the new monitor restart feature works and what it means to your management environment. I'll start with a brief scenario to give an idea of what monitor restart does.


You are using system monitors to notify you of peak CPU usage times so that you can adjust your workloads and optimize your computing resource. Your system monitor is configured to notify you and take some actions when usage thresholds are met.. The problem is that every night your iSeries systems get backed up and then restarted, but your CPU utilization monitor is not reactivated. This creates a monitoring gap from 1:00 a.m. to 8:30 a.m., when you arrive at work and restart your monitors. Your systems consist of one V5R2 iSeries, one V5R1 iSeries, and two V4R5 iSeries. You are interested in monitoring all three systems.

By making the V5R2 iSeries your central system for the CPU utilization monitor, you can exploit the monitor restart feature. This way, as nightly backups and restarts complete and your iSeries servers start up, your CPU utilization monitor that was running before the restart took place will begin running again. The monitor will behave as though you started it yourself and attempt to connect to its various endpoints. If the endpoints have not yet recovered from the restart, no problem. The CPU utilization monitor will continue attempting to start on those endpoints until they come back online. The monitoring gap is eliminated!

In this scenario, you're utilizing automatically started monitors to assure that no CPU utilization thresholds are missed so that proper notification and actions are taken even though you are not around to restart your monitor.

The "Automatically Restart Failed Monitors" Feature

The monitor restart feature of V5R2 is intended to keep iSeries Navigator monitors running--or at least attempting to run in spite of iSeries restarts, system outages, LAN outages, and other assorted headaches that occasionally plague system administrators. The cool news for this feature is that although it is implemented on V5R2, it effectively restarts monitors managed by V5R2 on endpoint systems for any past release. No PTFs are necessary to make it work. Now, that's playing nice!

In simple terms, the "Automatically restart failed monitors" feature does exactly that; it keeps your iSeries Navigator monitors running or attempting to run in spite of various forms of interruptions. You have a backup plan that puts your iSeries in restricted mode? When the iSeries comes out of restricted state and Management Central servers start up, the monitors that were running when the system went to restricted state will start up again without your intervention. You have a few endpoints with monitors running to them and you suffer a LAN outage? When the LAN becomes active again, those endpoints will reconnect, and the monitors will go merrily on their way.

Configuring for Monitor Restart

To set your monitors to be restarted automatically, select Properties from the Management
Central context menu, as shown in Figure 1. Notice that what you're setting is a global property that is associated with your central system, so your settings will affect all the monitors managed by that central system. Select the Connections tab to reach the configurable properties of monitor restart. Checking the box for "Automatically restart monitors on failed systems" enables monitor restart. Once you've done that, you must stop and restart the Management Central servers for monitor restart to take effect. To start or stop those servers, in iSeries Navigator, go to Connection -> Network -> Servers -> TCP/IP Servers. Then, select Management Central, then Stop, then Start.

Figure 1: From the Management Central context menu you can set your monitors to be restarted automatically. (Click images to enlarge.)

The Connection tab includes fields for "How long to attempt restart" and "How often to attempt restart." The default property for monitor restart is to attempt to restart every five minutes for 180 minutes. You can change those retry attempt cycles to whatever intervals you desire. In both fields, the possible intervals are limited by the interface to a maximum value of 9,999 minutes and a minimum value of one minute. The interface also requires that the value for "How often to attempt restart " cannot be greater than the value for "How long to attempt restart."  
Monitors are candidates for restart if they are running. Running monitors are those with an overall status of Starting, Started, Started on x of y, Triggered, or Failed on x of y. Monitors that have an overall status of Failed or Stopped do not qualify.

Central System vs. Endpoint System

It's very important that you understand that restarting monitors is a function of the central system. Because restart is a central system behavior, endpoints that are V5R1 and earlier can exploit restart behavior. In other words, if you have a V5R2 central system and V4R5 or V5R1 endpoint systems, monitors that are managed from the V5R2 central system to those previous release endpoint systems will take advantage of monitor restart. The restart feature affects monitors in two distinct ways:
1. Central system restart
2. Endpoint system restart or reconnect 

Restart of the V5R2 Central System

When starting the Management Central servers on the central system (maybe as the result of an iSeries restart, for example), all the monitors that were managed and running from that central system when the iSeries restart began will be started again or reconnected when the Management Central servers start back up. This behavior is independent of the release of any endpoints your monitors may be managed on and is driven entirely by the central system where the monitors are created and managed. Monitors that are restart candidates and managed on that central system will be activated at startup, and the monitors reporting from various endpoints will reconnect and begin reporting data again.

Restart of the Endpoint System

In the second restart behavior, an endpoint has gone down or offline (for whatever reason--maybe as the result of a LAN malfunction or the endpoint getting restarted). When the V5R2 central system loses contact with that endpoint, the restart feature kicks in. Every five minutes (or whatever value you've chosen), the monitor that is managed by the central system will try to reconnect with the endpoint it has lost contact with. It will continue these restart (connect) attempts for however long you've specified.

Implementation Details

OK, now that you know the basics, I'll discuss some of the side effects of automatically restarting failed monitors. Earlier, I mentioned starting a "running" monitor. A running monitor refers to the overall status of a monitor--that is, the status that you see in the details panel of iSeries Navigator (on the right side). In the session pictured in Figure 2, notice that one monitor has a status of Failed, another has a status of Failed on 1 of 3 systems, and another has a triggered status. The running monitors here are the triggered monitor and the monitor that shows Failed on 1 of 3 systems. If this central system is stopped and then restarted, those two monitors will restart. The idea here is to only start monitors that are running when the central system ends. If you right-click on "Monitor that restarts" (highlighted in the figure), the detailed status will tell you something about why the monitor is not started on the other two systems. The information in those detailed status reports is not considered when automatically restarting monitors.
Figure 2: iSeries Navigator will reveal which monitors have restarted and explain why the others haven't.

Special Considerations

Any V5R2 iSeries--or even multiple V5R2 iSeries--can be designated as a central system. The choice of central system is merely a statement of which iSeries you have chosen to create and manage an iSeries Navigator monitor or task. When utilizing the automatic monitor restart feature, keep in mind that you must turn it off when you no longer need it. Properly managing this feature will help prevent unwanted restarts of monitors you no longer intend to use. This may not seem like a big deal, but some monitors, based upon the number of metrics and collection interval, can consume CPU or even disk space. You probably do not want them automatically restarting when you are not aware of it. You turn monitor restart off the same way you turned it on, through the iSeries Navigator interface. Simply uncheck "Automatically restart monitors on failed systems." Remember, you will need to restart the Management Central servers on that iSeries for the change to take effect.

There is a behavior of restart worth mentioning at this point. Restart is intended to act only on monitors that are running or were known to be running when an interruption like those described occurred. Therefore, if the overall state of a monitor is Failed on 1 of 2 for example, that monitor is running. Restart will take effect for the configured amount of time on the single endpoint that is failed. On the other hand, if the monitor has an overall status of Failed, this monitor is not running and restart will have no effect on it. This behavior allows failed monitors to exist on the central system and not be restarted. Unfortunately, there are conditions under which you may want a failed monitor to restart. As an example, suppose you have a central system where all your monitors are created, managed, and viewed through iSeries Navigator. You have an endpoint system--for example, an HTTP server--where there is a job whose log you are monitoring. The monitor for the endpoint is created on and managed from a separate central system. If you experience a LAN outage between the central system and the endpoint or you restart the servers on the endpoint, the status of the HTTP monitor will go to an overall status of Failed. Notice that a running status like Failed on 1 of 2 will occur if this monitor is assigned to multiple endpoints. Since this monitor is assigned to a single endpoint that does not reside on the central server, the overall Failed status prevents automatic restart for that monitor. Alternatively, if the endpoint system is at V5R2, you can manage that monitor directly on the endpoint system that runs the job you are monitoring. With the monitor created and managed on that endpoint system, restart will take the central system behavior and not be affected by the single endpoint system failure. This may be an inconvenience to the system administrator who wants to manage all his endpoints from a single central system, but it does allow exploiting monitor restart.

In this article, I have described how the monitor restart feature of iSeries Navigator works. I have tried to give some idea of its limitations and its overall usefulness. You can find out more about iSeries Navigator by going to the iSeries Navigator Web site.

Tom Brekke is staff software engineer at IBM Rochester working on iSeries Navigator and related projects. He can be reached by email at This email address is being protected from spambots. You need JavaScript enabled to view it..



Support MC Press Online





  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things

    Read Node.js for Enterprise IBM i Modernization Now!


  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!


  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.


  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline



  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.


  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact


  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using as a pre-built development environment



  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.



  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.



  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails


  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.



  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.