=head1 NAME
-README.vms - Configuring, building, testing, and installing perl on VMS
+perlvms - Configuring, building, testing, and installing perl on VMS
=head1 SYNOPSIS
=head2 Important safety tip
-The build and install procedures have changed significantly from the 5.004
-releases! Make sure you read the "Configuring the Perl Build", "Building
-Perl", and "Installing Perl" sections of this document before you build or
-install.
+For best results, make sure you read the "Configuring the Perl Build",
+"Building Perl", and "Installing Perl" sections of this document before
+you build or install. Also please note other changes in the current
+release by having a look at L<perldelta/VMS>.
Also note that, as of Perl version 5.005 and later, an ANSI C compliant
-compiler is required to build Perl. VAX C is *not* ANSI compliant, as it
+compiler is required to build Perl. VAX C is I<not> ANSI compliant, as it
died a natural death some time before the standard was set. Therefore
-VAX C will not compile perl 5.005. We are sorry about that.
+VAX C will not compile Perl 5.005 or later. We are sorry about that.
-If you are stuck without DEC C (the VAX C license should be good for DEC C,
-but the media charges might prohibit an upgrade), consider getting Gnu C
-instead.
+There have been no recent reports of builds using Gnu C, but latent
+(and most likely outdated) support for it is still present in various
+parts of the sources. Currently the HP (formerly Compaq, and even
+more formerly DEC) C compiler is the only viable alternative for
+building Perl.
+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">).
-=head2 Introduction
+
+=head2 Introduction to Perl on VMS
The VMS port of Perl is as functionally complete as any other Perl port
(and as complete as the ports on some Unix systems). The Perl binaries
could use modules implementing useful VMS system services, so if you'd like
to lend a hand we'd love to have you. Join the Perl Porting Team Now!
-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.
-
-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
-document.
-
-=head2 Other required software
+=head2 Other required software for Compiling Perl on VMS
In addition to VMS and DCL you will need two things:
=item 1 A C compiler.
-DEC C or gcc for VMS (AXP or VAX).
+HP (formerly Compaq, more formerly DEC) C for VMS (VAX, Alpha, or Itanium).
+Various ancient versions of DEC C had some caveats, so if you're using a
+version older than 7.x on Alpha or Itanium or 6.x on VAX, you may need to
+upgrade to get a successful build.
=item 2 A make tool.
-DEC's MMS (v2.6 or later), or MadGoat's free MMS
-analog MMK (available from ftp.madgoat.com/madgoat) both work
-just fine. Gnu Make might work, but it's been so long since
-anyone's tested it that we're not sure. MMK is free though, so
-go ahead and use that.
+HP's MMS may work, but MadGoat's free MMS analog MMK (available from
+http://www.kednos.com/kednos/Resources/MMK) has consistently worked
+better. Gnu Make might work, but it's been so long since anyone's tested
+it that we're not sure. MMK is free though, so go ahead and use that.
=back
-=head2 Additional software that is optional
+=head2 Additional software that is optional for Perl on VMS
You may also want to have on hand:
=over 4
-=item 1 GUNZIP/GZIP.EXE for VMS
+=item 1 GUNZIP/GZIP for VMS
A de-compressor for *.gz and *.tgz files available from a number
-of web/ftp sites.
+of web/ftp sites and is distributed on the OpenVMS Freeware CD-ROM
+from HP.
- http://www.fsf.org/order/ftp.html
- ftp://ftp.uu.net/archive/systems/gnu/diffutils*.tar.gz
- ftp://gatekeeper.dec.com/pub/GNU/diffutils*.tar.gz
- ftp://ftp.gnu.org/pub/gnu/diffutils*.tar.gz
- http://www.openvms.digital.com/cd/GZIP/
- ftp://ftp.digital.com/pub/VMS/
+ http://www.hp.com/go/openvms/freeware/
=item 2 VMS TAR
For reading and writing unix tape archives (*.tar files). Vmstar is also
-available from a number of web/ftp sites.
+available from a number of web/ftp sites and is distributed on the OpenVMS
+Freeware CD-ROM from HP.
+
+ http://www.hp.com/go/openvms/freeware/
- ftp://ftp.lp.se/vms/
- http://www.openvms.digital.com/cd/VMSTAR/
- ftp://ftp.digital.com/pub/VMS/
+Recent versions of VMS tar on ODS-5 volumes may extract tape archive
+files with ^. escaped periods in them. See below for further workarounds.
-=item 3 UNZIP.EXE for VMS
+A port of GNU tar is also available as part of the GNV package:
+
+ http://h71000.www7.hp.com/opensource/gnv.html
+
+=item 3 UNZIP for VMS
A combination decompressor and archive reader/writer for *.zip files.
Unzip is available from a number of web/ftp sites.
- http://www.cdrom.com/pub/infozip/UnZip.html
- http://www.openvms.digital.com/cd/INFO-ZIP/
- ftp://ftp.digital.com/pub/VMS/
- ftp://ftp.openvms.digital.com/
- ftp://ftp.madgoat.com/madgoat/
- ftp://ftp.wku.edu/vms/
+ http://www.info-zip.org/UnZip.html
+ http://www.hp.com/go/openvms/freeware/
+ ftp://ftp.process.com/vms-freeware/fileserv/
-=item 4 MOST
+=item 5 GNU PATCH and DIFFUTILS for VMS
-Most is an optional pager that is convenient to use with perldoc (unlike
-TYPE/PAGE, MOST can go forward and backwards in a document and supports
-regular expression searching). Most builds with the slang
-library on VMS. Most and slang are available from:
+Patches to Perl are usually distributed as GNU unified or contextual diffs.
+Such patches are created by the GNU diff program (part of the diffutils
+distribution) and applied with GNU patch. VMS ports of these utilities are
+available here:
- ftp://space.mit.edu/pub/davis/
- ftp://ftp.wku.edu/vms/narnia/most.zip
+ http://www.antinode.info/dec/sw/diffutils.html
+ http://www.hp.com/go/openvms/freeware/
=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 format (this includes copies 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.
+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
+wish to add later) hence you probably want to have GUNZIP.EXE and
+VMSTAR.EXE on your VMS machine.
If you want to include socket support, you'll need a TCP/IP stack and either
DEC C, or socket libraries. See the "Socket Support (optional)" topic
for more details.
+=head1 Unpacking the Perl source code
+
+You may need to set up a foreign symbol for the unpacking utility of choice.
+
+As of version 5.10.0, Perl will still build and run on ODS-2 volumes,
+including on VAX, but there are a number of modules whose temporary
+files and tests are much happier residing on ODS-5 volumes. For
+example, CPANPLUS will fail most of its tests on an ODS-2 volume because
+it includes files with multiple dots that will have been converted to
+underscores and the tests will have difficulty finding them. So your
+best bet is to unpack the Perl source kit on an ODS-5 volume using
+recent versions of vmstar (e.g. V3.4 or later). Contrary to advice
+provided with previous versions of Perl, do I<not> use the ODS-2
+compatibility qualifier. Instead, use a command like the following:
+
+ vmstar -xvf perl-5^.17^.0.tar
+
+Then rename the top-level source directory like so:
+
+ set security/protection=(o:rwed) perl-5^.17^.0.dir
+ rename perl-5^.17^.0.dir perl-5_17_0.dir
+
+The reason for this last step is that while filenames with multiple dots
+are generally supported by Perl on VMS, I<directory> names with multiple
+dots are a special case with special problems because the dot is the
+traditional directory delimiter on VMS. Rudimentary support for
+multi-dot directory names is available, but some of the oldest and most
+essential parts of Perl (such as searching for and loading library
+modules) do not yet fully support the ODS-5 caret-escape syntax.
+
=head1 Configuring the Perl build
To configure perl (a necessary first step), issue the command
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
-which one to use. Various older versions of DEC C had some caveats, so if
-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
will try to warn you about them. If a logical name is causing
otherwise simply deassign the dangerous logical names. The potentially
troublesome logicals and symbols are:
- TMP "LOGICAL"
- LIB "LOGICAL"
- T "LOGICAL"
- FOO "LOGICAL"
- EXT "LOGICAL"
- TEST "SYMBOL"
+ COMP "LOGICAL"
+ EXT "LOGICAL"
+ FOO "LOGICAL"
+ LIB "LOGICAL"
+ LIST "LOGICAL"
+ MIME "LOGICAL"
+ POSIX "LOGICAL"
+ SYS "LOGICAL"
+ T "LOGICAL"
+ THREAD "LOGICAL"
+ THREADS "LOGICAL"
+ TIME "LOGICAL"
+ TMP "LOGICAL"
+ UNICODE "LOGICAL"
+ UTIL "LOGICAL"
+ TEST "SYMBOL"
As a handy shortcut, the command:
@ Configure "-des"
(note the quotation marks and case) will choose reasonable defaults
-automatically (it takes DEC C over Gnu C, DEC C sockets over SOCKETSHR
-sockets, and either over no sockets). More help with configure.com is
-available from:
+automatically. Some options can be given explicitly on the command line;
+the following example specifies a non-default location for where Perl
+will be installed:
+
+ @ 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
+source into:
+
+ DKA200:[PERL-5_10_2...]
+
+Then the PERL_SETUP.COM that gets written out by CONFIGURE.COM will
+try to DEFINE your installation PERL_ROOT to be:
+
+ DKA200:[PERL-5_10_2_ROOT.]
+
+More help with configure.com is available from:
@ Configure "-h"
fresh (optional)" and the checklist of items in the "CAVEATS" sections
below.
-=head2 Changing compile-time options (optional)
+=head2 Changing compile-time options (optional) for Perl on VMS
Most of the user definable features of Perl are enabled or disabled in
-[.VMS]CONFIG.VMS. 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 CONFIG.VMS can render perl
-unbuildable.
+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
+unbuildable; odds are that there's nothing in there you'll need to
+change.
-Odds are that there's nothing here to change, unless you're on a version of
-VMS later than 6.2 and DEC C later than 5.6. Even if you are, the correct
-values will still be chosen, most likely. Poking around here should be
-unnecessary.
-
-The one exception is the various *DIR install locations. Changing those
-requires changes in genconfig.pl as well. Be really careful if you need to
-change these, as they can cause some fairly subtle problems.
-
-=head2 Socket Support (optional)
+=head2 Socket Support (optional) for Perl on VMS
Perl includes a number of functions for IP sockets, which are available if
-you choose to compile Perl with socket support. Since IP networking is an
-optional addition to VMS, there are several different IP stacks available.
-How well integrated they are into the system depends on the stack, your
-version of VMS, and the version of your C compiler.
-
-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
-all the compilers on both VAX and Alpha. The socket interface is also
-consistent across versions of VMS and C compilers. It has a problem with
-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.
+you choose to compile Perl with socket support. It does this via the socket
+routines built into the CRTL regarless of which TCP/IP stack your system
+has.
=head1 Building Perl
somehow and yield a dysfunctional Perl for you.
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
+distribution. To run the tests, enter the I<exact> MMS line you used to
compile Perl and add the word "test" to the end, like this:
If the compile command was:
At the end of all the tests, a summary of the tests, the number passed and
failed, and the time taken will be displayed.
-If any tests fail, it means something is wrong with Perl. If the test suite
+The test driver invoked via MMS TEST has a DCL wrapper ([.VMS]TEST.COM) that
+downgrades privileges to NETMBX, TMPMBX for the duration of the test run,
+and then restores them to their prior state upon completion of testing.
+This is done to ensure that the tests run in a private sandbox and can do no
+harm to your system even in the unlikely event something goes badly wrong in
+one of the test scripts while running the tests from a privileged account.
+A side effect of this safety precaution is that the account used to run the
+test suite must be the owner of the directory tree in which Perl has been
+built; otherwise the manipulations of temporary files and directories
+attempted by some of the tests will fail.
+
+If any tests fail, it means something is wrong with Perl, or at least
+with the particular module or feature that reported failure. 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
-don't be hasty), then the test *after* the last one displayed failed. Don't
+don't be hasty), then the test I<after> the last one displayed failed. Don't
install Perl unless you're confident that you're OK. Regardless of how
confident you are, make a bug report to the VMSPerl mailing list.
where ".typ" is the file type of the Perl images you just built (if you
didn't do anything special, use .EXE), and "[.subdir]test.T" is the test
that failed. For example, with a normal Perl build, if the test indicated
-that [.op]time failed, then you'd do this:
+that t/op/time failed, then you'd do this:
@ [.VMS]TEST .EXE "" "-v" [.OP]TIME.T
+Note that test names are reported in UNIX syntax and relative to the
+top-level build directory. When supplying them individually to the test
+driver, you can use either UNIX or VMS syntax, but you must give the path
+relative to the [.T] directory and you must also add the .T extension to the
+filename. So, for example if the test lib/Math/Trig fails, you would run:
+
+ @ [.VMS]TEST .EXE "" -"v" [-.lib.math]trig.t
+
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:
MMK you are running try "MMS/ident" or "MMK /ident". The GNU make version
can be identified with "make --version".
-=head2 Cleaning up and starting fresh (optional)
+=head2 Cleaning up and starting fresh (optional) installing Perl on VMS
If you need to recompile from scratch, you have to make sure you clean up
-first. There is a procedure to do it--enter the *exact* MMS line you used
+first. There is a procedure to do it--enter the I<exact> MMS line you used
to compile and add "realclean" at the end, like this:
if the compile command was:
=item 2
-Create a directory somewhere and either run @perl_setup or
-define the concealed logical PERL_ROOT to point to it by hand.
-For example,
-
- CREATE/DIRECTORY dka200:[perl]
- @PERL_SETUP
- SHOW LOGICAL PERL_ROOT
-
-or,
-
- CREATE/DIRECTORY dka200:[perl]
- DEFINE/TRANS=(CONC,TERM) PERL_ROOT dka200:[perl.]
+Decide where you want Perl to be installed (unless you have already done so
+by using the "prefix" configuration parameter -- see the example in the
+"Configuring the Perl build" section).
+The DCL script PERL_SETUP.COM that is written by CONFIGURE.COM will help you
+with the definition of the PERL_ROOT and PERLSHR logical names and the PERL
+foreign command symbol. Take a look at PERL_SETUP.COM and modify it if you
+want to. The installation process will execute PERL_SETUP.COM and copy
+files to the directory tree pointed to by the PERL_ROOT logical name defined
+there, so make sure that you have write access to the parent directory of
+what will become the root of your Perl installation.
=item 3
=back
-The DCL script PERL_SETUP.COM that is written by CONFIGURE.COM
-will help you with the definition of PERL_ROOT, PERLSHR and the PERL
-Foreign symbol. Take a look at PERL_SETUP.COM and modify it if you want
-to. Then copy PERL_SETUP.COM to a place accessible to your perl users.
+Copy PERL_SETUP.COM to a place accessible to your perl users.
+
For example:
COPY PERL_SETUP.COM SYS$LIBRARY:
See also the "INSTALLing images (optional)" section.
-=head2 Installing Perl into DCLTABLES (optional)
+=head2 Installing Perl into DCLTABLES (optional) on VMS
Execute the following command file to define PERL as a DCL command.
You'll need CMKRNL privilege to install the new dcltables.exe.
$ install replace sys$common:[syslib]dcltables.exe
$ exit
-=head2 INSTALLing images (optional)
+=head2 INSTALLing Perl images (optional) on VMS
On systems that are using perl quite a bit, and particularly those with
minimal RAM, you can boost the performance of perl by INSTALLing it as
-a known image. PERLSHR.EXE is typically larger than 2000 blocks
+a known image. PERLSHR.EXE is typically larger than 3000 blocks
and that is a reasonably large amount of IO to load each time perl is
invoked.
If your code 'use's modules, check to see if there is a shareable image for
them, too. In the base perl build, POSIX, IO, Fcntl, Opcode, SDBM_File,
-DCLsym, and Stdio all have shared images that can be installed /SHARE.
+DCLsym, and Stdio, and other extensions all have shared images that can be
+installed /SHARE.
How much of a win depends on your memory situation, but if you are firing
off perl with any regularity (like more than once every 20 seconds or so)
While there is code in perl to remove privileges as it runs you are advised
to NOT INSTALL PERL.EXE with PRIVs!
+=head2 Running h2ph to create perl header files (optional) on VMS
+
+If using 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
+ SYS$LIBRARY:SYS$LIB_C.TLB
+ SYS$LIBRARY:SYS$STARLET_C.TLB
+
+etcetera.
+
+If using GNU cc then also check your GNU_CC:[000000...] tree for the locations
+of the GNU cc headers.
+
=head1 Reporting Bugs
If you come across what you think might be a bug in Perl, please report
=head1 CAVEATS
Probably the single biggest gotcha in compiling Perl is giving the wrong
-switches to MMS/MMK when you build. Use *exactly* what the configure.com
+switches to MMS/MMK when you build. Use I<exactly> what the configure.com
script prints!
The next big gotcha is directory depth. Perl can create directories four,
five, or even six levels deep during the build, so you don't have to be
-too deep to start to hit the RMS 8 level limit (for versions of VMS prior
-to V7.2 and even with V7.2 on the VAX). It is best to do
+too deep to start to hit the RMS 8 level limit (for ODS 2 volumes which were
+common on versions of VMS prior to V7.2 and even with V7.3 on the VAX).
+It is best to do:
DEFINE/TRANS=(CONC,TERM) PERLSRC "disk:[dir.dir.dir.perldir.]"
SET DEFAULT PERLSRC:[000000]
a VAX or on Alpha versions of VMS prior to 7.2). But MakeMaker will not
warn you if you start out building a module too deep in a directory.
+As noted above ODS-5 escape sequences such as ^. can break the perl
+build. Solutions include renaming files and directories as needed
+when unpacking perl or CPAN modules on ODS-5 volumes.
+
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
defined (in seconds) in the logical name SYS$TIMEZONE_DIFFERENTIAL before
build. If things go wrong make sure you do a "(MMK|MMS|make) realclean"
before you rebuild.
-=head2 DEC C issues
-
-Note to DEC C users: Some early versions (pre-5.2, some pre-4. If you're DEC
-C 5.x or higher, with current patches if any, you're fine) of the DECCRTL
-contained a few bugs which affect Perl performance:
-
-=over 4
-
-=item - pipes
-
-Newlines are lost on I/O through pipes, causing lines to run together.
-This shows up as RMS RTB errors when reading from a pipe. You can
-work around this by having one process write data to a file, and
-then having the other read the file, instead of the pipe. This is
-fixed in version 4 of DEC C.
-
-=item - modf()
-
-The modf() routine returns a non-integral value for some values above
-INT_MAX; the Perl "int" operator will return a non-integral value in
-these cases. This is fixed in version 4 of DEC C.
-
-=item - ALPACRT ECO
-
-On the AXP, if SYSNAM privilege is enabled, the CRTL chdir() routine
-changes the process default device and directory permanently, even
-though the call specified that the change should not persist after
-Perl exited. This is fixed by DEC CSC patch ALPACRT04_061 or later.
-See also:
-
- http://ftp.service.digital.com/patches/.new/openvms.html
-
-=back
-
-Please note that in later versions "DEC C" may also be known as
-"Compaq C".
-
-=head2 GNU issues
+=head2 GNU issues with Perl on VMS
It has been a while since the GNU utilities such as GCC or GNU make
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://vms.gnu.org/
- http://www.lp.se/products/gnu.html
+
+=head2 Floating Point Considerations
+
+Prior to 5.8.0, Perl simply accepted the default floating point options of the
+C compiler, namely representing doubles with D_FLOAT on VAX and G_FLOAT on
+Alpha. Single precision floating point values are represented in F_FLOAT
+format when either D_FLOAT or G_FLOAT is in use for doubles. Beginning with
+5.8.0, Alpha builds now use IEEE floating point formats by default, which in
+VMS parlance are S_FLOAT for singles and T_FLOAT for doubles. IEEE is not
+available on VAX, so F_FLOAT and D_FLOAT remain the defaults for singles and
+doubles respectively. Itanium builds have always used IEEE by default. The
+available non-default options are G_FLOAT on VAX and D_FLOAT or G_FLOAT on
+Alpha or Itanium.
+
+The use of IEEE on Alpha or Itanium 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
+of strings to numbers, but it is preferable to get the real thing by using
+IEEE where possible.
+
+Regardless of what floating point format you consider preferable, be aware
+that the choice may have an impact on compatibility with external libraries,
+such as database interfaces, and with existing data, such as data created with
+the C<pack> function and written to disk, or data stored via the Storable
+extension. For example, a C<pack("d", $foo)")> will create a D_FLOAT,
+G_FLOAT, or T_FLOAT depending on what your Perl was configured with. When
+written to disk, the value can only be retrieved later by a Perl configured
+with the same floating point option that was in effect when it was created.
+
+To obtain a non-IEEE build on Alpha, simply answer no to the "Use IEEE math?"
+question during the configuration. To obtain an option different from the C
+compiler default on either VAX or Alpha, put in the option that you want in
+answer to the "Any additional cc flags?" question. For example, to obtain a
+G_FLOAT build on VAX, put in C</FLOAT=G_FLOAT>.
=head1 Mailing Lists
there is the VMSPERL mailing list. It is usually a low-volume (10-12
messages a week) mailing list.
-The subscription address is MAJORDOMO@PERL.ORG. Send a mail message with
-just the words SUBSCRIBE VMSPERL in the body of the message.
-
-The VMSPERL mailing list address is VMSPERL@PERL.ORG. Any mail sent there
-gets echoed to all subscribers of the list. There is a searchable archive of
-the list on the web at:
+To subscribe, send a mail message to VMSPERL-SUBSCRIBE@PERL.ORG. The VMSPERL
+mailing list address is VMSPERL@PERL.ORG. Any mail sent there gets echoed
+to all subscribers of the list. There is a searchable archive of the list
+on the web at:
http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
-
-To unsubscribe from VMSPERL send the message UNSUBSCRIBE VMSPERL to
-MAJORDOMO@PERL.ORG. Be sure to do so from the subscribed account that
-you are canceling.
-=head2 Web sites
+To unsubscribe from VMSPERL send a message to VMSPERL-UNSUBSCRIBE@PERL.ORG.
+Be sure to do so from the subscribed account that you are canceling.
+
+=head2 Web sites for Perl on VMS
Vmsperl pages on the web include:
http://www.sidhe.org/vmsperl/index.html
- http://duphy4.physics.drexel.edu/pub/cgi_info.htmlx
- http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
http://www.cpan.org/modules/by-module/VMS/
- http://nucwww.chem.sunysb.edu/htbin/software_list.cgi
- http://www.best.com/~pvhp/vms/
- http://bkfug.kfunigraz.ac.at/~binder/perl.html
+ http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
+ http://www-ang.kfunigraz.ac.at/~binder/perl.html
+ http://archive.develooper.com/vmsperl@perl.org/
+ http://h71000.www7.hp.com/openvms/products/ips/apache/csws_modperl.html
=head1 SEE ALSO
Perl information for users and programmers about the port of perl to VMS is
-available from the [.
VMS]PERLVMS.POD file that gets installed as L<perlvms>.
+available from the [.
POD]PERLVMS.POD file that gets installed as L<perlvms>.
For administrators the perlvms document also includes a detailed discussion
of extending vmsperl with CPAN modules after Perl has been installed.
=head1 AUTHORS
-Last revised 25-February-2000 by Peter Prymmer pvhp@best.com.
-Revised 27-October-1999 by Craig Berry craig.berry@metamorgs.com.
-Revised 01-March-1999 by Dan Sugalski dan@sidhe.org.
-Originally by Charles Bailey bailey@newman.upenn.edu.
+Originally by Charles Bailey bailey@newman.upenn.edu. See the git repository
+for history.
=head1 ACKNOWLEDGEMENTS
the opportunity to test and develop for the AXP,
John Hasstedt John.Hasstedt@sunysb.edu
for VAX VMS V7.2 support
+ John Malmberg wb8tyw@qsl.net
+ for ODS-5 filename handling and other modernizations
and to the entire VMSperl group for useful advice and suggestions. In
addition the perl5-porters deserve credit for their creativity and
https://perl5.git.perl.org / perl5.git / blobdiff