ÿSCRIPT/VS 4.0.0: DEVICE 1403N8 CHARS MONO ¯ ÿ ÿ ÿ ÿ ÿ Program Directory for ÿ ÿ Page Printer Migration Programs ÿ ÿ Version 2 ÿ Release 2.0, Service Level 9803 ÿ ÿ Program Number 5695-040 ÿ ÿ FMID HPRF224 ÿ ÿ for Use with ÿ MVS ÿ ÿ CBPDO Level SMC9803 ÿ ÿ ÿ Document Date: March 1998 ÿ ÿ ÿ ÿ ÿ ÿ ÿ GI10-0213-00 ¯ ÿ ÿ ¬ÿÿÿ NOTE! ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » Before using this information and the product it supports, be sure » ÿ » to read the general information under "Notices" on page v. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ This program directory, dated March 1998, applies to Page Printer ÿ Migration Programs Version 2 (PPMP 2.2.0) Release 2.0 Service Level ÿ 9803, Program Number 5695-040 for the following: ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ ¼ ¼ ÿ » FMIDS » FEATURE NUMBERS» SYSTEM NAME » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » ÿ » HPRF224 » 6022 » MVS » ÿ » » 6023 » » ÿ » » 5395 » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ¨ ÿ ÿ 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 1989, 1998. ÿ ALL RIGHTS RESERVED. ÿ Note to U.S. Government Users ÿÿ Documentation related to restricted ÿ rights ÿÿ Use, duplication or disclosure is subject to restrictions ÿ set forth in GSA ADP Schedule Contract with IBM Corp. ¯ ÿ ÿ CONTENTS ÿ ÿ ÿ NOTICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V ÿ Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . v ÿ ÿ 1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 1 ÿ 1.1 PPMP 2.2.0 Description . . . . . . . . . . . . . . . . . . . 1 ÿ ÿ 2.0 PROGRAM MATERIALS . . . . . . . . . . . . . . . . . . . . . 3 ÿ 2.1 Basic Machine-Readable Material . . . . . . . . . . . . . . 3 ÿ 2.2 Optional Machine-Readable Material . . . . . . . . . . . . . 3 ÿ 2.3 Program Publications . . . . . . . . . . . . . . . . . . . . 3 ÿ 2.3.1 Basic Program Publications . . . . . . . . . . . . . . . 4 ÿ 2.4 Publications Useful During Installation . . . . . . . . . . 4 ÿ 2.4.1 Optional Program Publications . . . . . . . . . . . . . 4 ÿ 2.5 Program Source Materials . . . . . . . . . . . . . . . . . . 4 ÿ ÿ 3.0 PROGRAM SUPPORT . . . . . . . . . . . . . . . . . . . . . . 5 ÿ 3.1 Service Instructions . . . . . . . . . . . . . . . . . . . . 5 ÿ 3.2 Preventive Service Planning . . . . . . . . . . . . . . . . 5 ÿ 3.3 Statement of Support Procedures . . . . . . . . . . . . . . 5 ÿ ÿ 4.0 PROGRAM AND SERVICE LEVEL INFORMATION . . . . . . . . . . . 6 ÿ 4.1 Program Level Information . . . . . . . . . . . . . . . . . 6 ÿ 4.2 Service Level Information . . . . . . . . . . . . . . . . . 6 ÿ 4.3 Cumulative Service Tape . . . . . . . . . . . . . . . . . . 7 ÿ ÿ 5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS . . . . . . . . 8 ÿ 5.1 Driving System Requirements . . . . . . . . . . . . . . . . 8 ÿ 5.1.1 Programming Requirements . . . . . . . . . . . . . . . . 8 ÿ 5.1.2 DASD Storage Requirements . . . . . . . . . . . . . . . 8 ÿ 5.2 Target System Requirements . . . . . . . . . . . . . . . . . 8 ÿ 5.2.1 Operating System Requirements . . . . . . . . . . . . . 8 ÿ 5.2.2 Machine Requirements . . . . . . . . . . . . . . . . . . 8 ÿ 5.2.3 Programming Requirements . . . . . . . . . . . . . . . . 9 ÿ 5.2.4 DASD Storage Requirements . . . . . . . . . . . . . . . 9 ÿ 5.2.5 Target and Distribution Library Storage Requirements . . 9 ÿ 5.3 Program Considerations . . . . . . . . . . . . . . . . . . . 11 ÿ 5.3.1 Programming Considerations . . . . . . . . . . . . . . . 11 ÿ 5.3.1.1 CALLLIBS Considerations . . . . . . . . . . . . . . 11 ÿ ÿ 6.0 INSTALLATION INSTRUCTIONS . . . . . . . . . . . . . . . . . 13 ÿ 6.1 Installation Steps . . . . . . . . . . . . . . . . . . . . . 13 ÿ 6.1.1 Unload Sample Jobs . . . . . . . . . . . . . . . . . . . 14 ÿ 6.1.2 Delete Load Module Entries from PPMP Version 1.3.0 . . . 14 ÿ 6.1.3 RECEIVE PPMP 2.2.0 . . . . . . . . . . . . . . . . . . . 15 ÿ 6.1.4 RECEIVE Cumulative Service Tape, if applicable . . . . . 15 ÿ 6.1.5 JCL to Allocate Target and Distribution Library Data Sets 16 ÿ 6.1.6 Target and Distribution Library DDDEFs . . . . . . . . . 18 ÿ 6.1.7 Perform SMP/E APPLY CHECK . . . . . . . . . . . . . . . 21 ÿ 6.1.8 Load Target Libraries Using APPLY . . . . . . . . . . . 22 ÿ 6.1.9 Perform SMP/E ACCEPT CHECK . . . . . . . . . . . . . . . 23 ÿ 6.1.10 Load Distribution Libraries using ACCEPT . . . . . . . 23 ÿ 6.1.11 Cleanup PPMP Version 2.1.0 or PPMP Version 2.1.1 Data ÿ Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 ÿ 6.2 Installation Verification Procedures . . . . . . . . . . . . 24 ÿ 6.2.1 Run AIORNRFT JCL . . . . . . . . . . . . . . . . . . . . 24 ÿ 6.2.2 Copy Xerox Fonts P0612C and L0112B to Tape . . . . . . . 27 ÿ 6.2.3 Run AIORNRFF JCL . . . . . . . . . . . . . . . . . . . . 27 ÿ 6.2.4 Run AIORNDSC JCL . . . . . . . . . . . . . . . . . . . . 29 ÿ ÿ APPENDIX A. PPMP 2.2.0 INSTALL LOGIC . . . . . . . . . . . . . . 31 ÿ ÿ APPENDIX B. JCLIN FOR PPMP 2.2.0 . . . . . . . . . . . . . . . . 32 ÿ ÿ APPENDIX C. IVP SAMPLE OUTPUT . . . . . . . . . . . . . . . . . 37 ÿ C.1 AIORNRFT Sample Report . . . . . . . . . . . . . . . . . . . 37 ÿ C.2 AIORNRFF Sample Report . . . . . . . . . . . . . . . . . . . 39 ÿ C.3 AIORNDSC Sample Reports . . . . . . . . . . . . . . . . . . 41 ÿ ÿ APPENDIX D. COVER LETTER DATA . . . . . . . . . . . . . . . . . 44 ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 iii ¯ ÿ ÿ D.1 COVER LETTER FOR PTF UW32208 . . . . . . . . . . . . . . . . 44 ÿ D.2 COVER LETTER FOR PTF UW33692 . . . . . . . . . . . . . . . 46 ÿ D.3 COVER LETTER FOR PTF UW35078 . . . . . . . . . . . . . . . . 48 ÿ D.4 COVER LETTER FOR PTF UW37778 . . . . . . . . . . . . . . . . 50 ÿ D.5 COVER LETTER FOR PTF UW40161 . . . . . . . . . . . . . . . . 51 ÿ D.6 COVER LETTER FOR PTF UW00062 . . . . . . . . . . . . . . . . 54 ÿ D.7 COVER LETTER FOR PTF UW26942 . . . . . . . . . . . . . . . . 56 ÿ D.8 COVER LETTER FOR PTF UW29462 . . . . . . . . . . . . . . . . 63 ÿ D.9 COVER LETTER FOR PTF UW30900 . . . . . . . . . . . . . . . . 67 ÿ D.10 COVER LETTER FOR PTF UW42243 . . . . . . . . . . . . . . . 69 ÿ ÿ READER'S COMMENTS . . . . . . . . . . . . . . . . . . . . . . . . 72 ÿ ÿ ÿ ÿ FIGURES ÿ ÿ ÿ 1. Basic Material: Program Tape . . . . . . . . . . . . . . . 3 ÿ 2. Program Tape: File Content . . . . . . . . . . . . . . . . 3 ÿ 3. Basic Program Publications . . . . . . . . . . . . . . . . . 4 ÿ 4. Publications Useful During Installation . . . . . . . . . . 4 ÿ 5. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . 5 ÿ 6. Component IDs . . . . . . . . . . . . . . . . . . . . . . . 5 ÿ 7. PSF/MVS 2.2.0 Resources and Fonts Required for PPMP 2.2.0 . 9 ÿ 8. Abbreviations used for the data set type . . . . . . . . . . 10 ÿ 9. Storage Requirements for PPMP 2.2.0 Target and Distribution ÿ Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 11 ÿ 10. Sample Unload JCL . . . . . . . . . . . . . . . . . . . . . 14 ÿ 11. RECEIVE Job . . . . . . . . . . . . . . . . . . . . . . . . 15 ÿ 12. RECEIVE Job for Cumulative Service Tape . . . . . . . . . . 16 ÿ 13. Job to Allocate PPMP 2.2.0 Target and Distribution Data Sets 17 ÿ 14. JCL to Create Target and Distribution DDDEFs for PPMP 2.2.0 18 ÿ 15. APPLY CHECK Job . . . . . . . . . . . . . . . . . . . . . . 21 ÿ 16. APPLY Job . . . . . . . . . . . . . . . . . . . . . . . . . 22 ÿ 17. Unresolved External References for APPLY of HPRF224 . . . . 22 ÿ 18. Return Codes expected on message GIM23903 . . . . . . . . . 23 ÿ 19. ACCEPT CHECK Job . . . . . . . . . . . . . . . . . . . . . . 23 ÿ 20. ACCEPT Job . . . . . . . . . . . . . . . . . . . . . . . . . 24 ÿ 21. AIORNRFT JCL IVP Job . . . . . . . . . . . . . . . . . . . . 26 ÿ 22. AIORNRFF JCL IVP Job . . . . . . . . . . . . . . . . . . . . 28 ÿ 23. AIORNDSC JCL IVP Job . . . . . . . . . . . . . . . . . . . . 30 ÿ 24. JCLIN . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 ÿ 25. AIORNRFT Sample Report . . . . . . . . . . . . . . . . . . . 37 ÿ 26. AIORNRFF Sample Report . . . . . . . . . . . . . . . . . . . 39 ÿ 27. AIORNDSC SYSPRINT Sample Report . . . . . . . . . . . . . . 41 ÿ 28. AIORNDSC DJDERPT Sample Report . . . . . . . . . . . . . . . 42 ÿ 29. AIORNDSC Printer Sample Report . . . . . . . . . . . . . . . 43 ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Contents iv ¯ ÿ ÿ NOTICES ÿ ÿ ÿ References in this document to IBM products, programs, or services do ÿ not imply that IBM intends to make these available in all countries in ÿ which IBM operates. Any reference to an IBM product, program, or ÿ service is not intended to state or imply that only IBM's product, ÿ program, or service may be used. Any functionally equivalent product, ÿ program, or service that does not infringe on any of IBM's ÿ intellectual property rights may be used instead of the IBM product, ÿ program, or service. Evaluation and verification of operation in ÿ conjunction with other products, except those expressly designated by ÿ IBM, is the user's responsibility. ÿ ÿ APAR numbers are provided in this document to assist in locating PTFs ÿ that may be required. Ongoing problem reporting may result in ÿ additional APARs being created. Therefore, the APAR lists in this ÿ document may not be complete. To obtain current service ÿ recommendations and to identify current product service requirements, ÿ always contact the IBM Customer Support Center. ÿ ÿ IBM may have patents or pending patent applications covering subject ÿ matter in this document. The furnishing of this document does not ÿ give you any license to these patents. You can send license ÿ inquiries, in writing, to the ÿ ÿ International Business Machines Corporation ÿ IBM Director of Licensing ÿ 500 Columbus Avenue ÿ Thornwood, New York 10594 ÿ USA ÿ ÿ For online versions of this book, we authorize you to: ÿ ÿ ¯ Copy, modify, and print the documentation contained on the media, ÿ for use within your enterprise, provided you reproduce the ÿ copyright notice, all warning statements, and other required ÿ statements on each copy or partial copy. ÿ ÿ ¯ Transfer the original unaltered copy of the documentation when you ÿ transfer the related IBM product (which may be either machines you ÿ own, or programs, if the program's license terms permit a ÿ transfer). You must, at the same time, destroy all other copies ÿ of the documentation. ÿ ÿ You are responsible for payment of any taxes, including personal ÿ property taxes, resulting from this authorization. ÿ ÿ THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES ÿ OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. ÿ ÿ Some jurisdictions do not allow the exclusion of implied warranties, ÿ so the above exclusion may not apply to you. ÿ ÿ Your failure to comply with the terms above terminates this ÿ authorization. Upon termination, you must destroy your machine ÿ readable documentation. ÿ ÿ TRADEMARKS ÿ ÿ The following terms used in this document, are trademarks of IBM ÿ Corporation in the United States or other countries: ÿ ÿ IBM(R) MVS ÿ Advanced Function Presentation MVS/SP ÿ AFP MVS/ESA ÿ CBPDO OS/390 ÿ CBIPO Print Services Facility ÿ IBMLink PSF ÿ IPDS RETAIN ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 v ¯ ÿ ÿ The following term, used in this document, is a trademark of the Xerox ÿ Corporation: ÿ ÿ Xerox ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Notices vi ¯ ÿ ÿ 1.0 INTRODUCTION ÿ ÿ ÿ This program directory is intended for the system programmer ÿ responsible for program installation and maintenance. It contains ÿ information concerning the material and procedures associated with the ÿ installation of PPMP 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 3 identifies the basic and ÿ optional program materials and documentation for PPMP 2.2.0. ÿ ÿ ¯ 3.0, "Program Support" on page 5 describes the IBM support ÿ available for PPMP 2.2.0. ÿ ÿ ¯ 4.0, "Program and Service Level Information" on page 6 lists the ÿ program level Authorized Program Analysis Reports (APARs) and ÿ service level Program Temporary Fixes (PTFs) incorporated into ÿ PPMP 2.2.0. ÿ ÿ ¯ 5.0, "Installation Requirements and Considerations" on page 8 ÿ identifies the resources and considerations for installing and ÿ using PPMP 2.2.0. ÿ ÿ ¯ 6.0, "Installation Instructions" on page 13 provides detailed ÿ installation instructions for PPMP 2.2.0. ÿ ÿ ¯ Appendix A, "PPMP 2.2.0 Install Logic" on page 31 lists the SMPMCS ÿ for PPMP 2.2.0. ÿ ÿ ¯ Appendix B, "JCLIN for PPMP 2.2.0" on page 32 lists the JCLIN for ÿ PPMP 2.2.0. ÿ ÿ ¯ Appendix C, "IVP Sample Output" on page 37 lists each report that ÿ is received when running the IVP jobs. ÿ ÿ ¯ Appendix D, "Cover Letter Data" on page 44 lists PTF HOLD ÿ information ÿ ÿ Before installing PPMP 2.2.0, read 3.2, "Preventive Service Planning" ÿ on page 5. This section tells you how to find any updates to the ÿ information and procedures in this program directory. ÿ ÿ Do not use this program directory if you are installing PPMP 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 PPMP 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 PPMP 2.2.0 are included on the CBPDO tape. ÿ ÿ 1.1 PPMP 2.2.0 DESCRIPTION ÿ ÿ PPMP 2.2.0 software conversion tools are used with Print Services ÿ Facility/MVS Version 2.2.0, to provide for the migration from Xerox ÿ Laser Printing System (LPS) printers to the IBM Advanced Function ÿ ÿ ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 1 ¯ ÿ ÿ Presentation (AFP) printers, including: ÿ ÿ ¯ 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 ÿ ¯ 3835 Advanced Function Printer Model 002 (1) ÿ ¯ 3900 Advanced Function Printer Model 001 (1) ÿ ¯ 3900 Advanced Function Duplex Printing System (2) ÿ ¯ 3900 Wide Advanced Function Printer Model 0W1 (2) ÿ ¯ 3912 Page Printer Model NS1 ÿ ¯ 3916 Page Printer Model NS1 ÿ ¯ 3935 Advanced Function Printer Model 001 (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 ¯ ÿ ÿ 2.0 PROGRAM MATERIALS ÿ ÿ ÿ An IBM program is identified by a program number and a feature code. ÿ The program number for PPMP 2.2.0 is 5695-040. ÿ ÿ The program announcement material describes the features supported by ÿ PPMP 2.2.0. Ask your IBM marketing representative for this ÿ information if you have not already received a copy. ÿ ÿ 2.1 BASIC MACHINE-READABLE MATERIAL ÿ ÿ PPMP 2.2.0 is distributed on 6250 bpi tape, 3480 cartridge, or 4mm ÿ cartridge. 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 13 for more information about how ÿ to install the program. Figure 1 describes the tape or cartridge. ÿ Figure 2 describes the file content of the program tape or cartridge. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 1. Basic Material: Program Tape » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¼ ¼ ¼ ¼ » ÿ » » FEATURE » PHYSICAL » EXTERNAL LABEL » » ÿ » MEDIUM » NUMBER » VOLUME » IDENTIFICATION » VOLSER » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » ÿ » 6250 tape » 6022 » 1 » PSF.PPMP...2.2.0 » PRF224 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » ÿ » 3480 cart » 6023 » 1 » PSF.PPMP...2.2.0 » PRF224 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » ÿ » 4 mm » 5395 » 1 » PSF.PPMP...2.2.0 » PRF224 » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ¨ ¨ ¨ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 2. Program Tape: File Content » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¼ ¼ ¼ ¼ ¼ ¼ » ÿ » » » » » » BLK » NUMBER OF » ÿ » VOLSER » FILE » NAME » RECFM » LRECL » SIZE » ELEMENTS » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » ÿ » PRF224 » 1 » SMPMCS » FB » 80 » 6400 » 1 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » ÿ » » 2 » IBM.HPRF224.F1» FB » 80 » 8800 » 1 » ÿ » » » » » » » (JCLIN) » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » ÿ » » 3 » IBM.HPRF224.F2» U » 0 » 6144 » 74 » ÿ » » » » » » » (AAIODIST) » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » ÿ » » 4 » IBM.HPRF224.F3» FB » 80 » 8800 » 7 » ÿ » » » » » » » (AAIOSAMP) » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » ÿ » » 5 » IBM.HPRF224.F4» VB » 516 » 520 » 2 » ÿ » » » » » » » (AAIOXRS) » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ¨ ¨ ¨ ¨ ¨ ÿ ÿ 2.2 OPTIONAL MACHINE-READABLE MATERIAL ÿ ÿ There are no optional machine-readable materials for PPMP 2.2.0. ÿ ÿ 2.3 PROGRAM PUBLICATIONS ÿ ÿ The following sections identify the basic and optional publications ÿ for PPMP 2.2.0. ÿ ÿ ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 3 ¯ ÿ ÿ 2.3.1 BASIC PROGRAM PUBLICATIONS ÿ ÿ Figure 3 on page 4 identifies the basic program publications for PPMP ÿ 2.2.0. A copy of Page Printer Migration Programs/MVS for Version ÿ 2.2.0 and one copy of each of these publications is included when you ÿ order the basic materials for PPMP 2.2.0. For additional copies, ÿ contact your IBM representative. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 3. Basic Program Publications » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¼ » ÿ » PUBLICATION TITLE » FORM NUMBER » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » Page Printer Migration: General Information » G544-3227 » ÿ » » » ÿ » ¯ Used as a guide in determining the steps to take » » ÿ » in migrating from Xerox Laser Printing Subsystem » » ÿ » (LPS) print applications to IBM Advanced » » ÿ » Function Printing (AFP) applications. » » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » Page Printer Migration: Programming Guide » S544-3228 » ÿ » » » ÿ » ¯ Used as an aid for data processing » » ÿ » administrators and application programmers to » » ÿ » migrate from Xerox LPS print applications to IBM » » ÿ » AFP print applications. » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ÿ ÿ 2.4 PUBLICATIONS USEFUL DURING INSTALLATION ÿ ÿ The publications listed in Figure 4 may be useful during the ÿ installation of PPMP 2.2.0. To order copies, contact your IBM ÿ representative. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 4. Publications Useful During Installation » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¼ » ÿ » PUBLICATION TITLE » FORM NUMBER » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » OS/390 SMP/E Commands » SC28-1805 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » OS/390 SMP/E Reference » SC28-1806 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » OS/390 SMP/E User's Guide » SC28-1740 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » OS/390 SMP/E Messages and Codes » SC28-1738 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » SMP/E Reference » SC28-1107 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » SMP/E User's Guide » SC28-1302 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » SMP/E Messages and Codes » SC28-1108 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » OS/390 MVS JCL Reference » GC28-1757 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » MVS/ESA V5 JCL Reference » GC28-1479 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » MVS/ESA V4 JCL Reference » GC28-1654 » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ÿ ÿ 2.4.1 OPTIONAL PROGRAM PUBLICATIONS ÿ ÿ There are no optional publications for PPMP 2.2.0. ÿ ÿ 2.5 PROGRAM SOURCE MATERIALS ÿ ÿ No program source materials or viewable program listings are provided ÿ for PPMP 2.2.0. ÿ ÿ ÿ Program Materials 4 ¯ ÿ ÿ 3.0 PROGRAM SUPPORT ÿ ÿ ÿ This section describes the IBM support available for PPMP 2.2.0. ÿ ÿ 3.1 SERVICE INSTRUCTIONS ÿ ÿ Contact your IBM marketing representative or systems engineer (SE) for ÿ specific information about available service instructions. ÿ ÿ 3.2 PREVENTIVE SERVICE PLANNING ÿ ÿ Whether PPMP 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 Information/Access or SoftwareXcel Extended. ÿ Specify the following upgrade and subset values: ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 5. PSP Upgrade and Subset ID » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¼ ¼ » ÿ » UPGRADE » SUBSET » RETAIN RELEASE » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » ÿ » PSFMVS220 » HPRF224/9803 » 224 » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ¨ ÿ ÿ If PPMP 2.2.0 was obtained as part of a CBPDO, HOLDDATA and Preventive ÿ Service Planning (PSP) information may be available for PPMP 2.2.0 on ÿ the CBPDO tape. ÿ ÿ 3.3 STATEMENT OF SUPPORT PROCEDURES ÿ ÿ Report any difficulties you have using this program to your IBM ÿ Support Center. If an APAR is required, the Support Center will ÿ provide the address to which any needed documentation can be sent. ÿ ÿ Figure 6 identifies the component ID (COMP ID) for PPMP 2.2.0. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 6. Component IDs » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¼ ¼ ¼ » ÿ » FMID » COMPID » COMPONENT NAME » REL » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » ÿ » HPRF224 » 569504001 » Page Prt Migration Programs » 224 » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ¨ ¨ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 5 ¯ ÿ ÿ 4.0 PROGRAM AND SERVICE LEVEL INFORMATION ÿ ÿ ÿ This section identifies the program and any relevant service levels of ÿ PPMP 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. ÿ ÿ 4.1 PROGRAM LEVEL INFORMATION ÿ ÿ The following APAR fixes against PPMP Version 2.1.1 are incorporated ÿ into this release: ÿ ÿ OY44607 OY48545 OY53686 OY56427 OY61131 OY66607 ÿ OY44608 OY48816 OY53687 OY56428 OY60923 OY66802 ÿ OY44609 OY49234 OY54082 OY56429 OY61371 OY66980 ÿ OY44902 OY49235 OY54085 OY56437 OY61686 OY67499 ÿ OY44903 OY49236 OY54086 OY56458 OY61802 OY67576 ÿ OY45610 OY49237 OY54087 OY56551 OY61669 OW00449 ÿ OY47047 OY49574 OY54088 OY58753 OY62079 OW00513 ÿ OY47568 OY49773 OY54525 OY58754 OY64778 OW02834 ÿ OY47925 OY49922 OY54686 OY55161 OY65392 OW03950 ÿ OY47927 OY50507 OY54686 OY59160 OY65393 ÿ OY47928 OY51027 OY55161 OY59566 OY65906 ÿ OY48542 OY51445 OY55793 OY59768 OY66091 ÿ OY48544 OY51937 OY56426 OY60157 OY66477 ÿ ÿ ÿ 4.2 SERVICE LEVEL INFORMATION ÿ ÿ The following PTFs contain the APAR fixes against PPMP Version 2.1.1. ÿ They have been incorporated into PPMP 2.2.0. ÿ ÿ UY70474 UY72459 UY76006 UY81677 UY88580 UY97253 ÿ UY70522 UY72918 UY76779 UY83380 UY92247 UY97740 ÿ UY70527 UY73090 UY80374 UY83456 UY89421 UY98190 ÿ UY70746 UY73423 UY82091 UY83589 UY91954 UY98375 ÿ UY71539 UY73424 UY79770 UY83637 UY89788 UY99056 ÿ UY68079 UY73671 UY79900 UY83681 UY91647 UY99977 ÿ UY70222 UY73672 UY80051 UY82721 UY89905 UW00888 ÿ UY70780 UY73673 UY80120 UY83549 UY91346 UW01443 ÿ UY71826 UY73916 UY80232 UY85987 UY92629 UW04392 ÿ UY71922 UY74410 UY80501 UY89018 UY95312 UW06779 ÿ UY72110 UY74901 UY80233 UY87812 UY96899 ÿ UY72347 UY75436 UY80915 UY88449 UY96968 ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 6 ¯ ÿ ÿ The following PTFs containing APAR fixes against this release of PSF ÿ PPMP 2.2.0 have been integrated into this release. ÿ ÿ NOTE: COR-CLOSED PTFs are available for 'Corrective Service' and will ÿ be placed on the next available ESO Tape (Expanded Service Option, ÿ formerly known as PUT Tapes). The following sub-categories for ÿ COR-CLOSED PTFs have been provided by the Software Manufacturing ÿ Center (SMC), Poughkeepsie: ÿ ÿ PUTYYMM COR-CLOSED PTFs that are available on an ESO Tape, where ÿ 'yynn' indicates the year and the month that the ESO tape ÿ became available. ÿ ÿ RSUYYMM RSU (Recommended Service Upgrade) is a preventive service ÿ philosophy for all S/390 products that are serviced by IBM for ÿ the OS/390 and MVS platforms. RSU reduces the volume of PTFs ÿ customers need to apply for preventive maintenance. RSU became ÿ available at OS/390 Release 2 GA (9/96), and is identified via ÿ an additional SOURCEID of RSUyymm, where 'yymm' indicates the ÿ year and the month the PTF was assigned this SOURCEID. ÿ ÿ SMCREC COR-CLOSED PTFs that are not yet available on an ESO Tape, but ÿ have been researched and recommended for installation by the ÿ Software Manufacturing Center (SMC) in Poughkeepsie. ÿ ÿ SMCCOR COR-CLOSED PTFs that are not yet available on an ESO Tape and ÿ have no special recommendation for installation. ÿ ÿ HPRF224 ÿ ÿ UW00035-PUT9410 UW00045-PUT9410 UW00054-PUT9411 ÿ UW00062-PUT9412 UW00067-PUT9501 UW13959-PUT9412 ÿ UW14774-PUT9502 UW16278-PUT9504 UW17017-PUT9504 ÿ UW17106-PUT9505 UW17617-PUT9505 UW22663-PUT9512 ÿ UW24105-PUT9512 UW24182-PUT9512 UW24371-PUT9512 ÿ UW24501-PUT9601 UW25805-PUT9603 UW26942-PUT9603 ÿ UW27663-PUT9604 UW28552-PUT9605 UW29334-PUT9606 ÿ UW29402-PUT9606 UW29462-PUT9606 UW29782-PUT9606 ÿ UW29901-PUT9607 UW30245-PUT9607 UW30900-PUT9608 ÿ UW30965-PUT9608 UW31079-PUT9608 UW31395-PUT9608 ÿ UW31770-PUT9609 UW32208-PUT9609 UW33692-PUT9611 ÿ UW34055-PUT9612 UW34658-PUT9612 UW35078-RSU9701 ÿ UW35234-PUT9701 UW35367-PUT9701 UW35793-PUT9702 ÿ UW35920-PUT9702 UW36224-PUT9702 UW37246-PUT9704 ÿ UW37778-PUT9704 UW38070-PUT9705 UW38984-PUT9706 ÿ UW39547-PUT9706 UW40161-PUT9707 UW41476-RSU9709 ÿ UW42243-PUT9710 UW42636-RSU9710 UW43230-RSU9711 ÿ ÿ 4.3 CUMULATIVE SERVICE TAPE ÿ ÿ A cumulative service tape, containing PTFs not incorporated into this ÿ release, might be included with this program. If the 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 7 ¯ ÿ ÿ 5.0 INSTALLATION REQUIREMENTS AND CONSIDERATIONS ÿ ÿ ÿ The following sections identify the system requirements for installing ÿ and activating PPMP 2.2.0. In most cases, you can install PPMP 2.2.0 ÿ on a running system (target system). However, sometimes two systems ÿ may be required. If two systems are required, then the following ÿ terminology is used: ÿ ÿ 1. The system used to install the program (driving system) ÿ ÿ 2. The system on which the program is installed (target system). ÿ ÿ 5.1 DRIVING SYSTEM REQUIREMENTS ÿ ÿ This section describes the environment of the driving system required ÿ to install PPMP 2.2.0. ÿ ÿ 5.1.1 PROGRAMMING REQUIREMENTS ÿ ÿ PPMP 2.2.0 is installed using System Modification Program Extended ÿ (SMP/E), program number 5668-949. The level of SMP/E required on the ÿ driving system to install PPMP 2.2.0 is SMP/E Release 8.0, or higher. ÿ ÿ 5.1.2 DASD STORAGE REQUIREMENTS ÿ ÿ PPMP 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 9 for additional information about the amount of ÿ storage required to install PPMP 2.2.0. ÿ ÿ 5.2 TARGET SYSTEM REQUIREMENTS ÿ ÿ This section describes the environment of the target system required ÿ to install and use PPMP 2.2.0. ÿ ÿ 5.2.1 OPERATING SYSTEM REQUIREMENTS ÿ ÿ PPMP 2.2.0 operates under the one of the following operating systems: ÿ ÿ ¯ MVS/SP JES2 V3 or higher (5685-001) ÿ ÿ ¯ MVS/SP JES3 V3 or higher (5685-002) ÿ ÿ ¯ MVS/SP JES2 V4 or higher (5695-047) ÿ ÿ ¯ MVS/SP JES3 V4 or higher (5695-048) ÿ ÿ ¯ MVS/SP JES2 V5 or higher (5655-068) ÿ ÿ ¯ MVS/SP JES3 V5 or higher (5655-069) ÿ ÿ ¯ OS/390 V1 or higher (5645-001) ÿ ÿ ¯ OS/390 V2 or higher (5647-A01) ÿ ÿ 5.2.2 MACHINE REQUIREMENTS ÿ ÿ See the "Target System Machine Requirements" section of the Print ÿ Services Facility/MVS Program Directory for Version 2.2.0, for machine ÿ requirements for PPMP 2.2.0. PPMP 2.2.0 has the same machine ÿ requirements as PSF/MVS Version 2.2.0. ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 8 ¯ ÿ ÿ 5.2.3 PROGRAMMING REQUIREMENTS ÿ ÿ See the "Operating System and Programming Requirements" section of the ÿ Print Services Facility/MVS: Program Directory for Version 2.2.0 for ÿ a list of operating system requirements and programming requirements ÿ for PPMP 2.2.0. PPMP 2.2.0 runs under the same operating systems and ÿ programming environments as PSF/MVS Version 2.2.0. ÿ ÿ PPMP 2.2.0 has additional programming requirements. They are listed ÿ below. ÿ ÿ ¯ A PL/I execution environment is required for PPMP 2.2.0. One of ÿ the following products must be installed and ACCEPTed into the ÿ SMP/E distribution libraries before PPMP 2.2.0 installation. ÿ ÿ ÿ PL/I Version 2 Release 2.0 or higher (program numbers ÿ 5668-909, 5668-910, 5668-911). ÿ ÿ ÿ LE/370 Version 1 Release 5.0 or higher (program number ÿ 5688-198). ÿ ÿ ÿ LE element of OS/390 (5645-001 or 5647-A01). ÿ ÿ ¯ PPMP 2.2.0 can be installed in the same consolidated software ÿ inventory (CSI) as the PL/I product, or it can be installed in a ÿ separate CSI. ÿ ÿ ¯ AFP resource libraries and font libraries must be available from ÿ PSF/MVS Version 2 Release 1.0 or higher. If you do not have the ÿ resource libraries and fonts available, they are provided with ÿ PSF/MVS 2.2.0. The FMIDs for the resource libraries and fonts ÿ that are required to run the IVP for PPMP 2.2.0 are listed in ÿ Figure 7. You may choose to install additional resources and ÿ fonts to use with PPMP 2.2.0 in your production environment. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 7. PSF/MVS 2.2.0 Resources » ÿ » and Fonts Required for » ÿ » PPMP 2.2.0 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¼ » ÿ » RESOURCE TYPE » FMID » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » Overlay Library » JPRF223 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » Page Segment Library » JPRF223 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » Code Pages » JPRF172 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » ÿ » Compatibility Fonts » JPRF174 » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ÿ ÿ NOTE: If you have installed the AFP Font Collection, 5648-113, FMIDs ÿ H0HL141 and J0HL143 provide equivalent fonts and may be used in place ÿ of FMIDs JPRF172 and JPRF174. ÿ ÿ 5.2.4 DASD STORAGE REQUIREMENTS ÿ ÿ The default SMP/E space parameters for DSSPACE, PEMAX, SMPWRK data ÿ sets, and SMP/E TLIB data sets are adequate to install PPMP 2.2.0. ÿ ÿ 5.2.5 TARGET AND DISTRIBUTION LIBRARY STORAGE REQUIREMENTS ÿ ÿ Abbreviations describing the data set type are listed in Figure 8. ÿ These abbreviations are used in the figures in this section. ÿ ÿ ÿ ÿ ÿ Installation Requirements and Considerations 9 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 8. 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 PPMP 2.2.0. New target ÿ and distribution library data sets must be allocated as indicated in ÿ the tables in this section. See 6.1.5, "JCL to Allocate Target and ÿ Distribution Library Data Sets" on page 16 for JCL that allocates the ÿ new data sets. ÿ ÿ In all the figures in this section, the following applies: ÿ ÿ ¯ The number of blocks and directory blocks specified is the minimum ÿ storage required after the program is installed and the data sets ÿ are compressed. When allocating these data sets, additional ÿ storage and directory blocks should be specified to allow for ÿ maintenance. ÿ ÿ ¯ Data sets may be reblocked to a larger size. ÿ ÿ Figure 9 lists the storage requirements for target library and ÿ distribution library data sets for PPMP 2.2.0. ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Requirements and Considerations 10 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 9. Storage Requirements for PPMP 2.2.0 Target and » ÿ » 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 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » » ÿ » PPMP.SAIOLOAD » NU/EU » PO » U » 0 » 6144 » 200 » 1 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » » ÿ » PPMP.SAIORUN » NU/EU » PO » U » 0 » 6144 » 200 » 1 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » » ÿ » PPMP.SAIOSAMP » NU/EU » PO » FB » 80 » 6160 » 29 » 2 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » » ÿ » PPMP.SAIOXRS » NU/EU » PO » VB » 516 » 520 » 15 » 1 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » » ÿ » PPMP.AAIODIST » NU/EU » PO » U » 0 » 6144 » 259 » 15 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » » ÿ » PPMP.AAIOSAMP » NU/EU » PO » FB » 80 » 6160 » 29 » 2 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » » » » » » ÿ » PPMP.AAIOXRS » NU/EU » PO » VB » 516 » 520 » 15 » 1 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¨ ¨ ¨ ¨ ¨ ¨ ¨ » ÿ » NOTE: » ÿ » » ÿ » See 6.1.5, "JCL to Allocate Target and Distribution Library Data » ÿ » Sets" on page 16 for JCL that allocates these data sets. » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ÿ 5.3 PROGRAM CONSIDERATIONS ÿ ÿ The following sections list the programming considerations for ÿ installing PPMP 2.2.0 and activating its functions. ÿ ÿ If you have PPMP Version 2.1.1 or lower on your system, please note ÿ that the target and distribution library data set names are changed ÿ for PPMP 2.2.0. These names are changed to comply with IBM naming ÿ standards for MVS products. ÿ ÿ 5.3.1 PROGRAMMING CONSIDERATIONS ÿ ÿ ¬ÿÿÿ IMPORTANT ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » The target library data set PPMP.SAIOXRS is a sample data set that » ÿ » should only be used when running the IVP jobs. This data set » ÿ » should not be used when executing PPMP 2.2.0 in production. For » ÿ » production use, an XRSPDS data set should be defined as described » ÿ » in the Page Printer Migration: Programming Guide. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ÿ 5.3.1.1 CALLLIBS CONSIDERATIONS ÿ ÿ PPMP 2.2.0 uses the CALLLIBS function provided in SMP/E Release 8 to ÿ resolve the PL/I and/or LE/370 subroutines. ÿ ÿ When installing PPMP 2.2.0, the following considerations apply: ÿ ÿ 1. Verify that the SMPLTS data set has been allocated ÿ ÿ The SMPLTS data set is new in SMP/E Release 8, and is required to ÿ install FMIDs that use the CALLLIBS function. See the SMP/E ÿ Reference, for information on allocating the SMPLTS data set. ÿ ÿ NOTE: Two cylinders of 3380/3390 DASD space are adequate for the ÿ SMPLTS. ÿ ÿ 2. Provide DDDEFs for the following libraries: ÿ ÿ SCEELKED ÿ PLIBASE ÿ ÿ Installation Requirements and Considerations 11 ¯ ÿ ÿ PLILINK ÿ SIBMBASE ÿ SIBMLINK ÿ ÿ DDDEFs for SCEELKED, PLIBASE, PLILINK, SIBMBASE, and SIBMLINK are ÿ required for the installation of PPMP 2.2.0. PPMP 2.2.0 can be ÿ installed on a system that did not previously have all of these ÿ data sets allocated and defined in DDDEFs to SMP/E. However, you ÿ must first create DDDEFs for any missing libraries, and point the ÿ DDDEF to a data set (in some cases this may be an empty data set). ÿ ÿ The SYSLIB concatenation for CALLLIBS has SCEELKED in front of ÿ PLIBASE, PLILINK, SIBMBASE, and SIBMLINK. If you want to use the ÿ PLI V2 libraries, then you must define the DDDEF for SCEELKED to ÿ point to an empty data set. This will allow the runtime routines ÿ to be resolved from the PLI V2 libraries. IBM recommends that you ÿ create a data set with the name hlq.SCEELKED and define the DDDEF ÿ for SCEELKED to point to that empty data set. This will ease ÿ migration to an LE environment at some future time. ÿ ÿ If you have both existing PLI V2 runtime and LE/370 installed, you ÿ should already have DDDEFs defined for all five of the libraries ÿ in the SYSLIB concatenation. You may use your existing DDDEFs ÿ without change. Because SCEELKED is first in the SYSLIB ÿ concatenation, the LE runtime routines will be linkedited into ÿ PPMP automatically when PPMP 2.2.0 is applied. ÿ ÿ See 6.1.6, "Target and Distribution Library DDDEFs" on page 18 for ÿ a sample job to define these DDDEFs. ÿ ÿ NOTE: The DDDEFs for SCEELKED, PLIBASE, PLILINK, SIBMBASE, and ÿ SIBMLINK are used only to resolve the link-edit for PPMP 2.2.0 ÿ using CALLLIBS. These data sets are not updated during the ÿ installation of PPMP 2.2.0. ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Requirements and Considerations 12 ¯ ÿ ÿ 6.0 INSTALLATION INSTRUCTIONS ÿ ÿ ÿ This section describes the installation method and the step-by-step ÿ procedures to install and to activate the functions of PPMP 2.2.0. ÿ ÿ If you obtained PPMP 2.2.0 in a CBPDO, the RCVPDO job in the CBPDO ÿ RIMLIB data set can be used to run the SMP/E RECEIVE for PPMP 2.2.0. ÿ All service, HOLDDATA, and preventive service planning (PSP) ÿ information is included on the CBPDO tape. For more information, see ÿ the MVS CBPDO Memo to User Extension included with the CBPDO. ÿ ÿ PPMP 2.2.0 is installed using the SMP/E RECEIVE, APPLY, and ACCEPT ÿ method. ÿ ÿ Many of the installation steps can be done using the SMP/E dialog ÿ panels. If you choose not to use the SMP/E dialog panels, sample jobs ÿ are provided for the installation of PPMP 2.2.0. ÿ ÿ All sample SMP/E installation JCL provided with PPMP 2.2.0 assumes the ÿ existence of a cataloged procedure called SMPPROC containing all ÿ necessary DD statements for the execution of SMP/E. If your SMP/E ÿ procedure is not named SMPPROC, substitute your procedure name for ÿ SMPPROC. If you do not have an SMP/E procedure, refer to System ÿ Modification Program Extended (SMP/E) Users Guide or System ÿ Modification Program Extended (SMP/E) Reference for instructions to ÿ build one. ÿ ÿ The SMPPROC procedure is not required when using the SMP/E dialog ÿ panels. The equivalent function is accomplished through the SMP/E ÿ dialog panels. ÿ ÿ In the sample SMP/E JCL 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 ÿ ÿ The following steps are described in this section to install PPMP ÿ 2.2.0: ÿ ÿ 1. Unload sample JCL from the product tape. ÿ ÿ 2. Delete load module entries from PPMP Version 1.3.0 if necessary ÿ ÿ 3. RECEIVE PPMP 2.2.0 ÿ ÿ 4. RECEIVE cumulative service tape, if applicable ÿ ÿ 5. Allocate the target and distribution libraries ÿ ÿ 6. Define SMP/E DDDEFs ÿ ÿ 7. Perform SMP/E APPLY CHECK ÿ ÿ 8. Load target libraries using APPLY ÿ ÿ 9. Perform SMP/E ACCEPT CHECK ÿ ÿ 10. Load distribution libraries using ACCEPT ÿ ÿ 11. Cleanup PPMP Version 2.1.0 or PPMP Version 2.1.1 data sets, if ÿ necessary ÿ ÿ 12. Perform all activities in 6.2, "Installation Verification ÿ Procedures" on page 24 to run the installation verification ÿ procedure for PPMP 2.2.0. ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 13 ¯ ÿ ÿ 6.1.1 UNLOAD SAMPLE JOBS ÿ ÿ Sample JCL is provided on the product tape to install PPMP 2.2.0. ÿ ÿ Use the JCL shown in Figure 10 on page 14 to unload the sample JCL ÿ from the PPMP 2.2.0 tape. If the sample JCL is unloaded into a data ÿ set with a different name than ppmp.jcllib, all references in this ÿ directory to the data set ppmp.jcllib should be replaced with that new ÿ data set name. ÿ ÿ Alternatively, you can access the sample installation jobs by ÿ performing an SMP/E RECEIVE for FMID HPRF224, and then copying the ÿ jobs from dataset HLQ.HPRF224.F3 to a work dataset for editing and ÿ submission. ÿ ÿ NOTE: The high-level qualifier (hlq) is the qualifier specified as ÿ the DSPREFIX in the SMP/E OPTIONS. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //UNLOAD JOB ,'account #','name',MSGLEVEL=(1,1) » ÿ » //STEP1 EXEC PGM=IEBCOPY » ÿ » //SYSPRINT DD SYSOUT=* » ÿ » //* » ÿ » //*----------------------------------------------------------- » ÿ » //* UNLOAD SAMPLE JOBS FROM TAPE. » ÿ » //* Note: CHANGE THE JOBCARD TO MEET YOUR LOCAL REQUIREMENTS » ÿ » //* CHANGE tape TO A VALID NAME FOR A TAPE DRIVE » ÿ » //* CHANGE nnnnnn TO A VALID VOLSER. » ÿ » //* CHANGE ppmp.jcllib TO A VALID DATA SET NAME » ÿ » //* FOR YOUR INSTALLATION. » ÿ » //*----------------------------------------------------------- » ÿ » //* » ÿ » //INTAPE DD DSNAME=IBM.HPRF224.F3,DISP=(OLD,PASS), » ÿ » // UNIT=(tape,,DEFER), » ÿ » // LABEL=(4,SL), » ÿ » // VOL=SER=PRF224 » ÿ » //OUTDISK DD DSNAME=ppmp.jcllib, » ÿ » // DISP=(NEW,CATLG,DELETE), » ÿ » // DCB=(RECFM=FB,LRECL=80,BLKSIZE=8800), » ÿ » // UNIT=SYSDA,SPACE=(TRK,(6,1,2)),VOL=SER=nnnnnn » ÿ » //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1)),DISP=(NEW,DELETE) » ÿ » //SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(1,1)),DISP=(NEW,DELETE) » ÿ » //SYSIN DD * » ÿ » COPY OUTDD=OUTDISK,INDD=INTAPE » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 10. Sample Unload JCL ÿ ÿ After running the UNLOAD job, the data set ppmp.jcllib contains the ÿ following members which may be used to aid in SMP/E installation. ÿ ÿ ¯ AIOACCC - Sample ACCEPT CHECK ÿ ¯ AIOACCEP - Sample ACCEPT ÿ ¯ AIOALLOC - New data set allocation ÿ ¯ AIOAPPLC - Sample APPLY CHECK ÿ ¯ AIOAPPLY - Sample APPLY ÿ ¯ AIOCLNUP - UCLIN job to delete load module entries from PPMP ÿ previous release ÿ ¯ AIODDEF - Sample job to define SMP/E DDDEFs ÿ ¯ AIORECV - Sample RECEIVE for receiving PPMP 2.2.0 ÿ ÿ 6.1.2 DELETE LOAD MODULE ENTRIES FROM PPMP VERSION 1.3.0 ÿ ÿ If you installed PPMP Version 1.3.0, the load module entries created ÿ when PPMP Version 1.3.0 was installed (AIOARFT and AIOBDSC), must be ÿ deleted from the SMP/E zone. ÿ ÿ Run the job in ppmp.jcllib(AIOCLNUP) to delete the PPMP Version 1.3.0 ÿ load module entries. ÿ ÿ Since there are no elements in the dummy SYSMOD defined in the ÿ ÿ Installation Instructions 14 ¯ ÿ ÿ AIOCLNUP job, SMP/E issues a warning message GIM39701W, and a return ÿ code of "4". ÿ ÿ 6.1.3 RECEIVE PPMP 2.2.0 ÿ ÿ Run the SMP/E RECEIVE job in Figure 11 to unload PPMP 2.2.0 data from ÿ the product tape into SMP/E temporary data sets. ÿ ÿ This JCL exists in ppmp.jcllib(AIORECV). ÿ ÿ The SMP/E dialog panels can be used for the RECEIVE step instead of ÿ the supplied JCL. If the supplied JCL is used, the UNIT field on the ÿ SMPPTFIN and SMPTLIB DD statements must be filled in with a valid tape ÿ and DASD unit name, respectively, and the VOLSER nnnnnn must be filled ÿ in with a valid volume for your installation. ÿ ÿ NOTE: This step is bypassed if receiving the product from a CBPDO. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIORECV JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //RECEIVE EXEC SMPPROC » ÿ » //SMP.SMPPTFIN DD DSN=SMPMCS,DISP=(OLD,PASS), » ÿ » // VOL=SER=PRF224,LABEL=(1,SL), » ÿ » // UNIT=(tape,,DEFER) » ÿ » //SMP.SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn » ÿ » //SMP.SMPCNTL DD * » ÿ » SET BDY(GLOBAL). » ÿ » RECEIVE S(HPRF224) SYSMOD. » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 11. RECEIVE Job ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '0' should be ÿ received from this job. ÿ ÿ 6.1.4 RECEIVE CUMULATIVE SERVICE TAPE, IF APPLICABLE ÿ ÿ A cumulative service tape may be shipped with the product package. If ÿ no cumulative service tape is shipped or if the product is received by ÿ CBPDO, disregard this section. ÿ ÿ The JCL in Figure 12 on page 16 is a sample job to RECEIVE the PTFs ÿ and HOLDDATA from the cumulative service tape. Create JCL similar to ÿ this example, modify the job to specify the appropriate parameters for ÿ your installation. ÿ ÿ If any of the PTFs on the tape have a system hold by the ++HOLD SYSTEM ÿ modification control statement with a reason ID equal to UCLIN, file 6 ÿ of the cumulative service tape will contain the UCLIN for that PTF. ÿ The instructions for the UCLIN are contained in the cover letter of ÿ the PTF. ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Instructions 15 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //RECEIVEC JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //************************************************************* » ÿ » //* RECEIVE CUMULATIVE SERVICE DATA. * » ÿ » //* MAKE THE FOLLOWING MODIFICATIONS: * » ÿ » //* 1) CHANGE THE JOBCARD TO MEET YOUR LOCAL REQUIREMENTS * » ÿ » //* 2) CHANGE #globalcsi - TO THE DATA SET NAME OF YOUR * » ÿ » //* GLOBAL CSI DATA SET * » ÿ » //* 3) CHANGE tape TO A VALID TAPE UNIT NAME * » ÿ » //* 4) CHANGE sssssss TO A VALID SOURCE NAME * » ÿ » //************************************************************* » ÿ » //RECEIVE EXEC PGM=GIMSMP,REGION=4096K » ÿ » //SMPCSI DD DSN=#globalcsi, » ÿ » // DISP=SHR » ÿ » //SMPHOLD DD UNIT=tape,LABEL=(4,NL),DISP=SHR, » ÿ » // VOL=SER=CUMTAP, » ÿ » // DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200) » ÿ » //SMPPTFIN DD UNIT=tape,LABEL=(1,NL),DISP=SHR, » ÿ » // VOL=SER=CUMTAP, » ÿ » // DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200) » ÿ » //SMP.SMPCNTL DD * » ÿ » SET BDY(GLOBAL). » ÿ » RECEIVE SYSMODS HOLDDATA SOURCEID(sssssss). » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 12. RECEIVE Job for Cumulative Service Tape ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '0' should be ÿ received from this job. ÿ ÿ 6.1.5 JCL TO ALLOCATE TARGET AND DISTRIBUTION LIBRARY DATA SETS ÿ ÿ Run the AIOALLOC job in Figure 13 on page 17 to allocate the new ÿ target and distribution data sets needed for installation of PPMP ÿ 2.2.0. ÿ ÿ This JCL exists in ppmp.jcllib(AIOALLOC). Consult the instructions in ÿ the sample job for more information. ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Instructions 16 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIOALLOC JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //********************************************************** » ÿ » //* ALLOCATE TARGET AND DISTRIBUTION DATA SETS FOR PPMP. » ÿ » //* 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 SMPPRFX=PPMP,UNIT=xxxx,DVOL=dddddd, » ÿ » // TVOL=tttttt » ÿ » //ALLOC1 EXEC PGM=IEFBR14 » ÿ » //********************************************************** » ÿ » //* ALLOCATE TARGET LIBRARIES » ÿ » //********************************************************** » ÿ » //SAIOLOAD DD DSN=&SMPPRFX..SAIOLOAD,DISP=(NEW,CATLG), » ÿ » // UNIT=&UNIT,VOL=SER=&TVOL, » ÿ » // SPACE=(6144,(200,16,1)), » ÿ » // DCB=(RECFM=U,LRECL=0,BLKSIZE=6144) » ÿ » //SAIORUN DD DSN=&SMPPRFX..SAIORUN, » ÿ » // DISP=(NEW,CATLG), » ÿ » // UNIT=&UNIT,VOL=SER=&TVOL, » ÿ » // SPACE=(6144,(200,16,1)), » ÿ » // DCB=(RECFM=U,LRECL=0,BLKSIZE=6144) » ÿ » //SAIOSAMP DD DSN=&SMPPRFX..SAIOSAMP,DISP=(NEW,CATLG), » ÿ » // UNIT=&UNIT,VOL=SER=&TVOL, » ÿ » // SPACE=(6160,(29,3,2)), » ÿ » // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160) » ÿ » //SAIOXRS DD DSN=&SMPPRFX..SAIOXRS,DISP=(NEW,CATLG), » ÿ » // UNIT=&UNIT,VOL=SER=&TVOL, » ÿ » // SPACE=(520,(15,2,1)), » ÿ » // DCB=(RECFM=VB,LRECL=516,BLKSIZE=520) » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 13 (Part 1 of 2). Job to Allocate PPMP 2.2.0 Target and ÿ Distribution Data Sets ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //********************************************************** » ÿ » //* ALLOCATE DISTRIBUTION LIBRARIES » ÿ » //********************************************************** » ÿ » //AAIODIST DD DSN=&SMPPRFX..AAIODIST,DISP=(NEW,CATLG), » ÿ » // UNIT=&UNIT,VOL=SER=&DVOL, » ÿ » // SPACE=(6144,(259,20,15)), » ÿ » // DCB=(RECFM=U,LRECL=0,BLKSIZE=6144) » ÿ » //AAIOSAMP DD DSN=&SMPPRFX..AAIOSAMP,DISP=(NEW,CATLG), » ÿ » // UNIT=&UNIT,VOL=SER=&DVOL, » ÿ » // SPACE=(6160,(29,3,2)), » ÿ » // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160) » ÿ » //AAIOXRS DD DSN=&SMPPRFX..AAIOXRS,DISP=(NEW,CATLG), » ÿ » // UNIT=&UNIT,VOL=SER=&DVOL, » ÿ » // SPACE=(520,(15,2,1)), » ÿ » // DCB=(RECFM=VB,LRECL=516,BLKSIZE=520) » ÿ » //* » ÿ » //ENDALLO PEND » ÿ » //* ========> END OF PROC ALLOC <======== » ÿ » //ALLOCAT EXEC ALLOC » ÿ » //* ========> END OF JOB ALLOC <======== » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 13 (Part 2 of 2). Job to Allocate PPMP 2.2.0 Target and ÿ Distribution Data Sets ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '0' should be ÿ received from this job. ÿ ÿ ÿ ÿ Installation Instructions 17 ¯ ÿ ÿ 6.1.6 TARGET AND DISTRIBUTION LIBRARY DDDEFS ÿ ÿ Run the AIODDEF job in Figure 14 on page 18 to create the required ÿ SMP/E DDDEFs to install PPMP 2.2.0. ÿ ÿ This JCL exists in ppmp.jcllib(AIODDEF). Consult the instructions in ÿ the sample job for more information. ÿ ÿ See 5.3.1.1, "CALLLIBS Considerations" on page 11 and review the ÿ CALLIBS DDDEFs that are required by PPMP 2.2.0. ÿ ÿ NOTE: If this job is re-run, change the ADD command to REP to replace ÿ the existing entries. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIODDEF JOB » ÿ » //***************************************************************» ÿ » //* » ÿ » //* THIS JCL WILL CREATE DDDEF ENTRIES FOR PRODUCT PAGE PRINTER » ÿ » //* MIGRATION PROGRAMS » ÿ » //* » ÿ » //* CAUTION: THIS IS NEITHER A JCL PROCEDURE NOR A COMPLETE JOB.» ÿ » //* BEFORE USING THIS JOB STEP, YOU WILL HAVE TO MAKE THE » ÿ » //* FOLLOWING MODIFICATIONS: » ÿ » //* » ÿ » //* » ÿ » //* 1) CHANGE THE JOB CARD TO MEET YOUR SYSTEM REQUIREMENTS » ÿ » //* 2) CHANGE #globalcsi TO THE DATASET NAME OF YOUR GLOBAL CSI » ÿ » //* DATASET » ÿ » //* 3) CHANGE #tzone TO THE NAME OF YOUR TARGET ZONE » ÿ » //* 4) CHANGE #dzone TO THE NAME OF YOUR DISTRIBUTION ZONE » ÿ » //* 5) CHANGE tttttt AND tuuu TO THE VOLSER AND UNIT TYPE » ÿ » //* OF THE TARGET VOLUME. » ÿ » //* 6) CHANGE dddddd AND duuu TO THE VOLSER AND UNIT TYPE » ÿ » //* OF THE DISTRIBUTION VOLUME. » ÿ » //* 7) THE REQUIRED CALLLIB DDDEF ENTRIES ARE INCLUDED IN THIS » ÿ » //* JOB. VERIFY THE DATA SET NAMES FOR THE CALLLIBS » ÿ » //* LIBRARIES ARE CORRECT FOR YOUR INSTALLATION AND » ÿ » //* CHANGE hhh TO THE APPROPRIATE HIGH-LEVEL QUALIFIER. » ÿ » //* THE DDDEFS FOR LIBRARIES NOT BEING USED CAN POINT TO » ÿ » //* EMPTY DATA SETS. IF THESE CALLLIB DDDEFS HAVE PREVIOUSLY» ÿ » //* BEEN DEFINED, THE STATEMENTS CAN BE DELETED FROM THIS » ÿ » //* JOB. » ÿ » //* » ÿ » //* NOTES: » ÿ » //* » ÿ » //* 1. THIS JOB SHOULD COMPLETE WITH A RETURN CODE 0. HOWEVER, » ÿ » //* IF SOME OR ALL OF THESE DDDEF ENTRIES ALREADY EXIST, THEN» ÿ » //* THE JOB WILL COMPLETE WITH A RETURN CODE 8. YOU WILL HAVE» ÿ » //* TO EXAMINE THE OUTPUT AND DETERMINE WHETHER OR NOT THE » ÿ » //* EXISTING ENTRIES SHOULD BE REPLACED. YOU CAN CHANGE THE » ÿ » //* 'ADD' TO 'REP' IN THIS JOB TO REPLACE EXISTING ENTRIES. » ÿ » //* » ÿ » //* 2. THE UNIT AND VOLUME PARAMETERS MAY BE DELETED FOR » ÿ » //* DATASETS THAT ARE CATALOGUED. » ÿ » //* » ÿ » //***************************************************************» ÿ » //DDDEF EXEC PGM=GIMSMP,REGION=4096K » ÿ » //SMPCSI DD DSN=#globalcsi, » ÿ » // DISP=SHR » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 14 (Part 1 of 4). JCL to Create Target and Distribution DDDEFs ÿ for PPMP 2.2.0 ÿ ÿ ÿ ÿ ÿ Installation Instructions 18 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //SMPCNTL DD * » ÿ » SET BDY(#tzone). » ÿ » UCLIN. » ÿ » /**************************************************************/» ÿ » /* */» ÿ » /* THE FOLLOWING ARE THE TARGET ZONE DDDEFS FOR THE TARGET */» ÿ » /* LIBRARIES. */» ÿ » /* */» ÿ » /**************************************************************/» ÿ » ADD DDDEF (SAIOLOAD) » ÿ » DATASET(PPMP.SAIOLOAD) » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (SAIORUN) » ÿ » DATASET(PPMP.SAIORUN) » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (SAIOSAMP) » ÿ » DATASET(PPMP.SAIOSAMP) » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (SAIOXRS) » ÿ » DATASET(PPMP.SAIOXRS) » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » /**************************************************************/» ÿ » /* */» ÿ » /* THE FOLLOWING ARE THE TARGET ZONE DDDEFS FOR THE */» ÿ » /* DISTRIBUTION LIBRARIES. */» ÿ » /* */» ÿ » /**************************************************************/» ÿ » ADD DDDEF (AAIODIST) » ÿ » DATASET(PPMP.AAIODIST) » ÿ » UNIT(duuu) » ÿ » VOLUME(dddddd) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 14 (Part 2 of 4). JCL to Create Target and Distribution DDDEFs ÿ for PPMP 2.2.0 ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Instructions 19 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » ADD DDDEF (AAIOSAMP) » ÿ » DATASET(PPMP.AAIOSAMP) » ÿ » UNIT(duuu) » ÿ » VOLUME(dddddd) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (AAIOXRS) » ÿ » DATASET(PPMP.AAIOXRS) » ÿ » UNIT(duuu) » ÿ » VOLUME(dddddd) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » /**************************************************************/» ÿ » /* */» ÿ » /* THE FOLLOWING ARE THE TARGET ZONE DDDEFS FOR THE CALLLIB */» ÿ » /* DATA SETS. IF THESE HAVE PREVIOUSLY BEEN DEFINED, THEN */» ÿ » /* THEY CAN BE DELETED FROM THIS JOB. */» ÿ » /* */» ÿ » /**************************************************************/» ÿ » ADD DDDEF (SCEELKED) » ÿ » DATASET(hhh.SCEELKED) » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (PLIBASE) » ÿ » DATASET(hhh.PLIBASE) » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (PLILINK) » ÿ » DATASET(hhh.PLILINK) » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (SIBMBASE) » ÿ » DATASET(hhh.SIBMBASE) » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (SIBMLINK) » ÿ » DATASET(hhh.SIBMLINK) » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 14 (Part 3 of 4). JCL to Create Target and Distribution DDDEFs ÿ for PPMP 2.2.0 ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Instructions 20 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » UNIT(tuuu) » ÿ » VOLUME(tttttt) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ENDUCL. » ÿ » SET BDY(#dzone). » ÿ » UCLIN. » ÿ » /**************************************************************/» ÿ » /* */» ÿ » /* THE FOLLOWING ARE THE DISTRIBUTION ZONE DDDEFS FOR THE */» ÿ » /* DISTRIBUTION LIBRARIES. */» ÿ » /* */» ÿ » /**************************************************************/» ÿ » ADD DDDEF (AAIODIST) » ÿ » DATASET(PPMP.AAIODIST) » ÿ » UNIT(duuu) » ÿ » VOLUME(dddddd) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (AAIOSAMP) » ÿ » DATASET(PPMP.AAIOSAMP) » ÿ » UNIT(duuu) » ÿ » VOLUME(dddddd) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ADD DDDEF (AAIOXRS) » ÿ » DATASET(PPMP.AAIOXRS) » ÿ » UNIT(duuu) » ÿ » VOLUME(dddddd) » ÿ » WAITFORDSN » ÿ » SHR. » ÿ » ENDUCL. » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 14 (Part 4 of 4). JCL to Create Target and Distribution DDDEFs ÿ for PPMP 2.2.0 ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '0' should be ÿ received from this job. ÿ ÿ 6.1.7 PERFORM SMP/E APPLY CHECK ÿ ÿ Run the SMP/E APPLY CHECK job in Figure 15 to determine which SYSMODS, ÿ if any, are missing. Any missing SYSMODS should be installed before ÿ continuing with the installation of PPMP 2.2.0. ÿ ÿ This JCL exists in ppmp.jcllib(AIOAPPLC). If the supplied JCL is ÿ used, change the job card to meet your local requirements, change the ÿ UNIT xxxx on the SMPTLIB DD statement with a valid DASD unit name, ÿ change the VOLSER nnnnnn with a valid volume for your installation, ÿ and change tgtzone to the name of your targrt zone. ÿ ÿ SMP/E dialog panels can be used for the APPLY CHECK instead of the ÿ supplied JCL. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIOAPPLC JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //APPLY EXEC SMPPROC » ÿ » //SMP.SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn » ÿ » //SMP.SMPCNTL DD * » ÿ » SET BDY(tgtzone). » ÿ » APPLY CHECK S(HPRF224) » ÿ » BYPASS(HOLDSYS,HOLDUSER,HOLDCLASS(UCLREL,ERREL)) » ÿ » GROUPEXTEND. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 15. APPLY CHECK Job ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '0' should be ÿ received from this job. ÿ ÿ Installation Instructions 21 ¯ ÿ ÿ Any problems must be investigated before continuing with the PPMP ÿ 2.2.0 installation. ÿ ÿ 6.1.8 LOAD TARGET LIBRARIES USING APPLY ÿ ÿ Run the SMP/E APPLY job in Figure 16 to load the SMP/E target ÿ libraries from SMP/E temporary data sets. ÿ ÿ This JCL exists in ppmp.jcllib(AIOAPPLY). If the supplied JCL is ÿ used, change the job card to meet your local requirements, change the ÿ UNIT xxxx on the SMPTLIB DD statement with a valid DASD unit name, ÿ change the VOLSER nnnnnn with a valid volume for your installation, ÿ and change tgtzone to the name of your targrt zone. ÿ ÿ SMP/E dialog panels can be used for the APPLY instead of the supplied ÿ JCL. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIOAPPLY JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //APPLY EXEC SMPPROC » ÿ » //SMP.SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn » ÿ » //SMP.SMPCNTL DD * » ÿ » SET BDY(tgtzone). » ÿ » APPLY S(HPRF224) » ÿ » BYPASS(HOLDCLASS(UCLREL,ERREL)) » ÿ » GROUPEXTEND. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 16. APPLY Job ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '4' should be ÿ received from this job. You will receive IEW0461 unresolved external ÿ reference messages using the linkage editor or, if linkediting with ÿ the Program Management Binder, IEW2454W symbol unresolved messages, ÿ for the modules listed in Figure 17. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » Load Module AIOARFT and AIOARFTX » ÿ » » ÿ » IBMLLIST IBMBBGKA IBMBCEDB IBMBSEDA IBMBCCCA » ÿ » IBMBPIRA IBMBOCLA IBMBCODE IBMBSEOA IBMBCCQA » ÿ » IBMBPIRB IBMBPAFA IBMBCKDD IBMBSFIA IBMBCVDY » ÿ » IBMBPIRC IBMBRIOA IBMBEOCA IBMBSISA IBMBCPBD » ÿ » IBMBAMMA IBMBBCVA IBMBSPLA IBMBSPOA IBMBCRFB » ÿ » IBMBAPMA IBMBCCAA IBMBJDDA IBMBCWDH IBMBSAOA » ÿ » IBMBBGBA IBMBCGZA IBMBPRCA IBMBSFOA IBMBSLOA » ÿ » IBMBBGIA IBMBCHFD IBMBKDMA IBMBPAMA » ÿ » IBMBCBCA IBMBCTHD IBMBSIOA IBMBBGCA » ÿ » IBMBMXSA IBMBCUID IBMBBCTA IBMBCACA » ÿ » » ÿ » Load Module AIOBDSC and AIOBDSCX » ÿ » » ÿ » IBMLLIST IBMBEOCA IBMBCCCA IBMBSEDA IBMBSIOA » ÿ » IBMBPIRA IBMBSEOA IBMBCCQA IBMBBCVA IBMBPAMA » ÿ » IBMBPIRB IBMBSISA IBMBCCSA IBMBCBCA IBMBPAFA » ÿ » IBMBPIRC IBMBSPOA IBMBCEDB IBMBBCTA IBMBSEIA » ÿ » IBMBAMMA IBMBCKDD IBMBCTHD IBMBBGBA IBMBCRFB » ÿ » IBMBOCLA IBMBBGIA IBMBCUID IBMBSFIA IBMBCCAA » ÿ » IBMBRIOA IBMBBCKA IBMBCVDY IBMBCPBD IBMBCGZA » ÿ » IBMBPRCA IBMBBGKA IBMBCWDH IBMBSPLA IBMBSLOA » ÿ » IBMBCHFD IBMBBGCA IBMBSAOA IBMBJDDA » ÿ » IBMBCODE IBMBCACA IBMBSFOA IBMBKDMA » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 17. Unresolved External References for APPLY of HPRF224 ÿ ÿ Message GIM23903 will include either a return code 4 or return code 0 ÿ for the link-edit of each module, depending on the target library. ÿ Figure 18 identifies the expected return code for the modules in each ÿ of the load modules created during APPLY processing. ÿ ÿ ÿ Installation Instructions 22 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » Figure 18. Return Codes expected on » ÿ » message GIM23903 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » ¼ ¼ » ÿ » LMOD » LIBRARY » RETURN CODE » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » ÿ » AIOARFTX » SAIOLOAD » RC 4 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » ÿ » AIOBDSCX » SAIOLOAD » RC 4 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » ÿ » AIOARFT » SMPLTS » RC 4 » ÿ » » SAIORUN » RC 0 » ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » » » ÿ » AIOBDSC » SMPLTS » RC 4 » ÿ » » SAIORUN » RC 0 » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ¨ ÿ ÿ 6.1.9 PERFORM SMP/E ACCEPT CHECK ÿ ÿ Run the SMP/E ACCEPT CHECK job in Figure 19 to determine which ÿ SYSMODS, if any, are missing. Any missing SYSMODS should be installed ÿ before continuing with the installation of PPMP 2.2.0. ÿ ÿ This JCL exists in ppmp.jcllib(AIOACCC). If the supplied JCL is used, ÿ change the job card to meet your local requirements, change the UNIT ÿ xxxx on the SMPTLIB DD statement with a valid DASD unit name, change ÿ the VOLSER nnnnnn with a valid volume for your installation, and ÿ change dlibzone to the name of your distribution zone. ÿ ÿ SMP/E dialog panels can be used for the ACCEPT CHECK instead of the ÿ supplied JCL. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIOACCC JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //ACCEPT EXEC SMPPROC » ÿ » //SMP.SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn » ÿ » //SMP.SMPCNTL DD * » ÿ » SET BDY(dlibzone). » ÿ » ACCEPT CHECK S(HPRF224) » ÿ » BYPASS(HOLDSYS,HOLDUSER,HOLDCLASS(UCLREL,ERREL)) » ÿ » GROUPEXTEND. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 19. ACCEPT CHECK Job ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '0' should be ÿ received from this job. ÿ ÿ Any problems must be investigated before continuing with the PPMP ÿ 2.2.0 installation. ÿ ÿ 6.1.10 LOAD DISTRIBUTION LIBRARIES USING ACCEPT ÿ ÿ Run the SMP/E ACCEPT job in Figure 20 on page 24 to load the SMP/E ÿ distribution libraries from SMP/E temporary data sets. ÿ ÿ This JCL exists in ppmp.jcllib(AIOACCEP). If the supplied JCL is ÿ used, change the job card to meet your local requirements, change the ÿ UNIT xxxx on the SMPTLIB DD statement with a valid DASD unit name, ÿ change the VOLSER nnnnnn with a valid volume for your installation, ÿ and change dlibzone to the name of your distribution zone. ÿ ÿ SMP/E dialog panels can be used for the ACCEPT instead of the supplied ÿ JCL. ÿ ÿ ÿ ÿ ÿ Installation Instructions 23 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIOACCEP JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //ACCEPT EXEC SMPPROC » ÿ » //SMP.SMPTLIB DD UNIT=xxxx,DISP=OLD,VOL=SER=nnnnnn » ÿ » //SMP.SMPCNTL DD * » ÿ » SET BDY(dlibzone). » ÿ » ACCEPT S(HPRF224) » ÿ » BYPASS(HOLDCLASS(UCLREL,ERREL)) » ÿ » GROUPEXTEND COMPRESS(ALL). » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 20. ACCEPT Job ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '0' should be ÿ received from this job. ÿ ÿ 6.1.11 CLEANUP PPMP VERSION 2.1.0 OR PPMP VERSION 2.1.1 DATA SETS ÿ ÿ If you are migrating from PPMP Version 2.1.0 or PPMP Version 2.1.1 to ÿ PPMP 2.2.0, the target and distribution library names have changed. ÿ The target and distribution library data sets for PPMP Version 2.1.0 ÿ and PPMP Version 2.1.1 should be deleted. The target and distribution ÿ library names for PPMP Version 2.1.0 and PPMP Version 2.1.1 are: ÿ ÿ ¯ PPM.V2R1M0.PPMLOAD ÿ ¯ PPM.V2R1M0.PPMSAMP ÿ ¯ PPM.V2R1M0.XRSPDS ÿ ¯ PPM.V2R1M0.PPMRUN ÿ ¯ PPM.V2R1M0.PPMDIST ÿ ¯ PPM.V2R1M0.APPMSAMP ÿ ¯ PPM.V2R1M0.AXRSPDS ÿ ÿ You should also delete any corresponding DDDEFs that were created for ÿ the PPMP Version 2.1.0 or PPMP Version 2.1.1 data sets. ÿ ÿ 6.2 INSTALLATION VERIFICATION PROCEDURES ÿ ÿ After installing PPMP 2.2.0, verify that the product has installed ÿ correctly. The installation verification procedures (IVP) allow an ÿ evaluation of the installation of PPMP 2.2.0. ÿ ÿ There are three sample JCL jobs provided on the PPMP 2.2.0 tape for ÿ the IVP: AIORNRFT, AIORNRFF and AIORNDSC. These jobs are located in ÿ the data set PPMP.SAIOSAMP. ÿ ÿ The data set names on the STEPLIB DD statement in all of the IVP jobs ÿ must be modified to include the PL/I run-time libraries prior to ÿ running the IVP jobs. If the PL/I run-time libraries are included in ÿ the linklist at your installation, they should be removed from the ÿ STEPLIB DD statement concatenation. ÿ ÿ The following steps are performed for the installation verification: ÿ ÿ 1. Run AIORNRFT JCL ÿ ÿ 2. Copy Xerox fonts to tape ÿ ÿ 3. Run AIORNRFF JCL ÿ ÿ 4. Run AIORNDSC JCL ÿ ÿ 6.2.1 RUN AIORNRFT JCL ÿ ÿ Edit the AIORNRFT JCL in the data set PPMP.SAIOSAMP(AIORNRFT). See ÿ Figure 21 on page 26 for an example of the AIORNRFT JCL. ÿ ÿ Complete the following steps: ÿ ÿ 1. The AIORNRFT JCL as distributed will default to using the LE/370 ÿ runtime library, SCEERUN. If you have LE/370, change the cee ÿ prefix on the SCEERUN data set name to the data set name of your ÿ ÿ Installation Instructions 24 ¯ ÿ ÿ installation's LE/370 runtime library. If you do not have LE/370, ÿ comment out the DD statement for SCEERUN, and uncomment the DD ÿ statements for PLILINK and SIBMLINK. Change the pli prefix for ÿ these data set names to the data set names of your installation's ÿ PL/I runtime libraries. ÿ ÿ 2. Change the word pseglib to the data set name of your ÿ installation's page segment library. ÿ ÿ 3. Change the word fontlib to the data set name of your ÿ installation's font library. ÿ ÿ 4. Change the word overlib to the data set name of your ÿ installation's overlay library. ÿ ÿ 5. The SPACE parameter for the RFTXRS data set must be completed. ÿ The size of the data set depends on the number of resources that ÿ are reformatted. If the two resources used for this IVP are the ÿ only resources reformatted at this time, the RFTXRS data set SPACE ÿ parameter may be allocated as SPACE=(TRK,(2,1,2)). More storage ÿ will be needed for any additional resources that are reformatted. ÿ Refer to Page Printer Migration: Programming Guide for additional ÿ information about reformatting Xerox resources. ÿ ÿ ¬ÿÿÿ IMPORTANT ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » The data sets PPMP.RFTXRS and PPMP.SAIOXRS are sample data sets » ÿ » that are only used when running the IVP jobs. These data sets » ÿ » should not be used when executing PPMP 2.2.0 in production. For » ÿ » production use, the RFTXRS and XRSPDS data sets should be defined » ÿ » as described in the Page Printer Migration: Programming Guide. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ÿ Run the AIORNRFT JCL. Two Xerox job descriptor libraries (JDLs) are ÿ converted to a format that is used as input to the AIORNDSC program. ÿ These reformatted JDL's are placed in the RFTXRS data set. ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Instructions 25 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIORNRFT JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //***************************************************************» ÿ » //* » ÿ » //* Before running this job, edit the JCL as follows: » ÿ » //* » ÿ » //* If you have LE/370, change the cee prefix on » ÿ » //* the SCEERUN data set name to the data set name of » ÿ » //* your installation's LE/370 runtime library. » ÿ » //* » ÿ » //* If you don't have LE/370, comment out the DD statement for » ÿ » //* SCEERUN, and uncomment the DD statements for PLILINK » ÿ » //* and SIBMLINK. Change the pli prefix for these data set » ÿ » //* names to the data set names of your installation's » ÿ » //* PL/I runtime libraries. » ÿ » //* » ÿ » //* In addition, » ÿ » //* 1. Change the word pseglib to the data set name of your » ÿ » //* installation's page segment library. » ÿ » //* 2. Change the word fontlib to the data set name of your » ÿ » //* installation's font library. » ÿ » //* 3. Change the word overlib to the data set name of your » ÿ » //* installation's overlay library. » ÿ » //* 4. The SPACE parameter for the RFTXRS data set must be » ÿ » //* completed. The size of the data set depends on the » ÿ » //* number of resources that are reformatted. If the two » ÿ » //* resources used for this IVP are the only resources » ÿ » //* reformatted at this time, the RFTXRS data set SPACE » ÿ » //* parameter may be allocated as SPACE=(TRK,(2,1,2)). » ÿ » //* More storage will be needed for any additional » ÿ » //* resources that are reformatted. Refer to Page Printer » ÿ » //* Migration: Programming Guide for additional information» ÿ » //* about reformatting Xerox resources. » ÿ » //***************************************************************» ÿ » //RFTFPD EXEC PGM=AIOARFT,REGION=2M, » ÿ » // PARM='ISASIZE(64K),HEAP(564K,20K),ER(0),DEP(0)/' » ÿ » //STEPLIB DD DSN=PPMP.SAIORUN,DISP=SHR » ÿ » // DD DSN=cee.SCEERUN,DISP=SHR » ÿ » //* DD DSN=pli.PLILINK,DISP=SHR » ÿ » //* DD DSN=pli.SIBMLINK,DISP=SHR » ÿ » //SYSPRINT DD SYSOUT=* » ÿ » //RFTXRS DD DSN=PPMP.RFTXRS,UNIT=SYSDA, » ÿ » // SPACE=(TRK,(x,x,x)), » ÿ » // DCB=(RECFM=VB,LRECL=8004,BLKSIZE=8008), » ÿ » // DISP=(NEW,CATLG) » ÿ » //XRSPDS DD DSN=PPMP.SAIOXRS, » ÿ » // DISP=SHR » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //CSRC DD DSN=PPMP.SAIOSAMP(AIOCSRC), » ÿ » // DISP=SHR » ÿ » //TRANSRC DD DSN=PPMP.SAIOSAMP(AIOTRANS), » ÿ » // DISP=SHR » ÿ » //PSEGLIB DD DSN=pseglib, » ÿ » // DISP=SHR » ÿ » //FONTLIB DD DSN=fontlib, » ÿ » // DISP=SHR » ÿ » //AFPOPDS DD DSN=overlib, » ÿ » // DISP=SHR » ÿ » //SYSIN DD * » ÿ » FORMAT-PDS JDL CSRC TRANSRC » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 21 (Part 2 of 2). AIORNRFT JCL IVP Job ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '4' should be ÿ received from this job. The output you receive is a report similar to ÿ the example found in Appendix C, "IVP Sample Output" on page 37. ÿ Several messages are produced stating that Xerox fonts were not found. ÿ Message number AIOTSF249I appears in the report stating that two ÿ ÿ Installation Instructions 26 ¯ ÿ ÿ translation tables (XRXLIC and XRXSTD) are written to the RFTXRS. ÿ Message number AIORPT260I also appears in the report stating that two ÿ Xerox resources (DFAULT.JDL and PPMP.JDL) are formatted/copied ÿ successfully. Refer to Page Printer Migration: Programming Guide for ÿ more information on translation tables and resources. ÿ ÿ NOTE: After this IVP step is run, do not load any job descriptor ÿ library (JDL) files until the last IVP step is successfully run. If ÿ other JDL files are loaded, the two JDL files created in this IVP step ÿ may be overlaid by other resources that will prevent the last IVP step ÿ from running successfully. ÿ ÿ 6.2.2 COPY XEROX FONTS P0612C AND L0112B TO TAPE ÿ ÿ The Xerox fonts P0612C and L0112B must be available on a tape as input ÿ to the AIORNRFF JCL. ÿ ÿ If you have the Xerox A03 font distribution tape and have not modified ÿ the fonts P0612C and L0112B on the tape, you may use this tape as ÿ input to the AIORNRFF JCL. If you do not have the distribution tape, ÿ or have modified these two fonts, a tape containing these fonts must ÿ be made. If you do not have a tape drive, contact your IBM Support ÿ Center for instructions to copy these fonts to disk. ÿ ÿ To create a new tape containing Xerox fonts P0612C and L0112B, ÿ follow these steps: ÿ ÿ 1. Take the Xerox printer offline. ÿ ÿ 2. Mount a tape on the Xerox tape drive. When the BOT indicator ÿ light comes on, touch the ONLINE button to put the tape drive ÿ online to the printer. ÿ ÿ 3. Issue the following commands at the Xerox printer console: ÿ ÿ TAPE VOLINIT,6250 ÿ COPY TAPE WRITE LABEL P0612C.FNT ÿ COPY TAPE WRITE LABEL L0112B.FNT ÿ TAPE REW (do not rewind the tape manually) ÿ TAPE LIST,PRINT (the Xerox LPS will prompt you for a ÿ tape label; enter a string of up to ÿ 30 characters) ÿ TAPE UNLOAD (the tape drive will go offline from the ÿ printer automatically) ÿ ÿ 4. Remove the tape and put the Xerox printer back online. ÿ ÿ The TAPE LIST,PRINT command prints a list of the names of the files on ÿ the tape. Check that the files P0612C.FNT and L0112B.FNT are present ÿ in this list. ÿ ÿ 6.2.3 RUN AIORNRFF JCL ÿ ÿ Edit the AIORNRFF JCL in the data set PPMP.SAIOSAMP(AIORNRFF). See ÿ Figure 22 on page 28 for an example of the AIORNRFF JCL. ÿ ÿ Complete the following steps: ÿ ÿ 1. The AIORNRFT JCL as distributed will default to using the LE/370 ÿ runtime library, SCEERUN. If you have LE/370, change the cee ÿ prefix on the SCEERUN dataset name to the dataset name of your ÿ installation's LE/370 runtime library. If you do not have LE/370, ÿ comment out the DD statement for SCEERUN, and uncomment the DD ÿ statements for PLILINK and SIBMLINK. Change the pli prefix for ÿ these data set names to the data set names of your installation's ÿ PL/I runtime libraries. ÿ ÿ 2. Change the word pseglib to the data set name of your ÿ installation's page segment library. ÿ ÿ 3. Change the word fontlib to the data set name of your ÿ installation's font library. ÿ ÿ Installation Instructions 27 ¯ ÿ ÿ 4. Change the word overlib to the data set name of your ÿ installation's overlay library. ÿ ÿ 5. Change the word tape in the XRSTAPE DD statement to a valid tape ÿ device name for your installation. ÿ ÿ Run the AIORNRFF JCL. The files P0612C.FNT and L0112B.FNT are placed ÿ in the RFTXRS data set, and reformatted. The RFTXRS data set is used ÿ as input to the AIORNDSC program. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIORNRFF JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //***************************************************************» ÿ » //* » ÿ » //* Before running this job, edit the JCL as follows: » ÿ » //* » ÿ » //* If you have LE/370, change the cee prefix on » ÿ » //* the SCEERUN dataset name to the dataset name of » ÿ » //* your installation's LE/370 runtime library. » ÿ » //* » ÿ » //* If you don't have LE/370, comment out the DD statement for » ÿ » //* SCEERUN, and uncomment the DD statements for PLILINK » ÿ » //* and SIBMLINK. Change the pli prefix for these data set » ÿ » //* names to the data set names of your installation's » ÿ » //* PL/I runtime libraries. » ÿ » //* » ÿ » //* In addition, » ÿ » //* 1. Change the word pseglib to the data set name of your » ÿ » //* installation's page segment library. » ÿ » //* 2. Change the word fontlib to the data set name of your » ÿ » //* installation's font library. » ÿ » //* 3. Change the word overlib to the data set name of your » ÿ » //* installation's overlay library. » ÿ » //* 4. Change the word tape in the XRSTAPE DD statement to » ÿ » //* a valid tape device name for your installation. » ÿ » //***************************************************************» ÿ » //RFTFTP EXEC PGM=AIOARFT,REGION=2M, » ÿ » // PARM='ISASIZE(64K),HEAP(564K,20K),ER(0),DEP(0)/' » ÿ » //STEPLIB DD DSN=PPMP.SAIORUN,DISP=SHR » ÿ » // DD DSN=cee.SCEERUN,DISP=SHR » ÿ » //* DD DSN=pli.PLILINK,DISP=SHR » ÿ » //* DD DSN=pli.SIBMLINK,DISP=SHR » ÿ » //SYSPRINT DD SYSOUT=* » ÿ » //XRSTAPE DD DSN=SYS1.XRSTAPE, » ÿ » // UNIT=tape, » ÿ » // LABEL=(1,NL), » ÿ » // VOL=SER=FNTAPE, » ÿ » // DCB=(BLKSIZE=8192,RECFM=U), » ÿ » // DISP=SHR » ÿ » //XRSPDS DD DSN=PPMP.SAIOXRS, » ÿ » // DISP=SHR » ÿ » //RFTXRS DD DSN=PPMP.RFTXRS, » ÿ » // DISP=SHR » ÿ » //CSRC DD DSN=PPMP.SAIOSAMP(AIOCSRC), » ÿ » // DISP=SHR » ÿ » //TRANSRC DD DSN=PPMP.SAIOSAMP(AIOTRANS), » ÿ » // DISP=SHR » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Instructions 28 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //PSEGLIB DD DSN=pseglib, » ÿ » // DISP=SHR » ÿ » //FONTLIB DD DSN=fontlib, » ÿ » // DISP=SHR » ÿ » //AFPOPDS DD DSN=overlib, » ÿ » // DISP=SHR » ÿ » //SELECT DD * » ÿ » P0612C.FNT » ÿ » L0112B.FNT » ÿ » /* » ÿ » //SYSIN DD * » ÿ » FORMAT-TAPE SELECT NOCSRC NOTRANSRC » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 22 (Part 2 of 2). AIORNRFF JCL IVP Job ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '4' should be ÿ received from this job. The output you receive is a report similar to ÿ the example found in C.2, "AIORNRFF Sample Report" on page 39. ÿ Several messages are produced stating that Xerox fonts are not found. ÿ Message number AIORPT260I appears in the report stating that two Xerox ÿ resources (P0612C.FNT and L0112B.FNT) are formatted/copied ÿ successfully. Refer to Page Printer Migration: Programming Guide for ÿ more information about formatting the Xerox resources. ÿ ÿ 6.2.4 RUN AIORNDSC JCL ÿ ÿ Edit the AIORNDSC JCL in the data set PPMP.SAIOSAMP(AIORNDSC). See ÿ Figure 23 on page 30 for an example of the AIORNDSC JCL. ÿ ÿ Complete the following steps: ÿ ÿ 1. The AIORNRFT JCL as distributed will default to using the LE/370 ÿ runtime library, SCEERUN. If you have LE/370, change the cee ÿ prefix on the SCEERUN dataset name to the dataset name of your ÿ installation's LE/370 runtime library. If you do not have LE/370, ÿ comment out the DD statement for SCEERUN, and uncomment the DD ÿ statements for PLILINK and SIBMLINK. Change the pli prefix for ÿ these dataset names to the dataset names of your installation's ÿ PL/I runtime libraries. ÿ ÿ 2. Change the word fontlib to the data set name of your ÿ installation's font library. ÿ ÿ 3. Change the DSCOUT statement, DEST=xxxx, to your installation's ÿ appropriate AFP printer destination. ÿ ÿ 4. Change the AFPOUT DD statement, SYSOUT=x, to the appropriate ÿ SYSOUT class for your installation's AFP printer. ÿ ÿ Run the AIORNDSC JCL. The reformatted resources and a Xerox ÿ datastream (AIOCHDMP) are converted from ASCII format to EBCDIC ÿ format. ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Installation Instructions 29 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AIORNDSC JOB 'account #','name',MSGLEVEL=(1,1) » ÿ » //***************************************************************» ÿ » //* Before running this job, edit the JCL as follows: » ÿ » //* » ÿ » //* If you have LE/370, change the cee prefix on » ÿ » //* the SCEERUN dataset name to the dataset name of » ÿ » //* your installation's LE/370 runtime library. » ÿ » //* » ÿ » //* If you don't have LE/370, comment out the DD statement for » ÿ » //* SCEERUN, and uncomment the DD statements for PLILINK » ÿ » //* and SIBMLINK. Change the pli prefix for these dataset » ÿ » //* names to the dataset names of your installation's » ÿ » //* PL/I runtime libraries. » ÿ » //* » ÿ » //* In addition, » ÿ » //* 1. Change the word fontlib to the dataset name of your » ÿ » //* installation's font library. » ÿ » //* 2. Change the DSCOUT statement, DEST=xxxx to your » ÿ » //* installation's appropriate AFP printer destination. » ÿ » //* 3. Change the AFPOUT DD statement, SYSOUT=x, to the » ÿ » //* appropriate SYSOUT class for your installation's » ÿ » //* AFP printer. » ÿ » //***************************************************************» ÿ » //DSC EXEC PGM=AIOBDSC,REGION=2M, » ÿ » // PARM='ISASIZE(64K),HEAP(1088K,512K),ER(0),DEP(0)/' » ÿ » //STEPLIB DD DSN=PPMP.SAIORUN,DISP=SHR » ÿ » // DD DSN=cee.SCEERUN,DISP=SHR » ÿ » //* DD DSN=pli.PLILINK,DISP=SHR » ÿ » //* DD DSN=pli.SIBMLINK,DISP=SHR » ÿ » //DSCOUT OUTPUT FORMDEF=AIOFDF,DEST=xxxx » ÿ » //SYSPRINT DD SYSOUT=* » ÿ » //DJDERPT DD SYSOUT=* » ÿ » //RFTXRS DD DSN=PPMP.RFTXRS, » ÿ » // DISP=SHR » ÿ » //XRXIN DD DSN=PPMP.SAIOSAMP(AIOCHDMP), » ÿ » // DISP=SHR,DCB=RECFM=FBA » ÿ » //FONTLIB DD DSN=fontlib, » ÿ » // DISP=SHR » ÿ » //SYSUT1 DD DSN=&&TEMP, » ÿ » // UNIT=SYSDA,SPACE=(TRK,(25,25)), » ÿ » // DCB=(RECFM=VBM,LRECL=8207,BLKSIZE=23476), » ÿ » // DISP=(NEW,DELETE) » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //AFPOUT DD SYSOUT=x, » ÿ » // DCB=(RECFM=VBM,LRECL=8205,BLKSIZE=8209), » ÿ » // OUTPUT=*.DSCOUT » ÿ » //SYSIN DD * » ÿ » JDL=DFAULT JDE=ONLN REPORT » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 23 (Part 2 of 2). AIORNDSC JCL IVP Job ÿ ÿ EXPECTED RETURN CODES AND MESSAGES: A return code of '0' should be ÿ received from this job. The output you receive is a report similar to ÿ the example found in C.3, "AIORNDSC Sample Reports" on page 41. A ÿ DJDERPT report is also produced similar to the example found in C.3, ÿ "AIORNDSC Sample Reports" on page 41. ÿ ÿ ÿ ÿ ÿ ÿ Installation Instructions 30 ¯ ÿ ÿ APPENDIX A. PPMP 2.2.0 INSTALL LOGIC ÿ ÿ ÿ If you ordered PPMP 2.2.0 as an individual product (not in a CBIPO or ÿ CBPDO), then the SMP/E modification control statements (SMPMCS) for ÿ PPMP 2.2.0 are obtained by printing the first file of the product ÿ tape. The SMPMCS is included in this section for information purposes ÿ only. ÿ ÿ ++FUNCTION(HPRF224 ) FESN(0561046 ) REWORK(1998013 ) ÿ RFDSNPFX(IBM ) FILES(4) ÿ /*********************************************************/ ÿ /* */ ÿ /* 5695-040 (C) COPYRIGHT IBM CORP. 1989, 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 ) DELETE(JAF1248 JPRF114 ) ÿ SUP(AW08998 AW09119 AW09215 AW09270 AW10069 ÿ AW10208 AW10914 AW11461 AW11472 AW12157 ÿ AW12991 AW16405 AW16490 AW16651 AW17528 ÿ AW17623 AW18513 AW19035 AW19183 AW19373 ÿ AW20096 AW20698 AW20861 AW20883 AW21134 ÿ AW21200 AW21377 AW21742 AW21869 AW21903 ÿ AW22132 AW22395 AW22661 AW23490 AW23506 ÿ AW23674 AW24017 AW24546 AW24671 AW24957 ÿ AW25090 AW25155 AW25336 AW26001 AW26587 ÿ AW26834 AW27501 AW27738 AW28957 AW29261 ÿ AW29555 JAF1248 JPRF114 UW00035 UW00045 ÿ UW00054 UW00062 UW00067 UW13959 UW14774 ÿ UW16278 UW17017 UW17106 UW17617 UW22663 ÿ UW24105 UW24182 UW24371 UW24501 UW25805 ÿ UW26942 UW27663 UW28552 UW29334 UW29402 ÿ UW29462 UW29782 UW29901 UW30245 UW30900 ÿ UW30965 UW31079 UW31395 UW31770 UW32208 ÿ UW33692 UW34055 UW34658 UW35078 UW35234 ÿ UW35367 UW35793 UW35920 UW36224 UW37246 ÿ UW37778 UW38070 UW38984 UW39547 UW40161 ÿ UW41476 UW42243 UW42636 UW43230 ) . ÿ ++JCLIN CALLLIBS RELFILE(1) . ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 31 ¯ ÿ ÿ APPENDIX B. JCLIN FOR PPMP 2.2.0 ÿ ÿ ÿ The JCLIN for PPMP 2.2.0 can be obtained by printing the second file ÿ of the PPMP 2.2.0 tape. The JCLIN is included in this section for ÿ information purposes only. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » //JCLIN JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) » ÿ » //* » ÿ » //* LINK-EDIT JCLIN FOR PPMP INSTALL » ÿ » //* » ÿ » //STEP1 EXEC PGM=HEWL,REGION=768K, » ÿ » // PARM='XREF,LIST,LET,NCAL,SIZE=(396K,96K)' » ÿ » //SYSPRINT DD SYSOUT=* » ÿ » //SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1)) » ÿ » //AAIODIST DD DISP=OLD,DSN=PPMP.AAIODIST » ÿ » //SYSLMOD DD DISP=OLD,DSN=PPMP.SAIOLOAD » ÿ » //SYSLIN DD * » ÿ » INCLUDE AAIODIST(AIOCOPYR) » ÿ » INCLUDE AAIODIST(AIOAC@M) » ÿ » INCLUDE AAIODIST(AIOAC@R) » ÿ » INCLUDE AAIODIST(AIOACSF) » ÿ » INCLUDE AAIODIST(AIOADIR) » ÿ » INCLUDE AAIODIST(AIOAF@M) » ÿ » INCLUDE AAIODIST(AIOAI@M) » ÿ » INCLUDE AAIODIST(AIOAJ@M) » ÿ » INCLUDE AAIODIST(AIOAJ@0) » ÿ » INCLUDE AAIODIST(AIOAJ@1) » ÿ » INCLUDE AAIODIST(AIOAJ@2) » ÿ » INCLUDE AAIODIST(AIOAJ@3) » ÿ » INCLUDE AAIODIST(AIOAJ@4) » ÿ » INCLUDE AAIODIST(AIOAJ@5) » ÿ » INCLUDE AAIODIST(AIOAL@M) » ÿ » INCLUDE AAIODIST(AIOAM@M) » ÿ » INCLUDE AAIODIST(AIOAP@M) » ÿ » INCLUDE AAIODIST(AIOAP@R) » ÿ » INCLUDE AAIODIST(AIOAPAT) » ÿ » INCLUDE AAIODIST(AIOAPMS) » ÿ » INCLUDE AAIODIST(AIOARFT) » ÿ » INCLUDE AAIODIST(AIOARPT) » ÿ » INCLUDE AAIODIST(AIOAS@M) » ÿ » INCLUDE AAIODIST(AIOASEL) » ÿ » INCLUDE AAIODIST(AIOAT@M) » ÿ » INCLUDE AAIODIST(AIOAT@R) » ÿ » INCLUDE AAIODIST(AIOATRD) » ÿ » INCLUDE AAIODIST(AIOATSF) » ÿ » INCLUDE AAIODIST(AIOAWRX) » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 24 (Part 1 of 5). JCLIN ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 32 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » INCLUDE AAIODIST(AIOBAMD) » ÿ » INCLUDE AAIODIST(AIOBCF1) » ÿ » INCLUDE AAIODIST(AIOBMTD) » ÿ » INCLUDE AAIODIST(AIOBTPX) » ÿ » INCLUDE AAIODIST(AIOBTXO) » ÿ » INCLUDE AAIODIST(AIOBWF1) » ÿ » INCLUDE AAIODIST(AIOBXFN) » ÿ » INCLUDE AAIODIST(AIOBXOP) » ÿ » INCLUDE AAIODIST(AIOBXPS) » ÿ » INCLUDE AAIODIST(AIOBXTA) » ÿ » INCLUDE AAIODIST(AIOCAIO) » ÿ » INCLUDE AAIODIST(AIOCBUG) » ÿ » INCLUDE AAIODIST(AIOCJOB) » ÿ » INCLUDE AAIODIST(AIOCMWR) » ÿ » INCLUDE AAIODIST(AIOCPIO) » ÿ » INCLUDE AAIODIST(AIOCRRX) » ÿ » INCLUDE AAIODIST(AIOCR2E) » ÿ » ENTRY PLISTART » ÿ » NAME AIOARFTX(R) » ÿ » INCLUDE AAIODIST(AIOCOPYR) » ÿ » INCLUDE AAIODIST(AIOBADR) » ÿ » INCLUDE AAIODIST(AIOBAMD) » ÿ » INCLUDE AAIODIST(AIOBARL) » ÿ » INCLUDE AAIODIST(AIOBCF1) » ÿ » INCLUDE AAIODIST(AIOBDSC) » ÿ » INCLUDE AAIODIST(AIOBEDR) » ÿ » INCLUDE AAIODIST(AIOBINI) » ÿ » INCLUDE AAIODIST(AIOBJDP) » ÿ » INCLUDE AAIODIST(AIOBJIC) » ÿ » INCLUDE AAIODIST(AIOBJJD) » ÿ » INCLUDE AAIODIST(AIOBJPG) » ÿ » INCLUDE AAIODIST(AIOBJPS) » ÿ » INCLUDE AAIODIST(AIOBJRC) » ÿ » INCLUDE AAIODIST(AIOBLCM) » ÿ » INCLUDE AAIODIST(AIOBLDD) » ÿ » INCLUDE AAIODIST(AIOBLGF) » ÿ » INCLUDE AAIODIST(AIOBLSF) » ÿ » INCLUDE AAIODIST(AIOBLTF) » ÿ » INCLUDE AAIODIST(AIOBMTD) » ÿ » INCLUDE AAIODIST(AIOBNDC) » ÿ » INCLUDE AAIODIST(AIOBNDR) » ÿ » INCLUDE AAIODIST(AIOBNLP) » ÿ » INCLUDE AAIODIST(AIOBOLG) » ÿ » INCLUDE AAIODIST(AIOBORP) » ÿ » INCLUDE AAIODIST(AIOBPGE) » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 24 (Part 2 of 5). JCLIN ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix B. JCLIN for PPMP 2.2.0 33 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » INCLUDE AAIODIST(AIOBRPT) » ÿ » INCLUDE AAIODIST(AIOBSDR) » ÿ » INCLUDE AAIODIST(AIOBSMM) » ÿ » INCLUDE AAIODIST(AIOBSRT) » ÿ » INCLUDE AAIODIST(AIOBTPX) » ÿ » INCLUDE AAIODIST(AIOBTXO) » ÿ » INCLUDE AAIODIST(AIOBWF1) » ÿ » INCLUDE AAIODIST(AIOBXFN) » ÿ » INCLUDE AAIODIST(AIOBXJJ) » ÿ » INCLUDE AAIODIST(AIOBXOP) » ÿ » INCLUDE AAIODIST(AIOBXPS) » ÿ » INCLUDE AAIODIST(AIOBXRC) » ÿ » INCLUDE AAIODIST(AIOBXTA) » ÿ » INCLUDE AAIODIST(AIOCAIO) » ÿ » INCLUDE AAIODIST(AIOCBUG) » ÿ » INCLUDE AAIODIST(AIOCJOB) » ÿ » INCLUDE AAIODIST(AIOCMWR) » ÿ » INCLUDE AAIODIST(AIOCPIO) » ÿ » INCLUDE AAIODIST(AIOCRRX) » ÿ » INCLUDE AAIODIST(AIOCR2E) » ÿ » ENTRY PLISTART » ÿ » NAME AIOBDSCX(R) » ÿ » /* » ÿ » //********************************************** » ÿ » //STEP2 EXEC PGM=HEWL,REGION=768K, » ÿ » // PARM='XREF,LIST,LET,CALL,SIZE=(396K,96K)' » ÿ » //SYSLIB DD DISP=SHR,DSN=CEE.SCEELKED » ÿ » // DD DISP=SHR,DSN=PLI.V2R3M0.PLIBASE » ÿ » // DD DISP=SHR,DSN=PLI.V2R3M0.PLILINK » ÿ » // DD DISP=SHR,DSN=PLI.V2R3M0.SIBMBASE » ÿ » // DD DISP=SHR,DSN=PLI.V2R3M0.SIBMLINK » ÿ » //SYSPRINT DD SYSOUT=* » ÿ » //SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1)) » ÿ » //AAIODIST DD DISP=OLD,DSN=PPMP.AAIODIST » ÿ » //SYSLMOD DD DISP=OLD,DSN=PPMP.SAIORUN » ÿ » //SYSLIN DD * » ÿ » INCLUDE AAIODIST(AIOCOPYR) » ÿ » INCLUDE AAIODIST(AIOAC@M) » ÿ » INCLUDE AAIODIST(AIOAC@R) » ÿ » INCLUDE AAIODIST(AIOACSF) » ÿ » INCLUDE AAIODIST(AIOADIR) » ÿ » INCLUDE AAIODIST(AIOAF@M) » ÿ » INCLUDE AAIODIST(AIOAI@M) » ÿ » INCLUDE AAIODIST(AIOAJ@M) » ÿ » INCLUDE AAIODIST(AIOAJ@0) » ÿ » INCLUDE AAIODIST(AIOAJ@1) » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 24 (Part 3 of 5). JCLIN ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix B. JCLIN for PPMP 2.2.0 34 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » INCLUDE AAIODIST(AIOAJ@2) » ÿ » INCLUDE AAIODIST(AIOAJ@3) » ÿ » INCLUDE AAIODIST(AIOAJ@4) » ÿ » INCLUDE AAIODIST(AIOAJ@5) » ÿ » INCLUDE AAIODIST(AIOAL@M) » ÿ » INCLUDE AAIODIST(AIOAM@M) » ÿ » INCLUDE AAIODIST(AIOAP@M) » ÿ » INCLUDE AAIODIST(AIOAP@R) » ÿ » INCLUDE AAIODIST(AIOAPAT) » ÿ » INCLUDE AAIODIST(AIOAPMS) » ÿ » INCLUDE AAIODIST(AIOARFT) » ÿ » INCLUDE AAIODIST(AIOARPT) » ÿ » INCLUDE AAIODIST(AIOAS@M) » ÿ » INCLUDE AAIODIST(AIOASEL) » ÿ » INCLUDE AAIODIST(AIOAT@M) » ÿ » INCLUDE AAIODIST(AIOAT@R) » ÿ » INCLUDE AAIODIST(AIOATRD) » ÿ » INCLUDE AAIODIST(AIOATSF) » ÿ » INCLUDE AAIODIST(AIOAWRX) » ÿ » INCLUDE AAIODIST(AIOBAMD) » ÿ » INCLUDE AAIODIST(AIOBCF1) » ÿ » INCLUDE AAIODIST(AIOBMTD) » ÿ » INCLUDE AAIODIST(AIOBTPX) » ÿ » INCLUDE AAIODIST(AIOBTXO) » ÿ » INCLUDE AAIODIST(AIOBWF1) » ÿ » INCLUDE AAIODIST(AIOBXFN) » ÿ » INCLUDE AAIODIST(AIOBXOP) » ÿ » INCLUDE AAIODIST(AIOBXPS) » ÿ » INCLUDE AAIODIST(AIOBXTA) » ÿ » INCLUDE AAIODIST(AIOCAIO) » ÿ » INCLUDE AAIODIST(AIOCBUG) » ÿ » INCLUDE AAIODIST(AIOCJOB) » ÿ » INCLUDE AAIODIST(AIOCMWR) » ÿ » INCLUDE AAIODIST(AIOCPIO) » ÿ » INCLUDE AAIODIST(AIOCRRX) » ÿ » INCLUDE AAIODIST(AIOCR2E) » ÿ » ENTRY PLISTART » ÿ » NAME AIOARFT(R) » ÿ » INCLUDE AAIODIST(AIOCOPYR) » ÿ » INCLUDE AAIODIST(AIOBADR) » ÿ » INCLUDE AAIODIST(AIOBAMD) » ÿ » INCLUDE AAIODIST(AIOBARL) » ÿ » INCLUDE AAIODIST(AIOBCF1) » ÿ » INCLUDE AAIODIST(AIOBDSC) » ÿ » INCLUDE AAIODIST(AIOBEDR) » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 24 (Part 4 of 5). JCLIN ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix B. JCLIN for PPMP 2.2.0 35 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » INCLUDE AAIODIST(AIOBINI) » ÿ » INCLUDE AAIODIST(AIOBJDP) » ÿ » INCLUDE AAIODIST(AIOBJIC) » ÿ » INCLUDE AAIODIST(AIOBJJD) » ÿ » INCLUDE AAIODIST(AIOBJPG) » ÿ » INCLUDE AAIODIST(AIOBJPS) » ÿ » INCLUDE AAIODIST(AIOBJRC) » ÿ » INCLUDE AAIODIST(AIOBLCM) » ÿ » INCLUDE AAIODIST(AIOBLDD) » ÿ » INCLUDE AAIODIST(AIOBLGF) » ÿ » INCLUDE AAIODIST(AIOBLSF) » ÿ » INCLUDE AAIODIST(AIOBLTF) » ÿ » INCLUDE AAIODIST(AIOBMTD) » ÿ » INCLUDE AAIODIST(AIOBNDC) » ÿ » INCLUDE AAIODIST(AIOBNDR) » ÿ » INCLUDE AAIODIST(AIOBNLP) » ÿ » INCLUDE AAIODIST(AIOBOLG) » ÿ » INCLUDE AAIODIST(AIOBORP) » ÿ » INCLUDE AAIODIST(AIOBPGE) » ÿ » INCLUDE AAIODIST(AIOBRPT) » ÿ » INCLUDE AAIODIST(AIOBSDR) » ÿ » INCLUDE AAIODIST(AIOBSMM) » ÿ » INCLUDE AAIODIST(AIOBSRT) » ÿ » INCLUDE AAIODIST(AIOBTPX) » ÿ » INCLUDE AAIODIST(AIOBTXO) » ÿ » INCLUDE AAIODIST(AIOBWF1) » ÿ » INCLUDE AAIODIST(AIOBXFN) » ÿ » INCLUDE AAIODIST(AIOBXJJ) » ÿ » INCLUDE AAIODIST(AIOBXOP) » ÿ » INCLUDE AAIODIST(AIOBXPS) » ÿ » INCLUDE AAIODIST(AIOBXRC) » ÿ » INCLUDE AAIODIST(AIOBXTA) » ÿ » INCLUDE AAIODIST(AIOCAIO) » ÿ » INCLUDE AAIODIST(AIOCBUG) » ÿ » INCLUDE AAIODIST(AIOCJOB) » ÿ » INCLUDE AAIODIST(AIOCMWR) » ÿ » INCLUDE AAIODIST(AIOCPIO) » ÿ » INCLUDE AAIODIST(AIOCRRX) » ÿ » INCLUDE AAIODIST(AIOCR2E) » ÿ » ENTRY PLISTART » ÿ » NAME AIOBDSC(R) » ÿ » /* » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 24 (Part 5 of 5). JCLIN ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix B. JCLIN for PPMP 2.2.0 36 ¯ ÿ ÿ APPENDIX C. IVP SAMPLE OUTPUT ÿ ÿ ÿ This appendix shows each report that is received when running the IVP ÿ jobs AIORNRFT, AIORNRFF and AIORNDSC. These reports may vary ÿ depending on the contents of your FONTLIB library. ÿ ÿ C.1 AIORNRFT SAMPLE REPORT ÿ ÿ Figure 25 shows the report received after running the AIORNRFT JCL. ÿ The job descriptor libraries J$PPMP and J$DFAULT are reformatted. The ÿ translation tables XRXLIC and XRXSTD are written to the data set ÿ RFTXRS. ÿ ÿ A return code of "4" should be received. Several messages are written ÿ stating that IBM resources correlated to Xerox resources are not ÿ found. There are also several messages stating that Xerox fonts do ÿ not exist. The number of messages depends on the number of Xerox ÿ resources and fonts that are available as input to this program. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » Date: mm/dd/yy Page Printer Migration Program Job: AIORNRFT » ÿ » Time: 15:30:05 Resource Reformatter Report Step: RFTFPD » ÿ » » ÿ » » ÿ » » ÿ » AIORFT204I AIOARFT reading parameters from SYSIN DD dataset. » ÿ » » ÿ » AIOPMS210I Processing RFT parameters... » ÿ » » ÿ » AIORFT226I The RFT options in effect are: » ÿ » » ÿ » FORMAT-PDS WORDSPC CSRC TRANSRC USLETTER » ÿ » NOPLIDUMP XCHECK LSKIP PTXSIZE=(52K,52K) » ÿ » PTXMAXAREAS=611 NOOVSAMPLE NOLFORMFONTS » ÿ » NOXRXSRCFILES » ÿ » » ÿ » AIORFT228I Files with the following filetypes will be processed:» ÿ » » ÿ » JDL (J$/J@) » ÿ » » ÿ » AIOTSF240I Processing Translation Source File... » ÿ » AIOTSF249I 2 translation tables were written to the RFTXRS PDS: » ÿ » XRXLIC XRXSTD » ÿ » » ÿ » AIOCSF230I Processing Correlation Source File... » ÿ » AIOCSF239I FCTAB was created with 246 entries. » ÿ » AIOCSF238W ICTAB was not created. » ÿ » AIOCSF238W LCTAB was not created. » ÿ » » ÿ » AIORFT250I Formatting/copying Xerox resources... » ÿ » » ÿ » AIORPT260I 2 Xerox resources were formatted/copied successfully:» ÿ » » ÿ » DFAULT.JDL PPMP.JDL » ÿ » » ÿ » » ÿ » AIORPT263I All requested Xerox resources were formatted/copied » ÿ » successfully. » ÿ » » ÿ » AIORPT262I No Xerox resources were skipped. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 25 (Part 1 of 2). AIORNRFT Sample Report ÿ ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 37 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » AIORPT270I The FCTAB has 246 entries. » ÿ » AIORPT271W IBM resource C0L0FM15, correlated to Xerox resource » ÿ » FFMT01, does not exist in the FONTLIB PDS. » ÿ » AIORPT271W IBM resource C0L0FM15, correlated to Xerox resource » ÿ » FFMT02 does not exist in the FONTLIB PDS. » ÿ » AIORPT271W IBM resource C0L0FM15, correlated to Xerox resource » ÿ » FFMT03, does not exist in the FONTLIB PDS. » ÿ » AIORPT271W IBM resource C0L0FM15, correlated to Xerox resource » ÿ » FFMT04, does not exist in the FONTLIB PDS. » ÿ » . » ÿ » . » ÿ » . » ÿ » AIORPT273W Xerox font UN611B referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » AIORPT273W Xerox font UN611C referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » AIORPT273W Xerox font UN611D referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » AIORPT273W Xerox font UN611E referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » AIORPT273W Xerox font UN611F referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » » ÿ » AIORPT270I The ICTAB has 0 entries. » ÿ » » ÿ » AIORPT270I The LCTAB has 0 entries. » ÿ » » ÿ » Processing ended with return code 4. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 25 (Part 2 of 2). AIORNRFT Sample Report ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix C. IVP Sample Output 38 ¯ ÿ ÿ C.2 AIORNRFF SAMPLE REPORT ÿ ÿ Figure 26 shows the report received after running the AIORNRFF JCL. ÿ The resources P0612C.FNT and L0112B.FNT are reformatted. ÿ ÿ A return code of "4" should be received. Several messages are written ÿ stating that IBM resources correlated to Xerox resources are not ÿ found. There are also several messages stating that Xerox fonts do ÿ not exist. The number of messages depends on the number of Xerox ÿ resources and fonts that are available as input to this program. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » Date: mm/dd/yy Page Printer Migration Program Job: AIORNRFF » ÿ » Time: 09:51:05 Resource Reformatter Report Step: RFTFTP » ÿ » » ÿ » » ÿ » AIORFT204I AIOARFT reading parameters from SYSIN DD dataset. » ÿ » » ÿ » AIOPMS210I Processing RFT parameters... » ÿ » » ÿ » AIOSEL220I Processing selection criteria... » ÿ » » ÿ » AIORFT226I The RFT options in effect are: » ÿ » » ÿ » FORMAT-TAPE WORDSPC NOCSRC NOTRANSRC » ÿ » USLETTER NOPLIDUMP XCHECK LSKIP » ÿ » PTXSIZEE=(52K,52K) PTXMAXAREAS=611 » ÿ » NOOVSAMPLE NOLFORMFONTS NOXRXSRCFILES » ÿ » » ÿ » AIORFT227I Members of the XRSPDS PDS with internal file » ÿ » names matching the following SELECT criteria » ÿ » will be processed: » ÿ » P0612C.FNT » ÿ » L0112B.FNT » ÿ » » ÿ » AIORFT250I Formatting/copying Xerox resources... » ÿ » » ÿ » AIORPT260I 2 Xerox resources were formatted/copied » ÿ » successfully: » ÿ » » ÿ » P0612C.FNT L0112B.FNT » ÿ » » ÿ » » ÿ » AIORPT263I All requested Xerox resources were » ÿ » formatted/copied successfully » ÿ » » ÿ » AIORPT262I No Xerox resources were skipped. » ÿ » » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 26 (Part 1 of 2). AIORNRFF Sample Report ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix C. IVP Sample Output 39 ¯ ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » AIORPT270I The FCTAB has 246 entries » ÿ » AIORPT271W IBM resource C0L0FM15, correlated to Xerox resource » ÿ » FFMT01, does not exist in the FONTLIB PDS. » ÿ » AIORPT271W IBM resource C0L0FM15, correlated to Xerox resource » ÿ » FFMT02, does not exist in the FONTLIB PDS. » ÿ » AIORPT271W IBM resource C0L0FM15, correlated to Xerox resource » ÿ » FFMT03, does not exist in the FONTLIB PDS. » ÿ » AIORPT271W IBM resource C0L0FM15, correlated to Xerox resource » ÿ » FFMT04, does not exist in the FONTLIB PDS. » ÿ » . » ÿ » . » ÿ » . » ÿ » AIORPT273W Xerox font UN611B referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » AIORPT273W Xerox font UN611C referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » AIORPT273W Xerox font UN611D referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » AIORPT273W Xerox font UN611E referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » AIORPT273W Xerox font UN611F referenced in the FCTAB » ÿ » does not exist in the RFTXRS PDS. » ÿ » » ÿ » AIORPT270I The ICTAB has 0 entries » ÿ » » ÿ » AIORPT270I The LCTAB has 0 entries » ÿ » » ÿ » Processing ended with return code 4. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 26 (Part 2 of 2). AIORNRFF Sample Report ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix C. IVP Sample Output 40 ¯ ÿ ÿ C.3 AIORNDSC SAMPLE REPORTS ÿ ÿ Figure 27 shows the SYSPRINT report received after running the ÿ AIORNDSC JCL. ÿ ÿ A return code of "0" should be received. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » Date: mm/dd/yy Page Printer Migration Program Job: AIORNDSC » ÿ » Time: 10:19:42 Data Stream Conversion Report Step: DSC » ÿ » » ÿ » » ÿ » AIODSC204I AIOBDSC reading parms from SYSIN DD dataset. » ÿ » » ÿ » AIODSC226I The DSC options in effect are: » ÿ » » ÿ » JDL=DFAULT JDE=ONLN COPIES=1 LINECOUNT=66 » ÿ » NOSPC REPORT NOPLIDUMP ACCOUNT » ÿ » PTXSIZE=(832K,832K) PTXMAXAREAS=39 » ÿ » PCCTYPE=IBM3211 NOTRBLANKS NONULLXRXIN » ÿ » » ÿ » AIONDR404I The XRXIN data set will be processed using » ÿ » ISO/ANSI/FIPS control characters. » ÿ » » ÿ » Processing ended with return code 0. » ÿ » » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 27. AIORNDSC SYSPRINT Sample Report ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix C. IVP Sample Output 41 ¯ ÿ ÿ Figure 28 shows the DJDERPT report received after running the AIORNDSC ÿ JCL. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » Date: mm/dd/yy Page Printer Migration Program Job: AIORNDSC» ÿ » Time: 10:19:42 Data Stream Conversion DJDE Report Step: DSC » ÿ » » ÿ » » ÿ » DJDE identifier found on record 1: » ÿ » $$XEROX DATA=(0,79),FONTS=(P0612C),; » ÿ » DJDE identifier found on record 2: » ÿ » $$XEROX PMODE=PORTRAIT,BEGIN=(1,1),; » ÿ » DJDE identifier found on record 3: » ÿ » $$XEROX END; » ÿ » » ÿ » » ÿ » END - An 'END;' DJDE was found. » ÿ » » ÿ » » ÿ » FONTS - The number of fonts listed was 1. » ÿ » » ÿ » FNT name IBM name(s) line spacing value » ÿ » » ÿ » P0612C C0D0GT15 T1D0BASE 0.125 inches or 30 pels » ÿ » BEGIN - The new page position is (1.000,1.000) inches » ÿ » or (240,240) pels. » ÿ » PMODE - The print mode will be portrait. » ÿ » DATA - Printable data now begins at byte 0 and » ÿ » continues for up to 79 bytes. » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 28. AIORNDSC DJDERPT Sample Report ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix C. IVP Sample Output 42 ¯ ÿ ÿ Figure 29 shows the output received from your AFP printer after ÿ running the AIORNDSC JCL. ÿ ÿ ¬ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ¼ ÿ » » ÿ » This is the output of the Page Printer Migration Programs » ÿ » Installation Verification Program. This text was originally » ÿ » printed on a Xerox LPS printer using the font P0612C. Now » ÿ » it is printed on an IBM Advanced Function Printer using the » ÿ » font GT15. The page should be printed in the portrait » ÿ » orientation. » ÿ » » ÿ » Numeric characters - 1234567890 » ÿ » Upper case alpha - ABCDEFGHIJKLMNOPQRSTUVWXYZ » ÿ » Lower case alpha - abcdefghijklmnopqrstuvwxyz » ÿ » » ÿ » AFP is a collection of licensed programs that, when used » ÿ » with a family of IBM page printers, can improve the quality » ÿ » and increase the flexibility of computer-printed output. » ÿ » These printers have the ability to place data not just at » ÿ » line and character positions but at any addressable point on » ÿ » the page. This capability is called all-points- » ÿ » addressability (APA). » ÿ » » ÿ » » ÿ » o Xerox is a registered trademark of the Xerox Corporation. » ÿ » o IBM is a registered trademark of the International » ÿ » Business Machines Corporation. » ÿ » » ÿ » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ Figure 29. AIORNDSC Printer Sample Report ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Appendix C. IVP Sample Output 43 ¯ ÿ ÿ APPENDIX D. COVER LETTER DATA ÿ ÿ ÿ Some PTFs incorporated into this level of PPMP 2.2.0 contain ÿ documentation changes that are not reflected in the PPMP 2.2.0 ÿ publications. These PTF cover letters should be reviewed for possible ÿ impact to the execution of this product. ÿ ÿ The Cover Letter Data for PPMP 2.2.0 follows: ÿ ÿ D.1 COVER LETTER FOR PTF UW32208 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW22395 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: When AIOBDSC processes input with * ÿ * comment or certain other valid DJDEs, * ÿ * MSGAIOJDP569E or MSGAIOJPS569E * ÿ * (invalid DJDE) is issued. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ OEM documentation of the comment DJDE is rather misleading, ÿ since it suggests that commentary text is terminated by the ÿ first comma or semicolon found outside of paired parentheses. ÿ AIOBDSC attempted to emulate this literally, with the result ÿ that parsing continued throughout comment DJDE records. Any ÿ text that might have been encountered was then identified as an ÿ invalid DJDE. In some cases, comment DJDE records were not ÿ recognized or identified as comments. ÿ ÿ Contrary to the original understanding of OEM documentation, ÿ printer tests show that, once the 'C ' DJDE has been ÿ encountered, the OEM LPS treats the entire remaining record ÿ as commentary. ÿ ÿ In addition, AIOBDSC was not able to recognize several valid ÿ DJDE parameters and options that have come into existence since ÿ the PPMP programs were first written. These were also flagged ÿ as invalid. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW22395 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ This APAR provides for correct handling of comment DJDEs. ÿ Although OEM documentation was originally understood to mean ÿ that parsing of comment DJDEs ends when a comma or semicolon is ÿ found outside of parentheses, OEM printer tests show that, once ÿ the comment DJDE 'C ' is encountered in the IDEN skip position, ÿ the remainder of the record is taken to be comments and no other ÿ parsing occurs. In other words, no other DJDE commands ÿ following a comment DJDE text will be processed. The DSC ÿ program now emulates this. ÿ Several other DJDEs are also now recognized and listed as ÿ unsupported in the DJDE report, rather than causing invalid ÿ DJDE message AIOxxx569E. ÿ * ÿ * Documentation changes for OW22395 ÿ * ÿ * Changes to Chapter 3 ÿ * ÿ On page 97 in Table 6, add to the supported DJDE commands, ÿ retaining alphabetical order: ÿ BATCH ÿ DEPT ÿ On page 98 in Table 7, remove from the unsupported DJDE ÿ commands, retaining alphabetical order: ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 44 ¯ ÿ ÿ BATCH ÿ DEPT ÿ On page 98 in Table 7, add to the unsupported DJDE commands, ÿ retaining alphabetical order: ÿ ICATALOG ÿ IDFAULT ÿ IDR ÿ ILIST ÿ INKINDEX ÿ IPALETTE ÿ IRESULT ÿ SEFFNT ÿ SEFMAP ÿ STOCKS ÿ XMP ÿ * ÿ * Changes to the Messages ÿ * ÿ On page 295, in the DJDE messages, after the existing FEED ÿ entry, add the following: ÿ FEED - The {option} option of the FEED DJDE is not ÿ supported. ÿ Explanation: Only the AUX, MAIN and OPR FEED options are ÿ supported at this time. ÿ On page 295, in the DJDE messages, after the existing ÿ GRAPHIC entry, add the following: ÿ ICATALOG - The ICATALOG DJDE is not supported. ÿ Explanation: This messages indicates that an ICATALOG ÿ DJDE (which is not supported by the DSC program) ÿ is present. ÿ IDFAULT - The IDFAULT DJDE is not supported. ÿ Explanation: This messages indicates that an IDFAULT ÿ DJDE (which is not supported by the DSC program) ÿ is present. ÿ IDR - The IDR DJDE is not supported. ÿ Explanation: This messages indicates that an IDR DJDE ÿ (which is not supported by the DSC program) is ÿ present. ÿ ILIST - The ILIST DJDE is not supported. ÿ Explanation: This messages indicates that an ILIST DJDE ÿ (which is not supported by the DSC program) is ÿ present. ÿ On page 295, in the DJDE messages, after the existing ÿ IMAGE entry, add the following: ÿ INKINDEX - The INKINDEX DJDE is not supported. ÿ Explanation: This messages indicates that an INKINDEX ÿ DJDE (which is not supported by the DSC program) ÿ is present. ÿ IPALETTE - The IPALETTE DJDE is not supported. ÿ Explanation: This messages indicates that an IPALETTE ÿ DJDE (which is not supported by the DSC program) ÿ is present. ÿ IRESULT - The IRESULT DJDE is not supported. ÿ Explanation: This messages indicates that an IRESULT ÿ DJDE (which is not supported by the DSC program) ÿ is present. ÿ On page 300, in the DJDE messages, after the existing ÿ SAVE entry, add the following: ÿ SEFFNT - The SEFFNT DJDE is not supported. ÿ Explanation: This messages indicates that a SEFFNT ÿ DJDE (which is not supported by the DSC program) ÿ is present. ÿ SEFMAP - The SEFMAP DJDE is not supported. ÿ Explanation: This messages indicates that a SEFMAP ÿ DJDE (which is not supported by the DSC program) ÿ is present. ÿ On page 300, in the DJDE messages, after the existing ÿ SIDE entry, add the following: ÿ STOCKS - The STOCKS DJDE is not supported. ÿ Explanation: This messages indicates that a STOCKS ÿ DJDE (which is not supported by the DSC program) ÿ is present. ÿ On page 300, in the DJDE messages, after the existing ÿ TOF entry, add the following: ÿ XMP - The XMP DJDE is not supported. ÿ ÿ Appendix D. Cover Letter Data 45 ¯ ÿ ÿ Explanation: This messages indicates that an XMP DJDE ÿ (which is not supported by the DSC program) is ÿ present. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOBJDP OW22395 ÿ AIOBJPS OW22395 ÿ AIOCMWR OW22395 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW22395 AIOBJDP AIOBJPS AIOCMWR ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOBJDP ÿ AIOBJPS ÿ AIOCMWR ÿ ÿ LISTEND ÿ */. ÿ ÿ D.2 COVER LETTER FOR PTF UW33692 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW22661 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: When AIOBDSC processes input using * ÿ * the ACCT JDL/JDE parameter, extra and * ÿ * otherwise inaccurate accounting pages * ÿ * are printed. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ Accounting pages generated by AIOBDSC refer to the wrong ÿ JDL and JDE, show incorrect font, forms and CME lists and ÿ contain numerous other errors. Extraneous accounting pages are ÿ issued which also appear to contain incorrect data. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW22661 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ ACTION: ÿ Emulation of accounting pages. ÿ This APAR incorporates numerous corrections to the PPMP ÿ emulation of OEM accounting pages. Anyone making use of these ÿ pages should reformat any JDLs which include CMEs, so that the ÿ reformatted JDLs in the RFTXRS will include internal CME names ÿ for the accounting page CME list. ÿ Corrections, improvements and additions have been made to ÿ many parts of the accounting pages: ÿ 1. The date and time are derived separately for each ÿ accounting page. ÿ 2. The accuracy of several counters has been improved, ÿ including PAGES TO BIN, LINES PRINTED, BLOCKS READ, RECORDS ÿ READ, DJDE RECORDS READ and OVERPRINTS. ÿ 3. SIMPLEX/DUPLEX now shows BOTH in duplex mode, since ÿ the accounting page itself is simplex. ÿ 4. The correct JDE,JDL USED is shown. ÿ 5. The correct INITIAL FONT, FORM and CME LISTs are ÿ shown. ÿ The accounting page control blocks now include bit flags for ÿ indicating whether the "(DJDE MODIFIED)" message is to appear ÿ with the FORMS, FONTS or CMES accounting page lists. AIOBJDP ÿ sets the new flags to true if the FORMS, FONTS or MODIFY DJDEs ÿ are encountered. AIOBJPG also sets the FORMS flag when it ÿ detects the FORMS DJDE. AIOBJJD sets the CME flag if it finds ÿ that a JDL/JDE invoked by a DJDE changes the presence or absence ÿ ÿ Appendix D. Cover Letter Data 46 ¯ ÿ ÿ of CMEs. ÿ AIOBRPT prints the "(DJDE MODIFIED)" messages when signaled ÿ to do so by the flags, and then resets all three flags to false ÿ in both active and next active environments. ÿ Users should note that the values printed by AIOBRPT for ÿ some of the accumulators may not match those produced by the ÿ OEM LPS in all cases. For example, the LPS includes OEM, ÿ site-dependent banner pages in the PAGES TO BIN and LINES ÿ PRINTED. PPMP has no way of knowing about these in an AFP ÿ environment, so no attempt has been made to account for them. ÿ It has also been observed that, if CMEs are in effect, the ÿ OEM LINES PRINTED value is greater than the number of lines ÿ actually printed. No correlation could be found with the CMEs ÿ used in testing, so PPMP will continue to show the actual ÿ number of lines printed, regardless of whether CMEs are in ÿ effect. Likewise, when online input data uses a carriage ÿ control scheme other than IBM3211 (so that translation to ÿ IBM3211 occurs), the RECORDS READ total may not match the ÿ number of records actually found in the XRXIN dataset. ÿ There is one other OEM accounting page peculiarity that ÿ should be noted. When running several jobs on an OEM printer ÿ (e.g., 97xx, 4050, 4090, etc.), if a job issuing accounting ÿ pages follows one or more which do not, some of the counter ÿ values from the jobs not issuing accounting pages appear to ÿ carry over into the values for the first page issued by the ÿ job that does create such pages. In an AFP environment, PPMP ÿ cannot access such information from preceding jobs and so will ÿ not attempt to emulate this particular oddity. ÿ Users may also notice certain differences in layout between ÿ OEM and PPMP accounting pages, such as header and footer lines, ÿ indentation, line spacing and the like. OEM documentation ÿ suggests that it is possible to customize the appearance of ÿ accounting pages with regard to such particulars. Owing to ÿ the migratory nature of the use of PPMP, no attempt will be ÿ made at this time to emulate accounting page customization. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOAJ@3 OW22661 ÿ AIOBDSC OW22661 ÿ AIOBEDR OW22661 ÿ AIOBINI OW22661 ÿ AIOBJDP OW22661 ÿ AIOBJJD OW22661 ÿ AIOBJPG OW22661 ÿ AIOBLDD OW22661 ÿ AIOBNDR OW22661 ÿ AIOBOLG OW22661 ÿ AIOBRPT OW22661 ÿ AIOBSDR OW22661 ÿ AIOBSRT OW22661 ÿ AIOBXJJ OW22661 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW22661 AIOAJ@3 AIOBDSC AIOBEDR AIOBINI AIOBJDP AIOBJJD ÿ AIOBJPG AIOBLDD AIOBNDR AIOBOLG AIOBRPT AIOBSDR ÿ AIOBSRT AIOBXJJ ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOAJ@3 ÿ AIOBDSC ÿ AIOBEDR ÿ AIOBINI ÿ AIOBJDP ÿ AIOBJJD ÿ AIOBJPG ÿ AIOBLDD ÿ AIOBNDR ÿ AIOBOLG ÿ AIOBRPT ÿ AIOBSDR ÿ AIOBSRT ÿ AIOBXJJ ÿ ÿ Appendix D. Cover Letter Data 47 ¯ ÿ ÿ LISTEND ÿ */. ÿ ÿ D.3 COVER LETTER FOR PTF UW35078 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW23506 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: While reformatting FRMs, AIOARFT * ÿ * issues MSGAIOM@M259S citing FRM file * ÿ * extensions which are neither FNT nor * ÿ * LGO. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ This APAR marks PPMP's first encounter with FRM files ÿ created on one of the OEM highlight color printer models ÿ (4850/4890). The resource lists in these FRMs include color ÿ ink references. Since PPMP could not recognize these, it ÿ issued MSGAIOM@M259S for each ink reference. ÿ ÿ Testing also showed that, if an FRM contained text and ÿ graphic fonts, logos, images and/or ink references, none of the ÿ resources in any category were listed if errors occurred in any ÿ of them. For example, if an FRM included fonts, logos, images ÿ and ink references, none if these would be listed if one of the ÿ logos was not found in the correlation table, even though no ÿ errors were encountered in connection with the fonts, images or ÿ inks. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW23506 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ COLOR INK REFERENCES IN FRM FILES. ÿ Application of this APAR fix allows AIOARFT to recognize, ÿ list and ignore highlight color ink references in FRM files ÿ being converted to overlays. If the LFF option is in effect, ÿ AIOARFT lists any ink references encountered along with fonts, ÿ logos and images used in each FRM file. ÿ * ÿ * Documentation changes for OW23506 ÿ * ÿ * Changes to Chapter 1 ÿ * ÿ On page 9 under Printing Resources, the bulleted items ÿ should read: ÿ . Job Descriptor Library (JDL) files ÿ . Page Descriptor Entry (PDE) files ÿ . Copy Modification Entry (CME) files ÿ . Routing text (TST) files ÿ . Font (FNT) files ÿ . Form (FRM) files ÿ . Image (IMG) and Logo (LGO) files ÿ . Stockset (STK) files ÿ . Ink Catalog (ICT) and Ink Descriptor Entry (IDR) files ÿ (highlight color only) ÿ . Command (CMD), Data (DAT), Forms Source Library (FSL), Ink ÿ Source Library (ISL), Job Source Library (JSL), Utility ÿ (LIB), User Temporary (MSC), Patch (PCH) and Temporary ÿ (TMP) files ÿ On page 9, change the second sentence from the end of the ÿ page to read: ÿ The Xerox CMD, DAT, FSL, ICT, IDR, ISL, JSL, LIB, MSC, ÿ PCH, STK, TMP and TST files have no AFP resource ÿ equivalents. ÿ On page 17, in Table 3, add an entry in the existing format ÿ after "FDL Forms Source Library (FSL) files": ÿ ICO Ink Source Library (ISL) files ÿ * ÿ * Changes to Chapter 3 ÿ ÿ Appendix D. Cover Letter Data 48 ¯ ÿ ÿ * ÿ On page 42 in Figure 15, add these filetypes, retaining ÿ alphabetical order: ÿ ICT ÿ IDR ÿ ISL ÿ STK ÿ On pages 48 and 49, under Filetype Parameters, add these ÿ entries, retaining alphabetical order: ÿ . ICT Specifies that RFT should process ink catalog files. ÿ . IDR Specifies that RFT should process Ink Descriptor ÿ Entry files. ÿ . ISL Specifies that RFT should process Ink Source Library ÿ files. ÿ . STK Specifies that RFT should process stockset files. ÿ On page 49, add ISL to the lists of source file types in the ÿ NOXRXSRCFILES and XRXSRCFILES bullets, retaining ÿ alphabetical order. ÿ On page 77, in Table 5, add the following entries in the ÿ existing format, retaining alphabetical order by Xerox ÿ Resource PDS prefix: ÿ .ICT U$ n/a n/a ÿ .IDR V$ n/a n/a ÿ .ISL W$ W@ n/a ÿ .STK Y$ Y@ (future) n/a ÿ On page 78, add ISL to the lists of source file types in the ÿ Reformatted Xerox Resources and Reformatted Xerox Source ÿ Files materials, retaining alphabetical order. ÿ On page 98 in Table 7, under unsupported DJDE commands, ÿ change IPALETTE to PALETTE, retaining alphabetical order. ÿ * ÿ * Changes to the Messages ÿ * ÿ On page 282, add the following for AIOxxx444I, after the ÿ message text for image references: ÿ AIOxxx444I The number of highlight color ink references in ÿ form ffffff was x. ÿ Ink catalog name.Palette name.Color name ÿ ict_name.palette_name.color_name ÿ . . . ÿ . . . ÿ . . . ÿ ict_name.palette_name.color_name ÿ On page 282, change the explanation of message AIOxxx444I ÿ to read: ÿ Explanation: This is an informational message indicating ÿ which fonts, logos, images or highlight color resources ÿ are used in Xerox form ffffff. x and y are numeric values. ÿ fnt_name identifies a Xerox font, lgo_name identifies a ÿ Xerox logo and img_name identifies a Xerox image. If ÿ Xerox highlight color resource references were found, ÿ ict_name identifies an ink catalog, palette_name identifies ÿ a palette within the catalog and color_name identifies a ÿ color within the palette. ibm_name identifies the AFP font ÿ name.... (unchanged from this point) ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOAJ@M OW23506 ÿ AIOAJ@1 OW23506 ÿ AIOAM@M OW23506 ÿ AIOAPMS OW23506 ÿ AIOARFT OW23506 ÿ AIOARPT OW23506 ÿ AIOBDSC OW23506 ÿ AIOBINI OW23506 ÿ AIOBXFN OW23506 ÿ AIOCMWR OW23506 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW23506 AIOAJ@M AIOAJ@1 AIOAM@M AIOAPMS AIOARFT AIOARPT ÿ AIOBDSC AIOBINI AIOBXFN AIOCMWR ÿ ÿ Appendix D. Cover Letter Data 49 ¯ ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOAJ@M ÿ AIOAJ@1 ÿ AIOAM@M ÿ AIOAPMS ÿ AIOARFT ÿ AIOARPT ÿ AIOBDSC ÿ AIOBINI ÿ AIOBXFN ÿ AIOCMWR ÿ ÿ LISTEND ÿ */. ÿ ÿ D.4 COVER LETTER FOR PTF UW37778 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW26001 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: Reports produced by AIOARFT and * ÿ * AIOBDSC show dates as mm/dd/yy and * ÿ * thus do not support Year2000 (YR2000). * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ Reports produced by AIOARFT (SYSPRINT) and AIOBDSC (DJDERPT ÿ and SYSPRINT) include dates with 2-digit years. The year shown ÿ in OEM accounting page dates is also limited to 2 digits. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW26001 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ * Documentation changes for OW26001 ÿ * ÿ * Changes to Chapter 3 ÿ * ÿ On page 80, in Figure 37, change the date in the first ÿ line of the example to a 4-digit year: ÿ Date: 02/25/1994 Page Printer Migration Program ... ÿ On page 96, in Figure 48, change the date in the first ÿ line of the example to a 4-digit year: ÿ Date: 02/25/1994 Page Printer Migration Program ... ÿ On page 97, in Figure 49, change the date in the first ÿ line of the example to a 4-digit year: ÿ Date: 02/25/1994 Page Printer Migration Program ... ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOARFT OW26001 ÿ AIOBDSC OW26001 ÿ AIOBEDR OW26001 ÿ AIOBINI OW26001 ÿ AIOBJDP OW26001 ÿ AIOBJJD OW26001 ÿ AIOBJPG OW26001 ÿ AIOBNDR OW26001 ÿ AIOBRPT OW26001 ÿ AIOBSDR OW26001 ÿ AIOBSRT OW26001 ÿ AIOBXJJ OW26001 ÿ AIOCMWR OW26001 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW26001 AIOARFT AIOBDSC AIOBEDR AIOBINI AIOBJDP AIOBJJD ÿ AIOBJPG AIOBNDR AIOBRPT AIOBSDR AIOBSRT AIOBXJJ ÿ ÿ Appendix D. Cover Letter Data 50 ¯ ÿ ÿ AIOCMWR ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOARFT ÿ AIOBDSC ÿ AIOBEDR ÿ AIOBINI ÿ AIOBJDP ÿ AIOBJJD ÿ AIOBJPG ÿ AIOBNDR ÿ AIOBRPT ÿ AIOBSDR ÿ AIOBSRT ÿ AIOBXJJ ÿ AIOCMWR ÿ ÿ LISTEND ÿ */. ÿ ÿ D.5 COVER LETTER FOR PTF UW40161 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW27501 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: When processing line data, AIOBDSC * ÿ * causes some lines to be printed too * ÿ * high or too low on the page. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ When beginning new pages (logical or physical), the OEM LPS ÿ adjusts initial baselines up or down. Although documentation ÿ of this adjustment is scant or nonexistent in the OEM manuals, ÿ research showed that the adjustment is made according to the ÿ following formula: ÿ ÿ BLinit = BLinit + (FontHeight(CurrFont) - ÿ FontHeight(PrevFont)) ÿ ÿ where ÿ ÿ BLinit is the initial baseline ÿ ÿ FontHeight is the OEM font height metric ÿ ÿ CurrFont is the font of the initial, current line ÿ ÿ PrevFont is the last (rightmost) font used on the ÿ last line of the previous page. ÿ ÿ Since AIOBDSC had no provision for making this adjustment, ÿ output lines were printed too high or too low if the last font ÿ of a logical or physical page just concluded had a font height ÿ different from that of the initial font of the new page. ÿ ÿ The particular data involved in testing also caused a large ÿ number of occurrences of MSGAIOLTF610E (translation error ÿ due to a character not being found in the code page). ÿ ÿ Several other problems are addressed by this APAR, in ÿ addition to the one reported: ÿ ÿ I. Image position is calculated using the wrong ÿ orientation, and AIOBDSC times out in infinite loop. ÿ ÿ AIOBMTD was updating lp_LANDSCAPE so it would know the ÿ orientation of the last record when a font change occurred. ÿ However, AIOBMTD is internally coded to start each record in a ÿ ÿ Appendix D. Cover Letter Data 51 ¯ ÿ ÿ portrait orientation. Thus, lp_LANDSCAPE did not represent ÿ the actual orientation from the currently active JDE or ÿ overriding PMODE. This wasn't a problem till AIOBJRC used the ÿ lp_LANDSCAPE to determine the orientation from the JDE/PMODE ÿ (for which there is no longer a variable). ÿ ÿ When AIOBNDR tries to skip past an inline graphic (in the ÿ read_graphic routine), it knows to stop reading records when it ÿ hits EOF but it keeps checking the last record for the end ÿ graphic character. If no record exists with the end graphic ÿ character, it loops forever. ÿ ÿ II. RTEXT=('....',ALL) on a DJDE is never honored. ÿ ÿ When an RTEXT with the passnum set to ALL is encountered, ÿ rtx_PASSNUM is being set to 32767 in AIOBJPS. This eventually ÿ is propogated to rxr_TST_pass(n). When AIOBSRT tries to ÿ determine if there is an RTEXT for the current copy ply, it does ÿ not honor a value of 32767 in the rxr_TST_pass to signify all ÿ copy plys so it will not use that RTEXT until copy number is ÿ 32767. ÿ ÿ III. When AIOBDSC processes line data input, page breaks ÿ occur in the wrong places. ÿ ÿ This problem was observed when running with CYCLEFORMS, ÿ DUPLEX and no data on the back sides. In the datastream ANSI ÿ carriage control '1's immediately precede and follow DJDE ÿ packets. In this situation, when the djde-before-end-of-page ÿ processing is occurring, if the DJDE causes the page to end ÿ but the page ending routine is not called (because there is no ÿ text on the page) yet the sheet is ended, the end-of-page flag ÿ is left on, causing a page eject after the 1st record of the ÿ next sheet is processed. ÿ ÿ IV. The accounting page is missing at the start of a job. ÿ ÿ The accounting page is a result of an RSTACK at the ÿ beginning of the job after a DJDE. ÿ ÿ AIOBRPT was actually called and control blocks were built ÿ for the accounting page. However, when AIOBEDR was processing ÿ the environment change, since there were no normal printed ÿ pages, the control block chain in which the accounting page was ÿ anchored was discarded. ÿ ÿ Also, when AIOBARL was preparing to generate AFPDS, it put ÿ the accounting page at the end of the appropropriate control ÿ block chain only if there were pages in the chain. If there ÿ were no pages, the accounting page was not put at the end of the ÿ chain, so no pages were generated. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW27501 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ New Options: NOTRBLANKS, TRBLANKS ÿ * Changes to Chapter 3 ÿ * ÿ On page 83 in Figure 39, after the line for NOSPC » WORDSPC, ÿ etc., add: ÿ {NOTRBLANKS » TRBLANKS} ÿ with NOTRBLANKS underlined. Use square brackets, as with ÿ the other parameters in the figure (I don't have them under ÿ ISPF). ÿ On page 83 in Figure 40, after the line for CHARSPC add: ÿ NOTRBLANKS NTB ÿ TRBLANKS TB ÿ On page 85 in the last paragraph of the Print Fidelity ÿ Parameters section, the first sentence should be changed to ÿ read ÿ If either word or character spacing is specified, the DSC ÿ program will ... ÿ On page 85 at the end of the discussion of Print Fidelity ÿ ÿ Appendix D. Cover Letter Data 52 ¯ ÿ ÿ Parameters and just before the section on Report Parameters, ÿ add the following: ÿ If you select NOSPC and you are processing line data input, ÿ two additional parameters allow you to control whether ÿ trailing blanks in the input records will be written to the ÿ AFP output: ÿ TRBLANKS This parameter specifies that trailing blanks in ÿ line data input should be written to the AFP ÿ output. ÿ NOTRBLANKS This parameter specifies that trailing blanks in ÿ line data input should not be written to the AFP ÿ output. Input records consisting entirely of ÿ blanks will be truncated to a single blank. ÿ This is the default. ÿ Using the NOTRBLANKS parameter can significantly reduce the ÿ size of your AFP output data set and improve printer ÿ performance. ÿ If you select WORDSPC or CHARSPC, TRBLANKS and NOTRBLANKS ÿ will be ignored and will not be listed with the options in ÿ effect in message AIODSC226I in the DSC report. ÿ DOCUMENTATION: ÿ DCB RECFM no longer examined ÿ Beginning with this APAR, the DCB RECFM parameter for the ÿ XRXIN dataset will no longer be examined to determine whether ÿ printer carriage controls should be expected. Instead, the ÿ PCCTYPE option and the carriage control type indicator in ÿ reformatted JDLs will be used to make this determination. ÿ This means that, for example, an XRXIN file with ANSI ÿ carriage controls could be allocated as RECFM=FB or VB, rather ÿ than FBA or VBA, so long as the correct control character type ÿ is specified. ÿ * ÿ * Documentation changes for OW21742 ÿ * These changes apply to the Page Printer Migration Programming ÿ * Guide: S544-3228-03. ÿ * ÿ * Changes to Chapter 3 ÿ * ÿ On page 87 change the bullet added for OW08454, after ÿ "you should note the following about the DSC DD ÿ statements:", to read: ÿ XRXIN If the XRXIN data set includes printer carriage ÿ control characters, you should verify that the ÿ correct control character type is specified in ÿ the PCCTYPE option (see Printer Carriage Control ÿ Type Parameter on page 84). ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ Reformat OEM fonts ÿ Application of this APAR fix allows AIOARFT to accurately ÿ emulate OEM placement of initial lines on pages produced from ÿ line data. In order to implement this fix, you must reformat ÿ all of your OEM fonts using the AIOARFT program, so as to make ÿ additional OEM font metrics available in the reformatted font ÿ members of your RFTXRS PDS. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOAF@M OW27501 ÿ AIOAM@M OW27501 ÿ AIOBARL OW27501 ÿ AIOBCF1 OW27501 ÿ ÿ Appendix D. Cover Letter Data 53 ¯ ÿ ÿ AIOBEDR OW27501 ÿ AIOBINI OW27501 ÿ AIOBJJD OW27501 ÿ AIOBLCM OW27501 ÿ AIOBLDD OW27501 ÿ AIOBLGF OW27501 ÿ AIOBLSF OW27501 ÿ AIOBLTF OW27501 ÿ AIOBMTD OW27501 ÿ AIOBNDR OW27501 ÿ AIOBOLG OW27501 ÿ AIOBPGE OW27501 ÿ AIOBRPT OW27501 ÿ AIOBSDR OW27501 ÿ AIOBSRT OW27501 ÿ AIOBTPX OW27501 ÿ AIOBWF1 OW27501 ÿ AIOBXFN OW27501 ÿ AIOBXJJ OW27501 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW27501 AIOAF@M AIOAM@M AIOBARL AIOBCF1 AIOBEDR AIOBINI ÿ AIOBJJD AIOBLCM AIOBLDD AIOBLGF AIOBLSF AIOBLTF ÿ AIOBMTD AIOBNDR AIOBOLG AIOBPGE AIOBRPT AIOBSDR ÿ AIOBSRT AIOBTPX AIOBWF1 AIOBXFN AIOBXJJ ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOAF@M ÿ AIOAM@M ÿ AIOBARL ÿ AIOBCF1 ÿ AIOBEDR ÿ AIOBINI ÿ AIOBJJD ÿ AIOBLCM ÿ AIOBLDD ÿ AIOBLGF ÿ AIOBLSF ÿ AIOBLTF ÿ AIOBMTD ÿ AIOBNDR ÿ AIOBOLG ÿ AIOBPGE ÿ AIOBRPT ÿ AIOBSDR ÿ AIOBSRT ÿ AIOBTPX ÿ AIOBWF1 ÿ AIOBXFN ÿ AIOBXJJ ÿ ÿ LISTEND ÿ */. ÿ ÿ D.6 COVER LETTER FOR PTF UW00062 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW09270 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP V2R2M0 * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: When AIOBDSC processes line data * ÿ * containing DJDE records, extraneous * ÿ * blank lines are written to the AFP * ÿ * output. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ When AIOBDSC processes line data containing DJDE records ÿ with ANSI carriage controls, extraneous blank lines may be ÿ written to the AFP output. This happens because AIOBNDR ÿ contains no provision for halting the incrementing of line ÿ ÿ Appendix D. Cover Letter Data 54 ¯ ÿ ÿ numbers when DJDE records with spacing carriage controls are ÿ encountered within the page. Since many of the most commonly ÿ used DJDEs are effective on page boundaries, DJDE records tend ÿ to occur immediately prior to the beginning of a new page. Thus ÿ the line numbering problem is masked when the affected fields ÿ are reset for the page break. However, if DJDE records which ÿ are immediately effective (e.g., ASSIGN, TOF, BOF, IMAGE or ÿ ALTER) appear in the middle of a page and include ANSI carriage ÿ controls other than "+" or "1", the locations of subsequent data ÿ records are thrown off by the failure of AIOBNDR to suspend the ÿ incrementing of line numbers. ÿ ÿ Testing for this APAR showed that AIOBDSC has no way to ÿ handle an incorrect carriage control type specification in the ÿ XRXIN data set RECFM. ÿ ÿ Research on this problem also revealed that, when the OEM ÿ accounting page is to be printed but OEM font P0612C is missing ÿ from the font correlation table, an ABEND0C4 occurs because ÿ AIOBRPT does not properly issue a return code that can be ÿ intercepted on return to AIOBNDR. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW09270 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ PPMP will verify the type of carriage controls in the data. ÿ The following changes refer to the Page Printer Migration ÿ Programming Guide, S544-3228-03. ÿ * ÿ * Changes to Chapter 3: ÿ * ÿ On page 87 insert a bullet, using the existing format, ÿ after "you should note the following about the DSC DD ÿ statements:" ÿ XRXIN If the XRXIN data set consists of line data with ÿ printer carriage control characters, you should ÿ verify that the correct control character type is ÿ specified, either in the data set attributes or ÿ using DCB=RECFM in the JCL DD statement for ÿ XRXIN. For line data input with carriage ÿ controls, the DSC program will attempt to verify ÿ the control character type by examining the ÿ control character of the first record. If the ÿ type of control characters found in the data set ÿ do not match those specified in the attributes or ÿ JCL, a warning message will be issued and the ÿ control character type actually found in the ÿ XRXIN data set will be used. Note that the DSC ÿ program will not attempt to distinguish between ÿ ANSI and machine code control characters if the ÿ first control character in the data set is x'C1' ÿ or x'C3', since these may function as either ÿ type. ÿ * ÿ * Addition to Appendix E: ÿ * ÿ On page 287 add: ÿ AIOxxx404W The type of control characters specified for the ÿ XRXIN data set (RECFM=recfm_1) does not match the ÿ control characters found in the file. AIOBDSC ÿ will assume cc_type2 control characters ÿ (RECFM=recfm_2) instead of cc_type1 control ÿ characters (RECFM=recfm_1). ÿ Explanation: One type of printer carriage control records ÿ was specified for the XRXIN data set but another type was found. ÿ recfm_1 is the RECFM of the XRXIN data set (whether from the ÿ data set attributes or from DCB=RECFM=recfm_1 in the XRXIN DD ÿ JCL statement), cc_type1 is the carriage control type associated ÿ with recfm_1, cc_type2 is the carriage control type found in the ÿ XRXIN data set and recfm_2 is the RECFM with recfm_2, the ÿ carriage control type that will be assumed by AIOBDSC. cc_type1 ÿ and cctype_2 can be either of the following: ÿ . ISO/ANSI/FIPS ÿ ÿ Appendix D. Cover Letter Data 55 ¯ ÿ ÿ . machine code ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOARFT OW09270 ÿ AIOATSF OW09270 ÿ AIOBDSC OW09270 ÿ AIOBINI OW09270 ÿ AIOBNDR OW09270 ÿ AIOBRPT OW09270 ÿ AIOCMWR OW09270 ÿ AIOCPIO OW09270 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW09270 AIOARFT AIOATSF AIOBDSC AIOBINI AIOBNDR AIOBRPT ÿ AIOCMWR AIOCPIO ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOARFT ÿ AIOATSF ÿ AIOBDSC ÿ AIOBINI ÿ AIOBNDR ÿ AIOBRPT ÿ AIOCMWR ÿ AIOCPIO ÿ ÿ LISTEND ÿ */. ÿ ÿ D.7 COVER LETTER FOR PTF UW26942 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW19035 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: AIOBDSC abends with ONCODE3094 * ÿ * (S0C4). LINECOUNT and COPIES options * ÿ * may be reported as zero. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ When reporting on the options in effect, AIOBINI attempts ÿ to show values for COPIES and LINECOUNT, but the control block ÿ pointers required to access the variables needed have not been ÿ initialized. Depending on what the contents of the pointer ÿ variables happens to be at the time, an S0C4 abend may result ÿ or COPIES and LINECOUNT may simply be reported as having been ÿ set to zero. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW19035 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ DOWNLOADABLE PDES ÿ These are the changes to the Page Printer Migration Programmin ÿ Guide (S544-3228) for this PTF: ÿ On page 289, add the following to the explanation for ÿ AIOxxx550W: ÿ djde_record is the DJDE record that was ignored. If the ÿ DJDE record was a downloadable PDE (FORMAT=*), djde_record ÿ contains a message indicating that the fonts listed in the ÿ downloadable PDE will not be used. ÿ On page 294, add the following to the explanation for ÿ DJDE -: ÿ If the DJDE record is a downloadable PDE (FORMAT=*), ÿ djde_record contains a message indicating that the fonts ÿ in the downloadable PDE will be listed subsequently in a ÿ ÿ Appendix D. Cover Letter Data 56 ¯ ÿ ÿ FORMAT message (see FORMAT - on p. 295). ÿ * ÿ * Addition to the Glossary of selected Xerox Terms: ÿ * ÿ On page 315 add: ÿ Downloadable PDE. A DJDE which begins with 'FORMAT=*' and ÿ contains a list of fonts and linespacing overrides. The ÿ downloadable PDE was developed for use with early versions ÿ of Xerox printer software. Although it has been ÿ supplanted by the FONTS DJDE, it is still supported by ÿ later printer software versions. XICS and HFDL can ÿ optionally generate downloadable PDEs when producing ÿ metacode output. The FORMAT=* DJDE may also be found in ÿ metacode produced by programs written by Xerox customers. ÿ DOCUMENTATION: ÿ PTXSIZE and PTXMAXAREAS documentation ÿ On page 51 under Performance Parameters, change the ÿ existing wording to read: ÿ The RFT program has two performance parameters. ÿ PTXSIZE Specifies the sizes of internal data areas used ÿ by the RFT program when reformatting Xerox FRM ÿ files..... (rest of paragraph unchanged) ÿ The syntax for the PTXSIZE parameter can be one of the ÿ following: ÿ . PTXSIZE=nU (use the default secondary PTXSIZE) ÿ . PTS=nU (use the default secondary PTXSIZE) ÿ . PTXSIZE=(nU) (use the default secondary PTXSIZE) ÿ . PTS=(nU) (use the default secondary PTXSIZE) ÿ . PTXSIZE=(nU,nU) (specify primary and secondary PTXSIZEs) ÿ . PTS=(nU,nU) (specify primary and secondary PTXSIZEs) ÿ where n is a numeric integer character string representing ÿ the wanted number of kilobytes (K) or megabytes (M) and ÿ U is the units (K or M). The default primary and ÿ secondary PTXSIZE for the RFT program is the lesser of ÿ 52K, or the adjusted GETMAIN limit for virtual storage ÿ above 16M....(rest of paragraph unchanged) ÿ PTXMAXAREAS Specifies the maximum number of primary and ÿ secondary internal data areas that can be ÿ allocated. ÿ The syntax for the PTXMAXAREAS parameter is: ÿ . PTXMAXAREAS=n ÿ where n is a nonzero numeric integer character string ÿ representing the wanted number of internal data areas. If ÿ PTXMAXAREAS is not coded, the RFT program will calculate ÿ the number of areas that can be allocated, based on the ÿ primary and secondary PTXSIZE values. ÿ On page 99 and following pages, under Using the PTXSIZE ÿ and PTXMAXAREAS Parameters, change the wording to read as ÿ follows: ÿ PPMP Version 2 Release 1, or later releases, lets you ÿ control performance of the RFT and DSC programs using the ÿ PTXSIZE and PTXMAXAREAS parameters and extended virtual ÿ storage. Both programs use internal areas for storing ÿ output data in an internediate format. ÿ If the amount of data processed exceeds the primary data ÿ area, PPMP allocates and uses secondary areas as long as ÿ space is available and the number of areas does not ÿ exceed PTXMAXAREAS. When more than one area is used, ÿ message AIOxxx205I is issued to indicate how many areas ÿ were allocated and the primary PTXSIZE that would have ÿ been required to only use one area. This information ÿ can be helpful in improving performance of other jobs, ÿ since use of multiple intermediate format data areas can ÿ increase execution time due to the additional HEAP ÿ requests to get system storage that may be required. ÿ If the amount of data processed exceeds the size of the ÿ available internal areas, PPMP uses the temporary dataset ÿ SYSUT1, in addition to virtual storage, which can greatly ÿ increase execution time. When PPMP writes data to SYSUT1, ÿ message AIOxxx200I is issued to indicate how much data is ÿ involved and to recommend values to use for PTXSIZE and ÿ HEAP. ÿ The effect of PTXSIZE, PTXMAXAREAS and HEAP should be to ÿ allow you to allocate, above 16M, an area of virtual ÿ storage large enough to hold all the intermediate data. ÿ ÿ Appendix D. Cover Letter Data 57 ¯ ÿ ÿ Since it is difficult to know in advance exactly how much ÿ virtual storage will be needed, you can use the secondary ÿ PTXSIZE parameter to decrease the chances of using I/O ÿ to SYSUT1 and yet avoid requesting more storage than ÿ your job actually needs. If a large amount of data is ÿ being processed and too much virtual storage is being ÿ used, PTXMAXAREAS allows you to limit the number of ÿ secondary data areas that will be allocated. ÿ The minimum size for the data areas of both AIOARFT and ÿ AIOBDSC is 12K (12288) bytes. If you request a primary ÿ or secondary PTXSIZE less than the minimum, ... (rest ÿ of paragraph is unchanged) ÿ To determine the maximum size, your primary and ÿ secondary PTXSIZE requests are first compared to ÿ 2097148K (2147479552) bytes, or 2048M minus 4K. If ÿ your request exceeds this limit, no messages are issued, ÿ but the amount of the PTXSIZE request is reduced to the ÿ limit. The recommended value for the primary or ÿ secondary PTXSIZE, which is included in message ÿ AIOxxx200I, conforms to this limit. ÿ Your primary PTXSIZE request is then compared to the ÿ system maximum for virtual storage above 16M. This ÿ maximum is the system GETMAIN limit, reduced by 512K ÿ to allow for PPMP and PL/I storage requirements, and ÿ rounded to the next lower multiple of 4K. If you request ÿ a primary PTXSIZE greater than the maximum, message ÿ AIOxxx201W is issued to indicate that the upper limit ÿ has been exceeded and that the requested primary PTXSIZE ÿ has been adjusted to conform to the maximum allowed. ÿ When the maximum amount is substituted for the primary ÿ PTXSIZE, message AIOxxx206W is also issued, indicating ÿ that no secondary data areas will be allocated since the ÿ primary area will use all of the available space. This ÿ message will also be issued if the space remaining after ÿ the allocation of the primary data area will be less than ÿ 12K (12288) bytes. ÿ If the primary PTXSIZE request was less than the ÿ maximum allowed and at least 12K (12288) bytes will be ÿ available after the primary area has been allocated, ÿ the secondary PTXSIZE request is compared to the system ÿ maximum, as described above, minus the size of the ÿ primary area minus the recommended HEAP margin (512K ÿ for RFT and 256K for DSC). If you request a secondary ÿ PTXSIZE greater than this maximum, message AIOxxx200W is ÿ issued to indicate that the upper limit has been ÿ exceeded and that the requested secondary PTXSIZE has ÿ been adjusted to conform to the maximum allowed. ÿ If you do not specifically request a secondary PTXSIZE, ÿ the default size is compared to the amount of storage that ÿ will be available after the primary area is allocated. If ÿ the space that will be available is at least 12K (12288) ÿ bytes but is smaller than the default secondary PTXSIZE, ÿ the default is reduced so that at least one secondary data ÿ area can be allocated, and PTXMAXAREAS is reduced ÿ accordingly. If the space remaining after the primary ÿ area is allocated will be less than 12K (12288) bytes, ÿ PTXMAXAREAS is reduced to one and no secondary areas will ÿ be allocated. Since the default size is being changed, ÿ rather than a size you requested, no message will be ÿ issued in either case. However, the listing of the ÿ options in effect will reflect the secondary PTXSIZE and ÿ the PTXMAXAREAS values actually used. ÿ On page 100, under Using the HEAP Parameter, change the ÿ wording to read as follows: ÿ (first sentence unchanged) ... The effect of HEAP, as ÿ illustrated here, is to allocate the data areas defined by ÿ PTXSIZE and other storage needed by PPMP programs above ÿ 16M. The combination of large data areas and the use of ÿ extended virtual storage can result in dramatic ÿ improvements in PPMP performance....(rest of paragraph ÿ unchanged) ÿ On page 100, after Figure 50, change the wording to read as ÿ follows: ÿ (first 2 sentences unchanged) ... The initial HEAP value ÿ should be about 512K larger than the primary PTXSIZE for ÿ ÿ Appendix D. Cover Letter Data 58 ¯ ÿ ÿ AIOARFT, or 256K larger for AIOBDSC, whether the default ÿ or user-requested PTXSIZE is used. The HEAP increment ÿ value should be at least the same as the secondary ÿ PTXSIZE. The 512K/256K margins are not required for ÿ secondary PTXSIZE and HEAP increment. ÿ On page 103, after Figure 53, change the third bullet to ÿ read: ÿ . (first 2 sentences unchanged) ... If the initial HEAP ÿ value is sufficiently large, you should be able to ÿ minimize the number of HEAP requests, even if secondary ÿ data areas are used. This should shorten execution ÿ time....(rest of paragraph unchanged) ÿ * ÿ * Changes to the messages in Appendix E: ÿ * ÿ On page 273, change the text and explanation of AIOxxx200I: ÿ AIOxxx200I For form formname, AIOARFT wrote n bytes to ÿ temporary dataset SYSUT1. To avoid I/O to ÿ SYSUT1, a primary PTXSIZE of at least ptxsizeK ÿ bytes is required, with a suggested initial ÿ HEAP value of at least heapsizeK. ÿ Explanation: (first 2 sentences unchanged)... Specify a ÿ primary PTXSIZE of ptxsizeK, and an initial ÿ HEAP of heapsize K and rerun the job...(rest ÿ of paragraph unchanged) ÿ On pages 273-274, change the text and explanation of ÿ AIOxxx201W: ÿ AIOxxx201W The minimum » maximum PTXSIZE value of n bytes ÿ has been substituted for the requested primary » ÿ secondary amount, which was too small » large. ÿ Explanation: A PTXSIZE request was too small (less than 12K) ÿ or too large ... (rest of paragraph unchanged) ÿ On page 274, add the text and explanation of AIOxxx205I: ÿ AIOxxx205I For form formname, AIOARFT allocated n1 primary ÿ and n2 secondary intermediate format data areas. ÿ To optimize performance, a primary PTXSIZE of ÿ at least ptxsizeK bytes is required, with a ÿ suggested initial HEAP value of at least ÿ heapsizeK. ÿ Explanation: While reformatting Xerox form formname, AIOARFT ÿ required more intermediate format data storage ÿ than was available in the primary area, and ÿ allocated n2 additional areas. This may have ÿ increased execution time by requiring several ÿ HEAP requests to get system storage. Specify ÿ a primary PTXSIZE of ptxsizeK, and an initial ÿ HEAP of heapsizeK and rerun the job. To ÿ determine the optimum PTXSIZE and HEAP for your ÿ environment, see "Performance and Tuning" on ÿ page 99. ÿ On page 274, add the text and explanation of AIOxxx206W: ÿ AIOxxx206W The primary intermediate format data area will ÿ use all of the available storage. No secondary ÿ areas will be allocated. ÿ Explanation: AIOARFT has calculated that there will not be ÿ enough virtual storage to allocate any ÿ secondary intermediate format data areas. ÿ Either the requested primary PTXSIZE was too ÿ large and has been replaced by the system ÿ maximum size, or less than 12K will be ÿ available after the primary area has been ÿ allocated. If the primary area is filled, any ÿ additional data will be written to SYSUT1, ÿ which may adversely affect execution time. ÿ Coding REGION=0M may allow your job to access a ÿ larger amount of virtual storage and avoid this ÿ situation. ÿ On page 283, add the text and explanation of AIOxxx480E, ÿ exactly as it now appears on page 287, leaving the entry on ÿ page 287 unchanged. ÿ On page 283, add the text and explanation of AIOxxx482E, ÿ exactly as it now appears on page 288, leaving the entry on ÿ page 288 unchanged. ÿ On page 285, change the text and explanation of AIOxxx200I: ÿ AIOxxx200I AIOBDSC wrote n bytes to temporary dataset ÿ ÿ Appendix D. Cover Letter Data 59 ¯ ÿ ÿ SYSUT1. To avoid I/O to SYSUT1, a primary ÿ PTXSIZE of at least ptxsizeK bytes is required, ÿ with a suggested initial HEAP value of at least ÿ heapsizeK. ÿ Explanation: (first 2 sentences unchanged)... Specify a ÿ primary PTXSIZE of ptxsizeK, and an initial ÿ HEAP of heapsize K and rerun the job...(rest ÿ of paragraph unchanged) ÿ On page 285, change the text and explanation of AIOxxx201W: ÿ AIOxxx201W The minimum » maximum PTXSIZE value of n bytes ÿ has been substituted for the requested primary » ÿ secondary amount, which was too small » large. ÿ Explanation: A PTXSIZE request was too small (less than 12K) ÿ or too large ... (rest of paragraph unchanged) ÿ On page 286, add the text and explanation of AIOxxx205I: ÿ AIOxxx205I AIOBDSC allocated n1 primary and n2 secondary ÿ intermediate format data areas. To optimize ÿ performance, a primary PTXSIZE of at least ÿ ptxsizeK bytes is required, with a suggested ÿ initial HEAP value of at least heapsizeK. ÿ Explanation: While converting the XRXIN data stream, AIOBDSC ÿ required more intermediate format data storage ÿ than was available in the primary area, and ÿ allocated n2 additional areas. This may have ÿ increased execution time by requiring several ÿ HEAP requests to get system storage. Specify ÿ a primary PTXSIZE of ptxsizeK, and an initial ÿ HEAP of heapsizeK and rerun the job. To ÿ determine the optimum PTXSIZE and HEAP for your ÿ environment, see "Performance and Tuning" on ÿ page 99. ÿ On page 286, add the text and explanation of AIOxxx206W: ÿ AIOxxx206W The primary intermediate format data area will ÿ use all of the available storage. No secondary ÿ areas will be allocated. ÿ Explanation: AIOBDSC has calculated that there will not be ÿ enough virtual storage to allocate any ÿ secondary intermediate format data areas. ÿ Either the requested primary PTXSIZE was too ÿ large and has been replaced by the system ÿ maximum size, or less than 12K will be ÿ available after the primary area has been ÿ allocated. If the primary area is filled, any ÿ additional data will be written to SYSUT1, ÿ which may adversely affect execution time. ÿ Coding REGION=0M may allow your job to access a ÿ larger amount of virtual storage and avoid this ÿ situation. ÿ DOCUMENTATION: ÿ Instructions for handling images merged inline with XICS ÿ metacode output. ÿ If you are using the Xerox Integrated Composition System ÿ (XICS), you may have additional graphic image resources which ÿ are stored in one or more XICS DCLIB data sets and then merged ÿ into the XICS metacode output using the IMG command. ÿ These images should be copied to a Xerox LPS format tape ÿ using the SPOL option of the XICS DOCUTL program. The images ÿ will be copied to the tape in the Interpress (.IMG) format. ÿ They can then be copied into the XRSPDS data set and ÿ reformatted by the RFT program. ÿ After the images have been converted to page segments using ÿ the methods described in chapter 7 of the Page Printer Migration ÿ Programming Guide or other tools that may be available to you, ÿ you should create an entry for each image in the Correlation ÿ Source file and run the RFT program to create or update the ÿ Image Correlation Table. ÿ When these steps are complete, the DSC program will be able ÿ to correctly interpret GRAPHIC DJDEs within your XICS metacode ÿ output by invoking the correct AFP page segment and ignoring ÿ the inline image records that follow the GRAPHIC DJDE. ÿ * ÿ * Documentation changes for OW18513 ÿ * ÿ * ÿ * Changes to Chapter 3: ÿ ÿ Appendix D. Cover Letter Data 60 ¯ ÿ ÿ * ÿ On page 65, add the following to the end of the Xerox ÿ Resources discussion: ÿ If you are using the Xerox Integrated Composition System ÿ (XICS), you may have additional graphic image resources ÿ which are stored in one or more XICS DCLIB data sets and ÿ then merged into the XICS metacode output using the IMG ÿ command. These images should be copied to a Xerox LPS ÿ format tape using the SPOL option of the XICS DOCUTL ÿ program. The images will be copied to the tape in the ÿ Interpress (.IMG) format. They can then be copied into ÿ the XRSPDS data set and reformatted by the RFT program. ÿ On page 65 under Xerox Resources, the second RFT program ÿ input format is Host-based PDS, but the bulleted paragraph ÿ for Host-based PDS is incorrectly located at the bottom ÿ of the page. This paragraph should precede the Correlation ÿ Source File section and follow the material on Xerox-format ÿ tape. ÿ * ÿ * Changes to Chapter 7: ÿ * ÿ On page 215, after the paragraph beginning "In the Xerox ÿ LPS environment, graphic images can be stored..." add a ÿ new paragraph: ÿ The Xerox Integrated Composition System (XICS) can also ÿ store graphic images in DCLIB data sets. The XICS IMG ÿ command can then be coded so that the images are merged ÿ inline with the XICS metacode output. ÿ ACTION: ÿ IF USING SMP/E RELEASE 7 OR LOWER, RUN THE AIOLNKED JOB AFTER ÿ APPLYING THIS PTF. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ Instructions for using new and changed performance parameters. ÿ In order to permit greater flexibility in PPMP performance ÿ and tuning, the existing PTXSIZE parameter has been enhanced ÿ and a new PTXMAXAREAS parameter has been added. ÿ First, it is now possible to request primary and ÿ secondary PTXSIZE amounts. Second, the user can now specify ÿ the maximum number of data areas to be allocated. ÿ Both of these facilities are available when running AIOBDSC and ÿ when reformatting FRM files into AFP overlays using AIOARFT. ÿ If no PTXSIZE is specified, the defaults will be used. ÿ For AIOBDSC, the default primary and secondary PTXSIZE is ÿ 832K. For AIOARFT, the default primary and secondary PTXSIZE ÿ is 52K. If a primary PTXSIZE is specified but no secondary, ÿ the default secondary is used. ÿ As far as syntax is concerned, PTXSIZE can be coded as it ÿ has been heretofore, or with only the primary PTXSIZE in ÿ parentheses, or with both primary and secondary PTXSIZE in ÿ parentheses, separated by a comma. No embedded blanks are ÿ allowed. If both primary and secondary PTXSIZEs are coded, ÿ they must be enclosed in parentheses and separated by a ÿ comma. All primary and secondary PTXSIZE requests are ÿ rounded to the next multiple of 4K. The actual size of the ÿ data area itself is reduced by the number of bytes taken up ÿ by control fields associated with the data area. Currently, ÿ 60 bytes are used for this purpose. Here are some examples ÿ of correct PTXSIZE syntax and the results: ÿ PTXSIZE=500M Primary = 500M, secondary = 832K (DSC) ÿ PTS=960K Primary = 960M, secondary = 832K (DSC) ÿ PTS=(76K) Primary = 76K, secondary = 52K (RFT) ÿ PTS=(256M,128M) Primary = 256M, secondary = 128M (DSC) ÿ The recommended relationship between the PL/I HEAP runtime ÿ parameter and the primary PTXSIZE remains the same as before ÿ (initial HEAP = primary PTXSIZE + 512K for AIOARFT or + 256K ÿ for AIOBDSC). However, no such margin is needed for the HEAP ÿ ÿ Appendix D. Cover Letter Data 61 ¯ ÿ ÿ increment. It should be at least equal to the secondary ÿ PTXSIZE, if not larger. In the examples of correct PTXSIZE ÿ syntax shown above, the recommended HEAP values would be: ÿ PTXSIZE=500M HEAP=(512256K,832K) (DSC) ÿ PTS=960K HEAP=(1216K,832K) (DSC) ÿ PTS=(76K) HEAP=(588K,52K) (RFT) ÿ PTS=(256M,128M) HEAP=(262400K,128M) (DSC) ÿ The minimum for both primary and secondary PTXSIZE is ÿ 12K. This minimum has been increased from 8K to 12K so that ÿ at least one complete AFP record can be written in even the ÿ smallest possible intermediate format data area. ÿ The total number of intermediate format data areas can be ÿ controlled as in these examples: ÿ PTXMAXAREAS=40 1 primary and 39 secondary areas ÿ PTM=5 1 primary and 4 secondary areas ÿ PPMP limits itself to the lesser of the number of areas ÿ requested by the user or the number of areas actually ÿ available, based on the PTXSIZE values in use and the system ÿ GETMAIN limit in effect. Thus a greater number of data areas ÿ is available when REGION=0M is coded than when a nonzero ÿ REGION value is specified in the JCL but the same PTXSIZE ÿ values are used. ÿ The number of areas actually available is calculated as ÿ 1 + ((GETMAIN limit - (primary PTXSIZE + margin1)) / ÿ secondary PTXSIZE) + x ÿ where margin1 is 256K for AIOBDSC and 512K for AIOARFT and x is ÿ either 1 or 0, depending on whether space would exist for a ÿ single additional area smaller than the requested secondary ÿ PTXSIZE but larger than the 12K minimum. If such an area is ÿ allocated, its actual size will be rounded down to the nearest ÿ multiple of 4K. The result of the calculation shown above is ÿ truncated into an integer. ÿ This is the default number of maximum areas that will be ÿ used if PTXMAXAREAS is not specified. The smaller of this ÿ number or the number of areas requested will appear among ÿ the options in effect (message AIOxxx226I). ÿ Beginning with this APAR, PPMP will not write intermediate ÿ format data to DASD unless either the maximum number of of data ÿ areas has been filled or no more virtual storage is available ÿ for allocating such areas. For the purposes of allocating ÿ intermediate format data areas and deciding whether to write ÿ subsequent records to SYSUT1, PPMP considers that an out of ÿ storage condition exists when it calculates that less than 12K ÿ of virtual storage is available. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOBINI OW19035 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW19035 AIOBINI ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOAJ@M ÿ AIOAJ@1 ÿ AIOAM@M ÿ ÿ Appendix D. Cover Letter Data 62 ¯ ÿ ÿ AIOAP@M ÿ AIOAP@R ÿ AIOAPMS ÿ AIOARFT ÿ AIOARPT ÿ AIOAT@M ÿ AIOAT@R ÿ AIOBADR ÿ AIOBARL ÿ AIOBDSC ÿ AIOBINI ÿ AIOBJDP ÿ AIOBMTD ÿ AIOBNDR ÿ AIOBRPT ÿ AIOBSDR ÿ AIOBTPX ÿ AIOBTXO ÿ AIOBXFN ÿ AIOBXJJ ÿ AIOCJOB ÿ AIOCMWR ÿ ÿ LISTEND ÿ */. ÿ ÿ D.8 COVER LETTER FOR PTF UW29462 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW20861 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: When reformatting OEM JDL files, * ÿ * message AIOJ@M259S is issued for a * ÿ * JDE length error. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ The JDL files in question included the OUTPUT SHIFT option ÿ and had been compiled under a version of the OEM LPS software ÿ which predated the use of xdots as a units base for SHIFT and ÿ other options. Whereas with xdots, the SHIFT values are stored ÿ as two halfwords requiring a secondary offset from the beginning ÿ of the JDE, the older software stored these values in two bytes, ÿ located where the secondary offset is currently found. AIOAJ@M ÿ interpreted the two single-byte values as a halfword offset, ÿ which then appeared to contain an invalid value. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW20861 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ User-developed carriage control tables. ÿ JDLs reformatted with this APAR fix include new fields to ÿ indicate the particular OEM or user carriage control table ÿ specified in the original JDL. A bit flag indicates whether ÿ a particular reformatted JDL has been processed with this fix, ÿ so that backward compatibility is possible with JDLs which were ÿ reformatted prior to the application of this fix. While it is ÿ recommended that all JDLs be reprocessed by AIOARFT after this ÿ fix is applied, this is not a requirement. ÿ A new AIOBDSC option has been added to facilitate use of the ÿ various carriage control types supported by OEM. The syntax of ÿ the new option is ÿ PCCTYPE=xxxx or PCC=xxxx ÿ where xxxx is one of the following values: ÿ A » ANSI ÿ M » MACHINE » IBM1403 » IBM3211 ÿ U » USER ÿ The new PCC option is implemented as follows: ÿ I. OEM online environment. ÿ A. PCC is not specified. ÿ ÿ Appendix D. Cover Letter Data 63 ¯ ÿ ÿ The default is IBM3211. This accords with the OEM ÿ expectation that, even though the host may generate ÿ some other scheme of carriage control characters, ÿ the online channel adapter in use will translate the ÿ host characters to IBM3211 controls. ÿ B. PCC is specified. ÿ The value specified will be used instead of the ÿ default. This allows the user to indicate the type ÿ of control characters actually written by the host ÿ application (e.g., ANSI). ÿ C. Reformatted JDL in use may or may not have been ÿ processed after this APAR fix was applied. ÿ Since the reformatted JDL carriage control table ÿ will always be IBM3211 in the online environment, ÿ AIOBDSC will determine whether ANSI or IBM3211 is ÿ in use independently of the reformatted JDL. To ÿ use carriage control types other than ANSI or ÿ IBM3211 in the online environment, you must code ÿ the PCCTYPE option to reflect the type actually ÿ used. ÿ II. OEM offline environment. ÿ A. Reformatted JDL in use was processed before this ÿ APAR fix was applied. ÿ 1. The user may either specify a carriage control ÿ type via the PCC option or ÿ 2. If ANSI carriage control is in use, the user ÿ may allow the OEM offline default of ANSI to ÿ take effect. ÿ B. Reformatted JDL in use was processed after this APAR ÿ fix was applied. ÿ The carriage control table already present in the ÿ reformatted JDL will be used. In this case, the ÿ specified PCC option will be ignored in favor of ÿ the values in the reformatted JDL. Reprocessing ÿ offline JDLs can help the user avoid having to ÿ specify the PCCTYPE in the AIOBDSC JCL. ÿ After AIOBDSC has determined the type of carriage control ÿ characters expected to be use, it reports the adjusted value of ÿ the PCC option. ÿ If the carriage control type expected is ANSI or ÿ IBM3211 characters are in use and the BLOCK/RECORD environment ÿ is not in effect, AIOBDSC examines up to 25 initial records of ÿ the XRXIN file to determine which type of controls are actually ÿ employed. This is necessary because (a) the only OEM option is ÿ IBM3211 but other kinds of carriage control may be generated on ÿ the host side of the channel adapter and (b) it effectively ÿ eliminates dependence on the MVS DCB RECFM parameter as an ÿ indicator of carriage control type. If AIOBDSC finds that the ÿ carriage control characters are not of the same type as those ÿ expected, a message is issued to inform the user of which ÿ control character type is actually in use: ÿ AIONDR404I The XRXIN data set will be processed using ÿ ISO/ANSI/FIPS control characters. ÿ AIONDR404I The XRXIN data set will be processed using ÿ IBM3211 (machine code) control characters. ÿ Note that this message replaces the original AIONDR404W, which ÿ was based on interpretation of the DCF RECFM JCL parameter. ÿ Although this APAR specifically addresses IBM3211, ANSI and ÿ USER carriage control schemes, preliminary testing indicates ÿ that several other OEM_supported types may be supportable by ÿ PPMP as well. These include H6000, IBM1401, US70 and XEROX. ÿ Tests with actual user data will be required to confirm that ÿ these carriage control types can be handled as thoroughly as ÿ IBM3211, ANSI and USER are at the present. ÿ Another control type, H2000, was also tested, but the test ÿ suggests that the table published in the OEM Tape Formats Manual ÿ is significantly different from the H2000 table actually stored ÿ in the printers. ÿ Finally, no attempt has been made at this time to support ÿ carriage control schemes which use more than one byte. These ÿ include B2500, B2700, B3500, B3700, B4700, B6700 and NCR. ÿ * ÿ * Documentation changes for OW19183 ÿ * ÿ * Changes to Chapter 3: ÿ ÿ Appendix D. Cover Letter Data 64 ¯ ÿ ÿ * ÿ On page 82, add the following bullet after "The DSC ÿ parameters allow you to do the following:" ÿ . Specify the type of printer carriage control characters ÿ used in the input data set ÿ On page 83, in Figure 39, add the following after PTXSIZE, ÿ using square brackets: ÿ { PCCTYPE } ÿ On page 83, in Figure 40, add the following after PTXSIZE: ÿ PCCTYPE= PCC= ÿ On page 84, after Performance Parameter, add the following: ÿ Printer Carriage Control Type Parameter ÿ The DSC program has one printer carriage control type ÿ parameter. ÿ PCCTYPE Specifies the type of control characters used ÿ in the XRXIN data set. ÿ The syntax for the PCCTYPE parameter is one of the ÿ following: ÿ . PCCTYPE=x ÿ . PCC=x ÿ where x is one of the supported carriage control ÿ character types: ÿ . A » ANSI ÿ . M » MACHINE » IBM1403 » IBM3211 ÿ . U » USER ÿ In the Xerox online environment, the host application ÿ programs may generate any one of several types of ÿ carriage control characters (such as ANSI), but the ÿ online channel adapter in use translates the host ÿ characters to IBM3211 controls. Thus, if you do not ÿ specify PCCTYPE when an online JDL/JDE is in use, the ÿ default is IBM3211. If the PCCTYPE is specified, ÿ the value you coded will be used instead of the ÿ default. This allows you to indicate the type of ÿ control characters actually written by the host ÿ application (e.g., ANSI). ÿ In the Xerox offline environment, the effect of the ÿ the PCCTYPE option depends on whether the JDL you are ÿ using was reprocessed by the RFT program after the ÿ option became available to you. If the JDL was not ÿ processed after PCCTYPE became available you may either ÿ specify a carriage control type using the PCC option or ÿ allow the Xerox offline default of ANSI to take effect. ÿ If the JDL in use was processed after PCCTYPE became ÿ available, the carriage control table already present in ÿ the reformatted offline JDL will be used. In this case, ÿ the specified PCC option will be ignored in favor of the ÿ values in the reformatted JDL. Thus, reprocessing ÿ offline JDLs can help you avoid having to specify the ÿ PCCTYPE in offline situations. ÿ Regardless of whether the online or offline environment ÿ is in effect, if IBM3211 or ANSI control characters are ÿ expected and the BLOCK/RECORD environment is not in use, ÿ the DSC will examine the XRXIN data set to determine ÿ which is actually being used. An information message, ÿ AIOxxx404I, will be issued if the XRXIN control ÿ characters are different from what the DSC program ÿ expects to find. ÿ On page 96, in Figure 48, add the following to the listed ÿ DSC options in effect in message AIODSC226I: ÿ PCCTYPE=IBM3211 ÿ * ÿ * Changes to the messages in Appendix E: ÿ * ÿ On page 287, replace the entire entry for AIOxxx404W with ÿ the following: ÿ AIOxxx404I The XRXIN data set will be processed using ÿ control_type control characters. ÿ Explanation: The DSC program examined the XRXIN data set ÿ to determine whether ANSI or IBM3211 printer carriage ÿ control characters were in use. The type of controls ÿ found was different from the type expected. ÿ Control_type is either: ÿ . ISO/ANSI/FIPS ÿ . IBM3211 (machine code) ÿ ÿ Appendix D. Cover Letter Data 65 ¯ ÿ ÿ DOCUMENTATION: ÿ Support for JDL/JDE BLOCK option ZERO=YES. ÿ When processing input datasets using the OEM BLOCK/RECORD ÿ JDL commands, AIOBDSC may have erroneously issued AIONDR404W ÿ MSGAIONDR404W with confusing wording such as the following: ÿ The type of control characters specified for the XRXIN data ÿ set (RECFM=FB) does not match the control characters found ÿ in the file. AIOBDSC will assume ISO/ANSI/FIPS control ÿ characters (RECFM=FA) instead of machine code control ÿ characters (RECFM=FB). ÿ The code changes made for this APAR will prevent AIOBNDR ÿ from issuing AIONDR404W in this fashion. If your dataset's ÿ RECFM attributes do not include specification of a carriage ÿ control type, you do not need to code one in a JCL override ÿ (e.g., DCB=RECFM=FBA or DCB=RECFM=VBM) in order to keep this ÿ message from appearing, once this PTF is applied. ÿ * ÿ * Documentation changes for OW19373 ÿ * ÿ * Changes to Chapter 3: ÿ * ÿ On page 97, in Table 6, add ZERO to the list of supported ÿ BLOCK commands. ÿ On page 98, in Table 7, remove ZERO from the list of ÿ unsupported BLOCK commands and change the superscript ÿ numbers for RECORD to 1, 2 and 4. ÿ On page 99, in the notes for Table 7, remove note number ÿ 4 for ZERO. Change the numbering of the note for RECORD ÿ STRUCTURE from 5 to 4. ÿ * ÿ * Changes to the messages in Appendix E: ÿ * ÿ On page 277, change the second sentence of the explanation ÿ for AIOXXX252W to read: ÿ The unsupported functions that may be listed are FORMAT º= ÿ BIN and LMULT º= 1. ÿ On page 292, change the first sentence of the explanation ÿ for AIOXXX775S to read: ÿ PPMP cannot process input data from XRXIN using the ÿ unsupported function FORMAT º= BIN or LMULT º= 1. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ After applying this PTF, use RFT to reformat your JDLs before ÿ running the DSC program. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOAJ@M OW20861 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW20861 AIOAJ@M ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOAJ@M ÿ AIOAJ@0 ÿ AIOAJ@2 ÿ AIOAJ@5 ÿ AIOBDSC ÿ AIOBEDR ÿ AIOBINI ÿ ÿ Appendix D. Cover Letter Data 66 ¯ ÿ ÿ AIOBJJD ÿ AIOBJRC ÿ AIOBNDR ÿ AIOBNLP ÿ AIOBOLG ÿ AIOBXJJ ÿ AIOCMWR ÿ ÿ LISTEND ÿ */. ÿ ÿ D.9 COVER LETTER FOR PTF UW30900 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW21377 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: When reformatting FRMs or * ÿ * processing input intended for OEM * ÿ * 17 x 11 inch ledger size paper, * ÿ * PPMP generates output which causes * ÿ * the printer to print PEMs down the * ÿ * middle of the paper. Data is printed * ÿ * on only one half of the page; the * ÿ * other half is blank. When printing * ÿ * folio size pages, PEMs appear across * ÿ * the bottom of the page. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ The PPMP programs do not include logic for handling the ÿ paper sizes in use here. Since the paper sizes are not ÿ recognized, AIOARFT assumes USLETTER instead and AIOBDSC writes ÿ USLETTER paper size values to the PGD structured field, ÿ resulting in the PEMs down the center of the page (ledger size) ÿ or across the bottom (folio size). ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW21377 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ New Papersizes ÿ This APAR introduces support for ledger (17 x 11 inch) and ÿ folio (8.5 x 13 inch) paper sizes, the use of which is an option ÿ on certain OEM printer models. These paper sizes are made ÿ available to PPMP users through two new AIOARFT paper size ÿ options and by expansion of the existing overlay sampling ÿ facility. ÿ The new AIOARFT options are specified as USLEDGER / USLR ÿ for ledger size or as FOLIO/FO for folio size. Specifying ÿ these options when JDLs are reformatted causes the appropriate ÿ paper dimensions to be used as the defaults for each JDE. When ÿ FRMs are being converted to overlays, USLR causes the 17 x 11 ÿ dimensions to be included in overlays created from FRMs which ÿ have no internal PAPERSIZE values and FO causes the 8.5 x 13 ÿ dimensions to be used. ÿ When sampling 17 x 11 overlays using the OVS / OVSA options, ÿ a new DDNAME, OVSMPLR, is required. The DDNAME for sampling ÿ folio size overlays is OVSMPFO. Message AIOxxx265I informs ÿ the user of how many and which overlays were sampled to the ÿ OVSMPLR and/or OFSMPFO data sets. ÿ * ÿ * Documentation changes for OW21377 ÿ * ÿ * Additions and changes to Chapter 3 ÿ * ÿ On page 43, in Figure 16, add the following after the ÿ entries for USLEGAL, in the same format: ÿ USLEDGER USLR ÿ FOLIO FO ÿ On page 47, under Paper Size Parameters, change the first ÿ sentence to read: ÿ ÿ Appendix D. Cover Letter Data 67 ¯ ÿ ÿ The RFT program has five paper size parameters: ÿ On page 47, under Paper Size Parameters, after the entry ÿ for USLEGAL, add: ÿ USLEDGER This parameter specifies that the RFT program ÿ should assume a paper size of 17.0 x 11.0 ÿ inches. ÿ FOLIO This parameter specifies that the RFT program ÿ should assume a paper size of 8.5 x 13.0 ÿ inches. ÿ On page 52, continuing Other Control Statements from page ÿ 51, after the OVSMPLG entry, add an entry for: ÿ OVSMPLR Specifies the name of the AFP output data set ÿ containing copies of the overlays reformatted by ÿ the RFT program from Xerox forms using USLEDGER ÿ paper size. Use the OVSMPLR DD name when you ÿ select the OVSAMPLE option to enable overlay ÿ sampling. OVSMPLR is not required unless the ÿ OVSAMPLE option is selected and USLEDGER paper size ÿ forms are being converted. ÿ OVSMPFO Specifies the name of the AFP output data set ÿ containing copies of the overlays reformatted by ÿ the RFT program from Xerox forms using FOLIO ÿ paper size. Use the OVSMPFO DD name when you ÿ select the OVSAMPLE option to enable overlay ÿ sampling. OVSMPFO is not required unless the ÿ OVSAMPLE option is selected and FOLIO paper size ÿ forms are being converted. ÿ On page 54, continuing Usage Notes, in the paragraph which ÿ begins "When overlay sampling is selected...", change all ÿ occurrences of ÿ OVSMPLT, OVSMPLG and/or OVSMPA4 ÿ to ÿ OVSMPLT, OVSMPLG, OVSMPLR, OVSMPFO and/or OVSMPA4 ÿ On page 59 in Figure 22, change the OVSMPxx DD statements ÿ to read: ÿ //OVSMPLT DD DSN=dsn9,DISP=SHR ÿ //OVSMPLG DD DSN=dsn10,DISP=SHR ÿ //OVSMPA4 DD DSN=dsn11,DISP=SHR ÿ //OVSMPLR DD DSN=dsn12,DISP=SHR ÿ //OVSMPFO DD DSN=dsn13,DISP=SHR ÿ On page 60 in the explanation for Figure 22, add entries ÿ dsn12 and dsn13: ÿ dsn12 Identifies the name of the AFP output data set for ÿ printing copies of the overlays converted from ÿ USLEDGER size Xerox FRM files. ÿ dsn13 Identifies the name of the AFP output data set for ÿ printing copies of the overlays converted from ÿ FOLIO size Xerox FRM files. ÿ On page 79, in the AFP Overlay Samples section, change the ÿ last sentence to read: ÿ These data streams will be written to the SYSOUT class ÿ or file you specify in the OVSMPLT, OVSMPLG, OVSMPLR, ÿ OVSMPFO or OVSMPA4 DD statement. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOAJ@M OW21377 ÿ AIOAJ@1 OW21377 ÿ AIOAJ@5 OW21377 ÿ AIOAM@M OW21377 ÿ AIOAPMS OW21377 ÿ AIOARFT OW21377 ÿ AIOARPT OW21377 ÿ AIOBADR OW21377 ÿ AIOBAMD OW21377 ÿ AIOBARL OW21377 ÿ AIOBINI OW21377 ÿ ÿ Appendix D. Cover Letter Data 68 ¯ ÿ ÿ AIOBJPG OW21377 ÿ AIOBMTD OW21377 ÿ AIOBXJJ OW21377 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW21377 AIOAJ@M AIOAJ@1 AIOAJ@5 AIOAM@M AIOAPMS AIOARFT ÿ AIOARPT AIOBADR AIOBAMD AIOBARL AIOBINI AIOBJPG ÿ AIOBMTD AIOBXJJ ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOAJ@M ÿ AIOAJ@1 ÿ AIOAJ@5 ÿ AIOAM@M ÿ AIOAPMS ÿ AIOARFT ÿ AIOARPT ÿ AIOBADR ÿ AIOBAMD ÿ AIOBARL ÿ AIOBINI ÿ AIOBJPG ÿ AIOBMTD ÿ AIOBXJJ ÿ ÿ LISTEND ÿ */. ÿ ÿ D.10 COVER LETTER FOR PTF UW42243 ÿ ÿ PROBLEM DESCRIPTION(S): ÿ OW29261 - ÿ **************************************************************** ÿ * USERS AFFECTED: ALL USERS OF PPMP * ÿ **************************************************************** ÿ * PROBLEM DESCRIPTION: When AIOBDSC encounters an empty * ÿ * XRXIN input file, MSGAIONDR621S * ÿ * is issued and the program ends with * ÿ * CC12. Attempts to print * ÿ * the resulting AFP files cause PSF error * ÿ * MSGAPS251I. * ÿ **************************************************************** ÿ * RECOMMENDATION: Apply the applicable PTF. * ÿ **************************************************************** ÿ In some environments, applications that create input to ÿ AIOBDSC may generate empty XRXIN files. If a great many of ÿ these occur in a nightly production cycle, the condition codes ÿ of 12 that result are indistinguishable from other problems ÿ that may be more significant. ÿ ÿ When the AFP files resulting from such jobs are printed, ÿ PSF issues APS251I because the skeletal inline FORMDEF does ÿ not include any medium maps. ÿ COMPONENT: 5695-04001-HPRF224 ÿ APARS FIXED: OW29261 ÿ SPECIAL CONDITIONS: ÿ COPYRIGHT: 5695-04001 (C) COPYRIGHT IBM CORP. 1994 ÿ LICENSED MATERIAL - PROGRAM PROPERTY OF IBM ÿ DOCUMENTATION: ÿ New Parameter: NULLXRXIN, new messages ÿ Application of this APAR fix allows AIOBDSC to handle empty ÿ XRXIN input files more gracefully. When the new parameter ÿ NULLXRXIN (abbrev. NLX) is selected and the XRXIN file is empty, ÿ a new message, AIONDR622W is issued and AIOBDSC ends with a ÿ condition code of at least 4. If NONULLXRXIN (abbrev. NONLX) ÿ is selected and the input is empty, AIOBDSC behaves as it has ÿ previously: AIONDR621S is issued and the program ends with a ÿ condition code of at least 12. ÿ * ÿ * Documentation changes for OW29261 ÿ * ÿ * Changes to Chapter 3 ÿ ÿ Appendix D. Cover Letter Data 69 ¯ ÿ ÿ * ÿ On page 83 in Figure 39, add these parameters, retaining ÿ alphabetical order, with NONULLXRXIN underlined: ÿ NONULLXRXIN | NULLXRXIN ÿ On page 83 in Figure 40, add these abbreviations at the end ÿ of the list: ÿ NULLXRXIN NLX ÿ NONULLXRXIN NONLX ÿ On pages 86, after the Performance Parameter section, add ÿ the following: ÿ NULL INPUT PARAMETER ÿ The DSC program has two parameters that determine how ÿ empty XRXIN input files are to be handled: ÿ NULLXRXIN Specifies that DSC should only issue a warning ÿ message (AIONDR622W) when empty input is ÿ encountered, and end with a condition code of ÿ at least 4. ÿ NONULLXRXIN Specifies that DSC should issue a serious ÿ error message (AIONDR621S) when empty input ÿ is encountered, and end with a condition code ÿ of at least 12. This is the default. ÿ * ÿ * Changes to the Messages ÿ * ÿ On page 290, change the entry for AIOxxx621S: ÿ AIOxxx621S The XRXIN input file is empty. No printable ÿ AFP output could be produced. ÿ Explanation: No input data was found in the XRXIN data set ÿ and the NONULLXRXIN parameter was in effect. ÿ Although a minimal AFP output file may be ÿ produced to prevent PSF errors, it will contain ÿ no printable data. Ensure that the proper data ÿ set name has been specified and that the data ÿ set contains valid input. ÿ On page 290, add an entry for AIOxxx622W: ÿ AIOxxx622W The XRXIN input file is empty. No printable ÿ AFP output will be produced. ÿ Explanation: No input data was found in the XRXIN data set ÿ and the NULLXRXIN parameter was in effect. ÿ Although a minimal AFP output file may be ÿ produced, it will contain no printable data. ÿ Ensure that the proper data set name has been ÿ specified and that the data set contains valid ÿ input. ÿ ACTION: ÿ IF USING SMP/E VERSION 7 OR LOWER, ÿ AFTER APPLYING THIS PTF, RUN THE AIOLNKED JOB FROM PPMSAMP. ÿ COMMENTS: ÿ CROSS REFERENCE-MODULE/MACRO NAMES TO APARS ÿ AIOBAMD OW29261 ÿ AIOBDSC OW29261 ÿ AIOBINI OW29261 ÿ AIOBNDR OW29261 ÿ AIOCMWR OW29261 ÿ ÿ CROSS REFERENCE-APARS TO MODULE/MACRO NAMES ÿ OW29261 AIOBAMD AIOBDSC AIOBINI AIOBNDR AIOCMWR ÿ ÿ THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF: ÿ ÿ MODULES ÿ AIOBAMD ÿ AIOBDSC ÿ AIOBINI ÿ AIOBNDR ÿ AIOCMWR ÿ ÿ LISTEND ÿ */. ÿ ÿ ÿ ÿ Appendix D. Cover Letter Data 70 ¯ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ 71 ¯ ÿ ÿ READER'S COMMENTS ÿ ÿ ÿ PROGRAM DIRECTORY FOR PPMP 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 » » » » » » » ÿ ¨ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ] ÿ ¨ ¨ ¨ ¨ ¨ ¨ ÿ ÿ Did you order this product as part of a package, or as an independent ÿ product? ÿ ÿ __ CBIPO ÿ __ 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 ÿ ÿ ÿ (C) Copyright IBM Corp. 1989, 1998 72 ¯ ÿ ÿ If yes, how many years? __ ÿ ÿ If you have any comments to make about your ratings above, or any ÿ other aspect of the product installation, please list them below: ÿ ÿ ____________________________________________________________ ÿ ÿ ____________________________________________________________ ÿ ÿ ____________________________________________________________ ÿ ÿ ____________________________________________________________ ÿ ÿ ____________________________________________________________ ÿ ÿ ____________________________________________________________ ÿ ÿ ____________________________________________________________ ÿ ÿ ____________________________________________________________ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Reader's Comments 73 ¯ ÿ ÿ 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 Page Printer Migration Programs Development ÿ group): ÿ ÿ IBM Printing Systems Company ÿ Box 1900 ÿ Boulder, Colorado 80301-9191 ÿ Attention: Dept. RJXA/003G ÿ FAX Number: (800) 524-1519 ÿ E-Mail: printpubs@us.ibm.com ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ Reader's Comments 74 ¯ ÿ ÿ IBM ÿ ÿ ÿ Program Number: 5695-040 6022 ÿ 6023 ÿ 5395 ÿ ÿ Printed in U.S.A.