Broadcom z/OS

CA ROSCOE Modernization Guide

TSO/ISPFApplication/Application Enviroment

CA ROSCOE is a tso/ispf product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

CA ROSCOE is an online environment for z/OS, providing an interactive interface similar to TSO.

Configuration is managed through configuration files that define user profiles and system parameters.

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 CA ROSCOE?

CA ROSCOE is an online environment for z/OS, similar to TSO, that allows users to interact with the operating system and applications. It uses the ROSCOE Programming Facility (RPF) scripting language.

What are some common commands in CA ROSCOE?

Common commands include LIST to display datasets, EDIT to modify files, SUBMIT to run batch jobs, and OUTPUT to view job output. RPF scripts are used for automating tasks.

How is CA ROSCOE configured?

CA ROSCOE uses configuration files to define user profiles, security settings, and system parameters. These files are typically maintained by system administrators.

What is RPF?

RPF is the primary scripting language. It is similar to REXX and CLIST. It allows users to automate tasks and create custom applications within the ROSCOE environment.

Technical

What are the basic syntax examples for common operations?

Basic operations include listing datasets using `LIST 'dataset.name'`, editing files with `EDIT 'dataset.name'`, and submitting jobs using `SUBMIT 'jobname'`. RPF scripts are executed using the `EXEC` command.

Does CA ROSCOE expose APIs?

CA ROSCOE does not expose standard APIs like REST or SOAP. Integration typically involves using RPF scripts to interact with other z/OS applications and systems.

What are the main system components?

The main system components include the ROSCOE nucleus, the command processor, and the RPF interpreter. These components communicate through internal system calls and data structures.

How does CA ROSCOE handle security?

CA ROSCOE relies on z/OS security features for authentication and authorization. It uses standard z/OS security products like RACF, ACF2, or Top Secret.

Business Value

What is the business value of CA ROSCOE?

CA ROSCOE provides a familiar online environment for z/OS users, improving productivity and efficiency. RPF scripting allows for automation of repetitive tasks.

How does CA ROSCOE reduce costs?

By automating tasks and providing a centralized interface, CA ROSCOE can reduce operational costs and improve overall system management.

How does CA ROSCOE integrate with other applications?

RPF scripts can be used to integrate CA ROSCOE with other z/OS applications, creating streamlined workflows and improved data exchange.

Security

What authentication methods are supported?

CA ROSCOE leverages z/OS security features, including RACF, ACF2, and Top Secret, for authentication and authorization. It supports access control lists (ACLs) to manage resource access.

What access control model is used?

CA ROSCOE uses the z/OS access control model, which includes access control lists (ACLs) to manage resource access. User permissions are defined and enforced by the underlying security system.

What encryption is used and where?

Encryption is typically handled by the underlying z/OS system. Data-at-rest encryption can be implemented using z/OS encryption facilities.

What audit/logging capabilities exist?

CA ROSCOE provides audit logging capabilities through z/OS System Management Facilities (SMF). These logs can be used to track user activity and system events.

Operations

What administrative interfaces are available?

CA ROSCOE provides administrative interfaces through TSO commands and ISPF panels. User management is handled through z/OS security products like RACF.

What are the main configuration parameters?

Main configuration parameters include user profile settings, security definitions, and system initialization parameters. These are typically stored in configuration files.

What monitoring/logging capabilities exist?

CA ROSCOE provides monitoring and logging capabilities through z/OS SMF and system logs. These logs can be analyzed to identify performance issues and security threats.

How is user management handled?

User management is primarily handled through z/OS security products such as RACF, ACF2, or Top Secret. These tools allow administrators to define user profiles, permissions, and access rights.

Ready to Start Your Migration?

Download our comprehensive migration guide for CA ROSCOE or calculate your ROI.

Calculate ROI