
This document Copyright 1999, The Portland Group, Incorporated.
All rights reserved.


INSTALLING RELEASE 3.1 OF THE PGI IA-32 COMPILERS AND TOOLS

Contents:

1.1 Installing on Linux or Solaris with temporary evaluation license
    or with permanent license based on PGI= hostid
1.2 Using FLEXlm-style license daemons on Linux
1.3 Using FLEXlm-style license daemons on Solaris86
1.4 Installing on Windows NT

Note:

If you are installing a PGI Server or PGI Cluster Development Kit (CDK)
product on Linux or Solaris86, or wish to use FLEXlm for license
management of your PGI Workstation product on Linux or Solaris86, you
must install the software as specified in section 1.1 and then use
either section 1.2 or 1.3 to complete your installation.


For the first 60 days after your purchase, you may send technical
questions about these products to the e-mail address trs@pgroup.com.
If you have purchased a subscription, you will have access to e-mail
service for an additional 12 months and will be notified by e-mail when
maintenance releases occur and are available for electronic download and
installation. Contact PGI at sales@pgroup.com if you would like
information on signing up for PGI's subscription service for the PGI
products you have purchased.


1.1	Installing on Linux or Solaris86

STEP 1 - Create the directory in which you wish to install the
software.  Common locations would be /usr/pgi or /usr/local/pgi, but
installation can occur in any directory where you have appropriate
permissions.  Please make sure that the installation directory has the
necessary ownership and permissions appropriate for your site by using
the chown and chmod commands.

The following assumes installation in /usr/pgi.  Set the environment
variable PGI to the name of the installation directory.  Assuming csh:

	% setenv PGI /usr/pgi

Or, assuming sh or ksh:

	% PGI=/usr/pgi
	% export PGI

STEP 2 - If you received this software on a CD-ROM, please skip to step
3.  If you downloaded the software from ftp://ftp.pgroup.com/x86 or
another PGI electronic distribution site, then in the instructions that
follow, <tarfile> needs to be replaced with the name of the file that
was downloaded.

The compressed tar file needs to be uncompressed and untard before
installation.

        % gunzip <tarfile>.tar.gz
        % tar xpf <tarfile>.tar

Note that the products cannot be installed into the same directory where
the tar file is unpacked, so it is recommended you execute the above
commands in /tmp or another location that is not the installation
directory.

All software should fit into less than 35 MB of disk space. 
Approximately 70 MB are required during installation, but half of that
can be recovered by deleting the tar file after installation is
complete.

STEP 3 - The install script must be run to properly install the
software.  If you are installing from a CD-ROM, issue the following
command:

	% /mnt/cdrom/install

Note that some systems use a CD-ROM volume manager that may insert  an
additional directory in the above pathname.  For example, the pathname
might be

	% /cdrom/pgiws31/install

on a Solaris86 system using volume management.  If you are not sure how
to access the CD-ROM drive, please check with your system administrator.
If you downloaded the software from the Internet, change to the
directory where you uncompressed and untar'd the tar file, and run:
 
	% ./install

The install script will list the products that are available on this
CD-ROM.  You will be asked which products should be installed and to
select an installation directory.  After the software is installed, the
script will do some system-specific customization and then initialize 
the licensing, which is covered in step 4 below.

STEP 4 - All PGI products are license-managed.  PGI Workstation products
which are node-locked and limited to a single user have no need to run a
license daemon. If you want your PGI Workstation compilers to be usable
by any one user, rather than locked to a specific username, you must use 
FLEXlm and must specifically request a FLEXlm-style license from PGI. 
Note:  FLEXlm-style licensing of PGI products is not available on NT.

The install script asks for your real name, your username, and your
email address.  It then creates a fifteen-day license and prints a
message like this:

        NOTE: your evaluation license will expire in 	
        14 days, 23.6 hours. Please contact PGI or 	
        an authorized PGI distributor for a permanent 
        license.  See http://www.pgroup.com for 
        a list of authorized PGI distributors. 

        Send the following information to license@pgroup.com 
        or to the corresponding address for your authorized 
        PGI distributor: 
	
        Name:   <your name>
        User:   <your username>
        Email:  <your e-mail address>
        Hostid: PGI=9BF378E0131FF0C3CD37F6
	
        FLEXlm hostid: 00a024a3dfe7
        Hostname:      computer.pgroup.com
        Installation:  /usr/pgi

        You may also send the information by fax to 
        +1-503-682-2637 or to the corresponding fax 
        number for your authorized PGI distributor.

The message above is also saved to the file $PGI/license.info for
retrieval at a later time.  Be sure to send purchasing information if
you have not already purchased.  If you have purchased, include the PIN
number given to you at the time of the purchase.

After the information is sent to PGI, a permanent license will be
returned to you.  Once you have obtained your permanent license keys,
place them in the file $PGI/license.dat. If you want your PGI
Workstation compilers to be usable by any one user, rather than locked
to a specific username, you must use FLEXlm and must specifically
request a FLEXlm-style license when sending the above license
information to PGI.

Unlike previous releases of PGI software, the environment variable
LM_LICENSE_FILE is no longer used or necessary when using the default
licensing mechanism.  Note that is required for installations which use
FLEXlm-style licensing.

STEP 5 - You can view the online HTML documentation using any web
browser.  Assuming you use netscape, issue the following command:

	% netscape $PGI/doc/pgi.index.html

You may want to place a bookmark on this location for easy future
reference to the online manuals.

STEP 6 - With either the temporary or permanent license file in place,
execute the following commands to make the PGI products you have
purchased accessible. Note that the path settings below assume that a
Linux product has been installed.  If you have purchased PGI products
for Solaris86, you would substitute solaris86 for linux86 in the
specified shell commands. 

Assuming csh:

	% setenv PGI /usr/pgi
	% set path = ( $PGI/linux86/bin $path )
	% setenv MANPATH "$MANPATH":$PGI/man

Or, assuming sh or ksh:

	% PGI=/usr/pgi
	% export PGI
	% PATH=$PGI/linux86/bin:$PATH
	% export PATH
	% MANPATH=$MANPATH:$PGI/man
	% export MANPATH

If $MANPATH is not currently set, then please omit it in the above 
commands.

You should add the above commands to your startup files to ensure you
have access to the PGI products upon future logins.

STEP 7 - You can verify the release number of the products you have
installed using the -dryrun -V options on any of the compiler commands. 
This will also show you the sequence of steps the compiler will use to
compile and link programs for execution on your system.  

      For Fortran 77, use "pgf77 -dryrun -V x.f"
      For Fortran 90, use "pgf90 -dryrun -V x.f"
      For HPF, use "pghpf -dryrun -V x.f"
      For C++, use "pgCC -dryrun -V x.c"
      For C, use "pgcc -dryrun -V x.c"

Note that the files x.f or x.c need not exist in order for you to
successfully execute these commands.

Installation is now complete.  For the first 60 days after your
purchase, you may send technical questions about these products to the
e-mail address trs@pgroup.com.  If you have purchased a subscription,
you will have access to e-mail service and automatic minor upgrade
releases for an additional 12 months and will be notified by e-mail
whenever a new release is available for electronic download and
installation.  Contact PGI at sales@pgroup.com if you would like
information on signing up for PGI's subscription service for the PGI
products you have purchased. 


1.2	Using FLEXlm on Linux

STEP 1 - Install the software as described in section 1.1 above.

STEP 2 - All PGI Server and PGI Cluster Development Kit (CDK) products 
are license-managed using the FLEXlm software license management system 
from Globetrotter Software.  If you want PGI Workstation compilers to 
be usable by any one user, rather than locked to a specific username, 
you must use FLEXlm-style licensing.

STEP 3 - Once you have obtained permanent license keys (see section 1.1
above for how to obtain these), place them in a file named license.dat
in the $PGI directory.  For example, if you have purchased PGF77
Workstation for Linux, the license.dat file should look similar to the
following:

  SERVER <hostname> <hostid> 7496
  DAEMON pgroupd <install_dir>/linux86/bin/pgroupd

  FEATURE pgf77-linux86 pgroupd 3.000 31-dec-0 1 \   
    2B9CF0F163159E4ABE32 VENDOR_STRING=107209:16 \
    HOSTID=<hostid> ck=49

  FEATURE pgprof pgroupd 3.000 31-dec-0 1 \
    6BDCE0B12EC19D0909F0 VENDOR_STRING=107209:16 \
    HOSTID=<hostid> ck=60

<hostname> and <hostid> should match those you submitted to PGI and
<install_dir> must be changed to match the directory in which the
compilers are installed.  In particular, <install_dir> should match the
value of $PGI as defined above.

STEP 4 - When the license file is in place, execute the following
commands to make the PGI products you have purchased accessible. If you
are not using other products managed by FLEXlm, and have not previously
set the environment variable LM_LICENSE_FILE, issue the following
command to do so (assuming csh):
 
	% setenv LM_LICENSE_FILE $PGI/license.dat

Or, assuming sh or ksh:
 
	% LM_LICENSE_FILE=$PGI/license.dat
	% export LM_LICENSE_FILE

If you are using other products managed by FLEXlm, and have previously
set the environment variable LM_LICENSE_FILE, either incorporate the PGI
license keys into your existing license file or issue the following
command to append the PGI license file to the definition of LM_LICENSE_FILE 
(assuming csh):

        % setenv LM_LICENSE_FILE "$LM_LICENSE_FILE":$PGI/license.dat

Or, assuming sh or ksh:

        % LM_LICENSE_FILE=$LM_LICENSE_FILE:$PGI/license.dat
        % export LM_LICENSE_FILE

You should add the above commands to your startup files to ensure you
have access to the PGI products upon future logins.

If LM_LICENSE_FILE is not set or exported, and the node-locked 15-day
temporary license file $PGI/PGIinstall still exists, then $PGI/PGIinstall
will be used for resolving compiler licenses.

STEP 5 - You must now start the license manager daemon.  Edit the shell
script template $PGI/linux86/bin/lmgrd.rc.  If you have installed the
compiler(s) in a directory other than /usr/pgi, substitute the correct
installation directory into the definition of the PGI environment
variable on line 3 of the script. Now exit the editor and issue the
following command to start the license server and PGI license daemon
running on your system:
 
        % lmgrd.rc start

If you wish to stop the license server and license daemon at a later
time, you can do so with the command:
 
        % lmgrd.rc stop

To make sure that the license server and PGI daemon are started each
time your system is booted, log in as root, set the PGI environment
variable as above, and then execute the following two commands:
 	
        % cp $PGI/linux86/bin/lmgrd.rc /etc/rc.d/init.d/lmgrd
        % ln -s /etc/rc.d/init.d/lmgrd /etc/rc.d/rc2.d/S90lmgrd

If you're using a Linux distribution other than Red Hat, your
rc files may be in a directory other than /etc/rc.d.

Also note that the default multi-user run level might be different than '2'.
Please run the command '/sbin/runlevel'.  The second number is the value
that should be used in the above command that creates the symlink.

Installation of your PGI products for Linux is now complete. If you have
difficulties with the installation, send e-mail to trs@pgroup.com for
assistance.


1.3	Using FLEXlm on Solaris86

STEP 1 - Install the software as described in section 1.1 above.

STEP 2 - All PGI Server and PGI Cluster Development Kit (CDK) products are 
license-managed using the FLEXlm software license management system from 
Globetrotter Software.  If you want PGI Workstation compilers to be usable 
by any one user, rather than locked to a specific username, you must use 
FLEXlm-style licensing.

STEP 3 - Once you have obtained license keys (see section 1.1 above),
place them in a file named license.dat in the $PGI directory.  For
example, you have purchased the PGF77 compiler and PGPROF profiler for
Solaris86.  The license.dat file should look something like the
following:
 
   SERVER <hostname> <hostid> 7496
   DAEMON pgroupd <install_dir>/solaris86/bin/pgroupd

   FEATURE pgf77-sol86 pgroupd 3.000 31-dec-0 1 \
     2B9CF0F163159E4ABE32 VENDOR_STRING=107209:16 \
     HOSTID=<hostid> ck=49

   FEATURE pgprof pgroupd 3.000 31-dec-0 1 \
     6BDCE0B12EC19D0909F0  VENDOR_STRING=107209:16 \
     HOSTID=<hostid> ck=60

<hostname> and <hostid> should match those you submitted to PGI and
<install_dir> must be changed to match the directory in which the
compiler(s) are installed.  In particular, <install_dir> should match
the value of $PGI as defined above.

STEP 4 - When the license file is in place, execute the following
commands to make the PGI products you have purchased accessible. If you
are not using other products managed by FLEXlm, and have not previously
set the environment variable LM_LICENSE_FILE, issue the following
command to do so (assuming csh):

        % setenv LM_LICENSE_FILE $PGI/license.dat

 Or, assuming sh or ksh:
 
        % LM_LICENSE_FILE=$PGI/license.dat
        % export LM_LICENSE_FILE

If you are using other products managed by FLEXlm, and have previously
set the environment variable LM_LICENSE_FILE, either incorporate the PGI
license keys into your existing license file or issue the following
command to append the PGI license file to the definition of
LM_LICENSE_FILE:
 
        % setenv LM_LICENSE_FILE "$LM_LICENSE_FILE":$PGI/license.dat

 Or, assuming sh or ksh:

        % LM_LICENSE_FILE=$LM_LICENSE_FILE:$PGI/license.dat
        % export LM_LICENSE_FILE

You should add the above commands to your startup files to ensure you
have access to the PGI products upon future logins.

If LM_LICENSE_FILE is not set or exported, and the node-locked license
file $PGI/PGIinstall still exists, then $PGI/PGIinstall will be used for
resolving compiler licenses.

STEP 5 - You must now start the license manager daemon.  Edit the shell
script template $PGI/solaris86/bin/lmgrd.rc.  If you have installed the
compiler(s) in a directory other than /usr/pgi, substitute the correct
installation directory into the definition of the PGI environment
variable on line 3 of the script.  Now exit the editor and issue the
following command to start the license server and PGI license daemon
running on your system:
 
        % lmgrd.rc start

If you wish to stop the license server and license daemon at a later
time, you can do so with the command:
 
        % lmgrd.rc stop

To make sure that the license server and PGI daemon are started each
time your system is booted, log in as root, set the PGI environment
variable as above, and then execute the following two commands:
 
	% cp $PGI/solaris86/bin/lmgrd.rc /etc/init.d/lmgrd
	% ln -s /etc/init.d/lmgrd /etc/rc2.d/S90lmgrd

Installation of your PGI products for Solaris86 is now complete.  If you
have difficulties with the installation, send e-mail to trs@pgroup.com for
assistance.


1.4	Installing on  NT

If you are installing PGI Workstation from a CD-ROM, insert the CD-ROM
into the CD-ROM drive on the system on which the install is to take
place.  An installation script will automatically be invoked and the
installation process will begin.  Follow the directions printed to your
screen.

If you are installing PGI Workstation from the self-extracting file
downloaded electronically via ftp, double-click on the pgiws.exe file
with the left mouse button.  The installation process will begin. 
Follow the instructions printed to your screen.

As with Linux and Solaris86, the PGI compilers and tools on NT are
license-managed.  However, FLEXlm-style licensing is not available on
NT.  All licenses are node-locked.  The NT serial number is used as the
hostid.  This number will be printed to your screen during the
installation process, or can be located by left-clicking on
Start->Settings->Control Panel and then double-left-clicking on the
"System" icon and left-clicking on the "General" tab.  The NT serial
number will be in the middle of the System Properties window and look
something like the following:

     Registered to:
       <your name>
       <your organization>
       22296-oem-0014072-07487

The last number above is the NT serial number.  Mail this information
to license@pgroup.com along with your purchasing information (or PIN
number if you've already purchased the product), and permanent keys will
be returned to you by e-mail.

1.4.1 Using the EMACS Editor

The EMACS editor consumes nearly 20 MB of installation space within the
NT version of PGI Workstation.  For this reason, it is decoupled from
the main distribution file, pgiws.exe.  If you are an EMACS user and
would like it installed, retrieve the file:

    ftp://ftp.pgroup.com/x86/emacs.exe

It is a self-installing file.  As with pgiws.exe, simply
double-left-click on EMACS.exe after downloading and follow the
instructions for installation.

1.4.2	Customizing the PGI Command Window

By default, when you double-left-click on the PGI Workstation desktop
icon, a standard size black-background command window appears on your
screen pre-initialized with environment and path settings for use of the
PGI compilers and tools.  If you prefer different background or text
colors, font style, window size, or scrolling capability, you can
customize the "shortcut" that creates the PGI command window. 
Right-click on the PGI Workstation desktop icon, and left-click
"Properties" from the pop-up menu.  You can modify the features
mentioned above by selecting the appropriate tabs in the resulting
pop-up window and  making modifications as desired.
