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).
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.
Submitting remote build requests using rccbuild
This topic describes rccbuild command options and processing.
Quick reference for rccbuild
The following table provides a synopsis of the functionality of rccbuild commands, options, and arguments.
Specifying code pages
Use the -k, -r, and -ke options to specify code pages.

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.
    - Setting server connection options
    - Submitting remote build requests using rccbuild
      This topic describes rccbuild command options and processing.
      - Using previous versions of the Remote Build server
      - Repeating rccbuild command options
        You can repeat rccbuild command options. This topic describes the effect of repeating options.
      - Quick reference for rccbuild
        The following table provides a synopsis of the functionality of rccbuild commands, options, and arguments.
        Sending user IDs and passwords
        Use the –au, –ap, and -rl options to pass user IDs and passwords to the server.
        Sending ClearQuest® credentials
        Use the –qu, –qp, and -qdb options to ClearQuest® credentials to the server.
        Specifying a worker job name
        Use the -j option to specify the text that is used in constructing the JCL job name for the worker job.
        Sending worker job account
        Use the -ja option to specify the text that is used in constructing the JCL job account information for the worker job.
        Obtaining the Remote Build client version
        Use the -version option to obtain the Remote Build client version.
        Specifying a Remote Build server
        Use the -h option to specify the Remote Build server to process a build request.
        Pinging a Remote Build server
        Use the -testServer option to ping a Remote Build server.
        Specifying a local build script
        Use the -f and -b options to specify a local build script.
        Specifying a server-side build script
        Use the -b option to specify a server-side build script.
        Specifying a server-side build script in a nondefault PDS
        Use the -proclib option to specify a server-side build script in a nondefault PDS.
        Specifying client-based source files
        Use the -i and -d options and arguments to specify client-based source files.
        Returning output files to the client computer
        Use the -o option to return output files to the client computer.
        Keeping output files on the server
        Use the -on option to keep output files on the server.
        Specifying the directory for a z/OS® UNIX® System Services build
        Use the -loption to specify the directory for a z/OS® UNIX® System Services build.
        Specifying code pages
        Use the -k, -r, and -ke options to specify code pages.
        Specifying escape codes
        Use the -ec option to specify escape characters for file transfers.
        Setting message verbosity
        Use the -V option to set message verbosity.
        Setting the condition for valid return codes
        Use the following options and arguments to set the condition for valid return codes. After each job step is executed, the system performs the condition test against the return codes from completed job steps. If a job step fails the condition test, the job will be terminated.
        Specifying a timeout factor
        Use the -T option to specify a timeout factor.
        Setting environment variables
        Use the -v option to set environment variables.
        Passing variables to build scripts
        Use the -p option to pass variables to build scripts.
        Specifying a prefix for messages returned to the client log file
        Use the -P option to specify a prefix for messages returned to the client log file.
    - Working with build scripts
      The build script for the Remote Build feature of z/OS® Extensions is called BCL (Build Control Language). It is similar to z/OS MVS™ JCL in appearance and, for many basic parameters and options, it is identical to MVS JCL.
    - Using Remote Build with the clearmake command
      The clearmake command is the DevOps Code ClearCase® variant of the Linux® and the UNIX® system make command. Using clearmake, you can audit remote builds and trigger future build events.
    - Sample build requests
      The topics in this section illustrate how to submit two different Remote Build requests using the client command rccbuild.
  - 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.
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

Specifying code pages

Use the -k, -r, and -ke options to specify code pages.

Syntax

–k client_codepage –r server_codepage –ke runtime_codepage

client_codepage: Specifies the code page for the input, output, and build script files on the client. Code page conversion occurs only on text files. The default code page for the Windows® client is IBM-850. The default for Linux® and the UNIX® system is ISO-8859-1.
server_codepage: Specifies the code page used on the server. The default code page is IBM-1047.
runtime_codepage: Specifies the code page for the distributed system's locale. This option defaults to the same value as is specified with the client codepage -k option.

Platforms

z/OS® MVS™, z/OS® UNIX® System Services

Example

Note: The examples in this topic are for illustrating command syntax. You need to substitute values appropriate to your site for the command parameters.

If Taiwanese Windows® is used as the distributed system and the code pages of the input, the output, and the build script files are UTF-8, specify the following the code page options:

-k UTF-8 -r IBM-937 -ke IBM-950