BMC AMI Application Restart and VSAM Recovery Modernization Guide

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.

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.

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.

The system components include the Checkpoint Manager, the Restart Controller, and the VSAM Recovery module. The Checkpoint Manager handles the creation of checkpoints. The Restart Controller manages the restart process. The VSAM Recovery module ensures data integrity during restarts.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.