Configuring CAT/ADAMS - MSC...

Configuring the CAT/ADAMS Code Tree 3

Working with CAT/ADAMS Environment Variables 11

Changing CATIA Parameters 19

CAT/ADAMS Code Tree Files 23

Configuring CAT/ADAMS


Copyright2

U.S. Government Restricted Rights: If the Software and Documentation are provided in connection with a government

contract, then they are provided with RESTRICTED RIGHTS. Use, duplication or disclosure is subject to restrictions

stated in paragraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at 252.227-7013.

Mechanical Dynamics, Incorporated, 2300 Traverwood Drive, Ann Arbor, Michigan 48105.

The information in this document is furnished for informational use only, may be revised from time to time, and

should not be construed as a commitment by Mechanical Dynamics, Incorporated. Mechanical Dynamics,

Incorporated, assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.

This document contains proprietary and copyrighted information. Mechanical Dynamics, Incorporated permits

licensees of ADAMS® software products to print out or copy this document or portions thereof solely for internal use

in connection with the licensed software. No part of this document may be copied for any other purpose or distributed

or translated into any other language without the prior written permission of Mechanical Dynamics, Incorporated.

©2002 by Mechanical Dynamics, Incorporated. All rights reserved. Printed in the United States of America.

ADAMS ® is a registered United States trademark of Mechanical Dynamics, Incorporated.

All other product names are trademarks of their respective companies.

Part number: 120CATCG-01

1
Configuring the CAT/ADAMS Code Tree
OverviewYou can use one of two procedures to configure CAT/ADAMS after installation. You can either configure CAT/ADAMS as a new CATIA code tree or you can incorporate CAT/ADAMS files into an existing code tree. In the following sections you can learn more about CATIA code trees and the configuration procedures:

■ About CATIA Code Trees, 4

■ Configuring CAT/ADAMS as a New CATIA Code Tree, 5

■ Incorporating CAT/ADAMS into an Existing Code Tree, 8


Configuring the CAT/ADAMS Code Tree4

About CATIA Code TreesA CATIA code tree is a single directory, with subdirectories, that contains the files that comprise custom CATIA software. The software can be IUA macros, CATIA commands, CATIA functions, or CATIA utilities. The catadams subdirectory of the CAT/ADAMS installation directory is organized as a CATIA code tree, and you can use it as such after minimal configuration.

At large CATIA sites, there is usually an existing code tree that contains site-specific software. At these sites, it’s usually best to incorporate the elements of the CAT/ADAMS code tree into the existing code tree. This procedure must be done by a CATIA site administrator who is familiar with the CATIA directory structure and with the CATIA environment variables that comprise the CATIA operating environment.

Both configuration procedures refer to CATIA environment variables. The following table describes the referenced environment variables and their values in a default CATIA installation.

Table 1. Referenced Environment Variables

Variable name: Description: Default value:

CAT_UNLOAD CATIA installation directory /usr/catia/unload

CATIA CATIA configuration directory /usr/catia/cfg

CAT_CUST CATIA administrator directory /home/catadm

CAT_ADM CATIA administrative information directory $CAT_CUST/adm

CAT_CODE Active CATIA code tree directory $CAT_CUST/code

CAT_ENV Active CATIA environment file /home/catadm/env/YOUR.env

CATIA_OS Operating system name that CATIA uses to organize platform-specific files

AIX, HP-UX, IRIX, or SunOS



Configuring CAT/ADAMS as a New CATIA Code TreeUse this procedure only if you don’t have custom CATIA software installed on your system or if you don't mind that such software will not be accessible when the CAT/ADAMS environment is active.

This procedure will create a separate CATIA environment, used for the operation of CAT/ADAMS. Standard CATIA commands and functions will be accessible within this environment, but custom CATIA macros, commands, and functions that are not a part of a standard CATIA installation may not be accessible.

When you install CAT/ADAMS, an installation script does some of the configuration for you. If you intend to use the CAT/ADAMS installation directory tree, as installed, as a new CATIA code tree, then Step 5 of the following procedure is optional.

CATDEC List of directories that contain CATIA declaration files

$CATIA/dec:$CAT_CUST/dec:$CAT_CODE/dec

CATMSTR User CATIA declaration file $HOME/USRENV.dcls

LANG NLS name of the language used at your site en_US

XAPPLRESDIR Location of the CATIA X Window System resource directory

$CAT_ADM/xcfg

Table 1. Referenced Environment Variables (continued)

Variable name: Description: Default value:



To configure CAT/ADAMS as a new CATIA code tree:

1 Log on as the CATIA administrator account, usually catadm.

2 Use the following commands to determine the values of the CATIA environment variables that are referenced in this procedure. If a command doesn’t display a value, verify that your CATIA installation is correct.

echo $CATIAecho $CAT_UNLOADecho $CAT_CUSTecho $XAPPLRESDIR

3 If you want to make the CAT/ADAMS environment available for selection from the CATIA desktop, copy the sample environment file to the env subdirectory in the CATIA administrator environment directory.

cp /install_dir/catadams/env/ADAMS.env $CAT_CUST/env/

If you don't want to add the CAT/ADAMS environment to the CATIA desktop, copy the appropriate sample environment file to some other location, such as the home directory of a CATIA user.

4 To reflect conditions at your site, use a text editor to edit the copy of the environment file that you just made by modifying the values assigned to the standard CATIA environment variables. If you are installing in a customized environment, you might need the help of a CATIA site administrator. The following table lists the variables that you must modify:

Table 2. CATIA Variables Requiring Modification

Variable name: New value: Old value:

CATIA Value for $CATIA from Step 2 /usr/catia/cfg

CAT_UNLOAD Value for $CAT_UNLOAD from Step 2 /usr/catia/unload

CAT_CUST Value for $CAT_CUST from Step 2 /home/catadm



5 Use a text editor to edit the copy of the environment file by modifying the values of the CAT/ADAMS environment variables, as described in Working with CAT/ADAMS Environment Variables on page 11.

6 Copy the bitmapped graphics files from the installation directory to the CATIA X Window resource directory. At some installations you might not be able to do this, unless you have root permission.

cp /install_dir/catadams/bitmaps/* $XAPPLRESDIR/bitmaps/

7 Inform the CAT/ADAMS users of the location of the landing gear tutorial models. The location information is in the guide, Getting Started Using CAT/ADAMS. They must copy these models into a CATIA model file directory before running the tutorial. An example command is shown, which assumes that the user’s home directory contains the directory db, which is also declared as a CATIA model file directory.

cp /install_dir/catadams/samples/landing_gear/* $HOME/db/

If you have questions regarding this procedure or if you need help during program installation, you can contact your local Technical Support office.

Tip: Be sure to visit the MDI support web pages at http://support.adams.com for the latest troubleshooting information on ADAMS products. Our Knowledge Base articles http://support.adams.com/kb/ and Frequently Asked Questions (FAQs) are especially useful.

For a description of the files that comprise the CAT/ADAMS code tree, please refer to CAT/ADAMS Code Tree Files on page 23.

http://support.adams.com

http://support.adams.com/kb/



Incorporating CAT/ADAMS into an Existing Code TreeWe recommend that only CATIA site administrators attempt to complete this procedure.

Complete this procedure if you are configuring CAT/ADAMS at a large CATIA site and want to incorporate it into an existing CATIA code tree that contains custom CATIA macros, commands, functions, or utilities.

Note: This procedure may not be adequate for all CATIA sites. Some CATIA sites do not use the standard CATIA code tree mechanism to organize custom CATIA software. If this is the case at your site, use this procedure as a guide for accomplishing the tasks described.

To incorporate CAT/ADAMS into an existing code tree:

1 Log on as the CATIA administrator, usually catadm.

2 Activate a CATIA environment in which the existing code tree is accessible. For most CATIA installations, you can use the following command, replacing the text XXXXXXX with the name of the environment that you are activating:

. catiaenv $CAT_CUST/env/XXXXXXX.env

3 Use the following commands to determine the values of the CATIA environment variables that this procedure references. If a command doesn’t display a value, verify that your CATIA installation is correct.

echo $CAT_CODEecho $CAT_CUSTecho $CAT_ENVecho $CATIA_OSecho $CATDECecho $LANGecho $XAPPLRESDIR



4 Copy platform-independent files from the CAT/ADAMS installation directory to directories in the existing CATIA code tree. If $CATDEC doesn’t include the directory $CAT_CODE/dec, then copy the files, ADAMS.dcls and ADAMSN.dcls, to one of the directories that $CATDEC does include.

cp -p /install_dir/catadams/bitmaps/* $XAPPLRESDIR/bitmaps/cp -p /install_dir/catadams/dec/ADAMS.dcls $CAT_CODE/dec/cp -p /install_dir/catadams/dec/ADAMSN.dcls $CAT_CODE/dec/$LANG/cp -p /install_dir/catadams/msg/* $CAT_CODE/msg/

5 Copy platform-dependent files from the CAT/ADAMS installation directory to directories in the existing CATIA code tree. If you installed CAT/ADAMS for one platform only, use the command for your platform. CATIA uses $CATIA_OS to distinguish among the various platforms.

cp -p /install_dir/catadams/steplib/$CATIA_OS/* $CAT_CODE/steplib/$CATIA_OS

6 Append the contents of the CAT/ADAMS function declaration file to the file with the same name in the existing CATIA code tree. If $CATDEC does not include the directory $CAT_CODE/dec, then you must replace the pathname of the target file, $CAT_CODE/dec/CATCMD.dcls, with the pathname of another file of the same name in one of the directories that $CATDEC does include. Be careful to type >>, not >; otherwise, the command will overwrite the target file.

cat /install_dir/catadams/dec/CATCMD.dcls >> $CAT_CODE/dec/CATCMD.dcls

7 Append the contents of the CAT/ADAMS environment file to the active CATIA environment file. Alternatively, you could add any or all of the CAT/ADAMS shell environment variable definitions that the CAT/ADAMS environment file contains to the file .profile in the home directory of each CAT/ADAMS user. Be careful to type >>, not >; otherwise, the command will overwrite the active CATIA environment file.

cat /install_dir/catadams/env/ADAMS.CATV4R1.env.delta >> $CAT_ENV

8 Use a text editor to edit the active environment file by modifying the values of the CAT/ADAMS environment variables, as described in Working with CAT/ADAMS Environment Variables on page 11.



9 Inform the CAT/ADAMS users of the location of the landing gear tutorial models. The location information is in the guide, Getting Started Using CAT/ADAMS. They must copy these models into a CATIA model file directory before running the tutorial. The example command shown below assumes that the user’s home directory contains the directory db, which is also declared as a CATIA model file directory.

cp /install_dir/catadams/samples/landing_gear/* $HOME/db/

If you have any questions regarding this procedure or if you need help during program installation, please contact your local support center, which can be found at http://support.adams.com/support/suppcent.html. For a description of the files that comprise the CAT/ADAMS code tree, please refer to CAT/ADAMS Code Tree Files on page 23.

http://support.adams.com/support/suppcent.html

2
Working with CAT/ADAMS Environment Variables
OverviewYou can customize the operation of CAT/ADAMS with the use of the CAT/ADAMS environment variables. You must set these variables correctly to ensure proper operation of CAT/ADAMS.

The following sections explain more about the CAT/ADAMS environment variables:

■ Values of CAT/ADAMS Environment Variables, 12

■ Specifying Values for CAT/ADAMS Environment Variables, 15

■ Examples of CAT/ADAMS Environment Variable Specifications, 16


Working with CAT/ADAMS Environment Variables12

Values of CAT/ADAMS Environment VariablesYou can use the following environment variables in CAT/ADAMS:

■ topdir, 12

■ LM_LICENSE_FILE, 13

■ MDI_AVIEW_MESSAGES, 13

■ CATADAMS_DIR, 13

■ CATADAMS_DEF_CDB, 14

■ CATADAMS_AVIEW_COMMAND, 14

■ CATADAMS_ACAR_COMMAND, 14

■ CATADAMS_EDITOR_COMMAND, 14

■ CATADAMS_PLOT_COMMAND, 15

topdir

The value of topdir must be the full UNIX pathname of the directory in which you installed CAT/ADAMS from the CD-ROM. This is the directory that contains the subdirectories catadams, common, network, and so on. The value must include a trailing slash (/) character.



LM_LICENSE_FILE

The value of LM_LICENSE_FILE can be either the full UNIX pathname of the CAT/ADAMS license file that the installation program created or a port and server value. For example:

UNIX pathname: LM_LICENSE_FILE=${topdir}network/$MDI_CPU/license.datPort and server: LM_LICENSE_FILE=1986@katmandu

In the first example, the default value is shown, which is sufficient if the CAT/ADAMS file server, license server, and client are the same machine. MDI_CPU is another CAT/ADAMS environment variable. The CAT/ADAMS environment file, however, contains commands to determine its value automatically. You should not set the value yourself. If the license server and client are different machines, then you should use a port and server value for LM_LICENSE_FILE, as shown in the second example.

You can change this variable at any time to reflect a new license server.

MDI_AVIEW_MESSAGES

The value of MDI_AVIEW_MESSAGES is the full UNIX pathname of the CAT/ADAMS binary message file. The content and format of this file differ from platform to platform. The value ${topdir}catadams/aux/$CATIA_OS/catadams.msg is sufficient, unless you decide to move it from its original location.

CATADAMS_DIR

The value of CATADAMS_DIR is a full or relative pathname of a UNIX directory. It specifies a location for work, output, and report files that CAT/ADAMS generates during its operation. The user must have read, write, and search permission to this directory. If the directory doesn’t exist, CAT/ADAMS will not create it for you. If no value is specified, then CAT/ADAMS uses the current working directory, which is usually the CAT/ADAMS user's home directory.

If you set the value of CATADAMS_DIR to $HOME/catadams, then all CAT/ADAMS users will have output files placed by default in the catadams subdirectory of their home directories. If each user wants to set the value of CATADAMS_DIR individually, then they should do it in the their .profile file, and not in the CAT/ADAMS environment file.



CATADAMS_DEF_CDB

The value of CATADAMS_DEF_CDB is a full or relative pathname of a UNIX directory that also serves as an ADAMS/Car database. By default, CAT/ADAMS reads and writes ADAMS/Car files in this directory.

CATADAMS_AVIEW_COMMAND

The value of CATADAMS_AVIEW_COMMAND is the command that CAT/ADAMS uses to start ADAMS/View after the user exports a dataset file using the CAT/ADAMS menu item ADAMS + FILE + SAVE + DATASET. If you installed ADAMS/View in the same directory as CAT/ADAMS, the default value, ${topdir} mdi -c aview ru-s i exit, will be sufficient. Otherwise, you must modify the value to reflect conditions at your site. If the ADAMS installation directory is /usr/adams11, then the command should be /usr/adams11/mdi -c aview ru-s i exit. If you want a user ADAMS/View executable that was created at your site to be used, then you should replace ru-s with ru-u. For more information, see the guide, Running and Configuring ADAMS on UNIX.

CATADAMS_ACAR_COMMAND

The value of CATADAMS_ACAR_COMMAND is the command that CAT/ADAMS uses to start ADAMS/Car after the user exports a subsystem file using the CAT/ADAMS menu item ADAMS + FILE + SAVE + SUBSYST. If you installed ADAMS/Car in the same directory as CAT/ADAMS, the default value, ${topdir}mdi -c acar ru-acar i exit, will be sufficient. Otherwise, you must modify the value to reflect conditions at your site. If the ADAMS installation directory is /usr/adams11, then the command should be /usr/adams11/mdi -c acar ru-acar i exit. You can customize the command to use a private, site, or standard acar.bin file by replacing ru-acar with ru-private, ru-site, or ru-standard, respectively. For more information, see the guide, Running and Configuring ADAMS on UNIX.

CATADAMS_EDITOR_COMMAND

The value of CATADAMS_EDITOR_COMMAND is the UNIX command that CAT/ADAMS uses to start a text editor to edit the function for motions and loads. If you are using CAT/ADAMS on an SGI, you might want to use /usr/sbin/jot -f rather than the default vi editor. Users of CATIA in the Common Desktop Environment (CDE) might want to use /usr/dt/bin/dtpad.



CATADAMS_PLOT_COMMAND

The value of CATADAMS_PLOT_COMMAND is the command that CAT/ADAMS uses to start ADAMS/PostProcessor when the user selects the CAT/ADAMS menu item ADAMS + REVIEW + PLOT. If you installed ADAMS/PostProcessor in the same directory as CAT/ADAMS, the default value, ${topdir}mdi -c appt exit, will be sufficient. Otherwise, you must modify the value to reflect conditions at your site. If the ADAMS installation directory is /usr/adams11, then the command should be /usr/adams11/mdi -c appt exit. For more information, see the guide, Running and Configuring ADAMS on UNIX.

Specifying Values for CAT/ADAMS Environment VariablesYou must specify the value for each variable using Bourne or Korn shell syntax, not C shell syntax. The correct syntax is the variable name, followed by an equal sign (=), followed by the value. If the value contains spaces or characters that might be misinterpreted by the shell, then the value must be quoted using double quotes. Don’t place spaces immediately before or after the equal sign. Table 3 shows examples of shell environment variable specifications:

Table 3. Shell Environment Variable Specifications

Specification: Description:

CATADAMS_DIR=$HOME/catadams_work Specification is correct. The value of CATADAMS_DIR is set to the directory named catadams_work in the home directory of the CAT/ADAMS user.

CATADAMS_DIR =local Specification is incorrect. A space appears after the name of the variable.

CATADAMS_EDITOR_COMMAND="/usr/sbin/jot -f" Specification is correct. The value is the command used to start the SGI jot editor.

CATADAMS_EDITOR_COMMAND=xterm -e vi Specification is incorrect. The value contains spaces and is not quoted.



Examples of CAT/ADAMS Environment Variable SpecificationsTable 4 shows the shell environment variables that CAT/ADAMS uses. The sample environment file, ADAMS.env, shows how these variables are incorporated into a CATIA environment. It’s possible to incorporate these variables into an existing CATIA environment file by appending to it the contents of the sample file, ADAMS.CATV4R1.env.delta. You must modify the values of the variables so that they conform to the conditions at your site.

You normally define the CAT/ADAMS environment variables in a CATIA environment file. Users of CAT/ADAMS that use the same environment file share the same values for the CAT/ADAMS environment variables. It’s possible to work around this restriction by specifying values that use the values of other shell environment variables, such as $HOME, or by setting the value in the .profile file of each CAT/ADAMS user.

Table 4. CAT/ADAMS Environment Variables

Variable name: Description:Value in sample environment files:

topdir CAT/ADAMS installation directory

(configured during installation)

LM_LICENSE_FILE Location of CAT/ADAMS license file

(configured during installation)

MDI_AVIEW_MESSAGES Location of CAT/ADAMS binary message file

${todir}catadams/aux/$CATIA_OS/catadams.msg

CATADAMS_DIR Default output directory (none)

CATADAMS_DEF_CDB Default ADAMS/Car database directory

$HOME/private.cdb

CATADAMS_AVIEW_COMMAND

Command used to start ADAMS/View

${topdir}mdi -c aview ru-s i exit



CATADAMS_ACAR_COMMAND

Command used to start ADAMS/Car

${topdir}mdi -c acar ru-acar i exit

CATADAMS_EDITOR_COMMAND

Command used to start text editor

xterm -e vi

CATADAMS_PLOT_COMMAND

Command used to start ADAMS/PostProcessor

${topdir}mdi -c appt exit

Table 4. CAT/ADAMS Environment Variables (continued)

Variable name: Description:Value in sample environment files:

3
Changing CATIA Parameters
OverviewThe default installation of CATIA sets some resource parameters too low. Depending on the user’s model and session size, these parameters, swap space, and memory requirements might change. To run the tutorial in the guide, Getting Started Using CAT/ADAMS successfully, you must manually set these parameters.


Changing CATIA Parameters20

Changing Parameters

To change parameters:

1 Edit the file /usr/catusr/MECENV.dcls

2 Replace this parameter:

catia.MODEL_KBYTES.MAX_ACTIVE_INDEX = 400;

with:



catia.MODEL_KBYTES.MAX_ACTIVE_DATA = 1200;

with:



catia.MODEL_KBYTES.TOTAL_OVERLAY_INDEX = 1200;

with:

catia.MODEL_KBYTES.TOTAL_OVERLAY_INDEX = 30000;

5 Add the following line:

catia.SESSION_MANAGER_KBYTES = 1000;

6 Edit the file /usr/catusr/USRENV.dcls.


catia.LONBUF_GRAPHIC = 400;

with:

catia.LONBUF_GRAPHIC = 10000;




catia.LONMOD_GRAPHIC = 800;

with:

catia.LONMOD_GRAPHIC = 20000;

9 Add the following line:

catia.DETAIL_MULTISETS = TRUE;

4
CAT/ADAMS Code Tree Files
OverviewThis chapter describes the purpose and suggested location for each of the files in a typical CATIA code tree.

The CAT/ADAMS code tree files are:

■ /install_dir/catadams/env/ADAMS.env, /install_dir/catadams/env/ADAMS.CATV4R1.env.delta, 24

■ /install_dir/catadams/dec/CATCMD.dcls, 24

■ /install_dir/catadams/dec/ADAMS.dcls, 24

■ /install_dir/catadams/dec/ADAMSN.dcls, 25

■ /install_dir/catadams/steplib/AIX/*, /install_dir/catadams/steplib/HP-UX/*, /install_dir/catadams/steplib/IRIX/*, /install_dir/catadams/steplib/SunOS/*, 25

■ /install_dir/catadams/msg/ADMCATER.msg, /install_dir/catadams/msg/ADMCATHE.msg, 25

■ /install_dir/catadams/aux/$CATIA_OS/catadams.msg, 26

■ /install_dir/catadams/bitmaps/ADM*.*, 26

■ /install_dir/catadams/samples/four_bar/*, /install_dir/catadams/samples/landing_gear/*, 26

In the sections that follow, we refer to some CATIA environment variables. For a description of these and other CATIA environment variables, see Table 1 on page 4.


CAT/ADAMS Code Tree Files24

/install_dir/catadams/env/ADAMS.env,/install_dir/catadams/env/ADAMS.CATV4R1.env.deltaADAMS.env defines the environment variables necessary for a single code tree that supports the operation of CAT/ADAMS. This file is a customization of the file, YOUR.env, created during CATIA installation, and is normally placed in the directory $CAT_CUST/env.

If you want to incorporate the CAT/ADAMS code tree into an existing CATIA code tree, you need to incorporate only the contents of the file, ADAMS.CATV4R1.env.delta, into the appropriate .env file that selects the existing code tree. The file, ADAMS.CATV4R1.env.delta, represents the differences between the standard CATIA environment file, YOUR.env, and the file ADAMS.env. To learn how to specify values for the CAT/ADAMS environment variables, see Working with CAT/ADAMS Environment Variables on page 11.

/install_dir/catadams/dec/CATCMD.dclsThe file, CATCMD.dcls, identifies the ADAMS function to CATIA. It is a customization of the file with the same name found in the directory $CAT_CUST/dec or $CAT_CODE/dec in a typical CATIA installation. You can incorporate the declaration of the ADAMS function, which reads:

CATCMD.FUNCTION.LOAD3D.ADAMS=’ADAMS’;

into any other file named CATCMD.dcls that is accessible in an existing code tree. You can also simply insert this declaration into other CATIA declaration files, such as $CATMSTR.

/install_dir/catadams/dec/ADAMS.dclsThe file, ADAMS.dcls, defines a CATIA declaration set used by the ADAMS function during operation. The function requires the entire set. You can find such declaration sets either in $CAT_CUST/dec or in $CAT_CODE/dec. To incorporate this file into an existing code tree, place it in one of the directories specified by the CATIA environment variable $CATDEC.



/install_dir/catadams/dec/ADAMSN.dclsThe file, ADAMSN.dcls, also defines a CATIA declaration set used by the ADAMS function during operation. It is used only for National Language Support (NLS) customization. You can find such declaration sets either in $CAT_CUST/dec/$LANG or in $CAT_CODE/dec/$LANG, where $LANG is the name of the NLS language target.

This file is only useful if you want to customize the ADAMS function for a language other than English by changing the language of the menu items, prompts, and text labels on the Motif forms created by the function.

To incorporate this file into an existing code tree, place it in the $LANG subdirectory of one of the directories specified by the CATIA environment variable $CATDEC.

/install_dir/catadams/steplib/AIX/*, /install_dir/catadams/steplib/HP-UX/*, /install_dir/catadams/steplib/IRIX/*, /install_dir/catadams/steplib/SunOS/*These files are the shared executable objects you need if you want to run the ADAMS function within the CATIA environment. To incorporate them into another code tree, you should move the files from the directory /install_dir/catadams/steplib/$CATIA_OS to the directory $CAT_CODE/steplib/$CATIA_OS, where $CATIA_OS is one of AIX, HP-UX, IRIX, or SunOS. You can place them into the directory in which CATIA load modules are installed, $CATIA/code/steplib, but we recommend that you don’t do this, because a subsequent installation of CATIA will overwrite them.

/install_dir/catadams/msg/ADMCATER.msg,/install_dir/catadams/msg/ADMCATHE.msgThe files, ADMCATER.msg and ADMCATHE.msg, are the message files you need if you want to run the ADAMS function within the CATIA environment. To incorporate these files into another code tree, you should place them in the directory $CAT_CODE/msg. You can place them into the directory in which CATIA message files are installed, $CATIA/code/msg, but we recommend that you don’t do this, because a subsequent installation of CATIA will overwrite them.



/install_dir/catadams/aux/$CATIA_OS/catadams.msgThe binary message file, /install_dir/catadams/aux/$CATIA_OS/catadams.msg, is used by internal CAT/ADAMS utilities. Because it is an auxiliary file specific to the application, it has no standard location in a CATIA code tree, so you can move it to any location. If the file is to be stored in a code tree that is to be shared by users on heterogeneous platforms, then the versions for all platforms must reside in a common directory, within subdirectories named AIX, HP_UX, IRIX, and SunOS, respectively.

You must set the value of the environment variable, MDI_AVIEW_MESSAGES, appropriately. We recommend that you use the CATIA_OS environment variable that is always active in the CATIA execution environment to reference the subdirectory. For example, if the files and their parent directories are moved to /adams, then using /adams/$CATIA_OS/catadams.msg for MDI_AVIEW_MESSAGES ensures that you access the correct message file during CAT/ADAMS operation.

/install_dir/catadams/bitmaps/ADM*.*The files, /install_dir/catadams/bitmaps/ADM*.*, are bitmapped graphics files necessary to run the ADAMS function in the CATIA environment. You should place them in the directory $XAPPLRESDIR/bitmaps. This directory may be a subdirectory of a CATIA configuration directory, $CATIA, which can lead to difficulties when a new version of CATIA is installed. In other installations of CATIA, bitmapped graphic files are often placed in the CATIA administrator environment, in the directory $CAT_ADM/xcfg/bitmaps, with XAPPLRESDIR set to $CAT_ADM/xcfg.

/install_dir/catadams/samples/four_bar/*,/install_dir/catadams/samples/landing_gear/*The files, /install_dir/catadams/samples/four_bar/* and /install_dir/catadams/samples/landing_gear/*, are not required for the operation of the ADAMS function. They are used as part of a tutorial to introduce users to the CAT/ADAMS interface. You should place them in a directory accessible to all users.

v

Configuring CAT/ADAMS 27

C

CAT/ADAMS environment variablesCATADAMS_ACAR_COMMAND 14CATADAMS_AVIEW_COMMAND 14CATADAMS_DEF_CDB 14CATADAMS_DIR 13CATADAMS_EDITOR_COMMAND 14CATADAMS_PLOT_COMMAND 15examples of specifications 16LM_LICENSE_FILE 13MDI_AVIEW_MESSAGES 13specifying values for 15topdir 12

CATIA environment variablesCAT_ADM 4CAT_CODE 4CAT_CUST 4CAT_ENV 4CAT_UNLOAD 4CATDEC 5CATIA 4CATIA_OS 4CATMSTR 5LANG 5XAPPLRESDIR 5

CATIA parameters, about 19

Code treeabout 4configuring CAT/ADAMS as a new 5incorporating CAT/ADAMS into existing 8

Code tree files/install_dir/catadams/aux/$CATIA_OS.catadams.msg 26

Configuring CAT/ADAMS28

/install_dir/catadams/bitmaps/ADM*.* 26/install_dir/catadams/dec/ADAMS.dcls 24/install_dir/catadams/dec/ADAMSN.dcls 25/install_dir/catadams/dec/CATCMD.dcls 24/install_dir/catadams/env/ADAMS.CATV4R1.env. delta 24/install_dir/catadams/env/ADAMS.env 24/install_dir/catadams/msg/ADMCATER.msg 25/install_dir/catadams/msg/ADMCATHE.msg 25/install_dir/catadams/samples.landing_gear/* 26/install_dir/catadams/samples/four_bar/* 26/install_dir/catadams/steplib/AIX/* 25/install_dir/catadams/steplib/HP-UX/* 25/install_dir/catadams/steplib/IRIX/* 25/install_dir/catadams/steplib/SunOS/* 25listed 23

E

Environment variablesfor CAT/ADAMS 11for CATIA 4

P

Parameters, recommended 19

S

Specifying values for CAT/ADAMS environment variablesabout 15examples 16

Configuring CAT/ADAMS - MSC...

Documents

Transcript of Configuring CAT/ADAMS - MSC...