IBM z/OS

IMS Image Copy Extensions Modernization Guide

Tools and UtilitiesIMSBackup and Restore

IMS Image Copy Extensions is a tools and utilities product by IBM. Explore technical details, modernization strategies, and migration paths below.

Product Overview

IMS Image Copy Extensions was a utility designed for organizations using IMS databases on z/OS.

Additionally, it allowed multiple image copy datasets to be placed on a single tape volume, optimizing tape usage.

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 did IMS Image Copy Extensions do?

IMS Image Copy Extensions provided compression of IMS database image copies and other features such as checking database pointers during image copy, placing multiple image copy datasets on a single tape volume, and database group processing.

Was IMS Image Copy Extensions a system, application, or tool?

IMS Image Copy Extensions was a tool designed to enhance the image copy process for IMS databases. It was not a complete system or application, but rather a utility to improve backup and recovery operations.

What types of organizations used IMS Image Copy Extensions?

Organizations using IMS databases on z/OS systems, particularly those with large databases and a need for efficient backup and recovery processes, could have benefited from IMS Image Copy Extensions.

When should a company have considered using IMS Image Copy Extensions?

Companies should have considered using IMS Image Copy Extensions when they needed to optimize their IMS database backup and recovery procedures, reduce storage space for image copies through compression, and improve the overall efficiency of their data management processes.

What were the alternatives to IMS Image Copy Extensions?

Alternatives to IMS Image Copy Extensions include IMS High Performance Image Copy, which eventually incorporated its features, and other third-party backup and recovery tools designed for IMS databases on z/OS.

Technical

What infrastructure was required for IMS Image Copy Extensions?

IMS Image Copy Extensions required an existing IMS database environment running on z/OS. It extended the functionality of the standard IMS image copy utility.

For mainframe products: Did IMS Image Copy Extensions run in an LPAR?

As a z/OS-based tool, IMS Image Copy Extensions ran within an LPAR on a mainframe system. It was dependent on the z/OS operating system and the IMS subsystem.

Did IMS Image Copy Extensions enhance another product?

IMS Image Copy Extensions enhanced the standard IMS image copy utility by adding features like compression and improved dataset management. It was not a standalone product but rather an extension of existing IMS functionality.

What other products or components were needed for it to work?

The tool required access to the IMS control region and the databases being backed up. It also needed sufficient storage space for the image copy datasets, whether on tape or disk.

Business Value

What were the business benefits of using IMS Image Copy Extensions?

Using IMS Image Copy Extensions provided benefits such as reduced storage costs through compression of image copies, faster backup times due to more efficient data handling, and improved disaster recovery capabilities with enhanced image copy management.

What would happen if an organization did not use IMS Image Copy Extensions?

Without IMS Image Copy Extensions, organizations might have faced higher storage costs for image copies, longer backup windows, and less efficient management of their IMS database backups.

How did IMS Image Copy Extensions integrate with enterprise ecosystems?

The features of IMS Image Copy Extensions were eventually integrated into IMS High Performance Image Copy, providing a more comprehensive solution for IMS database backup and recovery.

Security

How did IMS Image Copy Extensions handle security?

IMS Image Copy Extensions leveraged the security features of z/OS and IMS. Access to the image copy datasets was controlled through standard z/OS security mechanisms.

What access control model was used?

The access control model relied on z/OS Resource Access Control Facility (RACF) or equivalent security systems to manage user access and permissions to the image copy datasets.

What encryption was used and where?

Encryption of image copy datasets could be implemented using z/OS encryption facilities. This would protect the data both in transit and at rest.

Operations

How was IMS Image Copy Extensions typically deployed?

Deployment of IMS Image Copy Extensions typically involved installing the tool on the z/OS system and configuring it to work with the existing IMS environment. This required technical expertise in both z/OS and IMS.

What ongoing operational requirements existed?

Ongoing operational requirements included monitoring the image copy jobs, managing storage space for the image copy datasets, and ensuring the integrity of the backups. Skilled personnel were needed to handle these tasks.

What were common implementation challenges?

Common implementation challenges included ensuring compatibility with the existing IMS environment, configuring the tool correctly to achieve optimal performance, and managing the storage space required for the image copies.

Ready to Start Your Migration?

Download our comprehensive migration guide for IMS Image Copy Extensions or calculate your ROI.

Calculate ROI