Welcome
Installing
Learn how to install the product.
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).
Reference
The reference topics in this section provide material that is helpful while using z/OS® Extensions features.
TSO Client API Functions

Overview
Learn general information about the product.
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.
  - Reference
    The reference topics in this section provide material that is helpful while using z/OS® Extensions features.
    - Remote build messages
      This section explains remote build messages and provides some diagnostic information for people who write BCL scripts.
    - TSO Client API Functions
      - TSO API functions by category
        A list of TSO Client API functions by category.
      - Commonly used parameters
      - RCCADD
        RCCADD adds the list of specified files to the specified DevOps Code ClearCase® source file directory.
      - RCCCI
        RCCCI checks in the list of files identified by the fully qualified file names.
      - RCCCID
        RCCCID checks in the specified directory.
      - RCCCO
        RCCCO checks out the files specified by the fully qualified file names.
      - RCCCOD
        RCCCOD checks out the specified directory.
      - RCCDIFF
        RCCDIFF determines the difference between two versions of a specified file.
      - RCCDIFFP
        RCCDIFFP determines the difference between the current and previous versions of the file identified by the fully qualified name.
      - RCCDOWN
        RCCDOWN downloads a list of files from a single mainframe PDS.
      - RCCGTDIR
        RCCGTDIR gets the current directory on the distributed system.
      - RCCLACT
        RCCLACT lists the activities for a given view on the distributed system.
      - RCCLFILE
        RCCLFILE lists files of a pattern and specified view.
      - RCCLTREE
        RCCLTREE lists the version tree for a file identified by a fully qualified file name on the distributed system. All versions of the file are listed.
      - RCCLVIEW
        RCCLVIEW lists the views on the distributed system.
      - RCCMACT
        RCCMACT creates a DevOps Code ClearCase® activity for a given view on the distributed system.
      - RCCSECF
        RCCSECF adds a host name, user name, and password to the SECF file with the password encrypted.
      - RCCTSTC
        RCCTSTC tests the connection to the distributed system.
      - RCCUALOC
        RCCUALOC creates, allocates, or frees commonly used data sets and associated DD names used by other API functions.
      - RCCUCO
        RCCUCO cancels check out for the list of files identified by the fully qualified file names.
      - RCCUECMD
        RCCUECMD invokes RCCTSOC.
      - RCCULOG
        RCCULOG writes log entries for running an API function.
      - RCCUMSG
        RCCUMSG extracts and returns a requested error message from the message file.
      - RCCUP
        RCCUP uploads a list of files to a mainframe PDS.
      - RCCVACT
        RCCVACT validates the activity name argument. A valid activity name may not contain blanks.
      - RCCVDUN
        RCCVDUN validates the distributed user name argument. A valid user name may not contain blanks. A valid user name is required to access authentication mode 2.
      - RCCVDUP
        RCCVDUP validates the distributed user password argument. A valid password may not contain blanks.
      - RCCVFQFT
        RCCVFQFT validates the FullyQualifiedFileType argument.
      - RCCVHOST
        RCCVHOST validates the host argument.
      - RCCVLFN
        RCCVLFN validates the listOfFullyQualifiedFileName argument.
      - RCCVNAH
        RCCVNAH validates the newActivityHead argument.
      - RCCVPDS
        RCCVPDS validates the localPDS argument. A valid local PDS name must not contain blanks.
      - RCCVPLTF
        RCCVPLTF validates the platform argument.
      - RCCVPORT
        RCCVPORT validates the port argument.
      - RCCVTSCD
        RCCVTSCD validates the TSCdirectory argument.
      - RCCVTYPE
        RCCVTYPE validates the CCtype argument.
      - RCCVVDIR
        RCCVVDIR validates the distributedViewDirectory argument.
      - RCCVVERS
        RCCVVERS validates the fullyQualifiedVersionOfaFile argument specified.
      - RCCVVIEW
        RCCVVIEW validates the view argument.
      - RCCVVTYP
        RCCVVTYP validates the viewType argument.
      - Example of a log entry
        The following syntax is an example of a log entry resulting from the successful execution of the RCCCO API function.
    - TSO Client API Messages
      This section explains TSO Client API messages and provides some diagnostic information for people who debug programs.
Upgrading and migrating
Learn how to upgrade and migrate data for the product.
Administering
Learn how to administer the product.
Developing
Learn how to develop software with DevOps Code ClearCase® and ClearCase Remote Client.
Managing change and releases
Learn how to manage change and release in the product.
Integrating
Learn how to integrate DevOps Code ClearCase® with other products.
Tutorials
Complete tutorials with specific learning objectives for the product.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.
Glossary

TSO Client API Functions

This reference section provides detailed information about the available API functions and how to use them. The API function descriptions in this section us the following syntax notations:

If an argument is required, it appears in italics, like this: host.
If an argument or series of arguments is enclosed in brackets ([ ]), the arguments of one of the alternatives inside the brackets can be explicitly specified or omitted. No default is implied for the omitted element.

High-level API functions

The name of each high-level TSO Client API function begins with the three-character prefix RCC; for example, RCCTSTC and RCCLVIEW.

Low-level API functions

The low-level functions used to validate individual arguments syntactically have a “RCCV prefix; for example, RCCVPLTF, RCCVHOST, and RCCVPORT. The high-level functions use the low-level functions to validate arguments before performing the requested functions. You can also invoke these argument validation functions from user programs.