Creating a local property group for a user build

You can generate a local property group for a z/OS® project with Dependency Based Build (DBB) integration support or add DBB integration properties to an existing property group.

1. In the z/OS Projects view, right-click a local z/OS project that has DBB integration support, and then select Dependency Based Build > Generate a Local Property Group.
2. In the Generate a Local Property Group window, select the language support tabs you want to include in the property group.
   Tip: After the property group is generated, you can add Assembler support to it:

   1. In the Property Group Manager view, double-click the generated property group. It opens in the property group editor.
   2. Click the Categories tab.
   3. Click Local Assembler Settings and then save the property group.
3. Optional: To generate a user build property group from an existing local property group, click Browse and then select the property group you want to use.
   Choosing this option creates a copy of the selected property group and updates it with the user build dependencies. The property group copy is named after the project.
4. You can add paths to any local or remote dependencies that are not in the Git repository. If the Git repository contains multiple dependency files with the same name in different folders, you need to add these folders to the SYSLIB or local macro libraries in the order that you want the folders to be searched.
5. To add remote libraries to the property group, do these steps:
   1. In the Property Group Manager view, double-click the generated property group. It opens in the property group editor.
   2. Click the COBOL, PL/I, or Assembler tab.
   3. Open Copy Libraries, Include Libraries, or Remote Macro Libraries page
   4. From the Connection name list, choose a remote system.
   5. Click Add, Edit, or Remove to add copy, include, or macro libraries to the table, edit the entries in the table, or remove entries from the table.
      When you click Add or Edit, a window opens prompting you for a library name and a data set name.
   6. In the Library name field, type a name for the library.
      For example, type SYSLIB.
      • The table can have only one SYSLIB entry.
      • The table allows for the specification of a name other than SYSLIB for the library, as in the following examples. The editor searches the partitioned data sets defined in MYLIB instead of SYSLIB. If you have the following statements in COBOL or PL/I code you can use this field to define the library name MYLIB.
        • COBOL example: COPY MYFILE OF MYLIB.
        • PL/I example: %INCLUDE MYLIB (MYFILE);
      • If the library name is set to JCLLIB and the path is specified as **, the system searches for the include library using the datasets defined in the JCL JOB Card. The search order is as follows:
        • JCLLIB
        • JOBLIB
        • PROCLIB
        • SYS1.PROCLIB
        • The system extracts and searches the datasets specified in these statements. If a dataset name is referenced using a variable declared by a SET statement within the same JOB Card, the variable is resolved before performing the search.
   7. In the Library path field, type one or more partitioned data set names to search and click OK.
      Separate multiple data set names with a space. The editor searches the data sets in the order listed.
6. Save the property group.