DOCSLIB.ORG

Pdflib 6 Reference Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pdflib 6 Reference Manual PDFlib GmbH München, Germany www.pdflib.com Reference Manual ® A library for generating PDF on the fly Version 6.0.1 General Edition for Cobol, C, C++, Java, Perl, PHP, Python, RPG, and Tcl Copyright © 1997–2004 PDFlib GmbH and Thomas Merz. All rights reserved. PDFlib GmbH Tal 40, 80331 München, Germany www.pdflib.com phone +49 • 89 • 29 16 46 87 fax +49 • 89 • 29 16 46 86 If you have questions check the PDFlib mailing list and archive at groups.yahoo.com/group/pdflib Licensing contact: [email protected] Support for commercial PDFlib licensees: [email protected] (please include your license number) This publication and the information herein is furnished as is, is subject to change without notice, and should not be construed as a commitment by PDFlib GmbH. PDFlib GmbH assumes no responsibility or lia- bility for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with re- spect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for par- ticular purposes and noninfringement of third party rights. PDFlib and the PDFlib logo are registered trademarks of PDFlib GmbH. PDFlib licensees are granted the right to use the PDFlib name and logo in their product documentation. However, this is not required. Adobe, Acrobat, and PostScript are trademarks of Adobe Systems Inc. AIX, IBM, OS/390, WebSphere, iSeries, and zSeries are trademarks of International Business Machines Corporation. ActiveX, Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation. Apple, Macintosh and TrueType are trademarks of Apple Computer, Inc. Unicode and the Unicode logo are trademarks of Unicode, Inc. Unix is a trademark of The Open Group. Java and Solaris are trademarks of Sun Microsystems, Inc. HKS is a registered trade- mark of the HKS brand association: Hostmann-Steinberg, K+E Printing Inks, Schmincke. Other company product and service names may be trademarks or service marks of others. PANTONE® colors displayed in the software application or in the user documentation may not match PANTONE-identified standards. Consult current PANTONE Color Publications for accurate color. PANTONE® and other Pantone, Inc. trademarks are the property of Pantone, Inc. © Pantone, Inc., 2003. Pantone, Inc. is the copyright owner of color data and/or software which are licensed to PDFlib GmbH to distribute for use only in combination with PDFlib Software. PANTONE Color Data and/or Software shall not be copied onto another disk or into memory unless as part of the execution of PDFlib Software. PDFlib contains modified parts of the following third-party software: ICClib, Copyright © 1997-2002 Graeme W. Gill GIF image decoder, Copyright © 1990-1994 David Koblas PNG image reference library (libpng), Copyright © 1998-2004 Glenn Randers-Pehrson Zlib compression library, Copyright © 1995-2002 Jean-loup Gailly and Mark Adler TIFFlib image library, Copyright © 1988-1997 Sam Leffler, Copyright © 1991-1997 Silicon Graphics, Inc. Cryptographic software written by Eric Young, Copyright © 1995-1998 Eric Young ([email protected]) Independent JPEG Group’s JPEG software, Copyright © 1991-1998, Thomas G. Lane PDFlib contains the RSA Security, Inc. MD5 message digest algorithm. Viva Software GmbH contributed improvements to the font handling for Mac OS. Author: Thomas Merz Design and illustrations: Alessio Leonardi Quality control (manual): Katja Schnelle Romaus, Kurt Stützer Quality control (software): a cast of thousands Contents 0 Applying the PDFlib License Key 9 1 Introduction 11 1.1 PDFlib Programming 11 1.2 Major new Features in PDFlib 6 13 1.3 PDFlib Features 15 1.4 Availability of Features in different Products 17 2 PDFlib Language Bindings 19 2.1 Overview 19 2.2 Cobol Binding 20 2.2.1 Special Considerations for Cobol 20 2.2.2 The »Hello world« Example in Cobol 20 2.3 COM Binding 24 2.4 C Binding 24 2.4.1 Availability and Special Considerations for C 24 2.4.2 The »Hello world« Example in C 24 2.4.3 Using PDFlib as a DLL loaded at Runtime 25 2.4.4 Error Handling in C 26 2.4.5 Memory Management in C 27 2.4.6 Unicode in the C language binding 28 2.5 C++ Binding 28 2.5.1 Availability and Special Considerations for C++ 28 2.5.2 The »Hello world« Example in C++ 28 2.5.3 Error Handling in C++ 29 2.5.4 Memory Management in C++ 29 2.5.5 Unicode in the C++ language binding 29 2.6 Java Binding 30 2.6.1 Installing the PDFlib Java Edition 30 2.6.2 The »Hello world« Example in Java 31 2.6.3 Error Handling in Java 32 2.7 .NET Binding 33 2.8 Perl Binding 33 2.8.1 Installing the PDFlib Perl Edition 33 2.8.2 The »Hello world« Example in Perl 33 2.8.3 Error Handling in Perl 34 2.9 PHP Binding 34 2.9.1 Installing the PDFlib PHP Edition 34 2.9.2 The »Hello world« Example in PHP 35 Contents 3 2.9.3 Error Handling in PHP 37 2.10 Python Binding 38 2.10.1 Installing the PDFlib Python Edition 38 2.10.2 The »Hello world« Example in Python 38 2.10.3 Error Handling in Python 38 2.11 REALbasic Binding 39 2.12 RPG Binding 39 2.12.1 Compiling and Binding RPG Programs for PDFlib 39 2.12.2 The »Hello world« Example in RPG 39 2.12.3 Error Handling in RPG 41 2.13 Tcl Binding 43 2.13.1 Installing the PDFlib Tcl Edition 43 2.13.2 The »Hello world« Example in Tcl 43 2.13.3 Error Handling in Tcl 44 3 PDFlib Programming 45 3.1 General Programming 45 3.1.1 PDFlib Program Structure and Function Scopes 45 3.1.2 Parameters 45 3.1.3 Exception Handling 46 3.1.4 Option Lists 48 3.1.5 The PDFlib Virtual File System (PVF) 50 3.1.6 Resource Configuration and File Searching 51 3.1.7 Generating PDF Documents in Memory 55 3.1.8 Using PDFlib on EBCDIC-based Platforms 55 3.1.9 Large File Support 56 3.2 Page Descriptions 57 3.2.1 Coordinate Systems 57 3.2.2 Page Sizes and Coordinate Limits 59 3.2.3 Paths 60 3.2.4 Templates 61 3.3 Working with Color 63 3.3.1 Color and Color Spaces 63 3.3.2 Patterns and Smooth Shadings 63 3.3.3 Spot Colors 64 3.3.4 Color Management and ICC Profiles 67 3.4 Hypertext Elements 71 3.4.1 Examples for Creating Hypertext Elements 71 3.4.2 Formatting Options for Text Fields 74 4 Text Handling 77 4.1 Overview of Fonts and Encodings 77 4.1.1 Supported Font Formats 77 4.1.2 Encodings 78 4 Contents 4.1.3 Support for the Unicode Standard 79 4.2 Font Format Details 80 4.2.1 PostScript Fonts 80 4.2.2 TrueType and OpenType Fonts 81 4.2.3 User-Defined (Type 3) Fonts 83 4.3 Font Embedding and Subsetting 84 4.3.1 How PDFlib Searches for Fonts 84 4.3.2 Font Embedding 85 4.3.3 Font Subsetting 87 4.4 Encoding Details 89 4.4.1 8-Bit Encodings 89 4.4.2 Symbol Fonts and Font-specific Encodings 92 4.4.3 Glyph ID Addressing for TrueType and OpenType Fonts 93 4.4.4 The Euro Glyph 93 4.5 Unicode Support 95 4.5.1 Unicode for Page Content and Hypertext 95 4.5.2 Content Strings, Hypertext Strings, and Name Strings 96 4.5.3 String Handling in Unicode-capable Languages 97 4.5.4 String Handling in non-Unicode-capable Languages 98 4.5.5 Character References 100 4.5.6 Unicode-compatible Fonts 102 4.6 Text Metrics and Text Variations 104 4.6.1 Font and Character Metrics 104 4.6.2 Kerning 105 4.6.3 Text Variations 106 4.7 Chinese, Japanese, and Korean Text 108 4.7.1 CJK support in Acrobat and PDF 108 4.7.2 Standard CJK Fonts and CMaps 108 4.7.3 Custom CJK Fonts 112 4.7.4 Forcing monospaced Fonts 114 4.8 Placing and Fitting Single-Line Text 115 4.8.1 Simple Text Placement 115 4.8.2 Placing Text in a Box 116 4.8.3 Aligning Text 117 4.9 Multi-Line Textflows 118 4.9.1 Placing Textflows in the Fitbox 119 4.9.2 Paragraph Formatting Options 120 4.9.3 Inline Option Lists and Macros 121 4.9.4 Tab Stops 123 4.9.5 Numbered Lists 124 4.9.6 Control Characters, Character Mapping, and Symbol Fonts 125 4.9.7 Hyphenation 127 4.9.8 Controlling the Linebreak Algorithm 129 4.9.9 Formatting CJK Text with Textflow 132 Contents 5 5 Importing and Placing Objects 133 5.1 Importing Raster Images 133 5.1.1 Basic Image Handling 133 5.1.2 Supported Image File Formats 134 5.1.3 Image Masks and Transparency 136 5.1.4 Colorizing Images 138 5.1.5 Multi-Page Image Files 139 5.1.6 OPI Support 139 5.2 Importing PDF Pages with PDI (PDF Import Library) 140 5.2.1 PDI Features and Applications 140 5.2.2 Using PDI Functions with PDFlib 140 5.2.3 Acceptable PDF Documents 142 5.3 Placing Images and Imported PDF Pages 144 5.3.1 Scaling, Orientation, and Rotation 144 5.3.2 Adjusting the Page Size 146 6 Variable Data and Blocks 149 6.1 Installing the PDFlib Block Plugin 149 6.2 Overview of the PDFlib Block Concept 150 6.2.1 Complete Separation of Document Design and Program Code 150 6.2.2 Block Properties 151 6.2.3 Why not use PDF Form Fields? 152 6.3 Creating PDFlib Blocks 154 6.3.1 Creating Blocks interactively with the PDFlib Block Plugin 154 6.3.2 Editing Block Properties 156 6.3.3 Copying Blocks between Pages and Documents 157 6.3.4 Converting PDF Form Fields to PDFlib Blocks 159 6.4 Standard Properties for Automated Processing 161 6.4.1 General Properties 161 6.4.2 Text Properties 163 6.4.3 Image Properties 167 6.4.4 PDF Properties 167 6.4.5 Custom Properties 168 6.5 Querying Block Names and Properties 169 6.6 PDFlib Block Specification 171 6.6.1 PDF Object Structure for PDFlib Blocks 171 6.6.2 Generating PDFlib Blocks with pdfmarks 173 7 Generating various PDF Flavors 175 7.1 Acrobat and PDF Versions 175 7.2 Encrypted PDF 176 7.2.1 Strengths and Weaknesses of PDF Security 176 7.2.2 Protecting Documents with PDFlib 177 6 Contents 7.3 Web-Optimized (Linearized) PDF 179 7.4 PDF/X 180 7.4.1 The PDF/X Family of Standards 180 7.4.2 Generating PDF/X-conforming Output 181 7.4.3 Importing PDF/X
Load more

Recommended publications
  • Unicode and Code Page Support
    Natural for Mainframes Unicode and Code Page Support Version 4.2.6 for Mainframes October 2009 This document applies to Natural Version 4.2.6 for Mainframes and to all subsequent releases. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © Software AG 1979-2009. All rights reserved. The name Software AG, webMethods and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. Other company and product names mentioned herein may be trademarks of their respective owners. Table of Contents 1 Unicode and Code Page Support .................................................................................... 1 2 Introduction ..................................................................................................................... 3 About Code Pages and Unicode ................................................................................ 4 About Unicode and Code Page Support in Natural .................................................. 5 ICU on Mainframe Platforms ..................................................................................... 6 3 Unicode and Code Page Support in the Natural Programming Language .................... 7 Natural Data Format U for Unicode-Based Data ....................................................... 8 Statements .................................................................................................................. 9 Logical
    [Show full text]
  • Pdflib Reference Manual
    PDFlib GmbH München, Germany Reference Manual ® A library for generating PDF on the fly Version 5.0.2 www.pdflib.com Copyright © 1997–2003 PDFlib GmbH and Thomas Merz. All rights reserved. PDFlib GmbH Tal 40, 80331 München, Germany http://www.pdflib.com phone +49 • 89 • 29 16 46 87 fax +49 • 89 • 29 16 46 86 If you have questions check the PDFlib mailing list and archive at http://groups.yahoo.com/group/pdflib Licensing contact: [email protected] Support for commercial PDFlib licensees: [email protected] (please include your license number) This publication and the information herein is furnished as is, is subject to change without notice, and should not be construed as a commitment by PDFlib GmbH. PDFlib GmbH assumes no responsibility or lia- bility for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with re- spect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for par- ticular purposes and noninfringement of third party rights. PDFlib and the PDFlib logo are registered trademarks of PDFlib GmbH. PDFlib licensees are granted the right to use the PDFlib name and logo in their product documentation. However, this is not required. Adobe, Acrobat, and PostScript are trademarks of Adobe Systems Inc. AIX, IBM, OS/390, WebSphere, iSeries, and zSeries are trademarks of International Business Machines Corporation. ActiveX, Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation. Apple, Macintosh and TrueType are trademarks of Apple Computer, Inc. Unicode and the Unicode logo are trademarks of Unicode, Inc. Unix is a trademark of The Open Group.
    [Show full text]
  • Basis Technology Unicode対応ライブラリ スペックシート 文字コード その他の名称 Adobe-Standard-Encoding A
    Basis Technology Unicode対応ライブラリ スペックシート 文字コード その他の名称 Adobe-Standard-Encoding Adobe-Symbol-Encoding csHPPSMath Adobe-Zapf-Dingbats-Encoding csZapfDingbats Arabic ISO-8859-6, csISOLatinArabic, iso-ir-127, ECMA-114, ASMO-708 ASCII US-ASCII, ANSI_X3.4-1968, iso-ir-6, ANSI_X3.4-1986, ISO646-US, us, IBM367, csASCI big-endian ISO-10646-UCS-2, BigEndian, 68k, PowerPC, Mac, Macintosh Big5 csBig5, cn-big5, x-x-big5 Big5Plus Big5+, csBig5Plus BMP ISO-10646-UCS-2, BMPstring CCSID-1027 csCCSID1027, IBM1027 CCSID-1047 csCCSID1047, IBM1047 CCSID-290 csCCSID290, CCSID290, IBM290 CCSID-300 csCCSID300, CCSID300, IBM300 CCSID-930 csCCSID930, CCSID930, IBM930 CCSID-935 csCCSID935, CCSID935, IBM935 CCSID-937 csCCSID937, CCSID937, IBM937 CCSID-939 csCCSID939, CCSID939, IBM939 CCSID-942 csCCSID942, CCSID942, IBM942 ChineseAutoDetect csChineseAutoDetect: Candidate encodings: GB2312, Big5, GB18030, UTF32:UTF8, UCS2, UTF32 EUC-H, csCNS11643EUC, EUC-TW, TW-EUC, H-EUC, CNS-11643-1992, EUC-H-1992, csCNS11643-1992-EUC, EUC-TW-1992, CNS-11643 TW-EUC-1992, H-EUC-1992 CNS-11643-1986 EUC-H-1986, csCNS11643_1986_EUC, EUC-TW-1986, TW-EUC-1986, H-EUC-1986 CP10000 csCP10000, windows-10000 CP10001 csCP10001, windows-10001 CP10002 csCP10002, windows-10002 CP10003 csCP10003, windows-10003 CP10004 csCP10004, windows-10004 CP10005 csCP10005, windows-10005 CP10006 csCP10006, windows-10006 CP10007 csCP10007, windows-10007 CP10008 csCP10008, windows-10008 CP10010 csCP10010, windows-10010 CP10017 csCP10017, windows-10017 CP10029 csCP10029, windows-10029 CP10079 csCP10079, windows-10079
    [Show full text]
  • IBM Data Conversion Under Websphere MQ
    IBM WebSphere MQ Data Conversion Under WebSphere MQ Table of Contents .................................................................................................................................................... 3 .................................................................................................................................................... 3 Int roduction............................................................................................................................... 4 Ac ronyms and terms used in Data Conversion........................................................................ 5 T he Pieces in the Data Conversion Puzzle............................................................................... 7 Coded Character Set Identifier (CCSID)........................................................................................ 7 Encoding .............................................................................................................................................. 7 What Gets Converted, and How............................................................................................... 9 The Message Descriptor.................................................................................................................... 9 The User portion of the message..................................................................................................... 10 Common Procedures when doing the MQPUT................................................................. 10 The message
    [Show full text]
  • JFP Reference Manual 5 : Standards, Environments, and Macros
    JFP Reference Manual 5 : Standards, Environments, and Macros Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 817–0648–10 December 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, 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. 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. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • IBM AS/400 Printing V
    IBM AS/400 Printing V A primer on AS/400 printing in today’s networked environment Configuration, performance, problem determination, enhancements In-depth education on AFP and ASCII printing Alain Badan Simon Hodkin Jacques Hofstetter Gerhard Kutschera Bill Shaffer Whit Smith ibm.com/redbooks International Technical Support Organization SG24-2160-01 IBM AS/400 Printing V October 2000 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix L, “Special notices” on page 407. Second Edition (October 2000) The document was created or updated on June 12, 2001. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2 3605 Highway 52N Rochester, Minnesota 55901-7829 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1998, 2000. 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 Preface . xiii The team that wrote this redbook . xiii Comments welcome . xiv Chapter 1. Printing on the AS/400 system. .1 1.1 Output queues: Spooled files . .1 1.2 Data streams supported on the AS/400 system. .3 1.3 Printer writer . .6 1.3.1 Print writer. .8 1.3.2 Print Services Facility/400 . .9 1.3.3 Host print transform. .13 1.3.4 Image print transform .
    [Show full text]
  • DB2 UDB for Z/OS V8 and UNICODE: It’S No Tower of Babel by Jim Schesvold
    DB2 UDB for z/OS V8 and UNICODE: It’s No Tower of Babel By Jim Schesvold INTRODUCTION DB2 UDB for z/OS Version 8 is the largest, most profound, highest impact version in the product’s history. Consider: There are more new lines of code in DB2 V8 than there were total lines of code in DB2 Version 1.1. Some individuals say migrating to DB2 V8 is a migration equivalent to DB2 V6 and V7 combined. The Quality Partnership Program—a beta program—lasted 14 months, the longest ever for DB2. There are more changes to the catalog than any other release or version of DB2. DB2 V8 requires 64-bit addressing. A DB2 V8 address space can be up to 16 exobytes, 8 billion times the storage available with V7 and prior. DB2 V8 entities have been increased by magnitudes. For example: Maximum table size has been increased from 16 terabytes to 128 terabytes. Table names can now be up to 128 bytes instead of 18 bytes. The number of partitions for a table has been increased from 254 to 4096. SQL statement length can now be up to 2 MB instead of 32KB. Archive logs have been increased to 10,000 from 1,000. And the list goes on and on. The installation methodology of DB2 has—optionally—been re-worked through the implemen- tation of msys for Setup as an installation technique. Yet for all these product changes and enhancements, one of the largest modifications in DB2 V8 is the implementation of Unicode. While earlier versions of DB2 had Unicode capability, DB2 V8 has extensively integrated character conversion into nearly every aspect of the product.
    [Show full text]
  • Abkürzungs-Liste ABKLEX
    Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte
    [Show full text]
  • Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems
    Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems Release 13.10 B035-2417-020A February 2010 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You’ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI and Engenio are registered trademarks of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries.
    [Show full text]
  • What's New and Exciting in RPG
    What's New and Exciting in RPG (AKA Scott Goes Crazy.) Presented by Scott Klement http://www.scottklement.com © 2016-2019, Scott Klement There's a band called 1023 MB. They haven't had any gigs yet. This Session Is Organized by Feature This session is organized by feature… …not by release. i Nex i Next IBM i 7.4 IBM i 7.3 IBM i 7.2 A chart at the end will detail the releases. IBM i 7.1 IBM i 6.1 2 IBM No Longer Waits For Next Release This is really, really cool! • Prior to IBM i 7.1 ("V7R1") to get new RPG feature, you waited for next release. • Couldn't install it right away? Had to wait longer. • Needed to support both newer and older releases? Wait longer. • Could be 5+ years before you could use a feature you wanted. This is no longer true! • Starting with Open Access (should've been a 7.2 feature) most new stuff is available on all supported releases! • Fully free format • DATA-INTO • Nested Data Structures 3 Is This Good Or Bad? Definitely good for developers? • especially software companies. Does it look bad for IBM? • why should people update releases? • do people perceive IBM's RPG commitment as "less"? For this reason, IBM holds back at least some of the updates to the next release. 4 Support in SEU There is none. SEU has not had updates since the release of IBM i 6.1 That was March 21 2008! Use the current version of RDi, or a 3 rd party tool (ILEditor, MiWorkplace) 5 OVERLOAD (TO BE RELEASED IN NOVEMBER 2019) PTF for 7.4, 7.3 • OVERLOAD keyword allows multiple "candidate prototypes" to be considered • RPG automatically picks
    [Show full text]
  • View Character Data Translation Guide
    WWW.ASNA.COM Character Data Translation in DataGate/400 (Applies to Release 7.2 and above) One of the most important and overlooked features of ASNA DataGate is its ability to render character data (database fields and text) in various character encodings, as dictated by platforms and globalization requirements. Using the facilities of the iSeries and Windows, DataGate not only supports transparent iSeries-based EBCDIC character translation, but also the unique international character sets supported by particular platforms. This document discusses iSeries, Windows, and DataGate character translation functionality; past and present. By illuminating DataGate’s translation techniques and corresponding facilities, users are better equipped to configure and maintain robust character data applications. This document assumes some familiarity of applications programming with Windows, the iSeries, and DB2/400 database architecture. International Character Sets In the traditional green screen environment, developers were not as concerned with character translation issues, because in this hardware-based scheme, data entered into a green screen terminal was only rendered on a green screen terminal (or its report-printing twin). This “panacea” was disrupted by emerging globalization, the Internet, personal computers, and client/server-based access schemes. From very early on however, IBM and other computer vendors had introduced “national language” character sets reflecting local language and culture in international markets. In the case of IBM, these character sets were based on the original eight- bit EBCDIC character code. Later, to penetrate Asian and other markets with larger character sets, IBM introduced the idea of 16-bit character codes, known as Double- Byte Character Sets (DBCS). IBM identifies its various iSeries character encodings with Coded Character Set Identifiers (CCSIDs).
    [Show full text]
  • UTR#17: Unicode Character Encoding Model
    UTR#17: Unicode Character Encoding Model http://www.unicode.org/reports/tr17/tr17-6.html Technical Reports Proposed Update Unicode Technical Report #17 UNICODE CHARACTER ENCODING MODEL Authors Ken Whistler ([email protected]), Mark Davis ([email protected]), Asmus Freytag ([email protected]) Date 2008-08-25 This Version http://www.unicode.org/reports/tr17/tr17-6.html Previous Version http://www.unicode.org/reports/tr17/tr17-5.html Latest Version http://www.unicode.org/reports/tr17/ Revision 6 Summary This document clarifies a number of the terms used to describe character encodings, and where the different forms of Unicode fit in. It elaborates the Internet Architecture Board (IAB) three-layer “text stream” definitions into a four-layer structure. Status This document is a proposed update of a previously approved Unicode Technical Report. This document may be updated, replaced, or superseded by other documents at any time. Publication does not imply endorsement by the Unicode Consortium. This is not a stable document; it is inappropriate to cite this document as other than a work in progress. A Unicode Technical Report (UTR) contains informative material. Conformance to the Unicode Standard does not imply conformance to any UTR. Other specifications, however, are free to make normative references to a UTR. Please submit corrigenda and other comments with the online reporting form [Feedback]. Related information that is useful in understanding this document is found in the References. For the latest version of the Unicode Standard see [Unicode]. For a list of current Unicode Technical Reports see [Reports]. For more information about versions of the Unicode Standard, see [Versions].
    [Show full text]