RADE

Overview

TCK stands for Tool Configuration Key and is a label identifying a specific installation of a set of tools. Different TCKs can be defined for either

• installing different tools
• installing different set of tools
• installing different levels of the same tools

[Top]

TCK Attributes

Any TCK is defined by a set of attributes and a set of tools:

• A unique identifier.
  It is what we call the TCK, that is to say the string identifying a set of tools when running a TCK command.
• The author (read-only).
  The login name of the user who created the TCK.
• The last modification date (read-only).
  Any modification on an existing TCK causes this date to be updated.
• A set of environment variables.
  They are used only when TCKs are managed by a TCK server.
  They are set in the user's environment before calling tools's profiles.
• A set of tools.
  Tools can be shared by TCKs and each tool is defined by a set of attributes.
  • A unique identifier.
    It is a string used by TCK commands to specified a particular tool.
  • The last modification date (read-only).
    Any modification on an existing tool causes this date to be updated.
  • A set of profiles.
    Any tool can own one Unix profile and one Windows-NT profile.
    If two different profiles exist on the same platform, then two different tools must be declared.

[Top]

Site or Local Management

TCKs can be created either locally on each user's machine or on a specific host that we call the TCK server host.

	When a TCK is declared locally on a given machine, this TCK is accessible for every users working on that machine. Conversely, each machine has its own defnitions of TCKs and there is no communication between them.
	When a TCK is managed by a TCK server, any user is able to use this TCK from his/her machine and any change performed on the server is seen by users. By this way any client machine communicates with the server machine to retrieve TCK information and these information are managed on only one host.

The ability to perform local registration or to retrieve information from a TCK server depends on the type of TCK installation chosen when installing the CAA2 Development Toolkit product:

1. If the "NoServer" setup was chosen, only local registrations are possible.
2. If the "Client" setup was chosen, both local and remote registrations are possible.
3. However, it is not possible to launch a TCK server on that host.
4. If the "Server" setup was chosen, the host is considered as being the TCK server host and then a TCK server can be launched.

To know which kind of installation has been set up on a machine, consult this section.

[Top]

Site and Local Management

TCK commands support two levels of registration:

• TCKs defined at site level : they correspond to TCKs managed by a TCK server and they can be used from any host where a "Client" installation has been done.
• TCKs defined at host level : they correspond to TCKs defined locally on a machine and they can be used only from that machine. Local registrations can be done on any host where a "NoServer" or "Client" installation has been done.

Depending on the way TCKs are registered, there can be several definitions of the same TCK (site and local). Here is some explanations for understanding which TCK is chosen by TCK commands.

• If a "NoServer" installation has been set up, only local registrations are available and there is only one definition for a given TCK.
• If a "Client" or "Server" installation has been set up, both site and local registrations can be done. In this case, there are three situations:
  • A given TCK exists only locally: this TCK will be chosen automatically.
  • A given TCK exists only on the TCK server: this TCK will be chosen automatically.
  • A given TCK exists both locally and on the TCK server: a temporary TCK is generated by selecting all the tools defined in the two TCKs. However, if the same tool is found in both TCKs, the local tool definition is selected.

What is the interest of having a TCK defined both on current host and on the TCK server?

It is easier for installing new tools or new versions of tools to declare them on a single host (the TCK server host). However, if some tools are composed of big modules, the local network might be heavily loaded by users running the tools over the network. In this case it is interesting to install tools on users' machines to avoid network access:

• For a daily use of tools, it is advised to install tools locally on users' machine.
• For a non frequent use, the use of a TCK server avoids the installation of tools on all machines.

Another interest of having two definitions of the same TCK is when testing an application based upon tools managed by TCKs. If a new version of a given tool must be tested, this new version of the tool can be installed on a host and declared locally the official TCK but with a different location for the associated tool.

[Top]

TCK Box in RADE Installation Program

This section describes the different installations that are available from the TCK Box displayed when installing the CAA RADE V5 CD-ROM.

"Local" Installation

This installation corresponds to the choice "No Server Setup" in the figure hereafter. It is proposed by default and corresponds to an installation which is visible only from the current host. However it is shared by all users working on this host.

The TCKs corresponding to the new installation will be added to the ones that have been installed already on the current host (use tck_list to list them).

[Top]

"Client" Installation

This installation corresponds to the choice "Client Setup" in the figure hereafter. The purpose of the "client" installation is to generate a tck_init profile which is suitable for accessing a TCK server that is running on the host specified in the "Server Name" field and using the port number specified in the "Communication port for TCK server" field.

The interest of choosing the "Client" installation is when a "Server" installation has been done on another host and for a CAA RADE installation path that is visible from the other hosts on the local network. In that case, the "Client" installation can be done on all other hosts by specifying the host where the "Server" installation has been done and the same port as given for this "Server" installation.

If the "Server" installation was performed on a UNIX platform with the user "root", it is mandatory to run other "Client" installations with a user named "root" or "CAA". Otherwise the "Client" installations will not be able to modify the TCKs created by the "Server" installation.

At the end of the "Server" installation a TCK daemon has been started, running with the user "root". The TCKs created by this installation is owned by the user "CAA". When modifying an existing TCK, the server checks that you are the owner of this TCK or the same user that is running the TCK server. In this case, only the user "CAA" and the user "root" are allowed to modify the TCK. The "Client" installation on Windows, which will use the existing TCK server running on UNIX, will try to update the TCK on the server to add the Windows profiles for each tools (mkmk, mkCheckSource, SCM .). If the user used for the "Client" installation is neither "CAA" nor "root", the TCK server will not allow the modification of the TCK.

It is important that the directory where the CAA RADE V5 CD-ROM has been installed on the TCK server is seen with the same path from hosts where a "Client" installation has been done.

It is possible to specify a TCK server corresponding to an older RADE installation. If this TCK server is running while installing the new version, the new TCKs will be registered automatically in this server.

[Top]

"Server" Installation

This installation corresponds to the choice "Server Setup" in the figure hereafter. Its purpose is to install RADE on one host and to start a TCK server on this host in order to let other hosts to access this installation. Here are the steps to go through to achieve such an installation:

1. Perform a "Server" installation using the path P, on host X and using port Y (note that X must be the host where the installation being done)
2. Start the TCK server on X as follows (example given for UNIX platform and Sun operating system)

   $ . P/solaris_a/code/command/tck_init $ tck_server Starting TCK server... $

3. Perform a "Client" installation on each host from which you want to access the "Server" installation
4. Mount X:P on each "Client" host using the same path P ((example given for UNIX platform, Sun operating system and using a "hard" mount):

   $ mount X:P / $

5. Execute the tck_init profile of the "Client" installation:

   $ . <local_client_installation_path>/solaris_a/code/command/tck_init $ tck_profile V5R11 ...

It is possible to specify a TCK server corresponding to an older RADE installation. If this TCK server is running while installing the new version, the new TCKs will be registered automatically in this server.

[Top]

User Commands

User commands are the subset of TCK commands that can be useful for any users.

These commands are available as soon as the current environment has been set up [1].

[Top]

Listing Defined TCKs

The tck_list command displays either TCK defined at site level or on current host.

Syntax

tck_list [TCK] [-tool Tool] [-all] [-local|-server] [-off] [-admin] [-h|-help|-?]

[TCK]: when no TCK is specified, all TCKs are selected.
If this parameter is set, all TCKs whose identifier contains the given string are selected.
This parameter is not case-sensitive.

[-tool Tool]: this option is used to select TCKs containing the given tool
or containing at least one tool whose identifier contains the given string.
This parameter is not case-sensitive.

[-all]: this option is used to display all information about the selected TCKs.
Without this option, only TCK and tool identifiers are displayed.

[-local|-server]: these options are useful for selecting either TCK defined locally or in a TCK server.
When the -local option is used, only the TCKs that are defined locally are selected.
When the -server option is used, only the TCKs that are defined in a TCK server are selected.
Without any of these options, the command will select TCKs defined both locally and in a TCK server.
The -all option can be used to know where is defined a TCK or a tool.

[-off]: to restrict display to official TCKs only. Default is official and administration TCKs.
By default, any new TCK is created as an official TCK.

[-admin]: to restrict display to administration TCKs only. Default is official and administration TCKs.
By default, any new TCK is created as an official TCK.

Usage

The command displays all information related to TCKs managed on a site (by a TCK server) or declared locally on current host.
As tools can be shared by several TCKs, the -tool option is useful for listing all TCKs owning a given tool specially when the tool's characteristics are being modified and one wants to know all TCKs that will be impacted by that changes.

The -local option is used to know if some local tool installations have been performed on current host.

Examples

To display all TCK identifiers along with tool identifiers:

$ tck_list

To display all TCKs whose identifier contains the string "V5R4":

$ tck_list V5R4

To display all TCKs containing at least one tool whose identifier contains the string "Mkmk":

$ tck_list –tool Mkmk

To display all information for all TCKs whose identifier contains the string "V5R4" and having at least one tool whose identifier contains the tring "Mkmk":

$ tck_list V5R4 –tool Mkmk –all

To display all official TCKs and leaving hidden all administrative TCKs:

$ tck_list –off

To use the -all option to know if a TCK or a tool is defined locally on current host:

$ tck_list –all V5R9_T01 CAA 2002/11/30-06:55:13 local Type = Official Mkmk_V5R9_T09 2002/11/30-06:55:13 local Windows NT: C:\Program Files\Dassault Systemes\V5R9_T09\intel_a\code\command\mkinit.bat SCM_V5R9_T09 2002/11/30-06:55:13 local Windows NT: C:\Program Files\Dassault Systemes\V5R9_T09\intel_a\code\command\adl_profile_cli.bat

[Top]

Accessing Tools Associated with a TCK

Given a TCK identifier, the tck_profile command sets up the current environment to give access to the tools belonging to this TCK.

Syntax

tck_profile [TCK] [-tool Tool …] [-ws ws_root_directory] [-update] [-force] [-h|-help|-?]

[TCK]: identifier of a TCK defined either on current host or at site level.
This parameter is not case-sensitive.

[-tool Tool …]: this option is used for limiting the environment setting to the tools whose identifiers are specified.
Without this option, all tools belonging to the TCK are selected.
This parameter is not case-sensitive.

[-ws ws_root_directory]: this option is used to specified a path to a "CNext" workspace
and it leads to changing the current working directory to that directory.
The directory must be accessible from the current host.

[-update]: this option is meaningful only when TCKs are declared both on current host and on a TCK server host.
It is used for replacing the local information by those managed by the TCK server.
Note that if you want to change local information without taking them from a TCK server, you must use the tck_update_local command.

[-force]: this option ensures that the tool's profiles will be executed even the given TCK has been already used in the current environment.

Usage

The tck_profile command is the command to be used for setting up a working environment with the tools belonging to a given TCK.
The main command parameter is a TCK identifier. The purpose of the command is to set some environment variables and to execute all the profiles that have been defined for all tools belonging to the TCK. Note that two profiles can be defined for a tool (Windows-NT and Unix) but the command will execute only the profile corresponding to the current platform.

If a path to a workspace is specified, it becomes the current working directory.

For performance considerations, the tck_profile command does not execute tool's profiles when it is called twice in the same environment for the same TCK. However the command checks for the last modification date of the TCK to know if its definition has changed since the last execution:

• if a new tool has been associated with a TCK, the TCK last modification date has changed
• if a tool definition has been modified, the TCK modification has changed
• if a variable value has been changed, the TCK modification has changed

Examples

To access tools associated with the "V5R4_SP1" TCK, on Windows-NT platform, execute:

$ tck_init.bat $ tck_profile V5R4 ... some messages from tools' profiles ... $

To access tools associated with the "V5R4_SP1" TCK, on Unix platform, execute:

$ . tck_init $ tck_profile V5R4 ... some messages from tools' profiles ... $

[Top]

Registering Local Tools Installations

The tck_update_local command is used for registering or updating TCKs on the current host.

Its purpose is to declare on current host a profile for a given tool and for a given TCK. After the triplet (TCK, Tool, Profile) has been registered, the environment can be set up by executing the tck_profile command with the given TCK as parameter.

Syntax

tck_update_local TCK -tool Tool [-profile profile_path] [-remove] [-h|-help|-?]

TCK: identifier of the TCK for which the tool is being registered, modified or removed.
This parameter is not case-sensitive.

-tool Tool: identifier of the tool being registered, modified or removed.
This parameter is not case-sensitive.

[-profile profile_path]: path to the profile to execute for setting the environment.
This profile must be suitable for the platform where the command is executed (Windows-NT or Unix).

[-remove]: this option is used for removing the association of the tool with the TCK.
The local tool definition is not destroyed since can be shared by several TCKs.

Usage

The tck_update_local command has two behaviours regarding the way TCKs are managed on the local network:

• If there is no TCK server, the command is used for creating, modifying and removing TCKs on current host.
• If a TCK server is available, the command is used to declare locally TCKs defined either on current host only or managed by the server but for which different tools' profiles must be used for the current host.

When a TCK is defined both on the TCK server and on a given host, any TCK command that is executed on that host will select tools from the local TCK (for those existing in both declarations). The figure below shows what profiles are selected regarding the declarations of TCKs:

TCK Definition on Server		TCK Definition on Current Host		Executing tck_profile TCK will give
TCK = { Tool1 profile = file_1 Tool2 profile = file_2 }	X	nothing		TCK = { Tool1 profile = file_1 Tool2 profile = file_2 }
TCK = { Tool1 profile = file_1 Tool2 profile = file_2 }	X	TCK = { Tool1 profile = file_3 Tool2 profile = file_4 }		TCK = { Tool1 profile = file_3 Tool2 profile = file_4 }
TCK = { Tool1 profile = file_1 Tool2 profile = file_2 }	X	TCK = { Tool1 profile = file_3 }		TCK = { Tool1 profile = file_3 Tool2 profile = file_2 }
TCK = { Tool1 profile = file_1 }	X	TCK = { Tool3 profile = file_5 Tool4 profile = file_6 }		TCK = { Tool1 profile = file_1 Tool3 profile = file_5 Tool4 profile = file_6 }

Examples

To declare on current host two versions "V1" and "V2" of the "Txxx" tool, others tools being those declared on the TCK server:

$ tck_update_local V1 -tool TxxxV1 -profile e:\local\tools\TxxxV1\profile.bat $ tck_update_local V2 -tool TxxxV2 -profile e:\local\tools\TxxxV2\profile.bat $

To declare on current host the "Txxx" tool in two different TCKs: Note that the second command does not specify the profile because the same tool identifier is used and then the corresponding profile is already registered.

$ tck_update_local V1 -tool TxxxV1 -profile e:\local\tools\TxxxV1\profile.bat $ tck_update_local V2 -tool TxxxV1 $

To change the profile associated with a tool: Note that all TCKs owning the same tool will be impacted as well.

$ tck_update_local V1 -tool TxxxV1 -profile e:\local\tools\TxxxV1\Txxx_init.bat $

To replace, in "V1" TCK, the "TxxxV1" tool by the "TxxxV2" tool: Note that as there are two different identifiers for the two tool versions it is necessary to use the -remove option to remove the first tool.

$ tck_update_local V1 -tool TxxxV2 -profile e:\local\tools\TxxxV2\profile.bat $ tck_update_local V1 -tool TxxxV1 -remove $

[Top]

Administrator Commands

The commands listed below are available as soon as the current environment has been set up [1].

These commands are needed only when managing TCKs with a TCK server. If there is no TCK server, only the user commands can work.

[Top]

Starting a TCK Server

The tck_server command starts a TCK server on the current host.

It's usual to have a single TCK server registering tools' installations on a local network.

Syntax

tck_server [-port port_number] [-h|-help|-?]

[-port port_number]: if the default port is busy,
another port can be specified using this option.

Usage

The TCK server can be launched without specifying any option since the environment has been set when executing the tck_init profile.

If the launching is successful, the command ends but leaving the TCK server running in background.

If the -port option is used to specified another port than the default one, each client must be updated as well:

• log on each client host
• edit the tck_init [1] file and change the value of the TCK_SERVER_PORT variable.

Example

$ tck_server Starting TCK server... $

[Top]

Pinging or Stopping a TCK Server

The tck_server_admin command is used to stop a TCK server or to check if one is running.

Syntax

tck_server_admin [-host host_name] [-port port_number] -ping|-stop [-h|-help|-?]

[-host host_name]: if the server is not running on the current host, this option is used to specify that host.
[-port port_number]: if the default port is busy, another port can be specified using this option.
-ping: this option causes the command to submit a request to the TCK server and returns a zero code
if there a response to the request.
-stop: this option is used for asking the server for stop.

Usage

The tck_server_admin command can be used from any host where a "Client" TCK installation has been done and by specifying the right TCK server host and port number.

Examples

To test if a server is running (from any host)

$ tck_server_admin -ping The TCK server is running on "bjork", port 23400. $ echo %errorlevel% 0

To stop a server (from any host)

$ tck_server_admin -stop $ tck_server_admin -ping # TCK - 0406: The TCK server is not running on "bjork", port 23400. $ echo %errorlevel% 5

[Top]

Registering a New TCK

The tck_create command is used to register a new TCK in the server, changes in an existing TCK can be done using the tck_modify command.

Syntax

tck_create TCK [-from TCK] [-admin] [-h|-help|-?]

TCK: identifier of the TCK to be created.
This parameter is not case-sensitive.

[-from TCK]: this option takes as parameter the identifier of an existing TCK.
This TCK is used for proposing defaults when creating the new one (variables, associated tools).

[-admin]: this option indicates that the new TCK is not created for administration and not for all users.
See -admin and -off options of the tck_list command.

Usage

The command is an interactive command and prompts the user for entering information, the execution falls down in three steps:

1. Description of the new TCK
   The tool asks to enter a brief description of the purpose of the new TCK. This description will be displayed by the tck_list command afterwards.
2. Variable definitions
   The variables are those defined in the variable file. Each variable name is displayed with its default value and the command waits for the user to enter the new value or to keep the default one.
3. Tool definitions
   The information to enter for each tool are the identifier and the Unix and Windows-NT profiles, it is not mandatory to specify a profile on both platforms since a tool may exist on only one.
   If the identifier corresponds to an existing tool, its profiles are displayed for information (they cannot be edited).

When the -from option is used to specify a reference TCK, the execution falls down in four steps:

1. Description of the new TCK
   The tool asks to enter a brief description of the purpose of the new TCK. This description will be displayed by the tck_list command afterwards. As this description should be associated with only one TCK, there is no default proposed.
2. Variables definitions
   The default values are not those defined in the variable file but the ones defined for the reference TCK.
3. Existing tool definitions
   The tools associated with the reference TCK are listed and they can be kept or ignored.
4. New tool definitions
   The last step is the same as without the -from option: new tool can be associated to the new TCK.
   If somes already exist, their profiles are listed but cannot be modified.

When the -from option is used, it is not possible to skip a tool definition. The tck_remove command can be used afterwards for removing a tool definition.

Note: it is not possible to refuse to associate a variable with a TCK. Either the default value is kept or a new value is entered. If some variables are specific to some TCKs or tools, they should be set up in tool profiles and not defined in the TCK variable file.

Here are the different use cases:

1. Creation of a new TCK with new tools
   Run the command <tck_create tck> and enter the values for the different variables, then enter the tool identifier and its Unix and Windows-NT profiles. If there is no profile on one platform, just press "ENTER" when the command prompts for it.
   The commands loops on tool definitions and ends when no tool identifier is entered.
2. Creation of a new TCK with both new and existiing tools
   Run the command <tck_create tck> and enter the values for the different variables, then enter a tool identifier. If this identifier corresponds to an existing tool, its profiles are listed but cannot be modified.
   The commands loops on tool definitions and ends when no tool identifier is entered.
3. Creation of a new TCK having the same tools as another one
   Run the command <tck_create tck -from tck2> where tck2 already exists. The command lists the identifiers of tools associated with tck2 and they can be kept (by pressing "ENTER") or replaced by new tool (by entering new tool identifiers). When all tck2's tools have been listed, the command prompts for entering a tool identifier and ends when no one is entered.

Examples

In the following examples, the TCK variable file contains only one variable ("Release"). Defaults are proposed between '[]'.

Creation of a new "CXR4" TCK with two tools "mkmkcxr4" and "adl", these tools are not yet defined in the system. The command ends when no identifier is entered.

$ tck_create CXR4 Associated comment [ENTER to skip] = tools for level CXR4 Release [-] = CXR4 Tool identifier [ENTER to terminate]: mkmkcxr4 Unix profile [ENTER to skip]: /u/users/bsfr/mkmk_profile_cxr4 Windows NT profile [ENTER to skip]: //lisa/tools/mkmk_profile_cxr4.bat Tool identifier [ENTER to terminate]: adl Unix profile [ENTER to skip]: /u/env/adlbin/adl_profile Windows NT profile [ENTER to skip]: //lisa/tools/adl_profile.bat Tool identifier [ENTER to terminate]: $

Creation of a new "CXR4" TCK with two tools "mkmkcxr4" and "adl", the "adl" tools already exists in the system.

$ tck_create CXR4 Associated comment [ENTER to skip] = tools for level CXR4 Release [-] = CXR4 Tool identifier [ENTER to terminate]: mkmkcxr4 Unix profile [ENTER to skip]: /u/users/bsfr/mkmk_profile_cxr4 Windows NT profile [ENTER to skip]: //lisa/tools/mkmk_profile_cxr4.bat Tool identifier [ENTER to terminate]: adl Unix profile = /u/env/adlbin/adl_profile Windows NT profile = //lisa/tools/adl_profile.bat Tool identifier [ENTER to terminate]: $

In this example, the -from option is used to get the same tools as those associated with the reference TCK.

$ tck_create CXR5 –from CXR4 Associated comment [ENTER to skip] = tools for level CXR5 Release [CXR4] = CXR5 Tool identifier [mkmkcxr4]: Unix profile = /u/users/bsfr/mkmk_profile_cxr4 Windows NT profile = //lisa/tools/mkmk_profile_cxr4.bat Tool identifier [adl]: Unix profile = /u/env/adlbin/adl_profile Windows NT profile = //lisa/tools/adl_profile.bat Tool identifier [ENTER to terminate]: $

[Top]

Modifying TCK's Information

The tck_modify command is used for changing the definition of an existing TCK managed by a TCK server. For modifying an existing local TCK, use the tck_update_local command instead.

Syntax

tck_modify TCK [-tool Tool] [-h|-help|-?]

TCK: identifier of the TCK to be modified.
This parameter is not case-sensitive.

[-tool Tool]: identifier of a tool associated with the TCK.
This option is used for limiting modifications to the tools whose identifier contains this string.
This parameter is not case-sensitive.

Usage

When no option is specified, the command starts by asking for a new TCK identifier, if the TCK is not to be renamed, then press "ENTER". After that, the associated type (official or administration) and comment are listed and can be changed. Then the variable are listed and their value can be changed. In the next step, all tools are listed and their identifier and profiles can be changed. When the command has gone through all tool definitions, it prompts for entering new tools (then press "ENTER" when no more tool is to be defined).

When the -tool option is used, only tools whose identifier contains this string are proposed for modifications and the command ends when they have been listed (no new tool can be specified).

When a tool identifier is changed, the profiles associated with the old tool are proposed as defaults.

If one tool profile is modified, all TCKs having the same tool are impacted automatically.

There are time stamps for TCKs and tools, here is how they works:

• Each time the command tck_modify is executed, the last modification date of the TCK is set to the current date/time.
• Each time a tool is modified, its last modification date is set to the current date.
• If one tool is proposed for modifications but no value is entered, the time stamp is not changed.
  To change the time stamp without changing definitions, at least one characteristic must be entered, even if is the same value as the default.

Examples

In the following examples, the TCK variable file contains only one variable ("Release").

Defaults are proposed between '[]'.

In the following example, the "mkmkcxr3" tool is replaced by the "mkmkcxr4" tool.

$ tck_modify CXR4 -tool mkmkcxr3 Tool identifier [mkmkcxr3]: mkmkcxr4 Unix profile [ENTER to skip] = /u/users/bsfr/mkmk_profile_cxr4 Windows NT profile [ENTER to skip] = //lisa/tools/mkmk_profile_cxr4.bat $

In the following example, the location of the Windows-NT profile of the "mkmkcxr4" tool is modified. Note that all TCKs having the "mkmkcxr4" tool will see this new location.

$ tck_modify CXR4 -tool mkmkcxr4 Tool identifier [mkmkcxr4]: Unix profile [/u/users/bsfr/mkmk_profile_cxr4] = Windows NT profile [//lisa/tools/mkmk_profile_cxr4.bat] = //ginger/tools/mkmk_profile_cxr4.bat $

In the following example, no option is specified and all information are proposed for modifications.

$ tck_modify CXR4 TCK identifier [CXR4] = Type (O|A) [Official] = Associated comment [Tools for level CXR4] = Release [CXR4] = Tool identifier [mkmkcxr3] = mkmkcxr4 Unix profile [/u/users/bsfr/cxr3/mkmk_profile] = /u/users/bsfr/cxr4/mkmk_profile Windows NT profile [\\lisa\tools\mkmk_profile_cxr3.bat] = \\lisa\tools\mkmk_profile_cxr4.bat Tool identifier [adl] = Unix profile [/u/env/adlbin/adl_profile] = Windows NT profile [\\lisa\tools\adl_profile.bat] = Tool identifier [ENTER to terminate] = $

[Top]

Removing a TCK

The tck_remove command is used for removing a TCK or the association between a tool and a TCK.

Syntax

tck_remove TCK [-tool Tool] [-h|-help|-?]

TCK: identifier of the TCK to remove or from which a tool is to be removed.
This parameter is not case-sensitive.

[-tool Tool]: identifier of a tool to removed from the TCK.
This parameter is not case-sensitive.
Only the tool is removed, the TCK remains valid.

Usage

The command is useful for fixing incorrect information or removing obsolete TCKs and tools.

If a tool is shared by several TCKs, it is removed only in the given TCK.

This command cannot be used for removing the variable in a TCK because only variables meaningful for any TCK should have been defined in the TCK server. The only way for removing a variable is to remove its definition in the the variable file and to restart server, then to use the tck_modify command for removing the variable from each TCK.

Examples

In the following example, the command is used to remove the "mkmk" tool from the "CXR4" TCK.

$ tck_remove CXR4 -tool mkmk

[Top]

Associating Environment Variables with TCKs

When using a TCK server, a set of environment variables can be associated with all TCKs managed by this server. Note that the purpose of this feature is not to defined different variables for different TCKs but for all TCKs: the setting of particular variable might be done inside tools' profiles.

The variables names are defined in the file whose path is given by the TCK_VAR_FILE environment variable. This variable is set in the working environment after having executed the tck_init [1] file.

Each time a new TCK is being created (see tck_create), or an existing TCK is being modified (see tck_modify), the command prompts the user for setting each variable.

The TCK_VAR_FILE can be edited for addiing, modifying or removing some variables: the file can contain empty lines or lines of the form

# a comment

or

VARIABLE VALUE

A variable must be defined only once.
Spaces or tabulations before a variable name or between the name and the value are ignored but are kept when found in value.

After the file has been edited, the TCK server must be restarted because the server loads the file in main memory.

Note that the new definition set has no direct impact on defined TCKs but the changes will be taken into account by TCK editing commands:

• for setting new variables, use the tck_modify command that will propose all variables including the new ones
• for removing variables, use the tck_modify command that will propose only variables defined in the variable file and will remove obsolete variable by side effect (it won't be proposed since no more managed by the TCK server).

[Top]

Retrieving the Type of TCK Installation

This information is useful when deciding to manage TCKs by a server and checking that the TCK installation on a given host is a "Client" installation.

To retrieve this information

• Log on the host to be checked
• Set up the environment to access TCK commands (using the tck_init [1] profile).
• Check the value of the TCK_NO_SERVER environment variable:
• If this variable is not defined, you have a "Client" installation.
• if this variable is defined, you have a "NoServer" installation.

In the case where you need to access a TCK server from a host where there is a "NoServer" installation, you must (re)install the CAA2 Development Toolkit products and select the "Client" setup in the TCK installation panel.

[Top]

References

History

Copyright © 2000, Dassault Systèmes. All rights reserved.