<< >> Title Contents Index Home Help

1 PGI Workstation 4.0
Installation Notes


Section 1.1 below describes how to install the PGI Workstation in a generic manner on either Linux or Solaris86. Section 1.4 describes how to install Workstation on Win32 systems. Installations using these instructions do not need to run a license daemon, except as noted below.

The compilers and tools are license-managed. As noted in the sections that follow, generation of permanent license keys is performed using your personalized account on our web page. When you purchase a permanent license from us, the e-mail order acknowledgement you receive includes complete instructions for logging on to our web page and generating your permanent license keys.

For our Workstation products using PGI-style licensing (the default), a single user can run as many simultaneous copies of the compiler as desired, on a single system, and no license daemon or Ethernet card is required. However, usage of the compilers and tools is restricted to a pre-specified username. If you would like the compilers and tools to be usable under any username, or if you are installing a multi-user Server product, you must request FLEXlm-style license keys when generating your keys and use FLEXlm-style licensing as outlined below.

Installation of FLEXlm-style licensing is more complicated than PGI-style licensing. If you require FLEXlm-style licensing, you must follow the installation instructions as specified in section 1.1 and then use either section 1.2 or 1.3 to complete your installation. Section 1.2 describes how to configure license daemons for Linux and section 1.3 describes the process for Solaris86, including installation of the license daemon and proper initialization of the LD_LIBRARY_PATH environment variable. FLEXlm-style licensing is not currently available with our products for Win32.

Regardless of the licensing mechanism you choose, when our compilers are first installed they are usable for 15 days without a permanent license key.



NOTE


At the conclusion of the trial period, the PGI compilers and tools and any executable files generated prior to the installation of permanent license keys will cease to function. Any executables, object files, or libraries created using the PGI compilers in demo mode must be recompiled with permanent license keys in place.

Executable files generated with permanent license keys in place are unconstrained, and will run on any compatible system regardless of whether our compilers are installed. However, if you change the configuration of your system by adding or removing hardware, your license key may become invalid. Please contact us if you expect to reconfigure your system to ensure that you do not temporarily lose the use of the PGI compilers and tools.

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 support 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 us at sales@pgroup.com if you would like information regarding our subscription service for the PGI products you have purchased.

1.1 Installing the Workstation on Linux or Solaris86

Bring up a shell command window on your system. The instructions below assume you are using csh, sh, ksh, or some compatible shell. Appropriate modifications will be necessary when setting environment variables if you are using a shell that is not compatible with one of these three.

Step 1 - If you received this software on a CD-ROM, please skip to step 2. If you downloaded the software from ftp://ftp.pgroup.com/x86 or another Portland Group 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 untar'd 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 100 MB of disk space. Approximately 250 MB are required during installation. Half of that can be recovered by deleting the tar file after installation is complete.

Step 2 - 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: If you have difficulty running this script, especially on a Slackware Linux system, check the permissions on /dev/null. Permission should be set to "crw-rw-rw-". Reset permissions to this value if necessary - superuser permissions are required.

Also 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/pgisoft/install

on a Solaris86 system using volume management. If you are not sure how to access the CD-ROM drive, 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 3 below.

Step 3 - All of our products are license-managed. The Workstation products that are node-locked and limited to a single user have no need to run a license daemon. If you want our Workstation compilers to be usable by any one user rather than locked to a specific username, or if you are installing a multi-user Server product, you must use FLEXlm and must specifically request FLEXlm-style keys when generating license keys over the PGI web page at http://www.pgroup.com. If you have purchased our compiler or tools that you are installing, you should have received an order acknowledgement e-mail with instructions on how to generate your license keys through the PGI web page. Note: FLEXlm-style licensing of our products is not available on Win32 systems.

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. For a
    permanent license, please read the order acknowledgement that you received.
    Connect to https://www.pgroup.com/License with the username and password in
    the order acknowledgement.

        Name:   <your name>
        User:   <your username>
        Email:  <your e-mail address>
        Hostid: PGI=9BF378E0131FF0C3CD37F6
        FLEXlm hostid: 00a024a3dfe7
        Hostname: yourhost.yourdomain.com
        Installation: /usr/pgi
        PGI Release: 4.0-1

The message above is also saved to the file /usr/pgi/license.info for retrieval at a later time.

Once you have obtained your permanent license keys using your personalized account on our web page, place them in the file /usr/pgi/license.dat (substitute the appropriate installation directory path if you have not installed in the default /usr/pgi directory). If you want your Workstation compilers to be usable by any one user, rather than locked to a specific username, you must use FLEXlm and must specifically request FLEXlm-style license keys using your account on our web page.

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

        % netscape /usr/pgi/doc/index.htm

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

Step 5 - 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 our products for Solaris86, you would substitute solaris86 for linux86 in the specified shell commands.

Assuming csh and installation in the default /usr/pgi directory:

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

Or, assuming bash, sh or ksh:

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

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

Step 6 - You can verify the release number of the products you have installed using the -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.

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 support 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 us at sales@pgroup.com if you would like information regarding our subscription service for the PGI products you have purchased.

1.2 Using FLEXlm on Linux

If you want the Workstation compilers to be usable by any one user, rather than locked to a specific username, or if you are installing a multi-user Server product, you must use the FLEXlm software license management system from Globetrotter Software as outlined below.

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

Step 2 - Once you have obtained permanent FLEXlm-style license keys (see section 1.1 above, Step 4, 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 4.000 31-dec-0 1 2B9CF0F163159E4ABE32 \
            VENDOR_STRING=107209:16 HOSTID=<hostid> ck=49
        FEATURE pgprof pgroupd 4.000 31-dec-0 1 6BDCE0B12EC19D0909F0 \
            VENDOR_STRING=107209:16 HOSTID=<hostid> ck=60

<hostname> and <hostid> should match those you submitted to us 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.

NOTE: In the feature line component VENDOR_STRING=107209, 107209 is the Product ID Number (PIN) for this installation. You will have a similar unique PIN number for your installation. Please include your PIN number when sending mail to us regarding technical support for the products you have purchased.

Step 3 - 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 bash, 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 our license keys into your existing license file or issue the following command to append our 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 our 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 4 - 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 pgroupd 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 pgroupd 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/rc3.d/S90lmgrd

Note that your system's default runlevel may be something other than `3', and if it is, that number should be used above in setting the correct subdirectory. Run /sbin/runlevel to check the system's runlevel. Note also that if you're using a Linux distribution other than Red Hat, your rc files may be in a directory other than /etc/rc.d. Some Linux distributions, such as Red Hat and Mandrake, include the chkconfig(8) utility that manages the runlevel scripts. If your system has this tool and you wish to use it, then run the following commands:

        % cp $PGI/linux86/bin/lmgrd.rc /etc/rc.d/init.d
        % chkconfig -- add lmgrd.rc

The appropriate links will be created in the /etc/rc.d directory hierarchy. For more information on chkconfig, please see the manual page.

Installation of your FLEXlm-style licensing of our 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

If you want the Workstation compilers to be usable by any one user, rather than locked to a specific username, or if you are installing a multi-user Server product, you must use the FLEXlm software license management system from Globetrotter Software as outlined below.

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

Step 2 - Once you have obtained permanent FLEXlm-style 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> 1796
        DAEMON pgroupd <install_dir>/solaris86/bin/pgroupd
        FEATURE pgf77-sol86 pgroupd 4.000 31-dec-0 1 2B9CF0F163159E4ABE32 \
            VENDOR_STRING=107209:16  HOSTID=<hostid> ck=49
        FEATURE pgprof pgroupd 4.000 31-dec-0 1 6BDCE0B12EC19D0909F0 \
            VENDOR_STRING=107209:16 HOSTID=<hostid> ck=60

<hostname> and <hostid> should match those you submitted to us 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 3 - 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 bash, 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 our license keys into your existing license file or issue the following command to append our license file to the definition of LM_LICENSE_FILE:

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

Or, assuming bash, 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 our 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 4 - 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 our 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 pgroupd 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 FLEXlm-style licensing for the 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 the Workstation on Win32

If you are installing the 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 the 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, our compilers and tools on Win32 are license-managed. However, FLEXlm-style licensing is not available on Win32. All licenses are node-locked. The Win32 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 Win32 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 Win32 serial number. Obtain your permanent license keys using your personalized account on our web page as outlined in your order acknowledgement, and place them in the file C:/PGI/license.dat (or specify the appropriate directory path if you have installed in a directory other than the default C:/PGI). You should now be able to use our compilers and tools from any PGI command window.

Note for Win2000 and WinXP installations: The 4.0 release will suggest a location for a TEMP area, and the user can approve or change the directory. The directory will be created by the install script..

1.4.1 Installing the EMACS Editor for Win32

The emacs editor consumes nearly 20 MB of installation space within the Win32 version of the PGI Workstation. For this reason, it is de-coupled 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/Zx86/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.

Similarly, emacs does not auto-install from the PGI Workstation 4.0 CD-ROM. You must explore the CD-ROM drive and double-left-click on emacs.exe to install emacs from CD-ROM.

1.4.2 Customizing the PGI Window on Win32

By default, when you double-left-click on the Workstation desktop icon, a standard black-background command window appears on your screen pre-initialized with environment and path settings for use of our 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 Workstation desktop icon, and left-click "Properties" from the pop-up menu. Modify the features mentioned above by selecting the appropriate tabs in the pop-up window and making modifications as desired.


<< >> Title Contents Index Home Help