Product Documentation
Abstract
Product maintenance information for z/TPF 1.1 & z/TPFDF 1.1
Content
|
Description |
CSV | XLSX |
| APAR Data Information for closed APARs and open field APARs. The content includes APAR close sequence, abstract, correcting APARs, corrected APARs, functional area, HIPER classification, links to APAR document, download package, and so on. More Information. |
zTPFAPARData | zTPFAPARData |
| Segment Prerequisite Data A list of z/TPF source and binary files and the APARs that affect each one. More Information |
zTPFPrereqs | zTPFPrereqs |
| Macro-to-Header Associations A cross-reference list of macros and headers that support the same data. More Information |
zTPF-xref | zTPF-xref |
| Functional Area Data CSV file listing the functional area codes and the corresponding functional area name. |
zTPF-FAC |
CSV: CSV is a text file that can be displayed and edited with any standard editor.
XLSX: XLSX files can be viewed, printed, or modified by using Microsoft Excel or the Microsoft Excel Viewer.
(Format changed from XLS to XLSX on March 20, 2023)
z/TPF APAR Download Tools
The z/TPF APAR Download tools can be used to download individual APARs as well as generate cumulative APAR packages.
Download Instructions
Access to the z/TPF and z/TPFDF APAR packages is restricted to z/TPF license holders. To obtain access to download the APAR packages, contact TPFQA@us.ibm.com.
Unpack Instructions
z/TPF and z/TPFDF APAR packages are created on a Linux system by using the tar command with Lempel-Ziv (gzip) compression. The naming convention is Pxyyyyy.tar.gz. There is a single package for each APAR and it can include both text and binary files.
The files in each APAR package have a relative directory structure that includes the APAR number as the highest level directory. For example, the file named base/cp/cpse.cpy that is delivered for an APAR named PJ12345 is delivered as:
PJ12345/base/cp/cpse.cpy
This naming convention is used so that if multiple APAR packages are extracted under a common root directory, the files for each APAR remain unique from one another.
The Pxyyyyy.tar.gz file can be unpacked on a workstation by using a program such as WinZip that supports this format.
The Pxyyyyy.tar.gz file must be unpacked on a Linux system in order to build the APAR. To unpack the APAR package on Linux, do one of the following:
- Place the APAR gz file on Linux and use this tar command to unpack the file:
- tar -xzf Pxyyyyy.tar.gz
- Place the APAR gz file on a Windows drive, extract the contents to the drive, and then copy the files to Linux.
- Use WinZip or another unpack utility to unpack the file on a workstation.
- If you use FTP to copy extracted files between Windows and Linux platforms, you must ensure that binary or ascii mode is set as needed, for each file copied.
- If you copy extracted files to an NFS-mounted Linux drive, two separate mounts are required, one for text and one for binary. The extracted files must be copied to the appropriate drive by type.
- If you copy extracted files to an SMB-mounted Linux drive, only one mount is required because SMB can determine the type of file when it is copied.
- Place the APAR gz file on a Windows drive and extract the files directly to a Linux-mounted drive.
- If you use NFS-mounted drives, you must have a separate mount for text and binary, and you must extract only the text files to the text-mounted drive and only binary files to the binary-mounted drive.
- If you use an SMB-mounted drive, a single extract of all files can be used.
z/TPF includes z/OS offline utility programs. Even though these programs must be built and run on z/OS, it is recommended that you store the source files on Linux and gain access to the code for build purposes by using a Linux-mounted drive. This way, all source code can be managed on the Linux platform.
Was this topic helpful?
Document Information
Modified date:
06 April 2023
UID
swg27049604