E-GEN/iCAN Modernization Guide
E-GEN/iCAN is a data discovery, mining and processi product by International Software Company. Explore technical details, modernization strategies, and migration paths below.
Product Overview
E-GEN/iCAN is a tool designed to document z/OS mainframe environments.
This helps in managing complex systems, meeting compliance requirements, and planning modernization efforts.
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 E-GEN/iCAN do?
E-GEN/iCAN is a utility designed to document z/OS environments. It collects information about job scheduling, program source, JCL, CICS, and IMS definitions. It allows users to view reports and information on discovered resources, browse resources in ISPF, and generate GUI views.
Is this a system, application, or tool?
E-GEN/iCAN is a tool set that provides capabilities for data discovery, documentation, and visualization of z/OS environments. It helps organizations understand and manage their mainframe resources.
What types of organizations use this?
Organizations that rely on z/OS mainframe environments, particularly those in industries like banking, insurance, and government, commonly use E-GEN/iCAN. These organizations need to understand and manage their mainframe resources effectively.
When should we consider E-GEN/iCAN?
A company should consider using E-GEN/iCAN when they need to document, understand, and manage their z/OS environment. This is especially important when dealing with complex systems, compliance requirements, or modernization efforts.
What are the alternatives to E-GEN/iCAN?
Alternatives to E-GEN/iCAN include Enterprise>Meta Environment, BMC Helix Discovery, Tivoli Application Dependency Discovery Manager, Mainframe Topology, and EView/390z Discovery. These products offer similar capabilities for discovering and documenting mainframe environments.
Technical
What infrastructure is required?
E-GEN/iCAN requires a z/OS environment to run. It may also require specific subsystems like CICS and IMS, depending on the data being collected. The product is z/OS dependent and typically runs in an LPAR.
For mainframe products: Does this run in an LPAR?
E-GEN/iCAN runs on the z/OS platform. It is designed to discover and document resources within the z/OS environment, making it platform-specific.
What data sources does E-GEN/iCAN use?
E-GEN/iCAN collects information from various sources within the z/OS environment, including job scheduling systems, program source code, JCL, CICS definitions, and IMS definitions. It uses collectors to gather this data.
How can users interact with the discovered data?
E-GEN/iCAN provides interfaces for browsing resources in ISPF and generating GUI views of resources. This allows users to interact with the discovered data in different ways.
Business Value
How does E-GEN/iCAN provide business value?
E-GEN/iCAN helps organizations understand their z/OS environment, which can lead to better resource management, improved compliance, and more efficient modernization efforts. By documenting the environment, it reduces the risk associated with changes and provides a foundation for future development.
What happens if an organization does not use E-GEN/iCAN?
Without E-GEN/iCAN, organizations may struggle to understand their z/OS environment, leading to inefficient resource utilization, increased risk of errors, and difficulty in meeting compliance requirements. This can hinder modernization efforts and increase operational costs.
When is E-GEN/iCAN a good fit?
E-GEN/iCAN is a good fit for organizations that need to document and understand their z/OS environment. It is particularly useful for organizations undergoing modernization efforts or those with complex mainframe systems.
Security
What specific authentication methods are supported?
Specific authentication methods supported by E-GEN/iCAN would need to be confirmed in the product documentation. Mainframe security typically involves integration with systems like RACF, ACF2, or Top Secret.
What access control model is used?
The access control model used by E-GEN/iCAN would need to be confirmed in the product documentation. Mainframe security often relies on Role-Based Access Control (RBAC) or Access Control Lists (ACLs) managed by security systems like RACF.
What encryption is used and where?
Encryption used by E-GEN/iCAN and where it is used would need to be confirmed in the product documentation. Encryption is often used to protect sensitive data at rest and in transit within the mainframe environment.
Operations
What ongoing operational requirements exist?
Ongoing operational requirements for E-GEN/iCAN include monitoring the collectors, maintaining the repository of discovered data, and ensuring the product is properly configured. Staffing requirements depend on the size and complexity of the z/OS environment.
What are common implementation challenges?
Common implementation challenges for E-GEN/iCAN include configuring the collectors to gather the necessary data, integrating with existing security systems, and ensuring the discovered data is accurate and up-to-date.
What administrative interfaces are available?
Administrative interfaces available for E-GEN/iCAN would need to be confirmed in the product documentation. Mainframe administration often involves using ISPF panels or command-line interfaces.
Ready to Start Your Migration?
Download our comprehensive migration guide for E-GEN/iCAN or calculate your ROI.