IBM To: Licensees of Transaction Processing Facility Version 4 Subject: Program Number 5748-T14 Release 1, Modification Level 00 Features 5831, 5832, 5702 The material you have received is listed on the enclosed Packing List. Please review the Packing List to ensure you have received all items listed. IBM Software Manufacturing Solutions. Attached to this memorandum: Summary of Changes. List of Program Material. Installation Instructions. Please refer to the attachment(s) for further description. IBM Software Manufacturing Solutions GI10-0689-04 1
2
Summary of Changes This memo is intended for the system programmer responsible for maintenance tape installation and maintenance. It contains information concerning the material and procedures associated with the installation of the maintenance tape for TPF 4.1. You should read all of it before installing the maintenance tape, and then keep it for future reference. APARs Included on the Program Update Tape (PUT) 13 PJ27273 Copyright IBM Corp. 1998, 2000 3
4
List of Program Material An IBM program is identified by a program number and a feature code. The program number of Transaction Processing Facility is 5748-T14. The program announcement material describes the features provided by Transaction Processing Facility. Ask your IBM marketing representative for this information if you have not already received a copy. The following sections identify the basic and optional program materials available with this program. Basic Machine-Readable Material The distribution medium for this maintenance tape is 9-track magnetic tape (written at 6250 BPI) or 3480 cartridge. The tape or cartridge contains all the programs and data needed for installation. Transaction Processing Facility is installed using the MVS/ESA operating system. See Installation Instructions on page 7 for more information about how to install this maintenance tape. Table 1 describes the tape or cartridge. See Table 2 describes the file content of the program tape or cartridge. Table 1. PUT 13 MPIF Tapes Medium Feature Number Physical Volume External Label Identification Description 9 Track/6250 BPI 5831 1 5748-T14-E-M013 Source Code for the Multi-Processor Interconnect Facility (MPIF) Feature 3480 Cartridge 5832 1 5748-T14-E-M013 Source Code for the Multi-Processor Interconnect Facility (MPIF) Feature 4 MM Tape 5702 1 5748-T14-E-M013 Source Code for the Multi-Processor Interconnect Facility (MPIF) Feature Table 2 (Page 1 of 2). Program Tape 1: File Content File Number Name Description Format BLK SIZE 1 NA Contains all APAR responses. 2 NA Contains all APAR abstracts. 3 NA Contains a list of closed APARs. 4 NA Contains a list of closed APARs in closed order. IEBGENER 12,100 IEBGENER 800 IEBGENER 800 IEBGENER 800 Copyright IBM Corp. 1998, 2000 5
Table 2 (Page 2 of 2). Program Tape 1: File Content File Number Name Description Format BLK SIZE 5 ACP.SRCE.RT.REL40 Contains replacements to the real-time programs (A-B). 6 ACP.SRCE.CP.REL40 Contains replacements to the copy programs. 7 ACP.OBJ.REL40 Contains replacements to all the object shippable code. 8 MPIF.PUT13.SOURCE.ASCII.TAR.Z Contains HFS format full source replacement of all MPIF base code. 9 MPIF.PJ27273.SOURCE.ASCII.TAR.Z Contains HFS format full source replacements for PUT 13 10 MPIF.PJ27273.SRCE.RT2 Full Segment Replacements for PUT 13 11 MPIF.PUT13.SRCE.RT2 Full Segment Replacements for PUT 13 IEBCOPY 12,000 IEBCOPY 12,000 IEBCOPY 12,000 IEBGENER 32,760 IEBGENER 32,760 IEBCOPY 12,000 IEBCOPY 12,000 Program Information See the memo to Licensees of TPF 4.1 Version 4, Transaction Processing Facility for Program Number 5748-T14 Release 1, Modification Level 00 Features 5811, 5812 for information about the program publications that were updated for PUT 13. 6
Installation Instructions This chapter describes the installation method and step-by-step procedures to install PUT 13. The JCL samples that are provided in this chapter are designed to install PUT 13 without affecting previously installed levels of Transaction Processing Facility. Installing PUT 13 for New TPF 4.1 Installations Instructions are provided here for installing PUT 13 for new TPF 4.1 installations. Step 1. Print File 1. The following is a sample of the JCL used to print File 1. //PRTTP JOB (ACCOUNTING INFO),MSGLEVEL=1 //LIST EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=A //SYSIN DD DUMMY //SYSUT1 DD DSN=TAPE,DISP=OLD,UNIT=348,VOL=SER=PTFTP1,LABEL=(1,NL), // DCB=(LRECL=121,BLKSIZE=121,RECFM=FBM) //SYSUT2 DD SYSOUT=A / Step 2. Print Files 2-4. The following is a sample of the JCL used to print Files 2-4. //PRTTP JOB (ACCOUNTING INFO),MSGLEVEL=1 //LIST EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=A //SYSIN DD DUMMY //SYSUT1 DD DSN=TAPE,DISP=OLD,UNIT=348,VOL=SER=PTFTP1,LABEL=(X,NL), // DCB=(LRECL=8,BLKSIZE=8,RECFM=FB) //SYSUT2 DD SYSOUT=A / Step 3. Unload Files 5 through 7. The following is a sample of the JCL used for Files 5 through 7. //UNLOAD JOB (ACCOUNTING INFO),MSGLEVEL=1 //LIST EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=A //INPUT DD VOL=SER=PTFTP1,LABEL=(X,NL),UNIT=348,DISP=(OLD,PASS), // DCB=(RECFM=FB,LRECL=8,BLKSIZE=12 ),DSN=MNTRTP //OUTPUT DD DISP=(OLD,PASS),DSN=ACP.xxxx.xx.RELvv,UNIT=338, // VOL=SER=UPDT 1 //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(8)),DISP=(,PASS) //SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(8)),DISP=(,PASS) //SYSIN DD COPY OUTDD=OUTPUT,INDD=((INPUT,R)) / Copyright IBM Corp. 1998, 2000 7
Installing PUT 13 for Existing TPF 4.1 Installations Instructions are provided here for installing PUT 13 for existing TPF 4.1 installations. Step 1. Print File 1. The following is a sample of the JCL used to print File 1. //PRTTP JOB (ACCOUNTING INFO),MSGLEVEL=1 //LIST EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=A //SYSIN DD DUMMY //SYSUT1 DD DSN=TAPE,DISP=OLD,UNIT=348,VOL=SER=PTFTP1,LABEL=(1,NL), // DCB=(LRECL=121,BLKSIZE=121,RECFM=FBM) //SYSUT2 DD SYSOUT=A / Step 2. Print Files 2-4. The following is a sample of the JCL used to print Files 2-4. //PRTTP JOB (ACCOUNTING INFO),MSGLEVEL=1 //LIST EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=A //SYSIN DD DUMMY //SYSUT1 DD DSN=TAPE,DISP=OLD,UNIT=348,VOL=SER=PTFTP1,LABEL=(X,NL), // DCB=(LRECL=8,BLKSIZE=8,RECFM=FB) //SYSUT2 DD SYSOUT=A / HFS Format Full Segment Replacements: Instructions are provided here for unloading HFS format full segment replacements. See Moving and Expanding TAR Files on page 10 for instructions about TAR files. Step 1 Unload Files 8 9. The following is a sample of the JCL used for Files 8 9. //JOB EXEC PGM=IEBGENER,TIME=22,REGION= M //SYSPRINT DD SYSOUT=A //SYSIN DD DUMMY //SYSUT1 DD VOL=SER=XXXXXX,LABEL=(X,NL),UNIT=348,DISP=(OLD,PASS), // DCB=(DSORG=PS,RECFM=VB,LRECL=32756,BLKSIZE=3276 ), // DSN=MNTOBJ //SYSUT2 DD DSN=MPIF.XXXX.XXXX.TAR.Z,DISP=(,CATLG), // DCB=(DSORG=PS,RECFM=VB,LRECL=32756,BLKSIZE=3276 ), // SPACE=(TRK,(1,1)),VOL=SER=T2TSO4,UNIT=339 / MVS Full Segment Replacements: Instructions are provided here for unloading MVS full segment replacements. Step 1 Unload Files 10 11. The following is a sample of the JCL used for Files 10 11. 8
//JOB JOB (ACCOUNTING INFO),MSGLEVEL=1 //LIST EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=A //INPUT DD VOL=SER=PTFTP1,LABEL=(X,NL),UNIT=348,DISP=(OLD,PASS), // DCB=(RECFM=FB,LRECL=8,BLKSIZE=12 ),DSN=MNTOBJ //OUTPUT DD DISP=(OLD,PASS),MPIF.xxxx.xxxx // VOL=SER=UPDT 1 //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(8)),DISP=(,PASS) //SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(8)),DISP=(,PASS) //SYSIN DD COPY OUTDD=OUTPUT,INDD=((INPUT,R)) / Note: For all MPIF.xxxxxxx.MODULES data sets use RECFM=U for the DCB definitions in the sample JCL listed above. Installation Instructions 9
Moving and Expanding TAR Files The TPF 4.1 PUT 13 tape contains the following TAR files: APAR source Binary objects Listing Full source replacement. Table 3. TAR File Types and Naming Conventions Type of File File Naming Convention Notes APAR source MPIF.PJxxxxx.SOURCE.ASCII.TAR.Z Every APAR has a source TAR file. Binary MPIF.PJxxxxx.BINARY.ASCII.TAR.Z Some APARs have a binary TAR file, which contains binary objects or load modules. Listings MPIF.PJxxxxx.LISTINGS.ASCII.TAR.Z Some APARs have a listings TAR file. Full source MPIF.PUT13.SOURCE.ASCII.TAR.Z The full source TAR file contains all the source code for TPF 4.1 PUT 13. This is a complete replacement of all source code. Note: An APAR may have more than one TAR file. The TAR files are stored in MVS sequential data sets when the PUT tape is unpacked. APAR Source TAR File The changed parts for an APAR and the APAR Response document are stored in the APAR source file. The source is converted from an EBCDIC format to an ASCII format so that you can unpack the TAR file on a work station. To process the file on OS/390 Unix System Services (USS), you must convert it back to the EBCDIC format by doing the following: 1. Create the directory /yourdir/pjxxxxx/text where you will put the source TAR file. 2. Transmit the TAR file to OS/390 USS using the TSO oput command. For example: oput 'mpif.pjxxxxx.source.ascii.tar.z' '/yourdir/pjxxxxx/text/pjxxxxx.source.ascii.tar.z' binary 3. Expand the TAR file using the OS/390 pax command, including the ASCII-to-EBCDIC character conversion. For example: pax -rf /yourdir/pjxxxxx/text/pjxxxxx.source.ascii.tar.z -ofrom=iso8859-1,to=ibm-1 47 10
The APAR response document will be in /yourdir/pjxxxxx/text/pjxxxx.txt and for all APARs delivering source shippable code, a subdirectory structure will be created in the /text directory. The subdirectory structure will vary depending on what source was changed for the APAR. Binary File TAR files that contain binary data can hold load modules, object code for non-shippable source code, and library stubs. Binary TAR files are not converted from an EBCDIC format to an ASCII format; expand them only on an OS/390 system. 1. Create the directory /yourdir/pjxxxxx/binary where you will put the binary TAR file. 2. Transmit the TAR file to OS/390 USS using the TSO oput command. For example: oput 'mpif.pjxxxxx.binary.tar.z' '/yourdir/pjxxxxx/binary/pjxxxxx.binary.tar.z' binary 3. Expand the TAR file using the OS/390 UNIX pax command. For example: pax -rf /yourdir/pjxxxxx/binary/pjxxxxx.binary.tar.z A README file is stored in /yourdir/pjxxxxx/binary/readme. A subdirectory structure will be created in the /binary directory. The subdirectory structure will vary depending on what binary objects are delivered for the APAR. Listings TAR File If a source code change for an APAR results in a load module being relinked, and if the source code change was made to source code that ships, TPF will provide both the linked module and the listing of the changed source that went in the module. The listings TAR file contains those listings. Each listing file is converted from an EBCDIC to an ASCII format so that the TAR file can be unpacked on a work station. To process the file on OS/390 Unix System Services (USS), you must convert it to the EBCDIC format by doing the following: 1. Create the directory /yourdir/pjxxxxx/listings where you will put the listing TAR file. 2. Transmit the TAR file to OS/390 USS using the TSO oput command. For example: oput 'mpif.pjxxxxx.listings.ascii.tar.z' '/yourdir/pjxxxxx/listings/pjxxxxx.listings.ascii.tar.z' binary 3. Expand the TAR file using the OS/390 UNIX pax command, including the ASCII-to-EBCDIC character conversion. For example: pax -rf /yourdir/pjxxxxx/listings/pjxxxxx.listings.ascii.tar.z -ofrom=iso8859-1,to=ibm-1 47 The listings for this APAR are stored in the /listings directory. No other subdirectory structure is created. Installation Instructions 11
Full Source Replacement TAR File The full source replacement TAR file contains all the shipped TPF source code for PUT 13. This is a complete replacement of all source code. The name of this file is MPIF.PUT13.SOURCE.ASCII.TAR.Z. The TAR file is stored in a sequential data set on an MVS system. Do the following to create and unpack the TAR file. 1. Use the TSO oput command to copy the data set to the HFS directory of your choice. For example: oput 'MPIF.PUT13.SOURCE.ASCII.TAR.Z' '/yourdir/mpif.put13.source.ascii.tar.z' binary 2. Access OS/390 UNIX and change the directory to /yourdir. 3. Unpack the TAR file using the following command: pax -rf mpif.put13.source.ascii.tar.z -ofrom=iso8859-1,to=ibm-1 47 The result of this command is a new directory structure in /yourdir called put13mpif; this directory will have other subdirectories that contain all source, shipped, base TPF code for PUT 13. 12 IBM is the registered trademark of International Business Machines Corporation.
IBM December 2000 References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM program product in this publication is not intended to state or imply that only IBM s program product may be used. Any functionally equivalent program may be used instead. Copyright International Business Machines Corporation 1998, 2000. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. GI1-689- 4