What infrastructure was required?

CA VM:DB REXX for DB2 required a z/VM environment with DB2 installed and configured. It also needed the REXX interpreter and any necessary libraries or modules to support the interface between REXX and DB2.

For mainframe products: Did this run in an LPAR?

As a mainframe product, CA VM:DB REXX for DB2 ran within an LPAR (Logical Partition) on a z/VM system. It was not directly z/OS dependent but required the z/VM operating system to function.

Did this extend another product?

The product extended the capabilities of REXX by providing functions and commands to interact with DB2. It required both REXX and DB2 to be present.

What were the main system components?

The core components likely included a REXX interface module, a DB2 communication module, and potentially some utility programs for managing connections and executing SQL statements. Specific component names are not available.

What was the business value of using CA VM:DB REXX for DB2?

The primary business value was enabling developers to leverage their REXX skills to access and manipulate DB2 data. This could reduce development time and costs for applications that needed to interact with DB2 on z/VM.

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

Without CA VM:DB REXX for DB2, organizations would need to find alternative ways to access DB2 data from REXX programs. This might involve using other programming languages, developing custom interfaces, or using less efficient data access methods.

What was the typical licensing model and total cost of ownership?

The product likely used a perpetual licensing model. The total cost of ownership would include the initial license fee, maintenance fees, and the cost of any required training or consulting services.

What security features did CA VM:DB REXX for DB2 provide?

Security features likely included authentication to DB2 using standard DB2 security mechanisms. Access control would be managed through DB2's authorization model, which controls which users can access specific tables and data.

How did it integrate with existing security systems?

The product likely integrated with existing security systems on z/VM, such as RACF, ACF2, or Top Secret, to manage user authentication and authorization. This allowed organizations to leverage their existing security infrastructure.

What auditing and logging capabilities existed?

Auditing and logging capabilities were likely provided through DB2's audit facilities. This allowed organizations to track data access and modifications made through REXX programs.

How was this product typically deployed?

Deployment typically involved installing the product on the z/VM system and configuring it to connect to the DB2 database. This required technical expertise in both z/VM and DB2.

What ongoing operational requirements existed?

Ongoing operational requirements included monitoring the performance of REXX programs and DB2, as well as performing regular maintenance tasks such as backups and security updates. Staffing requirements included system programmers and database administrators with expertise in z/VM and DB2.

What were common implementation challenges?

Common implementation challenges included ensuring compatibility between the REXX interface and the DB2 version, as well as configuring security settings correctly. Performance tuning was also important to ensure that REXX programs did not negatively impact DB2 performance.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

CA VM:DB REXX for DB2

CA Technologies Not Supported z/VM

REXX Application Development Db2

Vendor

CA Technologies

Product Overview

CA VM:DB REXX for DB2 architecture centered around providing a seamless interface between REXX programs and DB2 databases on z/VM. The core components likely included a REXX interpreter, a DB2 communication module, and a set of APIs or functions that allowed REXX scripts to execute SQL statements. The architecture facilitated data exchange between REXX applications and DB2, enabling developers to build custom solutions for data access and manipulation.

The product is no longer supported. When planning a migration, consider the following architectural options: 1. **IBM Data Access Common Collector (DACC):** A potential replacement that offers similar functionality for REXX and DB2 integration.

2. **COBOL or Assembler with Embedded SQL:** Rewriting REXX scripts in these languages allows direct DB2 access. 3.

**Java with JDBC:** Provides a platform-independent approach to DB2 access. The chosen architecture should address key requirements such as performance, scalability, security, and maintainability. A detailed architectural blueprint should outline the components, interfaces, data flows, and security considerations for the new solution.

Thorough testing and validation are essential to ensure that the migrated architecture meets the organization's needs.

Frequently Asked Questions

What did CA VM:DB REXX for DB2 do?

CA VM:DB REXX for DB2 provided an interface that allowed REXX programs to execute SQL statements and access DB2 data. It acted as a bridge between the REXX scripting language and the DB2 database management system, enabling developers to write REXX programs that could interact with DB2.

Was this a system, application, or tool?

CA VM:DB REXX for DB2 was middleware. It facilitated communication and data exchange between REXX applications and DB2 databases.

What types of organizations used this?

Organizations that relied on z/VM and DB2 for their mainframe applications and needed to integrate REXX scripting with DB2 data access would have used this product. These were typically large enterprises in industries like banking, finance, and insurance.

When should a company have considered CA VM:DB REXX for DB2?

Companies would have considered using CA VM:DB REXX for DB2 when they needed to develop or maintain applications that required REXX scripting to interact with DB2 databases on z/VM. It provided a way to leverage existing REXX skills for DB2 data access.

What are the alternatives to CA VM:DB REXX for DB2?

Alternatives to CA VM:DB REXX for DB2 include other REXX-DB2 interfaces or using different programming languages and database access methods. Examples include IBM Data Access Common Collector (DACC), or developing custom solutions using languages like COBOL or Java with JDBC.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Share Your Product Experience

CA VM:DB REXX for DB2

Product Overview

Frequently Asked Questions

What did CA VM:DB REXX for DB2 do?

Was this a system, application, or tool?

What types of organizations used this?

When should a company have considered CA VM:DB REXX for DB2?

What are the alternatives to CA VM:DB REXX for DB2?

What infrastructure was required?

For mainframe products: Did this run in an LPAR?

Did this extend another product?

What were the main system components?

What was the business value of using CA VM:DB REXX for DB2?

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

What was the typical licensing model and total cost of ownership?

What security features did CA VM:DB REXX for DB2 provide?

How did it integrate with existing security systems?

What auditing and logging capabilities existed?

How was this product typically deployed?

What ongoing operational requirements existed?

What were common implementation challenges?

Related Products

More from CA Technologies

ADC2

AutoMate

CA 90s

CA Alert/VM

CA APAS Insight

CA Automated Code Structuring for COBOL

Similar Products

Ab Initio Business Rules Environment

AcceleREXX

Access Manager for CICS

Access Manager for IMS

ACCOLADE

ADF II

Help Improve This Directory

Share Your Product Experience