msc.mvision builder and evaluator 2006 - msc software corporation

MSC.Mvision Builder and Evaluator 2006

Installation Guide

CorporateMSC.Software Corporation2 MacArthur PlaceSanta Ana, CA 92707 USATelephone: (800) 328-4672Fax: (714) 784-4056

EuropeMSC.Software GmbHAm Moosfeld 1381829 Munich, GermanyTelephone: +(49) (89) 431 987 0Fax: +(49) (89) 436 17 16

Asia Pacific

MSC Software Japan Ltd., Asia-Pacific OperationsShinjuku First West 8F23-7 Nishi Shinjuku1-Chome, Shinjuku-KuTokyo, JAPAN 107-0052Main Phone: (81) 3 6911-1200Fax: (81) 3 6911-1201

Worldwide Webwww.mscsoftware.com

Disclaimer

MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document without prior notice.

The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation assumes no liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information contained herein.

User Documentation: Copyright 2006 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved.

This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this document, in whole or in part, without the prior written consent of MSC.Software Corporation is prohibited.

MSC is a registered trademark and service mark of MSC.Software Corporation. Mvision and Patran are registered trademarks of MSC.Software Corporation.

MSC.Enterprise Mvision, MSC.Mvision, MSC.Mvision Builder, MSC.Mvision Evaluator, MSC.Mvision Pro, MSC.Patran and MSC. are trademarks of MSC.Software Corporation.

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

We acknowledge the use of MKS Toolkit® (NuTCRACKER® Workstation and NuTCRACKER® Server), copyright 1995 - 2006, MKS Software Inc. All rights reserved.

MV*V2006*Z*Z*Z*DC-OPS

http://www.mscsoftware.com

C O N T E N T SMSC.Mvision Builder and Evaluator 2006 Installation Guide

1Introduction � Overview, 8

� Organization of the Installation Guide, 8

� Using This Document, 9

� MSC.Mvision Terminology, 10

� MSC.Mvision Materials Information System Products, 11❑ MSC.Mvision Software, 11❑ MSC.Mvision Databanks, 11❑ Overview of MSC.Mvision Product Lines, 13

� Deliverables, 14

� Related Documentation, 14

� Technical Support, 14

2Installation Preparation

� Overview, 18

� Preparing for Installation, 18

� Checking Your Software and Hardware Configuration, 18❑ Hardware Requirements, 18❑ Memory Requirements, 19

� Supported Operating Systems, 19

� Size of the MSC.Mvision Installation, 20

� Correcting Font Errors on Silicon Graphics Workstations, 20

� Updating the MSC.Mvision Installation, 20

� Directories and Files Created During Installation, 21

� Preview of the Installation Procedure, 22

� Required Hardware & Software Configurations, 23❑ mscinfo Utility (UNIX/Linux only), 23

❑ RAM, Swap, and Disk Space, 23

� Additional Hardware & Software Configurations, 25❑ HP-UX Kernel Settings, 25❑ Increasing HP Performance, 25❑ Linux, 26

3Installing MSC.Mvision Builder and Evaluator

� Overview, 28

� Installation Process Outline, 28

� Installing MSC.Mvision Builder Evaluator on Windows, 29❑ For operation of MSC.Mvision Builder Evaluator on Windows/XP the

MKS NuTCRACKER for Windows Operations software is required and consists of one copy of MKS NuTCRACKER Workstation and one copy of MKS Local X Server. This MKS software is included on the MSC.Mvision Builder Evaluator CD and is activated by authorization codes provided by MSC.Software. The license for this component software must be obtained prior to installation. The required MKS component software is automatically installed as part of the MSC.Mvision Builder Evaluator installation and no special actions are required., 29

❑ MSC.Mvision Builder Evaluator Setup Instructions, 29❑ MSC.Mvision Builder Evaluator Install Instructions, 29

� Installing MSC.Mvision Builder Evaluator on UNIX/LINUX, 30

� Installing MSC.Mvision with mscsetup, 31❑ Step 1: Mounting the CD-ROM, 32❑ Step 2: Starting the mscsetup Installation Utility, 33❑ Step 3: Selecting an Installation Device, 34❑ Step 4: Selecting the Installation Directory, 34❑ Step 5: Selecting Products to Install, 35❑ Step 6: Selecting a Product Installation Type, 37❑ Step 7: Setting Application Prerequisites, 40❑ Step 8: License File Setup, 40❑ Step 9: Authorization Request Form, 41❑ Step 11: Installation Messages, 42❑ Step 12: Setting User Environment, 45❑ Step 13: Installing MSC.Mvision Databanks, 45❑ Step 14: Verifying the Installation, 45

� Updating a Previous Release, 47

� Customizing the Installation, 49

� Application Resource File, 49

❑ Changing Resources for All Users, 49❑ Changing Resources for Individual Use, 50❑ How the System finds the Application Resources Settings, 50❑ Window Manager Settings, 51

4Installing FLEXlm � Overview, 54

� Obtaining an MSC.Mvision License File, 54

� Installing a Server, 54❑ Place the License File on the Server, 54❑ Check Paths and Server Names in the license.dat File, 55❑ Start the Manager Deamons, 55❑ Setting the lmgrd Daemon to Execute on Reboot, 56❑ Setting up Clients to Access the Floating License, 56

� Installing a Nodelock File, 56

� Updating Codes on an Existing Unix Server, 57❑ Editing the New License File, 57❑ Replacing the Existing License File, 57❑ Forcing Daemon to Read the New License File, 57

� Additional Documentation, 58

5Setting the User Environment

� Overview, 60

� Starting MSC.Mvision Builder and Evaluator Windows/XP, 60

� Starting MSC.Mvision Builder and Evaluator (Unix/Linux), 60❑ Modifying the User Path, 60❑ Creating an Alias, 61❑ Creating a Script, 62❑ Creating a Link, 63❑ Setting DISPLAY Variable, 63❑ Command Line Options, 64

� Setting Print and Preview Options, 64❑ Setup and Operation HTML Print/Preview, 65❑ Setup and Operation PDF Print/Preview, 65❑ Setup and Operation MIF Print/Preview, 66❑ Trouble Shooting Print/Preview, 67

� Setting the Default Printer, 67❑ Printing from the Materials Browser or Data Viewer, 68

❑ Printing from the Spreadsheet, 69❑ Printing from the Full-Text Browser, 69

� Environment Variables, 70❑ Licensing Environment Variable, 70

� Required Environment Variable for DPI, 74

� Customizing Start-up and Shut-down, 74

� Trouble Shooting, 75❑ Multiple platform usage, 76❑ MSC.Mvision Databank access on Windows/XP, 76

MSC.Mvision Builder and Evaluator 2002 Installation Guide

1 Introduction

� Overview

� Organization of the Installation Guide

� Using This Document

� MSC.Mvision Terminology

� MSC.Mvision Materials Information System Products

� Deliverables

� Related Documentation

� Technical Support

8

OverviewThis Installation Guide contains all the information you will need to install and maintain MSC.Mvision Builder and Evaluator software. System specific information is included for you to take full advantage of MSC.Mvision Builder and Evaluator capabilities and features on your system.

Organization of the Installation GuideThis Guide consists of the following chapters and appendices:

Introduction (Chapter 1) describes the contents of each chapter, plus information on documentation conventions, related documentation, MSC.Mvision Materials Information system products available on your computer system, deliverables, and terminology.

Installation Preparation (Chapter 2) outlines the procedures for installing and verifying MSC.Mvision Builder and Evaluator software products on your computer system. We recommend that you read this chapter thoroughly to understand these procedures prior to installation.

Installing MSC.Mvision Builder and Evaluator (Chapter 3) contains complete step-by-step instructions for installing MSC.Mvision Builder and Evaluator software on any supported platforms. These instructions are intended for first-time installations and for existing customers who are upgrading their current production environment.

Installing FLEXlm (Chapter 4) contains detailed information concerning the function and operation of the Network Licensing software. This includes the purpose and function of each FLEXlm parameter and the parameter settings.

Setting the User Environment (Chapter 5) explains the environment variables and file management procedures required to run MSC.Mvision Builder and Evaluator on supported platforms.

9CHAPTER 1Introduction

Using This DocumentThis Installation Guide contains many examples and references to computer commands and output. These items are printed in a fixed pitch font called Courier New. (This sentence is in Courier New.)

In order to clarify the discussions of various topics, the following conventions have been employed throughout this Installation Guide.

menu options Menu names and options are shown in bold sans serif print but in mixed case (uppercase & lowercase) print.

<install-directory> User-defined directories or user-defined files are enclosed in chevrons <install-directory> and are shown in italics. If they are part of an input command, they are shown in courier <italics>.

user input Input required from the user is shown in 10 pt. courier font.

Example:

Enter the command: mveval at the UNIX prompt.

return key The return key is not shown in all examples, but is presented <cr> in some instances. Assume that the user must press return after typing in a command or other input to the system unless instructed otherwise.

10

MSC.Mvision TerminologyThe following list contains MSC.Mvision and computer terms frequently used in this Installation Guide.

databank

Collection of materials information in the MSC.Mvision database format. MSC.Software sells several databanks, or you can use MSC.Mvision Builder to construct your own databanks.

database

A generic term referring to a collection of data in an electronic format. The databanks used by MSC.Mvision Builder and Evaluator are databases created for use by all MSC.Mvision software products.

Motif window An interactive window composed of widgets configured in the X Window system environment.

Software Authorization Information Sheet

List of the authorization codes that enable you to run your licensed MSC.Mvision products. These codes are used in a procedure outlined in Installing MSC.Mvision Builder and Evaluator (Chapter 3).

Customer Information Sheet

List of your licensed products from MSC.Software Corporation.


MSC.Mvision Materials Information System Products The MSC.Mvision Materials Information System includes the following software and databank products:

MSC.Mvision Software• MSC.Mvision Builder - Easy-to-use software tool enabling users to create a

customized materials information system.

• MSC.Mvision Evaluator - Easy-to-use standalone software to access and work with MSC-supplied or user-created materials databanks.

• MSC.Patran Materials - Direct access to MSC.Mvision materials databanks for the MSC.Patran analysis system.

• MSC.Mvision Pro - Direct access to MSC.Mvision materials databanks for the Pro/ENGINEER CAD system.

• MSC.Enterprise Mvision - Direct access to MSC.Mvision materials databanks using standard web browsers.

MSC.Mvision Databanks• Standards Databanks:

MIL-HDBK-5 Databank (Metals)

MIL-HDBK-17A Databank (Aerospace Composites)

MIL-HDBK-17-2F Databank (Polymer Matrix Composites)

MIL-HDBK-17-4F Databank (Metal Matrix Composites)

MIL-HDBK-17-5F Databank (Ceramic Matrix Composites)

PMC-90 Databank (Advanced Composites)

Metal Matrix Composites (MIL-HDBK-17-4)

ESDU Metallic Materials Data

• FEA Databanks

JAHM MPDB Temperature Dependent Properties Databank

Analysis Databank

• Materials Selector Databank

• Producers Databanks:

IDES Plastics Prospector

12

• Reference Databanks:

Penton’s Materials Selector

PDL Chemical Compatibility of Plastics

PDL Effect of Temperature on Plastics

PDL Effect of Creep on Plastics

ASM Alloy Steel Databank

ASM Aluminum Databank

ASM Composites Databank

ASM Copper Databank

ASM Corrosion Databank

ASM Magnesium Databank

ASM Nylons Databank

ASM Stainless Steels Databank

ASM Structural Steels Databank

ASM Thermoplastics Databank

ASM Thermoset Plastics Databank

ASM Titanium Databank

• Cross Reference Databanks:

ASM Alloy Finder

ASM Woldman’s Engineering Alloys

ASM Worldwide Guide to Equivalent Irons & Steels

ASM Worldwide Guide to Nonferrous Metals & Alloys

• GE Plastics Databank

• Special Purpose Databank:

Fatigue

Fibers

Thermal

Electromagnetic Materials

Dytran

• Demo Tutorial Databanks:

Demo_Composites

Demo_Metals


Overview of MSC.Mvision Product Lines

MSC.Mvision Builder™

MaterialsAuthority

• Materials Test• Corp. Knowledge• Design Allowables

• Producers• Standards• Reference• CrossReference

Databanks

MSC-Supplied Databanks

Customer-DefinedDatabanks

(Materials Libraries)

MSC.PatranMaterials™

MSC.MvisionEvaluator™

Analysis

Design andManufacturing

ProgrammaticAccess

MSC.MvisionDPI™

ProgrammaticAccess

MSC.Mvision

DPI™

Worldwide Usersvia Internet

MSC.Enterprise Mvision™

CAD Design

MSC.Mvision Pro™

14

DeliverablesThe MSC.Mvision delivery package consists of the following items:

1. MSC.Mvision CD-ROM

2. MSC.Mvision Cover Letter

3. MSC.Mvision Release Notes

4. MSC.Mvision User’s Guide and Reference

5. MSC.Mvision Installation Guide

6. MSC.Mvision Building Databanks

7. MSC Software Authorization Key Request Form

Related DocumentationThe following documents are included with the MSC.Mvision software:

MSC.Mvision Database Programmatic Interface Manual

Technical SupportIt is our goal at MSC.Software to provide the highest quality software, documentation, and product support as possible. MSC.Software Corporation has established a number of technical support centers around the world to meet this goal.

Please call the technical support center nearest you if you have any questions or difficulties concerning our products. We are ready to help you.

You may get help on MSC.Mvision products by contacting Support Services using any of the options in the table on the next page. To aid us in giving you a quick and correct answer to your questions, please supply us with the following information:

Customer Information

Name: Telephone Number:Fax Number:E-mail Address: Company Name & Address:

Product & Platform Information

Computer Type & Operating System:Product Name & Version:Detailed Description of the Question/Problem:


For help with installing or using an MSC.Software product, contact your local technical support services. Our technical support provides the following services:

• Resolution of installation problems

• Advice on specific analysis capabilities

• Advice on modeling techniques

• Resolution of specific analysis problems (e.g., fatal messages)

• Verification of code error.

We suggest that you contact us in the early stages of your analysis with any concerns you may have about your particular analysis problems.

Technical support is available to you on the web, by telephone, or e-mail:

Web Go to the MSC.Software web site at www.mscsoftware.com, and click on Support. A wide variety of support resources are available at the MSC.Software Training, Technical Support, and Documentation web page including: application examples, technical application notes, training courses, and documentation updates.

Phone and Fax

Email Send a detailed description of the problem to [email protected].

United StatesTelephone: (800) 328-4672Fax: (714) 784-4056

Frimley, CamberleySurrey, United KingdomTelephone: +(44) (1276) 60 19 00Fax: +(44) (1276) 60 19 09

Munich, GermanyTelephone: +(49) (89) 431 987 0Fax: +(49) (89) 436 17 16

Tokyo, JapanTelephone: (81) (3) 6911 1200Fax: (81) (3) 6911 1201

Rome, ItalyTelephone: +(39) (06) 52 79 931Fax: +(39) (06) 52 27 32 32

Paris, FranceTelephone: (33) (1) 69 36 69 36Fax: (33) (1) 69 36 45 17

Moscow, RussiaTelephone: +(7) (095) 363 06 83Fax: +(7) (095) 787 76 06

Gouda, The NetherlandsTelephone: +(31) (182) 536 444Fax: +(31) (182) 538 418

Madrid, SpainTelephone: +(34) (91) 5560 919Fax: +(34) (91) 5567 280

http://www.mscsoftware.com


2 Installation Preparation

n Overview

n Preparing for Installation

n Checking Your Software and Hardware Configuration

n Supported Operating Systems

n Correcting Font Errors on Silicon Graphics Workstations

n Updating the MSC. Enterprise Mvision Installation

n Directories and Files Created During Installation

n Preview of the Installation Procedure

n Required Hardware & Software Configurations

n Additional Hardware & Software Configurations

18

OverviewThis chapter outlines the procedures you should follow prior to installing MSC.Mvision Builder and Evaluator on your computer system. Please read this chapter thoroughly before starting the installation.

Chapter 3 describes in detail the installation for all computer platforms supported by MSC.Mvision Builder and Evaluator.

Preparing for InstallationBefore you begin the installation, please note the following items:

• Verify the system requirements for your computer platform.

• Prior to starting the installation, make sure that you obtain the necessary license codes required to run MSC.Mvision Builder and Evaluator. Feel free to ask your local sales representative for assistance on this important step of the installation.

• Your installation package comes with a CD-ROM containing all required files.

• The installation procedure should be performed when no one else is using MSC.Mvision Builder and Evaluator in order to avoid unpredictable results.

• The entire installation procedure generally takes less than an hour.

Checking Your Software and Hardware ConfigurationThis section helps you verify that your hardware and software meet the minimum requirements for installation of the MSC.Mvision Builder and Evaluator software.

There are additional configuration suggestions included at the end of this chapter that can help you improve the performance of MSC.Mvision Builder and Evaluator on your system. We recommend that you make these modifications for optimum performance.

Hardware RequirementsMSC.Mvision Builder and Evaluator has been developed to work on UNIX/LINUX workstations and PC's with Microsoft Windows/XP operating Systems. See Supported Operating Systems. page 19 for specific OS requirements. There are no special graphics hardware requirements. because MSC.Mvision uses standard X Window system graphics in 8-bit pseudo-color mode. A full-color graphics system is not required.

19CHAPTER 2Installation Preparation

Memory RequirementsMSC.Mvision Builder and Evaluator performance is affected by the availability of main memory and system swap space. You should have a minimum of 64 megabytes of real memory, although we recommend 128 megabytes or more to minimize swapping when running MSC.Mvision Builder and Evaluator with large databanks or large spreadsheets.

Supported Operating SystemsMSC.Mvision Builder and Evaluator runs on the following workstations and operating systems. Refer to the section, Required Hardware & Software Configurations on page 23 for more information.

HP, IBM and SUN workstations have no special requirements. LINUX and Microsoft Windows/XP do not support FrameViewer, and only html and PDF printing is available.

Vendor Operating System Unix Command and Result

Redhat Linux RedHat 9.0 cat /etc/redhat-release

Red Hat Linux release 9.0

HP HP-UX 11.0, 11i uname -srv

HP-UX B.11.00 A

HP-UX B.11.11 A

IBM AIX 4.3.2, 5.2 oslevel

4.3.3.0

5.2

SGI*

* SGI requires specific software to be installed as described in the section, Correcting Font Errors on Sili-con Graphics Workstations on page 20.

IRIX 6.5 uname -sr

IRIX 6.5

SUN Solaris 2.6

Solaris 7,8,9

uname -sr

SunOS 5.6

SunOS 5.7

SunOS 5.8

SunOS 5.9

Microsoft Windows 2000, XP N/A

20

Size of the MSC.Mvision InstallationMSC.Mvision Builder and Evaluator require about 130 megabytes of disk space when fully installed (excluding FLEXlm). If you have installed all the MSC.Mvision databanks, the space required is at least 400 megabytes. The exact size of the installation is listed when you run the mscsetup utility.

The following table lists the approximate size required for each workstation and the command you use to determine your available disk space:

Correcting Font Errors on Silicon Graphics WorkstationsSince MSC.Mvision Builder and Evaluator may use fonts that are not installed on your SGI workstation, you may get font errors after its installation. We recommend that you install these fonts to avoid additional font errors. They are included on the x_eoe.sw.Xoptfonts software product found on the IRIX software CD-ROM.

If you do not install these fonts, you must make changes to the MSC.Mvision Builder and Evaluator application resource files to avoid additional font errors.

Updating the MSC.Mvision InstallationThe installation script, mscsetup, is used by all MSC.Software Corporation software and places all MSC.Software products in a common directory with individual products stored in subdirectories. These subdirectories are labeled with the software name and version. Release 2006 of MSC.Mvision Builder and Evaluator is placed in the sub-directory named mvision2006. Auxiliary software such as Acrobat are placed in their own sub-directories.

Vendor Size in megabytes *

*This size excludes the FLEXlm delivery, which is approximately 2Mb.

Unix Command

LINUX 133 df -k .

HP 139 bdf .

IBM 123 df .

SGI 120 df -k .

SUN 130 df -k .

Microsoft 400 Use folder properties to determine disk space available


This allows you to put several versions of MSC.Mvision in the same directory and switch versions by referring to the sub-directory which contains the version you want by its name. You can also load a new version of the software and test it without affecting users who are using an older version.

This installation scheme does not match the scheme for releases prior to v3.2.

Note: MSC.Software Corp. no longer distributes FrameViewer. However, MSC.Mvision Builder and Evaluator still uses FrameViewer, in addition to Adobe Acrobat, as an option for print preview and print. If you currently have a installation of FrameViewer, it is recommended that you leave it intact. You must set your environment variable FMHOME to the location of this installation to use it with MSC.Mvision Builder and Evaluator 2006.

Directories and Files Created During InstallationThe exact number and names of the files installed on your system depends on the version numbers of the products that are currently compatible with your system. For all installations, the following directories and files will be created:

Directory or File Description

mvision2006/bin/ Directory where MSC.Mvision Builder and Evaluator executable is located.

mvision2006/resources/ Directory where various resource files are located including the on-line documentation and application resource file.

mvision2006/lib/ Directory where object libraries files are located for use with Export and spreadsheet external functions.

mvision2006/dpi/ Directory of examples of DPI program files.

mvision2006/ExFunc/ External Function directory.

mvision2006/export_functions/ Export Function directory.

mvision2006/include/ Location of include files used to create export and spreadsheet functions.

mvision2006/shareware/ Location of the shareware utility scripts and source files.

flexlm/ Location of the FLEXlm licensing software.

acroread405 Adobe Acrobat directory. Used as an MSC.Mvision Helper application.

22

Preview of the Installation ProcedureThe MSC.Mvision Builder and Evaluator installation procedure is designed to give you control of the entire process. The installation is accomplished in the following steps:

1. Mount the CD-ROM on your machine’s CD-ROM drive.

2. Extract the required software from the CD-ROM using mscsetup.

3. Install MSC.Mvision Databanks from the latest Databank CD-ROM. Instructions for installing the databanks is contained in the MSC.Mvision Databank User’s Guide and Reference Manual. If databanks are already installed, you will need to run the mvinstall_db script, which can be found in the installation directory, to link the existing databanks to your new MSC.Mvision Builder and Evaluator installation. As an alternative to running the mvinstall_db script, you can create a link to an existing databank installation directory. This link must be named <mvision_install>/db. Also if Adobe Acrobat reader is alreay installed on your system you can choose not to install the software provided on the CD-ROM and create a link to the existing acroread directory. This link must be named <mvision_install>/acroread.

4. Customize your installation to meet your individual requirements.

bin/ Primary bin directory for the installation. If MSC.Mvision is installed with other MSC.Software products then those products will have executables or links to executables in that directory. There are several FLEXlm executables located in the bin directory.

mscsetup.pbkmscsetup.log

Playback and log file from the mscsetup install script.

mscauth.txt This contract amendment, signed by an authorized person, can be faxed or mailed to MSC.Software Corporation Corporation to update your software license agreement with your current license server information (Computer ID).

Gunzip/ Utility directory used by the mscsetup script to decompress the files on the CD-ROM.

tetex LaTex directory. This directory stores files used to generate PDF printing.

texmf LaTex format directory. This directory stores files used to generate PDF printing.

Directory or File Description


Required Hardware & Software Configurations

mscinfo Utility (UNIX/Linux only)MSC.Mvision Builder and Evaluator 2006 provides a utility that obtains most of the system requirements information used in this chapter. The mscsetup utility automatically executes this utility. If required, you can run the mscinfo utility from a MSC.Mvision installation using:

<install_dir>/mvision2006/bin/mscinfo

RAM, Swap, and Disk SpaceMSC.Mvision Builder and Evaluator hardware requirements vary according to databank size and the functions you execute. Be aware that solvers or other software that run concurrently with MSC.Mvision increase RAM, swap, and disk space requirements.

Total memory is the sum of swap space and RAM. A given process requires a minimum amount of total memory. If the minimum memory to execute a process is higher than the total memory available, MSC.Mvision Builder and Evaluator will generate memory allocation (memalloc) errors. Some operating systems will terminate with a segmentation fault.

Since RAM is very fast in comparison to the disk-based swap, more RAM generally translates into better performance. A general rule is to provide 25% to 30% of total memory as RAM. Consult your operating system documentation for additional information.

Note: You must have root access to obtain complete graphics and virtual memory information under Hewlett Packard HP-UX. However, if you use normal access, you can access all information required for this installation procedure.

mscinfo option Use

mscinfo -x Displays information pertaining to the Xserver. You must run from a window being displayed on the machine in question.

mscinfo -v Verbose mode - applicable only under IBM AIX.

mscinfo -commands Displays a list of the commands used to determine system information.

24

The following table lists the minimum disk space, swap and RAM guidelines necessary to run MSC.Mvision Builder and Evaluator.

The mscsetup utility indicates required disk space for each product set.

Note: The installation process requires some small additional space for file decompression. At most, decompression requires about 50MB beyond product disk requirements, but 10MB of additional space is typical. If insufficient space is available in the installation directory, the mscsetup utility attempts to use /tmp for decompression.

Resource Minimum Standard LargeSpreadsheet

Random Access Memory (RAM) per user

64 Mb 128 Mb 256 Mb

Paging Disk Space (Swap) 200 Mb 300 Mb 300 Mb

Scratch Disk Space (/tmp) 50 Mb 100 Mb 100 Mb


Additional Hardware & Software Configurations

HP-UX Kernel SettingsThe HP-UX Operating System contains a utility named SAM that allows you to tune many different kernel parameters. We recommend the following:

MSC.Mvision requires >64Mb of virtual memory to run. If the default maxdsiz is too low, this causes MSC.Mvision to run out of virtual memory unless both the swap, and the maxdsiz parameter are increased. It is not necessary to change the MSC.Mvision 64Mb maxtsiz parameter.

Increasing HP PerformanceTo increase performance on the HP, you can try the following system configuration:

Setting fs_async and default_disk_ir to 1 enables asynchronous disk writes and disk write caching. This lets MSC.Mvision Builder and Evaluator perform I/O faster, since it does not wait to verify that the write was completed. A drawback to this parameter setting is if your computer crashes when the disk write has not completed. Therefore, backups are recommended for large network cluster applications, such as on-line transaction processing where data integrity is the primary concern.

Maxusers sets the maximum number of users, and allows SAM to tune other parameters that can increase the performance of MSC.Mvision Builder and Evaluator.

Using all three of these parameter settings may have a significant positive effect on the performance of MSC.Mvision Builder and Evaluator, particularly I/O speed.

Parameter Description Default Recommended

maxdsiz Maximum Data Segment Size 64Mb 90% of swap

maxtsiz Maximum Text Segment Size 64Mb 90% of swap

maxssiz Maximum Stack Segment Size 8Mb 67108864 (64 Mb)

Parameter Setting Default

fs_async 1 0

default_disk_ir 1 1 on HP700 class; 0 on HP800 Class

maxusers 100 32

26

LinuxMSC.Mvision Builder and Evaluator 2006 will function with Lestiff, but OpenMotif is preferred and offers improved performance. If OpenMotif 2.1 is not currently installed on your system, you must install the RPM file provided in the MSC.Mvision CD. To install this software, issue the following command from the CDROM directory:

rpm-ivh openmotif-2.1.30-1_ICS.i386.rpm


3 Installing MSC.Mvision Builder and Evaluator

� Overview

� Installation Process Outline

� Installing MSC.Mvision Builder Evaluator on Windows

� Installing MSC.Mvision Builder Evaluator on UNIX/LINUX

� Installing MSC.Mvision with mscsetup

� Updating a Previous Release

� Customizing the Installation

� Application Resource File

28

Overview This chapter details the installation of MSC.Mvision Builder and Evaluator software on supported platforms. It is recommended that you read this chapter thoroughly before proceeding with the installation

Installation Process Outline

MSC.Mvision Builder and Evaluator 2006 uses an installation script common to all MSC.Software products. From this single script, you can unload all the necessary software and prepare it for use. The installation script requires the CD-ROM drive to be mounted on the local machine either directly or via an NFS mount.

Note: The following items are of particular note when beginning the installation process:

• Review the system configuration requirements as outlined in Installation Preparation (Chapter 2), to see if your system meets the minimum requirements for installation of MSC.Mvision Builder and Evaluator. You will have to make necessary changes before you can complete the installation.

• With the exception of FLEXlm licensing software, MSC.Mvision Builder and Evaluator can be installed without using a superuser account or privileges. Using a superuser account for the install will not change any directories other than the ones you create as part of the installation procedure. See Installing FLEXlm (Chapter 4) for details on installing the licensing software.

• The software can be installed anywhere on a machine’s file system, as long as the account you use has write permission to that area.

29CHAPTER 3Installing MSC.Mvision Builder and Evaluator

Installing MSC.Mvision Builder Evaluator on Windows

For operation of MSC.Mvision Builder Evaluator on Windows/XP the MKS NuTCRACKER for Windows Operations software is required and consists of one copy of MKS NuTCRACKER Workstation and one copy of MKS Local X Server. This MKS software is included on the MSC.Mvision Builder Evaluator CD and is activated by authorization codes provided by MSC.Software. The license for this component software must be obtained prior to installation. The required MKS component software is automatically installed as part of the MSC.Mvision Builder Evaluator installation and no special actions are required.

MSC.Mvision Builder Evaluator Setup InstructionsThe setup.exe installation application performs all the steps necessary to get the MSC.Mvision up and running.

To run the setup.exe application:

1. Insert the MSC.Mvision CD-ROM in your CD-ROM drive.

2. Double-click the icon or the drive label that represents your CD-ROM drive.

3. Double-click the setup.exe program icon to initiate the installation. Note that when the CD-Rom is installed into the CD-ROM drive, it will automatically start running if you have the auto-start setting for the CD-ROM turned on. This is the Windows 2000/XP default.

The Welcome Panel appears.

MSC.Mvision Builder Evaluator Install InstructionsTo install MSC.Mvision:

1. From the Welcome Panel, press the Next button.

2. Choose a destination location, and then press the Next button. A default location is shown but you can change it to any valid directory on the system.

3. MSC.Mvision requires an Xserver to be installed. The default is to install the MKS provided Xserver. If you already have Xserver software such as HummingBird Exceed or PCWare installed select "No".

4. Click the Next button.

5. Review the settings and verify that the values are specified correctly.

6. Click the Install button to begin the installation process.

7. Select Reboot to complete the installation.

8. To test the installation, navigate to <mvision_install>/bin folder and execute the mvbuild.bat script.

Note: Setting the User Environment (Chapter 5) for additional operating environment requirements.

30

Installing MSC.Mvision Builder Evaluator on UNIX/LINUXThe following flowchart outlines the steps for installing MSC.Mvision Builder and Evaluator.

Step 4: Selecting the Installation Directory (p. 34)

Step 1: Mounting the CD-ROM (p. 32)

Step 3: Selecting an Installation Device (p. 34)

Step 5: Selecting Products to Install (p. 35)

Step 8: License File Setup (p. 40)

.Step 9: Authorization Request Form (p. 41)

Step 11: Installation Messages (p. 42)

Step 12: Setting User Environment (p. 45)

Step 13: Installing MSC.Mvision Databanks (p. 45).

Step 10: Installation Review (p. 42)

Step 2: Starting the mscsetup Installation Utility (p. 33)

Step 6: Selecting a Product Installation Type (p. 37)

Step 7: Setting Application Prerequisites (p. 40)

Step 14: Verifying the Installation (p. 45)


Installing MSC.Mvision with mscsetupThe mscsetup utility performs almost all of the steps necessary to get MSC.Mvision Builder and Evaluator running. It creates a log file, mscsetup.log, as a record of all messages, prompts, and user input. The mscsetup utility also creates a playback file, mscsetup.pbk.

For a basic interactive installation, MSC.Software recommends executing the mscsetup utility with no flags or options. For advanced installers, mscsetup offers the following additional capabilities:

Command Line Arguments Purpose

mscsetup <playback.pbk> Runs playback file in install-only mode. Useful to repeat identical installations.

mscsetup amendment Generates a contract amendment form.

mscsetup flexlm <license_file> Installs a new FLEXlm license file into the flexlm/licenses directory. Also checks the file for correct checksum, SERVER line, and invalid characters.

mscsetup flexlmcheck <license_file>

Tests FLEXlm licensing. The default is the current MSC_LICENSE_FILE setting. See Installing FLEXlm (Chapter 4) for additional information.

mscsetup help Prints information on command line arguments.

mscsetup id Displays the MSCID System id used to generate licenses. See Installing FLEXlm (Chapter 4) for additional information.

mscsetup mscinfo Executes the mscinfo utility. See the mscinfo Utility (UNIX/Linux only) on page 23 for additional information.

mscsetup -b <installation_dir> Sets the default installation directory.

mscsetup -l <log_file> Writes the installation log to <log_file>. The default is mscsetup.log.

mscsetup -m <media>:<path> Specifies default installation media and path, for example “cd:/CDROM”

mscsetup -n Turns off screen handling for text-only scrolling mode.

mscsetup -p <playback_file> Writes the playback file to <playback_file>. The default is mscsetup.pbk.

mscsetup -r <user@node> Sets the user and node for remote installation.

32

Step 1: Mounting the CD-ROMMounting the CD-ROM can vary according to your operating system setup. The following steps represent default mounting procedures. However, simpler tools are often available as part of user environment packages, such as the Common Desktop Environment (CDE) or SGI’s 4DWM. Consult your operating system documentation for the best method.

1. Create a directory for the CD-ROM (if it does not already exist):

mkdir /CDROM

2. Mount the CD-ROM drive by issuing the command that corresponds to your operating system setup:

3. Remove the CD-ROM, by entering:

cd <other_dir>umount /CDROM

where <other_dir> is any directory, other than /CDROM.

4. Press the Eject button on the CD-ROM drive. On Sun Solaris, enter: eject cdrom

mscsetup -t <tmp_dir> Sets the directory mscsetup will use for scratch space. The default is /tmp.

mscsetup -x Shows menus and prompts with no explanatory text (expert mode). Recommended only for users very familiar with mscsetup.

Linux: If your machine does not automatically mount the CD, enter the following command: mount /dev/cdrom /CDROM

HP: mount -F cdfs /dev/dsk/c0tUd0 /CDROM

where U = the SCSI controller # for the CD-ROM drive

IBM: mount -rv cdrfs /dev/cd0 /CDROM

SGI: mount -rt iso9660 /dev/scsi/scCdUl0 /CDROM

where C = the SCSI controller # and U = CD-ROM unit #. These values can be found by entering the command, /bin/hinv.

Note: The “l” in scCdUl0 is the letter “L” in lowercase, not a “one”.

Sun Solaris: You do not need to enter a mount command, because the MSC.Mvision CD-ROM is automatically mounted by the Solaris vold daemon. The actual mount point is specified in the file, /etc/vold.conf, which by default, is /cdrom/cdrom0. If this directory does not appear after inserting the CD-ROM, make sure the vold daemon is running.

Command Line Arguments Purpose


Step 2: Starting the mscsetup Installation UtilityYou do not need to be superuser (root) to run mscsetup. However, in order to get FLEXlm to restart on reboot, you might need superuser (root) access. The mscsetup utility keeps a log of important information, so it is not necessary to make detailed notes. To execute mscsetup from the CD-ROM, enter:

<cdrom_dir>/mscsetup

The following information and instructions for installation on an HP workstation are displayed on the screen in the following example. Other platforms display similar screens.

Note: The mscsetup program can be terminated at any prompt command by entering the character “x” and <cr>.

Please wait...MSC Installation and Setup - IntroductionNOTE: You might need superuser (root) privileges to use the default installation directory /msc.The following products are available on this delivery:* MVISION 2006Please note that new FLEXlm authorization codes are required to complete the installation of products contained on this media.*TeTex 1.07This will initiate the TeTex application utilized in conjuction with creating pdf files for MSC.Mvision products.* Adobe Acrobat 4.05This will install the Adobe Acroread application utilized in conjunction with MSC products.* FLEXlm V9.2hThis will install the FLEXlm License Server and End-User tools. You should have a file or an e-mail message containing licensing data before installing this product.Do you want to continue (default = Y)? <cr>

34

Step 3: Selecting an Installation DeviceWhen using the mscsetup utility, you must identify the type of media from which you are installing, and the path to that media.

The local CD option assumes that the CD-ROM is available in the same file system as the installation directory. The CD-ROM must be either locally mounted or NFS mounted on the same machine as the installation directory.

The remote CD option allows accessing a CD-ROM on a remote machine using commands such as rsh and rcp.

Step 4: Selecting the Installation DirectoryThe installation directory is the location where you will install all products. If a previous version of MSC.Mvision Builder and Evaluator is installed on this machine, refer to Updating a Previous Release on page 47. For example, if you choose /msc as the installation directory, a typical installation would look as shown below at completion:

ls -l /mscdrwxr-xr-x 2 root sys 1024 Apr 21 16:33 bindrwxr-xr-x 5 root sys 96 Apr 21 16:33 flexlmdrwxr-xr-x 17 root sys 2048 Apr 21 16:03 mvisiondrwxr-xr-x 17 root sys 1024 Apr 21 16:03 acroread405

MSC Installation and Setup - Installation Device Location

1. Install from a local CD. Select this item if the installation CD is attached to this

computer, or NFS mounted on this computer. 2. Install from a remote CD. Select this item if the installation CD is attached to another

computer. X. Completely exit this installation now Select this item to end this procedure now.

Enter 1, 2, or X (default = 1)? <cr>

MSC Installation and Setup - Local Installation Device or File

Enter the pathname of the local CD-ROM mount point.Pathname (default = /CDROM)?

Install from /CDROMIs this correct (default = Y)? <cr>

Please wait...................................


The utility also checks the amount of disk space available for the path.

Enter the pathname of the directory you want to install into,X to completely exit this installation, or? for a list of available filesystems.

Pathname (default = /msc)? <cr>

If the directory /msc does not exist, then:

The directory “/msc” does not exist.

If the directory /msc exists, then:

Directory /msc exists.

When given permission to proceed, the script checks the available space on the disk.

Checking available disk spaceThe size of the filesystem containing this directory is2896 MB, with 1182 MB currently available.

Do you want to use this directory (default = Y)? <cr>

Step 5: Selecting Products to InstallAfter you have entered the appropriate file paths, you will be presented with a menu of all available product sets on the CD-ROM:

Select each product set that you wish to install. You must select products one at a time, since each product set selection is followed by appropriate setup questions.

Note: mscsetup requires additional disk space for decompression of the files contained on the CD-ROM.

MSC Installation and Setup - Installation Base DirectoryMSC strongly recommends installing this software in a “common” MSC productdirectory to allow MSC products to share common software and settings.

This can - Reduce the amount of installation space needed by a product. - Make future installations easier. - Reduce the effort needed to administer MSC products.

MSC recommends the standard directory /msc, but alternate choices,such as /usr/local/msc, are also acceptable.

Enter the number of the product to select or deselect, X to completely exit this installation.

Enter 1-5 or X (no default)? 1 <cr>

36

The selections for an MSC.Mvision Builder and Evaluator installation are:

• MVISION Application - This is the core software for operation of the MSC.Mvision product on an supported platform.

• Adobe Acroread - The MSC.Mvision Helper function uses this product to view documents contained in MSC.Mvision commercial databanks. Install it only if it does not currently exist on your system.

• FLEXlm - See Installing FLEXlm (Chapter 4), for the requirements for, and installation of FLEXlm.

• TeTex (1.07) - This software is required to produce PDF output and must be installed for MSC.Mvision to function correctly.

• MVISION Asian Application - This is the core software for operation of MSC.Mvision Builder and Evaluator on double-byte platforms. This product selection is only available for the Sun Solaris and SGI platforms. This product should only be selected if your system currently supports multi-byte languages, such as Japanese and Chinese. If this product is selected, do not select MVISION Application (item 1).

Selecting a product and then choosing a “Custom” installation in Step 6: Selecting a Product Installation Type on page 37 allows you to see the full contents of each product set.

Note: For most licensed products, there is a “Product” listing in mscsetup that corresponds to each product, module, or databank.

MSC Installation and Setup - Select Product1182 MB available in installation directory.

Product Comments ---------------------------------------- -------------------- 1. MVISION Standard Application . . . . . . Not selected yet. 2. MVISION Asian Application Not selected yet.3. TeTex (1.07) . . . . . . . . . . . . . . Not selected yet.4. Adobe Acroread (4.05) Not selected yet.5. FLEXlm License Server v9.2h . . . . . . Not selected yet.

X. Completely exit this installation now.


Step 6: Selecting a Product Installation TypeMSC.Mvision product sets contain two installation options. The installation types for MSC.Mvision product sets are:

• Standard includes all files necessary to run the product.

All MSC.Mvision product selections contain the standard option only - no custom option is available. Proceed as instructed in the next step after selecting the standard installation.

• Custom permits selection of individual components of the product set. You select individual optional components from menus similar to the product selection menu.

The FLEXlm v9.2h product contains a custom installation option.

Note: To deselect an installation that was previously selected, re-enter its number.

MSC Installation and Setup - Installation Type

1182 MB available in installation directory. 159 MB required by previously selected products.Note: Installation of FLEXlm is NOT required on client systems. A typical network-licensed site will include one FLEXlm license server machine to provide runtime license authorization for several client systems. You should not proceed with installation of FLEXlm unless you intend to use this system as a FLEXlm license server. You must obtain licensing data from MSC.Software in order to complete a FLEXlm installation.

1. Standard Installation. 4 megabytes required. Install executables and documentation for FLEXlm License Server

V9.2h on Silicon Graphics R4X00, R5K systems. 2. Custom Installation. Select specific architectural and optional components to install.

R. Return. X. Completely exit this installation now.

Enter 1, 2, R, or X (default = 1)? 2

38

Selecting a custom installation provides additional options, depending on the installation types selected. The installation options in the current example are:

MSC Installation and Setup - Architectural Components

1182 MB available in installation directory. 159 MB required by previously selected products.No. Architectural Component Mode MB 1. Linux No 2 2. Hewlett-Packard . . . . . . . . . . . . . . . . . No 1 3. IBM RS/6000 Yes 1 4. Silicon Graphics . . . . . . . . . . . . . . . . . Yes 2 5. Sun SPARC Solaris . . . . . . . . . . . . . . . . .No 2

Space Required for Architectural Components 3

C. Continue to the Optional Components Menu.X. Completely exit this installation now.

Enter a list of component numbers to select or deselect (you may usespaces or commas, a dash indicates a range, e.g., “1,3-5”),C. when you are done selecting architectural components, orX to exit this installation.Enter 1-5, C, or X (no default)? C


The FLEXlm product provides an option to view help documents as HTML files. To enable this option, select item 2 in the Optional Components installation screen.

WARNING: The Base files entry is required for the proper functioning of FLEXlm License Server v9.2h. Deleting this entry may cause the system to fail!

Load Base files (default = YES)? <cr>

MSC Installation and Setup - Optional Components

1182 MB available in installation directory. 159 MB required by previously selected products.

No. Optional Component Mode MB 1. Base files . . . . . . . . . . . . . . . . . . . . Req 1 2. HTML Documentation files . . . . . . . . . . . . . Yes 1

Space Required for Optional Components 2

C. Continue with product configuration. X. Completely exit this installation now.

Enter a list of component numbers to select or deselect (you may usespaces or commas, a dash indicates a range, e.g., “1,3-5”),C. when you are done selecting optional components, orX to exit this installation.

Enter 1, 2, C, or X (no default)? C

MSC Installation and Setup - Optional Components

1182 MB available in installation directory. 159 MB required by previously selected products.

No. Optional Component Mode MB 1. Base files. . . . . . . . . . . . . . . . . . . . .Req 1 2. HTML Documentation files . . . . . . . . . . . . . .No 1

Space Required for Optional Components 2

C. Continue with product configuration. X. Completely exit this installation now.

Enter a list of component numbers to select or deselect (you may usespaces or commas, a dash indicates a range, e.g., “1,3-5”),C. when you are done selecting optional components, orX to exit this installation.

Enter 1, 2, C, or X (no default)? 2

40

Step 7: Setting Application PrerequisitesSome products include components that require special set-up. For each of these special components, you are provided additional setup information and prompted for required input.

There are no application prerequisites required for MSC.Mvision Builder and Evaluator 2006.

Step 8: License File SetupMSC.Mvision uses the FLEXlm network licensing system. If you elect to install FLEXlm in Step 5: Selecting Products to Install on page 35, the install procedure prompts you for the information necessary to start the local machine as a license server.

If you do not elect FLEXlm, the install procedure prompts you to provide the location of an existing nodelock file or license file, or to identify another machine as the server. For more information on FLEXlm, see Installing FLEXlm (Chapter 4).

Selection 1 requires a license file (i.e. license.dat) containing nodelock licenses or a reference to another server. The MSC_LICENSE_FILE environment variable will be set to reference this file.

Note: The exact format of the messages and prompts vary according to product selection and your local environment.

MSC Installation and Setup - Licensing Information

1. Specify an existing “license.dat” file. This file may be an e-mail message sent by MSC containing this data.

D. Do not set authorization information now. Select this if licensing information is already configured or will be configured after this installation. X. Completely exit this installation now.

Enter 1, D, or X (default = D)? 1

MSC Installation and Setup - Existing Licensing File

Enter the pathname of an existing file containing FLEXlm License Server licensing data. This file can be an email message; it can also contain data for any number of MSC products.

Enter R to cancel this input and return to the previous menu, orX to completely exit this installation.

Pathname (no default)? <full_path_to_license_file>


Step 9: Authorization Request FormIf you have not already received licenses from MSC.Software, or do not have an existing license server, the install procedure prompts you to generate an “Authorization Request Form”. This step creates a file containing the system information that MSC.Mvision needs to generate FLEXlm license codes.

Note: This step of the installation will attempt to modify the file, <install_dir>/resources/mv_prolog to add the following line:setenv MSC_LICENSE_FILE <XXXXX>.If you have problems obtaining an MSC.Mvision license at run time, check that this variable is set properly and that it is pointed to a valid FLEXlm license server or a license file.

Caution: This portion of the installation can cause problems. It assumes that FLEXlm is already installed or that the license file already exists. If this is the first time you have installed FLEXlm, then select option D. When the installation is complete, go to Installing FLEXlm (Chapter 4), to complete the installation of the licensing information.

MSC Installation and Setup - Product Licensing Requirements

Licensing Licensing Product Methods Installed ------------- ---------------- ---------------- ----------------MVISION Standard Application Network No Adobe Acroread (4.05) None n/aFLEXlm License Server v9.2h license.dat No TeTex (1.07) None No

You can generate a contract amendment that can be completed and mailed or faxed to MSC to request a software license.

Do you want to generate a contract amendment (default = Y)? <cr>The MSC Contract Amendment has been written to

/msc/mscauth.txtPress ENTER or RETURN to continue...

42

Step 10: Installation Review

Prior to actually performing the installation, the mscsetup utility reviews your current selections. You may change the installation source, target install directory, or product selection.

Step 11: Installation MessagesAs the mscsetup utility performs the installation, it issues messages informing you of its progress.

Note: This information is also recorded in the mscsetup.log file.

MSC Installation and Setup - Installation Review

1. Installation Source; Local CD /CDROM

2. Installation Directory: /msc2896 MB total

1182 MB available 3. Product Type Size Test

----------------------- -------- ----------- ----MVISION Application Standard 84 MB n/aFLEXlm v9.2h Custom 5 MB n/aAdobe Acroread (4.05) Standard 11 MB n/aTeTex (1.07) Standard 5 MB n/a

Enter Y to begin the installation now, orN to change the installation options.

Is this OK (no default)? Y


In this example we are installing the MSC.Mvision core product set including the TeTex, Acrobat components and the FLEXlm license management software.

MSC Installation and Setup - Installation

No additional user input will be required.Writing new playback file, /msc/mscsetup.pbk”

Changing working directory to /mscLoading installation files. Tue Dec 20 14:51:18 PDT 2005Using CD-ROM /CDROM Begin loading files from flexlm/aix.tar Verifying CD load operation... Begin loading files from flexlm/base.tar Verifying CD load operation... Begin loading files from flexlm/htmlman.tar Verifying CD load operation... Begin loading files from flexlm/irix.tar Verifying CD load operation... Begin loading files from irix/acroread405.tar Verifying CD load operation... Begin loading files from irix/mvision2006.tar Verifying CD load operation...Begin loading files from tools/gunzip.tar

Verifying CD load operation...Unpacking installation files. Tue Dec 20 14:52:56 PDT 2005Unpack complete.Decompressing installation files. Tue Dec 20 14:52:56 PDT 2005Decompression complete.Configuring Products. Tue Dec 20 14:56:12 PDT 2005 Configuring FLEXlm License Server V9.2h Creating directories, setting modes... Miscellaneous configuration commands... Updating installation base directory...

44

FLEXlm License Server (lmgrd) Notes:

The FLEXlm license server can be manually started with the command/msc/bin/flexlm lmgrd

where the default license and log files are/msc/flexlm/licenses/license.dat/msc/flexlm/lmgrd.log

An alternate license file can be specified with the “-c” option, e.g.,/msc/bin/flexlm lmgrd -c <license_file>

An alternate log file can be specified with the “-l” option, e.g.,/msc/bin/flexlm lmgrd -l <log_file>

DO NOT SHUT DOWN THE FLEXlm LICENSE SERVER USING THE kill(1) COMMAND.

Use the following command to shut down the license server./msc/bin/flexlm lmdown

or/msc/bin/flexlm lmdown -c <license>

It may take a few minutes for the shutdown to complete.

FLEXlm Status Tool (lmstat) Notes:

On the server node, the status tool can be run with the command/msc/bin/flexlm lmstat

On a FLEXlm client node, the status tool can be run with the command/msc/bin/flexlm lmstat -c 1700@<server>

where <server> is the name of the FLEXlm server node.

FLEXlm Documentation Notes:

The HTML documentation can be viewed with any WEB browser, open the URL

file:/msc/flexlm/htmlman/flexframe.html

FLEXlm documentation is also available via the Web at

http://www.globetrotter.com


Step 12: Setting User EnvironmentYou must decide how your installation intends to make MSC.Mvision Builder and Evaluator accessible to your user community. Refer to Setting the User Environment (Chapter 5) for a full discussion of the various options available.

Step 13: Installing MSC.Mvision DatabanksThe MSC.Mvision commercial databanks are delivered on a separate software CD-ROM. Included on the MSC.Mvision Materials Databank CD-ROM is the script used for installation of all databanks on your system for use by MSC.Mvision Builder and Evaluator. Installation procedures are found in MSC.Mvision Materials Databanks Installation Guide.

The MSC.Mvision Materials Databank CD-ROM provides many special interest and tutorial databanks free of charge to MSC.Mvision users, in addition to a wide selection of databanks created from the data supplied by renowned institutions. The content of the commercial databanks is documented in the MSC.Mvision Materials Databanks Data Sheet, included with the CD-ROM. Licenses to access these databanks can be purchased from MSC.Software. If you have an existing MSC.Mvision Databanks directory, you can link these databanks to the MSC.Mvision db directory. To do this, navigate to <install_dir>/mvision2006/ and execute the following command:

ln -s <fullpath_to_existing_databanks_directory> db

Step 14: Verifying the Installation All installation steps have been completed and the software is now ready to use.

Configuring TeTex(1.07)Configuring Adobe Acroread (4.05)

Configuring MVISION Standard Application Miscellaneous configuration commands...Configuration complete. Tue Dec 20 14:56:36 PDT 2005

REMINDER

An “MSC Contract Amendment” was written to/msc/mscauth.txt

Please edit the file and forward it to MSC as described in the file.

Installation complete. Tue Dec 20 14:56:36 PDT 2005

The above notes were also written to the log file.

A log of this installation was written to: /msc/mscsetup.log

46

To verify the installation type:

mvevalor,

mvbuild

You should see a display that starts with a panel announcing the product, MSC.Mvision Evaluator or Builder. That panel is followed by a large window titled Materials Browser.

To quit, pick the Exit MVISION option from the File menu.

If the mveval or mvbuild command does not produce the windows described above, check the user configuration outlined in Setting the User Environment (Chapter 5).

To verify the installation independent from the user environment, type the following on the command line:

<install_dir>/mvision2006/bin/mveval

<install_dir>/mvision2006/bin/mvbuild

This will bypass the user environment and verify that the software is properly installed.


Updating a Previous ReleaseInstalling MSC.Mvision Builder and Evaluator 2006 on a machine that has an older version already installed requires some additional procedures. We recommend that you install MSC.Mvision Builder and Evaluator 2006 in a directory separate from the older releases. This is important because the location of the installed software for MSC.Mvision Builder and Evaluator 2006 is different from previous releases. Installing MSC.Mvision Builder and Evaluator 2006 in the same directory as versions 3.4 or 2004 will damage both releases and neither will work properly.

You have several options if you are installing MSC.Mvision Builder and Evaluator 2006 on a machine which has a previous release of MSC.Mvision Builder and Evaluator. The main concern is making the transition for the users as simple as possible.

• Install MSC.Mvision Builder and Evaluator 2006 and leave the previous installation untouched.

The users will have to change their start-up procedure to address the new directory when they want to execute MSC.Mvision Builder and Evaluator 2006 or they can leave their start-up procedure alone to execute the older version.

• Install MSC.Mvision Builder and Evaluator 2006 and move the contents of the previous release into its own sub-directory in the MSC.Mvision Builder and Evaluator 2006 install directory.

If the previous release is 2004, then you would move the files in <install_dir> for 2004 into a new directory named <new_install_dir>/mvision2004.

All users in this case will have to change to the new installation directory and chose between mvision2006/bin and mvision2004/bin.

• You can simplify transition from one release to the other for all the user’s at your facility using a link.

After you move the contents of the old release to the new directory, create a link that points from the old location to the new location in <new_install_dir>/mvision2004. When you are ready to switch all the users to MSC.Mvision Builder and Evaluator 2006, change the link to point to <new_install_dir>/mvision2006.

Note: Do not install MSC.Mvision Builder and Evaluator 2006 in the same directory as a previous release of MSC.Mvision Builder and Evaluator. If you do, you will damage both releases.

48

The following figure illustrates the use of this link. In this example, the old version of MSC.Mvision is 2004 which is installed in the directory /appl/mvision. Release MSC.Mvision 2006 is installed in /appl/msc. The user has /appl/mvision/bin in his PATH environment variable.

Before MSC.Mvision Builder and Evaluator 2006 is installed

/appl/mvision/bin/...

After MSC.Mvision Builder and Evaluator 2006 is installed. Before switch to MSC.Mvision Builder and Evaluator 2006

/appl/mvision -> /appl/msc/mvision2004

/appl/msc/mvision2006/bin/...


After MSC.Mvision Builder and Evaluator 2006 is installed. After switch to MSC.Mvision Builder and Evaluator 2006

/appl/mvision -> /appl/msc/mvision2006




Customizing the InstallationThere are some customization options you may want to consider at this time. Customizing MSC.Mvision Builder and Evaluator for your installation is possible via various resource files that are delivered with the product. The following sections cover the most common customization tasks.

Application Resource FileWhen MSC.Mvision Builder and Evaluator start, they search for resource settings (fonts, colors, window positions, etc.) in the standard X Window System application resource files. MSC.Mvision Builder and Evaluator use application resource files named Mveval and Mvbuild.

The application resource file is a special text file containing various resource settings used when running MSC.Mvision Builder and Evaluator. These resource settings control a wide variety of program features. Examine these resource settings to determine which, if any, you want to change. Each user can have his own version of the application resource file to tailor the program to his individual needs.

Note: MSC.Mvision Builder and Evaluator automatically use the application resource file contained in the MSC.Mvision installation. You do not need to copy the resource files to the system application defaults directory, nor does a user need to copy the whole file to change one resource. A user’s application resource file is only required to contain those resource settings he needs to change.

The X Windows System looks for resource files in several places, which allows you to customize the installation for your site. Edit Mveval in your installation resources directory to change MSC.Mvision Evaluator settings for all users at your site. Individual users can put a copy of the file in their home directory and make changes which will affect only their use of MSC.Mvision Evaluator. See the section, How the System finds the Application Resources Settings on page 50.

Changing Resources for All UsersTo change resources for all users at your site, change the files located in:

<install_dir>/mvision2006/resources/

The MSC.Mvision startup will look in this directory for the resource files Mveval and Mvbuild.

After editing resources in these files, you must restart MSC.Mvision. MSC.Mvision checks these files only at startup, so your changes will not take effect until you restart.

Note: Note: Special mv_prolog and mv_epilog scripts located in the resources directory can be usedto set the environment variables mentioned in the following sections. Refer to Customizing Start-up and Shut-down on page 74 for further information.

50

Changing Resources for Individual UseEach user may have their own copy of the application resource file. When you start a MSC.Mvision product, your personal resources override all others.

You can store MSC.Mvision Evaluator resources in a file name Mveval in your home directory. A personal application resource file does not need to set all the possible resources but only those that will be different from the system application resource file. You can copy a complete version of the MSC.Mvision Builder and Evaluator application resource file located at:

<install_dir>/mvision2006/resources/Mveval<install_dir>/mvision2006/resources/Mvbuild

If MSC.Mvision Builder and Evaluator are to be accessed primarily via X-emulators, you may want to consider using the resources files provided in <install_dir>/shareware, which produce smaller window and font sizes.

How the System finds the Application Resources SettingsMSC.Mvision Builder and Evaluator search for application resources in the following manner to build a resource database. Resources found in files searched first take precedence over those found in later files.

1. Command line options you entered on the command used to start MSC.Mvision Evaluator or Builder.

2. The following files are searched in order:

$ENVIRONMENT~/.Xdefaults-hostname

Note: $ENVIRONMENT must be a complete path.

3. A server database that you loaded or the default database is searched (for example, ~/.Xdefaults).

4. For an Mveval or Mvbuild file in the following paths:

$XUSERFILESEARCHPATH$XAPPLRESDIR$HOME

5. For an Mveval or Mvbuild file in the following paths:

$XFILESREACHPATH/usr/lib/X11/app-defaults

OR, if you are using OpenWindows:

$OPENWINHOME/lib/app-defaults

Note: The MSC.Mvision wrapper script adds to the XFILESEARCH environment variable the location of the <install_dir>/mvision2006/resources directory. This is how the resources in that directory can be used to control all of the individuals at a particular installation.


All resource settings found are used to determine the proper setup. If a resource setting is found

more than once, the first value found is used. For more information, see your X Window System documentation.

Window Manager SettingsIn general you should not need to set any window manager resources to run MSC.Mvision Builder and Evaluator. However if a user has turned off the client borders and menus, they may want to turn them back on for MSC.Mvision Builder and Evaluator and FrameViewer clients as follows:

*mveval.clientDecoration: all*mveval.transientDecoration: all*mvbuild.clientDecoration: all*mvbuild.transientDecoration: all*maker.clientDecoration: all*maker.transientDecoration: all

Put these settings in the window manager resource file or in the .Xdefaults file. This will activate the resize borders and window manager menus for all windows in your MSC.Mvision session.


4 Installing FLEXlm

� Overview

� Obtaining an MSC.Mvision License File

� Installing a Server

� Installing a Nodelock File

� Updating Codes on an Existing Unix Server

� Additional Documentation

54

OverviewThe following steps summarize the FLEXlm installation as it pertains to MSC.Mvision. For more specific information, or information on integration with other products using FLEXlm, consult the FLEXlm documentation. See the section, Additional Documentation on page 58. For Windows users, please use the install shield program to install the FLEXlm server or to point to a license.dat file. The following instructions are for Unix/Linux only.

Obtaining an MSC.Mvision License File

To obtain a license file from MSC.Software, you need to determine the host id of the machine that will function as your license server. The mscsetup utility obtains this information for you, or you can run the lmhostid utility:

<install_dir>/bin/lmhostid

You can use the /flexlm/mscsetup utility to create an Authorization Request form. Send this form to your MSC.Software sales representative to obtain your permanent license.

Installing a ServerMSC.Mvision obtains a license by locating the license file, license.dat, which tells it the name of the license server node and the port number for communicating with the license manager daemon, lmgrd. The lmgrd daemon determines what node and port are associated with the vendor daemon, msc, and returns that information to MSC.Mvision. The application then contacts the vendor daemon which grants licenses, if they are available.

Place the License File on the ServerThe mscsetup utility automatically installs the license.dat file, if you provide it during installation.

If you have other existing FLEXlm products, you need to integrate them with the new MSC.Mvision license. See the section, Additional Documentation on page 58 for documents that will provide instructions for this integration.

The license file may be located anywhere on your license server. MSC.Software recommends locating it in:

<install_dir>/flexlm/licenses/license.dat.

55CHAPTER 4Installing FLEXlm

Check Paths and Server Names in the license.dat FileCheck that the license.dat file for your installation contains the correct server and port settings:

SERVER hostname XXXXXXXX portDAEMON MSC <install_dir>/flexlm/<platform>/msc

The first line is the server line. SERVER must be in all caps, followed by the hostname, then the lmhostid, then the port the daemon will monitor.

The hostname can be determined by typing hostname on the machine you are using as the license server.

The second line is the daemon line. DAEMON must be in all caps, followed by MSC, which also must be in all caps. This is followed by the path to the MSC.Software vendor daemon executable which is in lower case. The executable is located in

<install_dir>/flexlm/<platform>/msc,

where <platform> is machine dependent and has the following values:

• hpux

• irix

• solaris

• aix

• linux

Start the Manager DeamonsOn the license server, start the license manager daemon with the flexlm script. Do not execute this as root since it may create a security risk on your network.

<install_dir>/flexlm/bin/flexlm lmgrd

If the license.dat file is located in <install-dir>/flexlm/licenses, this script will start the following daemons:

1. lmgrd - the server daemon

2. msc - the vendor daemon

Note: The port is 1700 by default, but can be any free port.

Note: XXXXXXXX is the host id of the system as obtained by lmhostid.

56

Setting the lmgrd Daemon to Execute on RebootCaution: Remember do not run lmgrd as root.

Modify the appropriate reboot script for your server (/etc/rc.boot, /etc/rc.local, etc.) to include the following line if the user’s () login shell is csh:

su username -c `umask 022; <install_dir>/flexlm/bin/lmgrd -c <license_path>& log_file&’

OR

If the username’s login shell is sh:

su username -c `umask 022; <install_dir>/flexlm/bin/lmgrd -c <license_path log_file 2>&1 &’

where license_path is the location of the license.dat file. For example,

<install-dir>/flexlm/licenses/license.dat)

and log_file is the file to which the daemon will write messages.

Setting up Clients to Access the Floating LicenseYou have two options for setting the file location on clients:

1. Make the license.dat file available on each client. The default location is <install_dir>/flexlm/licenses/licenses.dat

2. Set the MSC_LICENSE_FILE environment variable to “port@hostname.” This environment variable can also be set in the mv_prolog file in the <install-dir>.

Installing a Nodelock File

A FLEXlm nodelock license file differs from a network file with the addition of a host id at the end of each FEATURE line.

If you have a temporary or demonstration license it may be supplied as a nodelock license.dat file. To use this file, place it in the

<install_dir>/flexlm/licenses/license.dat

OR

set the MSC_LICENSE_FILE environment variable to the locations of the license file. For example:

setenv MSC_LICENSE _FILE <install-dir>/flexlm/licenses/license.dat

This environment variable can also be set in the mv_prolog file in the <install-dir>.

57CHAPTER 4Installing FLEXlm

Updating Codes on an Existing Unix ServerIf you have an existing MSC.Mvision Builder and Evaluator installation (Version 3.4.3 or later) and have received new codes, use the following procedure to update the licensing:

1. Edit the new license file.

2. Replace the existing license file.

3. Force the daemon to read the new license file.

Editing the New License FilePlace the new codes in a license file named license_new.dat in the same directory as the existing license.dat file. 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 123456 1700DAEMON MSC /<install_dir>/flexlm/bin/msc

Replacing the Existing License FileRename the existing license.dat file to license_old.dat, and the name the new file to the current license file name of license.dat:

mv license.dat license_old.datmv license_new.dat license.dat

Forcing Daemon to Read the New License FileUse the lmreread command to cause the lmgrd daemon to reset using the new license file:

<install_dir>/flexlm/bin/lmreread -c <license-path>/license.dat

You should now be able to run MSC.Mvision Builder and Evaluator using the new licenses. If for some reason this fails, kill and restart the daemons as follows:

<install_dir>/flexlm/bin/lmdown -c <license_path>/license.dat<install_dir>/flexlm/bin/lmgrd -c <license_path>/license.dat

where license_path is the location of the license.dat file, as in the example:

<install-dir>/flexlm/licenses/license.dat/license.dat

Caution: During this process, all users will temporarily lose contact with the license server. Therefore, we recommend that all users exit MSC.Mvision Builder and Evaluator until the update process is completed.

58

Additional DocumentationFor additional information concerning FLEXlm, consult your vendor documentation. MSC.Software provides a FAQ and End Users Guide in HTML format on the CD-ROM. To view these documents you need an HTML compatible World Wide Web browser such as Netscape Navigator, or Mosaic.

The documents are stored in:

<install_dir>/flexlm/htmlman/index.htm

To obtain additional information and information on auxiliary products such as FlexAdmin, visit the Globetrotter Web Page. If you have Internet access, set your browser to:


Note: MSC.Software provides only the End User Guide and FAQ.



5 Setting the User Environment

� Overview

� Starting MSC.Mvision Builder and Evaluator (Unix/Linux)

� Setting Print and Preview Options

� Setting the Default Printer

� Environment Variables

� Required Environment Variable for DPI

� Customizing Start-up and Shut-down

60

OverviewBefore using MSC.Mvision Builder and Evaluator, the user’s environment must be setup. Additional customization for your user community can be achieved by setting optional environment variables.

This chapter explains the environment settings and file management procedures required to run MSC.Mvision Builder and Evaluator on UNIX systems. You are urged to read this section carefully. The recommendations contained in this section effect how each individual at your site will use MSC.Mvision Builder and Evaluator.

Starting MSC.Mvision Builder and Evaluator Windows/XP After installation MSC.Mvision Builder and Evaluator can be started from the system Start Program menu. Select Start -> Programs -> MSC.Software -> MSC Mvision 2006r1 -> mvbuild or mveval. The default startup directory is the <mvision_install_dir>. The Mvision system will write log, session, export and output files to this directory, this is the "startup directory". You can change the "startup directory" by clicking the right mouse button on the mvbuild or mveval menu option and selecting "properties". In the properties dialog enter the desired location for the "startup directory" in the "Start in" text field and click "OK". MSC.Mvision Builder and Evaluator will now startup and write files to the specified directory. See Customizing Start-up and Shut-down on page 74 for further information and trouble shooting.

Starting MSC.Mvision Builder and Evaluator (Unix/Linux)

The startup of MSC.Mvision Builder and Evaluator requires very few changes to a user’s login environment. You have several methods from which to choose. Each method must be implemented for each MSC.Mvision Builder and Evaluator user.

Modifying the User PathMSC.Software recommends that you set each user’s path so that MSC.Mvision Builder and Evaluator can be started from any directory. This requires each user to add the bin directory found in MSC.Mvision Builder and Evaluator installation directory to their PATH environment variable. For example, if MSC.Mvision Builder and Evaluator is installed in the directory /msc/mvision2006, the user should add the following directory to the path:

/msc/mvision2006/bin

61CHAPTER 5Setting the User Environment

If you are using the C-shell, edit your ~/.cshrc file and add /msc/mvision2006/bin to the set path or setenv PATH line. If you can’t find that line in the file, add the following line to the end of the file:

set path = ( $path /msc/mvision2006/bin )

If you are using the Bourne shell or Korn shell, edit your .profile file and add /msc/mvision2004/bin to the PATH variable. If you cannot find that line in the file, add the following line to the end of the file:

PATH=$PATH:/msc/mvision2006/bin; export PATH

When this is complete, open a new X-window and type mvbuild or mveval to activate MSC.Mvision Builder and Evaluator. If this command does not work, add the flag -v to the command as follows:

mveval -v

or

mvbuild -v

This causes the command to issue messages (verbose mode) as it processes. This is particularly useful when diagnosing a problem with the installation.

Creating an Alias Executing MSC.Mvision Builder and Evaluator without adding the path to the user’s environment normally requires typing into the UNIX command line the full path to the executable and the startup command. You can effectively rename the path and command by adding an alias (a single word substitute) to the ~/.cshrc file in the user’s home directory.

In the following examples, MSC.Mvision Builder and Evaluator were installed in the directory /msc/mvision2006. An alias called mveval is being created for an individual user.

The syntax used to create the alias depends on the shell you are using.

• If you are using the C shell, use the following command to define an alias in the ~/.cshrc file:alias mveval /msc/mvision2006/bin/mveval

• If you are using Korn shell, use the following commands to define an alias in the .profile file:alias -x mveval=’/msc/mvision2006/bin/mveval’

• If you are using the Bourne shell, use the following command to define an alias in the .profile file:

mveval(){/msc/mvision2006/bin/mveval}

62

Creating a ScriptYou can also place a script named mvbuild and another named mveval to start MSC.Mvision Builder and Evaluator in a directory that is already in the user’s path. For example, a C shell script to start MSC.Mvision Evaluator could be as follows:

#!/bin/cshswitch ( $#argv )

case 0:exec /msc/mvision2006/bin/mvevalbreaksw

default:exec /msc/mvision2006/bin/mveval $argv[*]breaksw

endsw


Creating a LinkThe mveval and mvbuild commands do not work if you create a link which points to them. This is because the commands in the bin directory are links to a special wrapper script. The wrapper script attempts to determine the location of the MSC.Mvision installation and sets various environment variables based on the location of the original link. If you create a link to the link in the install, then the wrapper script will assume that your link is in the install and may set these environment variables incorrectly.

If you wish to set a link to the command, you must also set the MV_HOME environment variable to the location of the MSC.Mvision installation. In our previous example, the install was in /msc/mvision2006 and you would set MV_HOME as follows:

setenv MV_HOME /msc/mvision2006

Starting MSC.Mvision Builder and Evaluator (Windows)

1. Create a short-cut to the <install_directory>/bin/mvbuild.bat or mveval.bat file and place it on your desktop. Modify the Current Working directory to point to a folder that you would like the log and session files to be written to.

2. Select Start, Programs, MSC.Software, MSC.Mvision 2006, mvbuild.bat or mveval.bat

3. Make sure <installation_directory> is included in the Windows environement variable "Path". Once this is complete, the user can type in mvbuild.bat or mveval.bat from any CMD or CSH window.

Setting DISPLAY VariableUnder some circumstances, you may need to set your DISPLAY environment variable to your machine’s IP address. Normally you set your DISPLAY variable to <machine_name>:0.0 where <machine_name> is the name of your workstation.

For example, at MSC.Software, the workstations are named after cities. If your machine is named paris, then the display is set to:

setenv DISPLAY paris:0.0 (C shell)DISPLAY=paris:0.0;export (Bourne shell)export DISPLAY=paris:0.0 (Korn shell)

If you are planning to use MSC.Mvision Builder and Evaluator on a SGI workstation and display the output on paris, you will need to set the display to the machine’s IP address for paris instead of string paris. If the IP address for paris is 144.54.72.28, you would set the display using one of the following:

setenv DISPLAY 144.54.72.28:0.0 (C shell)DISPLAY=144.54.72.28:0.0;export (Bourne shell)export DISPLAY=144.54.72.28:0.0 (Korn shell)

64

This is necessary for FrameViewer to display on your workstation. If the DISPLAY is not set to the IP address, you may have problems with the print preview and the on-line help. If you are running locally on one of these machines, you can leave the DISPLAY set to the machine name.

Command Line OptionsThe mveval and mvbuild commands have the following command line options:

Setting Print and Preview OptionsMSC.Mvision Builder and Evaluator provides three print/previewer options. One or all of these options can be made available in your installation. The availability (visibility) of these options can also be controlled using the resource settings file, see Application Resource File on page 49. Required Environment variables for the Print/Preview options can be set in the <install_dir>/mvision2006/resources/mv_prolog script, see Customizing Start-up and Shut-down on page 74. The three Print/Preview options are:

• Output to PDF - PDF is the Portable Document Format used by Adobe Acrobat, the document formatting program used in formatting the printed output. PDF output is particularly useful if you are in an environment in which you use multiple system platforms, making it possible to view the PDF from virtually any operating system.

• Output to HTML - HTML (Hyper Text Markup Language) is a standard language used extensively for transporting and displaying documents on the World Wide Web (www). For example, if you output a file in HTML format, you can then display it using a web browser such as Netscape or Explorer.

Option Action

-h Lists all command line options

-notebook notebook_name

Starts Evaluator or Builder using the specified notebook (file name).

-last_notebook Starts Evaluator or Builder using all the settings present when the product was last shutdown. The notebook is stored in ~/.mvision/[mvbuild or mveval]/notebook.

[-databank file] Starts Evaluator or Builder with the specified databank opened by default.

[-settings settings_file] Starts Evaluator or Builder using the specified settings file.


• Output to MIF - MIF is the Maker Interchange Format used by Adobe FramemakerTM, the document formatting program used to format the printed output. MIF output is particularly useful is you use Framemaker, making it possible to incorporate the formatted output from MSC.Mvision directly into a Framemaker document. There are also many popular word processing programs that can either directly read or translate MIF files. This option is not supported on Microsoft Windows/XP.

Setup and Operation HTML Print/PreviewFor the HTML preview and print the Mvision system executes the $MV_HOME/bin/.bin/startbrowser script. This script initiates the $MV_BROWSER executable with the URL as the arguments. By default the MV_BROWSER executable is set in the mv_Prolog script to be "netscape". If you can execute the command "netscape" on the command line and a browser appears then nothing is required (this means that a netscape executable is in the users path). If this does not work then you must change the command value for MV_BROWSER in the mv_prolog script. The actual printing of the HTML document is performed by the browser application in accordance with the browser configuration.

The on-line help documentation is viewed using the HTML preview method.

Setup and Operation PDF Print/Preview For the PDF generation, the Mvision system first calls the $MV_HOME/bin/.bin/startpdflatex script which generates the pdf files using the latex translator. By default the system searches for "texmf' in $MV_HOME/tex and /usr/local/tex. If you have performed the standard installation the $MV_HOME/tex should exist. If not create a $MV_HOME/tex link to the location of the latex installation. If .pdf files are being created then this operation is okay.

Note: MSC.Software Corporation no longer distributes FrameViewer with its software. If you wish to preview and print using the Output to MIF option, you must have Adobe FrameViewer or Framemaker installed on your machine.

Note: The MSC.Mvision system operations and methods are very similar for both UNIX/LINUX and Windows/XP platforms. In the following discussions the references to $MV_HOME/bin/.bin/ scripts applies to Unix/Linux platforms. On the Windows/XP platform these same scripts are located in %MV_HOME%/bin and are DOS batch scripts (.bat). System variables referenced as "$" in this discussion apply to Unix/Linux platforms. On the Windows/XP platform these variables are referenced as "%".

66

For PDF preview, the Mvision system calls the $MV_HOME/bin/.bin/startacroread script. This script initiates the acroread application with the latex generated files as arguments. The script searches for "acroread" in $MV_HOME/acroread and /usr/local/acroread. If the acroread application does not exist at either of these locations you can set the ACROREADHOME variable in the mv_prolog script and this location will be added to the front of the search path. The actual printing of the PDF document is performed by the Adobe Acrobat application in accordance with the application configuration.

The on-line Manuals are viewed using the PDF preview method.

Setup and Operation MIF Print/PreviewFrameViewer is no longer included with MSC.Mvision products and is not supported on Microsoft Windows/XP. If you have a previous installation of FrameViewer, you can use the MIF Print/Preview option by configuring you system as described below.

The FMHOME Environment Variable is used by MSC.Mvision Builder and Evaluator to facilitate the Print/Preview function. The FMHOME environment variable defines the location of your FrameViewer installation directory. If the FMHOME variable is not set, the MSC.Mvision processes that use FrameViewer will use Adobe Acrobat instead.

If the "FMHOME" variable is set, you will see the "MIF" print options in the top of the "Print" dialog. The "FMHOME" variable must be set to use the MIF Print/Preview option.

For the MIF generation, the Mvision system first calls the $MV_HOME/bin/.bin/startfmbatch script which generates the mif files using the fmbatch application. By default the system searches for "/bin/fmbatch' in $FMHOME, $MV_HOME/frame, /usr/frame and /usr/local/frame. You can create a link <install_dir>/mvisison2006/frame that references your existing FrameMaker installation directory and set this as the value for the "FMHOME" variable. If .mif files are being created then this operation is okay.

For MIF preview, the Mvision system calls the $MV_HOME/bin/.bin/startviewer script. This script initiates the Frameviewer application with the fmbatch generated files as arguments. The script searches for "/bin/viewer" in $FMHOME, $MV_HOME/frame, /usr/local/frame and /usr/frame. The FMHOME variable can be set in the mv_prolog script and this location will be added to the front of the search path

Note: Support for international FrameViewer has been discontinued by Adobe Systems who produces FrameViewer. This means we are no longer able to support FrameViewer resource settings for French and German languages or European paper sizes.


Trouble Shooting Print/Preview To get more information on any commands not found or variables set incorrectly you can set the environment variable MV_DEBUG = 1 in you shell (window) before executing Mvision and the wrappers and scripts will provide verbose information to standard out.

For proper execution of the Print and Preview functions verify that the auxiliary application (i.e. netscape, acroread, viewer, etc.) that is being called is working correctly. From the command line execute the command as it is being called in the startup script. For example "netscape", or $ACROREADHOME/bin/acroread, or $FMHOME/bin/viewer, etc..

To get a verbose output of the variable setting and commands being called. Set the environment variable MV_DEBUG (i.e. setenv MV_DEBUG 1, or MV_DEBUG=1;export MV_DEBUG) and then execute Mvision and perform the print or preview operation.

If you are using HummingBird Exceed as an X-emulator and the HTML plot output is black, this is an exceed configuration setting problem. Set the print options to Print Graphics in Color. When viewing through Exceed, you must first go into the Exceed toolbox and open the configuration option. In the config GUI, select "Display and Video". In the screen0 page, select Pseudocolor from the Server Visual menu and then click the checkmark in the top menu bar to apply changes. Open a new Exceed window and run MSC.Mvision.

For operation on Windows/XP to specify an executable in a .bat script you must enter the full path to the executable. You can use any command that can be executed in a MSDOS command window and you can use any preset system or shell environment variables, For example, "%ProgramFiles%\Internet Explorer\IEXPLORE. EXE", If the path contains a "\" character you may be required to escape this character with an additional "\" (i.e. "file:///%URL%").

Setting the Default PrinterSetting the default printer for MSC.Mvision Builder and Evaluator 2006 requires setting the parameters for the individual processes (modules) that offer printing capability:

• Materials Browser and Data Viewer

• Spreadsheet

• Full-Text Browsers

Printers can be set globally or for individual users.

Note: To use FrameViewer it may be necessary to set the display on your workstation. If the DISPLAY is not set to the IP address, you may have problems with the print preview and the on-line help. Refer to "Setting DISPLAY Variable", for detailed instructions.

68

Printing from the Materials Browser or Data ViewerThe print functions for the Materials Browser and Data Viewer on Unix platforms uses the FrameViewer , Web Browser and Adobe Acrobat software. On Windows/XP and Linux the print functions for the Materials Browser and Data Viewer uses the Web Browser and Adobe Acrobat software. The preferred method to set the default printer for all modules of the MSC.Mvision system that use FrameViewer is to set the environment variable PRINTER in the user’s .cshrc file (for example: setenv PRINTER <printer-name>). If set, this variable will provide a default for the Material Browser and Data Viewer print functions as well as the lpr command. On platforms that use the lp command, set the environment variable LPDEST. The search path for the default printer uses the following order:

1. MV_PRINTER (variable setting in the user’s /home/.cshrc file)

2. PRINTER (variable setting in the user’s /home/.cshrc file)

3. LPDEST (variable setting in the user’s /home/.cshrc file)

4. startviewer script (in the <install_dir>/bin/.bin directory)

A global setting for the default printer for printing from the Materials Browser and Data Viewer can be set by modifying the startviewer script in the <install_dir>/bin/.bin directory. Change the line:

set default_printer = ps

to:

set default_printer = <printer_name>.

Or, a global printer setting can be invoked by including the line setenv PRINTER <printer-name> in the mv_prolog file. This will override individual user’s PRINTER settings.

Note: To set the system "default printer" for Windows/XP platforms refer to you Microsoft Operating System information. The print function with exception of the fulltext browser and spreadsheet is controlled by the configuration of the viewing application (i.e. web browser or Adobe Acrobat).

Note: Printer commands and settings are stored in the ~/.mvision notebook and settings file. If you are using a notebook or settings, modified environment variables maybe ignored. Remove the ~/.mvision directory and contents after changing environment variables.


To set the default printers for individual users to print from MSC.Mvision modules that use FrameViewer, set the user’s environment variable PRINTER in the ~/.cshrc file to the name of the printer as described above. This variable provides a default for the Materials Browser and Data Viewer print functions and the UNIX lpr command.

Setting the variable MV_PRINTER to the printer name will set the default printer for use with MSC.Mvision Builder and Evaluator without affecting general UNIX printing. Variables set in a user’s ~/.cshrc file override the default printer settings stored in the startviewer script.

Printing from the SpreadsheetPrinting from the spreadsheet requires that you change the resource setting Mvbuild*defaultPrinterName or Mveval*defaultPrinterName in the Mvbuild or Mveval resource files. This can be done on the user level, by creating a local resource file or on the site level by modifying the resource file in the installation directory for MSC.Mvision Builder and Evaluator 2006.

The file should read either:

Mvbuild*defaultPrinterName: <printer_name>Mveval*defaultPrinterName: <printer_name>

This setting applies only to the spreadsheet print functions. For Windows/XP the resource file should be:

Mvbuild*defaultPrinterName: /d:\\\\printserver\\sharename Mveval*defaultPrinterName: /d:\\\\printserver\\sharename

where the value is the full path to a network accessible printer. This process use the %SystemRoot%\system32\print.exe command.

Printing from the Full-Text BrowserTo set the default printer command for the Full-Text Browser, you must set the environment variable:

MV_PRINT_COMMAND

to a string containing the UNIX command used by your machine. If more than one argument is required, the string must be placed in double quotes.

MV_PRINT_COMMAND “lp -d<printer_id>”

If the environment variables PRINTER or LPDEST are set, the printer name is not required in the command. The variable is then simply:

MV_PRINT_COMMAND lpr

Note: Platforms that use the UNIX lp print command should set the environment variable LPDEST.

70

It is recommended that the environment variable be included in the user’s .cshrc file or the mv_prolog file.

On Windows/XP platforms the fulltext browser will prompt the user for the print command. To preset the print command on Windows/XP set the "MV_PRINT_COMMAND" in the <install_dir>/resources/mv_prolog file or the users ~/mv_prolog file. The command %SystemRoot%\system32\print.exe or just "print.exe" can be used . Refer to Microsoft system documentation for usage of this command. The filename argument is passed automatically and is not part of the command. You can use any command that can be executed in a MSDOS command window and you can use any preset system or shell environment variables, If the path contains a "\" character you may be required to escape this character with an additional "\". Also see Customizing Start-up and Shut-down on page 74 for additional information.

Environment VariablesThere are several environment variables that you can use to further customize MSC.Mvision Builder and Evaluator. If the MSC.Mvision software is properly installed, you are not required to set these variables; they are strictly options used to customize MSC.Mvision Builder and Evaluator’s operation. Refer to Customizing Start-up and Shut-down on page 74 for further information.

The command to set an environment variable depends on the type of shell you are running.

• For C-shell: setenv <variable_name> <value>

• For Bourne shell:<variable_name>=<value>; export <variable_name>

• Korn shell: export <variable_name>=<value>

• MS-DOS (Windows/XP): Environment variables can be set via Start -> Settings -> Control Panel -> System -> Properties -> Advanced -> Environment Variables Environment variables can be set in .bat scripts or on the command line with syntax "set <variable_name>=<value>"

Licensing Environment VariableThere are many environment variables that control the operation of MSC.Mvision. Most of these are optional or are automatically set for you each time you run MSC.Mvision Builder and Evaluator. One such environment variable is MSC_LICENSE_FILE, which identifies either the host machine for the license server or the location of the license file. In a typical installation the mscsetup installation script sets the MSC_LICENSE_FILE environment variable in the <install_dr>/mvision2006/resoureces/mv_prolog file during the install process.


The syntax for the variable is as follows:

MSC_LICENSE_FILE <port@hostname>

OR

MSC_LICENSE_FILE <license_path>

In the first case, the <port@hostname> is the hostname of the machine where the FLEXlm license server is running and the port on that host that the server is using. In the second case, the <license_path> is the full path to a license file. See Installing FLEXlm (Ch. ).

The MV_HOME Environment Variable

The most important environment variable is the MV_HOME variable. It defines where MSC.Mvision was installed and is automatically set when you start MSC.Mvision Builder and Evaluator. The system environment variable MV_HOME must be set to the full path of the <mvision_install_directory> for proper operation on Windows/XP, but is generally not required for operation on Unix/Linux platforms.

The MV_PATH Environment Variable

The MV_PATH environment variable defines a series of directories searched by the system for external files. It defines where MSC.Mvision Builder and Evaluator were installed and is automatically set at startup. You generally don’t need to set this variable.

MV_PATH is searched for all of the following:

• Databanks when opened from a Browser form (includes all databank units files, mapping files, and disclaimer files).

• FrameViewer hardcopy files (temp*.mif, logo.rf).

• On-line Help and User’s Manual resources.

• Icon resources.

• Message catalog.

• Export templates.

• .PDF hardcopy files (temp*.pdf, logo.jpg).

A version of all of these files is stored in the installation directory and does not need an MV_PATH to run. MSC.Mvision searches the directories in the MV_PATH for these files before it gets the version in the installation directories. This allows you to use customized versions of these files placed in your personal directories, instead of the files in the installation directory.

The default setting for MV_PATH is the current directory (the one you were in when you started MSC.Mvision Builder and Evaluator) and your home directory. The path can be set to multiple directories.

72

The MV_TMPDIR Environment Variable

The MV_TMPDIR environment variable defines a directory where all temporary files are stored during an MSC.Mvision Builder and Evaluator session. Temporary files include scratch files created by printing, imaging and the XY graphics subsystems. By default MV_TMPDIR is set to the current directory, i.e. the one you were in when you started the Builder or Evaluator session.

The MV_TMPDIR setting is ignored if you have set the system TMPDIR environment variable.

Note: The setting of this variable is very important when using MSC.Mvision Builder to build new databanks. You should make sure that it is set to a disk with free space. The Builder creates several scratch files using the directory set by this variable. A good rule of thumb is to have free disk space of at least three times the size of the complete databank.


The MV_DB_DIR Environment Variable

The MV_DB_DIR environment variable defines the location of the MSC.Mvision databanks. If undefined, MSC.Mvision Builder and Evaluator search for databanks in the following paths and files in the following order;

1. <install_dir>/db

2. MV_PATH

3. Mveval or Mvbuild resource files

To activate this feature, the appropriate lines in the <install_dir>/resource/Mveval or <install_dir>/resource/Mvbuild files must be uncommented. The setting in the resource file will take precedence over the MV_DB_DIR variable.

The MV_USER_BIN Environment Variable

The MV_USER_BIN defines a directory where a user can place modified MSC.Mvision executables. By default the system looks in ~/mvbin for these modified executables.

When you type an MSC.Mvision command, the startup script searches directories for the executable program in the following order and executes the first version of the executable it locates:

1. The directory defined by the MV_USER_BIN variable.

2. /~/mvbin

3. $MV_HOME/bin/.bin directory, where the executables are initially installed and permanently stored.

The MV_PRINTER Environment Variable

For a more complete description, see the section Setting the Default Printer on page 67.

The MV_PRINT_COMMAND Environment Variable

For a more complete description, see the section, Setting the Default Printer on page 67.

The FMHOME Environment Variable

FrameViewer is used by MSC.Mvision Builder and Evaluator to facilitate the print function. The FMHOME environment variable defines the location of your FrameViewer installation.

74

If the FMHOME variable is not set, the MSC.Mvision processes that use FrameViewer will use Adobe Acrobat instead.

Required Environment Variable for DPIThe DPI (Database Programmatic Interface) module can be executed directly from the command line. This module does not use the standard wrapper to setup the user’s environment. For MSC.Mvision Builder and Evaluator v2006, the message catalog has been changed to allow for internationalization. This means that the user must set the search path for the message catalog.

To execute the DPI directly, the user must have the following line in the ~/.cshrc file at startup or enter the following on the command line before initiating the DPI:

setenv NLSPATH <install_dir>/resource/%N

Customizing Start-up and Shut-down

The MSC.Mvision Builder and Evaluator uses a startup script called a wrapper script. The wrapper script is executed to setup the current shell environment and then calls the actual executable with the appropriate arguments. The wrapper script checks for most of the environment variables mentioned in the previous sections. The wrapper script is designed to check for the existence of environment variables which are required for proper execution. If the user has not set specific environment variables, then the wrapper script will create a default setting based on various assumptions. Generally, these assumptions produce the proper execution environment.

Note: If you have FrameMaker and FrameViewer already installed on your system, you can delete the frame directory that is in the MSC.Mvision installation and set FMHOME to the location of the installed executable.

Note: The MSC.Mvision system operations and methods are very similar for both UNIX/LINUX and Windows/XP platforms. In the following discussions the references to the $MV_HOME/bin/.wrapper script applies to Unix/Linux platforms. On the Windows/XP platform the mvbuild.bat and mveval.bat scripts operate in the same manner as the wrapper. These scripts and associated scripts are located in %MV_HOME%/bin. There is no .bin directory or folder in the Windows/XP installation. Any system variables which are set in the mv_prolog.bat file will be available in the resource file specification and in launching auxiliary applications from MSC.Mvision.


If the default settings are not correct, you can change the user’s ~/.cshrc or ~/.profile file by adding environment variables or modifying the wrapper script directly. The preferred method is to use a special feature built into the wrapper script for customizing these settings using a prolog file.

After the wrapper script has made all its checks and set all the required variables, it looks for a file named mv_prolog in all of the following locations: <install_dir>/mvision2006/resources, <~/.mvision/users_home_directory>, <Current_working_directory> If the wrapper script finds a file with the name mv_prolog in any of these locations, it includes the file and executes the mv_prolog file as if it were part of the wrapper script. When the wrapper has finished including any mv_prolog files, it issues the command to run the command you originally issued. The wrapper script and the mv_prolog file is executed every time that a command is issued.

The mv_prolog file is a very useful tool in setting the required environment variables described in the installation guide.

There is also a mv_epilog file that is executed just before the wrapper script quits and after your original command has completed. The mv_epilog file can be located in the same locations as the mv_prolog file. It can be useful in cleaning up after the command is complete. For instance, you may want to have the default settings file removed each time you exit MSC.Mvision Evaluator. In the mv_epilog file you could automatically remove the ~/.mvision/mveval/settings directory.

Trouble Shooting Only one XSever at a time can be active on the Windows/XP platform. If you have an existing XServer such as Hummingbird Exceed installed, you are not required and may not want to install the SCO XVision server. If both Xservers are installed, you must disable one of these XServers prior to initiating MSC.Mvision Builder Evaluator.

On Windows/XP, MSC.Mvision does not start after installation is complete and the computer has been rebooted. The problem may be that the appropriate XServer is not specified or is not running. First verify that the appropriate XServer is specified for the MKS Toolkit. Select Start -> Settings -> Control Panel -> MKS Toolkit -> Runtime Settings -> XWindow System Settings. If you have installed the SCO XVision server, verify that the "SCO XVision" is selected and that "Use Network connection" is enabled. If you are using Exceed, verify that "Hummingbird Exceed" is selected. Otherwise verify that your installed XWindows server appears in the list and is selected. Click the "OK" button. if you have installed the SCO XVision server. To select the XVision Server go to Start -> Programs -> vision -> XVision Server. This should startup the server and an icon should appear in the toolbar. If the program prompts a request for optimization, select "Yes". If you have a different XServer installed, startup the Xserver in accordance with the application documentation. Restart the MSC.Mvision application.

For all platforms, to personalize the system and enhance performance MSC.Mvision saves many environment variable settings and configuration settings in directories under the users home ~/.mvision directory. If you have reset environment variables in the startup scripts or have reconfigured the MSC.Mvision system. Copy the ~/.mvision directory to another name

76

(i.e. mvision_bak, this directory may contain spreadsheet or graphics setting you may want to reuse), then remove the ~/.mvision directory and restart the MSC.Mvision application. A new ~/.mvision directory will be created on startup. Compare the contents of the two directories to determine if you want to reuse any of the previous settings.

Multiple platform usageMSC.Mvision reads and writes the settings files to the user's home directory ~/.mvision for both the Windows/XP application and the Unix/Linux application. If you have both versions installed and you are accessing both versions the ~/.mvision settings files may conflict. To resolve this issue you can configure a ~/mv_prolog or ~/mv_epilog script to either prompt the user and switch ~/.mvision directories and files on startup or configure the mv_epilog script to remove the ~/.mvision directory on shut-down.

MSC.Mvision Databank access on Windows/XPThe MSC.Mvision Builder Evaluator Windows/XP application can access any version of MSC.Mvision databanks which were created (built) on Windows/XP, LINUX or DECA. As of version 2004 all MSC.Mvision databanks are platform independent and the MSC.Mvision Builder Evaluator Windows/XP application can access MSC.Mvision databanks built on UNIX platforms with version 2004 or higher. the inverse is also true. Note that Windows/XP can access Unix/Linux "files" via a network mounted connection, but the Windows/XP system cannot follow Unix/Linux "links". To access a MSC.Mvision databank on a Unix platform the databank must be MSC.Mvision version 2004 or higher and must be a network mounted "file".

Setting Edit Commands on Windows/XP

The file editing command which is initiated using the "edit" button in the MSC.Mvision Builder dialogs is controlled by the %MV_HOME/resources/Mvbuild file setting "Mvbuild.edit_command:". By default this is set to "%MV_HOME%/bin/xterm.exe -e vi". This command uses the MKS installed "xterm.exe" utility and the SystemRoot "vi" command. This will provide an editor in a separate xterm window. Refer to Microsoft system documentation for usage of this command. The filename argument is passed automatically and is not part of the command. You can use any command that can be executed in a MSDOS command window and you can use any preset system or shell environment variables, If the path contains a "\" character you may be required to escape this character with an additional "\". You can change this command to use your preferred editor.

Setting Helper Commands on Windows/XP

Refer to Using Helpers (p. 135) in MSC.Mvision Builder and Evaluator 2006 Installation Guide" section for detailed instructions on setting helper applications. For operation on Windows/XP to specify an executable you can use the browse button in the helper dialog to enter the command this will return the command in the form, "/C=/MSC.Software/MSC.Mvision/2006r1/bin/xterm.exe -e vi %s"

I N D E XMSC.Mvision Builder and Evaluator 2006 Installation Guide

Symbols$ENVIRONMENT, 50$XAPPLRESDIR, 50$XFILESREACHPATH, 50$XUSERFILESEARCHPATH, 50.Xdefaults, 50, 51

Aapplication resource file, 49

Mvbuild, 49Mveval, 49searching for, 50system, 49user, 50

authorization form, 41

Ccarriage return, 9CD-ROM

mounting, 32CD-ROM drive

how to remove, 32clientDecoration, 51Customer Information Sheet, 10

DDatabank

definition, 10database

definition, 10Deliverables, 14directories, 21

DISPLAY, 63Documentation, 14

Eenvironment variable

DISPLAY, 63FMHOME, 73MSC_LICENSE_FILE, 56MV_DB_DIR, 73MV_HOME, 71MV_PATH, 71MV_TMPDIR, 72MV_USER_BIN, 73

FFLEXlm

additional documentation, 58daemons, 55license.dat file, 40, 54lmgrd daemon, 55lmhostid, 54MSC_LICENSE_FILE, 56nodelock codes, 56server, 54SERVER setting, 55

FMHOME, 73FrameViewer

DISPLAY, 63

HHP

kernel settings, 25

INDEX74

Iinputting data, 9install

verify, 46installation, 28–??

device selection, 34directories, 21overview, 18–??preparation, 18removing CD-ROM, 32

installation directory, 34Introduction, 7

Llicense.dat file, 40, 54lmhostid, 54

MMSC.Mvision Building Databanks, 14MSC.Mvision Databanks, 11MSC.Mvision Installation Guide, 14MSC.Mvision User’s Guide and Reference, 14MSC_LICENSE_FILE, 56mscinfo, 23mscsetup, 31, 33

application options and prerequisites, 40authorization form, 41custom

custom, 37device selection, 34installation directory, 34license.dat file, 40selecting products, 35standard install, 37

MV_DB_DIR envirionment variable, 73MV_HOME environment variable, 71MV_PATH environment variable, 71MV_TMPDIR environment variable, 72MV_USER_BIN environment variable, 73Mvbuild, 49mvbuild command, 61Mveval, 49

OOpenMotif, installing, 26OpenMotif, prerequisites for, 26

Ppaging disk space, 24performance, improving with Linux, 26Preview of the Installation Procedure, 22product selection, 35

Rrandom access memory, 24resources

for your own use, changing, 49, 50window manager, 51

SSGI

DISPLAY, 63Software Authorization Information Sheet, 10standard installation, 37

XX Window resources

application resource files, 49window manager

borders, 51menus, 51

msc.mvision builder and evaluator 2006 - msc software corporation

Documents