Table of Contents

ArcView GIS 3.2

System requirements for ArcView GIS 3.2

System requirements
DATABASE INTEGRATOR system requirements
Developer Information

International language support

The ArcView^® GIS 3.2 software has maintained the tradition of being a powerful and easy-to-use tool that brings geographic information to your desktop.

New  features of ArcView GIS 3.2 will include:

• Enhanced SDE
• New data readers and converters
• ESRI Data and Maps data updates and new data

• SDTS Point to Arc:  A utility that lets you transfer earth referenced spatial data between different computer platforms and/or software products with the potential for no information loss. This converter generates an ArcInfo point coverage from an SDTS point profile.
• SDTS Raster to Grid:  A utility that lets you transfer earth referenced spatial data between different computer platforms and/or software products with the potential for no information loss. This converter generates a grid from an SDTS raster data set.

• The "What's New in ArcView GIS 3.2" book, provided in the ArcView GIS 3.2 package
• The "What's New" book found in the ArcView GIS 3.2 online help contents page
• $AVHOME/avdocs/newin32.pdf, a PDF file of the hard copy of "What's New in ArcView GIS 3.2" book

• ADRG Image Support
• CADRG Image Support
• CAD Reader
• CIB Image Support
• Database Access
• Dialog Designer
• Geoprocessing
• Graticules and Measured Grids
• IMAGINE Image Support
• JPEG [JFIF] Image Support
• Legend Tool
• MrSID Image Support (Solaris2 only)
• NITF Image Support
• TIFF 6.0 Image Support
• VPF Viewer

• The DBAccess2.pdf file is the User's Guide for the ArcView GIS 3.2 Database Access extension. The dbaccess.readme file contains last-minute information concerning the Database Access extension.
• The shapefile.pdf is the July 1998 version of the white paper containing a technical description of ESRI's shapefile format. This version has been updated with details about the new M and Z shapes.
• The EULA.htm document is the ESRI License Agreement.  To view the ESRI License Agreement in another language, see the PDF files located in the license directory on the CD-ROM.  By accepting the license agreement written in the English language the Licensee acknowledges it has had the opportunity to review the terms in the various languages included in the package.

Sample Scripts and Extensions provided with ArcView GIS 3.2:

Two files, samples.txt and samples.htm, are provided to help users locate and use the sample scripts and extensions that are part of ArcView GIS 3.2. These files are located in the $AVHOME/samples directory. To make use of the samples.txt file, add it as a table into ArcView GIS 3.2. Once the samples.txt file is added as a table, use the Find tool to locate scripts and extensions by keywords. The samples.htm file is similar to the samples.txt file in the HTML format. Open the samples.htm with your Internet browser to learn more about the ArcView GIS samples directory.

Note:    The extensions included with ArcView GIS 3.2 are not licensed; therefore, they do not require licenses to run.

Note:    ArcView GIS 3.2 will NOT work with the ArcView GIS 3.0x keycode. To acquire a new keycode, refer to the keycode form in your ArcView GIS 3.2 package. ArcView GIS 3.1 users will be able to use their same keycodes with ArcView GIS 3.2.

This section provides information about the system requirements for installing and using ArcView GIS on UNIX workstations. It contains information such as the supported operating systems and supported database management systems (DBMS). This information is vital if you are responsible for installing ArcView GIS or configuring UNIX workstations on which ArcView GIS is to be installed. This section is organized by platform and operating system. The following information is presented for each platform:

• Required system environment: Gives details about the operating systems required to run ArcView GIS, required window manager, memory requirement, and swap space.
• DATABASE INTEGRATOR^TM system requirements: Describes the database products and release versions that are supported by ArcView GIS 3.2. These are required to access attribute data in relational DBMSs from ArcView GIS.
• Developer information: Provides the run-time environment information for extension and ArcView Spatial Analyst^TM developers.

System requirements
 

Platform	Operating System	Window Manager	Memory*	Swap Space*
Compaq's DIGITAL UNIX® (now called: Tru64TM)	Compaq's DIGITAL UNIX 4.0D	CDE or Motif®	64 MB	75 MB
HP® 9000/700	HP-UX®  11.0	CDE	32 MB	100 MB
IBM® RS/6000TM	AIX® 4.3.2  (RTE supplied by ESRI)	CDE or AIXWindows®	32 MB	64 MB
SGI	IRIXTM 6.5	Version 6.5	64 MB	100 MB
SunTM SolarisTM 2.x	Solaris 2.6 (SunOS 5.6)	CDE or OpenWindowsTM	32 MB	100 MB

Note: * Memory and swap space are based on a single user. To optimize performance ESRI recommends a minimum of 64 MB of memory and 100 MB of swap space for all platforms.

DATABASE INTEGRATOR system requirements

DATABASE INTEGRATOR software accesses the DBMS through its own networking module (e.g., Oracle's SQL*Net^®). It only requires that the basic DBMS kernel and the networking tools be available from the remote node. All DBMS modules can reside on the server node. The networking implementation of the various DBMS will dictate whether a remote DBMS connection starts a process on the remote node or on the server.
 

Platform	Informix®Online  Dynamic Server	Oracle®	Sybase®	CA-OpenIngres®
Compaq's DIGITAL UNIX (Tru64)	7.30.FC6 9.14.FC6	8.0.4.0.0 8.1.5.0.0 (8i)	Server 11.5.1 Server 11.9.2 Client 11.1.1	1.2/01
HP 9000/700	7.30.UC6 9.16.UC1	8.0.4.0.0	Server 11.5.1 Server 11.9.2 Client 11.1.1	2.0
IBM RS/6000	7.30.UC5 9.16.UC1	8.0.4.0.0 8.1.5.0.0 (8i)	Server 11.9.2 Client 11.1.1	1.2/01
SGI	7.30.UC2 9.16.UC1	8.0.4.2.2	Server 11.5.1 Client 11.1.1	N/A
Solaris 2.x	7.30.UC5 9.16.UC1	8.0.4.0.0 8.1.5.0.0 (8i)	Server 11.5.1 Server 11.9.2 Client 11.1.1	1.2/01

Developer Information

This section is for developers creating extensions (DLL creation) and ArcView Spatial Analyst developers. The following information contains the required C and C++ Compilers for creating extensions and for ArcView Spatial Analyst developers who wish to use the GRID IO libraries to read and write the GRID format.
 
 

Platform	C and C++ Compilers
Compaq's DIGITAL UNIX (Tru64)	DEC C V5.6 and C++ V5.5 for Compaq's DIGITAL UNIX 4.0D
HP 9000/700	B.11.01.01 HP C/ANSI C Developers Bundle and B.11.01.01 HP C++
IBM RS/6000	C for AIX Preprocessor Version 4.3.0.1  C for AIX Compiler Version 3.6.4.2  C Set ++ for AIX Compiler Version 3.6.4.2  C Set ++ AIX RTE Version 3.6.4.2
SGI	ANSI C Compiler Version 7.2.1 and ANSI C++ Compiler Version 7.2.1
Solaris 2.x	SUNWspro 4.2 C Compiler and SUNWspro 4.2 C++ Compiler

Installation instructions

IMPORTANT:    Before you install ArcView GIS 3.2, make sure the system configurations for your machine and the DATABASE INTEGRATOR software you are using are correct. Refer to "System requirements for ArcView GIS 3.2" for details.

ArcView GIS 3.2 comes on two CD-ROM's, on one CD-ROM you will find the install programs for the Compaq's Digital UNIX (Tru64), HPUX, and IBM platforms, on the other CD-ROM you will find the install programs for the SGI and Solaris platforms. Both CD-ROM's include the sample data, acrobat_readers, and 3D Analyst 1.0 Patch directories. Be sure that you have the appropriate CD-ROM before you proceed to install ArcView GIS 3.2.

ESRI highly recommends installing ArcView GIS 3.2 into a new directory.  DO NOT overwrite your existing copy of ArcView GIS. Because of differences in ArcView GIS add-on extension versions, you will need to reinstall additionally purchased extensions after you install ArcView GIS 3.2.  For example, when installing ArcView 3D Analyst^TM 1.0, ArcView Spatial Analyst 1.1, or ArcView Internet Map Server^TM 1.0b extension, the CD-ROM will list two directories, one for ArcView GIS 3.0b and one for ArcView GIS 3.1. When reinstalling the extension be sure to use the version in the ArcView GIS 3.1 directory.

To install ArcView GIS 3.2, insert the CD-ROM for the desired platform into the CD-ROM drive, then become root user (excluding Solaris 2.x and IRIX 6.x):

% su

You will be prompted for your root user password. If you do not know this password, contact your system administrator. If a cdrom directory does not exist, you can create one by using the following command:

# mkdir /cdrom

To mount the CD-ROM, use one of the following based on your installation platform (where <dev> stands for the CD-ROM device):
 

Compaq's DIGITAL UNIX (Tru64)	mount -t cdfs -r -o nodefperm,rrip /<dev> /cdrom
HP 9000/700	mount -F cdfs -r /<dev> /cdrom (or use sam)
IBM RS/6000	mount -v 'cdrfs' -p'' -r'' /<dev> /cdrom (or use smit)
SGI	IRIX 6.x automatically mounts the CD-ROM as /CDROM.
Sun Solaris 2.x	Solaris 2.x includes the Volume ManagementTM software that automatically mounts the CD-ROM.

At this point, the ArcView GIS 3.2 CD-ROM should be mounted. Before installing the software, exit root user mode:

# exit

The "install" command has four options from which to select:
Usage: install <-help | -load | -remove | -verify | -lmhostid>

Type "install -help" to read more about the installation procedure.

To start the ArcView GIS CD-ROM installation, type one of the following based on your installation platform.
 

Compaq's DIGITAL UNIX (Tru64)	/cdrom/digunix/install -load
HP 9000/700	/cdrom/hpux/install -load
IBM RS/6000	/cdrom/ibm/install -load
SGI	/CDROM/sgi/install -load
Solaris 2.x	/cdrom/cdrom0/solaris/install -load

This starts the dialog for the menu driven installation procedure. Default selections are noted in brackets [ ]. To obtain a list of options or online help, type "?" at any prompt.  You can quit the installation procedure at any time by typing "quit" or "q".  To return to a previous question, type a caret "^".

Note:    The path name you specify as the ArcView GIS installation directory cannot contain any uppercase letters.

You cannot accept the default CD-ROM mount point when installing ArcView GIS 3.2.

The CD-ROM mount point should read as follows:

/cdrom/<platform>
/cdrom/cdrom0/solaris (Solaris 2.x only)

The sample data is a direct copy from the CD-ROM. The sample data is located at: /cdrom/av32data

The av32data directory contains two main data directories, the avtutor and the esridata directories. The avtutor directory includes the ArcView GIS 3.2 and Database Access 2.0 tutorial data, and the esridata directory includes sample data provided by ESRI. The data has been structured in this fashion to provide a choice in the amount of data that gets loaded on particular machines.

Setting up your account

The HOME environment variable ($HOME) must be set to a writable directory. When you start ArcView GIS, a warning message will appear if the HOME environment variable is not set.

Setting the TMPDIR variable

The TMPDIR environment variable ($TMPDIR) must be set to a writable directory. The TMPDIR environment variable is optional and only needs to be set if the you want to write temporary files in a location other that the /tmp directory.

Setting the AVHOME variable

The user account that will start the license manager must have the AVHOME variable set.

% setenv AVHOME /<arcview3_install_directory>/arcview3

To use ArcView GIS on all UNIX platforms, add one of the following lines to your .cshrc file:
alias arcview '/<arcview3_install_directory>/arcview3/bin/arcview \!* &'
or
alias arcview '$AVHOME/bin/arcview \!* &'
or add /<arcview3_install_directory>/arcview3/bin/ to your path.

Note:    Adding the "\!*" in the arcview alias allows the user to load a project file directly using the alias. The "&" allows you to run the process in the background.  If you add arcview3/bin to your path, you don't need to set the alias.

To use the IMPORT, MIF to Shape utility, or the SDTS converters, add the following to your .cshrc file:

alias import $AVHOME/bin/import
alias mifshape $AVHOME/bin/mifshape
alias sdtsp2a $AVHOME/bin/sdtspoint2arc    (Solaris Only)
alias sdtsr2g $AVHOME/bin/sdtsraster2grid   (Solaris Only)

Setting the LIBRARY PATH variable

All UNIX platforms need to set the LIBRARY PATH to include the ArcView GIS lib directory:

Compaq's DIGITAL UNIX (Tru64)
setenv LD_LIBRARY_PATH $AVHOME/lib:/usr/shlib

HP 9000/700
setenv SHLIB_PATH $AVHOME/lib

IBM RS/6000
setenv LIBPATH $AVHOME/lib:/usr/lib:/lib

SGI
setenv LD_LIBRARY_PATH $AVHOME/lib:/usr/lib:/lib

Solaris 2.x
setenv LD_LIBRARY_PATH $AVHOME/lib:/usr/lib:/usr/openwin/lib:/usr/ucblib
 

Setting the AVDATA variable

To use the projects provided with the sample data (esridata), you need to have the AVDATA variable set:

setenv AVDATA <esridata_install_directory>/esridata
 

Then, at the UNIX prompt,

% source .cshrc
 

Note:    You cannot start ArcView GIS until the license manager is running.

Installing ArcView GIS software license manager

The user account that will start the license manager must have the AVHOME variable set.

% setenv AVHOME /<arcview3_install_directory>/arcview3

For a detailed discussion of the license manager, refer to the "License Manager's Guide," which has been provided in PDF format. The license_managers_guide.pdf is located in the $AVHOME/avdocs directory.  See section "ArcView GIS 3.2" for details on using or obtaining the Adobe Acrobat Reader.

The license manager software is distributed with ArcView GIS. It can be found in the $AVHOME/sysgen directory:

• ESRI - the ArcView GIS application daemon
• lmgrd - the license manager daemon
• sample.dat - a sample license file
• lmutil - the license manager executable
• adminlicense - a utility to edit and verify the license file

• lmdown - shuts down the license and application daemon
• lmhostid - returns the FLEXlm hostid of a workstation
• lmremove - removes specific licenses
• lmreread - informs the license daemon of changes in the license file
• lmstat - reports on the status of the daemons and the license uses

• verify -verifies the contents of your license.dat file.
• convert -converts the old time-out dates (31-dec-99) in the license file to the correct no time-out date (1-jan-00).
• help -displays help for the ADMINLICENSE utility.

SERVER siddhartha 5500439b 1700
DAEMON ESRI $AVHOME/sysgen/ESRI
FEATURE ArcView ESRI 1.000 01-jan-00 500 EB068051E3BC56840630 ""
FEATURE ArcView3  ESRI 1.000 01-jan-00 500 1BD640A110179BDD9C28 ""
FEATURE ArcView31 ESRI 1.000 01-jan-00 500 1ED640B116179BDC9C54""
FEATURE AVSpatial1 ESRI 1.000 01-jan-00 500 2B06C01197F91E30C586 ""
FEATURE AVNetwork1 ESRI 1.000 01-jan-00 500 EB061091563BDF2F6D05 ""

The first line identifies the name and FLEXlm^® hostid of the workstation (in this case, siddhartha) on your network that will be the server for the license manager (the node from which the license manager daemons will run).  The second line identifies the license daemon for ArcView GIS and its location.  The following lines specify the software or features that are to be licensed, the name of the daemon that manages the licenses (ESRI), the application daemon version (1.000), the time-out date for the software (01-jan-00), the number of users (500), and a keycode for the product. Each line is called a FEATURE line.

Note:    Even though you're installing ArcView GIS 3.2, the feature line used will be ArcView31 and the application daemon will still read 1.000.

Note:    ArcView GIS 3.2 will not require a new keycode if you have an ArcView GIS 3.1 keycode; however, ArcView GIS 3.2 will not work with an ArcView GIS 3.0x keycode. To acquire a new keycode, also referred to as a feature line in the license file, refer to the keycode form in your ArcView GIS 3.2 package.

To obtain the license file for your site
To obtain the license file, you will need to provide the hostname and FLEXlm^® hostid of each workstation or server that will be running the license manager to ESRI or your distributor. The hostname of a workstation is obtained with the command:

% hostname

% $AVHOME/sysgen/lmutil lmhostid

• Complete the keycode request form included in your installation package. Keycode Support will also send, upon request, a keycode request form by E-mail.

• Mail, fax, or E-mail the completed form to Keycode Support.

Fax number: 909-335-1716
E-mail address: keycodes@esri.com

Contact your local ESRI^® software distributor for keycode information. ESRI in Redlands cannot respond to requests for keycodes received directly from international users.

Installing the license file

% cd $AVHOME/sysgen
% ./adminlicense
 

Starting the ArcView GIS software license manager for new users

This section describes the steps a new (non-ArcInfo^TM) user needs to go through to set up the ArcView GIS 3.2 license manager and the .cshrc environment.

The following instructions show you how to start the license manager interactively.

You should run the license manager as root or as the owner of the ArcView GIS installation directory. To start the license manager, become root user:

% su
# cd $AVHOME/sysgen
# ./lmgrd -c license.dat > /dev/console &

If you encounter an error, refer to the "License Manager's Guide" for a possible explanation.

 Note:    If you want the license manager to automatically start when rebooting the system, follow the directions outlined in the $AVHOME/sysgen/license.boot file.

To check the status of the license manager, use the following command in the $AVHOME/sysgen directory:

./lmutil lmstat -a -c license.dat

Once the license manager is running, you will need to set up the user account to run ArcView GIS. See "Setting up your account" for further details.

License manager setup procedures for existing ArcView GIS users

At ArcView GIS 3.2, ESRI is using a new version of the Flexible License Manager, FLEXlm Version 6.1f. ArcView GIS 3.2 will not work with the license manager distributed with previous versions of ArcInfo and/or ArcView GIS. You will need to restart the license manager with the new version of the daemons and executables. To do this, first become root user:

% su

1.  The easiest method for installing ArcView GIS 3.2 is to install the software to a new location. If you choose to install to the existing ArcView GIS location, remove the current arcview3 directory. Before installing, shut down the license manager. To shut down the license manager you must be the root user or the owner of the lmgrd process.

% cd $AVHOME/sysgen
% ./lmutil lmdown -c license.dat

2. Setting up your .cshrc file.

The .cshrc file contains UNIX environment settings for your user account. This file is located in the user's $HOME directory.  How you set up the .cshrc file depends on the method of installation you used.  If you have already been using a version of ArcView GIS, and installed to the same location, you will not need to make any changes in the .cshrc file. At this point you may start the license manager.

If you had been using ArcView GIS 2.x prior to installing ArcView GIS 3.2 or changed the location of the installation, you will want to set up your .cshrc file as described in "Setting up your account."

3. Starting the license manager.

 Start the license manager as described in  "Starting the ArcView GIS software license manager for new users" for further details.

Back to TOC

License manager setup procedure for existing ArcInfo users

1. Modify the existing license.dat file in the $ARCHOME/sysgen directory.

a. Change the DAEMON line to the following:

DAEMON ESRI $AVHOME/sysgen/ESRI

or use the absolute path to the /arcview3/sysgen directory.

DAEMON ESRI /<path_to_install_directory>/arcview3/sysgen/ESRI

Note:    ArcView GIS 3.2 installs and uses FLEXlm version 6.1f. While the prior version of FLEXlm shipped with ArcInfo 7.2.x (FLEXlm 6.0b) will recognize the ArcView31 feature line, ESRI recommends the use of FLEXlm version 6.1f with ArcView GIS 3.2. The FLEXlm versions prior to FLEXlm 6.0b will NOT recognize the ArcView31 feature line.

b. Add the new ArcView GIS feature lines to the existing license.dat file located in your $ARCHOME/sysgen directory.  Make sure the feature lines are  entered exactly as shown on the license.dat file from the keycode department.  The following is a sample line.

           Feature    Version   Expires  #licenses  Encryption string
          --------      -----  ---------   --    --------------------
FEATURE   ArcView31 ESRI 1.000  01-jan-00   50    6B5E20C1E1F85296E0 ""

Note:    The encryption string uses zeros(0) and ones(1). Uppercase O's and L's along with lowercase l's are not used. The only valid characters are 0 -> 9 and A -> F.

2.  Copy the license.dat file to the $AVHOME/sysgen directory.  You will need write permission to the $AVHOME/sysgen directory to do this.

 % cp $ARCHOME/sysgen/license.dat $AVHOME/sysgen/license.dat

You may also use the absolute path to the license.dat file, if the $ARCHOME and $AVHOME variables are not set.

3.  Shutting down and restarting the license manager.

Shut down the license manager if it is currently running.  Use the "ps" command from the UNIX prompt to determine the status of the license manager.  The following is an example. The usage may vary among operating systems. Refer to the man pages for the usage on your specific operating system.

% ps -ef |grep lmgrd
root  217  0.0  0.2 1380  324 ?  S  June 22  2:33 ./lmgrd -c license.dat

Navigate to the $ARCHOME/sysgen directory (the sysgen directory where the original license manager was started) and use the lmdown option of the lmutil command.  For this command to work, you will need to be logged in as the owner of the lmgrd process.

% ./lmutil lmdown -c license.dat

Start the license manager to initialize the updated license.dat file. Change your directory to the $AVHOME/sysgen directory and start the license manager with the following command.

% ./lmgrd -c license.dat &

If you encounter an error, refer to the "License Manager's Guide" for a possible explanation.

Note:    If you want the license manager to automatically start when rebooting the system, follow the directions outlined in the $AVHOME/sysgen/license.boot file.

4.  Preparing the user environment for execution of ArcView GIS 3.2.

Before ArcView GIS 3.2 can be used, environment variables must be set in the user's .login or .cshrc file. If no other versions of ArcView GIS are being used, add the following lines to the .login or .cshrc file. Eliminate any references to other versions of ArcView GIS.

setenv AVHOME /<path_to_install_directory>/arcview3
setenv LD_LIBRARY_PATH $AVHOME/lib (Note: This variable varies by platform. Refer to "Setting up your account.")

If you are using ArcInfo, you should already have an LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH.  Add $AVHOME/lib to this path.  Make sure that the AVHOME variable is set in a line prior to the library path variable, or use the direct path to the /arcview3/lib directory.

If you are using ArcInfo you should have one all-inclusive library path set for ArcView GIS and ArcInfo. Before starting ArcView GIS, you will need to ensure that the appropriate environment has been set.

To start ArcView GIS

Before starting ArcView GIS, you will need to ensure that the appropriate environment has been set.
Start ArcView GIS as the root user or owner of the arcview3 directory by typing in the alias set in the .cshrc file.

% arcview

If everything is correct, you should see a prompt for the ArcView GIS registration number.

Registration number

When ArcView GIS is started for the first time, you will be asked for a registration number. It is important that the user/account who installed the software starts ArcView GIS and keys in the registration number. Once this is done, other users will then be able to access ArcView GIS without having to type in this number repeatedly.  The registration number is printed on the ESRI registration form.  Please fill out your ArcView GIS registration card and return it to ESRI as soon as possible.  This will ensure that you will receive the following benefits:
 

• Discounts on software updates
• Complimentary subscription to ARC News^TM
• Special software announcements

Where to start

ArcView GIS comes with an online help system, sample data, and projects to help you learn the software. Start Help by selecting "How to Get Help" from the "Help" pulldown menu.

ArcView GIS online help

ArcView GIS Help provides references and how-to information along with a powerful and new search utility. A list of frequently asked questions (FAQ's) can also be found by searching Help for "FAQ".

The ArcView GIS 3.2 installation program installs a new arcview.cnt file. The new arcview.cnt file will overwrite the existing (ArcView GIS) arcview.cnt file if ArcView GIS 3.2 is installed in that existing ArcView GIS location. If you have previously made any edits to your arcview.cnt file, those edits will need to be added to the new arcview.cnt file.

Note:    The help directory for ArcView GIS 3.2 contains several <extension>.hlp files that are not part of the ArcView GIS 3.2 release (for example, threedx.hlp and inetmap.hlp). These files serve as placeholders for future extension products and are included now to build the "full text search index" correctly. Do not delete these placeholder files.

Using ArcView GIS on a network

Accessing data on a PC LAN server from a UNIX workstation

Accessing 6.x/7.x ArcInfo format data on a PC LAN server from a UNIX workstation

Accessing data on a Windows NT workstation or server from a UNIX workstation

Accessing data on a Mac^® server from a UNIX workstation

Information about the networking products mentioned above can be obtained from their respective Web sites.
 

• NetWare NFS Services from Novell         www.intranetware.com
• ENS for UNIX from Banyan                     www.banyan.com
• NFS Maestro Server from Hummingbird      www.hummingbird.com
• UNIX Link 97 from NetManage               www.netmanage.com
• Soltice NFS Server from Sun                    www.sun.com
• Partner from IPT                                       www.iptech.com

Troubleshooting the installation

% arcview:
Command not found

This indicates that something with the $AVHOME variable or alias is not correct.  Make sure the user has read access to the directory where ArcView GIS 3.2 and all of its subdirectories have been installed.  You may also try going to $AVHOME/bin directory and typing "./arcview".

% arcview
ld.so.1: /<path_to_install_directory>/arcview3/bin/arcview: fatal: libaicore.so: can't open file: errno=2
killed

This suggests that the LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH variable (depending on your operating system) is not set correctly.

Note:    The UNIX "env" command can be helpful in determining which UNIX variables are currently set.

Common license manager installation problems

Refer to Appendix B of the "License Manager's Guide" that is included in your ArcView GIS 3.2 package or the license_managers_guide.pdf located in the $AVHOME/avdocs directory.

Questions and feedback

The ArcView GIS 3.2 online help provides frequently asked questions and troubleshooting topics for the ArcView GIS 3.2 software. After completing the installation, search the Help Topics index for "frequently asked questions". ArcView GIS Help provides detailed information on how to contact ESRI Technical Support with any of your questions or comments. You can access this information from the Help Contents page by opening "Need more help", then "Obtaining technical support".

All questions and comments should be forwarded to ESRI Technical Support.

Sources for additional information

In your use of ArcView GIS 3.2, you may find the need for additional information about using the software. Answers to the most frequently asked questions and up-to-date tips can be found in one or more of the resources described below.

Desktop Support Services pamphlet

Subscribe to ESRI's World Wide Web-based discussion forum list ARCVIEW-L

Visit the ESRI home page on the Internet

You may also search or browse ArcView GIS and Avenue FAQs at www.esri.com/software/arcview/faq.html. Our site also offers an Internet Relay Chat (IRC) server. Our chat server will allow you to network with other ArcView GIS users and participate in scheduled "online conferences," all in real time.  The chat server is available at www.esri.com/chat.

Setting up the printing and plotting environment

This section provides information about setting up the printing and plotting environment for ArcView GIS 3.2 on UNIX computers. It contains information such as the printing variables and setting up and customizing the plot system. This information is vital if you are responsible for setting up the printing/plotting environment on UNIX workstations on which ArcView GIS is to be installed. This section is organized by platform and operating system. The following information is presented for each platform: local plotter configuration, remote plotter configuration, and creating spooling directories.

ArcView GIS uses two environment variables to construct the print command it sends to the operating system: PRINTER and PRINT_CMD. The default values of these variables are as follows:
 

The print command ArcView GIS sends to the operating system is:

$PRINT_CMD$PRINTER file

To customize the ArcView GIS printing environment, set these two variables in the .cshrc file.  The PRINTER variable requires the name of the printer only if it is named something other than "lp".  Change the options of "lp" or "lpr" to customize the PRINT_CMD.  Refer to the operating system "man" pages for more information on these options.

setenv PRINT_CMD <see chart>
setenv PRINTER <desired_printer>

Note:    In the Print Dialog box, the user will see the name of the printer defined by the PRINTER variable.

/tmp directory

When you print a layout or a view document directly to the printer, the tmp directory gets populated with files /tmp/tempx.ps or /tmp/tempx.cgm. Make sure to clean up the tmp directory periodically.

For information on how to print a help topic from ArcView GIS 3.2, search the ArcView online help index for "configuring HyperHelp for printing".

Setting up and customizing the plot system

Compaq's DIGITAL UNIX (Tru64) Workstations

The plot system installation proceeds in two steps:

Step 1.  Build the /etc/printcap file.
Step 2.  Create the spooling directories. Each workstation needs a local /etc/printcap file that identifies the printers/plotters locally attached or remotely available over the network.

Each entry in the /etc/printcap file must identify the local or remote spooling queue for the printer/plotter, the local serial port or remote node to which the plotter is physically attached, and the spooling directory. You must have root privileges to edit the /etc/printcap file.

Local plotter

The syntax of the /etc/printcap file uses a colon (:) as an element separator and the backslash (\) as a continuation character.  The format of the /etc/printcap file for a local plotter is as follows:

<queue_name>:\
:lp=<device>:sd=<spool_dir>:br#<rate>:sh:sf:\
:ms=<communication_parameters>:

where
<queue_name>-identifies the name of the spooling queue.

lp=<device>-identifies the name of the serial port, or the logical device on the local node to which the plotter is attached (e.g., /dev/tty01).

sd=<spool_dir>-identifies the spooling directory. This directory should be able to accommodate potentially large files. It should be located under /usr/spool and can be given any name.

br#<rate> -the baud rate for communication over the serial port with the plotter. Valid baud rates are 19200, 9600, 4800, 2400, and 1200.

sh:sf:-these parameters suppress the printing of the burst page header and the form feeds, respectively. They must be included when plotting graphical data.

ms=<communication_parameters>-configures the serial port communication with the plotter.

The possible configurations are listed below.

configuration: 8 data bits, no parity, xon/xoff
ms=cs8,-parenb,-opost,-echo,ixon,-istrip:

configuration: 7 data bits, even parity, xon/xoff
ms=cs7,parenb,-parodd,-opost,-echo,ixon,-istrip:

configuration: 7 data bits, odd parity, xon/xoff
ms=cs7,parenb,parodd,-opost,-echo,ixon,-istrip:

A sample printcap file for local plotters is provided:

# SAMPLE PRINTCAP FILE FOR NODE MARS
#
# This is a sample /etc/printcap file for a Compaq's DIGITAL UNIX (Tru64) Alpha
# workstation. It contains 2 entries for the following
# configurations:
#
#cal5912: Queue for the CalComp 5912 plotter on a
# Compaq's DIGITAL UNIX (Tru64) Alpha machine. Graphics files are
# converted to CalComp format prior to being
# sent to the plotter.
#
#cal5800: Queue for a CalComp 58xx on a Compaq's DIGITAL UNIX (Tru64) Alpha machine.
#
cal5912:\
:lp=/dev/tty01:sd=/usr/spool/cal5912:br#9600:sh:sf:\
:ms=cs8,-parenb,-opost,-echo,ixon, istrip:
#
cal5800:\
:lp=/dev/tty01:sd=/usr/spool/cal5800:br#9600:sh:sf:\
:ms=cs8,-parenb,-opost,-echo,ixon,-istrip:

Remote plotter

Use the following format to define a spooling queue for a plotter or printer located on a remote node.

<queue_name>:\
:lp=:rm=<remote_node>:rp=<remote_queue>:sd=<spool_dir>:

lp = is the logical device, which is left blank because the plotter is located on a remote node.

rm = <remote_node> identifies the remote node on the network to which the plotter is physically attached.

rp = <remote_queue> identifies the name of the spooling queue in the /etc/printcap file on the remote node. For the sake of simplicity, a given spooling queue should be referred to by the same name on all nodes.

You will need to add an entry in the /etc/printcap file for each plotter and printer that you will need to access with ArcView GIS 3.2.

A sample printcap file for remote plotters is provided:

# SAMPLE PRINTCAP FILE FOR NODE VENUS
# This is a sample /etc/printcap file.
# A CalComp 5912 plotter is connected to a remote workstation
# named MARS. The queue name for the plotter on the remote node
# is cal5912. The same queue name should be used.
#cal5912:\:lp=:rm=mars:rp=cal5912:sd=/usr/spool/cal5912:

Though not specified in the /etc/printcap file, the number of data bits (8), parity (None), number of stop bits (1), and protocol (XON/XOFF) are already set up on the system as the default parameters for tty serial ports and do not require additional setup. Make sure to set up the communication parameters for the printer or plotter to exactly match those used for tty serial port system default parameters, and set up the baud rate as specified in the /etc/printcap file.

Note:    Set the baud rate to the printer's or plotter's maximum for best performance. Then set up the printer or plotter for 8 data bits, no parity, 1 stop bit, and XON/XOFF protocol.

Spooling directories

The spooling directories associated with each spooling queue must be created before you use the spooling system. You must have root privileges to create the spooling directories, which you could create under /usr/spool. There must be one spooling directory for each spooling queue in the /etc/printcap file. There is a symbolic link between /usr/spool and /usr/var/spool.

Hewlett-Packard 9000 Series 700/8x7 Workstations

Creating the spooling queue

To use the spooling system, the built-in RS-232, and the MUX ports, configure the port to which the plotter is attached as the spooling queue device.

You will need to be logged in as root on the node to which the plotter is attached (in this example, mars) to configure the ports. You can do this either by logging in as root on mars or by logging in under another user name on mars and then typing "su":

mars% su

The command "sam" is used to configure the serial ports. To invoke the "sam" command, type

mars% sam

This will bring up an HP-UX interactive program. The following examples are taken from the HP System Administration Manager (SAM) using HP-UX 10.20.

Configuring a local printer/plotter

Select "Printers and Plotters" then "LP Spooler," then "Printers and Plotters".  From the "Actions" menu, select "Add Local Printer/Plotter" then "Add Serial (RS-232) Printer/Plotter" or "Add Parallel Printer/Plotter".  Select the available interface card from the popup menu, then click OK.  Your screen should then display the following:

Printer Name: ______
Printer Model/Interface: ______
Printer Class: ______ (optional)
Default Request Priority:
Make This Printer the Default Destination (button)

Printer Name: the name of the spooling queue.

Printer Model/Interface: choose your printer model if listed, or choose "dumbplot".  For PostScript^® printers choose PostScript.

Printer Class: the name of a group of printers (optional).

Default Request Priority: default is 0.

Make This Printer the Default Destination: tells whether the spooling queue will be used for printing if no queue is specified with the HP-UX command "lp".  For plotting queues, this should not be depressed.

The following is a sample configuration for the spooling queue "cal5912":

Printer name: cal5912
Printer Model/Interface: dumbplot
Printer Class:
Default Request Priority: 0

Configuring a remote printer/plotter

Select "Printers and Plotters" then "LP Spooler", then "Printers and Plotters".  From the Actions menu, select "Add Remote Printer/Plotter".  Your screen should then display:

Printer Name: ______
Remote System Name: ______
Remote Printer Name: ______
Remote Printer is on a BSD System (button)
Remote Cancel Model: ______
Remote Status Model: ______
Default Request Priority:
Allow Anyone to Cancel a Request (button)
Make This Printer the Default Destination (button)

Printer Name: the name of the spooling queue.

Remote System Name: the name of the remote node to which the printer/plotter is physically attached.

Remote Printer Name: the name of the spooling queue on the remote node.

Remote Cancel Model: default is "rcmodel".

Remote Status Model: default is "rsmodel".

The following is a sample configuration for the spooling queue "cal5912". The plotter is connected to a remote workstation named "peregrine". The spooling queue on the remote node is "calcomp".

Printer Name: cal5912
Remote System Name: peregrine
Remote Printer Name: calcomp
Remote Cancel Model: rcmodel
Remote Status Model: rsmodel
Allow Anyone to Cancel a Request
Remote Printer is on a BSD System

IBM RISC System/6000 Workstations and Servers

Creating a spooling queue and a spooling directory

Printing or plotting can be accomplished by using local or remote spooling queues. These spooling queues identify the printers and plotters that are locally attached or remotely available over a network. Each local or remote spooling queue identifies the printer's or plotter's local serial or parallel port, or the remote node to which the plotter is physically attached, and the spooling directory.

Local printer/plotter

Use the system administration utility "smit" to create a spooling queue for a local printer or plotter. A menu-driven utility, it can be invoked both from the terminal environment and from the X Windows environment. To create spooling queues, you must define the port that will be used, create the spooling queue, and assign the spooling queue to the port.

The steps required in creating a spooling queue are as follows:

Step 1.  Adding a printer/plotter attached to a serial port.
Step 2.  Adding a printer/plotter attached to a parallel port.

Because creating spooling queues will change system files and parameters, you must be logged in as root user to invoke "smit".

Adding a printer/plotter attached to a serial port

The steps for adding a plotter attached to a serial port are the same for AIX versions 4.1.5.0, 4.2.1.0, and 4.3.0.0.  To add a printer or plotter attached to a serial port on your system, first become root by typing "su" at the system prompt:

% su
# smit&

System Management menu: select Devices -> Printer/Plotter -> Printer/Plotter Devices -> Add a Printer/Plotter.

Printer/Plotter Type menu: select your plotter model if listed. If your plotter is not listed, select osp Other serial printer.

Printer/Plotter Interface menu: select rs232.

Parent Adapter menu: select sa0 (port 1) or sa1 (port 2).

A summary list will then be displayed. You must choose a port number from the options under this list. A finished example might look like this:

Printer/Plotter Type osp
Printer/Plotter Interface: rs232
Description: Other serial printer
Parent adapter: sa0
PORT number: s1
BAUD rate: 9600
PARITY: none
BITS per character: 8
Number of STOP BITS: 1
XON/XOFF handshaking: yes

When this menu is completed, press "do".  You should get a message that says tty0 or tty1 is available. If you are successful in getting this message, proceed to "Adding a virtual printer".

Note:    If you are unable to add the plotter, it may be because the device is already defined. You can modify the already defined device (tty), remove the device and re-create it, or choose another device.

Set your baud rate for serial communications to the printer's or plotter's maximum. You must match the operating parameters of your printer or plotter exactly with those of the serial port. To run the serial port successfully may require some operating system patches. Please call IBM at 1-800-237-5511 to report problems and to obtain necessary communications patches.

Adding a printer/plotter attached to a parallel port

The steps for adding a plotter attached to a parallel port are the same for AIX versions 4.1.5.0, 4.2.1.0, and 4.3.0.0.  To add a local printer or plotter attached to a parallel port on your system, first become root by typing "su" at the system prompt:

% su
# smit&

System Management menu: select Devices -> Printer/Plotter -> Printer/Plotter Devices -> Add a Printer/Plotter.

Printer/Plotter Type menu: select your plotter model if listed. If your plotter is not listed, select opp Other parallel plotter.

Printer/Plotter Interface menu: select parallel.

Parent Adapter menu: select ppa0.

A summary list will then be displayed. You must choose a port number from the options under this list. A finished example might look like this:

Printer/Plotter Type: opp
Printer/Plotter Interface: parallel
Description: Other parallel printer
Parent adapter: ppa0
PORT number: p
Type of PARALLEL INTERFACE: standard
Printer TIME OUT period: 60
STATE to be configured at boot time: available

Most of the parameters not listed in the examples, especially those referenced only when the printer or plotter is not used with a spooling queue or those not used by the printer or plotter, can remain at a default setting.

When this menu is completed, press "do". You should get a message that says lp0 or lp1 is available. If you get this message, proceed to "Adding a virtual printer".

Note:    You must match the operating parameters of your printer or plotter exactly with those of the parallel port.  To run the parallel port successfully may require some operating system patches. Please call IBM at 1-800-237-5511 to report problems and to obtain necessary communications patches.

Adding a virtual printer/plotter-Queue daemon

There is no need to add a virtual printer as a separate step when using AIX 4.1.5.0, 4.2.1.0, or 4.3.0.0.  These virtual printers are created automatically when you add a print queue for a local or remote printer or plotter.

Make sure that the qdaemon is running by issuing the command:

# ps -ef | grep qdaemon
root 118998 1320 0 Nov 28 - 0:00 /etc/qdaemon

Use the following command to start the queue daemon, if necessary:

# startsrc -s qdaemon

Adding a print queue

Now configure a local spooling queue using "smit" fastpaths. Log in as root and issue the following:

# smit rq

Once in the "Print Spooling" menu, select "Add a Print Queue". You are then asked to tell the system how your plotter is attached and what type of plotter is being used. Make the appropriate selection.  The following is an example of the steps to perform in creating a local spooling queue "new_queue" for a Hewlett-Packard model hp755 color PostScript plotter.

Attachment Type: Select remote for printer attached to remote host

Attachment Type: Select local for printer attached to local host

Printer Type:  Hewlett-Packard

Printer Type:  Other (Select this if your printer type is not listed)

Printer Type:  generic  Generic Printer

Printer Interface:  parallel     (NOTE:  Serial communications use rs232)

Parent Adapter:  ppa0 Available 00-00-0P Standard I/O Parallel Port Adapter

This puts you in a menu where you may set queue characteristics. Characteristics that require an answer have asterisks at the start of the line. When the menu comes up to add a print queue, the only entry you need to worry about for this example is PostScript.  Therefore, fill in the entry field for PostScript with a name, e.g. "new_queue" and hit <cr>.

Names of NEW print queues to add
     ASCII                            []
     GL Emulation                     []
     PCL Emulation                    []
     PostScript                       [new_queue]

When this parameter is set, press "done" to configure the local spooling queue.  Exit "smit".  This newly created local queue has been established for sending PostScript data to a Hewlett-Packard hp755 plotter via a parallel communication port.

Note:    The other print queues above, ASCII, GL Emulation, and PCL Emulation, will be used with either serial or parallel communications for the following cases:

            ASCII              - ASCII (text) data
            GL Emulation   - All other printer graphic language data other than PCL or PostScript, i.e. CHCBS, HPGL-2, etc
            PCL Emulation - PCL data
            PostScript         - PostScript data

Now start the "new_queue" queue using "smit" fastpaths:

# smit qstart

This brings up the Start a Print queue menu. Enter "new_queue" and press "do". Exit "smit".

Remote printer/plotter

To plot from a local node to a plotter attached to a remote node, you must create a remote spooling queue. A local spooling queue must already be defined on the node to which the plotter is attached.

In the following example, the remote node is "hotshot" and the local node is "coolcat".  The remote node must be able to authorize spooling requests from other nodes. As root, edit the /etc/hosts.lpd file on "hotshot" and add the names of the nodes that will be submitting spooling requests (in this case, "coolcat"). The lpd daemon must be restarted for the changes to take effect. If the lpd daemon is running, kill it and restart it.

The following commands will check to determine the daemon's PID and then kill the daemon:

# ps -ef | grep lpd
root 16873 15350 1 09:17:29 pts/4 0:00 grep lpd
root 15678 2397 0 08:23:45 - 0:00 /usr/lpd/lpd

# kill -9 15678

The following command will start the daemon:

# startsrc -s lpd

"Hotshot" is now ready to accept remote spooling requests.

Now configure a remote spooling queue on "coolcat" using "smit" fastpaths. Log in as root on "coolcat" and issue the following:

# smit rq

Once in the "Print Spooling" menu, select "Add a Print Queue". You are then asked to tell the system how your plotter is attached. Make the appropriate selection.

Attachment Type: Select remote for printer attached to remote host

You are then asked to specify the type of remote printing. Make the appropriate selection.

Type of Remote Printing: Standard processing

This puts you in a menu where you may set queue characteristics. Characteristics that require an answer have asterisks at the start of the line.

NAME of queue to add: create a queue name.

HOSTNAME for remote jobs: the name of the node that has the plotter attached to it. For an example, we will use "hotshot".

NAME of the queue on the remote server: enter the name of the plotter spooling queue on the host node, here "new_queue".

TYPE of print spooler on remote server for queue status output: if the host node is another IBM RISC System/6000, this field does not need to be edited. If the host node is a UNIX BSD-based system, such as a Sun Workstation, enter the following:

BSD

If the hostname node is a UNIX System V based system, such as Sun Solaris 2 workstation, enter the following:

System V

DESCRIPTION of printer on remote server is optional.

Example:
* NAME of queue to add new_queue
* HOSTNAME of remote server hotshot
* Name of QUEUE on remote server new_queue
Type of print spooler on remote server AIX Version 3 or 4

DESCRIPTION of printer on remote server Hewlett-Packard HP755 Color Printer

When these parameters are set, press "done" to configure the remote spooling queue.  Exit "smit".  Now start the queue using "smit" fastpaths:

# smit qstart

This brings up the Start a Print queue menu. Enter "new_queue" and press "do".  Exit "smit".

Verifying the plotter connection

Verify that your plotter is connected to the correct port on the workstation and that the communication parameters of your plotter match the settings on the port. If your plotter is connected via Ethernet, be sure to check that the plotter is accessible over the network.

SiliconGraphics^® Workstations

Building the /etc/printcap file and creating the spooling directories

Each workstation has a local /etc/printcap file that identifies the printers and plotters locally attached or remotely available over the network. Each entry in the /etc/printcap file must identify the plotter's spooling directory, spooling queue, and the port (serial or parallel).

Local plotter

The syntax of the /etc/printcap file uses a colon (:) as an element separator and the backslash (\) as a continuation character. The format of the /etc/printcap file for a local plotter is as follows:

<queue_name>:\
:lp=<device>:sd=<spool_dir>:br#<rate>:\
:ms=<communication_parameters:\
:sh:sf:

<queue_name> identifies the name of the spooling queue.

lp = <device> identifies the name of the serial port, parallel port, or the logical device on the local node to which the plotter is attached (e.g., /dev/ttyd2, /dev/plp).

sd = <spool_dir> identifies the spooling directory.  This directory should be able to accommodate large files. It should be located under /usr/spool and can be given any name.

br#<rate> is the baud rate for communication over the serial port with the plotter. Valid baud rates are 19200, 9600, 4800, 2400, and 1200.

ms = <communication_parameters> configures the serial port communication with the plotter.  The possible configurations are listed below:

configuration: 8 data bits, no parity
ms = cs8,-parenb,-opost,-echo,ixon,-istrip:

configuration: 7 data bits, even parity
ms = cs7,parenb,-parodd,-opost,-echo,ixon,-istrip:

configuration: 7 data bits, odd parity
ms = cs7,parenb,parodd,-opost,-echo,ixon,-istrip:

sh:sf: suppresses the printing of the burst page header and the form feeds, respectively. They must be included when plotting graphic data.

A sample printcap file for local plotters is provided:

# SAMPLE PRINTCAP FILE FOR NODE MARS
#
# This is a sample /etc/printcap file for an INDIGO workstation.
# It contains 2 entries for the following configurations:
#
# cal5912: Queue for a CalComp 5912 plotter.
# Graphics files are converted
# to CalComp format prior to being sent to
# the plotter.
#
# cal5800: Queue for a CalComp 58xx connected to a
# parallel printer.
#cal5912:\:lp=/dev/ttyd2:sd=/usr/spool/cal5912:br
#9600:sh:sf:\:ms=cs8,-parenb,-opost,-echo,ixon,-istrip:
#:cal5800:\:lp=/dev/plp:sd=/usr/spool/cal5800:sh:sf:

Remote plotter

Use the following format to define a spooling queue for a plotter or printer located on a remote node.

<queue_name>:\:
lp=:rm=<remote_node>:rp=<remote_queue>:sd=<spool_dir>:

lp = is the logical device, which is left blank as the plotter is located on a remote node.

rm = <remote_node> identifies the remote node on the network to which the plotter is physically attached.

rp = <remote_queue> identifies the name of the spooling queue in the /etc/printcap file on the remote node. For the sake of simplicity, a given spooling queue should be referred to by the same name on all nodes.

Add an entry in the /etc/printcap file for each plotter and printer that you will need to access with ArcView GIS. You must have root user privileges to edit the /etc/printcap file.

A sample printcap file for remote plotters is provided:

# SAMPLE PRINTCAP FILE FOR NODE VENUS
#
# This is a sample /etc/printcap file for an INDIGO
# workstation. A CalComp 5912 plotter is connected to
# a remote workstation named MARS. The queue name for
# the plotter on the remote node is cal5912. The same
# queue name should be used.
#cal5912:\:lp=:rm=mars:rp=cal5912:sd=/usr/spool/cal5912:

Spooling directory

The spooling directories associated with each spooling queue must be created before you use the spooling system. You must have root privileges to create the spooling directories. There must be one spooling directory for each spooling queue in the /etc/printcap file. Create the spooling directories under /usr/spool.

SPARCstation^® Solaris 2.x Workstations

Setting up plotter definitions

The Solaris operating environment does not make a distinction between "plotter" and "printer", therefore, the terms "printer" and "plotter" are used interchangeably in this section.

In order to add new printer definitions, become root, then start up the Solaris 2.x system administration tool, "admintool".

% su
# admintool &

In the Admintool: Users window, choose "Printers" from the Browse menu. The Admintool: Printers window will appear.  From the Edit menu, choose "Add", then select either "Local Printer..." or "Access to Printer..."

Local plotter

Select "Local Printer..." and fill in the required information.

Printer Name: enter a unique name for this printer.  It may contain any combination of fourteen alphanumeric characters and underscores.

Printer Port: identifies the name of the serial port, parallel port, or the logical device on the local node to which the plotter is connected (e.g., /dev/term/a, /dev/bpp0).

Printer Type: the plotter type may be in one of the directories located under the /usr/share/lib/terminfo directory. If you find it, enter the name here. If you don't, enter "tty", a generic printer type that can be used for any plotter. This will set the port characteristics of the plotter to the following system defaults:

9600     baud rate
cs8      8 data bits
-cstopb  one stop bit per byte
-parity  Do not generate parity
ixon     Enable Xon/Xoff
opost    Perform following output post-processing
-olcuc   Do not map lowercase to uppercase
onlcr    Change line feed to carriage return/line feed
-ocrnl   Do not change carriage returns to line feeds
-onocr   Output carriage return even at column 0

If you need to change any of these settings, see the discussion below on "Changing plotter port characteristics".

File Contents: if the plotter is a PostScript device, select "Postscript" when specifying "direct mode" for a plotter. Select "any" as the "file content" option. If using a filter, you may specify any type. If you want to specify a type not listed in the available options, see the discussion on "Changing plotter file content type".

Print Banner: to use filters to plot, you must have the "Not required" option selected.

When you're done, click "Add".  Click "Help..." for information on setting up the parameters for the "Printer Manager: Local Printer" menu.

Remote plotter

After you have chosen "Access to Printer...", fill in the required information.

Printer Name: the name by which the printer is known on its host machine. If the plotter is attached to a host running SunOS 4.x, this name should be the name of its spooling queue as defined in the /etc/printcap file on its host.

Print Server: the name of the remote node on the network to which the plotter is physically attached.

Click "Help..." for information on setting up the parameters in the "Access to Remote Printer" menu.

Changing plotter port characteristics

The plotter port characteristics define communication parameters used by the LP print service to "talk" to the plotter. These settings must be compatible with the plotter's own communication settings. To display the port characteristics for a plotter named "calcomp", type the following:

% lpstat -p calcomp -l

printer calcomp is idle. enabled since Thu Mar 11 10:49:19 PST 1994. available.
Form mounted:
Content types: any
Printer types: tty
Description: CalComp Classic Pen Plotter
Connection: direct
Interface: /usr/lib/lp/model/standard
After fault: continue
Users allowed:(all)
Forms allowed:(none)
Banner not required
Character sets:(none)
Default pitch:
Default page size: 72 wide
Default port settings:

Notice that the last line of the listing, "Default port settings:", has no options listed. This means that the system defaults (listed above) are in effect. For example, to change these options to 19200 baud, 7 data bits, enable parity and set it to even, do the following:

% su
# lpadmin -p calcomp -o "stty='19200 cs7 parenb -parodd' "
# lpstat -p calcomp -l

printer calcomp is idle. enabled since Thu Mar 11 10:49:19
PST 1994. available.
Form mounted:
Content types: any
Printer types: tty
Description: CalComp Classic Pen Plotter
Connection: direct
Interface: /usr/lib/lp/model/standard
On fault: write to root once
After fault: continue
Users allowed:(all)
Forms allowed:(none)
Banner not required
Character sets:(none)
Default pitch:
Default page size: 72 wide
Default port settings: 19200 cs7 parenb -parodd

Changing plotter file content type

The Printer Manager does not allow you to change the file content type of the files to be sent to a plotter. This has to be done with the "lpadmin" command. For example, to change the file content type for plotter "calcomp" from "any" to "calhcbs", type the following:

% su
# lpadmin -p calcomp -I calhcbs
# lpstat -p calcomp -l

printer calcomp is idle. enabled since Thu Mar 11 10:49:19 PST 1994. available.
Form mounted:
Content types: calhcbs
Printer types: ttyDescription: CalComp Classic Pen Plotter
Connection: direct
Interface: /usr/lib/lp/model/standard
On fault: write to root once
After fault: continue
Users allowed:(all)
Forms allowed:(none)
Banner not required
Character sets:(none)
Default pitch:
Default page size: 72 wide
Default port settings: 19200 cs7 parenb -parodd

Note:    If you use the "lpadmin" command to change the "plotter content types" field to something other than an available type under the Printer Manager menu, the type "Postscript" is the default assigned to the "File Contents" field.

Known limitations

Database Themes extension
The Database Themes extension no longer exists in ArcView GIS 3.2. This extension has been replaced by the Database Access extension. If you have projects created in ArcView GIS 3.0x that have the Database Themes extension loaded, you will have to remove the extension from those projects you want to use in ArcView GIS 3.2.

Workaround: In ArcView GIS 3.2, when you open a project created in ArcView GIS 3.0x that has the Database Themes extension loaded in it, a dialog will come up saying "Where is ...\arcview\ext\dbtheme.avx?". In this dialog, navigate to the $AVHOME/ext directory in your ArcView GIS 3.2 directory.  Choose "All" in the "List File of Types" drop-down list. Select DBTheme.fix as the file name. Click OK.

This DBTheme.fix extension is a dummy Database Themes extension that cleans up the project and automatically unloads the extension. This will only work on a project that is dependent upon Database Themes extension but does not have any DBThemes in it. It removes the two menu options that Database Themes extension added to the project and then unloads itself. Once this is done the project will work properly and will no longer depend on the Database Themes extension. If you have any projects that are dependent upon Database Themes extension and these projects have DBThemes in them, you will have to re-create the project using the Database Access extension. The DBTheme.fix extension will not clean up projects with DBThemes in them.

Picture Frame
When you try to add a CIB or CADRG image as a picture frame to a layout you will get the following error message, "The specified file is not a valid picture file".

The process of adding an image as a picture frame only allows images with file extensions that match those registered with ISrc. An ISrc is an Image Data Source that can be drawn in an image theme with an image legend. Since neither the CIB or CADRG image formats have a common file extension, a file extension is not registered to ISrc for them, therefore the error occurs.

Workaround: Add the CIB or CADRG image as a theme to a view and insert the view into the layout.

Another workaround is to use the following Avenue code to register the file extension of the CIB or CADRG image you want to add as a picture frame. For example, for a CIB image with the following name: bigimg.gnt, use the following Avenue code to register "gnt" to ISrc as a valid file extension:

imgExt = ISrc.ReturnExtensions
ISrc.SetExtensions(imgExt + {"gnt"})
 

SQL
When you connect to Informix, the OWNER text box will not work properly. If you type the name of a database owner, the tables are listed but the columns are not. Also, you will get a syntax error if you try to make a query with one of these tables.

Workaround: make sure to surround a database owner's name in single quotes (') when used in a query.  For example: Select * from 'owner'.table

Charts
ArcView GIS  will error if a chart with a logarithmic axis (Line or Scatter) is created from a table with large data values.

Tools
When using the Geoprocessing Wizard, the resulting shapefile may contain blanks or zeroes.  When input themes have field types or field names that are unsupported by dBASE, these fields become blank or zero when converted to create the output theme. For example, attributes of ArcInfo coverages contain a "COVER#" field. Since the "#" symbol is not allowed in dBASE field names, these fields are blank in the resulting theme.

Workaround: convert your input themes to shapefiles before using the Geoprocessing Wizard. This guarantees that all the fields in the output theme will have the attributes of the input themes.

Online help
In ArcView GIS online help, you will notice some >>Untitled<< topics in HyperHelp's Print, History or Bookmark dialogs. If topic titles are not defined in topics when they are created, HyperHelp will list them as untitled. Most untitled topics in ArcView GIS online help are FAQ-type help topics.

Multiuser file locking on HP workstations
In order for the File Lock Manager to work correctly on HP workstations, the file systems that contain your data must be hard mounted on the Lock Manager client machines. If these file systems are automounted on the client machines, the Lock Manager may not work correctly.

8-bit character problem in AIX 4.3.2 (IBM RISC System/6000 Workstations and Servers only)
8-bit characters are not displayed correctly and, therefore, produce incorrect results with Avenue in ArcView GIS on the IBM RS/6000 using AIX 4.3.2.  This problem occurs if the LANG variable is not set to "C" and the iso8859-1 character set is not used.

To determine the LANG variable for your login (system), do the following command:

% echo $LANG

LANG=C

The default LANG variable (locale) for IBM operating system AIX 4.x is "en_US".  If the current LANG variable is not set to "C", this can be changed either using "smit", command line, or at the console login characteristics via the new Common Desktop Environment (CDE) interface.  The LANG variable can be set up so that it affects all users on a system (globally).  You can also set the LANG variable in your .cshrc file locally so that when running ArcView GIS 3.2, only your login will be affected.  This is the recommended approach to allow all other users and the system to continue running under a LANG variable of "en_US".  A LANG variable of "en_US" is recommended for running ArcInfo.

To set up a local LANG environment of "C" for ArcView GIS, edit your .cshrc file by adding the line:

alias arcview "(setenv LANG C;$AVHOME/bin/arcview)"

To set up a global LANG environment of C for the system level, use the following command as root:

# chlang 'C'

For the CDE interface, after changing the LANG variable from using the above command globally, you will also need to choose "C" for your language variable under Options Language menu prior to logging in.

Running the IMAGINE and TIFF 6.0 extensions in AIX 4.3.2 (IBM RISC System/6000 Workstations only)
To get the IMAGINE and TIFF 6.0 extensions to load properly with ArcView GIS 3.2 on an IBM Workstation, the ASynchronous I/O driver must be loaded into the Kernel. The loading must be done on all machines in which ArcView GIS 3.2 will be run.

Workaround: Login as root and go to the $AVHOME/bin directory. From this directory you will need to run the imagine_fix script to configure the ASynchronous I/O driver. The command used at the prompt is: ./imagine_fix.

Arcview GIS and ArcInfo use different versions of the Erdas shared libraries
Having a single library path for both ArcView GIS and ArcInfo causes a problem with Erdas images, because Arcview GIS uses one version of Erdas shared libraries and ArcInfo uses a different version of the shared libraries.

Workaround: Set the library path seperately with aliases. (Note: This variable varies by platform. Refer to "Setting up your account.")

alias arcview "setenv LD_LIBRARY_PATH $AVHOME/lib:/usr/lib;$AVHOME/bin/arcview\!* &"
alias arc "setenv LD_LIBRARY_PATH $ARCHOME/lib:/usr/lib;$ARCHOME/bin/arc"

Database theme selections and the Tracking Analyst Extension (Solaris only)
You will not be able to make a selection on a database theme with the Tracking Analyst and the Database Access extensions loaded at the same time. If you try to make a selection on a database theme with Tracking Analyst loaded, it will be automatically cleared. Unloading the Tracking Analyst extension resolves this issue.

3D Analyst object/request conflict
The 3D Analyst request SetGraphic, used on a DDDMkGr object, will result in an error when 3D Analyst 1.0 is used with ArcView 3.2. ESRI has provided a 3D Analyst 1.0 Patch to resolve this issue.  The 3D Analyst 1.0 Patch files and 3d10patch.readme document are located in the /cdrom/threedx directory.

Loading 3D Analyst 1.0 will result in an error (HPUX 11.0 users only)
Workaround:  Install the 3D Analyst 1.0 Patch to correct this problem.  The 3D Analyst 1.0 Patch files and 3d10patch.readme document are located in the /cdrom/threedx directory.

Developers using the DLL and DLLProc functionality on UNIX workstations
The online documentation for DLL and DLLProc classes incorrectly states that this functionality is not supported on the UNIX platforms.  The DLL and DLLProc classes are supported in the UNIX environment, see the section "Developer Information" for the supported environments for each platform.

International language support

ArcView GIS interface (dialog boxes, text input, etc.) only supports the iso8859-1 set of languages. iso8859-1 contains characters that support all western European and English (American) languages.  The $AVHOME/etc directory contains the codeset and fontindex files used in ArcView GIS graphic programs (ArcView GIS canvas). Codesets, fontindex files, and fonts allow ArcView GIS to evaluate and handle language-specific characters.

Codesets are used to map the ASCII decimal equivalent (ADE) values to a character in a font. ADE^® values are sent to the operating system when a key is pressed on the keyboard. For information about accessing 8-bit characters from your operating system, please reference your system's National Language Support documentation. ArcView GIS processes each value and searches the current codeset file for the corresponding font glyph (pattern) number. For example, when the character `' is typed within an ArcView GIS graphic document, the ADE number 250 is passed to $AVHOME/etc/codeset. The codeset file references number 250 to the corresponding glyph number (256). If the current font contains the `' glyph number 256, it can be displayed in the ArcView GIS graphic program.

This is a sample entry in the codeset file for the character "FA":

Character----------------------------------- 'FA'
Font key index------------------------------ 1
Glyph number-------------------------------- 256
EUC or ADE---------------------------------- 250
Glyph name---------------------------------- uacute

'FA' 1 256 250 uacute

 "FA" is a hexadecimal notation for the character `'.  The actual character could be placed in the same position, if desired.

Numerous character sets have been created to support the many languages of the world. ArcView GIS provides the following codesets in $AVHOME/etc to support many of these languages:

 iso8859_2 -Central and Eastern Europe
 iso8859_5 -Cyrillic
 iso8859_7 -Greek
 turkish

To implement one of these codesets, first make a copy of the original codeset file.  Then rename the desired codeset set stored under $AVHOME/etc to $AVHOME/etc/codeset.

ArcView GIS also allows you to create custom codesets to manage their language-specific character sets.

Language-specific fonts must be obtained and installed to access the characters outside of the iso8859-1 and iso8859-2 sets of languages.  Currently, ArcView GIS does not support Asian or bidirectional languages.

The $AVHOME/etc/fontindex file is an ASCII file that is used to locate Intellifont fonts.

Most of the preloaded Intellifont fonts support only the iso8859-1 (Latin-1) set of languages. However, the cg_times and Univers font typefaces do provide character support for Eastern and Central European languages, Russian, Greek, and Turkish.

Copyright © 1996-1999 Environmental Systems Research Institute, Inc.
All Rights Reserved.

ArcView GIS software's JPEG image extension is based in part on the work of the Independent JPEG Group. Copyright 1991-1996 Thomas G. Lane. All Rights Reserved.

The information contained in this document is the exclusive property of Environmental Systems Research Institute, Inc.  This work is protected under United States copyright law and the copyright laws of the given countries of origin and applicable international laws, treaties, and/or conventions.  No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying or recording, or by any information storage or retrieval system, except as expressly permitted in writing by Environmental Systems Research Institute, Inc.  All requests should be sent to Attention: Contracts Manager, Environmental Systems Research Institute, Inc., 380 New York Street, Redlands, CA 92373-8100 USA.  The information contained in this document is subject to change without notice.

Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. In no event shall the Government acquire greater than RESTRICTED/LIMITED RIGHTS.  At a minimum, use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR §52.227-14 Alternates I, II, and III (JUN 1987); FAR §52.227-19 (JUN 1987) and/or FAR §12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (NOV 1995) (Technical Data) and/or DFARS §227.7202 (Computer Software), as applicable. Contractor/Manager is Environmental Systems Research Institute, Inc., 380 New York Street, Redlands, CA 92373-8100 USA.

ESRI, ArcInfo, and ArcView are registered trademarks; ArcInfo and Avenue, ArcStorm, 3D Anaylst, the ESRI corporate logo, the ArcView logo, GIS by ESRI, ARCNews, and GIS for Everyone are trademarks of Environmental Systems Research Institute, Inc. ArcView GIS uses Neuron Data's Open Interface and Database Intergrator.

The names of other companies and products herein are trademarks or registered trademarks of their respective trademark owners.

September 1999.