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. 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.

  5. Configuring parameterized build on UNIX®

    The topics in this section explain how to set up the parameterized build sample scripts to run on a UNIX® server and how to set up a UNIX ClearCase® client to run the scripts.

  6. Setting up the UNIX® environment

    Before users can submit parameterized build scripts, an administrator needs to set up the UNIX® environment.

  • 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.

      • 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.

        • Configuring parameterized build on Windows®

          The topics in this section explain how to set up the parameterized build sample scripts to run on a Windows® server and how to set up a Windows ClearCase® client to run the scripts.

        • Configuring parameterized build on UNIX®

          The topics in this section explain how to set up the parameterized build sample scripts to run on a UNIX® server and how to set up a UNIX ClearCase® client to run the scripts.

          • Setting up the UNIX® environment

            Before users can submit parameterized build scripts, an administrator needs to set up the UNIX® environment.

            • Locate the installed build scripts to a shared directory

            • Generate a user ID table

              A user ID table maps all users' UNIX® IDs to the TSO login IDs used to log in to the Remote Build server.

          • Designing a project life cycle map
          • Defining variables for the view elements

            Assign type attributes to each element to identify what language the element uses and whether a precompiling process is required by the element.

          • Setting up a test environment
          • Parameterized build scripts for UNIX®
        • Using the parameterized build sample scripts

          You can use the parameterized build sample scripts from the ClearCase® or Windows® explorer, UNIX® command line, TSO Client, or Rational® Developer for System z® or Eclipse platforms.

      • Reference

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

Setting up the UNIX environment

Before users can submit parameterized build scripts, an administrator needs to set up the UNIX® environment.

Procedure

To set up the UNIX environment for parameterized build, do these steps. Each of the steps in this procedure provides a link to further instructions.
  1. Locate the installed build scripts to a shared directory.
  2. Generate a user ID table.

What to do next

Next step: Define the user profile

Rate this topic


  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences