As you define your projects, instead of trying to group all of your programs into a single, large workspace, create logical groupings of related programs. Because the AcuBench project and workspace concepts are entirely virtual, these groupings do not affect the creation of object files or the execution of the final application. Placing extremely large numbers of programs into a single workspace, however, can have a negative impact on AcuBench's performance, and can make managing the version control repository more complicated.
Before importing a project into the version control repository, consider the following:
Creating and tracking customized project modes can help to create consistency in the building and testing process. Since .ini files created in the Tools > Options interface contain the defaults for screens, reports, and controls, maintaining a centralized .ini can help with consistency management. For more information about creating project modes, see Project Settings. For more information about the .ini file, and the Tools > Options interface used to modify the file, see The Tools > Options Dialog.
Because all of the information generated into AcuBench COPY files is stored in the program structure file (.psf), which must be tracked if you are using AcuBench code generation, it is more efficient to generate separate COPY files with version control. If all code is generated into the source (.cbl) file, then the same information is being tracked twice.
Do you plan to use the default directories created by AcuBench, or are you using an existing directory structure? Keep in mind that some version control systems require all project files to reside a single directory structure (a main project directory plus subdirectories).