Broadcom z/OS zVSE/VSEn

Intertest for CICS Modernization Guide

TestingApplication DevelopmentCICS

Intertest for CICS is a testing product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

Intertest for CICS is a tool designed to assist application developers in testing and debugging CICS applications written in Assembler, COBOL, and PL/1.

User authentication is managed through CICS security, typically using RACF.

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 Intertest for CICS?

Intertest for CICS is a tool designed to aid application developers in testing and debugging CICS applications. It supports applications written in Assembler, COBOL, and PL/1, providing features for dynamic testing and real-time analysis.

What programming languages does Intertest for CICS support?

Intertest for CICS supports applications written in Assembler, COBOL, and PL/1. This allows developers working with a variety of legacy and modern CICS applications to utilize the tool.

What are some common operations performed with Intertest for CICS?

Common operations include setting breakpoints, stepping through code, examining variables, and modifying data values during runtime. Specific commands include 'B' (Break), 'G' (Go), 'D' (Display), and 'M' (Modify).

What configuration files or interfaces are used with Intertest for CICS?

Intertest for CICS uses configuration files to define testing parameters and user preferences. The specific files and interfaces used can vary based on the installation and configuration.

Technical

How do I interact with Intertest for CICS?

The primary method of interaction is through a terminal-based interface within the CICS environment. Commands are entered directly to control the debugging process. For example, to set a breakpoint at line 100, you would use 'B 100'.

What types of APIs does Intertest for CICS expose?

Intertest for CICS primarily uses a terminal-based interface, so direct API exposure is limited. Integration typically involves setting up the testing environment and configuring Intertest to work with the target CICS application.

What are the main system components of Intertest for CICS?

The main system components include the Intertest control region, the user interface, and the data storage used for breakpoints and session information. These components communicate through CICS internal mechanisms.

What databases or storage mechanisms are used by Intertest for CICS?

Intertest for CICS uses VSAM datasets for storing breakpoints, session data, and configuration information. These datasets are accessed directly by the Intertest components.

Business Value

How does Intertest for CICS provide business value?

Intertest for CICS helps reduce application development time by providing developers with real-time debugging capabilities. This allows for faster identification and resolution of issues, leading to quicker deployment cycles.

How does Intertest for CICS help reduce risk?

By enabling developers to identify and fix errors early in the development process, Intertest for CICS helps reduce the risk of application failures in production. This leads to improved application stability and reliability.

How does Intertest for CICS improve quality assurance?

Intertest for CICS allows developers to test and debug applications in a controlled environment, ensuring that they meet the required performance and functionality standards before deployment.

Security

How does Intertest for CICS handle authentication?

Intertest for CICS integrates with CICS security to control access to debugging functions. User authentication is handled through CICS RACF or similar security systems.

What access control model is used by Intertest for CICS?

Intertest for CICS uses an access control model based on CICS security settings. Access to specific debugging functions can be restricted based on user roles and permissions defined in CICS.

What encryption is used and where?

Intertest for CICS leverages CICS security features for encryption. Sensitive data, such as passwords and configuration information, can be encrypted using CICS-supported encryption algorithms.

What audit/logging capabilities exist?

Intertest for CICS provides audit logging capabilities to track user activity and debugging sessions. These logs can be used to monitor security events and ensure compliance with security policies.

Operations

What administrative interfaces are available?

Intertest for CICS provides a command-line interface for administrative tasks. User management is handled through CICS security administration tools, such as RACF.

What are the main configuration parameters?

Main configuration parameters include settings for breakpoints, session recording, and data display. These parameters can be configured through the Intertest control region and configuration files.

What monitoring/logging capabilities exist?

Intertest for CICS provides monitoring and logging capabilities to track system performance and debugging activity. Logs can be used to identify issues and optimize performance.

Ready to Start Your Migration?

Download our comprehensive migration guide for Intertest for CICS or calculate your ROI.

Calculate ROI