Setting preferences for a zAppBuild user build

Dependency Based Build (DBB) uses three Preferences pages to configure user build operations. This topic describes these pages and the preferences you can set on each one.

For information about how these preferences work together during a remote build operation, see Preserving integrity of binary files.

Dependency Based Build

The DBB preferences set default values for user build configuration and runtime options. To open this page, select Dependency Based Build in the navigation pane of the Preferences window. Then, to open the preference settings for the user build wizard, select Wizard from the User build method list.

DBB_Home: Specify the path to the DBB installation folder on z/OS UNIX System Services. Consult your system administrator for the path.

Groovy version: Specify the path to Groovy used by DBB. Consult your system administrator for the path.

Specify file extensions and their corresponding data set qualifiers to be used during user builds: Use this table to map local file extensions to remote data set low-level qualifiers.

Seconds until DBB timeout: Specify how long the local process waits for a reply from the DBB server before timeout.

Support error feedback: Select this checkbox to generate error feedback. Error and warning entries are added to the Remote Error List view.
Tip: For user builds with zAppBuild, this field applies only to Assembler files. For COBOL and PL/I files, use the Support error feedback checkbox in the property group.
Note: Support error feedback is not applicable when multiple programs are selected for a user build.

Overwrite temporary log files: Select this checkbox if you want to enable this option.

Reload copybooks for user build: An option Reload copybooks for user build is available. When selected, this forces the system to re-parse the copybooks even if cached data is available.

You can manually trigger a re-parse of copybooks by selecting the Reload copybooks for user build checkbox in the DBB Preferences page.

Automatically overwrite existing files: Select this checkbox to skip confirmation prompts and automatically overwrite existing files when re-triggering zAppBuild.

Git Remote Integration

The Git remote integration preferences define how Dependency Based Build user build operations maintain file encoding and content type information for files that are transferred from a local Git repository to a remote system. To open this page, select Team > Git > Remote Integration in the navigation pane of the Preferences window.

Attributes file: Specify the file that contains host encoding and content type information used for file transfers from the local Git repository to the remote system. The file location is assumed to be in the same working tree as the file being built.

Enable scanning of attributes file for changes: When this option is selected, the product monitors the attributes file to detect changes to files and file encoding and content type information in the Git repository. When changes are detected, the product updates the persistent properties of the local files with these changes.

Local encoding and content type attributes take precedence over scanned attributes: When this option is selected, any encoding and content type information that is specified on the Local Content Details page of the local file Properties window takes precedence over settings detected in the attributes file.
Note: To specify local encoding and content type information on the Local Content Details page, you must enable the Team > Remote Integration > Enable local file specification of attribute information preference setting.

Team Remote Integration

The team remote integration preferences define default record lengths for binary files that are transferred from a local system to a remote system during a DBB user build operation, and to enable local override of the defaults. To open this page, select Team > Remote Integration in the navigation pane of the Preferences window.

The default settings for binary file record length assign a record length of 80 to all file types. To add entries for specific file types:
  1. Click * in the Pattern cell and change the value to a different file name pattern, such as, *.groovy.
  2. Click 80 in the Record length cell and change the value to a number appropriate for the file type.
  3. Click Apply.
  4. Click the second row in the table, and then click Add. A new row with Pattern * and Record length 80 is added to the table.
    Tip: The Add button is not enabled until you click Apply and then click a new row.
  5. Modify the new row as needed, then click Apply, click the third row, and click Add.
  6. Continue these steps until the table contains all of the file patterns and record lengths you need. The last row of the table always contains Pattern * and Record Length 80.
The result of this procedure is to assign the specified record lengths to the file patterns you add, and then to assign record length 80 to any remaining binary files that do not match any of the defined file patterns.

Pattern and Record length: Use this table to define default record lengths for file name patterns on the local system. By default all local binary files have a record length of 80. Click the Add, Remove, Up, and Down buttons to edit and reorder the table rows.

Enable local file specification of attribute information: Select this option to enable local override of the default record lengths. When this option is enabled, you can use the Local Content Details page of the file Properties window to set the file content type (text or binary), the remote encoding, and the record length for binary files.

What to do next

Using the user build wizard (zAppBuild)