SCRIPT/VS 4.0.0: DEVICE 1403N6 CHARS MONO ¤     Program Directory for  Print Services Facility/MVS   Version 2  Release 2.0, Service Level SMC9618   Program Number 5695-040   FMIDs HPRF220,JPRF223   for Use with  MVS   Document Date: June 1996        GI10-0201-02 ¤   ÚÄÄÄ NOTE! ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | Before using this information and the product it supports, be sure |  | to read the general information under "Notices" on page vii. |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ            This program directory, dated June 1996, applies to Print Services  Facility/MVS Version 2 Release 2.0 (PSF/MVS Version 2.2.0), Program  Number 5695-040 for the following:  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  ¿ ¿  | FMIDS | FEATURE NUMBERS| SYSTEM NAME |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | HPRF220 | 5801/5802/5337 | MVS |  | JPRF223 | | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À  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 1983, 1996.  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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . VII  Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . vii  1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 1  1.1 Print Services Facility/MVS Description . . . . . . . . . . 2  1.2 Overview of PSF/MVS Version 2.2.0 Features . . . . . . . . . 3  1.3 What's New - Packaging Changes . . . . . . . . . . . . . . . 4  2.0 PROGRAM MATERIALS . . . . . . . . . . . . . . . . . . . . . 5  2.1 Basic Machine-Readable Material . . . . . . . . . . . . . . 5  2.1.1 PSF/MVS Version 2.2.0 Machine-Readable Material . . . . 5  2.1.2 ACIF and AFP API Machine-Readable Material . . . . . . . 7  2.1.3 Font Material . . . . . . . . . . . . . . . . . . . . . 7  2.2 Optional Machine-Readable Material . . . . . . . . . . . . . 7  2.2.1 Page Printer Migration Programs Material . . . . . . . . 8  2.2.2 MVS Download Program Material . . . . . . . . . . . . . 8  2.2.3 Netspool Program Material . . . . . . . . . . . . . . . 8  2.2.4 AFP Upload for AIX Program Material . . . . . . . . . . 9  2.3 Program Publications . . . . . . . . . . . . . . . . . . . . 9  2.3.1 Basic Program Publications . . . . . . . . . . . . . . . 9  2.3.2 Optional Program Publications . . . . . . . . . . . . . 12  2.3.3 Publications Useful during Installation . . . . . . . . 13  2.4 Program Source Materials . . . . . . . . . . . . . . . . . . 15  3.0 PROGRAM SUPPORT . . . . . . . . . . . . . . . . . . . . . . 16  3.1 Service Instructions . . . . . . . . . . . . . . . . . . . . 16  3.2 Preventive Service Planning . . . . . . . . . . . . . . . . 16  3.3 Statement of Support Procedures . . . . . . . . . . . . . . 17  4.0 PROGRAM AND SERVICE LEVEL INFORMATION . . . . . . . . . . . 19  4.1 Program Level Information . . . . . . . . . . . . . . . . . 19  4.2 Service Level Information . . . . . . . . . . . . . . . . . 20  4.3 Cumulative Service Tape . . . . . . . . . . . . . . . . . . 22  5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS . . . . . . . . 23  5.1 Driving System Requirements . . . . . . . . . . . . . . . . 23  5.1.1 Programming Requirements . . . . . . . . . . . . . . . . 23  5.1.2 DASD Storage Requirements . . . . . . . . . . . . . . . 24  5.2 Target System Requirements . . . . . . . . . . . . . . . . . 24  5.2.1 Operating System and Programming Requirements . . . . . 24  5.2.2 Machine Requirements . . . . . . . . . . . . . . . . . . 25  5.2.2.1 General Attachment Information and Notes . . . . . . 28  5.2.3 PSF/MVS Version 2.2.0 Requirements for Special Functions 28  5.2.4 DASD Storage Requirements . . . . . . . . . . . . . . . 32  5.2.5 Target and Distribution Library Storage Requirements . . 32  5.2.5.1 Target Library Storage Requirements . . . . . . . . 33  5.2.5.2 Distribution Library Storage Requirements . . . . . 34  5.3 PSF/MVS Version 2.2.0 Installation Considerations . . . . . 35   (C) Copyright IBM Corp. 1983, 1996 iii ¤   5.3.1 Packaging Changes between PSF/MVS Version 2.1.0, PSF/MVS  Version 2.1.1, and PSF/MVS Version 2.2.0 . . . . . . . . . . . 36  5.3.2 Determine the PSF/MVS Version 2.2.0 Installation Option 36  5.3.2.1 Determine Installation Option Number for PSF/MVS  Version 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . 37  5.3.3 Installation Options for PSF/MVS Version 2.2.0 . . . . . 40  5.3.4 Considerations When Installing PSF/MVS Version 2.2.0 . . 43  5.3.5 Special Considerations . . . . . . . . . . . . . . . . . 46  6.0 INSTALLATION INSTRUCTIONS . . . . . . . . . . . . . . . . . 47  6.1 Installation Steps . . . . . . . . . . . . . . . . . . . . . 48  6.1.1 Unload Sample Jobs . . . . . . . . . . . . . . . . . . . 49  6.1.2 Allocate Target and Distribution Library Data Sets . . . 50  6.1.3 Create Target and Distribution Library DDDEFs . . . . . 53  6.1.4 Copy PSF/MVS Target Libraries from a Previous Release 57  6.1.4.1 Copy PSF/MVS LINKLIB into Another APF Authorized  Library . . . . . . . . . . . . . . . . . . . . . . . . . . 58  6.1.4.2 Copy PSF/MVS Resources to a Temporary Data Set . . . 58  6.1.4.3 Copy PSF/MVS Installation Exits to a Temporary Data  Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58  6.1.4.4 Copy PSF/MVS Startup Procedures to a Temporary Data  Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59  6.1.5 RECEIVE PSF/MVS Version 2.2.0 Applicable FMIDs . . . . . 59  6.1.6 RECEIVE Cumulative Service Tape, if Applicable . . . . . 60  6.1.7 Transfer Ownership of SYSMODS using UCLIN . . . . . . . 61  6.1.8 Delete PSF/MVS . . . . . . . . . . . . . . . . . . . . . 64  6.1.9 Perform APPLY CHECK . . . . . . . . . . . . . . . . . . 65  6.1.10 Load Target Libraries Using APPLY . . . . . . . . . . . 66  6.1.11 Perform I/O Configuration . . . . . . . . . . . . . . . 67  6.1.12 Modify the System Environment for PSF/MVS Version 2.2.0 67  6.1.13 Enable PSF/MVS Version 2.2.0 for OS/390 Systems . . . . 68  6.1.14 Re-IPL the MVS System . . . . . . . . . . . . . . . . . 68  6.1.15 Perform ACCEPT CHECK . . . . . . . . . . . . . . . . . 68  6.1.16 Load Distribution Libraries Using ACCEPT . . . . . . . 69  6.1.17 Replace PSF/MVS Startup Procedures from Previous Release 70  6.1.18 Perform Installation Verification . . . . . . . . . . . 70  6.1.19 Replace PSF/MVS Resources from Previous Release . . . . 70  6.1.20 Replace PSF/MVS Installation Exits from Previous Release 71  7.0 INSTALLATION VERIFICATION PROCEDURE . . . . . . . . . . . . 72  7.1 PSF/MVS Version 2.2.0 IVP . . . . . . . . . . . . . . . . . 72  7.1.1 Perform Tasks before Installation Verification . . . . . 72  7.1.2 Complete the Installation Verification . . . . . . . . . 72  7.1.2.1 IVP Job for JES Environment . . . . . . . . . . . . 73  7.1.2.2 IVP Job for Direct-Attach Environment . . . . . . . 75  APPENDIX A. SMP/E INSTALL LOGIC . . . . . . . . . . . . . . . . 78  A.1 FMID HPRF220 SMPMCS . . . . . . . . . . . . . . . . . . . . 78  A.2 FMID JPRF223 SMPMCS . . . . . . . . . . . . . . . . . . . . 81  A.3 PSF/MVS Version 2.2.0 JCLIN . . . . . . . . . . . . . . . . 82  APPENDIX B. STARTUP PROCEDURES FOR PSF/MVS VERSION 2.2.0 . . . . 84  B.1 Startup Procedure APSWPROA . . . . . . . . . . . . . . . . . 84  B.2 Startup Procedure APSWPROB . . . . . . . . . . . . . . . . . 88   Contents iv ¤   B.3 Startup Procedure APSWPROC . . . . . . . . . . . . . . . . . 92  B.4 Startup Procedure APSWPROD . . . . . . . . . . . . . . . . . 94  B.5 Startup Procedure APSWPROM . . . . . . . . . . . . . . . . . 98  B.6 Startup Procedure APSWPROP . . . . . . . . . . . . . . . . 102  B.7 Startup Procedure APSWPROS . . . . . . . . . . . . . . . . 105  B.8 Startup Procedure APSWPROT . . . . . . . . . . . . . . . . 108  APPENDIX C. NEW FUNCTIONS ADDED TO PSF/MVS VERSION 2.2.0 . . . 111  APPENDIX D. SMP/E DIALOG PANEL INFORMATION . . . . . . . . . . 118  APPENDIX E. CHECKLIST FOR PSF/MVS VERSION 2.2.0 INSTALLATION . 120  APPENDIX F. PTF COVER LETTER DATA FOR SERVICE LEVEL SMC9618 . 122  F.1 Cover Letter for PTF UW26752 . . . . . . . . . . . . . . . 122  F.2 Cover Letter for PTF UW26952 . . . . . . . . . . . . . . . 126  F.3 Cover Letter for PTF UW27158 . . . . . . . . . . . . . . . 129  F.4 Cover Letter for PTF UW27811 . . . . . . . . . . . . . . . 131  F.5 Cover Letter for PTF UW24450 . . . . . . . . . . . . . . . 134  F.6 Cover Letter for PTF UW24497 . . . . . . . . . . . . . . . 141  F.7 Cover Letter for PTF UW24258 . . . . . . . . . . . . . . . 151  F.8 Cover Letter for PTF UW13461 . . . . . . . . . . . . . . . 152  F.9 Cover Letter for PTF UW14560 . . . . . . . . . . . . . . . 154  F.10 Cover Letter for PTF UW19699 . . . . . . . . . . . . . . 154  F.11 Cover Letter for PTF UW21345 . . . . . . . . . . . . . . 156  F.12 Cover Letter for PTF UW23722 . . . . . . . . . . . . . . 162  F.13 Cover Letter for PTF UW25033 . . . . . . . . . . . . . . 170  F.14 Cover Letter for PTF UW25143 . . . . . . . . . . . . . . 174  F.15 Cover Letter for PTF UW25289 . . . . . . . . . . . . . . 178  F.16 Cover Letter for PTF UW25414 . . . . . . . . . . . . . . 182  F.17 Cover Letter for PTF UW18208 . . . . . . . . . . . . . . 184  F.18 Cover Letter for PTF UW17799 . . . . . . . . . . . . . . 186  F.19 Cover Letter for PTF UW09923 . . . . . . . . . . . . . . 188  F.20 Cover Letter for PTF UW09923 . . . . . . . . . . . . . . 194  F.21 Cover Letter for PTF UW14135 . . . . . . . . . . . . . . 198  F.22 Cover Letter for PTF UW16360 . . . . . . . . . . . . . . 199  F.23 Cover Letter for PTF UW11285 . . . . . . . . . . . . . . 205  F.24 Cover Letter for PTF UW09797 . . . . . . . . . . . . . . 210  F.25 Cover Letter for PTF UW10401 . . . . . . . . . . . . . . 212  F.26 Cover Letter for PTF UW19390 . . . . . . . . . . . . . . 214  F.27 Cover Letter for PTF UW15755 . . . . . . . . . . . . . . 215  F.28 Cover Letter for PTF UW15401 . . . . . . . . . . . . . . 217  F.29 Cover Letter for PTF UW19599 . . . . . . . . . . . . . . 220  F.30 Cover Letter for PTF UW20320 . . . . . . . . . . . . . . 221  APPENDIX G. READER'S COMMENTS . . . . . . . . . . . . . . . . 225     Contents v ¤   FIGURES    1. Basic Material: PSF/MVS Version 2.2.0 Tape . . . . . . . . . 5  2. Program Tape: PSF/MVS Version 2.2.0 Tape File Content . . . 6  3. Basic Program Publications . . . . . . . . . . . . . . . . . 9  4. Basic Material: Licensed Publications . . . . . . . . . . . 12  5. Optional Program Publications . . . . . . . . . . . . . . . 12  6. Useful Program Publications . . . . . . . . . . . . . . . . 13  7. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . 17  8. Component IDs . . . . . . . . . . . . . . . . . . . . . . . 18  9. Abbreviations used for the data set type . . . . . . . . . . 32  10. Storage Requirements for PSF/MVS Version 2.2.0 Target  Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 34  11. Storage Requirements for PSF/MVS Version 2.2.0 Distribution  Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 35  12. Sample JCL to Unload PSF/MVS Version 2.2.0 Sample Jobs . . . 49  13. Job to Allocate PSF/MVS Version 2.2.0 Data Sets . . . . . . 51  14. JCL to Create Target and Distribution DDDEFs for PSF/MVS  Version 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . 54  15. RECEIVE Job for PSF/MVS Version 2.2.0 . . . . . . . . . . . 60  16. RECEIVE Job for Cumulative Service Tape . . . . . . . . . . 61  17. Job to Transfer Ownership of SYSMODs . . . . . . . . . . . . 63  18. Job to Delete PSF/MVS . . . . . . . . . . . . . . . . . . . 65  19. FMIDs for PSF/MVS . . . . . . . . . . . . . . . . . . . . . 65  20. APPLY CHECK Job . . . . . . . . . . . . . . . . . . . . . . 66  21. APPLY Job . . . . . . . . . . . . . . . . . . . . . . . . . 67  22. ACCEPT CHECK Job . . . . . . . . . . . . . . . . . . . . . . 69  23. ACCEPT Job . . . . . . . . . . . . . . . . . . . . . . . . . 69  24. APSIVP Job . . . . . . . . . . . . . . . . . . . . . . . . . 73  25. APSIVPDA Job . . . . . . . . . . . . . . . . . . . . . . . . 76  26. FMID HPRF220 SMPMCS . . . . . . . . . . . . . . . . . . . . 78  27. FMID JPRF223 SMPMCS . . . . . . . . . . . . . . . . . . . . 81  28. APSWPROA Job . . . . . . . . . . . . . . . . . . . . . . . . 85  29. APSWPROB Job . . . . . . . . . . . . . . . . . . . . . . . . 89  30. APSWPROC Job . . . . . . . . . . . . . . . . . . . . . . . . 92  31. APSWPROD Job . . . . . . . . . . . . . . . . . . . . . . . . 95  32. APSWPROM Job . . . . . . . . . . . . . . . . . . . . . . . . 99  33. APSWPROP Job . . . . . . . . . . . . . . . . . . . . . . . 102  34. APSWPROS Job . . . . . . . . . . . . . . . . . . . . . . . 105  35. APSWPROT Job . . . . . . . . . . . . . . . . . . . . . . . 108  36. New Functions Added to PSF/MVS Version 2.2.0 . . . . . . . 111  37. SMP/E Dialog Panel Prompts and Suggested User Responses . 119  38. Installation Checklist for PSF/MVS Version 2.2.0 . . . . . 120     Figures vi ¤   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.  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  International Business Machines Corporation  IBM Director of Licensing  500 Columbus Avenue  Thornwood, New York 10594  USA   TRADEMARKS  The following terms used in this document are trademarks of IBM  Corporation in the United States or other countries:  ACF/VTAM MO:DCA  Advanced Function Presentation MVS/DFP  Advanced Function Printing MVS/ESA  AFCCU MVS/SP  AFP OS/2  AIX OS/390  AS/400 Print Services Facility  Bar Code Object Content Architecture PrintManager  BCOCA Proprinter  BookManager PS/2  CBIPO PSF  CBPDO PSF/6000  DFSMS/MVS RACF  ESCON RETAIN  Hardware Configuration Definition S/390  IBM(R) System/370  IBMLink System/390  Intelligent Printer Data Stream VTAM  IPDS   (C) Copyright IBM Corp. 1983, 1996 vii ¤   The following term used in this document is a trademark of the XEROX  Corporation:  XEROX(R)                   Notices viii ¤   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 PSF/MVS Version 2.2.0. 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 5 identifies the basic and  optional program materials and documentation for PSF/MVS Version  2.2.0.  ù 3.0, "Program Support" on page 16 describes the IBM support  available for PSF/MVS Version 2.2.0.  ù 4.0, "Program and Service Level Information" on page 19 lists the  program level Authorized Program Analysis Reports (APARs) and  service level Program Temporary Fixes (PTFs) incorporated into  PSF/MVS Version 2.2.0.  ù 5.0, "Installation Requirements and Considerations" on page 23  identifies the resources and considerations for installing and  using PSF/MVS Version 2.2.0.  ù 6.0, "Installation Instructions" on page 47 provides detailed  installation instructions for PSF/MVS Version 2.2.0.  ù 7.0, "Installation Verification Procedure" on page 72 provides the  installation verification procedures for PSF/MVS Version 2.2.0.  ù Appendix A, "SMP/E Install Logic" on page 78 lists the SMPMCS and  JCLIN for PSF/MVS Version 2.2.0.  ù Appendix B, "Startup Procedures for PSF/MVS Version 2.2.0" on  page 84 lists the startup procedures APSWPROC, APSWPROS, APSWPROA,  APSWPROB, APSWPROD, APSWPROM, APSWPROP and APSWPROT.  ù Appendix C, "New Functions Added to PSF/MVS Version 2.2.0" on  page 111 identifies new functions that have been added to PSF/MVS  Version 2.2.0 since it first became available.  ù Appendix D, "SMP/E Dialog Panel Information" on page 118 describes  SMP/E dialog panel information.  ù Appendix E, "Checklist for PSF/MVS Version 2.2.0 Installation" on  page 120 contains a checklist that can be used to help install  PSF/MVS Version 2.2.0.   (C) Copyright IBM Corp. 1983, 1996 1 ¤   ù Appendix F, "PTF Cover Letter Data for Service Level SMC9618" on  page 122 contains information from PTF cover letters for selected  PTFs that are included in this service level of PSF/MVS Version  2.2.0.  Before installing PSF/MVS Version 2.2.0, read 3.2, "Preventive Service  Planning" on page 16. 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 PSF/MVS  Version 2.2.0 with an MVS Custom-Built Installation Process Offering  (CBIPO) (5751-CS1). Instead, use the CBIPO Related Installation  Materials (RIMs) provided with the CBIPO. The CBIPO RIMs will point  you to specific sections of the program directory as required.  If you are installing PSF/MVS Version 2.2.0 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 PSF/MVS Version 2.2.0 are included on the  CBPDO tape.   1.1 PRINT SERVICES FACILITY/MVS DESCRIPTION  PSF/MVS Version 2.2.0 provides device and resource-management support  for the following printers:  ù 3112 Page Printer Model 001  ù 3116 Page Printer Models 001, 002, 003  ù 3130 Advanced Function Printer Models 01S, 02S, 02D, 03S (2)  ù 3160 Advanced Function Printer Model 001 (2)  ù 3800 Printing Subsystem Model 3, Model 6, and Model 8  ù 3812 Page Printer Model 2  ù 3816 Page Printer Model 01S and Model 01D  ù 3820 Page Printer  ù 3825 Page Printer (1)  ù 3827 Page Printer (1)  ù 3828 Advanced Function MICR Printer (1)  ù 3829 Advanced Function Printer (1)  ù 3831 Page Printer Model 001 (available only in Japan)  ù 3835 Page Printer Model 001 (1)  ù 3835 Advanced Function Printer Model 002 (1)  ù 3900 Advanced Function Printer Model 001 (1)  ù 3900 Advanced Function Standard Duplex Printing System Models D01  and D02 (2)  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ  (1) These printers support basic N_UP printing with default placement  of the pages in the partitions.  (2) These printers support basic and enhanced N_UP printing with  default and explicit placement of the pages in the partitions.   Introduction 2 ¤   ù 3900 Advanced Function Wide Duplex Printing System Models DW1 and  DW2 (2)  ù 3900 Wide Advanced Function Printer Models 0W1 and OW3 (2)  ù 3912 Page Printer Model NS1  ù 3916 Page Printer Model NS1  ù 3930 Page Printer Model 02S and Model 02D  ù 3935 Advanced Function Printer Model 001 (2)  ù LaserPrinter 4028 Model AS1 and Model NS1  ù 4224 Printer Models 201, 202, 2C2, 2E2, 2E3  ù 4230 Printer Model 202, Model 211, and Model 513 (in 4224  emulation mode only)  ù 4234 Printer Model 07 and 011  ù 6400 Line Matrix Printer Models 004, 008, 012  ù 6408 Line Matrix Printer Model CTA  ù 6412 Line Matrix Printer Model CTA  PSF/MVS Version 2.2.0 indirectly supports non-IPDS printers through  the following programs:  ù The Distributed Print Function (DPF) component of PSF for OS/2  ù The PSF Direct Feature of PSF for AIX  ù The MVS Download feature for PSF/MVS  Non-IPDS printers include:  ù LaserPrinter 4019 Model E01 and Model 001  ù LaserPrinter 5E Model 4029-010  ù LaserPrinter 6 Model 4029-020  ù LaserPrinter 10 Model 4029-030  ù LaserPrinter 10L Model 4029-040  ù LaserPrinter 4039 Model 10D, Model 10R, Model 12L, and Model 12R   1.2 OVERVIEW OF PSF/MVS VERSION 2.2.0 FEATURES  The following features and functions are available with PSF/MVS  Version 2.2.0:  ù PSF/MVS Version 2.2.0 base product  ù PSF/MVS Version 2.2.0 resources  ù PSF/MVS Version 2.2.0 compatibility fonts  ù AFP Conversion and Indexing Facility (ACIF)  ù AFP Application Programming Interface (AFP API)  ù Page Printer Migration Programs (PPMP) Feature  ù MVS Download Feature  ù NetSpool Feature   Introduction 3 ¤   ù AFP Upload for AIX Feature   1.3 WHAT'S NEW - PACKAGING CHANGES  Some packaging changes have taken place since PSF/MVS Version 2.2.0  was first available in July 1994. If you have a previous release of  PSF/MVS, or you are reinstalling PSF/MVS Version 2.2.0 with this  service-updated level (Service Level SMC9618), you may wish to review  these changes.  ù ACIF and AFP API  The ACIF and AFP API functions continue to ship with the basic  material for PSF/MVS Version 2.2.0. The installation instructions  are now contained in a separate Program Directory which ships as  part of the basic material.  ù Font Material  Only the Compatibility Fonts are now shipped as part of PSF/MVS  Version 2.2.0. If you have other fonts (Core Interchange Fonts or  4028 Font Metrics) that were shipped with a previous release of  PSF/MVS, you may continue to use those fonts with PSF/MVS Version  2.2.0. These fonts and many others are now available in the AFP  Font Collection, 5648-113.  ù New Function  Many new functions have been added to PSF/MVS Version 2.2.0 since  it first became available. A summary of these functions can be  found in Appendix C, "New Functions Added to PSF/MVS Version  2.2.0" on page 111.          Introduction 4 ¤   2.0 PROGRAM MATERIALS    An IBM program is identified by a program number and a feature number.  The program number for PSF/MVS Version 2.2.0 is 5695-040.  The program announcement material describes the features supported by  PSF/MVS Version 2.2.0. Ask your IBM marketing representative for this  information if you have not already received a copy.  This program directory describes the installation of PSF/MVS Version  2.2.0 HPRF220 (base product) and JPRF223 (resources).  The following sections identify the basic and optional program  materials available with this program.   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 tape. The tape or  cartridge contains all the programs and data needed for installation.  It is installed using SMP/E. See 6.0, "Installation Instructions" on  page 47 for more information about how to install the program.   2.1.1 PSF/MVS VERSION 2.2.0 MACHINE-READABLE MATERIAL  Figure 1 describes the PSF/MVS Version 2.2.0 tape or cartridge.  Figure 2 on page 6 describes the file content of the PSF/MVS Version  2.2.0 tape or cartridge.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 1. Basic Material: PSF/MVS Version 2.2.0 Tape |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ ¿ ¿ |  | | FEATURE | PHYSICAL | EXTERNAL LABEL | |  | MEDIUM | NUMBER | VOLUME | IDENTIFICATION | VOLSER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | |  | 6250 tape | 5801 | 1 | PSF.BASE...2.2.0 | PRF220 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | |  | 3480 cart. | 5802 | 1 | PSF.BASE...2.2.0 | PRF220 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | |  | 4mm tape | 5337 | 1 | PSF.BASE...2.2.0 | PRF220 |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À À À     (C) Copyright IBM Corp. 1983, 1996 5 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 2. Program Tape: PSF/MVS Version 2.2.0 Tape File Content |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ ¿ ¿ ¿ ¿ |  | | | | REC| | BLK | NUMBER OF |  | VOLSER | FILE | NAME | FM | LRECL | SIZE | ELEMENTS |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | PRF220 | 1 | SMPMCS | FB | 80 | 6400 | 1 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 2 | IBM.HPRF220.F1 | FB | 80 | 8800 | 1 (JCLIN) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 3 | IBM.HPRF220.F2 | U | 0 | 6144 | 421 |  | | | | | | | (AAPSMOD0) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 4 | IBM.HPRF220.F3 | FB | 80 | 8800 | 6 |  | | | | | | | (AMACLIB) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 5 | IBM.HPRF220.F4 | FB | 80 | 8800 | 3 |  | | | | | | | (AGENLIB) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 6 | IBM.HPRF220.F5 | FB | 80 | 8800 | 56 |  | | | | | | | (ASAMPLIB) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 7 | IBM.HPRF220.F6 | FB | 80 | 8800 | 8 |  | | | | | | | (APROCLIB) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 8 | IBM.HPRF220.F7 | U | 0 | 6144 | 5 |  | | | | | | | (ANUCLEUS) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 9 | IBM.HPRF220.F8 | U | 0 | 6144 | 3 |  | | | | | | | (ALINKLIB) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 10 | IBM.HPRF220.F9 | U | 0 | 6144 | 1 |  | | | | | | | (AOSC5) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 11 | IBM.HPRF220.F10 | VBM| 8205 | 8209 | 13 |  | | | | | | | (AAPSDAT0) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 13 | IBM.JPRF223.F1 | VBM| 8205 | 8209 | 66 |  | | | | | | | (AFDEFLIB) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 14 | IBM.JPRF223.F2 | VBM| 8205 | 8209 | 81 |  | | | | | | | (APDEFLIB) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 15 | IBM.JPRF223.F3 | VBM| 8205 | 8209 | 1 |  | | | | | | | (AOVERLIB) |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | |  | | 16 | IBM.JPRF223.F4 | VBM| 8205 | 8209 | 4 |  | | | | | | | (APSEGLIB) |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À À À À À    Program Materials 6 ¤   2.1.2 ACIF AND AFP API MACHINE-READABLE MATERIAL  A separate tape labelled PSF.ACIF.API.2.2.0 is available with the  basic material for PSF/MVS Version 2.2.0. This tape contains the  IBM-supplied ACIF feature and AFP API feature.  Refer to ACIF and AFP API Program Directory, shipped with the basic  material for PSF/MVS Version 2.2.0, for installation information.   2.1.3 FONT MATERIAL  Separate font tapes labelled  PSF.COMPATS.MVS  PSF.FONT300.MVS  are available with the basic material for PSF/MVS Version 2.2.0.  These tapes contain IBM-supplied compatibility fonts for PSF/MVS  Version 2.2.0.  The tape labelled PSF.COMPATS.MVS contains compatibility fonts in the  240-pel bounded box and 240-pel unbounded box printer formats. These  fonts are identical to the fonts supplied with PSF/MVS Version 2.1.1.  All FMIDs are the same and font content is the same. You do not have  to install the PSF/MVS Version 2.2.0 fonts if the PSF/MVS Version  2.1.1 fonts were installed.  The tape labelled PSF.FONT300.MVS contains compatibility fonts in the  300-pel printer format. These fonts are used for printing on 300-pel  page printers such as IBM 3935 and IBM 3916 printers.  Refer to the separate font program directories, shipped with the basic  material for PSF/MVS Version 2.2.0, for additional installation  information about these font tapes.  NOTE: Font packaging has changed for PSF/MVS Version 2.2.0. Only the  Compatibility Fonts are now shipped as part of PSF/MVS Version 2.2.0.  If you have other fonts (Core Interchange Fonts or 4028 Font Metrics)  that were shipped with a previous release of PSF/MVS, you may continue  to use those fonts with PSF/MVS Version 2.2.0. These fonts and many  others are now available in the AFP Font Collection, 5648-113.   2.2 OPTIONAL MACHINE-READABLE MATERIAL  This section describes the optional machine-readable material  available with PSF/MVS Version 2.2.0.     Program Materials 7 ¤   2.2.1 PAGE PRINTER MIGRATION PROGRAMS MATERIAL  A separate optional tape for Page Printer Migration Programs (PPMP),  FMID HPRF224, is available with PSF/MVS Version 2.2.0.  PPMP is used to convert Xerox(R) Laser Printer System print files so  that they will print on AFP printers.  Refer to Page Printer Migration Programs Version 2.2.0 Program  Directory, shipped if you ordered the PPMP feature, for installation  information about the PPMP tape.   2.2.2 MVS DOWNLOAD PROGRAM MATERIAL  A separate optional tape for the MVS Download feature, FMID JPRF225,  is available with PSF/MVS Version 2.2.0.  MVS Download automatically transmits data from the JES spool to AIX  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 AIX system receives the data sets for  printing with PSF/6000 or for archiving using OnDemand for AIX. MVS  Download provides high-speed data transfer, JES scheduling, job  management, data integrity, and job accounting for distributed  production print management.  Refer to MVS Download Version 2.2.0 Program Directory, shipped if you  ordered the MVS Download feature, for installation information about  the MVS Download tape.   2.2.3 NETSPOOL PROGRAM MATERIAL  A separate optional tape for the Netspool feature, FMID HPRF226, is  available with PSF/MVS Version 2.2.0.  The Netspool feature of PSF/MVS places VTAM output on the JES spool.  You can then use either JES or PSF/MVS to print or distribute this  output. Netspool enables VTAM applications to take advantage of AFP  solutions without program changes. Netspool allows multiple VTAM  applications to share a single multi-function printer, and also allows  a single VTAM application to broadcast output with the same or  different output formats to multiple distributed printers.  Refer to Netspool Version 2.2.0 Program Directory, shipped if you  ordered the Netspool feature, for installation information about the  Netspool tape.    Program Materials 8 ¤   2.2.4 AFP UPLOAD FOR AIX PROGRAM MATERIAL  A separate optional tape for the AFP Upload for AIX feature, FMID  HPRF227, is available with PSF/MVS Version 2.2.0.  The AFP Upload for AIX feature of PSF/MVS allows you to submit a job  to PSF for AIX for printing on any printer supported by PSF/MVS  Version 2.2.0. AFP Upload for AIX receives the print data from PSF  for AIX and places it on the JES spool for printing by PSF/MVS. Jobs  submitted to PSF for AIX can contain any type of data stream that PSF  for AIX can transform to MO:DCAÄÄP.  Refer to AFP Upload for AIX Program Directory, shipped if you ordered  the AFP Upload for AIX feature, for installation information about the  AFP Upload for AIX tape.   2.3 PROGRAM PUBLICATIONS  The following sections identify the basic and optional publications  for PSF/MVS Version 2.2.0.   2.3.1 BASIC PROGRAM PUBLICATIONS  Figure 3 identifies the basic program publications for PSF/MVS Version  2.2.0. A copy of the Print Services Facility/MVS: Program Directory,  a copy of the ACIF and AFP API Program Directory, a copy of the font  program directories, and one copy of each of these publications is  included with the basic materials for PSF/MVS Version 2.2.0. For  additional copies, contact your IBM representative.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 3 (Page 1 of 3). Basic Program Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | PUBLICATION TITLE | ORDER/FORM |  | | NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Print Services Facility/MVS: Licensed Program | G544-3674 |  | Specifications | |  | | |  | ù This publication describes the warranted | |  | functional characteristics of PSF/MVS. It | |  | also states the specified operating | |  | environment for PSF/MVS Version 2.2.0. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Print Services Facility/MVS: Update Guide | G544-3984 |  | | |  | ù This publication is an interim publication to | |  | cover changes to PSF/MVS for TCP/IP-attached | |  | printer support. | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À   Program Materials 9 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 3 (Page 2 of 3). Basic Program Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | PUBLICATION TITLE | ORDER/FORM |  | | NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Print Services Facility/MVS: System Programming | S544-3672 |  | Guide | |  | | |  | ù This publication provides information about | |  | installing, customizing, and maintaining | |  | PSF/MVS. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Print Services Facility/MVS: Application | S544-3673 |  | Programming Guide | |  | | |  | ù This publication describes the commands | |  | needed to print on AFP printers. The | |  | IBM-supplied resources are also described. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Print Services Facility/MVS: Messages and Codes | S544-3675 |  | | |  | ù This publication provides messages, system | |  | completion codes, and abend reason codes for | |  | PSF/MVS. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Mixed Object Document Content Architecture | SC31-6802 |  | Reference | |  | | |  | ù This publication contains the architecture | |  | definition of the Mixed Object Document | |  | Content Architecture and describes the | |  | functions and elements that make up the | |  | MO:DCA architecture. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Advanced Function Presentation: Printer Summary | G544-3135 |  | | |  | ù This publication lists all AFP-supported | |  | printers, some of their characteristics, and | |  | licensed programs supporting them. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Advanced Function Presentation: Printer | G544-3290 |  | Information | |  | | |  | ù This publication contains printer-specific | |  | information and information about | |  | printer-resident fonts. It also provides | |  | conversion and migration information. | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À    Program Materials 10 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 3 (Page 3 of 3). Basic Program Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | PUBLICATION TITLE | ORDER/FORM |  | | NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP Fonts: Font Summary | G544-3810 |  | | |  | ù This publication summarizes font information | |  | for the IBM Expanded Core Fonts, IBM | |  | Compatibility Fonts, IBM 4028 Font Metrics, | |  | and other IBM font licensed programs. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP: Application Programming Interface | S544-3872 |  | Programming Guide and Reference | |  | | |  | ù This publication describes general | |  | information about Advanced Function | |  | Presentation and AFP API. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP: Application Programming Interface COBOL | S544-3873 |  | Language Reference | |  | | |  | ù This publication contains the COBOL language | |  | bindings and COBOL AFP API procedure call | |  | summary. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP: Application Programming Interface PL/I | S544-3874 |  | Language Reference | |  | | |  | ù This publication contains the PL/I language | |  | bindings and PL/I AFP API procedure call | |  | summary. | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP Conversion and Indexing Facility: User's | S544-5285 |  | Guide | |  | | |  | ù This publication describes how to use the AFP | |  | Conversion and Indexing Facility (ACIF). | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | IBM Page Printer Formatting Aid: User's Guide | S544-5284 |  | | |  | ù This publication describes how to use | |  | PPFA/370 to create and compile form | |  | definitions and page definitions for Advanced | |  | Function Printing or viewing. | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À  Figure 4 identifies the licensed program publications for PSF/MVS  Version 2.2.0. The first copy is available at no charge to licensees  of the base material for PSF/MVS Version 2.2.0. Additional copies can  be ordered for a fee using the feature number listed in Figure 4.   Program Materials 11 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 4. Basic Material: Licensed Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | PUBLICATION TITLE | FORM NUMBER | FEATURE NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Print Services Facility/MVS: | LH40-0205 | 8003 |  | Diagnosis Guide and Reference | | |  | | | |  | ù This publication provides | | |  | information for diagnosing | | |  | failures in PSF/MVS and | | |  | communicating those failures to | | |  | an IBM representative. It also | | |  | describes how to use PSF/MVS | | |  | diagnostic aids. | | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Advanced Function Printing: | LH40-0201 | 8004 |  | Diagnosis Guide | | |  | | | |  | ù This publication helps | | |  | determine if a print-job | | |  | failure is caused by PSF/MVS | | |  | logic errors, user errors, or | | |  | an error in an associated | | |  | licensed program. | | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À   2.3.2 OPTIONAL PROGRAM PUBLICATIONS  Figure 5 identifies the optional program publications for PSF/MVS  Version 2.2.0. Additional publications are available for a fee.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 5 (Page 1 of 2). Optional Program Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | PUBLICATION TITLE | ORDER/FORM |  | | NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP Fonts: Font Samples | S544-3792 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP Fonts: Introduction to Typography | G544-3122 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP Fonts: Technical Reference for IBM Expanded | S544-5228 |  | Core Fonts | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP Fonts: Technical Reference for Code Pages | S544-3802 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | ABOUT TYPE: IBM's Technical Reference for 4028 | S544-3709 |  | Font Metrics | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Licensed Program Specifications for IBM AFP Font | G544-5229 |  | Collection | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À   Program Materials 12 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 5 (Page 2 of 2). Optional Program Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | PUBLICATION TITLE | ORDER/FORM |  | | NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Licensed Program Specifications for Advanced | G544-3295 |  | Function Printing: Font Licensed Programs | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Licensed Program Specifications for Bar | G544-3141 |  | Code/Optical Character Recognition | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP Fonts: Type Transformer User's Guide | G544-3796 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Intelligent Printer Data Stream Reference | S544-3417 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | AFP Fonts: Data Stream and Object Architectures: | S544-3285 |  | Font Object Content Architecture (FOCA) Reference | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Mixed Object Document Content Architecture | SC31-6802 |  | Reference | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Presentation Text Object Content Architecture | SC31-6803 |  | Reference | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Graphics Object Content Architecture Reference | SC31-6804 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Image Object Content Architecture Reference | SC31-6805 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Print Services Facility: Security Guide | S544-3291 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Page Printer Migration: General Information | G544-3227 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Page Printer Migration: Programming Guide | S544-3228 |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À   2.3.3 PUBLICATIONS USEFUL DURING INSTALLATION  The publications listed in Figure 6 may be useful during the  installation of PSF/MVS Version 2.2.0. To order copies, contact your  IBM representative.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 6 (Page 1 of 3). Useful Program Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | PUBLICATION TITLE | ORDER/FORM |  | | NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | System Modification Program Extended User's Guide | SC28-1302 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | System Modification Program Extended Reference | SC28-1107 |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À   Program Materials 13 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 6 (Page 2 of 3). Useful Program Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | PUBLICATION TITLE | ORDER/FORM |  | | NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | System Modification Program Extended Messages | SC28-1108 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 JES2 Commands | GC23-0084 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 JES2 Initialization and Tuning | SC23-0083 |  | Reference | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA JES3: Commands | SC23-0074 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA JES3: Initialization and Tuning | SC23-0073 |  | Reference | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 System Messages, Volume 1 | GC28-1656 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 System Messages, Volume 2 | GC28-1657 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 System Messages, Volume 3 | GC28-1658 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 System Messages, Volume 4 | GC28-1659 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 System Messages, Volume 5 | GC28-1660 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/DFP V3 Utilities | SC26-4559 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 Service Aids | GC28-1669 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 System Management Facilities | GC28-1628 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 Initialization and Tuning Guide | GC28-1634 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 Initialization and Tuning Reference | GC28-1635 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 JCL User's Guide | GC28-1653 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 JCL Reference | GC28-1654 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA Configuration Program Guide and Reference | GC28-1817 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA Hardware Configuration Definition: User's | GC33-6457 |  | Guide | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS/ESA SP V4 Planning: B1 Security | GC28-1171 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Systems Network Architecture Technical Overview | GC30-3073 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Network Program Products Planning | GC30-3351 |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À   Program Materials 14 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 6 (Page 3 of 3). Useful Program Publications |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | PUBLICATION TITLE | ORDER/FORM |  | | NUMBER |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | VTAM Version 3.4.1 Network Implementation Guide | SC31-6434 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | VTAM Version 3.4.1 Resource Definition Reference | SC31-6438 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | VTAM Version 3.4 Customization | LY43-0056 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | VTAM Version 3.4.1 Operation | SC31-6435 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | VTAM Version 3.4.1 Programming | SC31-6436 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | Systems Network Architecture Formats | GA27-3136 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | IBM 3130, 3160 and 3935 Advanced Function | S544-3977 |  | Printers: Attachment Configuration Handbook | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | MVS Software Manufacturing Offerings General | GC23-0351 |  | Information | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | OS/390 MVS Product Management | GC28-1730 |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À   2.4 PROGRAM SOURCE MATERIALS  No program source materials, microfiche, or viewable program listings  are provided for PSF/MVS Version 2.2.0.          Program Materials 15 ¤   3.0 PROGRAM SUPPORT    This section describes the IBM support available for PSF/MVS Version  2.2.0.  Refer to ACIF and AFP API Program Directory for information about  program support for ACIF and AFP API.  Refer to the font program directories for information about program  support of fonts for PSF/MVS Version 2.2.0.  Refer to Page Printer Migration Programs Version 2.2.0 Program  Directory for information about program support for PPMP.  Refer to MVS Download Version 2.2.0 Program Directory for information  about program support for MVS Download.  Refer to Netspool Version 2.2.0 Program Directory for information  about program support for Netspool.  Refer to AFP Upload for AIX Program Directory for information about  program support for AFP Upload for AIX.   3.1 SERVICE INSTRUCTIONS  Contact your IBM marketing representative or operations specialist  systems engineer (OPSSE) for specific information about available  service instructions.   3.2 PREVENTIVE SERVICE PLANNING  Whether PSF/MVS Version 2.2.0 was obtained from IBM Software  Distribution independently or obtained in a CBPDO, the latest  Preventive Service Planning (PSP) information should be received  before installing the product. To obtain this information, check with  your IBM Support Center or use either S/390 SoftwareXcel or IBMLink  (ServiceLink). Specify the following upgrade and subset values:      (C) Copyright IBM Corp. 1983, 1996 16 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 7. PSP Upgrade and Subset ID |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | UPGRADE | SUBSET | DESCRIPTION |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | PSFMVS220 | HPRF220/9618 | PSF/MVS Base |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | PSFMVS220 | JPRF223/9618 | PSF/MVS Resources |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | PSFPRINTERS 3130 | Printer Hardware |  |  | | 3160 | |  | | 3827 | |  | | 3828 | |  | | 3829 | |  | | 3835 | |  | | 3916 | |  | | 3930 | |  | | 3935 | |  | | 64XX | |  | | 3900STD | |  | | 3900DUP/WID | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À  If PSF/MVS Version 2.2.0 was obtained as part of a CBPDO, HOLDDATA and  Preventive Service Planning (PSP) information may be available for  PSF/MVS Version 2.2.0 on the CBPDO tape.  NOTE: The PSP SUBSET name reflects the Function Module Identifier  (FMID) that was updated and the corresponding CBPDO weekly service  tape that was used to supply the integrated PTFS. (Example;  FMID/YYWW, where YY is the year and WW is the week of the CBPDO weekly  service tape.)  The CBPDO weekly Service tape is the Service Level Indicator for any  products updated by the Software Manufacturing Center (SMC) processes.  If you wish to determine the latest level of PUT maintenance installed  in this product, see 4.0, "Program and Service Level Information" on  page 19.   3.3 STATEMENT OF SUPPORT PROCEDURES  Report any difficulties you have using this program or program  directory to your IBM Support Center. In the U.S.A., if an APAR is  required, the Support Center will provide the address to which any  needed documentation can be sent.  Figure 8 identifies the component IDs (COMP IDs) for PSF/MVS Version  2.2.0.    Program Support 17 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 8. Component IDs |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ ¿ |  | FMID | COMP ID | COMPONENT NAME | RELEASE |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | |  | HPRF220 | 569504001 | PSF/MVS V220 | 220 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | |  | JPRF223 | 569504001 | PSF/MVS V220 | 223 |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À À                  Program Support 18 ¤   4.0 PROGRAM AND SERVICE LEVEL INFORMATION    This section identifies the program and service levels of PSF/MVS  Version 2.2.0. The program level refers to the APAR fixes  incorporated into the program. The service level refers to the PTFs  incorporated. Information about the cumulative service tape is also  provided.  This program is at Service Level SMC9618.  Refer to ACIF and AFP API Program Directory for program and service  level information for ACIF and AFP API.  Refer to the font program directories for program and service level  information of fonts for PSF/MVS Version 2.2.0.  Refer to Page Printer Migration Programs Version 2.2.0 Program  Directory for program and service level information for PPMP.  Refer to MVS Download Version 2.2.0 Program Directory for program and  service level information for MVS Download.  Refer to Netspool Version 2.2.0 Program Directory for program and  service level information for Netspool.  Refer to AFP Upload for AIX Program Directory for program and service  level information for AFP Upload for AIX.   4.1 PROGRAM LEVEL INFORMATION  The following APAR fixes against PSF/MVS Version 2.1.1 are  incorporated into PSF/MVS Version 2.2.0. They are listed by FMID.  See 4.2, "Service Level Information" on page 20 for Service Level  SMC9618 PTFs incorporated into PSF/MVS Version 2.2.0.  FMID HPRF102  PSF/MVS Version 2.2.0 has incorporated all service equivalent to PUT  tape number 9404.   FMID JPRF113  OY66888    (C) Copyright IBM Corp. 1983, 1996 19 ¤   4.2 SERVICE LEVEL INFORMATION  The following PTFs contain the APAR fixes against PSF/MVS Version  2.1.1. They are listed by FMID and are incorporated into PSF/MVS  Version 2.2.0.  FMID HPRF102  PSF/MVS Version 2.2.0 has incorporated all service equivalent to PUT  tape number 9404.   FMID JPRF113  UW03721  The following PTFs containing APAR fixes against PSF/MVS Version 2.2.0  have been integrated into this Service Level SMC9618.  NOTE: COR-CLOSED PTFs are available for 'Corrective Service' and will  be placed on the next available Program Update Tape (PUT). The  following sub-categories for COR-CLOSED PTFs have been provided by the  Software Manufacturing Center (SMC), Kingston:  SMCREC COR-CLOSED PTFs that have been researched and recommended for  installation by the Software Manufacturing Center (SMC) in  Kingston.  SMCCOR COR-CLOSED PTFs that have no special recommendations for  installation.          Program and Service Level Information 20 ¤   FMID HPRF220  UW08938-PUT9407 UW09094-PUT9407 UW09430-PUT9408  UW09686-PUT9408 UW09797-PUT9408 UW09923-PUT9408  UW10030-PUT9408 UW10065-PUT9409 UW10089-PUT9408  UW10181-PUT9408 UW10192-PUT9408 UW10401-PUT9408  UW10549-PUT9409 UW10698-PUT9409 UW10766-PUT9409  UW10805-PUT9409 UW10909-PUT9409 UW10911-PUT9409  UW11022-PUT9409 UW11131-PUT9409 UW11285-PUT9409  UW11415-PUT9410 UW11470-PUT9409 UW11603-PUT9410  UW11720-PUT9410 UW11817-PUT9410 UW11886-PUT9410  UW11887-PUT9410 UW12180-PUT9410 UW12330-PUT9410  UW12331-PUT9410 UW12478-PUT9411 UW12621-PUT9411  UW12675-PUT9411 UW12729-PUT9411 UW12732-PUT9411  UW12785-PUT9411 UW12897-PUT9412 UW13010-PUT9411  UW13329-PUT9412 UW13460-PUT9412 UW13461-PUT9412  UW13689-PUT9412 UW13806-PUT9412 UW13973-PUT9412  UW14101-PUT9501 UW14135-PUT9501 UW14560-PUT9503  UW14572-PUT9501 UW14806-PUT9502 UW14814-PUT9502  UW14833-PUT9502 UW14857-PUT9502 UW15052-PUT9502  UW15054-PUT9502 UW15117-PUT9502 UW15272-PUT9502  UW15328-PUT9502 UW15401-PUT9503 UW15446-PUT9503  UW15504-PUT9502 UW15550-PUT9503 UW15755-PUT9503  UW15760-PUT9503 UW16061-PUT9503 UW16063-PUT9503  UW16360-PUT9503 UW16420-PUT9503 UW16449-PUT9504  UW16483-PUT9504 UW16499-PUT9504 UW16502-PUT9504  UW16556-PUT9504 UW17075-PUT9504 UW17259-PUT9504  UW17306-PUT9505 UW17402-PUT9505 UW17679-PUT9505  UW17799-PUT9505 UW17802-PUT9505 UW17942-PUT9505  UW18068-PUT9505 UW18070-PUT9505 UW18071-PUT9505  UW18072-PUT9505 UW18208-PUT9505 UW18226-PUT9506  UW18264-PUT9506 UW18313 UW18588-PUT9506  UW18648-PUT9506 UW18905-PUT9506 UW19044-PUT9507  UW19121-PUT9507 UW19134-PUT9507 UW19202-PUT9507  UW19390-PUT9507 UW19428-PUT9507 UW19599-PUT9507  UW19696-PUT9507 UW19697-PUT9507 UW19699-PUT9507  UW19866-PUT9508 UW20001-PUT9508 UW20021-PUT9508  UW20040-PUT9508 UW20159-PUT9508 UW20201-PUT9508  UW20250-PUT9508 UW20252-PUT9508 UW20318-PUT9508  UW20567-PUT9508 UW20941-PUT9509 UW21042-PUT9509  UW21095-PUT9509 UW21121 UW21345-PUT9509  UW21369-PUT9509 UW21459-PUT9509 UW21461-PUT9509  UW21466-PUT9509 UW22030-PUT9510 UW22331-PUT9510  UW22554-PUT9510 UW22555-PUT9510 UW22557-PUT9510  UW22696-PUT9511 UW23081-PUT9511 UW23083-PUT9511  UW23275-PUT9511 UW23722-PUT9512 UW23840-PUT9512  UW23864-PUT9512 UW24162 UW24201-PUT9512     Program and Service Level Information 21 ¤   UW24258-PUT9512 UW24273-PUT9512 UW24303  UW24430-PUT9512 UW24446-PUT9512 UW24450-PUT9512  UW24497-PUT9512 UW24604-PUT9512 UW24616-PUT9601  UW24677-PUT9601 UW24725-PUT9601 UW24747-PUT9601  UW24899-PUT9601 UW24971-PUT9601 UW25033-PUT9601  UW25143-PUT9601 UW25289-PUT9601 UW25414-PUT9602  UW26050-PUT9602 UW26051-PUT9602 UW26166-PUT9602  UW26263-PUT9602 UW26483-PUT9603 UW26527-PUT9603  UW26603-PUT9603 UW26752-PUT9603 UW26952-PUT9603  UW26975-PUT9603 UW27158-SMCREC UW27333-SMCCOR  UW27810-SMCCOR UW27811-SMCREC UW27813-SMCCOR  UW27864-SMCCOR UW27934-SMCREC UW28082-SMCCOR  UW28279-SMCCOR   FMID JPRF223  UW14253-PUT9501 UW20320-PUT9508   4.3 CUMULATIVE SERVICE TAPE  A cumulative service tape, containing PTFs not incorporated into this  release, might be included with this program. If this product was  received as part of a CBPDO, a cumulative service tape will not be  included. Service is included on the CBPDO tape.            Program and Service Level Information 22 ¤   5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS    The following sections identify the system requirements for installing  and activating PSF/MVS Version 2.2.0. In most cases, you should not  install PSF/MVS Version 2.2.0 on a running system. You should make a  copy of your running system and install PSF/MVS Version 2.2.0 on the  copy (target system). The following terminology is used to describe  the two systems used during installation:  1. The system used to install the program (driving system)  2. The system on which the program is installed (target system).  Refer to ACIF and AFP API Program Directory for installation  requirements for ACIF and AFP API.  Refer to the font program directories for the installation of fonts  for PSF/MVS Version 2.2.0.  Refer to Page Printer Migration Programs Version 2.2.0 Program  Directory for installation requirements for PPMP.  Refer to MVS Download Version 2.2.0 Program Directory for installation  requirements for MVS Download.  Refer to Netspool Version 2.2.0 Program Directory for installation  requirements for Netspool.  Refer to AFP Upload for AIX Program Directory for installation  requirements for AFP Upload for AIX.   5.1 DRIVING SYSTEM REQUIREMENTS  This section describes the environment of the driving system required  to install PSF/MVS Version 2.2.0.   5.1.1 PROGRAMMING REQUIREMENTS  PSF/MVS Version 2.2.0 operates on IBM processors capable of supporting  MVS/ESA Version 3 Release 1.3, or later releases and modification  levels.  SMP/E Version 1 Release 8.0 (5668-949) or above is required to install  PSF/MVS Version 2.2.0.    (C) Copyright IBM Corp. 1983, 1996 23 ¤   5.1.2 DASD STORAGE REQUIREMENTS  PSF/MVS Version 2.2.0 uses any storage device that is supported by the  environment in which it is operating. See 5.2.4, "DASD Storage  Requirements" on page 32 for additional information about the amount  of storage required for PSF/MVS Version 2.2.0.   5.2 TARGET SYSTEM REQUIREMENTS  This section describes the environment of the target system required  to install and use PSF/MVS Version 2.2.0.   5.2.1 OPERATING SYSTEM AND PROGRAMMING REQUIREMENTS  Before installing PSF/MVS Version 2.2.0, the target operating system  must be at, or above, the following levels:  ù MVS Operating System:  One of the following versions of MVS is required, with any level  of JES2 or JES3 that is supported in that environment:  Ä MVS/SP-JES2 Version 3 Release 1.3 (5685-001) or MVS/SP-JES3  Version 3 Release 1.3 (5685-002)  Ä MVS/ESA SP-JES2 Version 4 Release 2 (5695-047) or MVS/ESA  SP-JES3 Version 4 Release 2 (5695-048)  Ä MVS/ESA SP-JES2 Version 5 Release 1 (5655-068) or MVS/ESA  SP-JES3 Version 5 Release 1 (5655-069)  Ä OS/390 Version 1 (5645-001)  ù MVS/ESA Data Facility Product (DFP) Version 3 Release 1.1  (5665-XA3) or DFSMS/MVS Version 1 Release 1 (5695-DF1)  ù SMP/E Version 1 Release 8.0 (5668-949) to install PSF/MVS Version  2.2.0  Both ACF/VTAM Version 3.4 (5685-085) or later and ACF/NCP Version  4.3.1 (5668-854) or later are required for the following:  ù Printing on SNA-attached printers  ù Printing on OS/2 or AIX printers, using DPF or PSF Direct     Installation Requirements and Considerations 24 ¤   5.2.2 MACHINE REQUIREMENTS  PSF/MVS Version 2.2.0 operates on the IBM processors capable of  supporting MVS/ESA Version 3 Release 1.3 or subsequent release and  modification levels unless otherwise identified.  Not all printers support all functions provided by PSF/MVS Version  2.2.0. Refer to the manuals in 5.2.2.1, "General Attachment  Information and Notes" on page 28 the end of this section for  information concerning supported functions.  Some printers require special levels of microcode to support certain  functions. Contact your IBM Hardware Customer Engineer to determine  if your printer requires a microcode update.  The following MINIMUM level of microcode requirements apply for the  indicated hardware:  ù IBM 3130  Ä Models 01S, 02S, 02D, and 03S - No special microcode required  Ä APAR OW14128 needs to be applied to PSF/MVS V2.2.0 for  support. (PTF integrated at Service Level SMC9618)  ù IBM 3160  Ä No special microcode required  Ä APAR OW13387 needs to be applied to PSF/MVS V2.2.0 for  support. (PTF integrated at Service Level SMC9618)  ù IBM 3800  Ä IBM 3800 Models 3 & 8 without Storage Expansion Feature (SEF)  require engineering change (EC) 847612 with patches P401 thru  P420  Ä IBM 3800 Models 3 and 8 with SEF require (EC) C05192 and  patches P501 thru P525  Ä IBM 3800 Model 6 without SEF requires (EC) 847661 and patches  P701 thru P706  Ä IBM 3800 Model 6 with SEF requires (EC) C05193 and patches  P801 thru P803.  ù IBM 3812  Ä IBM 3812 Model 2 requires 3270 IDS microcode Version 2.4.0 (or  above).  ù IBM 3816   Installation Requirements and Considerations 25 ¤   Ä IBM 3816 Models 01S, 01D require 3270 IDS microcode Version  3.11 (or above).  ù IBM 3820  Ä IBM 3820 requires microcode Patch P50B05 P/N 1693492 to print  with the Core Interchange and Proprinter Emulation fonts.  ù IBM 3825  Ä To support basic N_UP printing, install microcode Version 6.B  (or above).  ù IBM 3827  Ä Requires microcode Version 10.0 (or above)  Ä To support basic N_UP printing, install microcode Version 12.Q  (or above).  ù IBM 3828  Ä To support basic N_UP printing, install microcode Version 4.E  (or above).  ù IBM 3829  Ä To support basic N_UP printing, install microcode Version 1.C  (or above).  ù IBM 3831  Ä No special microcode required.  ù IBM 3835  Ä Model 001 - To support basic N_UP printing, install microcode  Version 23 (or above)  Ä Model 002 - To support basic N_UP printing, install microcode  Version 12.1 (or above).  ù IBM 3900 (CCU)  Ä Model 001 - To support basic N_UP printing, install microcode  Version 6.E.7 (or above).  ù IBM 3900 (AFCCU)  Ä ALL AFCCU MODELS - To use the Enhanced N_UP capability,  install microcode Version 5.0 (or above).    Installation Requirements and Considerations 26 ¤   Ä APAR OW04452 needs to be applied to PSF/MVS Version 2.2.0 for  ESCON attachment support. (PTF integrated at Service Level  SMC9618)  ù IBM 3912  Ä Model NS1 - No special microcode required.  ù IBM 3916  Ä Model NS1 - No special microcode required.  ù IBM 3930  Ä Models 02S and 02D - No special microcode required.  ù IBM 3935  Ä Model 001 - To use the Enhanced N_UP capability, install  microcode Version 3.0.2 (or above).  ù IBM 4019  Ä Models E01 and 001 are supported by PSF/MVS Version 2.2.0 only  through the Distributed Print Function (DPF) provided with the  PSF/2 licensed program.  ù IBM 4028  Ä Model NS1 and AS1 - No special microcode required  ù IBM 4029  Ä All models are supported by PSF/MVS Version 2.2.0 only through  the Distributed Print Function (DPF) provided with the PSF/2  licensed program.  ù IBM 4039  Ä Models 10D, 10R, 12L and 12R are supported by PSF/MVS Version  2.2.0 only through the Distributed Print Function (DPF)  provided with the PSF/2 licensed program.  ù IBM 4224  Ä Models 201, 202, 2C2, 2E2, 2E3 with serial number AA001 or  higher.  ù IBM 4230  Ä Models 202, 2T1 are supported in 4224 emulation mode only.  Ä Model 5I3 is supported in 4230 mode.   Installation Requirements and Considerations 27 ¤   ù IBM 4234  Ä Models 07 and 011 with serial number AA030 or above.  ù IBM 6400  Ä Model 004 - Supported in 4234 emulation mode only.  Ä APAR OW04104 needs to be applied to PSF/MVS Version 2.2.0 for  support. (PTF integrated at Service Level SMC9618)  ù IBM 6408  Ä Model CTA - Supported in 4234 emulation mode only.  Ä APAR OW04104 needs to be applied to PSF/MVS Version 2.2.0 for  support. (PTF integrated at Service Level SMC9618)  ù IBM 6412  Ä Model CTA - Supported in 4234 emulation mode only.  Ä APAR OW04104 needs to be applied to PSF/MVS Version 2.2.0 for  support. (PTF integrated at Service Level SMC9618)   5.2.2.1 GENERAL ATTACHMENT INFORMATION AND NOTES  Refer to Advanced Function Presentation: Printer Information for  detailed information regarding each printer type.  Refer to Print Services Facility/MVS: System Programming Guide for  information on attaching any of the printers supported by PSF/MVS  Version 2.2.0.  Refer to IBM 3130, 3160, and 3935 Advanced Function Printers:  Attachment Configuration Handbook for 3130, 3160, and 3935 attachment  information.  For PSF/MVS VTAM SNA attached printers, see the specific Printer  Announcement Letter for appropriate 3174 and 3274 attachment  information and for levels of microcode required for the controller.  See 3.2, "Preventive Service Planning" on page 16 for Preventive  Service Planning (PSP) information on specific device types.   5.2.3 PSF/MVS VERSION 2.2.0 REQUIREMENTS FOR SPECIAL FUNCTIONS  Program version minimum requirements are listed below for special  functions of PSF/MVS Version 2.2.0. Your system must be at or above  the stated levels.   Installation Requirements and Considerations 28 ¤   For private resource libraries (User libraries) support:  ù MVS/SP Version 3 Release 1.3 with APAR OY30620 with  Ä MVS/SP - JES2 Version 3 Release 1.3 (5685-001), or  Ä MVS/SP - JES3 Version 3 Release 1.3 (5685-002)  Ä TSO/E Version 2 Release 4.0 (5685-025)  Ä For RACF protection for User libraries, use RACF Version 1  Release 9.0 (5740-XXH).   For PSF abend and dump enhancements:  ù MVS/SP Version 3 Release 1.3 with  Ä MVS/SP - JES2 Version 3 Release 1.3 (5685-001) with APAR  OY31209  Ä MVS/SP - JES3 Version 3 Release 1.3 (5685-002) with APAR  OY30952   For printer intervention support in the System Display and Search  Facility:  ù MVS/SP Version 3 Release 1.3 with APAR OY31210 with  Ä MVS/SP - JES2 Version 3 Release 1.3 (5685-001) and  Ä SDSF Version 1 Release 3.1 (5665-488).   To route print-completion messages to the print-job submitter, to  relieve storage constraints or to achieve Dynamic Reconfiguration  Management (DRM):  ù MVS/ESA SP Version 4 Release 2.0 with  Ä MVS/ESA - JES2 Version 4 Release 2.0 (5695-047), or  Ä MVS/ESA - JES3 Version 4 Release 2.1 (5695-048).   Dynamic Reconfiguration Management support is provided for  channel-attached printers only.     Installation Requirements and Considerations 29 ¤   For Avoid Processer Power on Resets (POR's):  ù MVS/ESA Version 4 Release 2.0 with  Ä MVS/ESA - JES3 Version 4 Release 2.1 (5695-048)   For print security labelling:  ù MVS/SP Version 3 Release 1.3 with  Ä MVS/SP - JES2 Version 3 Release 1.3 (5685-001) or  Ä MVS/SP - JES3 Version 3 Release 1.3 (5685-002)  ù Data Facility Product (MVS/DFP) Version 3 Release 1.1 (5665-XA3)  ù RACF Version 1 Release 9.0 (5740-XXH) or above.   To use the distribution parameters on the separator pages:  ù MVS/ESA Version 4 Release 2.0 with  Ä MVS/ESA - JES2 Version 4 Release 2.0 (5695-047) or  Ä MVS/ESA - JES3 Version 4 Release 2.1 (5695-048).   For TCP/IP attached printer support:  ù MVS/ESA Version 4 Release 2.0 with APAR OW12236 with  Ä MVS/ESA - JES2 Version 3 Release 1.3 (5685-001) or  Ä MVS/ESA - JES3 Version 3 Release 1.2 (5685-002).  Ä TCP/IP Version 3 Release 1.0 (5665-HAL)   For Microfilm device support:  ù MVS/ESA Version 4 Release 2.0 with APAR OW12236 with  Ä MVS/ESA - JES2 Version 3 Release 1.3 (5685-001) or  Ä MVS/ESA - JES3 Version 3 Release 1.2 (5685-002).     Installation Requirements and Considerations 30 ¤   For PSF/MVS blank compression support:  ù MVS/ESA Version 4 Release 2.0 with APAR OW04349 with  Ä MVS/ESA - JES2 Version 3 Release 1.3 (5685-001) or  Ä MVS/ESA - JES3 Version 3 Release 1.2 (5685-002).   For printer sharing support:  ù MVS/ESA Version 4 Release 3.0 with APAR OW16442 with  Ä MVS/ESA - JES2 Version 3 Release 1.3 (5685-001) or  Ä MVS/ESA - JES3 Version 3 Release 1.2 (5685-002).               Installation Requirements and Considerations 31 ¤   5.2.4 DASD STORAGE REQUIREMENTS  The default SMP/E space parameters for DSSPACE, PEMAX, SMPWRK data  sets and SMP/E data sets are adequate to install PSF/MVS Version  2.2.0.   5.2.5 TARGET AND DISTRIBUTION LIBRARY STORAGE REQUIREMENTS  Abbreviations describing the data set type are listed in Figure 9.  These abbreviations are used in the figures in this section.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 9. Abbreviations used for the data set type |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ |  | ABBREVIATION | DATA SET TYPE |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | NU | New data set used by only the FMIDs listed. In |  | | order to determine the correct storage needed for |  | | this data set, only the storage size given in the |  | | one table needs to be used. No other tables (or |  | | program directories) need to be referenced for the |  | | data set size. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | NM | New 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 the |  | | one table needs to be added to other tables |  | | (perhaps in other program directories). |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | EU | Existing data set used by only the FMIDs listed. |  | | In order to determine the correct storage needed |  | | for this data set, only the storage size given in |  | | the one table needs to be used. No other tables |  | | (or program directories) need to be referenced for |  | | the data set size. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | |  | EM | Existing 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 |  | | the one table needs to be added to other tables |  | | (perhaps in other program directories). |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À  The following figures list the target and distribution library data  sets and their attributes required to install PSF/MVS Version 2.2.0.  New target and distribution library data sets must be allocated as  indicated in the tables in this section. See 6.1.2, "Allocate Target  and Distribution Library Data Sets" on page 50 for JCL that allocates  the new data sets.  In all the figures in this section, the following applies:   Installation Requirements and Considerations 32 ¤   ù The DASD space requirements shown represent the actual storage  required by the listed PSF/MVS Version 2.2.0 FMIDs after the  program is installed and the data sets are compressed, plus  approximately 15%. The additional 15% allows for concurrent  service installation. When allocating these data sets, you can  specify additional storage and directory blocks to allow for  future maintenance.  ù The storage requirements for existing target and distribution  library data sets must be added to the storage required by other  programs having data in the same library data set. An estimate of  required storage is the data set's current allocation plus the  storage required by PSF/MVS Version 2.2.0.  ù Data sets may be reblocked to a larger size.  If PSF/MVS Version 2.2.0 will be installed into unique libraries, see  consideration G on page 45 for information on allocating and using  unique libraries.   5.2.5.1 TARGET LIBRARY STORAGE REQUIREMENTS  Figure 10 lists the target library data sets for PSF/MVS Version  2.2.0.            Installation Requirements and Considerations 33 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 10. Storage Requirements for PSF/MVS Version 2.2.0 Target |  | Libraries |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ ¿ ¿ ¿ ¿ ¿ |  | | | D | R | L | | | |  | | T | S | E | R | | | NO. |  | DATA SET NAME | Y | O | C | E | | NO. | OF |  | OR | P | R | F | C | BLK | OF | DIR |  | LIBRARY NAME | E | G | M | L | SIZE | BLKS | BLKS |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.APSDAT00 | NU/EU | PO | VBM | 8205 | 8209 | 36 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.LINKLIB | EM | PO | U | 0 | 6144 | 400 | 7 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.MACLIB | EM | PO | FB | 80 | 6160 | 40 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.NUCLEUS | EM | PO | U | 0 | 6144 | 16 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.PROCLIB | EM | PO | FB | 80 | 6160 | 24 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.SAMPLIB | EM | PO | FB | 80 | 6160 | 456 | 5 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.FDEFLIB | NM/EM | PO | VBM | 8205 | 8209 | 24 | 6 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.PDEFLIB | NM/EM | PO | VBM | 8205 | 8209 | 66 | 7 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.OVERLIB | NM/EM | PO | VBM | 8205 | 8209 | 12 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.PSEGLIB | NM/EM | PO | VBM | 8205 | 8209 | 18 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | À À À À À À À |  | NOTE: |  | |  | Data set SYS1.APSDAT00 contains information used by the font |  | conversion utility APSRCF30. Refer to the appendix entitled |  | "Font Conversion Program, 240-pel to 300-pel" in Print Services |  | Facility/MVS: System Programming Guide for information about the |  | font conversion utility. If PSF/MVS is being installed for the |  | first time, see 6.1.2, "Allocate Target and Distribution Library |  | Data Sets" on page 50 for JCL that allocates this data set and |  | the data sets for the resources. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ   5.2.5.2 DISTRIBUTION LIBRARY STORAGE REQUIREMENTS  Figure 11 lists the distribution library data sets for PSF/MVS Version  2.2.0.     Installation Requirements and Considerations 34 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 11. Storage Requirements for PSF/MVS Version 2.2.0 |  | Distribution Libraries |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ ¿ ¿ ¿ ¿ ¿ |  | | | D | R | L | | | |  | | T | S | E | R | | | NO. |  | DATA SET NAME | Y | O | C | E | | NO. | OF |  | OR | P | R | F | C | BLK | OF | DIR |  | LIBRARY NAME | E | G | M | L | SIZE | BLKS | BLKS |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.AAPSDAT0 | NU/EU | PO | VBM | 8205 | 8209 | 42 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.AAPSMOD0 | NU/EU | PO | U | 0 | 6144 | 712 | 81 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.AGENLIB | EM | PO | FB | 80 | 6160 | 40 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.ALINKLIB | EM | PO | U | 0 | 6144 | 16 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.AMACLIB | EM | PO | FB | 80 | 6160 | 40 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.ANUCLEUS | EM | PO | U | 0 | 6144 | 16 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.AOSC5 | EM | PO | U | 0 | 6144 | 16 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.APROCLIB | EM | PO | FB | 80 | 6160 | 24 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.ASAMPLIB | EM | PO | FB | 80 | 6160 | 456 | 5 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.AFDEFLIB | NM/EM | PO | VBM | 8205 | 8209 | 24 | 6 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.APDEFLIB | NM/EM | PO | VBM | 8205 | 8209 | 66 | 7 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.AOVERLIB | NM/EM | PO | VBM | 8205 | 8209 | 12 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | | | | | | |  | SYS1.APSEGLIB | NM/EM | PO | VBM | 8205 | 8209 | 18 | 2 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | À À À À À À À |  | NOTE: See 6.1.2, "Allocate Target and Distribution Library Data |  | Sets" on page 50 for JCL that allocates the data set |  | SYS1.AAPSDAT0, and the resources. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ   5.3 PSF/MVS VERSION 2.2.0 INSTALLATION CONSIDERATIONS  Several installation options are available for PSF/MVS Version 2.2.0.  For each installation option, there are considerations that should be  noted before installing PSF/MVS Version 2.2.0.  This section contains:  ù Packaging changes between PSF/MVS Version 2.1.0, PSF/MVS Version  2.1.1, and PSF/MVS Version 2.2.0  ù Decision chart to determine the installation option to use for  PSF/MVS Version 2.2.0   Installation Requirements and Considerations 35 ¤   ù PSF/MVS Version 2.2.0 installation option description  ù Considerations that should be noted when installing PSF/MVS  Version 2.2.0, depending upon the installation option that was  chosen  ù Special considerations that should be noted when installing  PSF/MVS Version 2.2.0.   5.3.1 PACKAGING CHANGES BETWEEN PSF/MVS VERSION 2.1.0, PSF/MVS  VERSION 2.1.1, AND PSF/MVS VERSION 2.2.0  Packaging changes were made between PSF/MVS Version 2.1.0, PSF/MVS  Version 2.1.1, and PSF/MVS Version 2.2.0. If PSF/MVS Version 2.1.0,  or PSF/MVS Version 2.1.1 is already installed, it will affect how  PSF/MVS Version 2.2.0 is installed.  The PSF/MVS Version 2.1.1 base tape, including the base product (FMID  HPRF102) and resources (FMID JPRF113), is a service update of PSF/MVS  Version 2.1.0. PSF/MVS Version 2.1.1 base product and resources have  the same FMIDs as the PSF/MVS Version 2.1.0 base product and  resources.  PSF/MVS Version 2.2.0 base product tape, including the base product  and resources, have new FMIDs; HPRF220 for the base product, and  JPRF223 for the resources.   5.3.2 DETERMINE THE PSF/MVS VERSION 2.2.0 INSTALLATION OPTION  Use the following decision chart to determine the installation option  to use when installing PSF/MVS Version 2.2.0. The installation option  number corresponds to the option identified in 5.3.3, "Installation  Options for PSF/MVS Version 2.2.0" on page 40.          Installation Requirements and Considerations 36 ¤   5.3.2.1 DETERMINE INSTALLATION OPTION NUMBER FOR PSF/MVS VERSION  2.2.0  ÚÄÄÄ¿  |001|  ÀÄÄÄÙ  DO YOU WANT TO INSTALL PSF/MVS VERSION 2.2.0?  YES NO  | |  | ÚÄÄÄ¿  À  | |002|  | ÀÄÄÄÙ  | Choose installation option 5 to delete PSF/MVS Version 2.2.0  | only. See the description on page 43.  |  ÚÄÄÄ¿  À  |003|  ÀÄÄÄÙ  IS THIS THE FIRST TIME THAT PSF/MVS WILL BE INSTALLED ON THIS  OPERATING SYSTEM?  YES NO  | |  | ÚÄÄÄ¿  À  | |004|  | ÀÄÄÄÙ  | CAN YOU INSTALL PSF/MVS VERSION 2.2.0 ON ANOTHER MVS OPERATING  | SYSTEM THAT DOES NOT HAVE PSF/MVS RUNNING OR WHERE PSF/MVS CAN BE  | DELETED?  | YES NO  | | |  | | ÚÄÄÄ¿  À  | | |005|  | | ÀÄÄÄÙ  | | Continue at Step 008 on page 38.  | |  | ÚÄÄÄ¿  À  | |006|  | ÀÄÄÄÙ  | Continue at Step 013 on page 38.  | ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ  |  ÚÄÄÄ¿  À  |007|  ÀÄÄÄÙ  Choose installation option 1 to install PSF/MVS Version 2.2.0 only.  See the description on page 40.  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ     Installation Requirements and Considerations 37 ¤   ÚÄÄÄ¿  |008|  ÀÄÄÄÙ  DO YOU WANT TO DELETE THE PREVIOUS RELEASE OF PSF/MVS?  YES NO  | |  | ÚÄÄÄ¿  À  | |009|  | ÀÄÄÄÙ  | DO YOU WANT TO MAINTAIN SERVICE FOR THE PREVIOUS RELEASE OF  | PSF/MVS?  | YES NO  | | |  | | ÚÄÄÄ¿  À  | | |010|  | | ÀÄÄÄÙ  | | Choose installation option 4 to install PSF/MVS Version  | | 2.2.0 and retain the previous release of PSF/MVS. See the  | | description on page 42.  | |  | ÚÄÄÄ¿  À  | |011|  | ÀÄÄÄÙ  | Choose installation option 3 to install PSF/MVS Version 2.2.0 and  | maintain service for the previous release of PSF/MVS. See the  | description on page 41.  | ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ  |  ÚÄÄÄ¿  À  |012|  ÀÄÄÄÙ  Choose installation option 2 to install PSF/MVS Version 2.2.0 and  delete the previous release of PSF/MVS. See the description on  page 40.  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ  ÚÄÄÄ¿  |013|  ÀÄÄÄÙ  Ä PSF/MVS Version 2.2.0 can be installed on another operating system.  IS A PREVIOUS PSF/MVS RELEASE RUNNING ON THE OPERATING SYSTEM?  YES NO  | |  | ÚÄÄÄ¿  À  | |014|  | ÀÄÄÄÙ  | Choose installation option 1 to install PSF/MVS Version 2.2.0  | only. See the description on page 40.  |  ÚÄÄÄ¿  À  |015|  ÀÄÄÄÙ  (Step 015 continues)   Installation Requirements and Considerations 38 ¤   015 (continued)  Choose installation option 2 to install PSF/MVS Version 2.2.0 and  delete the previous release of PSF/MVS. See the description on  page 40.  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ                   Installation Requirements and Considerations 39 ¤   5.3.3 INSTALLATION OPTIONS FOR PSF/MVS VERSION 2.2.0  This section describes the different installation options that are  possible when PSF/MVS Version 2.2.0 is installed. Only one  installation option can be used. If you are unsure which installation  option to use, see the decision chart in 5.3.2, "Determine the PSF/MVS  Version 2.2.0 Installation Option" on page 36. This chart helps  determine which installation option to choose. Once you have  completed reading the section that applies to the installation option  that you have chosen, you should proceed to 6.0, "Installation  Instructions" on page 47.  1. YOU WANT TO INSTALL PSF/MVS VERSION 2.2.0 ONLY.  With this option, PSF/MVS has never been installed on the MVS  operating system and PSF/MVS Version 2.2.0 is installed using  SMP/E.  ù For this option, PSF/MVS Version 2.2.0 device support is run.  ù SYSGEN is supported for PSF/MVS Version 2.2.0 using this  option.  ù PSF/MVS Version 2.2.0 can be installed in the Link Pack Area  (LPA). See consideration H on page 46 for more information.  ù For this option, an I/O configuration is required for all  channel-attached printers except 3800-3 printer.  ù You may install PSF/MVS Version 2.2.0 in different SMP/E zones  than the base control program (BCP). See consideration A on  page 43 for more information.  2. A PREVIOUS RELEASE OF PSF/MVS IS INSTALLED, YOU WANT TO  INSTALL PSF/MVS VERSION 2.2.0, AND DELETE THE PREVIOUS RELEASE.  With this option, the previous release of PSF/MVS is deleted and  PSF/MVS Version 2.2.0 is installed using SMP/E.  ù PSF/MVS Version 2.2.0 device support is run using this option.  ù SYSGEN is supported for PSF/MVS Version 2.2.0 using this  option.  ù PSF/MVS Version 2.2.0 can be installed in the Link Pack Area  (LPA). See consideration H on page 46 for more information.  ù An I/O configuration is not required using this option; the  device support code for the previous release and PSF/MVS  Version 2.2.0 are the same.  ù You may install PSF/MVS Version 2.2.0 in different SMP/E zones  than the Base Control Program (BCP). See consideration A on  page 43 for more information.  ù You may install PSF/MVS Version 2.2.0 in the same SMP/E zones  as the previous release. See consideration B on page 43 for  more information.  ù You may use the resources from the previous release for  PSF/MVS Version 2.2.0. See consideration C on page 44 for  more information. To use the PSF/MVS Version 2.2.0 resources,  see consideration D on page 44.   Installation Requirements and Considerations 40 ¤   ù You may use the installation exits from the previous release  for PSF/MVS Version 2.2.0. See consideration E on page 44 for  more information.  ù You may use the startup procedures from the previous release  for PSF/MVS Version 2.2.0. See consideration F on page 45 for  more information.   3. A PREVIOUS RELEASE OF PSF/MVS IS INSTALLED, YOU WANT TO  INSTALL PSF/MVS VERSION 2.2.0, AND MAINTAIN BOTH RELEASES USING  SMP/E.  With this option, the previous release of PSF/MVS is running in a  production environment. PSF/MVS Version 2.2.0 is installed in a  test environment using SMP/E. Both releases of PSF/MVS are  maintained through SMP/E. When the test is completed, PSF/MVS  Version 2.2.0 is deleted from the test environment and installed  into the production environment; the previous release of PSF/MVS  is deleted from that production environment.  ù PSF/MVS Version 2.2.0 must be installed into unique target  libraries using SMP/E. See consideration G on page 45 for  more information about allocating unique target libraries.  ù PSF/MVS Version 2.2.0 must be installed in different SMP/E  zones than the previous release.  ù Device support for the previous release is run using this  option.  ù SYSGEN is supported for the previous release using this  option. SYSGEN is not supported for PSF/MVS Version 2.2.0.  ù Either the previous release or PSF/MVS Version 2.2.0 can be  installed in the Link Pack Area (LPA). See consideration H on  page 46 for more information.  ù For deferred printing, a separate startup procedure must be  established for each PSF/MVS release. One PSF/MVS release is  invoked through a LINKLIB concatenation order. The other is  invoked by a STEPLIB DD statement that points to the other  PSF/MVS release. Refer to the chapter entitled "Using  Deferred-Printing Mode" in Print Services Facility/MVS:  System Programming Guide for more information.  ù For direct-attach printers, the first occurrence in the  LINKLIB concatenation search order must contain the libraries  for the PSF/MVS release that will be used.  ù An I/O configuration is not required using this option; the  device support code for the previous release and PSF/MVS  Version 2.2.0 are the same.  ù You may use the resources from the previous release for  PSF/MVS Version 2.2.0. See consideration C on page 44 for  more information. To use the PSF/MVS Version 2.2.0 resources,  see consideration D on page 44.  ù You may use the installation exits from the previous release  for PSF/MVS Version 2.2.0. See consideration E on page 44 for  more information.   Installation Requirements and Considerations 41 ¤   ù You may use the startup procedures from the previous release  for PSF/MVS Version 2.2.0. See consideration F on page 45 for  more information.  ù The ACCEPT CHECK and ACCEPT steps should not be performed  using this option.  ù When PSF/MVS Version 2.2.0 is ready to be run in the  production environment, PSF/MVS Version 2.2.0 must be deleted  from the test environment using installation option 5 on  page 43, then PSF/MVS Version 2.2.0 must be re-installed into  the production environment using installation option 2 on  page 40. When PSF/MVS Version 2.2.0 is re-installed, the  target and distribution libraries with the high level  qualifier of SYS1 should be used to APPLY and ACCEPT PSF/MVS  Version 2.2.0.  4. A PREVIOUS RELEASE OF PSF/MVS IS INSTALLED, YOU WANT TO  INSTALL AND MAINTAIN PSF/MVS VERSION 2.2.0 USING SMP/E WHILE  RETAINING THE PREVIOUS RELEASE.  With this option, the previous release is placed in a non-SMP/E  environment by copying the previous release executable members  from LINKLIB into another Authorized Program Facility (APF)  library prior to installing PSF/MVS Version 2.2.0. When PSF/MVS  Version 2.2.0 is installed using SMP/E, the previous release  target and distribution library information is deleted. The  previous release is no longer maintained using SMP/E, however it  can be run from the APF authorized library. For more information  about APF authorized libraries, see Print Services Facility/MVS:  System Programming Guide.  ù PSF/MVS Version 2.2.0 device support is run using this option.  ù SYSGEN is supported for PSF/MVS Version 2.2.0 using this  option. SYSGEN is not supported for the previous release.  ù Either the previous release or PSF/MVS Version 2.2.0 can be  installed in the Link Pack Area (LPA). See consideration H on  page 46 for more information.  ù For deferred printing, a separate startup procedure must be  established for each PSF/MVS release. One PSF/MVS release is  invoked through a LINKLIB concatenation order. The other is  invoked by a STEPLIB DD statement that points to the other  PSF/MVS release. Refer to the chapter entitled "Using  Deferred-Printing Mode" in Print Services Facility/MVS:  System Programming Guide for more information.  ù For direct-attach printers, the first occurrence in the  LINKLIB concatenation search order must contain the libraries  for the PSF/MVS release that will be used.  ù An I/O configuration is not required using this option; the  device support code for the previous release and PSF/MVS  Version 2.2.0 are the same.  ù You may install PSF/MVS Version 2.2.0 in different SMP/E zones  than the base control program (BCP). See consideration Aon  page 43 for more information.   Installation Requirements and Considerations 42 ¤   ù You may install PSF/MVS Version 2.2.0 in the same SMP/E zones  as the previous release. See consideration B on page 43 for  more information.  ù You may use the resources from the previous release for  PSF/MVS Version 2.2.0. See consideration C on page 44 for  more information. To use the PSF/MVS Version 2.2.0 resources,  see consideration D on page 44.  ù You may use the installation exits from the previous release  for PSF/MVS Version 2.2.0. See consideration E on page 44 for  more information.  ù You may use the startup procedures from the previous release  for PSF/MVS Version 2.2.0. See consideration F on page 45 for  more information.  5. YOU WANT TO DELETE PSF/MVS VERSION 2.2.0 ONLY.  The installation step on 6.1.8, "Delete PSF/MVS" on page 64 can be  used to delete PSF/MVS Version 2.2.0 and any features. This is  the only installation step that must be completed for this option.   5.3.4 CONSIDERATIONS WHEN INSTALLING PSF/MVS VERSION 2.2.0  The following considerations should be noted when PSF/MVS Version  2.2.0 is being installed. If you are unsure of which considerations  apply to your installation, you should review 5.3.3, "Installation  Options for PSF/MVS Version 2.2.0" on page 40.  A. INSTALL PSF/MVS VERSION 2.2.0 IN DIFFERENT ZONES THAN THE BCP.  ù If PSF/MVS Version 2.2.0 is installed using installation  option 3 on page 41, and the previous release of PSF/MVS is  installed in the same zones as the BCP, PSF/MVS Version 2.2.0  MUST be installed in different zones than the BCP.  ù The SMPMCS statements listed in Appendix A, "SMP/E Install  Logic" on page 78, verify that the required licensed programs  for PSF/MVS Version 2.2.0 and required maintenance are  installed on your MVS system. However, SMP/E logic does not  allow this verification to be done across different SMP/E  zones. Therefore, if PSF/MVS Version 2.2.0 is installed into  different SMP/E zones than the BCP, the required licensed  programs and required maintenance must be manually verified  that they are installed on your MVS system in the SMP/E zones  of the BCP. See 5.2, "Target System Requirements" on page 24  for more information on operating system, programming, and  program PTF requirements.  B. INSTALL PSF/MVS VERSION 2.2.0 IN THE SAME SMP/E ZONES AS THE  PREVIOUS RELEASE.  ù If PSF/MVS Version 2.2.0 base product and resources are  installed into the same SMP/E zones as the previous release,  SMP/E deletes the base product and resources for the previous  releases of PSF/MVS.   Installation Requirements and Considerations 43 ¤   ù If PSF/MVS Version 2.2.0 is installed using installation  option 3 on page 41, PSF/MVS Version 2.2.0 CANNOT be installed  into the same SMP/E zones as that of the previous release.  C. USE THE RESOURCES FROM A PREVIOUS RELEASE OF PSF/MVS FOR  PSF/MVS VERSION 2.2.0.  ù The resources from PSF/MVS Version 2.1.0 or PSF/MVS Version  2.1.1 can be used when PSF/MVS Version 2.2.0 is run. If the  resources from PSF/MVS Version 2.1.0 are used, the new page  definitions and form definitions that were included with  PSF/MVS Version 2.1.1 will not be available unless APAR  OY57166 for the PSF/MVS Version 2.1.0 resources is installed.  ù To use the resources from the previous release of PSF/MVS, the  PSF/MVS Version 2.2.0 resources FMID (JPRF223) should not be  installed.  ù To merge the resources from the previous release of PSF/MVS  and PSF/MVS Version 2.2.0, the resources from the previous  release are saved into a temporary data set before the PSF/MVS  Version 2.2.0 resources are installed. After running the  Installation Verification Procedure (IVP), the resources from  the previous release are copied into the new PSF/MVS Version  2.2.0 resources data set.  ù The data set allocation sizes specified for the resources in  this program directory may be insufficient to store merged  resource data sets. The size of the resource data sets may  need to be increased.  D. USE THE RESOURCES PROVIDED WITH PSF/MVS VERSION 2.2.0.  ù To use the resources provided with PSF/MVS Version 2.2.0, the  resources FMID (JPRF223) should be installed.  ù If the resources for a previous release of PSF/MVS are  installed, and the PSF/MVS Version 2.2.0 resources are  installed into the same SMP/E zones as the previous release,  SMP/E deletes the resources for the previous release.  ù The names of the resources provided with PSF/MVS Version 2.2.0  can be found by listing the SMPMCS file. Refer to Print  Services Facility/MVS: Application Programming Guide for more  information regarding resources and their use.  E. USE THE INSTALLATION EXITS FROM A PREVIOUS RELEASE OF PSF/MVS  FOR PSF/MVS VERSION 2.2.0.  ù The installation exits from PSF/MVS Version 2.1.0 or PSF/MVS  Version 2.1.1 can be used when PSF/MVS Version 2.2.0 is run.  If the PSF/MVS Version 2.1.0 installation exits are used, the  additional function that was added for the installation exits  in PSF/MVS Version 2.1.0 may not be used unless APARs OY54600,  OY51438, and OY43462 for PSF/MVS Version 2.1.0 have been  installed. These APARs are included in the PSF/MVS Version  2.2.0 base product.  ù To use the installation exits from PSF/MVS Version 2.1.0, the  installation exits APSUX01, APSUX02, APSUX03, APSUX04,   Installation Requirements and Considerations 44 ¤   APSUX05, APSUX06, APSUX07, and APSUX16 from the PSF/MVS  Version 2.1.0 SAMPLIB data set are copied into a temporary  data set before PSF/MVS Version 2.2.0 is installed. After  running the Installation Verification Procedure (IVP), the  PSF/MVS Version 2.1.0 installation exits are copied into the  new PSF/MVS Version 2.2.0 SAMPLIB data set. After copying the  installation exits, the installation exits must be reassembled  and link-edited using the PSF/MVS Version 2.2.0 macro library.  The resulting object must be placed in the PSF/MVS Version  2.2.0 LINKLIB data set.  ù Refer to the chapter entitled "Using Installation Exits" in  Print Services Facility/MVS: System Programming Guide for  more information on installation exits.  F. USE THE STARTUP PROCEDURES FROM A PREVIOUS RELEASE OF PSF/MVS  FOR PSF/MVS VERSION 2.2.0.  ù The startup procedures from PSF/MVS Version 2.1.0 or PSF/MVS  Version 2.1.1 can be used when PSF/MVS Version 2.2.0 is run.  The startup procedures for all three releases are the same.  ù To use the startup procedures from a previous release, the  startup procedures APSWPROA, APSWPROC, APSWPROS, APSWPROD, and  APSWPROB from the PROCLIB data set are copied into a temporary  data set before PSF/MVS Version 2.2.0 is installed. Before  running the Installation Verification Procedure (IVP), the  previous release startup procedures are copied into the new  PSF/MVS Version 2.2.0 PROCLIB data set.  G. ALLOCATE UNIQUE TARGET LIBRARIES.  ù You are required to allocate unique target libraries for  PSF/MVS Version 2.2.0 if installation option 3 on page 41 is  used.  ù You may allocate unique target libraries for PSF/MVS Version  2.2.0 if installation option 2 on page 40, or option 4 on  page 42 is used.  ù If the target libraries used for PSF/MVS Version 2.2.0 are  different than the target libraries used for the previous  release of PSF/MVS, PSF/MVS Version 2.2.0 must be installed in  different SMP/E zones than the previous release.  ù If unique target libraries are used, references to the high  level qualifier SYS1 must be changed in this program  directory, in the sample jobs, and in the startup procedures,  to be the unique high level qualifier name.  ù If unique target libraries are used, SYSGEN is not supported.  ù If installation option 2 on page 40 or option 4 on page 42 is  used, some PSF/MVS Version 2.2.0 members cannot be installed  in unique target libraries. The following members MUST be  installed into the specified SYS1 data sets:  Ä For device support from the previous release, module  IGE0000E must be installed in the data set SYS1.LINKLIB.  Ä All members from the previous release that are installed  in the data set SYS1.NUCLEUS, cannot be installed in a  unique target library.   Installation Requirements and Considerations 45 ¤   H. INSTALL PSF/MVS VERSION 2.2.0 INTO THE LINK PACK AREA (LPA).  ù If PSF/MVS Version 2.2.0 will be used with direct attach  printers, then PSF/MVS Version 2.2.0 CANNOT be installed into  LPA.  ù PSF/MVS Version 2.2.0 performance may be improved if many  functional subsystems (FSS) are defined and PSF/MVS Version  2.2.0 is installed into LPA. For deferred printing, certain  load modules can be installed into LPA. Some high usage  modules are listed below which are good candidates to be  placed into the MVS LPA and ELPA to obtain performance  improvements.  Ä APSPPIEP (aliases APSAFSA, APSPPFSA, APSPPNST, APSZCMND,  APSZRSTR) - ELPA  Ä APSGBTL - LPA  Ä APSFSI24, if you use JES2 or JES3, Version 2 or 3 - LPA  Ä APSFSI31, if you use JES2 or JES3, Version 4 - ELPA  Ä DCKVTBL, if you use SNA printers - ELPA.   5.3.5 SPECIAL CONSIDERATIONS  ù INSTALL PSF/MVS VERSION 2.2.0 USING SYSGEN.  SYSGEN is not required to install PSF/MVS Version 2.2.0. The  recommended method to install PSF/MVS Version 2.2.0 is using the  SMP/E RECEIVE, APPLY, and ACCEPT method instead of a full SYSGEN.  However, PSF/MVS Version 2.2.0 supports installation of the base  product using SYSGEN on MVS systems that allow SYSGEN. The  resources (JPRF223) are not installable using SYSGEN on any MVS  system.  NOTE: The high level qualifier for your distribution library data  sets must be SYS1, the same name as the data sets listed in 6.1.3,  "Create Target and Distribution Library DDDEFs" on page 53. If  not, SYSGEN will not be supported on your MVS system.  ù MIGRATE FROM PSF/MVS VERSION 1.3.0  Instructions to migrate from PSF/MVS Version 1.3.0 are in Print  Services Facility/MVS: Program Directory for Version 2.1.1  (G544-3668-01).      Installation Requirements and Considerations 46 ¤   6.0 INSTALLATION INSTRUCTIONS    This section describes the installation method and the step-by-step  procedures to install and to activate the functions of PSF/MVS Version  2.2.0.  Refer to the font program directories for PSF/MVS Version 2.2.0 font  installation instructions.  Refer to ACIF and AFP API Version 2.2.0 Program Directory for  installation instructions for ACIF and AFP API.  Refer to Page Printer Migration Programs Version 2.2.0 Program  Directory for PPMP installation instructions.  Refer to MVS Download Version 2.2.0 Program Directory for installation  instructions for MVS Download.  Refer to Netspool Version 2.2.0 Program Directory for installation  instructions for Netspool.  Refer to AFP Upload for AIX Program Directory for installation  instructions for AFP Upload for AIX.  If PSF/MVS Version 2.2.0 was obtained as part of a CBPDO, the RCVPDO  job in the CBPDO RIMLIB data set can be used to run the SMP/E RECEIVE  for PSF/MVS Version 2.2.0. All service, HOLDDATA, and preventive  service planning (PSP) information is included on the CBPDO tape. For  more information, refer to the MVS CBPDO Memo to User Extension  included with the CBPDO.  PSF/MVS Version 2.2.0 is installed using the SMP/E RECEIVE, APPLY, and  ACCEPT commands.  Many of the installation steps can be completed using the SMP/E dialog  panels. See Appendix D, "SMP/E Dialog Panel Information" on page 118  for more information about SMP/E dialog panels. If you choose not to  use the SMP/E dialog panels, sample jobs are provided for the  installation of PSF/MVS Version 2.2.0.  All SMP/E installation jobs provided, assume the existence of two  cataloged procedures called SMPPROC and smpbase containing all  necessary DD statements for the execution of SMP/E. SMPPROC must  point to the SMP/E zones where you are installing PSF/MVS Version  2.2.0. If a previous release of PSF/MVS is installed, smpbase must  point to those SMP/E zones. If your SMP/E procedures are not named  SMPPROC and smpbase, substitute your procedure names for SMPPROC and  smpbase. If an SMP/E procedure is not on your system, refer to System  Modification Program Extended (SMP/E) User's Guide, or System   (C) Copyright IBM Corp. 1983, 1996 47 ¤   Modification Program Extended (SMP/E) Reference for instructions to  build one.  The SMPPROC procedure is not required when using the SMP/E dialogs.  The equivalent function can be accomplished through the SMP/E dialogs.  In the sample SMP/E jobs provided, the global zone name in the SMP/E  consolidated software inventory (CSI) is GLOBAL. The target zone name  is tgtzone. The distribution zone name is dlibzone. The sample jobs  should be updated to reflect the zone names used at your installation.   6.1 INSTALLATION STEPS  ÚÄÄÄ NOTE ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | Before installing PSF/MVS Version 2.2.0, read 5.3.3, |  | "Installation Options for PSF/MVS Version 2.2.0" on page 40 to |  | determine the installation option that you will use and the |  | considerations that correspond to that installation option. |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  The following steps are described in this section. Depending on the  installation option that is used, (See 5.3.3, "Installation Options  for PSF/MVS Version 2.2.0" on page 40), some or all of these steps are  completed:  1. Unload sample jobs  2. Allocate target and distribution library data sets  3. Create target and distribution library DDDEFs  4. Copy PSF/MVS target libraries from a previous release to temporary  data sets.  5. RECEIVE PSF/MVS Version 2.2.0 applicable FMIDs.  6. RECEIVE the cumulative service tape, if applicable.  7. Transfer ownership of SYSMODs using UCLIN.  8. Delete a previous release of PSF/MVS.  9. Perform APPLY CHECK.  10. Load target libraries using APPLY.  11. Perform I/O Configuration.  12. Modify the system environment for PSF/MVS Version 2.2.0.  13. IPL the MVS System.  14. Perform ACCEPT CHECK.  15. Load distribution libraries using ACCEPT.  16. Replace PSF/MVS startup procedures from a previous release.  17. Perform all activities in 7.0, "Installation Verification  Procedure" on page 72.  18. Replace PSF/MVS resources from a previous release.  19. Replace PSF/MVS installation exits from a previous release.  See Appendix E, "Checklist for PSF/MVS Version 2.2.0 Installation" on  page 120 for a check list of installation steps that can be used when  PSF/MVS Version 2.2.0 is installed.   Installation Instructions 48 ¤   6.1.1 UNLOAD SAMPLE JOBS  Sample jobs are provided on the PSF/MVS Version 2.2.0 tape to help  install PSF/MVS Version 2.2.0 base product and resources.  Use the JCL shown in Figure 12 on page 49 to unload the sample jobs  from file "IBM.HPRF220.F5" on the PSF/MVS Version 2.2.0 tape.  If the sample jobs are unloaded into a data set with a different name  from psf.jcllib, all future references in this directory to psf.jcllib  should be replaced with that new name.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //UNLOAD JOB 'account #','name',MSGLEVEL=(1,1) |  | //STEP1 EXEC PGM=IEBCOPY |  | //SYSPRINT DD SYSOUT=* |  | //* |  | //*----------------------------------------------------------- |  | //* UNLOAD SAMPLE JOBS FROM TAPE. |  | //* NOTE: CHANGE tape TO A VALID NAME FOR A TAPE DRIVE. |  | //* CHANGE nnnnnn TO A VALID VOLSER. |  | //* CHANGE psf.jcllib TO A VALID DATA SET NAME |  | //* FOR YOUR INSTALLATION. |  | //*----------------------------------------------------------- |  | //* |  | //INTAPE DD DSNAME=IBM.HPRF220.F5,DISP=(OLD,KEEP), |  | // UNIT=(tape,,DEFER), |  | // LABEL=(6,SL), |  | // VOL=SER=PRF220 |  | //OUTDISK DD DSNAME=psf.jcllib,DISP=(NEW,CATLG,DELETE), |  | // UNIT=SYSDA,SPACE=(TRK,(5,1,3)),VOL=SER=nnnnnn |  | //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(30,5)),DISP=(NEW,DELETE) |  | //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(30,5)),DISP=(NEW,DELETE) |  | //SYSIN DD * |  | COPY OUTDD=OUTDISK,INDD=INTAPE |  | S M=(APSWAC,APSWACCK,APSWALOC,APSWAP,APSWAPCK,APSWDDEF + |  | APSWDEL,APSWMFID,APSWRCV,APWSRCVC) |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 12. Sample JCL to Unload PSF/MVS Version 2.2.0 Sample Jobs  When this job is submitted, the following sample jobs to install  PSF/MVS Version 2.2.0 are put into the psf.jcllib data set:      Installation Instructions 49 ¤   APSWAC Sample ACCEPT job  APSWACCK Sample ACCEPT CHECK job  APSWALOC New data set allocation PSF/MVS Version 2.2.0  APSWAP Sample APPLY job  APSWAPCK Sample APPLY CHECK job  APSWDDEF Sample job to define SMP/E DDDEFs  APSWDEL Sample job to delete a previous release of PSF/MVS  APSWMFID Sample UCLIN to transfer ownership of SYSMODs  APSWRCV Sample RECEIVE job  APSWRCVC Sample RECEIVE job for cumulative service   6.1.2 ALLOCATE TARGET AND DISTRIBUTION LIBRARY DATA SETS  The APSWALOC JCL on the PSF/MVS Version 2.2.0 base tape, contains JCL  that allocates the new target and distribution data sets needed for  installation of PSF/MVS Version 2.2.0. After the sample installation  JCL is unloaded from the base tape, the APSWALOC JCL shown in  Figure 13 on page 51 exists in the data set psf.jcllib(APSWALOC).           Installation Instructions 50 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWALOC JOB 'account #','name',MSGLEVEL=(1,1) |  | //* |  | //*********************************************************** |  | //* ALLOCATE THE NEW TARGET AND DISTRIBUTION DATA SETS * |  | //* FOR PSF/MVS BASE PRODUCT AND THE RESOURCES. * |  | //* CHANGE xxxx TO BE A VALID UNIT NAME FOR YOUR * |  | //* INSTALLATION. * |  | //* CHANGE tttttt TO BE A VALID VOLUME SERIAL NAME FOR * |  | //* THE TARGET LIBRARIES. * |  | //* CHANGE dddddd TO BE A VALID VOLUME SERIAL NAME FOR * |  | //* THE DISTRIBUTION LIBRARIES. * |  | //*********************************************************** |  | //ALLOC PROC PSFPRFX=SYS1, |  | // UNIT=xxxx,TVOL=tttttt,DVOL=dddddd |  | //ALLOC1 EXEC PGM=IEFBR14 |  | //AAPSMOD0 DD DSN=&PSFPRFX..AAPSMOD0,DISP=(NEW,CATLG), |  | // DCB=(RECFM=U,LRECL=0,BLKSIZE=6144), |  | // UNIT=&UNIT,VOL=SER=&DVOL,SPACE=(6144,(712,71,81)) |  | //* |  | //AAPSDAT0 DD DSN=&PSFPRFX..AAPSDAT0,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&DVOL,SPACE=(8209,(36,4,2)) |  | //* |  | //APSDAT00 DD DSN=&PSFPRFX..APSDAT00,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&TVOL,SPACE=(8209,(36,4,2)) |  | //* |  | //*********************************************************** |  | //* ALLOCATE THE TARGET DATA SETS FOR THE RESOURCES. * |  | //* COMMENT OUT THIS SECTION IF YOU ARE NOT INSTALLING * |  | //* THE RESOURCES. * |  | //*********************************************************** |  | //* |  | //FDEFLIB DD DSN=&PSFPRFX..FDEFLIB,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&TVOL,SPACE=(8209,(24,2,5)) |  | //* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 13 (Part 1 of 2). Job to Allocate PSF/MVS Version 2.2.0 Data  Sets      Installation Instructions 51 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //PDEFLIB DD DSN=&PSFPRFX..PDEFLIB,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&TVOL,SPACE=(8209,(54,5,5)) |  | //* |  | //OVERLIB DD DSN=&PSFPRFX..OVERLIB,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&TVOL,SPACE=(8209,(12,1,1)) |  | //* |  | //PSEGLIB DD DSN=&PSFPRFX..PSEGLIB,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&TVOL,SPACE=(8209,(24,2,1)) |  | //* |  | //*********************************************************** |  | //* ALLOCATE THE DISTRIBUTION DATA SETS FOR THE RESOURCES. * |  | //* COMMENT OUT THIS SECTION IF YOU ARE NOT INSTALLING * |  | //* THE RESOURCES. * |  | //*********************************************************** |  | //* |  | //AFDEFLIB DD DSN=&PSFPRFX..AFDEFLIB,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&DVOL,SPACE=(8209,(24,2,5)) |  | //* |  | //APDEFLIB DD DSN=&PSFPRFX..APDEFLIB,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&DVOL,SPACE=(8209,(54,5,5)) |  | //* |  | //AOVERLIB DD DSN=&PSFPRFX..AOVERLIB,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&DVOL,SPACE=(8209,(12,1,1)) |  | //* |  | //APSEGLIB DD DSN=&PSFPRFX..APSEGLIB,DISP=(NEW,CATLG), |  | // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), |  | // UNIT=&UNIT,VOL=SER=&DVOL,SPACE=(8209,(24,2,1)) |  | //* |  | //EALLOC PEND |  | //* |  | //ALLOCAT EXEC ALLOC |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 13 (Part 2 of 2). Job to Allocate PSF/MVS Version 2.2.0 Data  Sets  A return code of "0" should be received from the APSWALOC JCL.     Installation Instructions 52 ¤   6.1.3 CREATE TARGET AND DISTRIBUTION LIBRARY DDDEFS  SMP/E DDDEF entries for each target and distribution library data set  should be defined at this time, if not already done. If you are  planning to install PSF/MVS Version 2.2.0 into the same zone as a  previous release of PSF/MVS, the DDDEFs may already be defined. See  5.3, "PSF/MVS Version 2.2.0 Installation Considerations" on page 35  for the installation options possible for PSF/MVS Version 2.2.0.  These data sets have a high-level qualifier of SYS1, or PSF. If a  different high level qualifier is used to install PSF/MVS Version  2.2.0, the target library data set with the low level qualifier of  LINKLIB must be authorized by the authorized program facility (APF).  SYSGEN for PSF/MVS Version 2.2.0 is not supported if the distribution  library data sets do not have the same data set names as the names  listed in this section. See 5.3.5, "Special Considerations" on  page 46 for information about SYSGEN.  The JCL in Figure 14 on page 54 is used to create the required SMP/E  DDDEFs to install PSF/MVS Version 2.2.0. After the PSF/MVS Version  2.2.0 sample JCL is unloaded from the tape, this JCL exists in the  data set psf.jcllib(APSWDDEF).  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. See 6.1.2, "Allocate Target and Distribution  Library Data Sets" on page 50 for information on allocating the  target and distribution data sets.  NOTE: SMP/E dialog panels may be used to define these DDDEFs instead  of the JCL.  NOTE: If installation option 1, 2, or 4 is used, and you want to  install PSF/MVS Version 2.2.0 into the same SMP/E zones as the base  control program (BCP), some DDDEFs may already be defined. If the  following DDDEFs are already defined, you should edit APSWDDEF to  remove them before running this job:  LINKLIB  MACLIB  NUCLEUS  PROCLIB  SAMPLIB  AGENLIB  ALINKLIB  AMACLIB  ANUCLEUS  AOSC5  APROCLIB  ASAMPLIB    Installation Instructions 53 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSDDDEF JOB 'acct. no.','name',MSGLEVEL=(1,1) |  | //SMP EXEC SMPPROC |  | //* |  | //************************************************* |  | //* Allocate SMP/E DDDEFS FOR PSF/MVS. |  | //* Modify the tgtzone, dlibzone, uuuu, tvol, |  | //* and dvol names in lower case as appropriate |  | //* for your installation. |  | //* The distribution library DDDEFS are defined |  | //* to the target zone for RESTORE purposes. |  | //************************************************* |  | //SMP.SMPCNTL DD * |  | SET BDY(tgtzone) . |  | UCLIN . |  | REP DDDEF(APSDAT00) |  | DATASET(SYS1.APSDAT00) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(LINKLIB) |  | DATASET(SYS1.LINKLIB) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(MACLIB) |  | DATASET(SYS1.MACLIB) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(NUCLEUS) |  | DATASET(SYS1.NUCLEUS) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(PROCLIB) |  | DATASET(SYS1.PROCLIB) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(SAMPLIB) |  | DATASET(SYS1.SAMPLIB) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(FDEFLIB) |  | DATASET(SYS1.FDEFLIB) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 14 (Part 1 of 4). JCL to Create Target and Distribution DDDEFs  for PSF/MVS Version 2.2.0     Installation Instructions 54 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | REP DDDEF(PDEFLIB) |  | DATASET(SYS1.PDEFLIB) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(OVERLIB) |  | DATASET(SYS1.OVERLIB) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(PSEGLIB) |  | DATASET(SYS1.PSEGLIB) |  | UNIT(uuuu) VOLUME(tvol) |  | OLD . |  | REP DDDEF(AAPSDAT0) |  | DATASET(SYS1.AAPSDAT0) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AAPSMOD0) |  | DATASET(SYS1.AAPSMOD0) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AGENLIB) |  | DATASET(SYS1.AGENLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(ALINKLIB) |  | DATASET(SYS1.ALINKLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AMACLIB) |  | DATASET(SYS1.AMACLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(ANUCLEUS) |  | DATASET(SYS1.ANUCLEUS) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AOSC5) |  | DATASET(SYS1.AOSC5) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(APROCLIB) |  | DATASET(SYS1.APROCLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 14 (Part 2 of 4). JCL to Create Target and Distribution DDDEFs  for PSF/MVS Version 2.2.0    Installation Instructions 55 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | REP DDDEF(ASAMPLIB) |  | DATASET(SYS1.ASAMPLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AFDEFLIB) |  | DATASET(SYS1.AFDEFLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(APDEFLIB) |  | DATASET(SYS1.APDEFLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AOVERLIB) |  | DATASET(SYS1.AOVERLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(APSEGLIB) |  | DATASET(SYS1.APSEGLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | ENDUCL. |  | SET BDY(dlibzone) . |  | UCLIN . |  | REP DDDEF(AAPSDAT0) |  | DATASET(SYS1.AAPSDAT0) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AAPSMOD0) |  | DATASET(SYS1.AAPSMOD0) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AGENLIB) |  | DATASET(SYS1.AGENLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(ALINKLIB) |  | DATASET(SYS1.ALINKLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AMACLIB) |  | DATASET(SYS1.AMACLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 14 (Part 3 of 4). JCL to Create Target and Distribution DDDEFs  for PSF/MVS Version 2.2.0    Installation Instructions 56 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | REP DDDEF(ANUCLEUS) |  | DATASET(SYS1.ANUCLEUS) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AOSC5) |  | DATASET(SYS1.AOSC5) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(APROCLIB) |  | DATASET(SYS1.APROCLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(ASAMPLIB) |  | DATASET(SYS1.ASAMPLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AFDEFLIB) |  | DATASET(SYS1.AFDEFLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(APDEFLIB) |  | DATASET(SYS1.APDEFLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(AOVERLIB) |  | DATASET(SYS1.AOVERLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | REP DDDEF(APSEGLIB) |  | DATASET(SYS1.APSEGLIB) |  | UNIT(uuuu) VOLUME(dvol) |  | OLD . |  | ENDUCL . |  | /* |  | // |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 14 (Part 4 of 4). JCL to Create Target and Distribution DDDEFs  for PSF/MVS Version 2.2.0  A return code of "4" and the message GIM27701W should be received from  this JCL if the DDDEFs have never been created. A return code of "0"  should be received if the DDDEFs were created previously.   6.1.4 COPY PSF/MVS TARGET LIBRARIES FROM A PREVIOUS RELEASE  If installation option 2, 3 or 4 is used to install PSF/MVS Version  2.2.0, the items in this section apply to the installation.    Installation Instructions 57 ¤   6.1.4.1 COPY PSF/MVS LINKLIB INTO ANOTHER APF AUTHORIZED LIBRARY  If installation option 4 is used to install PSF/MVS Version 2.2.0, the  LINKLIB members from the previous release of PSF/MVS must be copied  into a new APF authorized library before PSF/MVS Version 2.2.0 is  installed. Refer to Print Services Facility/MVS: System Programming  Guide for more information on APF authorized libraries.   6.1.4.2 COPY PSF/MVS RESOURCES TO A TEMPORARY DATA SET  If installation option 2, 3 or 4 is used, and you want to use the  resources from a previous release of PSF/MVS, then complete the  following step.  To use the resources from a previous release of PSF/MVS with PSF/MVS  Version 2.2.0, do not install the PSF/MVS Version 2.2.0 resources FMID  (JPRF223).  To merge the resources from the previous release of PSF/MVS and  PSF/MVS Version 2.2.0, copy the resources from the previous release  into a temporary data set so that they are not overwritten by the  resources supplied with PSF/MVS Version 2.2.0. See consideration C on  page 44 for more information about using resources from a previous  release of PSF/MVS with PSF/MVS Version 2.2.0.  After the installation verification procedure is completed, these  members are copied into the PSF/MVS Version 2.2.0 resources data sets  using the instructions in 6.1.19, "Replace PSF/MVS Resources from  Previous Release" on page 70.   6.1.4.3 COPY PSF/MVS INSTALLATION EXITS TO A TEMPORARY DATA SET  If installation option 2, 3 or 4 is used, and you want to use the  installation exits from a previous release of PSF/MVS, then complete  the following step.  To use the installation exits from PSF/MVS Version 2.1.0 or PSF/MVS  Version 2.1.1 with PSF/MVS Version 2.2.0, the installation exits from  the previous release must be copied into a temporary data set so that  they are not overwritten by the installation exits supplied with  PSF/MVS Version 2.2.0. See consideration E on page 44 for more  information about using installation exits from a previous release of  PSF/MVS.  To use the installation exits from PSF/MVS Version 2.1.0 or PSF/MVS  Version 2.1.1 with PSF/MVS Version 2.2.0, copy the installation exit  members APSUX01, APSUX02, APSUX03, APSUX04, APSUX05, APSUX06, APSUX07,  and APSUX16 from the SAMPLIB data set into a temporary data set.  After the installation verification procedure is completed, these  members are copied into the PSF/MVS Version 2.2.0 SAMPLIB data set   Installation Instructions 58 ¤   using the instructions in 6.1.20, "Replace PSF/MVS Installation Exits  from Previous Release" on page 71.   6.1.4.4 COPY PSF/MVS STARTUP PROCEDURES TO A TEMPORARY DATA SET  If installation option 2, 3 or 4 is used, and you want to use the  startup procedures from a previous release of PSF/MVS, then complete  the following step.  To use the startup procedures from PSF/MVS Version 2.1.0 or PSF/MVS  Version 2.1.1 with PSF/MVS Version 2.2.0, the startup procedures from  the previous release must be copied into a temporary data set so that  they are not overwritten by the startup procedures supplied with  PSF/MVS Version 2.2.0. See consideration F on page 45 for more  information about using startup procedures from a previous release of  PSF/MVS.  To use the startup procedures from PSF/MVS Version 2.1.0 or PSF/MVS  Version 2.1.1 with PSF/MVS Version 2.2.0, copy the startup procedure  members APSWPROA, APSWPROC, APSWPROS, APSWPROD, and APSWPROB from the  PROCLIB data set into a temporary data set.  After the installation verification procedure is completed, these  members are copied into the PSF/MVS Version 2.2.0 PROCLIB data set  using the instructions in 6.1.17, "Replace PSF/MVS Startup Procedures  from Previous Release" on page 70.   6.1.5 RECEIVE PSF/MVS VERSION 2.2.0 APPLICABLE FMIDS  If installation option 1, 2, 3, or 4 is used, then run the SMP/E  RECEIVE job to unload the PSF/MVS Version 2.2.0 applicable data from  the product tape into SMP/E temporary data sets.  The RECEIVE job exists in the data set psf.jcllib(APSWRCV), and is  shown in Figure 15 on page 60.  Modify the RECEIVE statement to specify the FMIDs that you want to  install. HPRF220, and JPRF223 are valid FMIDs for the PSF/MVS Version  2.2.0 base product tape.  The SMP/E dialog panels may be used for the RECEIVE step instead of  the supplied sample job. See Appendix D, "SMP/E Dialog Panel  Information" on page 118 for dialog information.  NOTE: If PSF/MVS Version 2.2.0 is not RECEIVED into the SMP/E zones  of the BCP, the IFREQ statements in the SMPMCS file are not resolved.  NOTE: This step is bypassed if receiving the product from a CBPDO.    Installation Instructions 59 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWRCV JOB 'account #','name',MSGLEVEL=(1,1) |  | //RECEIVE EXEC SMPPROC |  | //SMP.SMPPTFIN DD DSN=SMPMCS,DISP=(OLD,PASS), |  | // VOL=SER=PRF220,LABEL=(1,SL), |  | // UNIT=(tape,,DEFER) |  | //SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn |  | //SMP.SMPCNTL DD * |  | SET BDY(GLOBAL). |  | RECEIVE S(HPRF220, JPRF223) SYSMOD . |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 15. RECEIVE Job for PSF/MVS Version 2.2.0  A return code of "0" should be received from the RECEIVE job.   6.1.6 RECEIVE CUMULATIVE SERVICE TAPE, IF APPLICABLE  A cumulative service tape may be shipped with the product package. If  no cumulative service tape is shipped or if the product is received by  CBPDO, skip this section.  If installation option 1, 2, 3, or 4 is used, then run the job in  Figure 16 on page 61. This is a sample job to RECEIVE the PTFs and  HOLDDATA from the cumulative service tape.  This job exists in the data set psf.jcllib(APSWRCVC) and also in  psf.jcllib.(APKQRCVC).          Installation Instructions 60 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWRCVC JOB 'account #','name',MSGLEVEL=(1,1) |  | //*********************************** *************** |  | //* RECEIVE CUMULATIVE SERVICE DATA. * |  | //* CHANGE tape TO BE A VALID UNIT. |  | //* CHANGE sssssss TO BE A SOURCEID. . * |  | //* SOURCEID IS A UNIQUE NAME THAT ASSIGNS * |  | //* A COMMON IDENTIFIER TO THE SYSMODS RECEIVED. * |  | //*************************************************** |  | //APSWRCVC EXEC SMPPROC |  | //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 16. RECEIVE Job for Cumulative Service Tape  A return code of "0" should be received from this job.  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.   6.1.7 TRANSFER OWNERSHIP OF SYSMODS USING UCLIN  ÚÄÄÄ NOTE ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | Most installations do NOT need to run this step. Skip this step |  | under the following circumstances: |  | |  | 1. If DFP Version 3 Release 3 or higher is installed, and PSF/MVS |  | was not previously installed |  | |  | 2. If a prior level of PSF/MVS was installed in the same zone as |  | the BCP, and PSF/MVS 2.2.0 is being installed in this same |  | zone |  | |  | 3. If installation option 3 is used |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ    Installation Instructions 61 ¤   If installation option 2 or 4 is used, and PSF/MVS Version 2.2.0 will  be installed into different SMP/E zones than the previous release of  PSF/MVS, this step must be completed.  This step must also be completed if installation option 1 is used AND  DFP Version 3 release 2.0 or lower is installed on your MVS operating  system.  Run the SMP/E job in Figure 17 on page 63 to transfer ownership of the  elements to the PSF/MVS Version 2.2.0 FMID HPRF220.  This job exists in the data set psf.jcllib(APSWMFID).  This job must be run against the SMP/E zones where the PREVIOUS  release of PSF/MVS is installed, or if you have never installed  PSF/MVS, this job must be run against the SMP/E zones of the BCP. The  SMP/E procedure, smpbase, in this job must be changed to the  appropriate zone.               Installation Instructions 62 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWMFID JOB 'account #','name',MSGLEVEL=(1,1) |  | //***************************************************** |  | //* JOB TO TRANSFER OWNERSHIP OF SYSMODS FROM * |  | //* DFP TO PSF/MVS. * |  | //* CHANGE smpbase TO BE THE SMP/E PROCEDURE THAT * |  | //* POINTS TO THE BCP CSI. * |  | //* CHANGE tgtzone TO BE THE TARGET ZONE FOR THE * |  | //* BCP CSI. * |  | //* CHANGE dlibzone TO BE THE DISTRIBUTION LIBRARY * |  | //* ZONE FOR THE BCP CSI. * |  | //*01* CHANGE-ACTIVITY : * |  | //* $01=OY43206,HPRF102,042991,BLDMAN : ADD RMID * |  | //***************************************************** |  | //MODFMID EXEC smpbase |  | //SMP.SMPCNTL DD * |  | SET BDY(tgtzone). |  | UCLIN. |  | REP MAC(SGAPS4PP) DISTLIB(AGENLIB) FMID(HPRF220) |  | RMID(HPRF220). |  | REP MAC(SGAPS5PR) DISTLIB(AGENLIB) FMID(HPRF220) |  | RMID(HPRF220). |  | REP MAC(SGIEI610) DISTLIB(AGENLIB) FMID(HPRF220) |  | RMID(HPRF220). |  | ENDUCL. |  | SET BDY(dlibzone). |  | UCLIN. |  | REP MAC(SGAPS4PP) DISTLIB(AGENLIB) FMID(HPRF220) |  | RMID(HPRF220). |  | REP MAC(SGAPS5PR) DISTLIB(AGENLIB) FMID(HPRF220) |  | RMID(HPRF220). |  | REP MAC(SGIEI610) DISTLIB(AGENLIB) FMID(HPRF220) |  | RMID(HPRF220). |  | ENDUCL. |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 17. Job to Transfer Ownership of SYSMODs  A return code of "0" should be received from this job.  After the APPLY and ACCEPT have been run, an SMP/E query should  indicate that PSF HPRF220 is the owner of the SGAPS4PP, SGAPS5PR, and  SGIEI610 macros.      Installation Instructions 63 ¤   6.1.8 DELETE PSF/MVS  The job in Figure 18 on page 65 deletes a PSF/MVS release.  Complete this step if installation option 5 on page 43 is used. This  step must also be completed if installation option 2 or 4 is used, and  PSF/MVS Version 2.2.0 will be installed in different SMP/E zones than  the previous release of PSF/MVS. The previous release must be deleted  from the zones that it was installed in.  The fonts and resources do not have to be deleted if you delete  PSF/MVS Version 2.2.0.  The job in Figure 18 on page 65 creates a dummy SYSMOD entry called  deltpsf, and deletes PSF/MVS by performing a RECEIVE, APPLY, and  ACCEPT of the dummy SYSMOD that points to the target and distribution  library zones where PSF/MVS resides.  This job exists in the data set psf.jcllib(APSWDEL). The Hnnnnnn  parameter in the job corresponds to the base product FMID for PSF/MVS,  and each Jnnnnnn parameter corresponds to the feature FMIDs for  PSF/MVS. See Figure 19 on page 65 to determine the base product FMIDs  and feature FMIDs for PSF/MVS. The SMP/E procedure, smpbase, in this  job must be changed to an SMP/E procedure that points to the SMP/E  zones where PSF/MVS was installed.  ÚÄÄÄ WARNING ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | After the previous release of PSF/MVS is deleted, your MVS system |  | may not IPL until the SMP/E APPLY job for PSF/MVS Version 2.2.0 is |  | run (see 6.1.10, "Load Target Libraries Using APPLY" on page 66) |  | and the I/O configuration is completed (see 6.1.11, "Perform I/O |  | Configuration" on page 67). PSF/MVS Version 2.2.0 must be |  | installed immediately after the APSWDEL job is run. |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ         Installation Instructions 64 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWDEL JOB 'account #','name',MSGLEVEL=(1,1) |  | //DELETE EXEC smpbase |  | //SMPHOLD DD DUMMY |  | //SMPRPT DD SYSOUT=* |  | //SMPOUT DD SYSOUT=* |  | //SMPPTFIN DD * |  | ++FUNCTION(deltpsf) /* DUMMY SYSMOD TO DELETE FMIDS */. |  | ++VER(Z038) DELETE(HAFnnnn,JAFnnnn). |  | //SMPCNTL DD * |  | SET BDY(GLOBAL). |  | RECEIVE S(deltpsf) . |  | SET BDY(tgtzone). |  | APPLY S(deltpsf) . |  | SET BDY(dlibzone). |  | ACCEPT S(deltpsf) . |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 18. Job to Delete PSF/MVS  A return code of "4" should be received from this job because the  dummy SYSMOD deltpsf has no elements in it.  The table in Figure 19 identifies the FMIDs for PSF/MVS.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 19. FMIDs for PSF/MVS |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | | | FEATURE |  | PSF/MVS RELEASE NO. | BASE FMID | FMIDS |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | PSF/MVS Ver. 2 Rel. 1.0 | HPRF102 | JPRF113 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | PSF/MVS Ver. 2 Rel. 1.1 | HPRF102 | JPRF113 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | PSF/MVS Ver. 2 Rel. 2.0 | HPRF220 | JPRF223 |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À   6.1.9 PERFORM APPLY CHECK  If installation option 1, 2, 3, or 4 is used, then run the SMP/E APPLY  CHECK job to determine which SYSMODs, if any, are missing. Any  missing SYSMODs should be installed before continuing with the  installation of PSF/MVS Version 2.2.0.  Modify the APPLY CHECK statement to specify the FMIDs that were  RECEIVEd. HPRF220 and JPRF223 are valid FMIDs.  The APPLY CHECK job exists in the data set psf.jcllib(APSWAPCK), and  is shown in Figure 20 on page 66.   Installation Instructions 65 ¤   SMP/E dialog panels can be used for the APPLY CHECK instead of the  supplied job. See Appendix D, "SMP/E Dialog Panel Information" on  page 118 for dialog information.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWAPCK JOB 'account #','name',MSGLEVEL=(1,1) |  | //APPLY EXEC SMPPROC |  | //SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn |  | //SMP.SMPCNTL DD * |  | SET BDY(tgtzone). |  | APPLY CHECK S(HPRF220,JPRF223) |  | BYPASS(HOLDSYS,HOLDUSER, |  | HOLDCLASS(UCLREL,ERREL)) GROUPEXTEND. |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 20. APPLY CHECK Job  A return code of "0" should be received from the APPLY CHECK job.  Investigate any problems if a return code of "0" is not received from  this job before continuing with the installation of PSF/MVS Version  2.2.0.   6.1.10 LOAD TARGET LIBRARIES USING APPLY  If installation option 1, 2, 3, or 4, is used, then run the SMP/E  APPLY job to load the SMP/E target libraries from SMP/E temporary data  sets.  Modify the APPLY statement to specify the FMIDs that were RECEIVEd.  HPRF220 and JPRF223 are valid FMIDs.  The APPLY job exists in the data set psf.jcllib(APSWAPP), and is shown  in Figure 21 on page 67.  SMP/E dialog panels can be used for the APPLY instead of the supplied  job. See Appendix D, "SMP/E Dialog Panel Information" on page 118 for  dialog information.       Installation Instructions 66 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWAP JOB 'account #','name',MSGLEVEL=(1,1) |  | //APPLY EXEC SMPPROC |  | //SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn |  | //SMP.SMPCNTL DD * |  | SET BDY(tgtzone). |  | APPLY S(HPRF220,JPRF223) |  | BYPASS(HOLDCLASS(UCLREL,ERREL)) |  | GROUPEXTEND. |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 21. APPLY Job  A return code of "0" should be received from the APPLY job.  Investigate any problems if a return code of "0" is not received from  this job before continuing with the installation of PSF/MVS Version  2.2.0.   6.1.11 PERFORM I/O CONFIGURATION  If installation option 1 is used, or if your I/O configuration has  changed, complete this step.  An I/O configuration must be performed for printers that are channel  attached to the host and new printers that are added to your system by  using either MVSCP or Hardware Configuration Dialog (HCD) if MVS/ESA  Version 4.2.0 or above is installed on your MVS operating system.  Refer to the section entitled "Defining Channel-Attached Printers to  MVS" in Print Services Facility/MVS: System Programming Guide for  information on configuration definitions.   6.1.12 MODIFY THE SYSTEM ENVIRONMENT FOR PSF/MVS VERSION 2.2.0  If installation option 1, 2, 3, or 4 is used, complete this step.  The installation of PSF/MVS Version 2.2.0 may require that the system  environment be modified before PSF/MVS Version 2.2.0 can be used. The  system environment, in this case, is the MVS program properties table,  system libraries, JES, and VTAM. The modifications required depend  upon whether PSF/MVS has been installed before, what printers will be  used, and whether the printers will be controlled with a job entry  subsystem (JES) or not.  If installation option 2, 3, or 4 is used and you do not plan to  change the system environment, then skip this step.  Refer to Print Services Facility/MVS: System Programming Guide for  information on changing the system environment.   Installation Instructions 67 ¤   6.1.13 ENABLE PSF/MVS VERSION 2.2.0 FOR OS/390 SYSTEMS  PSF/MVS Version 2.2.0 uses dynamic enablement when running on OS/390.  If you are running on an OS/390 system, you must update the IFAPRDxx  member of SYS1.PARMLIB to enable PSF/MVS. This step MUST be completed  to allow full use of PSF/MVS on OS/390. Before you can use PSF/MVS  Version 2.2.0 on OS/390, you must insure that the active IFAPRDxx  member has been updated with the correct information for PSF/MVS.  PSF/MVS Version 2.2.0 provides a sample IFAPRDxx entry in member  APSWPRDX of SYS1.SAMPLIB. Copy APSWPRDX into your active IFAPRDxx  member of SYS1.PARMLIB to enable PSF/MVS Version 2.2.0.  For more information on OS/390 dynamic enablement, refer to OS/390 MVS  Product Management, GC28-1730.   6.1.14 RE-IPL THE MVS SYSTEM  If installation option 1, 2, 3, or 4 is used, complete this step.  All previous installation steps must be successfully completed before  the MVS system is re-IPLed.  Re-IPL your MVS system to enable the changes that have been made up to  this point in the installation.  After the IPL is completed, it is possible to perform the Installation  Verification Procedures that are in 7.0, "Installation Verification  Procedure" on page 72.   6.1.15 PERFORM ACCEPT CHECK  If installation option 1, 2, or 4 is used, run the SMP/E ACCEPT CHECK  job to determine which SYSMODs, if any, are missing. Any missing  SYSMODs should be installed before continuing with the installation of  PSF/MVS Version 2.2.0.  Modify the ACCEPT CHECK statement to specify the FMIDs that were  RECEIVEd. HPRF220 and JPRF223 are valid FMIDs.  The ACCEPT CHECK job exists in the data set psf.jcllib(APSWACCK), and  is shown in Figure 22 on page 69.  SMP/E dialog panels can be used for the ACCEPT CHECK instead of the  supplied job. See Appendix D, "SMP/E Dialog Panel Information" on  page 118 for dialog information.     Installation Instructions 68 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWACCK JOB 'account #','name',MSGLEVEL=(1,1) |  | //ACCEPT EXEC SMPPROC |  | //SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn |  | //SMP.SMPCNTL DD * |  | SET BDY(dlibzone). |  | ACCEPT CHECK S(HPRF220,JPRF223) |  | BYPASS(HOLDSYS,HOLDUSER, |  | HOLDCLASS(UCLREL,ERREL)) GROUPEXTEND. |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 22. ACCEPT CHECK Job  A return code of "0" should be received from the ACCEPT CHECK job.  Investigate any problems if a return code of "0" is not received from  this job before continuing with the installation of PSF/MVS Version  2.2.0.   6.1.16 LOAD DISTRIBUTION LIBRARIES USING ACCEPT  If installation option 1, 2, or 4 is used, run the SMP/E ACCEPT job to  load the SMP/E distribution libraries from SMP/E temporary data sets.  Modify the ACCEPT statement to specify the FMIDs that were RECEIVEd.  HPRF220 and JPRF223 are valid FMIDs.  The ACCEPT job exists in the data set psf.jcllib(APSWAC), and is shown  in Figure 23.  SMP/E dialog panels can be used for the ACCEPT instead of the supplied  job. See Appendix D, "SMP/E Dialog Panel Information" on page 118 for  dialog information.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWAC JOB 'account #','name',MSGLEVEL=(1,1) |  | //ACCEPT EXEC SMPPROC |  | //SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn |  | //SMP.SMPCNTL DD * |  | SET BDY(dlibzone). |  | ACCEPT S(HPRF220,JPRF223) |  | BYPASS(HOLDCLASS(UCLREL,ERREL)) |  | GROUPEXTEND COMPRESS(ALL). |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 23. ACCEPT Job  A return code of "0" should be received from the ACCEPT job.   Installation Instructions 69 ¤   6.1.17 REPLACE PSF/MVS STARTUP PROCEDURES FROM PREVIOUS RELEASE  If the startup procedures from a previous release of PSF/MVS will be  used with PSF/MVS Version 2.2.0, and the instructions in 6.1.4.4,  "Copy PSF/MVS Startup Procedures to a Temporary Data Set" on page 59  were completed, copy the startup procedures from the previous release  from the temporary data set into the PSF/MVS Version 2.2.0 PROCLIB  data set.  To use the startup procedures from PSF/MVS Version 2.1.0 or PSF/MVS  Version 2.1.1 with PSF/MVS Version 2.2.0, copy the startup procedure  members APSWPROA, APSWPROC, APSWPROS, APSWPROD, and APSWPROB from the  temporary data set into the PSF/MVS Version 2.2.0 PROCLIB data set.   6.1.18 PERFORM INSTALLATION VERIFICATION  When all the previous installation steps have been completed  successfully, the installation verification procedure listed in 7.0,  "Installation Verification Procedure" on page 72 should be performed.   6.1.19 REPLACE PSF/MVS RESOURCES FROM PREVIOUS RELEASE  If the resources from a previous release of PSF/MVS will be merged  with the PSF/MVS Version 2.2.0 resources, and the instructions in  6.1.4.2, "Copy PSF/MVS Resources to a Temporary Data Set" on page 58  were completed, the resources from the previous release should be  copied from the temporary data set into the PSF/MVS Version 2.2.0  resource data sets. The resources from the previous release should be  copied into the PSF/MVS Version 2.2.0 resources data sets only after  the installation verification procedure is completed for PSF/MVS  Version 2.2.0.  NOTE:  ù The Installation Verification Procedure (IVP) jobs for PSF/MVS  Version 2.2.0 use some resources supplied on the PSF/MVS Version  2.2.0 tape. If the resources supplied with PSF/MVS Version 2.2.0  are not used, the IVP may not complete successfully.  ù The data set allocation sizes specified for the resources in this  program directory may be insufficient to store merged resource  data sets. The size of the resources data sets may need to be  increased.      Installation Instructions 70 ¤   6.1.20 REPLACE PSF/MVS INSTALLATION EXITS FROM PREVIOUS RELEASE  If the installation exits from a previous release of PSF/MVS will be  used with PSF/MVS Version 2.2.0, and the instructions in 6.1.4.3,  "Copy PSF/MVS Installation Exits to a Temporary Data Set" on page 58  were completed, the installation exits from the previous release  should be copied from the temporary data set into the PSF/MVS Version  2.2.0 SAMPLIB data set. The installation exits should be replaced  after the IVP for PSF/MVS Version 2.2.0 is completed.  To use the installation exits from PSF/MVS Version 2.1.0 or PSF/MVS  Version 2.1.1 with PSF/MVS Version 2.2.0, copy the installation exit  members APSUX01, APSUX02, APSUX03, APSUX04, APSUX05, APSUX06, APSUX07,  and APSUX16 from the temporary data set into the PSF/MVS Version 2.2.0  SAMPLIB data set.  After installation exits are copied into the PSF/MVS Version 2.2.0  SAMPLIB data set, they must be reassembled and link-edited using the  PSF/MVS Version 2.2.0 macro library. The resulting object must be  placed in the PSF/MVS Version 2.2.0 LINKLIB data set.              Installation Instructions 71 ¤   7.0 INSTALLATION VERIFICATION PROCEDURE    The following sections give detailed installation verification  procedures (IVP) for PSF/MVS Version 2.2.0.   7.1 PSF/MVS VERSION 2.2.0 IVP  Complete the following steps for the PSF/MVS Version 2.2.0 IVP:  ù Perform PSF/MVS Version 2.2.0 tasks before installation  verification  ù Complete the installation verification  ù Perform PSF/MVS Version 2.2.0 tasks after running installation  verification.   7.1.1 PERFORM TASKS BEFORE INSTALLATION VERIFICATION  The fonts provided with PSF/MVS Version 2.2.0 must be installed before  you run the PSF/MVS Version 2.2.0 installation verification procedure.  Refer to the font program directories for font installation  instructions.  The default fonts specified in the PRINTDEV must be made available  before the installation verification procedure can be run. This can  be accomplished by either:  1. Installing the appropriate fonts from a separate font tape  2. Converting the default fonts using the font conversion utility  APSRCF30.  See the NOTES section in the appropriate writer procedure for further  information. The writer startup procedures are listed in Appendix B,  "Startup Procedures for PSF/MVS Version 2.2.0" on page 84.   7.1.2 COMPLETE THE INSTALLATION VERIFICATION  To verify that PSF/MVS Version 2.2.0 has been installed correctly, IVP  procedures are provided in either a JES environment (for all printers  supported by PSF/MVS Version 2.2.0) or in direct-attach mode.  The IVP consists of an IEBGENER job that prints a page segment called  IVP. The page segment was placed on your system during the  installation of the resources FMID (JPRF223).   (C) Copyright IBM Corp. 1983, 1996 72 ¤   The logical-page size needed for any printer for this IVP is 8.5  inches wide by 11 inches long.   7.1.2.1 IVP JOB FOR JES ENVIRONMENT  Perform the following steps if PSF/MVS Version 2.2.0 will be used in a  JES environment:  1. Submit the APSIVP job shown in Figure 24. This job exists in the  data set SYS1.SAMPLIB(APSIVP). The job produces a listing of the  member SYS1.PSEGLIB(IVP) for output on the printer.  The output class in the SYSUT2 DD statement for the printer in the  job is class A. If this class is incorrect for your installation,  the output class should be changed to the correct value.  If PSF/MVS Version 2.2.0 will be used to print on an IBM 3800,  this job must be modified according to the comments within the  job.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSIVP JOB 'acct. #','name',MSGLEVEL=(1,1) |  | //STEP1 EXEC PGM=IEBGENER |  | //* |  | //************************************************************ |  | //* THIS IVP IS DESIGNED TO VERIFY THAT PSF HAS BEEN * |  | //* INSTALLED CORRECTLY FOR PRINTERS SUPPORTED BY PSF * |  | //* * |  | //* NOTE: * |  | //* IF THIS IVP JOB IS BEING RUN FOR A 3800 PRINTER, * |  | //* COMMENT OUT THE FIRST 'OUTPUT1' STATEMENT, AND * |  | //* UNCOMMENT THE SECOND 'OUTPUT1' STATEMENT. * |  | //************************************************************ |  | //* |  | //SYSIN DD DUMMY |  | //SYSPRINT DD SYSOUT=A |  | //OUTPUT1 OUTPUT FORMDEF=A10110 /* <-- SEE NOTE ABOVE */ |  | //*OUTPUT1 OUTPUT FORMDEF=0101 /* <-- SEE NOTE ABOVE */ |  | //SYSUT2 DD SYSOUT=A, |  | // OUTPUT=*.OUTPUT1, |  | // DCB=(RECFM=VBA,BLKSIZE=8509) |  | //SYSUT1 DD DSN=SYS1.PSEGLIB(IVP),DISP=SHR |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 24. APSIVP Job  2. Set up and start the printer. To use PSF/MVS Version 2.2.0 to  print the output of the job APSIVP, the printer must be set up  with the correct output class (class A). If you are not using the  startup procedures supplied in SYS1.PROCLIB, your startup  procedure should specify the same default page definition as   Installation Verification Procedure 73 ¤   specified in the startup procedure APSWPROA, APSWPROC, APSWPROS,  APSWPROB, APSWPROD, APSWPROM, APSWPROP or APSWPROT.  Startup procedure APSWPROA is for the following channel-attached  printers:  ù 3160 - if configured as a channel attached printer  ù 3825  ù 3827  ù 3828  ù 3829  ù 3831  ù 3835  ù 3900  ù 3935 - if configured as a channel attached printer   Startup procedure APSWPROB is for the following SNA-attached  printers using 300-pel fonts:  ù 3112  ù 3116  ù 3130 - if configured as an SNA-attached printer  ù 3912  ù 3916  ù 3935 - if configured as an SNA-attached printer  ù LaserPrinter 4019  ù LaserPrinter 4028  ù LaserPrinter 4029  ù LaserPrinter 4039  Startup procedure APSWPROC is for the IBM 3800 Printer.  Startup procedure APSWPROD is for the following SNA-attached  printers that support resident symbol sets:  ù 4224  ù 4230  ù 4234  ù 6400  Startup procedure APSWPROM is for microfilm printer support.  Startup procedure APSWPROP is for OS/390 Softcopy Print support.  Startup procedure APSWPROS is for the following SNA-attached  printers using 240-pel fonts:  ù 3130 - if configured as an SNA-attached printer  ù 3160 - if configured as an SNA-attached printer  ù 3820  ù 3812  ù 3816  ù 3930   Installation Verification Procedure 74 ¤   Startup procedure APSWPROT is for TCP/IP attached devices.  JES2 SETUP: To set up for printing under JES2, change the printer  settings, and start the printer using the following commands:  $TPRTnn,Q=A  $SPRTnn  where "nn" is the printer number set up in the JES2 INIT deck as a  page printer.  JES3 SET UP: To set up for printing under JES3, change the  printer settings, and start the printer using the following  commands:  *V jname ON  *S jname,WC=A  where "jname" is the printer name as specified in the JES3 INISH  deck.  Refer to the appropriate MVS/SP or MVS/ESA JES2 or JES3 Commands  publication for additional information about the JES commands to  use when starting a printer.  3. Check the result. The expected result of the IVP is a frame with  the letters IBM placed at an angle in the left corner of the  frame, the words Print Services Facility in the middle of the  frame, and the words Advanced Function Printing rotated 90 degrees  at the bottom of the frame. Refer to Print Services Facility/MVS:  System Programming Guide for an example of the IVP frame.   7.1.2.2 IVP JOB FOR DIRECT-ATTACH ENVIRONMENT  Perform the following steps if PSF/MVS Version 2.2.0 will be used in a  direct-attach environment:  1. Set aside the printer in direct-attach mode. The printer cannot  be allocated to other applications on the system if it is running  in direct-attach mode.  2. Submit the APSIVPDA job shown in Figure 25 on page 76. This job  exists in the data set SYS1.SAMPLIB(APSIVPDA). The job produces a  listing of the member SYS1.PSEGLIB(IVP) for output on the printer.  If you plan to print on an IBM 3800, this job must be modified  according to the comments within the job.     Installation Verification Procedure 75 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSIVPDA JOB 'acct. #','name',MSGLEVEL=(1,1) |  | //STEP1 EXEC PGM=IEBGENER,REGION=750K |  | //* |  | //************************************************************ |  | //* THIS IVP IS DESIGNED TO VERIFY THAT PSF HAS BEEN * |  | //* INSTALLED CORRECTLY AND THAT YOUR INSTALLATION CAN * |  | //* USE A PRINTER IN DIRECT ATTACH MODE. * |  | //* * |  | //* NOTE: * |  | //* IF YOU PLAN ON RUNNING THIS IVP FOR A 3800 PRINTER, * |  | //* COMMENT OUT THE FIRST OCCURRENCES OF THE FOLLOWING * |  | //* STATEMENTS: * |  | //* 'MSGDS', 'FONT01', 'FORMDEF', 'PAGEDEF' AND 'OUTPUT1'. * |  | //* THEN UNCOMMENT THE SECOND OCCURRENCES OF THE SAME * |  | //* STATEMENTS. * |  | //************************************************************ |  | //* |  | //MSGDS OUTPUT FORMDEF=A10110 /* <-- SEE NOTE ABOVE */ |  | //*MSGDS OUTPUT FORMDEF=0101 /* <-- SEE NOTE ABOVE */ |  | //FONT01 DD DSN=SYS1.FONTLIBB, /* <-- SEE NOTE ABOVE */ |  | //*FONT01 DD DSN=SYS1.FONTLIB, /* <-- SEE NOTE ABOVE */ |  | // DISP=SHR /* SYSTEM FONTS */ |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */ |  | // DISP=SHR |  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM OVERLAYS */ |  | // DISP=SHR |  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */ |  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */ |  | // DISP=SHR |  | //* |  | //DAPRT1 CNTL |  | //DAPRT1 PRINTDEV FONTDD=*.FONT01, /* FONT LIBRARY DD */ |  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */ |  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */ |  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */ |  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */ |  | // MESSAGE=*.MSGDS, /* MSG DATA SET OUTPUT */ |  | // FORMDEF=A10110, /* <-- SEE NOTE ABOVE */ |  | //* FORMDEF=0101, /* <-- SEE NOTE ABOVE */ |  | // PAGEDEF=A06462, /* <-- SEE NOTE ABOVE */ |  | //* PAGEDEF=06080, /* <-- SEE NOTE ABOVE */ |  | // BUFNO=5, /* NO. WRITE DATA BUFFER*/ |  | // TRACE=NO, /* TRACE FLAG */ |  | // PIMSG=YES /* ACCUM. DATA SET MSGS */ |  | //DAPRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 25 (Part 1 of 2). APSIVPDA Job    Installation Verification Procedure 76 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //* |  | //SYSIN DD DUMMY |  | //SYSPRINT DD SYSOUT=A |  | //* |  | //OUTPUT1 OUTPUT FORMDEF=A10110 /* <-- SEE NOTE ABOVE */ |  | //*OUTPUT1 OUTPUT FORMDEF=0101 /* <-- SEE NOTE ABOVE */ |  | //* |  | //************************************************************ |  | //* NOTE: * |  | //* THE 'UNIT=' PARAMETER BELOW MUST BE UPDATED TO POINT TO * |  | //* THE ADDRESS OF THE PRINTER THAT YOU ARE GOING TO USE AS * |  | //* A DIRECT ATTACH PRINTER. * |  | //************************************************************ |  | //* |  | //SYSUT2 DD UNIT=nnn, /* <-- SEE NOTE ABOVE */ |  | // CNTL=*.DAPRT1, |  | // DCB=(RECFM=VBA,BLKSIZE=8509), |  | // OUTPUT=(*.OUTPUT1) |  | //SYSUT1 DD DSN=SYS1.PSEGLIB(IVP),DISP=SHR |  | /* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 25 (Part 2 of 2). APSIVPDA Job  3. Check the result. The expected result of the IVP is a frame with  the letters IBM placed at an angle in the left corner of the  frame, the words Print Services Facility in the middle of the  frame, and the words Advanced Function Printing rotated 90 degrees  at the bottom of the frame. Refer to Print Services Facility/MVS:  System Programming Guide for an example of the IVP frame.          Installation Verification Procedure 77 ¤   APPENDIX A. SMP/E INSTALL LOGIC    The install logic for PSF/MVS Version 2.2.0 are listed in this  section.  If you ordered PSF/MVS Version 2.2.0 as an individual product (not in  CBIPO or CBPDO), then the SMP/E modification control statements for  the installation can be obtained by printing the first file of the  PSF/MVS Version 2.2.0 base product tape. The SMPMCS is included in  this section only for information purposes.   A.1 FMID HPRF220 SMPMCS  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | ++FUNCTION(HPRF220 ) FESN(0561046 ) REWORK(1996124 ) |  | RFDSNPFX(IBM ) FILES(10)  |  | /*********************************************************/ |  | /* */ |  | /* 5695-040 (C) COPYRIGHT IBM CORP. */ |  | /* 1984, 1994 */ |  | /* */ |  | /* 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 ) NPRE(EBB1102 ) |  | DELETE(HAF1103 HAF1203 HAF1220 HAF1228 HPRF102  |  | JAF1110 JAF1111 JAF1210 JAF1211 JAF1213  |  | JAF1218 JAF1222 JAF1223 JAF1224 JAF1225  |  | JAF1227 JAF1230 JAF1231 JAF1232 JAF1233  |  | JAF1235 J00M110 ) |  | SUP(AW01421 AW03243 AW03536 AW04104 AW04452 |  | AW05273 AW05579 AW06310 AW06321 AW06408 |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 26 (Part 1 of 3). FMID HPRF220 SMPMCS    (C) Copyright IBM Corp. 1983, 1996 78 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | AW06631 AW06775 AW06799 AW06943 AW06977 |  | AW06979 AW07305 AW07348 AW07359 AW07400 |  | AW07430 AW07446 AW07459 AW07536 AW07612 |  | AW07738 AW07806 AW07995 AW08022 AW08159 |  | AW08336 AW08338 AW08340 AW08438 AW08451 |  | AW08453 AW08593 AW08612 AW08623 AW08819 |  | AW08936 AW08944 AW08946 AW08956 AW08975 |  | AW08979 AW08999 AW09046 AW09054 AW09221 |  | AW09290 AW09445 AW09512 AW09625 AW09626 |  | AW09728 AW09854 AW09987 AW10066 AW10067 |  | AW10068 AW10071 AW10101 AW10239 AW10530 |  | AW10532 AW10550 AW10748 AW10787 AW10887 |  | AW10891 AW10903 AW10928 AW11235 AW11255 |  | AW11287 AW11773 AW11808 AW12021 AW12023 |  | AW12081 AW12092 AW12168 AW12274 AW12326 |  | AW12698 AW12700 AW12710 AW12811 AW12840 |  | AW12896 AW12903 AW12904 AW13045 AW13145 |  | AW13161 AW13171 AW13197 AW13242 AW13387 |  | AW13531 AW13627 AW13631 AW13702 AW13836 |  | AW13936 AW13965 AW14055 AW14056 AW14103 |  | AW14115 AW14128 AW14303 AW14307 AW14437 |  | AW14522 AW14552 AW14565 AW14708 AW14975 |  | AW15013 AW15018 AW15088 AW15113 AW15171 |  | AW15188 AW15599 AW15940 AW16007 AW16075 |  | AW16122 AW16209 AW16398 AW16407 AW16432 |  | AW16562 AW16589 AW16647 AW16789 AW16843 |  | AW16864 AW16914 AW16932 AW17026 AW17258 |  | AW17445 AW17446 AW17456 AW17525 AW17541 |  | AW17550 AW17564 AW17625 AW17669 AW17750 |  | AW17839 AW18088 AW18225 AW18369 AW18534 |  | AW18550 AW18551 AW18606 AW18619 AW18774 |  | AW19139 AW19288 AW19344 AW19765 AW19814 |  | AW19912 AW20126 HAF1103 HAF1203 HAF1220 |  | HAF1228 HPRF102 JAF1110 JAF1111 JAF1210 |  | JAF1211 JAF1213 JAF1218 JAF1222 JAF1223 |  | JAF1224 JAF1225 JAF1227 JAF1230 JAF1231 |  | JAF1232 JAF1233 JAF1235 J00M110 UW08938 |  | UW09094 UW09430 UW09686 UW09797 UW09923 |  | UW10030 UW10065 UW10089 UW10181 UW10192 |  | UW10401 UW10549 UW10698 UW10766 UW10805 |  | UW10909 UW10911 UW11022 UW11131 UW11285 |  | UW11415 UW11470 UW11603 UW11720 UW11817 |  | UW11886 UW11887 UW12180 UW12330 UW12331 |  | UW12478 UW12621 UW12675 UW12729 UW12732 |  | UW12785 UW12897 UW13010 UW13329 UW13460 |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 26 (Part 2 of 3). FMID HPRF220 SMPMCS    Appendix A. SMP/E Install Logic 79 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | UW13461 UW13689 UW13806 UW13973 UW14101 |  | UW14135 UW14560 UW14572 UW14806 UW14814 |  | UW14833 UW14857 UW15052 UW15054 UW15117 |  | UW15272 UW15328 UW15401 UW15446 UW15504 |  | UW15550 UW15755 UW15760 UW16061 UW16063 |  | UW16360 UW16420 UW16449 UW16483 UW16499 |  | UW16502 UW16556 UW17075 UW17259 UW17306 |  | UW17402 UW17679 UW17799 UW17802 UW17942 |  | UW18068 UW18070 UW18071 UW18072 UW18208 |  | UW18226 UW18264 UW18313 UW18588 UW18648 |  | UW18905 UW19044 UW19121 UW19134 UW19202 |  | UW19390 UW19428 UW19599 UW19696 UW19697 |  | UW19699 UW19866 UW20001 UW20021 UW20040 |  | UW20159 UW20201 UW20250 UW20252 UW20318 |  | UW20567 UW20941 UW21042 UW21095 UW21121 |  | UW21345 UW21369 UW21459 UW21461 UW21466 |  | UW22030 UW22331 UW22554 UW22555 UW22557 |  | UW22696 UW23081 UW23083 UW23275 UW23722 |  | UW23840 UW23864 UW24162 UW24201 UW24258 |  | UW24273 UW24303 UW24430 UW24446 UW24450 |  | UW24497 UW24604 UW24616 UW24677 UW24725 |  | UW24747 UW24899 UW24971 UW25033 UW25143 |  | UW25289 UW25414 UW26050 UW26051 UW26166 |  | UW26263 UW26483 UW26527 UW26603 UW26752 |  | UW26952 UW26975 UW27158 UW27333 UW27810 |  | UW27811 UW27813 UW27864 UW27934 UW28082 |  | UW28279 ) . |  | ++IF FMID(JBB2220 ) |  | REQ(UY02712 UY14981 UY34536 UY90121 ) . |  | ++IF FMID(HJS2220 ) REQ(UY90124 ) . |  | ++IF FMID(HJE2221 ) REQ(UY90118 ) . |  | ++JCLIN RELFILE(1) . |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 26 (Part 3 of 3). FMID HPRF220 SMPMCS        Appendix A. SMP/E Install Logic 80 ¤   A.2 FMID JPRF223 SMPMCS  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | ++FUNCTION(JPRF223 ) FESN(0561046 ) REWORK(1996124 ) |  | RFDSNPFX(IBM ) FILES(4)|  | /*********************************************************/ |  | /* */ |  | /* 5695-040 (C) COPYRIGHT IBM CORP. */ |  | /* 1984, 1994 */ |  | /* */ |  | /* 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 ) FMID(HPRF220 ) |  | DELETE(JAF1226 JAF1234 JPRF113 ) |  | SUP(AW10498 AW14505 JAF1226 JAF1234 JPRF113 |  | UW14253 UW20320 ) . |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 27. FMID JPRF223 SMPMCS           Appendix A. SMP/E Install Logic 81 ¤   A.3 PSF/MVS VERSION 2.2.0 JCLIN  The JCLIN for PSF/MVS Version 2.2.0 is contained on the installation  tape in file "IBM.HPRF220.F1" member "HPRF220". This file will be  loaded to disk by SMP/E when PSF/MVS Version 2.2.0 is SMP/E RECEIVEd.  You may browse or print the JCLIN file using TSO/E, ISPF, or IEBGENER.  NOTE: JPRF223 has no JCLIN.                  Appendix A. SMP/E Install Logic 82 ¤                      Appendix A. SMP/E Install Logic 83 ¤   APPENDIX B. STARTUP PROCEDURES FOR PSF/MVS VERSION 2.2.0    B.1 STARTUP PROCEDURE APSWPROA  The sample startup procedure in Figure 28 on page 85 is for the  following channel-attadhed printers:  ù 3160 - if configured as a channel attached printer  ù 3825  ù 3827  ù 3828  ù 3829  ù 3831  ù 3835  ù 3900  ù 3935 - if configured as a channel attached printer  This procedure is placed in your PROCLIB as member APSWPROA during the  installation of PSF/MVS Version 2.2.0. Only a minimum set of options  are specified in this sample startup procedure. Refer to the section  entitled "PSF Startup Procedures for AFP Printers" in Print Services  Facility/MVS: System Programming Guide for further information on  available options and their functions.  The data sets referred to in this sample startup procedure have the  high-level qualifier of SYS1. If a different high-level qualifier is  used, the names in the procedure must be changed accordingly.  If the resources at your installation are consolidated into one font  library, modify this procedure to refer to the one font library.  ÚÄÄÄ NOTE ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | THE FONT01 DD STATEMENT IN THE APSWPROA PROCEDURE REFERENCES THE |  | DATA SET(S) THAT CONTAINS THE DEFAULT FONTS LISTED IN THE |  | PRINTDEV. FOR THE 3935 PRINTER, THE FONT01 DD STATEMENT MUST |  | REFERENCE THE DATA SET CONTAINING THE 300-PEL FONTS. EITHER |  | 300-PEL FONTS MUST BE INSTALLED, OR THE 240-PEL FONTS MUST BE |  | CONVERTED USING THE FONT CONVERSION UTILITY APSRCF30. Refer to |  | the PSF/MVS System Programming Guide or the PSF/MVS Application |  | Programming Guide for additional information. |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ     (C) Copyright IBM Corp. 1983, 1996 84 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWPROA PROC |  | //**************** THE PSF WRITER PROCEDURE ****************** |  | //* |  | //*01* MODULE-NAME = APSWPROA |  | //* $MOD(APSWPROA) COMP(APS) PROD(PSF) : RELEASE 2.2.0 @H7C|  | //* |  | //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR PSF: |  | //* |  | //* 3825 |  | //* 3827 |  | //* 3828 |  | //* 3829 |  | //* 3831 |  | //* 3835 |  | //* 3900 |  | //* 3935 - IF CONFIGURED |  | //* AS A CHANNEL ATTACHED |  | //* PRINTER |  | //* |  | //* |  | //*01* STATUS = VERSION 2, RELEASE 2, LEVEL 0 @H7C|  | //* |  | //*01* FUNCTION = THIS PROCEDURE IS COPIED FROM THE |  | //* DISTRIBUTION TO SYS1.PROCLIB. THE 'COPY' IS |  | //* PERFORMED BY MACRO 'SGAPS5PR'. |  | //* |  | //*01* NOTES = THE FULL NAME OF THE DEFAULT PAGEDEF IS |  | //* P1A06462. |  | //* THE FULL NAME OF THE DEFAULT FORMDEF IS |  | //* F1A10110. |  | //* THE FULL NAMES OF THE DEFAULT FONTS ARE |  | //* X0GF10, X0GS10, X0TU10, AND X0GU10. |  | //* THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS |  | //* P1V06483. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FONT IS |  | //* X0GT15. |  | //* |  | //* IF THE PRINTER IS A 300 PEL FONT PRINTER (A @01A|  | //* 3935 FOR EXAMPLE), @01A|  | //* THE FIRST FONT01 DD STATEMENT BELOW @01A|  | //* MUST BE COMMENTED OUT AND THE SECOND FONT01 @01A|  | //* DD MUST BE UNCOMMENTED. @01A|  | //* THE FONT01 DATA SET MUST CONTAIN THE CONVERTED@01A|  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 28 (Part 1 of 3). APSWPROA Job     Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 85 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //* DEFAULT FONTS LISTED IN THE PRINTDEV. @01A|  | //* THE FONTS ARE CONVERTED USING THE FONT @01A|  | //* CONVERSION UTILITY APSRCF30. SEE THE PSF @01A|  | //* SYSTEM PROGRAMMING GUIDE OR THE PSF @01A|  | //* APPLICATION PROGRAMMING GUIDE @01A|  | //* |  | //*01* CHANGE-ACTIVITY : @L1C|  | //* $H1=LAPS0001, HAF1103, 110984 TD4 : RELEASE 1.1 @L1A|  | //* $H2=LAPS0002, HAF1203, 022586 BJ13RK : RELEASE 2.0 @L1A|  | //* $H3=LAPS0003, HAF1220, 081787 B53KJG : RELEASE 2.1 @L1A|  | //* $L1=LAPS0004, HAF1228, 011389 B53KJG : RELEASE 3.0 @L1A|  | //* $H7=LAPS0005, HPRF102, 071990 B53KDAR : REL 2.1.0 NEW FNC@H7A|  | //* $01=OW80593, HPRF220, 020995 J13JAU : REL 2.2.0 @01A|  | //* |  | //**** END OF SPECIFICATIONS ***/ |  | //STEP01 EXEC PGM=APSPPIEP,REGION=4096K |  | //JOBHDR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDF@H3C*/|  | //JOBTLR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDF@H3C*/|  | //DSHDR OUTPUT PAGEDEF=V06483, /* DATA SET SEPARATOR */|  | //* /* PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* DATASET SEPARATOR */|  | //* /* FORMDEF @H3C*/|  | //MSGDS OUTPUT PAGEDEF=A06462, /* MESSAGE DATASET PAGEDEF */|  | // FORMDEF=A10110 /* MESSAGE DATASET FMDEFH3C*/|  | //FONT01 DD DSN=SYS1.FONTLIBB, /* SYSTEM FONTS */|  | //* ****************************************************** @01A*/|  | //* TO USE THE FOLLOWING FONT SET, THE FONTS MUST @01A*/|  | //* FIRST BE CONVERTED AND IN THE 300 PEL FONT LIBRARY, @01A*/|  | //* SEE NOTES @01A*/|  | //* ****************************************************** @01A*/|  | //*FONT01 DD DSN=SYS1.FONT300, /* SYSTEM FONTS,300 PEL@01A*/|  | // DISP=SHR |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */|  | // DISP=SHR /* @H3C*/|  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM OVERLAYS @H3C*/|  | // DISP=SHR /* @H3C*/|  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */|  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */|  | // DISP=SHR |  | //PRT1 CNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 28 (Part 2 of 3). APSWPROA Job     Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 86 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //PRT1 PRINTDEV FONTDD=*.FONT01, /* FONT LIBRARY DD */|  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */|  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */|  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */|  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */|  | // JOBHDR=*.JOBHDR, /* JOB HEADER SEPARATOR */|  | //* /* OUTPUT */|  | // JOBTRLR=*.JOBTLR, /* JOB TRAILER SEPARATOR */|  | //* /* OUTPUT */|  | // DSHDR=*.DSHDR, /* DATA SET HEADER */|  | //* /* SEPARATOR */|  | // MESSAGE=*.MSGDS, /* MESSAGE DATA SET OUTPUT*/|  | // BUFNO=5, /* NUMBER OF WRITE DATA */|  | //* /* BUFFERS */|  | // PAGEDEF=A06462, /* DEVICE PAGEDEF DEFAULT */|  | // FORMDEF=A10110, /* DEVICE FRMDF DFAULT@H3C*/|  | // CHARS=(GF10, /* DEVICE */|  | // GS10,TU10,GU10), /* DEFAULT FONT SET @H3C*/|  | // PIMSG=YES, /* ACCUMULATE DATA SET */|  | //* /* MESSAGES */|  | // DATACK=UNBLOCK, /* UNBLOCK DATA CHECKS */|  | // TRACE=NO /* BUILD INTERNAL TRCE@H3C*/|  | //PRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 28 (Part 3 of 3). APSWPROA Job           Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 87 ¤   B.2 STARTUP PROCEDURE APSWPROB  The sample startup procedure in Figure 29 on page 89 is for the  following SNA-attached printers using 300-pel fonts:  ù 3112  ù 3116  ù 3130 - if configured as an SNA-attached printer  ù 3912  ù 3916  ù 3935 - if configured as an SNA-attached printer  ù LaserPrinter 4019  ù LaserPrinter 4028  ù LaserPrinter 4029  ù LaserPrinter 4039  This procedure is placed in your PROCLIB as member APSWPROB during the  installation of PSF/MVS Version 2.2.0. Only a minimum set of options  are specified in this sample startup procedure. Refer to the section  entitled "PSF Startup Procedures for AFP Printers" in Print Services  Facility/MVS: System Programming Guide for further information on  available options and their functions.  The data sets referred to in this sample startup procedure have the  high-level qualifier of SYS1. If a different high-level qualifier is  used, the names in the procedure must be changed accordingly.  If the resources at your installation are consolidated into one font  library, modify this procedure to refer to the one font library.  ÚÄÄÄ NOTE ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | THE FONT01 DD STATEMENT IN THE APSWPROB PROCEDURE REFERENCES THE |  | DATA SET(S) THAT CONTAINS THE DEFAULT FONTS LISTED IN THE |  | PRINTDEV. THE FONT01 DATA SET MUST REFERENCE THE DATA SET |  | CONTAINING THE 300-PEL FONTS. EITHER 300-PEL FONTS MUST BE |  | INSTALLED, OR THE 240-PEL FONTS MUST BE CONVERTED USING THE FONT |  | CONVERSION UTILITY APSRCF30. Refer to the PSF/MVS System |  | Programming Guide or the PSF/MVS Application Programming Guide for |  | additional information. |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ       Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 88 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWPROB PROC |  | //**************** THE PSF SNA WRITER PROCEDURE *************** |  | //* |  | //*01* MODULE-NAME = APSWPROB |  | //* $MOD(APSWPROB) COMP(APS) PROD(PSF) : RELEASE 2.2.0 |  | //* |  | //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR PSF: |  | //* |  | //* 3912 |  | //* 3916 |  | //* 3935 - IF CONFIGURED |  | //* AS AN SNA-ATTACHED PRINTER|  | //* LaserPrinter 4019 |  | //* LaserPrinter 4028 |  | //* LaserPrinter 4029 |  | //* LaserPrinter 4039 |  | //* |  | //*01* STATUS = VERSION 2, RELEASE 2, LEVEL 0 |  | //* |  | //*01* FUNCTION = THIS PROCEDURE IS COPIED FROM THE |  | //* DISTRIBUTION |  | //* LIBRARY TO SYS1.PROCLIB. THIS COPY |  | //* IS PERFORMED BY MACRO 'SGAPS5PR'. |  | //* |  | //*01* NOTES = THE FULL NAME OF THE DEFAULT PAGEDEF IS |  | //* P1A06462. |  | //* THE FULL NAME OF THE DEFAULT FORMDEF IS |  | //* F1A10110. |  | //* |  | //* THE FULL NAMES OF THE DEFAULT FONTS ARE |  | //* X0GF10, X0GS10, X0TU10, AND |  | //* X0GU10. |  | //* |  | //* THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS |  | //* P1V06483. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FONT IS |  | //* X0GT15. |  | //* |  | //* THE FONT01 DD STATEMENT BELOW |  | //* REFERENCES THE DATA SET(S) |  | //* THAT CONTAINS THE 300 PEL FONTS. |  | //* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 29 (Part 1 of 3). APSWPROB Job     Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 89 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //* THE FONT01 DATA SET MUST CONTAIN THE CONVERTED |  | //* DEFAULT FONTS LISTED IN THE PRINTDEV. |  | //* THE FONTS ARE CONVERTED USING THE FONT |  | //* CONVERSION UTILITY APSRCF30. SEE THE PSF |  | //* SYSTEM PROGRAMMING GUIDE OR THE PSF |  | //* APPLICATION PROGRAMMING GUIDE |  | //* |  | //*01* CHANGE-ACTIVITY : |  | //* $00=LAPS0005, HPRF102, 120390 B53KJAU : INITIAL VERSION @00A|  | //* |  | //**** END OF SPECIFICATIONS ***/ |  | //* |  | //STEP01 EXEC PGM=APSPPIEP,REGION=1750K |  | //JOBHDR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDEF */|  | //JOBTLR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDEF */|  | //DSHDR OUTPUT PAGEDEF=V06483, /* DS SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* DS SEPARATOR FORMDEF */|  | //MSGDS OUTPUT PAGEDEF=A06462, /* MESSAGE DATASET PAGEDEF */|  | // FORMDEF=A10110 /* MESSAGE DATASET FORMDEF */|  | //FONT01 DD DSN=SYS1.FONT300, /* 300 PEL FONT LIBRARY */|  | // DISP=SHR |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */|  | // DISP=SHR |  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM MEDIUM OVERLAYS */|  | // DISP=SHR /* */|  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */|  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */|  | // DISP=SHR |  | //* ************************************************************/|  | //* PRINTDEV */|  | //* ************************************************************/|  | //PRT1 CNTL |  | //PRT1 PRINTDEV FONTDD=*.FONT01, /* FONT LIBRARY DD */|  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */|  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */|  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */|  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */|  | // JOBHDR=*.JOBHDR, /* JOB HEADER SEPARATOR */|  | //* /* OUTPUT */|  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 29 (Part 2 of 3). APSWPROB Job     Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 90 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | // JOBTRLR=*.JOBTLR, /* JOB TRAILER SEPARATOR */|  | //* /* OUTPUT */|  | // DSHDR=*.DSHDR, /* DATA SET HEADER */|  | //* /* SEPARATOR */|  | // MESSAGE=*.MSGDS, /* MESSAGE DATA SET OUTPUT*/|  | // PAGEDEF=A06462, /* DEVICE PAGEDEF DEFAULT */|  | // FORMDEF=A10110, /* DEVICE FORMDEF DEFAULT */|  | //* ************************************************************/|  | //* TO USE THE FOLLOWING DEFAULT FONT SET, THE FONTS MUST */|  | //* FIRST BE CONVERTED AND IN THE 300 PEL FONT LIBRARY, SEE */|  | //* NOTES */|  | //* ************************************************************/|  | // CHARS=(GF10, /* DEVICE */|  | // GS10,TU10,GU10), /* DEFAULT FONT SET */|  | // PIMSG=YES, /* ACCUMULATE DATA SET */|  | //* /* MESSAGES */|  | // DATACK=UNBLOCK, /* REPORT ALL DATA-CHECK */|  | //* /* ERRORS */|  | // TRACE=NO, /* CREATE INTERNAL TRACE */|  | // FAILURE=WCONNECT, /* PSF ACTION ON PRINTER */|  | //* /* FAILURE */|  | // TIMEOUT=REDRIVE, /* PSF ACTION ON TIMEOUT */|  | // DISCINTV=1800, /*DISCONNECT INTERVAL IN */|  | //* /* SECONDS */|  | // APPLID=xxxxxxxx, /*VTAM APPLICATION PGM */|  | //* /* NODE NAME */|  | // LOGMODE=xxxxxxxx, /*VTAM LOGON MODE TABLE */|  | //* /* ENTRY */|  | // MGMTMODE=OUTAVAIL, /*PRINTER MANAGEMENT MODE */|  | // LUNAME=xxxxxxxx /* VTAM LOGICAL UNIT NAME */|  | //PRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 29 (Part 3 of 3). APSWPROB Job         Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 91 ¤   B.3 STARTUP PROCEDURE APSWPROC  The sample startup procedure in Figure 30 is for the IBM 3800. This  procedure is placed in your PROCLIB as member APSWPROC during the  installation of PSF/MVS Version 2.2.0. Only a minimum set of options  are specified in this sample startup procedure. Refer to the section  describing PSF startup procedures for AFP printers in Print Services  Facility/MVS: System Programming Guide for further information on  available options and their functions.  The data sets referred to in this sample startup procedure have the  high-level qualifier of SYS1. If a different high-level qualifier is  used, the names in the procedure must be changed accordingly.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWPROC PROC |  | //**************** THE PSF WRITER PROCEDURE ****************** |  | //* |  | //*01* MODULE-NAME = APSWPROC |  | //* $MOD(APSWPROC) COMP(APS) PROD(PSF) : RELEASE 2.2.0 @H7C|  | //* |  | //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR PSF (3800 |  | //* PRINTERS) |  | //* |  | //*01* STATUS = VERSION 2, RELEASE 2, LEVEL 0 @H7C|  | //* |  | //*01* FUNCTION = THIS PROCEDURE IS COPIED FROM THE |  | //* DISTRIBUTION TO SYS1.PROCLIB. THE 'COPY' IS |  | //* PERFORMED BY MACRO 'SGAPS5PR'. |  | //* |  | //*01* NOTES = THE FULL NAME OF THE DEFAULT PAGEDEF IS P106080. |  | //* THE FULL NAME OF THE DEFAULT FORMDEF IS F10101. |  | //* THE FULL NAMES OF THE DEFAULT FONTS ARE |  | //* X1GF12, X1GS12, X1GT12, AND X1GU12. |  | //* THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS |  | //* P18. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FONT IS |  | //* X1GT15. |  | //* |  | //*01* CHANGE-ACTIVITY : @L1C|  | //* $H1=LAPS0001, HAF1103, 110984 TD4 : RELEASE 1.1 @L1A|  | //* $H2=LAPS0002, HAF1203, 022586 BJ13RK : RELEASE 2.0 @L1A|  | //* $H3=LAPS0003, HAF1220, 081787 B53KJG : RELEASE 2.1 @L1A|  | //* $L1=LAPS0004, HAF1228, 011389 B53KJG : RELEASE 3.0 @L1A|  | //* $H7=LAPS0005, HPRF102, 071990 B53KDAR : REL 2.1.0 NEW F @H7A|  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 30 (Part 1 of 2). APSWPROC Job    Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 92 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //* |  | //**** END OF SPECIFICATIONS ***/ |  | //STEP01 EXEC PGM=APSPPIEP,REGION=1750K |  | //JOBHDR OUTPUT PAGEDEF=8, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=0101,CHARS=GT15 /* JOB SEPARATOR FORMDEF */|  | //JOBTLR OUTPUT PAGEDEF=8, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=0101,CHARS=GT15 /* JOB SEPARATOR FORMDEF */|  | //DSHDR OUTPUT PAGEDEF=8, /* DS SEPARATOR PAGEDEF */|  | // FORMDEF=0101,CHARS=GT15 /* DS SEPARATOR FORMDEF */|  | //MSGDS OUTPUT PAGEDEF=8, /* MESSAGE DATASET PAGEDEF */|  | // FORMDEF=0101,CHARS=GT15 /* MESSAGE DATASET FORMDEF */|  | //FONT01 DD DSN=SYS1.FONTLIB, /* SYSTEM FONTS */|  | // DISP=SHR |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */|  | // DISP=SHR |  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM MED OVERLAYS @H3C*/|  | // DISP=SHR /* @H3C*/|  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */|  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */|  | // DISP=SHR |  | //PRT1 CNTL |  | //PRT1 PRINTDEV FONTDD=*.FONT01, /* FONT LIBRARY DD */|  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */|  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */|  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */|  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */|  | // JOBHDR=*.JOBHDR, /* JOB HEADER SEPARATOR */|  | //* /* OUTPUT */|  | // JOBTRLR=*.JOBTLR, /* JOB TRAILER SEPARATOR */|  | //* /* OUTPUT */|  | // DSHDR=*.DSHDR, /* DATA SET HEADER */|  | //* /* SEPARATOR */|  | // MESSAGE=*.MSGDS, /* MESSAGE DATA SET OUTPUT*/|  | // BUFNO=5, /* NUMBER OF WRITE DATA */|  | //* /* BUFFERS */|  | // PAGEDEF=06080, /* DEVICE PAGEDEF DEFAULT */|  | // FORMDEF=0101, /* DEVICE FORMDEF DEFAULT */|  | // CHARS=(GF12, /* DEVICE @H1C*/|  | // GS12,GT12,GU12), /* DEFAULT FONT SET @H1C*/|  | // PIMSG=YES, /* ACCUMULATE DATA SET */|  | //* /* MESSAGES */|  | // DATACK=UNBLOCK, /* REPORT DATA-CHECK @H7A*/|  | //* /* ERRORS */|  | // TRACE=NO /* BUILD INTRNL TRACE @H3C*/|  | //PRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 30 (Part 2 of 2). APSWPROC Job    Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 93 ¤   B.4 STARTUP PROCEDURE APSWPROD  The sample startup procedure in Figure 31 on page 95 is for the  following SNA-attached printers that support resident symbol sets:  ù 4224  ù 4230  ù 4234  ù 6400  This procedure is placed in your PROCLIB as member APSWPROD during the  installation of PSF/MVS Version 2.2.0. Only a minimum set of options  are specified in this sample startup procedure. Refer to the section  entitled "PSF Startup Procedures for AFP Printers" in Print Services  Facility/MVS: System Programming Guide for further information on  available options and their functions.  The data sets referred to in this sample startup procedure have the  high-level qualifier of SYS1. If a different high-level qualifier is  used, the names in the procedure must be changed accordingly.  If the resources at your installation are consolidated into one font  library, modify this procedure to refer to the one font library.             Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 94 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWPROD PROC |  | //**************** THE PSF SNA WRITER PROCEDURE *************** |  | //* |  | //*01* MODULE-NAME = APSWPROD |  | //* $MOD(APSWPROD) COMP(APS) PROD(PSF) : RELEASE 2.2.0 |  | //* |  | //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR PSF: |  | //* |  | //* 4224 |  | //* 4230 |  | //* 4234 |  | //* 6408 |  | //* 6412 |  | //* |  | //*01* STATUS = VERSION 2, RELEASE 2, LEVEL 0 |  | //* |  | //*01* FUNCTION = THIS PROCEDURE IS COPIED FROM THE |  | //* DISTRIBUTION |  | //* LIBRARY TO SYS1.PROCLIB. THIS COPY |  | //* IS PERFORMED BY MACRO 'SGAPS5PR'. |  | //* |  | //*01* NOTES = THE FULL NAME OF THE DEFAULT PAGEDEF IS |  | //* P1A06462. |  | //* THE FULL NAME OF THE DEFAULT FORMDEF IS |  | //* F1A10110. |  | //* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 31 (Part 1 of 3). APSWPROD Job          Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 95 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //* THE FULL NAMES OF THE DEFAULT FONTS ARE |  | //* X0GT10, X0GT12, X0GB10, AND |  | //* X0GB12. |  | //* |  | //* THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS |  | //* P1V06483. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FONT IS |  | //* X0GT15. |  | //* |  | //* TO USE THE FONTS CALLED FOR BELOW, THE DEFAULT |  | //* PRINT QUALITY OF THE PRINTER NEEDS TO BE SET |  | //* PROPERLY TO AVOID FONT ERROR MESSAGES AT PRINT |  | //* TIME. SEE THE PRINTER INFORMATION MANUAL AND |  | //* THE SELECTED PRINTER OPERATOR'S MANUAL FOR |  | //* MORE INFORMATION. |  | //* |  | //* |  | //*01* CHANGE-ACTIVITY : |  | //* $00=LAPS0005, HPRF102, 071990 B53KJAU : INITIAL VERSION @00A|  | //* |  | //**** END OF SPECIFICATIONS ***/ |  | //* |  | //STEP01 EXEC PGM=APSPPIEP,REGION=1750K |  | //JOBHDR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDEF */|  | //JOBTLR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDEF */|  | //DSHDR OUTPUT PAGEDEF=V06483, /* DS SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* DS SEPARATOR FORMDEF */|  | //MSGDS OUTPUT PAGEDEF=A06462, /* MESSAGE DATASET PAGEDEF */|  | // FORMDEF=A10110 /* MESSAGE DATASET FORMDEF */|  | //FONT01 DD DSN=SYS1.FONTLIBB, /* SYSTEM FONTS */|  | // DISP=SHR |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */|  | // DISP=SHR |  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM MEDIUM OVERLAYS */|  | // DISP=SHR /* */|  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */|  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */|  | // DISP=SHR |  | //* ************************************************************/|  | //* PRINTDEV */|  | //* ************************************************************/|  | //PRT1 CNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 31 (Part 2 of 3). APSWPROD Job    Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 96 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //PRT1 PRINTDEV FONTDD=*.FONT01, /* FONT LIBRARY DD */|  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */|  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */|  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */|  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */|  | // JOBHDR=*.JOBHDR, /* JOB HEADER SEPARATOR */|  | //* /* OUTPUT */|  | // JOBTRLR=*.JOBTLR, /* JOB TRAILER SEPARATOR */|  | //* /* OUTPUT */|  | // DSHDR=*.DSHDR, /* DATA SET HEADER */|  | //* /* SEPARATOR */|  | // MESSAGE=*.MSGDS, /* MESSAGE DATA SET OUTPUT*/|  | // PAGEDEF=A06462, /* DEVICE PAGEDEF DEFAULT */|  | // FORMDEF=A10110, /* DEVICE FORMDEF DEFAULT */|  | //* ********************************************************** */|  | //* TO USE THE FONTS CALLED FOR BELOW, THE DEFAULT PRINT */|  | //* QUALITY OF THE PRINTER NEEDS TO BE SET PROPERLY TO AVOID */|  | //* FONT ERROR MESSAGES AT PRINT TIME. SEE THE PRINTER */|  | //* INFORMATION MANUAL AND THE SELECTED PRINTER OPERATOR'S */|  | //* MANUAL FOR MORE INFORMATION. */|  | //* ********************************************************** */|  | // CHARS=(GT10, /* DEVICE */|  | // GT12,GB10,GB12), /* DEFAULT FONT SET */|  | // PIMSG=YES, /* ACCUMULATE DATA SET */|  | //* /* MESSAGES */|  | // DATACK=UNBLOCK, /* REPORT ALL DATA-CHECK */|  | //* /* ERRORS */|  | // TRACE=NO, /* CREATE INTERNAL TRACE */|  | // FAILURE=WCONNECT, /* PSF ACTION ON PRINTER */|  | //* /* FAILURE */|  | // TIMEOUT=REDRIVE, /* PSF ACTION ON TIMEOUT */|  | // DISCINTV=1800, /*DISCONNECT INTERVAL IN */|  | //* /* SECONDS */|  | // APPLID=xxxxxxxx, /*VTAM APPLICATION PGM */|  | //* /* NODE NAME */|  | // LOGMODE=xxxxxxxx, /*VTAM LOGON MODE TABLE */|  | //* /* ENTRY */|  | // MGMTMODE=OUTAVAIL, /*PRINTER MANAGEMENT MODE */|  | // LUNAME=xxxxxxxx /* VTAM LOGICAL UNIT NAME */|  | //PRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 31 (Part 3 of 3). APSWPROD Job      Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 97 ¤   B.5 STARTUP PROCEDURE APSWPROM  The sample startup procedure in Figure 32 on page 99 is for microfilm  devices. This procedure is placed in your PROCLIB as member APSWPROM  during the installation of PSF/MVS Version 2.2.0. Only a minimum set  of options are specified in this sample startup procedure. Refer to  the section entitled "PSF Startup Procedures for AFP Printers" in  Print Services Facility/MVS: System Programming Guide for further  information on available options and their functions.  The data sets referred to in this sample startup procedure have the  high-level qualifier of SYS1. If a different high-level qualifier is  used, the names in the procedure must be changed accordingly.  If the resources at your installation are consolidated into one font  library, modify this procedure to refer to the one font library.               Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 98 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWPROM PROC |  | //**************** THE PSF WRITER PROCEDURE ****************** |  | //* |  | //*01* MODULE-NAME = APSWPROM |  | //* $MOD(APSWPROM) COMP(APS) PROD(PSF) : RELEASE 2.2.0 |  | //* |  | //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR MICROFILM |  | //* DEVICES |  | //* |  | //*01* STATUS = VERSION 2, RELEASE 2, LEVEL 0 |  | //* |  | //*01* FUNCTION = THIS PROCEDURE IS COPIED FROM THE |  | //* DISTRIBUTION TO SYS1.PROCLIB. THE 'COPY' IS |  | //* PERFORMED BY MACRO 'SGAPS5PR'. |  | //* |  | //*01* NOTES = THE FULL NAME OF THE DEFAULT PAGEDEF IS |  | //* P1A06462. |  | //* THE FULL NAME OF THE DEFAULT FORMDEF IS |  | //* F1A10110. |  | //* THE FULL NAMES OF THE DEFAULT FONTS ARE |  | //* X0GF10, X0GS10, X0TU10, AND X0GU10. |  | //* THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS |  | //* P1V06483. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FONT IS |  | //* X0GT15. |  | //* |  | //*01* REQUIRED ACTIONS = |  | //* 1) DEFAULT COMSETUP-DEFAULT COMSETUP FILES ARE SPECIFIED|  | //* IN THIS START PROCEDURE BUT ARE NOT PROVIDED WITH |  | //* PSF/MVS. DEFAULT COMSETUP FILES MUST BE GENERATED |  | //* WITH SOFTWARE PROVIDED WITH YOUR AFP/COM DEVICE AND|  | //* PLACED IN THE DATASET SPECIFIED ON THE OBJCON01 DD |  | //* IN THIS START PROCEDURE. |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 32 (Part 1 of 3). APSWPROM Job        Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 99 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //* |  | //* THE FULL NAME OF THE DEFAULT COMSETUP IS H1SETUPD.|  | //* THE FULL NAME OF THE SEPARATOR PAGE COMSETUP IS |  | //* H1SETUPS. |  | //* |  | //* 2) RESOLUTION-THIS START PROCEDURE IS SET UP FOR DRIVING|  | //* THE AFP/COM DEVICE AT 240 PEL RESOLUTION. TO CHANGE|  | //* IT TO DRIVE 300 PEL RESOLUTION AFP/COM DEVICES: |  | //* A) COMMENT OUT THE FIRST PRINTDEV STATEMENT AND |  | //* UNCOMMENT THE SECOND PRINTDEV STATEMENT. |  | //* B) THE FONT02 DATA SET MUST CONTAIN THE CONVERTED |  | //* DEFAULT FONTS LISTED IN THE PRINTDEV. |  | //* THE FONTS ARE CONVERTED USING THE FONT |  | //* CONVERSION UTILITY APSRCF30. SEE THE PSF |  | //* SYSTEM PROGRAMMING GUIDE. |  | //* |  | //*01* CHANGE-ACTIVITY : |  | //* $00=OW10067, HPRF220, 102494 BJ13JPG : AFP/COM SUPPORT |  | //* |  | //**** END OF SPECIFICATIONS ***/ |  | //STEP01 EXEC PGM=APSPPIEP,REGION=4096K |  | //JOBHDR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15, /* JOB SEPARATOR FORMDEF */|  | // COMSETUP=H1SETUPS /* JOB SEPARATOR COMSETUP */|  | //JOBTLR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15, /* JOB SEPARATOR FORMDEF */|  | // COMSETUP=H1SETUPS /* JOB SEPARATOR COMSETUP */ |  | //DSHDR OUTPUT PAGEDEF=V06483, /* DATA SET SEPARATOR PAGEDEF*/|  | // FORMDEF=A10110,CHARS=GT15,/* DATA SET SEPARATOR FRMDEF*/|  | // COMSETUP=H1SETUPS /* DATA SET SEPARATOR COMSETUP*/|  | //MSGDS OUTPUT PAGEDEF=A06462, /* MESSAGE DATASET PAGEDEF */|  | // FORMDEF=A10110, /* MESSAGE DATASET FORMDEF */|  | // PIMSG=NO,CLASS=A /* SEND MSG DATASET TO CLASS A*/|  | //FONT01 DD DSN=SYS1.FONTLIBB, /* SYSTEM FONTS - 240 PEL */|  | // DISP=SHR |  | //FONT02 DD DSN=SYS1.FONT300, /* SYSTEM FONTS - 300 PEL */|  | // DISP=SHR |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */|  | // DISP=SHR |  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM OVERLAYS */|  | // DISP=SHR |  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */|  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */|  | // DISP=SHR |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 32 (Part 2 of 3). APSWPROM Job    Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 100 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //OBJCON01 DD DSN=SYS1.APSOCLIB, /* SYSTEM OBJECT CONTAINERS*/|  | // DISP=SHR /* */|  | //PRT1 CNTL |  | //PRT1 PRINTDEV FONTDD=*.FONT01, /* 240 PEL FONT LIBRARY DD*/|  | //* /* <-- SEE REQUIRED ACTIONS*/|  | //* /* ABOVE */|  | //*PRT1 PRINTDEV FONTDD=*.FONT02,/* 300 PEL FONT LIBRARY DD*/|  | //* /* <-- SEE REQUIRED ACTIONS*/|  | //* /* ABOVE */|  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */|  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */|  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */|  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */|  | // OBJCONDD=*.OBJCON01, /* OBJECT LIBRARY DD */|  | // JOBHDR=*.JOBHDR, /* JOB HEADER SEPARATOR OUTPUT */|  | // JOBTRLR=*.JOBTLR, /* JOB TRAILER SEPARATOR OUTPUT*/|  | // DSHDR=*.DSHDR, /* DATA SET HEADER OUTPUT */|  | // MESSAGE=*.MSGDS, /* MESSAGE DATA SET OUTPUT */|  | // BUFNO=5, /* NUMBER OF WRITE DATA BUFFERS*/|  | // PAGEDEF=A06462, /* DEVICE PAGEDEF DEFAULT */|  | // FORMDEF=A10110, /* DEVICE FORMDEF DEFAULT */|  | // COMSETUP=H1SETUPD, /* DEFAULT COMSETUP MEMBER */|  | // CHARS=(GF10, /* DEVICE */|  | // GS10,TU10,GU10), /* DEFAULT FONT SET */|  | // PIMSG=YES, /* ACCUMULATE DATA SET MESSAGES*/|  | // DATACK=BLOCK, /* UNBLOCK DATA CHECKS */|  | // TRACE=NO /* BUILD INTERNAL TRACE */|  | //PRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 32 (Part 3 of 3). APSWPROM Job          Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 101 ¤   B.6 STARTUP PROCEDURE APSWPROP  The sample startup procedure in Figure 33 is for OS/390 Softcopy Print  support. This procedure is placed in your PROCLIB as member APSWPROP  during the installation of PSF/MVS Version 2.2.0. Only a minimum set  of options are specified in this sample startup procedure. Refer to  the section entitled "PSF Startup Procedures for AFP Printers" in  Print Services Facility/MVS: System Programming Guide for further  information on available options and their functions.  The data sets referred to in this sample startup procedure have the  high-level qualifier of SYS1. If a different high-level qualifier is  used, the names in the procedure must be changed accordingly.  If the resources at your installation are consolidated into one font  library, modify this procedure to refer to the one font library.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWPROP PROC |  | //**************** THE PSF WRITER PROCEDURE *************** |  | //* |  | //*01* MODULE-NAME = APSWPROP |  | //* $MOD(APSWPROP) COMP(APS) PROD(PSF) : RELEASE 2.2.0 |  | //* |  | //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR SOFTCOPY PRINT |  | //* |  | //*01* STATUS = VERSION 2, RELEASE 2, LEVEL 0 |  | //* |  | //*01* FUNCTION = SET PSF OPTIONS AND RESOURCES |  | //* |  | //*01* REQUIRED ACTIONS = |  | //* RESOLUTION - THIS START PROCEDURE IS SET UP FOR 240 PEL |  | //* RESOLUTION. TO CHANGE IT TO 300 PEL RESOLUTION: |  | //* - COMMENT OUT THE FIRST FONTDD LINE AND |  | //* - UNCOMMENT THE SECOND FONTDD LINE |  | //* |  | //* ATTACHMENT - THIS START PROCEDURE IS SET UP FOR A TCP/IP|  | //* ATTACHED PRINTER. TO CHANGE IT TO SNA OR CHANNEL: |  | //* - UNCOMMENT AND MODIFY THE STATEMENTS INDICATED. |  | //* |  | //*01* NOTES = |  | //* THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS P1V06483. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FORMDEF IS F1A10110. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FONT IS X060D8. |  | //* THE FULL NAME OF THE MESSAGE DATA SET PAGEDEF IS P1A08682.|  | //* THE FULL NAME OF THE DEFAULT PAGEDEF IS P1A06462. |  | //* THE FULL NAME OF THE DEFAULT FORMDEF IS F1A10110. |  | //* THE FULL NAME OF THE DEFAULT FONT IS X060DB. |  | //* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 33 (Part 1 of 3). APSWPROP Job   Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 102 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //*01* CHANGE-ACTIVITY : |  | //* $00=OW19344, HPRF220, 960411, BDKUELJ: INITIAL VERSION |  | //* |  | //**************** END OF SPECIFICATIONS ******************/ |  | //* |  | //STEP01 EXEC PGM=APSPPIEP,REGION=4096K |  | //JOBHDR OUTPUT PAGEDEF=V06483, /* JOB HEADER PAGEDEF */|  | // FORMDEF=A10110,CHARS=60D8 /* JOB HEADER FORMDEF */|  | //JOBTLR OUTPUT PAGEDEF=V06483, /* JOB TRAILER PAGEDEF */|  | // FORMDEF=A10110,CHARS=60D8 /* JOB TRAILER FORMDEF */|  | //DSHDR OUTPUT PAGEDEF=V06483, /* DS SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=60D8 /* DS SEPARATOR FORMDEF */|  | //MSGDS OUTPUT PAGEDEF=A08682, /* MESSAGE DATASET PAGEDEF */|  | // FORMDEF=A10110,CHARS=60DB /* MESSAGE DATASET FORMDEF */|  | //FONT240 DD DSN=SYS1.FONTLIBB, /* SYSTEM FONTS - 240 PEL */|  | // DISP=SHR |  | //FONT300 DD DSN=SYS1.FONT300, /* SYSTEM FONTS - 300 PEL */|  | // DISP=SHR |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */|  | // DISP=SHR |  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM MEDIUM OVERLAYS */|  | // DISP=SHR /* */|  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */|  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */|  | // DISP=SHR |  | //* ************************************************************/|  | //* PRINTDEV */|  | //* ************************************************************/|  | //PRT1 CNTL |  | //PRT1 PRINTDEV PAGEDEF=A06462, /* DEFAULT PAGEDEF */|  | // FORMDEF=A10110, /* DEFAULT FORMDEF */|  | // FONTDD=*.FONT240, /* 240 PEL FONT LIBRARY DD*/|  | //* FONTDD=*.FONT300, /* 300 PEL FONT LIBRARY DD*/|  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */|  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */|  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */|  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */|  | // JOBHDR=*.JOBHDR, /* JOB HEADER OUTPUT */|  | // JOBTRLR=*.JOBTLR, /* JOB TRAILER OUTPUT */|  | // DSHDR=*.DSHDR, /* DATA SET HEADER OUTPUT */|  | // MESSAGE=*.MSGDS, /* MESSAGE DATA SET OUTPUT*/|  | // PIMSG=YES, /* ACCUMULATE MESSAGES */|  | // CHARS=60DB, /* DEFAULT FONT */|  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 33 (Part 2 of 3). APSWPROP Job    Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 103 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | // DATACK=BLOCK, /* BLOCK DATA CHECK ERRORS*/|  | //** FOR SNA OR TCP/IP ** |  | // MGMTMODE=IMMED, /* WHEN TO START SESSION */|  | // FAILURE=WCONNECT, /* ACTION ON SESSION FAILURE*/|  | //** FOR TCP/IP ** |  | // IPADDR='xxx.xxx.xxx.xxx',/* IP ADDRESS FOR TCP/IP */|  | //** FOR SNA ** |  | //* APPLID=name, /* VTAM APPLICATION PGM NAME*/|  | //* LUNAME=name, /* VTAM LOGICAL UNIT NAME */|  | //** FOR CHANNEL ATTACH ** |  | //* BUFNO=5, /* NUMBER OF WRITE DATA BUFFERS*/|  | //** |  | // TRACE=NO /* INTERNAL TRACE */|  | //PRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 33 (Part 3 of 3). APSWPROP Job              Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 104 ¤   B.7 STARTUP PROCEDURE APSWPROS  The sample startup procedure in Figure 34 is for most SNA/LU6.2 or  SNA/LU1 attached printers, including the following printers that use  240-pel fonts:  ù 3130 - if configured as an SNA-attached printer  ù 3160 - if configured as an SNA-attached printer  ù 3820  ù 3812  ù 3816  ù 3930  This procedure is placed in your PROCLIB as member APSWPROS during the  installation of PSF/MVS Version 2.2.0. Only a minimum set of options  are specified in this sample startup procedure. Refer to the section  entitled "PSF Startup Procedures for AFP Printers" in Print Services  Facility/MVS: System Programming Guide for further information on  available options and their functions.  The data sets referred to in this sample startup procedure have the  high-level qualifier of SYS1. If a different high-level qualifier is  used, the names in the procedure must be changed accordingly.  If the resources at your installation are consolidated into one font  library, modify this procedure to refer to the one font library.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWPROS PROC |  | //**************** THE PSF SNA WRITER PROCEDURE *************** |  | //* |  | //*01* MODULE-NAME = APSWPROS |  | //* $MOD(APSWPROS) COMP(APS) PROD(PSF) : RELEASE 2.2.0 @H7C |  | //* |  | //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR PSF: |  | //* |  | //* 3820 |  | //* 3812 |  | //* 3816 |  | //* 3930 |  | //* |  | //* |  | //*01* STATUS = VERSION 2, RELEASE 2, LEVEL 0 @H7C |  | //* |  | //*01* FUNCTION = THIS PROCEDURE IS COPIED FROM THE |  | //* DISTRIBUTION |  | //* LIBRARY TO SYS1.PROCLIB. THIS COPY |  | //* IS PERFORMED BY MACRO 'SGAPS5PR'. |  | //* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 34 (Part 1 of 3). APSWPROS Job   Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 105 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //*01* NOTES = THE FULL NAME OF THE DEFAULT PAGEDEF IS |  | //* P1A06462. |  | //* THE FULL NAME OF THE DEFAULT FORMDEF IS |  | //* F1A10110. |  | //* |  | //* THE FULL NAMES OF THE DEFAULT FONTS ARE |  | //* X0GF10, X0GS10, X0TU10, AND X0GU10. |  | //* |  | //* THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS |  | //* P1V06483. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FONT IS |  | //* X0GT15. |  | //* |  | //* |  | //*01* CHANGE-ACTIVITY : @L1C|  | //* $H1=LAPS0001, HAF1103, 110984 TD4 : RELEASE 1.1 @L1A|  | //* $H2=LAPS0002, HAF1203, 022586 BJ13RK : RELEASE 2.0 @L1A|  | //* $H3=LAPS0003, HAF1220, 081787 B53KJG : RELEASE 2.1 @L1A|  | //* $L1=LAPS0004, HAF1228, 011389 B53KJG : RELEASE 3.0 @L1A|  | //* $H7=LAPS0005, HPRF102, 071990 B53KDAR : REL 2.1.0 NEW FU @H7A|  | //* |  | //**** END OF SPECIFICATIONS ***/ |  | //* |  | //STEP01 EXEC PGM=APSPPIEP,REGION=1750K |  | //JOBHDR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDEF@H3C*/|  | //JOBTLR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDEF@H3C*/|  | //DSHDR OUTPUT PAGEDEF=V06483, /* DS SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* DS SEPARATOR FORMDEF@H3C*/|  | //MSGDS OUTPUT PAGEDEF=A06462, /* MESSAGE DATASET PAGEDEF */|  | // FORMDEF=A10110 /* MESSAGE DATASET FMDEF@H3C*/|  | //FONT01 DD DSN=SYS1.FONTLIBB, /* SYSTEM FONTS */|  | // DISP=SHR |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */|  | // DISP=SHR |  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM MED OVERLAY @H3C*/|  | // DISP=SHR /* @H3C*/|  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */|  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */|  | // DISP=SHR |  | //* ************************************************************/|  | //* PRINTDEV */|  | //* ************************************************************/|  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 34 (Part 2 of 3). APSWPROS Job    Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 106 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //PRT1 CNTL |  | //PRT1 PRINTDEV FONTDD=*.FONT01, /* FONT LIBRARY DD */|  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */|  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */|  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */|  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */|  | // JOBHDR=*.JOBHDR, /* JOB HEADER SEPARATOR */|  | //* /* OUTPUT */|  | // JOBTRLR=*.JOBTLR, /* JOB TRAILER SEPARATOR */|  | //* /* OUTPUT */|  | // DSHDR=*.DSHDR, /* DATA SET HEADER */|  | //* /* SEPARATOR */|  | // MESSAGE=*.MSGDS, /* MESSAGE DATA SET OUTPUT*/|  | // PAGEDEF=A06462, /* DEVICE PAGEDEF DEFAULT */|  | // FORMDEF=A10110, /* DEVICE FORMDEF DEFAULTC*/|  | // CHARS=(GF10, /* DEVICE */|  | // GS10,TU10,GU10), /* DEFAULT FONT SET */|  | // PIMSG=YES, /* ACCUMULATE DATA SET */|  | //* /* MESSAGES */|  | // DATACK=UNBLOCK, /* REPORT ALL DATA-CHE@H7A*/|  | //* /* ERRORS */|  | // TRACE=NO, /* CREATE INTERNAL TRC@H3C*/|  | // FAILURE=WCONNECT, /* PSF ACTION ON PRINTER */|  | //* /* FAILURE */|  | // TIMEOUT=REDRIVE, /* PSF ACTION ON TIMEOUT */|  | // DISCINTV=1800, /*DISCONNECT INTERVAL IN */|  | //* /* SECONDS */|  | // APPLID=xxxxxxxx, /*VTAM APPLICATION PGM */|  | //* /* NODE NAME */|  | // LOGMODE=xxxxxxxx, /*VTAM LOGON MODE TABLE */|  | //* /* ENTRY */|  | // MGMTMODE=OUTAVAIL, /*PRINTER MANAGEMENT MODE */|  | // LUNAME=xxxxxxxx /* VTAM LOGICAL UNIT NAME */|  | //PRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 34 (Part 3 of 3). APSWPROS Job        Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 107 ¤   B.8 STARTUP PROCEDURE APSWPROT  The sample startup procedure in Figure 35 is for TCP/IP attached  devices.  This procedure is placed in your PROCLIB as member APSWPROT during the  installation of PSF/MVS Version 2.2.0. Only a minimum set of options  are specified in this sample startup procedure. Refer to the section  entitled "PSF Startup Procedures for AFP Printers" in Print Services  Facility/MVS: System Programming Guide for further information on  available options and their functions.  The data sets referred to in this sample startup procedure have the  high-level qualifier of SYS1. If a different high-level qualifier is  used, the names in the procedure must be changed accordingly.  If the resources at your installation are consolidated into one font  library, modify this procedure to refer to the one font library.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //APSWPROT PROC |  | //**************** THE PSF TCP/IP WRITER PROCEDURE **************|  | //* |  | //*01* MODULE-NAME = APSWPROT |  | //* $MOD(APSWPROT) COMP(APS) PROD(PSF) : RELEASE 2.2.0 |  | //* |  | //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR PSF: |  | //* |  | //* TCP/IP ATTACHED DEVICES |  | //* |  | //*01* STATUS = VERSION 2, RELEASE 2, LEVEL 0 |  | //* |  | //*01* FUNCTION = THIS PROCEDURE IS COPIED FROM THE |  | //* DISTRIBUTION |  | //* LIBRARY TO SYS1.PROCLIB. THIS COPY |  | //* IS PERFORMED BY MACRO 'SGAPS5PR'. |  | //* |  | //*01* NOTES = THE FULL NAME OF THE DEFAULT PAGEDEF IS |  | //* P1A06462. |  | //* THE FULL NAME OF THE DEFAULT FORMDEF IS |  | //* F1A10110. |  | //* THE FULL NAMES OF THE DEFAULT FONTS ARE |  | //* X0GF10, X0GS10, X0TU10, AND X0GU10. |  | //* THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS |  | //* P1V06483. |  | //* THE FULL NAME OF THE SEPARATOR PAGE FONT IS |  | //* X0GT15. |  | //* |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 35 (Part 1 of 3). APSWPROT Job   Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 108 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //* REQUIRED ACTIONS = |  | //* RESOLUTION - THIS START PROCEDURE IS SET UP FOR DRIVING |  | //* A TCP/IP DEVICE AT 240 PEL RESOLUTION. TO CHANGE IT |  | //* TO DRIVE 300P PEL RESOLUTION TCP/IP ATTACHED DEVICES: |  | //* |  | //* A) COMMENT OUT THE FIRST PRINTDEV STATEMENT AND UNCOMMENT|  | //* THE SECOND PRINTDEV STATEMENT |  | //* |  | //* B) THE FONT02 DATA SET MUST CONTAIN THE CONVERTED |  | //* DEFAULT FONTS LISTED IN THE PRINTDEV. |  | //* THE FONTS ARE CONVERTED USING THE FONT |  | //* CONVERSION UTILITY APSRCF30. SEE THE PSF |  | //* SYSTEM PROGRAMMING GUIDE. |  | //* |  | //* |  | //* |  | //*01* CHANGE-ACTIVITY : |  | //* $H1=LAPS0001, HAF1103, 080195 DKU1JAU : TCP/IP SUPPORT |  | //* $01=OW15599 , HAF1103, 080195 DKU1JAU : @01A|  | //* |  | //**** END OF SPECIFICATIONS ***/ |  | //* |  | //STEP01 EXEC PGM=APSPPIEP,REGION=4096K |  | //JOBHDR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDEF */|  | //JOBTLR OUTPUT PAGEDEF=V06483, /* JOB SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* JOB SEPARATOR FORMDEF */|  | //DSHDR OUTPUT PAGEDEF=V06483, /* DS SEPARATOR PAGEDEF */|  | // FORMDEF=A10110,CHARS=GT15 /* DS SEPARATOR FORMDEF */|  | //MSGDS OUTPUT PAGEDEF=A06462, /* MESSAGE DATASET PAGEDEF */|  | // FORMDEF=A10110 /* MESSAGE DATASET FORMDEF */|  | //FONT01 DD DSN=SYS1.FONTLIBB,/* SYSTEM FONTS - 240 PEL */|  | // DISP=SHR |  | //FONT02 DD DSN=SYS1.FONT300, /* SYSTEM FONTS - 300 PEL */|  | // DISP=SHR |  | //PSEG01 DD DSN=SYS1.PSEGLIB, /* SYSTEM PAGE SEGMENTS */|  | // DISP=SHR |  | //OLAY01 DD DSN=SYS1.OVERLIB, /* SYSTEM MEDIUM OVERLAYS */|  | // DISP=SHR /* */|  | //PDEF01 DD DSN=SYS1.PDEFLIB, /* SYSTEM PAGEDEFS */|  | // DISP=SHR |  | //FDEF01 DD DSN=SYS1.FDEFLIB, /* SYSTEM FORMDEFS */|  | // DISP=SHR |  | //* ************************************************************/|  | //* PRINTDEV */|  | //* ************************************************************/|  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 35 (Part 2 of 3). APSWPROT Job    Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 109 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | |  | //PRT1 CNTL |  | //PRT1 PRINTDEV FONTDD=*.FONT01, /* 240 PEL FONT LIBRARY DD*/|  | //* /* <-- SEE REQUIRED ACTIONS */|  | //* /* ABOVE */|  | //*PRT1 PRINTDEV FONTDD=*.FONT02,/* 300 PEL FONT LIBRARY DD*/|  | //* /* <-- SEE REQUIRED ACTIONS*/|  | //* /* ABOVE */|  | // OVLYDD=*.OLAY01, /* OVERLAY LIBRARY DD */|  | // PSEGDD=*.PSEG01, /* SEGMENT LIBRARY DD */|  | // PDEFDD=*.PDEF01, /* PAGEDEF LIBRARY DD */|  | // FDEFDD=*.FDEF01, /* FORMDEF LIBRARY DD */|  | // JOBHDR=*.JOBHDR, /* JOB HEADER SEPARATOR */|  | //* /* OUTPUT */|  | // JOBTRLR=*.JOBTLR, /* JOB TRAILER SEPARATOR */|  | //* /* OUTPUT */|  | // DSHDR=*.DSHDR, /* DATA SET HEADER */|  | //* /* SEPARATOR */|  | // MESSAGE=*.MSGDS, /* MESSAGE DATA SET OUTPUT*/|  | // BUFNO=5, /* NUMBER OF WRITE DATA BUFFERS*/|  | // PAGEDEF=A06462, /* DEVICE PAGEDEF DEFAULT */|  | // FORMDEF=A10110, /* DEVICE FORMDEF DEFAULT */|  | // CHARS=(GF10, /* DEVICE */|  | // GS10,TU10,GU10), /* DEFAULT FONT SET */|  | // PIMSG=YES, /* ACCUMULATE DATA SET */|  | //* /* MESSAGES */|  | // DATACK=BLOCK, /* REPORT ALL DATA-CHECK */|  | //* /* ERRORS */|  | // TRACE=NO, /* CREATE INTERNAL TRACE */|  | // FAILURE=WCONNECT, /* PSF ACTION ON PRINTER */|  | //* /* FAILURE */|  | // TIMEOUT=REDRIVE, /* PSF ACTION ON TIMEOUT */|  | // MGMTMODE=IMMED, |  | // DISCINTV=0, /*DISCONNECT INTERVAL IN */|  | //* /* SECONDS */|  | // IPADDR='xxx.xxx.xxx.xxx' /* IP ADDRESS FOR TCP/IP */|  | //PRT1 ENDCNTL |  | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  Figure 35 (Part 3 of 3). APSWPROT Job       Appendix B. Startup Procedures for PSF/MVS Version 2.2.0 110 ¤   APPENDIX C. NEW FUNCTIONS ADDED TO PSF/MVS VERSION 2.2.0    The following table lists new functions that have been added to  PSF/MVS Version 2.2.0 since it was originally released in July 1994.  These APARs have all been incorporated into the base for PSF/MVS  Version 2.2.0 as part of Service Level SMC9618.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 36 (Page 1 of 7). New Functions Added to PSF/MVS Version |  | 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | FUNCTION | APAR | DESCRIPTION |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | MVS Download Record | OW17839 | You can now request that MVS |  | Length Support | | Download not append a record |  | | | length field when transmitting |  | | | data sets to certain AIX servers. |  | | | This support is for OnDemand for |  | | | AIX applications. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | OS/390 Support | OW18774 | A subset of PSF/MVS that can |  | | OW19344 | print online IBM publications |  | | | only, is now an integral |  | | | component of OS/390 Version 1 |  | | | Release 2. For full PSF |  | | | function, however, you must |  | | | purchase a PSF/MVS license. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | User Defined | OW17564 | You can now print double-byte |  | Characters | | outline fonts that contain user |  | | | defined characters (UDCs). The |  | | | AFP Font Collection (5648-113) |  | | | International Fonts and Programs |  | | | Feature 6208 contains information |  | | | on creating UDCs. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | MVS Download | OW17525 | You can now use an installation |  | Installation Exit | | exit for MVS Download to pass |  | | | additional job information to the |  | | | PSF server on the AIX system. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Enhancement to | OW17669 | PSF now selects the first inline |  | Support for Inline | | form definition, page definition, |  | Resources | | or microfilm setup resource in |  | | | the print data set when the user |  | | | JCL does not specify this |  | | | resource. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À   (C) Copyright IBM Corp. 1983, 1996 111 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 36 (Page 2 of 7). New Functions Added to PSF/MVS Version |  | 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | FUNCTION | APAR | DESCRIPTION |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | 7913 TWINAX Support | N/A | PSF now supports the TWINAX |  | | | connection of the i-data 7913 |  | | | Printer LAN attachment on the IBM |  | | | 4028 model AS1 printer, the IBM |  | | | 6400 model 004, 008, and 012 |  | | | printers, and on future printers |  | | | that are attached using the 7913. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Bar Code Support in | OW17445 | You can now generate bar codes |  | PAGEDEF | | using a page definition. To do |  | | | this, you specify that a field in |  | | | a line data record be presented |  | | | as a bar code. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | TCP/IP Address Space | OW16914 | You can now define any TCP/IP |  | Names | | address space name to PSF. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | SOSI Support in | OW16843 | You can now use more than one |  | PAGEDEF | | single-byte and double-byte font |  | | | per page when using |  | | | shift-in/shift-out codes to |  | | | switch fonts. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Non-N_UP to N_UP | OW16432 | You can now interrupt a job on a |  | Switching | | printer that is using a non-N_UP |  | | | form definition and complete it |  | | | on a printer that is using an |  | | | N_UP form definition. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À         Appendix C. New Functions Added to PSF/MVS Version 2.2.0 112 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 36 (Page 3 of 7). New Functions Added to PSF/MVS Version |  | 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | FUNCTION | APAR | DESCRIPTION |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Printer Sharing | OW15018 | For network-attached printers, |  | | | PSF/MVS now supports another |  | | | method of sharing printers with |  | | | other print drivers. The |  | | | port-switching method is |  | | | available for printers that |  | | | support multiple active ports. |  | | | For example, the 3130 with |  | | | Release 2 microcode, supports |  | | | multiple, simultaneous host |  | | | drivers sending one IPDS data |  | | | stream and multiple PCL or |  | | | PostScript data streams to the |  | | | printer. |  | | | |  | | | In addition, using the new |  | | | PRINTDEV keyword CONNINTV, you |  | | | can limit how long PSF continues |  | | | to retry starting a session or |  | | | dialog with the printer. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Font Capture Support | OW14128 | PSF now supports the font-capture |  | | | function available on printers |  | | | such as the 3130 with Release 2 |  | | | microcode. Such printers can |  | | | store raster and single-byte |  | | | outline fonts downloaded by PSF, |  | | | so that PSF does not need to |  | | | download these fonts each time |  | | | they are used. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Resident Double-Byte | OW14128 | PSF/MVS now supports |  | Outline Fonts | | printer-resident double-byte |  | | | outline fonts. PSF can activate |  | | | printer-resident outline fonts in |  | | | printers that support double-byte |  | | | outline fonts, regardless of the |  | | | resolution of the printer. The |  | | | printer can rotate and scale an |  | | | outline font character set to the |  | | | size needed. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Abend Information | OW12092 | PSF now provides more information |  | | | when PSF abends. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À    Appendix C. New Functions Added to PSF/MVS Version 2.2.0 113 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 36 (Page 4 of 7). New Functions Added to PSF/MVS Version |  | 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | FUNCTION | APAR | DESCRIPTION |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Huffman Compression | OW17625 | You can now enable the Huffman |  | Support | | compression algorithm in exit |  | | | APSUX07 to compress data at the |  | | | host and have the printer |  | | | decompress the data. This |  | | | function only works on |  | | | SDLC-attached printers. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | TCP/IP-Attached | OW15599 | PSF/MVS can now print on |  | Printers | | TCP/IP-attached printers running |  | | | in deferred-printing mode. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Reduce CSA Storage | OW01421 | Now you can reduce the amount of |  | Usage When Using | | common storage area (CSA) |  | PDSEs | | required when you use partitioned |  | | | data set extended (PDSEs) for |  | | | your resource libraries. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | 3160 Printer | OW13387 | PSF/MVS now supports the 3160 |  | | | printer. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | MVS Download | OW12811 | This APAR supports the MVS |  | | | Download feature, which allows |  | | | you to send output from an MVS |  | | | system to and AIX system for |  | | | printing with PSF for AIX or for |  | | | archiving with AFP OnDemand. To |  | | | use MVS Download, you must also |  | | | install the MVS Download feature |  | | | of PSF/MVS. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Microfilm Devices | OW10067 | PSF/MVS can now send AFP data to |  | | | microfilm devices running in |  | | | deferred printing mode. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | 6400, 6408, 6412 | OW04104 | PSF/MVS now supports the 6400, |  | Printers | | 6408, and 6412 printers. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Redirecting the | OW10066 | You can now put the message data |  | Message Data Set | | set in a SYSOUT data set or |  | | | direct it to a specified CLASS or |  | | | DEST. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À    Appendix C. New Functions Added to PSF/MVS Version 2.2.0 114 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 36 (Page 5 of 7). New Functions Added to PSF/MVS Version |  | 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | FUNCTION | APAR | DESCRIPTION |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | 4-Digit Year on | OW08944 | You can now print the entire |  | Separator Pages | | 4-digit year (1995) on your PSF |  | | | separator pages, rather than the |  | | | 2-digit year (95) currently |  | | | printed. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Single-Byte Outline | OW08340 | PSF/MVS now supports single-byte |  | Fonts | | outline fonts as well as raster |  | | | fonts. Outline fonts can be |  | | | downloaded or activated in |  | | | printers that support outline |  | | | fonts, regardless of the |  | | | resolution. The printer can |  | | | scale an outline font character |  | | | set to the size needed. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | SNA LU1 Suppression | OW10887 | You can now prevent ABEND024 |  | of a 2BA Abend | | RC02BA abends in many situations |  | | | when you use SNA LU1 printers. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | IOCA Replicate and | OW10903 | PSF/MVS now supports the IOCA |  | Trim | | replicate and trim mapping |  | | | option. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | 3800 Media Origin | OW10928 | You can now set the media origin |  | | | on the AFP continuous-forms |  | | | printer to be the same as the |  | | | media origin on the 3800 printer. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | 3112 and 3116 | OW11499 | PSF/MVS now supports the 3112 and |  | Printers | | 3116 printers. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Copy-Level Recovery | OW09054 | If you print multiple copies of |  | for JES Commands | | pages and lose some of these |  | | | copies when you enter an operator |  | | | command such as $ZPRTxxx or *S |  | | | DEV,L=0, then this new copy-level |  | | | recovery function can prevent |  | | | loss of copies of a page. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À     Appendix C. New Functions Added to PSF/MVS Version 2.2.0 115 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 36 (Page 6 of 7). New Functions Added to PSF/MVS Version |  | 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | FUNCTION | APAR | DESCRIPTION |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | PSF Direct | OW08338 | PSF Direct uses the SNA LU6.2 |  | | | protocol to print remotely on |  | | | OS/2 or AIX printers. PSF sends |  | | | the print data stream directly to |  | | | the OS/2 or AIX printer, |  | | | bypassing the OS/2 or AIX spool. |  | | | The PSF/MVS operator controls |  | | | printing as though the printers |  | | | were attached directly to |  | | | PSF/MVS. |  | | | |  | | | NOTES: |  | | | |  | | | 1. To print on an OS/2 printer, |  | | | you must also install PSF for |  | | | OS/2 (with the PSF Direct |  | | | function). |  | | | |  | | | 2. To print on an AIX printer, |  | | | you must also install the PSF |  | | | Direct feature of PSF for |  | | | AIX. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | 3800 Line Mode | OW08438 | PSF now allows perf-to-perf |  | Perforation-to-Perforation | printing if the FCB indicates |  |  | Printing | | perf-to-perf printing. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Indicate Last or | OW07738 | PSF installation exits can now |  | Only Data Set to | | determine when they have |  | Exits | | encountered the last data set of |  | | | a multi-data set job. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Additional Job Page | OW07446 | PSF/MVS now provides new job |  | Counters | | counters. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | CPU Performance | OW07305 | PSF/MVS now improves CPU |  | Improvement | | utilization for GROUP3 and 3800 |  | | | parallel- or ESCON |  | | | channel-attached printers. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Selection of Media | OW07348 | You can now select the media |  | Destination Output | | destination (output bin) for a |  | Bin | | job or data set, on a printer |  | | | with more than 1 output bin. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À    Appendix C. New Functions Added to PSF/MVS Version 2.2.0 116 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 36 (Page 7 of 7). New Functions Added to PSF/MVS Version |  | 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | FUNCTION | APAR | DESCRIPTION |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Suppression of | OW06631 | You can now set a new field in |  | Interrupt Message | | installation exit APSUX07 to |  | Pages | | suppress printing of the |  | | | interrupt message page in the |  | | | middle of your output. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Blank Compression | OW07350 | Blank Compression may improve |  | | | your printer throughput if you |  | | | print line data containing many |  | | | blanks over slower-speed |  | | | attachment communication lines. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Enhanced N_UP | OW03243 | Using N_UP printing, you can |  | Printing | | place up to eight pages on a |  | | | duplexed sheet. On wide |  | | | printers, you can place up to |  | | | four 8 1/2 x 11 pages on a |  | | | duplexed sheet. With Enhanced |  | | | N_UP, you have greater |  | | | flexibility in where and how you |  | | | place pages on the sheet. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Enhanced Tracing of | OW06775 | PSF now traces all installation |  | Exits | | exits in the PSF internal and |  | | | external traces. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | ESCON Channel | OW04452 | PSF/MVS now supports connecting a |  | Attachment for | | printer to the fiber optics ESCON |  | Printers | | (Enterprise Systems Connection) |  | | | channel, in addition to |  | | | supporting parallel |  | | | channel-attached printers capable |  | | | of handling 16K I/O buffers. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Printer NACK Support | OW08946 | PSF now supports the new X'22' |  | | | NACKS, which printers such as the |  | | | 3900 or 3835 (with the large |  | | | mail-room function enabled) can |  | | | send when printer supplies need |  | | | to be refreshed. |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Enhanced Block | OW08336 | PSF now allows you to customize |  | Letter Support | | the block letters on the PSF |  | | | separator pages. You can create |  | | | all new block letters or modify |  | | | the existing ones. |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À   Appendix C. New Functions Added to PSF/MVS Version 2.2.0 117 ¤   APPENDIX D. SMP/E DIALOG PANEL INFORMATION    Through SMP/E dialog panels, you can create, modify, and submit the  sample jobs for some of the installation steps described in this  program directory; therefore, you do not need to use the sample jobs  shipped on the installation tape for these specific tasks. You can  use the dialog panels to:  ù Identify the target and distribution libraries to SMP/E (DDDEFs)  ù Create a job that performs the SMP/E RECEIVE process  ù Create jobs that perform the SMP/E APPLY CHECK and APPLY process  ù Create jobs that perform the SMP/E ACCEPT CHECK and ACCEPT  process.  If you choose to use the dialog panels, you must supply information to  SMP/E at the various stages of installation. The information  described in Figure 37, assumes that all steps are performed during  one SYSMOD INSTALL session within the SYSMOD MANAGEMENT panels of  SMP/E. DDDEFs can be created using the SMP/E ADMINISTRATION dialog  panels.  Figure 37 does not imply that the installation steps are done in order  from top to bottom. In addition, there are specific non-SMP/E  procedures that must be done between these steps for PSF/MVS Version  2.2.0 installation. SMP/E lets you suspend an installation session  between steps, exit SMP/E to do the non-SMP/E procedures, then resumes  the SMP/E session at the point it was suspended.         (C) Copyright IBM Corp. 1983, 1996 118 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 37. SMP/E Dialog Panel Prompts and Suggested |  | User Responses |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | STEP | PROMPT | RESPONSE |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | SYSMOD | Zone Name | Your target or |  | Install | | distribution zone |  | | | name |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | RECEIVE | VOLUME | PRF220 |  | Product | UNIT | Unit Name |  | | FMID | HPRF220 and |  | | | JPRF223 are valid |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APPLY | Perform APPLY CHECK | YES |  | CHECK | GROUPEXTEND | YES |  | | COMPRESS DURING APPLY | NO |  | | SKIP JCLIN PROCESSING | NO |  | | BYPASS IFREQ CHECK | NO |  | | BYPASS PRE CHECK | NO |  | | BYPASS REQ CHECK | NO |  | | Other Fields | Optional |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APPLY | GROUPEXTEND MODE | YES |  | | COMPRESS DURING APPLY | NO |  | | SKIP JCLIN PROCESSING | NO |  | | RECOVER FROM X37 ABEND | YES |  | | BYPASS ID | NO |  | | BYPASS PRE | NO |  | | BYPASS IFREQ | NO |  | | BYPASS REQ | NO |  | | Other Fields | Optional |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | ACCEPT | Perform ACCEPT CHECK | YES |  | CHECK | GROUPEXTEND | YES |  | | SKIP JCLIN PROCESSING | NO |  | | BYPASS IFREQ CHECK | NO |  | | BYPASS PRE CHECK | NO |  | | BYPASS REQ CHECK | NO |  | | Other Fields | Optional |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | ACCEPT | GROUPEXTEND | YES |  | | SKIP JCLIN PROCESSING | NO |  | | COMPRESS DURING ACCEPT | YES |  | | RECOVER FROM X37 ABEND | YES |  | | BYPASS ID | NO |  | | BYPASS PRE | NO |  | | BYPASS IFREQ | NO |  | | BYPASS REQ | NO |  | | Other Fields | Optional |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À   Appendix D. SMP/E Dialog Panel Information 119 ¤   APPENDIX E. CHECKLIST FOR PSF/MVS VERSION 2.2.0 INSTALLATION    The following checklist can be used to help install PSF/MVS Version  2.2.0.  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 38 (Page 1 of 2). Installation Checklist for PSF/MVS |  | Version 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | JOBNAME | DESCRIPTION | NOTES |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | UNLOAD | 6.1.1, "Unload Sample Jobs" on page 49 | |  | | | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWALOC | 6.1.2, "Allocate Target and Distribution | |  | | Library Data Sets" on page 50 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWDDEF | 6.1.3, "Create Target and Distribution | |  | | Library DDDEFs" on page 53 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Copy Previous | 6.1.4, "Copy PSF/MVS Target Libraries | |  | Release Data | from a Previous Release" on page 57 | |  | Sets | | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWRCV | 6.1.5, "RECEIVE PSF/MVS Version 2.2.0 | |  | | Applicable FMIDs" on page 59 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWRCVC | 6.1.6, "RECEIVE Cumulative Service Tape, | |  | | if Applicable" on page 60 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWMFID | 6.1.7, "Transfer Ownership of SYSMODS | |  | | using UCLIN" on page 61 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWDEL | 6.1.8, "Delete PSF/MVS" on page 64 | |  | | | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWAPCK | 6.1.9, "Perform APPLY CHECK" on page 65 | |  | | | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWAP | 6.1.10, "Load Target Libraries Using | |  | | APPLY" on page 66 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | I/O | 6.1.11, "Perform I/O Configuration" on | |  | Configuration | page 67 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Modify System | 6.1.12, "Modify the System Environment | |  | Environment | for PSF/MVS Version 2.2.0" on page 67 | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À   (C) Copyright IBM Corp. 1983, 1996 120 ¤   ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | Figure 38 (Page 2 of 2). Installation Checklist for PSF/MVS |  | Version 2.2.0 |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | ¿ ¿ |  | JOBNAME | DESCRIPTION | NOTES |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Re-IPL | 6.1.14, "Re-IPL the MVS System" on | |  | | page 68 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWACCK | 6.1.15, "Perform ACCEPT CHECK" on page 68 | |  | | | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSWAC | 6.1.16, "Load Distribution Libraries | |  | | Using ACCEPT" on page 69 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Replace | 6.1.17, "Replace PSF/MVS Startup | |  | Startup | Procedures from Previous Release" on | |  | Procedures | page 70 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | APSIVP, | 6.1.18, "Perform Installation | |  | APSIVPDA | Verification" on page 70 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Replace | 6.1.19, "Replace PSF/MVS Resources from | |  | Resources | Previous Release" on page 70 | |  ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿  | | | |  | Replace | 6.1.20, "Replace PSF/MVS Installation | |  | Installation | Exits from Previous Release" on page 71 | |  | Exits | | |  ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ  À À           Appendix E. Checklist for PSF/MVS Version 2.2.0 Installation 121 ¤   APPENDIX F. PTF COVER LETTER DATA FOR SERVICE LEVEL SMC9618    The PTFs listed in this section have been incorporated into the base  for PSF/MVS Version 2.2.0 at Service Level SMC9618. The included  cover letters for "++HOLD...SYSTEM" PTFs should be reviewed, as they  contain documentation changes that have not been included in the  publications that ship with PSF/MVS Version 2.2.0.   F.1 COVER LETTER FOR PTF UW26752   PROBLEM DESCRIPTION(S):  OW17525 -  ****************************************************************  * USERS AFFECTED: ALL PSF/MVS 2.2.0 USERS USING THE MVS *  * DOWNLOAD FEATURE. *  ****************************************************************  * PROBLEM DESCRIPTION: CURRENTLY MVS DOWNLOAD DOES NOT SUPPORT *  * A WAY TO ALLOW ADDITIONAL JOB INFORMA- *  * TION TO BE TRANSMITTED TO THE TARGET *  * SERVER ON AIX. FOR EXAMPLE, MVS DOWN- *  * LOAD DOES NOT TRANSMIT THE JOB OUTPUT *  * GROUP ID TO THE SERVER AND THERE IS NO *  * WAY FOR A USER TO TELL MVS DOWNLOAD TO *  * DO SO. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  MVS DOWNLOAD NEEDS SUPPORT TO TRAMSMIT THE JES JOB ID  INFORMATION AND USER-SPECIFIED JOB INFORMATION  TO THE TARGET MVS DOWNLOAD SERVER ON THE AIX SYSTEM.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW17525  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Make the following changes to the Print Services Facility/MVS  System Programming Guide Version 2, Release 2, Modification 0  (S544-3672-02).  1. On page 176 add the following entry before APSUX16X.ASSEMBLE  in Table 24, "PSF Exit Routines in SYS1.SAMPLIB".  ------------------------------------------------------------  | APSUX15X.ASSEMBLE | Sample source routine to provide|  | | the printer device name and the |  | | output group name for MVS |  | | Download to transmit to its |  | | server on AIX. |   (C) Copyright IBM Corp. 1983, 1996 122 ¤   ------------------------------------------------------------  2. On page 176 change the note following table 24 to read as  follows.  NOTE: PSF provides object code for the default separator-page  exits (modules APSUX01, APSUX02, and APSUX03). PSF does not  provide object code for the other exits -- logical-record  processing, SMF type 6 record processing, PSF-message  processing, resource processing, MVS download and direct  printing.  3. On page 182 in table 59, "Format of Exit-Communications Area  Extension (APSUECE) change ECEX15P to read as follows.  204 (CC) Address 4 ECEX15P Address of exit APSUX15  (in MVS Download only)  4. On page 182 in table 59, "Format of Exit-Communications Area  Extension (APSUECE) change the entry at "216 (D8)" to read  as follows.  216 (D8) Character 12 ECEDSID FSI GETDS dataset ID  (in MVS Download only)  228 (E4) Character 16 * Reserved  5. On page 222 add a new exit section following the section  entitled "Resource-Management Exit: APSUX07" that reads  as follows.  MVS Download Print Parameter Exit: APSUX15  Using this exit with MVS Download, you can provide  additional job information (as passthru print parameters)  to be transmitted to the target MVS Download server  on AIX.  MVS Download provides a sample print parameter routine  that you can use to create, assemble, install  (or link-edit) an exit that provides additional job  information to be transmitted to the target MVS Download  server on AIX. This routine runs in the same  address space as does MVS Download.  Input for APSUX15  Upon entry to the print parameter exit, the contents of  the registers are:  Register 1 Pointer to the address of parameter area  APSGEXTP  Register 13 Pointer to caller's save area  Register 14 Return address  Register 15 Entry-point address  Output for APSUX15  ECARECAD Pointer to the EBCDIC string of additional  job information  ECARECLN Length of the string  Programming Considerations for APSUX15  The following general considerations apply to APSUX15:  o Upon entry to this routine, register 1 points to a  one-word parameter list that contains the address  of APSGEXTP. APSGEXTP contains a pointer to the  exit-communications area (APSUECA).  o APSUX15 can use the APSUECA work buffer (ECAWKBUF)  to store the EBCDIC string of additional job  information. If this work buffer is too small, see   Appendix F. PTF Cover Letter Data for Service Level SMC9618 123 ¤   "Exit Table (APSUCOM)" on page 188 for information  on expanding ECAWKBUF.  o The following fields in APSUECA and APSUECE are  valid when exit 15 is called:  ECAECEP APSUECE address  ECAUCOMP APSUCOM address  ECAUSAVE Save area  ECAWKBUF Exit work buffer  ECEPDEVK PRINTDEV SWB token  ECEOUTTK Print dataset SWB token  ECEJDVTN Print dataset JDVT name  ECETUPTR Address of SWBTU  ECETULEN SWBTU length  ECEDSID FSI dataset ID  o On entry, register 13 points to a standard 18-word  save area that should be used to save the caller's  register.  o Use register 12 as a base register for all exit  routines. If register 12 points to the beginning  of an exit routine and the module name begins in the  sixth byte of the routine, then the module name will  appear on the SDUMP title page if an abend occurs.  o ECARECAD, upon return from exit 15, is the pointer  to the EBCDIC string of additional job information.  For example, the format of the string can be:  devname=PRT600,outgrp_name=2  MVS Download removes any blank characters or  nulls (X'00') in the string and includes the string  in the passthru print parameter (-opa) to be  transmitted to the AIX system. To avoid removal  of blank characters or nulls, exit 15 must replace  them with X'1C'.  MVS Download does not perform any syntax or validity  check of the string. It is assumed the receiver of  the string in the AIX system can handle it.  With the above example, the final format of the  passthru parameter looks like:  -opa=forms=STD,class=X,destination=LOCAL,  jobid=JOB00074,devname=PRT600,outgrp_name=2  o ECARECLN, upon return from exit 15, is the length  of the string.  ----------------------------------------------------------------  Make the following changes to the Print Services Facility/MVS:  MVS Download Guide (G544-5294-00).  1. At the top of page 52, add a new section before the section  entitled "Using Accounting Information" that reads as  follows:  Using the MVS Download Exit: APSUX15  MVS Download supports an installation exit, APSUX15. The  exit allows you to provide additional job information(as  passthru print parameters) to be transmitted to the target  MVS Download server on AIX.  Refer to the PSF/MVS System Programming Guide V2.2.0,  (S544-3672-02), Chapter 15, "Using Installation Exits", for   Appendix F. PTF Cover Letter Data for Service Level SMC9618 124 ¤   a detailed description concerning the use of APSUX15.  2. On page 60 add the following entry after APS072I in the table  "Message-to-Module Cross-Reference".  APS095I APSUEXTI  3. On page 61 add the following message as the first message in  the section entitled "MESSAGES".  APS095I INSTALLATION EXIT APSUX15 WILL NOT BE INVOKED  Explanation: The initialization of the MVS Download exit  routine failed because insufficient length  was specified in the APSUCOM table, the  APSUCOM module could not be located, or a  BLDL macro failed.  System Action: Processing continues without the installation  exit.  User Response: No response is necessary.  System Programmer Response: Evaluate any changes made to  the APSUCOM module (static  table), to the exit routines,  or to the methods used to  establish the tables or  routines in the system. Other  messages may contain BLDL macro  return and reason codes.  Operator Response: Inform your system programmer that this  error occurred.  Problem Determination: Items 1, 3.  ACTION:  If you have modified your source code for APSUECA, then save it  before applying this PTF as this PTF will replace your copy of  APSUECA. You will need to merge your changes into APSUECA.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSKAFPD OW17525  APSKDVP OW17525  APSKFSA OW17525  APSKIFA OW17525  APSKOPT OW17525  APSMSTXT OW17525  APSUECA OW17525  APSUEXIT OW17525  APSUEXTI OW17525  APSUFSSI OW17525  APSUX15X OW17525  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW17525 APSKAFPD APSKDVP APSKFSA APSKIFA APSKOPT APSMSTXT  APSUECA APSUEXIT APSUEXTI APSUFSSI APSUX15X  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APSKAFPD  APSKDVP  APSKFSA   Appendix F. PTF Cover Letter Data for Service Level SMC9618 125 ¤   APSKIFA  APSKOPT  APSMSTXT  APSUEXIT  APSUEXTI  APSUFSSI  MACROS  APSUECA  APSUX15X  LISTEND   F.2 COVER LETTER FOR PTF UW26952   PROBLEM DESCRIPTION(S):  OW17564 -  ****************************************************************  * USERS AFFECTED: PSF/MVS 2.2.0 customers who want to print *  * with double byte outline fonts that contain *  * user defined characters(UDCs). *  * Also any PSF/MVS 2.2.0 customers who have *  * experienced the following problems: *  * 1. ABEND024 RC0724 *  * 2. MSGAPS558I and the data set prints fine *  * 3. MSGAPS701I for code page name and *  * character set coming out with 'UNKNOWN' *  * when using double byte outline fonts *  ****************************************************************  * PROBLEM DESCRIPTION: Customers could not print with fonts *  * that contained user defined characters *  * which were in the form of extension *  * font character sets. PSF/MVS also: *  * 1. Issued ABEND024 RC0724 if a coded *  * font did not activate successfully *  * 2. Issued MSGAPS558I when it wasn't *  * necessary and *  * 3. Was not filling in the code page *  * and character set names correctly *  * in MSGAPS701I for double byte *  * outline fonts. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  Resource Mgr needed additional function to support extension  font character sets.  1. Resource Mgr abended with ABEND024 RC0724 when  a coded font did not activate successfully.  2. Resource Mgr issued message APS558I when it ran out of  HAIDs even if it could recover from this problem and  successfully complete printing of the data set.  3. Resource Mgr did not correctly locate the names of the   Appendix F. PTF Cover Letter Data for Service Level SMC9618 126 ¤   code page and character set for double byte outline fonts  when MSGAPS701I was being issued.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW17564  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Update the following publications:  PSF/MVS Messages and Codes S544-3675-02  Page 146 remove the entry for message APS558I  Page 149 following the entry for APS565I add this new message:  APS566I AN ATTEMPT WAS MADE TO ACTIVATE A CODED FONT member  name USING FONT CHARACTER SET member name, CODE PAGE member  name, VERTICAL FONT SIZE size, HORIZONTAL FONT SIZE  size, AND HORIZONTAL SCALE FACTOR scale factor. THE ATTEMPT WAS  NOT SUCCESSFUL.  EXPLANATION:  PSF was attempting to activate a Coded Font but was not  successful. To activate the Coded Font, the Code Page and  Font Character Set should have already been loaded in the  printer or activated. The message contains the member names  of the Coded Font, Code Page, and Font Character Set that were  involved in this error. Also included in the message is the  vertical and horizontal font sizes and the horizontal  scale factor.  Some possible causes of this error are listed below:  - The Character Set and Code Page are not compatible. It is  possible for a user to create a Coded Font resource that  specifies a Font Character Set and Code Page that can not  be used together.  - A Coded Font with the same HAID was already active.  This would be a PSF logic error.  - The printer found something wrong with the values specified  in the Active Resource command. This would be a PSF logic  error.  - The Font Character Set or Code Page were not activated or  loaded in the printer prior to activating the Coded Font.  This would be a PSF logic error.  SYSTEM ACTION:  PSF was unable to activate all the necessary resources in the  printer that were required for printing this page. As a result  PSF will not print the page containing the error.  PSF issues a message identifying the page which contained the  resource which had the error. PSF will issue additional  messages identifying the processing environment when the error  was found.  USER RESPONSE:  Ensure that the Code Page and the Font Character Set for the  Coded Font that is in error are compatible, refer to the  "Font Object Content Architecture (FOCA) Reference" S544-3285  for information about how to select compatible Code Pages and  Font Character Sets. If the Code Page and Font Character Set  are compatible then this may be a PSF logic error.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 127 ¤   SYSTEM PROGRAMMER RESPONSE:  If an IBM licensed program was used to create the structured  fields for the resource with the error, verify that the input  to that program was valid. If the input was valid, refer to  Advanced Function Printing: Diagnosis Guide and Print Services  Facility/MVS: Diagnosis Guide and Reference for assistance in  determining the source of the problem. If the error involves  separator pages or the message data set, use the information  provided in the User Response section to correct the error.  OPERATOR RESPONSE:  If this message appears on the operator's console, it indicates  that the resource containing the error is defined for a  separator page or the message data set in the PSF startup  procedure. Inform your system programmer.  PROBLEM DETERMINATION:  Items 2, 8, 17, 19.  Page 212, update message APS824I as follows:  APS824I THE MAXIMUM NUMBER OF FONTS IS ALREADY LOADED.  EXPLANATION: While PSF was loading fonts, the maximum number of  fonts allowed on a single sheet was reached.  SYSTEM ACTION: (remains the same)  USER RESPONSE: (everything remains the same except the last  sentence)  If the above situation does not apply, then  reduce the number of fonts used on the sheet or resource and  resubmit the print request.  The rest of the message entry remains the same.  Page 300, delete the entry for abend 724.  Page 303, add a new entry for abend 784  0784  Explanation: This abend is issued by module APSRROCK--  A NACK was reported during the loading/activation of an  outline font, but the flags inside the Resource Control Block  did not indicate which part was being processed at the time  of the error.  System Action: PSF processing terminates abnormally.  System Programmer Response: This PSF abend reason code  indicates a possible logic error. Contact your service  representative in the IBM Support Center, or use your electronic  link with IBM service for assistance regarding this error code.  Print Services Facility/MVS: Diagnosis Guide and Reference  LH40-0205-01  In Appendix A, pg 60 delete the entry for APS558I and add a new  entry APS566I APSRLOAD.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRCS2AZ OW17564  APRGRNEX OW17564  APROAEEX OW17564  APSEMSG OW17564  APSERRM OW17564  APSMSTXT OW17564  APSRDEL OW17564  APSRFLST OW17564   Appendix F. PTF Cover Letter Data for Service Level SMC9618 128 ¤   APSRHAID OW17564  APSRLOAD OW17564  APSRNAME OW17564  APSRROCK OW17564  APSRSTAT OW17564  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW17564 APRCS2AZ APRGRNEX APROAEEX APSEMSG APSERRM APSMSTXT  APSRDEL APSRFLST APSRHAID APSRLOAD APSRNAME APSRROCK  APSRSTAT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRCS2AZ  APRGRNEX  APROAEEX  APSEMSG  APSERRM  APSMSTXT  APSRDEL  APSRFLST  APSRHAID  APSRLOAD  APSRNAME  APSRROCK  APSRSTAT  LISTEND  */.   F.3 COVER LETTER FOR PTF UW27158   PROBLEM DESCRIPTION(S):  OW18774 -  ****************************************************************  * USERS AFFECTED: Users of PSF/MVS 2.2.0 on OS/390 Version 1 *  * Release 2 or later. *  ****************************************************************  * PROBLEM DESCRIPTION: PSF support needed for OS/390. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW18774  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Change the PSF/MVS 2.2.0 Messages and Codes, S544-3675-02:  On page 46, add   Appendix F. PTF Cover Letter Data for Service Level SMC9618 129 ¤   APS211I THE PRINT DATA SET IS NOT RECOGNIZED AS A SOFTCOPY  PUBLICATION. PSF IS ENABLED ONLY FOR SOFTCOPY PRINT.  Explanation: PSF is included in the base of OS/390 for print of  SoftCopy publications. To print other documents on OS/390, PSF  must be enabled by the system programmer. The print data set  did not contain the identifier which is generated by BookManager  Read when printing a SoftCopy publication.  System Action: PSF stops processing the data set. This message  is followed by another message (such as APS101I) indicating  the action taken.  User Response: If you are on an MVS system prior to OS/390  Version 1 Release 2, or if you are  attempting to print a softcopy publication on OS/390 Version 1  Release 2 or later, contact your system programmer.  If you are on OS/390 Version 1 Release 2 or later, and you think  PSF full function is enabled, contact your system programmer.  Otherwise, request the purchase of a PSF license.  System Programmer Response: If PSF is running on MVS prior to  OS/390 Version 1 Release 2 or if the user was attempting to  print a valid SoftCopy publication, contact IBM service.  If PSF is running on OS/390 Version 1 Release 2  or later and you have enabled PSF,  verify that the PSF PRODUCT statement is correct in PARMLIB.  Operator Response: No response is necessary.  Problem Determination: Items 1, 2, 13, 17, 31  In Appendix A Problem Determination, on page 335, add the item  Ú--------------------------------------------------------------¿  | 31 | On OS/390, verify the enable/disable state of PSF with |  | | the command D PROD,STATE and save the system log. |  À--------------------------------------------------------------Ù  ...............................................................  Change the PSF/MVS 2.2.0 Diagnosis Guide and Reference,  LH40-0205-01:  In table 6, Message-to-Module Cross-Reference, on page 55, add  Ú------------------------¿  | APS211I | APSDECH |  À------------------------Ù  In table 9, PSF Reason Codes, on page 71, add  Ú--------------------------------------------------------------¿  | X'08070101' | PSF is not enabled and the print | APRINPEX |  | | DS is not a SoftCopy publication. | |  À--------------------------------------------------------------Ù  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRINPEX OW18774  APSAFSA OW18774  APSDECH OW18774  APSGAD31 OW18774  APSMSTXT OW18774  APSPCKEN OW18774  APSPPFSA OW18774  APSPPIEP OW18774  APSUEXTI OW18774  APSUFSSI OW18774   Appendix F. PTF Cover Letter Data for Service Level SMC9618 130 ¤   HPRF220J OW18774  SGAPS4PP OW18774  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW18774 APRINPEX APSAFSA APSDECH APSGAD31 APSMSTXT APSPCKEN  APSPPFSA APSPPIEP APSUEXTI APSUFSSI HPRF220J SGAPS4PP  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRINPEX  APSAFSA  APSDECH  APSGAD31  APSMSTXT  APSPCKEN  APSPPFSA  APSPPIEP  APSUEXTI  APSUFSSI  MACROS  SGAPS4PP  LISTEND  */.   F.4 COVER LETTER FOR PTF UW27811   PROBLEM DESCRIPTION(S):  OW19765 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users who have applied PTF *  * UW24899 and are not using TCP/IP attached *  * printers. *  ****************************************************************  * PROBLEM DESCRIPTION: TCP/IP INITAPI was hanging. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  TCP/IP services were being invoked even  when no TCP/IP printers were attached.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW19765  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  In Section 1, Chapter 19, on page 22 of Print Services  Facility/MVS: Version 2, Release 2, Modification 0 Update Guide  (G544-3984-01):  Replace the Note specifying that the TCP/IP address space name   Appendix F. PTF Cover Letter Data for Service Level SMC9618 131 ¤   must be 'TCPIP'.  Replace with the following text:  To specify a different TCP/IP address space name other than the  default 'TCPIP' code the following EXEC statement in the  appropriate writer procedure:  //STEP01 EXEC PGM=APSPPIEP,REGION=4096K,PARM=(,,,,tcpip_name)  where tcpip_name is the name of the TCP/IP address space name.  If this parameter is not coded, PSF/MVS will use the default  name of 'TCPIP'. See PSF/MVS Diagnosis Guide and Reference  (S544-3673-02) for documentation on the first four parameters.  In Section 2, on page 51 of Print Services  Facility/MVS: Version 2, Release 2, Modification 0 Update Guide  (G544-3984-01):  Add a Message APS949I.  APS949I INITAPI FAILED FOR TCP/IP ADDRESS SPACE NAME OF  (tcpip_name) WITH A RETURN CODE OF (nnnn) AND  AN ERRNO OF (nnnn).  Explanation: The INITAPI call to TCP/IP failed. RETURN CODE has  the return code from the call and ERRNO has the TCP/IP error  number. The tcpip_name has the TCP/IP address space name, either  the default name of 'TCPIP' or the name specified as a parameter  on the EXEC statement.  System Action: This message is issued only to the operator  console. This message will be followed by an E91 abend and  the printer will drain.  System Programmer Response: Verify that the tcpip_name is the  address space name of TCP/IP. Check the ERRNO value in the IBM  TCP/IP for MVS: Messages and Codes Version 3 Release 1 for any  actions required by TCP/IP.  Operator Response: Verify that the TCP/IP procedure with the  tcpip_name was started. If the task has not been started, cancel  the writer procedure then start the TCP/IP task and restart  the printer.  Problem Determination: None.  ----------------------------------------------------------------  In Section 3, on page 72 of Print Services  Facility/MVS: Version 2, Release 2, Modification 0 Update Guide  (G544-3984-01):  add the following message to the Message-to-Module  Cross-Reference table:  -------------------------  | APS949I | APSNINIT |  -------------------------  DOCUMENTATION:  Update the PSF/MVS Version 2, Release 2, Modification 0 update  Guide:  1. In Section 2, Chapter 1, add the following new message after  APS935I:  APS948I FSS LEVEL INITAPI COULD NOT BE DONE FOR ADDRESS SPACE  NAME OF (tcpip_name) FOR REASON (reason).  Explanation: The PSF FSA detected that the FSS did not issue  a successful INITAPI request using the indicated  'tcpip_name'.  'reason' may be one of the following:   Appendix F. PTF Cover Letter Data for Service Level SMC9618 132 ¤   o GETMAIN FAILURE - The FSS was not able to  getmain storage for its work areas.  o NO TCP/IP - The FSS was not able to locate  the TCP/IP module EZASOK03.  o INIT API FAILURE - The FSS received a non-  zero return code from the INITAPI.  o INIT API HUNG - The FSS has not responded  after 5 minutes. The FSS appears to be hung.  System Action: The PSF FSA is ended.  User Response: Inform your System Programmer that this error  has occurred.  System Programmer Response:  o GETMAIN FAILURE - Increase the REGION  parameter on the procedure used to start PSF.  o NO TCP/IP - Ensure that TCP/IP was installed  in a library that is loadable by PSF.  o INIT API FAILURE - See the APS949I message  issued by this FSS prior to this message to  evaluate the problem.  o INIT API HUNG - Cancel the PSF address space  and inform your IBM Support Center.  Operator Response: Inform your System Programmer.  Problem Determination: 1, 4, 5, 9, 17.  2. In Section 2, Chapter 2, System Completion Codes and PSF  Abend Reason Codes, add the following abend:  0E98  ----  Explanation: This abend is issued by module APSNINIT -  The FSS level INITAPI was not completed successfully.  See message APS948I issued prior to this abend for  additional information.  System Action: PSF processing terminates abnormally.  System Programmer Response: See message APS948I issued  prior to this abend for the appropriate response.  3. In Appendix A, add the following entry to the Message-to-  Module Cross Reference table (Table 6):  +--------------------+  | APS948I | APSNINIT |  +--------------------+  4. In Appendix A, change the entry for APS949I in the Message  to Module Cross Reference table (Table 6) to the following:  +--------------------+  | APS949I | APSNINIT |  | | APSPPFSP |  +--------------------+  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSAFSA OW19765  APSCESTA OW19765  APSCTCP OW19765  APSMSTXT OW19765  APSNINIT OW19765  APSNLINK OW19765  APSPPASI OW19765   Appendix F. PTF Cover Letter Data for Service Level SMC9618 133 ¤   APSPPFSP OW19765  APSPPIEP OW19765  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW19765 APSAFSA APSCESTA APSCTCP APSMSTXT APSNINIT APSNLINK  APSPPASI APSPPFSP APSPPIEP  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APSAFSA  APSCESTA  APSCTCP  APSMSTXT  APSNINIT  APSNLINK  APSPPASI  APSPPFSP  APSPPIEP  LISTEND  */.   F.5 COVER LETTER FOR PTF UW24450   PROBLEM DESCRIPTION(S):  OW17625 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users using an *  * AFCCU printer with a SDLC attachment and *  * low speed communication line such as *  * 9.6 kbs. *  ****************************************************************  * PROBLEM DESCRIPTION: Support is provided in PSF/MVS to *  * allow data to be compressed using the *  * Huffman compression algorithm. This *  * algorithm may improve printer *  * throughput if you are using an AFCCU *  * printer with a SDLC attachment and a *  * low speed communication line such as *  * 9.6 kbs. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  PSF/MVS can now compress any type of data using the Huffman  compression algorithm and send it to the printer; this is only  supported for any AFCCU printer with a SDLC attachment. This  may improve printer throughput when using low speed  communication lines such as 9.6 kbs.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW17625   Appendix F. PTF Cover Letter Data for Service Level SMC9618 134 ¤   SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Add the following changes to the PSF/MVS 2.2.0 System  Programming Guide (S544-3672):  ----------------------------------------------------------  On page 101, at the end of the first paragraph, add a new  sentence.  The Huffman compression algorithm cannot be used if  the AFCCU printer is attached to RPM2, RPM3, DPF,  or PSF Direct.  On page 125 after the fourth bullet, add another bullet  that states.  If the Huffman compression algorithm is being used, 38000  bytes per FSA will be required to perform the compression.  See page 231 for more information,  On page 212, at the end of the "Recover-from-Font-Not-Found  Flag Considerations" section, add a new section titled  "Huffman Compression Considerations"  You can use APSUX07 to indicate that PSF use the  Huffman compression algorithm to compress the data before  being sent to the printer by setting the XTP7HCA flag  in the initialization call.  Data compressed using the Huffman compression algorithm  can only be sent to those printers (SDLC attached)  which have the decompression microcode - AFCCU printers.  Data cannot be sent to AFCCU printers attached to  RPM2, RPM3, DPF, or PSF Direct.  For a description of the algorithm and information about  performance, see section "Transmission and Compression  of Data" on page 231 in Chapter 16, Understanding AFP  Performance.  The XTP7HCA flag defaults to B'0'. The default specifies  that PSF will not compress the IPDS data. If the flag is  set to B'1' and the printer is SDLC-attached,  then PSF will compress the IPDS data using  the Huffman compression algorithm. The flag can be set  during the INIT call, and it remains set between calls;  only APSUX07 can change the state of this flag.  On page 212, at the end of the page add the following  paragraph.  This call can be used to enable the compression of the  data sent to the printer using the Huffman compression  algorithm. See "Huffman Compression Considerations"  on page 212 for more information.  On page 231, change the title to "Transmission and  Compression of Data"  On page 231, change the first paragraph under the title  "Transmission and Compression of Line Data".  When PSF is driving a printer, compression of the  data sent to the printer may enhance the throughput  of the printer. There are two types  of compression that PSF itself can perform. One is line-data   Appendix F. PTF Cover Letter Data for Service Level SMC9618 135 ¤   only compression which can be activated by specifying the  optional COMPRESS keyword on the PRINTDEV statement or  the other is Huffman compression which  can be used to compress any type of data and is activated  by using Exit 7. Depending on the majority of data that  you plan on sending to the printer and the type of  printer (SDLC attached) you will be using will determine  the type of compression you use.  If possible, you may  want to try both separately to see which one gives you the  best results. See "Huffman Compression Considerations"  on page 212 for more on exit 7.  On page 231, under the "Transmission and Compression of  Line Data" section and after the last paragraph, add  the following paragraph.  Huffman compression may improve performance, because the  algorithm compresses on a byte-by-byte basis and  a different compression bit code is assigned to represent  each indivisible character in the uncompressed data.  The number of bits used to represent each uncompressed  character depends upon how frequently the character occurs  in the data to be compressed. Characters that occur  frequently are assigned short compression bit codes and  characters that occur less frequently are assigned longer  compression bit codes. The Huffman compression algorithm  can be used on any type of data (line data, MO:DCAÄÄP, image,  fonts, etc.). Data compressed using the Huffman algorithm  can only be sent to those printers (AFCCU - SDLC attached)  that contain the decompression microcode.  Data cannot be sent to those AFCCU printers attached to  RPM2, RPM3, DPF or PSF Direct.  Huffman compression may improve  printer throughput when the following conditions  are met:  o The printer is attached with a low-speed communications  line, for example, a 9.2 kbs line.  o Printer throughput is limited by the attachment.  o The arrangement of the data (occurrence and position)  is irregular, for example, text that has many  embedded blanks will do well.  On page 233 under the "PSF Direct, Distributed Print Function  (DPF), or Remote PrintManager (RPM) section, add the  following at the end of the first paragraph:  The Huffman compression algorithm cannot be used if the  AFCCU printer is attached to RPM2, RPM3, DPF, or PSF  Direct.  On page 236 under the "System Tuning" section, after the  last paragraph on the page, add the following.  Compressing Data using the Huffman algorithm: APSUX07  7 can be used to enable compression of data by PSF before  being sent to the printer. The data is compressed  on a byte-by-byte basis and a different compression  bit code is assigned to represent each indivisible  character in the uncompressed data. The number of bits   Appendix F. PTF Cover Letter Data for Service Level SMC9618 136 ¤   used to represent each uncompressed character depends  upon how frequently the character occurs  in the data to be compressed. Characters that occur  frequently are assigned short compression bit codes and  characters that occur less frequently are assigned longer  compression bit codes. The Huffman compression algorithm  can be used on any type of data (line data, MO:DCAÄÄP, image,  fonts, etc.).  Huffman compression may improve  printer throughput when the following conditions  are met:  o The printer is attached with a low-speed communications  line, for example, a 9.2 kbs line.  o Printer throughput is limited by the attachment.  o The arrangement of the data (occurrence and position)  is irregular, for example, text that has many  embedded blanks will do well.  The compression ratio varies considerably. It does best when  arrangement of the data (occurrence and position) is  irregular, for example, text that has many embedded  blanks or trailing blanks will do well. Double byte fonts  also do well. In general, you may get a compression ratio  of approximately 1.75-to-1, BUT the results will depend on  the characteristics of the print data.  Using Huffman compression may significantly increase the  number of CPU cycles that PSF requires. It may also  change PSF from being an I/O-bound process to being a  CPU-bound process. The cost-effectiveness of compression  depends upon a balance between the availability and cost  of additional host CPU cycles to perform compression and  the cost of additional communications bandwidth.  For maximum data transfer, remember to set the RU size.  On a clean line (retranmissions are infrequent)  choose the largest RU size as possible.  On page 238 after the last paragraph, add the following  paragraph.  If the Huffman compression algorithm is being used, 38000  bytes per FSA will be required to perform the compression.  On page 274, figure 70 (part 3 of 4) change the  following:  .... ..11 * RESERVED field to  .... ..1. XTP7HCA COMPRESS IPDS DATA USING THE  HUFFMAN COMPRESSION ALGORITHM  (VALID FOR INITIALIZATION  "XTP7INIT")  1 = COMPRESS IPDS DATA  0 = NO COMPRESSION  .... ...1 * RESERVED  On page 280, add the following after the paragraph  under XTP738MO:  XTP7HCA  This field is valid only on the INIT call. PSF  initially sets this field to B'0' to indicate that the  IPDS data will not be compressed. If APSUX07 sets   Appendix F. PTF Cover Letter Data for Service Level SMC9618 137 ¤   this field to B'1' and the printer is SDLC-attached,  then PSF will compress the IPDS  data using the Huffman compression algorithm.  On page 297, table 29 (page 1 of 2) add the following  entry after the XTP738MO entry:  XTP7HCA and under the INIT column add an IO.  Add the following changes to the PSF/MVS 2.2.0 Program  Directory (G544-3668):  ----------------------------------------------------------  Under Appendix A, section A.1 SMPMCS, figure 56,  add a ++MOD statement for each of the following new  modules, for example,  ++MOD (APSCHUFC) DISTLIB(AAPSMOD0) RELFILE(2).  The modules are: APSCHUFC, APSCHUFF, APSCSORT, APSVABND,  APSVBTCA, APSVCEE, APSVFREE, APSVGET, APSVHEAP,  APSVHFRE, APSVHGET, APSVHOTC, APSVHOTT, APSVHOTU,  APSVKJUM, APSVMEM, APSVSG03, APSVTOVF, APSVUNLD,  APSV4KGT  These modules are arranged alphabetically.  Under Appendix A, section A.2 JCLIN, figure 57,  add an include for  each of the following new modules, for example,  "INCLUDE AAPSMOD0(APSCHUFF)".  The modules are: APSCHUFC, APSCHUFF, APSCSORT, APSVABND,  APSVBTCA, APSVCEE, APSVFREE, APSVGET, APSVHEAP,  APSVHFRE, APSVHGET, APSVHOTC, APSVHOTT, APSVHOTU,  APSVKJUM, APSVMEM, APSVSG03, APSVTOVF, APSVUNLD,  APSV4KGT  These modules are arranged alphabetically.  On page 230, after the last entry (APRCONAZ) for the  ORDER statement APRBRSEX, DATA CONVERSION - INFREQUENT  and before the ENTRY APSPPIEP statement,  add the following ORDER statement.  ORDER APSCHFC1, (APSCHUFC)MODULES FOR HUFFMAN COMPRESS  APSCHFC2, (APSCHUFF CSECT NAME)  APSCSORT,  EDCXABND, (APSVABND CSECT NAME)  EDCXBTCA, (APSVBTCA CSECT NAME)  EDCXCEE, (APSVCEE CSECT NAME)  EDCXFREE, (APSVFREE CSECT NAME)  EDCXGET, (APSVGET CSECT NAME)  EDCXHEAP, (APSVHEAP CSECT NAME)  EDCXHFRE, (APSVHFRE CSECT NAME)  EDCXHGET, (APSVHGET CSECT NAME)  EDCXHOTC, (APSVHOTC CSECT NAME)  EDCXHOTT, (APSVHOTT CSECT NAME)  EDCXHOTU, (APSVHOTU CSECT NAME)  @@KJUMP, (APSVKJUM CSECT NAME)  EDCXMEM, (APSVMEM CSECT NAME)  CEESG003, (APSVSG03 CSECT NAME)  @@XTOVFN, (APSVTOVF CSECT NAME)  EDCXUNLD, (APSVUNLD CSECT NAME)  EDCX4KGT (APSV4KGT CSECT NAME)  Add the following changes to the PSF/MVS 2.2.0 Service   Appendix F. PTF Cover Letter Data for Service Level SMC9618 138 ¤   Diagnosis Guide (ZZ20-9713):  ----------------------------------------------------------  On page 21, under the Print Services Facility  subcomponent letters, add the following letter:  V C Services (interlanguage calls and C functions)  On page 22, Table 1 PSF Module Directory, add the  following module IDs and Module Descriptions in  the appropriate alphabetical order.  APSCHUFC PSF/MVS interface module to APSCHUFF  APSCHUFF Performs the Huffman compression  APSCSORT Used by APSCHUFF to perform sorting  APSVABND Generate an abend if internal error  APSVBTCA  APSVCEE  APSVFREE Returns storage to the operating system  APSVGET Gets storage from the operating system  APSVHEAP Manages heap storage  APSVHFRE Frees heap storage  APSVHGET Gets heap storage  APSCHOTC Establishes a persistent C environment without  accessing the C run-time libraries  APSCHOTT Terminates a persistent C environment  APSCHOTU Executes a C function from an assembler function  APSVKJUM  APSVMEM Contains built-in functions used for memory  management  APSVSG03  APSVTOVF  APSVUNLD Deletes named module from storage  APSV4KGT Gets page-aligned storage from the operating  system  ACTION:  If you have modified your source code for APSGEXTP  then save it before applying this PTF as this PTF will replace  your copy of APSGEXTP in the MACLIB.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APROUTEX OW17625  APSCABE OW17625  APSCADD OW17625  APSCBMGR OW17625  APSCCDEV OW17625  APSCCHE OW17625  APSCCLR OW17625  APSCCOMP OW17625  APSCESTA OW17625  APSCHUFC OW17625  APSCHUFF OW17625  APSCINFO OW17625  APSCINIT OW17625  APSCIPRT OW17625  APSCOPCI OW17625  APSCPCIA OW17625  APSCPRCT OW17625   Appendix F. PTF Cover Letter Data for Service Level SMC9618 139 ¤   APSCRDRV OW17625  APSCRSET OW17625  APSCSNA OW17625  APSCSNIO OW17625  APSCSORT OW17625  APSCSYNC OW17625  APSCTERM OW17625  APSCTPRT OW17625  APSCWRT OW17625  APSGAD31 OW17625  APSGDUMP OW17625  APSGEXTP OW17625  APSGFSSI OW17625  APSUREXT OW17625  APSVABND OW17625  APSVBTCA OW17625  APSVCEE OW17625  APSVFREE OW17625  APSVGET OW17625  APSVHEAP OW17625  APSVHFRE OW17625  APSVHGET OW17625  APSVHOTC OW17625  APSVHOTT OW17625  APSVHOTU OW17625  APSVKJUM OW17625  APSVMEM OW17625  APSVSG03 OW17625  APSVTOVF OW17625  APSVUNLD OW17625  APSV4KGT OW17625  HPRF220J OW17625  SGAPS4PP OW17625  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW17625 APROUTEX APSCABE APSCADD APSCBMGR APSCCDEV APSCCHE  APSCCLR APSCCOMP APSCESTA APSCHUFC APSCHUFF APSCINFO  APSCINIT APSCIPRT APSCOPCI APSCPCIA APSCPRCT APSCRDRV  APSCRSET APSCSNA APSCSNIO APSCSORT APSCSYNC APSCTERM  APSCTPRT APSCWRT APSGAD31 APSGDUMP APSGEXTP APSGFSSI  APSUREXT APSVABND APSVBTCA APSVCEE APSVFREE APSVGET  APSVHEAP APSVHFRE APSVHGET APSVHOTC APSVHOTT APSVHOTU  APSVKJUM APSVMEM APSVSG03 APSVTOVF APSVUNLD APSV4KGT  HPRF220J SGAPS4PP  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APROUTEX  APSCABE  APSCADD  APSCBMGR  APSCCDEV  APSCCHE   Appendix F. PTF Cover Letter Data for Service Level SMC9618 140 ¤   APSCCLR  APSCCOMP  APSCESTA  APSCHUFC  APSCHUFF  APSCINFO  APSCINIT  APSCIPRT  APSCOPCI  APSCPCIA  APSCPRCT  APSCRDRV  APSCRSET  APSCSNA  APSCSNIO  APSCSORT  APSCSYNC  APSCTERM  APSCTPRT  APSCWRT  APSGAD31  APSGDUMP  APSGFSSI  APSUREXT  APSVABND  APSVBTCA  APSVCEE  APSVFREE  APSVGET  APSVHEAP  APSVHFRE  APSVHGET  APSVHOTC  APSVHOTT  APSVHOTU  APSVKJUM  APSVMEM  APSVSG03  APSVTOVF  APSVUNLD  APSV4KGT  MACROS  APSGEXTP  SGAPS4PP  LISTEND  */.   F.6 COVER LETTER FOR PTF UW24497    Appendix F. PTF Cover Letter Data for Service Level SMC9618 141 ¤   PROBLEM DESCRIPTION(S):  OW15018 -  ****************************************************************  * USERS AFFECTED: Users of PSF/MVS 2.2.0 who want printer *  * sharing functions *  ****************************************************************  * PROBLEM DESCRIPTION: 1. PSF/MVS does not support the VTAM *  * RELREQ function. This was requested *  * by PASR number R008939. *  * *  * 2. Some new printers allow multiple, *  * simultaneous host drivers, both IPDS *  * and PCL/PostScript. An example is the *  * IBM D/T3130 with the Release 2 micro- *  * code. New support is required in PSF *  * to use this printer capability. *  * *  * 3. When an error occurs during printer *  * initialization, a loop may occur where *  * the printer continually reports Unit *  * Check. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  New printer sharing methods are needed.  The Unit Check error loop during printer initialization occurs  if the printer continues to report Unit Check when PSF sends a  NOP to attempt to retrieve all the errors the printer has  queued.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW15018  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Change the PSF/MVS System Programming Guide, S544-3672-02:  In Chapter 6, PRINTDEV Parameters,  add or replace the following keyword descriptions:  Ú--------------------------------------------------------------¿  | Parameter| Description |  |----------Å---------------------------------------------------|  | ACQINTV | Specifies the acquire interval in seconds. |  |(optional)| This is the time period between releasing a |  | | printer and attempting to acquire it again. |  | | ACQINTV is used only when RELMODE=TIME. |  | | |  | | Syntax: ACQINTV=nn nn=0-86400 default=0 |  |----------Å---------------------------------------------------|  | CONNINTV | Specifies the connect interval in seconds. |  |(optional)| This is the time limit for an attempt to start a |  | | session or dialog with a printer. |  | | When the connect interval expires before |   Appendix F. PTF Cover Letter Data for Service Level SMC9618 142 ¤   | | connection is complete, PSF will issue a message |  | | and end the FSA. |  | | If CONNINTV is not specified or CONNINTV=0, PSF |  | | will attempt to connect for an unlimited period |  | | of time. |  | | |  | | For SNA, the connect interval is used when |  | | queueing a session request after a busy or not |  | | available condition. |  | | |  | | For TCP/IP, the connect interval is used when |  | | restarting the session after any retriable |  | | error condition. |  | | |  | | For IPDS dialogs, the connect interval is used |  | | when restarting a dialog after it has been |  | | released (RELMODE=IDLE|TIME). |  | | |  | | Syntax: CONNINTV=nn nn=0-86400 |  |----------Å---------------------------------------------------|  | DISCINTV | Specifies the disconnect interval in seconds. |  |(optional)| When no output is available from JES for this |  | | time period, PSF ends the session with the |  | | printer. PSF ensures that all pages from the last |  | | job reach the stacker before ending the session |  | | and allowing that job to be purged from the spool.|  | | |  | | If DISCINTV=0, PSF does not end the printer |  | | session because of a lack of output. (See note 2 |  | | for additional information.) |  | | |  | | If RELMODE=IDLE or TIME, DISCINTV is ignored. |  | | See "Printer Sharing in the MVS Environment" |  | | following this table for more information. |  | | |  | | Syntax: DISCINTV=nnn nnn=0-86400 |  | | |  | | Notes: |  | | 1. DISCINTV is used only for SNA-attached or |  | | TCP/IP-attached printers. |  | | |  | | 2. Some printers have a network inactivity timer. |  | | If the timer is enabled, the DISCINTV value |  | | must be less than that of the inactivity |  | | timer and greater than 0. Otherwise PSF abends |  | | when the inactivity timer expires. |  | | |  | | 3. When some printers (such as the 3820) become |  | | inoperative, a local intervention timer is |  | | started. When the timer expires, an action |  | | code X'22' negative acknowledgmemt (NACK) is |  | | sent to PSF. PSF then issues message APS923I |  | | and performs the action specified in the |  | | FAILURE parameter. If the system operator does |   Appendix F. PTF Cover Letter Data for Service Level SMC9618 143 ¤   | | not need this message, you can disable the |  | | timer. PSF then waits for the printer operator |  | | to correct the problem. |  |----------Å---------------------------------------------------|  | FAILURE | Specifies PSF action after failure to establish |  |(optional)| a SNA or TCP/IP session with printers that are |  | | busy or not enabled. If FAILURE=STOP, PSF must be |  | | restarted by an operator command. |  | | If FAILURE=WCONNECT and the printer is connected |  | | to another host when PSF attempts to establish |  | | connection, PSF will wait for the printer (up to |  | | the time specified by CONNINTV) as follows: |  | | For SNA, PSF will queue a session request in VTAM |  | | which will respond when the printer becomes |  | | available. |  | | For TCP/IP, PSF will continuously retry until the |  | | printer becomes available. |  | | |  | | Syntax: FAILURE=STOP|WCONNECT default=WCONNECT |  |----------Å---------------------------------------------------|  | RELINTV | Specifies the release interval in seconds. |  |(optional)| This is the time period after which a request |  | | to release the printer is honored. |  | | The timer for the release interval is not begun |  | | until PSF is at the next job boundary. |  | | |  | | Syntax: RELINTV=nn nn=0-86400 default=0 |  |----------Å---------------------------------------------------|  | RELMODE | Specifies the manner in which PSF will respond to |  |(optional)| a request to release the printer. A request to |  | | release a printer can be either an IPDS release |  | | dialog request or a VTAM release session request. |  | | See "Printer Sharing in the MVS Environment" |  | | following this table for more information. |  | | |  | | Syntax: RELMODE=IDLE|TIME|NONE |  | | |  | | IDLE specifies release the printer when a request |  | | to release has been received and there is no |  | | output on the spool for this printer for the time |  | | specified by the release interval. |  | | |  | | TIME specifies begin the release interval when a |  | | request to release has been received even when |  | | there is more output on the spool. |  | | |  | | NONE specifies do not release the printer. This |  | | is the default. |  À--------------------------------------------------------------Ù  In Chapter 6, replace the section titled "Printer Sharing in the  MVS Environment" with the following:  Printer Sharing in the MVS Environment  For network attached printers, PSF/MVS supports sharing  of printers with other print drivers by three different   Appendix F. PTF Cover Letter Data for Service Level SMC9618 144 ¤   methods:  1. JES Spool Driven  2. VTAM RELREQ  3. Port Switching  PSF will release a printer only at the end of a job so that  job output is never split.  I. JES Spool Driven  This method is valid for SNA or TCP/IP attached printers.  A session with the printer is maintained while there is  output on the JES spool and the printer is available.  When there is no more output on the spool and the disconnect  interval expires, PSF ends the session with the printer.  PSF will attempt to restart the session when there is more  work on the spool for this printer.  After the session is restarted, PSF must reload the resources  required for following print jobs.  With this method, there is no means for PSF to determine if  another print driver is active.  This method is requested by specifying the following  PRINTDEV parameters:  ù MGMTMODE=OUTAVAIL  ù DISCINTV=nn  ù TIMEOUT=REDRIVE  ù FAILURE=WCONNECT  II. VTAM RELREQ  This method is valid only for SNA attached printers. A ses-  sion with printer is maintained until VTAM indicates that  another print driver in the VTAM network has requested a  session with the printer. The session with the printer is  then ended according to the RELMODE specified. After the  session is restarted, PSF must reload any resources required  for following print jobs.  If RELMODE=IDLE, PSF will end the session when a VTAM re-  quest to release has been received and there is no output on  the spool for the printer for the time specified by the re-  lease interval. PSF will attempt to restart the session  when there is more work on the spool for this printer.  This method is requested by specifying the following  PRINTDEV parameters:  ù MGMTMODE=OUTAVAIL  ù RELMODE=IDLE  ù RELINTV=nn  If RELMODE=TIME, when a VTAM request to release is received  PSF will wait for the time specified by the release interval  and then end the session. PSF will attempt to restart the  session when the acquire interval expires based on the  MGMTMODE specified.  This method is requested by specifying the following  PRINTDEV parameters:  ù RELMODE=TIME  ù RELINTV=nn  ù ACQINTV=nn  III. Port Switching  This method is valid for printers which support multiple ac-   Appendix F. PTF Cover Letter Data for Service Level SMC9618 145 ¤   tive ports (i.e. 3130, release 2). Currently, these print-  ers support only SNA or TCP/IP attachment. One of these  printers can be in session with multiple print drivers si-  multaneously. Control of the print mechanism is passed be-  tween the ports by means of an IPDS "dialog". When an IPDS  print driver starts a dialog with the printer, it has con-  trol of the print mechanism and can continue to print until  it ends its dialog. This is the most efficient printer  sharing method because print resources are retained in the  printer while the printer is switched to another port.  When the printer indicates that another port has requested  control, PSF will end its dialog according to the RELMODE  specified.  If RELMODE=IDLE, PSF will end the dialog when an IPDS re-  quest to release has been received and there is no output on  the spool for the printer for the time specified by the re-  lease interval. PSF will attempt to restart the dialog when  there is more work on the spool for this printer.  This method is requested by specifying the following  PRINTDEV parameters:  ù RELMODE=IDLE  ù RELINTV=nn  If RELMODE=TIME, when an IPDS request to release is received  PSF will wait for the time specified by the release interval  and then end the dialog. PSF will attempt to restart the  dialog when the acquire interval expires.  This method is requested by specifying the following  PRINTDEV parameters:  ù RELMODE=TIME  ù RELINTV=nn  ù ACQINTV=nn  Note: When a release or acquire interval of 0 is specified,  the related action is taken immediately.  ----------------------------------------------------------------  Change the PSF/MVS Messages and Codes, S544-3675-02:  In Chapter 1, add the following messages:  APS936I COMMUNICATION WITH SNA-ATTACHED PRINTER(prtnnnn)  LUNAME(luname) WAS TERMINATED DUE TO A RELEASE REQUEST  FROM VTAM.  EXPLANATION: Communication with PRINTER (prtnnnn) was ended  after VTAM indicated that another print driver queued a session  request for the printer and the release interval (RELINTV)  expired. PRINTER (prtnnnn) specifies the name of the PRINTDEV  statement defining this printer. LUNAME (luname) specifies  the SNA logical unit name of the SNA-attached printer.  SYSTEM ACTION: Communication with the SNA-attached printer is  ended. PSF attempts to restart the session with the printer  according to the management mode (MGMTMODE) specified on the  PRINTDEV statement.  USER RESPONSE: No response is necessary.  SYSTEM PROGRAMMER RESPONSE: If this message appears too  frequently, consider increasing the amount of time specified in  the RELINTV parameter on the PRINTDEV statement in the procedure  used to start PSF. For information on printer sharing, refer to   Appendix F. PTF Cover Letter Data for Service Level SMC9618 146 ¤   Print Services Facility/MVS: System Programming Guide.  OPERATOR RESPONSE: If this message appears frequently, inform  your system programmer.  PROBLEM DETERMINATION: Items 1, 17, 19.  ----------------------------------------------------------------  APS937I IPDS DIALOG WITH PRINTER(prtnnnn) WAS ENDED DUE TO A  RELEASE REQUEST FROM THE PRINTER.  EXPLANATION: The IPDS dialog with PRINTER (prtnnnn) was ended  after a release request (NACK) was received from the printer and  the release interval (RELINTV) expired. PRINTER (prtnnnn)  specifies the name of the PRINTDEV statement defining this  printer.  SYSTEM ACTION: Communication with the printer is suspended  temporarily. PSF attempts to restart the dialog with the  printer according to the release mode (RELMODE) specified on the  PRINTDEV statement. When the release mode is IDLE, the dialog  is restarted when there is another data set for the printer on  the JES spool. When the release mode is TIME, the dialog  is restarted after the acquire interval (ACQINTV) expires.  USER RESPONSE: No response is necessary.  SYSTEM PROGRAMMER RESPONSE: If this message appears too  frequently, consider increasing the amount of time specified in  the RELINTV (and the ACQINTV if RELMODE=TIME) parameter on the  PRINTDEV statement in the procedure used to start PSF. For  information on printer sharing, refer to Print Services  Facility/MVS: System Programming Guide.  OPERATOR RESPONSE: If this message appears frequently, inform  your system programmer.  PROBLEM DETERMINATION: Items 1, 17, 19.  ----------------------------------------------------------------  APS938I IPDS DIALOG WITH PRINTER(prtnnnn) WAS RESTARTED.  EXPLANATION: The IPDS dialog with PRINTER (prtnnnn) had been  suspended and is now restarted. PRINTER (prtnnnn) specifies the  name of the PRINTDEV statement defining this printer.  SYSTEM ACTION: Communication with the printer continues.  USER RESPONSE: No response is necessary.  SYSTEM PROGRAMMER RESPONSE: No response is necessary. For  information on printer sharing, refer to Print Services  Facility/MVS: System Programming Guide.  OPERATOR RESPONSE: No response is necessary.  ----------------------------------------------------------------  APS939I STARTUP OF COMMUNICATION WITH PRINTER (prtnnnn) WAS  ABORTED DUE TO A CONNECT INTERVAL TIMEOUT.  EXPLANATION: PSF attempted to start a session or dialog with  the printer for the period of time specified by the connect  interval (CONNINTV). The printer was busy or unavailable for  this period of time. PRINTER (prtnnnn) specifies the name of  the PRINTDEV statement defining this printer.  SYSTEM ACTION: The PSF FSA for the printer is terminated via an  abend 024 RC E20.  USER RESPONSE: No response is necessary.  SYSTEM PROGRAMMER RESPONSE: If this message appears too  frequently, consider increasing the amount of time specified in  the CONNINTV parameter on the PRINTDEV statement in the   Appendix F. PTF Cover Letter Data for Service Level SMC9618 147 ¤   procedure used to start PSF.  OPERATOR RESPONSE: If this message appears frequently, inform  your system programmer.  PROBLEM DETERMINATION: Items 1, 17, 19.  ----------------------------------------------------------------  In Chapter 2, add the following PSF Abend Reason Code:  02E7  EXPLANATION: This abend is issued by module APSCCTIM--  The STIMERM macro failed to set a timer.  SYSTEM ACTION: PSF processing terminates abnormally.  SYSTEM PROGRAMMER RESPONSE: Refer to your operating system  publication that explains system macros to determine why the  macro failed.  ----------------------------------------------------------------  On page 284, change PSF abend reason code 2EE to now read:  2EE  EXPLANATION: This abend is issued by module APSCSNIO -- The  APSCSNIO SENSEID function was unable to successfully complete  its function. The printer did not respond to the first PSF  IPDS command (STM). The SNA or TCP/IP connection may have  failed or a printer hardware error may be the cause. No IPDS  information on the reason for the failure is available.  SYSTEM ACTION: PSF attempts to recover from this abend by  restarting. Message APS057I is issued if PSF successfully  restarts.  SYSTEM PROGRAMMER RESPONSE: This abend indicates a possible  printer hardware error. Correct any problems indicated on the  printer operator panel. Correct any outstanding intervention  conditions at the printer. Verify that a good network path  exists to the printer. Re-IML the printer. If the problem  persists, contact your systems engineer for assistance  regarding this error.  ----------------------------------------------------------------  Add the following PSF Abend Reason Codes:  0605  EXPLANATION: This abend is issued by module APSERRM--  It indicates that the printer is reporting a unit check  in response to the IPDS NOP command.  SYSTEM ACTION: PSF processing terminates abnormally.  SYSTEM PROGRAMMER RESPONSE: This PSF abend could indicate a  printer microcode logic error, however most likely it is due  to communication problems between PSF and the printer usually  caused by a channel protocol/speed mismatch. Verify that the  CNTLUNIT PROTOCL statement matches the protocol for which the  printer is configured.  ----------------------------------------------------------------  0E20  EXPLANATION: This abend is issued by module APSCCTME--  The acquire interval timer expired before connection with the  printer was successful.  SYSTEM ACTION: PSF issues message APS939I. PSF processing  terminates abnormally.  SYSTEM PROGRAMMER RESPONSE: See message APS939I.  ----------------------------------------------------------------   Appendix F. PTF Cover Letter Data for Service Level SMC9618 148 ¤   Changes to LH40-0205-01 "PSF/MVS Diagnosis Guide and Reference"  In appendix A, "Message-to-Module Cross Reference", add:  Ú-----------------------------¿  | Message | Modules |  |-----------------------------|  | APS936I | APSCCLR |  |-----------------------------|  | APS937I | APSCCLR |  |-----------------------------|  | APS938I | APSCCLR |  |-----------------------------|  | APS939I | APSCCTME |  À-----------------------------Ù  DEPENDENCY:  This PTF can be applied without any software prerequisites.  The new PRINTDEV keywords ACQINTV, CONNINTV, RELINTV, and  RELMODE require MVS/ESA 4.3.0 or later and the MVS Scheduler  APAR OW16442.  The Port Switching function of the D/T3130 requires the Release  2 microcode or Feature 4810 or 4815.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APROUTEX OW15018  APSCADD OW15018  APSCCLR OW15018  APSCCTIM OW15018  APSCCTME OW15018  APSCINFO OW15018  APSCINIT OW15018  APSCSNA OW15018  APSCSTMI OW15018  APSCTCP OW15018  APSCTPRT OW15018  APSEATCD OW15018  APSEMSG OW15018  APSERRM OW15018  APSGAD31 OW15018  APSGDUMP OW15018  APSJCL OW15018  APSJCLI OW15018  APSKDVP OW15018  APSKFSA OW15018  APSMSTXT OW15018  APSNLINK OW15018  APSPEFSA OW15018  APSPPCNP OW15018  APSPPDCM OW15018  APSPPDSP OW15018  APSPPDVP OW15018  APSPPFSA OW15018  APSPPGDS OW15018  APSPPIFA OW15018  APSPPNPR OW15018  APSPPNST OW15018   Appendix F. PTF Cover Letter Data for Service Level SMC9618 149 ¤   APSPPODR OW15018  APSQDEQ OW15018  HPRF220J OW15018  IGE0000E OW15018  SGAPS4PP OW15018  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW15018 APROUTEX APSCADD APSCCLR APSCCTIM APSCCTME APSCINFO  APSCINIT APSCSNA APSCSTMI APSCTCP APSCTPRT APSEATCD  APSEMSG APSERRM APSGAD31 APSGDUMP APSJCL APSJCLI  APSKDVP APSKFSA APSMSTXT APSNLINK APSPEFSA APSPPCNP  APSPPDCM APSPPDSP APSPPDVP APSPPFSA APSPPGDS APSPPIFA  APSPPNPR APSPPNST APSPPODR APSQDEQ HPRF220J IGE0000E  SGAPS4PP  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APROUTEX  APSCADD  APSCCLR  APSCCTIM  APSCCTME  APSCINFO  APSCINIT  APSCSNA  APSCSTMI  APSCTCP  APSCTPRT  APSEATCD  APSEMSG  APSERRM  APSGAD31  APSGDUMP  APSJCL  APSJCLI  APSKDVP  APSKFSA  APSMSTXT  APSNLINK  APSPEFSA  APSPPCNP  APSPPDCM  APSPPDSP  APSPPDVP  APSPPFSA  APSPPGDS  APSPPIFA  APSPPNPR  APSPPNST  APSPPODR  APSQDEQ  IGE0000E   Appendix F. PTF Cover Letter Data for Service Level SMC9618 150 ¤   MACROS  SGAPS4PP  LISTEND  */.   F.7 COVER LETTER FOR PTF UW24258   PROBLEM DESCRIPTION(S):  OW12092 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1 and 2.2.0 users. *  ****************************************************************  * PROBLEM DESCRIPTION: 1) On non-PSF abend codes, PSF over- *  * writes the reason code in the SDWA. *  * 2) PSF does not set the failing module *  * name in the dump title to the real *  * module name when it is known. *  * 3) When modules with a name starting *  * with APR abend, the module name and *  * CSECT name in the SDWA are set *  * to UNKNOWN. *  * 4) The PSF abending module name is *  * not known from PSF console messages *  * alone. *  * 5) The reason code for non-PSF abend *  * codes is set to UNKN in the dump *  * title. *  * 6) APAR OW08453 causes all PPCC abends *  * (completion code 0A6) to not *  * generate a dump, even when they *  * should. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  1) PSF is overwriting the abend reason code in the SDWA on non-  PSF abend codes.  2) PSF always sets the name of the failing module in the dump  title to the name of the ESTAE.  3) PSF does not gather some information when PSF modules whose  names start with APR abend.  4) The PSF MSGAPS050I and MSGAPS055I messages do not include  the abending module name when it is known to the ESTAE.  5) The abend reason code for non-PSF abend reason codes in the  dump title is UNKN, not the reason code from the SDWA.  6) The PSF ESTAE is suppressing dumps for abends with all abends  with an abend code of 0A6.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW12092  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994   Appendix F. PTF Cover Letter Data for Service Level SMC9618 151 ¤   LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  The 'PSF/MVS Messages and Codes' manual (S544-3675-02) is  updated as follows:  On page 10, change the message text for APS050I to the  following:  APS050I SYSTEM COMPLETION CODE system completion code, PSF ABEND  REASON CODE reason code, HAS BEEN DETECTED BY estae  name, ISSUED BY MODULE abending module name.  On page 11, change the message text for APS055I to the  following:  APS055I PSF ESTAE CANNOT EVALUATE SYSTEM COMPLETION CODE system  completion code ISSUED BY MODULE abending module name.  ABNORMAL TERMINATION PROCESSING WILL CONTINUE.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSMSTXT OW12092  APSPEFSA OW12092  APSPEFSS OW12092  APSPENST OW12092  APSPPATR OW12092  APSZESTI OW12092  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW12092 APSMSTXT APSPEFSA APSPEFSS APSPENST APSPPATR APSZESTI  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APSMSTXT  APSPEFSA  APSPEFSS  APSPENST  APSPPATR  APSZESTI  LISTEND  */.   F.8 COVER LETTER FOR PTF UW13461   PROBLEM DESCRIPTION(S):  OW09290 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1 and 2.2.0 users. *  ****************************************************************  * PROBLEM DESCRIPTION: When a restartable PSF abend occurs *  * during FSA initialization, the restart *  * of the FSA will fail with an ABEND0C1 *  * in IAZFSIT if the FSI Connect FSA was *  * not done before the abend. *  ****************************************************************   Appendix F. PTF Cover Letter Data for Service Level SMC9618 152 ¤   * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  Abend restart is attempted without checking if the FSA  initialization is complete.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW09290  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  The following publication changes are required:  LH40-0205-00 "PSF/MVS Diagnosis Guide and Reference"  ----------------------------------------------------  page 22  add X'2BA' to the RESTARTABLE ABEND CODES table.  S544-3675-01 "PSF/MVS Messages and Codes Version 2.1.1"  -------------------------------------------------------  page 244  change the entry for abend reason code "02BA" as follows  02BA  Explanation: This abend issued by module APSCCOMP -  APSCCOMP detected a protocol error. PPCC indicated that  the printer or controller recovered incorrectly from an  intervention required condition at the printer. The SNA  level recovery (sending -rsp 0802) was done without first  sending the required IPDS NACK. The IPDS NACK is required  for PSF to reposition correctly. Examples of intervention  required conditions include paper jams and out of paper.  System Action: PSF attempts to recover from this abend by  restarting. Message APS057I is issued if PSF successfully  restarts.  System Programmer Response: This PSF abend reason code indicates  a logic error in either the microcode of the printer or the  SNA controller. Contact your hardware service representative.  This is NOT a PSF logic error.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSPEFSA OW09290  APSPPDVP OW09290  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW09290 APSPEFSA APSPPDVP  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APSPEFSA  APSPPDVP  LISTEND  */.    Appendix F. PTF Cover Letter Data for Service Level SMC9618 153 ¤   F.9 COVER LETTER FOR PTF UW14560   PROBLEM DESCRIPTION(S):  OW07536 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1 and 2.2.0 users who *  * use the external trace function. *  ****************************************************************  * PROBLEM DESCRIPTION: APSGDUMP MAY LOOP TRYING TO OBTAIN DCX *  * LOCK AT OFFSET X'9A' IF PSF/MVS *  * EXTERNAL TRACE IS ACTIVE. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  If PSF/MVS trace code is executing when an abnormal termination  occurs, subsequent tracing from the ESTAE waits infinitely for  the terminated tracing to complete.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW07536  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  The 'Print Services Facility/MVS: Diagnosis Guide and Reference'  (LH40-0205-00) will have the following note added to page 45  under the description of the FORCE parameter of the MODIFY  command:  Note: If the FSA is tracing to an external trace data set when  this command is issued, a C03 system abend may result for  the trace data set when the FSS address space is  terminated.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSGTROC OW07536  APSPEFSA OW07536  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW07536 APSGTROC APSPEFSA  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APSGTROC  APSPEFSA  LISTEND  */.   F.10 COVER LETTER FOR PTF UW19699    Appendix F. PTF Cover Letter Data for Service Level SMC9618 154 ¤   PROBLEM DESCRIPTION(S):  OW13171 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users who are using *  * direct-printing mode, who do *  * not use channel extenders, *  * who are not attached to a D/T3800, *  * and who wish to verify the received page *  * counter to ensure that it is being *  * incremented correctly by the printer. *  ****************************************************************  * PROBLEM DESCRIPTION: The OEM printer was losing data *  * and was not *  * informing PSF that data was being lost. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  The OEM printer was losing data and was not detecting the loss  and not informing PSF that data was being lost. When the  OEM printer was losing data, it  was not incrementing the received page  counter even though it had received another page from PSF.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW13171  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  In the Print Services Facility/MVS Messages and Codes Version 2  Release 2 Modification 0 (S544-3675-02) on page 283 add the  following new abend reason code after abend reason code 2E5.  02E6  Explanation: This abend is issued by module  APSCPRCT--  APSCPRCT detected that the received page counter from the  printer was not incremented by 1.  System Action: PSF processing terminates abnormally.  System Programmer Response: This PSF abend reason code  indicates a possible logic error within the microcode  of the printer. Contact your service representative in the  IBM support center or use your electronic link with IBM  service for assistance regarding this error code.  Some channel extenders do not increment  the received page counter for performance reasons. If you  are using channel extenders, check  with your OEM channel extender vendor before setting  XTP16RPC.  In the Print Services Facility/MVS System Programming Guide  Version 2 Release 2 Modification 0 (S544-3672-02) make the  following changes.  1. On page 222 under "Begin-Data-Set Call (BDSC)" add the  following paragraph after the paragraph that begins  "If the bit labeled XTP16MRK....".   Appendix F. PTF Cover Letter Data for Service Level SMC9618 155 ¤   Use XTP16RPC to request that PSF verify that the  received page counter has been incremented by 1 for  each page that was sent to the printer. This is the only  call that can be used to verify the received page counter.  If the bit labeled XTP16RPC is set in the APSUXP16 control  block, PSF will abend if the received page counter has  not been incremented by 1 for each page that was sent to  the printer. This bit is ignored if attached to a 3800  printer. *** WARNING *** SOME CHANNEL EXTENDERS DO NOT  INCREMENT THE RECEIVED PAGE COUNTER FOR PERFORMANCE  REASONS. CHECK WITH YOUR OEM CHANNEL EXTENDER VENDOR BEFORE  SETTING XTP16RPC.  2. On page 222 under "Output for APSUX16 Begin-Data-Set Call"  add the following after "XTP16MRK".  XTP16RPC Received page counter flag  ACTION:  If you have modified your source for APSUXP16, then save it  before applying this PTF as this PTF will replace your copy of  APSUXP16.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APROUTEX OW13171  APSCADD OW13171  APSCPRCT OW13171  APSUEXIT OW13171  APSUXP16 OW13171  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW13171 APROUTEX APSCADD APSCPRCT APSUEXIT APSUXP16  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APROUTEX  APSCADD  APSCPRCT  APSUEXIT  MACROS  APSUXP16  LISTEND  */.   F.11 COVER LETTER FOR PTF UW21345     Appendix F. PTF Cover Letter Data for Service Level SMC9618 156 ¤   PROBLEM DESCRIPTION(S):  OW15599 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users requiring TCP/IP- *  * attached IPDS printer support and/or I-data *  * 7913 IPDS LAN attachment device support. *  ****************************************************************  * PROBLEM DESCRIPTION: New function support of TCP/IP-attached *  * IPDS printers and I-data 7913 IPDS LAN *  * attachment device. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  PSF/MVS 2.2.0 did not support any TCP/IP IPDS attached devices.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW15599  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  In the Print Services Facility/MVS Messages and Codes  Version 2 Release 1 Modification 1 manual (S544-3675-01)  under APS923I under "EXPLANATION" add the 5 new  conditions to the bulleted list of conditions.  o Fuser oil supply empty  o Developer mix needs changing  o Oiler felt needs changing  o Toner collector full  o Fine filter needs changing  DOCUMENTATION:  Change the Print Services Facility/MVS Diagnosis Guide and  Reference,LH40-0205-00:  In Appendix C, PSF Reason Codes and Return Codes,  On page 61,  insert after X'02061500'  X'02160802' - Intervention and recovery reported on SNA, retry  now possible (APSCSNA).  DOCUMENTATION:  PSF/MVS, IBM IPDS printers and the I-data 7913 IPDS LAN  attachment device use an IBM application layer protocol for  transmitting IPDS data. This protocol does not support FTP or  LPR.  PSF/MVS 2.2.0 support of TCP/IP attached printers requires that  the IPADDR keyword be added to the printdev of each TCP/IP  attached printer. An example coding of this keyword might be:  IPADDR='9.99.12.33'. Note that the quotes around the IP address  are required.  The MGMTMODE, DISCINTV, and TIMEOUT printdev keywords are  supported identically as with an SNA attached printer.  APSWPROT is the sample writer procedure supplied with this apar  and is placed in PROCLIB during the application of this PTF.  The KEEPALIVE value should be configured in the TCP/IP profile.  Set the KEEPALIVE value to an acceptable time that can expire   Appendix F. PTF Cover Letter Data for Service Level SMC9618 157 ¤   before PSF/MVS is notified that the printer or 7913 has been  powered off. The KEEPALIVE value is the number of minutes to  wait between KEEPALIVE probes sent by TCP/IP to a device. If  there is no response, TCP/IP will notify PSF/MVS, resulting in  an APS934I message.  The following is an example of the KEEPALIVEOPTION coded in  the TCP/IP profile:  KEEPALIVEOPTIONS INTERVAL 10 SENDGARBAGE TRUE  ENDKEEPALIVEOPTIONS  See the IBM TCP/IP for MVS Customization and Administration  Guide for details on coding this statement.  A complete update guide will be available in the future. The  order number for the update guide is G544-3984-01.  DOCUMENTATION:  PSF/MVS, IBM IPDS printers and the I-data 7913 IPDS LAN  attachment device use an IBM application layer protocol for  transmitting IPDS data. This protocol does not support FTP or  LPR.  PSF/MVS 2.2.0 support of TCP/IP attached printers requires that  the IPADDR keyword be added to the printdev of each TCP/IP  attached printer. An example coding of this keyword might be:  IPADDR='9.99.12.33'. Note that the quotes around the IP address  are required.  The MGMTMODE, DISCINTV, and TIMEOUT printdev keywords are  supported identically as with an SNA attached printer.  APSWPROT is the sample writer procedure supplied with this apar  and is placed in PROCLIB during the application of this PTF.  The KEEPALIVE value should be configured in the TCP/IP profile.  Set the KEEPALIVE value to an acceptable time that can expire  before PSF/MVS is notified that the printer or 7913 has been  powered off. The KEEPALIVE value is the number of minutes to  wait between KEEPALIVE probes sent by TCP/IP to a device. If  there is no response, TCP/IP will notify PSF/MVS, resulting in  an APS934I message.  The following is an example of the KEEPALIVEOPTION coded in  the TCP/IP profile:  KEEPALIVEOPTIONS INTERVAL 10 SENDGARBAGE TRUE  ENDKEEPALIVEOPTIONS  See the IBM TCP/IP for MVS Customization and Administration  Guide for details on coding this statement.  A complete update guide will be available in the future. The  order number for the update guide is G544-3984-01.  ACTION:  The following lists installation requirements for PSF/MVS 2.2.0  to support TCP/IP attached printers and/or I-data 7913 IPDS LAN  attachment device.  TCP/IP must be Version 3 Release 1 or higher, with the  applicable TCP/IP performance ptfs applied.  PSF/MVS 2.2.0 support of TCP/IP attached printers requires that  the TCP/IP address space name be 'TCPIP'. Otherwise, PSF/MVS  will not be able to establish an interface with TCP/IP.  The MVS scheduler apar OW12236 must be applied for MVS levels  at or below MVS 5.1.0 to pick up the IPADDR keyword support.  The TCP/IP attached printer must be defined to JES and MVS as   Appendix F. PTF Cover Letter Data for Service Level SMC9618 158 ¤   specified in the PSF/MVS 2.2.0 System Programming Guide. SNA  printer definition examples in the System Programming Guide  also provide excellent examples for defining TCP/IP attached  printers. Don't use APPLID, LOGMODE and/or LUNAME, use IPADDR  instead.  Note that the I-data 7913 IPDS LAN attachment device must get  its configuration information using the BOOTP protocol. The  configuration information can be saved but must be downloaded  at least once.  The BOOTP protocol is available only on OS/2 or AIX systems.  ACTION:  The following lists installation requirements for PSF/MVS 2.2.0  to support TCP/IP attached printers and/or I-data 7913 IPDS LAN  attachment device.  TCP/IP must be Version 3 Release 1 or higher, with the  applicable TCP/IP performance ptfs applied.  PSF/MVS 2.2.0 support of TCP/IP attached printers requires that  the TCP/IP address space name be 'TCPIP'. Otherwise, PSF/MVS  will not be able to establish an interface with TCP/IP.  The MVS scheduler apar OW12236 must be applied for MVS levels  at or below MVS 5.1.0 to pick up the IPADDR keyword support.  The TCP/IP attached printer must be defined to JES and MVS as  specified in the PSF/MVS 2.2.0 System Programming Guide. SNA  printer definition examples in the System Programming Guide  also provide excellent examples for defining TCP/IP attached  printers. Don't use APPLID, LOGMODE and/or LUNAME, use IPADDR  instead.  Note that the I-data 7913 IPDS LAN attachment device must get  its configuration information using the BOOTP protocol. The  configuration information can be saved but must be downloaded  at least once.  The BOOTP protocol is available only on OS/2 or AIX systems.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APROUTEX OW15599  APSCABE OW15599  APSCADD OW15599  APSCBMGR OW15599  APSCCDEV OW15599  APSCCHE OW15599  APSCCLR OW15599  APSCCOMP OW15599  APSCESTA OW15599  APSCINFO OW15599  APSCINIT OW15599  APSCIPRT OW15599  APSCOPCI OW15599  APSCPCIA OW15599  APSCPRCT OW15599  APSCRDRV OW15599  APSCRSET OW15599  APSCSNA OW15599  APSCSNIO OW15599  APSCSYNC OW15599   Appendix F. PTF Cover Letter Data for Service Level SMC9618 159 ¤   APSCTCP OW15599  APSCTERM OW15599  APSCTPRT OW15599  APSCWRT OW15599  APSECUR OW15599  APSEMSG OW15599  APSERRM OW15599  APSGAD31 OW15599  APSGDUMP OW15599  APSGFSSI OW15599  APSGTRCE OW15599  APSJCL OW15599  APSJCLI OW15599  APSMSTXT OW15599  APSNDOWN OW15599  APSNES OW15599  APSNINIT OW15599  APSNLINK OW15599  APSNRM OW15599  APSNSC OW15599  APSNSEND OW15599  APSNSM OW15599  APSNSSEL OW15599  APSNSSND OW15599  APSNTERM OW15599  APSPPATR OW15599  APSPPDVP OW15599  APSPPFSA OW15599  APSPPIEP OW15599  APSPPIFA OW15599  APSQDEQ OW15599  APSWPROT OW15599  APSZCTBL OW15599  APSZTRCE OW15599  HPRF220J OW15599  SGAPS4PP OW15599  SGAPS5PR OW15599  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW15599 APROUTEX APSCABE APSCADD APSCBMGR APSCCDEV APSCCHE  APSCCLR APSCCOMP APSCESTA APSCINFO APSCINIT APSCIPRT  APSCOPCI APSCPCIA APSCPRCT APSCRDRV APSCRSET APSCSNA  APSCSNIO APSCSYNC APSCTCP APSCTERM APSCTPRT APSCWRT  APSECUR APSEMSG APSERRM APSGAD31 APSGDUMP APSGFSSI  APSGTRCE APSJCL APSJCLI APSMSTXT APSNDOWN APSNES  APSNINIT APSNLINK APSNRM APSNSC APSNSEND APSNSM  APSNSSEL APSNSSND APSNTERM APSPPATR APSPPDVP APSPPFSA  APSPPIEP APSPPIFA APSQDEQ APSWPROT APSZCTBL APSZTRCE  HPRF220J SGAPS4PP SGAPS5PR  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APROUTEX   Appendix F. PTF Cover Letter Data for Service Level SMC9618 160 ¤   APSCABE  APSCADD  APSCBMGR  APSCCDEV  APSCCHE  APSCCLR  APSCCOMP  APSCESTA  APSCINFO  APSCINIT  APSCIPRT  APSCOPCI  APSCPCIA  APSCPRCT  APSCRDRV  APSCRSET  APSCSNA  APSCSNIO  APSCSYNC  APSCTCP  APSCTERM  APSCTPRT  APSCWRT  APSECUR  APSEMSG  APSERRM  APSGAD31  APSGDUMP  APSGFSSI  APSGTRCE  APSJCL  APSJCLI  APSMSTXT  APSNDOWN  APSNES  APSNINIT  APSNLINK  APSNRM  APSNSC  APSNSEND  APSNSM  APSNSSEL  APSNSSND  APSNTERM  APSPPATR  APSPPDVP  APSPPFSA  APSPPIEP  APSPPIFA  APSQDEQ  APSZCTBL  APSZTRCE  MACROS   Appendix F. PTF Cover Letter Data for Service Level SMC9618 161 ¤   APSWPROT  SGAPS4PP  SGAPS5PR  LISTEND  */.   F.12 COVER LETTER FOR PTF UW23722   PROBLEM DESCRIPTION(S):  OW14128 -  ****************************************************************  * USERS AFFECTED: PSF/MVS 2.2.0 Customers using D/T3130 with *  * Microcode Release 2 or with features 4802, *  * 4810, or 4815. *  * PSF/MVS 2.2.0 Customers who need either of *  * the following two printer functions: *  * - Font capture for raster fonts or *  * for single-byte outline fonts. *  * - Printer resident double-byte outline *  * fonts. *  ****************************************************************  * PROBLEM DESCRIPTION: ABEND024 RC0601 SNS0239..02 or *  * SNS0246..02 can occur if D/T3130 with *  * Microcode Release 2 is attached to *  * PSF/MVS without this APAR. *  * *  * PSF/MVS 2.2.0 needs support for two *  * new functions available on D/T3130 *  * Microcode Release 2. *  * - Font capture for raster fonts and *  * for single-byte outline fonts. *  * - Resident double-byte outline *  * (scalable) font support. *  * *  * The following D/T3130 features also *  * require this APAR, because they *  * include D/T3130 microcode release 2. *  * 3130 Feature 4802 - DBCS Font Package *  * 3130 Feature 4810 - Postscript Level 2 *  * 3130 Feature 4815 - PCL5e Support *  * *  * APAR OW15018 is additionally required *  * to enable support for D/T3130 *  * Data Stream Switching. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  New function is required which supports D/T3130 Microcode  Release 2. The functions enabled by this APAR are:  - Font capture for raster fonts and single-byte outline fonts.  - Printer resident double-byte outline (scalable) fonts.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 162 ¤   Double-byte outline resident fonts are a feature on D/T3130.  To use double-byte outline fonts you need:  - PSF/MVS 2.2.0 with this APAR (OW14128)  - IBM AFP CJK Metric-only Fonts (product number 5799-FCQ)  (RPQ 8A8080) installed on the host (usually in SYS1.FONTOLN)  and available to the PSF startup proc for the D/T3130 printer.  - D/T3130 Hardware feature 4802 installed on the printer.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW14128  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Changes to the PSF/MVS documentation are as follows:  S544-3672-02 "PSF/MVS System Programming Guide"  On page 50 add the following new section:  "3130, 3160 and 3935 Configuration Information"  Specific information and examples for various attachments of  these printers is available in S544-3977 "3130, 3160, and 3935  AFP Attachment Configuration Handbook."  On page 139 under "Supporting Resident Fonts" add new note 4  and an index entry for "font capture".  4. Some printers, such as the 3130, can capture downloaded  fonts. See "Font Capture" on page 152 for more information.  On page 142 under "APSRMARK Considerations" add the following  to the end of both bullet 1 and bullet 4:  Do not mark metric-only font character sets "PRIVATE".  Do not mark code pages used with double-byte outline fonts  "PRIVATE". They must be "PUBLIC" so the proper C-MAP in the  double-byte outline character set can be identified.  On page 145 under (PUBLIC|PRIVATE) add the following to the  end of the paragraph:  Do not mark metric-only font character sets "PRIVATE".  Do not mark code pages used with double-byte outline fonts  "PRIVATE". They must be "PUBLIC" so the proper C-MAP in the  double-byte outline character set can be identified.  On page 152 add a new chapter and a "font capture" index entry:  "CHAPTER 12.1 - FONT CAPTURE"  Some printers, such as the 3130, can capture downloaded fonts.  The concept is similar to "dynamic-caching" in RPM 3.0 or in  DPF. See Chapter 14 on page 161 for information on RPM and DPF.  Captured fonts automatically become new temporary "printer  resident fonts". This improves performance on future jobs  which use the same fonts. Both raster and outline fonts can be  captured. The printer manages the captured font library. If  the fonts are ever deleted from the printer, the host version  is automatically downloaded by PSF the next time it is needed.  A font character set or code page must be "PUBLIC" to be  captured. "PRIVATE" fonts are always downloaded and never  captured. APSRMARK can be used to mark a resource. Raster  character sets and code pages may also need to be marked with  RRID, RRDATE and RRTIME information. See "PSF Resident Font  Utility (APSRMARK)" on page 141 for information on using   Appendix F. PTF Cover Letter Data for Service Level SMC9618 163 ¤   APSRMARK. The following sections explain what needs to be done  for different types of fonts.  "Single-byte Raster Font Capture Considerations"  1. For raster fonts that were previously shipped as a part of  the PSF product, run the sample APSRMARK jobs that were  shipped with PSF. See "APSRMARK Sample Jobs" on page 259  for more information.  2. The single-byte raster fonts shipped in the IBM AFP Font  Collection (program number 5648-113) are already marked  correctly for both activating resident fonts and for font  capture.  3. For raster single-byte fonts that you create or change,  run APSRMARK to mark them "PUBLIC" and specify the GRID part  in RRID and the new date and time in RRDATE and RRTIME. See  "PSF Resident Font Utility (APSRMARK)" on page 141 for  information on using APSRMARK. Mark the font "PRIVATE" when  the font should not be captured. For example, if there is a  copyright restriction against having a copy of the font on  the printer hard drive, mark the font "PRIVATE".  "Single-byte Outline Font Capture Considerations"  1. All single-byte outline fonts shipped in the IBM AFP Font  Collection (program number 5648-113) are already marked  correctly for both activating resident fonts and for font  capture.  2. Any single-byte outline fonts created or changed by IBM Type  Transformer may need to be marked "PUBLIC", but contain all  other information needed for font capture. You do not need  to specify RRID, RRDATE, or RRTIME when you run APSRMARK.  Mark the font "PRIVATE" when the font should not be  captured. For example, if there is a copyright restriction  against having a copy of the font on the printer hard drive,  mark the font "PRIVATE".  "Double-byte Raster Font Capture Considerations"  1. If you are migrating from a printer with resident fonts to a  printer that captures fonts, the host libraries are already  marked correctly.  2. For new installations of DBCS font product IDs 5771-AGB,  5771-AEK, 5771-AFZ, 5771-AFW, or 5771-AEN run the sample  APSRMARK job included with the product.  3. For raster double-byte sections that you create or change,  run APSRMARK to mark them "PUBLIC" and specify the GRID part  in RRID and the new date and time in RRDATE and RRTIME. See  "PSF Resident Font Utility (APSRMARK)" on page 141 for  information on using APSRMARK. Mark the font "PRIVATE" when  the font should not be captured. For example, if there is a  copyright restriction against having a copy of the font on  the printer hard drive, mark the font "PRIVATE".  "Double-byte Outline Font Capture Considerations"  1. The double-byte fonts in "IBM AFP CJK Metric-only Fonts"  RPQ 8A8080 are not suitable for capture because they do not  contain font data. However, they are correctly marked for  activating the printer resident version of the fonts.  You do not need to run APSRMARK.  On page 154 under "Creating new fonts"   Appendix F. PTF Cover Letter Data for Service Level SMC9618 164 ¤   change the title in paragraph 3 (the list of actions) to:  "To Add A New Single-Byte Outline Font"  On page 155 add a new section and index entry for "font capture"  "Capturing New Outline Fonts"  Some printers, such as the 3130, can capture downloaded fonts.  See "Font Capture" on page 152 for more information.  On page 155 "Font Mapping" add to the end of the first bullet:  Note: Double-byte fonts can only be technology mapped at the  coded font prefix level. They are not mapped through the user  mapping tables.  On page 156 under "Mapping Algorithms" add an index entry  for "prefix mapping" and the following to the end of the first  bullet:  "This is called 'prefix mapping'."  On page 156 under "Using the Font Mapping Tables"  add to the end of the first paragraph:  "These tables are used to map single-byte fonts of one  technology to single-byte fonts of another technology."  On page 156 under "Using the Font Mapping Tables"  change the first sentence in the first bullet to read:  "Map input single-byte font names to equivalent raster or  outline font names."  On page 211 under "Mapping to Outline Fonts Considerations"  add an index entry for 'prefix mapping' and  change bullet 3 to say:  "A double-byte raster font section is requested by character set  and code page name. Note: Double-byte raster coded fonts are  prefix mapped to equivalent outline coded fonts."  On page 216 "RAC and Fonts" change the first sentence to read:  "Fonts are resources specified in a Map Coded Font (MCF)  structured field."  On page 216 "RAC and Fonts" change the words 'Double-byte fonts'  to 'Raster Double-byte fonts' in the third paragraph. Only  raster double-byte fonts have sections.  On page 230 add a new section and a "font capture" index entry:  "Captured Fonts"  Some printers, such as the 3130, can capture downloaded fonts.  Captured fonts automatically become new temporary "printer  resident fonts". This improves performance on future jobs  which use the same fonts. See "Font Capture" on page 152 for  more information.  On page 279 under "XTP7MTOF"  add an index entry for 'prefix mapping' and  change the last sentence to read:  "Double-byte raster coded fonts are prefix mapped to equivalent  outline coded fonts. However, a double-byte raster font  section requested by character set and code page name is not  mapped to outline, because there is no outline equivalent for  just one section."  On page 331 add the following Glossary entry:  "capture"  Some printers can capture downloaded resources such as fonts  These saved fonts automatically become new temporary "printer  resident fonts". This improves performance on future jobs   Appendix F. PTF Cover Letter Data for Service Level SMC9618 165 ¤   which use the same fonts. Both raster and outline fonts can be  captured.  On page 344 add the following Glossary entry:  "prefix mapping"  The process PSF uses to change font names at the coded font  level to a name appropriate to the font technology supported by  the printer. For example, XZ is the prefix for an outline  font. When the printer only supports bounded box raster fonts,  PSF will change the font prefix to X0. X0 is the correct  prefix for the same font in the correct raster font library.  ---------------------------------------------------------------  Changes to S544-3673-02 "PSF/MVS Application Programming Guide"  On page 20 under "Library-Member Types"  on the third sentence of the first bullet change "double-byte  coded font" to read "raster double-byte coded font".  to the end of the first bullet add:  "An outline double-byte font contains one code-page and font-  character-set pair."  On page 20 under "Printer-Resident Fonts"  before the last sentence of the first paragraph add:  "Some AFP printers, such as the 3130, can capture host fonts  as new resident fonts."  On page 21 under "Printer-Resident fonts"  before the last sentence of the paragraph that begins  "If you update a font ..." add the following:  "This means that the old printer resident version will be used.  To use the new version, the font can be marked "PRIVATE", or  marked 'PUBLIC" with a new RRDATE and RRTIME. Some printers  can capture and make resident these modified fonts once they  are correctly marked. Do not mark metric-only font character  sets "PRIVATE". Do not mark code pages used with double-byte  outline fonts "PRIVATE". They must be "PUBLIC" so the proper  C-MAP in the double-byte outline character set can be  identified."  On page 21 add a new section and a "font capture" index entry:  "Font Capture"  Some printers, such as the 3130, can capture downloaded fonts.  The concept is similar to "dynamic-caching" in RPM 3.0 or in  DPF. Captured fonts automatically become new temporary  "printer resident fonts". This improves performance on future  jobs which use the same fonts. Both raster and outline fonts  can be captured. For more information on font capture, refer  to "PSF/MVS System Programming Guide" (S544-3672).  On page 21 under "Single-Byte and Double-byte Fonts"  to the end of the first paragraph add:  For example, double-byte raster fonts are available as a  feature in "The AFP Font Collection". Double-byte outline  (scalable) fonts are available as RPQ 8A8080 product 5799-FCQ,  "IBM AFP CJK Metric-only Fonts". This RPQ contains fonts  needed by PSF to activate printer resident versions of double-  byte outline fonts, such as Japanese Heisei Mincho or Korean  Myengjo.  On page 21 "Font Formats"  change the section heading to "240-Pel Raster Font Formats"   Appendix F. PTF Cover Letter Data for Service Level SMC9618 166 ¤   On page 22 under "Outline Fonts"  add a new paragraph at the end of the section which reads:  "PSF/MVS 2.2.0 with APAR OW14128 supports printer resident  double-byte outline fonts. These scalable fonts are available  as a feature on some printers. Host versions of the fonts are  available in "IBM AFP CJK Metric-only Fonts" product number  5799-FCQ RPQ number 8A8080."  On page 41 under "CHARS"  add to the last two bullets (right before "Examples"):  "Raster versions of the outline fonts will be used unless the  system programmer specifies XTP7MTOF in PSF exit 7 (APSUX07).  Generally, you should request raster fonts with CHARS."  ---------------------------------------------------------------  Changes to S544-3675-02 "PSF/MVS Messages and Codes"  on page 93 change message APS374I to now read:  APS374I THE HOST VERSION OF THE REQUESTED OUTLINE FONT  CHARACTER SET IS NOT DOWNLOADABLE BECAUSE IT  DOES NOT CONTAIN ANY FONT PATTERN DATA.  IT MAY BE A METRIC-ONLY OUTLINE FONT CHARACTER SET.  EXPLANATION: Some printers have optional font features  or user installable fonts on cards or other media. This  message may indicate that the referenced font was not  installed in the printer when this data set was printed.  To support printing with printer resident fonts, the host  font libraries may contain font resources with formatting  information but no downloadable font pattern data. These  metric-only font character sets (MOF) are used only to  activate printer resident fonts. Because there is no font  data, the character set cannot be downloaded.  The pattern technology specified in byte 1 in the Font  Control (FNC) structured field is X'1E' or X'1F', bytes  28-31 in the FNC structured field contain the total  number of bytes in the Font Patterns (FNG) structured  field.  SYSTEM ACTION: PSF cannot print the current page. PSF  attempts to locate the end of the current page and resume  printing on the next page. If the end of the current  page cannot be located, PSF stops printing the data set.  PSF issues a message identifying the position of the  structured field in the input data stream or resource.  PSF issues additional messages identifying the processing  environment when the error was found.  USER RESPONSE: Install the font on the printer, change  to a font that is either installed or downloadable, or  inform your system programmer that this error occurred.  SYSTEM PROGRAMMER RESPONSE: If the font character set is  a standard IBM supplied font, then it may be a  metric-only (MOF) font. If so, then that specific font  must be resident in the printer. Verify that the font is  resident in the printer being used. For example,  double-byte outline (scalable) fonts generally have  metric-only fonts on the host system. Double-byte  outline resident fonts may be a separate printer feature.  Check the printer publications for information on   Appendix F. PTF Cover Letter Data for Service Level SMC9618 167 ¤   resident fonts.  If the font is resident in the printer, then ensure that  the character set is marked PUBLIC (by APSRMARK). In the  font data definition (FONTDD) parameter in the PSF  PRINTDEV statement, ensure that the font libraries  containing marked resources are specified first in the  library concatenation order. If you use fonts as INLINE  or USERLIB resources, verify that they are marked PUBLIC.  If an IBM licensed program was used to create the  structured fields for the font with the error, verify  that the input to that program was valid. If the input  was valid, refer to Advanced Function Printing:  Diagnosis Guide and Print Services Facility/MVS:  Diagnosis Guide and Reference for assistance in  determining the source of the problem. If the error  involves separator pages or the message data set, use the  information provided in the User Response section to  correct the error.  OPERATOR RESPONSE: If this message appears on the  operator's console, it indicates that the resource  containing the error is defined for a separator page or  the message data set in the PSF startup procedure.  Inform your system programmer.  PROBLEM DETERMINATION: Items 1, 2, 3, 8, 13, 17, 19.  On page 284 change PSF Abend Reason Code 2EE to now read:  2EE  EXPLANATION: This abend is issued by module APSCSNIO -- The  APSCSNIO SENSEID function was unable to successfully complete  its function. The printer did not respond to the first PSF  IPDS command (STM). The SNA or TCP/IP connection may have  failed or a printer hardware error may be the cause. No IPDS  information on the reason for the failure is available.  SYSTEM ACTION: PSF attempts to recover from this abend by  restarting. Message APS057I is issued if PSF successfully  restarts.  SYSTEM PROGRAMMER RESPONSE: This abend indicates a possible  printer hardware error. Correct any problems indicated on the  printer operator panel. Correct any outstanding intervention  conditions at the printer. Verify that a good network path  exists to the printer. Re-IML the printer. If the problem  persists, contact your systems engineer for assistance  regarding this error.  DEPENDENCY:  This PTF can be applied without any software prerequisites.  To use the new function "Double-Byte Outline Font Support"  you will need:  1. IBM AFP CJK Metric-only Fonts (product number 5799-FCQ  RPQ number 8A8080) installed in your MVS host font  library (usually in SYS1.FONTOLN).  2. An IBM 3130 printer with feature 4802 installed.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRACTEZ OW14128  APRCP2AZ OW14128   Appendix F. PTF Cover Letter Data for Service Level SMC9618 168 ¤   APRCS2AZ OW14128  APRFTIEX OW14128  APRGRNEX OW14128  APRMFTEZ OW14128  APSCINFO OW14128  APSCSTMI OW14128  APSDLOAD OW14128  APSMSTXT OW14128  APSRCPDS OW14128  APSRDEL OW14128  APSRFLST OW14128  APSRLOAD OW14128  APSRMFNT OW14128  APSRMFNX OW14128  APSRMOVL OW14128  APSRMPSG OW14128  APSRNAME OW14128  APSRROCK OW14128  APSRSRT OW14128  APSRSTAT OW14128  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW14128 APRACTEZ APRCP2AZ APRCS2AZ APRFTIEX APRGRNEX APRMFTEZ  APSCINFO APSCSTMI APSDLOAD APSMSTXT APSRCPDS APSRDEL  APSRFLST APSRLOAD APSRMFNT APSRMFNX APSRMOVL APSRMPSG  APSRNAME APSRROCK APSRSRT APSRSTAT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRACTEZ  APRCP2AZ  APRCS2AZ  APRFTIEX  APRGRNEX  APRMFTEZ  APSCINFO  APSCSTMI  APSDLOAD  APSMSTXT  APSRCPDS  APSRDEL  APSRFLST  APSRLOAD  APSRMFNT  APSRMFNX  APSRMOVL  APSRMPSG  APSRNAME  APSRROCK  APSRSRT  APSRSTAT   Appendix F. PTF Cover Letter Data for Service Level SMC9618 169 ¤   LISTEND  */.   F.13 COVER LETTER FOR PTF UW25033   PROBLEM DESCRIPTION(S):  OW17669 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users who want to *  * use inline form definitions, inline *  * page definitions, and inline microfilm *  * setups without specifying them in the *  * user JCL. *  ****************************************************************  * PROBLEM DESCRIPTION: User would like the ability to use *  * inline form definitions, inline *  * page definitions, and inline *  * microfilm setups without *  * specifying them in user JCL. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  Inline resources can only be selected by specifying them  in JCL.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW17669  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Change the PSF/MVS System Programming Guide, Version 2.2.0,  S544-3672-02;  On page 130,  In the section "Form Definitions in Deferred-Printing Mode",  replace Table 17 with:  |--------------------------------------------------------------|  | Table 17. Hierarchy of Form Definition Selection |  | in Deferred-Printing Mode |  |--------------------------------------------------------------|  | User JCL | OUTPUT statement | Explicitly referred | FORMDEF =|  | | | to (see notes 1,2) | |  | |---------------------------------------------------|  | | | Implicitly referred | FORMDEF =|  | | | to step-level | |  | |---------------------------------------------------|  | | | Implicitly referred | FORMDEF =|  | | | to job-level | |  |--------------------------------------------------------------|  | First inline form definition |  | (see note 3) |  |--------------------------------------------------------------|  | PRINTDEV statement from the PSF startup procedure | FORMDEF =|   Appendix F. PTF Cover Letter Data for Service Level SMC9618 170 ¤   |--------------------------------------------------------------|  Notes:  1. This includes inline form definitions, which are  specified by name, or with the name DUMMY, on the  OUTPUT statement.  2. This includes a form definition in a user library, which  must be specified by name on the OUTPUT statement.  3. If the user JCL does not specify the FORMDEF  parameter and there are inline form definitions, the  first inline form definition in the print data set is  selected.  On page 130,  in the section "Form Definitions in Direct-Printing Mode"  replace table 18 with:  |--------------------------------------------------------------|  | Table 18. Hierarchy of Form Definition Selection in |  | Direct-Printing Mode |  |--------------------------------------------------------------|  | User JCL | Explicitly referred to OUTPUT statement| FORMDEF =|  | | (See note 1.) | |  |--------------------------------------------------------------|  | First inline form definition |  | (see note 2) |  |--------------------------------------------------------------|  | User JCL | PRINTDEV statement | FORMDEF =|  |--------------------------------------------------------------|  Notes:  1. This includes inline form definitions, which are  specified by name, or with the name DUMMY, on the  OUTPUT statement.  2. If the user JCL does not specify the FORMDEF  parameter and there are inline form definitions, the  first inline form definition in the print data set is  selected.  3. PSF does not use user libraries in direct-printing mode.  On page 131,  in the section "Page Definitions in Deferred-Printing Mode",  replace Table 19  -------------------------------------------------------------  | Table 19. Hierarchy of Page Definition Selection |  | in Deferred-Printing Mode |  |-------------------------------------------------------------|  | User JCL | OUTPUT statement | PAGEDEF = |  | | (see note 1) | |  | |------------------------------------------------|  | | DD statement | FCB = |  | |------------------------------------------------|  | | OUTPUT statement | FCB = |  | | (see note 1) | |  |-------------------------------------------------------------|  | JES default in the current printer setup |  | (see notes 2 and 3) |  |-------------------------------------------------------------|  | First inline page definition |   Appendix F. PTF Cover Letter Data for Service Level SMC9618 171 ¤   | (see note 4 and 5) |  |-------------------------------------------------------------|  | PRINTDEV statement from the PSF startup | PAGEDEF = |  | procedure (see note 3) | |  -------------------------------------------------------------  Notes:  1. The OUTPUT statement used is the first one found from  explicit, step-level implicit and job-level implicit  in that order.  2. Under JES2, the JES default PAGEDEF can be specified by the  FCB parameter in the PRTnnn statement or, if this parameter  is not present, by the NIFCB parameter in the PRINTDEF  statement.  3. Under JES3, a page definition specified in the PRINTDEV  statement is never selected because JES3 always has a  default page definition. This default page definition is  taken from the CARRIAGE parameter in the DEVICE statement  or, if this parameter is not present, from the CARRIAGE  parameter on the OUTSERV statement. If the OUTSERV  statement has no CARRIAGE parameter, a default of 6 lines  per inch is used, which invokes page definition P16.  To use inline page definitions in JES3, the resource  name should be specified in the PAGEDEF or FCB of the user  JCL.  4. For JES2, if the user JCL does not specify the PAGEDEF or  FCB parameter and there are inline page  definitions, the first inline page definition in the  print data set is selected unless there is a JES default.  5. If an inline page definition is included in the print data  set and its name matches the name selected or the name from  the JCL is DUMMY, the inline will be used.  6. A page definition from a user library will be used if its  name matches the name selected.  On page 132,  in the section "Page Definitions in Direct-Printing Mode",  replace Table 20  -------------------------------------------------------------  | Table 20. Hierarchy of Page Definition Selection |  | in Direct-Printing Mode |  |-------------------------------------------------------------|  | User JCL | Explicitly referred to OUTPUT | PAGEDEF = |  | | statement | |  | |--------------------------------------------------|  | | DD statement | FCB = |  | |--------------------------------------------------|  | | Explicitly referred to OUTPUT | FCB = |  | | statement | |  |-------------------------------------------------------------|  | First inline page definition |  | (see note 3) |  |-------------------------------------------------------------|  | User JCL | PRINTDEV statement | PAGEDEF = |  -------------------------------------------------------------  Notes:   Appendix F. PTF Cover Letter Data for Service Level SMC9618 172 ¤   1. If an inline page definition is included in the print data  set and its name matches the name selected or the name from  the JCL is DUMMY, the inline will be used.  2. User libraries are not used in direct-printing mode.  3. If the user JCL does not specify the PAGEDEF or  FCB parameter and there are inline page  definitions, the first inline page definition in the print  data set is selected.  Change the PSF/MVS Application Programming Guide, Version 2,  Release 2, Modification 0, S544-3673  Page 44, 'Using Inline Microfilm Setup Resources'  1. page 44, replace bullet 3 with:  If you do not specify the COMSETUP parameter in your JCL, the  first inline COMSETUP in the print data set  is selected.  2. page 45, add to last paragraph:  If you do not specify the COMSETUP parameter in your JCL, the  first inline COMSETUP in the print data set  is selected.  Page 51, 'Using Inline Form Definition:' section.  replace bullet 3 with:  If you do not specify the FORMDEF parameter in your JCL, the  first inline form definition in the print data set is selected.  Page 54, 'Using Inline Page Definitions:'  replace bullet 3 with:  For JES2, if you do not specify the PAGEDEF parameter or FCB  parameter in your JCL, the first inline page definition  in the print data set is selected unless there is a JES default.  Page 59, 'Using Inline Resources'  replace second paragraph, last two sentences with:  Note that for an inline form definition, page definition, or  microfilm setup resource, you may specify the name in the JCL  FORMDEF, PAGEDEF, COMSETUP parameter, or specify the name  DUMMY or specify no parameters.  If you have specified the inline resource name in the  FORMDEF, PAGEDEF, or COMSETUP parameter, and your  data set contains these inline resources, PSF uses the  inline resource. If the name in the FORMDEF, PAGEDEF, or  COMSETUP parameter does not match the name of an inline  resource, PSF will use the resource from the resource library  that matches the name in the JCL.  If you have not specified the FORMDEF, PAGEDEF, COMSETUP  parameter, and your data set contains inline resources, PSF  uses the first inline resource (FORMDEF, PAGEDEF, or COMSETUP)  encountered in the data set. For information on how PSF  selects resources, see Print Services Facility/MVS: System  Programming Guide.  Page 89, 'Specifying a Form Definition' in EXAMPLES section.  Last example on page 90, replace paragraph after  example with:  The FORMDEF parameter may specify the resource name of  the inline form definition, or the keyword DUMMY.  If the name in the FORMDEF does not match the name of  an inline form definition, PSF will use the resource   Appendix F. PTF Cover Letter Data for Service Level SMC9618 173 ¤   from the resource library that matches the name in the JCL.  If the job does not specify the FORMDEF parameter,  the first inline form definition in the print data set  is selected.  Page 96, 'Specifying a Page Definition' in EXAMPLES section.  Last example on page 97, replace paragraph after  example with:  The PAGEDEF parameter may specify the resource name of  the inline page definition, or the keyword DUMMY.  If the name in the PAGEDEF does not match the name of  an inline page definition, PSF will use the resource  from the resource library that matches the name in the JCL.  If the job does not specify the PAGEDEF parameter,  the first inline page definition in the print data set  is selected.  DOCUMENTATION:  Add to the PSF/MVS System Programming Guide Version 2.2.0  Chapter 16, page 239, section - Checkpointing:  second paragraph, third and fourth sentences,  replace with:  For printers (footnoot 23) that can report  data stream errors asynchronously, PSF issues  a print buffered data command when a checkpoint  is taken.  footnote 23  change to:  Some examples of printers that produce asynchronous data  stream errors include: 3812, 3816, 3912, 3916, 3930, 4028  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRBPGEX OW17669  APRBRSEX OW17669  APSDDS OW17669  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW17669 APRBPGEX APRBRSEX APSDDS  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRBPGEX  APRBRSEX  APSDDS  LISTEND  */.   F.14 COVER LETTER FOR PTF UW25143    Appendix F. PTF Cover Letter Data for Service Level SMC9618 174 ¤   PROBLEM DESCRIPTION(S):  OW16864 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1, or 2.2.0 users who *  * print celled 240-pel IM1 images to 300-pel *  * printers that do not support the IOCA *  * replicate and trim function. *  ****************************************************************  * PROBLEM DESCRIPTION: After APAR OW10903 was applied, users *  * of 4028 printers noticed a performance *  * degradation when printing 240-pel IM1 *  * celled images that request replication. *  * *  * *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  APAR OW10903 sent down each cell of an IM1 image as a separate  IO image to the printer. Even though less overall data was sent  to the 4028 printer, the overhead of processing all the IO image  controls caused a performance degradation.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW16864  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Changes to PSF/MVS documentation are:  S544-3675-02 "PSF/MVS Messages and Codes"  on page 53, add the following new message:  APS245I A COMPLEX IM IMAGE OBJECT CONTAINS INVALID OR INCORRECT  DATA. THE COMPLEX IM IMAGE OBJECT CANNOT BE CONVERTED  TO AN IO IMAGE OBJECT.  EXPLANATION: This message is issued when PSF converts a  complex IM image object to an IO image object and the image  size is not large enough to contain the image raster data from  the IRD structured fields. This message is issued only when  Exit 7 has requested that PSF convert a complex IM image object  to a single IO image object.  This message is issued if either of the following are true:  o The XCSize or YCSize parameter value of the ICP structured  field is larger than the calculated image X size or Y size,  respectively.  o The XCOset plus XFilSize parameter values or the YCOset  plus YFilSize parameter values of the ICP structured field  are larger than the calculated image X size or Y size,  respectively.  When PSF converts a complex IM image object to an IO image  object, PSF calculates the image size by subtracting the X and  Y image origins from the X and Y page sizes.  The X and Y image origins are from the XoaOset and YoaOset  parameter values of the IOC structured field.  The X and Y page sizes are from the XpgSize and YpgSize   Appendix F. PTF Cover Letter Data for Service Level SMC9618 175 ¤   parameter values of the PGD structured field, if the image  object is contained in a MO:DCAÄÄP data set or in an overlay or is  imbedded in a data set containing line data. For an image  object in a page segment, the X and Y page sizes used by PSF  are from the X and Y paper sizes of the current media source  (input bin).  The IOC and ICP structured fields are contained in a MO:DCAÄÄP  data set, in an overlay, or in a page segment or are imbedded  in a data set containing line data. The PGD structured field  is contained in a MO:DCAÄÄP data set, in an overlay, or in a page  definition.  SYSTEM ACTION: PSF stops processing the image object and  issues additional messages that identify the processing  environment when the error was found. PSF sends the portion of  the image that was successfully processed, if any, to the  printer. PSF then continues processing the current data set.  USER RESPONSE: If you created the structured fields for the  resource or print data set containing the image, correct the  error in the referenced structured field and resubmit the print  request. Refer to Mixed Object Document Content Architecture  Reference for more information about the structured field. If  the structured field has no error, the error may be a PSF or  printer logic error. If you used a program to create the  structured fields for the resource or print data set containing  the image, contact your system programmer.  SYSTEM PROGRAMMER RESPONSE: If an IBM licensed program was  used to create the structured fields for the print data set or  the resource with the error, verify that the input to that  program was valid. If the input was valid, refer to Advanced  Function Printing: Diagnosis Guide and Print Services  Facility/MVS: Diagnosis Guide and Reference for assistance in  determining the source of the problem.  OPERATOR RESPONSE: If this message appears on the operator's  console, it indicates that the resource containing the error is  defined for a separator page or the message data set in the PSF  startup procedure. Inform your system programmer.  PROBLEM DETERMINATION: Items 13, 17, 19.  ---------------------------------------------------------------  LH40-0205-01 "PSF/MVS Diagnosis Guide and Reference"  on page 57, add the following new message to the table:  -----------------------------  | APS245I | APRIMGAZ |  -----------------------------  on page 77, add the following new code to the table:  ----------------------------------------------------------  | X'08140141' | Complex IM image object contains| APRMSGEX |  | | invalid or incorrect data. The | |  | | complex IM image object cannot | |  | | be converted to an IO object. | |  ----------------------------------------------------------  ----------------------------------------------------------------  S544-3672-02 "Print Services Facility/MVS System Programming  Guide Version 2, Release 2, Modification 0"  1. On page 207 insert the following new section after the   Appendix F. PTF Cover Letter Data for Service Level SMC9618 176 ¤   "Overlay Considerations" section.  Converting a Multiple Celled IM1 Image Considerations  With APSUX07, you can control whether a multiple celled IM1  image is converted to a single IOCA image or converted to  multiple IOCA images:  XTP7C2SI Controls conversion of a multiple celled IM1 image  This flag defaults to 0. The default specifies that PSF will  convert a multiple celled IM1 image to multiple IOCA images.  If the flag is set to 1, then PSF will convert a multiple  celled IM1 image to a single IOCA image. The flag can be set  during the INIT call or the BDSC call and it remains set  between calls; only APSUX07 can change the state of this  flag.  This request is only honored if the printer does not support  IOCA replicate and trim.  This change only produces a performance enhancement if the  image is a 240-pel IM1 celled image that requests  replication and you are printing on a 300 pel printer.  For any other case, this change may cause a performance  degradation.  2. On page 212 under "Initialization Call (INIT)" after the 4th  paragraph add the following paragraph.  This call can be used to control the conversion of a multiple  celled IM1 image. See "Converting a Multiple Celled IM1  Image Considerations" on page 207 for more information.  3. On page 213 under "Begin-Data-Set Call (BDSC)" after the 5th  bullet add the following.  o Control converting a multiple celled IM1 image. See  "Converting a Multiple Celled IM1  Image Considerations" on page 207 for more information.  4. On page 274 replace the "RESERVED" field with the following.  .... ...1 XTP7C2SI CONVERT A MULTIPLE CELLED IM1  IMAGE TO A SINGLE IOCA IMAGE  (VALID FOR INITIALIZATION  "XTP7INIT" AND BDS "XTP7BDS")  1 = CONVERT TO SINGLE  IOCA IMAGE  0 = CONVERT TO MULTIPLE  IOCA IMAGES  5. On page 280 after description of XTP7HCA add the following.  XTP7C2SI  This field is valid only on the INIT and BDSC  calls. PSF initially sets this field to B'0' to  indicate that a multiple celled IM1 image is to  be converted to multiple IOCA images. If APSUX07  sets this flag to B'1', then PSF will convert  a multiple celled IM1 image to a single IOCA  image.  6. On page 297 after XTP7HCA add the following entry to the  table.  INIT BDSC  XTP7C2SI IO IO  ACTION:  If you have modified your source code for APSGEXTP, then save it   Appendix F. PTF Cover Letter Data for Service Level SMC9618 177 ¤   before applying this PTF as this PTF will replce your copy of  APSGEXTP.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRBPGEX OW16864  APRIMGAZ OW16864  APRMSGEX OW16864  APSDDOC OW16864  APSDDS OW16864  APSDECH OW16864  APSGEXTP OW16864  APSMSTXT OW16864  APSUREXT OW16864  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW16864 APRBPGEX APRIMGAZ APRMSGEX APSDDOC APSDDS APSDECH  APSGEXTP APSMSTXT APSUREXT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRBPGEX  APRIMGAZ  APRMSGEX  APSDDOC  APSDDS  APSDECH  APSMSTXT  APSUREXT  MACROS  APSGEXTP  LISTEND  */.   F.15 COVER LETTER FOR PTF UW25289   PROBLEM DESCRIPTION(S):  OW17445 -  ****************************************************************  * USERS AFFECTED: PSF/MVS 2.2.0 customers who want to generate *  * bar codes via page definitions. *  ****************************************************************  * PROBLEM DESCRIPTION: Customers would like the ability to *  * specify that a field in a line data *  * record be presented as a bar code. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  The design of line data processing does not allow for bar  code specification in a page definition. New code is   Appendix F. PTF Cover Letter Data for Service Level SMC9618 178 ¤   needed to allow this function.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW17445  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Changes to PSF/MVS documentation are:  S544-3673-02 "PSF/MVS Application Programming Guide"  on page 124 in the section "Using Shift-Out, Shift-In  (SOSI) Codes, replace the first sentence of the third paragraph  with:  You can either specify a specific single-byte and double-byte  font pair to use on a line or field basis or you can use the  same single-byte and double-byte font pair for the entire page.  If specifying a specific single-byte and double-byte font pair  on a line or field basis, you must use the font list in a page  definition to specify the single-byte and double-byte fonts  you wish to use for the page. This allows you to use more  than one single-byte font per page as well as more than  one double-byte font per page.  If you choose to use the same single-byte and double-byte  font pair for the entire page, the first font you specify must  be a single byte font and the second font must be a double-byte  font.  on page 125, add the following phrase to the beginning of the  first sentence in Notes 1 and 2:  When using the same single-byte and double-byte font pair for  the entire page,  S544-3675-02 "PSF/MVS Messages and Codes"  on page 88, add the following new message:  APS350I DATA IN A PAGEDEF RESOURCE IS INVALID: IN LND  STRUCTURED FIELD NUMBER structured field number, THE  SHIFT-OUT CODED FONT LOCAL IDENTIFIER WAS NON-ZERO BUT  THE GENERATE FONT CHANGE FLAG WAS NOT SET.  EXPLANATION: In the Line Descriptor (LND) structured field  identified in this message, the Shift-out Coded Font Identifier  was non-zero. The Generate Font Change flag should be set to  indicate that the Primary Coded Font Local Identifier should be  used whenever a shift-in code is processed. However, the  Generate Font Change flag had a value of B'0'. The LND  structured field is contained in the page definition.  SYSTEM ACTION: PSF stops processing the current data set and  issues additional messages that identify the processing  environment when the error was found.  USER RESPONSE: If you created the structured fields for the  page definition, correct the error and resubmit the print  request. Refer to Advanced Function Presentation: Programming  Guide and Line Data Reference and Mixed Object Document Content  Architecture Reference for more information about the  structured field. If the structured field has no error, the  error may be a PSF logic error. If you used a program to  create the structured fields for the page definition, contact  your system programmer.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 179 ¤   SYSTEM PROGRAMMER RESPONSE: If an IBM licensed program was  used to create the structured fields for the page definition  with the error, verify that the input to that program was  valid. If the input was valid, refer to Advanced Function  Printing: Diagnosis Guide and Print Services Facility/MVS:  Diagnosis Guide and Reference for assistance in determining the  source of the problem. If the error involves separator pages  or the message data set, use the information provided in the  User Response section to correct the error.  OPERATOR RESPONSE: If this message appears on the operator's  console, it indicates that the resource containing the error is  defined for a separator page, for the message data set, or as  the default resource for user print data sets in the PSF  startup procedure. Inform your system programmer.  PROBLEM DETERMINATION: Items 2, 17, 27.  LH40-0205-01 "PSF/MVS Diagnosis Guide and Reference"  on page 58, add the following new message to the table after  the entry for APS346I:  Ú-----------------------------¿  | APS350I | APRPDPAZ |  À-----------------------------Ù  on page 80, add the following new code to the table after  the entry for X'08140339':  Ú----------------------------------------------------------¿  | X'08140340' | Data in a PAGEDEF is invalid, | APRMSGEX |  | | the shift-out coded font local | |  | | identifier was non-zero but the | |  | | generate font change flag was | |  | | not set. | |  À----------------------------------------------------------Ù  DOCUMENTATION:  Changes to PSF/MVS documentation are:  S544-3673-02 "PSF/MVS Application Programming Guide"  on page 12, change the first sentence of the second paragraph  under the section titled "Using MO:DCAÄÄP Bar Code Objects" to  read:  A bar code data object can be included in a print data set,  in an overlay resource, or can be created from bar code  specifications in a page definition.  on page 12, add the following sentence to the 3rd bullet  under the section titled "Using MO:DCAÄÄP Bar Code Objects" to  read:  Color cannot be selected when specifying bar codes in a  page definition.  on page 12, add the following sentence to the end of the  first paragraph following the bulleted list in  the section titled "Using MO:DCAÄÄP Bar Code Objects" to  read:  For more information about coding bar code specifications  in page definitions, refer to the documentation section of  PPFA/370 APAR PN79369.  on page 12, add the following paragraph after the last paragraph  on the page:  Bar codes generated on printers with different resolutions may   Appendix F. PTF Cover Letter Data for Service Level SMC9618 180 ¤   differ in length. This is due to resolution correction needed  to round the bar code widths to a specific pel size. Each  printer may use a different algorithm for this calculation.  Therefore, the user needs to test on each type of printer to be  used for bar code printing.  S544-3675-02 "PSF/MVS Messages and Codes"  on page 88, add the following new message:  APS352I BAR CODE GENERATION WAS REQUESTED ON LND STRUCTURED  FIELD structured field number, BUT THE PRINTER DOES NOT  SUPPORT BAR CODE OBJECTS.  EXPLANATION: An LND structured field within a page definition  has requested PSF to generate a bar code object from the line  data but the printer does not support bar code objects.  SYSTEM ACTION: PSF ignores the request and continues  processing the data set.  USER RESPONSE: To print the data set and have PSF generate bar  code objects, submit the print job to a printer that supports  bar code objects. For more information about AFP printers that  support bar code objects, refer to Advanced Function  Presentation: Printer Information.  SYSTEM PROGRAMMER RESPONSE: If the page definition is for a  separator page, the message data set, the default page  definition for the user print data sets defined in the PSF  startup procedure, delete the bar code generation request from  the page definition.  OPERATOR RESPONSE: If this message appears on the operator's  console, it indicates that the resource containing the error is  defined for a separator page, for the message data set, or as  the default resource for user print data sets in the PSF  startup procedure. Inform your system programmer.  PROBLEM DETERMINATION: None.  On page 168 update the explanation for APS708I. Start the  explanation with the following new paragraph:  EXPLANATION: An undefined character has been detected:  o in a bar code data (BDA) command  o in the font specified for text, bar code HRI, or graphics  character-string data.  o in Presentation Text (PTX) command data at the quality  level specified  Continue with the original explanation for this message.  LH40-0205-01 "PSF/MVS Diagnosis Guide and Reference"  on page 58, add the following new message to the table:  -----------------------------  | APS352I | APRPLNAZ |  -----------------------------  on page 80, add the following new code to the table:  ----------------------------------------------------------  | X'08140341' | Bar code generation was | APRMSGEX |  | | requested on an LND structured | |  | | field but the printer does not | |  | | support bar code objects. | |  ----------------------------------------------------------  DEPENDENCY:  This PTF can be applied without any software prerequisites.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 181 ¤   The enhanced FONT subcommand requires Page Printer Formatting  Aid/370 with APAR PN77186. This APAR allows you to generate  the page definitions necessary to invoke the new function  supplied by this PSF/MVS APAR.  DEPENDENCY:  This PTF can be applied without any software prerequisites.  The bar codes in page definitions support requires Page  Printer Formatting Aid/370 with APAR PN79369. That APAR  allows you to generate the page definitions necessary to  invoke the new function supplied by this PSF/MVS APAR.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRBLPAZ OW17445  APRELPAZ OW17445  APRMSGEX OW17445  APRPDFEZ OW17445  APRPDPAZ OW17445  APRPLNAZ OW17445  APSDECH OW17445  APSMSTXT OW17445  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW17445 APRBLPAZ APRELPAZ APRMSGEX APRPDFEZ APRPDPAZ APRPLNAZ  APSDECH APSMSTXT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRBLPAZ  APRELPAZ  APRMSGEX  APRPDFEZ  APRPDPAZ  APRPLNAZ  APSDECH  APSMSTXT  LISTEND  */.   F.16 COVER LETTER FOR PTF UW25414   PROBLEM DESCRIPTION(S):  OW17541 -  ****************************************************************  * USERS AFFECTED: PSF/MVS 2.1.0 and 2.1.1 customers who have *  * applied PTF UW19133 and use conditional *  * processing Page Definitions and 2.2.0 *  * customers who have applied PTF UW19134 and *  * use conditional processing Page *  * Definitions. *  ****************************************************************   Appendix F. PTF Cover Letter Data for Service Level SMC9618 182 ¤   * PROBLEM DESCRIPTION: No Load Font Equivalence (LFE) command *  * was sent for a page so the printer uses *  * the last LFE it was sent. There is a *  * Set Coded Font Local (SCFL) command *  * in the page that calls out a local *  * font ID that is not defined in the *  * LFE the printer is using. This causes *  * the printer to send back the 0218...01 *  * sense data. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  PSF/MVS is writing over the end of a data structure and  incorrectly setting some variables that are needed to send  out an LFE command for the page.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW17541  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Changes to PSF/MVS documentation are:  S544-3675-02 "PSF/MVS Messages and Codes"  on page 18, revise the text for message APS105I to read (only  the third paragraph under the explanation has actually changed):  APS105I THE ERROR REPORTED ABOVE OCCURRED IN LOGICAL RECORD  NUMBER record number, WHOSE SEQUENCE NUMBER IS sequence  number.  EXPLANATION: This message is given in addition to the message  that describes the error. It identifies the specific invalid  input record. The object (if any) that contains the invalid  record is identified in either message APS108I or message  APS109I, which follows this message.  The record number specified is relative to the user data stream  and is different for multiple transmissions of the data set.  However, the record number may be inaccurate if the data set is  using a page definition that performs conditional processing.  The sequence number may print as NOT AVAILABLE in the message.  For example, this will happen if the sequence number is zero or  it will happen for a line-data record since it does not have a  sequence number.  SYSTEM ACTION: The printing disposition depends upon the error  described in the accompanying messages.  USER RESPONSE: See the specific error conditions described in  the accompanying messages to determine an appropriate response.  SYSTEM PROGRAMMER RESPONSE: See the specific error conditions  described in the accompanying messages to determine an  appropriate response.  OPERATOR RESPONSE: If this message appears on the operator's  console, it indicates that the resource containing the error is  defined for a separator page, for the message data set, or as  the default resource for user print data sets in the PSF  startup procedure. Inform your system programmer.  PROBLEM DETERMINATION: Items 1, 2, 3, 8, 17.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 183 ¤   DOCUMENTATION:  S544-3675-02 "PSF/MVS Messages and Codes"  on page 308, add the following new reason code:  08D4  EXPLANATION: This abend is issued by module APRMSGEX--  CCM has run out of its object stack area. This is a logic  error.  SYSTEM ACTION: PSF processing terminates abnormally.  SYSTEM PROGRAMMER RESPONSE: This PSF abend reason code  indicates a logic error. Contact your service representative  in the IBM Support Center or use your electronic link with IBM  service for assistance regarding this error code.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRINMAZ OW17541  APRMSGEX OW17541  APRSTMAZ OW17541  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW17541 APRINMAZ APRMSGEX APRSTMAZ  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRINMAZ  APRMSGEX  APRSTMAZ  LISTEND  */.   F.17 COVER LETTER FOR PTF UW18208   PROBLEM DESCRIPTION(S):  OW04104 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1 and 2.2.0 users. *  ****************************************************************  * PROBLEM DESCRIPTION: 1. PSF/MVS support for 64xx *  * coax-attached printers configured *  * for native mode. *  * *  * 2. INCORROUT occurs on PSF/MVS 2.2.0 *  * when a form definition requests *  * duplex printing but the printer is *  * unable to print in duplex mode AND *  * a reposition occurs. *  * *  * 3. After applying PTF UW15328 on *  * PSF/MVS 2.2.0, if there is an error *  * in a medium overlay that is required *  * for the page, error sense bytes *   Appendix F. PTF Cover Letter Data for Service Level SMC9618 184 ¤   * SNS0292..01 may be returned by the *  * printer causing an abend ABND024 *  * RC0601. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  1. If a D/T64xx printer is configured in native mode and this  PTF has not been applied, then an ABEND024 RC023D will occur.  2. When a form definition requesting duplex printing is used on  a printer that cannot print in duplex mode, and an error or  operator command causes PSF to reposition, PSF may use the  wrong medium overlay or wrong logical page offset following  the reposition. Another symptom may be that PSF reprints  one or two sheets that is should not have printed following  the reposition.  3. When a medium overlay contains an error that causes the  overlay to NOT be loaded in the printer, PSF is still  requesting that the medium overlay be placed on the sheet.  This will cause the printer to return error sense byte  0292..01.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW04104  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Change the Print Services Facilty/MVS: Messages and Codes,  S544-3675-02:  In Chapter 2 , Systems Completion Codes and PSF Abend Reason  Codes, abend code 023D,  Change the EXPLANATION to read as follows:  APSCSTMI or APSCOPCI -  APSCSTMI or APSCOPCI detected that coded fonts were not  designated as supported by the acknowledgment reply.  ACTION:  This PTF installs new source and object code for APSRFTBL,  the PSF resident font table. If APSRFTBL has been modified,  then it needs to be saved to ensure it does not get replaced by  the new one. Modifications to the previous APSRFTBL needs to be  migrated into the new APSRFTBL and the object code regenerated.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRDCSAZ OW04104  APREAGAZ OW04104  APREPPAZ OW04104  APRIBPAZ OW04104  APRIMGAZ OW04104  APRLCCAZ OW04104  APSCCOMP OW04104  APSCINFO OW04104  APSCOPCI OW04104  APSCSNIO OW04104   Appendix F. PTF Cover Letter Data for Service Level SMC9618 185 ¤   APSCSTMI OW04104  APSECUR OW04104  APSRFTBL OW04104  APSRLRT OW04104  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW04104 APRDCSAZ APREAGAZ APREPPAZ APRIBPAZ APRIMGAZ APRLCCAZ  APSCCOMP APSCINFO APSCOPCI APSCSNIO APSCSTMI APSECUR  APSRFTBL APSRLRT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRDCSAZ  APREAGAZ  APREPPAZ  APRIBPAZ  APRIMGAZ  APRLCCAZ  APSCCOMP  APSCINFO  APSCOPCI  APSCSNIO  APSCSTMI  APSECUR  APSRFTBL  APSRLRT  LISTEND  */.   F.18 COVER LETTER FOR PTF UW17799   PROBLEM DESCRIPTION(S):  OW12168 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1 users who have *  * applied PTF UW15549 or all PSF/MVS 2.2.0 *  * users who have applied PTF UW15550. *  ****************************************************************  * PROBLEM DESCRIPTION: When PSF converts IM1 image to IOCA *  * (IO) image, storage obtained for the *  * conversion is not always freed. This *  * is only a problem for simple IM1 image *  * conversion. *  * *  * Another problem exists where the *  * conversion to IOCA does not always send *  * all the bytes of image data to the *  * printer, causing MSGAPS418I to be *  * issued. *  ****************************************************************   Appendix F. PTF Cover Letter Data for Service Level SMC9618 186 ¤   * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  The new function added for APAR OW10903 is not always freeing  storage that was obtained for converting an IM1 image to an IO  image. IM1 is converted to IO when the IM1 image resolution  does not match the printer resolution. The code that frees the  storage obtained for converting IM1 image to IO image was in a  place that only worked all the time for complex IM1 image, but  not for simple IM1 image.  A variable of an incorrect size is being used to break up the  image data into smaller pieces. This causes the number of bytes  of image data to get truncated.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW12168  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Replace the APS299I message explanation in the PSF/MVS 2.1.1  Messages and Codes manual (S544-3675-01) and the PSF/MVS 2.2.0  Update Guide (G544-3984-00) with the following explanation.  EXPLANATION: This message is issued when PSF converts an  IM image object to an IO image object and one of the image  size values is zero.  For a simple IM image object, this message is issued if  either the XSize or YSize parameter value of the IID  structured field is zero.  For a complex IM image object, this message is issued if  one of the XCSize, YCSize, XFilSize, or YFilSize parameter  values of the ICP structured field is zero.  ACTION:  Currently, the printers that support the IOCA Replicate and Trim  mapping option are the D/T3935, D/T3130, D/T3112, and D/T3116.  To take advantage of this new IPDS support of the IOCA Replicate  and Trim mapping option the D/T3935 and D/T3130 require a new  level of microcode. Without the new level of microcode on these  printers, there will be no reduction (or very little reduction)  in the amount of data sent to the printer when PSF is converting  IM1 shaded areas to IOCA image data. Please have your hardware  Customer Engineer contact hardware Level 2 to obtain the  appropriate microcode levels for these printers.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APREAGAZ OW12168  APRIMGAZ OW12168  APROUTEX OW12168  APSCADD OW12168  APSCINFO OW12168  APSCSNIO OW12168  APSCSTMI OW12168  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW12168 APREAGAZ APRIMGAZ APROUTEX APSCADD APSCINFO APSCSNIO   Appendix F. PTF Cover Letter Data for Service Level SMC9618 187 ¤   APSCSTMI  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APREAGAZ  APRIMGAZ  APROUTEX  APSCADD  APSCINFO  APSCSNIO  APSCSTMI  LISTEND  */.   F.19 COVER LETTER FOR PTF UW09923   PROBLEM DESCRIPTION(S):  OW04452 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 customers using Group3 *  * ESCON (Enterprise Systems Connection) *  * channel-attached printers and Group3 *  * parallel channel-attached printers *  * (AFP1 Family). *  ****************************************************************  * PROBLEM DESCRIPTION: Support is provided for Group3 ESCON *  * channel-attached printers. Support is *  * also provided for Group3 parallel *  * channel-attached printers capable *  * of handling 16K I/O buffers. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  Add the following changes to the PSF/MVS 2.1.1 System  Programming Guide (S544-3672):  ----------------------------------------------------------  On Page 10, following the paragraph "Using RPM with channel..."  add a new section titled "Using ESCON channel-attached printers"  The ESCON attachment provides improvements in data rate,  physical path-length, space requirements and overall system  connectivity.  The dynamic pathing function is also exploited with the ESCON  attachment. To take advantage of dynamic pathing multiple  paths must be defined to the device. Dynamic pathing  provides reliability and performance improvements because  of multiple paths. See the printer hardware manual on how  to define multiple paths to the device.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 188 ¤   The BUFNO minimum value is raised to 9. This provides 2  16K buffers used for I/O, however, consider increasing the  BUFNO value for better performance.  PSF/MVS only supports an ESCON channel-attached printer  in a single host configuration i.e. dynamic printer sharing  is not supported.  If running MVS second-level on VM and dynamic pathing is  active and MVS is re-ipled, the printer may not VARY ONLINE  successfully. If this happens, the channel path must be  disabled then enabled at the printer to clear this condition.  Also, the device must be defined as "unsupported" to VM using  the RDEVICE statement in the system configuration file.   Change the title on page 13 to "Defining Group3 parallel channel  attached Printers (AFP1 Family) with MVSCP".   After page 13, create a new section titled "Defining Group3  ESCON channel-attached Printers (AFP1 Family) with MVSCP"  then add the following under the title.  This configuration definition consists of CHPID, CNTLUNIT and  IODEVICE statements for ESCON channel-attached printers using  a version prior to MVS/ESA 4.1.0. An ESCON channel has an  ESCON channel-to-control unit I/O interface that uses fiber  optic cables as a transmission medium.  PSF/MVS supports the generic device type "AFP1"  for Group3 printers which is specified on the UNIT keyword,  similar to the generic device type of 3800 that is specified  for 3800 printers. This example assumes an ESCON director  (9032, 9033) is not used in the configuration and the printer  is configured with one device per control unit. For infor-  mation on defining with an ESCON director, see the following  publication IOCP User's Guide and ESCON Channel-to-Channel  Reference (GC38-0401).  CHPID PATH=03,TYPE=CNC (CNC indicates an ESCON  channel)  CNTLUNIT CUNUMBR=392,  PATH=03,  UNIT=AFP1, (PROTOCL, SHARED parameters  not needed. LINK parameter  not coded because 9032/9033  not being used)  UNITADD=((92,1))  IODEVICE ADDRESS=392,  CUNUMBR=392, (same as CUNUMBR on CNTLUNIT)  MODEL=0, (optional)  UNIT=AFP1 (TIMEOUT parameter ignored)   Appendix F. PTF Cover Letter Data for Service Level SMC9618 189 ¤    If the printer is configured in dual simplex mode (two devices  behind one control unit), then the following is an example  of the MVSCP statements that could be used. This example also  assumes no ESCON director is used.  CHPID PATH=03,TYPE=CNC  CHPID PATH=04,TYPE=CNC (This CHPID stmt is optional  but is added for performance  reasons)  CNTLUNIT PATH=(03,04),  UNIT=AFP1,  CUNUMBR=392,  UNITADD=((92),(93)) (No LINK or PROTOCL stmt  needed)  IODEVICE CUNUMBR=392,  ADDRESS=392,  UNIT=AFP1,  MODEL=0  IODEVICE CUNUMBR=392,  ADDRESS=393,  UNIT=AFP1,  MODEL=0   On page 15, add the following paragraph after the fourth  paragraph.  When adding an ESCON channel-attached printer, it must be  attached to an ESCON channel (type=CNC).   On page 61, under the BUFNO parameter change "the default value  is 5" to "the minimum BUFNO value is 5, but for ESCON channel-  attached printers and printers that support 16K I/O buffers  the minimum BUFNO value is 9."   On page 112, Table 14 under the BUFNO PRINTDEV entry change  "24K (default = 5)+" to "24K (minimum = 5)+ For parallel  channel-attached printers. 40K (minimum = 9)+ For ESCON  channel-attached printers and printers that support 16K I/O  buffers."  On page 113 under Installation Options, fourth bullet.  Change  "default is 5..." to "minimum is 5, but for ESCON channel-  attached printers and printers that support 16K I/O buffers  the minimum BUFNO value is 9 in real, fixed storage."   Appendix F. PTF Cover Letter Data for Service Level SMC9618 190 ¤   On page 206 seventh paragraph, change "... value at 5,  initially." to "... value at 5, initially, but for ESCON  channel-attached printers and printers that support 16K I/O  buffers set the BUFNO value at 9."   Add the following changes to the PSF/MVS 2.1.1 Messages and  Codes manual (S544-3675-01):  ----------------------------------------------------------  020C  Explanation: This abend is issued by module APSCINIT-  APSCINIT issued the senseid CCW and it failed or it issued  the read configuration data CCW and it failed. This probably  indicates that an I/O error was encountered when the senseid  or read configuration data CCWs were sent to the printer.  System Action: PSF processing terminates abnormally  System Programmer Response: Check the MVS system console log  or run the EREP report for the device to determine the I/O  error. Contact your systems engineer that a hardware error  may have occurred.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW04452  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Add the following changes to the PSF/MVS 2.1.1 System  Programming Guide (S544-3672):  ----------------------------------------------------------  On Page 10, following the paragraph "Using RPM with channel..."  add a new section titled "Using ESCON channel-attached printers"  The ESCON attachment provides improvements in data rate,  physical path-length, space requirements and overall system  connectivity.  The dynamic pathing function is also exploited with the ESCON  attachment. To take advantage of dynamic pathing multiple  paths must be defined to the device. Dynamic pathing  provides reliability and performance improvements because  of multiple paths. See the printer hardware manual on how  to define multiple paths to the device.  The BUFNO minimum value is raised to 9. This provides 2  16K buffers used for I/O, however, consider increasing the  BUFNO value for better performance.  PSF/MVS only supports an ESCON channel-attached printer  in a single host configuration i.e. dynamic printer sharing  is not supported.  If running MVS second-level on VM and dynamic pathing is  active and MVS is re-ipled, the printer may not VARY ONLINE  successfully. If this happens, the channel path must be   Appendix F. PTF Cover Letter Data for Service Level SMC9618 191 ¤   disabled then enabled at the printer to clear this condition.  Also, the device must be defined as "unsupported" to VM using  the RDEVICE statement in the system configuration file.  Change the title on page 13 to "Defining Group3 parallel channel  attached Printers (AFP1 Family) with MVSCP".  After page 13, create a new section titled "Defining Group3  ESCON channel-attached Printers (AFP1 Family) with MVSCP"  then add the following under the title.  This configuration definition consists of CHPID, CNTLUNIT and  IODEVICE statements for ESCON channel-attached printers using  a version prior to MVS/ESA 4.1.0. An ESCON channel has an  ESCON channel-to-control unit I/O interface that uses fiber  optic cables as a transmission medium.  PSF/MVS supports the generic device type "AFP1"  for Group3 printers which is specified on the UNIT keyword,  similar to the generic device type of 3800 that is specified  for 3800 printers. This example assumes an ESCON director  (9032, 9033) is not used in the configuration and the printer  is configured with one device per control unit. For infor-  mation on defining with an ESCON director, see the following  publication IOCP User's Guide and ESCON Channel-to-Channel  Reference (GC38-0401).  CHPID PATH=03,TYPE=CNC (CNC indicates an ESCON  channel)  CNTLUNIT CUNUMBR=392,  PATH=03,  UNIT=AFP1, (PROTOCL, SHARED parameters  not needed. LINK parameter  not coded because 9032/9033  not being used)  UNITADD=((92,1))  IODEVICE ADDRESS=392,  CUNUMBR=392, (same as CUNUMBR on CNTLUNIT)  MODEL=0, (optional)  UNIT=AFP1 (TIMEOUT parameter ignored)  If the printer is configured in dual simplex mode (two devices  behind one control unit), then the following is an example  of the MVSCP statements that could be used. This example also  assumes no ESCON director is used.  CHPID PATH=03,TYPE=CNC  CHPID PATH=04,TYPE=CNC (This CHPID stmt is optional  but is added for performance  reasons)  CNTLUNIT PATH=(03,04),  UNIT=AFP1,  CUNUMBR=392,  UNITADD=((92),(93)) (No LINK or PROTOCL stmt  needed)  IODEVICE CUNUMBR=392,  ADDRESS=392,  UNIT=AFP1,  MODEL=0  IODEVICE CUNUMBR=392,  ADDRESS=393,   Appendix F. PTF Cover Letter Data for Service Level SMC9618 192 ¤   UNIT=AFP1,  MODEL=0  On page 15, add the following paragraph after the fourth  paragraph.  When adding an ESCON channel-attached printer, it must be  attached to an ESCON channel (type=CNC).  On page 61, under the BUFNO parameter change "the default value  is 5" to "the minimum BUFNO value is 5, but for ESCON channel-  attached printers and printers that support 16K I/O buffers  the minimum BUFNO value is 9."  On page 112, Table 14 under the BUFNO PRINTDEV entry change  "24K (default = 5)+" to "24K (minimum = 5)+ For parallel  channel-attached printers. 40K (minimum = 9)+ For ESCON  channel-attached printers and printers that support 16K I/O  buffers."  On page 113 under Installation Options, fourth bullet.  Change  "default is 5..." to "minimum is 5, but for ESCON channel-  attached printers and printers that support 16K I/O buffers  the minimum BUFNO value is 9 in real, fixed storage."  On page 206 seventh paragraph, change "... value at 5,  initially." to "... value at 5, initially, but for ESCON  channel-attached printers and printers that support 16K I/O  buffers set the BUFNO value at 9."  Add the following changes to the PSF/MVS 2.1.1 Messages and  Codes manual (S544-3675-01):  ----------------------------------------------------------  020C  Explanation: This abend is issued by module APSCINIT-  APSCINIT issued the senseid CCW and it failed or it issued  the read configuration data CCW and it failed. This probably  indicates that an I/O error was encountered when the senseid  or read configuration data CCWs were sent to the printer.  System Action: PSF processing terminates abnormally  System Programmer Response: Check the MVS system console log  or run the EREP report for the device to determine the I/O  error. Contact your systems engineer that a hardware error  may have occurred.  ACTION:  IECVAFP1, which is a member of SYS1.NUCLEUS, has been modified,  therefore a re-ipl will need to be done to pick up the  changes.  IGE0000E has also been modified and resides in PLPA so a re-ipl  will be necessary to rebuild PLPA.  CBDUS022 must be installed in SYS1.NUCLEUS before defining  a Group3 ESCON channel-attached printer using HCD.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APROUTEX OW04452  APSCADD OW04452  APSCBMGR OW04452  APSCESTA OW04452  APSCINIT OW04452  APSCPRCT OW04452   Appendix F. PTF Cover Letter Data for Service Level SMC9618 193 ¤   APSCTERM OW04452  APSGDUMP OW04452  CBDUS022 OW04452  IECVAFP1 OW04452  IGE0000E OW04452  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW04452 APROUTEX APSCADD APSCBMGR APSCESTA APSCINIT APSCPRCT  APSCTERM APSGDUMP CBDUS022 IECVAFP1 IGE0000E  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APROUTEX  APSCADD  APSCBMGR  APSCESTA  APSCINIT  APSCPRCT  APSCTERM  APSGDUMP  CBDUS022  IECVAFP1  IGE0000E  LISTEND  */.   F.20 COVER LETTER FOR PTF UW09923   PROBLEM DESCRIPTION(S):  OW08338 -  ****************************************************************  * USERS AFFECTED: ALL PSF/MVS 2.1.0, 2.1.1 and 2.2.0 users *  * who use the PSF/2 PSF Direct function. *  ****************************************************************  * PROBLEM DESCRIPTION: Support is provided for the PSF/2 *  * PSF Direct. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  Support is added for the PSF/2 PSF Direct.  Support is provided in a similar manner as  to that provided by RPM2, except PSF Direct  does not provide PS/2 resource caching.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW08338  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  In the Print Services Facility/MVS System Programming Guide   Appendix F. PTF Cover Letter Data for Service Level SMC9618 194 ¤   Version 2.1.1 (S544-3672-01) on page 154 under  "Exit-Communications Areas (APSUECA and APSUECE)" in Figure  55 "Format of Exit-Communications Area (APSUECA)" change the  following.  1. At offset 55 (37) which has already been changed to  ECAFLAG by a previous apar, add the following new flag  after ECAMFTRL (also added by the same previous apar).  ECALSTDS EQU B'01000000' Last or only dataset  0 = Not the last or only  dataset of the job  1 = Last or only dataset  of the job  DOCUMENTATION:  The following PSF/MVS publications are affected by this APAR:  In the Print Services Facility/System Programming Guide  Version 2 Release 1 Modification 1 (S544-3672-01) make the  following changes.  #1 Page 17 Chapter 3. change the the fourth paragraph to  read as follows.  Do not use this chapter when configuring printers supported  through the Distributed Print Function(DPF) or PSF Direct  of PSF/2. Instead, refer to  Advanced Function Presentation Print Services Facility for  OS/2: A Network Configuration Guide for System/370 and  Communications Manager/2 Version 2.00.  The graphics contain DPF, RPM and PSF Direct together  because conceptually they work the same way. The details of  configuration, however, are different.  #2 Page 62 Chapter 6 Table 11 parameter DISCINTV change Notes:  to read as follows.  1. For RPM, PSF Direct and SNA-attached printers only.  #3 Page 65 Chapter 6 Table 11 parameter NPRO change Notes:  to read as follows.  1. This parameter is for only direct printing mode with  channel-attached printers.  2. In deferred-printing mode, the value for NPRO is derived  from the JES NPRO definition. The PSF NPRO parameter  described above has no affect.  Delete note 5. which has been moved to 2.  #4 Page 123 Chapter 11 "Supporting Resident Fonts" add a new  sentence after the last sentence to read as follows.  PSF Direct, however, does support printer resident fonts  in both utility and symbol set access methods.  #5 Change the "Exit-Communications Areas" in Chapter 13 page 155  Figure 56 - "Format of Exit-Communications Area Extension"  (APSUECE) as follows.  Offsets Type Length Name Description  83 (53) Bitstring  .1.. .... ECERPM RPM is attached  ..1. .... ECEDPF DPF is attached  ...1 .... ECEPSFD PSF Direct is attached  .... 1111 * Reserved  #6 Page 202 Chapter 14 change the heading to read as follows.  Remote PrintManger, Distributed Print Function or PSF Direct   Appendix F. PTF Cover Letter Data for Service Level SMC9618 195 ¤   #7 Page 202 Chapter 14 change the first two sentences to read.  Printers can be remotely attached with Remote PrintManager  Version 2 (RPM 2.0), Remote PrintManager Version 3 (RPM 3.0),  PSF/2 Distributed Print Function (DPF), or PSF/2 PSF Direct.  PSF can send the print data to PSF Direct, DPF or RPM over a  SDLC line, over a local token ring, or over a remote token ring.  #8 Page 202 Chapter 14 Add a new section after RPM Version 2:  to read as follows.  PSF Direct: In a PSF/2 PSF Direct configuration, PSF sends the  print data set to PSF Direct, which passes the data set to  a PSF/2 supported attached printer. PSF Direct does not support  remote resource caching.  When installing and configuring PSF Direct, consider the  following:  * Data rate capability of the printer  * Data rate capability of the host attachment  * Data rate requirements of the print data set  #9 Page 202 Chapter 14 change the last sentence to read.  The maximum data rates in RPM Version 3 or DPF can be lower  than RPM Version 2 with RPM Library Mode OFF or PSF/2 PSF  Direct, depending on attachment speeds.  #10 Page 311 GLOSSARY add.  PSF Direct. A PSF/2 function that provides remote attachment  from the host PSF to any PSF/2 supported printer.  In the Print Services Facility/MVS Messages and Codes Version 2  Release 1 Modification 1 (S544-3675-01) make the following  changes.  #1 Add to message APS922I after DEALLOCATE-ABEND a new CAUSE  to read as follows.  DEALLOCATE-TIMER. The remote transaction program has  deallocated the communication with TYPE(ABEND_TIMER)  because its Device Busy Timer has expired.  #2 Change message APS933I to read as follows.  PRINTER INFORMATION DEV=pppp, ADDR=cuu|luname,  SYSNAME=ssssssss, CPUID=cccccccccccc, ATTACH=psf|rpm2|  rpm3|dpf|psfdirect.  #3 Change the last sentence in the "Explanation" for message  APS933I to read as follows.  ATTACH indicates whether the printer is attached by Remote  PrintManager 2 (RPM2), Remote PrintManager 3 (RPM3),  Print Services Facility (PSF), PSF/2 Distributed Print  Function (DPF), or PSF/2 PSF Direct (PSFDIRECT).  #4 Change the OPERATOR RESPONSE for message APS933I to read  as follows.  Ensure the correct printer device type was  started and attached correctly (CUU or LUNAME and PSF,  RPM2, RPM3, DPF or PSFDIRECT).  DOCUMENTATION:  In the Print Services Facility/MVS Messages and Codes Version 2  Release 1 Modification 1 (S544-3675-01) make the following  changes.  1. Change message APS933I to read as follows.  PRINTER INFORMATION, DEV=pppp, ADDR=cuu|luname,  SYSNAME=ssssssss, CPUID=cccccccccccc, ATTACH=psf|rpm2|   Appendix F. PTF Cover Letter Data for Service Level SMC9618 196 ¤   rpm3|dpf.  2. Change the last sentence in the "Explanation" for message  APS933I to read as follows.  ATTACH indicates whether the printer is attached by Remote  PrintManager 2 (RPM2), Remote PrintManager 3 (RPM3),  Print Services Facility (PSF), or Distributed Print  Manager (DPF) of PSF/2.  3. Change the note following the "Explanation" for message  APS933I to read as follows:  NOTE: If RPM 2.0 is in use and library mode is off, this  parameter will be ATTACH=PSF.  4. Change the OPERATOR RESPONSE for message APS933I to  read as follows.  Ensure that the correct printer device type was started  and attached correctly (CUU or LUNAME and PSF, RPM2,  RPM3, or DPF).  COMMENTS:  When RPM3 was initially released, PSF/MVS was not able to  distinguish between RPM3 and RPM2. Service level RPM 3.0.6F  corrected this. Therefore MSGAPS933I will only specify  ATTACH=RPM3 if your RPM3 is at service level 3.0.6F or above.  Before this service level, MSGAPS933I will specify ATTACH=RPM2  when connected to remote print manager 3.  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSCCDEV OW08338  APSCESTA OW08338  APSCRPII OW08338  APSCSNA OW08338  APSCSNIO OW08338  APSUECA OW08338  APSUEXIT OW08338  APSUNEXT OW08338  APSUREXT OW08338  DCKCPG7E OW08338  DCKCPRCE OW08338  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW08338 APSCCDEV APSCESTA APSCRPII APSCSNA APSCSNIO APSUECA  APSUEXIT APSUNEXT APSUREXT DCKCPG7E DCKCPRCE  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APSCCDEV  APSCESTA  APSCRPII  APSCSNA  APSCSNIO  APSUEXIT  APSUNEXT  APSUREXT  DCKCPG7E  DCKCPRCE   Appendix F. PTF Cover Letter Data for Service Level SMC9618 197 ¤   MACROS  APSUECA  LISTEND  */.   F.21 COVER LETTER FOR PTF UW14135   PROBLEM DESCRIPTION(S):  OW09512 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0 and 2.2.0 users *  ****************************************************************  * PROBLEM DESCRIPTION: MSGAPS102I is issued when a partitioned *  * data set member is empty or a premature *  * end-of-file has been reached. It is *  * not clear from the message which *  * problem it is or what member it is. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  MSGAPS102I is issued for a partitioned data set member when  a member is empty or when a premature end-of-file has been  reached. In some cases, it does not give the member name  of the resource in error.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW09512  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  PSF/MVS: Messages and Codes, S544-3675  Replace APS102I with:  APS102I AN END OF FILE WAS FOUND BEFORE THE LOGICAL END  OF A RESOURCE OR THE RESOURCE CONTAINED NO DATA.  THE MEMBER NAME OF THE RESOURCE IS 'member name'.  Explanation: (1) The end of file for a resource was found before  the End-type structured field, causing the resource definition  to be incomplete or (2) The resource existed as a member of  a partitioned data set, however no data was found in the member.  System Action: PSF stops processing the current page, and any  accumulated data for the current page is printed. PSF attempts  to locate the end of the current page and to resume printing on  the next page. If the end of the page cannot be located, PSF  stops printing the data set. PSF issues additional messages that  identify the processing environment when the error was found.  User Response: (1) If you created the structured fields for the  resource, correct the error and resubmit the print request or  (2) If you created the empty partitioned member for the  resource, correct the error by creating a resource that  contains the structured fields for the resource type that  you want and resubmit the print request. Refer to Mixed   Appendix F. PTF Cover Letter Data for Service Level SMC9618 198 ¤   Object Document Content Architecture Reference for more  information about the structured fields.  If the structured field has no error, the error may be a PSF  logic error. If you used a program to create the structured  fields for the resource, contact your system programmer.  System Programmer Response: If an IBM licensed program was used  to create the structured fields for the resource with the error,  verify that the input to that program was valid. If the input  was valid, refer to Advanced Function Printing: Diagnosis Guide  and Print services Facility/MVS: Diagnosis Guide and Reference  for assistance in determining the source of the problem. If the  error involves separator pages or the message data set, use the  information provided in the User Response section to correct  the error.  Operator Response: If this message appears on the operator's  console, it indicates that the resource containing the error  is defined for a separator page, for the message data set, or  as the default resource for user print data sets in the PSF  startup procedure. Inform your system programmer.  Problem Determination: items 1, 2, 3, 15c, 17, 19.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRINPEX OW09512  APSDECH OW09512  APSDGET OW09512  APSMSTXT OW09512  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW09512 APRINPEX APSDECH APSDGET APSMSTXT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRINPEX  APSDECH  APSDGET  APSMSTXT  LISTEND  */.   F.22 COVER LETTER FOR PTF UW16360      Appendix F. PTF Cover Letter Data for Service Level SMC9618 199 ¤   PROBLEM DESCRIPTION(S):  OW10928 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users. *  ****************************************************************  * PROBLEM DESCRIPTION: 1. The media origin is not the same *  * for the D/T3800 and D/T3900 when the *  * leading edge is the long side of the *  * paper or when a form definition that *  * specifies a PRESENT/DIRECTION of some- *  * thing other than PORTRAIT/ACROSS is *  * used and the leading edge is the short *  * side of the paper. *  * *  * 2. The IPDS Eject to Front-Facing order *  * will not always be sent to the printer *  * correctly when being controlled by *  * the XTP7ETFF and XTP7EFFH flags in *  * APSUX07 if an error occurs and PSF *  * has to reposition back into the *  * previous dataset. *  * *  * 3. The spoof proof number on the *  * security trailer separator sheet *  * will not always be correct if an *  * error occurs and PSF has to reposition *  * back into the previous dataset. *  * *  * 4. The control of the interrupt message *  * page (number of copies, offset *  * stacking, mark forms) by the exit *  * fields XTP7IPMF, XTP7IPOS, XTP7IPCC *  * in APSUX07 will not always be correct *  * if an error occurs and PSF has to *  * reposition back into the previous *  * dataset. *  * *  * 5. After applying PTF UW11131 the *  * spoof proof number will disappear from *  * the security header (APSUX01S) and *  * the security trailer (APSUX02S) pages. *  * *  * 6. After applying PTF UW11131 the *  * control of the interrupt message page *  * (number of copies, offset stacking, *  * mark forms) by the exit fields *  * XTP7IPMF, XTP7IPOS, XTP7IPCC in APSUX07 *  * will cause unpredictable results. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  1. When the leading edge of the paper is the long side of the  paper or when the leading edge of the paper is the short side of   Appendix F. PTF Cover Letter Data for Service Level SMC9618 200 ¤   the paper and the form definition specifies a PRESENT/DIRECTION  of something other than PORTRAIT/ACROSS, the D/T3800 and the  D/T3900 do not have the same media origin. This requires  modifications when migrating from the D/T3800 to the D/T3900.  (NOTE: PSF provides various form definitions specifying various  presentation controls.)  2. When using XTP7ETFF and XTP7EFFH on the BDS call for APSUX07  to control the sending of the IPDS Eject to Front-Facing order,  the order will not always be sent to the printer correctly  if an error occurs and PSF has to reposition back into the  previous dataset.  3. When using the security header and trailer installation  separator pages, the spoof proof number on the trailer sheet  will not always match the spoof proof number on the header  sheet if an error occurs and PSF has to reposition back into  the previous dataset.  4. When controlling the interrupt message page with XTP7IPMF,  XTP7IPOS, and XTP7IPCC on the BDS call for APSUX07, this  control will not always be correct if an error occurs and PSF  has to reposition back into the previous dataset.  5. After applying PTF UW11131 the spoof proof number will  not be printed on the security header and security trailer  separator pages.  6. After applying PTF UW11131 the control of the interrupt  message page with XTP7IPMF, XTP7IPOS, and XTP7IPCC will  cause unpredictable results.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW10928  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Modify the PSF/MVS System Programming Guide Version 2.1.1,  S544-3672:  On page 99,  under System Management Facility Type 6 Records,  change "Logical-page count" to "Impression count".  On page 155,  add the following to Figure 56 Format of Exit Communications  Area Extension (APSUECE)  Offsets Type Length Name Description  104 (68) Signed 4 ECEJOBLP Logical pages in the job  108 (6C) Signed 4 ECEJOBIM Impressions (sides) in the job  112 (70) Signed 4 ECEJOBPP Physical pages in the job  212 (D4) Signed 4 ECEIMPS Impressions (sides) printed for  the data set  DOCUMENTATION:  1. In the Print Services Facility/MVS: Diagnosis Guide and  Reference (LH40-0205-00) in Appendix A: Message-to-Module   Appendix F. PTF Cover Letter Data for Service Level SMC9618 201 ¤   Cross Reference on page 50 add the following message after  APS207I.  APS209I APRIBPAZ  2. In the Print Services Facility/MVS: Diagnosis Guide and  Reference (LH40-0205-00) in Appendix C: PSF Reason Codes  and Return Codes on page 66 add the following return code  after X'08140136'.  X'08140140' The media origin override request by  installation exit APSUX07 has been  ignored and the FORMDEF resource used.  3. In the Print Services Facility/MVS Messages and Codes  Version 2 Release 1 Modification 1 (S544-3675-01)  on page 43 add the following message after APS207I.  APS209I DATA IN FORMDEF RESOURCE formdef name IS NOT  ACCEPTABLE FOR MEDIA ORIGIN OVERRIDE AS  REQUESTED BY INSTALLATION EXIT APSUX07.  Explanation: Installation exit 7 requested that the  media origin be changed to match the  3800 media origin, but the form definition  specified N_UP, Page Modification Controls,  or Post-processing controls. These functions  are not acceptable when overriding the media origin.  System Action: The media origin override request is  ignored and PSF continues processing using the  current form definition and its requested functions.  User Response: No response is necessary.  System Programmer Response: No response is necessary.  Operator Response: No response is necessary.  Problem Determination: None  4. In the Print Services Facility/MVS System Programming  Guide Version 2.1.1 (S544-3672-01) in Chapter 13 "Using  Installation Exits" on page 180 add a new section  entitled "3800 Compatible Media Origin Considerations"  that reads as follows.  APSUX07 can aid in the migration from the 3800 printers to  the 3835 or 3900 printers by setting the printer media origin  to match that of the 3800. One of the major differences  between the 3800 and other AFP continuous-forms printers  is the location of the media origin. See Appendix A  "Compatibility, Conversion, and Performance" in the AFP  Printer Information Manual for a discussion  of the differences in media origin between  AFP printers. When migrating 3800 print jobs,  you can provide a compatible media origin  by including the proper presentation options in the form  definition resource used for each job. Alternatively, you can  tailor APSUX07 to enforce a 3800-compatible form origin  for any designated job.  This compatibility of APSUX07 should be used for migration  purposes only!! Jobs designated by this exit bit should not  specify capabilities that are not supported by the 3800  printer, such as N_UP, page modification controls, or  post-processing controls. If, for example, N_UP is specified  in the form definition of a job designated as 3800   Appendix F. PTF Cover Letter Data for Service Level SMC9618 202 ¤   compatible, the 3800-compatible bit will be ignored.  The job will process using the N_UP capabilities of the  3900 or 3835 to which it is sent, but a warning message  will be issued noting the conflict between the exit bit and  the form definition.  If the exit bit is set for a job that is routed to a  cut-sheet printer or routed to a continuous forms printer  that does not support changeable media origin,  the exit bit will be ignored but no message will be  issued.  With APSUX07, you can control whether to set the media  origin to the 3800 media origin using one flag.  XTP738MO Controls setting the media origin on  continuous forms printers to the 3800 media  origin.  This flag defaults to 0. The default specifies that PSF  will not set the media origin to the 3800 media origin.  If the flag is set to 1, then PSF will set the media  origin to the 3800 media origin. Only the media origin  of the user's dataset will be changed to match the  media origin of the 3800. The media origin of the  separator pages, the interrupt message page, and the  message dataset will be unchanged. This flag may be set  during the INIT call or the BDSC call and remains set  between calls; only APSUX07 can change the state of this  flag.  5. In the Print Services Facility/MVS System Programming  Guide Version 2.1.1 (S544-3672-01) in Chapter 13 "Using  Installation Exits" on page 183 add a new paragraph  after the 3rd paragraph on the page that starts "This  call can also be used to control ETFF....." that  reads as follows.  This call can be used to control whether to set the media  origin to the 3800 media origin. See "3800 Compatible  Media Origin Considerations" on page 180 for more  information.  6. In the Print Services Facility/MVS System Programming  Guide Version 2.1.1 (S544-3672-01) in Chapter 13 "Using  Installation Exits" on page 184 add a new bullet under  Begin-Data-Set Call (BDSC) that reads as follows.  o Control setting the media origin to the 3800 media origin.  See "3800 Compatible Media Origin Considerations" on page  180 for more information.  7. In the Print Services Facility/MVS System Programming  Guide Version 2.1.1 (S544-3672-01) in Appendix D "Field  Descriptions for APSUX07" in Figure 62 on page 259 add  the following after XTP7IPSU and change the following  RESERVED field.  .... 1... XTP738MO Set the media origin to the 3800  media origin  (Valid for initialization  "XTP7INIT" and BDS "XTP7BDS")  1 = Set media origin to 3800  media origin   Appendix F. PTF Cover Letter Data for Service Level SMC9618 203 ¤   0 = Do not set media origin to  3800 media origin  .... .111 * Reserved  8. In the Print Services Facility/MVS System Programming  Guide Version 2.1.1 (S544-3672-01) in Appendix D "Field  Descriptions for APSUX07" on page 263 add  the following after XTP7IPSU.  XTP738MO This field is valid only on the INIT and BDSC  calls. PSF initially sets this field to B'0'  to indicate to not set the media origin to  the 3800 media origin. If APSUX07 sets this  flag to B'1', then PSF will set the media  origin to the 3800 media origin.  9. In the Print Services Facility/MVS System Programming  Guide Version 2.1.1 (S544-3672-01) in Appendix D "Field  Descriptions for APSUX07" on page 275 after XTP7IPSU  in the table "Processing Indicator Cross-Reference  for APSUX07" add the following.  XTP738MO IO IO  The "IO"s above go under the INIT and BDSC headings in the  table.  ACTION:  If you have modified your source code for APSUECA or APSGEXTP,  then save it before applying this PTF as this PTF will replace  your copy of APSUECA and APSGEXTP.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRBPGEX OW10928  APRDCSAZ OW10928  APRDOCEX OW10928  APREPGEX OW10928  APRFDPAZ OW10928  APRIBPAZ OW10928  APRINMAZ OW10928  APRINPEX OW10928  APRMSGEX OW10928  APSDDOC OW10928  APSDDS OW10928  APSDECH OW10928  APSGEXTP OW10928  APSMSTXT OW10928  APSPPDCM OW10928  APSPPDVP OW10928  APSPPFSA OW10928  APSPPGDS OW10928  APSPPSEP OW10928  APSPPSMF OW10928  APSQENQ OW10928  APSUECA OW10928  APSUEXIT OW10928  APSUNEXT OW10928  APSUREXT OW10928  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES   Appendix F. PTF Cover Letter Data for Service Level SMC9618 204 ¤   OW10928 APRBPGEX APRDCSAZ APRDOCEX APREPGEX APRFDPAZ APRIBPAZ  APRINMAZ APRINPEX APRMSGEX APSDDOC APSDDS APSDECH  APSGEXTP APSMSTXT APSPPDCM APSPPDVP APSPPFSA APSPPGDS  APSPPSEP APSPPSMF APSQENQ APSUECA APSUEXIT APSUNEXT  APSUREXT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRBPGEX  APRDCSAZ  APRDOCEX  APREPGEX  APRFDPAZ  APRIBPAZ  APRINMAZ  APRINPEX  APRMSGEX  APSDDOC  APSDDS  APSDECH  APSMSTXT  APSPPDCM  APSPPDVP  APSPPFSA  APSPPGDS  APSPPSEP  APSPPSMF  APSQENQ  APSUEXIT  APSUNEXT  APSUREXT  MACROS  APSGEXTP  APSUECA  LISTEND  */.   F.23 COVER LETTER FOR PTF UW11285   PROBLEM DESCRIPTION(S):  OW07348 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users who wish to select *  * the media-destination (output bin) for a *  * job or data set. *  ****************************************************************  * PROBLEM DESCRIPTION: PSF/MVS 2.2.0 users lack the capability *  * to select the media-destination (output *  * bin) for a job or data set. *   Appendix F. PTF Cover Letter Data for Service Level SMC9618 205 ¤   ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  This APAR adds support for Media-Destination  (output bin) Selection for a job or data set.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW07348  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  In the PSF/MVS Messages and Codes manual, Version 2 Release 2  Modification 0, message APS225I has changed.  The message text is now:  'SYSTEM ACTION TAKEN: THE ERRORS LISTED PREVENTED  PRINTING OF THE DATA SET. THE DATA SET WILL BE HELD.'  Under Explanation, the next to the last sentence  has changed to the following:  'PSF marked the data set unprintable, and returned the data  set to the Job Entry Subsystem (JES) to be held by the system.'  DOCUMENTATION:  Update the PSF/MVS publications as follows:  PSF/MVS: Application Programming Guide, S544-3673-01  -----------------------------------------------------  Chapter 2, page 39, figure 22, add the new OUTBIN parameter:  OUTBIN=bin-number  Chapter 2, page 50, add explanation for new OUTBIN keyword:  OUTBIN=bin-number  Specifies the output bin to use for the job or data set.  The valid range is 1 to 65535.  If the OUTBIN keyword is not specified or if the printer  does not support output bin selection, the output will be  sent to the printer default output bin.  EXAMPLE:  In the following example, output bin 2 is selected  for the job:  //OUTPUT1 OUTPUT OUTBIN=2  PSF/MVS: Messages and Codes, S544-3675-01  -----------------------------------------------------  Add the following new messages:  APS360I OUTPUT BIN 'bin number' WAS REQUESTED FOR JOB  'jobname', BUT EITHER THE PRINTER DOES NOT SUPPORT  OUTPUT BIN SPECIFICATION OR THE BIN SPECIFIED WAS NOT  AVAILABLE. THE PRINTER DEFAULT BIN WAS USED.  Explanation: The OUTBIN keyword on the JCL OUTPUT statement  specified an output bin that is not available, or the device  does not support specification of an output bin.  System Action: PSF continues processing, sending paper to the  printer default output bin.  User Response: If the output is not acceptable, submit the print  request to a printer that supports specification of an output  bin and has the output bin available, or ensure that the bin  is enabled on the original printer before resubmitting the print  request   Appendix F. PTF Cover Letter Data for Service Level SMC9618 206 ¤   System Programmer Response: No response is necessary.  Operator Response: No response is necessary.  Problem Determination: 1,2,8,19  APS361I OUTPUT FOR JOB 'jobname' CANNOT BE SENT TO OUTPUT BIN  'bin #' DUE TO A PRINTER BIN AVAILABILITY CHANGE.  REMAINING OUTPUT WILL BE SENT TO OUTPUT BIN 'bin #'  OR THE DATA SET WILL BE TERMINATED.  Explanation: The output bin characteristics changed while the  data set was printing. The output may be in two different bins.  This can happen for the following reasons:  1. The data set was printing to the default bin, and that bin  became unavailable for some reason. The printer will pick a  new default output bin, and the data set will continue  printing and will be sent to that bin.  2. The data set specified an output bin with the OUTBIN keyword  on the JCL OUTPUT statement, but that output bin was  unavailable when PSF began printing the data set so it was  sent to the default output bin. While PSF was printing the  data set, the specified output bin became available so PSF  sent the remainder of the data set to the specified bin.  System Action: If mandatory print labeling is enabled, the data  set is terminated. If mandatory print labeling is not enabled,  PSF continues processing, and the portion of the data set that  has not completed is sent to either the printer default output  bin or the specified output bin, if it is now available.  User Response: If the output is not acceptable, submit the  print request to a printer that has the output bin available for  the entire duration of the processing of the data set.  System Programmer Response: No response is necessary.  Operator Response: Combine the data set output from the bins  identified in the error message.  Problem Determination: 1,2,8,19  APS872I THE SPECIFIED INPUT BIN CANNOT BE USED WITH THE  SPECIFIED OUTPUT BIN.  Explanation: The paper size in the input bin selected is  not compatible with the output bin selected for the data set.  The input bin is either the printer default input bin, or  the bin specified in the form definition for the data set.  The output bin is either the printer default output bin,  or the bin specified on the OUTBIN keyword on the JCL OUTPUT  statement for the data set.  System Action: PSF will release the current data set back to  JES and will request that it be held by the system.  System User Response: If you specified an output bin with the  OUTBIN keyword, and it is the wrong output bin, change the  bin and resubmit the print job.  System Programmer Response: No response is necessary.  System Operator Response: No response is necessary.  Problem Determination: Items 1, 2, 17, 27.  APS874I OUTPUT BIN bin number WAS REQUESTED BUT CANNOT BE  USED WITH INPUT BIN bin number.  Explanation: The paper size in the input bin selected is not  compatible with the output bin selected for the data set. The  input bin is either the printer default input bin, or the bin   Appendix F. PTF Cover Letter Data for Service Level SMC9618 207 ¤   specified in the form definition for the data set. The output  bin is either the printer default output bin, or the bin  specified on the OUTBIN keyword on the JCL OUTPUT statement  for the data set.  System Action: PSF will release the current data set back to  JES and will request that it be held by the system.  System User Response: If you specified an output bin with the  OUTBIN keyword, and it is the wrong output bin, change the bin  and resubmit the print job. If the bin values are correct,  then the data set must have been sent to a printer with a bin  configuration which was not compatible with the bins requested  for the data set. Contact your Operator to determine to which  printer the data set should be rerouted.  System Programmer Response: No response is necessary.  System Operator Response: If you are running under Job Entry  Subsystem (JES), use the JES data-set release commands to  release the data set to a printer with consistent bins. Refer  to the publication containing JES commands for your operating  system for a JES command to release the data set for printing.  Problem Determination: Items 1, 2, 17, 27.  APS930I PRINTER ("prtnnn"), WHICH IS A ("printer model"),  SPECIFIED AN INVALID OUTPUT BIN ID RANGE OF  (first bin ID) - (last bin ID)  Explanation: During the processing of the OPC response, an  invalid output bin range was detected. An invalid output bin  range means that the last id in the range is incorrectly less  than the first id in the range.  System Action: This message is issued during PSF initialization  and the invalid output bin range is ignored. PSF initialization  continues.  User Response: No response is necessary.  System Programmer Response: This indicates a possible logic  error within the microcode of the printer. Contact your micro-  code service representative in the IBM Support Center for  assistance regarding this error.  Operator Response: PSF initialization continues without  operator assistance. It is possible that some output bins on  the printer will not be available for use. It may be useful  to reenable the bins or perform a power-on-reset.  Problem Determination: 1,18  Make the following changes to existing messages:  Message APS061I:  Message Text: THE ERRORS LISTED PREVENTED PRINTING OF THE  JOB. ALL DATASETS IN THE JOB WILL BE HELD.  Explanation: While processing the job, PSF detected an error  that makes printing the job in a secure environment impossible.  PSF/MVS: Program Directory, G544-3668-02  -----------------------------------------------------  Under section 5.2.4 PSF/MVS Version 2.2.0 Requirements for  Special Functions add the following:  For Media-Destination Selection Support:  - MVS/ESA SP Version 4 Release 2.0 (5695-047) with  PTF UW90066. For use with JES2, no additional requirements  exist. For use with JES3, the system must be at or above:   Appendix F. PTF Cover Letter Data for Service Level SMC9618 208 ¤   - MVS/SP JES3 Version 4 Release 2.1 (5695-048) with  APAR OW07286  - MVS/ESA SP Version 4 Release 3.0 (5695-047) with  PTF UW90067. For use with JES2, no additional requirements  exist. For use with JES3, the system must be at or above:  - MVS/SP JES3 Version 4 Release 2.1 (5695-048) with  APAR OW07286  - MVS/ESA SP Version 5 Release 1.0 (5655-069) with  PTF UW90068. For use with JES2, no additional requirements  exist. For use with JES3, the system must be at or above:  - MVS/SP JES3 Version 4 Release 2.1 (5695-048) with  APAR OW07286  - SDSF Version 1 Release 4.0 (HQX1400) with  APAR PN60152  PSF/MVS: Diagnosis Guide and Reference, LH40-0205-00  -----------------------------------------------------  In Appendix A: Message-To-Module Cross Reference, add the  following message-to-module entries to the table:  Message Module(s)  ------- ---------  APS360I APSDDS  APRLCCAZ  APS361I APSDDS  APS872I APSEATCD  APS874I APSEATCD  APS930I APSCOPCI  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRDOCEX OW07348  APRMSGEX OW07348  APSDDS OW07348  APSDECH OW07348  APSEATCD OW07348  APSECUR OW07348  APSGDUMP OW07348  APSJCL OW07348  APSMSTXT OW07348  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW07348 APRDOCEX APRMSGEX APSDDS APSDECH APSEATCD APSECUR  APSGDUMP APSJCL APSMSTXT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRDOCEX  APRMSGEX  APSDDS  APSDECH  APSEATCD  APSECUR  APSGDUMP  APSJCL  APSMSTXT   Appendix F. PTF Cover Letter Data for Service Level SMC9618 209 ¤   LISTEND  */.   F.24 COVER LETTER FOR PTF UW09797   PROBLEM DESCRIPTION(S):  OW06631 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users who want to suppress *  * the interrupt message page. *  ****************************************************************  * PROBLEM DESCRIPTION: An interrupt message page is not always *  * desired to be printed. There needs to *  * be a way to suppress an interrupt *  * message page via installation exits. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  There needs to be a way to suppress the interrupt message page  via installation exits for those customers who do not wish to  have the interrupt message page printed.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW06631  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  In the Print Services Facility/MVS System Programming Guide  Version 2.1.1 (S544-3672-01) make the following changes.  1. On page 180 add a new section entitled "Interrupt Message  Page Suppression Considerations" that reads as follows:  With APSUX07, you can control whether the interrupt  message page that PSF inserts in your printed output  is printed using 1 flag:  XTP7IPSU Controls the suppression of the  interrupt message page.  This flag defaults to 0. The default specifies that PSF  will print the interrupt message page. If the flag is  set to 1, then PSF will suppress the interrupt message  page. The flag may be set during the INIT call  and remains set between calls; only APSUX07 can  change the state of this flag.  2. On page 183 under section "Initialization Call (INIT)"  add the following paragraph at the end of the section:  This call can be used to control the suppression of the  interrupt message page. See "Interrupt Message Page  Suppression Considerations" on page 180 for more  information.  3. On page 259 under "21 (15) BITSTRING 1" after flag  XTP7IPOS add the following flag:  .1.. .... XTP7IPSU SUPPRESS INTERRUPT MESSAGE PAGES   Appendix F. PTF Cover Letter Data for Service Level SMC9618 210 ¤   (VALID FOR INITIALIZATION  "XTP7INIT")  1 = SUPPRESS INT MSG PAGES  0 = ALLOW INT MSG PAGES  4.On page 263 after XTP7IPOS add the following:  XTP7IPSU  This field is valid only on the INIT call.  PSF initially sets this field  to B'0' to indicate that interrupt message pages  are to be printed. See "Interrupt Message Page  Suppression Considerations" on page 180 for more  information. If APSUX07 sets this field to B'1',  then interrupt message pages will be suppressed  by PSF.  In the Print Services Facility/MVS: Diagnosis Guide and  Reference (LH40-0205-00) make the following changes.  1. In Appendix A. "Message-To-Module Cross Reference" add the  new message APS074I into the table on page 49 in the correct  numerical sequence after APS068I as follows.  APS074I APSPPDVP  In the Print Services Facility/MVS Messages and Codes Version  2 Release 1 Modification 1 (S544-3675-01) make the following  changes.  1. On page 14 after APS072I add the following new error message.  APS074I AN INTERRUPT MESSAGE PAGE WOULD HAVE BEEN  GENERATED BUT INSTALLATION EXIT APSUX07  HAS SUPPRESSED IT.  Explanation: The interrupt message page that PSF inserts  in your printed output was suppressed because  APSUX07 was written to suppress it.  System Action: Processing continues without the interrupt  message page being printed.  User response: If you feel that this message has been issued  incorrectly, then inform your system  programmer and have him check APSUX07 for  correctness.  System Programmer Response: Ensure that XTP7IPSU is set  correctly by APSUX07.  Operator Response: No response is necessary.  Problem Determination: Items 1 and 3  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSGEXTP OW06631  APSMSTXT OW06631  APSPPDCM OW06631  APSPPDVP OW06631  APSUEXTI OW06631  APSUREXT OW06631  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW06631 APSGEXTP APSMSTXT APSPPDCM APSPPDVP APSUEXTI APSUREXT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:   Appendix F. PTF Cover Letter Data for Service Level SMC9618 211 ¤   MODULES  APSMSTXT  APSPPDCM  APSPPDVP  APSUEXTI  APSUREXT  MACROS  APSGEXTP  LISTEND  */.   F.25 COVER LETTER FOR PTF UW10401   PROBLEM DESCRIPTION(S):  OW06977 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users. *  ****************************************************************  * PROBLEM DESCRIPTION: Named groups within named groups *  * (multiple ENG structured fields) cause *  * MSGAPS104I invalid sequence messages *  * to be issued. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW06977  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  This PTF includes the fix for APAR OW06971.  APAR OW06971 changes messages APS808I and APS809I.  The following message explanation changes are needed in the  PSF/MVS 2.1.1 Messages and Codes manual (S544-3675-01):  On page 184, in the explanation of message APS808I, change the  last sentence of the second paragraph to read:  In this case, the image size is also specified in the IDD  structured field.  On page 185, after the first paragraph of the explanation of  message APS809I, insert the following paragraph:  If the printer does not support Image Object Content  Architecture (IOCA), PSF may have converted your IOCA image  to an IM1 image. In this case, the image size is also  specified in the IDD structured field.  ACTION:  This PTF includes the fix for APAR OW06964.  APAR OW06964 exposes a D/T4028 microcode problem.  If images printed on the D/T4028 appear disrupted, partially   Appendix F. PTF Cover Letter Data for Service Level SMC9618 212 ¤   scrambled or misaligned after applying the PSF PTF, then the  D/T4028 EPROM upgrade kit should be ordered. To obtain the  necessary eproms, the customer should contact his/her CE to  order part numbers 1381456 (Model NS1) and 1381454 (Model AS1).  If these parts are not available, or the part number has been  changed, please contact Level 2 Hardware Support for the  D/T4028.  ----------------------------------------------------------------  This PTF includes the fix for APAR OW05210.  APAR OY58384 was included in PSF/MVS 2.2.0 base code.  APAR OY58384 was flagged PE because it did not adequately warn  users of the changes to the way some applications work. In  addition, no adequate migration path was provided for affected  customers. This APAR backs out some of the changes in OY58384  until such a migration path can be provided. Specifically,  IOCA, BCOCA and GOCA objects will again be oriented with  respect to the text orientation (LND orientation) in line  data. Positioning of objects with respect to the LND position  is the same as in OY58384, with the exception that if no line  data has been processed on a page (this includes a skip to  channel 1 immediate) the object will effectively be positioned  and oriented with respect to the page coordinate system. Note  that rotated IOCA will not convert to rotated IM1 with this  APAR applied. OY58384 avoided that problem by restricting  IOCA. Please read the complete APAR text of APAR OW05210 for  more details.  ----------------------------------------------------------------  This PTF includes the fix for APAR OW06966.  The OW06966 APAR changed the way IM images are converted to IO.  If you have altered your IM image that has an orientation other  than 0,90 to account for the way PSF converts IM image to IO  image (IOCA), then your changes will need to be removed from  your IM image. Typical alterations are cell positions and image  orientation. This will only affect customers who had  experienced incorrect output when printing IM images to a  printer with a resolution different than the image resolution  and the printer supports IO image (IOCA).  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APRCF2AZ OW06977  APRIMGAZ OW06977  APRMSGEX OW06977  APROCAAZ OW06977  APROSTAZ OW06977  APROVLEZ OW06977  APRPLNAZ OW06977  APRPOSAZ OW06977  APRPRFEZ OW06977  APRPSGEZ OW06977  APRSTMAZ OW06977  APSDECH OW06977  APSMSTXT OW06977  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES   Appendix F. PTF Cover Letter Data for Service Level SMC9618 213 ¤   OW06977 APRCF2AZ APRIMGAZ APRMSGEX APROCAAZ APROSTAZ APROVLEZ  APRPLNAZ APRPOSAZ APRPRFEZ APRPSGEZ APRSTMAZ APSDECH  APSMSTXT  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APRCF2AZ  APRIMGAZ  APRMSGEX  APROCAAZ  APROSTAZ  APROVLEZ  APRPLNAZ  APRPOSAZ  APRPRFEZ  APRPSGEZ  APRSTMAZ  APSDECH  APSMSTXT  LISTEND  */.   F.26 COVER LETTER FOR PTF UW19390   PROBLEM DESCRIPTION(S):  OW13387 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1, and 2.2.0 users *  * who are using the D/T3160 printer in a *  * parallel channel attached environment *  * and are using HCD to define the printer. *  ****************************************************************  * PROBLEM DESCRIPTION: Add support for the D/T3160 printer. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  Add support for the D/T3160 printer.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW13387  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Add the following changes to the PSF/MVS 2.1.1 System  Programming Guide (S544-3672-01):  ------------------------------------------------------------  On page 13 with heading "Defining Group3 parallel channel  attached Printers (AFP1 Family) with MVSCP" under the CNTLUNIT  statement, change the PROTOCL keyword to read "PROTOCL=D, S or  S4, ..... S or S4 is recommended(2)   Appendix F. PTF Cover Letter Data for Service Level SMC9618 214 ¤   ACTION:  If HCD is currently being used when the PTF is installed, then  HCD must be exited and reinvoked in order to cause  the new version of CBDUS022 to be reloaded by HCD.  If HCD is not being used, the new version of CBDUS022 will  be loaded when HCD is invoked.  ACTION:  If HCD is currently being used when the PTF is installed, then  HCD must be exited and reinvoked in order to cause  the new version of CBDUS022 to be reloaded by HCD.  If HCD is not being used, the new version of CBDUS022 will  be loaded when HCD is invoked.  ACTION:  The system must be IPL'ED to activate this change. The system  must be IPL'ED to activate the HCD portion of this change  if defining the D/T3160 as a channel attached device to MVS.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  CBDUS022 OW13387  IECVAFP1 OW13387  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW13387 CBDUS022 IECVAFP1  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  CBDUS022  IECVAFP1  LISTEND  */.   F.27 COVER LETTER FOR PTF UW15755   PROBLEM DESCRIPTION(S):  OW08944 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.2.0 users. *  ****************************************************************  * PROBLEM DESCRIPTION: 1. The support of a 4 digit year on all *  * separator sheets (job header and job *  * trailer) is required for the year *  * 2000. *  * *  * 2. Also in the year 2000 - 2009 the *  * last 2 digits of the year would not *  * print correctly on the separator *  * pages. *  * *  * 3. Upon adding the extra 2 digits for *  * the year in the APSUX01 header and *   Appendix F. PTF Cover Letter Data for Service Level SMC9618 215 ¤   * APSUX02 trailer in the 16 repeated *  * lines at the bottom of the page, it *  * was found that the line was too *  * long for the page. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  1. Support is needed for the year 2000 by printing the 4 digit  digit year on all separator pages.  2. The last 2 digits of the year in the years 2000 - 2009  does not print correctly.  3. The line that is repeated at the bottom of the APSUX01  header and APSUX02 trailer page is too long and no longer  fits on the page.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW08944  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  In the Print Services Facility/MVS Application Programming  Guide Version 2, Release 1, Modification 1 (S544-3673-01)  on page 59 in Figure 26 "Sample Header Page with Additional  Distribution Information" change the figure as follows.  Change the "PRINT DATE:" to read as follows.  PRINT DATE: 11 SEP 1990  In the Print Services Facility/MVS System Programming  Guide Version 2.1.1 (S544-3672-01) make the following  changes.  1. On page 87 in Figure 30 "Example of a Default PSF  Job-Header Page" change the lines at the bottom of the  separator page to read as follows below. Leave the  spacing the same in the lines as shown in the current  figure. The 4 digit year has been added to the line.  The word "START" and the asterisk (not shown)  have been deleted from the end of the lines. The  class (not shown) should have already been at the end  of the line before the trailing asterisk that was removed.  *START JOB 61 PRINTIT 3 001 001 LOCAL USERNAME ROOM  3.57.04 PM 28 SEP 1987 PRT 9 LIT8 Q  2. On page 87 in Figure 30 "Example of a Default PSF  Job-Header Page" add another one of the same lines at the  bottom of the page to make a total of 16 lines.  3. On page 88 in Figure 31 "Example of a Fast-Printing  Job-Header Page for PSF" change the "PRINT DATE" to  read as follows.  PRINT DATE: 28 SEP 1987  4. On page 90 in Figure 32 "Sample Header Page" change  the "PRINT DATE" to read as follows.  PRINT DATE: 11 SEP 1990  5. On page 91 in Figure 33 "Sample Header Page" change  the "PRINT DATE" to read as follows.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 216 ¤   PRINT DATE: 11 SEP 1990  ACTION:  If you have modified your sample source code for APSUX01,  APSUX02, APSUX01P, APSUX02P, APSUX01S, or APSUX02S then you will  need to save it before applying this PTF as this PTF will  replace the source code for these modules.  If you are not using the IBM supplied default header or trailer  separator pages (you have modified the original ones) then you  will need to save them before applying this PTF as this PTF  will replace these 2 exits (APSUX01 and APSUX02) in the linklib.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSUX01 OW08944  APSUX01P OW08944  APSUX01S OW08944  APSUX02 OW08944  APSUX02P OW08944  APSUX02S OW08944  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW08944 APSUX01 APSUX01P APSUX01S APSUX02 APSUX02P APSUX02S  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APSUX01  APSUX02  MACROS  APSUX01P  APSUX01S  APSUX02P  APSUX02S  LISTEND  */.   F.28 COVER LETTER FOR PTF UW15401   PROBLEM DESCRIPTION(S):  OW10068 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1 and 2.2.0 users who *  * run the APSRMARK utility. *  ****************************************************************  * PROBLEM DESCRIPTION: When the APSRMARK utility is run *  * against a dataset with an end of *  * directory list indicator as the first *  * directory entry in a directory block *  * (including an empty dataset), an *  * ABEND013-018 will result. Also, if the *  * APSRMARK utility is run specifying a *   Appendix F. PTF Cover Letter Data for Service Level SMC9618 217 ¤   * member that is an alias of another *  * member that has been updated or deleted *  * the same abend will result. *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  APSRMARK was processing the end of directory list indicator  incorrectly when it was the first directory entry in a directory  block. APSRMARK also assumed that aliases always had primaries  and that the data pointed to by the alias and it's primary was  the same physical data.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW10068  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  The PSF/MVS: System Programming Guide (S544-3672-01) is updated  as follows:  1 - Chapter 11, page 129  The bullets INDD, MEMBER, NEWNAME, and REPORT are  replaced by:  - INDD=DDname  Specifies the name of the input data set to be used  when you are marking or reporting resources. The INDD  parameter can name either a sequential data set or a  partitioned data set. This parameter is required.  - MEMBER=name|ALL  This parameter is required for partitioned data sets.  Do not specify this parameter for sequential data sets.  - name  Specifies that resource marking or resource reporting  be done for a single member (primary or alias) of a  partitioned data set. When being marked, both the  primary member and its alias are marked unless the  primary has been updated or deleted since the alias  was generated, in which case the alias is not updated.  An alias whose primary has been updated or deleted can  only be marked by specifying the name of the alias and  specifying the NEWNAME keyword.  - ALL  Specifies that resource marking or resource reporting  be done for all members of a partitioned data set.  When being marked, all primary members and aliases  whose primaries have not been updated or deleted are  marked. Aliases whose primaries have been updated or  deleted are not marked. When being reported, only  primary members are listed. Do not specify MEMBER=ALL  when marking multiple fonts for printer-resident use.  Instead, specify each member name in multiple control  statements. However, you can specify MEMBER=ALL when  you specify the REPORT parameter.  - NEWNAME=name  Specifies a new name for a member of a partitioned data   Appendix F. PTF Cover Letter Data for Service Level SMC9618 218 ¤   set. This parameter is optional and has meaning only  when a specific member is specified by MEMBER=name.  The newly named member will be marked and will become  a primary member without an associated alias.  - REPORT  Specifies that a report be formatted and printed.  This report lists how resources are marked. The INDD  and MEMBER parameters determine which resources are  reported.  - INDD specifies the name of the input data set.  - MEMBER=ALL specifies that resource reporting be done  on all primary members of a partitioned data set.  - MEMBER=name specifies that resource reporting be done  on a single primary or alias member of a partitioned  data set.  2 - Chapter 12, pages 138-139  The bullets INDD, MEMBER, NEWNAME, and REPORT are  replaced by:  - INDD=DDname  Specifies the name of the input data set to be used  when you are marking or reporting resources. The INDD  parameter can name either a sequential data set or a  partitioned data set. This parameter is required.  - MEMBER=name|ALL  This parameter is required for partitioned data sets.  Do not specify this parameter for sequential data sets.  - name  Specifies that resource marking or resource reporting  be done for a single member (primary or alias) of a  partitioned data set. When being marked, both the  primary member and its alias are marked unless the  primary has been updated or deleted since the alias  was generated, in which case the alias is not updated.  An alias whose primary has been updated or deleted can  only be marked by specifying the name of the alias and  specifying the NEWNAME keyword.  - ALL  Specifies that resource marking or resource reporting  be done for all members of a partitioned data set.  When being marked, all primary members and aliases  whose primaries have not been updated or deleted are  marked. Aliases whose primaries have been updated or  deleted are not marked. When being reported, only  primary members are listed. Do not specify MEMBER=ALL  when marking multiple fonts for printer-resident use.  Instead, specify each member name in multiple control  statements. However, you can specify MEMBER=ALL when  you specify the REPORT parameter.  - NEWNAME=name  Specifies a new name for a member of a partitioned data  set. This parameter is optional and has meaning only  when a specific member is specified by MEMBER=name. The  newly named member will be marked and will become a  primary member without an associated alias.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 219 ¤   - REPORT  Specifies that a report be formatted and printed.  This report lists how resources are marked. The INDD  and MEMBER parameters determine which resources are  reported.  - INDD specifies the name of the input data set.  - MEMBER=ALL specifies that resource reporting be done  on all primary members of a partitioned data set.  - MEMBER=name specifies that resource reporting be done  on a single primary or alias member of a partitioned  data set.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APSRMARK OW10068  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW10068 APSRMARK  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APSRMARK  LISTEND  */.   F.29 COVER LETTER FOR PTF UW19599   PROBLEM DESCRIPTION(S):  OW14103 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1, and 2.2.0 users *  * that are using the 3800 line mode conversion *  * function. *  ****************************************************************  * PROBLEM DESCRIPTION: When using square paper or paper in *  * which the width is within an inch of *  * the length and using the 3800 line mode *  * conversion, the media origin may be *  * placed in the wrong corner of the *  * paper. *  * *  * Also MSGAPS972I does not contain *  * the correct "system completion code" *  * and "system reason code". *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  When using square paper or paper in which the width is within an  inch of the length and using 3800 line mode conversion, the  wrong SMO (Set Media Origin) IPDS order may be sent to the  printer thus causing the media origin to be incorrect.   Appendix F. PTF Cover Letter Data for Service Level SMC9618 220 ¤   All zeroes are contained in the "system completion code" and  "system reason code" in MSGAPS972I rather than the  valid completion and reason codes.  COMPONENT: 5695-04001-HPRF220  APARS FIXED: OW14103  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  In the Print Services Facility/MVS System Programming Guide  Version 2, Release 2, Modification 0 (S544-3672-02) on page 121  under "Considerations and Limitations of the 3800 Line Mode  Conversion Function" add the following before "The following  functions may be used with 3800 Line Mode Conversion, subject  to....".  The following restrictions apply to the 3800 Line Mode  Conversion:  o 240 pel  You can only use the 3800 Line Mode Conversion to print  3800 line mode jobs on 240 pel printers.  o One input bin  The 3800 Line Mode Conversion assumes the printer only  has one input bin and will only use the paper from the  first input bin identified by the printer.  ------------------------------------------------------------  In Print Services Facility/MVS Messages and Codes Version 2  Release 2 Modification 0 on page 248 change the message text  for APS972I to read as follows.  APS972I A SYSTEM LOAD ERROR WAS DETECTED WHILE ATTEMPTING  TO LOAD MEMBER member name FROM SYS1.IMAGELIB,  SYSTEM COMPLETION CODE system completion code,  SYSTEM REASON CODE system reason code. THE DATA SET  WILL BE HELD BY THE SYSTEM.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  APS4MBCB OW14103  APS4MLD OW14103  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW14103 APS4MBCB APS4MLD  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MODULES  APS4MBCB  APS4MLD  LISTEND  */.   F.30 COVER LETTER FOR PTF UW20320   Appendix F. PTF Cover Letter Data for Service Level SMC9618 221 ¤   PROBLEM DESCRIPTION(S):  OW14505 -  ****************************************************************  * USERS AFFECTED: All PSF/MVS 2.1.0, 2.1.1 and 2.2.0 users who *  * use any of the following page definitions *  * provided with PSF: P1R04863, P1V0598B, *  * P1V0618B, P1W1188B, P1W220FB or P1X04863. *  ****************************************************************  * PROBLEM DESCRIPTION: The above page definitions can cause *  * data to be placed off the logical page *  * when the last line of data on the page *  * contains characters with descenders *  * (pels placed below the baseline - e.g. *  * a comma or a 'g'). *  ****************************************************************  * RECOMMENDATION: Apply the applicable PTF. *  ****************************************************************  Some page definitions supplied with PSF/MVS did not account for  descenders when determining the number of print lines per page.  COMPONENT: 5695-04001-JPRF223  APARS FIXED: OW14505  SPECIAL CONDITIONS:  COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994  LICENSED MATERIAL - PROGRAM PROPERTY OF IBM  DOCUMENTATION:  Change the PSF/MVS Application Programming Guide  (S544-3673-02) as follows:  In Appendix B Table 22 on page 147 and Table 24 on page 148,  replace the information in the row for P1X04863 with the  following information:  +--------+--------+--------+--------+--------+--------+-------+  | NAME | PRINT- | LINES | PAGE | RECOM- | PRINT- | PAGE |  | | ABLE | PER | POSI- | MENDED |ING DI- |PRESEN-|  | | AREA | PAGE | TION | FONT |RECTION |TATION |  | | (WXH) | | (D/A) | | | |  +--------+--------+--------+--------+--------+--------+-------+  |P1X04763|10.60 x | 47 at | 30/0 | GT10 | Down | Land- |  | | 7.77 |6.1 lpi | | | | scape |  +--------+--------+--------+--------+--------+--------+-------+  In Appendix B Table 25 on page 148, replace the information  in the row for P1R04863 with the following information:  +--------+--------+--------+--------+--------+--------+-------+  | NAME | PRINT- | LINES | PAGE | RECOM- | PRINT- | PAGE |  | | ABLE | PER | POSI- | MENDED |ING DI- |PRESEN-|  | | AREA | PAGE | TION | FONT |RECTION |TATION |  | | (WXH) | | (D/A) | | | |  +--------+--------+--------+--------+--------+--------+-------+  |P1R04763|13.60 x | 47 at | 30/0 | GT10 | Down | Land- |  | | 8.00 | 6 lpi | | | | scape |  +--------+--------+--------+--------+--------+--------+-------+  In Appendix B Table 31 on page 152, replace the information  in the last 4 rows (for P1V0598B, P1V0618B, P1W1188B and  P1W220FB) with the following information:   Appendix F. PTF Cover Letter Data for Service Level SMC9618 222 ¤   +--------+--------+--------+--------+--------+--------+-------+  | NAME | PRINT- | LINES | PAGE | RECOM- | PRINT- | PAGE |  | | ABLE | PER | POSI- | MENDED |ING DI- |PRESEN-|  | | AREA | PAGE | TION | FONT |RECTION |TATION |  | | (WXH) | | (D/A) | | | |  +--------+--------+--------+--------+--------+--------+-------+  |P1V0588B|10.67 x | 58 at | 24/0 | GT12 | Up | Land- |  | | 7.11 |8.2 lpi | | | | scape |  +--------+--------+--------+--------+--------+--------+-------+  |P1V0608B|10.67 x | 60 at | 24/224 | GT15 | Up | Land- |  | | 7.11 |8.5 lpi | | | | scape |  +--------+--------+--------+--------+--------+--------+-------+  |P1W1168B|10.67 x | 58 at | 24/0 | GT15 | Up | Land- |  | | 7.11 |8.2 lpi | | | | scape |  | | | 58 at |24/1281 | | | |  | | |8.2 lpi | | | | |  +--------+--------+--------+--------+--------+--------+-------+  |P1W216FB|10.67 x | 54 at | 16/48 | GT24 | Up | Land- |  | | 7.11 | 15.2 | | | | scape |  | | | lpi | | | | |  | | | 54 at | 890/48 | | | |  | | | 15.2 | | | | |  | | | lpi | | | | |  | | | 54 at |16/1322 | | | |  | | | 15.2 | | | | |  | | | lpi | | | | |  | | | 54 at |890/1322| | | |  | | | 15.2 | | | | |  | | | lpi | | | | |  +--------+--------+--------+--------+--------+--------+-------+  In Appendix B Table 34 on page 154, replace P1X04863 in the  row for 6.1 lpi with P1X04763.  In Appendix B Table 36 on page 155:  o in the row for 8.2 lpi:  - change P1V0598B to P1V0588B  - change P1W1188B to P1W1168B  o in the row for 8.5 lpi add page definition P1V0608B.  o in the row for 15.2 lpi change P1W220FB to P1W116FB.  ACTION:  This APAR provides additional page definitions P1R04763,  P1V0588B, P1V0608B, P1W1168B and P1W216FB to be used in place of  P1R04863, P1V0598B, P1V0618B, P1W1188B and P1W220FB which can  cause off logical page errors. The erroneous page definitions  are not being deleted to prevent application changes but  application programmers should be informed to use the page  definitions provided by this PTF in place of those in error.  The erroneous page definitions will not be provided in future  release of PSF/MVS.  COMMENTS:  CROSS REFERENCE-MODULE/MACRO NAMES TO APARS  P1R04763 OW14505  P1V0588B OW14505  P1V0608B OW14505  P1W1168B OW14505   Appendix F. PTF Cover Letter Data for Service Level SMC9618 223 ¤   P1W216FB OW14505  P1X04763 OW14505  CROSS REFERENCE-APARS TO MODULE/MACRO NAMES  OW14505 P1R04763 P1V0588B P1V0608B P1W1168B P1W216FB P1X04763  THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:  MACROS  P1R04763  P1V0588B  P1V0608B  P1W1168B  P1W216FB  P1X04763  LISTEND  */.               Appendix F. PTF Cover Letter Data for Service Level SMC9618 224 ¤   APPENDIX G. READER'S COMMENTS    PSF/MVS VERSION 2.2.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?  __ CBIPO   (C) Copyright IBM Corp. 1983, 1996 225 ¤   __ CBPDO  __ 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:  ____________________________________________________________  ____________________________________________________________  ____________________________________________________________  ____________________________________________________________  ____________________________________________________________  ____________________________________________________________  ____________________________________________________________  ____________________________________________________________       Appendix G. Reader's Comments 226 ¤   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 Print Services Facility/MVS Development  group):  IBM Printing Systems Company  Attention: Dept. DME/003G  Box 1900  Boulder, Colorado 80301-9191             Appendix G. Reader's Comments 227 ¤   IBM   Program Number: 5695-040 5801  5802  5337  Printed in U.S.A.