CPGJDBC Modernization Guide
CPGJDBC is a application development product by Lattwein. Explore technical details, modernization strategies, and migration paths below.
Product Overview
CPGJDBC enables CICS and batch applications running on z/OS and z/VSE to access data in non-mainframe databases.
You will also need to define the connection parameters and security settings.
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 CPGJDBC do?
CPGJDBC enables CICS and batch applications running on z/OS and z/VSE to access data stored in non-mainframe databases. It acts as a bridge, allowing these applications to leverage data from systems supporting JDBC or ODBC.
Is this a system, application, or tool?
CPGJDBC is middleware. It facilitates communication and data exchange between mainframe applications and other database systems.
What types of organizations use this?
Organizations that rely on mainframe systems for core business processes but need to integrate with modern, distributed databases are ideal users. This includes enterprises in finance, insurance, and retail.
When should we consider CPGJDBC?
Consider CPGJDBC when you need to access data from distributed databases from your CICS or batch applications running on z/OS or z/VSE. It is especially useful when migrating data or building new applications that require access to both mainframe and non-mainframe data.
What are the alternatives to CPGJDBC?
Alternatives include other JDBC or ODBC connectivity solutions, custom-built integration solutions, or migrating mainframe applications to distributed platforms. However, these options may involve significant development effort or infrastructure changes.
Technical
What infrastructure is required?
CPGJDBC requires a mainframe environment running z/OS or z/VSE, CICS or batch processing capabilities, and access to databases supporting JDBC or ODBC. Network connectivity between the mainframe and the target databases is also essential.
For mainframe products: Does this run in an LPAR?
CPGJDBC runs within the z/OS or z/VSE environment, typically in an LPAR. It leverages standard mainframe communication protocols to interact with CICS or batch applications.
How does CPGJDBC connect to databases?
CPGJDBC uses standard JDBC or ODBC drivers to connect to target databases. Configuration files specify connection parameters, data mappings, and security settings.
What SQL commands are supported?
CPGJDBC supports standard SQL commands for data access. The exact syntax depends on the target database and the JDBC or ODBC driver used.
Business Value
What is the business value of CPGJDBC?
CPGJDBC enables organizations to leverage existing mainframe investments while accessing data from modern, distributed systems. This can improve application functionality, reduce data silos, and support new business initiatives.
How can CPGJDBC improve business processes?
By providing seamless access to non-mainframe data, CPGJDBC can improve decision-making, streamline business processes, and enhance customer service. It allows mainframe applications to participate in modern data ecosystems.
Can CPGJDBC reduce IT costs?
CPGJDBC can reduce the need for costly data replication or migration projects. It allows organizations to access data in place, minimizing disruption and reducing IT costs.
Security
What authentication methods are supported?
CPGJDBC supports various authentication methods, including user IDs and passwords, Kerberos, and multi-factor authentication. The specific methods depend on the configuration of the mainframe environment and the target databases.
What access control model is used?
CPGJDBC uses an access control model based on user roles and permissions. Administrators can define roles with specific privileges and assign users to those roles. This controls access to data and functionality.
What encryption is used and where?
CPGJDBC supports encryption of data in transit using SSL/TLS. This protects sensitive data from eavesdropping during transmission between the mainframe and the target databases.
What audit/logging capabilities exist?
CPGJDBC provides audit logging capabilities to track user activity and data access. Audit logs can be used to monitor security events, detect unauthorized access, and comply with regulatory requirements.
Operations
How is CPGJDBC typically deployed?
CPGJDBC is typically deployed on-premise within the mainframe environment. It requires technical expertise in mainframe systems, networking, and database administration.
What ongoing operational requirements exist?
Ongoing operational requirements include monitoring system performance, managing user accounts, and maintaining database connections. Regular maintenance is required to ensure system stability and security.
What are common implementation challenges?
Common implementation challenges include configuring network connectivity, resolving data mapping issues, and ensuring security compliance. Thorough testing and planning are essential for a successful implementation.
Ready to Start Your Migration?
Download our comprehensive migration guide for CPGJDBC or calculate your ROI.