Setting up a workspace for editing source code

Edit online

Learn what tasks you need to complete to setup your workspace for editing source code in COBOL, High-level Assembler, JCL, PL/I, or REXX. Link to the guide builder to generate a documentation set that is tailored to these tasks and to the languages and editors you need to use.

When you are ready to generate the documentation set, click this link:
Open Guide Builder to Build My Documentation

Roadmap

Use this roadmap to understand the tasks you must complete to set up a development environment for editing source code.

  1. Verify installed components: If your source files are located in a Git repository, a Jazz® repository, or on z/OS® under control of the CA Endevor source control manager, verify that the features necessary for accessing these repositories are installed with the product.
  2. Set up access to your source files. The product provides access to source files in several locations:
    • On a z/OS system
    • In a Git repository
    • In a Jazz repository
    • On a z/OS system under CA Endevor source control
  3. Set up a property group. Property groups provide a central location for settings that the product uses for several functions. Some common tasks in the development of COBOL applications use property group settings:
    • Editing source files
    • Generating JCL
    • Compiling source code
    • Running applications
    Property groups support other functions as well, such as unit testing, debug, and code coverage, but this section describes property group settings for editing, compilation, and runtime.
  4. Create a z/OS project. Although you can work with your source files directly in an MVS file system or source control repository, adding them to a z/OS project has several benefits:
    • You can include in the project only the exact resources you need.
    • z/OS projects are enabled for a number of product features, such as integration with EGit, IBM® Dependency Based Build, Engineering Workflow Management, and Z Systems Development and Test Environment.
    • z/OS projects are shareable either through export and import or through the push-to-client feature.
    The product provides several methods for creating z/OS projects depending on where your source files are located.
  5. Set up the editors. The product provides editors that are optimized specifically for development in each of these source languages: COBOL, High-Level Assembler, JCL, PL/I, and REXX. The workbench Preferences window contains several pages for setting options for editor functions.