SCRIPT/VS 4.0.0: DEVICE 1403N6 CHARS MONO Program Directory for IP PrintWay  Program Number 5655-B17  FMID HMOS100  for Use with MVS OS/390  CBPDO Level SMC9704 Service Level 9704 Document Date: January 1999  GI10-0230-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 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . vi 1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 PrintWay Description . . . . . . . . . . . . . . . . . . . 2 1.2 PrintWay 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 . . . . . . . . . . . . . 5 2.4 Program Source Materials . . . . . . . . . . . . . . . . . . 5 2.5 Publications Useful During Installation . . . . . . . . . . 5 3.0 PROGRAM SUPPORT . . . . . . . . . . . . . . . . . . . . . . 7 3.1 Program Services . . . . . . . . . . . . . . . . . . . . . . 7 3.2 Preventive Service Planning . . . . . . . . . . . . . . . . 7 3.3 Statement of Support Procedures . . . . . . . . . . . . . . 7 4.0 PROGRAM AND SERVICE LEVEL INFORMATION . . . . . . . . . . . 9 4.1 Program Level Information . . . . . . . . . . . . . . . . . 9 4.2 Service Level Information . . . . . . . . . . . . . . . . . 9 4.3 Cumulative Service Tape . . . . . . . . . . . . . . . . . . 10 5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS . . . . . . . . 11 5.1 Driving System Requirements . . . . . . . . . . . . . . . . 11 5.1.1 Machine Requirements . . . . . . . . . . . . . . . . . . 11 5.1.2 Programming Requirements . . . . . . . . . . . . . . . . 11 5.2 Target System Requirements . . . . . . . . . . . . . . . . . 12 5.2.1 Machine Requirements . . . . . . . . . . . . . . . . . . 12 5.2.2 Programming Requisites . . . . . . . . . . . . . . . . . 12 5.2.2.1 Minimum Requisites . . . . . . . . . . . . . . . . . 12 5.2.2.2 Functional Requisites . . . . . . . . . . . . . . . 13 5.2.2.3 Toleration/Coexistence Requisites . . . . . . . . . 14 5.2.2.4 Incompatibility (Negative) Requisites . . . . . . . 14 5.2.3 DASD Storage Requirements . . . . . . . . . . . . . . . 15 5.3 FMIDs Deleted . . . . . . . . . . . . . . . . . . . . . . . 18 5.4 Special Considerations . . . . . . . . . . . . . . . . . . . 19 6.0 INSTALLATION INSTRUCTIONS . . . . . . . . . . . . . . . . . 20 6.1 Installing PrintWay . . . . . . . . . . . . . . . . . . . . 20 6.1.1 SMP/E Considerations for Installing PrintWay . . . . . . 20 6.1.2 SMP/E Environment . . . . . . . . . . . . . . . . . . . 20 6.1.3 SMP/E Options Subentry Values . . . . . . . . . . . . . 21 6.1.4 SMP/E CALLLIBS Processing . . . . . . . . . . . . . . . 21 6.1.5 Unload the Sample JCL from the Product Tape . . . . . . 22  (C) Copyright IBM Corp. 1996, 1998 iii 6.1.6 Perform SMP/E RECEIVE . . . . . . . . . . . . . . . . . 22 6.1.7 RECEIVE the Cumulative Service Tape . . . . . . . . . . 23 6.1.8 Allocate SMP/E Target and Distribution Libraries . . . . 24 6.1.9 Create DDDEF Entries . . . . . . . . . . . . . . . . . . 25 6.1.10 Perform SMP/E APPLY CHECK . . . . . . . . . . . . . . . 25 6.1.11 Perform SMP/E APPLY . . . . . . . . . . . . . . . . . . 25 6.1.12 Update MVS System Environment . . . . . . . . . . . . . 26 6.1.12.1 Set up APF Authorization . . . . . . . . . . . . . 26 6.1.12.2 Update Program Properties Table . . . . . . . . . . 26 6.1.12.3 Enable IP PrintWay for OS/390 Systems . . . . . . . 27 6.1.12.4 Customize PrintWay . . . . . . . . . . . . . . . . 28 6.1.13 Perform SMP/E ACCEPT CHECK . . . . . . . . . . . . . . 28 6.1.14 Perform SMP/E ACCEPT . . . . . . . . . . . . . . . . . 28 6.2 Activating PrintWay . . . . . . . . . . . . . . . . . . . . 29 APPENDIX A. PRINTWAY INSTALL LOGIC . . . . . . . . . . . . . . . 30 A.1 SMP/E Modification Control Statements . . . . . . . . . . . 30 A.2 SMP/E JCLIN . . . . . . . . . . . . . . . . . . . . . . . . 30 READER'S COMMENTS . . . . . . . . . . . . . . . . . . . . . . . . 32 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 . . . . . . . . . . . . . . . . . 7 6. Component IDs . . . . . . . . . . . . . . . . . . . . . . . 8 7. Driving System Software Requirements . . . . . . . . . . . . 12 8. Minimum Requisites . . . . . . . . . . . . . . . . . . . . . 12 9. Functional Requisites . . . . . . . . . . . . . . . . . . . 14 10. Total DASD Space Required by PrintWay . . . . . . . . . . . 15 11. Storage Requirements for SMP/E Work Data Sets . . . . . . . 16 12. Storage Requirements for SMP/E Data Sets . . . . . . . . . . 16 13. Storage Requirements for PrintWay Target Libraries . . . . . 17 14. Storage Requirements for PrintWay Distribution Libraries . . 18 15. Storage Requirements for PrintWay Non-SMP/E Data Sets . . . 18 16. SMP/E Options Subentry Values . . . . . . . . . . . . . . . 21 17. Sample SMP/E RECEIVE Job . . . . . . . . . . . . . . . . . . 23 18. RECEIVE Job for Cumulative Service Tape . . . . . . . . . . 24 19. Sample PPT Entry for ANFFIEP . . . . . . . . . . . . . . . . 27 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. 1996, 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: CBIPO Language EnvironmentProductPac CBPDO MVS/ESA PSF IBM(R) NetSpool RETAIN IBMLink OS/390(R) S/390 IP PrintWay PrintWay SystemPac  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 IP PrintWay. This publication refers to IP PrintWay as PrintWay. 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 PrintWay. 3.0, "Program Support" on page 7 describes the IBM support available for PrintWay. 4.0, "Program and Service Level Information" on page 9 lists the APARs (program level) and PTFs (service level) incorporated into PrintWay. 5.0, "Installation Requirements and Considerations" on page 11 identifies the resources and considerations for installing and using PrintWay. 6.0, "Installation Instructions" on page 20 provides detailed installation instructions for PrintWay. It also describes the procedures for activating the functions of PrintWay, or refers to appropriate publications. Appendix A, "PrintWay Install Logic" on page 30 provides the install logic for PrintWay. Before installing PrintWay, read 3.2, "Preventive Service Planning" on page 7. 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 PrintWay 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 PrintWay 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 PrintWay are included on the CBPDO tape. (C) Copyright IBM Corp. 1996, 1998 1 1.1 PRINTWAY DESCRIPTION PrintWay is a robust method of automatically routing JES2 or JES3 print data from your MVS or OS/390 system to printers in your TCP/IP network without changing your application program. It is the strategic replacement for the Network Print Facility (NPF) feature of the MVS TCP/IP product, providing improved function, capacity, performance, and usability. PrintWay is capable of addressing printers in heterogenous networks of operating system Line Printer Daemons (LPDs) and printer LPDs which adhere to industry open protocol standards. PrintWay will take any data format on the spool and use the LPR/LPD protocol to transport it to another spool or printer. Depending on the options specified, the data will either be left alone (the binary option) or transformed from EBCDIC to ASCII (alternate translation tables may be specified). PrintWay can route data to your printer in either of two ways: For maximum flexibility on JES2 systems, and JES3 systems at OS/390 V2R5 or higher, you can specify your host system and printer address directly in your JCL. This gives you dynamic addressing capability for any workstation printer, departmental printer, or system printer in your TCP/IP network. You can select printer destinations which have not been previously defined by the system administrator, thus relieving you of dependencies on other functions to route print jobs within the network. For more centralized control, an update to a routing table can provide the network addressing.  1.2 PRINTWAY FMID PrintWay consists of the following FMID: HMOS100  Introduction 2 2.0 PROGRAM MATERIALS  An IBM program is identified by a program number and a feature number. The program number for IP PrintWay 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 PrintWay. 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 20 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 PrintWay 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 | 5821 | 1 | PSF.PRINTWAY.V310 | MOS100 |  ׯ | | | | | | | 3480 cart. | 5822 | 1 | PSF.PRINTWAY.V310 | MOS100 |  ׯ | | | | | | | 4mm cart. | 5339 | 1 | PSF.PRINTWAY.V310 | MOS100 |  ר (C) Copyright IBM Corp. 1996, 1998 3 ׯ | Figure 2. Program Tape: File Content |  ׯ | | | | | | DIST | | | BLK | | VOLSER | FILE | NAME | LIBRARY | RECFM | LRECL | SIZE |  ׯ | | | | | | | | | MOS100 | 1 | SMPMCS | n/a | FB | 80 | 8800 |  ׯ | | | | | | | | | | 2 | IBM.HMOS100.F1 | JCLIN | FB | 80 | 8800 |  ׯ | | | | | | | | | | 3 | IBM.HMOS100.F2 | AANFSAMP| FB | 80 | 8800 |  ׯ | | | | | | | | | | 4 | IBM.HMOS100.F3 | AANFLOAD| U | 0 | 6144 |  ׯ | | | | | | | | | | 5 | IBM.HMOS100.F4 | AANFPLIB| FB | 80 | 8800 |  ׯ | | | | | | | | | | 6 | IBM.HMOS100.F5 | AANFMLIB| FB | 80 | 8800 |  ׯ | | | | | | | | | | 7 | IBM.HMOS100.F6 | AANFPROC| FB | 80 | 8800 |  ׯ | | | | | | | | | | 8 | IBM.HMOS100.F7 | AANFEXEC| FB | 80 | 8800 |  ׯ | | | | | | | | | | 9 | IBM.HMOS100.F8 | AANFMAC | FB | 80 | 8800 |  ר  2.2 OPTIONAL MACHINE-READABLE MATERIAL No optional machine-readable materials are provided for PrintWay.  2.3 PROGRAM PUBLICATIONS The following sections identify the basic and optional publications for PrintWay.  2.3.1 BASIC PROGRAM PUBLICATIONS Figure 3 identifies the basic unlicensed program publications for PrintWay. One copy of this publication is included when you order the basic materials for PrintWay. For additional copies, contact your IBM representative. ׯ | Figure 3. Basic Material: Unlicensed Publications |  ׯ | | | PUBLICATION TITLE | FORM NUMBER |  ׯ | | | | IBM IP PrintWay Guide | S544-5379 |  ר  Program Materials 4 2.3.2 OPTIONAL PROGRAM PUBLICATIONS No optional publications are provided for PrintWay.  2.4 PROGRAM SOURCE MATERIALS No program source materials or viewable program listings are provided for PrintWay.  2.5 PUBLICATIONS USEFUL DURING INSTALLATION The publications listed in Figure 4 may be useful during the installation of PrintWay. To order copies, contact your IBM representative. ׯ | Figure 4 (Page 1 of 2). 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 |  ׯ | | | | OS/390 MVS Initialization and Tuning Reference | SC28-1752 |  ׯ | | | | MVS/ESA SP V5 Initialization and Tuning Reference | GC28-1452 |  ׯ | | | | OS/390 MVS Authorized Assembler Services Guide | GC28-1763 |  ׯ | | | | OS/390 MVS Authorized Assembler Services Reference | GC28-1764 | | ALE-DYN | |  ׯ | | | | OS/390 MVS Authorized Assembler Services Reference | GC28-1765 | | ENF-IXG | |  ר Program Materials 5 ׯ | Figure 4 (Page 2 of 2). Publications Useful During Installation |  ׯ | | | PUBLICATION TITLE | FORM NUMBER |  ׯ | | | | OS/390 MVS Authorized Assembler Services Reference | GC28-1766 | | LLA-SDU | |  ׯ | | | | OS/390 MVS Authorized Assembler Services Reference | GC28-1767 | | SET-WTO | |  ׯ | | | | MVS/ESA SP V5 Authorized Assembler Services Guide | GC28-1467 |  ׯ | | | | MVS/ESA SP V5 Programming: Authorized Assembler | GC28-1475 | | Services Reference, Volume 1 (ALESERV-DYNALLOC) | |  ׯ | | | | MVS/ESA SP V5 Programming: Authorized Assembler | GC28-1476 | | Services Reference, Volume 2 (ENFREQ-ITTFMTB) | |  ׯ | | | | MVS/ESA SP V5 Programming: Authorized Assembler | GC28-1477 | | Services Reference, Volume 3 (LLACOPY-SDUMPX) | |  ׯ | | | | MVS/ESA SP V5 Programming: Authorized Assembler | GC28-1478 | | Services Reference, Volume 4 (SETFRR-WTOR) | |  ׯ | | | | OS/390 eNetwork Communications Server: IP | SC31-8513 | | Configuration Guide | |  ׯ | | | | IBM TCP/IP for MVS: Customization and Administration | SC31-7134 | | Guide | |  ׯ | | | | IBM NetSpool Guide | G544-5301 |  ׯ | | | | OS/390 Planning for Installation | GC28-1726 |  ׯ | | | | OS/390 MVS Product Management | GC28-1730 |  ר Program Materials 6 3.0 PROGRAM SUPPORT  This section describes the IBM support available for PrintWay.  3.1 PROGRAM SERVICES Contact your IBM representative for specific information about available program services.  3.2 PREVENTIVE SERVICE PLANNING Before installing PrintWay, you should review the current Preventive Service Planning (PSP) information. If you obtained PrintWay as part of a CBPDO, there is HOLDDATA and PSP information included on the CBPDO tape. If you obtained PrintWay 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 PrintWay are: ׯ | Figure 5. PSP Upgrade and Subset ID |  ׯ | | | UPGRADE | SUBSET | DESCRIPTION |  ׯ | | | | | PRINTWAY | HMOS100/9704 | IP PrintWay |  ר  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 PrintWay. (C) Copyright IBM Corp. 1996, 1998 7 ׯ | Figure 6. Component IDs |  ׯ | | | | | | RETAIN | | FMID | COMPID | COMPONENT NAME | RELEASE |  ׯ | | | | | | HMOS100 | 569504004 | IP PrintWay | 100 |  ר Program Support 8 4.0 PROGRAM AND SERVICE LEVEL INFORMATION  This section identifies the program and any relevant service levels of PrintWay. 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 9704.  4.1 PROGRAM LEVEL INFORMATION The following APAR fixes against PrintWay have been incorporated into this Service Update, Service Level 9704. They are listed by FMID. FMID HMOS100 OW22200 OW23485 OW24432 OW22764 OW23537 OW24567 OW22776 OW24227 OW24625 OW23395 OW24266 OW24681 OW23418 4.2 SERVICE LEVEL INFORMATION The following PTFs containing the APAR fixes against PrintWay have been integrated into this Service Update Service Level 9704. 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. (C) Copyright IBM Corp. 1996, 1998 9 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. FMID HMOS100 UW32872-RSU9610 UW34403-PUT9612 UW34953-PUT9701 UW33063-RSU9610 UW34882-PUT9612 UW35216-PUT9701 UW33748-RSU9611 UW34900-PUT9701 UW35307-PUT9701 UW34008-RSU9611 UW34947-RSU9612 UW35373-PUT9701 UW34402-PUT9612 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. Program and Service Level Information 10 5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS  The following sections identify the system requirements for installing and activating PrintWay. 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 PrintWay.  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. 1996, 1998 11 ׯ | Figure 7. Driving System Software Requirements |  ׯ | | | PROGRAM | PRODUCT NAME AND | | NUMBER | MINIMUM VRM/SERVICE LEVEL |  ׯ | | | | 5668-949| System Modification Program/Extended (SMP/E) Release 8.1 | | | or higher |  ר  5.2 TARGET SYSTEM REQUIREMENTS This section describes the environment of the target system required to install and use PrintWay.  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. ׯ | Figure 8 (Page 1 of 2). Minimum Requisites |  ׯ | | | | PRODUCT NAME AND | INSTALL | | PROGRAM NUMBER | MINIMUM VRM/SERVICE LEVEL | REQ? |  ׯ | | | | | 5685-054 | ISPF Version 3.5 or higher | No |  ׯ | | | | | 5685-025 | TSO/E Version 2.4 or higher | No |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5655-068 | MVS/ESA SP JES2 Version 5 Release 2.2 | Yes | | | | or higher | |  ר  Installation Requirements and Considerations 12 ׯ | Figure 8 (Page 2 of 2). Minimum Requisites |  ׯ | | | | PRODUCT NAME AND | INSTALL | | PROGRAM NUMBER | MINIMUM VRM/SERVICE LEVEL | REQ? |  ׯ | | | | | | 5655-069 | MVS/ESA SP JES3 Version 5 Release 2.2 | Yes | | | | or higher | |  ׯ | | | | | | | 5645-001 | OS/390 Version 1 Release 1 or higher | Yes |  ׯ | | | | | | | 5647-A01 | OS/390 Version 2 Release 4 or higher | Yes |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5688-198 | Language Environment for MVS & VM | Yes | | | | Version 1.5 or higher | |  ׯ | | | | | | | 5655-068 | MVS C/C++ Language Support Feature of | Yes | | | 5655-069 | MVS/ESA Version 5.2 | |  ׯ | | | | | | | 5645-001 | Language Environment element of OS/390 | Yes | | | | Version 1 or higher | |  ׯ | | | | | | | 5647-A01 | Language Environment element of OS/390 | Yes | | | | Version 2 or higher | |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5655-HAL | MVS TCP/IP Version 3.2 or higher | Yes |  ׯ | | | | | | | 5647-A01 | eNetwork Communication Server element | Yes | | | | of OS/390 Version 2 Release 5 or higher | |  ר  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. Installation Requirements and Considerations 13 ׯ | Figure 9. Functional Requisites |  ׯ | | | | PRODUCT NAME AND | | | | PROGRAM | MINIMUM VRM/SERVICE | | INSTALL | | NUMBER | LEVEL | FUNCTION | REQ? |  ׯ | | | | | | 5665-488 | SDSF Version 1.6 | Inquiry/modification | No | | | with APAR PN87129 or | of JCL keywords for | | | | higher | printer address, | | | | | retry, and retain | |  ׯ | | | Any ONE of the following: |  ׯ | | | | 5655-068 | MVS/ESA SP JES2 | JCL parameters for | No | | | | Version 5.2 with | dynamically | | | | | APARs OW21839 and | specifying printer | | | | | OW21918 or higher | address, retry, | | | | | | and retain | |  ׯ | | | | | | | | 5645-001 | JES2 element of | JCL parameters for | No | | | | OS/390 Version 1 | dynamically | | | | | or higher | specifying printer | | | | | | address, retry, | | | | | | and retain | |  ׯ | | | | | | | | 5647-A01 | JES3 element of | JCL parameters for | No | | | | OS/390 Version 2 | dynamically | | | | | Release 5 or | specifying printer | | | | | higher | address, retry, | | | | | | and retain | |  ר  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. PrintWay has no toleration/coexistence rquisites.  5.2.2.4 INCOMPATIBILITY (NEGATIVE) REQUISITES A negative requisite identifies products which must not be installed on the same system as this product. PrintWay has no negative requisites.  Installation Requirements and Considerations 14 5.2.3 DASD STORAGE REQUIREMENTS PrintWay libraries can reside on any DASD supported by the operating system. Figure 10 on page 15 lists the total space required for each type of library. ׯ | Figure 10. Total DASD Space Required by PrintWay |  ׯ | | | LIBRARY TYPE | TOTAL SPACE REQUIRED |  ׯ | | | | Target | 61 tracks on 3390 DASD |  ׯ | | | | Distribution | 65 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  Installation Requirements and Considerations 15 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 24. ׯ | 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 | -- | -- | 30 | 30 | 0 |  ׯ | | | | | | | | | | SYSUT2 | U | PS | -- | -- | 30 | 30 | 0 |  ׯ | | | | | | | | | | SYSUT3 | U | PS | -- | -- | 30 | 30 | 0 |  ׯ | | | | | | | | | | SYSUT4 | U | PS | -- | -- | 30 | 30 | 0 |  ר The following table provides an estimate of the storage needed in the SMP/E data sets for PrintWay. The estimates must be added to those of any other programs and service being installed to determine the total additional storage requirements. ׯ | Figure 12 (Page 1 of 2). 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 | S | PO | U | 0 | 30 | 30 | 6 |  ׯ | | | | | | | | | | SMPMTS | S | PO | FB | 80 | 7 | 7 | 2 |  ר  Installation Requirements and Considerations 16 ׯ | Figure 12 (Page 2 of 2). 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 |  ׯ | | | | | | | | | | SMPPTS | S | PO | FB | 80 | 3 | 3 | 2 |  ׯ | | | | | | | | | | SMPSCDS | S | PO | FB | 80 | 0 | 0 | 0 |  ׯ | | | | | | | | | | SMPSTS | S | PO | FB | 80 | 0 | 0 | 0 |  ר The following figures list the target and distribution libraries (data sets) and their attributes required to install PrintWay. The storage requirements of PrintWay must be added to the storage required by other programs having data in the same data set (library). ׯ | Figure 13. Storage Requirements for PrintWay 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 |  ׯ | | | | | | | | | | SANFEXEC | U | PO| FB | 80 | 2 | 2 | 2 |  ׯ | | | | | | | | | | SANFLOAD | U | PO| U | 0 | 26 | 23 | 5 |  ׯ | | | | | | | | | | SANFMAC | U | PO| FB | 80 | 9 | 7 | 2 |  ׯ | | | | | | | | | | SANFMLIB | U | PO| FB | 80 | 2 | 2 | 2 |  ׯ | | | | | | | | | | SANFPLIB | U | PO| FB | 80 | 18 | 15 | 8 |  ׯ | | | | | | | | | | SANFPROC | U | PO| FB | 80 | 1 | 1 | 2 |  ׯ | | | | | | | | | | SANFSAMP | U | PO| FB | 80 | 13 | 11 | 4 |  ר Installation Requirements and Considerations 17 ׯ | Figure 14. Storage Requirements for PrintWay 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 |  ׯ | | | | | | | | | | AANFEXEC | U | PO | FB | 80 | 2 | 2 | 2 |  ׯ | | | | | | | | | | AANFLOAD | U | PO | U | 0 | 30 | 27 | 24 |  ׯ | | | | | | | | | | AANFMAC | U | PO | FB | 80 | 9 | 7 | 2 |  ׯ | | | | | | | | | | AANFMLIB | U | PO | FB | 80 | 2 | 2 | 2 |  ׯ | | | | | | | | | | AANFPLIB | U | PO | FB | 80 | 18 | 15 | 8 |  ׯ | | | | | | | | | | AANFPROC | U | PO | FB | 80 | 1 | 1 | 2 |  ׯ | | | | | | | | | | AANFSAMP | U | PO | FB | 80 | 13 | 11 | 4 |  ר The following figures list data sets that are not used by SMP/E, but are required for PrintWay to execute. ׯ | Figure 15. Storage Requirements for PrintWay 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 |  ׯ | | | | | | | | | | ANF.ROUTING | U | VS | -- | -- | 30 | 30 | -- |  ׯ | | | | | | | | | | ANF.OPTIONS | U | VS | -- | -- | 30 | 30 | -- |  ׯ | | | | | | | | | | ANF.QUEUE | U | VS | -- | -- | 30 | 30 | -- |  ׯ | | | NOTE: Sample job ANFDEAL can be used to allocate the PrintWay | | routing, options, and queue VSAM data sets. For more information | | about these data sets, see IBM IP PrintWay Guide, S544-5379. | ר  5.3 FMIDS DELETED Installing PrintWay will not result in the deletion of any FMIDs. Installation Requirements and Considerations 18 5.4 SPECIAL CONSIDERATIONS If you are installing PrintWay on an OS/390 Release 3 or higher system, the SMP/E processing for FMID HMOS100 was completed as part of the installation of OS/390, and the PrintWay code is already installed in the target and distribution libraries. If you previously installed PrintWay as a feature of PSF/MVS 2.2.0, and your maintenance is at Service Level 9704 or higher, then you do not need to reinstall HMOS100. The FMID is identical to that provided in PSF/MVS 2.2.0. In these cases, skip to 6.1.12.3, "Enable IP PrintWay for OS/390 Systems" on page 27 for instructions on how to dynamically enable PrintWay.  Installation Requirements and Considerations 19 6.0 INSTALLATION INSTRUCTIONS  This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of PrintWay. Please note the following: If you want to install PrintWay 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 PRINTWAY  6.1.1 SMP/E CONSIDERATIONS FOR INSTALLING PRINTWAY This release of PrintWay 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 PrintWay. After the RECEIVE step has been completed, the sample jobs can be found in SMPTLIB: IBM.HMOS100.F2. Make a copy of these jobs in your own library and modify them to use during the installation of PrintWay. The sample jobs are: ANFALLOC Sample job to allocate target and distribution libraries ANFDDDEF Sample job to define SMP/E DDDEFs ANFAPCK Sample APPLY CHECK job ANFAPPLY Sample APPLY job (C) Copyright IBM Corp. 1996, 1998 20 ANFACCK Sample ACCEPT CHECK job ANFACCEP 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 | (50,10,50) | |  ׯ | | | | | PEMAX | 9999 | The SMP/E default is larger than | | | | what can be specified here |  ר  6.1.4 SMP/E CALLLIBS PROCESSING PrintWay uses the CALLLIBS function provided in SMP/E Release 8 to resolve external references during installation. When PrintWay 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. NOTE: For PrintWay, 2 cylinders of 3380/3390 DASD space is adequate for the SMPLTS. Provide DDDEFs for the following libraries: CSSLIB SCEELKED SEZACMTX See 6.1.9, "Create DDDEF Entries" on page 25 for a sample job to define these DDDEFs. Installation Instructions 21 NOTE: The DDDEFs above are used only to resolve the link-edit for PrintWay using CALLLIBS. These data sets are not updated during the installation of PrintWay.  6.1.5 UNLOAD THE SAMPLE JCL FROM THE PRODUCT TAPE Sample installation jobs are provided on the distribution tape to help you install PrintWay. The following sample JCL will copy the PrintWay 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.HMOS100.F2,UNIT=TUNIT,VOL=SER=MOS100, // 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,(8,1,2)) //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1)) //SYSIN DD * COPY INDD=IN,OUTDD=OUT /* 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 HMOS100 and then copying the jobs from dataset HLQ.IBM.HMOS100.F2 to a work dataset for editing and submission.  6.1.6 PERFORM SMP/E RECEIVE Figure 17 on page 23 contains a sample job that can be used to perform the SMP/E RECEIVE for PrintWay. Create JCL similar to this sample, modifying the job to specify the appropriate parameters for your installation. NOTE: if you obtained PrintWay as part of a CBPDO, you can use the RCVPDO job found in the CBPDO RIMLIB data set to RECEIVE the PrintWay 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.  Installation Instructions 22 ׯ | | | //ANFRCV JOB 'account #','name',MSGLEVEL=(1,1) | | //************************************************************* | | //* MAKE THE FOLLOWING MODIFICATIONS: * | | //* 1) CHANGE #GLOBALCSI - TO THE DATASET NAME OF YOUR * | | //* GLOBAL CSI DATASET * | | //* 2) 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=MOS100,LABEL=(1,SL), | | // UNIT=(tape,,DEFER) | | //SMP.SMPCNTL DD * | | SET BDY(GLOBAL). | | RECEIVE S(HMOS100) SYSMOD . | | /* | | | ר Figure 17. Sample SMP/E RECEIVE Job  6.1.7 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, skip this section. Figure 18 on page 24 contains a sample job to RECEIVE the PTFs and HOLDDATA from the cumulative service tape. Create JCL similar to this sample, modifying 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: A return code of "0" should be received from this job. Installation Instructions 23 ׯ | | | //ANFRCVC JOB 'account #','name',MSGLEVEL=(1,1) | | //*************************************************** | | //* RECEIVE CUMULATIVE SERVICE DATA. * | | //* MAKE THE FOLLOWING MODIFICATIONS: * | | //* 1) CHANGE #GLOBALCSI TO THE DATA SET NAME OF * | | //* YOUR GLOBAL CSI DATA SET * | | //* 2) CHANGE tape TO A VALID TAPE UNIT NAME * | | //* 2) CHANGE sssssss TO A VALID SOURCEID 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 ANFALLOC to allocate the SMP/E target and distribution libraries for PrintWay. Consult the instructions in the sample job for more information. The ANFALLOC sample job specifies the storage requirements using average block lengths. BLKSIZE=0 indicates that system-determined block sizes are being used. For example, the sizes might look like this: SPACE=(8800,(135,27,6)), DCB=(RECFM=FB,LRECL=80,BLKSIZE=0) Do not confuse the SPACE=8800 (average block length) parameter with the BLKSIZE=0 (block size) parameter. If you would like to change the block size to something other than the system-determined block size, you can change the BLKSIZE parameter. Do not change the SPACE parameter. You can use the storage allocations as they are, or convert them to cylinder or track allocations. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from this job. Installation Instructions 24 6.1.9 CREATE DDDEF ENTRIES Edit and submit sample job ANFDDDEF to create DDDEF entries for the SMP/E target and distribution libraries for PrintWay. Consult the instructions in the sample job for more information. If the CALLLIBs DDDEFs: CSSLIB SCEELKED SEZACMTX are already defined in the target zone, delete the statements from "ANFDDDEF" before running this job. If the target and distribution data sets that correspond to the DDDEFs will be cataloged, the UNIT and VOLUME parameters can be deleted before the job is run. 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.  6.1.10 PERFORM SMP/E APPLY CHECK Edit and submit sample job ANFAPCK to perform an SMP/E APPLY CHECK for PrintWay. Consult the instructions in the sample job for more information. 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: A return code of "0" should be received from this job.  6.1.11 PERFORM SMP/E APPLY Edit and submit sample job ANFAPPLY to perform an SMP/E APPLY for PrintWay. Consult the instructions in the sample job for more information. When using SMP/E CALLLIBS, you will receive warning messages when the load modules are link edited into the SMPLTS data set. For example:  Installation Instructions 25 IEW2454W SYMBOL xxxxxxxx UNRESOLVED. NO AUTOCALL(NCAL) SPECIFIED IEW2480W EXTERNAL SYMBOL xxxxxxxx OF TYPE LD WAS ALREADY DEFINED AS A SYMBOL OF TYPE LD IN SECTION csectname These warning messages are acceptable. EXPECTED RETURN CODES AND MESSAGES: A return code of "0" should be received from this job.  6.1.12 UPDATE MVS SYSTEM ENVIRONMENT  6.1.12.1 SET UP APF AUTHORIZATION The PrintWay load library ANF.SANFLOAD must be designated as an APF-authorized library. You can accomplish this by either of the following methods: 1. Designate ANF.SANFLOAD as an APF-authorized data set using member PROGnn of SYS1.PARMLIB. 2. If all data sets in the LINKLST concatenation are to be treated as APF-authorized, include ANF.SANFLOAD in the LNKLSTnn member of SYS1.PARMLIB and remove the STEPLIB statements from the procedures and JCL used by PrintWay. Refer to the Authorized Assembler Services Guide for your operating system for more information on APF authorization.  6.1.12.2 UPDATE PROGRAM PROPERTIES TABLE The MVS program properties table must be updated to define the program ANFFIEP to execute with the following special properties: Unique protect key - key 1 System task Non-swappable Data set integrity not required No preferred storage required To update the table, update the appropriate SCHEDxx member of SYS1.PARMLIB. A sample PPT entry for ANFFIEP is shown in Figure 19 on page 27. NOTE: If you are installing PrintWay on an OS/390 Version 2 Release 5 system or higher, the IP PrintWay entry is already included in the system default PPT. You do not have to include ANFFIEP in SCHEDxx on OS/390 Release 5 or higher.  Installation Instructions 26 ׯ | | | /***************************************************************/| | /* Program Properties Table Addition for IP PrintWay */| | /* */| | /* The following defaults are taken for this entry: */| | /* NOPRIV Not a privileged job */| | /* CANCEL Cancellable */| | /* PASS Requires password protection */| | /* AFF(NONE) No affinity to a particular processor */| | /***************************************************************/| | /* */| | PPT PGMNAME(ANFFIEP) /* PROGRAM NAME ANFFIEP */| | KEY(1) /* PROTECTION KEY 1 */| | NOSWAP /* NONSWAPPABLE */| | SYST /* SYSTEM TASK */| | NOPREF /* NO PREFERRED STORAGE REQUIRED */| | NODSI /* DOES NOT REQUIRE DATA SET */| | /* INTEGRITY */| | | ר Figure 19. Sample PPT Entry for ANFFIEP For information on updating the MVS program properties table, refer to the Initialization and Tuning Reference for your operating system.  6.1.12.3 ENABLE IP PRINTWAY FOR OS/390 SYSTEMS If you are installing IP PrintWay on MVS/ESA V5, you may skip this step and continue with 6.1.12.4, "Customize PrintWay" on page 28. If you are installing PrintWay on an OS/390 system, you must complete this step to enable PrintWay. For information on OS/390 dynamic enablement, refer to OS/390 MVS Product Management, GC28-1730. A sample IFAPRDxx entry is provided in member ANFPRDXX of ANF.SANFSAMP. Copy ANFPRDXX into your active IFAPRDxx member of SYS1.PARMLIB to enable PrintWay, following the instructions in ANFPRDXX. Your IFAPRDxx entry should look like this:  PRODUCT OWNER('IBM CORP') NAME('PSF FOR OS/390') ID(5655-B17) VERSION(*) RELEASE(*) MOD(*) FEATURENAME('IP PRINTWAY') STATE(ENABLED) NOTE: The IFAPRDxx entry listed above is for PrintWay when ordered as a feature of PSF Version 3 for OS/390 (described in this program directory). PTF UW53745, which is included on your cumulative service tape, provided the dynamic enablement support for PrintWay as a  Installation Instructions 27 feature of PSF Version 3 for OS/390. PrintWay is also available using alternate ordering methods, and uses a different product statement in those cases. If you ordered PrintWay as a feature of PSF/MVS 2.2.0, or as part of the OS/390 Print Server feature of OS/390 Version 2 Release 5 or higher, refer to the documentation for that product to obtain the correct values to be placed in IFAPRDxx.  6.1.12.4 CUSTOMIZE PRINTWAY After completing the above steps, you may activate PrintWay as described in 6.2, "Activating PrintWay" on page 29 at any time.  6.1.13 PERFORM SMP/E ACCEPT CHECK Edit and submit sample job ANFACCK to perform an SMP/E ACCEPT CHECK for PrintWay. Consult the instructions in the sample job for more information. 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: A return code of "0" should be received from this job.  6.1.14 PERFORM SMP/E ACCEPT Edit and submit sample job ANFACCEP to perform an SMP/E ACCEPT for PrintWay. Consult the instructions in the sample job for more information. 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: A return code of "0" should be received from this 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 IEW0461 or IEW2454W messages documenting unresolved external  Installation Instructions 28 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.  6.2 ACTIVATING PRINTWAY The publication IBM IP PrintWay Guide, S544-5379 contains the step-by-step procedures to activate the functions of PrintWay. Installation Instructions 29 APPENDIX A. PRINTWAY INSTALL LOGIC  A.1 SMP/E MODIFICATION CONTROL STATEMENTS The SMP/E Modification Control Statements (SMPMCS) for PrintWay 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). ++FUNCTION(HMOS100 ) REWORK(1997021 ) RFDSNPFX(IBM ) FILES(8) /***********************************************************/ /* 5695-040, 5645-001 (C) COPYRIGHT IBM CORP. 1996,1997 */ /* 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(AW22200 AW22764 AW22776 AW23395 AW23418 AW23485 AW23537 AW24227 AW24266 AW24432 AW24567 AW24625 AW24681 UW32872 UW33063 UW33748 UW34008 UW34402 UW34403 UW34882 UW34900 UW34947 UW34953 UW35216 UW35307 UW35373 ) . ++JCLIN CALLLIBS RELFILE(1) .  A.2 SMP/E JCLIN  The JCLIN for PrintWay 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 file containing JCLIN is: FMID HMOS100: 'high-level-qualifier.HMOS100.F1(HMOS100)' NOTE: The high-level qualifier is the qualifier specified as the DSPREFIX in the SMP/E OPTIONS.  (C) Copyright IBM Corp. 1996, 1998 30  31 READER'S COMMENTS  PROGRAM DIRECTORY FOR IP PRINTWAY SERVICE LEVEL 9704 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  (C) Copyright IBM Corp. 1996, 1998 32 __ 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 33 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 IP PrintWay 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 34  IBM Program Number: 5655-B17 5821 5822 5339 Printed in U.S.A.