CDDF Modernization Guide
CDDF is a abend product by NETEC International. Explore technical details, modernization strategies, and migration paths below.
Product Overview
CDDF was a tool designed to assist in managing and analyzing CICS transaction dumps on z/OS systems.
Organizations used CDDF to reduce the time and resources required to analyze and resolve CICS transaction abends.
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 CDDF do?
CDDF is a tool designed to assist in managing and analyzing CICS transaction dumps on z/OS systems. It provides features such as interactive dump viewing, automatic storage and retrieval, and notifications to various consoles and users.
Is this a system, application, or tool?
CDDF is primarily a tool set designed to enhance the management and analysis of CICS transaction dumps. It provides functionalities that extend beyond basic system or application capabilities, focusing on problem determination and recovery.
What types of organizations use this?
Organizations that rely heavily on CICS for transaction processing and require robust tools for diagnosing and resolving abends would find CDDF useful. These organizations are often in industries such as banking, finance, insurance, and retail, where transaction integrity and system availability are critical.
When should we consider CDDF?
A company should consider using CDDF when they experience frequent CICS transaction abends and need a more efficient way to analyze and resolve these issues. It is particularly useful when manual dump analysis is time-consuming and resource-intensive.
What are the alternatives to CDDF?
Alternatives to CDDF include SymDump CICS, SLAMDUMP/CICS, and Dump Detective for CICS. These products offer similar capabilities for analyzing and managing CICS transaction dumps, but may differ in features, integration, and ease of use.
Technical
What infrastructure is required?
CDDF runs on the z/OS platform and is dependent on the CICS subsystem. It requires access to CICS transaction dumps and integrates with z/OS consoles and Netview for notifications.
For mainframe products: Does this run in an LPAR?
As a z/OS product, CDDF runs within an LPAR (Logical Partition). It is tightly integrated with the z/OS operating system and requires the CICS subsystem to be active and properly configured.
Does this extend/enhance another product?
CDDF enhances CICS by providing advanced dump analysis and management capabilities. It is not a standalone product in the sense that it requires CICS to be present, but it significantly extends the functionality available for diagnosing and resolving transaction abends.
What configuration files are used?
CDDF likely uses configuration files to define parameters for dump storage, retrieval, and notification settings. These files would specify details such as dump dataset names, notification thresholds, and integration points with Netview and z/OS consoles.
Business Value
How does CDDF provide business value?
CDDF provides business value by reducing the time and resources required to analyze and resolve CICS transaction abends. This leads to improved system availability, reduced operational costs, and enhanced customer satisfaction.
What happens if an organization does NOT use this product?
Without CDDF, organizations would rely on manual dump analysis, which is a time-consuming and error-prone process. This can lead to longer outage times, increased operational costs, and potential business disruptions.
How does this product integrate with enterprise ecosystems?
CDDF integrates with existing enterprise ecosystems by providing notifications to Netview and z/OS consoles. This allows operations teams to be alerted to transaction abends and take corrective action quickly. It may also integrate with other monitoring and management tools.
Security
How is user management handled?
CDDF likely uses the z/OS security infrastructure (such as RACF, ACF2, or Top Secret) for authentication and access control. This ensures that only authorized personnel can access and analyze CICS transaction dumps.
What access control model is used?
CDDF likely employs an access control model based on roles, where users are assigned specific roles that determine their access privileges. This ensures that sensitive dump data is only accessible to authorized personnel.
What audit/logging capabilities exist?
CDDF's audit and logging capabilities would track user access to transaction dumps, changes to configuration settings, and other security-related events. This information can be used to monitor for unauthorized activity and ensure compliance with security policies.
Operations
How is this product typically deployed?
CDDF is typically deployed on-premise, as it is tightly integrated with the z/OS environment and CICS subsystem. It requires a certain level of technical expertise to implement and maintain, including knowledge of z/OS, CICS, and dump analysis techniques.
What ongoing operational requirements exist?
Ongoing operational requirements for CDDF include monitoring dump storage utilization, ensuring the availability of the CICS subsystem, and maintaining the integration with Netview and z/OS consoles. Regular maintenance is also required to apply updates and address any issues.
What are common implementation challenges?
Common implementation challenges for CDDF include configuring the dump storage datasets, integrating with existing security systems, and training personnel on how to use the tool effectively. It is important to plan the implementation carefully and involve experienced z/OS and CICS administrators.
Ready to Start Your Migration?
Download our comprehensive migration guide for CDDF or calculate your ROI.