What infrastructure is required?

R to R runs on the z/OS platform. It requires a z/OS environment with RACF installed and configured. It leverages the REXX runtime environment available on z/OS.

For mainframe products: Does this run in an LPAR?

R to R runs within an LPAR on z/OS. It is dependent on the z/OS operating system and requires the presence of RACF.

Does this extend/enhance another product?

R to R extends the capabilities of RACF by providing a REXX interface. It requires RACF to be present and configured on the z/OS system.

What other products or components must be present for this to work?

R to R requires a z/OS system with RACF installed and a REXX runtime environment. No other specific products are explicitly required, but it will likely interact with other system components depending on the application being developed.

What business problems does it solve?

R to R simplifies the development of RACF applications, reducing development time and effort. It enables organizations to automate security tasks, improve compliance, and integrate RACF with other systems.

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

If an organization does not use R to R, they would need to rely on more complex and time-consuming methods for developing RACF applications, such as using Assembler language or manual security administration processes. This can lead to increased costs and potential errors.

When is this product NOT a good fit?

R to R is a good fit for organizations that need to customize or automate RACF security functions and have developers familiar with REXX. It is not a good fit for organizations that do not use RACF or do not have a need for custom RACF applications.

How does R to R handle security?

R to R leverages RACF's security features for authentication and authorization. Access to RACF resources is controlled by RACF profiles and permissions. The REXX APIs provided by R to R operate within the security context established by RACF.

What authentication methods are supported?

R to R relies on RACF for authentication. Therefore, the authentication methods supported are those provided by RACF, such as password authentication, multi-factor authentication, and certificate-based authentication.

What access control model is used?

R to R uses the access control model provided by RACF, which is primarily an Access Control List (ACL) model. Access to resources is determined by the permissions granted to users or groups in RACF profiles.

How is R to R typically deployed?

R to R is typically deployed on-premise within the z/OS environment. Implementation requires expertise in z/OS, RACF, and REXX programming. Ongoing operational requirements include monitoring the performance of REXX applications and maintaining RACF security profiles.

What level of technical expertise is required to implement it?

Implementation of R to R requires technical expertise in z/OS, RACF administration, and REXX programming. Common implementation challenges include ensuring proper RACF configuration and developing efficient REXX code.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring the performance and security of REXX applications developed with R to R, as well as maintaining the underlying RACF security profiles and configurations. Regular audits of RACF configurations are recommended.

Share Your Product Experience

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

Share Your Experience

R to R

Open Software Technologies Active z/OS

Security REXX Application Development

Vendor

Open Software Technologies

Product Overview

R to R is a tool set that provides REXX APIs for developing RACF applications on z/OS. It simplifies the development process, allowing developers to automate security tasks, customize RACF functions, and integrate RACF with other enterprise systems. This leads to improved efficiency and compliance.

The architecture of R to R involves a REXX runtime environment interacting with RACF through its APIs. REXX programs use R to R APIs to perform RACF operations. These operations are then executed by RACF, which enforces security policies and access controls.

R to R relies on RACF's security features for authentication and authorization. The access control model used is primarily an Access Control List (ACL) model, as provided by RACF. Alternatives to R to R include using Assembler language directly with RACF APIs or other security administration tools.

However, R to R offers a more accessible REXX-based approach. It runs on z/OS and requires RACF to be installed. Common implementation challenges include ensuring proper RACF configuration and developing efficient REXX code.

Ongoing operational requirements include monitoring the performance of REXX applications and maintaining RACF security profiles.

Frequently Asked Questions

What does R to R do?

R to R provides REXX APIs that enable developers to create RACF applications. It simplifies the process of interacting with RACF, allowing for easier management and automation of security functions on z/OS systems.

Is this a system, application, or tool?

R to R is a tool set that provides APIs for application development. It is specifically designed to facilitate the creation of applications that interact with RACF for security management.

What types of organizations use this?

Organizations that require automation and customization of RACF security functions on z/OS systems benefit from R to R. This includes enterprises in industries such as banking, finance, insurance, and government.

When should we consider R to R?

A company should consider R to R when they need to develop custom applications that interact with RACF, automate security tasks, or integrate RACF with other systems using REXX.

What are the alternatives to R to R?

Alternatives to R to R include Assembler language programming directly with RACF APIs or other security administration tools that may offer scripting capabilities. However, R to R provides a REXX-based approach, which can be easier to use for some developers.

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

R to R

Product Overview

Frequently Asked Questions

What does R to R do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider R to R?

What are the alternatives to R to R?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

Does this extend/enhance another product?

What other products or components must be present for this to work?

What business problems does it solve?

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

When is this product NOT a good fit?

How does R to R handle security?

What authentication methods are supported?

What access control model is used?

How is R to R typically deployed?

What level of technical expertise is required to implement it?

What ongoing operational requirements exist?

Related Products

More from Open Software Technologies

EuropaMail

Memocast for z/OS

REXXTOOLS/MVS

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta access monitor

Ab Initio Business Rules Environment

AcceleREXX

Help Improve This Directory

Share Your Product Experience