summaryrefslogtreecommitdiff
path: root/README.os390
diff options
context:
space:
mode:
authorMike Fulton <mikefultonpersonal@gmail.com>2021-12-31 13:44:02 -0800
committerKarl Williamson <khw@cpan.org>2022-01-05 12:17:13 -0700
commitadcefe44077ee893a779279ff143a0ec267701ee (patch)
tree2e1d2c07b8b77357c87564696a40f1fec3532f66 /README.os390
parentf0ff81efc195f719dd9527c95caca27e0bc727ed (diff)
downloadperl-adcefe44077ee893a779279ff143a0ec267701ee.tar.gz
Update the README to describe ASCII and EBCDIC builds
Rewrite of the readme file to bring it up to date and to document the various ways Perl can now be built and used on z/OS.
Diffstat (limited to 'README.os390')
-rw-r--r--README.os390429
1 files changed, 139 insertions, 290 deletions
diff --git a/README.os390 b/README.os390
index 87f1094c04..c56990c120 100644
--- a/README.os390
+++ b/README.os390
@@ -1,145 +1,149 @@
This document is written in pod format hence there are punctuation
-characters in odd places. Do not worry, you have apparently got the
-ASCII->EBCDIC translation worked out correctly. You can read more
+characters in odd places. You can read more
about pod in pod/perlpod.pod or the short summary in the INSTALL file.
=head1 NAME
-perlos390 - building and installing Perl for OS/390 and z/OS
+perlos390 - building and installing Perl for z/OS (previously called OS/390)
=head1 SYNOPSIS
This document will help you Configure, build, test and install Perl
-on OS/390 (aka z/OS) Unix System Services.
-
-B<This document needs to be updated, but we don't know what it should say.
-Please submit comments to L<https://github.com/Perl/perl5/issues>.>
+on z/OS Unix System Services.
=head1 DESCRIPTION
-This is a fully ported Perl for OS/390 Version 2 Release 3, 5, 6, 7,
-8, and 9. It may work on other versions or releases, but those are
-the ones we have tested it on.
+This is a ported Perl for z/OS. It has been tested on z/OS 2.4 and
+should work fine with z/OS 2.5.
+It may work on other versions or releases, but those are
+the ones it has been tested on.
+There are many ways you can build Perl for z/OS. This document
+will describe how to build a 64-bit Dynamic EBCDIC Perl as well as a
+64-bit Dynamic ASCII Perl.
You may need to carry out some system configuration tasks before
running the Configure script for Perl.
-
=head2 Tools
-The z/OS Unix Tools and Toys list may prove helpful and contains links
-to ports of much of the software helpful for building Perl.
-L<http://www.ibm.com/servers/eserver/zseries/zos/unix/bpxa1toy.html>
+You will want to get GNU make 4.1 or later. GNU make can be downloaded from a port
+that Rocket Software provides.
+You will need the z/OS c99 compiler from IBM.
+You can also obtain a z/OS native git client port that Rocket Software
+provides. This is optional - you can use git on another platform and
+transfer the code via ftp to z/OS
+For EBCDIC only, you will need gunzip client port that Rocket Software provides
+to unzip the zipped tarball you upload to z/OS
+=head2 Building a 64-bit Dynamic ASCII Perl
-=head2 Unpacking Perl distribution on OS/390
+Using the native git on z/OS, clone Perl:
-If using ftp remember to transfer the distribution in binary format.
+ git clone https://github.com/Perl/perl5.git perl
-Gunzip/gzip for OS/390 is discussed at:
+Change into the perl directory and tag all the code as ASCII:
- http://www.ibm.com/servers/eserver/zseries/zos/unix/bpxa1ty1.html
+ cd perl
+ chtag -R -h -t -cISO8859-1 *
-to extract an ASCII tar archive on OS/390, try this:
+Configure the build environment as 64-bit, Dynamic, ASCII, development,
+deploying it to F</usr/local/perl/ascii>:
- pax -o to=IBM-1047,from=ISO8859-1 -r < latest.tar
+ export PATH=$PWD:$PATH
+ export LIBPATH=$PWD:$PATH
+ ./Configure -Dprefix=/usr/local/perl/ascii -des -Dusedevel \
+ -Duse64bitall -Dusedl
-or
+Run GNU make to build Perl
- zcat latest.tar.Z | pax -o to=IBM-1047,from=ISO8859-1 -r
+ make
-If you get lots of errors of the form
+Run tests to ensure Perl is working correctly. Currently, there are 33 failing tests out of 2479
- tar: FSUM7171 ...: cannot set uid/gid: EDC5139I Operation not permitted
+ make tests
-you did not read the above and tried to use tar instead of pax, you'll
-first have to remove the (now corrupt) perl directory
+Install Perl into F</usr/local/perl/ascii>:
- rm -rf perl-...
+ make install
-and then use pax.
+=head2 Building a 64-bit Dynamic EBCDIC Perl
-=head2 Setup and utilities for Perl on OS/390
+Using the native git on a platform other than z/OS, (e.g. Mac, Windows, Linux) clone Perl:
+
+ git clone https://github.com/Perl/perl5.git perl
+
+Change into the perl directory and modify the source so it is suitable for building on z/OS
+
+ cd perl
+ Porting/makerel -e
+
+If the Porting/makerel step fails with an error that it can not issue the tar
+command, proceed to issue the command interactively, where V.R.M is the
+version/release/modification of Perl you are uploading:
+
+ cd ../
+ tar cf - --format=ustar perl-V.R.M | gzip --best > perl-V.R.M.tar.gz
+
+Use sftp to upload the zipped tar file to z/OS:
+
+ sftp <your system>
+ cd /tmp
+ put perl-V.R.M.tar.gz
-Be sure that your yacc installation is in place including any necessary
-parser template files. If you have not already done so then be sure to:
+Unzip and untar the zipped tar file on z/OS:
- cp /samples/yyparse.c /etc
+ cd /tmp
+ gunzip perl-V.R.M.tar.gz
+ tar -xvf perl-V.R.M.tar
-This may also be a good time to ensure that your /etc/protocol file
-and either your /etc/resolv.conf or /etc/hosts files are in place.
-The IBM document that described such USS system setup issues was
-SC28-1890-07 "OS/390 UNIX System Services Planning", in particular
-Chapter 6 on customizing the OE shell.
+You now have the source code for the EBCDIC Perl on z/OS and can proceed to build it. This is analagous to how you
+would build the code for ASCII, but note: you B<should not> tag the code but instead leave it untagged.
-GNU make for OS/390, which is recommended for the build of perl (as
-well as building CPAN modules and extensions), is available from the
-L</Tools>.
+Configure the build environment as 64-bit, Dynamic, ASCII, development,
+deploying it to F</usr/local/perl/ebcdic>:
-Some people have reported encountering "Out of memory!" errors while
-trying to build Perl using GNU make binaries. If you encounter such
-trouble then try to download the source code kit and build GNU make
-from source to eliminate any such trouble. You might also find GNU make
-(as well as Perl and Apache) in the red-piece/book "Open Source Software
-for OS/390 UNIX", SG24-5944-00 from IBM.
+ export PATH=$PWD:$PATH
+ export LIBPATH=$PWD:$PATH
+ ./Configure -Dprefix=/usr/local/perl/ebcdic -des -Dusedevel \
+ -Duse64bitall -Dusedl
-If instead of the recommended GNU make you would like to use the system
-supplied make program then be sure to install the default rules file
-properly via the shell command:
+Run GNU make to build Perl
- cp /samples/startup.mk /etc
+ make
-and be sure to also set the environment variable _C89_CCMODE=1 (exporting
-_C89_CCMODE=1 is also a good idea for users of GNU make).
+Run tests to ensure Perl is working correctly. Currently, there are 99 tests failing out of 1949
-You might also want to have GNU groff for OS/390 installed before
-running the "make install" step for Perl.
+ make tests
-There is a syntax error in the /usr/include/sys/socket.h header file
-that IBM supplies with USS V2R7, V2R8, and possibly V2R9. The problem with
-the header file is that near the definition of the SO_REUSEPORT constant
-there is a spurious extra '/' character outside of a comment like so:
+Install Perl into F</usr/local/perl/ebcdic>:
- #define SO_REUSEPORT 0x0200 /* allow local address & port
- reuse */ /
+ make install
-You could edit that header yourself to remove that last '/', or you might
-note that Language Environment (LE) APAR PQ39997 describes the problem
-and PTF's UQ46272 and UQ46271 are the (R8 at least) fixes and apply them.
-If left unattended that syntax error will turn up as an inability for Perl
-to build its "Socket" extension.
+=head2 Setup and utilities for Perl on OS/390
+
+This may also be a good time to ensure that your F</etc/protocol> file
+and either your F</etc/resolv.conf> or F</etc/hosts> files are in place.
+The IBM document that describes such USS system setup issues is
+"z/OS UNIX System Services Planning"
For successful testing you may need to turn on the sticky bit for your
world readable /tmp directory if you have not already done so (see man chmod).
-=head2 Configure Perl on OS/390
+=head2 Useful files for trouble-shooting
-Once you have unpacked the distribution, run "sh Configure" (see INSTALL
-for a full discussion of the Configure options). There is a "hints" file
-for os390 that specifies the correct values for most things. Some things
-to watch out for include:
+If your configuration is failing, read hints/os390.sh
+This file provides z/OS specific options to direct the build process.
=head3 Shell
A message of the form:
(I see you are using the Korn shell. Some ksh's blow up on Configure,
- mainly on older exotic systems. If yours does, try the Bourne shell instead.)
+ mainly on older exotic systems. If yours does, try the Bourne shell
+ instead.)
is nothing to worry about at all.
-=head3 Samples
-
-Some of the parser default template files in /samples are needed in /etc.
-In particular be sure that you at least copy /samples/yyparse.c to /etc
-before running Perl's Configure. This step ensures successful extraction
-of EBCDIC versions of parser files such as perly.c and perly.h.
-This has to be done before running Configure the first time. If you failed
-to do so then the easiest way to re-Configure Perl is to delete your
-misconfigured build root and re-extract the source from the tar ball.
-Then you must ensure that /etc/yyparse.c is properly in place before
-attempting to re-run Configure.
-
=head3 Dynamic loading
Dynamic loading is required if you want to use XS modules from CPAN (like
@@ -147,96 +151,25 @@ DBI (and DBD's), JSON::XS, and Text::CSV_XS) or update CORE modules from
CPAN with newer versions (like Encode) without rebuilding all of the perl
binary.
-This port will support dynamic loading, but it is not selected by
-default. If you would like to experiment with dynamic loading then
-be sure to specify -Dusedl in the arguments to the Configure script.
+The instructions above will create a dynamic Perl. If you do not want to
+use dynamic loading, remove the -Dusedl option.
See the comments in hints/os390.sh for more information on dynamic loading.
-If you build with dynamic loading then you will need to add the
-$archlibexp/CORE directory to your LIBPATH environment variable in order
-for perl to work. See the config.sh file for the value of $archlibexp.
-If in trying to use Perl you see an error message similar to:
-
- CEE3501S The module libperl.dll was not found.
- From entry point __dllstaticinit at compile unit offset +00000194
- at
-
-then your LIBPATH does not have the location of libperl.x and either
-libperl.dll or libperl.so in it. Add that directory to your LIBPATH and
-proceed.
-
-In hints/os390.sh, selecting -Dusedl will default to *also* select
--Duseshrplib. Having a shared plib not only requires LIBPATH to be set to
-the correct location of libperl.so but also makes it close to impossible
-to run more than one different perl that was built this way at the same
-time.
-
-All objects that are involved in -Dusedl builds should be compiled for
-this, probably by adding to all ccflags
-
- -qexportall -qxplink -qdll -Wc,XPLINK,dll,EXPORTALL -Wl,XPLINK,dll
=head3 Optimizing
-Do not turn on the compiler optimization flag "-O". There is
-a bug in either the optimizer or perl that causes perl to
-not work correctly when the optimizer is on.
-
-=head3 Config files
-
-Some of the configuration files in /etc used by the
-networking APIs are either missing or have the wrong
-names. In particular, make sure that there's either
-an /etc/resolv.conf or an /etc/hosts, so that
-gethostbyname() works, and make sure that the file
-/etc/proto has been renamed to /etc/protocol (NOT
-/etc/protocols, as used by other Unix systems).
-You may have to look for things like HOSTNAME and DOMAINORIGIN
-in the "//'SYS1.TCPPARMS(TCPDATA)'" PDS member in order to
-properly set up your /etc networking files.
-
-=head2 Build, Test, Install Perl on OS/390
-
-Simply put:
-
- sh Configure
- make
- make test
-
-if everything looks ok (see the next section for test/IVP diagnosis) then:
-
- make install
-
-this last step may or may not require UID=0 privileges depending
-on how you answered the questions that Configure asked and whether
-or not you have write access to the directories you specified.
+Optimization has not been turned on yet. There may be issues if Perl
+is optimized.
=head2 Build Anomalies with Perl on OS/390
"Out of memory!" messages during the build of Perl are most often fixed
by re building the GNU make utility for OS/390 from a source code kit.
-Building debugging-enabled binaries (with -g or -g3) will increase the
-chance of getting these errors. Prevent -g if possible.
-
-Another memory limiting item to check is your MAXASSIZE parameter in your
-'SYS1.PARMLIB(BPXPRMxx)' data set (note too that as of V2R8 address space
-limits can be set on a per user ID basis in the USS segment of a RACF
-profile). People have reported successful builds of Perl with MAXASSIZE
-parameters as small as 503316480 (and it may be possible to build Perl
-with a MAXASSIZE smaller than that).
-
-Within USS your /etc/profile or $HOME/.profile may limit your ulimit
+Within USS your F</etc/profile> or F<$HOME/.profile> may limit your ulimit
settings. Check that the following command returns reasonable values:
ulimit -a
-To conserve memory you should have your compiler modules loaded into the
-Link Pack Area (LPA/ELPA) rather than in a link list or step lib.
-
-If the c89 compiler complains of syntax errors during the build of the
-Socket extension then be sure to fix the syntax error in the system
-header /usr/include/sys/socket.h.
-
=head2 Testing Anomalies with Perl on OS/390
The "make test" step runs a Perl Verification Procedure, usually before
@@ -244,44 +177,19 @@ installation. You might encounter STDERR messages even during a successful
run of "make test". Here is a guide to some of the more commonly seen
anomalies:
-=head3 Signals
-
-A message of the form:
-
- io/openpid...........CEE5210S The signal SIGHUP was received.
- CEE5210S The signal SIGHUP was received.
- CEE5210S The signal SIGHUP was received.
- ok
-
-indicates that the t/io/openpid.t test of Perl has passed but done so
-with extraneous messages on stderr from CEE.
+=head3 Out of Memory (31-bit only)
-=head3 File::Temp
-
-A message of the form:
+Out of memory problems should not be an issue, unless you are attempting to build
+a 31-bit Perl.
- lib/ftmp-security....File::Temp::_gettemp: Parent directory (/tmp/)
- is not safe (sticky bit not set when world writable?) at
- lib/ftmp-security.t line 100
- File::Temp::_gettemp: Parent directory (/tmp/) is not safe (sticky
- bit not set when world writable?) at lib/ftmp-security.t line 100
- ok
-
-indicates a problem with the permissions on your /tmp directory within the HFS.
-To correct that problem issue the command:
-
- chmod a+t /tmp
-
-from an account with write access to the directory entry for /tmp.
-
-=head3 Out of Memory!
-
-Recent perl test suite is quite memory hungry. In addition to the comments
+If you _are_ building a 31-bit Perl, the constrained environment may mean you
+need to change memory options for Perl.
+In addition to the comments
above on memory limitations it is also worth checking for _CEE_RUNOPTS
-in your environment. Perl now has (in miniperlmain.c) a C #pragma
+in your environment. Perl now has (in miniperlmain.c) a C #pragma for 31-bit only
to set CEE run options, but the environment variable wins.
-The C code asks for:
+The 31-bit C code asks for:
#pragma runopts(HEAP(2M,500K,ANYWHERE,KEEP,8K,4K) STACK(,,ANY,) ALL31(ON))
@@ -300,69 +208,18 @@ case something like:
is needed to get through the test suite.
-=head2 Installation Anomalies with Perl on OS/390
+=head2 Usage Hints for Perl on z/OS
-The installman script will try to run on OS/390. There will be fewer errors
-if you have a roff utility installed. You can obtain GNU groff from the
-Redbook SG24-5944-00 ftp site.
-
-=head2 Usage Hints for Perl on OS/390
-
-When using perl on OS/390 please keep in mind that the EBCDIC and ASCII
+When using Perl on z/OS please keep in mind that the EBCDIC and ASCII
character sets are different. See perlebcdic.pod for more on such character
set issues. Perl builtin functions that may behave differently under
EBCDIC are also mentioned in the perlport.pod document.
-Open Edition (UNIX System Services) from V2R8 onward does support
-#!/path/to/perl script invocation. There is a PTF available from
-IBM for V2R7 that will allow shell/kernel support for #!. USS
-releases prior to V2R7 did not support the #! means of script invocation.
-If you are running V2R6 or earlier then see:
-
- head `whence perldoc`
-
-for an example of how to use the "eval exec" trick to ask the shell to
-have Perl run your scripts on those older releases of Unix System Services.
-
If you are having trouble with square brackets then consider switching your
rlogin or telnet client. Try to avoid older 3270 emulators and ISHELL for
working with Perl on USS.
-=head2 Floating Point Anomalies with Perl on OS/390
-
-There appears to be a bug in the floating point implementation on S/390
-systems such that calling int() on the product of a number and a small
-magnitude number is not the same as calling int() on the quotient of
-that number and a large magnitude number. For example, in the following
-Perl code:
-
- my $x = 100000.0;
- my $y = int($x * 1e-5) * 1e5; # '0'
- my $z = int($x / 1e+5) * 1e5; # '100000'
- print "\$y is $y and \$z is $z\n"; # $y is 0 and $z is 100000
-
-Although one would expect the quantities $y and $z to be the same and equal
-to 100000 they will differ and instead will be 0 and 100000 respectively.
-
-The problem can be further examined in a roughly equivalent C program:
-
- #include <stdio.h>
- #include <math.h>
- main()
- {
- double r1,r2;
- double x = 100000.0;
- double y = 0.0;
- double z = 0.0;
- x = 100000.0 * 1e-5;
- r1 = modf (x,&y);
- x = 100000.0 / 1e+5;
- r2 = modf (x,&z);
- printf("y is %e and z is %e\n",y*1e5,z*1e5);
- /* y is 0.000000e+00 and z is 1.000000e+05 (with c89) */
- }
-
-=head2 Modules and Extensions for Perl on OS/390
+=head2 Modules and Extensions for Perl on z/OS (Static Only)
Pure Perl (that is non XS) modules may be installed via the usual:
@@ -373,7 +230,7 @@ Pure Perl (that is non XS) modules may be installed via the usual:
If you built perl with dynamic loading capability then that would also
be the way to build XS based extensions. However, if you built perl with
-the default static linking you can still build XS based extensions for OS/390
+static linking you can still build XS based extensions for z/OS
but you will need to follow the instructions in ExtUtils::MakeMaker for
building statically linked perl binaries. In the simplest configurations
building a static perl + XS extension boils down to:
@@ -385,17 +242,30 @@ building a static perl + XS extension boils down to:
make install
make -f Makefile.aperl inst_perl MAP_TARGET=perl
-In most cases people have reported better results with GNU make rather
-than the system's /bin/make program, whether for plain modules or for
-XS based extensions.
+=head2 Running Perl on z/OS
-If the make process encounters trouble with either compilation or
-linking then try setting the _C89_CCMODE to 1. Assuming sh is your
-login shell then run:
+To run the 64-bit Dynamic Perl environment, update your PATH and LIBPATH
+to include the location you installed Perl into, and then run the perl you
+installed as perlV.R.M where V/R/M is the Version/Release/Modification level
+of the current development level.
+If you are running the ASCII/EBCDIC Bi-Modal Perl environment, you also need to set up
+your ASCII/EBCDIC Bi-Modal environment variables, and ensure
+any Perl source code you run is tagged appropriately as ASCII or EBCDIC
+using chtag -t -c<CCSID>:
- export _C89_CCMODE=1
+=head3 For ASCII Only:
-If tcsh is your login shell then use the setenv command.
+ export _BPXK_AUTOCVT=ON
+ export _CEE_RUNOPTS="FILETAG(AUTOCVT,AUTOTAG),POSIX(ON)"
+ export _TAG_REDIR_ERR="txt"
+ export _TAG_REDIR_IN="txt"
+ export _TAG_REDIR_OUT="txt"
+
+=head3 For ASCII or EBCDIC:
+
+ export PATH=/usr/local/perl/ascii:$PATH
+ export LIBPATH=/usr/local/perl/ascii/lib:$LIBPATH
+ perlV.R.M args
=head1 AUTHORS
@@ -405,54 +275,33 @@ Thanks to Mike MacIsaac and Egon Terwedow for SG24-5944-00.
Thanks to Ignasi Roca for pointing out the floating point problems.
Thanks to John Goodyear for dynamic loading help.
-=head1 SEE ALSO
-
-L<INSTALL>, L<perlport>, L<perlebcdic>, L<ExtUtils::MakeMaker>.
-
- http://www.ibm.com/servers/eserver/zseries/zos/unix/bpxa1toy.html
-
- http://www.redbooks.ibm.com/redbooks/SG245944.html
-
- http://www.ibm.com/servers/eserver/zseries/zos/unix/bpxa1ty1.html#opensrc
-
- http://www.xray.mpe.mpg.de/mailing-lists/perl-mvs/
-
- http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/ceea3030/
-
- http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/CBCUG030/
-
-=head2 Mailing list for Perl on OS/390
+Mike Fulton and Karl Williamson have provided updates for UTF8, DLL, 64-bit and ASCII/EBCDIC Bi-Modal support
-If you are interested in the z/OS (formerly known as OS/390)
-and POSIX-BC (BS2000) ports of Perl then see the perl-mvs mailing list.
-To subscribe, send an empty message to perl-mvs-subscribe@perl.org.
+=head2 Other sites
-See also:
-
- https://lists.perl.org/list/perl-mvs.html
-
-There are web archives of the mailing list at:
-
- https://www.nntp.perl.org/group/perl.mvs/
+L<https://github.com/ZOSOpenTools/perlport/> provides documentation and tools
+for building various z/OS Perl configurations and has some useful tools in the
+'bin' directory you may want to use for building z/OS Perl yourself.
=head1 HISTORY
-This document was originally written by David Fiander for the 5.005
-release of Perl.
+Updated 24 December 2021 to enable initial ASCII support
-This document was podified for the 5.005_03 release of Perl 11 March 1999.
+Updated 03 October 2019 for perl-5.33.3+
-Updated 12 November 2000 for the 5.7.1 release of Perl.
+Updated 28 November 2001 for broken URLs.
-Updated 15 January 2001 for the 5.7.1 release of Perl.
+Updated 12 March 2001 to mention //'SYS1.TCPPARMS(TCPDATA)'.
Updated 24 January 2001 to mention dynamic loading.
-Updated 12 March 2001 to mention //'SYS1.TCPPARMS(TCPDATA)'.
+Updated 15 January 2001 for the 5.7.1 release of Perl.
-Updated 28 November 2001 for broken URLs.
+Updated 12 November 2000 for the 5.7.1 release of Perl.
-Updated 03 October 2019 for perl-5.33.3+
+This document was podified for the 5.005_03 release of Perl 11 March 1999.
+This document was originally written by David Fiander for the 5.005
+release of Perl.
=cut