PIE/REXX Modernization Guide

PIE/REXX enables the development of REXX routines that operate within the CICS environment. It allows users to create applications that interact with CICS resources and other PIE/CICS products, extending the capabilities of CICS with the REXX language.

PIE/REXX is a tool set that provides the necessary components for developing and executing REXX routines within CICS. It is not a standalone application but rather a framework that enhances CICS functionality.

Organizations that rely on CICS for transaction processing and want to leverage the REXX language for application development and customization would benefit from PIE/REXX. These organizations are typically enterprises with mainframe environments.

A company should consider PIE/REXX when they need to develop custom CICS applications using REXX, integrate CICS with other systems, or automate CICS tasks. It is particularly useful when existing CICS applications need to be extended or modified without extensive COBOL programming.

Alternatives to PIE/REXX include other REXX interpreters and development environments for CICS, as well as using COBOL or other languages directly supported by CICS. However, PIE/REXX provides a specific integration with CICS and other PIE/CICS products.

PIE/REXX runs on z/OS and requires CICS Transaction Server. It operates within an LPAR and relies on CICS subsystems for transaction management and resource access.

PIE/REXX extends CICS by allowing REXX routines to interact with CICS resources. It requires CICS to be present and operational.

PIE/REXX requires CICS Transaction Server to be installed and configured. It also benefits from the presence of other PIE/CICS products for enhanced integration.

PIE/REXX routines can interface with CICS using specific APIs and commands. The exact syntax depends on the specific CICS resource being accessed.

PIE/REXX allows organizations to develop custom CICS applications more quickly and easily than using traditional languages like COBOL. This can reduce development costs and improve time-to-market for new CICS-based services.

By enabling REXX-based development, PIE/REXX can reduce the need for specialized COBOL skills, which can be difficult and expensive to acquire. This allows organizations to leverage a broader pool of developers.

PIE/REXX integrates with existing CICS infrastructure, leveraging existing investments in CICS and related technologies. It enhances the value of these investments by providing a more flexible development environment.

PIE/REXX leverages CICS security mechanisms for authentication and authorization. Access to CICS resources from REXX routines is controlled by CICS security profiles.

PIE/REXX relies on CICS for auditing and logging. All access to CICS resources from REXX routines is logged by CICS, providing an audit trail of user activity.

PIE/REXX uses the access control model provided by CICS, which typically involves defining user profiles and resource profiles. Access control lists (ACLs) are used to control access to CICS resources.

PIE/REXX is typically deployed on-premise alongside CICS. It requires installation and configuration within the CICS environment.

Implementing PIE/REXX requires expertise in both CICS and REXX. Familiarity with CICS administration and security is also important.

Ongoing operational requirements include monitoring CICS performance, managing REXX routines, and ensuring the security of CICS resources. Regular maintenance and updates may also be required.