Managing Version Control › Secondary Server and Client Control Files

Secondary Server and Client Control Files

Version control on a CA SDM secondary server or client consists of one executable (pdm_ver) and a version control file (secondary.ver). If you want, you can create and maintain a second version control file to manage customizations: server_secondary_custom.ver.

The client software includes one executable, pdm_ver, and a default version file, default.ver. Version control automatically creates a second version file (custom.ver) on the client if a server_custom.ver file exists on the server. The two client version files track the versions of standard and customized components installed on the client.

The default setting of the ver_ctl Options Manager option is UPGRADE, causing version control to upgrade the secondary server when a discrepancy is detected. Version checking is performed only for secondary servers and remote clients (there is no need for version control on clients running on the primary server because the server contains the master copies of all components). Version control is always performed against the primary server. When a secondary server or client starts, it reads its version files and sends a message to the primary server listing all installed components and their versions. If a component version discrepancy occurs, the server determines its response by checking the ver_ctl option setting. The server response tells the client whether to continue, terminate, or upgrade components.

Note: Most clients receive a download of files and option variables upon initial startup. This reflects the options chosen by the administrator when the server was configured and options installed.