Synchronizing Mainframe Members

The Synchronize Mainframe Members feature allows the user to specify whether IBM® AD Build must update against specific libraries, where to add/remove the related members in/from the project (that is, which virtual folder to use) and also which type of members IBM AD Build must use when you add members. The basic assumption is that the specified libraries do not contain members that do not need to be added even though they are there.

The Synchronize Members action can be performed against sources that are based on the Host Side and also locally on the PC Side (local/remote path).

The Synchronize Members action is run by using a configuration file that specifies what members of what type to be brought into which mapped virtual folder of the project. When you run Synchronize Members on a project, only the members that belong to libraries specified in the configuration file for this particular project is synchronized.

Note: When adding mainframe members, if the limit of 40000 members is reached, additional virtual folders are created at the project's level. They do not have correspondent on disk and they cannot be deleted manually from IBM AD Build Client. The additional virtual folders are different than the existing virtual folders by having a special naming convention, suffixed by @&@<incremental_number>. Examples of additional virtual folders for

zOS
Cobol

zOS Cobol@&@1

zOS Cobol@&@2

The Synchronize Members feature is activated from IBM AD Configuration Server.

For details on the syntax of the configuration file and an example, see Synchronize Members Configuration File Examples.

After the members’ synchronization process is finished, use Make to ensure that the analyses you ran are done on the current version of the mainframe sources (updated, added, or removed).