Configuring General Settings

Set required BRP initialization values on the General tab. The settings are described in the table below.
Setting Description
EA Install Path Specifies the path of the EA installation folder.
BRP Install Path Specifies the path of the BRP installation folder. This folder must contain the Reports, PreparedSources, Staging, Utility, and Working folders. Use override parameters for folders in a different location.
Workspace Path Specifies the path of the folder for the workspace to be refreshed. This folder is at the same level as the workspace (.rwp) file.
Location of Source Files Specifies the path of the folder that contains all of your sources to register. Then running the BRP for the first time will register and analyze all sources in the specified folder and subfolders. After the initial registration, running the BRP will update the sources the same way as the Source Synchronization feature.

After you have specified the location and run BRP, the value of the option will be erased, so if you need to register more files from a different folder, make sure you specify the new location for this option again.

Note: This option is only for in-place registration.
Obsolete Processing Check this box to turn on obsolete processing. Obsolete processing automatically determines which source files are no longer part of a "live" application and moves them to another project. Sources are determined to be obsolete by virtue of being absent from the set of incoming sources for a BRP run.
Obsolete Project If Obsolete Processing is selected, specifies the project to which obsolete source files will be moved.
Obsolete Exclusions File      If Obsolete Processing is selected, specifies a text file that lists files that should be ignored during obsolete processing. This mechanism is intended to avoid having EA generated or provided files classified as obsolete. For example, EA-provided system copybooks or DASDL-generated copybooks. The text file should be formatted with a single file name per line. This mechanism is also useful when there are sources that are particularly difficult to provide on an ongoing basis or if a source is generated during runtime in the application.