Name: REXXSQL
Availability: InStock

Question 1

What does REXXSQL do?

Accepted Answer

REXXSQL enables REXX procedures to interact with DB2 databases on z/VM and z/VSE systems. It provides an interface for executing SQL statements from within REXX code, simplifying data access and manipulation. This allows developers to leverage the power of SQL within their REXX applications.

Question 2

Is this a system, application, or tool?

Accepted Answer

REXXSQL is middleware that bridges the gap between REXX scripting and DB2 databases. It provides the necessary functions and interfaces for REXX programs to communicate with and query DB2. It is not a standalone application but rather a toolset that enhances the capabilities of REXX.

Question 3

What types of organizations use this?

Accepted Answer

Organizations using DB2 on z/VM or z/VSE platforms that need to integrate database access into their REXX-based applications will find REXXSQL valuable. This includes businesses in finance, insurance, and other sectors that rely on mainframe systems for critical operations. Any organization seeking to streamline data access within their REXX environment should consider REXXSQL.

Question 4

When should we consider REXXSQL?

Accepted Answer

Consider REXXSQL when you need to embed SQL queries within REXX scripts to automate data processing, generate reports, or perform database administration tasks. If your organization already uses REXX for application development and needs to interact with DB2 databases, REXXSQL provides a straightforward solution. It is particularly useful when existing REXX applications need to be extended with database functionality.

Question 5

What are the alternatives to REXXSQL?

Accepted Answer

Alternatives to REXXSQL include developing custom interfaces using native DB2 APIs or employing other scripting languages that have built-in database connectivity. However, these options may require more complex coding and a deeper understanding of DB2 internals. Other products that offer similar functionality might exist, but REXXSQL is specifically designed for REXX and DB2 environments on z/VM and z/VSE.

Question 6

What infrastructure is required?

Accepted Answer

REXXSQL requires a running DB2 instance on either z/VM or z/VSE. It also needs a REXX interpreter to execute the scripts that utilize the REXXSQL interface. The system must have sufficient resources to support both DB2 and the REXX environment. Ensure that the necessary communication protocols between REXX and DB2 are configured correctly.

Question 7

For mainframe products: Does this run in an LPAR?

Accepted Answer

REXXSQL operates within the z/VM or z/VSE environment, typically running in an LPAR. It is not directly z/OS dependent but relies on the underlying operating system services provided by z/VM or z/VSE. It enhances DB2 by providing a REXX interface, and it requires DB2 to be present to function.

Question 8

What configuration files or interfaces are used?

Accepted Answer

REXXSQL uses configuration files to define database connection parameters, such as the DB2 subsystem ID, user credentials, and other connection-related settings. These files are typically text-based and can be edited using standard text editors. The interface also provides options for specifying SQL statement execution parameters.

Question 9

What types of APIs does this product expose?

Accepted Answer

REXXSQL exposes a set of functions that can be called from within REXX scripts. These functions allow you to connect to DB2, execute SQL statements, fetch results, and handle errors. The API is native to REXX and does not typically involve REST or SOAP interfaces.

Question 10

How does REXXSQL provide business value?

Accepted Answer

REXXSQL simplifies database interactions for REXX developers, reducing the need for complex coding and manual data handling. By enabling REXX scripts to directly access and manipulate DB2 data, it automates tasks, improves data accuracy, and accelerates application development. This leads to increased efficiency and reduced operational costs.

Question 11

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

Accepted Answer

Without REXXSQL, organizations would need to rely on more complex and time-consuming methods for integrating REXX applications with DB2 databases. This could involve writing custom interfaces or using other scripting languages, which may require specialized skills and increase development time. The absence of REXXSQL can lead to increased costs and reduced efficiency.

Question 12

How does this product integrate with enterprise ecosystems?

Accepted Answer

REXXSQL integrates into enterprise ecosystems by providing a seamless interface between REXX applications and DB2 databases. This allows organizations to leverage their existing REXX investments while taking advantage of DB2's robust data management capabilities. It fits into environments where REXX is used for scripting and automation tasks.

Question 13

What is the typical licensing model?

Accepted Answer

The typical licensing model for REXXSQL is likely a perpetual license or a subscription-based model, depending on the vendor's policies. The total cost of ownership includes the initial license fee, maintenance costs, and any required training or consulting services. Vendor lock-in considerations depend on the extent to which REXXSQL is integrated into critical applications.

Question 14

What specific authentication methods are supported?

Accepted Answer

REXXSQL supports authentication methods provided by the underlying DB2 system. This may include user IDs and passwords, as well as more advanced authentication mechanisms such as Kerberos. The specific methods depend on the DB2 configuration and security policies.

Question 15

What access control model is used?

Accepted Answer

REXXSQL leverages the access control model implemented by DB2. This typically involves Role-Based Access Control (RBAC), where users are assigned roles with specific privileges. Access to DB2 data and resources is controlled based on these roles. REXXSQL does not implement its own access control model but relies on DB2's security features.

Question 16

What encryption is used and where?

Accepted Answer

Encryption in REXXSQL depends on the encryption capabilities of the underlying DB2 system. Data can be encrypted at rest within the DB2 database, and data in transit can be encrypted using protocols such as SSL/TLS. REXXSQL itself does not provide encryption but relies on DB2's encryption features.

Question 17

What audit/logging capabilities exist?

Accepted Answer

REXXSQL utilizes DB2's audit and logging capabilities to track database access and modifications. Audit trails can be generated to record user activity, SQL statement execution, and other relevant events. These logs can be used for security monitoring and compliance purposes. The specific logging options depend on the DB2 configuration.

Question 18

How is this product typically deployed?

Accepted Answer

REXXSQL is typically deployed on-premise, alongside the DB2 database on z/VM or z/VSE systems. The implementation requires technical expertise in both REXX scripting and DB2 database administration. Ongoing operational requirements include monitoring database performance, managing user access, and maintaining the REXXSQL interface.

Question 19

What ongoing operational requirements exist?

Accepted Answer

REXXSQL requires ongoing monitoring to ensure that the interface between REXX and DB2 is functioning correctly. This includes monitoring database connections, SQL execution performance, and error logs. Regular maintenance is needed to apply updates, manage user access, and optimize performance. Staffing requirements include REXX developers and DB2 administrators.

Question 20

What administrative interfaces are available?

Accepted Answer

REXXSQL provides administrative interfaces through the REXX environment and DB2's administrative tools. User management is handled within DB2, using its security features. Configuration parameters are typically set in configuration files. Monitoring and logging capabilities are provided by DB2 and can be accessed through its administrative interfaces.

Question 21

What are common implementation challenges?

Accepted Answer

Common implementation challenges include configuring the communication protocols between REXX and DB2, ensuring proper authentication and authorization, and optimizing SQL query performance. It is important to thoroughly test the REXXSQL interface and monitor its performance in a production environment.

Share Your Product Experience

REXXSQL

Product Overview

Frequently Asked Questions