SPC Systems z/OS

RW2 Modernization Guide

MigrationReport Generation and ManagementCOBOL

RW2 is a migration product by SPC Systems. Explore technical details, modernization strategies, and migration paths below.

Product Overview

RW2 is a precompiler designed to support COBOL Report Writer statements when using IBM Enterprise COBOL compilers on z/OS.

RW2 integrates with the z/OS security environment, leveraging RACF for access control.

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 is RW2 and what does it do?

RW2 is a precompiler that enables the use of COBOL Report Writer language features with IBM Enterprise COBOL compilers. It translates Report Writer statements into standard COBOL code.

What COBOL Report Writer statements does RW2 support?

RW2 supports standard COBOL Report Writer syntax, including statements like INITIATE, GENERATE, and TERMINATE for report processing. It also supports clauses for defining report groups, control breaks, and summary calculations.

How is RW2 configured?

RW2 uses configuration files to specify precompiler options, such as input and output file names, listing options, and diagnostic message levels. These files are typically specified using JCL parameters when invoking the precompiler.

Technical

How does RW2 work technically?

RW2 operates as a precompiler. It takes COBOL source code containing Report Writer statements as input and produces standard COBOL source code as output. This output is then compiled using a standard COBOL compiler.

What are the main system components of RW2?

The primary system component is the RW2 precompiler itself. It reads the COBOL source, parses Report Writer statements, and generates equivalent COBOL code. The generated code is then passed to the COBOL compiler.

Does RW2 expose any APIs?

RW2 does not expose APIs directly. It functions as a precompiler, transforming COBOL source code before compilation. Integration with other systems typically involves incorporating the precompilation step into the build process.

What databases or storage mechanisms are used by RW2?

RW2 uses standard z/OS file system for input and output. It reads COBOL source files and writes the precompiled COBOL source files to disk. No specific database or storage mechanism is required beyond the z/OS file system.

Business Value

What is the business value of using RW2?

RW2 allows organizations to continue using COBOL Report Writer features with newer IBM Enterprise COBOL compilers. This preserves existing report generation logic and reduces the effort required to migrate to newer COBOL versions.

How does RW2 improve developer productivity?

By automating the translation of Report Writer statements, RW2 reduces the manual effort required to maintain and update report generation programs. This can lead to significant cost savings and improved developer productivity.

Security

How does RW2 integrate with z/OS security?

RW2 operates within the security framework of the z/OS environment. Access to the precompiler and the COBOL source files is controlled by z/OS security mechanisms, such as RACF.

What authentication methods are supported by RW2?

RW2 itself does not implement specific authentication methods. It relies on the authentication mechanisms provided by the z/OS operating system.

What encryption is used by RW2?

RW2 does not perform encryption. The security of the COBOL source code and the generated reports depends on the security measures implemented at the z/OS level, such as data set encryption.

Operations

How is RW2 administered and monitored?

RW2 is administered through JCL parameters and configuration files. There is no separate administrative interface. Monitoring is typically done through standard z/OS monitoring tools and the precompiler's listing output.

What monitoring and logging capabilities exist in RW2?

RW2 generates listing output that includes diagnostic messages and information about the precompilation process. This output can be used to troubleshoot issues and monitor the performance of the precompiler.

Ready to Start Your Migration?

Download our comprehensive migration guide for RW2 or calculate your ROI.

Calculate ROI