What databases or storage mechanisms are used?

The product uses VSAM datasets to store checkpoint information. These datasets contain the necessary data and metadata to restore the application to a consistent state. Db2 and IMS databases are also directly supported for checkpointing.

What types of APIs does this product expose?

The product exposes a native API for integration with other z/OS applications. This API allows programs to query the status of checkpoints and initiate restart processes. Specific API endpoint patterns are not publicly documented.

What protocols does it use for communication?

The product supports communication via standard z/OS communication protocols, including inter-process communication (IPC) and potentially TCP/IP for distributed components.

What is the business value of using BMC AMI Application Restart and VSAM Recovery?

By providing automated checkpointing and restart capabilities, the product reduces the impact of batch job failures. This leads to improved service levels and reduced operational costs. It minimizes the need for manual intervention and data recovery efforts.

How does the product ensure data consistency?

The product ensures data consistency by capturing the state of VSAM datasets, IMS, and Db2 databases at each checkpoint. This minimizes data loss and corruption during restarts. It supports transactional integrity across multiple systems.

How does the product reduce downtime?

The product reduces the time required to recover from batch job failures, minimizing downtime and improving overall system availability. It automates the restart process, eliminating the need for manual intervention.

What authentication methods are supported?

The product supports authentication via z/OS security systems, such as RACF, ACF2, and Top Secret. It leverages these systems to verify user identities and control access to resources.

What access control model is used?

The product uses an access control model based on z/OS security profiles. These profiles define the permissions and privileges associated with users and groups. It supports role-based access control (RBAC) through the underlying z/OS security system.

What audit/logging capabilities exist?

The product integrates with z/OS audit logging facilities to record security-related events. These logs can be used to track user activity and identify potential security breaches. Specific events logged include checkpoint creation, restart initiation, and access control changes.

What administrative interfaces are available?

The product provides a command-line interface (CLI) and a web-based console for administrative tasks. The CLI allows administrators to manage checkpoint definitions and monitor restart processes. The web console provides a graphical interface for managing the product.

How is user management handled?

User management is handled through the underlying z/OS security system (RACF, ACF2, Top Secret). The product leverages these systems to authenticate users and control access to resources. Administrators can define user roles and permissions within these systems.

What monitoring/logging capabilities exist?

The product provides monitoring and logging capabilities through z/OS system logs and dedicated log files. These logs contain information about checkpoint creation, restart processes, and system events. Administrators can use these logs to monitor the health and performance of the product.

What are the main configuration parameters?

Key configuration parameters include checkpoint frequency, dataset selection, and database selection. These parameters are defined in configuration files and can be modified through the administrative interface. The checkpoint frequency determines how often checkpoints are created.

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

BMC AMI Application Restart and VSAM Recovery

Name: BMC AMI Application Restart and VSAM Recovery
Availability: InStock

BMC Active z/OS

Problem Analysis and Recovery Batch Db2

Vendor

BMC

Product Overview

BMC AMI Application Restart and VSAM Recovery is designed with a modular architecture comprising the Checkpoint Manager, Restart Controller, and VSAM Recovery module. The Checkpoint Manager handles the creation of checkpoints, storing data in VSAM datasets. The Restart Controller manages the restart process, coordinating with the VSAM Recovery module to ensure data integrity.

The product integrates with z/OS security systems (RACF, ACF2, Top Secret) for authentication and access control, utilizing security profiles and RBAC. Communication between components relies on standard z/OS communication protocols, including IPC. The product exposes a native API for integration with other z/OS applications.

Configuration is managed through configuration files and a web-based console. Key configuration parameters include checkpoint frequency and dataset selection. The product supports monitoring and logging through z/OS system logs.

Competing products include CA Restart and IBM Automatic Restart Manager. A key architectural difference is the product's tight integration with VSAM for recovery purposes. The product merges Application Restart Control for DB2, IMS, and VSAM into a single solution.

Frequently Asked Questions

What is the main function of BMC AMI Application Restart and VSAM Recovery?

BMC AMI Application Restart and VSAM Recovery provides checkpointing for batch applications, allowing restarts from the last checkpoint. It supports VSAM datasets, IMS, and Db2 databases without requiring application or JCL modifications. The product merges Application Restart Control for DB2, IMS, and VSAM.

How does BMC AMI Application Restart and VSAM Recovery integrate with existing batch processes?

The product integrates with existing batch processes without requiring changes to application code or JCL. It automatically detects and manages checkpointing opportunities based on the configuration.

How is checkpoint frequency configured?

Configuration files define the checkpoint frequency and conditions. These files specify which datasets, databases, and programs are monitored for checkpointing. The administrative interface allows modification of these parameters.

Related Products

View Details →

Administrative Assistant for DB2

Supported

by BMC

z/OS

Administrative Assistant for DB2 is a comprehensive suite designed to enhance the efficiency and reduce the complexity of DB2 database administration on z/OS. The product...

Tools and Utilities Administration

View Details →

ADS for CICS

Active

by Gary Bergman Associates

z/OS

ADS for CICS is a debugging tool designed for CICS applications, supporting languages such as PL/1, C/370, Assembler, and COBOL. It provides a command-line interface...

Problem Analysis and Recovery CICS

View Details →

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

Are You a Vendor? Claim Your Listing

BMC AMI Application Restart and VSAM Recovery

Product Overview

Frequently Asked Questions

What is the main function of BMC AMI Application Restart and VSAM Recovery?

How does BMC AMI Application Restart and VSAM Recovery integrate with existing batch processes?

How is checkpoint frequency configured?

What are the main system components?

What databases or storage mechanisms are used?

What types of APIs does this product expose?

What protocols does it use for communication?

What is the business value of using BMC AMI Application Restart and VSAM Recovery?

How does the product ensure data consistency?

How does the product reduce downtime?

What authentication methods are supported?

What access control model is used?

What audit/logging capabilities exist?

What administrative interfaces are available?

How is user management handled?

What monitoring/logging capabilities exist?

What are the main configuration parameters?

Related Products

More from BMC

Similar Products

Help Improve This Directory

Are You a Vendor? Claim Your Listing