Infotel z/OS

MasterReorg for DB2 on z/OS Modernization Guide

Tools and UtilitiesAdministrationDatabasesDb2

MasterReorg for DB2 on z/OS is a tools and utilities product by Infotel. Explore technical details, modernization strategies, and migration paths below.

Product Overview

MasterReorg automates the reorganization of DB2 objects (tables, indexes) on z/OS.

It uses standard DB2 APIs for interaction.

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 MasterReorg?

MasterReorg automates the reorganization of DB2 objects, such as tables and indexes, to improve performance and reclaim space. It uses a time-window approach, selecting objects for reorganization based on estimated completion time. It is part of the MASTER-UTIL suite.

How does MasterReorg decide which DB2 objects to reorganize?

MasterReorg determines which objects to reorganize based on estimated completion time within a defined time window. It considers factors like object size, fragmentation level, and system load to prioritize objects that will benefit most from reorganization within the available time.

What type of DB2 reorganization does MasterReorg perform?

MasterReorg performs complete DB2 reorganization, which involves rebuilding indexes, reordering rows in tables, and reclaiming fragmented space. This process optimizes data access and improves overall database performance.

How does MasterReorg relate to the MASTER-UTIL suite?

MasterReorg is part of the MASTER-UTIL suite, which provides a range of utilities for DB2 database management, including backup, recovery, and data migration tools. These utilities are designed to work together to streamline DB2 administration tasks.

Technical

What configuration files are used by MasterReorg?

MasterReorg uses configuration files to define reorganization parameters, such as time windows, object selection criteria, and system resource limits. These files can be customized to meet specific requirements and optimize performance.

What APIs does MasterReorg expose?

MasterReorg uses standard DB2 APIs for interacting with the DB2 subsystem. It does not expose any custom APIs.

How does MasterReorg interact with the DB2 catalog?

MasterReorg interacts directly with the DB2 catalog to gather information about DB2 objects, such as tables, indexes, and their characteristics. This information is used to determine which objects to reorganize and how to optimize the reorganization process.

What ports or network configurations are required for MasterReorg?

MasterReorg uses standard DB2 commands and utilities for performing reorganization tasks. It does not require any special ports or network configurations beyond those required for DB2 itself.

Business Value

How does MasterReorg improve DB2 performance?

MasterReorg improves DB2 performance by optimizing data access and reducing I/O operations. By reorganizing tables and indexes, it reduces fragmentation and improves data locality, leading to faster query execution and reduced response times.

How does MasterReorg reduce administrative overhead?

MasterReorg automates the reorganization process, reducing the need for manual intervention and freeing up DBAs to focus on other tasks. By selecting objects based on a time window, it ensures that reorganization tasks are completed efficiently and without disrupting critical business operations.

How does MasterReorg reduce storage costs?

By reclaiming fragmented space and optimizing data storage, MasterReorg can reduce storage costs and improve storage utilization. This can lead to significant cost savings, especially in large DB2 environments.

Security

What authentication methods are supported by MasterReorg?

MasterReorg leverages the existing DB2 security infrastructure for authentication and authorization. It does not introduce any new security mechanisms or protocols.

What access control model is used by MasterReorg?

MasterReorg relies on the DB2 access control model for managing user permissions and access to DB2 objects. It does not implement its own access control model.

What encryption is used by MasterReorg?

MasterReorg does not encrypt data itself. It relies on DB2's encryption capabilities for protecting sensitive data.

What audit/logging capabilities exist in MasterReorg?

MasterReorg logs all reorganization activities, providing an audit trail for tracking changes and identifying potential issues. These logs can be used for security monitoring and compliance purposes.

Operations

What administrative interfaces are available for MasterReorg?

MasterReorg is administered through configuration files and command-line interfaces. It does not have a dedicated GUI or web console.

How is user management handled in MasterReorg?

User management is handled through the standard DB2 security administration tools. MasterReorg does not provide its own user management capabilities.

What monitoring/logging capabilities exist in MasterReorg?

MasterReorg provides logging and monitoring capabilities to track the progress of reorganization tasks and identify potential issues. These logs can be integrated with standard monitoring tools for proactive problem detection.

What are the main configuration parameters for MasterReorg?

MasterReorg configuration parameters include time windows for reorganization, object selection criteria, system resource limits, and logging options. These parameters can be customized to optimize performance and meet specific requirements.

Ready to Start Your Migration?

Download our comprehensive migration guide for MasterReorg for DB2 on z/OS or calculate your ROI.

Calculate ROI