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 TSO Client feature
Use the TSO Client feature to perform DevOps Code ClearCase® operations on the distributed system without leaving the mainframe system environment.
Working with files
After you set up your environment, choose your view, and upload your files to the remote system, you can use the client component of TSO Client to perform basic file tasks with the files associated with your chosen view.
Checking out files, checking in files, hijacking files, and merging changes
This topic explains some of the things you need to consider when checking files in and out and provides links to instructions for checkout, checkin, hijack, merge, and undo checkout operations.
Checking out files - unreserved
You can check out files by using the TSO Client View Files List and File Actions panels.

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.
    - Quick reference for TSO Client
      This topic provides a synopsis of the functionality of TSO Client commands and panels.
    - Displaying TSO Client help
      This topic describes how to update your ISPF profile to display TSO Client helps. You need to do this task only if have used a previous version of z/OS® Extensions and your installation has upgraded to version 7.1.0.2.
    - Setting up your TSO Client environment
      Before you use TSO Client, customize your environment by performing these tasks.
    - Starting and stopping the server and client components of TSO Client
    - Working with views and streams
      Use the options on the View and Stream panel to select a view, create a stream, create a view, and synchronize a view with a stream.
    - Preparing to work with files
      After you set up your TSO Client environment and start the client component of TSO Client, you must complete these tasks before you can work with your files.
    - Working with files
      After you set up your environment, choose your view, and upload your files to the remote system, you can use the client component of TSO Client to perform basic file tasks with the files associated with your chosen view.
      - Locating files in a file list
      - Adding files to source control
      - Uploading files
      - Filtering file names
      - Filtering file states
      - Checking out files, checking in files, hijacking files, and merging changes
        This topic explains some of the things you need to consider when checking files in and out and provides links to instructions for checkout, checkin, hijack, merge, and undo checkout operations.
        Checking out files - reserved
        You can check out files by using the TSO Client View Files List and File Actions panels.
        Checking out files - unreserved
        You can check out files by using the TSO Client View Files List and File Actions panels.
        Hijacking a file
        This topic describes a TSO Client usage scenario that allows you to perform a hijack-like operation.
        Merging changes
        If you have hijacked or copied a file, you can use the ISPF compare tool to merge your changes with the current version of the file before checking it in.
        Checking in files
        You can check in files by using the TSO Client View Files List and File Actions panels.
        Undoing a checkout
        The undo checkout operation returns a file to checked-in status. Any changes you have made since checking out the file are discarded.
      - Copying a file
        z/OS® Extensions provides a copy operation that you can use to work on a file that is checked out by someone else.
      - Editing a file
        z/OS® Extensions provides an edit operation that you can use to edit files that are checked out, files that are not checked out, or view-private files. When used on a file that is under source control but is not checked out, this operation is similar to a hijack operation.
      - Working with previous file versions
        In addition to checking your files in and out, you can also use the client component of TSO Client to compare previous file versions and view the version history (version tree).
      - Deleting PDS members
        You can also use the client component of TSO Client to delete PDS members.
      - Compressing partitioned data sets
        You can use the client component of TSO Client to compress partitioned data sets.
      - Refreshing the View Files List panel
      - Adding attributes to files
        Use the aat command to add attributes to a file under source control.
      - Enable REXX Trigger
        Enabling a REXX trigger for TSO Client commands.
    - Query files
      Once you set up your environment and choose your view, you can use the client component of TSO Client to perform query tasks by specifying certain criteria.
    - Building with TSO Client
      You can create either a local or a remote build by using the TSO Client feature.
    - Getting help with errors
      TSO Client displays short and long error messages to help you troubleshoot problems.
    - Opening the TSO Client log file
      TSO Client records messages in a log file to help you troubleshoot problems.
  - 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

Checking out files - unreserved

You can check out files by using the TSO Client View Files List and File Actions panels.

About this task

In a multiview environment, you can request an unreserved checkout if someone else has checked out a file. If a successor version of the file is subsequently checked in, you might need to merge your changes with the successor version.

Note: Unreserved checkout is not supported in a single view environment. To support this action, your profile must specify ENABLE_MULTIVIEW TRUE.

Procedure

On the option line of the TSO Client Main Menu, type 4.
On the left side of the Dataset Action panel, under DSLIST, type s to select a data set.
The View Files List panel displays.
To check out files, do one of the following actions:
- Type cou next to the file name. TSO Client prompts you to type a descriptive comment.
  Note: If the content of the member and the content of the file in ClearCase® are different, and if the ENABLE_CHECKOVERWRITE option is enabled in your profile, then TSO Client prompts you to either overwrite the existing file or cancel the checkout operation. This action is similar to a hijack operation. For more information about the ENABLE_CHECKOVERWRITE option, see Profile parameters.
- Type s next to the file name, type cou on the option line of the File Actions panel, type a descriptive comment, and press Enter.
Note: SBC case characters are not supported in comments.
The State field is updated to reflect the action performed.
Note: When file names (not including file type extension) are greater than 8 characters long, the first 8 characters must be unique. Otherwise, they will be overlaid when uploaded into the same copy area PDS. This requirement is due to the MVS™ 8-character restriction for member names. Likewise, because of the ambiguity, the download of the member might not update the proper file.