Enterprise Research z/OS

ERi/CICS Modernization Guide

Tools and UtilitiesAdministrationCICS

ERi/CICS is a tools and utilities product by Enterprise Research. Explore technical details, modernization strategies, and migration paths below.

Product Overview

ERi/CICS is a suite of tools designed to enhance the administration of CICS environments running on z/OS.

ERi/CICS integrates with z/OS security systems like RACF, ACF2, and Top Secret to provide secure access to CICS resources.

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 ERi/CICS do?

ERi/CICS is a suite of tools designed to simplify and enhance the administration of CICS environments. It provides functionalities such as single sign-on, data viewing, lock management, and duplicate dataset management, all aimed at improving efficiency and control within CICS.

Is this a system, application, or tool?

ERi/CICS is a toolset designed to enhance the administration of CICS regions. It provides utilities to manage security, data access, and system resources within the CICS environment, making it easier to maintain and optimize CICS operations.

What types of organizations use this?

Organizations that rely on CICS for transaction processing and application hosting, particularly those in industries like banking, finance, and insurance, would benefit from ERi/CICS. These organizations typically require robust administration and security features for their CICS environments.

When should we consider ERi/CICS?

A company should consider ERi/CICS when they need to streamline CICS administration tasks, improve security, and enhance data management within their CICS regions. It is particularly useful when dealing with complex CICS environments that require centralized control and monitoring.

What are the alternatives to ERi/CICS?

Alternatives to ERi/CICS include other CICS administration tools and utilities offered by different vendors, as well as manual administration processes. Some organizations may also develop custom solutions to address specific CICS management needs.

Technical

What infrastructure is required?

ERi/CICS requires a z/OS environment with CICS Transaction Server. It operates within an LPAR and relies on CICS subsystems for its functionality. Specific components like CICS/SSO, CICS/View, CICS/Lock, and CICS/DupS may have additional dependencies.

For mainframe products: Does this run in an LPAR?

Yes, ERi/CICS runs in an LPAR within a z/OS environment. It is dependent on z/OS and requires CICS Transaction Server to be present. The specific subsystems required depend on the components of ERi/CICS being used.

Does this extend or enhance another product?

ERi/CICS enhances CICS by providing additional administrative and security features. It extends the capabilities of CICS by offering tools for single sign-on, data viewing, lock management, and duplicate dataset management.

What are the main system components?

The main components of ERi/CICS include CICS/SSO for single sign-on, CICS/View for data viewing, CICS/Lock for lock management, and CICS/DupS for duplicate dataset management. These components work together to provide a comprehensive CICS administration solution.

Business Value

What business problem does it solve?

ERi/CICS solves the business problem of complex CICS administration by providing a suite of tools that simplify tasks such as security management, data access control, and resource monitoring. Without ERi/CICS, organizations may face increased administrative overhead, security vulnerabilities, and operational inefficiencies.

What is the primary business value?

The primary business value of ERi/CICS is improved efficiency and control over CICS environments. It reduces administrative overhead, enhances security, and streamlines data management, leading to cost savings and improved operational performance.

What would happen if an organization did NOT use this product?

If an organization did not use ERi/CICS, they would likely face increased administrative overhead, potential security vulnerabilities, and difficulties in managing CICS resources. This could lead to higher operational costs and reduced efficiency.

Security

What authentication methods are supported?

ERi/CICS supports authentication methods compatible with z/OS security systems, such as RACF, ACF2, and Top Secret. It leverages these systems to control access to CICS resources and ensure secure operations.

What access control model is used?

ERi/CICS uses an access control model based on the underlying z/OS security system (RACF, ACF2, Top Secret). It leverages these systems to define and enforce access controls for CICS resources, ensuring that only authorized users can access sensitive data and functions.

What audit/logging capabilities exist?

ERi/CICS integrates with z/OS security systems to provide comprehensive audit and logging capabilities. It logs security-related events and activities within the CICS environment, allowing administrators to monitor and track access to sensitive resources.

Operations

How is this product typically deployed?

ERi/CICS is typically deployed on-premise within a z/OS environment. It requires technical expertise in CICS administration and z/OS security to implement and maintain. Ongoing operational requirements include monitoring system performance, managing user access, and applying security updates.

What level of technical expertise is required to implement it?

Implementing ERi/CICS requires a strong understanding of CICS administration and z/OS security. Common challenges include configuring security settings, integrating with existing security systems, and ensuring compatibility with other CICS applications.

What ongoing operational requirements exist?

Ongoing operational requirements for ERi/CICS include monitoring system performance, managing user access, applying security updates, and troubleshooting any issues that arise. This requires dedicated staff with expertise in CICS and z/OS.

Ready to Start Your Migration?

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

Calculate ROI