This document outlines the steps needed to install Apache onto a TPF system.
You should first read htdocs/manual/readme-tpf.html for basic information on the port of Apache to TPF including required PUT level and supported functions & modules.
Due to the use of EBCDIC on MVS OS/390 Open Edition (later referred to simply as "Open Edition"), we've found that the most reliable method for loading Apache onto your system is to unzip and tar the distribution file on your PC, and then copy the extracted files to Open Edition via an NFS client capable of transferring the data in EBCDIC format.
Before moving the distribution to an Open Edition environment, verify that the NFS drive will transfer the filenames with upper/lower case preserved.
Since Open Edition is not the ultimate destination of the files, the only required files and subdirectories that need to be moved to Open Edition are in /src.
WARNING: If you are using a product such as WinZip on your PC, verify that the "TAR File Smart CR/LF Conversion" option is NOT checked. You can find this in WinZip under Options, Configuration. Since you had to tar and unzip the file to read this document, you need to re-tar and -unzip if the CR/LF option was checked. This will save you lots of headaches later on.
WARNING: Editing files on a PC before moving them to Open Edition may result in the loss/addition of unprintable characters. Files of concern include shell scripts and src/Configuration. The most common problems are with tab characters and CR/LF characters. Most editors will handle the CR/LF problem correctly but none seem to handle tab characters. If you need to edit files, edit them in a UNIX editor such as vi or emacs.
Apache supports the notion of "optional modules". However, the server has to know which modules are compiled into it. In order for those modules to be effective, it is necessary to generate a short bit of code ("modules.c") which simply has a list of them. If you are using the make and Configure utility, "modules.c" will be created for you.
The provided scripts assume a c89 compiler and have only been tested on an Open Edition environment. If you are using a platform other that Open Edition you may need to modify src/os/tpf/TPFExport and src/Configure to match your environment.
Note that UNIX/Open Edition commands in this section are shown in bold, are case sensitive, and must be made from the "src" directory.
Using config file: Configuration Creating Makefile + configured for TPF platform + setting C compiler to c89 + setting C pre-processor to c89 -E + checking for system header files + adding selected modules Creating Makefile in support Creating Makefile in main Creating Makefile in ap Creating Makefile in regex Creating Makefile in os/tpf Creating Makefile in modules/standard Creating Makefile in modules/example $ _This generates modules.c and new versions of the Makefiles.
Using config file: Configuration.ai Creating Makefile + configured for <whatever> platform + setting C compiler to <whatever> et ceteraIf you receive an error such as "Configure 146: FSUM7351 not found" the most likely explanation is that one or more of the make related files were edited on a non-UNIX platform, corrupting the end-of-line marks. Verify that lines ending with "\" in the flagged file do not have trailing spaces. Using the vi editor and the sample error above as an example...
pull up the flagged file: vi Configure turn on punctuation: :set list go to the line in question: 146G or find a line with a "\": /\\The end of line should display as "\$". If it is displayed as "\ $" (with a blank between \ and $) then you should revert to the distributed version of the file and make the site-specific changes again using a UNIX compatible editor such as vi or emacs. Then try the Configure command again.
close the file: :q (or :quit!)
ZINET ADD S-TFTP PGM-CTFT PORT-69 PROTOCOL-UDP MODEL-NOWAIT ZINET ADD S-APACHE PGM-pppp PORT-80 PROTOCOL-TCP MODEL-NOWAITPlease refer to IBM Transaction Processing Facility Transmission Control Protocol/Internet Protocol Version 4 Release 1 for more information on ZCLAW, INETD, and TFTP.
/usr/local/apache/conf /usr/local/apache/logs /usr/local/apache/icons /usr/local/apache/htdocsThe logs directory must exist in order to avoid an
fopenerror while running Apache. TFTP an empty file into the logs subdirectory to create it. All gif, jpg, and zip files should be TFTP'd as binary; conf files and html pages should be TFTP'd as text.
It is not required that "make" be used to compile Apache for TPF:
Individual programs may be compiled using IBM's VisualAge TPF product.
This is particularly useful when compiling selected programs for the Debug Tool.
The following VisualAge compile settings are required: