Name: Compuware COPE
SKU: 1313
Availability: InStock

Virtualize IMS Systems and Reduce Subsystem Creation Costs

Creating and maintaining multiple IMS development and test systems can be a slow, expensive and technically daunting task. Compuware COPE virtualizes IMS systems, enabling new development images of IMS to be available practically on demand, significantly reducing the delays and costs associated with creating completely new IMS subsystems for critical initiatives.

Using COPE, IMS application developers can:

Rapidly deploy multiple virtual IMS databases to multiple active projects, where each system can either share or have unique databases, Db2 table programs and MFS formats
Avoid creating costly new IMS instances, modifying underlying master databases or relying on experts
Maintain their testing methodology or compile procedures and access additional isolated testing environments without significant costs

The Value of COPE

Reduces the expertise and time needed to maintain separate IMS systems and related components for every development and testing stage of every application
Increases digital business agility by allowing customers to create multiple versions of the same database for parallel application execution
Allows customers to leverage existing maintenance processes and JCL procedures using an external COPE interface
Supports the IMS Dynamic Resource Definition (DRD) feature of IMS

Key Features of COPE

Virtualized IMS Environments

COPE transforms physical resources in various stages of IMS application development and testing into virtualized and extensible representations of this same set of physical resources. All that a developer, QA specialist or database professional needs to do is change a set of required parameters, which COPE then copies and compiles to create virtual IMS systems for application development and testing.

An IMS subsystem can be virtualized with multiple versions of a given application, satisfying needs for development, integration test, UAT, pre-prod and/or other desired environments.

Database, program and library names are changed before regeneration to allow multiple copies of identically named objects to exist within a single IMS system without modifying application program names and libraries.