For mainframe products: Does this run in an LPAR?

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.

What infrastructure is required?

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.

What are the most common commands and configuration files?

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.

What protocols does it use for communication?

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.

What business problem does it solve?

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.

How does this product provide business value?

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.

What are the business considerations when purchasing this product?

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.

What security features does Availability Checker offer?

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.

How is access control handled?

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.

What audit/logging capabilities exist?

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.

How is this product typically deployed?

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.

What level of technical expertise is required to implement it?

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.

What are common implementation challenges?

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.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Availability Checker

Name: Availability Checker
Availability: InStock

Inside Products Active z/OS

Tools and Utilities Networks and Communication Monitor

Vendor

Inside Products

Product Overview

Availability Checker is a z/OS-based tool designed for automated monitoring of TCP/IP connected hosts. Its architecture comprises several key components: a monitoring engine responsible for sending ping requests and collecting response times; a data storage component, likely a VSAM dataset or a DB2 table, for maintaining historical data; a reporting engine for generating reports on unavailable resources; and an administrative interface for configuring monitoring parameters and managing users. The monitoring engine uses standard TCP/IP protocols, primarily ICMP, to check host availability.

It communicates with the data storage component to persist response time data. The reporting engine retrieves data from the data storage component and generates reports in various formats, such as PDF or CSV. The administrative interface, which could be a TSO/ISPF panel or a web-based console, allows administrators to define hosts to monitor, set ping intervals, configure reporting parameters, and manage user access.

The tool integrates with z/OS security systems, such as RACF or ACF2, for authentication and authorization. It may also expose APIs, such as REST APIs, for integration with other monitoring tools and systems management platforms. Understanding these architectural details is crucial for designing effective integration strategies and ensuring the tool's scalability and reliability.

Frequently Asked Questions

What does Availability Checker do?

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.

Is this a system, application, or tool?

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.

What types of organizations use this?

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.

When should we consider Availability Checker?

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.

What are the alternatives to Availability Checker?

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.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Share Your Product Experience

Availability Checker

Product Overview

Frequently Asked Questions

What does Availability Checker do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider Availability Checker?

What are the alternatives to Availability Checker?

For mainframe products: Does this run in an LPAR?

What infrastructure is required?

What are the most common commands and configuration files?

What protocols does it use for communication?

What business problem does it solve?

How does this product provide business value?

What are the business considerations when purchasing this product?

What security features does Availability Checker offer?

How is access control handled?

What audit/logging capabilities exist?

How is this product typically deployed?

What level of technical expertise is required to implement it?

What are common implementation challenges?

Related Products

More from Inside Products

Application Checker

Connection Log

Early Warning System

EE Problem Finder

Inside the Stack

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta doc|z plus

_beta doc|z transform

(E)JES

Help Improve This Directory

Are You a Vendor? Claim Your Listing