Installing AVS/Express

Chapter 2 Installing and Licensing AVS/Express

---

This chapter provides instructions for installing AVS/Express Release 6.2. It includes the following sections:

• Installing AVS/Express
• Licensing AVS/Express
• Linking AVS/Express to the Database Kit
• Starting AVS/Express

Each of these sections contains detailed steps for installing AVS/Express. You should read the sections in order and complete all of the indicated tasks in the order presented to ensure a successful installation.

IMPORTANT: If you have not already read Chapter 1, System Prerequisites Release 6.2, and met all of the listed prerequisites for your platform, you must do so before you continue with the procedures in this chapter.

2.1 Installing AVS/Express

AVS/Express is supplied on compact disk (CD-ROM). The CD-ROM contains versions of AVS/Express for multiple hardware platforms. If you did not receive the CD, you should contact Advanced Visual Systems immediately. (This manual uses the terms CD and CD-ROM interchangeably to describe a compact disk.)

Note: If you cannot install from CD-ROM and must install from tape, please contact AVS Customer Support for assistance.

The installation procedure can be summarized in six steps.

• Install any other software listed in Chapter 1, System Prerequisites Release 6.2 as required for running AVS/Express on your platform.
• Mount the media.
• Run the installation script.
• Install or update the AVS/Express license.
• If necessary, link AVS/Express with the Database Kit.
• Set the variables that are necessary for finding AVS/Express when you start the application.

These steps are described in the sections that follow.

Mounting the Media

Before you mount the media, you should know where you want to install AVS/Express. By default, the installation program creates an express directory and installs AVS/Express in it. However, the installation program allows you to select a different installation directory.

Choose or create an installation directory now, and then write the full path and directory name in the table below for future reference. In the steps that follow, this install or home directory will be referred to as install-dir.

On some systems, the CD-ROM is automatically mounted; on others you need to use the mount command. Similarly, some systems require that you create a mount directory, whereas others have a /cdrom directory.

At this point, you should decide whether you already have a /cdrom directory, whether you want to use an existing directory, or whether you want to create a directory for mounting CD-ROMs. In any case, write the mount directory name in the table below for future reference. The directory that you specify will be referred to as /cdrom in all of the instructions that follow.

Follow the procedure below to mount the CD-ROM.

1. Insert the AVS/Express CD-ROM into the CD-ROM drive.

2. If necessary, mount the CD-ROM.

The mount command varies from platform to platform, and the device number for the CD-ROM drive depends on its SCSI ID. The device numbers shown below are sample numbers, so you should contact your system administrator to obtain the correct device number for your system.

Table 0-10

Operating System	Sample Mount Command
Windows 95, 98, 2000 Windows NT 4.0	No mount command is necessary.
Compaq Tru64 UNIX	mount -r -t cdfs /dev/rz4c /cdrom
HP-UX	mount -r -t cdfs /dev/dsk/5s0 /cdrom
AIX	mount -r -v cdrfs /dev/cd0 /cdrom
IRIX	The default IRIX configuration uses the mediad system daemon to automatically mount the CD-ROM as /CDROM. If the mediad daemon is not running, mount the CD-ROM as shown below: mount -r -t iso9660 /dev/scsi/sc0d4l0 /CDROM
Solaris	mount -r -t hsfs /dev/sr0 /cdrom

Running the Installation Script

This section describes how to read the AVS/Express software from the media and execute the installation program.

UNIX Platforms

1. Run the install.xp script.

Note: Depending on your system platform, the directory, file and script names may appear as all uppercase or all lowercase. If you notice a case difference, make the necessary adjustment when you enter commands.Some differences are highlighted in the table below.

Table 0-11

Platform	Command
Compaq Tru64 UNIX	/cdrom/INSTALL.XP
SGI with mediad	/CDROM/install.xp
Solaris with vold	/cdrom/avs_xp/install.xp

2. The installation program then leads you through the installation process.

IMPORTANT: If a "Permission denied" error message is displayed while you are running the installation script, the permissions need to be modified before you attempt to run the script again. Use the chmod a+x install.xp command to modify the permissions.

Note: On Unix platforms, when the installation is finished, you may wish to rename the install directory. Such renaming is helpful if you wish to maintain multiple versions of AVS/Express installed on the same machine.

Relinking Errors on some UNIX Platforms

When AVS/Express is installed, it is dynamically linked with many of its own shared libraries. In some cases additional libraries are required that may not be installed on your system. Advanced Visual Systems has included the libraries that might be missing in the directory <install-dir>/lib/<machine>/missing.

If you find the libraries required by the express executable are not available on your system, change the LD_LIBRARY_PATH variable to include the <install-dir>/lib/<machine>/missing directory as in the following example (assumes SunOS):

setenv LD_LIBRARY_PATH <install-dir>/lib/sun:<install-dir>/lib/sun/missing:/usr/openwin/lib

For more details, see the Installing AVS/Express manual.

Installing on Linux

To install AVS/Express on a Linux system:

1. Review the prerequisites described in Linux Prerequisites of this document.

2. Use the standard Linux commands to mount the AVS/Express CD.

3. Follow the instructions in the UNIX Installation section of the Installing AVS/Express manual to install AVS/Express from the tar file on the CD.

4. Set the LD_LIBRARY_PATH to include:

the Express runtime shared library path

the Mesa OpenGL shared library path, and

the Motif shared library path

5. Follow the licensing procedure outlined in Licensing AVS/Express 6.1 for Linux of this document.

To use Viz/Express, start AVS/Express with the -viz command line option.

Windows Platforms

You must have administrator privileges in order to install AVS/Express. This is because the installation program modifies the system PATH environment variable in the Windows Registry. Also, when you install the FLEXlm License Server, you will be adding a new system service, which requires administrator privileges.

The complete procedure for installing AVS/Express consists of the following steps:

1. Bring up the Run dialog box.

2. Click Start and select Run... from the options menu.

3. Run the setup.exe file by typing the following in the Run dialog box. (The example commands below assume that your CD-ROM drive is the D drive. If your CD-ROM is installed as a different drive, make the appropriate substitution in the command.)

• For Intel systems:

D:\windows\setup.exe

The installation program leads you through the installation process and takes about 10 minutes on an average 133MHz system.

2.2 Licensing AVS/Express

AVS/Express Release 6.2 uses version 5.12a of the FLEXlm license server. Read the items below to determine the steps you should take in order to license AVS/Express.

• If you are a new AVS/Express user...
  • ... and FLEXlm is not installed, you will need to install the FLEXlm software and create an AVS/Express license. Complete the procedure described in Requesting and Installing a New License File and then complete the procedure described in Installing and Starting the License Server.
  • ... and you are running a pre-5.12a version of the FLEXlm license server, you will need to update the FLEXlm software and create an AVS/Express license. Complete the procedure described in Requesting and Installing a New License File and then complete the procedure described in Installing and Starting the License Server.
  • ... and the 5.12a (or higher) version of the FLEXlm license server is installed, you will need to create an AVS/Express license. Complete the procedure described in Requesting and Installing a New License File.
• If you are upgrading from an earlier release of AVS/Express...
  • ... and you are running a pre-5.12a version of the FLEXlm license server, you will need to update the FLEXlm software. Complete the procedure described in Installing and Starting the License Server.
  • ... and the 5.12a (or higher) version of the FLEXlm license server is installed, you can skip this licensing section and go directly to either Linking AVS/Express to the Database Kit or Starting AVS/Express.

If your needs go beyond the information in this section or if you encounter any problems, you will find additional license-related discussions in Appendix A, Detailed Licensing Information. If your license situation is not described, please contact Advanced Visual Systems before continuing.

Note: Many of the examples in this chapter are based on the UNIX operating system. Wherever necessary, Windows-based information has been included; however, if you are running on a Windows platform, you should note that the paths in some of the examples may not match your system.

Licensing AVS/Express 6.1 for Linux

To license AVS/Express on Linux, you should create a file named license.dat that contains your license key on a single line, with no spaces or other characters. You should set the XP_LICENSE_FILE environment variable to tell AVS/Express where to look for the license.dat file. This variable must specify the full path, filename and extension of the license file, for example:

setenv XP_LICENSE_FILE /usr/licenses/license.dat

If XP_LICENSE_FILE is not defined, AVS/Express searches for the license file in $XP_ROOT. AVS/Express will also check for the license file in the top level project directory from which it is run.

License keys can be obtained by contacting AVS customer support.

Running AVS/Express Visualization Edition

AVS/Express Visualization Edition users should ensure that the XP_FEATURE environment variable is set to VIZ_EXPRESS before using the licdiag utility and before starting AVS/Express.

For UNIX:

setenv XP_FEATURE VIZ_EXPRESS

For Windows:

1. Select Start->Settings->Control Panel.

2. Double-click on the System icon.

3. Go to the Environment tab.

4. Change or create the XP_FEATURE environment variable and set it to VIZ_EXPRESS.

Running AVS/Express with the Solaris Visual Debugger

The Solaris Visual Debugger resets the LM_LICENSE_FILE environment variable to /opt/SUNWspro/license_dir. This prevents you from checking out a license when you try to run AVS/Express in the Solaris Visual Debugger. To avoid this problem, start the Solaris Visual Debugger, and set the LM_LICENSE_FILE environment variable to your AVS/Express license.dat file.

Requesting and Installing a New License File

If you are a new AVS/Express user, you must complete the following procedure to create a new license file.

If you have not yet completed a license request form, do so now.

The License Request Form was included with your media and documentation, but it is also available on the Advanced Visual Systems web page, at http://help.avs.com/licensing/.

FLEXlm works on the client/server model, so in order to complete the License Request Form, you must know where the licensing server processes will run (the host machine), whether you purchased a node-locked or floating license, and you will need to know which AVS/Express edition (Developer or Visualization) you are licensing.

Advanced Visual Systems will send the license information to you within eight hours of your request. The information that you receive will look similar to the information shown below.

• If you requested a license for a UNIX platform, you will receive information that looks similar to the following:

SERVER cobra 77baf8d9 7121
DAEMON avs_lmd <install-dir>/express/bin/<machine type>/avs_lmd
FEATURE EXPRESS avs_lmd 4.000 26-apr-99 1 0C645B33176F2661ACEA "GgVvDdCcJTSs"
77baf8d9

• If you requested a license for a Windows platform, you will receive information that looks similar to what is shown below:

SERVER cobra DISK_SERIAL_NUM=77baf829 7121
DAEMON avs_lmd <install-dir>\runtime\bin\<machine type>\avs_lmd.exe
FEATURE EXPRESS/PC avs_lmd 4.000 26-apr-99 1 5CD48B53B1B618DE753E "GgVvDdCcJTSs"
DISK_SERIAL_NUM=77baf829

Note: In both of these examples, the FEATURE line has wrapped to an additional line. It may also wrap when you copy it into your license file in Step Copy the SERVER, DAEMON, and FEATURE lines into the license.dat file.. The FEATURE line does not contain any line breaks; be sure not to add line breaks to the FEATURE (or any other) line when you add it to your license file or you will not be able to run AVS/Express.

Upon receiving the license-related information, contact Advanced Visual Systems for assistance if any of the following statements are true, because this manual does not include the procedures for licensing under these conditions.

• If the license information has three SERVER lines, you are running redundant servers.
• If the license file you received has only a FEATURE line and the number of licenses is set to 0, you do not need a license server. The following line highlights (in bold text) the number-of-licenses argument.

FEATURE EXPRESS avs_lmd 4.000 26-apr-99 0 0C645B33176F2661ACEA "GgVvDdCcJTSs"
77baf8d9

• If you have more than one existing license file; that is, more than one product is using FLEXlm licensing.

If the FLEXlm license server is running on your system, type the following command to stop the license server.

lmutil lmdown

Instructions to install the license on UNIX

1. Update the license.dat file.

The data in the license.dat file is used by the FLEXlm licensing mechanism to ensure that you are a licensed user of AVS/Express. The license.dat file is either in the location specified by the LM_LICENSE_FILE environment variable or in following directory:

• /usr/local/flexlm/licenses

Copy the SERVER, DAEMON, and FEATURE lines into the license.dat file.

If this directory does not exist, you can create the directory. If you are typing the information into the license.dat file, be sure not to confuse the letters "l" and "O" with the numbers "1" (one) and "0" (zero).

If you save the license.dat file in another location, make sure you set the environment variable LM_LICENSE_FILE to point to the license file.

Note: Do not add line breaks to these lines when you add them to your license file or you will not be able to run AVS/Express.

If you are using multiple license files, LM_LICENSE_FILE should contain all license file names in a colon separated list. For example:

LM_LICENSE_FILE=/usr/local/flexlm/licenses/license.dat:/u2/express/license/avslic.dat

Once you have set LM_LICENSE_FILE, run lmstat -a and licdiag to verify that the license-related files are working.

On a UNIX platforms, these commands are in the following directory:

<install-dir>/express/bin/<machine type>

2. Here is a sample of what a license.dat file might look like:

SERVER unknown 77baf8d9 1700
DAEMON avs_lmd <install-dir>/express/bin/<machine type>/avs_lmd
FEATURE EXPRESS avs_lmd 6.000 1-jan-00 1 0C645B33176F2661ACEA "GgVvDdCcJTSs"

Edit only the SERVER and DAEMON lines:

The hostname is the name of the system where AVS/ Express will be running. Verify that the hostname on the SERVER line matches the value that is returned by either the uname -n or the hostname command.

The DAEMON line has two arguments: the daemon name and the path to the daemon. The license server uses this information to start the vendor daemon. The Advanced Visual Systems vendor daemon is called avs_lmd. Do not change the avs_lmd daemon name.Verify the information on the DAEMON line.

DAEMON avs_lmd <install-dir>/express/bin/<machine type>/avs_lmd

a. Ensure that the path to the avs_lmd executable is correct.

b. Ensure that the path to the avs_lmd does not include environment variables.

Note: If you are an advanced user of FLEXlm there may be an [options file] at the end of this line. Refer to Globetrotter's documentation for use of these control options. They are not necessary for installing or using AVS/Express.

DAEMON avs_lmd <install-dir>/express/bin/<machine type>/avs_lmd

The SERVER line has three arguments: the hostname, the host ID, and the port number. In the following example, the hostname, host ID, and port number are cobra, 77baf8d9, and 7121, respectively.

SERVER cobra 77baf8d9 7121

a. The hostname is the name of the system where AVS/Express will be running. Verify that the hostname on the SERVER line matches the value that is returned by either the uname -n or the hostname command.

b. Verify that the host ID matches the value returned by the lmhostid command (UNIX) or the vol command (Windows).

The host ID is used to create the encrypted FEATURE lines. If the host ID on the SERVER line does not match the value returned by either of the commands listed above, you must contact Advanced Visual Systems and request a new license.

c. The port number is the TCP/IP socket number that the AVS/Express process uses to connect to the license server.

On UNIX platforms this number may be absent if it is defined in the /etc/services file. If you need to change the port number, choose a port in the user-defined range between 1700 and 8000.

Make no changes to the FEATURE line, verify the FEATURE line.

The arguments on the FEATURE line are encrypted, therefore they cannot be modified. If you typed the information into the license.dat file, verify that you typed all the values and spaces correctly.

FEATURE EXPRESS avs_lmd 4.000 26-apr-99 1 0C645B33176F2661ACEA "GgVvDdCcJTSs"
77baf8d9

The arguments after the FEATURE keyword are as follows:

• <feature name> is the name of the product or feature being licensed. The feature name for the AVS/Express Developer Edition is EXPRESS; the feature name for the Visualization Edition is VIZ_EXPRESS.
• <vendor daemon> is the name of the vendor daemon associated with the licensed feature; all Advanced Visual Systems products use the avs_lmd vendor daemon.
• <vers> is the version number of the licensed feature. The 3.000 value allows you to run all AVS/Express 3.x releases and above.
• <date> is the expiration date of the license; 1-jan-00 means there is no expiration date.
• <# of licenses> is the number of licenses that have been purchased.
• <code> is an alphanumeric string containing encrypted licensing information.
• <"vendor_string"> contains a series of characters that control specific components of the licensed feature.
• [node machine id] appears only for node-locked licenses and is the machine id of the system where the feature executes. If the host server and execution node are the same (as is usually the case), this is the same machine id that appears on the SERVER line.

In Windows-platform based license.dat files DISK_SERIAL_NUM= appears before the node machine id

Make sure that you have not added any extra spaces or carriage returns to the

license file and resave it.

3. If you are using the Express Visualization edition, please set the following environment variable:

setenv XP_FEATURE VIZ_EXPRESS

4. Now you must start the license server.

see Installing and Starting the License Server in the Installing AVS/Express, section A, Detailed Licensing Information. Specifically, put here the Installing Licensing on UNIX Platforms. (its in the Installing and Starting the License Server)

5. Add here License Administration

6. Now you are ready to start Express. Add:

<install-dir>/express/bin/<machine type> to your search path.

The AVS/Express executable resides in the <install-dir>/express/bin/<machine type> directory.

Defining License-related Variables

Complete the steps below to ensure that the license server can locate your license.dat file.

1. Set the LM_LICENSE_FILE environment variable so that it points to your license file.

If you are using multiple license files, LM_LICENSE_FILE should contain all license file names in a colon separated list. For example:

LM_LICENSE_FILE=/usr/local/flexlm/licenses/license.dat:/u2/express/license/avslic.dat

2. Once you have set LM_LICENSE_FILE, run lmstat -a and licdiag to verify that the license-related files are working. Once you have set LM_LICENSE_FILE, run lmstat -a and licdiag to verify that the license-related files are working.

<install-dir>/express/bin/<machine type>

Instructions to install the license on a PC

VIZ EXPRESS on a PC floating license.

1. Copy the three line license file and save this in the C:\Flexlm directory as license.dat. If C:\Flexlm does not exist, you can create the directory.

2. An example of license.dat is shown below:

SERVER unknown DISK_SERIAL_NUM=2cc8e9e5 1700
DAEMON avs_lmd /usr/avs/license/avs_lmd
FEATURE VIZ_EXPRESS/PC avs_lmd 6.000 1-jan-00 1 1C7866FEA1C2F81FCAA6 "gvdcP"

Edit only the SERVER and DAEMON lines:

In the SERVER line, replace unknown with the host name of your machine.

In the DAEMON line, change the path to avs_lmd:

<path to avs_lmd>\avs_lmd.exe

Note: the default location of avs_lmd is c:\express\runtime\bin\pc\avs_lmd.exe, if you have placed it elsewhere, put this path in the DAEMON line.

Make sure that you have not added any extra spaces or carriage returns to the license file and resave it.

3. Set the XP_FEATURE environment variable:

Because you are running VIZ_EXPRESS/PC, you will have to direct Express to look for that product. It defaults to look for EXPRESS. Select: Control Panel>System>Environment. Set the variable XP_FEATURE to the value VIZ_EXPRESS/PC (notice this is the feature in the third line of your license file). Once this is set, you may have to reboot. When/if you have rebooted, go to the License Manager and proceed...

4. Set up the Flexlm License Manager in the Control Panel:

The Setup tab - In the empty space next to lmgrd.exe type in the path to lmgrd.exe (this should be where avs_lmd.exe is). Do the same for license.dat. (or click on the Browse button and find the file)

The Licenses tab - Make sure that you can pull up your license file by pressing "Show License File" key.

The Control tab - Now you are ready to start the server and run Express Viz.

Make sure you are trying to start Viz Express, and AVS/Express.

Express on a PC floating license.

1. Copy the three line license file and save this in the C:\Flexlm directory as license.dat. If C:\Flexlm does not exist, you can create the directory.

2. An example of license.dat is shown below:

SERVER unknown DISK_SERIAL_NUM=2cc8e9e5 1700
DAEMON avs_lmd /usr/avs/license/avs_lmd
FEATURE EXPRESS/PC avs_lmd 6.000 1-jan-00 1 1C7866FEA1C2F81FCAA6 "GgVvDdCcJTSs"

Edit only the SERVER and DAEMON lines:

In the SERVER line, replace unknown with the host name of your machine.

In the DAEMON line, change the path to avs_lmd:

<path to avs_lmd>\avs_lmd.exe

Note: the default location of avs_lmd is c:\express\runtime\bin\pc\avs_lmd.exe, if you have placed it elsewhere, put this path in the DAEMON line.

Make sure that you have not added any extra spaces or carriage returns to the license file and resave it.

3. Set up the Flexlm License Manager in the Control Panel:

The Setup tab - In the empty space next to lmgrd.exe type in the path to lmgrd.exe (this should be where avs_lmd.exe is). Do the same for license.dat. (or click on the Browse button and find the file)

The Licenses tab - Make sure that you can pull up your license file by pressing "Show License File" key.

The Control tab - Now you are ready to start the server

Express PC locked license

1. Copy the one line license file and save this in the C:\Flexlm directory as license.dat. If C:\Flexlm does not exist, you can create the directory.

2. An example of license.dat is shown below:

FEATURE EXPRESS/PC avs_lmd 6.000 1-jan-00 0 1C7866FEA1C2F81FCAA6 "GgVvDdCcJTSs" DISK_SERIAL_NUM=2cc8e9e5

Because this license file is just a FEATURE line, you do NOT need to start the license server. Simply save this line in the license.dat file. Make sure its one long continuous line (if its 2 lines, it will not work).

3. Set up the Flexlm License Manager in the Control Panel:

The Setup tab - In the empty space next to lmgrd.exe type in the path to lmgrd.exe (this should be where avs_lmd.exe is). Do the same for license.dat. (or click on the Browse button and find the file)

The Licenses tab - Make sure that you can pull up your license file by pressing "Show License File" key.

The Control tab - Do not start the License server.

VIZ Express PC locked license

1. Copy the one line license file and save this in the C:\Flexlm directory as license.dat. If C:\Flexlm does not exist, you can create the directory.

2. An example of license.dat is shown below:

FEATURE VIZ_EXPRESS/PC avs_lmd 6.000 1-jan-00 0 1C7866FEA1C2F81FCAA6 "gvdc" DISK_SERIAL_NUM=2cc8e9e5

Because this license file is just a FEATURE line, you do NOT need to start the license server. Simply save this line in the license.dat file. Make sure its one long continuous line (if its 2 lines, it will not work).

3. Set up the Flexlm License Manager in the Control Panel:

The Setup tab - In the empty space next to lmgrd.exe type in the path to lmgrd.exe (this should be where avs_lmd.exe is). Do the same for license.dat. (or click on the Browse button and find the file)

The Licenses tab - Make sure that you can pull up your license file by pressing "Show License File" key.

The Control tab - Do not start the License server.

Defining License-related Variables

Complete the steps below to ensure that the license server can locate your license.dat file.

1. Set the LM_LICENSE_FILE environment variable so that it points to your license file.

If you are using multiple license files, LM_LICENSE_FILE should contain all license file names in a colon separated list. For example:

LM_LICENSE_FILE=/usr/local/flexlm/licenses/license.dat:/u2/express/license/avslic.dat

2. Once you have set LM_LICENSE_FILE, run lmstat -a and licdiag to verify that the license-related files are working.

<install-dir>\runtime\bin\<machine type>

Upgrading an Existing AVS/Express License

If you already have an AVS/Express license, but you need to upgrade or update your license information, complete the procedure below. Some situations where this procedure would be necessary are listed below.

• upgrading from a demonstration license to permanent license
• increasing the number of AVS/Express licenses
• changing the license server host machine

1. If you have not yet completed a Change of License request form, do so now.

The Change of License request form is available on the Advanced Visual Systems web page, at http://help.avs.com/licensing/.

2. If the FLEXlm license server is running on your system, type the following command to stop the license server.

lmutil lmdown

3. Upon receiving the license-related information, replace or modify the information in your existing license.dat file with the new information.

4. Restart the FLEXlm license server.

Using a Demonstration License

If you are installing AVS/Express Release 6.2 for only a short time-if, for example, if you are evaluating AVS/Express-you only need to install a temporary demonstration license. Demonstration licenses are node-locked licenses that allow you to use the product for up to 30 days.

1. Contact the local Advanced Visual Systems and obtain the demo license password.

This password is valid for a particular day, so be sure you are prepared to license the product on the day you request the password.

2. On UNIX platforms, run: <install-dir>/express/bin/<machine type>/demo_license
On Windows platforms, run: <install-dir>\runtime\bin\<machine type>\demo_lic

<install-dir> is the name of the directory in which you installed AVS/Express Release 6.2

<machine type> is a string that corresponds to the platform on which you are running. See Supported Platforms for a listing of machine types.

The demo_license program creates a temporary license.dat file in the current directory.

2.3 Linking AVS/Express to the Database Kit

Read this section only if you want to link AVS/Express with the Database Kit. If you are not using the Database Kit, skip this section and go to Starting AVS/Express.

Two files are of particular interest when linking AVS/Express to the Database kit and to the database specific libraries; the express.exe and the config.h files.

• express.exe is the AVS/Express executable. When AVS/Express is installed, this executable is not linked to the database libraries. In order to use the Database kit, you need to use a batch file or a script file to produce an express.exe file that is linked to the database libraries.
• install.sh is the script file that updates your express.exe file if you are running on a UNIX platform.
• go_ora.bat, go_odbc.bat go_db.bat, go_ndb.bat are the batch files that update your express.exe file if you are running on a Windows platform.
• config.h contains configuration information. When you run a batch file or the script file, the config.h file is updated to include database-specific configuration information.

Linking the Database Libraries

CAUTION: When you run any of the batch files or the install.sh script, a new version of express.exe overwrites the existing version. If you want to keep the current version for later use (for example, to revert to it after testing the Database Kit), you must save a copy of the current express.exe by renaming it.

Follow the instructions below to modify your express.exe file so that it is linked with the appropriate database-specific libraries. The necessary files and their locations are identified in the table below.

Table 0-12

File Name	UNIX Directory	Windows Directory
express.exe	<install-dir>/express	<install-dir>\bin\<machine type>
config.h	<install-dir>\include\<machine type>	<install-dir>\include\<machine type>
install.sh	<install-dir>/express/dbkit	Not applicable.
go_ora.bat, go_odbc.bat go_db.bat, go_ndb.bat	Not applicable.	<install-dir>

On UNIX Platforms

1. Log in as root.

2. Set the environment variable XP_ROOT to the <install-dir>/express directory.

3. Type the following command:

$XP_ROOT/db_kit/install.sh

4. Respond to the prompts that are displayed by the script.

When the script completes, your AVS/Express executable will be linked to the database libraries and you will be ready to run AVS/Express with the Database Kit.

On Windows Platforms

Invoke the appropriate batch file.

Table 0-13

Invoke this batch file...	To link express.exe to...
go_ora.bat	Oracle database libraries
go_odbc.bat	ODBC database libraries
go_db.bat	all of the databases libraries listed above
go_ndb.bat	none of the database libraries

When the batch job completes, your AVS/Express executable will be linked to the database libraries and you will be ready to run AVS/Express with the Database Kit.

Linking a Non-supported Database

If you want to link AVS/Express with a non-certified version of a database, you need to modify the corresponding database link line in the <install-dir>/express/include/<machine type>/machinc.mk makefile. This makefile links the database version specified in the machinc.mk makefile to the AVS/Express executable when you install the Database Kit.

2.4 Starting AVS/Express

Use the appropriate platform-specific procedure below to start AVS/Express.

Note: AVS/Express Visualization Edition users must set the following environment variable before using the licdiag utility and before starting AVS/Express.

setenv XP_FEATURE VIZ_EXPRESS

UNIX Platforms

1. Add <install-dir>/express/bin/<machine type> to your search path.

The AVS/Express executable resides in the <install-dir>/express/bin/<machine type> directory.

<machine type> is a string that corresponds to the name of the platform you are running on.

2. Launch AVS/Express using either the express command or the xp shell script (for the Developer Edition) or use the vxp shell script to start the Visualization Developer Edition.

For the Developer edition...

• The express command starts AVS/Express, but it does not set the library path or the XP_FEATURE environment variables.
• The xp shell script, sets the shared library path environment variables, sets the XP_FEATURE environment variable for the licensing of your runtime applications, and calls the express executable.

Note: If the license.dat file is stored somewhere other than in the default directory, you must explicitly tell AVS/Express where to find the license.dat file. Depending on your platform, the default location is either /usr/local/flexlm/licenses/license.dat, or c:\flexlm\license.dat.

Windows Platforms

Either:

Select Start-Programs->AVS Express Collection->AVS Express
or Start-Programs->AVS Express Collection->Viz Express.

Or:

1. Open a command shell.

2. Change to the AVS/Express directory (most likely C:\express).

3. Type start bin\<machine type>\express.

Troubleshooting Errors while Starting AVS/Express

If your system is not properly configured, it is possible that you could receive error messages when you first start AVS/Express. These problems could be a result of an improperly set environment variable, a license server problem, or some other configuration problem. Some of the more commonly errors are described below; whenever possible, a remedy for the problem is also provided.

Locale Database Errors

A locale database is used by AVS/Express' worldwide language support facilities and is required in order to initialize the User Interface Kit. On most systems, Motif and its associated locale support are integrated into the operating system. However, on SunOS 4.1.x, Motif must be obtained from a third-party vendor, and the locale database is, by default, not available on SunOS 4.1.x systems.

If you attempt to start AVS/Express without a valid locale database, the following messages are displayed.

Warning: This version of Xlib does not support locale; using C
Warning: This version of Xlib does not support locale modifiers
Error: Unable to find Locale Database
Error: Try setting XNLSPATH environment variable

If you see these messages, set your XNLSPATH environment variable to the full pathname of the <install-dir>/runtime/sun/nls subdirectory. This should enable you to successfully start AVS/Express.

"Cannot find .v file" Messages

If, while AVS/Express is starting, you notice messages stating "cannot find V files", in particular, the sys.v file, it is possible that the XP_PATH variable was not set correctly.

Typically, you do not need to define the XP_PATH environment variable to run AVS/Express; it is automatically determined and set based on your directory file search path. However, if the current directory (.) is not in your path, AVS/Express can fail to correctly set XP_PATH.

Follow this procedure to solve this problem.

1. Type the following command to determine the value of XP_PATH.

express -version

2. If the path information is incorrect, either explicitly set an XP_PATH environment variable or use the path option when starting AVS/Express as shown below.

express -path "/<path>/express"

The quotation marks around the directory specification are required.