This draft documentation is taylored for a perl to specifically go with
the RMS Symbolic link test SDK, so may need some changes for other purposes.
The specific information on about the Posix Compliant mode may change
with the eventual VMS release that implements it.
The Perl for the RMS Symbolic Link test kit has not yet finished QTV
testing.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- README.vms_5_8_6 Thu Jun 30 13:42:50 2005
+++ README.vms Fri Jul 1 16:12:43 2005
@@ -4,11 +4,160 @@
=head1 NAME
-README.vms - Configuring, building, testing, and installing perl on VMS
+README.vms - Configuring, building, testing, and installing Perl on VMS
+
+=head1 Special HP Symbolic Link test Perl information
+
+This HP SYMBOLIC LINK SDK test release of Perl is a demonstration kit
+for evaluation and testing of using the new RMS support for POSIX
+Compliant Pathnames, and symbolic links.
+
+Some of the features in the SYMBOLIC LINK SDK may be different than what
+will eventually be provided as part of the OpenVMS operating system.
+
+The Perl source kit for the SDK provides an additional command procedure
+that can recreate the distributed binaries.
+
+It is an test demonstration kit for evaluating the new RMS Symbolic Link
+features and better UNIX compatibility.
+
+The HP supplied test demonstration binary Perl kit can only be used with
+systems that have the RMS Symbolic link SDK kit installed.
+
+The HP supplied test demonstration Perl Binary Kit is built with the
+following options: "unlink_all_versions" and "uselargefiles".
+
+Currently this test version of Perl for OpenVMS is distributed by BACKUP
+SAVE SETS that may be compressed in ZIP archives, as the INFO-ZIP program
+on OpenVMS does not fully support the extended file specifications on ZIP
+archives that it creates.
+
+This saveset is intended to be installed on ODS-5 volumes, but also has
+additional copies of some files with names changed to be compatible with
+scripts that assume ODS-2 restrictions.
+
+The saveset names will be in PCSI convention so will be similar to
+HP-*VMS-PERL-T0508-06*-1.BCK and HP-VMS-PERL_SRC-T0508-06*-1.BCK.
+
+To install, chose the physical or concealed rooted logical disk that you
+want to install on and do a normal restore, for example
+
+ BACKUP HP_AXPVMS-PERL-T0508-06-1.BCK/SAV device:[*...]
+
+Then use the command @device:[HP_PERL_5_8_6]PERL_SETUP.COM to your
+LOGIN.COM in order to have the Perl logicals and symbols defined.
+
+=head2 Usage of new features in this test version of Perl
+
+This test version of Perl has improved support for ODS-5 volumes.
+
+To enable improved support for ODS-5, you need to activate the CRTL
+feature.
+
+ $DEFINE DECC$EFS_CHARSET "ENABLE"
+
+There is now optional support for case preserved file specifications.
+
+ $DEFINE DECC$EFS_CASE_PRESERVE "ENABLE"
+
+If the running process is set to case sensitive mode, Perl will also
+be case sensitive on VMS and will report it. Running a process in
+case sensitive mode with out enabling case preserved file specifications,
+will probably not work very well. At this time, the case sensitive mode
+has not been tested.
+
+To enable case sensitive mode:
+
+ $SET PROCESS/CASE_LOOKUP=SENSITIVE
+
+
+This test version of Perl has two optional UNIX/POSIX compatibility modes
+that are enabled by DECC feature logicals.
+
+To enable a mode where pathnames will be output as UNIX in the close to the
+traditional CRTL format:
+
+ $DEFINE DECC$EFS_CASE_PRESERVE "ENABLE"
+ $DEFINE DECC$EFS_CHARSET "ENABLE"
+ $DEFINE DECC$FILENAME_UNIX_NO_VERSION "ENABLE"
+ $DEFINE DECC$READDIR_DROPDOTNOTYPE "ENABLE"
+ $DEFINE DECC$FILENAME_UNIX_REPORT "ENABLE"
+
+To enable a mode where pathnames will be output as POSIX and the symbolic
+link function, use the same logical names as before and add:
+
+ $DEFINE DECC$POSIX_COMPLIANT_PATHNAMES 3 !Ambiguous names presumed VMS
+
+For this test version of Perl and the RMS Symbolic link SDK, the following
+logicals are also needed to temporarily work around issues in POSIX handling.
+
+ $!Special case for mkdir/chdir/rmdir/opendir treating a directory name
+ $!with no with no path or type delimiters only as a VMS logical name when
+ $!DECC$POSIX_COMPLIANT_PATHNAMES is defined a 3.
+
+ $DEFINE DECC_DIR_BARENAME "ENABLE"
+
+ $! Readdir in DECC$READDIR_UNIX_REPORT mode escaping EFS characters
+ $! in SDK CRTL
+
+ $DEFINE DECC_BUG_READDIR_EFS1 "ENABLE"
+
+ $! POSIX compliance mode requires a /dev/null be created.
+ $! The RMS Symbolic link SDK will create one.
+ $! If you do not want to use it, as a temporary work around
+
+ $! DEFINE DECC_BUG_DEVNULL "ENABLE"
+
+ $! The SDK CRTL realpath() is not working on pathnames that are a
+ $! symbolic link with no UNIX or VMS directory or file type delimiters.
+ $! Perl has a bsd_realpath function that can be used as a fallback,
+ $! but it is significantly slower.
+
+ $! DEFINE DECC_DISABLE_CRTL_REALPATH
+
+=head2 Known BUGS
+
+The change directory routine in the lib/vms_stdio module may not permanently
+change the default directory when the image exits.
+
+VMS file specifications ending with explicit NULL extensions are being
+incorrectly converted to POSIX pathnames with trailing dot characters.
+VMS::Filespec::unixify("[]foo.") should return "./foo", but is instead
+returning "./foo."
+
+A new CRTL is supplied in in the same locations as this Perl binary kit.
+
+This new CRTL fixes time zone handling and the handling of fgetname() when
+DECC$POSIX_COMPLIANT_PATHNAMES is enabled.
+
+
+=head2 Building the test Perl from a source kit
+
+The source kit should be able to be used on any version of OpenVMS that
+the kit for Perl 5.8.6 available from CPAN. Some additional OpenVMS features
+may be enabled if present on the system, but the symbolic link support will
+only be built on systems with the SDK installed.
+
+If the logical PCSI_PRODUCER is defined as "USER", it will stage an install
+directory and create a backup save set to allow it to be further distributed.
+The directory names and saveset names will be also renamed to match.
+
+It is recommended that PCSI_PRODUCER names of "HP" be only used on
+distributions provided by HP, and that the PCSI_PRODUCER of "PERL" only be
+used for kits intended for distribution by CPAN.
+
+The PCSI_PRODUCER name of "USER" is recommended for building kits that will
+be used internal to a network.
+
+The command procedure is run with:
+
+ @ build_bin_symlink_perl.com
+
=head1 SYNOPSIS
-To configure, build, test, and install perl on VMS:
+
+To configure, build, test, and install Perl on VMS:
@ Configure
mms
@@ -17,6 +166,11 @@
mmk may be used in place of mms in the last three steps.
+At this time, if the Perl source has been places on an ODS-5 disk
+with case preserved, the MMK program must be used for the build, or the
+extensions of the files must be renamed to upper case.
+
+
=head1 DESCRIPTION
=head2 Important safety tip
@@ -32,9 +186,9 @@
died a natural death some time before the standard was set. Therefore
VAX C will not compile Perl 5.005 or later. We are sorry about that.
-If you are stuck without Compaq (formerly DEC) C consider trying Gnu C
-instead, though there have been no recent reports of builds using Gnu C.
-There is minimal support for Compaq C++ but this support is not complete;
+If you are stuck without HP (formerly DEC and Compaq) C consider trying
+Gnu C instead, though there have been no recent reports of builds using
+Gnu C. There is minimal support for HP C++ but this support is not complete;
if you get it working please write to the vmsperl list (for info see
L</"Mailing Lists">).
@@ -56,7 +210,7 @@
The current sources and build procedures have been tested on a VAX using
DEC C, and on an AXP using DEC C. If you run into problems with
other compilers, please let us know. (Note: DEC C was renamed to Compaq C
-around version 6.2).
+around version 6.2). The compiler is now being rebranded as "HP C".
There are issues with various versions of DEC C, so if you're not running a
relatively modern version, check the "DEC C issues" section later on in this
@@ -70,7 +225,7 @@
=item 1 A C compiler.
-DEC (now Compaq) C or gcc for VMS (AXP or VAX).
+DEC (now HP) C or gcc for VMS (AXP or VAX).
=item 2 A make tool.
@@ -80,6 +235,15 @@
anyone's tested it that we're not sure. MMK is free though, so
go ahead and use that.
+Note, templates are missing from GNU make, and it appears that the
+MAKEMAKER module assumes that it is building for MMS/MMK when it is
+running on OpenVMS as it will output traditional OpenVMS file specifications.
+
+To operate under the GNU make provided by the GNV kit, not only will
+the missing template have to be provided or derived from the
+descrip_mms.template, the resulting file specifications and compiler
+and linker flags will also need to be in UNIX notation.
+
=back
=head2 Additional software that is optional for Perl on VMS
@@ -92,20 +256,29 @@
A de-compressor for *.gz and *.tgz files available from a number
of web/ftp sites and is distributed on the OpenVMS Freeware CD-ROM
-from Compaq.
+from HP.
+
+ http://www.hp.com/go/openvms/freeware/
+ http://www.hp.com/go/openvms/ and navigate to the sidebar link of
+ "OpenVMS Software" and then to the sidebar link of
+ "Opensource tools" and then "GNV" or "VMSTar"
- http://www.fsf.org/order/ftp.html
- http://www.openvms.compaq.com/freeware/
http://www.crinoid.com/utils/
+ http://www.fsf.org/order/ftp.html (Link is 404)
=item 2 VMS TAR
-For reading and writing unix tape archives (*.tar files). Vmstar is also
+For reading and writing UNIX tape archives (*.tar files). Vmstar is also
available from a number of web/ftp sites and is distributed on the OpenVMS
-Freeware CD-ROM from Compaq.
+Freeware CD-ROM and in the GNV kit from HP.
ftp://ftp.lp.se/vms/
- http://www.openvms.compaq.com/freeware/
+
+ http://www.hp.com/go/openvms/freeware/
+ http://www.hp.com/go/openvms/ and navigate to the sidebar link of
+ "OpenVMS Software" and then to the sidebar link of
+ "Opensource tools" and then "GNV" or "VMSTar"
+
Recent versions of VMS tar on ODS-5 volumes may extract tape archive
files with ^. escaped periods in them. See below for further workarounds.
@@ -116,11 +289,14 @@
Unzip is available from a number of web/ftp sites.
http://www.info-zip.org/UnZip.html
- http://www.openvms.compaq.com/freeware/
- ftp://ftp.openvms.compaq.com/
ftp://ftp.madgoat.com/madgoat/
ftp://ftp.process.com/vms-freeware/
+ http://www.hp.com/go/openvms/freeware/
+ http://www.hp.com/go/openvms/ and navigate to the sidebar link of
+ "OpenVMS Software" and then to the sidebar link of
+ "Opensource tools" and then "GNV" or "ZIP".
+
=item 4 MOST
Most is an optional pager that is convenient to use with perldoc (unlike
@@ -139,14 +315,18 @@
available here:
http://www.crinoid.com/utils/
- http://www.openvms.compaq.com/freeware/
+
+ http://www.hp.com/go/openvms/freeware/
+ http://www.hp.com/go/openvms/ and navigate to the sidebar link of
+ "OpenVMS Software" and then to the sidebar link of
+ "Opensource tools" and then "GNV".
=back
Please note that UNZIP and GUNZIP are not the same thing (they work with
different formats). Many of the useful files from CPAN (the Comprehensive
Perl Archive Network) are in *.tar.gz or *.tgz format (this includes copies
-of the source code for perl as well as modules and scripts that you may
+of the source code for Perl as well as modules and scripts that you may
wish to add later) hence you probably want to have GUNZIP.EXE and
VMSTAR.EXE on your VMS machine.
@@ -158,10 +338,10 @@
You may need to set up a foreign symbol for the unpacking utility of choice.
-If you unpack a perl source kit with a name containing multiple periods on
+If you unpack a Perl source kit with a name containing multiple periods on
an ODS-5 volume using recent versions of vmstar (e.g. V3.4 or later) you may
need to be especially careful in unpacking the tape archive file. Try to use
-the ODS-2 compatability qualifiers such as:
+the ODS-2 compatibility qualifiers such as:
vmstar /extract/verbose/ods2 perl-V^.VIII^.III.tar
@@ -175,21 +355,32 @@
set security/protection=(o:rwed) perl-5^.8^.6.dir
rename perl-5^.8^.6.dir perl-5_8_6.dir
-Perl on VMS as of 5.8.6 does not completely handle extended file
-parse styles such as are encountered on ODS-5. While it can be built,
-installed, and run on ODS-5 filesystems; it may encounter
-trouble with characters that are otherwise illegal on ODS-2
-volumes (notably the ^. escaped period sequence).
+Perl on VMS as of 5.8.6 as provided by this SDK does not completely
+handle extended file parse styles such as are encountered on ODS-5.
+
+It is however improved over the Perl 5.8.6 that is currently distributed
+by CPAN.
+
+For compatibility with the OpenVMS C runtime, this feature is enabled
+with the C feature logical name DECC$EFS_CHARSET.
+
+$DEFINE DECC$EFS_CHARSET "ENABLE"
+
+With this set, Perl will handle files and directories with extra "^." in
+them for obviously traditional OpenVMS file specifications, and for what
+is obviously UNIX file specifications, no "^" should be used for special
+characters. Some other EFS file specifications may also work.
+
=head1 Configuring the Perl build
-To configure perl (a necessary first step), issue the command
+To configure Perl (a necessary first step), issue the command
@ Configure
-from the top of an unpacked perl source directory. You will be asked a
+from the top of an unpacked Perl source directory. You will be asked a
series of questions, and the answers to them (along with the capabilities
-of your C compiler and network stack) will determine how perl is custom
+of your C compiler and network stack) will determine how Perl is custom
built for your machine.
If you have multiple C compilers installed, you'll have your choice of
@@ -197,12 +388,12 @@
you're using a version older than 5.2, check the "DEC C Issues" section.
If you have any symbols or logical names in your environment that may
-interfere with the build or regression testing of perl then configure.com
+interfere with the build or regression testing of Perl then configure.com
will try to warn you about them. If a logical name is causing
you trouble but is in an LNM table that you do not have write access to
then try defining your own to a harmless equivalence string in a table
such that it is resolved before the other (e.g. if TMP is defined in the
-SYSTEM table then try DEFINE TMP "NL:" or somesuch in your process table)
+SYSTEM table then try DEFINE TMP "NL:" or some such in your process table)
otherwise simply deassign the dangerous logical names. The potentially
troublesome logicals and symbols are:
@@ -236,7 +427,7 @@
@ Configure "-d" "-Dprefix=dka100:[utils.perl5.]"
Note that the installation location would be by default where you unpacked
-the source with a "_ROOT." appended. For example if you unpacked the perl
+the source with a "_ROOT." appended. For example if you unpacked the Perl
source into:
DKA200:[PERL-5_10_2...]
@@ -263,7 +454,7 @@
configure.com, which processes the hints file config_h.SH. There is
code in there to Do The Right Thing, but that may end up being the
wrong thing for you. Make sure you understand what you are doing since
-inappropriate changes to configure.com or config_h.SH can render perl
+inappropriate changes to configure.com or config_h.SH can render Perl
unbuildable; odds are that there's nothing in there you'll need to
change.
@@ -279,6 +470,30 @@
How well integrated they are into the system depends on the stack, your
version of VMS, and the version of your C compiler.
+The actual most portable solution available is to use the socket routines
+built into DEC C. Which routines are available depend on the version of
+VMS you're running, and require proper UCX emulation by your TCP/IP vendor.
+Relatively current versions of Multinet, TCPWare, Pathway, and HP TCPIP
+(Formerly UCX) all provide the required libraries--check your manuals or
+release notes to see if your version is new enough.
+
+As the socket support from the TCPIP product is loaded as needed at run
+time by the DEC C runtime, there is really little reason to not build
+with socket support, unless you are running CMU-IP on VAX-VMS.
+
+The paragraph following this next one is left for historical reasons.
+
+The SOCKETSHR library no longer appears to be supported and it and
+NetLib are only needed to provide socket support for use with the CMU-IP
+TCP/IP stack, which is also appears unsupported. In addition the versions of
+SOCKETSHR that do not contain a patch by John Malmberg, are not fully
+compatible with NetLib, and that patch required SOCKETSHR depending
+on NetLib not changing an undocumented internal coding practice. With out
+this patch, the SOCKETSHR routine that returns an OpenVMS channel number is
+returning incorrect data. The CMU-IP TCP/IP stack is only available for
+VAX, and some of the more current source code for CMU-IP seems to be
+unavailable, which pretty much restrict CMU-IP to older versions of VAX/VMS.
+
The most portable solution uses the SOCKETSHR library. In combination with
either UCX or NetLib, this supports all the major TCP stacks (Multinet,
Pathways, TCPWare, UCX, and CMU) on all versions of VMS Perl runs on, with
@@ -287,18 +502,33 @@
UDP sockets when used with Multinet, though, so you should be aware of
that.
-The other solution available is to use the socket routines built into DEC
-C. Which routines are available depend on the version of VMS you're
-running, and require proper UCX emulation by your TCP/IP vendor.
-Relatively current versions of Multinet, TCPWare, Pathway, and UCX all
-provide the required libraries--check your manuals or release notes to see
-if your version is new enough.
=head1 Building Perl
The configuration script will print out, at the very end, the MMS or MMK
-command you need to compile perl. Issue it (exactly as printed) to start
-the build.
+command you need to compile Perl. Issue it (exactly as printed) to start
+the build after reading all the directions here.
+
+The Perl build may be sensitive to the behavior of the feature settings of
+of the OpenVMS C runtime library. In particular, it is recommended that
+the following logicals either not be defined or the feature turned off by
+the logical name.
+
+$SET NOON
+$DEASSIGN DECC$EFS_CASE_PRESERVE
+$DEASSIGN DECC$FILENAME_UNIX_REPORT
+$DEASSIGN DECC$FILENAME_UNIX_ONLY
+$DEASSIGN DECC$FILE_PERMISSION_UNIX
+$DEASSIGN DECC$FILENAME_UNIX_NO_VERSION
+$DEASSIGN DECC$READDIR_DROPDOTNOTYPE
+$DEASSIGN DECC$POSIX_COMPLIANT_PATHNAMES ! New with the SDK
+$!
+
+If the logical name SYS$POSIX_ROOT is defined, you may need to disable
+the OpenVMS C runtime from using it. Note that the GNV kit will cause the
+SYS$POSIX_ROOT to be defined.
+
+$DEFINE DECC$DISABLE_POSIX_ROOT "ENABLE"
Once you issue your MMS or MMK command, sit back and wait. Perl should
compile and link without a problem. If a problem does occur check the
@@ -312,7 +542,16 @@
This step is very important since there are always things that can go wrong
somehow and yield a dysfunctional Perl for you.
-Testing is very easy, though, as there's a full test suite in the perl
+For Perl built on systems that support hard links on an ODS-5 volume with
+hard links enabled, the feature logical DECC$FILE_PERMISSION_UNIX must
+be enabled.
+
+ $DEFINE DECC$FILE_PERMISSION_UNIX "ENABLE"
+
+Otherwise some of the tests will fail. For running Perl, you may set this
+feature logical to what ever your site requires.
+
+Testing is very easy, though, as there's a full test suite in the Perl
distribution. To run the tests, enter the *exact* MMS line you used to
compile Perl and add the word "test" to the end, like this:
@@ -340,6 +579,10 @@
built; otherwise the manipulations of temporary files and directories
attempted by some of the tests will fail.
+Another interesting side effect of this wrapper is that some tests will be
+silently skipped as they require elevated privileges to run. If you are
+concerned about these tests, you must run them with out the DCL wrapper.
+
If any tests fail, it means something is wrong with Perl. If the test suite
hangs (some tests can take upwards of two or three minutes, or more if
you're on an especially slow machine, depending on your machine speed, so
@@ -367,6 +610,9 @@
@ [.VMS]TEST .EXE "" -"v" [-.lib.math]trig.t
+Please be aware that some of the tests that output UNICODE sequences will
+lock up a DECTERM when run in the "-v" or verbose mode.
+
When you send in a bug report for failed tests, please include the output
from this command, which is run from the main source directory:
@@ -434,6 +680,20 @@
there, so make sure that you have write access to the parent directory of
what will become the root of your Perl installation.
+If the PCSI_PRODUCER logical name was set when the CONFIGURE step is run,
+the PERL_SETUP.COM that is generated will set up the PERL_ROOT based on the
+directory that the PERL_SETUP.COM currently resides in. This is to allow a
+binary kit to be built that can be easily moved to another location.
+
+This is intended for use with the command procedure BUILD_BIN_SYMLINK_PERL.COM,
+which will also produce a backup save set for a binary kit.
+
+When the PCSI_PRODUCER logical name is defined to name like "USER", the
+BUILD_BIN_SYMLINK_PERL.COM will run from the "CONFIGURE" stage through the
+INSTALL phase and build a backup save set. With out the PCSI_PRODUCER logical
+name being set, the command procedure will stop after the "TEST" phase.
+
+
=item 3
Run the install script via:
@@ -449,13 +709,18 @@
=back
-Copy PERL_SETUP.COM to a place accessible to your perl users.
+The PERL_SETUP.COM that is provided with the binary kits provided by HP needs
+to be left in the directory where the binary kit is installed, and run from
+there.
+
+If using a PERL_SETUP with the location of the installed Perl hardcoded into
+it copy PERL_SETUP.COM to a place accessible to your Perl users.
For example:
COPY PERL_SETUP.COM SYS$LIBRARY:
-If you want to have everyone on the system have access to perl
+If you want to have everyone on the system have access to Perl
then add a line that reads
$ @sys$library:perl_setup
@@ -520,7 +785,7 @@
=head2 Running h2ph to create perl header files (optional) on VMS
-If using DEC C or Compaq C ensure that you have extracted loose versions
+If using DEC C (now HP C) ensure that you have extracted loose versions
of your compiler's header or *.H files. Be sure to check the contents of:
SYS$LIBRARY:DECC$RTLDEF.TLB
@@ -566,7 +831,7 @@
build. Solutions include renaming files and directories as needed or
being careful to use the -o switch or /ODS2 qualifier with latter
versions of the vmstar utility when unpacking perl or CPAN modules
-on ODS-5 volumes.
+on ODS-5 volumes, or enabling the DECC$EFS_CHARSET feature logical.
Be sure that the process that you use to build perl has a PGFLQ greater
than 100000. Be sure to have a correct local time zone to UTC offset
@@ -612,12 +877,12 @@
Perl exited. This is fixed by DEC CSC patch ALPACRT04_061 or later.
See also:
- http://ftp.support.compaq.com/patches/.new/openvms.shtml
+ http://ftp.itrc.hp.com/openvms_patches/
=back
Please note that in later versions "DEC C" may also be known as
-"Compaq C".
+"Compaq C" and now "HP C".
=head2 GNU issues with Perl on VMS
@@ -625,9 +890,13 @@
were used to build perl on VMS. Hence they may require a great deal
of source code modification to work again.
- http://slacvx.slac.stanford.edu/HELP/GCC
- http://www.progis.de/
- http://www.lp.se/products/gnu.html
+ http://www.levitte.org/~ava/vms_gnu.htmlx
+ ftp://ftp.tmk.com/vms-freeware/gcc-for-alpha/
+ ftp://ftp.qsl.net/pub/wb8tyw/gcc281_u/
+
+ http://slacvx.slac.stanford.edu/HELP/GCC (No response when tested)
+ http://www.progis.de/ (No GCC links found when tested)
+ http://www.lp.se/products/gnu.html (No GCC links found when tested)
=head2 Floating Point Considerations
@@ -641,6 +910,9 @@
doubles respectively. The available non-default options are G_FLOAT on VAX
and D_FLOAT or G_FLOAT on Alpha.
+On I64 IEEE floating point is the default for the C compiler, and using the
+other floating point types is not recommend as they are emulated in software.
+
The use of IEEE on Alpha introduces NaN, infinity, and denormalization
capabilities not available with D_FLOAT and G_FLOAT. When using one of those
non-IEEE formats, silent underflow and overflow are emulated in the conversion
@@ -744,7 +1016,9 @@
http://www-ang.kfunigraz.ac.at/~binder/perl.html
http://lists.perl.org/showlist.cgi?name=vmsperl
http://archive.develooper.com/vmsperl@perl.org/
- http://www.openvms.compaq.com/openvms/products/ips/apache/csws_modperl.html
+ http://www.hp.com/go/openvms/ and navigate to the sidebar link of
+ "OpenVMS Software" and then to the sidebar link of
+ "Opensource tools"
=head1 SEE ALSO
@@ -755,6 +1029,7 @@
=head1 AUTHORS
+Revised 30-June-2005 by John Malmberg [EMAIL PROTECTED]
Revised 10-October-2001 by Craig Berry [EMAIL PROTECTED]
Revised 25-February-2000 by Peter Prymmer [EMAIL PROTECTED]
Revised 27-October-1999 by Craig Berry [EMAIL PROTECTED]
