Broadcom z/OS

Mainframe Restart Manager for IMS Modernization Guide

IMSProblem Analysis and RecoveryBatch

Mainframe Restart Manager for IMS is a ims product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

Mainframe Restart Manager for IMS automates the restart of failed IMS DLI batch and BMP jobs, ensuring correct checkpointing and data recovery.

Authentication methods supported include LDAP, RACF, ACF2, and Top Secret.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What is the primary function of Mainframe Restart Manager for IMS?

Mainframe Restart Manager for IMS automates the restart of failed IMS DLI batch and BMP jobs. It ensures proper checkpointing, automates data recovery, and supports batch backout of database updates after the last checkpoint for DLI batch jobs.

How does Mainframe Restart Manager for IMS integrate with IMS?

The product integrates with IMS to monitor job execution and intercepts relevant events, such as job failures. It uses information from the IMS control region and system logs to determine the appropriate restart point and recovery actions.

What are the main components of the architecture?

The system components include the Restart Controller, the Recovery Engine, and the Log Analyzer. The Restart Controller manages the overall restart process, the Recovery Engine performs the actual data recovery, and the Log Analyzer analyzes system logs to determine the appropriate recovery steps.

How is the system configured?

The product uses configuration files to define restart rules, recovery procedures, and database mappings. These files specify how the system should respond to different types of failures and which recovery actions should be taken.

Technical

What are the most common operations performed by users?

The most common operations include defining restart rules, initiating a restart, monitoring restart progress, and reviewing recovery logs. Users define rules based on job names, program names, or other criteria.

What is the command structure for basic operations?

The product uses a command-line interface (CLI) for administrative tasks. For example, to initiate a restart, the command might be `RESTART JOB(jobname)`. Configuration files are typically used to define restart rules and recovery procedures.

How does the product determine the restart point?

The product uses system logs and IMS control region data to determine the appropriate restart point. It analyzes log records to identify the last successful checkpoint and any subsequent database updates that need to be backed out.

What types of APIs does the product expose?

The product supports integration through a native API, allowing other applications to trigger restarts and monitor recovery progress. The API exposes methods for submitting restart requests, querying restart status, and retrieving recovery logs.

Business Value

How does Mainframe Restart Manager for IMS improve business value?

By automating the restart process, the product reduces the manual effort required to recover from job failures. This leads to faster recovery times and reduced downtime, minimizing the impact on business operations.

How does the product ensure data consistency?

The product ensures data consistency by backing out any uncommitted database updates after the last checkpoint. This prevents data corruption and ensures that the database is in a consistent state after a restart.

How does the product reduce the risk of human error?

The product reduces the risk of human error during the recovery process. By automating the restart and recovery steps, it eliminates the potential for mistakes that can occur when performing these tasks manually.

Security

What authentication methods are supported?

The product supports authentication via LDAP, RACF, ACF2, and Top Secret. These methods ensure that only authorized users can access the system and perform administrative tasks.

What access control model is used?

The product uses a role-based access control (RBAC) model. This allows administrators to assign specific roles to users, granting them only the permissions they need to perform their job functions.

What encryption is used and where?

The product encrypts sensitive data, such as passwords and connection strings, using AES-256 encryption. This protects the data from unauthorized access and ensures its confidentiality.

What audit/logging capabilities exist?

The product provides comprehensive audit logging capabilities. It logs all user activity, including login attempts, configuration changes, and restart requests. These logs can be used to track user behavior and identify potential security breaches.

Operations

What administrative interfaces are available?

The product provides a web-based console for monitoring system activity and managing restart rules. This console provides a centralized view of the system's status and allows administrators to quickly identify and resolve any issues.

How is user management handled?

User management is handled through the administrative interface. Administrators can add, modify, and delete user accounts, as well as assign roles and permissions.

What are the main configuration parameters?

The main configuration parameters include restart rules, recovery procedures, database mappings, and security settings. These parameters are defined in configuration files and can be modified through the administrative interface.

What monitoring/logging capabilities exist?

The product provides extensive monitoring and logging capabilities. It monitors system activity in real-time and logs all events to a central repository. These logs can be used to troubleshoot problems and track system performance.

Ready to Start Your Migration?

Download our comprehensive migration guide for Mainframe Restart Manager for IMS or calculate your ROI.

Calculate ROI