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).
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 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 a test environment
Submitting multiple COBOL programs linked into one module

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.
    - 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.
      - 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
        Submitting a single program
        Submitting a single program with a copybook
        Submitting multiple COBOL programs
        Submitting multiple COBOL programs linked into one module
      - 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.
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

Submitting multiple COBOL programs linked into one module

Before you begin

Before performing this sample parameterized build request, you need to ensure that the test programs have been set up as described in Setting up a test environment.

About this task

Use sample programs pbtest.cbl and pbtest3.cbl and the link control file pbmain.link to perform this test case. This test case assumes both pbtest.cbl and pbtest3.cbl have been compiled and located in USERID.XOBJLIB. The link control file is uploaded to the z/OS® system with the name PBMAIN located in USERID.XLOADLIB.

Procedure

Edit the link control file USERID.XLOADLIB(PBMAIN) on the z/OS® system if needed.
The following is the sample link control PBMAIN:
```
INCLUDE OBJLIB(PBTEST)
INCLUDE OBJLIB(PBTEST3)
ENTRY PBTEST
NAME PBTEST(R)
```
Add the type attribute LNKDECK to pbtest.cbl and assign the value PBMAIN to LNKDECK as described in Defining variables for the view elements.
Issue the following two commands from the UNIX® command line:
```
perl  bccPmbld_main.pl -i /userProfilePath/profileUSER -d /viewElementDirectoryPath pbtest.cbl

perl  bccPmbld_main.pl -i /userProfilePath/profileUSER -d /viewElementDirectoryPath pbtest3.cbl
```
In this command:

userProfilePath

Is the location of the profileUSER file.

viewElementDirectoryPath

Is the location of the parameterized build sample programs.
Verify that pbtext.cbl and pbtest3.cbl are build successfully.
Issue the following command from the UNIX® command line:
```
perl  bccPmbld_main.pl -l -i /userProfilePath/profileUSER -d /viewElementDirectoryPath pbtest.cbl
```
In this command:

userProfilePath

Is the location of the profileUSER file.

viewElementDirectoryPath

Is the location of the parameterized build sample programs.
Verify the following expected results:
- The following files are found in the OUTPUT_LOG location defined in profileUSER:
  - userid_pbtest_linkjob.log
  - userid_pbtest_rccbuild.log
- The following files are found in the OUTPUT_LIST location defined in profileUSER:
  - userid_sourceFile_lked.sysprint, where userid is the user ID of the person submitting the parameterized build request and sourceFile is the name of the file for which the request was submitted
- The following files are found in the viewElementDirectoryPath:
  - pbtest_lnkbatch.jcl
- The return code for MVS™ step LKED is '000000'.