ADPAC Corporation z/OS

IMPACT Modernization Guide

Tools and UtilitiesApplication Development

IMPACT is a tools and utilities product by ADPAC Corporation. Explore technical details, modernization strategies, and migration paths below.

Product Overview

IMPACT is a tool designed for organizations using z/OS mainframes to manage and maintain applications written in Assembler, COBOL, and PL/1.

This leads to more stable and reliable software.

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 IMPACT do?

IMPACT analyzes the potential effects of modifications to application programs. It identifies related programs, copy members, and screen maps that could be affected by a change.

Is this a system, application, or tool?

IMPACT is a tool designed to aid application development and maintenance. It provides insights into the relationships between different components of a software system.

What types of organizations use this?

Organizations that develop and maintain applications in Assembler, COBOL, or PL/1 on z/OS mainframes can benefit from using IMPACT. These are often large enterprises in industries like banking, insurance, and government.

When should we consider IMPACT?

A company should consider using IMPACT when making changes to application programs to understand the potential ripple effects. This helps prevent unexpected issues and ensures that all necessary components are updated.

What are the alternatives to IMPACT?

Alternatives to IMPACT include manual analysis, custom scripting, or other impact analysis tools. Some competing products are SVCommands, Rational Programming Patterns for System z, CA Vollie, and SCOUT².

Technical

What infrastructure is required?

IMPACT runs on the z/OS platform. It analyzes application programs written in Assembler, COBOL, and PL/1.

For mainframe products: Does this run in an LPAR?

As a mainframe product, IMPACT runs within an LPAR on z/OS. It leverages z/OS facilities for data access and processing.

How does IMPACT analyze program dependencies?

IMPACT analyzes source code and related files to determine dependencies. It uses standard z/OS datasets for input and output.

What programming languages does IMPACT support?

IMPACT supports Assembler, COBOL, and PL/1 programming languages. It parses source code to identify dependencies between programs, copy members, and screen maps.

Business Value

How does IMPACT provide business value?

IMPACT helps organizations reduce the risk of introducing errors when modifying application programs. By identifying dependencies, it ensures that all affected components are updated, leading to more reliable software.

How does IMPACT improve development efficiency?

By providing a clear understanding of program dependencies, IMPACT reduces the time and effort required to make changes to application programs. This leads to faster development cycles and lower maintenance costs.

How does IMPACT contribute to application stability?

IMPACT helps organizations maintain the stability and reliability of their mainframe applications. This is especially important for critical business systems that require high availability.

Security

How does IMPACT ensure data security?

IMPACT leverages the security features of the z/OS operating system. Access to source code and related files is controlled through standard z/OS security mechanisms.

Does IMPACT handle sensitive data?

IMPACT does not directly handle sensitive data. It analyzes source code to identify dependencies, but it does not store or process application data.

How does IMPACT integrate with existing security systems?

IMPACT integrates with existing security systems on z/OS. It uses standard z/OS security protocols for authentication and authorization.

Operations

How is IMPACT typically deployed?

IMPACT is typically deployed on-premise within the z/OS environment. It requires access to source code libraries and related datasets.

What level of technical expertise is required to implement IMPACT?

Implementing IMPACT requires expertise in z/OS and application development. Familiarity with Assembler, COBOL, and PL/1 is also helpful.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring the performance of IMPACT and ensuring that it has access to the necessary datasets. Regular maintenance may be required to keep the tool up-to-date.

Ready to Start Your Migration?

Download our comprehensive migration guide for IMPACT or calculate your ROI.

Calculate ROI