Jump to main content
HCL Logo Product Documentation
Customer Support Software Academy Community Forums
DevOps Code ClearCase version 11.0.0
  • Overview
  • Installing
  • Upgrading and migrating
  • Administering
  • Developing
  • Managing change and releases
  • Integrating
  • Tutorials
  • Extending product function
  • Reference
  • Glossary
  1. Home
  2. Installing

    Learn how to install the product.

  3. Installing and using z/OS® Extensions

    z/OS® Extensions is a component of IBM® Rational® ClearCase® that enables mainframe users to perform select DevOps Code ClearCase operations. z/OS Extensions include Remote Build, TSO Client, and ClearCase RAM (CCRAM).

  4. Configuring z/OS® Extensions

    z/OS® Extensions include basic configuration tasks required to use the z/OS Extensions features and some optional configuration tasks. Some of these options need to be configured by an administrator and some need to be configured by individual users for their client environment.

  5. Working with the Role-based Resource Manager

    The Role-based Resource Manager adds a layer of security for accessing system resources.

  • Installing

    Learn how to install the product.

    • DevOps Code ClearCase® Release Notes

      The release notes provide you with information that you might want to know before you install the product.

    • Deploy DevOps Code ClearCase®

      Read these topics for information about planning, installing, and configuring your DevOps Code ClearCase® deployment.

    • Use IBM® installation and packaging utilities

      Use IBM installation and packaging utilities to download and install IBM® software.

    • Installing and using z/OS® Extensions

      z/OS® Extensions is a component of IBM® Rational® ClearCase® that enables mainframe users to perform select DevOps Code ClearCase operations. z/OS Extensions include Remote Build, TSO Client, and ClearCase RAM (CCRAM).

      • Reading roadmap
      • Installing z/OS® Extensions

        Use these instructions to plan for, complete, and check the progress of installation and configuration tasks for z/OS® Extensions.

      • Configuring z/OS® Extensions

        z/OS® Extensions include basic configuration tasks required to use the z/OS Extensions features and some optional configuration tasks. Some of these options need to be configured by an administrator and some need to be configured by individual users for their client environment.

        • Configuring the Remote Build server

          This topic describes how to configure and run a Remote Build server. It also explains how to verify client/server communication.

        • Configuring the TSO Client feature

          This topic describes TSO Client configuration tasks.

        • Installing and configuring CCRAM

          This topic provides instructions for installing and configuring ClearCase® Repository Access Manager (CCRAM).

        • Using secure password protection

          Secure password protection stores encrypted passwords for use by the Remote Build client and the server component of the TSO Client feature.

        • Working with the Role-based Resource Manager

          The Role-based Resource Manager adds a layer of security for accessing system resources.

          • Activating the Role-based Resource Manager

            The Role-based Resource Manager is activated by a parameter to the Remote Build server. The server option is specified in the server startup JCL RCCRUNM.

          • Managing user activities

            The administrator for the Remote Build server can use profiles in the FACILITY class to enable resource managers to control a user’s ability to perform an action.

          • Using the Role-based Resource Manager

            Your security administrator now controls access to certain z/OS® resources (typically a set of MVS™ data sets); the security administrator controls access to multiple sets of Remote Build invokers based on user roles (such as development, test, production, etc.). The administrator enables such controls for each role through one instance of Remote Build server. Data sets controlled this way cannot be accessed directly through an MVS batch job or through ISPF.

      • Using the Remote Build feature

        The Remote Build feature submits build requests from DevOps Code ClearCase® client platforms running on Windows®, Linux®, and the UNIX® system to z/OS® (MVS™ and z/OS UNIX System Services). This feature consists of both server and client components.

      • Using the TSO Client feature

        Use the TSO Client feature to perform DevOps Code ClearCase® operations on the distributed system without leaving the mainframe system environment.

      • Managing builds with impact analysis

        z/OS® Extensions provides impact analysis tools that you can use to manage COBOL, PL/I, and High Level Assembler (HLASM) builds.

      • Using the TSO Client API

        The TSO Client API enables you to perform Remote Build functionality by using a TSO Client API application. Use the TSO Client API to create your own custom TSO Client calls to a distributed system running DevOps Code ClearCase®.

      • Using the ClearCase® Repository Access Manager

        ClearCase® Repository Access Manager (CCRAM) provides a seamless interface that enables those who use IBM® Rational® Developer for System z® to access assets stored in ClearCase.

      • Automating builds with parameterized build scripts

        Parameterized build is a script-based, sample-driven approach to automating Remote Build scripts. It provides you with sample scripts that you can use as a starting point for developing your own approach to automating Remote Build scripts. These sample scripts are provided as-is and require customization and alteration before they can be used in your z/OS® Extensions environment.

      • Reference

        The reference topics in this section provide material that is helpful while using z/OS® Extensions features.

Working with the Role-based Resource Manager

The Role-based Resource Manager adds a layer of security for accessing system resources.

About this task

The following topics explain how to activate and use the Role-based Resource Manager:
  • Activating the Role-based Resource Manager
  • Managing user activities
  • Using the Role-based Resource Manager
  • Activating the Role-based Resource Manager
    The Role-based Resource Manager is activated by a parameter to the Remote Build server. The server option is specified in the server startup JCL RCCRUNM.
  • Managing user activities
    The administrator for the Remote Build server can use profiles in the FACILITY class to enable resource managers to control a user’s ability to perform an action.
  • Using the Role-based Resource Manager
    Your security administrator now controls access to certain z/OS resources (typically a set of MVS data sets); the security administrator controls access to multiple sets of Remote Build invokers based on user roles (such as development, test, production, etc.). The administrator enables such controls for each role through one instance of Remote Build server. Data sets controlled this way cannot be accessed directly through an MVS batch job or through ISPF.
Related tasks
  • Using secure password protection
Related reference
  • Sending user IDs and passwords

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.

Rate this topic


Comment on this topic
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences