RADE

Source Code Manager

adl_chk

Controlling workspace's directories

Quick Reference

Abstract

The adl_chk command controls files and directories of the current image of the current workspace..

Synopsis
Usage
Options
Examples
References

Synopsis

adl_chk [-l] [framework1 ... frameworkn]

Usage

The adl_chk command verifies that the current workspace's image is up-to-date with regards to the contents of the SCM database. The "JAVA" and "Doc" directories of a workspace's image are not analyzed any longer if they are at the top of the image.

If a framework name is specified the adl_chk command restricts the check to this framework.

If an object xxx has been created out of SCM scope (message ADL010E), to register it, run: adl_mk_elem xxx
If an object xxx has been modified out of SCM scope, (message ADL020E), to register it, run: adl_co xxx -no_check
If an object xxx has been deleted out of SCM scope, (message ADL040E), to register it, run: adl_restore_image xxx then adl_rm xxx
If a directory yyy has been created right under the workspace out of SCM scope, (message ADL060E), to register it, run: adl_mk_fw yyy
If a directory yyy has been created right under a framework out of SCM scope, (message ADL070E), to register it, run: adl_mk_mod yyy or adl_mk_data yyy
If a directory yyy has been created somewhere under a module or data (message ADL010E), to register it, run: adl_mk_dir yyy
If two messages concern the same object xxx (message ADL010E and message ADL040E) this object has been moved out of SCM scope; to register it, run:
mv yyy xxx then run: adl_mv xxx yyy

With the "-l" option, you won't have any message if a framework or a module is a symbolic link on a directory. This should not be true with the V5 version. This was useful before the concatenation has been taken in account by the "mkmk" command. Symbolic link were done on others workspaces' frameworks.

The adl_chk command should not executed by a user with "superuser" priveleges to avoid ADL020E message (ADL020E - File "/u/users/xxx/SCM/Fw/Mod.m/src/main.cpp" is writable for UNIX and not for SCM) for each SCM file.

[Top]

Options

adl_chk accepts the following options:

`-h\|-help\|-?`	Help of the command
`-l`	No messages with symbolic link
`framework1 ... frameworkn`	List of framework to be checked

Examples

If a file "MyFile" has been created out of SCM scope:

adl_chk
10: ADL010E - File MyFile is not in SCM

If the characteristics of a file "MyFile" has been modified (writable) on an OS (platform_name) out of SCM scope:

adl_chk
20: ADL020E - File MyFile is writable for "platform_name" and not for SCM

If the characteritics of a file "MyFile" has been modified (read only) on an OS (platform_name) out of SCM scope:

adl_chk
30: ADL030E - File MyFile is writable for SCM and not for "platform_name"

If a file "MyFile" has been deleted out of SCM scope:

adl_chk
40: ADL040E - SCM File MyFile is not in "platform_name"

If a directory "MyDirectory" has been created right under the workspace directory, out of SCM scope:

adl_chk
60: ADL060E - Directory MyDirectory is not a framework

If a directory "MyDirectory" has been created under a framework, out of SCM scope:

adl_chk
70: ADL070E - Directory MyDirectory is not a module

If a file "MyFile" has been modified out of SCM scope:

adl_chk
80: ADL080E - File MyFile has been modified out of SCM scope

If a "end of file" character is missing at the end of a file (Toto):

adl_chk
90: ADL090E - The last line of file MyFile is incomplete

Example of check in an user workspace

adl_chk
Processing framework "\\zorg\home\users\UserName\AdeleV5\MyWsName/AdeleTools"
Framework ok
Processing framework "\\zorg\home\users\UserName\AdeleV5\MyWsName/AdeleMultiSite"
Framework ok
Processing framework "\\zorg\home\users\UserName\AdeleV5\MyWsName/AdeleConfigManagement.tst"
Framework ok
Processing framework "\\zorg\home\users\UserName\AdeleV5\MyWsName/AdeleConfigManagement"
Framework ok

[Top]

References

[1]	Changing workspace: adl_ch_ws
[Top]

History

Version: 1 [Feb 2001]	Document created
[Top]