Rational Developer for System z


Add to SCLM

To add files to an SCLM project, select the project, Folder, or File right click and select Team-> Add To SCLM.

The Add To SCLM function allows you to copy files on your PC into the SCLM project mapped to the project. This migration of data can be done at the project, folder or file level. From the selection wizard you can select individual or groups of files by selecting the checkbox next to the folder or file in the Resource Selection Page.

The Resource Selection Page provides a number of action buttons and services to expedite this function. The project folders can be expanded by selecting the + and - symbols. Click Finish to use the default values. Click Next, and the Add Member Property Page is displayed where you can specify more detailed instructions about how these members are stored in SCLM.

The Update and Update All buttons enable you to select the language and type for a member or group of members. By selecting one of these buttons the Language and Type dialog is displayed.

The Language and Type dialog can be used to specify the language, type, authorization code, and change code. Alternatively, the Retrieve button can be used to extract a list of values from SCLM. Return to the Add Member Property Page and click Finish to transfer the files to SCLM. If the names of the files that you are adding to SCLM require long name translation, the language Retrieve button on the Language and Type dialog retrieves only languages that support long names.
Note: If the files you are adding from the Package Explorer or Navigator do not match the z/OSĀ® member naming conventions, or they do not reside in the root directory of the Eclipse project, the Retrieve button will only retrieve languages that are defined as long name languages by your system administrator. For example, files with names that contain more than eight characters or contain extensions can only be assigned language names that allow long file names. Lower case file names that otherwise match the z/OS member naming conventions are allowed, but are stored and retrieved as upper case names.

An additional feature allows you to perform batch-based migrations. For large scale migrations of code into SCLM, the batch style function is a practical solution because it allows you to carry on with other tasks while the members are being migrated. To run the batch migrate function, select Batch Migrate in the dialog.

One significant feature available in SCLM Developer Toolkit is the ability to store artefacts other than code fragments in SCLM. Non development documents can be stored and edited using the SCLM Developer Toolkit. For example, a Microsoft Word document can be copied into the Package Explorer and then stored in SCLM. By selecting Word as the external editor for this form of document extension, standard editing services on these non IDE type files can be affected. See the Usage scenarios topic for details on implementing this function.

Note: When long name translatable files are being added to SCLM, it is important that package naming conventions are established. Since multiple projects can be stored in one SCLM project, the potential for collisions can occur when class objects are built. If two identical package files are stored under different SCLM TYPES, the source members are treated as separate entities. When they are built, however, they are potentially built at the same location resulting in a corrupted build. Be sure to follow package naming standards to prevent this from happening.
Attention: For the SCLM Administrator

All new binary or ASCII stored files added or created in SCLM from the Eclipse Package Explorer should be stored in variable record length datasets that is, RECFM=VB. Using RECFM=FB can corrupt files by adding trailing blanks in the member. Using RECFM=FB datasets for source files that are ASCII to EBCDIC translated and stored is acceptable as most standard host component members reside in datasets of fixed record length. It is recommended that you use VB datasets for PC and Java/J2EE files. You should be aware that editors used in the Eclipse Package Explorer are generally variable record length format and storing them into fixed record length datasets in SCLM pads the records with trailing spaces.


Terms of use | Feedback



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