Database Management for IMS Modernization Guide
Database Management for IMS is a tools and utilities product by Broadcom. Explore technical details, modernization strategies, and migration paths below.
Product Overview
Database Management for IMS is a set of tools designed to manage and optimize IMS databases within a z/OS environment.
It is not a good fit if you do not use IMS databases or if you have very simple IMS environments that do not require advanced management tools.
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 does Database Management for IMS do?
Database Management for IMS is a suite of tools designed to manage and maintain IMS databases on z/OS systems. It provides functionalities for database analysis, copying, organization, and recovery, ensuring data integrity and availability. The tools help optimize database performance and reduce downtime.
Is this a system, application, or tool?
This is a tool set designed to enhance and manage IMS databases. It is not a complete system or application but rather a collection of utilities that address specific database management needs such as analysis, copying, organization, and recovery.
What types of organizations use this?
Organizations that rely on IMS databases for critical business applications on the z/OS platform benefit most from this product. These typically include large enterprises in industries such as banking, insurance, and government that require robust and reliable database management capabilities.
When should we consider Database Management for IMS?
A company should consider using Database Management for IMS when they need to improve the performance and availability of their IMS databases, streamline database maintenance tasks, and ensure data integrity. It is particularly useful when dealing with large and complex IMS database environments.
What are the alternatives to Database Management for IMS?
Alternatives include BMC AMI Database Management Solutions for IMS, IBM IMS Database Solution Pack, and other third-party IMS database management tools. Database Management for IMS distinguishes itself through its specific set of tools focused on analysis, copying, organization, and recovery.
Technical
What infrastructure is required?
Database Management for IMS runs on the z/OS platform and requires an IMS environment to be present. It operates within an LPAR and leverages z/OS subsystems for its functionalities. The tools extend and enhance the capabilities of existing IMS databases.
For mainframe products: Does this run in an LPAR?
Yes, this runs in an LPAR on z/OS. It is dependent on the z/OS operating system and requires the presence of an IMS subsystem. It integrates directly with IMS databases to provide its management capabilities.
What are the main system components?
The main system components include tools such as CA Database Analyzer for IMS, CA Database Copier for IMS, CA Database Organizer for IMS, and CA High Performance Recovery for IMS. These components communicate directly with the IMS database and utilize z/OS services for their operations.
What configuration files are used?
The product uses configuration files to define parameters for database analysis, copying, organization, and recovery processes. These files specify database names, dataset names, and other relevant options. The administrative interfaces are typically command-line based.
Business Value
What business problems does it solve?
Database Management for IMS helps organizations ensure the availability and integrity of their IMS databases, which are critical for many core business applications. By optimizing database performance and streamlining maintenance tasks, it reduces downtime and improves overall operational efficiency.
What would happen if an organization did NOT use this product?
If an organization did not use this product, they might experience increased downtime, data inconsistencies, and higher operational costs associated with managing IMS databases. They would need to rely on manual processes or less efficient tools, which can be error-prone and time-consuming.
What is the typical licensing model?
The typical licensing model is perpetual or subscription-based, depending on the vendor's offerings. The total cost of ownership includes licensing fees, implementation costs, training expenses, and ongoing maintenance. Vendor lock-in can be a consideration due to the specialized nature of IMS database management.
Security
What authentication methods are supported?
Database Management for IMS leverages the security features of the z/OS operating system and IMS subsystem. It supports authentication methods such as RACF, ACF2, and Top Secret. Access control is typically managed through an access control list (ACL) model.
How is user management handled?
The product integrates with z/OS security systems such as RACF, ACF2, and Top Secret to control access to IMS databases and related resources. It uses an access control list (ACL) model to define permissions for users and groups.
What audit/logging capabilities exist?
The product provides audit and logging capabilities to track database access, modifications, and administrative actions. These logs can be used for security monitoring and compliance purposes. Encryption is used to protect sensitive data both in transit and at rest.
Operations
What level of technical expertise is required to implement it?
Implementing Database Management for IMS requires expertise in z/OS, IMS, and database administration. Common implementation challenges include configuring the tools to work with existing IMS environments, ensuring compatibility with other software, and training staff on the new tools.
What ongoing operational requirements exist?
Ongoing operational requirements include monitoring database performance, performing regular backups, applying maintenance updates, and troubleshooting issues. This requires skilled personnel with expertise in IMS database management and z/OS operations.
What administrative interfaces are available?
Administrative interfaces are available through command-line interfaces (CLIs). User management is handled through integration with z/OS security systems like RACF, ACF2, or Top Secret. Monitoring and logging capabilities are provided to track database activities and system performance.
Ready to Start Your Migration?
Download our comprehensive migration guide for Database Management for IMS or calculate your ROI.