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

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

  5. TSO Client API Messages

    This section explains TSO Client API messages and provides some diagnostic information for people who debug programs.

  • 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 Client API Messages

          This section explains TSO Client API messages and provides some diagnostic information for people who debug programs.

          • RCCE-611

            Invalid APIfunc request. Required argname argument was not specified. Processing is terminated

          • RCCE-612

            Invalid APIfunc request. An invalid argname argument argvalue was specified. Processing is terminated.

          • RCCE-614

            Nonzero return code from command name in APIfunc. Processing is terminated.

          • RCCE-615

            Allocation for required data set dsname failed. Processing is terminated.

          • RCCE-616

            An invalid number of arguments was passed to APIfunc. Processing is terminated.

          • RCCE-617

            An invalid file type filetype was specified as part of the fullyQualifiedFileName argument. Processing is terminated.

          • RCCE-618

            Multiple file types filetype are not allowed in the listOfFullyQualifiedFileName argument. Processing is terminated.

          • RCCE-619

            File type filetype is not specified in the fullyQualifiedFileType argument. Processing is terminated.

          • RCCE-620

            Only UCM CCtype is allowed to create an activity. Processing is terminated.

          • RCCE-621

            Multiple directories directory are not allowed in the listOfFullyQualifiedFileName argument. Processing is terminated.

          • RCCE-622

            File name filename is not allowed in the listOfFullyQualifiedFileName argument. Processing is terminated.

          • RCCE-698

            Internal error. APIfunc passed an invalid message severity severity to this function.

          • RCCE-699

            Internal error. APIfunc passed an invalid message number number to this function.

TSO Client API Messages

This section explains TSO Client API messages and provides some diagnostic information for people who debug programs.

  • RCCE-611
  • RCCE-612
  • RCCE-614
  • RCCE-615
  • RCCE-616
  • RCCE-617
  • RCCE-618
  • RCCE-619
  • RCCE-620
  • RCCE-621
  • RCCE-622
  • RCCE-698
  • RCCE-699
  • RCCE-611
    Invalid APIfunc request. Required argname argument was not specified. Processing is terminated
  • RCCE-612
    Invalid APIfunc request. An invalid argname argument argvalue was specified. Processing is terminated.
  • RCCE-614
    Nonzero return code from command name in APIfunc. Processing is terminated.
  • RCCE-615
    Allocation for required data set dsname failed. Processing is terminated.
  • RCCE-616
    An invalid number of arguments was passed to APIfunc. Processing is terminated.
  • RCCE-617
    An invalid file type filetype was specified as part of the fullyQualifiedFileName argument. Processing is terminated.
  • RCCE-618
    Multiple file types filetype are not allowed in the listOfFullyQualifiedFileName argument. Processing is terminated.
  • RCCE-619
    File type filetype is not specified in the fullyQualifiedFileType argument. Processing is terminated.
  • RCCE-620
    Only UCM CCtype is allowed to create an activity. Processing is terminated.
  • RCCE-621
    Multiple directories directory are not allowed in the listOfFullyQualifiedFileName argument. Processing is terminated.
  • RCCE-622
    File name filename is not allowed in the listOfFullyQualifiedFileName argument. Processing is terminated.
  • RCCE-698
    Internal error. APIfunc passed an invalid message severity severity to this function.
  • RCCE-699
    Internal error. APIfunc passed an invalid message number number to this function.

Rate this topic


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