RADE

Source Code Manager

adl_mk_data

Creating a data module

Quick Reference

Abstract

The adl_mk_data command creates one or more data module(s) in the current image of the current workspace.

Synopsis
Usage
Naming rules
Options
Examples
References

Synopsis

adl_mk_data data... [-force] -resp responsible_name [-h | -help | -?]

Usage

Once the data is created in the current image, it will be automatically created:

In the other images of the workspace, when the next refresh will be executed
In the parent workspace, when the next promotion/collect will be done

The data will be available for child workspaces

after the initial workspace has published and the child workspaces have synchronized themselves
then the adl_attach command will be used for attaching the new data module.

To create a module, you have to run the [1] adl_mk_mod command, and to create SCM elements as files, run the [2] adl_mk_elem command.

A SCM option allows the creation of a “data” with a name already used by a component or by a directory (for example, you can create two data with the same name under the same framework, in two different workspaces of the same tree. Note however that this can be used only in rare cases where the second user cannot wait for the first data to come in his/her workspace. Even in that case, a better way will be to use the adl_import command to make visible the new data in the second workspace.

Another example: if a data is deleted by the [3] adl_rm command, you can use the name again to create a new data. Name conflicts are detected and resolved when both “data” are located at the same time in the same workspace (when a collect is done for example). In this case, SCM calls forth the user to resolve the conflict.

A user is associated with each data: by default it is the current user. There is no user management in SCM databases. No verification is done on the responsible associated with a data.

Once the adl_mk_data command has been run in an image, no modification command (creation, move, rename, deletion, or modification of content) can be launched in another image of the same workspace, till a refresh is run

Naming rules

The basic naming rules are:

Maximum length: 128 characters.
Forbidden names: Public/Protected/PrivateInterfaces, IdentityCard.
Extension: optional.
Forbidden extensions: m, mext, etc

For more information on the naming rules, see the [4] naming rules document.

[Top]

Options

adl_mk_data accepts the following options:

`-h\|-help\|-?`	Help of the command
`data ...`	Name of the new data
`-force`	Ignore data whose names conflict with the one to create
`-resp responsible_name`	Name of the data's responsible

Examples

Creation of the "MyData" data under the framework "MyFw" under the "MyWsDev" workspace:

adl_ch_ws MyWsDev
adl_mk_data MyFw/MyData -resp user1

or

adl_ch_ws MyWsDev
cd MyFw
adl_mk_data MyData -resp user1

Creation of the "MyData" data under the "MyFw" framework, using an old data name:

adl_ch_ws MyWsDev
adl_mk_fw MyFw/MyData -resp user1 -force

or

adl_ch_ws MyWsDev
cd MyFw
adl_mk_data MyData -resp user1 -force

[Top]

References

[1]
[2]
[3]
[4]

adl_mk_mod: creating module
adl_mk_elem: creating element
adl_rm: deleting element
naming rules document

[Top]

History

Version: 2 [Mar 2004]	Document update: -resp option mandatory
Version: 1 [Mar 2001]	Document created

[Top]