Note: The following instructions refer to two directories, the distribution (source) directory which will contain the PGPLOT source code directory tree, and the binary directory in which the machine-specific libraries, data files, and demonstration programs will be created. It is recommended that you create new, empty directories for these. They should not be the same directory. In the examples below, these directories are named
USR:[LOCAL.PGPLOT] (distribution directory)
USR:[LOCAL.PGBIN] (binary directory)
but you can use any convenient names. Unusual (system) privileges are not required to install PGPLOT, assuming you have write access to the directories. In a mixed VAX-Alpha cluster, you can use a single distribution directory, but you will need two binary directories, one for each architecture. The distribution directory may be deleted after the installation has been competed, but it will be needed if you later decide to select different device drivers..
anonymous, password: your id
username@machine) to node
The distribution file is a UNIX tar file compressed with Gzip. Issue the following ftp commands to retrieve the file:
cd pub/pgplot binary get pgplot5.2.tar.gz pgplot.tar-gz(Note that you need to provide a VMS-compatible output file name in the
vmstar. These programs are not part of VMS, but are widely available on the Internet, e.g., at
decompress the distribution file, e.g.,
$ gunzip pgplot.tar-gzThen use
vmstarto extract the contents of the archive:
$ set default USR:[LOCAL} $ vmstar/extract/verbose pgplot.tar OR $ vmstar xvf pgplot.tar $ delete pgplot.tar;This will create a subdirectory
[.PGPLOT](and lower-level subdirectories) in the current directory, e.g.,
USR:[LOCAL.PGPLOT...]. Make sure that your current directory is where you want to create the ``PGPLOT distribution'' directory tree.
$ create/directory USR:[LOCAL.PGBIN] $ set default USR:[LOCAL.PGBIN]Do not try to create the PGPLOT library in the source (``distribution'') directory.
drivers.listfrom the distribution directory to the binary directory, and then use a text editor to select device drivers. This file contains one line for each available device driver: delete the exclamation mark (!) at the beginning of the line to include the driver, or ensure that an exclamation mark is present if you want to exclude the driver. Many of the drivers can be used only on certain operating systems (see notes in
drivers.list), so include only the drivers you plan to use. PGPLOT can later be reconfigured by restarting the installation at this step. Most installations should include: the null device (/NULL), PostScript printers (/PS, /VPS, /CPS, and /VCPS), Tektronix terminals (/TEK, /XTERM, and possibly other variants), and, if the X window system (DECwindows) is available, the X window drivers (/XWIN, /XSERV). You may also wish to include drivers for GIF files (/GIF, /VGIF) or some of the other printers.
$ copy USR:[LOCAL.PGPLOT]drivers.list  $ edit drivers.list
install.comfrom the VMS subdirectory of the distribution directory, e.g.:
$ @USR:[LOCAL.PGPLOT.SYS_VMS]install USR:[LOCAL.PGPLOT]The first argument supplied to
installis the name of the distribution directory. The script will attempt to determine your machine architecture (VAX or Alpha) and compile appropriate code. The script has been tested under several versions of VMS, but if you have problems, you may need to edit the script.
The install script issues messages as it proceeds: it usually takes quite a long time. It should generate the following files:
DRIVERS.LIST GREXEC.F GRFONT.DAT GRPCKG.OLB GRPSHR.EXE GRPSHR.OLB PGDEMO1.EXE ... PGDEMO16.EXE PGXWIN_SERVER.EXE RGB.TXTThe script assumes that you have the current DEC Fortran and C compilers installed. A C compiler is required for XWDRIV and X2DRIV and the associated programs PGXWIN_SERVER and PGDISP, and for generating the C wrapper library CPGPLOT.OLB. If you don't have the DEC C compiler, the script will have to be modified.
The script may fail if you redefine any of the common DCL commands like PURGE or DELETE.
Note: Demonstration program
pgdemo14 is compiled
incorrectly by the DEC Fortran 6.2 compiler when optimization is
enabled; the symptom is that the labels like "Number of Vertices:" do
not appear on the screen. The problem is solved by disabling
$ @USR:[LOCAL.PGPLOT.SYS_VMS]install USR:[LOCAL.PGPLOT] CPGThis creates three files:
CPGPLOT.H (ANSI C header file) CPGPLOT.OLB (library containing the C binding) CPGDEMO.EXE (demonstration program)
$ @USR:[LOCAL.PGPLOT.SYS_VMS]install USR:[LOCAL.PGPLOT] PGDISPThis adds one file,
PGDISP.EXE. The PGDISP program sometimes gives compilation problems. Most of these are non-fatal warnings that can be ignored.
drivers.listbefore installing the PGPLOT library; and (c) install the C wrapper library. Execute the following command:
$ @USR:[LOCAL.PGPLOT.SYS_VMS]install USR:[LOCAL.PGPLOT] PGMDEMOThis creates five files:
PGMDEMO.EXE (executable demo program) PGMOTIF.OPT (linker options file for linking PGPLOT/Motif applications) PGXWIN.OBJ (object module required by PGPLOT/Motif applications) XMPGPLOT.OBJ (object module required by PGPLOT/Motif applications) XMPGPLOT.H (header file required by PGPLOT/Motif applications)(This step may not work on all VMS systems: there are many differences between the various available versions of the DEC C compiler and DECwindows Motif. If you get error messages, you may need to modify file
GRPSHR.EXE, with complete directory information, e.g.,
$ define GRPSHR PGPLOT_DIR:GRPSHR.EXEIf this logical name is not defined, RUN will look for
GRPSHR.EXEin the system library directory (
rgb.txt(unless logical names
PGPLOT_RGBare defined to override this default behavior), and, if needed, the X-window server program
$ define PGPLOT_DIR USR:[LOCAL.PGBIN]
$ define PGPLOT_DEV "/xwin"
GRPSHR.OLBin one of the
LNK$LIBRARY*logical names, e.g.
$ define LNK$LIBRARY PGPLOT_DIR:GRPSHR.OLBIf you do not do this, you will need to include this library (note:
GRPSHR.EXE) in your LINK commands.
To run a program, use the RUN command:
$ run pgdemo1 $ run pgdemo2 ... $ run cpgdemo ! optional component $ run pgmdemo ! optional componentAll the demonstration programs prompt for a device name and type. Type a question mark
?to see a list of the available device types and verify that PGPLOT has been configured properly.
Points to check for: the PGPLOT program correctly reads the font file and displays superscripts, subscripts and special characters (pgdemo2); the PGPLOT program can read the color database (pgdemo10); on interactive devices, the cursor works correctly (pgdemo5, pgdemo6).
$ library/insert/help pgplot.hlb pgplot.hlp