Availability Checker Modernization Guide

Availability Checker is a z/OS-based tool that automatically pings TCP/IP connected hosts on a regular schedule. It tracks response times and generates reports about unavailable resources.

This is a tool designed to monitor network availability. It is not a system or an application in the traditional sense, but rather a utility that provides specific monitoring functionality.

Organizations that rely on z/OS and need to ensure the continuous availability of TCP/IP connected hosts would benefit from this product. This includes enterprises in industries like banking, finance, and insurance.

Consider using Availability Checker when you need automated monitoring of TCP/IP hosts from a z/OS environment. It is especially useful when you need to maintain a historical record of response times and generate reports on unavailable resources.

Alternatives include general-purpose network monitoring tools like Nagios, Zabbix, or SolarWinds. However, these may not be specifically designed for z/OS or offer the same level of integration with the z/OS environment.

Availability Checker runs on the z/OS platform. It is z/OS dependent and likely runs within an LPAR. It may require specific z/OS subsystems to be active.

The product requires a functioning TCP/IP stack on z/OS. It needs to be able to send and receive TCP/IP packets to the hosts being monitored. It also needs sufficient storage to maintain the historical record of response times.

The exact commands and syntax would be specific to the product. However, common operations would include defining hosts to monitor, setting ping intervals, and generating reports. Configuration files would likely be used to define these parameters.

The product likely uses standard TCP/IP protocols for communication, such as ICMP (ping) to check host availability. It may also use TCP or UDP for more advanced monitoring functions.

Availability Checker solves the business problem of ensuring the availability of critical TCP/IP connected resources. Without it, organizations may experience unexpected outages and service disruptions, leading to financial losses and reputational damage.

The product provides value by automating the monitoring process, reducing the need for manual checks. It also provides historical data and reporting capabilities, allowing organizations to identify trends and proactively address potential issues.

Organizations should consider the total cost of ownership, including licensing, implementation, and ongoing operational costs. Vendor lock-in is a consideration, as migrating from one monitoring solution to another can be complex.

The product's security features would depend on its specific implementation. However, it should support authentication to prevent unauthorized access to monitoring data and configuration settings. It may also encrypt sensitive data in transit and at rest.

Access control would likely be based on roles, allowing administrators to grant different levels of access to different users. Audit logging should be in place to track user activity and changes to the system.

The product should provide audit logging capabilities to track user activity, configuration changes, and any security-related events. This information can be used to identify and investigate potential security breaches.

Deployment typically involves installing the product on a z/OS LPAR and configuring it to monitor the desired TCP/IP hosts. Ongoing operations include monitoring the product's performance, maintaining the configuration, and reviewing reports.

Implementing and operating this product requires z/OS systems programming skills, as well as networking knowledge. Staffing requirements depend on the size and complexity of the environment being monitored.

Common implementation challenges include configuring the product to correctly identify and monitor the desired hosts, ensuring that the product has sufficient resources to operate efficiently, and integrating the product with existing monitoring systems.