SCRIPT/VS 4.0.0: DEVICE 1403N8 CHARS MONO Program Directory for AFP Upload for AIX feature of PSF/MVS Program Number 5655-B17,5695-040  FMID HPRF227  for Use with MVS OS/390  CBPDO Level SMC9824 Service Level 9824 Document Date: January 1999  GI10-0219-01 NOTE! ׯ | | | Before using this information and the product it supports, be sure | | to read the general information under "Notices" on page v. | | | ר  A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. (C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1996, 1998. ALL RIGHTS RESERVED. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. CONTENTS  NOTICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . v 1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 AFP Upload Description . . . . . . . . . . . . . . . . . . 1 1.2 AFP Upload FMID . . . . . . . . . . . . . . . . . . . . . . 2 2.0 PROGRAM MATERIALS . . . . . . . . . . . . . . . . . . . . . 3 2.1 Basic Machine-Readable Material . . . . . . . . . . . . . . 3 2.2 Optional Machine-Readable Material . . . . . . . . . . . . . 3 2.3 Program Publications . . . . . . . . . . . . . . . . . . . . 4 2.3.1 Basic Program Publications . . . . . . . . . . . . . . . 4 2.3.2 Optional Program Publications . . . . . . . . . . . . . 4 2.4 Program Source Materials . . . . . . . . . . . . . . . . . . 4 2.5 Publications Useful During Installation . . . . . . . . . . 4 3.0 PROGRAM SUPPORT . . . . . . . . . . . . . . . . . . . . . . 5 3.1 Program Services . . . . . . . . . . . . . . . . . . . . . . 5 3.2 Preventive Service Planning . . . . . . . . . . . . . . . . 5 3.3 Statement of Support Procedures . . . . . . . . . . . . . . 5 4.0 PROGRAM AND SERVICE LEVEL INFORMATION . . . . . . . . . . . 7 4.1 Program Level Information . . . . . . . . . . . . . . . . . 7 4.2 Service Level Information . . . . . . . . . . . . . . . . . 7 4.3 Cumulative Service Tape . . . . . . . . . . . . . . . . . . 7 5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS . . . . . . . . 9 5.1 Driving System Requirements . . . . . . . . . . . . . . . . 9 5.1.1 Machine Requirements . . . . . . . . . . . . . . . . . . 9 5.1.2 Programming Requirements . . . . . . . . . . . . . . . . 9 5.2 Target System Requirements . . . . . . . . . . . . . . . . . 9 5.2.1 Machine Requirements . . . . . . . . . . . . . . . . . . 9 5.2.2 Programming Requisites . . . . . . . . . . . . . . . . . 9 5.2.2.1 Minimum Requisites . . . . . . . . . . . . . . . . . 10 5.2.2.2 Functional Requisites . . . . . . . . . . . . . . . 10 5.2.2.3 Toleration/Coexistence Requisites . . . . . . . . . 11 5.2.3 DASD Storage Requirements . . . . . . . . . . . . . . . 11 5.3 Special Considerations . . . . . . . . . . . . . . . . . . . 13 6.0 INSTALLATION INSTRUCTIONS . . . . . . . . . . . . . . . . . 15 6.1 Installing AFP Upload . . . . . . . . . . . . . . . . . . . 15 6.1.1 SMP/E Considerations for Installing AFP Upload . . . . . 15 6.1.2 SMP/E Environment . . . . . . . . . . . . . . . . . . . 15 6.1.3 SMP/E Options Subentry Values . . . . . . . . . . . . . 15 6.1.4 SMP/E CALLLIBS Processing . . . . . . . . . . . . . . . 16 6.1.5 Unload the Sample JCL from the Product Tape . . . . . . 16 6.1.6 Perform SMP/E RECEIVE . . . . . . . . . . . . . . . . . 17 6.1.7 RECEIVE Cumulative Service Tape, if applicable . . . . . 17 6.1.8 Allocate SMP/E Target and Distribution Libraries . . . . 18 6.1.9 Create DDDEF Entries . . . . . . . . . . . . . . . . . . 20 6.1.10 Perform SMP/E APPLY CHECK . . . . . . . . . . . . . . . 22 6.1.11 Perform SMP/E APPLY . . . . . . . . . . . . . . . . . . 23 6.1.12 Perform SMP/E ACCEPT CHECK . . . . . . . . . . . . . . 23 6.1.13 Perform SMP/E ACCEPT . . . . . . . . . . . . . . . . . 24 6.2 Activating AFP Upload . . . . . . . . . . . . . . . . . . . 25 APPENDIX A. AFP UPLOAD INSTALL LOGIC . . . . . . . . . . . . . . 27 A.1 SMP/E Modification Control Statements . . . . . . . . . . . 27 A.2 SMP/E JCLIN . . . . . . . . . . . . . . . . . . . . . . . . 27 APPENDIX B. USING IBM LANGUAGE ENVIRONMENT FOR MVS . . . . . . . 29 B.1 Deciding Whether to Use LE . . . . . . . . . . . . . . . . . 29 B.2 Installation Changes to Use LE . . . . . . . . . . . . . . . 30 B.3 Execution Changes to Use LE . . . . . . . . . . . . . . . . 30 B.3.1 Using LE with AFP Upload SNA: . . . . . . . . . . . . . 30 B.3.2 Using LE with AFP Upload TCP/IP: . . . . . . . . . . . . 31 READER'S COMMENTS . . . . . . . . . . . . . . . . . . . . . . . . 35 (C) Copyright IBM Corp. 1996, 1998 iii FIGURES  1. Basic Material: Program Tape . . . . . . . . . . . . . . . . 3 2. Program Tape: File Content . . . . . . . . . . . . . . . . . 3 3. Basic Material: Unlicensed Publications . . . . . . . . . . 4 4. Publications Useful During Installation . . . . . . . . . . 4 5. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . 5 6. Component ID . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Driving System Software Requirements . . . . . . . . . . . . 9 8. Minimum Requisites . . . . . . . . . . . . . . . . . . . . . 10 9. Functional Requisites . . . . . . . . . . . . . . . . . . . 11 10. Total DASD Space (in 3390 tracks) Required by AFP Upload . . 11 11. Storage Requirements for SMP/E Work Data Sets . . . . . . . 12 12. Storage Requirements for SMP/E Data Sets . . . . . . . . . . 13 13. Storage Requirements for AFP Upload Target Libraries . . . . 13 14. Storage Requirements for AFP Upload Distribution Libraries 13 15. SMP/E Options Subentry Values . . . . . . . . . . . . . . . 16 16. Sample UNLOAD Job . . . . . . . . . . . . . . . . . . . . . 16 17. Sample SMP/E RECEIVE Job . . . . . . . . . . . . . . . . . . 17 18. RECEIVE Job for Cumulative Service Tape . . . . . . . . . . 18 19. Sample Allocate Job . . . . . . . . . . . . . . . . . . . . 19 20. JCL to Create Target and Distribution DDDEFs . . . . . . . . 21 21. Sample SMP/E APPLY CHECK Job . . . . . . . . . . . . . . . . 23 22. Sample SMP/E APPLY Job . . . . . . . . . . . . . . . . . . . 23 23. Sample SMP/E ACCEPT CHECK Job . . . . . . . . . . . . . . . 24 24. Sample SMP/E ACCEPT Job . . . . . . . . . . . . . . . . . . 25  iv AFP Upload Program Directory NOTICES  References in this document 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 product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility. APAR numbers are provided in this document to assist in locating PTFs that may be required. Ongoing problem reporting may result in additional APARs being created. Therefore, the APAR lists in this document may not be complete. To obtain current service recommendations and to identify current product service requirements, always contact the IBM Customer Support Center. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 USA For online versions of this book, we authorize you to: Copy, modify, and print the documentation contained on the media, for use within your enterprise, provided you reproduce the copyright notice, all warning statements, and other required statements on each copy or partial copy. Transfer the original unaltered copy of the documentation when you transfer the related IBM product (which may be either machines you own, or programs, if the program's license terms permit a transfer). You must, at the same time, destroy all other copies of the documentation. You are responsible for payment of any taxes, including personal property taxes, resulting from this authorization. THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. Your failure to comply with the terms above terminates this authorization. Upon termination, you must destroy your machine readable documentation.  TRADEMARKS The following terms are trademarks of the IBM Corporation in the United States or other countries or both: ACF/VTAM IBMLink PSF AFP MO:DCA RETAIN AIX MVS RISC System/6000 CBIPO MVS/ESA S/370 CBPDO OpenEdition S/390 DFSMS OS/390 SystemPac IBM ProductPac (C) Copyright IBM Corp. 1996, 1998 v  vi AFP Upload Program Directory 1.0 INTRODUCTION  This program directory is intended for the system programmer responsible for program installation and maintenance. It contains information concerning the material and procedures associated with the installation of AFP Upload for AIX feature of PSF/MVS. This publication refers to AFP Upload for AIX feature of PSF/MVS as AFP Upload. You should read all of this program directory before installing the program and then keep it for future reference. The program directory contains the following sections: 2.0, "Program Materials" on page 3 identifies the basic and optional program materials and documentation for AFP Upload. 3.0, "Program Support" on page 5 describes the IBM support available for AFP Upload. 4.0, "Program and Service Level Information" on page 7 lists the APARs (program level) and PTFs (service level) incorporated into AFP Upload. 5.0, "Installation Requirements and Considerations" on page 9 identifies the resources and considerations for installing and using AFP Upload. 6.0, "Installation Instructions" on page 15 provides detailed installation instructions for AFP Upload. It also describes the procedures for activating the functions of AFP Upload, or refers to appropriate publications. Appendix A, "AFP Upload Install Logic" on page 27 provides the install logic for AFP Upload. Appendix B, "Using IBM Language Environment for MVS" on page 29 provides instructions for using LE. Before installing AFP Upload, read 3.2, "Preventive Service Planning" on page 5. This section tells you how to find any updates to the information and procedures in this program directory. Do not use this program directory if you are installing AFP Upload with an MVS Custom-Built Installation Process Offering (CBIPO), SystemPac, or ServerPac. When using these offerings, use the jobs and documentation supplied with the offering. This documentation may point you to specific sections of the program directory as required. If you are installing AFP Upload using the MVS Custom-Built Product Delivery Offering (CBPDO) (5751-CS3), use the softcopy program directory provided on the CBPDO tape. Your CBPDO contains a softcopy preventive service planning (PSP) upgrade for this product. All service and HOLDDATA for AFP Upload are included on the CBPDO tape.  1.1 AFP UPLOAD DESCRIPTION The AFP Upload feature of PSF/MVS allows you to take the following kinds of LAN-created data and pass them up to an MVS system for printing on a host-attached printer: PCL SAP OTF PostScript MO:DCA-P Line data that has been processed by the line2afp transform or the Advanced Function Conversion and Indexing Facility (ACIF) PSF for AIX takes the user's data off the AIX spool and transforms it to MO:DCA-P, if necessary. The AFP Upload feature of PSF/MVS, running on the S/370 or S/390, receives the print data from PSF for AIX and places it on the JES spool for printing by PSF/MVS. AFP Upload  (C) Copyright IBM Corp. 1996, 1998 1 supports all data streams that PSF for AIX can transform into MO:DCA-P and all printers supported by PSF/MVS. AFP Upload passes the following attributes (similar to JCL OUTPUT statement parameters) along with the print data: ADDRESS BUILDING CLASS COPIES DATACK DEPARTMENT DESTINATION FORMDEF FORMS NAME ROOM TITLE WRITER AFP Upload can use either SNA (via APPC/MVS) or TCP/IP communications protocol to communicate with PSF for AIX on the RISC System/6000.  1.2 AFP UPLOAD FMID AFP Upload consists of the following FMID: HPRF227 2 AFP Upload Program Directory 2.0 PROGRAM MATERIALS  An IBM program is identified by a program number and a feature number. The program number for AFP Upload is 5695-040, (MVS), and 5655-B17, (OS/390). Basic Machine-Readable Materials are materials that are supplied under the base license and feature code, and are required for the use of the product. Optional Machine-Readable Materials are orderable under separate feature codes, and are not required for the product to function. The program announcement material describes the features supported by AFP Upload. Ask your IBM representative for this information if you have not already received a copy.  2.1 BASIC MACHINE-READABLE MATERIAL The distribution medium for this program is 9-track magnetic tape (written at 6250 BPI), 3480 cartridge, or 4mm cartridge. The tape or cartridge contains all the programs and data needed for installation. It is installed using SMP/E, and is in SMP/E RELFILE format. See 6.0, "Installation Instructions" on page 15 for more information about how to install the program. Figure 1 describes the tape or cartridge. Figure 2 describes the file content of the program tape or cartridge. NOTE: If you are installing AFP Upload using the MVS Custom-Built Product Delivery Offering (CBPDO) (5751-CS3), some of the information in these figures may not be valid. Consult the CBPDO documentation for actual values. ׯ | Figure 1. Basic Material: Program Tape |  ׯ | | | | FEATURE | PHYSICAL | EXTERNAL LABEL | | | MEDIUM | NUMBER | VOLUME | IDENTIFICATION | VOLSER |  ׯ | | | | | | | 6250 tape | 5811 | 1 | PSF.AFP.UPLOAD | PRF227 |  ׯ | | | | | | | 3480 cart | 5812 | 1 | PSF.AFP.UPLOAD | PRF227 |  ׯ | | | | | | | 4mm cart | 5338 | 1 | PSF.AFP.UPLOAD | PRF227 |  ר ׯ | Figure 2. Program Tape: File Content |  ׯ | | | | | | DIST | | | BLK | | VOLSER | FILE | NAME | LIBRARY | RECFM | LRECL | SIZE |  ׯ | | | | | | | | | PRF227 | 1 | SMPMCS | n/a | FB | 80 | 8800 |  ׯ | | | | | | | | | | 2 | IBM.HPRF227.F1 | JCLIN | FB | 80 | 8800 |  ׯ | | | | | | | | | | 3 | IBM.HPRF227.F2 | AAUPSAMP| FB | 80 | 8800 |  ׯ | | | | | | | | | | 4 | IBM.HPRF227.F3 | AAUPLOAD| U | 0 | 6144 |  ר  2.2 OPTIONAL MACHINE-READABLE MATERIAL No optional machine-readable materials are provided for AFP Upload. (C) Copyright IBM Corp. 1996, 1998 3 2.3 PROGRAM PUBLICATIONS The following sections identify the basic and optional publications for AFP Upload.  2.3.1 BASIC PROGRAM PUBLICATIONS Figure 3 identifies the basic unlicensed program publications for AFP Upload. One copy of each of these publications is included when you order the basic materials for AFP Upload. For additional copies, contact your IBM representative. ׯ | Figure 3. Basic Material: Unlicensed Publications |  ׯ | | | PUBLICATION TITLE | FORM NUMBER |  ׯ | | | | PSF for AIX: AFP Upload Configuration Guide Using | S544-5422 | | SNA | |  ׯ | | | | PSF for AIX: AFP Upload Configuration Guide Using | S544-5423 | | TCP/IP | |  ר  2.3.2 OPTIONAL PROGRAM PUBLICATIONS No optional publications are provided for AFP Upload.  2.4 PROGRAM SOURCE MATERIALS No program source materials or viewable program listings are provided for AFP Upload.  2.5 PUBLICATIONS USEFUL DURING INSTALLATION ׯ | Figure 4. Publications Useful During Installation |  ׯ | | | PUBLICATION TITLE | FORM NUMBER |  ׯ | | | | OS/390 SMP/E Commands | SC28-1805 |  ׯ | | | | OS/390 SMP/E Reference | SC28-1806 |  ׯ | | | | OS/390 SMP/E User's Guide | SC28-1740 |  ׯ | | | | OS/390 SMP/E Messages and Codes | SC28-1738 |  ׯ | | | | SMP/E Reference | SC28-1107 |  ׯ | | | | SMP/E User's Guide | SC28-1302 |  ׯ | | | | SMP/E Messages and Codes | SC28-1108 |  ׯ | | | | OS/390 MVS JCL Reference | GC28-1757 |  ׯ | | | | MVS/ESA V5 JCL Reference | GC28-1479 |  ׯ | | | | MVS/ESA V4 JCL Reference | GC28-1654 |  ר 4 AFP Upload Program Directory 3.0 PROGRAM SUPPORT  This section describes the IBM support available for AFP Upload.  3.1 PROGRAM SERVICES Contact your IBM representative for specific information about available program services.  3.2 PREVENTIVE SERVICE PLANNING Before installing AFP Upload, you should review the current Preventive Service Planning (PSP) information. If you obtained AFP Upload as part of a CBPDO, there is HOLDDATA and PSP information included on the CBPDO tape. If you obtained AFP Upload on a product tape, or if the CBPDO is more than two weeks old when you install it, you should contact the IBM Support Center or use S/390 SoftwareXcel to obtain the current "PSP Bucket". PSP Buckets are identified by UPGRADEs, which specify product levels, and SUBSETs, which specify the FMIDs for a product level. The UPGRADE and SUBSET values for AFP Upload are: ׯ | Figure 5. PSP Upgrade and Subset ID |  ׯ | | | UPGRADE | SUBSET | DESCRIPTION |  ׯ | | | | | AFPUPLOAD | HPRF227/9824 | PSF AIX UPLOAD |  ר NOTE: The PSP SUBSET name reflects the Function Module Identifier (FMID) that was updated and the corresponding CBPDO weekly service tape that was used to supply the integrated PTFS. (Example; FMID/YYWW, where YY is the year and WW is the week of the CBPDO weekly service tape.). The CBPDO weekly Service tape is the Service Level Indicator for any products updated by the Software Manufacturing Center (SMC) processes. If you wish to determine the latest level of PUT maintenance installed in this product, please refer to 4.0, "Program and Service Level Information" on page 7.  3.3 STATEMENT OF SUPPORT PROCEDURES Report any difficulties you have using this program to your IBM Support Center. If an APAR is required, the Support Center will provide the address to which any needed documentation can be sent. Figure 6 identifies the component ID (COMPID) for AFP Upload. ׯ | Figure 6. Component ID |  ׯ | | | | | | RETAIN | | FMID | COMPID | COMPONENT NAME | RELEASE |  ׯ | | | | | | HPRF227 | 569504003 | PSF AIX Upload | 227 |  ר (C) Copyright IBM Corp. 1996, 1998 5  6 AFP Upload Program Directory 4.0 PROGRAM AND SERVICE LEVEL INFORMATION  This section identifies the program and any relevant service levels of AFP Upload. The program level refers to the APAR fixes incorporated into the program. The service level refers to the PTFs integrated. Information about the cumulative service tape is also provided. This program is at Service Level 9824.  4.1 PROGRAM LEVEL INFORMATION This is the first release of AFP Upload, and no APARs from prior releases have been incorporated.  4.2 SERVICE LEVEL INFORMATION The following PTFs containing APAR fixes against this release of AFP Upload have been integrated into this release. NOTE: COR-CLOSED PTFs are available for 'Corrective Service' and will be placed on the next available ESO Tape (Expanded Service Option, formerly known as PUT Tapes). The following sub-categories for COR-CLOSED PTFs have been provided by the Software Manufacturing Center (SMC), Poughkeepsie: PUTYYMM COR-CLOSED PTFs that are available on an ESO Tape, where 'yynn' indicates the year and the month that the ESO tape became available. RSUYYMM RSU (Recommended Service Upgrade) is a preventive service philosophy for all S/390 products that are serviced by IBM for the OS/390 and MVS platforms. RSU reduces the volume of PTFs customers need to apply for preventive maintenance. RSU became available at OS/390 Release 2 GA (9/96), and is identified via an additional SOURCEID of RSUyymm, where 'yymm' indicates the year and the month the PTF was assigned this SOURCEID. SMCREC COR-CLOSED PTFs that are not yet available on an ESO Tape, but have been researched and recommended for installation by the Software Manufacturing Center (SMC) in Poughkeepsie. SMCCOR COR-CLOSED PTFs that are not yet available on an ESO Tape and have no special recommendation for installation. HPRF227 UW30822-RSU9607 UW31580-PUT9608 UW39048-PUT9706 UW49150-PUT9806 UW49247-PUT9806  4.3 CUMULATIVE SERVICE TAPE A cumulative service tape, containing PTFs not incorporated into this release, might be included with this program. Installation instructions for cumulative service tapes can be found in the SMP/E publications. If you received this product as part of a CBPDO or a ProductPac, PTFs not incorporated into this release are provided on the tape, and a separate cumulative service tape will not be provided. (C) Copyright IBM Corp. 1996, 1998 7  8 AFP Upload Program Directory 5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS  The following sections identify the system requirements for installing and activating AFP Upload. The following terminology is used: Driving system: the system used to install the program. Target system: the system on which the program is installed. In many cases, the same system can be used as both a driving system and a target system. However, you may want to set up a clone of your system to use as a target system by making a separate IPL-able copy of the running system. The clone should include copies of all system libraries that SMP/E updates, copies of the SMP/E CSI data sets that describe the system libraries, and your PARMLIB and PROCLIB. Some cases where two systems should be used include the following: When installing a new level of a product that is already installed, the new product will delete the old one. By installing onto a separate target system, you can test the new product while still keeping the old one in production. When installing a product that shares libraries or load modules with other products, the installation can disrupt the other products. Installing onto a test system or clone will allow you to assess these impacts without disrupting your production system.  5.1 DRIVING SYSTEM REQUIREMENTS This section describes the environment of the driving system required to install AFP Upload.  5.1.1 MACHINE REQUIREMENTS The driving system can run in any hardware environment that supports the required software.  5.1.2 PROGRAMMING REQUIREMENTS ׯ | Figure 7. Driving System Software Requirements |  ׯ | | | PROGRAM | PRODUCT NAME AND | | NUMBER | MINIMUM VRM/SERVICE LEVEL |  ׯ | | | | 5668-949| System Modification Program/Extended (SMP/E) Release | | | 1.8.0 or higher |  ר  5.2 TARGET SYSTEM REQUIREMENTS This section describes the environment of the target system required to install and use AFP Upload.  5.2.1 MACHINE REQUIREMENTS The target system can run in any hardware environment that supports the required software.  5.2.2 PROGRAMMING REQUISITES (C) Copyright IBM Corp. 1996, 1998 9 5.2.2.1 MINIMUM REQUISITES A minimum requisite is defined as one of the following: 1. Installation Requisite: A product that is required at installation time. i.e. this product WILL NOT INSTALL successfully unless this requisite is met. This includes products that are specified as REQs, PREs, or CALLLIBs. 2. Run Time Requisite: A product that is NOT required for the successful installation of this product, but IS needed at run time in order for this product to work. ׯ | Figure 8. Minimum Requisites |  ׯ | | | | PRODUCT NAME AND | INSTALL | | PROGRAM NUMBER | MINIMUM VRM/SERVICE LEVEL | REQ? |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5668-909 | PL/I Comp/Lib/ITF Version 2.3.0 with | Yes | | | | PTFs UN25179 and UN74369 or higher | |  ׯ | | | | | | | 5668-910 | PL/I Comp/Lib Version 2.3.0 with PTFs | Yes | | | | UN25179 and UN74369 or higher | |  ׯ | | | | | | | 5668-911 | PL/I Lib Version 2.3.0 with PTFs | Yes | | | | UN25179 and UN74369 or higher | |  ׯ | | | | | | | 5688-198 | Language Environment for MVS & VM | Yes | | | | Version 1.5 with APARs PN81331 and | | | | | PN92107 or higher | |  ׯ | | | | | | | 5645-001 | Language Environment element of OS/390 | Yes | | | | Version 1 with APAR PN81331 | |  ׯ | | | | | | | 5647-A01 | Language Environment element of OS/390 | Yes | | | | Version 2 with APAR PN12915 | |  ׯ | | | NOTE: AFP Upload can be installed using the IBM Language | | Environment for MVS (LE), which includes PL/I runtime libraries, | | instead of the PL/I V2R3 product. Instructions for using LE with | | AFP Upload are contained in Appendix B, "Using IBM Language | | Environment for MVS" on page 29. |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5695-047 | MVS/ESA JES2 Version 4 or higher | Yes |  ׯ | | | | | | | 5695-048 | MVS/ESA JES3 Version 4 or higher | Yes |  ׯ | | | | | | | 5655-068 | MVS/ESA JES2 Version 5 or higher | Yes |  ׯ | | | | | | | 5655-069 | MVS/ESA JES3 Version 5 or higher | Yes |  ׯ | | | | | | | 5645-001 | OS/390 Version 1 or higher | Yes |  ׯ | | | | | | | 5647-A01 | OS/390 Version 2 or higher | Yes |  ר  5.2.2.2 FUNCTIONAL REQUISITES A functional requisite is defined as a product that is not required for the successful installation of this product or for the base function of the product, but is needed at run time for a specific function of this product to work. This includes products that are specified as IF REQs.  10 AFP Upload Program Directory ׯ | Figure 9. Functional Requisites |  ׯ | | | | PRODUCT NAME AND | | | | PROGRAM | MINIMUM VRM/SERVICE | | INSTALL | | NUMBER | LEVEL | FUNCTION | REQ? |  ׯ | | | | | | 5685-085 | ACF/VTAM Version | SNA communications | No | | | 3.4.0 or higher | | |  ׯ | | | | | | 5799-854 | ACF/Network Control | SNA communications | No | | | Program (NCP) | | | | | Version 4.3.1 or | | | | | higher | | |  ׯ | | | | | | 5655-HAL | Transmission Control | TCP/IP | No | | | Protocol/Internet | communications | | | | Protocol (TCP/IP) | | | | | Version 3.1.0 or | | | | | higher | | | | | | | | | | For TCP/IP 3.1, | | | | | PTFs UN94315, | | | | | UN94873, and | | | | | UQ01239 are | | | | | required | | | | | For TCP/IP 3.2, | | | | | PTFs UN94504 and | | | | | UN99683 are | | | | | required | | |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5695-040 | PSF/MVS Version | Printer support | No | | | | 2.2.0 with APAR | | | | | | OW08338 or higher | | |  ׯ | | | | | | | | 5655-B17 | PSF/MVS Version | Printer support | No | | | | 3.1.0 or higher | | |  ר  5.2.2.3 TOLERATION/COEXISTENCE REQUISITES A toleration/coexistence requisite is defined as a product which must be present on a sharing system. These systems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASD environment (such as test and production), or systems that reuse the same DASD at different time intervals. AFP Upload does not have toleration requisites.  5.2.3 DASD STORAGE REQUIREMENTS AFP Upload libraries can reside on 3390 (or 3380) DASD. Figure 10 lists the total space required for each type of library. ׯ | Figure 10. Total DASD Space (in 3390 tracks) Required by AFP | | Upload |  ׯ | | | LIBRARY TYPE | TOTAL SPACE REQUIRED |  ׯ | | | | Target | 60 tracks |  ׯ | | | | Distribution | 115 tracks |  ר NOTES: 1. The data set sizes specified contain 15% extra space. You may wish to revise these numbers based on your plans for adding additional function or service. Installation Requirements and Considerations 11 2. IBM recommends use of system determined blocksizes for efficient DASD utilization for all non-RECFM U data sets. For RECFM U data sets, IBM recommends a blocksize of 32760, which is the most efficient from a performance and DASD utilization perspective. If you choose not to use system determined blocksizes, use the blocksizes and numbers of blocks specified to allocate the data sets. Data sets can be reblocked to a larger size. Please note that the maximum allowable blocksize will depend on the type of DASD on which the dataset will reside; for example, the blocksize of datasets on a 3350 DASD cannot exceed 19,069. 3. Abbreviations used for the data set type are: U Unique data set used by only the FMIDs listed. In order to determine the correct storage needed for this data set, this table provides all required information; no other tables (or program directories) need to be referenced for the data set size. S Shared data set used by more than the FMIDs listed. In order to determine the correct storage needed for this data set, the storage size given in this table needs to be added to other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. If you currently have a previous release of this product installed in these libraries, the installation of this release will delete the old one and reclaim the space used by the old release and any service that had been installed. You can determine whether or not these libraries have enough space by deleting the old release with a dummy function, compressing the libraries, and comparing the space requirements with the free space in the libraries. For more information on the names and sizes of the required data sets, please refer to 6.1.8, "Allocate SMP/E Target and Distribution Libraries" on page 18. ׯ | Figure 11. Storage Requirements for SMP/E Work Data Sets |  ׯ | | | | | D | R | L | | | NO. | | | | | T | S | E | R | | | OF | NO. | NO. | | | Y | O | C | E | NO. | | 3380/| OF | OF | | LIBRARY | P | R | F | C | OF | BLK | 9345 | 3390 | DIR | | DDNAME | E | G | M | L | BLKS | SIZE | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | | | SMPWRK1 | S | PO | FB | 80 | -- | -- | -- | 75 | 50 |  ׯ | | | | | | | | | | | | SMPWRK2 | S | PO | FB | 80 | -- | -- | -- | 75 | 50 |  ׯ | | | | | | | | | | | | SMPWRK3 | S | PO | FB | 80 | -- | -- | -- | 75 | 50 |  ׯ | | | | | | | | | | | | SMPWRK4 | S | PO | FB | 80 | -- | -- | -- | 75 | 50 |  ׯ | | | | | | | | | | | | SMPWRK6 | S | PO | FB | 80 | -- | -- | -- | 75 | 50 |  ׯ | | | | | | | | | | | | SYSUT1 | U | PS | -- | -- | -- | -- | -- | 75 | 0 |  ׯ | | | | | | | | | | | | SYSUT2 | U | PS | -- | -- | -- | -- | -- | 75 | 0 |  ׯ | | | | | | | | | | | | SYSUT3 | U | PS | -- | -- | -- | -- | -- | 75 | 0 |  ׯ | | | | | | | | | | | | SYSUT4 | U | PS | -- | -- | -- | -- | -- | 75 | 0 |  ר The following table provides an estimate of the storage needed in the SMP/E data sets for AFP Upload. The estimates must be added to those of any other programs and service being installed to determine the total additional storage requirements. 12 AFP Upload Program Directory ׯ | Figure 12. Storage Requirements for SMP/E Data Sets |  ׯ | | | | | D | R | L | | | NO. | | | | | T | S | E | R | | | OF | NO. | NO. | | | Y | O | C | E | NO. | | 3380/| OF | OF | | LIBRARY | P | R | F | C | OF | BLK | 9345 | 3390 | DIR | | DDNAME | E | G | M | L | BLKS | SIZE | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | | | SMPLTS | S | PO | U | 0 | 16 | 23000 | -- | 7 | 1 |  ׯ | | | | | | | | | | | | SMPMTS | S | PO | FB | 80 | 16 | 8800 | -- | 2 | 1 |  ׯ | | | | | | | | | | | | SMPPTS | S | PO | FB | 80 | 48 | 8800 | -- | 3 | 1 |  ׯ | | | | | | | | | | | | SMPSCDS | S | PO | FB | 80 | 16 | 8800 | -- | 2 | 1 |  ׯ | | | | | | | | | | | | SMPSTS | S | PO | FB | 80 | 16 | 8800 | -- | 2 | 1 |  ר The following figures list the target and distribution libraries (data sets) and their attributes required to install AFP Upload. The storage requirements of AFP Upload must be added to the storage required by other programs having data in the same data set (library). ׯ | Figure 13. Storage Requirements for AFP Upload Target Libraries |  ׯ | | | | | D | R | L | | | NO. | | | | | T | S | E | R | | | OF | NO. | NO. | | | Y | O | C | E | NO. | | 3380/| OF | OF | | LIBRARY | P | R | F | C | OF | BLK | 9345 | 3390 | DIR | | DDNAME | E | G | M | L | BLKS | SIZE | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | | | SAUPSAMP | U | PO| FB | 80 | 5 | 8800 | 1 | 1 | 2 |  ׯ | | | | | | | | | | | | SAUPLOAD | U | PO| U | 0 | 56 | 6144 | 10 | 8 | 1 |  ר ׯ | Figure 14. Storage Requirements for AFP Upload Distribution | | Libraries |  ׯ | | | | | D | R | L | | | NO. | | | | | T | S | E | R | | | OF | NO. | NO. | | | Y | O | C | E | NO. | | 3380/| OF | OF | | LIBRARY | P | R | F | C | OF | BLK | 9345 | 3390 | DIR | | DDNAME | E | G | M | L | BLKS | SIZE | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | | | AAUPSAMP | U | PO | FB | 80 | 5 | 8800 | 1 | 1 | 2 |  ׯ | | | | | | | | | | | | AAUPLOAD | U | PO | U | 0 | 111 | 6144 | 20 | 16 | 13 |  ר  5.3 SPECIAL CONSIDERATIONS AFP Upload consists of two components. The first component runs on a RISC System/6000 along with PSF for AIX and takes data off the AIX spool, transforms it to MO:DCA-P if necessary, and passes it to the host via System Network Architecture (SNA) or TCP/IP. The second component, AFP Upload, runs on a S/390, receives the print data and places it on the JES spool for printing by PSF/MVS. The software requirements for the workstation component are: AIX Version 3.2.5 or AIX Version 4.1.3 or above. IBM PSF for AIX Version 2.1 (5765-505) with APAR IX57887 or above. For SNA communications, one of the following is also required: SNA Server/6000 Version 2.1.x (for AIX Version 3.2.5). SNA Server/6000 Version 2.2.x (for AIX Version 4.x). SNA Server/6000 Version 3.1.x (for AIX Version 4.x SMP).  Installation Requirements and Considerations 13 Communications Server for AIX Version 4 (for AIX Version 4.1.2 or later). For TCP/IP communications, support is built into AIX, and no additional software is required. 14 AFP Upload Program Directory 6.0 INSTALLATION INSTRUCTIONS  This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of AFP Upload. Please note the following: If you want to install AFP Upload into its own SMP/E environment, consult the SMP/E manuals for instructions on creating and initializing the SMPCSI and the SMP/E control data sets. Sample jobs have been provided to help perform some or all of the installation tasks. The SMP/E jobs assume that all DDDEF entries required for SMP/E execution have been defined in the appropriate zones. The SMP/E dialogs may be used instead of the sample jobs to accomplish the SMP/E installation steps.  6.1 INSTALLING AFP UPLOAD  6.1.1 SMP/E CONSIDERATIONS FOR INSTALLING AFP UPLOAD This release of AFP Upload is installed using the SMP/E RECEIVE, APPLY, and ACCEPT commands. The SMP/E dialogs may be used to accomplish the SMP/E installation steps.  6.1.2 SMP/E ENVIRONMENT All SMP/E installation jobs provided assume that all necessary DD statements for the execution of SMP/E are defined using DDDEFs. Sample jobs are provided to assist you in installing AFP Upload. After the RECEIVE step has been completed, the sample jobs can be found in SMPTLIB: IBM.HPRF227.F2. Make a copy of these jobs in your own library and modify them to use during the installation of AFP Upload. The sample jobs are: AUPALLOC Sample job to allocate target and distribution libraries AUPDDDEF Sample job to define SMP/E DDDEFs AUPAPCK Sample APPLY CHECK job AUPAPPLY Sample APPLY job AUPACCK Sample ACCEPT CHECK job AUPACCEP Sample ACCEPT job In the sample SMP/E jobs provided, the name of the SMP/E CSI is "#GLOBALCSI". The global zone name in the SMP/E CSI is "GLOBAL". The distribution zone name is "#DZONE". The target zone name is "#TZONE". The sample jobs should be updated to reflect the CSI and zone names used at your installation.  6.1.3 SMP/E OPTIONS SUBENTRY VALUES The recommended values for some SMP/E CSI subentries are shown in Figure 15. Use of values lower than these may result in failures in the installation process. DSSPACE is a subentry in the GLOBAL options entry. PEMAX is a subentry of the GENERAL entry in the GLOBAL options entry. Refer to the SMP/E manuals for instructions on updating the global zone. (C) Copyright IBM Corp. 1996, 1998 15 ׯ | Figure 15. SMP/E Options Subentry Values |  ׯ | | | SUB-ENTRY | VALUE | COMMENT |  ׯ | | | | | DSSPACE | (20,10,15)TRK | Recommended value for AFP Upload |  ׯ | | | | | PEMAX | 9999 | The SMP/E default is larger than | | | | what can be specified here |  ר  6.1.4 SMP/E CALLLIBS PROCESSING AFP Upload uses the CALLLIBS function provided in SMP/E Release 8 to resolve external references during installation. When AFP Upload is installed, ensure the following: Verify that the SMP/E SMPLTS data set has been allocated. Refer to SMP/E Reference for information on allocating the SMPLTS data set. See Figure 12 on page 12 for space requirements for the SMPLTS data set. Provide DDDEFs for the following PL/I runtime libraries and APPC library. PLITASK PLIBASE SIBMBASE CSSLIB See 6.1.9, "Create DDDEF Entries" on page 20 for a sample job to define these DDDEFs. If you want to use LE instead of PL/I V2R3, see Appendix B, "Using IBM Language Environment for MVS" on page 29 for additional instructions. NOTE: The DDDEFs above are used only to resolve the link-edit for AFP Upload using CALLLIBS. These data sets are not updated during the installation of AFP Upload.  6.1.5 UNLOAD THE SAMPLE JCL FROM THE PRODUCT TAPE Sample installation jobs are provided on the distribution tape to help you install AFP Upload. The following sample JCL will copy the AFP Upload jobs from the tape. Add a job card and modify the parameters in boldface to uppercase values to meet your site's requirements before submitting. ׯ | | | //STEP1 EXEC PGM=IEBCOPY | | //SYSPRINT DD SYSOUT=A | | //IN DD DSN=IBM.HPRF227.F2,UNIT=TUNIT,VOL=SER=PRF227, | | // LABEL=(3,SL),DISP=(OLD,KEEP) | | //OUT DD DSNAME=JCL-LIBRARY-NAME, | | // DISP=(NEW,CATLG,DELETE), | | // VOL=SER=DASDVOL,UNIT=DUNIT, | | // DCB=*.STEP1.IN,SPACE=(8800,(10,2,2)) | | //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1)) | | //SYSIN DD * | | COPY INDD=IN,OUTDD=OUT | | /* | | | ר Figure 16. Sample UNLOAD Job where TUNIT is the unit value matching the product tape or cartridge, JCL-LIBRARY-NAME is the name of the data set where the sample jobs will reside, DASDVOL is the volume serial of the DASD device where the data set will reside, and DUNIT is the DASD unit type of the volume. You can also access the sample installation jobs by performing an SMP/E RECEIVE for FMID HPRF227, and then copying the jobs from dataset HLQ.IBM.HPRF227.F2 to a work dataset for editing and submission.  16 AFP Upload Program Directory 6.1.6 PERFORM SMP/E RECEIVE The JCL in Figure 17 on page 17 is a sample job to RECEIVE AFP Upload. Create JCL similar to this example, modify the job to specify the appropriate parameters for your installation. NOTE: if you obtained AFP Upload as part of a CBPDO, you can use the RCVPDO job found in the CBPDO RIMLIB data set to RECEIVE the AFP Upload FMIDs as well as any service, HOLDDATA, or preventive service planning (PSP) information included on the CBPDO tape. For more information, refer to the documentation included with the CBPDO. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from this job. ׯ | | | //AUPRCV JOB 'account #','name',MSGLEVEL=(1,1) | | //************************************************************* | | //* MAKE THE FOLLOWING MODIFICATIONS: * | | //* 1) CHANGE THE JOB CARD TO MEET YOUR LOCAL REQUIREMENTS * | | //* 2) CHANGE #GLOBALCSI - TO THE DATASET NAME OF YOUR * | | //* GLOBAL CSI DATASET * | | //* 3) CHANGE tape TO A VALID TAPE UNIT NAME * | | //************************************************************* | | //RECEIVE EXEC PGM=GIMSMP,REGION=4096K | | //SMPCSI DD DSN=#GLOBALCSI, | | // DISP=SHR | | //SMP.SMPPTFIN DD DSN=SMPMCS,DISP=(OLD,PASS), | | // VOL=SER=PRF227,LABEL=(1,SL), | | // UNIT=(tape,,DEFER) | | //SMP.SMPCNTL DD * | | SET BDY(GLOBAL). | | RECEIVE S(HPRF227) SYSMODS . | | /* | | | ר Figure 17. Sample SMP/E RECEIVE Job  6.1.7 RECEIVE CUMULATIVE SERVICE TAPE, IF APPLICABLE A cumulative service tape may be shipped with the product package. If no cumulative service tape is shipped or if the product is received by CBPDO, disregard this section. The JCL in Figure 18 on page 18 is a sample job to RECEIVE the PTFs and HOLDDATA from the cumulative service tape. Create JCL similar to this example, modify the job to specify the appropriate parameters for your installation. If any of the PTFs on the tape have a system hold by the ++HOLD SYSTEM modification control statement with a reason ID equal to UCLIN, file 6 of the cumulative service tape will contain the UCLIN for that PTF. The instructions for the UCLIN are contained in the cover letter of the PTF. NOTE: This step is bypassed if receiving the product from a CBPDO. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from this job. Installation Instructions 17 ׯ | | | //RECEIVEC JOB 'account #','name',MSGLEVEL=(1,1) | | //************************************************************* | | //* RECEIVE CUMULATIVE SERVICE DATA. * | | //* MAKE THE FOLLOWING MODIFICATIONS: * | | //* 1) CHANGE THE JOB CARD TO MEET YOUR LOCAL REQUIREMENTS * | | //* 2) CHANGE #globalcsi - TO THE DATA SET NAME OF YOUR * | | //* GLOBAL CSI DATA SET * | | //* 3) CHANGE tape TO A VALID TAPE UNIT NAME * | | //* 4) CHANGE sssssss TO A VALID SOURCE NAME * | | //************************************************************* | | //RECEIVE EXEC PGM=GIMSMP,REGION=4096K | | //SMPCSI DD DSN=#globalcsi, | | // DISP=SHR | | //SMPHOLD DD UNIT=tape,LABEL=(4,NL),DISP=SHR, | | // VOL=SER=CUMTAP, | | // DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200) | | //SMPPTFIN DD UNIT=tape,LABEL=(1,NL),DISP=SHR, | | // VOL=SER=CUMTAP, | | // DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200) | | //SMP.SMPCNTL DD * | | SET BDY(GLOBAL). | | RECEIVE SYSMODS HOLDDATA SOURCEID(sssssss). | | /* | | | ר Figure 18. RECEIVE Job for Cumulative Service Tape  6.1.8 ALLOCATE SMP/E TARGET AND DISTRIBUTION LIBRARIES Edit and submit sample job AUPALLOC to allocate the SMP/E target and distribution libraries for AFP Upload. The sample job is shown in Figure 19 on page 19. Modify the sample job to specify the appropriate parameters for your installation, using the comments in the job as a guide. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from this job.  18 AFP Upload Program Directory ׯ | | | //AUPALLOC JOB 'account #','name',MSGLEVEL=(1,1) | | //*********************************************************** | | //* * | | //* THIS JCL WILL ALLOCATE TARGET AND DISTRIBUTION * | | //* LIBRARIES FOR AFP UPLOAD. * | | //* * | | //* CAUTION: THIS IS NEITHER A JCL PROCEDURE NOR A * | | //* COMPLETE JOB. BEFORE USING THIS JOB STEP, YOU WILL * | | //* HAVE TO MAKE THE FOLLOWING MODIFICATIONS: * | | //* * | | //* 1) CHANGE THE JOB CARD TO MEET YOUR LOCAL REQUIREMENTS * | | //* 2) CHANGE #HLQ TO THE DESIRED HIGH-LEVEL QUALIFIER * | | //* 3) CHANGE tttttt TO THE VOLSER FOR THE TARGET * | | //* LIBRARIES, AND tuuu TO THE CORRESPONDING UNIT TYPE * | | //* 4) CHANGE dddddd TO THE VOLSER FOR THE DISTRIBUTION * | | //* LIBRARIES, AND duuu TO THE CORRESPONDING UNIT TYPE * | | //* * | | //*********************************************************** | | //ALLOC PROC HLQ='#HLQ', | | // TUNIT=tuuu,TVOL=tttttt, | | // DUNIT=duuu,DVOL=dddddd | | //ALLOC1 EXEC PGM=IEFBR14 | | //* | | //*********************************************************** | | //* ALLOCATE TARGET LIBRARIES * | | //*********************************************************** | | //* | | //SAUPSAMP DD DSN=&HLQ..SAUPSAMP, | | // DISP=(NEW,CATLG), | | // DCB=(RECFM=FB,LRECL=80,BLKSIZE=8800), | | // UNIT=&TUNIT,VOL=SER=&TVOL,SPACE=(8800,(5,2,2)) | | //* | | //SAUPLOAD DD DSN=&HLQ..SAUPLOAD, | | // DISP=(NEW,CATLG), | | // DCB=(RECFM=U,LRECL=0,BLKSIZE=6144), | | // UNIT=&TUNIT,VOL=SER=&TVOL,SPACE=(6144,(62,5,1)) | | //* | | | ר Figure 19 (Part 1 of 2). Sample Allocate Job  Installation Instructions 19 ׯ | | | //*********************************************************** | | //* ALLOCATE DISTRIBUTION LIBRARIES * | | //*********************************************************** | | //* | | //AAUPSAMP DD DSN=&HLQ..AAUPSAMP, | | // DISP=(NEW,CATLG), | | // DCB=(RECFM=FB,LRECL=80,BLKSIZE=8800), | | // UNIT=&DUNIT,VOL=SER=&DVOL,SPACE=(8800,(5,2,2)) | | //* | | //AAUPLOAD DD DSN=&HLQ..AAUPLOAD, | | // DISP=(NEW,CATLG), | | // DCB=(RECFM=U,LRECL=0,BLKSIZE=6144), | | // UNIT=&DUNIT,VOL=SER=&DVOL,SPACE=(6144,(125,15,16)) | | //* | | //EALLOC PEND | | //* | | //ALLOCAT EXEC ALLOC | | /* | | | ר Figure 19 (Part 2 of 2). Sample Allocate Job 6.1.9 CREATE DDDEF ENTRIES SMP/E DDDEF entries for each target and distribution library data set should be defined at this time, if not already done. Also, DDDEF entries for the data sets defined for the CALLLIBS function should be defined. See 6.1.4, "SMP/E CALLLIBS Processing" on page 16 for information on DDDEF entries for the CALLLIBS function. Edit and submit sample job AUPDDDEF to create DDDEF entries for the SMP/E target and distribution libraries for AFP Upload. The sample job is shown in Figure 20 on page 21. Modify the sample job to specify the appropriate parameters for your installation, using the comments in the job as a guide. NOTE: If you want to use LE instead of PL/I V2R3, see Appendix B, "Using IBM Language Environment for MVS" on page 29 for additional instructions, prior to submitting the AUPDDDEF job. If the CALLLIBs DDDEFs: CSSLIB, PLIBASE, PLITASK and SIBMBASE, are already defined in the target zone, delete these statements from AUPDDDEF before running this job. If this job is re-run, change the "ADD" command to "REP" to replace the existing entries. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from this job. 20 AFP Upload Program Directory ׯ | | | //AUPDDDEF JOB 'acct. no.','name',MSGLEVEL=(1,1) | | //************************************************************ | | //* * | | //* THIS JCL WILL CREATE DDDEF ENTRIES FOR AFP UPLOAD. * | | //* * | | //* CAUTION: THIS IS NEITHER A JCL PROCEDURE NOR A * | | //* COMPLETE JOB. BEFORE USING THIS JOB STEP, YOU WILL * | | //* HAVE TO MAKE THE FOLLOWING MODIFICATIONS: * | | //* * | | //* 1) CHANGE THE JOB CARD TO MEET YOUR LOCAL REQUIREMENTS * | | //* 2) CHANGE #GLOBALCSI TO THE DATASET NAME OF YOUR * | | //* GLOBAL CSI DATASET * | | //* 3) CHANGE #TZONE TO THE NAME OF YOUR TARGET ZONE * | | //* 4) CHANGE #DZONE TO THE NAME OF YOUR DISTRIBUTION ZONE * | | //* 5) CHANGE #HLQ TO THE DESIRED HIGH-LEVEL QUALIFIER * | | //* 6) CHANGE tttttt TO THE VOLSER FOR THE TARGET * | | //* LIBRARIES, AND tuuu TO THE CORRESPONDING UNIT TYPE. * | | //* 7) CHANGE dddddd TO THE VOLSER FOR THE DISTRIBUTION * | | //* LIBRARIES, AND duuu TO THE CORRESPONDING UNIT TYPE. * | | //* 8) CHANGE PLI.V2R3M0.PLIBASE, PLI.V2R3M0.SIBMBASE, AND * | | //* AND PLI.V2R3M0.PLITASK TO THE DATA SET NAMES OF * | | //* YOUR PLI runtime LIBRARIES. * | | //* * | | //************************************************************ | | //DDDEF EXEC PGM=GIMSMP,REGION=4096K | | //SMPCSI DD DSN=#GLOBALCSI, | | // DISP=SHR | | //SMPCNTL DD * | | SET BDY(#TZONE). | | UCLIN. | | /********************************************/ | | /* DEFINE THE DDDEFS FOR CALLLIBS LIBRARIES */ | | /********************************************/ | | ADD DDDEF (CSSLIB) | | DATASET(SYS1.CSSLIB) | | SHR. | | ADD DDDEF (PLIBASE) | | DATASET(PLI.V2R3M0.PLIBASE) | | SHR. | | ADD DDDEF (SIBMBASE) | | DATASET(PLI.V2R3M0.SIBMBASE) | | SHR. | | ADD DDDEF (PLITASK) | | DATASET(PLI.V2R3M0.PLITASK) | | SHR. | | | ר Figure 20 (Part 1 of 2). JCL to Create Target and Distribution DDDEFs Installation Instructions 21 ׯ | | | /************************************/ | | /* DEFINE THE DDDEFS FOR THE TARGET */ | | /* AND DISTRIBUTION LIBRARIES */ | | /************************************/ | | ADD DDDEF (SAUPSAMP) | | DATASET(#HLQ.SAUPSAMP) | | UNIT(tuuu) VOLUME (tttttt) | | OLD. | | ADD DDDEF (SAUPLOAD) | | DATASET(#HLQ.SAUPLOAD) | | UNIT(tuuu) VOLUME (tttttt) | | OLD. | | ADD DDDEF (AAUPSAMP) | | DATASET(#HLQ.AAUPSAMP) | | UNIT(duuu) VOLUME (dddddd) | | SHR. | | ADD DDDEF (AAUPLOAD) | | DATASET(#HLQ.AAUPLOAD) | | UNIT(duuu) VOLUME (dddddd) | | SHR. | | ENDUCL. | | SET BDY(#DZONE). | | UCLIN. | | ADD DDDEF (AAUPSAMP) | | DATASET(#HLQ.AAUPSAMP) | | UNIT(duuu) VOLUME (dddddd) | | OLD. | | ADD DDDEF (AAUPLOAD) | | DATASET(#HLQ.AAUPLOAD) | | UNIT(duuu) VOLUME (dddddd) | | OLD. | | ENDUCL. | | /* | | | ר Figure 20 (Part 2 of 2). JCL to Create Target and Distribution DDDEFs  6.1.10 PERFORM SMP/E APPLY CHECK Edit and submit sample job AUPAPCK to perform an SMP/E APPLY CHECK for AFP Upload. To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the following on the APPLY CHECK: PRE, ID, REQ, and IFREQ. This is because the SMP/E root cause analysis identifies the cause only of ERRORS and not of WARNINGS (SYSMODs that are bypassed are treated as warnings, not errors, by SMP/E). The GROUPEXTEND operand indicates that SMP/E apply all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions. The sample job is shown in Figure 21 on page 23. Modify the sample job to specify the appropriate parameters for your installation, using the comments in the job as a guide. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from the APPLY CHECK job. 22 AFP Upload Program Directory ׯ | | | //AUPAPCK JOB 'account #','name',MSGLEVEL=(1,1) | | //************************************************************* | | //* MAKE THE FOLLOWING MODIFICATIONS: * | | //* 1) CHANGE THE JOB CARD TO MEET YOUR LOCAL REQUIREMENTS * | | //* 2) CHANGE #GLOBALCSI TO THE DATASET NAME OF YOUR * | | //* GLOBAL CSI DATASET * | | //* 3) CHANGE #TZONE TO THE NAME OF YOUR TARGET ZONE * | | //************************************************************* | | //APPLYC EXEC PGM=GIMSMP,REGION=4096K | | //SMPCSI DD DSN=#GLOBALCSI, | | // DISP=SHR | | //SMP.SMPCNTL DD * | | SET BDY(#TZONE). | | APPLY CHECK S(HPRF227) | | FORFMID(HPRF227) | | BYPASS(HOLDSYS,HOLDUSER,HOLDCLASS(UCLREL,ERREL)) | | GROUPEXTEND. | | /* | | | ר Figure 21. Sample SMP/E APPLY CHECK Job  6.1.11 PERFORM SMP/E APPLY Edit and submit sample job AUPAPPLY to perform an SMP/E APPLY for AFP Upload. The sample job is shown in Figure 22. Modify the sample job to specify the appropriate parameters for your installation, using the comments in the job as a guide. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from the APPLY job. ׯ | | | //AUPAPPLY JOB 'account #','name',MSGLEVEL=(1,1) | | //************************************************************* | | //* MAKE THE FOLLOWING MODIFICATIONS: * | | //* 1) CHANGE THE JOB CARD TO MEET YOUR LOCAL REQUIREMENTS * | | //* 2) CHANGE #GLOBALCSI TO THE DATASET NAME OF YOUR * | | //* GLOBAL CSI DATASET * | | //* 3) CHANGE #TZONE TO THE NAME OF YOUR TARGET ZONE * | | //************************************************************* | | //APPLY EXEC PGM=GIMSMP,REGION=4096K | | //SMPCSI DD DSN=#GLOBALCSI, | | // DISP=SHR | | //SMP.SMPCNTL DD * | | SET BDY(#TZONE). | | APPLY S(HPRF227) | | FORFMID(HPRF227) | | BYPASS(HOLDCLASS(UCLREL,ERREL)) | | GROUPEXTEND. | | /* | | | ר Figure 22. Sample SMP/E APPLY Job  6.1.12 PERFORM SMP/E ACCEPT CHECK Edit and submit sample job AUPACCK to perform an SMP/E ACCEPT CHECK for AFP Upload. To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the following on the ACCEPT CHECK: PRE, ID, REQ, and IFREQ. This is because the SMP/E root cause analysis identifies the cause only of ERRORS and not of WARNINGS (SYSMODs that are bypassed are treated as warnings, not errors, by SMP/E). Installation Instructions 23 The GROUPEXTEND operand indicates that SMP/E accept all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions. The sample job is shown in Figure 23. Modify the sample job to specify the appropriate parameters for your installation, using the comments in the job as a guide. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from the ACCEPT CHECK job. ׯ | | | //AUPACCK JOB 'account #','name',MSGLEVEL=(1,1) | | //************************************************************* | | //* MAKE THE FOLLOWING MODIFICATIONS: * | | //* 1) CHANGE THE JOB CARD TO MEET YOUR LOCAL REQUIREMENTS * | | //* 2) CHANGE #GLOBALCSI TO THE DATASET NAME OF YOUR * | | //* GLOBAL CSI DATASET * | | //* 3) CHANGE #DZONE TO THE NAME OF YOUR DISTRIBUTION ZONE * | | //************************************************************* | | //ACCEPTC EXEC PGM=GIMSMP,REGION=4096K | | //SMPCSI DD DSN=#GLOBALCSI, | | // DISP=SHR | | //SMP.SMPCNTL DD * | | SET BDY(#DZONE). | | ACCEPT CHECK S(HPRF227) | | FORFMID(HPRF227) | | BYPASS(HOLDSYS,HOLDUSER,HOLDCLASS(UCLREL,ERREL)) | | GROUPEXTEND. | | /* | | | ר Figure 23. Sample SMP/E ACCEPT CHECK Job  6.1.13 PERFORM SMP/E ACCEPT Edit and submit sample job AUPACCEP to perform an SMP/E ACCEPT for AFP Upload. Before using SMP/E to load new distribution libraries, it is recommended that you set the ACCJCLIN indicator in the distribution zone. This will cause entries produced from JCLIN to be saved in the distribution zone whenever a SYSMOD containing inline JCLIN is ACCEPTed. For more information on the ACCJCLIN indicator, see the description of inline JCLIN in the SMP/E manuals. The sample job is shown in Figure 24 on page 25. Modify the sample job to specify the appropriate parameters for your installation, using the comments in the job as a guide. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from the ACCEPT job. If PTFs containing replacement modules are being ACCEPTed, SMP/E ACCEPT processing will linkedit/bind the modules into the distribution libraries. During this processing, the Linkage Editor or Binder may issue messages documenting unresolved external references, resulting in a return code of 4 from the ACCEPT step. These messages can be ignored, because the distribution libraries are not executable and the unresolved external references will not affect the executable system libraries. 24 AFP Upload Program Directory ׯ | | | //AUPACCEP JOB 'account #','name',MSGLEVEL=(1,1) | | //************************************************************* | | //* MAKE THE FOLLOWING MODIFICATIONS: * | | //* 1) CHANGE THE JOB CARD TO MEET YOUR LOCAL REQUIREMENTS * | | //* 2) CHANGE #GLOBALCSI TO THE DATASET NAME OF YOUR * | | //* GLOBAL CSI DATASET * | | //* 3) CHANGE #DZONE TO THE NAME OF YOUR DISTRIBUTION ZONE * | | //************************************************************* | | //ACCEPT EXEC PGM=GIMSMP,REGION=4096K | | //SMPCSI DD DSN=#GLOBALCSI, | | // DISP=SHR | | //SMP.SMPCNTL DD * | | SET BDY(#DZONE). | | ACCEPT S(HPRF227) | | FORFMID(HPRF227) | | BYPASS(HOLDCLASS(UCLREL,ERREL)) | | GROUPEXTEND COMPRESS(ALL). | | /* | | | ר Figure 24. Sample SMP/E ACCEPT Job  6.2 ACTIVATING AFP UPLOAD The appropriate configuration guide contains the step-by-step procedures to activate the functions of AFP Upload: For SNA communications, refer to AFP Upload Configuration Guide Using SNA, S544-5422. For TCP/IP communications, refer to AFP Upload Configuration Guide Using TCP/IP, S544-5423. The following sample JCL is provided to assist you in configuring AFP Upload for SNA communications: AUPTPPRF Sample JCL to create an APPC/MVS TP profile Installation Instructions 25  26 AFP Upload Program Directory APPENDIX A. AFP UPLOAD INSTALL LOGIC  A.1 SMP/E MODIFICATION CONTROL STATEMENTS The entire set of SMP modification control statements for the installation can be obtained by printing the first file of the AFP Upload program tape. The Install Logic for AFP Upload follows: ++FUNCTION(HPRF227 ) REWORK(1998163 ) RFDSNPFX(IBM ) FILES(3) /***********************************************************/ /* 5695-040 (C) COPYRIGHT IBM CORP. */ /* 1996 */ /* ALL RIGHTS RESERVED */ /* US GOVERNMENT USERS RESTRICTED RIGHTS */ /* - USE, DUPLICATION OR DISCLOSURE */ /* RESTRICTED BY GSA ADP SCHEDULE */ /* CONTRACT BY IBM. */ /* */ /* LICENSED MATERIALS - PROPERTY OF IBM */ /***********************************************************/ . ++VER(Z038 ) SUP(AW21017 AW22183 AW27432 AW33621 AW33695 UW30822 UW31580 UW39048 UW49150 UW49247 ) . ++JCLIN CALLLIBS RELFILE(1) .  A.2 SMP/E JCLIN  The JCLIN for AFP Upload is contained in the RELFILEs on the installation tape. These files will be loaded to disk by SMP/E when the product is SMP/E RECEIVEd. You may browse or print these files using TSO/E, ISPF, or IEBGENER (or IEBPTPCH). The files containing JCLIN are: FMID HPRF227: 'high-level-qualifier'.HPRF227.F1(HPRF227) NOTE: The high-level qualifier is the qualifier specified as the DSPREFIX in the SMP/E OPTIONS. (C) Copyright IBM Corp. 1996, 1998 27  28 AFP Upload Program Directory APPENDIX B. USING IBM LANGUAGE ENVIRONMENT FOR MVS  The IBM Language Environment (LE) for MVS, which includes PL/I runtime libraries, can be used with AFP Upload instead of the PL/I V2R3 product. Changes are required at both installation and execution time in order to use LE. An overview of these changes is as follows: Installation - modify DDDEFs for CALLLIBS libraries Execution - modify the STEPLIB to point to the LE libraries  B.1 DECIDING WHETHER TO USE LE SNA: If you want to use AFP Upload with SNA, follow the instructions in the sections below for using LE. APPC/MVS provides the multi-tasking capabilities required by the AFP Upload SNA program, so the considerations listed in this section for AFP Upload with TCP/IP do not apply. TCP/IP: If you want to use AFP Upload with TCP/IP, additional considerations apply. The AFP Upload TCP/IP program uses PL/I multi-tasking capabilities. The PL/I multi-tasking support in Language Environment requires the OpenEdition MVS Services of MVS/ESA SP V5 or above. Therefore, to use LE with AFP Upload TCP/IP, all of the following must be true: 1. Language Environment Version 1 Release 5 or later must be installed. 2. The fix for LE APAR PN81331 must be installed. NOTE: There is more than one APAR to describe this fix, depending on the level of LE. APAR PN81331 applies to LE 1.5, and to the OS/390 R1 and R2 levels of LE. PTF UQ01984 for JMWL530 PTF UQ02004 for JMWL630 APAR PQ12915 applies to the OS/390 R3 - R5 levels of LE. PTF UQ14725 for HMWL710 PTF UQ14726 for HMWL810 APAR PQ19051 applies to the OS/390 R6 level of LE. PTF UQ21233 for HMWL910 3. One of the following OpenEdition MVS Services must be running: 5655-068 OpenEdition MVS Services in MVS/ESA SP JES2 V5 or higher 5655-069 OpenEdition MVS Services in MVS/ESA SP JES3 V5 or higher 5645-001 OpenEdition System Services of OS/390 Version 1 or higher 5647-A01 OpenEdition System Services of OS/390 Version 2 or higher If these three conditions are not met, then you should use the PL/I V2R3 libraries when you install and execute AFP Upload using the TCP/IP protocol. (C) Copyright IBM Corp. 1996, 1998 29 B.2 INSTALLATION CHANGES TO USE LE The AUPDDDEF sample JCL as distributed on the product tape uses the PL/I V2R3 libraries to resolve SMP/E CALLLIBS. To use Language Environment, you must change the DDDEFs for the CALLLIBS libraries to point to the LE data sets instead of the PL/I data sets. Modify the AUPDDDEF job, shown in Figure 20 on page 21, to change the DDDEFs for PLIBASE, SIBMBASE, and PLITASK to reference LE data sets as follows: Use  ADD DDDEF (PLIBASE) DATASET(CEE.V1R5M0.SCEELKED) SHR. ADD DDDEF (SIBMBASE) DATASET(CEE.V1R5M0.SCEELKED) SHR. ADD DDDEF (PLITASK) DATASET(CEE.V1R5M0.SIBMTASK) SHR. instead of  ADD DDDEF (PLIBASE) DATASET(PLI.V2R3M0.PLIBASE) SHR. ADD DDDEF (SIBMBASE) DATASET(PLI.V2R3M0.SIBMBASE) SHR. ADD DDDEF (PLITASK) DATASET(PLI.V2R3M0.PLITASK) SHR. Note that both the PLIBASE and SIBMBASE DDDEFs should point to the CEE.V1R5M0.SCEELKED data set.  B.3 EXECUTION CHANGES TO USE LE At execution time, the Language Environment runtime library, CEE.V1R5M0.SCEERUN should be used instead of the PL/I data sets.  B.3.1 USING LE WITH AFP UPLOAD SNA: The AUPTPPRF sample JCL is provided to create an APPC/MVS TP profile. Modify the STEPLIB to use the appropriate LE runtime library. Remove the DD statements for the PLILINK and SIBMLINK libraries. Use  //STEP EXEC PGM=AUPSNAS //STEPLIB DD DSN=AUP.SAUPLOAD,DISP=SHR // DD DSN=CEE.V1R5M0.SCEERUN,DISP=SHR instead of  //STEP EXEC PGM=AUPSNAS //STEPLIB DD DSN=AUP.SAUPLOAD,DISP=SHR // DD DSN=PLI.V2R3M0.PLILINK,DISP=SHR // DD DSN=PLI.V2R3M0.SIBMLINK,DISP=SHR  30 AFP Upload Program Directory B.3.2 USING LE WITH AFP UPLOAD TCP/IP: Sample JCL to invoke the AFP Upload TCP/IP program is shown in AFP Upload Configuration Guide Using TCP/IP, S544-5423, but no sample JCL is provided on the product tape. Modify the STEPLIB to use the appropriate LE runtime library. Remove the DD statements for the PLILINK and SIBMLINK libraries. Use  //STEP EXEC PGM=AUPTCPS //STEPLIB DD DSN=AUP.SAUPLOAD,DISP=SHR // DD DSN=CEE.V1R5M0.SCEERUN,DISP=SHR instead of  //STEP EXEC PGM=AUPTCPS //STEPLIB DD DSN=AUP.SAUPLOAD,DISP=SHR // DD DSN=PLI.V2R3M0.PLILINK,DISP=SHR // DD DSN=PLI.V2R3M0.SIBMLINK,DISP=SHR  Appendix B. Using IBM Language Environment for MVS 31  32 AFP Upload Program Directory  33  34 AFP Upload Program Directory READER'S COMMENTS  PROGRAM DIRECTORY FOR AFP UPLOAD FOR AIX FEATURE OF PSF/MVS SERVICE LEVEL 9824 You may use this form to comment about this document, its organization, or subject matter with the understanding that IBM may use or distribute whatever information you supply in any way it believes appropriate without incurring any obligation to you. For each of the topics below please indicate your satisfaction level by circling your choice from the rating scale. If a statement does not apply, please circle N. RATING SCALE ׯ | | | very very not | | satisfied <=====================> dissatisfied applicable | | 1 2 3 4 5 N | | | ר  ׯ | | SATISFACTION |  ׯ | | | | Ease of product installation | 1 | 2 | 3 | 4 | 5 | N |  ׯ | | | | | | | | | Contents of program directory | 1 | 2 | 3 | 4 | 5 | N |  ׯ | | | | | | | | | Installation Verification Programs | 1 | 2 | 3 | 4 | 5 | N |  ׯ | | | | | | | | | Time to install the product | 1 | 2 | 3 | 4 | 5 | N |  ׯ | | | | | | | | | Readability and organization of program | 1 | 2 | 3 | 4 | 5 | N | | directory tasks | | | | | | |  ׯ | | | | | | | | | Necessity of all installation tasks | 1 | 2 | 3 | 4 | 5 | N |  ׯ | | | | | | | | | Accuracy of the definition of the | 1 | 2 | 3 | 4 | 5 | N | | installation tasks | | | | | | |  ׯ | | | | | | | | | Technical level of the installation | 1 | 2 | 3 | 4 | 5 | N | | tasks | | | | | | |  ׯ | | | | | | | | | Ease of getting the system into | 1 | 2 | 3 | 4 | 5 | N | | production after installation | | | | | | |  ר How did you order this product? __ CBIPO __ CBPDO __ CustomPac __ ServerPac __ Independent __ Other Is this the first time your organization has installed this product? __ Yes __ No Were the people who did the installation experienced with the installation of MVS products? __ Yes __ No  (C) Copyright IBM Corp. 1996, 1998 35  If yes, how many years? __ If you have any comments to make about your ratings above, or any other aspect of the product installation, please list them below: ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________  36 AFP Upload Program Directory Please provide the following contact information: ____________________________________________________________ Name and Job Title ____________________________________________________________ Organization ____________________________________________________________ ____________________________________________________________ Address ____________________________________________________________ Telephone Thank you for your participation. Please send the completed form to (or give to your IBM representative who will forward it to the AFP Upload for AIX feature of PSF/MVS Development group): IBM Printing Systems Company Attention: Dept. RJXA/003G BOX 1900 Boulder, CO. 80301-9191 USA FAX Number: (800) 524-1519 E-Mail: printpub@us.ibm.com Reader's Comments 37 IBM Program Number: 5655-B17,5695-040 5811 5812 5338  Printed in U.S.A.