Administering Repositories

Administering Repositories

Note: The instances of Linux in this section refer to both the Linux and zLinux operating environments.

This section contains the following topics:

CA Harvest SCM Repositories

Create a Repository

Load Repositories

How to Move, Remove, or Rename an Item or Item Path

Create an Item Path

Delete an Item Path

Delete an Item

Duplicate a Repository

Delete a Repository

CA Harvest SCM Repositories

A repository is a collection of items and item paths. When you installCA Harvest SCM, no repositories exist in the installation. Administrators create repositories and control access to them.

Administrators can decide how they want to divide an application's code, using different repositories to build different products. For example, a site might have a repository for shared code (SHARED), a repository for application one (APP1), and another for application two (APP2). Projects that support a release of application one would be based on the SHARED and APP1 repositories, whereas projects associated with application two would be based on APP2 and SHARED.

The Repositories tab on the Administrator application shows all the repositories that you have access to. Expanding a repository shows the items and item paths that make up the repository. For every item and item path, the name that is displayed reflects the name given to the latest trunk version of the item and item path, respectively. When you navigate to an item path, you see the items whose latest trunk versions are below that path.

Repository Properties lets you create and define a CA Harvest SCM repository. You can also create an empty repository with all attributes copied from a source repository. The Duplicate Repository dialog lets you duplicate a CA Harvest SCM repository.

More information:

Load Repositories

File Extensions

Significant differences exist between UNIX, Windows, and z/OS operating systems that can affect updating files on these operating systems. Decide how you want to handle file conversion issues when you intend to use mixed clients. You must specify that CA Harvest SCM convert the end-of-line and end-of-file markers. The File Extensions tab of the Repository Properties dialog lets you specify how CA Harvest SCM performs these conversions. Because different repositories may contain different types of code, you can specify different conversion rules for each repository. In a repository, conversions are based on file type (extension). CA Harvest SCM does not automatically execute any file conversions on Windows clients because such a conversion can have negative effects on binary files. When you are loading a repository with files that are in Windows format, and that UNIX clients do not need to access, no conversion is needed.

Note: On the Workbench, you can display file type attributes (binary or text). For information about displaying file type attributes, see the Workbench User Guide.

Case Issues

CA Harvest SCM handles file character case as follows:

• Windows client files checked in to a Windows repository retain their original case, and checking in files of the same name regardless of case updates them. For example, File.c is stored in the repository exactly as loaded, and Windows client files FILE.C and file.c are interpreted as being the same file.
• Windows client files checked in to a UNIX repository are stored “case-aware.” For example, FILE.C and file.c are interpreted as being the same file.
• UNIX client files checked in to a UNIX repository are stored “case sensitive.” For example, FILE.C and file.c are interpreted as different files.

To help ensure that files have acceptable case on both UNIX and Windows operating environments, users must verify the case on new files being introduced into the repository (using the Load Repository function or by checking in new items), regardless of the client (Windows or UNIX) they are using.

File Conversion

Before you load files from a Windows client into a UNIX-based repository or from a UNIX client to a Windows-based repository, decide how you want to handle file conversion issues.

• UNIX files use the line feed character for end-of-line markers.

  Because UNIX and Windows clients can share files stored in a UNIX-based repository, you can specify that files be converted to UNIX format when they are loaded or checked in. Then when a user checks out a file to a UNIX directory, the file appears as expected. When the user checks out the file again to Windows, the file appears in a Windows format.

• Windows files use a carriage return and line feed combination for end‑of-line markers.

  When a user checks out a file to a UNIX directory, a Windows file that is not converted to UNIX format has a ^M character at the end of every line. Such a file can still be edited and checked back in without any problems by ignoring the ^M at the end of each line.

  If you edit files exclusively on Windows operating systems, these file conversions are not necessary, even when using a UNIX-based repository.

• If you use both UNIX and Windows clients, use the File Extensions tab of the Repository Properties dialog to select file options for the end-of-line conversion during check-in, check-out or load repository.

More information:

Create a Repository

Repository Access

When items are initially loaded, the user group Public, which includes all users, is granted view access to the items. You can use the Access tab of the Repository Properties dialog to change the user group access.

More information:

Controlling Object Access

Create a Repository

When you installCA Harvest SCM, repositories do not exist in the installation. You create repositories and control access to them.

Follow these steps:

1. Click the Repositories tab of the Administrator application.
2. Right-click the server in which you want to create a repository, and select New Repository from the shortcut menu.

   The Repository Properties dialog appears.

3. Define the properties of the repository:

   Name

   Names the repository and is the beginning point (root) of all paths to items in the repository.

   You can change the repository name. When you change a repository name, the repository base view name is also changed. If the repository is part of a snapshot view, a warning message appears and you can continue or cancel the rename operation.

   Compress All Files Except

   Manages binary files such as executables; this option is enabled by default to compress these files on check-in. You can exclude files from being compressed by typing their file extension in this field, or disable compression by clearing the check box.

   This Repository is for MVS files ONLY

   Stores the repository in PDS format, if selected, not a tree hierarchy structure. File extensions are not supported, and they cause errors during check-out to partitioned data sets.

   The properties are defined.

4. Click the File Extensions tab, and select file options for the end-of-line conversion during check-in, check-out or load repository when you use both UNIX and Windows clients.

   Do Not use any extension

   Treats all files as binary files with no extensions.

   Use Global text file extensions

   Shows a list of file extensions that you can include in the repository.

   Use Repository text file extensions

   Adds an extension. You can add an extension by typing an extension in the File Extension field and clicking Add. You can remove an extension by selecting the extension in the list box and clicking Remove.

   Note: If you want to treat files with no extensions as text files, use the File Extension field to add <NONE>.

   The file extension behavior is specified.

5. Click Apply.

   Saves the repository definition, but does not close the dialog.

6. Click the Access tab and set access for the repository. Click OK.

   The repository is created and appears in the Repositories tab.

More information:

File Conversion

Load Repositories

The load repository function is similar to check-in. The load operation brings files located in operating system directories into the CA Harvest SCM repository. You can load only new items into a repository. If the items exist in the repository, an error is generated. Files that are loaded are not associated with any package.

Load a Repository

After a repository is created with the Repository Properties dialog, the Load Repository dialog lets you bring an application into CA Harvest SCM.

Follow these steps:

1. Click the Repositories tab of the Administrator application.
2. Right-click the repository you want to load, and select Load Repository from the shortcut menu.

   The Load Repository dialog appears.

3. Complete the dialog fields:

   Directory

   Specifies the directory in the external file system where the files you want to load are located. This directory should contain the source files for the application that you want CA Harvest SCM to control. You can click the button next to the Directory field to open the Select Directory Path dialog.

   Note: The case of file and directory names are preserved in the repository exactly as they are loaded from the client.

   Files

   Specifies the files to load. You can use a wildcard pattern (*) to include all matching files in the load operation. Typically, a single wildcard is used, but you can use any number of wildcards in any position. You can also use the question mark (?) for a single character match.

   Recursive

   Loads an entire directory structure into a CA Harvest SCM repository. Each directory that contains files is created and the files matching the file name pattern are loaded. If corresponding paths do not exist in the repository, they are created if the paths are not empty.

   Create Empty Repository Paths

   Creates matching empty directories in the repository if any exist, and those directories containing files. This option is only available when Recursive is selected.

   Repository Path

   Specifies the repository name in which you want to load the files and create paths. When you initially load an empty repository, no paths exist. Load all files that you want to include in this repository beneath this top‑level name. Clicking the button next to the Repository Path field shows the Select a Repository Item Path dialog that lets you select the location in the repository for the loaded files.

   The Repository Path field is useful later when you want to load files into a specific directory in the repository.

   Comment

   Provides comments about the items being loaded.

   Click Load.

   The repository is loaded.

How to Move, Remove, or Rename an Item or Item Path

You can move, rename, or remove a repository item or item path only if there is no project that contains a version of the item or item path.

To perform any of those functions on an item or item path that has a version in a project, do the following procedure:

1. In the Workbench, go to the project and state that has the item or item path you want to move, rename, or remove.
2. Execute the process that corresponds to the action you want to perform on the item or item path:
   • Move Item
   • Remove Item
   • Rename Item
   • Move Path
   • Remove Path
   • Rename Path

   The Repositories tab of the Administrator interface shows the latest trunk version, regardless of the version's project location.

Create an Item Path

The New Item Path dialog lets administrators create item paths in existing repositories.

Follow these steps:

1. Click the Repositories tab in the Administrator application.
2. Right-click a repository or folder, and select New Item Path from the shortcut menu.

   The New Item Path dialog appears.

3. Complete the fields in the dialog, and click OK.

   The item path is created.

Delete an Item Path

You can delete an item path in existing data views when the item path meets the following requirements:

• The path and all its subitems are not associated to any project.
• The path and all its subitems are associated to only one project, even if that project already includes changes for them.
• The path and all its subitems are associated to more than one project, but the path and none of the items were changed in any project.
• The path does not have an item that was moved to the path from another location. This requirement is because this item might be an orphan item if the parent path is deleted; an error message appears in this case.

  Note: If an item was initially under the deleted path, even it was moved to another location in another project using the move item process; this item is deleted. This behavior is because in the Administrator repository editor, the item is still under this path.

Follow these steps:

1. Click the Repositories tab of the Administrator application.
2. Right-click the item path you want to delete, and select Delete from the shortcut menu.

   A confirmation dialog appears.

3. Click Yes.

   The item path is deleted.

Delete an Item

You can delete an item in existing data views when the item meets any of the following requirements:

• The item is not associated to any project.
• The item is associated to only one project, even if that project already includes changes for it.
• The item is associated to more than one project, but none of the items were ever changed in any project.

Follow these steps:

1. Click the Repositories tab of the Administrator application.
2. Right-click the item you want to delete, and select Delete from the shortcut menu.

   A confirmation dialog appears.

3. Click Yes.

   The item is deleted.

Duplicate a Repository

You can create an empty repository with all attributes copied from the source repository.

The following properties are duplicated when you duplicate a repository:

• Access (if selected on the Duplicate Repository dialog)
• Compress option
• MVS Option
• File Extension options

Follow these steps:

1. Click the Lifecycles tab of the Administrator application.
2. Right-click the repository you want to duplicate, and select Duplicate Repository from the shortcut menu.

   The Duplicate Repository dialog appears.

3. Name the new repository.
4. (Optional) Select the Duplicate Access Control check box if you want access control duplicated.

   The repository is duplicated.

Delete a Repository

You can delete a repository.

Follow these steps:

1. Click the Repositories tab of the Administrator application.
2. Right-click the repository you want to delete, and select Delete from the shortcut menu.

   A confirmation dialog appears.

3. Click Yes.

   The Repository is deleted.