SCRIPT/VS 4.0.0: DEVICE 1403N6 CHARS MONO Program Directory for Download for OS/390 Version 3 Release 1, Modification Level 0  Program Number 5655-B17  FMID JPRF312  for Use with MVS OS/390 Document Date: January 1999  GI10-0226-00 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 1995,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 . . . . . . . . . . . . . . . . . . . . . . . . . . . vi 1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Download Description . . . . . . . . . . . . . . . . . . . 2 1.2 Download FMID . . . . . . . . . . . . . . . . . . . . . . . 2 2.0 PROGRAM MATERIALS . . . . . . . . . . . . . . . . . . . . . 3 2.1 Basic Machine-Readable Material . . . . . . . . . . . . . . 3 2.2 Optional Machine-Readable Material . . . . . . . . . . . . . 4 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 . . . . . . . . . . 5 3.0 PROGRAM SUPPORT . . . . . . . . . . . . . . . . . . . . . . 6 3.1 Program Services . . . . . . . . . . . . . . . . . . . . . . 6 3.2 Preventive Service Planning . . . . . . . . . . . . . . . . 6 3.3 Statement of Support Procedures . . . . . . . . . . . . . . 6 4.0 PROGRAM AND SERVICE LEVEL INFORMATION . . . . . . . . . . . 8 4.1 Program Level Information . . . . . . . . . . . . . . . . . 8 4.2 Service Level Information . . . . . . . . . . . . . . . . . 8 4.3 Cumulative Service Tape . . . . . . . . . . . . . . . . . . 8 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 . . . . . . . . . . . . . . . . . 10 5.2.1 Machine Requirements . . . . . . . . . . . . . . . . . . 10 5.2.2 Programming Requisites . . . . . . . . . . . . . . . . . 10 5.2.2.1 Minimum Requisites . . . . . . . . . . . . . . . . . 10 5.2.2.2 Functional Requisites . . . . . . . . . . . . . . . 11 5.2.2.3 Toleration/Coexistence Requisites . . . . . . . . . 12 5.2.2.4 Incompatibility (Negative) Requisites . . . . . . . 12 5.2.3 DASD Storage Requirements . . . . . . . . . . . . . . . 12 5.3 FMIDs Deleted . . . . . . . . . . . . . . . . . . . . . . . 16 5.4 Special Considerations . . . . . . . . . . . . . . . . . . . 16 6.0 INSTALLATION INSTRUCTIONS . . . . . . . . . . . . . . . . . 17 6.1 Installing Download . . . . . . . . . . . . . . . . . . . . 17 6.1.1 SMP/E Considerations for Installing Download . . . . . . 17 6.1.2 SMP/E Environment . . . . . . . . . . . . . . . . . . . 17 6.1.3 SMP/E Options Subentry Values . . . . . . . . . . . . . 18 6.1.4 Perform SMP/E RECEIVE . . . . . . . . . . . . . . . . . 18 6.1.5 RECEIVE the Cumulative Service Tape . . . . . . . . . . 19  (C) Copyright IBM Corp. 1995,1998 iii 6.1.6 Allocate SMP/E Target and Distribution Libraries . . . . 20 6.1.7 Perform SMP/E APPLY CHECK . . . . . . . . . . . . . . . 20 6.1.8 Perform SMP/E APPLY . . . . . . . . . . . . . . . . . . 20 6.1.9 Perform SMP/E ACCEPT CHECK . . . . . . . . . . . . . . . 21 6.1.10 Perform SMP/E ACCEPT . . . . . . . . . . . . . . . . . 21 6.2 Activating Download . . . . . . . . . . . . . . . . . . . . 22 APPENDIX A. DOWNLOAD INSTALL LOGIC . . . . . . . . . . . . . . . 24 A.1 SMP/E Modification Control Statements . . . . . . . . . . . 24 A.1.1 FMID JPRF312 . . . . . . . . . . . . . . . . . . . . . . 24 A.2 SMP/E JCLIN . . . . . . . . . . . . . . . . . . . . . . . . 24 READER'S COMMENTS . . . . . . . . . . . . . . . . . . . . . . . . 26 FIGURES  1. Basic Material: Program Tape . . . . . . . . . . . . . . . . 3 2. Program Tape: File Content . . . . . . . . . . . . . . . . . 4 3. Basic Material: Unlicensed Publications . . . . . . . . . . 4 4. Publications Useful During Installation . . . . . . . . . . 5 5. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . 6 6. Component IDs . . . . . . . . . . . . . . . . . . . . . . . 7 7. Driving System Software Requirements . . . . . . . . . . . . 10 8. Minimum Requisites . . . . . . . . . . . . . . . . . . . . . 11 9. Functional Requisites . . . . . . . . . . . . . . . . . . . 11 10. Total DASD Space Required by Download . . . . . . . . . . . 13 11. Storage Requirements for SMP/E Work Data Sets . . . . . . . 14 12. Storage Requirements for SMP/E Data Sets . . . . . . . . . . 14 13. Storage Requirements for Download Target Libraries . . . . . 15 14. Storage Requirements for Download Distribution Libraries . . 15 15. Storage Requirements for Download Non-SMP/E Data Sets . . . 15 16. SMP/E Options Subentry Values . . . . . . . . . . . . . . . 18 17. RECEIVE Job for Cumulative Service Tape . . . . . . . . . . 19 Contents iv 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. (C) Copyright IBM Corp. 1995,1998 v 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: AIX(R) MVS/ESA CBPDO OS/390(R) CBIPO Print Services Facility DFSMS ProductPac DFSMS/MVS PSF IBM(R) RETAIN InfoPrint(R) S/390(R) MVS SP  Notices vi 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 Download for OS/390, a feature of Print Services Facility (PSF) Version 3 Release 1 for OS/390. This publication refers to Download for OS/390 as Download. 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 Download. 3.0, "Program Support" on page 6 describes the IBM support available for Download. 4.0, "Program and Service Level Information" on page 8 lists the APARs (program level) and PTFs (service level) incorporated into Download. 5.0, "Installation Requirements and Considerations" on page 9 identifies the resources and considerations for installing and using Download. 6.0, "Installation Instructions" on page 17 provides detailed installation instructions for Download. It also describes the procedures for activating the functions of Download, or refers to appropriate publications. Appendix A, "Download Install Logic" on page 24 provides the install logic for Download. Before installing Download, read 3.2, "Preventive Service Planning" on page 6. 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 Download 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 Download 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 Download are included on the CBPDO tape.  (C) Copyright IBM Corp. 1995,1998 1 1.1 DOWNLOAD DESCRIPTION Download automatically transmits data from the JES spool to remote systems using Transmission Control Protocol/Internet Protocol (TCP/IP). This eliminates the need for manual print file transfer using File Transfer Protocol (FTP). A cooperating print server or archive server running on the remote system receives the data sets for printing with PSF for AIX or InfoPrint Manager for AIX, or for archiving using EDMSuite OnDemand. Download provides high-speed data transfer, JES scheduling, job management, data integrity, and job accounting for distributed production print management.  1.2 DOWNLOAD FMID Download consists of the following FMID: JPRF312  Introduction 2 2.0 PROGRAM MATERIALS  An IBM program is identified by a program number and a feature number. The program number for Download is 5655-B17. 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 Download. 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 17 for more information about how to install the program. Figure 1 describes the tape or cartridge. Figure 2 on page 4 describes the file content of the program tape or cartridge. NOTE: If you are installing Download 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 | 6090 | 1 | PSF DOWNLOAD V3.1 | PRF312 |  ׯ | | | | | | | 3480 cart. | 6091 | 1 | PSF DOWNLOAD V3.1 | PRF312 |  ׯ | | | | | | | 4mm cart. | 6092 | 1 | PSF DOWNLOAD V3.1 | PRF312 |  ר (C) Copyright IBM Corp. 1995,1998 3 ׯ | Figure 2. Program Tape: File Content |  ׯ | | | | | | DIST | | | BLK | | VOLSER | FILE | NAME | LIBRARY | RECFM | LRECL | SIZE |  ׯ | | | | | | | | | PRF312 | 1 | SMPMCS | n/a | FB | 80 | 8800 |  ׯ | | | | | | | | | | 2 | IBM.JPRF312.F1 | JCLIN | FB | 80 | 8800 |  ׯ | | | | | | | | | | 3 | IBM.JPRF312.F2 | AAPSMOD0| U | 0 | 6144 |  ׯ | | | | | | | |  | | 4 | IBM.JPRF312.F3 | ASAMPLIB, FB | 80 | 8800 | | | | | | APROCLIB| | | |  ר  2.2 OPTIONAL MACHINE-READABLE MATERIAL No optional machine-readable materials are provided for Download.  2.3 PROGRAM PUBLICATIONS The following sections identify the basic and optional publications for Download.  2.3.1 BASIC PROGRAM PUBLICATIONS Figure 3 identifies the basic unlicensed program publications for Download. One copy of this publication is included when you order the basic materials for Download. For additional copies, contact your IBM representative. ׯ | Figure 3. Basic Material: Unlicensed Publications |  ׯ | | | PUBLICATION TITLE | FORM NUMBER |  ׯ | | | | PSF for OS/390: Download for OS/390 | S544-5624 |  ר  2.3.2 OPTIONAL PROGRAM PUBLICATIONS No optional publications are provided for Download.  2.4 PROGRAM SOURCE MATERIALS No program source materials or viewable program listings are provided for Download. Program Materials 4 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 |  ׯ | | | | IBM Print Services Facility for AIX: Print | S544-3817 | | Administration | |  ׯ | | | | IBM InfoPrint Manager for AIX: Administrator's | S544-5595 | | Guide | |  ׯ | | | | EDMSuite OnDemand: Installation and Configuration | G544-5598 | | Guide for UNIX Servers | |  ׯ | | | | EDMSuite OnDemand: Installation and Configuration | G544-5526 | | Guide for Windows NT Servers | |  ר Program Materials 5 3.0 PROGRAM SUPPORT  This section describes the IBM support available for Download.  3.1 PROGRAM SERVICES Contact your IBM representative for specific information about available program services.  3.2 PREVENTIVE SERVICE PLANNING Before installing Download, you should review the current Preventive Service Planning (PSP) information. If you obtained Download as part of a CBPDO, there is HOLDDATA and PSP information included on the CBPDO tape. If you obtained Download 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 Download are: ׯ | Figure 5. PSP Upgrade and Subset ID |  ׯ | | | UPGRADE | SUBSET | DESCRIPTION |  ׯ | | | | | PSFMVS310 | JPRF312 | DOWNLOAD FOR OS/390 |  ר  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 IDs (COMPID) for Download. (C) Copyright IBM Corp. 1995,1998 6 ׯ | Figure 6. Component IDs |  ׯ | | | | | | RETAIN | | FMID | COMPID | COMPONENT NAME | RELEASE |  ׯ | | | | | | JPRF312 | 5655B1701 | PSF V3R1 Download | 312 |  ר Program Support 7 4.0 PROGRAM AND SERVICE LEVEL INFORMATION  This section identifies the program and any relevant service levels of Download. 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.  4.1 PROGRAM LEVEL INFORMATION The following APAR fixes against previous releases of Download have been incorporated into this release. They are listed by FMID. FMID JPRF312 OW12811 OW19814 OW27623 OW13702 OW20061 OW27855 OW13936 OW20079 OW28351 OW15018 OW20090 OW30211 OW16209 OW21299 OW30796 OW17525 OW23852 OW31334 OW17839 OW23937 OW33049 OW19139 OW25560 OW34334 OW19236 4.2 SERVICE LEVEL INFORMATION No PTFs against this release of Download have been incorporated into the product tape.  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. 1995,1998 8 5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS  The following sections identify the system requirements for installing and activating Download. 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 Download.  5.1.1 MACHINE REQUIREMENTS The driving system can run in any hardware environment that supports the required software.  5.1.2 PROGRAMMING REQUIREMENTS (C) Copyright IBM Corp. 1995,1998 9 ׯ | Figure 7. Driving System Software Requirements |  ׯ | | | PROGRAM | PRODUCT NAME AND | | NUMBER | MINIMUM VRM/SERVICE LEVEL |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5668-949 | System Modification Program/Extended (SMP/E) | | | | Release 1.8.1 with PTF UR49485 or higher |  ׯ | | | | | | 5645-001 | SMP/E element of OS/390 Version 1 Release 2 with | | | | PTF UR48837 or higher | | | | SMP/E element of OS/390 Version 1 Release 3 with | | | | PTF UR48840 or higher |  ׯ | | | | | | 5647-A01 | SMP/E element of OS/390 Version 2 Release 4 with | | | | PTF UR48840 or higher | | | | SMP/E element of OS/390 Version 2 Release 5 or | | | | higher |  ר  5.2 TARGET SYSTEM REQUIREMENTS This section describes the environment of the target system required to install and use Download.  5.2.1 MACHINE REQUIREMENTS The target system can run in any hardware environment that supports the required software.  5.2.2 PROGRAMMING REQUISITES  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. Installation Requirements and Considerations 10 ׯ | Figure 8. Minimum Requisites |  ׯ | | | | PRODUCT NAME AND | INSTALL | | PROGRAM NUMBER | MINIMUM VRM/SERVICE LEVEL | REQ? |  ׯ | | | | | 5655-B17 | PSF 3.1.0 for OS/390 | Yes |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5655-068 | MVS/ESA SP JES2 Version 5 Release 2.2 | No | | | | or higher | |  ׯ | | | | | | | 5655-069 | MVS/ESA SP JES3 Version 5 Release 2.2 | No | | | | or higher | |  ׯ | | | | | | | 5645-001 | OS/390 Version 1 Release 1 or higher | No |  ׯ | | | | | | | 5647-A01 | OS/390 Version 2 Release 4 or higher | No |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5895-DF1 | DFSMS/MVS Version 1.2 | No |  ׯ | | | | | | | 5645-001 | DFSMS Element Of OS/390 Version 1 | No |  ׯ | | | | | | | 5647-A01 | DFSMS Element Of OS/390 Version 2 | No |  ר  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. ׯ | Figure 9 (Page 1 of 2). Functional Requisites |  ׯ | | | | PRODUCT NAME AND | | | | PROGRAM | MINIMUM VRM/SERVICE | | INSTALL | | NUMBER | LEVEL | FUNCTION | REQ? |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5655-HAL | TCP/IP Version 3.2 | Connectivity to | No | | | | with APARs | AIX | | | | | PQ07866, PQ13154, | | | | | | and PQ17052 or | | | | | | higher | | |  ר Installation Requirements and Considerations 11 ׯ | Figure 9 (Page 2 of 2). Functional Requisites |  ׯ | | | | PRODUCT NAME AND | | | | PROGRAM | MINIMUM VRM/SERVICE | | INSTALL | | NUMBER | LEVEL | FUNCTION | REQ? |  ׯ | | | | | 5647-A01 | e-Network | Connectivity to | No | | | | Communication | AIX | | | | | Server element of | | | | | | OS/390 Version 2 | | | | | | Release 5 or | | | | | | higher | | | | | | | | | | | | For OS/390 | | | | | | Version 2 | | | | | | Release 5, | | | | | | APARs PQ13154 | | | | | | and PQ17052 | | | | | | are required | | | | | | For OS/390 | | | | | | Version 2 | | | | | | Release 6, | | | | | | APAR PQ17052 | | | | | | is required | | |  ר  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. Download has no toleration/coexistence requisites.  5.2.2.4 INCOMPATIBILITY (NEGATIVE) REQUISITES A negative requisite identifies products which must not be installed on the same system as this product. Download has no negative requisites.  5.2.3 DASD STORAGE REQUIREMENTS Download libraries can reside on any DASD supported by the operating system. Figure 10 lists the total space required for each type of library. Installation Requirements and Considerations 12 ׯ | Figure 10. Total DASD Space Required by Download |  ׯ | | | LIBRARY TYPE | TOTAL SPACE REQUIRED |  ׯ | | | | Target | 40 Tracks on 3390 DASD |  ׯ | | | | Distribution | 3 Tracks on 3390 DASD |  ר 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. 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.6, "Allocate SMP/E Target and Distribution Libraries" on page 20. Installation Requirements and Considerations 13 ׯ | 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 | 3380/| OF | OF | | LIBRARY | P | R | F | C | 9345 | 3390 | DIR | | DDNAME | E | G | M | L | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | SMPWRK1 | S | PO | FB | 80 | 75 | 75 | 50 |  ׯ | | | | | | | | | | SMPWRK2 | S | PO | FB | 80 | 75 | 75 | 50 |  ׯ | | | | | | | | | | SMPWRK3 | S | PO | FB | 80 | 75 | 75 | 50 |  ׯ | | | | | | | | | | SMPWRK4 | S | PO | FB | 80 | 75 | 75 | 50 |  ׯ | | | | | | | | | | SMPWRK6 | S | PO | FB | 80 | 75 | 75 | 50 |  ׯ | | | | | | | | | | SYSUT1 | U | PS | -- | -- | 75 | 75 | 0 |  ׯ | | | | | | | | | | SYSUT2 | U | PS | -- | -- | 75 | 75 | 0 |  ׯ | | | | | | | | | | SYSUT3 | U | PS | -- | -- | 75 | 75 | 0 |  ׯ | | | | | | | | | | SYSUT4 | U | PS | -- | -- | 75 | 75 | 0 |  ר The following table provides an estimate of the storage needed in the SMP/E data sets for Download. The estimates must be added to those of any other programs and service being installed to determine the total additional storage requirements. ׯ | Figure 12. Storage Requirements for SMP/E Data Sets |  ׯ | | | | | D | R | L | NO. | | | | | T | S | E | R | OF | NO. | NO. | | | Y | O | C | E | 3380/| OF | OF | | LIBRARY | P | R | F | C | 9345 | 3390 | DIR | | DDNAME | E | G | M | L | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | SMPLTS (not used) | S | PO | U | 0 | 0 | 0 | 0 |  ׯ | | | | | | | | | | SMPMTS | S | PO | FB | 80 | 0 | 0 | 0 |  ׯ | | | | | | | | | | SMPPTS | S | PO | FB | 80 | 1 | 1 | 1 |  ׯ | | | | | | | | | | SMPSCDS | S | PO | FB | 80 | 0 | 0 | 0 |  ׯ | | | | | | | | | | SMPSTS | S | PO | FB | 80 | 0 | 0 | 0 |  ר Installation Requirements and Considerations 14 The following figures list the target and distribution libraries (data sets) and their attributes required to install Download. The storage requirements of Download must be added to the storage required by other programs having data in the same data set (library). ׯ | Figure 13. Storage Requirements for Download Target Libraries |  ׯ | | | | | D | R | L | NO. | | | | | T | S | E | R | OF | NO. | NO. | | | Y | O | C | E | 3380/| OF | OF | | LIBRARY | P | R | F | C | 9345 | 3390 | DIR | | DDNAME | E | G | M | L | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | LINKLIB | S | PO| U | 0 | 55 | 38 | 1 |  ׯ | | | | | | | | | | PROCLIB | S | PO| FB | 80 | 1 | 1 | 1 |  ׯ | | | | | | | | | | SAMPLIB | S | PO| FB | 80 | 1 | 1 | 1 |  ר ׯ | Figure 14. Storage Requirements for Download Distribution | | Libraries |  ׯ | | | | | D | R | L | NO. | | | | | T | S | E | R | OF | NO. | NO. | | | Y | O | C | E | 3380/| OF | OF | | LIBRARY | P | R | F | C | 9345 | 3390 | DIR | | DDNAME | E | G | M | L | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | AAPSMOD0 | S | PO | U | 0 | 1 | 1 | 1 |  ׯ | | | | | | | | | | APROCLIB | S | PO | FB | 80 | 1 | 1 | 1 |  ׯ | | | | | | | | | | ASAMPLIB | S | PO | FB | 80 | 1 | 1 | 1 |  ר The following figures list data sets that are not used by SMP/E, but are required for Download to execute. ׯ | Figure 15. Storage Requirements for Download Non-SMP/E Data Sets |  ׯ | | | | | D | R | L | NO. | | | | | T | S | E | R | OF | NO. | NO. | | | Y | O | C | E | 3380/| OF | OF | | DATA SET | P | R | F | C | 9345 | 3390 | DIR | | NAME | E | G | M | L | TRKS | TRKS | BLKS |  ׯ | | | | | | | | | | MVSDLOAD.ROUT.FILE | U | PS | FB | 80 | 1 | 1 | 0 |  ר Installation Requirements and Considerations 15 5.3 FMIDS DELETED This is a dependent function and does not explicitly delete previous levels. The previous level of this dependent function, JPRF225, will be implicitly deleted when the base function, HPRF220, is deleted by HPRF310.  5.4 SPECIAL CONSIDERATIONS Download has no special considerations for the target system. Installation Requirements and Considerations 16 6.0 INSTALLATION INSTRUCTIONS  This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of Download. Please note the following: If you want to install Download 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 DOWNLOAD  6.1.1 SMP/E CONSIDERATIONS FOR INSTALLING DOWNLOAD This release of Download 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. The sample JCL provided on the PSF V3.1.0 base product tape as part of FMID HPRF310 can be used to install Download. If FMID HPRF310 has been previously installed, these sample jobs can be found in SYS1.SAMPLIB. If FMID HPRF310 is being installed at the same time as Download, follow the instructions in the Program Directory for HPRF310 to unload the sample JCL from the PSF V3.1.0 base product tape. Make a copy of these jobs in your own library and modify them to use during the installation of Download. The sample jobs are: APSWREC Sample RECEIVE job APSWAPCK Sample APPLY CHECK job APSWAPP Sample APPLY job (C) Copyright IBM Corp. 1995,1998 17 APSWACCK Sample ACCEPT CHECK job APSWACC 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 16. 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. ׯ | Figure 16. SMP/E Options Subentry Values |  ׯ | | | SUB-ENTRY | VALUE | COMMENT |  ׯ | | | | | DSSPACE | (10,5,2)TRK | Recommended value for Download |  ׯ | | | | | PEMAX | 9999 | The SMP/E default is larger than | | | | what can be specified here |  ר  6.1.4 PERFORM SMP/E RECEIVE Edit and submit sample job APSWREC to perform the SMP/E RECEIVE for Download. Consult the instructions in the sample job for more information. Make the following changes to the APSWREC job to receive the Download tape: 1. Change the SMPPTFIN DD statement to specify VOL=SER=PRF312. 2. Change the SELECT operand on the RECEIVE statement to specify SELECT(JPRF312). NOTE: if you obtained Download as part of a CBPDO, you can use the RCVPDO job found in the CBPDO RIMLIB data set to RECEIVE the Download 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: Return code "0" should be received from this job. Installation Instructions 18 6.1.5 RECEIVE THE CUMULATIVE SERVICE TAPE 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 17 on page 19 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. EXPECTED RETURN CODES AND MESSAGES: Return code "0" should be received from this job. ׯ | | | //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 17. RECEIVE Job for Cumulative Service Tape  Installation Instructions 19 6.1.6 ALLOCATE SMP/E TARGET AND DISTRIBUTION LIBRARIES Download uses target and distribution libraries that were allocated by its base function, HPRF310. There are no unique libraries used by Download, so no allocate or DDDEF job is required. You should ensure that sufficient free space is available in the target and distribution libraries prior to continuing with the installation of JPRF312. See Figure 13 on page 15 and Figure 14 on page 15 for information on the amount of space required in the target and distribution libraries.  6.1.7 PERFORM SMP/E APPLY CHECK Edit and submit sample job APSWAPCK to perform an SMP/E APPLY CHECK for Download. Consult the instructions in the sample job for more information. Make the following changes to the APSWAPCK job for Download: 1. Change the SELECT operand on the APPLY CHECK statement to specify SELECT(JPRF312). 2. Change the FORFMID operand on the APPLY CHECK statement to specify FORFMID(JPRF312). 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. EXPECTED RETURN CODES AND MESSAGES: Return code "0" should be received from this job.  6.1.8 PERFORM SMP/E APPLY Edit and submit sample job APSWAPP to perform an SMP/E APPLY for Download. Consult the instructions in the sample job for more information. Make the following changes to the APSWAPP job for Download: 1. Change the SELECT operand on the APPLY statement to specify SELECT(JPRF312). 2. Change the FORFMID operand on the APPLY statement to specify FORFMID(JPRF312). Installation Instructions 20 EXPECTED RETURN CODES AND MESSAGES: Return code "0" should be received from this job.  6.1.9 PERFORM SMP/E ACCEPT CHECK Edit and submit sample job APSWACCK to perform an SMP/E ACCEPT CHECK for Download. Consult the instructions in the sample job for more information. Make the following changes to the APSWACCK job for Download: 1. Change the SELECT operand on the ACCEPT CHECK statement to specify SELECT(JPRF312). 2. Change the FORFMID operand on the ACCEPT CHECK statement to specify FORFMID(JPRF312). 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). The GROUPEXTEND operand indicates that SMP/E accept all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions. EXPECTED RETURN CODES AND MESSAGES: Return code "0" should be received from this job.  6.1.10 PERFORM SMP/E ACCEPT Edit and submit sample job APSWACC to perform an SMP/E ACCEPT for Download. Consult the instructions in the sample job for more information. Make the following changes to the APSWACC job for Download: 1. Change the SELECT operand on the ACCEPT statement to specify SELECT(JPRF312). 2. Change the FORFMID operand on the ACCEPT statement to specify FORFMID(JPRF312). 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. EXPECTED RETURN CODES AND MESSAGES: Return code "0" should be received from this job. Installation Instructions 21 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 IEW0461 or IEW2454W messages documenting unresolved external references, resulting in a return code of 4 from the ACCEPT step. These messages are acceptable, because the distribution libraries are not executable and the unresolved external references will not affect the executable system libraries.  6.2 ACTIVATING DOWNLOAD This section summarizes the tasks involved in configuring the Download feature after your installation. You must complete these tasks before you can verify that the Download installation was successful. These tasks are described in the PSF for OS/390: Download for OS/390. Section titles from that book are referenced in the checklist below, where applicable. 1. Plan the Download functional subsystem - Planning the Download for OS/390 Functional Subsystem. 2. Decide how many functional subsystems (FSS) and functional subsystem applications (FSAs) to create - Defining Multiple Functional Subsystems. __ Determine the region size for each FSS - Selecting a Region Size. __ Decide on the JES work-selection criteria for each FSA - Defining Work-Selection Criteria. __ Decide on a default checkpointing interval for each FSA - Requesting Checkpointing. __ Decide on default printing options, if any, for each FSA - Defining Default Printing Options. 3. Define the Download functional subsystem. JES2 - Defining a JES2 Functional Subsystem. __ Create an FSS(fss_name) statement for each FSS - FSS(fss_name) Statement. __ Create a PRT(nnnn) statement for each FSA - PRT(nnnn) Statement. JES3 - Defining a JES3 Functional Subsystem. __ Create an FSSDEF statement for each FSS - FSSDEF Statement. Installation Instructions 22 __ Create a DEVICE statement for each FSA - DEVICE Statement. 4. Create a startup procedure for each Download FSS - Creating a Download for OS/390 Startup Procedure. 5. Create a routing-control data set. __ Decide on routing criteria to use: class, form, and destination for each server - Defining Routing Criteria. __ Determine the socket address of each associated AIX server - Defining Socket Addresses.  6. Modify installation accounting routines if necessary - Using Accounting Information. 7. Update the MVS Program Properties Table (PPT) - Updating the MVS Program Properties Table. 8. Activate Download Activate the changes to the MVS Program Properties Table and the Download code in SYS1.LINKLIB by either IPLing the MVS or OS/390 system, or by using system commands to enable the changes to SYS1.LINKLIB and the program properties table. 9. Start a Download FSA on the MVS system - Operating Download for OS/390. You should get an APS992I message on the system console after the FSA is started. It is an indication the product is installed successfully. This can be considered a successful IVP of Download. To actually transmit a dataset to your remote system, you need to start the Download server on the remote system. Refer to the appropriate publication for information on configuring the server on the remote system: IBM Print Services Facility for AIX: Print Administration, IBM InfoPrint Manager for AIX: Administrator's Guide, EDMSuite OnDemand: Installation and Configuration Guide for UNIX Servers, or EDMSuite OnDemand: Installation and Configuration Guide for Windows NT Servers Installation Instructions 23 APPENDIX A. DOWNLOAD INSTALL LOGIC  A.1 SMP/E MODIFICATION CONTROL STATEMENTS  The SMP/E Modification Control Statements (SMPMCS) for Download are contained in the SMPMCS file on the installation tape. The SMPMCS for each FMID in the product will be loaded to the SMPPTS dataset, with a member name matching the FMID, when the FMID is SMP/E RECEIVEd. You may browse or print these members using TSO/E, ISPF, or IEBGENER (or IEBPTPCH).  A.1.1 FMID JPRF312 ++FUNCTION(JPRF312) FILES(3) REWORK(1998306) RFDSNPFX(IBM) /*********************************************************/ /* Licensed Materials - Property of IBM */ /* 5655-B17, (C) Copyright IBM Corp. 1984, 1998 */ /* All Rights Reserved */ /* US Government Users Restricted Rights - */ /* Use, duplication or disclosure restricted by */ /* GSA ADP Schedule Contract with IBM Corp. */ /*********************************************************/ . ++VER(Z038) FMID(HPRF310) PRE(JPRF311) SUP(JPRF225) . ++JCLIN RELFILE( 1).  A.2 SMP/E JCLIN  The JCLIN for Download 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 JPRF312: 'high-level-qualifier.JPRF312.F1(JPRF312) NOTE: The high-level qualifier is the qualifier specified as the DSPREFIX in the SMP/E OPTIONS. (C) Copyright IBM Corp. 1995,1998 24  25 READER'S COMMENTS  PROGRAM DIRECTORY FOR DOWNLOAD FOR OS/390 VERSION 3 RELEASE 1, MODIFICATION LEVEL 0 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? (C) Copyright IBM Corp. 1995,1998 26 __ 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 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: ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ Reader's Comments 27 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 Download for OS/390 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 28  IBM Program Number: 5655-B17 6090 6091 6092 Printed in U.S.A.