This task explains how to customize an existing environment on UNIX. | ||
To create or customize an environment using the catiaenv command |
||
There is now an interactive tool available for customizing
values for runtime environment variables: the
catiaenv command. Run the command as follows:
where "OS" is:
|
||
The Environment Editor appears. The user interface and functions are the same as on Windows. For more information, refer to the Windows description of the Environment Editor. | ||
To create or customize an environment using the setcatenv command |
||
The setcatenv command is available for
customizing environments. Run the command as follows:
where "OS" is:
The full list of options for the command: is as follows: |
||
Operating Environment Options |
||
These options specify the general operating environment:
|
||
Behavior Options |
||
These options determine a type of behavior
when creating or updating environments:
|
||
Action Options |
||
These options specify a particular creation or
modification action:
|
||
Any environment created by either an administrator or an end user using the setcatenv command is a user (not global) environment. | ||
What Is the Impact On My Workstation? |
||
Creating a global environment GLOBAL1 and a user environment USER1 using the setcatenv command creates the following files: | ||
$HOME/CATEnv Default environment:
Global environment:
User environment:
|
||
On AIX, HP-UX, SUN systems running the CDE desktopThe |
||
$HOME/CATEnv/CATCDE/MyProductLine/dt/appconfig/appmanager/C/MyProductLine /etc/dt/appconfig/appmanager/C/MyProductLine Contains files required for graphic representation of the default global environment and global environment in the CDE desktop:
|
||
Action description file for default global environment and global environment icon:
Action description file for MyProductLine directory:
(file created by the option "-regserver"; the file name depends on the product line). Action description file for MyProductLine document types:
|
||
$HOME/CATEnv/CATCDE/MyProductLine/dt/appconfig/icons/C /etc/dt/appconfig/icons/C Icons for MyProductLine document types. Files created by the option |
||
$HOME/.dt/appmanager/My_MyProductLine File required for graphic representation of user environment in he CDE desktop:
|
||
$HOME/.dt/types Action description file for user environment icon:
Note: the files MyProductLine.dt and CATIAFiles.dt are not present in
this directory because they are already present in: |
||
The MyProductLine icons are not present in this directory because they are already present in:
|
||
Application Manager Cabinet Default global environment and global environment icon:
Global environment icon:
User environment icon:
|
||
Note You do not see the icon immediately. To display the icon, you must click the Application manager icon on the CDE front panel, go into the Desktop Tools cabinet, then double-click the Reload Applications icon. You can also log off and log on to display the icon. |
||
Impact of Multiple Brand Installations on the Same Workstation in the CDE EnvironmentIf you have multiple brand installations on the same workstation, make sure that all the global environments related to a specfic product line (CATIA, ENOVIA DMU, DELMIA, etc...) are stored in the same CATEnv directory. The CDE file related to the environment file is stored in the CATEnv directory. If a DELMIA global environment is created using CATIAENV and stored in the CATIA CATEnv directory, the CDE will display the newly created DELMIA environment in the application manager window, but the icon created by the DELMIA installation will not be displayed anymore. |
||
To delete an environment using the delcatenv command |
||
Run the command as follows:
where "OS" is:
|
||
The full list of options for the command:
is as follows:
|
||
To list environments using the lscatenv command |
||
Run the lscatenv command to list
the names of all environments on your computer:
where "OS" is:
|
||
The full list of options for the command:
is as follows:
|
||
To read environments using the readcatenv command |
||
Run the readcatenv command to read the
environment variables in a specified environment.
Run the command as follows:
where "OS" is:
|
||
The full list of options for the command:
is as follows:
|
||
To modify environments using the chcatenv command |
||
Run the chcatenv command to edit one or more
environment variables.
Run the command as follows:
where "OS" is:
|
||
The full list of options for the command:
is as follows:
|
||
Examples |
||
Running this command... | Displays this: (where "OS" varies for the UNIX platform) |
|
./catstart -run "readcatenv -e
CATIAEnvironmentName -a global" |
CATInstallPath=UNIXInstallPath/OS |
|
|
||
./catstart -run "readcatenv -e
CATIAEnvironmentName -a global -var CATInstallPath" |
CATInstallPath=UNIXInstallPath/OS |
|
./catstart -run "readcatenv -e
CATIAEnvironmentName -d /CATEnv -var CATInstallPath" |
CATInstallPath=UNIXInstallPath/OS |
|
|
||
./catstart -run "chcatenv -e
CATIAEnvironmentName -a user -var CATInstallPath=\\\$CATInstallPath:/tmp" |
CATInstallPath=UNIXInstallPath/OS:/tmp |
|
./catstart -run "chcatenv -e
CATIAEnvironmentName -a user -var CATInstallPath=/tmp" |
CATInstallPath=/tmp |
|
./catstart -run "chcatenv -e
CATIAEnvironmentName -a user -var NewVar=/tmp -new" |
NewVar=/tmp |
|
|
||
./catstart -run "lscatenv -d /CATEnv" |
CATIA.V5R16.B16.txt |
|
Environment creation and manipulation commands are logged in the file $HOME/CATENV.log. | ||
The feedback obtained when using all the administration commands from the command line is now output to the current command prompt window. | ||
Running a Tool with the Correct Environment When Multiple Product Lines Are Installed Together |
||
In certain cases, you may have installed several products
in the same installation directory:
All of these products can install, by default, a runtime environment in the same location. If you run a tool using the catstart command without specifying which environment you want to use, the last environment installed will be executed. Consequently, make sure you use the "-env" option to specify which runtime environment you want to run. For example, if you want to run an ENOVIAV5VPM tool:
where "myenv" is the environment for your product, and "mytool" is the tool you are running. For example, if you want to run the VPMPeopleEdit tool, which is an ENOVIAV5VPM tool, use a command like this:
|
||
|