DOCSLIB.ORG

LANSA Version 11.3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

http://www.lansa.com Newsletter June 2006 LANSA version 11.3 Cumulative Update 3 (CU3) Information CU3 is a cumulative set of changes for a range of LANSA features. It includes software to be installed on an iSeries machine and on a Windows machine. CU3 provides a single install point for all features. So, although the software changes have been grouped for a product feature under an EPC number you do NOT need to directly invoke an EPC install. See the epc77n.htm files for details of the changes delivered. CU3 comprises these individual EPCs: • epc770 - LANSA Communications • epc771 - Visual LANSA • epc772 - LANSA Integrator (only on CU3 install CD) • epc773 - LANSA Web Utilities • epc774 - LANSA Web Server • epc775 - LANSA Open • epc776 - Visual LANSA Frameworks CU3 is distributed by CD-ROM or a Zip File that can be downloaded. LANSA version 11.3 page 1 Compile error RDMLX objecten page 10 In LANSA and V5R4 page 2 PrintScreen functionality in VL page 11 CGIConvMode Setting and L4Web page 3 Crash WAM on HP Notebook page 15 This Advanced Enter key in VL page 4 Cannot start VL on Server PC page 17 VLF Web with IE7 beta page 6 Using the PDFSpoolFileService page 18 Issue VLF demo before CU3 page 7 VLF: What’s new in CU3 page 19 LANSA Newsletter June 2006 page 1 © LANSA 2006 LANSA and V5R4 Description IBM’s latest release of i5/OS, V5R4 was made generally available on February 14th. This version of OS/400 is listed in the V11.0 Supported Platforms document as Confirmed. Refer to Supported Platforms : http://www.lansa.com/support/v11news/supportedversions.htm LANSA actively participated in the V5R4 beta program and conducted LANSA V11.0 testing on this version. LANSA's V11.0 testing of the entire LANSA suite of products on V5R4 did not highlight any issues that require correcting. One issue has been reported when using SSL in LANSA for the web on V5R4. However, this issue has been corrected via an IBM PTF. Refer to CGIConvMode setting causes various issues for LANSA for the Web on V5R4 : http://www.lansa.com/support/notes/p0281.htm Unless stated otherwise in the LANSA V11.0 What’s New or Online documentation, existing unsupported OS/400 features remain at the same status. Refer to Features in OS/400 that are not supported in the current versions of LANSA : http://www.lansa.com/support/tips/t0152.htm LANSA Newsletter June 2006 page 2 © LANSA 2006 CGIConvMode setting on V5R4 causes various issues for LANSA for the Web Description The CGIConvMode setting on V5R4 causes problems for LANSA for the web applications. If the CGIConvMode setting is %%MIXED/MIXED%%, the following 2 issues can be generated: 1. Certain character, for example "(" and "'" (single quote) can be mis-interpreted and returned as "M" and "}" respectively on the web browser. 2. SSL does not work properly in your LANSA for the web application. Possible error message would be: EBCDIC_to_UTF8(): Exception MCH1235 occurred while converting TRACE DATA to the job CCSID. Value 0 for CCSID not valid. In the short term, these problems can be circumvented by either commenting out the %MIXED/MIXED% directive or changing the directive to %EBCDIC/MIXED% IBM has produced a PTF to resolve issues introduced by have the CGIConvMode set to %MIXED/MIXED%. Refer to http://www- 912.ibm.com/a_dir/as4ptf.nsf/0/626a4f73de446c0b86257114005db5ae?OpenDocument LANSA Newsletter June 2006 page 3 © LANSA 2006 Advanced Enter Key Handling in VL applications The enter key is often used to indicate the initiation of some activity (eg: to perform a search, to save an update, etc) in VL applications. Typically the ButtonDefault() property is used on push buttons such as “Search” or “Save” so that the enter key causes a virtual click event to be issued against the button. In complex VL forms containing many different reusable parts the use of the ButtonDefault() property may become problematic for two reasons: 1. Only a single button can be the default at any point in time on a Windows form. 2. There is no ability to use program logic to decide what the enter key actually means and how it should be handled in different contexts. The most powerful solution to handling the enter key differently in different places on complex forms is be solved by using the KeyPress event. This allows the VL program to specifically trap the enter key and then respond to it in different ways. Consider the following modifications made to the logic in the filter DF_FILT1 example shipped with the VLF. 1. No button has ButtonDefault() specified This prevents any confusion about which button the enter key should be directed to. 2. The user may initiate an Employee name search in 2 ways Evtroutine Handling(#Surname.KeyPress) Keycode(#KeyCode) if ('#KeyCode.Value = Enter') If *SEARCHOK Execute Search Else Use Message_box_show (ok ok Error *Component 'Enter a search name') Endif Endif Endroutine * Search button pressed * Evtroutine Handling(#Search_phbn.Click) Execute Search Endroutine LANSA Newsletter June 2006 page 4 © LANSA 2006 The first event routine handles the use of the enter key within the Surname field. If the user presses enter then either a search is performed or an error message is displayed (Condition *SEARCHOK is true if field #Surname is non-blank). The second routine handles a specific click of the Search button. Both routines share a common SEARCH subroutine to perform the search logic. Note that where multiple fields (or other visual controls) are used you can handle them all through a single routine like this: Evtroutine Handling(#Surname.KeyPress #GiveName.KeyPress #ComboBox1.KeyPress etc etc) Keycode(#KeyCode) LANSA Newsletter June 2006 page 5 © LANSA 2006 Using VLF Web applications with IE7 beta How can I enable the Visual LANSA Framework to execute as a Web application in I.E. 7 Beta 2? Microsoft recently released the latest beta version of IE7.0. See http://www.microsoft.com/windows/ie/default.mspx If you want to use this IE beta version with VLF-WEB applications you need to do the following: To immediately enable any already deployed VLF-WEB applications • Modify any existing NNNNNNNNNNNN_LLLL_SSS.htm startup files (eg: VF_SY001_System_ENG_XP.HTM) on the HTTP server (where LLLL is the language code and SSS is WEB, XP, or WIN). NOTE: Unless you complete the next step this change is only effective until the next time the framework design is saved or deployed by a developer. • Make a backup copy of the file. • Open the file for editing • Locate the line 'else if (navigator.appMinorVersion.indexOf("SP3") >= 0) __strAppVersion__ = "6+";' • After this line add the line 'else if (navigator.appMinorVersion.indexOf("Beta 2") >= 0) __strAppVersion__ = "6+";' • Save the changes. To change the way that any new nnnnnnnnnnnn_LLLL_SSS.htm startup files are generated by developers • Modify the developers skeleton file VF_SY004_1.dat. • Locate the VF_SY004_1.dat file in the partition execute directory of the development system. • Make a backup copy of the file. • Open the file for editing. • Locate the line 'else if (navigator.appMinorVersion.indexOf("SP3") >= 0) __strAppVersion__ = "6+";' • After this line add the line 'else if (navigator.appMinorVersion.indexOf("Beta 2") >= 0) __strAppVersion__ = "6+";' • Save the changes. • Make a change to the framework design and save it. The startup file will be regenerated and copied to the HTTP server. LANSA Newsletter June 2006 page 6 © LANSA 2006 The VLF Demonstration and Programming Examples - before CU3 Until LANSA CU3, VLF upgrades always renamed and then replaced the standard shipped demonstration system in XML file VF_SY001_System.XML with the very latest shipped demonstration version. This was done to make sure everybody got to view and use the latest demonstration and programming techniques material. This upgrade approach tended to alarm people who had been putting there own VLF applications into VF_SY001_System.XML. Typically they did not read the upgrade notes or look in the online guide and instead contacted LANSA support in a panic, thinking that their own VLF changes had been lost. They were then directed to the guide and the problem was quickly resolved. This was a waste of everybody's time and the cause of needless angst. The VLF Demonstration and Programming Examples - after CU3 An existing VF_SY001_System.XML file is no longer renamed and replaced by a VLF upgrade. If it already exists it is left unchanged and the new shipped latest version is installed with the name VF_Sy001_System_LastShipped.XML instead. Sounds like a solution that makes everybody happier? Not quite.... So what's the downside to doing this? When a user starts the VLF in an upgraded system they now use the same VF_SY001_System.XML file as they were using before the upgrade. They are using an "old" version that contains the "old" definitions of the demonstration and programming examples. There are two significant downsides to this: 1. Developers may not get to view and use the latest demonstration and programming examples because they are not defined in their "old" VF_SY001_System.XML. 2. There may be incompatibilities between the newly upgraded demonstration filters and command handler programs and what is defined in their "old" VF_SY001_System.XML. LANSA Newsletter June 2006 page 7 © LANSA 2006 An example of (1) is the new "Advanced Instance List" examples. These are new to the CU3 version of the VLF. If you use an "old" version of VF_SY001_System.XML you will not see them and may never know they exist. An example of (2) relates to the shipped example EMPLOYEE and SECTIONS business objects. In the CU3 version of the VLF the instance lists and relationships for EMPLOYEE and SECTIONS were significantly changed to demonstrate the new parent/child type relationships.
Recommended publications
  • Cumberland Tech Ref.Book

    Cumberland Tech Ref.Book

    Forms Printer 258x/259x Technical Reference DRAFT document - Monday, August 11, 2008 1:59 pm Please note that this is a DRAFT document. More information will be added and a final version will be released at a later date. August 2008 www.lexmark.com Lexmark and Lexmark with diamond design are trademarks of Lexmark International, Inc., registered in the United States and/or other countries. © 2008 Lexmark International, Inc. All rights reserved. 740 West New Circle Road Lexington, Kentucky 40550 Draft document Edition: August 2008 The following paragraph does not apply to any country where such provisions are inconsistent with local law: LEXMARK INTERNATIONAL, INC., PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in later editions. Improvements or changes in the products or the programs described may be made at any time. Comments about this publication may be addressed to Lexmark International, Inc., Department F95/032-2, 740 West New Circle Road, Lexington, Kentucky 40550, U.S.A. In the United Kingdom and Eire, send to Lexmark International Ltd., Marketing and Services Department, Westhorpe House, Westhorpe, Marlow Bucks SL7 3RQ. Lexmark may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
  • INTERSKILL MAINFRAME QUARTERLY December 2011

    INTERSKILL MAINFRAME QUARTERLY December 2011

    INTERSKILL MAINFRAME QUARTERLY December 2011 Retaining Data Center Skills Inside This Issue and Knowledge Retaining Data Center Skills and Knowledge 1 Interskill Releases - December 2011 2 By Greg Hamlyn Vendor Briefs 3 This the final chapter of this four part series that briefly Taking Care of Storage 4 explains the data center skills crisis and the pros and cons of Learning Spotlight – Managing Projects 5 implementing a coaching or mentoring program. In this installment we will look at some of the steps to Tech-Head Knowledge Test – Utilizing ISPF 5 implementing a program such as this into your data center. OPINION: The Case for a Fresh Technical If you missed these earlier installments, click the links Opinion 6 below. TECHNICAL: Lost in Translation Part 1 - EBCDIC Code Pages 7 Part 1 – The Data Center Skills Crisis MAINFRAME – Weird and Unusual! 10 Part 2 – How Can I Prevent Skills Loss in My Data Center? Part 3 – Barriers to Implementing a Coaching or Mentoring Program should consider is the GROW model - Determine whether an external consultant should be Part Four – Implementing a Successful Coaching used (include pros and cons) - Create a basic timeline of the project or Mentoring Program - Identify how you will measure the effectiveness of the project The success of any project comes down to its planning. If - Provide some basic steps describing the coaching you already believe that your data center can benefit from and mentoring activities skills and knowledge transfer and that coaching and - Next phase if the pilot program is deemed successful mentoring will assist with this, then outlining a solid (i.e.
  • IBM Unica Campaign: Administrator's Guide to Remove a Dimension Hierarchy

    IBM Unica Campaign: Administrator's Guide to Remove a Dimension Hierarchy

    IBM Unica Campaign Version 8 Release 6 February, 2013 Administrator's Guide Note Before using this information and the product it supports, read the information in “Notices” on page 385. This edition applies to version 8, release 6, modification 0 of IBM Unica Campaign and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1998, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Administration in IBM Unica To view system table contents .......27 Campaign ..............1 Working with user tables ..........28 Campaign-related administrative tasks in IBM Unica About working with user tables ......28 Marketing ...............1 Guidelines for mapping user tables .....28 To access data sources from within a flowchart 29 Chapter 2. Managing security in IBM Working with user tables while editing a flowchart ..............29 Unica Campaign ...........3 Working with user tables from the Campaign About security policies ...........3 Settings page .............30 The global security policy .........3 Working with data dictionaries ........39 How Campaign evaluates permissions.....4 To open a data dictionary.........39 Using the Owner and Folder Owner roles . 4 To apply changes to a data dictionary ....40 Guidelines for designing security policies....5 When to use a data dictionary .......40 Security scenarios.............5 Data dictionary syntax..........40 Scenario 1: Company with a single division . 5 To manually create a new data dictionary . 40 Scenario 2: Company with multiple separate Working with table catalogs .........41 divisions...............7 To access table catalogs .........41 Scenario 3: Restricted access within a division .
  • INCITS Withdrawn Standards and Projects List - Prior to 2015

    INCITS Withdrawn Standards and Projects List - Prior to 2015

    INCITS Withdrawn Standards and Projects List - Prior to 2015 Key: Designation: The final standard designation given to the published standard Project: The initial number assigned to new project prior to 2013. Title: Title of the standard Committee: The committee assignment for the project. Designation: -[] Project: 1058 Knowledge Information Format (KIF) Committee: INCITS/DM32.8 Designation: -[] Project: 1059 Conceptual Graphs: A presentation language for knowledge in conceptual models Committee: INCITS/DM32.8 Designation: -[] Project: 106 USA Candidates for Registry Committee: INCITS/L2 Designation: -[] Project: 2113 Cartridge Characterization Standard - Part 4: Ink Cartridge Attributes Committee: INCITS/W1 Designation: -[] Project: 2113 Cartridge Characterization Standard - Part 5: Toner cartridge attributes Committee: INCITS/W1 Designation: -[] Project: 2086 Document Printing Application - Part 1: Abstract Service Definition and Procedures Committee: INCITS/T3 Designation: -[] Project: 2087 Application session service Committee: INCITS/T3 Designation: -[] Project: 1234 Information technology - Database languages - SQL - Part 4: Persistent Stored Modules (SQL/PSM) TECHNICAL CORRIGENDUM 1 Committee: INCITS/DM32.2 Designation: -[] Project: 1234 Information technology - Database languages - SQL - Part 1: Framework (SQL/Framework) TECHNICAL CORRIGENDUM 1 Committee: INCITS/DM32.2 Designation: -[] Project: 2061 Protocol Combinations to Provide and Support the OSI Network Service (Technical Report Type 3) Committee: INCITS/T3 Designation:
  • IGP® / VGL Emulation Code V™ Graphics Language Programmer's Reference Manual Line Matrix Series Printers

    IGP® / VGL Emulation Code V™ Graphics Language Programmer's Reference Manual Line Matrix Series Printers

    IGP® / VGL Emulation Code V™ Graphics Language Programmer’s Reference Manual Line Matrix Series Printers Trademark Acknowledgements IBM and IBM PC are registered trademarks of the International Business Machines Corp. HP and PCL are registered trademarks of Hewlett-Packard Company. IGP, LinePrinter Plus, PSA, and Printronix are registered trademarks of Printronix, LLC. QMS is a registered trademark and Code V is a trademark of Quality Micro Systems, Inc. CSA is a registered certification mark of the Canadian Standards Association. TUV is a registered certification mark of TUV Rheinland of North America, Inc. UL is a registered certification mark of Underwriters Laboratories, Inc. This product uses Intellifont Scalable typefaces and Intellifont technology. Intellifont is a registered trademark of Agfa Division, Miles Incorporated (Agfa). CG Triumvirate are trademarks of Agfa Division, Miles Incorporated (Agfa). CG Times, based on Times New Roman under license from The Monotype Corporation Plc is a product of Agfa. Printronix, LLC. makes no representations or warranties of any kind regarding this material, including, but not limited to, implied warranties of merchantability and fitness for a particular purpose. Printronix, LLC. shall not be held responsible for errors contained herein or any omissions from this material or for any damages, whether direct, indirect, incidental or consequential, in connection with the furnishing, distribution, performance or use of this material. The information in this manual is subject to change without notice. This document contains proprietary information protected by copyright. No part of this document may be reproduced, copied, translated or incorporated in any other material in any form or by any means, whether manual, graphic, electronic, mechanical or otherwise, without the prior written consent of Printronix, LLC.
  • JFP Reference Manual 5 : Standards, Environments, and Macros

    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.
  • Windows NLS Considerations Version 2.1

    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? .........................................................................................
  • Report Syntax Report Syntax

    Report Syntax Report Syntax

    Report Syntax Report Syntax Report Syntax This chapter describes the syntax and parameters of the ADAREP utility. Optional Parameters Examples Optional Parameters ADAREP can be specified alone to retrieve a database status report. You can optionally customize the report by added parameter values. ACODE: Identify Code Page for XML UTF-8 Output Use the ACODE parameter only if the UTF8 option is specified on the OUTPUT parameter. This parameter identifies the code page to which the database name, file names, and checkpoint names should be converted. This parameter is specified in three parts, in a specific order, and with each part separated by a comma from the others: ACODE=’database-name-codepage,file-name-codepage,checkpoint-name-codepage’ The database-name-codepage can either be the literal "GCB" or a valid code page number; the file-name-codepage can either be the literal "GCB", the literal "FCB", or a valid code page number; the checkpoint-name-codepage can either be the literal "GCB" or a valid code page number: A setting of "GCB" for any part indicates that the code page for that part should be acquired from the code page in the GCB (the GCB ACODE setting). 1 Report Syntax Optional Parameters A setting of "FCB" for the file-name-codepage indicates that the code page for converting file names in the XML document to UTF-8 should be acquired from the code page setting in the FCB (the FCB ACODE setting). If code pages for all three parts of the ACODE parameter are being specified, they must be specified in the order shown above.
  • Downloaded Truetype Fonts

    Downloaded Truetype Fonts

    Packet Reference Manual Monarch® 9825® and 9855® Printers TC9800PM Rev DR 10/15 Printer & Fastener Solutions ©1996 Avery Dennison Corp. All rights reserved. Each product and program carries a respective written warranty, the only warranty on which the customer can rely. Avery Dennison Corp. reserves the right to make changes in the product, the programs, and their availability at any time and without notice. Although Avery Dennison Corp. has made every effort to provide complete and accurate information in this manual, Avery Dennison Corp. shall not be liable for any omissions or inaccuracies. Any update will be incorporated in a later edition of this manual. ©1996 Avery Dennison Corp. All rights reserved. No part of this publication may be reproduced, transmitted, stored in a retrieval system, or translated into any language in any form by any means, without the prior written permission of Avery Dennison Corp. WARNING This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. CANADIAN D.O.C. WARNING This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications.Le présent appareil numérique német pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe A prescrites dans le Réglement sur le brouillage radioélectrique édicte par le ministére des Communications du Canada.
  • 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

    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.
  • Data Loss Prevention R80.40 Administration Guide

    Data Loss Prevention R80.40 Administration Guide

    22 January 2020 DATA LOSS PREVENTION R80.40 Administration Guide ] Protected [Classification: Check Point Copyright Notice © 2020 Check Point Software Technologies Ltd. All rights reserved. This product and related documentation are protected by copyright and distributed under licensing restricting their use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form or by any means without prior written authorization of Check Point. While every precaution has been taken in the preparation of this book, Check Point assumes no responsibility for errors or omissions. This publication and features described herein are subject to change without notice. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. TRADEMARKS: Refer to the Copyright page for a list of our trademarks. Refer to the Third Party copyright notices for a list of relevant copyrights and third-party licenses. Data Loss Prevention R80.40 Administration Guide Important Information Latest Software We recommend that you install the most recent software release to stay up-to-date with the latest functional improvements, stability fixes, security enhancements and protection against new and evolving attacks. Certifications For third party independent certification of Check Point products, see the Check Point Certifications page. Check Point R80.40 For more about this release, see the R80.40 home page. Latest Version of this Document Open the latest version of this document in a Web browser.
  • Pdflib Text Extraction Toolkit (TET) Manual

    Pdflib Text Extraction Toolkit (TET) Manual

    ABC Text Extraction Toolkit (TET) Version 4.3 Toolkit for extracting Text, Images, and Metadata from PDF Documents Copyright © 2002–2014 PDFlib GmbH. All rights reserved. Protected by European and U.S. patents. PDFlib GmbH Franziska-Bilek-Weg 9, 80339 München, Germany www.pdflib.com phone +49 • 89 • 452 33 84-0 fax +49 • 89 • 452 33 84-99 If you have questions check the PDFlib mailing list and archive at tech.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, PostScript, and XMP are trademarks of Adobe Systems Inc. AIX, IBM, OS/390, WebSphere, iSeries, and zSeries are trademarks of International Business Machines Corporation. ActiveX, Microsoft, OpenType, and Windows 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.