For more information please visit our Web Site at: http://tpf.ncsa.uiuc.edu/

This document outlines the steps needed to build the zfile tar/pax/du
commands (PJ31597) for use on the IBM z/TPF Enterprise Edition system.V1 R1

It assumes that you are familiar with the MakeTPF build solution and the TPF
APAR process.

For contact assistance and problem reporting, follow the normal problem
reporting process for z/TPF issues and questions or contact a TPF Customer
Support Representative.

The following naming conventions are used in this document:
   "TAR" refers to the entire zfile tar/pax/du package

1. Apply the z/TPF TAR APAR PJ31597.

z/TPF APARs PJ31596 and PJ31619 are prerequisites for TAR.
If you have not already done so, apply both apars along with PJ31597.

2. Acquire the TAR source files.

Download and extract the TAR source files from the z/TPF Repository using the
highest posted PUT level, regardless of your actual PUT level:

  a. Download the ztpftar.tar.gz file from http://tpf.ncsa.uiuc.edu/
     to your root source directory.
     
     Note: Issues with MS IE and WinZip

       When downloading the ztpftar.tar.gz package with Microsoft IE
       for Windows, the name might be changed to ztpftar.tar.tar.
       WinZip will fail when trying to extract the package while it is named 
       ztpftar.tar.tar.

       To correct this, rename the file back to ztpftar.tar.gz and
       WinZip will correctly extract the tarball.

     Notes: 
       Make sure you have "Hide Extensions for Known Types" un-checked in your
       Internet Explorer options so you will actually get access to the file
       extension.
 
       If you are using FTP - please ensure you use Binary transfer mode
  
  b. Unarchive ztpftar.tar.gz to your source directory. This package contains
     the tarred source trees for the TAR package with
     additional modifications for the z/TPF system.

     tar zxvfp ztpftar.tar.gz
 
     This will create the directory structure opensource/unix.

3. Apply any APARs listed in the repository following the downloaded PUT level.

4. Verify the TAR  MakeTPF control file entries for
   CUNX, CFVG, CFVJ, CFVR and CFVV.
 
The program name "CUNX" is used for a shared library used by the TAR
programs.
The program name "CFVG" is used for the zfile tar command.
The program name "CFVJ" is used for the zfile pax command.
The program name "CFVR" is used for the libarchive library used by tar.
The program name "CFVV" is used for the zfile du command.
The control file entries for TAR were added to base/cntl/tpf_app_base.cntl by
PJ31597.

5. The required MakeTPF environment files were included in apar PJ31597.
The maketpf.env_unix environment is used to build the TAR code.

6. Check that the makefiles for CUNX, CFVG, CFVJ, CFVR and CFVV exist
in base/filesys/.

The makefiles for z/TPF TAR are part of APAR PJ31597 so you do not
have to create them manually.

7. Flip the TAR switch.

Building the TAR support is optional and is controlled by a
a MakeTPF switch called TPF_SBTAR.
TPF_SBTAR was added to tpftools/include_ztpf/maketpf.rules_functionswitch2ksh
and tpftools/include_ztpf/maketpf.rules_functionswitch_defaults by APAR PJ31597.
The TAR= option in macro/sip/config.mac was added for the TPF_SBTAR switch.

Change the TAR= value from NO to YES in xxx/src/sip.asm, where "xxx" is the
system you are building (for example: bas, bss, wp).
This will set the TPF_SBTAR switch on.

Enter the following to run SIP:
   bldtpf -f -sip xxx/src/sip.asm

8. Build the TAR segments by entering the corresponding maketpfs in this
order:
   maketpf -f CUNX
   maketpf -f CFVR
   maketpf -f CFVG
   maketpf -f CFVJ
   maketpf -f CFVV

These create opensource/unix/output/load/PPPPvv.so
(where "PPPP" is the segment name and "vv" is the USER_VERSION_CODE in
your maketpf.cfg configuration file).

There should be no warnings nor errors.

9. Rebuild the following code that controls zfiles:
   maketpf -f CFIM
   maketpf -f CFIX

Usage notes:
The TAR packages were ported from FreeBSD. For basic command descriptions
see the man pages at:
  "http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+5.0-current"
   
The following are differences from the FreeBSD man page descriptions.
 
zfile tar:
The options "jwyz" are not supported by z/TPF.
The long option format "--option" is not supported by z/TPF,
so the "-W option" format must be used.
The z/TPF zfile tar support has added two new formats: "ASCIItar" and
"ASCIIcpio". These create ASCII formatted archive headers that can be
read on unix and linux systems.
The time parameter for the "-W newer" or "-W newer-mtime" is given in
the format "YYYY/MM/DD HH:MM" and must be abolsolute. Relative time
values are not supported.
Because the TPF Collection File System (TFS) does not support access or
access time (atime) or change time (ctime)
only modification time (mtime) can be used for file selection on
TFS.
 
zfile pax:
The options "iz" are not supported by pax on z/TPF.
Because the TPF Collection File System (TFS) does not support
access time (atime) or change time (ctime),
only modification time (mtime) can be used for file selection on
TFS.
 
[This document was last updated 2006-11-15]