Rational Developer for System z


Import SCLM Project

The Import SCLM Project function allows you to import SCLM members where the project is mapped. The imported members can be filtered through the use of wildcards on Group, Type, and Member filters. The Archdef filter, an alternate method of specifying the files to import, is optional and is described later in this text. To import an SCLM project, select the project, right click and select Team-> Import SCLM Project to import an SCLM project. Drop-down menus provide a list of options that can be selected or manually typed in. The use of wildcards on Group, Type, SCLM Language, Member , Authorization Code and Change Code filters denotes all values for those fields.

The import can be initiated using either Filter or Archdef mode. Archdef mode imports members based on the specified Architecture Definition. The Filter fields allow you to specify different levels of granularity for member selection. If you choose Archdef mode and the Import is successful, you are prompted to specify whether you want to associate the Archdef and project. If you choose to do this, the Archdef's name is used when invoking either the Archdef build, Archdef promote or synchronize functions. An association can be removed by unmapping a project from SCLM, or replaced by performing another Import by Archdef.

The import function will advise you of any conflicts and present the available options. This has the potential to affect packaging in Java members. It is important that a standard approach (lower case) be adopted for packaging and folder conventions in the Package Explorer to avoid this problem, since it is possible for SCLM to treat packages such as test.programs and Test.Programs as two different packages. The adoption of a lower (or upper) case standard will remove this potential ambiguity.

All files stored in SCLM have an eight character naming limit. A long/short name translation service is used to map the names stored in SCLM with the names in the project. The source's location and package details are used to produce an appropriate short name for any given longname.

Attention: Package Explorer source code folder naming

It is important to understand that the files imported from SCLM preserve the folder structure that existed when the files were placed in SCLM. Therefore, packaging directories and the source folder structures for the packages are created, if necessary, during the import function. If the files are stored in SCLM with a source prefix of /src then this folder will be the source location in the project. If you are importing to an existing folder, you must make sure that it is configured to use the correct source folder.

If you are importing into an existing project, it is important that the files that are imported from SCLM preserve the packaging directories and the source folder for the packages. If the files are stored in SCLM with a source prefix of /src then this should be the source location in the project. If the files are imported into a different directory, this will prevent the plug-in from resolving the location in SCLM. For example, if your project has all code stored under source in the Package Explorer and the files being imported have been stored as src in SCLM then the project should be changed so that all source code is also stored in src. The intention is to enable SCLM to be the master control for all configuration information so that projects can be disseminated to multiple developers.


Terms of use | Feedback



This information center is powered by Eclipse technology. (http://www.eclipse.org)