Anda di halaman 1dari 143

install.

book Page 1 Friday, August 5, 2005 11:37 AM

MSC.ADAMS
Installation and Operations Guide

MSC.ADAMS 2005 r2
ADAM*V2005R2*Z*Z*Z*DC-OPS
install.book Page 2 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


2 Copyright

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 MSC.Software Corporation. MSC.Software Corporation assumes no
responsibility or liability for any errors or inaccuracies that may appear in this document.

Copyright Information

This document contains proprietary and copyrighted information. MSC.Software Corporation permits licensees of
®
MSC.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 MSC.Software Corporation.

Copyright © 2005 MSC.Software Corporation. All rights reserved. Printed in the United States of America.

Trademarks

ADAMS, EASY5, MSC, MSC., MSC.ADAMS, MSC.EASY5, and all product names in the MSC.ADAMS Product
Line are trademarks or registered trademarks of MSC.Software Corporation and/or its subsidiaries.

NASTRAN is a registered trademark of the National Aeronautics Space Administration. MSC.Nastran is an enhanced
proprietary version developed and maintained by MSC.Software Corporation. All other trademarks are the property of
their respective owners.

Government Use

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212
(Commercial Computer Software) and DFARS 227.7202 (Commercial Computer Software and Commercial
Computer Software Documentation), as applicable.
install.book Page 3 Friday, August 5, 2005 11:37 AM

Contents

Getting Started 7
Overview 7
Welcome to MSC.ADAMS Products 8
What You Need 8
About the MSC.ADAMS CDs 11
Types of Installations 12
Product Categories 13
Getting Help 19

Hardware and Software Configurations 21


Overview 21
Product and Platform Support 22
Hardware and Software Specifications 25
System Requirements 26
Graphics Requirements 29
Licensing Requirements 30
Dropped Platforms and Transition Plan for MSC.ADAMS 2005 r2 31

Installing MSC.ADAMS on UNIX 33


Overview 33
Creating the Installation Directory 34
Copying and Starting the MSC.ADAMS Installation Program 35
Installing MSC.ADAMS 37
Installing the ADAMS/Controls Thin Client 41
Installing MSC.ADAMS Documentation 42
Installing the MSC.ADAMS Extension for MSC.EASY5 44
Duplicating and Installing MSC.ADAMS on Your Hard Disk 47
Installing on a Heterogeneous Network 49
install.book Page 4 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


4 Contents

Licensing on UNIX 51
Overview 51
About the MSC.ADAMS License Server 52
Licensing MSC.ADAMS When File and License Server Are Same Machine 55
Licensing MSC.ADAMS When File and License Server Are Different Machines 56
Starting the MSC.ADAMS License Server 58
Restarting the MSC.ADAMS License Daemons 59
Changing the License to Point to a Different License Server 62
Verifying a Successful License 62

Installing MSC.ADAMS on Windows 63


Overview 63
Installing MSC.ADAMS 64
Installing the ADAMS/Controls Thin Client 73
Installing MSC.ADAMS in Silent Mode (Batch) 74
Modifying the Installation 77

Licensing on Windows 79
Overview 79
Licensing Basics 80
Specifying your License 81
Running Two Versions of MSC.ADAMS Products 82
Setting up a Windows License Server 83
Replacing Codes (Licenses) on an Existing Windows Server 84
Customizing End-User License Administration 85

Running MSC.ADAMS Products 89


Starting MSC.ADAMS Products 89
Setting Preferences 91
Setting Your Working Directory 92

UNIX Administration and Configuration 93


Overview 93
Setting Up the Client Machine 94
Updating Passwords 95
Platform-Specific Commands 97
install.book Page 5 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Contents 5

Troubleshooting 99
Overview 99
Troubleshooting on Windows 100
Troubleshooting on UNIX 111

UNIX Installation Roadmaps 119


Overview 119
File Server, License Server, and Client - Same Machine 121
File Server and License Server - Same Machine,
Client - Different Machine 122
File Server and Client - Same Machine, License Server - Different Machine 123
File Server, License Server, and Client - Different Machines 125
File Server - Different Machine, License Server and
Client - Same Machine 127
Multiple File Servers, Central License Server, and
Single-to-Multiple Clients 129
Different UNIX Platforms - Heterogeneous Network 131

Index 133
install.book Page 6 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


6 Contents
install.book Page 7 Friday, August 5, 2005 11:37 AM

1 Getting Started

Overview
This chapter describes what you need to know and have available to
install the MSC.ADAMS® suite of software. It contains the sections:
■ Welcome to MSC.ADAMS Products, 8

■ What You Need, 8

■ About the MSC.ADAMS CDs, 11

■ Types of Installations, 12

■ Product Categories, 13

■ Getting Help, 19
install.book Page 8 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


8 Getting Started

Welcome to MSC.ADAMS Products


MSC.ADAMS products provide you with tools to model, simulate, and optimize your
mechanical systems. This guide explains how to install and license the MSC.ADAMS
products on Windows, and gives you troubleshooting tips if you have any problems during
an installation.

What You Need


Before you start installing MSC.ADAMS products, there are a few things that you should
be sure to do or have available:
■ Check to ensure that your system contains the required hardware and software.
See Hardware and Software Configurations on page 21. The hardware and
software specifications help you determine the requirements for your platform
so that you can install, license, and run the MSC.ADAMS products. They also
list the memory and disk space requirements. Please review these specifications
before you select the system on which you want to install the MSC.ADAMS
software.
■ Have your password certificate (license file) available so that you can get
passwords and other information from it. For more on your password certificate,
see About Your Password Certificate on page 9.
■ Obtain any general-user software patches at the MSC.ADAMS Web site at
http://www.mscsoftware.com/support/prod_support/adams/. Once you are at our
Web site, select Product Updates.
install.book Page 9 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Getting Started 9

About Your Password Certificate


To run the MSC.ADAMS products, you need passwords and licensing information that
authorize their use. The passwords are listed on your password certificate. The password
certificate is sent to you by e-mail.
When you receive the password certificate, copy it to a file as explained in the e-mail
message. You can then use the file as input to the installation program.
The password certificate contains information necessary for installation. The installation
information appears on the first page of the certificate as follows:
■ License contract information, including your request number, company name,
license agreement number, and platform.
■ MSC.ADAMS license server IDs and a password (FEATURE) for each product.
If you have an existing MSC license, you may not receive a new password. However, you
will still need to know the name of the license server and the port number used.
install.book Page 10 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


10 Getting Started

About Your License


MSC.Software offers you two basic methods of providing software, namely traditional
(per seat) method and the token-based method (MSC.MasterKey).
■ Traditional - In the traditional method of providing software products, one
software sale results in one license (or seat) of that product. Two seats of a
software product allow for two simultaneous users. If a different software item
is needed, you must purchase a new seat or seats of the new software item.
■ Token-based (MSC.MasterKey) - With the token-based method, you
purchase a pool of tokens. Your tokens are checked out from the pool and are
used to access and run a full range of CAE solutions available under the
MSC.MasterKey from MSC.Software. Each individual software item requires
a certain number of tokens to run. After each use, your tokens are returned to
the pool for other use. If all the tokens are in use, a batch request will go into a
queue or an interactive request can be made so that you may wait for available
tokens on a first-come/first-served basis. There are many ways in which you
can manage the usage of tokens, such as by product or by project. There are
roughly 250 different software items available under MSC.MasterKey.
Refer to Licensing on UNIX on page 51 or Licensing on Windows on page 79 for more
information on licensing.
install.book Page 11 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Getting Started 11

About the MSC.ADAMS CDs


All of the files required to run the MSC.ADAMS products and online documentation are
on the CDs that come with MSC.ADAMS. The CDs are:
■ Products CDs - Contain the complete set of MSC.ADAMS products. Each CD
contains a different set of platforms. The CD you use depends on the type of
platform on which you are installing MSC.ADAMS products. On Windows, the
products CD also includes the documentation (online help).
■ Documentation Only CD (UNIX only) - Contains online help and tutorials for
using MSC.ADAMS products. The MSC.ADAMS online help is provided in
HTML format, and the tutorials in Adobe Acrobat PDF format.
install.book Page 12 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


12 Getting Started

Types of Installations
The way in which you install and license the MSC.ADAMS products depends on your
installation configuration.
Any given installation configuration is composed of the following three components:
■ File server - Machine that contains the MSC.ADAMS files. It may be shared
with other computers on a network.
■ License Server - Machine that runs the MSC.ADAMS license server. The
licensing of MSC.ADAMS products depends on the type of license you
purchased. For a list of the license configurations, see About Your License on
page 10.
■ Client - Machine that runs the MSC.ADAMS products.
You can manage these three components on one machine, three different machines, or any
combination of machines. You can also install MSC.ADAMS products on a
heterogeneous network where you install MSC.ADAMS products for different platforms
all on one network. For information on the various UNIX configurations, see UNIX
Installation Roadmaps on page 119.
install.book Page 13 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Getting Started 13

Product Categories
The product(s) or feature package you are licensed to use for MSC.ADAMS 2005 r2
appear on the first page of your password certificate under the section Feature/Password.
When you install the products, MSC.Software uses the names of the products, not the
feature names. Use Table 1 on page 14 to help you know what products to install based on
the feature names on your password certificate.
Following are the product categories:
■ Core: Include ADAMS/View and ADAMS/Solver. Both core products are
required for any vertical or plugin product to run.
■ Vertical: Include ADAMS/Car, ADAMS/Driveline, ADAMS/Engine,
ADAMS/Rail, and ADAMS/Aircraft. Both core products must be installed for
any vertical product to run.
■ Plugin: Include ADAMS/Car RealTime, ADAMS/Car Ride, ADAMS/AutoFlex,
ADAMS/Controls, ADAMS/Durability, and ADAMS/Vibration. Both of the
core products and certain vertical products must be installed for these to run (see
Table 2 on page 17).
■ Standalone: Include ADAMS/PostProcessor, ADAMS/Insight, ADAMS/Chassis,
ADAMS/Car RealTime, ADAMS/SDK, and ADAMS/Flex. Standalone
products do not require core, vertical, or plugin products to be installed.
install.book Page 14 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


14 Getting Started

Table 1. Feature Name Mappings

Feature name on password


Product name:
certificate:
ADAMS/Aircraft ADAMS_Air_LandingGear
ADAMS_Air_LandingGear_Solver
ADAMS/Aircraft Handling Tire ADAMS_Air_HandlingTire_Solver
ADAMS/AutoFlex ADAMS_AutoFlex
ADAMS/Car Suspension Design ADAMS_Car_Suspension
ADAMS/Car Conceptual Suspension ADAMS_Car_Conceptual
ADAMS/Car Vehicle Dynamics ADAMS_Car_Vehicle_Dynamics
ADAMS/Car Ride ADAMS_Car_Ride
ADAMS_Car_Ride_IDTool
ADAMS_Car_Ride_Solver
ADAMS/Car RealTime Standalone ADAMS_Car_RealTime
ADAMS_Car_RealTime_Solver
ADAMSRT_TireHandling
ADAMSRT_SmartDriver
ADAMS/Car RealTime Embedded ADAMS_Car_RealTime_Export
ADAMS/Chassis ADAMS_Chassis
ADAMS_Chassis_Solver
ADAMS_Chassis_Utilities
ADAMS/Controls ADAMS_Controls
ADAMS/Driveline ADAMS_Driveline
ADAMS_Driveline_Solver
ADAMS/Durability ADAM_Durability
ADAMS/Driver ADAMS_Driver
ADAMS/Engine Base ADAMS_Engine
ADAMS_Engine_Solver
ADAMS/Engine Valvetrain ADAMS_Engine_VTrain
ADAMS_Engine_VTrain_Solver
install.book Page 15 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Getting Started 15

Table 1. Feature Name Mappings (continued)

Feature name on password


Product name:
certificate:
ADAMS/Engine Chain Drive ADAMS_Engine_Chain
ADAMS_Engine_Chain_Solver
ADAMS/Engine Timing Belt ADAMS_Engine_TBelt
ADAMS_Engine_TBelt_Solver
ADAMS/Engine Accessory Drive ADAMS_Engine_ABelt
ADAMS_Engine_ABelt_Solver
ADAMS/Engine Cranktrain ADAMS_Engine_Crank
ADAMS_Engine_Crank_Solver
ADAMS/Engine Advanced Cranktrain ADAMS_Engine_AdvCrank
ADAMS_Engine_AdvCrank_Solver
ADAMS/Engine Gear ADAMS_Engine_Gear_Solver
ADAMS/Engine Piston ADAMS_Engine_Piston
ADAMS_Engine_Piston_Solver
ADAMS/Flex ADAMS_Flex
Full Simulation Package ADAMS_View
ADAMS_Solver
ADAMS/Insight ADAMS_Insight
ADAMS/PostProcessor ADAMS_Postprocessor
ADAMS/Rail ADAMS_Rail
ADAMS_Rail_Solver
ADAMS/Tire 3D Contact ADAMS_Tire_3DContact
ADAMS/Tire Handling ADAMS_TireHandling
ADAMS/Tire FTire ADAMS_Tire_FTire
ADAMS/Tire SWIFT ADAMS_Tire_Swift
ADAMS/Tire Motorcycle Tire ADAMS_TireMotorcycle
ADAMS/3D Road ADAMS_3DRoad
ADAMS/Exchange ADAMS_Exchange
install.book Page 16 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


16 Getting Started

Table 1. Feature Name Mappings (continued)

Feature name on password


Product name:
certificate:
ADAMS/Solver Task ADAMS_Solver
ADAMS/Solver SMP ADAMS_Solver
ADAMS/Vibration ADAMS_Vibration
ADAMS_Vibration_Solver
ADAMS/View ADAMS_View
ADAMS/Linear ADAMS/Linear
install.book Page 17 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Getting Started 17

Table 2. Plugin Installation Configurations

This plugin: Works with this product:

ADAMS/Car Ride ADAMS/Car

ADAMS/Car ADAMS/Car
RealTime

ADAMS/AutoFlex ADAMS/Aircraft
ADAMS/Car
ADAMS/Driveline
ADAMS/Engine
ADAMS/Rail
ADAMS/View

ADAMS/Controls ADAMS/Aircraft
ADAMS/Car
ADAMS/Driveline
ADAMS/Engine
ADAMS/Rail
ADAMS/View

ADAMS/Durability ADAMS/Aircraft
ADAMS/Car
ADAMS/Driveline
ADAMS/Engine
ADAMS/Rail
ADAMS/View

ADAMS/Driveline ADAMS/Car
ADAMS/Engine

ADAMS/Engine ADAMS/Car
ADAMS/Driveline
install.book Page 18 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


18 Getting Started

Table 2. Plugin Installation Configurations (continued)

This plugin: Works with this product:

ADAMS/Vibration ADAMS/Car
ADAMS/Driveline
ADAMS/Engine
ADAMS/Rail
ADAMS/View
install.book Page 19 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Getting Started 19

Getting Help
If you have questions or problems installing or testing your MSC.ADAMS products, refer
to Troubleshooting on page 99. If the problems persist, go to the Customer Services Web
pages at http://www.mscsoftware.com/support/prod_support/adams/. If the problems still
persist, call MSC.Software Technical Support at the numbers listed below. Before
contacting Technical Support, please have the following information available:
■ Hardware type (be as specific as possible)
■ Version of the operating system, including build number and service packs, if
applicable
■ Version of compilers
■ Hardcopy of all error messages (you can send it by fax or through e-mail)
If possible, generate a troubleshooting report as explained in Generating Problem Reports
on page 100.

United States
(800) 732-7284

International
Contact your local distributor.
install.book Page 20 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


20 Getting Started
install.book Page 21 Friday, August 5, 2005 11:37 AM

2 Hardware and Software Configurations

Overview
This chapter provides the hardware and software configurations for
MSC.ADAMS.

Note: For the latest version of the hardware and software


specifications, see the MSC.ADAMS Support site at
http://www.mscsoftware.com/support/prod%5Fsupport/adams/.

This chapter includes the following sections:


■ Product and Platform Support, 22

■ Hardware and Software Specifications, 25

■ System Requirements, 26

■ Graphics Requirements, 29

■ Licensing Requirements, 30

■ Dropped Platforms and Transition Plan for MSC.ADAMS


2005 r2, 31
install.book Page 22 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


22 Hardware and Software Configurations

Product and Platform Support


Figure 1 on pages 23 and 24 outlines the UNIX and Windows platforms on which
each MSC.ADAMS product runs.
install.book Page 23 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Hardware and Software Configurations 23

Figure 1. MSC.ADAMS Platform Support


HP HP IBM Intel & AMD x86 Intel & AMD x86 Sun
Platforms SGI MIPS
PA-RISC Itanium2 POWER PCs PCs UltraSPARC
Red Hat Windows 2000,
Operating AIX Solaris
11, 11i 11.23 Linux 9.0, Windows XP IRIX 6.5.14c
Systems 5.1 8, 9, 10
Enterprise Linux 3 Professional
Graphics X11, X11, X11, X11, Microsoft Windows X11, X11,
Drivers OpenGL OpenGL OpenGL OpenGL Driver, OpenGL OpenGL OpenGL
Packages
ADAMS Full
Simulation Package
Products
ADAMS/View
ADAMS/PostProcessor
ADAMS/Insight
ADAMS/Solver Task
ADAMS/Solver SMP
ADAMS/Vibration
ADAMS/Durability
ADAMS/Controls
ADAMS/Flex
ADAMS/AutoFlex
ADAMS/Linear
Industry Products
ADAMS/Aircraft
Landing Gear
ADAMS/Aircraft
Handling Tire
ADAMS/Rail
Automotive Products
ADAMS/Car
Suspension Design
ADAMS/Car
Conceptual Suspension
ADAMS/Car
Vehicle Dynamics
ADAMS/Car Ride

Notes:
Intel IA-32 processors: Pentium 4, Xeon and AMD compatibles.
QA performed on 6.5.14, but MSC.ADAMS 2005 r2 is expected to work on levels above this.
MATLAB support is not available on this platform. See the Known Issues section of the Release
Notes for this product.
ADAMS/Controls is supported on these platforms. However, partner product support varies. See the
Known Issues section of the ADAMS/Controls Release Notes and Knowledge Base Article 12445.
install.book Page 24 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


24 Hardware and Software Configurations

MSC.ADAMS Platform Support (continued)


HP HP IBM Intel & AMD x86 Intel & AMD x86 Sun
Platforms SGI MIPS
PA-RISC Itanium2 POWER PCs PCs UltraSPARC
Red Hat Windows 2000,
Operating AIX Solaris
11, 11i 11.23 Linux 9.0, Windows XP IRIX 6.5.14c
Systems 5.1 8, 9, 10
Enterprise Linux 3 Professional
Graphics X11, X11, X11, X11, Microsoft Windows X11, X11,
Drivers OpenGL OpenGL OpenGL OpenGL Driver, OpenGL OpenGL OpenGL
Automotive Products, continued
ADAMS/Car RealTime
Standalone
ADAMS/Car RealTime
Embedded
ADAMS/Chassis
ADAMS/Driveline
ADAMS/Driver
ADAMS/SmartDriver
ADAMS/Engine Base
ADAMS/Engine
Valvetrain
ADAMS/Engine
Chain Drive
ADAMS/Engine
Timing Belt
ADAMS/Engine
Accessory Drive
ADAMS/Engine
Basic Cranktrain
ADAMS/Engine
Advanced Cranktrain
ADAMS/Engine Gear
ADAMS/Engine Piston
ADAMS/Tire Handling
ADAMS/Tire 3D
Contact
ADAMS/Tire FTire
ADAMS/Tire SWIFT
ADAMS/Tire
Motorcycle Tire
ADAMS/3D Road
CAD Interface Products
ADAMS/Exchange

Notes:
Intel IA-32 processors: Pentium 4 and Xeon and AMD compatibles.
QA performed on 6.5.14, but MSC.ADAMS 2005 r2 is expected to work on levels above this.
install.book Page 25 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Hardware and Software Configurations 25

Hardware and Software Specifications


Figure 2 outlines the hardware and software specifications for MSC.ADAMS.

Figure 2. Hardware and Software Specifications


Models and
Platform Processors Operating System Fortran C/C++

PA-8k based
HP PA-RISC B-class, C-class, c89 11.01.20
HP-UX 11, 11i f90 2.4.13
HP-UX J-class, and aCC 03.27
rp-class servers

HP Itanium2 c89 5.55


Intel Itanium 2 HP-UX 11.23 2.8.4
HP-UX aCC 5.55

IBM POWER Power3, Power3-II,


AIX 5.1 XL Fortran 8.1 Visual Age C/C++ 6.0.0.4
AIX Power4

Red Hat Linux 9.0 g77 3.2.2-5 or g++ 3.2.2-5


Intel Pentium 4, Intel Fortran 8.1.19
Intel & AMD x86
Xeon and
Linux RH Enterprise Linux 3.0 g77 3.2.3-24 or
compatibles g++ 3.2.3-24
Intel Fortran 8.1.19

Intel Pentium 4, Intel Fortran 8.1.28


Intel & AMD x86 Windows 2000,
Xeon, and Compaq Visual Visual Studio C++ .NET 2003
Windows Windows XP Professional
compatibles Fortran 6.6B

R5k, R8k, R10k,


SGI MIPS IRIX IRIX 6.5.14 7.3.1.2m 7.3.1.2m
R12, R14k

Sun UltraSPARC UltraSPARC III-


Solaris 8, 9, 10 Sun Studio 8, 9, 10 Sun Studio 8, 9, 10
Solaris based systems
install.book Page 26 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


26 Hardware and Software Configurations

System Requirements
Figure 3 on pages 26 through 28 outlines the system requirements for MSC.ADAMS.

Figure 3. System Requirements


Operating Memory and
Platform System System Patches Disk Space Swap Space
XSWGR1100 General Release Patches,
November 1999 (ACE)
QPK1100 Quality Pack for HP-UX
11.00 (December 2000)
PHSS_20853 Shared libF90
PHSS_24303 ld(1) and linker tools 512 Mb Minimum
cumulative patch 1 Gb Recommended
PHSS_25447 X/Motif 32bit Runtime
OCT2001 Periodic Patch Tunable Kernel
PHSS_25718 LIBCL patch Parameters:
HP PA-RISC Products 1004 Mb
HP-UX 11 PHSS_26628 3D Common Run maxdsiz = 256 Mb
HP-UX Docs 163 Mb
PHSS_26636 OpenGL 1.1 Run maxstsiz = 256 Mb
PHSS_26945 HP aC++ -AA runtime maxusers = 128 or
libraries (aCC A.03.37) higher
PHSS_30181 Xserver cumulative patch
PHCO_26449 Add Rock Ridge extension Swap = 2 x RAM
to mount_cdfs(1M)
PHKL_26450 Rock Ridge extension for
ISO-9660
PHKL_28060 Y2k; Rock Ridge extension
for ISO-9660

GOLDBASE11i Gold Base Patches for HP-UX


11i v1, December 2003
BUNDLE11i B.11.11.0306.1 Required
Patch Bundle for HP-UX
11i, June 2003
PHCO_25841 Add Rock Ridge extension
to mount_cdfs(1M)
PHKL_26269 Rock Ridge extension for
ISO-9660 512 Mb Minimum
PHKL_28025 Rock Ridge extension for 1 Gb Recommended
ISO-9660
PHSS_23352 Fortran90 B.11.01 Tunable Kernel
cumulative patch Parameters:
HP PA-RISC PHSS_26946 HP aC++ -AA runtime
Products 1004 Mb
HP-UX 11i maxdsiz = 256 Mb
HP-UX libraries (aCC A.03.37) Docs 163 Mb
maxstsiz = 256 Mb
PHSS_28303 LIBCL patch PHSS_28880 maxusers = 128 or
HP aC++ -AA runtime higher
libraries (aCC A.03.50)
PHSS_29371 X/Motif Runtime Periodic Swap = 2 x RAM
Patch
PHSS_30049 ld(1) and linker to
cumulative patch
PHSS_30170 Xserver cumulative patch
PHSS_30174 3D Common Run
PHSS_30496 OpenGL 1.1 Run
PHSS_30504 Xserver cumulative patch
install.book Page 27 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Hardware and Software Configurations 27

System Requirements (continued)


Operating Memory and
Platform System System Patches Disk Space Swap Space
512 Mb Minimum
1 Gb Recommended

B.11.23.0409. Required Patch Bundle for Tunable Kernel


HP-UX 11i v2 (B.11.23), September 2004 Parameters:
HP Itanium2 Products 1177 Mb
HP-UX 11.23 maxdsiz = 256 Mb
HP-UX Docs 163 Mb
PHCO_32667 11.23 csh(1) cumulative maxstsiz = 256 Mb
patch maxusers = 128 or
higher

Swap = 2 x RAM

512 Mb Minimum
Products 868 Mb 1 Gb Recommended
IBM POWER AIX AIX 5.1 bos.rte 5.1.0.50
Docs 190 Mb
Swap = 2 x RAM

512 Mb Minimum
Intel & AMD x86 Red Hat Products 945 Mb 1 Gb Recommended
Red Hat Kernel revision 2.4.20-8
Linux Linux 9.0 Docs 190 Mb
Swap = 2 x RAM

512 Mb Minimum
Intel & AMD x86 Enterprise Enterprise Linux Kernel Products 945 Mb 1 Gb Recommended
Linux Linux 3 revision 2.4.21-9 Docs 190 Mb
Swap = 2 x RAM

Windows Windows 2000 SP4


2000 512 Mb Minimum
Intel & AMD x86 Products 820 Mb 1 Gb Recommended
Windows Docs 190 Mb
Windows XP Windows XP Professional SP1,
Swap = 2 x RAM
Professional Windows XP Professional SP2

Support Levels above 6.5.14m are expected 512 Mb Minimum


to work under the SGI published "The Products 943 Mb 1 Gb Recommended
SGI MIPS IRIX IRIX 6.5.14
Mandate of Application Compatibility in SGI Docs 190 Mb
IRIX 6.5" Swap = 2 x RAM
install.book Page 28 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


28 Hardware and Software Configurations

System Requirements (continued)


Operating Memory and
Platform System System Patches Disk Space Swap Space
Recommended patch bundle later than
512 Mb Minimum
1/14/2003
Sun UltraSPARC Products 900 Mb 1 Gb Recommended
Solaris 8 Generic_108528-18
Solaris Docs 190 Mb
Latest revisions of patches:
Swap = 2 x RAM
106950, 108131, 108434

Recommended patch bundle later than 512 Mb Minimum


Sun UltraSPARC 8/14/2003 Products 900 Mb 1 Gb Recommended
Solaris 9
Solaris Generic_112233-08 Docs 190 Mb
Latest revisions of patches: 111711 Swap = 2 x RAM

Latest revisions of patches: 512 Mb Minimum


Sun UltraSPARC 113886, 113887, 118676, 116298, 116302, Products 900 Mb 1 Gb Recommended
Solaris 10
Solaris 113886, 117832, 117834, 117836, 117830, Docs 190 Mb
117840, 117844, 118678, 117838 Swap = 2 x RAM
install.book Page 29 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Hardware and Software Configurations 29

Graphics Requirements
The following are the graphics requirements for MSC.ADAMS.
Figure 4. Graphics Requirements
Platform Operating System System Runtime Libraries Validated Graphics Hardware

HP PA-RISC HP-UX 11, X11-R5, CDE/Motif,


fxe, fx10
HP-UX HP-UX 11i OpenGL 1.1

HP Itanium2 X11-R6, CDE/Motif,


HP-UX 11.23 ATI Fire GL4
HP-UX OpenGL 1.1

IBM POWER AIX AIX 5.1 OpenGL.OpenGL_X.rte.base 5.1 GXT3000, GXT4500P

The MSC.ADAMS products have


been developed in full compliance
X11, OpenGL 1.2
Intel & AMD x86 Red Hat Linux 9.0, with the OpenGL 1.2 specification.
nVIDIA users should load the Linux
Linux Enterprise Linux 3 The products should run properly
Display Driver 1.0-5336
with graphics cards that adhere to
the 1.2 or later OpenGL specification.

The MSC.ADAMS products have


been developed in full compliance
Windows 2000,
Intel & AMD x86 with the OpenGL 1.2 specification.
Windows XP OpenGL 1.2
Windows The products should run properly
Professional
with graphics cards that adhere to
the 1.2 or later OpenGL specification.

SGI MIPS IRIX IRIX 6.5.14 X11/Motif, OpenGL VPro Graphics systems

Solaris 8 X11 (CDE), OpenGL 1.2


Sun UltraSPARC
Solaris 9 X11 (CDE), OpenGL 1.3 Expert 3D, XVR 1000
Solaris
Solaris 10 X11 (CDE), OpenGL 1.3
install.book Page 30 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


30 Hardware and Software Configurations

Licensing Requirements
Following are the licensing requirements for MSC.ADAMS.
Figure 5. Licensing Requirements
Special Required
Platform Software Hostname Retrieval Host ID Retrieval
From a shell window, enter From a shell window, enter
the command: the command:
HP PA-RISC HP-UX N/A hostname uname –I
Then convert the number to hex.

From a shell window, enter From a shell window, enter


the command: the command:
HP Itanium2 HP-UX N/A
hostname getconf CS_PARTITION_IDENT
then prefix with “ID_STRING=” .

From a shell window, enter From a shell window, enter


IBM POWER AIX the command: the command:
N/A
hostname uname -l

From a shell window, enter From a shell window, enter


the command: the command:
Intel & AMD x86 Linux hostname /sbin/ifconfig eth0
N/A
Return the information in the line
labeled "HWaddr" and remove the
colons “ : ” .

TCP/IP Protocol From a "Command Prompt" From an "Command Prompt"


window, enter the command: window, enter the command:
Intel & AMD x86 Windows hostname ipconfig /all
Return the information in the
line labeled "Physical Address".

From a shell window, From a shell window, enter the


enter the command: command:
SGI MIPS IRIX N/A
hostname sysinfo -s
Then convert the number to hex.

From a shell window, From a shell window, enter the


Sun UltraSPARC Solaris N/A enter the command: command:
hostname hostid
install.book Page 31 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Hardware and Software Configurations 31

Dropped Platforms and Transition Plan for MSC.ADAMS


2005 r2
Each release we review the platforms and operating system changes by our partners and
in the industry, and address these changes in our release. For a complete list of the
supported platforms and operating systems for the MSC.ADAMS 2005 r2 release, see
Hardware and Software Specifications on page 25.
Table 3. Platforms No Longer Supported After the MSC.ADAMS 2005 r2 Release

Final MSC.ADAMS
Platform: Migration Platform:
Release Supported:

HP PA-RISC HP-UX 11.0 2005 r2 HP-UX 11i


Intel & AMD x86 2005 r2 Red Hat Enterprise Linux 3.0
Red Hat Linux 9.0
IBM POWER AIX 5.1 2005 r2 IBM AIX 5.2

Table 4. Compilers Dropped for the MSC.ADAMS 2005 r2 Release

Platform: Recommended Platform:

Microsoft Visual C/C++ 6 Microsoft Visual C/C++ 2003 .NET


Compaq Visual Fortran 6.6B Intel Visual Fortran 8.1.28

Table 5. Platforms Considered for Future Termination of Support

Platform: Recommended Platform:

SGI MIPS IRIX Other supported UNIX or Windows platform


install.book Page 32 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


32 Hardware and Software Configurations
install.book Page 33 Friday, August 5, 2005 11:37 AM

3 Installing MSC.ADAMS on UNIX

Overview
This chapter provides instructions for installing the MSC.ADAMS
software. It contains the sections:
■ Creating the Installation Directory, 34

■ Copying and Starting the MSC.ADAMS Installation


Program, 35

■ Installing MSC.ADAMS, 37

■ Installing the ADAMS/Controls Thin Client, 41

■ Installing MSC.ADAMS Documentation, 42

■ Installing the MSC.ADAMS Extension for MSC.EASY5, 44

■ Duplicating and Installing MSC.ADAMS on Your Hard


Disk, 47

■ Installing on a Heterogeneous Network, 49


After installing the MSC.ADAMS products, you need to set up the
licenses to run them. See Licensing on UNIX on page 51 for more
information.

Note: For general steps (roadmaps) for the various UNIX


configurations, see UNIX Installation Roadmaps on
page 119.
install.book Page 34 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


34 Installing MSC.ADAMS on UNIX

Creating the Installation Directory


This section explains how to create an installation directory in which to install the
MSC.ADAMS products. This is the location on your file server where you want the
MSC.ADAMS products to reside. Note that this directory must be accessible to all
departmental file servers on which you are going to install MSC.ADAMS products.
In addition, note that you can use a remote machine to mount the CD-ROM drive.
Note: You can enter the commands shown in this section in either uppercase or
lowercase depending on your system. For example, when you mount the
CD, the mount point can either be /cdrom or /CDROM.

To create the installation directory:

1 Log on to the UNIX system where you want to install the MSC.ADAMS
products (the file server).
2 Load the appropriate Products CD in the CD-ROM drive. Each Products CD
contains a different set of UNIX platforms. Be sure to load the correct CD for
the platform on which you are installing MSC.ADAMS.
3 Enter the mount command for your platform.
Note: For a listing of mount commands for UNIX systems, see Platform-
Specific Commands on page 97.
If you are using a remote machine on your network to mount the CD-ROM
drive, you must have permission to access that machine from the installer’s
account, with a remote-shell, requiring no password. For example, if the
remote machine’s hostname is server1, you need to be able to enter the
command rsh server1 (or remsh server1, for HP systems) and be able to log on
to server1 without entering a password.
4 Create a directory in which to place the MSC.ADAMS products by entering
the following command, where install_dir is the directory that you want to
create:
mkdir install_dir
We recommend that you create a directory called /usr/adamsx for the
MSC.ADAMS products. In the directory name, x represents the current version
of MSC.ADAMS. If you have a prior version of MSC.ADAMS on your
install.book Page 35 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on UNIX 35

system, you should install the new version in a different location. If, however, you
are adding the same version of software to an existing installation, place the new
software in the same location.

Copying and Starting the MSC.ADAMS Installation Program


This section contains instructions for copying and starting the MSC.ADAMS installation
program. You must perform all of the steps in the section before installing or licensing
MSC.ADAMS products.

To copy and start the installation program:

1 Change to the installation directory you created by entering the following


command:
cd /install_dir
2 Locate the installation program (INSTALL.ADAMS or install.adams) using the ls
command for the CD mount point. For example, depending on your system, enter
either of the following:
ls /cdrom
ls /CDROM
3 Copy the installation program on to your system using the command appropriate
for your system. For example, enter either of the following:
cp /CDROM/INSTALL.ADAMS ./
cp /cdrom/INSTALL.ADAMS ./
install.book Page 36 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


36 Installing MSC.ADAMS on UNIX

4 Enter the following command to start the installation script:


./INSTALL.ADAMS
The Installation Menu appears as shown next.

+--------------------------------------------------------+
| MSC.Software Corporation |
| MSC.ADAMS Selection Menu |
| Product Installation Menu |
| |
| Install MSC.ADAMS |
| 1) Install MSC.ADAMS from the CD-ROM |
| 2) Duplicate the CD-ROM to your hard disk |
| 3) Install MSC.ADAMS from your hard disk (step #2) |
| |
| License MSC.ADAMS |
| 4) Install MSC passwords on this license server |
| 5) Start the MSC license server on this system |
| 6) Stop the MSC license server(s) |
| |
| Troubleshooting |
| 7) Generate a problem report |
| 8) Check hostid on this system |
| |
| 9) Exit |
+--------------------------------------------------------+
Please enter your selection (CR=1):
install.book Page 37 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on UNIX 37

Installing MSC.ADAMS
Follow the procedure below to automatically copy and uncompress the files from the
Products CD to your installation directory.
Note: You can enter the commands shown in this section in either uppercase or
lowercase letters depending on your system. For example, when you mount
the CD-ROM, the mount point could be either /cdrom or /CDROM.

To install MSC.ADAMS products:

1 Start the installation program as described on page 34, if necessary.


2 At the prompt, enter 1 to select the option, Install MSC.ADAMS from CD-ROM.
3 Enter the name of the installation directory you created.
If you are logged in as root, the installation program automatically creates a soft
link named adams05r2 in /usr/bin for running the MSC.ADAMS products.
4 At the hostname prompt, enter the name of the machine to which the CD-ROM
drive is attached.
5 Enter the CD-ROM mount point (for example, /cdrom). For a listing of mount
commands for UNIX systems, see Platform-Specific Commands on page 97.
install.book Page 38 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


38 Installing MSC.ADAMS on UNIX

6 From the list of platforms on the Products CD that appears, enter the type of
platform on which you are installing MSC.ADAMS. An example of the list of
platforms is shown next.

*************************************************************
Platforms on this local CD are:

rhlinux - Linux ix86 systems running Red Hat 9


irix32 - SGI systems running IRIX
*************************************************************

Note: If the platform on which you are installing MSC.ADAMS products does
not appear in the list, you may have loaded the wrong Products CD. If
necessary, check the Products CD label, and load the appropriate CD.

7 Select the MSC.ADAMS files and products that you want to install by entering a y
after each option for which you are licensed.
The products you purchased appear on the first page of your password certificate.
Note that under the section Feature/Password, MSC.Software lists the products that
you have been licensed to use. MSC.Software uses the feature names of the
products as you enter them into the installation program, not the actual names of
the products.
Note: If you select to install the ADAMS/Control Client, you cannot install any
other MSC.ADAMS product. For more information, see Installing the
ADAMS/Controls Thin Client on page 41.
8 Verify that you have enough disk space to install the products you selected. A list
of the space required for each of the products you selected to install is shown at the
left and the space you have available in the installation directory is shown at the
top.
install.book Page 39 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on UNIX 39

9 Enter y after you have verified the availability of disk space. The installation
program automatically extracts and uncompresses the files required to use the
MSC.ADAMS products.
If you do not have enough space, enter n and the list of products appears again.
Either open another shell window and free up space at the location you want to
install or abort the installation program and start over selecting another
location to install MSC.ADAMS products. Note that the hardware and
software specifications list the disk space requirements for MSC.ADAMS
products, and you should review it before starting.
10 Enter the path to the local license file or the port number that is used by the
license server.
11 Enter the name of the MSC.ADAMS license server as it appears on your
password certificate.
12 Enter the path to your machine’s Internet browser.
You must have a browser installed to view the online help.
13 If you are installing ADAMS/View, select X11 to install the X11 driver or
select NATIVE to install the NATIVE driver.
The X11 driver supports local and remote displays with some performance
penalty. The NATIVE driver supports local displays with increased
performance if graphics acceleration hardware is present.
14 From the Product Installation Menu, select Option 9 (Exit).
You will be prompted to install the documentation in this location.
15 Select Y to install the documentation.
Note: If you don’t install the documentation now, you can use the UNIX
Online Documentation CD to install it later. See Installing
MSC.ADAMS Documentation on page 42.
16 Enter the name of the install directory for MSC.ADAMS.
17 Select CD-ROM to install from the documentation CD, or disk to install from a
disk drive where you copied the files.
install.book Page 40 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


40 Installing MSC.ADAMS on UNIX

18 Do one of the following:


■ If installing from disk, enter the disk mount point.
■ If installing from CD:
a At the hostname prompt, enter the name of the machine to which the CD-
ROM drive is attached.
b Enter the CD-ROM mount point at the prompt (for example, /cdrom).
19 Choose to install the MSC.ADAMS online help.
20 At each prompt, specify whether or not you want the online help installed for each
product. The default is whether or not the product itself is installed.
21 Verify that you have enough disk space to install the files. The space required to
install the files is shown at the left and the space you have available in the
installation directory is shown at the top.
22 After you have verified the availability of disk space, enter y.
If you do not have enough disk space, enter n. Then, either open another shell
window and free up space at the location you want to install or exit the installation
program and start over, selecting another location to install the MSC.ADAMS
documentation.
23 If you installed ADAMS/Controls, you need to install the MSC.ADAMS
Extension for MSC.EASY5. Previously, this was done automatically by the
ADAMS/Controls install program. For more information, refer to Installing the
MSC.ADAMS Extension for MSC.EASY5.
install.book Page 41 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on UNIX 41

Installing the ADAMS/Controls Thin Client


The ADAMS/Controls Thin Client is a subset of ADAMS/Controls. This client can be
helpful to MSC.EASY5 users who want to use TCP/IP communication when
performing co-simulations with ADAMS/Controls, but don’t want to do a full
installation of ADAMS/Controls.

To install the ADAMS/Controls Thin Client:

1 Follow steps Step 1 on page 37 through Step 6 on page 38.


2 When prompted to select the products that you want to install, enter y for the
ADAMS/Controls Thin Client.
3 Continue with Step 8 on page 38 and complete the remaining steps in the
installation procedure.

Note: You must install the MSC.ADAMS Extension for MSC.EASY5 to use the
ADAMS/Controls Thin Client. For more information, see Installing the
MSC.ADAMS Extension for MSC.EASY5 on page 44.
install.book Page 42 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


42 Installing MSC.ADAMS on UNIX

Installing MSC.ADAMS Documentation


Note: If you chose to install the documentation during the installation process (Step
15 on page 39), you do not need to complete this procedure.

Follow these steps to install the documentation after the product has already been installed.
Enter the commands shown in the procedure in either uppercase or lowercase, depending
on your system. For example, when you mount the CD, the mount point could be either
/cdrom or /CDROM.

Note: You must have an Internet browser to view the documentation.

To install documentation:

1 Log on to the UNIX system where you installed the MSC.ADAMS software.
2 Insert the UNIX Online Documentation CD in the CD-ROM drive.
3 Enter the mount command for your platform.
Note: For a listing of mount commands for UNIX systems, see Platform-Specific
Commands on page 97.
If you are using a remote machine on your network to mount the CD-ROM drive,
you must have permission to access that machine from the installer’s account, with
a remote-shell, requiring no password. For example, if the remote machine’s
hostname is server1, you need to be able to enter the command rsh server1 (or
remsh server1, for HP systems) and be able to log on to server1 without entering a
password.

4 Change to the MSC.ADAMS installation directory by entering the following


command, where install_dir is the directory where you installed the MSC.ADAMS
software:
cd /install_dir

5 Locate the installation program (INSTALL.DOC or install.doc) using the


ls command for the CD-ROM mount point. For example, depending on your
system, enter one of the following:
ls /cdrom
ls /CDROM
install.book Page 43 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on UNIX 43

6 Copy the installation program on to your system using the following command:
cp /CDROM/INSTALL.DOC ./
7 Enter the following command to start the installation script:
./INSTALL.DOC
8 Enter the name of the directory where you installed the MSC.ADAMS software.
9 Select CD-ROM to install from the UNIX Online Documentation CD, or disk to
install from a disk drive where you copied the files.
10 Do one of the following:
■ If installing from disk, enter the disk mount point.
■ If installing from CD:
a At the hostname prompt, enter the name of the machine to which the CD-
ROM drive is attached.
b Enter the CD-ROM mount point at the prompt (for example, /cdrom).

11 Choose to install the MSC.ADAMS online help.


12 At each prompt, specify whether or not you want the online help installed for each
product. The default is whether or not the product itself is installed.
13 Verify that you have enough disk space to install the files. The space required to
install the files is shown at the left and the space you have available in the
installation directory is shown at the top.
14 After you have verified the availability of disk space, enter y.
If you do not have enough disk space, enter n. Then, either open another shell
window and free up space at the location you want to install or exit the installation
program and start over, selecting another location to install the MSC.ADAMS
documentation.
install.book Page 44 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


44 Installing MSC.ADAMS on UNIX

Installing the MSC.ADAMS Extension for MSC.EASY5


Note: This procedure is only necessary if you installed ADAMS/Controls.

To run MSC.ADAMS and MSC.EASY5 together, you must install the MSC.ADAMS
extension into EASY5. To import models into MSC.ADAMS that were exported from
EASY5 (containing components from licensed EASY5 libraries), you must also
configure your computer so that MSC.ADAMS knows how to find your MSC.EASY5
license. The following procedures explain how to do this.

To install the MSC.ADAMS extension for MSC.EASY5:

1 Make sure that both MSC.EASY5 and MSC.ADAMS have been installed.
2 Make sure you have permission (that is, root ('superuser') privilege) to add and
modify files in the MSC.EASY5 installation directory.
3 Identify the command line command used to start the MSC.ADAMS version
you will use with MSC.EASY5, for example, adams05r2.
Note: If you are unable to identify a command line command to run
MSC.ADAMS but you can identify the top-level directory of the
MSC.ADAMS installation, you can use -d "directory path" in place of
the command line command in the following steps.
4 Perform the following, depending on your platform:
■ On UNIX:

a Open an xterm window and set your working directory to a directory


outside the MSC.EASY5 installation directory tree.

b Start MSC.EASY5. The standard command is easy5x.

c In the MSC.EASY5 main window, from the File menu, select Open
Command Shell.

d At the prompt in the command shell, enter:


$EZHOME/install_adams_controls.ksh adams_command
where adams_command is the command line command from Step 3 above.
install.book Page 45 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on UNIX 45

■ On Windows:

a From the Start menu, point to Programs, point to MSC.Software, point to


MSC.EASY5 7.x, point to Shell, and then select MSC.EASY5 Command Shell.

b At the prompt in the command shell, enter:


install_adams_controls.ksh adams_command
where adams_command is the command line command from
Step 3 on page 44.
3 Type exit to close the command window.
4 If you started MSC.EASY5, from the File menu, select Quit.
The MSC.ADAMS extension installation is complete. Be sure to configure your
computer as described next.

To configure your computer to run licensed exported MSC.EASY5 models within


MSC.ADAMS:

1 Start MSC.EASY5.
2 From the File menu, select Open Command Shell.
3 At the prompt in the command shell, type easy5x -license.
MSC.EASY5 displays the licensing information, beginning with the type of license
and the server name (if a server license) or the path to the license file.
4 Write down the contents of the line that starts with Active license file(s), and the
value that appears in the line following it (for example, 1700@rainier).
install.book Page 46 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


46 Installing MSC.ADAMS on UNIX

5 Perform one of the following:


■ If the line is Active license file(s) [EASY5_LMD_LICENSE_FILE], set the environment
variable EASY5_LMD_LICENSE_FILE to the output value displayed in
Step 4 on page 45 (for example, 1700@rainier).
■ If the line is Active license file(s) [MSC_LICENSE_FILE], find the value of the
environment variable MSC_LICENSE_FILE to see what license file MSC.ADAMS
is using.
❖ If MSC.EASY5 and MSC.ADAMS are using different licenses (or license
servers), set LM_LICENSE_FILE to the value for the MSC.EASY5 license (for
example 2500@bosco).
❖ If MSC.EASY5 and MSC.ADAMS are using the same license, your
computer is configured properly.
6 For Windows platforms only, modify the Path environment variable to include the
path to the lib_DVF6 subdirectory of your MSC.EASY5 installation tree.
Note: This feature is only supported with the DVF6 Fortran compiler on
Windows.
install.book Page 47 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on UNIX 47

Duplicating and Installing MSC.ADAMS on Your Hard Disk


This section explains how to install the MSC.ADAMS products when you have multiple
file servers and single-to-multiple clients. You first copy the files from the CD to your hard
disk. You then use this disk, or depot, location to install MSC.ADAMS on the other file
servers. Copying the MSC.ADAMS products from your hard disk is more convenient for
additional network installations then installing all of them from the CD.

Note: This procedure requires up to 660 MB of scratch disk space.

To install MSC.ADAMS from your hard disk:

1 Change to the installation directory. Note that this directory must be accessible to
all departmental file servers on which you are to install MSC.ADAMS products.
2 Start the installation program.
3 At the prompt, enter 2 to select the option, Duplicate the CD-ROM to your hard disk.
4 Enter the name of the installation directory of depot.
The default location is your current directory (that is, the installation directory).
Select the default by pressing Enter on your keyboard.
5 At the hostname prompt, enter the name of the machine to which the
CD-ROM drive is attached.
6 Enter the CD-ROM mount point (for example, /cdrom). For a listing of mount
commands for UNIX systems, see Platform-Specific Commands on page 97.
install.book Page 48 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


48 Installing MSC.ADAMS on UNIX

7 From the list of platforms on the Products CD that appears, enter the type of
platform on which you are installing MSC.ADAMS. An example of the list of
platforms is shown below. You can either copy the files for just one platform or
for all the platforms you need at one time.

*************************************************************
Platforms on this local CD are:

rhlinux - Linux ix86 systems running Red Hat 9


irix32 - SGI systems running IRIX
*************************************************************

8 At the prompt, enter 9 to select the option Exit.


9 Log on to one of your departmental file servers.
10 In the system window, enter the mkdir command to create an installation directory
and change to that new directory using the cd command.
We recommend that you create a directory called /usr/adamsx for the MSC.ADAMS
products. In the directory name, x represents the current version of MSC.ADAMS.
11 Mount the disk location that contains the copy of the MSC.ADAMS products
(see Step 4).
12 Copy the installation program to this machine by entering the following command,
where install_dir is the name of the disk depot:
cp /install_dir/INSTALL.ADAMS ./
13 Start the installation program and enter 3 to select the option, Install MSC.ADAMS from
your hard disk (step #2).

14 Enter the name of the MSC.ADAMS installation directory. This is the location
where you want to install the MSC.ADAMS software (see Step 10).
15 Enter the disk depot mount point. This is the directory you used in
Step 4 on page 47.
install.book Page 49 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on UNIX 49

16 Follow Steps 7 through 13 in Installing MSC.ADAMS on UNIX on page 33, to


complete the installation for the file server.
17 Now repeat the instructions for each file server.

Installing on a Heterogeneous Network


If you are installing the MSC.ADAMS products for use on different UNIX platforms (Sun,
SGI, and so on) you are performing a heterogeneous installation. MSC.ADAMS
installation directory can support multiple platforms. Binary files specific to each
supported platform are located in architecture directories under each product directory.
You can use a single installation directory to install all supported MSC.ADAMS platform
binaries or multiple file servers to spread out the NFS load to multiple systems.

To install MSC.ADAMS on a heterogeneous network:


■ Follow the instructions in Installing MSC.ADAMS on page 37, for each platform
on which you are installing MSC.ADAMS products.
install.book Page 50 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


50 Installing MSC.ADAMS on UNIX
install.book Page 51 Friday, August 5, 2005 11:37 AM

4 Licensing on UNIX

Overview
This chapter provides instructions for licensing the MSC.ADAMS
software. You must complete the steps in Installing MSC.ADAMS on
UNIX on page 33 before licensing the MSC.ADAMS software. Refer
to UNIX Installation Roadmaps on page 119 for which procedure in
this chapter to follow depending on your system configuration.
The chapter contains the sections:
■ About the MSC.ADAMS License Server, 52

■ Licensing MSC.ADAMS When File and License Server


Are Same Machine, 55

■ Licensing MSC.ADAMS When File and License Server


Are Different Machines, 56

■ Starting the MSC.ADAMS License Server, 58

■ Restarting the MSC.ADAMS License Daemons, 59

■ Changing the License to Point to a Different License


Server, 62

■ Verifying a Successful License, 62


install.book Page 52 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


52 Licensing on UNIX

About the MSC.ADAMS License Server


MSC.ADAMS licensing requires that you operate at least one license server. You can
optionally request to use three MSC.ADAMS license servers (see About a Three-Server
Configuration on page 53). The MSC.ADAMS license servers can be on any of the
supported MSC.ADAMS platforms connected to the network that runs the MSC.ADAMS
products. MSC.ADAMS uses the FLEXlm® license system from Macrovision.
The following sections give you tips for selecting the license server and explain different
configurations:
■ Tips for Selecting Your MSC.ADAMS License Server, 52

■ About a Three-Server Configuration, 53

■ About the License File Format, 53

Tips for Selecting Your MSC.ADAMS License Server


You should select the machine to use as your MSC.ADAMS license server using the
following guidelines. The machine should:
■ Have a local file system that can hold the MSC.ADAMS license server
software. If you use a remotely mounted file system for your MSC.ADAMS
license server, you risk having your users unable to run
the MSC.ADAMS products if the server goes down. You should never
run the MSC.ADAMS license server from a diskless node on the network.
■ Have enough system resources to robustly serve the number of MSC.ADAMS
users requesting a license.
■ Be on the same local area network (or sub-net) if the number of MSC.ADAMS
license requests is in the range of hundreds per day.
■ Be reliable. This means that it has reliable power and its hardware subsystems
are in good working order.
You should consolidate your licenses because redundant license servers add complexity.
Evaluate what you really want to achieve by using redundant license servers. More robust
hardware systems, instead of redundant license servers, can better ensure less down time.
You should look at ways to consolidate the number of license servers at the departmental,
division, or even at the company-wide level.
install.book Page 53 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on UNIX 53

About a Three-Server Configuration


For each of the license types, you can have three machines on your network that are
designated as license servers. Selecting three license servers lets you back up the main
license server in case one of the other machines is down. If your password certificate lists
three machines under the Server Host Name column, you purchased the three-server
configuration. You must install your passwords on each of the servers as explained in
Licensing MSC.ADAMS When File and License Server Are Same Machine on page 55.
You should log in to one of the servers and open three shell windows. Log in to the other
two servers in the different shell windows and repeat the procedures in this chapter for
each server. You also need to start each of the license servers as explained in Starting the
MSC.ADAMS License Server on page 58. The order of startup is not critical. The first
machine, however, to start the license daemons becomes the master server and serves
licenses until it is unavailable.

About the License File Format


The license file sent by MSC.Software is complete, except for the path to the license
daemon and the server name. The installation program will add this information when you
select Option 4 from the installation menu.

Sample MasterKey license


SERVER srvr21 83090b8f 1700
DAEMON MSC /usr/local/flexlm/msc
FEATURE CAMPUS MSC 2004.0331 31-mar-2004 2000 EC9FE6333D61B3B3584C \
ISSUED=03-dec-2003 ck=69 SN=1379876-cae4e9f3971c2cfcf675
FEATURE ADAMS_View MSC 2004.0331 31-mar-2004 1 5CBFE6F3A24FF84DA501 \
VENDOR_STRING="PID:10108,10208,10215 BLV:33 GROUP:CAMPUS,1" \
ISSUED=03-dec-2003 ck=84 SN=940426-17cbf8c0864988d6c4d0

Sample traditional license


SERVER L30131 00047652480a 1700
DAEMON MSC /your_path/msc
FEATURE ADAMS_View MSC 2005.0608 08-jun-2005 2 DDD03A3855FBFA721BB3 \
VENDOR_STRING=PID:10108,10208,10215,10229 HOSTID=00047652480a \
ISSUED=08-jun-2004 ck=48 SN=1364576-86ceaa6c30812cfc97ff
install.book Page 54 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


54 Licensing on UNIX

Following is an explanation of the components in your license:


■ SERVER keyword - The SERVER line contains the MSC.ADAMS license
server’s hostname, unique hostid, and the TCP socket number that the
procedures will use to communicate with license daemons.
■ DAEMON keyword - The DAEMON line contains MSC (the name of the
MSC.ADAMS license daemon) and the file system path to find that
daemon.
■ FEATURE keyword - FEATURE lines are the license for MSC.ADAMS
software. A FEATURE line always contains:
❖ FEATURE keyword
❖ FEATURE name - The name of the license.
❖ Name of the MSC.ADAMS license daemon (should be the same as the
DAEMON line).
❖ Version number - The major revision number of MSC.ADAMS for
which the license will authorize use. You can also run previous
versions of MSC.ADAMS that have a revision number less than the
revision number of your license.
❖ Expiration date - The date on which the license expires.
❖ Number of licenses granted (or tokens needed) - The number of
simultaneous uses of the product that the license authorizes.
Note: If the FEATURE name is CAMPUS, this value contains the
total number of tokens available.
❖ VENDOR_STRING - The company (MSC.Software) that issued the
password.
❖ ISSUED date - The date on which the license was issued. It acts as a
time-stamp on the password; it is used with the SUPERSEDE keyword.
❖ HOSTID - The optional host ID locks the use of the product to a
particular system.
install.book Page 55 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on UNIX 55

Licensing MSC.ADAMS When File and License Server Are


Same Machine
Follow the instructions below if your license server and file server are the same machine.
You should log in to the system that appears in the Server Host Name column on the
password certificate.

To set up licensing:

1 If necessary, start the installation program.


2 Enter 4 to select the option, Install MSC.ADAMS passwords on this license server.
3 Enter y if the name of the MSC.ADAMS license server that appears in the prompt
is the same as the machine designated as the server in your e-mail password
certificate. (Depending on the type of license you have, the server name may not
be listed in your e-mail certificate; in this case, use the hostid instead.)
The default is the machine to which you are logged on. If this is not your license
server, enter n, log in to your license server, and start the procedure again.
4 Follow the instructions in the e-mail password certificate to locate the information
required for licensing your MSC.ADAMS software.
5 At the prompt Are your passwords in a file e-mailed from MSC.Software?, enter y.
6 Enter the name of the text file that contains your passwords.
The installation program reads this file and constructs a properly formatted license
data file (license.dat) for you.
7 If the installation program cannot read the file, open the original file and verify
that you cut the information required for licensing at the correct locations.
8 Continue with Starting the MSC.ADAMS License Server on page 58.
install.book Page 56 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


56 Licensing on UNIX

Licensing MSC.ADAMS When File and License Server Are


Different Machines
Follow the instructions below if your license server and file server are different machines
or if you purchased a three-server configuration. You should log in to the system that
appears in the Server Host Name column on the password certificate.
If you are installing passwords for a three-server configuration, you should log in to one
of the servers and open three shell windows. Log in to the other two servers in the different
windows and repeat the instructions in this section for each server.

1 If necessary, start the installation program.


2 At the prompt, enter 4 to select the option, Install MSC.ADAMS passwords on this license
server.

3 Enter y if the name of the MSC.ADAMS license server that appears in the prompt
is the same as the machine designated as the server in your e-mail password
certificate. (Depending on the type of license you have, the server name may not
be listed in your e-mail certificate; in this case, use the hostid instead.)
The default is the machine to which you are logged on. If this is not your license
server enter n, log on to your license server, and start again.
4 Enter the name of the installation directory you created for the MSC.ADAMS
products.
5 At the hostname prompt, enter the name of the machine to which the CD-ROM
drive is attached.
6 Enter the CD-ROM mount point (for example, /cdrom).
7 Enter the type of platform you want to install.
8 Select the MSC.ADAMS licensing file by entering y at the prompt and entering n
to the remaining MSC.ADAMS products.
9 Follow the instructions in the e-mail password certificate to locate the information
required for licensing your MSC.ADAMS software.
10 At the prompt Are your passwords in a file e-mailed from MSC.Software?, enter y.
install.book Page 57 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on UNIX 57

11 Enter the name of the text file that contains your passwords.
The installation program reads this file and constructs a properly formatted license
data file (license.dat) for you.
12 If the installation program cannot read the file, open the original file and verify
that you cut the information required for licensing at the correct locations.
13 Continue with Starting the MSC.ADAMS License Server on page 58.
install.book Page 58 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


58 Licensing on UNIX

Starting the MSC.ADAMS License Server


Follow the instructions below for all of the license types, as well as the three-server
configuration. For three-server configurations, you must repeat this procedure on
each license server. You must enter the commands on each license server within one
minute.

To restart the MSC.ADAMS license server:

1 If necessary, start the installation program.


2 At the prompt, enter 5 to select the option, Start the MSC.ADAMS license server on
this system. The MSC.ADAMS license daemons are automatically started.

Continue with the next section to allow the license daemons to automatically
restart when you reboot your system.
install.book Page 59 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on UNIX 59

Restarting the MSC.ADAMS License Daemons


You must modify the reboot procedure on your license servers to include a restart of
the MSC.ADAMS license daemons during a system reboot. Follow the instructions
below for all three of the license types, as well as the three-server configuration. For
three-server configurations, you must repeat this procedure on each license server.

To restart the MSC.ADAMS license daemons:

1 Change to the directory /install_dir/network/arch, where install_dir is the


directory where the MSC.ADAMS products are installed and arch is the
platform type of your license server.
2 Locate the file reboot.txt.
3 The information in this file goes into different files on different systems. Find
your platform type below, and follow the instructions to add the
MSC.ADAMS license server startup commands to your system.

Hewlett Packard HP-UX


a Log on as root.
b Change to the directory rc2.d by entering cd /sbin/rc2.d.
c Enter the command ls *adams* to locate the file. The files in the rc2.d
directory begin SXX, where XX is a number from 01 to 99.
d Open the file that begins SXXMSC, where XX is greater than 50 and less
than 99 into a text editor so that you can edit it. If the file does not exist,
create it.
You must have permission to edit or create this file. If necessary, use the
following command to set permissions:
chmod 777 SXXMSC
e Enter the commands found in the reboot.txt file. To change the install_dir
text, change to your installation directory.
install.book Page 60 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


60 Licensing on UNIX

Hewlett Packard HP-IA64 Itanium


a Log on as root.
b Change to the directory rc2.d by entering cd /sbin/rc2.d.
c Enter the command ls *adams* to locate the file. The files in the rc2.d
directory begin with SXX, where XX is a number from 01 to 99.
d Open the file that begins with SXXMSC, where XX is greater than 50 and
less than 99, into a text editor so that you can edit it. If the file does not
exist, create it.
You must have permission to edit or create this file. If necessary, use the
following command to set permissions:
chmod 777 SXXMSC
e Enter the commands found in the reboot.txt file. To change the install_dir
text, change to your installation directory.

IBM AIX Systems


a Log on as root.
b Change to directory /etc by entering cd /etc.
c Copy the reboot.txt file, and then rename it as rc.MSC:
cp /install_dir/network/ibmrs/reboot.txt /etc/rc.MSC
d Using a text editor, open the file, rc.MSC, and replace every occurrence
of the text INSTALL_DIR with the name of the MSC.ADAMS installation
directory.
e Save the file, and then exit the text editor.
f Use the command mkitab to add a record of the file /etc/inittab to ensure
that the license server is started during a system reboot:
mkitab “MSC:2:wait:/etc/rc.MSC”
install.book Page 61 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on UNIX 61

Linux
❖ To add the MSC.ADAMS license server startup commands, follow the
instructions provided by your operating system.

Silicon Graphics IRIX Systems


Sun Solaris (UltraSPARC) Systems
a Log on as root.
b Change to the directory rc2.d by entering cd /etc/rc2.d.
c Enter the command ls *adams* to locate the file. The files in the rc2.d
directory begin with SXX, where XX is a number from 01 to 99.
d Open the file that begins with SXXMSC, where XX is greater than 50 and less
than 99, into a text editor so that you can edit it. If the file does not exist,
create it.
You must have permission to edit or create this file. If necessary, use the
following command to set permissions:
chmod 777 SXXMSC
e Enter the commands found in the reboot.txt file. Be sure to change the
install_dir text to be your installation directory.

The licensing of MSC.ADAMS products is complete. You can now verify that installation
was successful by following the procedures in Verifying a Successful License on page 62.
install.book Page 62 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


62 Licensing on UNIX

Changing the License to Point to a Different License Server


1 Start the installation program with the client argument (for example, install.adams
client).

2 Enter the port number that is used by the license server.


3 Enter the name of the MSC.ADAMS license server that has the licenses you want
to use. This can be a different machine than the machine on which you installed
the MSC.ADAMS products, which is the file server.

Verifying a Successful License


Follow the procedure below to verify that the MSC.ADAMS installation was successful.

1 If necessary, start the installation program on the license server.


2 At the prompt, enter 7 to select the option, Generate a problem report. This
automatically generates a report called PROBLEM.RPT that you can use to verify
the MSC.ADAMS installation.
3 Using a text editor, open the PROBLEM.RPT file and review the information.
Verify that each of the features installed are able to retrieve a license.
install.book Page 63 Friday, August 5, 2005 11:37 AM

5 Installing MSC.ADAMS on Windows

Overview
The following sections explain how to install MSC.ADAMS
products and online documentation by running the MSC.ADAMS
installation program. It also includes information on licensing your
MSC.ADAMS.
■ Installing MSC.ADAMS, 64

■ Installing the ADAMS/Controls Thin Client, 73

■ Installing MSC.ADAMS in Silent Mode (Batch), 74

■ Modifying the Installation, 77

Note: You must have administrative privileges to install


MSC.ADAMS.
install.book Page 64 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


64 Installing MSC.ADAMS on Windows

Installing MSC.ADAMS
This section shows you how to install MSC.ADAMS software and documentation. If you
already installed MSC.ADAMS for this release, refer to Modifying the Installation on
page 77.

To install MSC.ADAMS:

1 On your machine, log on to an account that has administrative privileges.


2 Insert the Windows Products CD into your CD-ROM drive.
The MSC.ADAMS for Windows Installation System dialog box appears. If the
setup program does not start automatically, open Windows Explorer, select your
computer’s CD-ROM drive, and double-click setup.exe. The Welcome dialog box
appears.
3 Select MSC.ADAMS 2005 r2.
4 Select Next.
5 Read the license agreement, and then select I accept.
The Customer Information window appears as shown in Figure 6 on page 65.
install.book Page 65 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on Windows 65

Figure 6. Customer Information Window

6 In the Customer Information window, enter your user and company name, and
then select one of the following:
■ Anyone who uses this computer (all users) - Anyone logged on to this machine can
run MSC.ADAMS.
■ Only for me - A user must be logged on using the user name and password that
was used at the time of installation.
7 Select Next.
The Setup Type window appears as shown in Figure 7 on page 66.
install.book Page 66 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


66 Installing MSC.ADAMS on Windows

Figure 7. Setup Type Window

8 Select the type of installation you want to perform:


■ Full - Installs all MSC.ADAMS products and documentation. This is the best
option if you’re using an MSC.MasterKey license. Also use this option if you
want to use this machine as a file server, allowing other machines to client to it.
■ User Selectable - Allows you to select the specific MSC.ADAMS products and
documentation you want to install.
■ Client - Allows you to link to a file server, where a full installation has already
been installed. You must know the location of the shared installation directory
before you continue with the installation.
9 If you would prefer MSC.ADAMS to be installed in a folder other than the default
destination folder, select Browse, and then select the desired folder.
The default directory for installing MSC.ADAMS products is
c:\MSC.Software\MSC.ADAMS\x, where x is the version of the products you are
installing.
install.book Page 67 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on Windows 67

10 Select Next.
11 Depending on your selection in Step 8 on page 66, do one of the following:
■ Full - Continue to Step 12.

■ User Selectable - In the Select Components window, select the components


you want to install. Then, select Next.
Note: You cannot install the ADAMS/Controls Thin Client at the same
time as other MSC.ADAMS products. You must install it by itself.
See Installing the ADAMS/Controls Thin Client on page 73 for more
information.
■ Client - Enter the location of the shared directory where MSC.ADAMS is
installed.
12 Confirm the installation settings and then select Next to begin the installation.
After the installation is complete, the Choose MSC.ADAMS Default Compiler
window appears as shown in Figure 8 on page 68.
install.book Page 68 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


68 Installing MSC.ADAMS on Windows

Figure 8. Default Compiler Window

13 Select the compiler you want to use, and then select Next.
The License Setup window appears as shown in Figure 9 on page 69.
install.book Page 69 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on Windows 69

Figure 9. License Setup Window

14 Enter the name of the license server or the path to your license file. If you
don’t enter this information here, you can specify your license using the
procedure in Specifying your License on page 81.
15 Select Next.
16 Specify whether or not you want to install the various desktop icons. If you
select Yes, then select the products for which you want icons created, as shown
in Figure 16 on page 69.
install.book Page 70 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


70 Installing MSC.ADAMS on Windows

Figure 10. MSC.ADAMS Desktop Icons Window

17 Select Next.
The Solver File Association window appears as shown in Figure 11 on page
71.
install.book Page 71 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on Windows 71

Figure 11. Solver File Association Window

18 Select the solver product with which you want .acf files on this machine
associated. You can also select not to associate .acf files with an MSC.ADAMS
product.
19 Select Next.
The Install File Permissions window appears as shown in Figure 12 on page 72.
install.book Page 72 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


72 Installing MSC.ADAMS on Windows

Figure 12. Install File Permissions Window

20 Select whether you want the installation files left as read-only or made writable.
■ If you leave them read-only, you may have to change the properties of the
example files before running through the various tutorials.
■ If you make them writable, be sure to use extreme caution while using the
installation files because you can overwrite them.
21 Select Next.
22 To view the readme file, select I would like to view the README file.
23 Select Finish.
24 If you installed ADAMS/Controls, you need to install the MSC.ADAMS
Extension for MSC.EASY5. Previously, this was done automatically by the
ADAMS/Controls install program. For more information, refer to Installing the
MSC.ADAMS Extension for MSC.EASY5 on page 44.
25 If you want to use this installation as a file server (so that other machines can
install from it), share the installation directory.
install.book Page 73 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on Windows 73

Installing the ADAMS/Controls Thin Client


The ADAMS/Controls Thin Client is a subset of ADAMS/Controls. This client can be
helpful to MSC.EASY5 users who want to use TCP/IP communication when performing
co-simulations with ADAMS/Controls, but don’t want to do a full installation of
ADAMS/Controls.

To install the ADAMS/Controls Thin Client:

1 Follow steps Step 1 on page 64 through Step 7 on page 65.


2 In the Select Setup Type window, select User Selectable.
3 Select ADAMS/Controls Thin Client, making sure no other products are selected.
4 Continue with Step 12 on page 67 and complete the remaining steps in the
installation procedure.
install.book Page 74 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


74 Installing MSC.ADAMS on Windows

Installing MSC.ADAMS in Silent Mode (Batch)


By creating a batch setup file, you can automate the process of performing identical
installs. You can customize this file with your preferred settings, put it on a server, and let
other users perform their own installation using the same settings. This section shows you
how to create and run the batch file.

To create the batch setup file:

1 From the Start menu, select Run.


2 In the Run dialog box, enter the following:
E:\msc.adams\setup.exe -r -f1”c:\temp\mysetup.iss”
where:
■ E: is the location of your setup.exe file

■ f1 is a lower-case f and the number 1

■ c:\temp\mysetup.iss is the location and name of the batch setup file

3 Select OK.
4 Follow the installation instructions in the section, Installing MSC.ADAMS, on page
64.
The batch installation file (.iss) is created.
install.book Page 75 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on Windows 75

To perform a batch installation:

1 Check the contents of the batch setup (.iss) file to make sure that it contains the
correct installation directory location. For example, if it specifies
D:\MSC.Software\MSC.ADAMS\2005r2 as the install directory, and you don’t have a D:
drive, you can change it to C:\MSC.Software\MSC.ADAMS\2005r2. See Figure 13 on page
76.
2 In a command window, enter the following command:
E:\msc.adams\setup.exe -s -f1”c:\temp\mysetup.iss”
where:
■ E: is the location of your setup.exe file

■ f1 is a lower-case f and the number 1

■ c:\temp\mysetup.iss is the location and name of the batch setup file.


install.book Page 76 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


76 Installing MSC.ADAMS on Windows

Figure 13. Sample setup.iss file

Installation
directory

License server
install.book Page 77 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Installing MSC.ADAMS on Windows 77

Modifying the Installation


Using the Add/Remove Programs capability of your Windows operating system, you can
modify your current installation by installing or deleting specific components. You can
also uninstall previous versions of MSC.ADAMS products and documentation. Note that
the uninstall program does not remove files that were created after the initial installation,
such as your license.dat.

To modify the MSC.ADAMS installation:

1 From the Start menu, point to Settings, and then select Control Panel.
2 Select Add/Remove Programs.
3 Select MSC.ADAMS 2005 r2, and then select Change/Remove.
4 Follow the instructions on your screen to modify the MSC.ADAMS installation.
Select the Next button to continue through the installation.
The installation program asks you to choose the type of uninstall you want to
perform. You can select:
■ Modify - Lets you select the files that you want to add or delete.

■ To install new components, check the box next to the component you
want to add.
■ To uninstall (delete) components, clear the selection of the box next to
the component you want to uninstall.
■ Repair - Reinstalls all components from the last install.

■ Remove - Removes all MSC.ADAMS product and documentation files. It does


not remove any files that you created in the installation directory.
5 When the uninstall is complete, select Finish.
install.book Page 78 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


78 Installing MSC.ADAMS on Windows
install.book Page 79 Friday, August 5, 2005 11:37 AM

6 Licensing on Windows

Overview
MSC.ADAMS products use a license server to manage the access to
its products. Therefore, before you can run the products you just
installed, you must license them. The next sections explain more
about MSC.ADAMS licensing, the initial licensing options, and how
you can manage the licensing after you’ve initially licensed the
products.
■ Licensing Basics, 80

■ Specifying your License, 81

■ Running Two Versions of MSC.ADAMS Products, 82

■ Setting up a Windows License Server, 83

■ Replacing Codes (Licenses) on an Existing Windows


Server, 84

■ Customizing End-User License Administration, 85


install.book Page 80 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


80 Licensing on Windows

Licensing Basics
You can license MSC.ADAMS products in the following ways:
■ Set up a license server that is available to your users through the network, and
set up the number of users who can use MSC.ADAMS. The number of users
who can run MSC.ADAMS concurrently depends on the number of licenses
you purchased. Refer to your password certificate for information on the
number of users who can run MSC.ADAMS.
You can run the license server on one machine or on three. We strongly
recommend that you use a one-server configuration, however. If you select a
three-server configuration, the machines act as backups to the other machines.
You must install passwords on all of the server machines to set up a three-server
configuration.
You can select to load only the licensing tools on the license server and install
the MSC.ADAMS products only on the clients.
You also can set up the licensing so that it is locked to a particular machine or
node. If your MSC.ADAMS licensing is node-locked, then users can only run
MSC.ADAMS products on that machine. To see if you have purchased node-
locked licensing, refer to your password certificate.
■ Set up a client using an existing license server.
In both cases, the procedure for licensing MSC.ADAMS is the same. For a detailed
description of the license file, see About the License File Format on page 53.
install.book Page 81 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on Windows 81

Specifying your License


You typically specify the license for MSC.ADAMS during the installation procedure (see
Step 14 on page 69). However, you can modify the license type, location, or name at any
time following the installation.
If you already installed MSC.ADAMS on your network and have a license server running,
you can enter the hostname and TCP/IP port number of the license server to run
MSC.ADAMS from that license server. If a license server is running on the current
machine, the installation program shuts it down.
For MSC.ADAMS installations, the TPC/IP port number defaults to 1700 and is in the
following format, where hostname is the name of the host:
1700@hostname
If you do not know the name of the host, enter the command hostname at a command
prompt. Or, you can refer to the SERVER line of your password certificate/license file.

To specify or modify MSC.ADAMS licensing:

1 From the Start menu, point to Programs, point to MSC.Software, point to MSC.ADAMS
2005 r2, and then select ADAMS - License Setup.

2 Enter the name of the license server or the path to your license file.
3 Select Finish.
install.book Page 82 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


82 Licensing on Windows

Running Two Versions of MSC.ADAMS Products


You can run two versions of MSC.ADAMS on the same machine. Both of the
versions can be installed on the same machine.

To install and license two versions of MSC.ADAMS:

1 Install the new version of MSC.ADAMS from the CD, as explained in


Installing MSC.ADAMS on Windows on page 63.
2 License the new version of MSC.ADAMS from the CD, as explained in
Specifying your License on page 81.
3 Set up previous version of MSC.ADAMS as client to the same machine.
For example, if the previous version of MSC.ADAMS was 2003, do the
following:
◆ From the Start menu, point to Programs, point to MSC.Software, point to
MSC.ADAMS 2003, point to License, and then select Client.

◆ Enter the name of the machine, and then select OK.


install.book Page 83 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on Windows 83

Setting up a Windows License Server


You can use your Windows machine as the license server for other MSC.ADAMS
installations.

Note: You must have the license file saved to your machine before completing this
procedure.

To set up the license server:

1 Insert the Windows Products CD into your CD-ROM drive.


The MSC.ADAMS for Windows Installation System dialog box appears. If the
setup program does not start automatically, open Windows Explorer, select your
computer’s CD-ROM drive, and double-click setup.exe. The Welcome dialog box
appears.
2 Select MSC.Licensing 9.2a.
The installation program displays an information window with your FLEXlm host
ID. Make sure this is the same host ID included in your license file.
3 Select Yes.
4 Select Next.
5 Read the license agreement, and then select I Accept.
6 Select the directory where you want MSC.Licensing installed, and then select Next.
7 Verify the installation settings, and then select Next.
8 Select your license file.
9 Select Finish.
10 Exit the installation program.
For more information on FLEXlm, refer to your FLEXlm documentation.
install.book Page 84 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


84 Licensing on Windows

Replacing Codes (Licenses) on an Existing Windows Server


Follow these steps if you have an existing MSC.ADAMS installation and have received
new codes (as a renewal, change, and so on).

To update your passwords:

1 Place the new codes as a license file in the same directory as the existing license.dat
file. Name it license_new.dat. Change the SERVER and DAEMON lines in the new
license file to include the same port number, server name, and paths as the existing
file. For example:
SERVER server1 123465 1700
DAEMON MSC c:\MSC.Software\MSC.Licensing\9.2\msc.exe
2 Use Windows Explorer to rename the existing license.dat file to license_old.dat, and
the new file to the current license file name (license.dat).
3 Run lmtools.exe, and then select Config Services.
4 Select the appropriate license server in the box below (if you have more than one).
5 Select the Start/Stop/Reread tab.
6 Select ReRead License File.
This should re-read the license.dat file and enable your new licenses. If there is a problem,
or if the licenses are still not available, restart the system.
install.book Page 85 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on Windows 85

Customizing End-User License Administration


You can use the daemon options file provided with the license manager to customize the
installation. This option file allows the end-user to:

■ Reserve licenses for specified users or groups of users.


■ Restrict the use of the software to certain people.
■ Set software time-outs.
■ Log activity for use with an optional report writer.
Note: For more information, refer to
http://www.macrovision.com/solutions/esd/support/index.html.

These options and their functions are listed below.

Table 6. Daemon Options File Options

The option: Does the following:

RESERVE Ensures that the MSC.ADAMS products are always available to


one or more users, or on one or more host computer systems.
INCLUDE Allows the end user to specify a list of users who are allowed to
access the MSC.Software software.
EXCLUDE Allows the end user to restrict certain people from using
MSC.ADAMS products.
GROUP Allows the specification of a group of users for use with other
commands.
LMREMOVE Allows the end user to remove a stalled license. The minimum
interval value is 600 seconds (10 minutes).
TIMEOUT Allows licenses that are idle to be returned to the free pool for use
by another user. The default value is 900 seconds (15 minutes).
REPORTLOG Specifies that a log file be written suitable for use by the report
writer.
install.book Page 86 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


86 Licensing on Windows

Table 6. Daemon Options File Options (continued)

The option: Does the following:

NOLOG Filters messages of a specified type out of the daemon's log


output.

To use the daemon options:

1 Create a daemon option file.


2 List its pathname as the fourth field in the DAEMON line of the license.dat
file.
A daemon options file consists of lines in the following format:
RESERVE number feature {USER | HOST | DISPLAY | GROUP} name
INCLUDE feature {USER | HOST | DISPLAY | GROUP} name
EXCLUDE feature {USER | HOST | DISPLAY | GROUP} name
GROUP name <list_of_users>
TIMEOUT feature timeout_in_seconds
NOLOG {IN | OUT | DENIED | QUEUED }
REPORTLOG file
The system ignores lines beginning with the # character, which you can use to specify
comments. If the filename in the REPORTLOG line starts with a + character, the old
report log file will be reopened for appending.
For example, the following options file reserves one copy of AVIEW for user pat, three
copies for user lee, and one copy for anyone on a computer with the hostname of terry.
In addition, it does not allow the user joe to use AVIEW. It also causes the log file to
omit QUEUED.
RESERVE 1 AVIEW USER pat
RESERVE 3 AVIEW USER lee
RESERVE 1 AVIEW HOST terry
EXCLUDE AVIEW USER joe
NOLOG QUEUED
install.book Page 87 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Licensing on Windows 87

If this data were in the file \install_dir\network\options.fil on Windows or the


/install_dir/network/arch/options file on UNIX (where install_dir is the directory where
MSC.ADAMS is installed), then you modify the license file DAEMON line as follows:
On Windows:
DAEMON msc \install_dir\network\msc.exe
\install_dir\network\options.fil
On UNIX:
DAEMON MSC /install_dir/network/arch/MSC
/install_dir/network/arch/options.file
install.book Page 88 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


88 Licensing on Windows
install.book Page 89 Friday, August 5, 2005 11:37 AM

7 Running MSC.ADAMS Products

Starting MSC.ADAMS Products


This section describes how you can start your MSC.ADAMS
products on UNIX and on Windows.

Starting MSC.ADAMS Products on UNIX


The MSC.ADAMS Toolbar is a starting point to using
MSC.ADAMS products on UNIX. The toolbar is shown below.

MSC.ADAMS Toolbar tool - Right-click to


set up Toolbar, manage memory models,
access online help and Technical
Support resources, and more.

Product tools - Click to run product or right-click


to configure products and create user libraries.
Hold the cursor over a tool to see the name of
the associated product.
You can also use the MSC.ADAMS Toolbar to:
■ Customize, keep track of, and organize multiple libraries
of standard MSC.ADAMS products
■ Create binaries
■ Manage custom memory models and product preferences
For more information on these or other MSC.ADAMS Toolbar
operations, see the Running and Configuring online help (from the
Help menu in any product, select MSC.ADAMS Help, near the bottom of
the pane on the left, select Running and Configuring MSC.ADAMS).
install.book Page 90 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


90 Running MSC.ADAMS Products

To start a product on UNIX:

1 To display the MSC.ADAMS Toolbar, at the command prompt, enter the command
adamsx where x is the version number, for example adams05r2.

2 Click on the tool representing the product you want to start.


Note: We recommend that you use the MSC.ADAMS Toolbar to start your
MSC.ADAMS products, but if you want to automate certain operations,
use the text-based Program Menu. For more information, see the Running
and Configuring online help.

Starting MSC.ADAMS Products on Windows


You start any MSC.ADAMS product from the Start menu. You can also use the Start menu
to:
■ Change your license type
■ Generate problem reports
■ Uninstall products, demonstrations, and documentation
■ Set MSC.ADAMS preferences
For more information on these or other operations, see the Running and Configuring
online help.

To start a product on Windows:


■ From the Start menu, point to Programs, point to MSC.Software, point to
MSC.ADAMS 2005 r2, point to the name of the product you want to start, and then
select the product type. For example, point to AEngine, and then select ADAMS -
Engine.

Tip: Select the corresponding desktop icon for the product, if you installed it
on your desktop.
install.book Page 91 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Running MSC.ADAMS Products 91

Setting Preferences
This section describes how you can set preferences, such as your working directory,
graphics setting, and memory model size.

Setting Preferences on UNIX


You use the Registry Editor from the MSC.ADAMS Toolbar to set a variety of
preferences. For information on the preferences you can set, see the Running and
Configuring online help.

To display the Registry Editor:


■ From the MSC.ADAMS Toolbar, right-click any product tool, and then select Change
<Product Name> Settings.

Setting Preferences on Windows


You use the Settings menu to modify:
■ Graphics settings
■ HOOPS settings
■ Memory model size

To display the Settings dialog box:


■ From the Start menu, point to Programs, point to MSC.Software, point to
MSC.ADAMS 2005 r2, and then select ADAMS - Settings.
install.book Page 92 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


92 Running MSC.ADAMS Products

Setting Your Working Directory


During a session in a default or custom product, you can select the directory where you
want to place your model and output files.
For ADAMS/View, you can set the working directory from the Welcome dialog box.

To set your working directory:

1 From the File menu, select Select Directory.


2 In the dialog box that appears, select the working directory.
install.book Page 93 Friday, August 5, 2005 11:37 AM

8 UNIX Administration and Configuration

Overview
This chapter describes some basic administration and configuration
operations you might want to perform after you install the
MSC.ADAMS products, and others that you might need to perform
periodically as you obtain new passwords. These operations include
the following:
■ Setting Up the Client Machine, 94

■ Updating Passwords, 95

■ Platform-Specific Commands, 97
install.book Page 94 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


94 UNIX Administration and Configuration

Setting Up the Client Machine


If you did not install the MSC.ADAMS software as root, you need to make MSC.ADAMS
available to all the users by creating a link from a user directory to the installation
directory.

To set up a client machine:

1 Mount the MSC.ADAMS installation directory from the central file server to each
machine that is going to run MSC.ADAMS.
2 Create a startup command on each user’s machine in the directory of your choice,
using the commands:
ln -s /install_dir/mdi adams05r2
install.book Page 95 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


UNIX Administration and Configuration 95

Updating Passwords
If you receive new passwords from MSC.Software, follow the instructions below to
update your passwords. If you receive new software along with the passwords, you should
follow the complete installation instructions in Installing MSC.ADAMS on UNIX on
page 33.
Note: If the license server started with root, you must be root to stop and start it.

The following are two ways to update your passwords:


■ Using the MSC.ADAMS Installation Script, 95
■ Updating Outside the Installation Script, 96

Using the MSC.ADAMS Installation Script

To update passwords using the installation script:

1 Log on to the MSC.ADAMS license server.


2 If necessary, start the installation program.
3 At the prompt, enter 6 to select the option, Stop the MSC.ADAMS license server(s).
4 At the prompt, enter 4 to select the option, Install MSC.ADAMS passwords on this license
server.

5 Enter the new information by entering the name of the file containing the
information.
6 At the prompt, enter 5 to select the option, Start the MSC.ADAMS license server on this
machine.
install.book Page 96 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


96 UNIX Administration and Configuration

Updating Outside the Installation Script

To update passwords outside the installation script:

1 Place the new codes as a license file in the same directory as the existing
license.dat file. Name it license_new.dat. Change the SERVER and DAEMON lines in
the new license file to include the same port number, server name, and paths as
the existing file. For example:
SERVER server1 123465 1700
DAEMON MSC /msc/flexlm/bin/msc
2 Rename the existing license.dat file to license_old.dat, and rename the new file to
the current license file name (license.dat):
# mv license.dat license_old.dat
# mv license_new.dat license.dat
3 Use the lmreread command to force the lmgrd daemon to reset using the new
license file.
# flexlm_install_dir/lmreread -c <path>/license.dat

where flexlm_install_dir is the directory where FLEXlm is installed.


Note: If you do not have an lmreread executable, copy lmdown and name it
lmreread.

You should now be able to run MSC.ADAMS products using the new licenses. If this
fails, kill and restart the daemons as follows:
# flexlm_install_dir/lmdown -c <path>/license.dat
# flexlm_install_dir/lmgrd -c <path>/license.dat
install.book Page 97 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


UNIX Administration and Configuration 97

Platform-Specific Commands
Table 7 lists common UNIX commands for installing from CD. In the commands:
■ The # character in device file names represents the SCSI address of the media
unit.
■ cdrom_dir is the name of the CD-ROM drive.

Table 7. Installation Commands

Machine: Commands:

HP-UX pfs_mount -o rrip /dev/dsk/c#t#d# cdrom_dir


HP-Itanium or
mount -r -F cdfs -o cdcase -o rr /dev/dsk/c#t#d# cdrom_dir
Note: The -o rr option requires that you install patches
for the Rockridge Standard. For a complete list of
patches, refer to the MSC.ADAMS Hardware
Specifications at
http://www.mscsoftware.com/support/prod_support/ada
ms/.

IBM AIX RS/6000 mount -v cdrfs -r /dev/cd0 cdrom_dir

Linux mounts automatically or


mount /mnt/cdrom

SGI mounts by itself if vold is running or


mount -rt iso9660 /dev/scsi/sc0d#l0 cdrom_dir

Sun mounts by itself if vold is running or


mount -F hsfs -r /dev/dsk/c0t6d0s2 cdrom_dir
install.book Page 98 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


98 UNIX Administration and Configuration
install.book Page 99 Friday, August 5, 2005 11:37 AM

9 Troubleshooting

Overview
This chapter describes how to generate problem reports to send to
MSC.ADAMS Technical Support. It also lists some common
problems that can occur when installing, updating, and running
MSC.ADAMS software, and recommends solutions to those
problems.
■ Troubleshooting on Windows, 100

■ Troubleshooting on UNIX, 111


If you do not find your problem in this chapter or if the
recommended solution does not solve your problem, then:
■ Refer to the MSC.ADAMS Knowledge base at
http://www.mscsoftware.com/support/prod_support/adams/
■ Contact MSC.ADAMS Technical Support as explained in
Getting Help on page 19.
install.book Page 100 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


100 Troubleshooting

Troubleshooting on Windows
Generating Problem Reports
You can generate a report that examines your system configuration and places important
debugging information in the file adams_problem_report.txt. If you have problems running
ADAMS, you can generate this report and review it or send it to MSC.ADAMS Technical
Support by fax or e-mail. As you review the report, refer to the sections in this chapter for
explanations of many of the error messages that appear in the report.
Note: For correct results, you must run the problem report from the license server,
not the client machine.

To generate and review a report:

1 From the Start menu, point to Programs, point to MSC.Software, point to


MSC.ADAMS 2005 r2, and then select ADAMS - Troubleshooting Report.

MSC.ADAMS creates a problem report in your home directory.


2 To review the report, open it into a text editor, such as Notepad.

Obtaining New Passwords


If you need new passwords, you can obtain them by calling your MSC.Software Sales
Administrator.
When requesting new passwords, provide the following information:
■ Request number and Schedule 1 number (Sched 1 #) from your password
certificate. The request number is at the top of the certificate and the Schedule 1
number is in the Administrative Information section.
■ System ID and host name of your CPU. Instructions for obtaining this
information for your particular CPU are in the hardware and software
specifications.
install.book Page 101 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 101

Licensing Problems
The following are some common licensing problems:
■ License Troubleshooting Checklist, 102

■ Troubleshooting the License Server, 103

■ MSC.ADAMS FLEXlm Service Does Not Start, 104

■ Client Cannot Connect to Server, 105

■ Not Licensed to Run Product, 106


install.book Page 102 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


102 Troubleshooting

License Troubleshooting Checklist


Here are some tips for checking the license installation:

1 Check the license.dat file:


■ Is the format correct? Check the lines: SERVER, DAEMON, FEATURE. For more
on license.dat, see About the License File Format on page 53.
■ Does the SERVER information match the machine hostname and hostid?
The data in the file license.dat must match the information on your password
certificate. The file license.dat is located in the subdirectory network of your
MSC.ADAMS installation directory. The licensing portion of the installation
program automatically creates license.dat if your site has network licensing. You
have network licensing if your password certificate lists the name of a network
license server. For more information on license.dat, see About the License File
Format on page 53.
2 Check the license.log (in the network subdirectory under the MSC.ADAMS
install_dir):

■ Are the FEATURE names listed?


■ Are there any error messages?
3 Can the client or server machine access the license server?
Tip: Use the program lmtools as explained in Troubleshooting the License
Server.
install.book Page 103 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 103

Troubleshooting the License Server


To help you track and manage license data, we’ve included a license tool, called lmtools.
The tool is in the network subdirectory of your MSC.ADAMS installation directory and it
is called lmtools.exe. For detailed information on using lmtools, refer to the lmtools
documentation.

To run lmtools:
■ From the Start menu, point to Programs, point to MSC.Software, point to
MSC.ADAMS 2005 r2, and then select FLEXlm Configuration Utility.

To check that the license manager daemon (lmgrd and msc) is running:

1 Right-click a blank area on the Start taskbar.


2 From the menu that appears, select Task Manager.
3 Select Processes.
4 Double-click Image Name.
5 Check that both msc.exe and lmgrd.exe are in the list.
Tip: If the lmgrd and msc are not in the list, see Licensing Problems on page 101.
install.book Page 104 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


104 Troubleshooting

MSC.ADAMS FLEXlm Service Does Not Start

Error message:
Error: Could not start Service on machine 'xxxxxx' error 1067.

Description:
You receive this error message if FLEXlm won't start as a service when you
select Start License Server.

Solution:
Depending on the cause of the error do one or more of the following:
■ The Simple TCP/IP Services software needs to be installed. To install it:
1 Insert the Windows Products CD into your CD-ROM drive.
2 From the Start menu, point to Settings, and then select Control Panel.
3 From the Control Panel folder, double-click Network, and then select the
tab Protocols.
4 Select TCP/IP Protocol, and then select Add.
5 Select Close.
■ The hostname of your computer has been changed and the DNS needs to be
reconfigured. To reconfigure the DNS:
1 Insert the Windows Products CD into your CD-ROM drive.
2 From the Start menu, point to Settings, and then select Control Panel.
3 From the Control Panel folder, double-click Network, and then select the
tab Protocols.
4 Select TCP/IP Protocol, and then select Properties.
5 Make sure the hostname is correct, and then select Close.
The above steps install or configure the necessary software to run the license
manager. Once completed, your machine reboots and the MSC.ADAMS
FLEXlm server starts.
install.book Page 105 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 105

Client Cannot Connect to Server

Error message:
Client cannot connect to license server on the server machine.

Description:
You receive this error message when the license manager daemon (lmgrd and msc)
is not running or your MSC_LICENSE_FILE environment variable is incorrect.

Solution:
Check the Services tool on the Control Panel folder for the FLEXlm license server.
Then, try restarting the daemon. If MSC.ADAMS still does not run, check to make
sure MSC_LICENSE_FILE is not set. The environment variable is not needed for
server licenses for MSC.ADAMS. At runtime, the mdi.bat script sets the variable.

To check that the environment variable is not set:


1 From a DOS prompt, type set | more.
If the variable doesn’t display, it is not set. Continue to step 3.
2 To unset the variable, type set MSC_LICENSE_FILE= and then press Enter.
The variable is now unset.
3 If you still cannot connect to the server, contact MSC.ADAMS Technical
Support and provide a problem report as explained in Generating Problem
Reports on page 100.

You can also check to ensure that the client can contact the server. If it
cannot, there is a problem with the connection. See your system
administrator.

To check if the client can contact the server:


■ At a DOS prompt, enter the following, where server_name is the name of
the server:
ping server_name

If there is no reply, see your system administrator.


install.book Page 106 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


106 Troubleshooting

Not Licensed to Run Product

Error message:
Cannot run <product>. Call your systems support personnel.

Description:
The system ID information in your password does not match the system ID you
are currently using.

Solution:
Make sure the system ID listed on your password certificate matches the physical
address of your CPU. If the network card has changed since MSC.Software
created the password, you need to get new passwords as explained in Obtaining
New Passwords on page 100.

TCP/IP Installation Problems


The following error indicates that TCP/IP is not installed correctly:
{hostname}: socket() call failed (-57, 17:10047) WinSock error code
Check all of the following:
■ TCP/IP Protocol network software is installed.
■ TCP/IP Protocol is configured.
■ Simple TCP/IP service is started.
■ Your network card supports TCP/IP.
install.book Page 107 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 107

Network License Daemon Problems


The next sections explain how to troubleshoot network license daemon problems:
■ Overview of Network Licensing Problems, 108

■ Incorrect Server Name in license.dat, 109

■ License Daemons Started on Machine Whose hostid is Not the Same as


Password Certificate hostid, 110
install.book Page 108 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


108 Troubleshooting

Overview of Network Licensing Problems


Network license daemons errors can occur because:
■ The daemons have not been started or have been shut down.
■ The daemons have been started more than once.
■ The hostid in license.dat is incorrect.
■ The hostid of the machine on which the license daemons have been started is
not the same as the hostid listed on the password certificate.
■ A different software product’s license daemon uses the same socket address.
When any of these occur, you usually see the following error message:
Checkout of XXXXX failed.
client:cannot connect to license server (Connection refused)
Cannot run ADAMS/XXX
Cannot grant a license
Call your system support personnel
Solutions to each of these errors are given in the next sections. In addition, you should
examine the license.log file to determine the cause of network licensing errors. license.log
is located in the subdirectory network, under your installation directory. The first and last
30 lines in license.log are useful for identifying errors. Some of the error messages listed
in the next sections can appear in license.log.
install.book Page 109 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 109

Incorrect Server Name in license.dat

Error message:
(lmgrd) "que": Not a valid server hostname, exiting

Description:
This message appears in the license.log file if the server name in the license.dat file
does not match the hostname of your machine.

Solution:
If the server name and hostname do not match, change the server name in the
license.dat file to match the string returned by the command hostname.
install.book Page 110 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


110 Troubleshooting

License Daemons Started on Machine Whose hostid is Not the Same as


Password Certificate hostid

Error message:
(msc) Wrong hostid, exiting (expected 760a0a2, got 76260a0a1)

Description:
This message appears in the license.log file if the license daemons were started on
a different hostid than the one listed on your password certificate.

Solution:
Shutdown the daemons and restart them on the correct hostid, as instructed in the
section, Specifying your License on page 81.
If the hostid does not match, you may need a new password. For instructions, see
Obtaining New Passwords on page 100.
install.book Page 111 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 111

Troubleshooting on UNIX
Generating Reports and Verifying Software
The installation program provides two options for performing troubleshooting operations.
■ Generate a problem report - Examines your system configuration and places
important debugging information in the file PROBLEM.RPT. If you have
problems running MSC.ADAMS, you can generate this report and review it or
send it to MSC.ADAMS Technical Support by fax or e-mail. As you review the
report, refer to License Server Problems on page 113 for explanations of many
of the error messages that appear in the report.
Note: For accurate results, you must run the problem report from the license
server, not the client machine.
■ Check hostid on the system - Returns the hardware identification number from
the system that is used for MSC.ADAMS licensing. This identification number
is also included in the problem report.

To generate a problem report:


■ From the installation program menu, enter 7 to select the option, Generate a
problem report.

If you do not have write permission in the working directory, you will be
prompted to enter another directory in which to write the files.

To check hostid on the system:


■ From the installation program menu, select 8 to select the option, Check hostid on
this system.
install.book Page 112 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


112 Troubleshooting

Obtaining New Passwords


If you need new passwords, you can obtain them by calling your MSC.Software Sales
Administrator.
Please provide the following information:
■ License agreement number and Schedule 1 number (Sched 1 #) from your
password certificate. The license agreement number is in the License Contract
Information section of the password certificate and the Schedule 1 number is in
the Administrative Information section of the password certificate.
■ System ID and host name of your CPU. Instructions for obtaining this
information for your particular CPU are in the hardware and software
specifications.

About License Server System Resources


The MSC.ADAMS license server runs two processes: lmgrd and MSC. These processes do
not require significant CPU use even for a large number of licenses.
Each time an MSC.ADAMS product talks to the license daemons, a process file descriptor
is used. It is very rare that normal MSC.ADAMS license transactions would use up all of
the available process file descriptors. The process file descriptor is allocated by a TCP
socket. If you have a large number of licenses (200+), you should confirm that the number
of sockets and process file descriptors limitations for your system is adequate to handle all
of the licenses. See your operating system’s documentation for the maximum number of
file descriptors available on the system designated as your MSC.ADAMS license server.
The license server writes a debug log file as it runs. It writes an entry for each license
request and return. If the file becomes too large, you can edit the log file periodically.
The MSC.ADAMS license daemons send small amounts of data across the network. Each
license transaction requires approximately 1 KB of data. If there are a lot of transactions
(in the hundreds), the network bandwidth use can become significant. If this happens, you
should consider keeping the license server on the same local area network as the one being
used for the MSC.ADAMS products.
install.book Page 113 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 113

License Server Problems


License server errors can occur for the following reasons:
■ The daemons have not been started or have been shut down.
■ The daemons have been started more than once.
■ The hostid in license.dat is incorrect.
■ A different software product’s license daemon uses the same socket address.

License Troubleshooting Checklist


Here are some tips for checking the license installation:

1 Check the license.dat file:


■ Is the format correct? Check the lines: SERVER, VENDOR, FEATURE.
■ Are the continuation characters where they need to be?
■ Does the SERVER information match the machine hostname and hostid?
2 Check the license.log (in the /install_dir/network/arch directory, where install_dir is
the installation directory and arch is the MSC.ADAMS platform type on which
you are running the license server):
■ Are the FEATURE names listed?
■ Are there any error messages?
3 Can the client or server machine access the license server? See Client Cannot
Connect to License Server on page 116.
install.book Page 114 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


114 Troubleshooting

Formatting Errors in license.dat

Description
The data in the license.dat file must match the information on your password certificate.
The installation program automatically creates license.dat file. For more on license.dat, see
About the License File Format on page 53.

Solution:
■ Recreate the license server as explained in Updating Passwords on page 95.

Server Hostname Invalid in license.dat

Error message:
(lmgrd) “xxx”: Not a valid server hostname, exiting

Description:
This error message appears in the license.log file if the server name in the license.dat
file does not match the hostname of the system on which you are attempting to run
the MSC.ADAMS license server.

Solution:
If the server name and hostname do not match, stop the license daemons, change the
server name in the license.dat file to match the string returned by the command
hostname, and then restart the daemons. You can stop and start the MSC.ADAMS
license server using the MSC.ADAMS installation program.
install.book Page 115 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 115

Wrong Hostid in license.dat

Error message:
(MSC) Wrong hostid, exiting (expecting 760a0a22, got 760b0a24)

Description:
You receive this message if the hostid of the machine on which you are starting the
license daemons on does not match the SERVER hostid in the license.dat file,

Solution:
If the hostid in the file that MSC.ADAMS sent to you does not match, you will need
a new password. See Obtaining New Passwords on page 100.

Incorrect Feature Line in license.log

Error message:
MSC: inconsistent encryption code for XXXXXX

Description:
This error message is found in the MSC.ADAMS license server debug log file
(license.log). The MSC.ADAMS vendor daemon (MSC) has found a FEATURE line
that it cannot recognize. This is typically due to a typographical error in that
FEATURE line. The FEATURE line in question corresponds to the MSC.ADAMS
product that you tried to run.

Solution:
Check the FEATURE line for typographical errors. You should always enter your
password through the MSC.ADAMS installation program.
install.book Page 116 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


116 Troubleshooting

Client Cannot Connect to License Server

Error message:
client: cannot connect to license server (Connection refused)

Description:
This error typically occurs because the MSC.ADAMS license server daemons are
not running. The MSC.ADAMS software you are trying to run reports this error.

Solution:
You should log on to the machine designated as your MSC.ADAMS license server
and verify that the license daemons are running. If you suspect that the license
daemons have not started or have shut down, you can check the status of the license
daemons.

To check the status of the license server:


1 From the /install_dir/network/arch directory, enter the following command:
./lmstat -a -c license.dat

where install_dir is the installation directory and arch is the MSC.ADAMS


platform type on which you are running the license server.
If the license daemons are down, the following message appears:
lmstat - Copyright (C) 2002 Macrovision Corporation
Flexible License Manager status on Mon. 5/12/2003 10:00
Error getting status:
Cannot connect to license server
(-15,570:146) “Connection refused”)
2 Run the installation program and select 6 (in case part is running).
3 Run the installation program and select 5. For more information, see
Restarting the MSC.ADAMS License Daemons on page 59.
4 Confirm that the daemons have started by entering the command:
./lmstat -a -c license.dat
install.book Page 117 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Troubleshooting 117

License Daemon Already Running

Error message:
(lmgrd) Retrying socket bind (address in use: port 1700)

Description:
This message is reported by the license daemon when it starts up. You receive this
error message if the license daemon is already running, or some other application on
the system is already using the TCP socket address as specified in the license.dat
file. It indicates that the license daemons have been started more than once.

Solution:

To stop the daemons and restart them:


1 From the MSC.ADAMS installation directory, run the installation program, and
select option 6 to stop the daemons.
2 Continue to enter this command until the following message appears:

Shutdown failed: Cannot connect to license server


3 Restart the daemons by selecting option 5.

For instructions on how to start daemons from a boot file, see Restarting the
MSC.ADAMS License Daemons on page 59.
install.book Page 118 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


118 Troubleshooting

License Daemon for a Different Software Product Uses Same Socket


Address

Error message:
(lmgrd) Retrying socket bind (address in use: port 1700)

Description:
This message appears if a license daemon for a different software product uses the
same socket address as MSC.

Solution:
1 Select a new socket address for the license daemons and verify that you are
not using a reserved socket number by checking the /etc/services file.
Socket addresses are listed in the last entry on the SERVER line(s) of
license.dat. They are four-digit integer and must be greater than 1200.

2 At the prompt, enter 6 to stop the license daemons.


3 Open the license.dat file in a text editor and change the socket number (the
last number on the VENDOR or DAEMON line).
4 At the prompt, enter 5 to restart the license daemons.

Allocating Disk Space for Temporary Files


You can change the location of temporary files created when running MSC.ADAMS. By
defining the environment variable TMPDIR, you can point to a file system that has enough
disk space to hold your temporary files. You must select a file system that has space and
a directory that you have write permissions for. For example, if you are using a UNIX
C-shell you would add the following line to your .cshrc file:

setenv TMPDIR /new_location


install.book Page 119 Friday, August 5, 2005 11:37 AM

A UNIX Installation Roadmaps

Overview
This appendix describes the overall steps or roadmaps that you perform
to install MSC.ADAMS products depending on your network
configuration. Use these roadmaps to guide your installation. For
complete installation and licensing instructions, see Installing
MSC.ADAMS on UNIX on page 33. The roadmaps are:
■ File Server, License Server, and Client - Same Machine, 121
■ File Server and License Server - Same Machine, Client -
Different Machine, 122
■ File Server and Client - Same Machine, License Server -
Different Machine, 123

■ File Server, License Server, and Client - Different


Machines, 125
■ File Server - Different Machine, License Server and Client -
Same Machine, 127
■ Multiple File Servers, Central License Server, and Single-to-
Multiple Clients, 129
■ Different UNIX Platforms - Heterogeneous Network, 131
install.book Page 120 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


120 UNIX Installation Roadmaps

For assistance in determining which roadmap to follow, see Table 8. It lists the seven types
of configurations and the page that contains the roadmap for performing installation and
licensing for that type of configuration. If your configuration is not in the table, review the
options in each chapter and choose the ones that best fit your needs.
Table 8. Types of Installation and License Configurations

If the file server The license server Then follow


The client is:
is: is: roadmap on:

Same machine Same machine Same machine 121

Same machine Same machine Different machine 122

Same machine Different machine Same machine 123

Different machine Different machine Different machine 125

Different machine Same machine Same machine 127

Multiple machines One machine One to multiple 129


machines

Differing UNIX platform(s) on any of the machines 131


(heterogeneous network)
install.book Page 121 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


UNIX Installation Roadmaps 121

File Server, License Server, and Client - Same Machine


This type of installation is typical of a single machine on a network. Only one engineer
uses MSC.ADAMS so the installation is placed on that person’s machine.
Table 9. Roadmap When All Same Machine

Do the following: For more information, see the section:

1. Log on to the MSC.ADAMS user’s --


workstation.

2. Create an installation directory. Creating the Installation Directory, 34

3. Copy and start the MSC.ADAMS Copying and Starting the MSC.ADAMS
installation program. Installation Program, 35

4. Install MSC.ADAMS. Installing MSC.ADAMS, 37

5. Install network passwords. Licensing MSC.ADAMS When File and


License Server Are Same Machine, 55

6. Start the license server. Starting the MSC.ADAMS License Server, 58

7. Install the online documentation. Installing MSC.ADAMS Documentation, 42

8. Modify the system startup Restarting the MSC.ADAMS License


procedures so they include the Daemons, 59
restarting of the MSC.ADAMS
license manager.

9. Generate a troubleshooting report Verifying a Successful License, 62


to verify that all products and files
were properly installed.
install.book Page 122 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


122 UNIX Installation Roadmaps

File Server and License Server - Same Machine,


Client - Different Machine
This type of installation is typical of larger networks, where there may be one-to-many
MSC.ADAMS users. Because there is more than one MSC.ADAMS user, a central server
is used as both file server and license server. The MSC.ADAMS users work on personal
machines, and access the software across the network using NFS.
Table 10. Roadmap When Only Client Different

Do the following: For more information, see the section:

1. Log on to the central server. --

2. Create an installation directory. Creating the Installation Directory, 34

3. Copy and start the MSC.ADAMS Copying and Starting the MSC.ADAMS
installation program. Installation Program, 35

4. Install MSC.ADAMS. Installing MSC.ADAMS, 37

5. Install network passwords. Licensing MSC.ADAMS When File and


License Server Are Same Machine, 55

6. Start the license server. Starting the MSC.ADAMS License Server, 58

7. Install the online documentation. Installing MSC.ADAMS Documentation, 42

8. Modify the system startup Restarting the MSC.ADAMS License


procedures so they include the Daemons, 59
restarting of the MSC.ADAMS
license manager.

9. Generate a troubleshooting Verifying a Successful License, 62


report to verify that all products
and files were properly installed.
install.book Page 123 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


UNIX Installation Roadmaps 123

File Server and Client - Same Machine, License Server -


Different Machine
This type of installation is typical of a large network where central servers have been
designated as license servers. MSC.ADAMS users work on personal machines and
access the software locally to increase performance.
Table 11. Roadmap When Only License Server Different

Do the following: For more information, see the section:

1. Log on to the MSC.ADAMS user’s --


workstation.
2. Create an installation directory. Creating the Installation Directory, 34

3. Copy and start the MSC.ADAMS Copying and Starting the MSC.ADAMS
installation program. Installation Program, 35

4. Install MSC.ADAMS. Installing MSC.ADAMS, 37

5. Install the online documentation. Installing MSC.ADAMS Documentation, 42

6. Exit from the installation program. --

7. Log on to the license server --


machine.
8. Create a directory for Creating the Installation Directory, 34
MSC.ADAMS on the license
server.
9. Copy and start the installation Copying and Starting the MSC.ADAMS
program from the CD to this Installation Program, 35
directory.
10. Install network passwords, which Licensing MSC.ADAMS When File and
unloads license software. License Server Are Different Machines, 56

11. Start the license server. Starting the MSC.ADAMS License Server, 58
install.book Page 124 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


124 UNIX Installation Roadmaps

Table 11. Roadmap When Only License Server Different (continued)

Do the following: For more information, see the section:

12. Modify the system startup Restarting the MSC.ADAMS License


procedures so they include the Daemons, 59
restarting of the MSC.ADAMS
license manager.
13. Generate a troubleshooting report Verifying a Successful License, 62
to verify that all products and files
were properly installed.
install.book Page 125 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


UNIX Installation Roadmaps 125

File Server, License Server, and Client - Different Machines


This type of installation is typical of a large network where central servers have been
designated as file servers and license servers. MSC.ADAMS users work on personal
machines, and access the software across the network using NFS.
Table 12. Roadmap When All Different Machines

Do the following: For more information, see the section:

1. Log on to the central NFS server. --

2. Create an installation directory. Creating the Installation Directory, 34

3. Copy and start the MSC.ADAMS Copying and Starting the MSC.ADAMS
installation program. Installation Program, 35

4. Install MSC.ADAMS. Installing MSC.ADAMS, 37

5. Install the online documentation. Installing MSC.ADAMS Documentation, 42

6. Exit from the installation program. --

7. Log in to the license server --


machine.

8. Create a directory for Creating the Installation Directory, 34


MSC.ADAMS on the license
server.

9. Copy and start the installation Copying and Starting the MSC.ADAMS
program from the CD to this Installation Program, 35
directory.

10. Install network passwords, which Licensing MSC.ADAMS When File and
unloads license software. License Server Are Different Machines, 56

11. Start the license server. Starting the MSC.ADAMS License


Server, 58
install.book Page 126 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


126 UNIX Installation Roadmaps

Table 12. Roadmap When All Different Machines (continued)

Do the following: For more information, see the section:

12. Modify the system startup Restarting the MSC.ADAMS License


procedures so they include the Daemons, 59
restarting of the MSC.ADAMS
license manager.

13. Generate a troubleshooting report Verifying a Successful License, 62


to verify that all products and files
were properly installed.
install.book Page 127 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


UNIX Installation Roadmaps 127

File Server - Different Machine, License Server and


Client - Same Machine
This type of installation is typical of a medium-sized network where a departmental NFS
server is used. A single MSC.ADAMS user works on a personal machine, and accesses
the software across the network through NFS. The MSC.ADAMS user’s machine also acts
as the license server.
Table 13. Roadmap When License Server and Client the Same Machine

Do the following: For more information, see the section:

1. Log on to the central NFS server. --

2. Create an installation directory. Creating the Installation Directory, 34

3. Copy and start the MSC.ADAMS Copying and Starting the MSC.ADAMS
installation program. Installation Program, 35

4. Install MSC.ADAMS. Installing MSC.ADAMS, 37

5. Install the online documentation. Installing MSC.ADAMS Documentation, 42

6. Exit from the installation program. --

7. Log on to license server and client. --

8. Mount MSC.ADAMS installation --


directory from file server on license
server system through NFS.

9. Create a directory for MSC.ADAMS Creating the Installation Directory, 34


on this machine.

10. Copy and start the installation Copying and Starting the MSC.ADAMS
program from the CD to directory. Installation Program, 35

11. Install network passwords. Licensing MSC.ADAMS When File and


License Server Are Different Machines, 56
install.book Page 128 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


128 UNIX Installation Roadmaps

Table 13. Roadmap When License Server and Client the Same Machine (continued)

Do the following: For more information, see the section:

12. Start the license server. Starting the MSC.ADAMS License


Server, 58

13. Modify system startup procedures so Restarting the MSC.ADAMS License


they include the restarting of the Daemons, 59
MSC.ADAMS license manager.

14. Generate a troubleshooting report to Verifying a Successful License, 62


verify that all products and files were
properly installed.
install.book Page 129 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


UNIX Installation Roadmaps 129

Multiple File Servers, Central License Server, and


Single-to-Multiple Clients
This situation is typical of large networks where multiple departmental file servers
exist to split the NFS load of widely used applications such as MSC.ADAMS. The
network also has a separate designated central license server machine. MSC.ADAMS
users access the software through NFS from their personal machines. In this example,
a central NFS server is used to create an online hard-disk copy of the UNIX Products
CD-ROM, which makes installations on the multiple departmental file servers much
easier.
Note: This procedure requires approximately 640 MB of scratch disk space.

Table 14. Roadmap When Multiple File Servers, Single License Server

Do the following: For more information, see the section:

1. Log in to the central NFS server. --

2. Create an installation directory. Creating the Installation Directory, 34

3. Copy MSC.ADAMS products to Duplicating and Installing MSC.ADAMS


hard disk. on Your Hard Disk, 47

4. Exit the installation program. --

5. Log into a departmental file server. --

6. Automount to the hard disk to which --


you copied the MSC.ADAMS
products in Step 3.

7. Create an installation directory and --


change to it.

8. Copy the MSC.ADAMS installation --


directory from the hard disk (see
Step 3) to this directory.

9. Run the installation program to Duplicating and Installing MSC.ADAMS


install from disk. on Your Hard Disk, 47
install.book Page 130 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


130 UNIX Installation Roadmaps

Table 14. Roadmap When Multiple File Servers, Single License Server (continued)

Do the following: For more information, see the section:

10. Install the online documentation. Installing MSC.ADAMS


Documentation, 42

11. Exit from the installation program. --

12. Repeat steps 5 to 10 for each --


departmental file server.

13. Log in to the central license server. --

14. Create a directory for MSC.ADAMS Creating the Installation Directory, 34


on this machine.

15. Copy and start the installation Copying and Starting the MSC.ADAMS
program from the CD to the new Installation Program, 35
directory.

16. Install network passwords. Licensing MSC.ADAMS When File and


License Server Are Different
Machines, 56

17. Start the license server. Starting the MSC.ADAMS License


Server, 58

18. Repeat Steps 11 to 15 if you have --


redundant file servers.

19. Modify the system startup procedures Restarting the MSC.ADAMS License
so they include the restarting of the Daemons, 59
MSC.ADAMS license manager.

20. Generate a troubleshooting report to Verifying a Successful License, 62


verify that all products and files were
properly installed.
install.book Page 131 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


UNIX Installation Roadmaps 131

Different UNIX Platforms - Heterogeneous Network


This situation is similar to the previous, except that multiple platforms may be involved.
The license server can be UNIX or Windows. However, the file servers must be
homogeneous. In other words, the UNIX file servers can only serve UNIX clients, and
Windows file servers can only serve Windows clients. You can use different UNIX
platforms for clients as long as the files for their platforms have been loaded onto the file
server. Note that you may experience degraded performance for a Windows client due to
network issues.
Table 15. Roadmap for Heterogeneous Network

Do the following: For more information, see the section:

1. Log in to the central NFS server. --

2. Copy and start the installation program. Copying and Starting the MSC.ADAMS
Installation Program, 35

3. Install MSC.ADAMS. --

4. Install the online documentation. Installing MSC.ADAMS Documentation, 42

5. Exit from the installation program. --

6. Repeat Steps 1 through 5 for any --


additional platforms and file servers.

7. Log in to the license server machine. --

8. Create a directory for MSC.ADAMS Creating the Installation Directory, 34


on this machine.

9. Copy and start the installation program Copying and Starting the MSC.ADAMS
from the CD to the new directory. Installation Program, 35

10. Install network passwords. Licensing MSC.ADAMS When File and


License Server Are Different Machines, 56
install.book Page 132 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


132 UNIX Installation Roadmaps

Table 15. Roadmap for Heterogeneous Network (continued)

Do the following: For more information, see the section:

11. Start the license server. Starting the MSC.ADAMS License


Server, 58

12. Modify the system startup procedures Restarting the MSC.ADAMS License
so they include the restarting of the Daemons, 59
MSC.ADAMS license manager.

13. Generate a troubleshooting report to Verifying a Successful License, 62


verify that all products and files were
properly installed.
install.book Page 133 Friday, August 5, 2005 11:37 AM

Index

Symbols
(lmgrd) “xxx”: Not a valid server hostname, exiting error message 111
(lmgrd) Retrying socket bind (address in use: port 1700) error message
114, 115
(msc) Wrong hostid, exiting (expecting 760a0a22, got 760b0a24)
error message 112

A
ADAMS/Controls Thin Client
installing on UNIX 41
installing on Windows 73

B
Batch installation 74

C
Checking
disk space for documentation 40, 43
disk space for products 38
Client
can’t connect to server 104
defined 12
installing ADAMS/Controls Thin on UNIX 41
installing ADAMS/Controls Thin on Windows 73
setting up 94
install.book Page 134 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


134 Index

client: cannot connect to license server (Connection refused) error message 113
Commands, platform-specific UNIX 97
Compilers, selecting 68
Configuration, three-server 53
Contacting Technical Support 19
Copying installation program 35

D
Daemon
restarting 114
uses same socket address 115
Desktop icons, installing 69
Directory, setting working 92
Disk space availability
checking for documentation 40, 43
checking for products 38
Disk space for temporary files 115
Documentation
about CD for 11
installing on UNIX 42
installing on Windows 64
Duplicating and installing MSC.ADAMS on hard disk 47

E
EASY5, installing MSC.ADAMS extension for 44
Environment variable, setting MSC_LICENSE_FILE 104
Extension, MSC.ADAMS for EASY5 44
install.book Page 135 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Index 135

F
Feature names 14
File server, defined 12
Files, temporary require more disk space 115
Format of license file 53
Formatting, incorrect in license.dat 101

G
Generating reports 108
Getting help 19
Graphics requirements 29

H
Hard disk, installing MSC.ADAMS on 47
Hardware and software specs 25
Help
getting 19
installing online on UNIX 42
installing online on Windows 64
Heterogeneous networks
installing 49
road map for 129
install.book Page 136 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


136 Index

I
Installation
ADAMS/Controls thin client on UNIX 41
ADAMS/Controls thin client on Windows 73
for multiple file servers and clients 47
MSC.ADAMS on hard disk 47
MSC.EASY5 extension 44
performing on heterogeneous network 49
procedure on Windows 64
requirements 8
road maps 117
running a basic on UNIX 37
silent mode (batch) on Windows 74
types of 12
verifying successful 62
Installation Menu, illustrated 36
Installation program, copying and starting 35
Installing MSC.ADAMS passwords
when file and license server are different 56
when file and license server the same 55

L
License administration, customizing 85
License daemons
problems 106
restarting 59
with same socket address 115
License file format 53
install.book Page 137 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Index 137

License server
cannot connect to 104
defined 12
doesn’t start as service 103
incorrect name for 107
setting up 83
starting 58
three-server configuration 53
tips for selecting 52
troubleshooting 102
license.dat
described 101, 111
format of 53
formatting problems 111
formatting problems in 101
incorrect server name in 107
typographical errors in 101
license.log, described 106
Licensing
basics of 80
MSC.MasterKey 10
not licensed to run product 105
problems 101
requirements 30
running two versions of MSC.ADAMS 82
setting when file and license server are different 56
setting when file and license server are same 55
traditional 10
install.book Page 138 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


138 Index

M
Modifying installation on Windows 77
Mount commands 97
MSC.ADAMS
starting products 89
MSC.ADAMS CDs, about 11
MSC.ADAMS Extension for EASY5, installing 44
MSC.ADAMS products
installing basic on UNIX 37
installing on hard disk 47
licensing two versions of 82
licensing when file and license server are different 56
licensing when file and license server are same 55
making available to users 94
modifying installation on Windows 77
names for 13
not licensed to run 105
selecting 56
uninstalling on Windows 77
ways to license 80
MSC.ADAMS Toolbar
about 89
MSC.MasterKey license 10
MSC.Software Technical Support, contacting 19
msc: inconsistent encryption code for XXXXXX error message 112
MSC_LICENSE_FILE environment variable 104
install.book Page 139 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Index 139

N
Names
incorrect 107
MSC.ADAMS products 13
Native window driver, selecting 39
Network licensing
customizing end-user 85
daemon problems 106–107
Network, installing on heterogeneous 49
New passwords, obtaining 100, 109

O
Obtaining new passwords 109
One-server configuration, explained 80
Online help
installing on UNIX 42
installing on Windows 64
Option
1) Install MSC.ADAMS from CD-ROM 37
2) Duplicate the CD-ROM to your hard disk 47
3) Install MSC.ADAMS from your hard disk (step #2) 48
4) Install MSC.ADAMS passwords on this license server 55, 56, 95
5) Start the MSC.ADAMS license server on this system 58
7) Generate a problem report 62, 108
8) Check hostid on this system 108

P
Password certificate 9
Passwords
entering new 95
obtaining 100, 109
Platform support, dropped 31
Plugin installation configurations 17
install.book Page 140 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


140 Index

Preferences, setting 91
Problem
Client cannot connect to server 104
daemons started more than once 114
incorrect formatting in license.dat 101
incorrect formatting in license.dat 111
incorrect server name in license.dat 107
incorrect server name in license.dat 111
license daemons not started or shut down 113
license daemons use same socket address 115
more disk space required for temporary files 115
MSC.ADAMS FLEXlm service does not start 103
not licensed to run product 105
Password certificate hostid different 107
Password certificate hostid is different 112
TCP/IP 105
Problem reports
UNIX 108
Windows 100
Products
licensing two versions of 82
modifying installation on Windows 77
not licensed to run 105
starting MSC.ADAMS 89
uninstalling MSC.ADAMS on Windows 77
Products CDs, about 11

R
Read-only files, specifying 72
Registry Editor
about 91
Remote machine, using for installation 34
install.book Page 141 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Index 141

Reports, generating on UNIX 108


Reports, generating problem on Windows 100
Requirements for installation 8
Restarting the license daemons 59
Road maps
about 117
for all same machines 119
for heterogeneous network 129
when all different machines 123
when licence server and client the same 125
when multiple file servers, single license server 127
when only client different 120
when only license server different 121
Running
products, not licensed to 105
two versions of MSC.ADAMS 82

S
Selecting license server, tips for 52
Service, license server doesn’t start as 103
Setting
license server 83
preferences 91
working directory 92
Setting up MSC_LICENSE_FILE 104
Silent-mode installation 74
Software, verifying 108
Starting
installation program 35
license server 58
MSC.ADAMS products 89
System requirements 8, 26
install.book Page 142 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


142 Index

T
TCP/IP installation problems 105
Technical Support, contacting 19
Temporary files, require more disk space 115
Three-server configuration
UNIX 53
Windows 80
Tips for selecting license server 52
Token-based licensing 10
Traditional license 10
Troubleshooting 99–115
Typographical errors in license.dat 101

U
Uninstalling MSC.ADAMS on Windows 77
UNIX
installing on 33
licensing on 51
mount commands 97
setting preferences on 91
starting products on 90
troubleshooting on 108
Updating passwords 95

V
Verifying
software 108
successful installation 62
install.book Page 143 Friday, August 5, 2005 11:37 AM

MSC.ADAMS Installation and Operations Guide


Index 143

W
Window driver, selecting for ADAMS/View 39
Windows
installing on 63
licensing on 79
setting preferences on 91
starting products on 90
troubleshooting on 100
Working directory, setting 92

X
X11 window driver, selecting 39