DOCSLIB.ORG

Infoprint Transforms to AFP for Z/OS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Infoprint Transforms to AFP for Z/OS IBM Version 2 Release 4 Infoprint Transforms to AFP for z/OS IBM G550-0443-06 Note Before using this information and the product it supports, read the information in “Notices” on page 133. This edition applies to Version 2 Release 4 of IBM® Infoprint Transforms to AFP for z/OS® (program number 5655–N60) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces G550–0443–05. © Copyright International Business Machines Corporation 2005, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................ vii Tables.................................................................................................................. ix About this publication...........................................................................................xi Who should read this publication............................................................................................................... xi How to read syntax diagrams......................................................................................................................xi Where to find more information.................................................................................................................xii Preventive Service Planning information............................................................................................. xii Related documentation........................................................................................................................ xii How to send your comments to IBM......................................................................xv If you have a technical problem.................................................................................................................xv Summary of changes..........................................................................................xvii Chapter 1. Introduction......................................................................................... 1 What is new in Version 2 Release 4.............................................................................................................1 What is new in Version 2 Release 3.............................................................................................................1 Transform names and levels........................................................................................................................2 Using transforms with Infoprint Server.......................................................................................................3 Printing web documents on AFP printers.............................................................................................. 3 Printing PDF documents on AFP printers.............................................................................................. 3 Printing SAP R/3 documents on AFP printers........................................................................................4 Methods for transforming documents.........................................................................................................5 Specifying transform options.......................................................................................................................6 Software requirements................................................................................................................................ 6 Performance considerations........................................................................................................................6 PCL to AFP transform...................................................................................................................................7 Supported fonts......................................................................................................................................7 PCL to AFP transform limitations........................................................................................................... 7 PDF to AFP transform.................................................................................................................................. 7 Supported fonts......................................................................................................................................8 PDF to AFP transform limitations...........................................................................................................8 PostScript to AFP transform........................................................................................................................ 8 Supported fonts......................................................................................................................................9 PostScript to AFP transform limitations................................................................................................ 9 SAP to AFP transform...................................................................................................................................9 Supported fonts....................................................................................................................................10 Supported input code pages................................................................................................................ 10 OTF BX command support................................................................................................................... 10 SAP to AFP transform limitations........................................................................................................ 10 Chapter 2. Using transforms.................................................................................11 pcl2afp—Transform PCL data to AFP data................................................................................................ 11 Format.................................................................................................................................................. 11 Description........................................................................................................................................... 11 Options................................................................................................................................................. 11 Operand................................................................................................................................................ 18 iii Usage notes.......................................................................................................................................... 18 Examples -- pcl2afp............................................................................................................................. 19 Environment variables..........................................................................................................................20 Files.......................................................................................................................................................20 Exit values.............................................................................................................................................21 pdf2afp—Transform PDF data to AFP data................................................................................................21 Format.................................................................................................................................................. 21 Description........................................................................................................................................... 21 Options................................................................................................................................................. 21 Operand................................................................................................................................................ 28 Usage notes.......................................................................................................................................... 28 Examples -- pdf2afp.............................................................................................................................28 Environment variables..........................................................................................................................29 Files.......................................................................................................................................................30 Exit values.............................................................................................................................................30 ps2afp—Transform PostScript data to AFP data.......................................................................................30 Format.................................................................................................................................................. 30 Description........................................................................................................................................... 30 Options................................................................................................................................................. 30 Operand...............................................................................................................................................
Load more

Recommended publications
  • MS Hatch-Waxman PTE REQUEST for EXTENSION of PATENT
    Docket No.: 029420.0155-US02 (PATENT) IN THE UNITED STATES PATENT AND TRADEMARK OFFICE In re United States Patent of: Alan J. Korman, et aL. Patent No.: 7,605,238 Issued: October 20, 2009 For: HUMAN CTLA-4 ANTIBODIES MS Hatch-Waxman PTE Commissioner for Patents Offce of Patent Legal Administration Room MDW 7D55 600 Dulany Street (Madison Building) Alexandria, VA 223 14 REQUEST FOR EXTENSION OF PATENT TERM UNDER 35 U.S.C. §156 Sir: Pursuant to 35 U.S.C. §156 and 37 C.F.R. §§1.710-1.791, Medarex, Inc., the current address of which is Route 206 and Province Line Road, Princeton, New Jersey 08540 ("Applicant" or "Medarex"), hereby requests an extension of U.S. Patent No. 7,605,238 (the "'238 patent"). As permitted by 37 C.F.R. §1.785(b) and MPEP §2761, Applicant is concurrently fiing a request for patent term extension of U.S. Patent No. 6,984,720 based upon the same regulatory review period. Medarex represents that it is the owner and assignee of the entire interest in and to Letters Patent of the United States No. 7,605,238 (Exhibit 1) granted to Alan J. Korman, Edward L. Halk, Nils Lonberg, Yashwant M. Deo and Tibor P. Keler (the "inventors") on October 20, 2009, for "Human CTLA-4 Antibodies and Their Uses" by virtue of an assignment from the DC; 3983891.1 Patent No.: 7,605,238 - 2- Docket No.: 029420.0155-US02 Alan J. Korman, Edward L. Halk and Nils Lonberg to Medarex, recorded in the United States Patent and Trademark Offce ("PTO") on March 6, 2003 at Reel 013817, Frame 0628 and an assignment from Yashwant M.
    [Show full text]
  • B2bi 2.5 Support Reference Catalog 3 Accessibility
    B2Bi Version 2.5 April 2019 Support Reference Catalog Copyright © 2019 Axway All rights reserved. This documentation describes the following Axway software: Axway B2Bi 2.5 No part of this publication may be reproduced, transmitted, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of the copyright owner, Axway. This document, provided for informational purposes only, may be subject to significant modification. The descriptions and information in this document may not necessarily accurately represent or reflect the current or planned functions of this product. Axway may change this publication, the product described herein, or both. These changes will be incorporated in new versions of this document. Axway does not warrant that this document is error free. Axway recognizes the rights of the holders of all trademarks used in its publications. The documentation may provide hyperlinks to third-party web sites or access to third-party content. Links and access to these sites are provided for your convenience only. Axway does not control, endorse or guarantee content found in such sites. Axway is not responsible for any content, associated links, resources or services associated with a third-party site. Axway shall not be liable for any loss or damage of any sort associated with your use of third-party content. Contents Accessibility 4 Accessibility features of B2Bi 4 Keyboard
    [Show full text]
  • Cloud Fonts in Microsoft Office
    APRIL 2019 Guide to Cloud Fonts in Microsoft® Office 365® Cloud fonts are available to Office 365 subscribers on all platforms and devices. Documents that use cloud fonts will render correctly in Office 2019. Embed cloud fonts for use with older versions of Office. Reference article from Microsoft: Cloud fonts in Office DESIGN TO PRESENT Terberg Design, LLC Index MICROSOFT OFFICE CLOUD FONTS A B C D E Legend: Good choice for theme body fonts F G H I J Okay choice for theme body fonts Includes serif typefaces, K L M N O non-lining figures, and those missing italic and/or bold styles P R S T U Present with most older versions of Office, embedding not required V W Symbol fonts Language-specific fonts MICROSOFT OFFICE CLOUD FONTS Abadi NEW ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 01234567890 Abadi Extra Light ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 01234567890 Note: No italic or bold styles provided. Agency FB MICROSOFT OFFICE CLOUD FONTS ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 01234567890 Agency FB Bold ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 01234567890 Note: No italic style provided Algerian MICROSOFT OFFICE CLOUD FONTS ABCDEFGHIJKLMNOPQRSTUVWXYZ 01234567890 Note: Uppercase only. No other styles provided. Arial MICROSOFT OFFICE CLOUD FONTS ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 01234567890 Arial Italic ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 01234567890 Arial Bold ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 01234567890 Arial Bold Italic ABCDEFGHIJKLMNOPQRSTUVWXYZ
    [Show full text]
  • Advanced Printer Driver Ver.4.13
    Advanced Printer Driver for South Asia Ver.4 TM Printer Manual APD Overview Descriptions of the APD features. Using the APD Descriptions of simple printings and useful functions. Reference Descriptions of property seings of the printer driver. TM Flash Logo Setup Utility Ver.3 Descriptions of how to set and use the TM Flash Logo Setup Utility Ver3. Restrictions Descriptions of restrictions on use of the APD. Printer Specification Descriptions of the specifications of TM-T81. M00024103-2 Rev. D Cautions • No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Seiko Epson Corporation. • The contents of this document are subject to change without notice. Please contact us for the latest information. • While every precaution has taken in the preparation of this document, Seiko Epson Corporation assumes no responsibility for errors or omissions. • Neither is any liability assumed for damages resulting from the use of the information contained herein. • Neither Seiko Epson Corporation nor its affiliates shall be liable to the purchaser of this product or third parties for damages, losses, costs, or expenses incurred by the purchaser or third parties as a result of: accident, misuse, or abuse of this product or unauthorized modifications, repairs, or alterations to this product, or (excluding the U.S.) failure to strictly comply with Seiko Epson Corporation’s operating and maintenance instructions. • Seiko Epson Corporation shall not be liable against any damages or problems arising from the use of any options or any consumable products other than those designated as Original EPSON Products or EPSON Approved Products by Seiko Epson Corporation.
    [Show full text]
  • The File Cmfonts.Fdd for Use with Latex2ε
    The file cmfonts.fdd for use with LATEX 2".∗ Frank Mittelbach Rainer Sch¨opf 2019/12/16 This file is maintained byA theLTEX Project team. Bug reports can be opened (category latex) at https://latex-project.org/bugs.html. 1 Introduction This file contains the external font information needed to load the Computer Modern fonts designed by Don Knuth and distributed with TEX. From this file all .fd files (font definition files) for the Computer Modern fonts, both with old encoding (OT1) and Cork encoding (T1) are generated. The Cork encoded fonts are known under the name ec fonts. 2 Customization If you plan to install the AMS font package or if you have it already installed, please note that within this package there are additional sizes of the Computer Modern symbol and math italic fonts. With the release of LATEX 2", these AMS `extracm' fonts have been included in the LATEX font set. Therefore, the math .fd files produced here assume the presence of these AMS extensions. For text fonts in T1 encoding, the directive new selects the new (version 1.2) DC fonts. For the text fonts in OT1 and U encoding, the optional docstrip directive ori selects a conservatively generated set of font definition files, which means that only the basic font sizes coming with an old LATEX 2.09 installation are included into the \DeclareFontShape commands. However, on many installations, people have added missing sizes by scaling up or down available Metafont sources. For example, the Computer Modern Roman italic font cmti is only available in the sizes 7, 8, 9, and 10pt.
    [Show full text]
  • Oracle® Database Installation Guide
    Oracle® Database Installation Guide 18c for Microsoft Windows E83888-01 August 2018 Oracle Database Installation Guide, 18c for Microsoft Windows E83888-01 Copyright © 1996, 2018, Oracle and/or its affiliates. All rights reserved. Primary Authors: Tanaya Bhattacharjee, Sunil Surabhi Contributing Authors: Prakash Jashnani, Mark Bauer, Bharathi Jayathirtha Contributors: Barb Glover, Eric Belden, Sudip Datta, David Friedman, Alex Keh, Peter LaQuerre, Rich Long, Matt McKerley, Sham Rao Pavan, Hanlin Qian, Sujatha Tolstoy, Sergiusz Wolicki, Sue Mavris, Mohammed Shahnawaz Quadri, Vishal Saxena, Krishna Itikarlapall, , Santanu Datta, Christian Shay, Aneesh Khanderwal, Michael Coulter, Robert Achacoso, Malai Stalin, David Price, Ramesh Chakravarthula This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S.
    [Show full text]
  • 1 Warum Hassen Alle Comic Sans?
    Preprint von: Meletis, Dimitrios. 2020. Warum hassen alle Comic Sans? Metapragmatische Onlinediskurse zu einer typographischen Hassliebe. In Jannis Androutsopoulos/Florian Busch (eds.), Register des Graphischen: Variation, Praktiken, Reflexion, 253-284. Boston, Berlin: De Gruyter. DOI: 10.1515/9783110673241-010. Warum hassen alle Comic Sans? Metapragmatische Onlinediskurse zu einer typographischen Hassliebe Dimitrios Meletis Karl-Franzens-Universität Graz 1. Einleitung If you love it, you don’t know much about typography, and if you hate Com- ic Sans you don’t know very much about typography either, and you should probably get another hobby. Vincent Connare, Designer von Comic Sans1 Spätestens ab dem Zeitpunkt, als mit dem Aufkommen des PCs einer breiten Masse die Möglichkeit geboten wurde, Schriftprodukte mithilfe von vorinstallierten Schriftbear- beitungsprogrammen und darin angebotenen Schriftarten nach Belieben selbst zu gestal- ten, wurde – oftmals unbewusst – mit vielen (vor allem impliziten) Konventionen ge- brochen. Comic Sans kann in diesem Kontext als Paradebeispiel gelten: Die 1994 ent- worfene Type (in Folge simplifiziert: Schriftart, Schrift) wird im Internet vor allem auf- grund von Verwendungen in dafür als unpassend empfundenen Situationen von vielen leidenschaftlich ‚gehasst‘. So existiert(e) unter anderem ein Manifest, das ein Verbot der Schrift fordert(e) (bancomicsans.com).2 Personen, die die „Schauder-Schrift“ (Lischka 2008) „falsch“ verwenden, werden als Comic Sans Criminals bezeichnet und ihnen wird Hilfe angeboten,
    [Show full text]
  • Latex2ε Font Selection
    LATEX 2" font selection c Copyright 1995{2000, LATEX3 Project Team. All rights reserved. 2 September 2000 Contents 1 Introduction 2 A 1.1 LTEX 2" fonts . 2 1.2 Overview . 2 1.3 Further information . 3 2 Text fonts 4 2.1 Text font attributes . 4 2.2 Selection commands . 6 2.3 Internals . 7 2.4 Parameters for author commands . 8 2.5 Special font declaration commands . 9 3 Math fonts 10 3.1 Math font attributes . 10 3.2 Selection commands . 11 3.3 Declaring math versions . 12 3.4 Declaring math alphabets . 12 3.5 Declaring symbol fonts . 13 3.6 Declaring math symbols . 14 3.7 Declaring math sizes . 16 4 Font installation 16 4.1 Font definition files . 16 4.2 Font definition file commands . 16 4.3 Font file loading information . 18 4.4 Size functions . 18 5 Encodings 20 5.1 The fontenc package . 20 5.2 Encoding definition file commands . 20 5.3 Default definitions . 23 5.4 Encoding defaults . 24 5.5 Case changing . 25 1 6 Miscellanea 25 6.1 Font substitution . 25 6.2 Preloading . 26 6.3 Accented characters . 26 6.4 Naming conventions . 27 7 If you need to know more . 28 1 Introduction A This document describes the new font selection features of the LTEX Document Preparation System. It is intended for package writers who want to write font- loading packages similar to times or latexsym. This document is only a brief introduction to the new facilities and is intended A for package writers who are familiar with TEX fonts and LTEX packages.
    [Show full text]
  • Draft NISTIR 7628 Revision 1, Guidelines for Smart Grid Cyber Security
    The attached DRAFT document (provided here for historical purposes) has been superseded by the following publication: Publication Number: NIST Interagency Report (NISTIR) 7628 Revision 1 Title: Guidelines for Smart Grid Cybersecurity: Volume 1: Smart Grid Cybersecurity Strategy, Architecture, and High- Level Requirements Volume 2: Privacy and the Smart Grid Volume 3: Supportive Analyses and References Publication Date: September 2014 • Final Publication: https://doi.org/10.6028/NIST.IR.7628r1 (direct link: http://nvlpubs.nist.gov/nistpubs/ir/2014/NIST.IR.7628r1.pdf). • Information on other NIST Computer Security Division publications and programs can be found at: http://csrc.nist.gov/ The following information was posted with the attached DRAFT document: Oct. 25, 2013 NIST IR 7628 Rev. 1 DRAFT Guidelines for Smart Grid Cybersecurity: Vol. 1 - Smart Grid Cybersecurity Strategy, Architecture, and High-Level Requirements Vol. 2 - Privacy and the Smart Grid Vol. 3 - Supportive Analyses and References The National Institute of Standards and Technology (NIST) seeks comments on draft NISTIR 7628 Revision 1, Guidelines for Smart Grid Cyber Security. The comment period will be open from October 25 through December 23, 2013. Draft NISTIR 7628 Rev. 1 was completed by the NIST-led Smart Grid Cybersecurity Committee (formerly the Cyber Security Working Group) of the Smart Grid Interoperability Panel. The document has been updated to address changes in technologies and implementations since the release of NISTIR 7628 in September 2010. In addition, the document development strategy, cryptography and key management, privacy, vulnerability classes, research and development topics, standards review, and key power system use cases have been updated and expanded to reflect changes in the Smart Grid environment since 2010.
    [Show full text]
  • International Language Environments Guide
    International Language Environments Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 806–6642–10 May, 2002 Copyright 2002 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, Java, XView, ToolTalk, Solstice AdminTools, SunVideo and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. SunOS, Solaris, X11, SPARC, UNIX, PostScript, OpenWindows, AnswerBook, SunExpress, SPARCprinter, JumpStart, Xlib The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry.
    [Show full text]
  • Involvement of CDP/Cux in the Regulation of Histone H4 Gene Expression, Proliferation and Differentiation: a Dissertation
    University of Massachusetts Medical School eScholarship@UMMS GSBS Dissertations and Theses Graduate School of Biomedical Sciences 2003-05-07 Involvement of CDP/Cux in the Regulation of Histone H4 Gene Expression, Proliferation and Differentiation: a Dissertation Mai X. Luong University of Massachusetts Medical School Let us know how access to this document benefits ou.y Follow this and additional works at: https://escholarship.umassmed.edu/gsbs_diss Part of the Amino Acids, Peptides, and Proteins Commons, Cells Commons, and the Genetic Phenomena Commons Repository Citation Luong MX. (2003). Involvement of CDP/Cux in the Regulation of Histone H4 Gene Expression, Proliferation and Differentiation: a Dissertation. GSBS Dissertations and Theses. https://doi.org/ 10.13028/10ah-dx47. Retrieved from https://escholarship.umassmed.edu/gsbs_diss/34 This material is brought to you by eScholarship@UMMS. It has been accepted for inclusion in GSBS Dissertations and Theses by an authorized administrator of eScholarship@UMMS. For more information, please contact [email protected]. INVOLVEMENT OF CDP/CUX IN THE REGULATION OF HISTONE H4 GENE EXPRESSION, PROLIFERATION AND DIFFERENTIATION A Dissertation Presented Mai Xuan Luong Submitted to the Faculty of the University of Massachusetts Graduate School of Biomedical Sciences, Worcester in partial fulfillment of the requirement for the degree of: DOCTOR OF PHILOSOPHY IN BIOMEDICAL SCIENCES MAY 7, 2003 CELL BIOLOGY Jeanne B. Lawrence, Chairman of Committee Stephen N. Jones, Member of Committee Tony Ip, Member of Committee Timothy F. Kowalik, Member of Committee Alain Nepveu, Member of Committee Janet L. Stein, Dissertation Mentor Gary S. Stein, Dissertation Mentor Anthony Carruthers, Dean of the : - DEDICA TION This thesis is dedicated to my parents, Xieu Tho Tran and Thuan Luong, who have encouraged and supported me in all my endeavors.
    [Show full text]
  • Windows NLS Considerations Version 2.1
    Windows NLS Considerations version 2.1 Radoslav Rusinov [email protected] Windows NLS Considerations Contents 1. Introduction ............................................................................................................................................... 3 1.1. Windows and Code Pages .................................................................................................................... 3 1.2. CharacterSet ........................................................................................................................................ 3 1.3. Encoding Scheme ................................................................................................................................ 3 1.4. Fonts ................................................................................................................................................... 4 1.5. So Why Are There Different Charactersets? ........................................................................................ 4 1.6. What are the Difference Between 7 bit, 8 bit and Unicode Charactersets? ........................................... 4 2. NLS_LANG .............................................................................................................................................. 4 2.1. Setting the Character Set in NLS_LANG ............................................................................................ 4 2.2. Where is the Character Conversion Done? .........................................................................................
    [Show full text]