DOCSLIB.ORG

Oracle Rdb™ SQL Reference Manual Volume 1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Oracle Rdb™ SQL Reference Manual Volume 1 Release 7.2 for HP OpenVMS Industry Standard 64 for Integrity Servers and OpenVMS Alpha operating systems October 2006 ® DEC_Callout (encoded characters) FullName: DEC Modular Callouts Distiller, PostScript v3011.104 r0 Notice: Copyright 1988 - 1993, Digital Equipment Corporation. Font version: 1.3, 13-Oct-1993 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 40 1.000 41 1.000 42 1.000 43 1.000 44 1.000 45 1.000 46 1.000 47 1.000 50 1.000 51 1.000 52 0.500 53 0.500 54 0.500 55 0.500 56 0.500 57 0.500 cx0 cx1 cx2 cx3 cx4 cx5 cx6 cx7 cx8 cx9 bx0 bx1 bx2 bx3 bx4 bx5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 60 0.500 61 0.500 62 0.500 63 0.500 64 0.375 65 0.375 66 0.375 67 0.375 70 0.375 71 0.375 72 0.375 73 0.375 74 0.375 75 0.375 76 0.500 77 0.500 bx6 bx7 bx8 bx9 mx0 mx1 mx2 mx3 mx4 mx5 mx6 mx7 mx8 mx9 ex0 ex1 2 3 4 5 6 7 8 9 100 0.500 101 0.500 102 0.500 103 0.500 104 0.500 105 0.500 106 0.500 107 0.500 110 0.000 111 0.000 112 0.000 113 0.000 114 0.000 115 0.000 116 0.000 117 0.000 ex2 ex3 ex4 ex5 ex6 ex7 ex8 ex9 120 0.000 121 0.000 122 0.000 123 0.000 124 0.000 125 0.000 126 0.000 127 0.000 130 0.000 131 0.000 132 0.000 133 0.000 134 0.000 135 0.000 136 0.000 137 0.000 140 0.000 141 0.000 142 0.000 143 0.000 144 0.000 145 0.000 146 0.000 147 0.000 150 0.000 151 0.000 152 0.000 153 0.000 154 0.000 155 0.000 156 0.000 157 0.000 160 0.000 161 0.000 162 0.000 163 0.000 164 0.000 165 0.000 166 0.000 167 0.000 170 0.000 171 0.000 172 0.000 173 0.000 174 0.000 175 0.000 176 0.000 177 0.000 0123456789012345678901234567890123456789 240 0.000 241 0.000 242 0.000 243 0.000 244 0.000 245 0.000 246 0.000 247 0.000 250 0.000 251 0.000 252 0.000 253 0.000 254 0.000 255 0.000 256 0.000 257 0.000 260 0.000 261 0.000 262 0.000 263 0.000 264 0.000 265 0.000 266 0.000 267 0.000 270 0.000 271 0.000 272 0.000 273 0.000 274 0.000 275 0.000 276 0.000 277 0.000 300 0.000 301 0.000 302 0.000 303 0.000 304 0.000 305 0.000 306 0.000 307 0.000 310 0.000 311 0.000 312 0.000 313 0.000 314 0.000 315 0.000 316 0.000 317 0.000 320 0.000 321 0.000 322 0.000 323 0.000 324 0.000 325 0.000 326 0.000 327 0.000 330 0.000 331 0.000 332 0.000 333 0.000 334 0.000 335 0.000 336 0.000 337 0.000 340 0.000 341 0.000 342 0.000 343 0.000 344 0.000 345 0.000 346 0.000 347 0.000 350 0.000 351 0.000 352 0.000 353 0.000 354 0.000 355 0.000 356 0.000 357 0.000 360 0.000 361 0.000 362 0.000 363 0.000 364 0.000 365 0.000 366 0.000 367 0.000 370 0.000 371 0.000 372 0.000 373 0.000 374 0.000 375 0.000 376 0.000 377 0.000 SQL Reference Manual, Volume 1 Oracle Rdb Release 7.2 for HP OpenVMS Industry Standard 64 for Integrity Servers and OpenVMS Alpha Copyright © 1987, 2006 Oracle Corporation. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the programs is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are ‘‘commercial computer software’’ or ‘‘commercial technical data’’ pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the Programs. Oracle is a registered trademark, and Oracle Rdb, Hot Standby, LogMiner for Rdb, Oracle CODASYL DBMS, Oracle RMU, Oracle CDD/Repository, Oracle SQL/Services, Oracle Trace, and Rdb are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services, or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Contents Send Us Your Comments ........................................... xi Preface ........................................................... xiii Technical Changes and New Features ............................... xvii 1 Introduction to SQL Syntax 1.1 Using SQL ................................................ 1–1 1.1.1 Invoking SQL Images . ................................. 1–2 1.2 Samples Directory . ......................................... 1–3 1.3 How to Read Syntax Diagrams ................................ 1–3 1.4 Executable and Nonexecutable Statements ....................... 1–6 1.5 Summary of SQL Statements . ................................. 1–7 1.6 Keywords and Line Terminators ............................... 1–13 1.6.1 Statement Terminators and Comment Characters ............... 1–13 1.7 Support for Multivendor Integration Architecture . ................ 1–16 2 Language and Syntax Elements 2.1 Supported Character Sets . ................................. 2–1 2.1.1 Automatic Translation . ................................. 2–6 2.1.2 Character Set HEX ...................................... 2–7 2.1.3 Default Character Sets . ................................. 2–8 2.1.4 Display Character Set . ................................. 2–9 2.1.5 Identifier Character Set . ................................. 2–10 2.1.6 Literal Character Sets . ................................. 2–11 2.1.7 National Character Set . ................................. 2–12 2.1.8 Character Set ISOLATIN9 ................................. 2–13 2.1.9 Oracle NLS Character Set Names . ......................... 2–14 2.1.10 Character Set UNSPECIFIED .............................. 2–15 2.1.11 Logical Names for Character Sets . ......................... 2–16 iii 2.2 User-Supplied Names . ...................................... 2–16 2.2.1 Aliases . .............................................. 2–25 2.2.2 Authorization Identifiers .................................. 2–26 2.2.2.1 Authorization Identifiers and Stored Modules . ............. 2–27 2.2.2.2 Authorization Identifiers and Nonstored Modules ............ 2–31 2.2.3 Catalog Names .......................................... 2–31 2.2.4 Column Names . ...................................... 2–32 2.2.4.1 Correlation Names .................................... 2–34 2.2.4.2 Outer References ..................................... 2–36 2.2.5 Connection Names . ...................................... 2–37 2.2.6 Constraint Names . ...................................... 2–38 2.2.7 Cursor Names .......................................... 2–38 2.2.8 Database Names . ...................................... 2–38 2.2.8.1 Oracle Rdb Attach Specifications . ...................... 2–39 2.2.8.2 Repository Path Names . .............................. 2–42 2.2.9 DomainNames ......................................... 2–43 2.2.10 Index Names ........................................... 2–44 2.2.11 Names in Multischema Databases ........................... 2–45 2.2.12 Nonstored Module, Procedure, and Parameter Names (Module Language Only) . ...................................... 2–46 2.2.13 Parameters, Routine Parameters, and SQL Variables ...........
Recommended publications
  • Documents and Attachments 57 Chapter 7: Dbamp Stored Procedure Reference

    Documents and Attachments 57 Chapter 7: Dbamp Stored Procedure Reference

    CData Software, Inc. DBAmp SQL Server Integration with Salesforce.com Version 5.1.6 Copyright © 2021 CData Software, Inc. All rights reserved. Table of Contents Acknowledgments ........................................................................... 7 Chapter 1: Installation/Upgrading ................................................. 8 Upgrading an existing installation ......................................................... 8 Prerequistes ....................................................................................... 9 Running the DBAmp installation file...................................................... 9 Configure the DBAmp provider options ................................................. 9 Connecting DBAmp to SQL Server ...................................................... 10 Verifying the linked server ................................................................. 11 Install the DBAmp Stored Procedures ................................................. 11 Running the DBAmp Configuration Program........................................ 11 Setting up the DBAmp Work Directory ................................................ 12 Enabling xp_cmdshell for DBAmp ....................................................... 13 Pointing DBAmp to your Salesforce Sandbox Instance ......................... 13 Chapter 2: Using DBAMP as a Linked Server ................................ 14 Four Part Object Names .................................................................... 14 SQL versus SOQL .............................................................................
  • Declare Syntax in Pl Sql

    Declare Syntax in Pl Sql

    Declare Syntax In Pl Sql NickieIs Pierre perennates desecrated some or constant stunner afterafter pomiferousprojectional Sydney Alberto appreciatingconfabulate mourningly.so Jewishly? Abused Gordan masons, his hakim barged fasts reparably. Encircled It could write utility it an sql in the original session state in turn off timing command line if it needs to learn about oracle Berkeley electronic form, and os commands, declare syntax in pl sql syntax shows how odi can execute. To select in response times when it declares an assignment statement to change each actual parameter can be open in a declarative part. Sql functions run on a timing vulnerabilities when running oracle pl sql syntax shows how use? To learn how to performance overhead of an object changes made to explain plan chooses by create applications. Have an archaic law that declare subprograms, declaring variables declared collection of declarations and return result set cookies that references or distinct or script? Plus statements that column, it is not oracle pl sql syntax shows no errors have a nested blocks or a recordset. Always nice the highest purity level line a subprogram allows. The script creates the Oracle system parameters, though reception can be changed by the inactive program. If necessary to declare that are declared in trailing spaces cause a declarative part at precompile time. This syntax defines cursors declared in oracle pl sql. Run on that subprograms as columns and you use a variable must be recompiled at any syntax defines cursors. All procedures move forward references to it is executed at runtime engine runs for this frees memory than store.
  • IBM Db2 High Performance Unload for Z/OS User's Guide

    IBM Db2 High Performance Unload for Z/OS User's Guide

    5.1 IBM Db2 High Performance Unload for z/OS User's Guide IBM SC19-3777-03 Note: Before using this information and the product it supports, read the "Notices" topic at the end of this information. Subsequent editions of this PDF will not be delivered in IBM Publications Center. Always download the latest edition from the Db2 Tools Product Documentation page. This edition applies to Version 5 Release 1 of Db2 High Performance Unload for z/OS (product number 5655-AA1) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM® Corporation 1999, 2021; Copyright Infotel 1999, 2021. All Rights Reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. © Copyright International Business Machines Corporation . US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this information......................................................................................... vii Chapter 1. Db2 High Performance Unload overview................................................ 1 What does Db2 HPU do?..............................................................................................................................1 Db2 HPU benefits.........................................................................................................................................1 Db2 HPU process and components.............................................................................................................2
  • DISSERTATION Concepts for Scientific Computing

    DISSERTATION Concepts for Scientific Computing

    DISSERTATION Concepts for Scientific Computing ausgefuhrt¨ zum Zwecke der Erlangung des akademischen Grades eines Doktors der technischen Wissenschaften eingereicht an der Technischen Universitat¨ Wien Fakultat¨ fur¨ Elektrotechnik und Informationstechnik von RENE´ HEINZL Rosensteingasse 7-9/2 A-1160 Wien, Osterreich¨ Matr. Nr. 9826031 geboren am 6. September 1977, Wien Wien, im Juli 2007 Abstract Scientific computing has traditionally been concerned with numerical issues such as the convergence of discrete approximations to partial differential equations, the stability of integration methods for time- dependent systems, and the computational efficiency of software implementations of these numerical methods. While computer performance is steadily increasing the additional complexity of these simulation models easily outgrows this gain in computational power. It is therefore of utmost importance to employ the latest techniques of software development to obtain high performance and thereby ensure adequate simulation times even for complex problems. As a consequence the development of high performance simulation software is quite challenging. Originating in the field of technology computer aided design as an important and complex area of sci- entific computing, this work is motivated by the fact, that different concepts were developed during the last decades for the field of scientific computing. The great diversity of physical phenomena present in semiconductor devices themselves and in the processes involved in their manufacture make the field of TCAD extremely challenging. Each of the phenomena can be described by differential equations of vary- ing complexity. The development of several different discretisation schemes has been necessary in order to best model the underlying physics and to accommodate the mathematical peculiarities of each of these equations while transferring them to the discrete world of digital computing.
  • Operation in Xql______34 4.5 Well-Formedness Rules of Xql ______36 4.6 Summary ______42

    Operation in Xql______34 4.5 Well-Formedness Rules of Xql ______36 4.6 Summary ______42

    Translation of OCL Invariants into SQL:99 Integrity Constraints Master Thesis Submitted by: Veronica N. Tedjasukmana [email protected] Information and Media Technologies Matriculation Number: 29039 Supervised by: Prof. Dr. Ralf MÖLLER STS - TUHH Prof. Dr. Helmut WEBERPALS Institut für Rechnertechnologie – TUHH M.Sc. Miguel GARCIA STS - TUHH Hamburg, Germany 31 August 2006 Declaration I declare that: this work has been prepared by myself, all literally or content-related quotations from other sources are clearly pointed out, and no other sources or aids than the ones that are declared are used. Hamburg, 31 August 2006 Veronica N. Tedjasukmana i Table of Contents Declaration __________________________________________________________________ i Table of Contents _____________________________________________________________ ii 1 Introduction ______________________________________________________________ 1 1.1 Motivation _____________________________________________________________ 1 1.2 Objective ______________________________________________________________ 2 1.3 Structure of the Work ____________________________________________________ 2 2 Constraint Languages ______________________________________________________ 3 2.1 Defining Constraint in OCL _______________________________________________ 3 2.1.1 Types of Constraints ________________________________________________ 4 2.2 Defining Constraints in Database ___________________________________________ 4 2.3 Comparison of Constraint Language_________________________________________
  • HAIL: an Algorithm for the Hardware Accelerated Identification of Languages, Master's Thesis, May 2006

    HAIL: an Algorithm for the Hardware Accelerated Identification of Languages, Master's Thesis, May 2006

    Washington University in St. Louis Washington University Open Scholarship All Computer Science and Engineering Research Computer Science and Engineering Report Number: WUCSE-2006-36 2006-01-01 HAIL: An Algorithm for the Hardware Accelerated Identification of Languages, Master's Thesis, May 2006 Charles M. Kastner This thesis examines in detail the Hardware-Accelerated Identification of Languages (HAIL) project. The goal of HAIL is to provide an accurate means to identify the language and encoding used in streaming content, such as documents passed over a high-speed network. HAIL has been implemented on the Field-programmable Port eXtender (FPX), an open hardware platform developed at Washington University in St. Louis. HAIL can accurately identify the primary languages and encodings used in text at rates much higher than what can be achieved by software algorithms running on microprocessors. Follow this and additional works at: https://openscholarship.wustl.edu/cse_research Part of the Computer Engineering Commons, and the Computer Sciences Commons Recommended Citation Kastner, Charles M., " HAIL: An Algorithm for the Hardware Accelerated Identification of Languages, Master's Thesis, May 2006" Report Number: WUCSE-2006-36 (2006). All Computer Science and Engineering Research. https://openscholarship.wustl.edu/cse_research/187 Department of Computer Science & Engineering - Washington University in St. Louis Campus Box 1045 - St. Louis, MO - 63130 - ph: (314) 935-6160. Department of Computer Science & Engineering 2006-36 HAIL: An Algorithm for the Hardware Accelerated Identification of Languages, Master's Thesis, May 2006 Authors: Charles M. Kastner Corresponding Author: [email protected] Web Page: http://www.arl.wustl.edu/projects/fpx/reconfig.htm Abstract: This thesis examines in detail the Hardware-Accelerated Identification of Languages (HAIL) project.
  • Regular Expressions in Jlex to Define a Token in Jlex, the User to Associates a Regular Expression with Commands Coded in Java

    Regular Expressions in Jlex to Define a Token in Jlex, the User to Associates a Regular Expression with Commands Coded in Java

    Regular Expressions in JLex To define a token in JLex, the user to associates a regular expression with commands coded in Java. When input characters that match a regular expression are read, the corresponding Java code is executed. As a user of JLex you don’t need to tell it how to match tokens; you need only say what you want done when a particular token is matched. Tokens like white space are deleted simply by having their associated command not return anything. Scanning continues until a command with a return in it is executed. The simplest form of regular expression is a single string that matches exactly itself. © CS 536 Spring 2005 109 For example, if {return new Token(sym.If);} If you wish, you can quote the string representing the reserved word ("if"), but since the string contains no delimiters or operators, quoting it is unnecessary. For a regular expression operator, like +, quoting is necessary: "+" {return new Token(sym.Plus);} © CS 536 Spring 2005 110 Character Classes Our specification of the reserved word if, as shown earlier, is incomplete. We don’t (yet) handle upper or mixed- case. To extend our definition, we’ll use a very useful feature of Lex and JLex— character classes. Characters often naturally fall into classes, with all characters in a class treated identically in a token definition. In our definition of identifiers all letters form a class since any of them can be used to form an identifier. Similarly, in a number, any of the ten digit characters can be used. © CS 536 Spring 2005 111 Character classes are delimited by [ and ]; individual characters are listed without any quotation or separators.
  • AVR244 AVR UART As ANSI Terminal Interface

    AVR244 AVR UART As ANSI Terminal Interface

    AVR244: AVR UART as ANSI Terminal Interface Features 8-bit • Make use of standard terminal software as user interface to your application. • Enables use of a PC keyboard as input and ascii graphic to display status and control Microcontroller information. • Drivers for ANSI/VT100 Terminal Control included. • Interactive menu interface included. Application Note Introduction This application note describes some basic routines to interface the AVR to a terminal window using the UART (hardware or software). The routines use a subset of the ANSI Color Standard to position the cursor and choose text modes and colors. Rou- tines for simple menu handling are also implemented. The routines can be used to implement a human interface through an ordinary termi- nal window, using interactive menus and selections. This is particularly useful for debugging and diagnostics purposes. The routines can be used as a basic interface for implementing more complex terminal user interfaces. To better understand the code, an introduction to ‘escape sequences’ is given below. Escape Sequences The special terminal functions mentioned (e.g. text modes and colors) are selected using ANSI escape sequences. The AVR sends these sequences to the connected terminal, which in turn executes the associated commands. The escape sequences are strings of bytes starting with an escape character (ASCII code 27) followed by a left bracket ('['). The rest of the string decides the specific operation. For instance, the command '1m' selects bold text, and the full escape sequence thus becomes 'ESC[1m'. There must be no spaces between the characters, and the com- mands are case sensitive. The various operations used in this application note are described below.
  • Management of Data Elements in Information Processing

    Management of Data Elements in Information Processing

    PB-249-530 MANAGEMENT OF DATA ELEMENTS IN INFORMATION PROCESSING U.S. DEPARTMENT OF COMMERCE / National Bureau of Standards SECOND NATIONAL SYMPOSIUM NATIONAL BUREAU OF STANDARDS GAITHERSBURG, MARYLAND 1975 OCTOBER 23-24 Available by purchase from the National Technical Information Service, 5285 Port Royal Road, Springfield, Va. 221 Price: $9.25 hardcopy; $2.25 microfiche. National Technical Information Service U. S. DEPARTMENT OF COMMERCE PB-249-530 Management of Data Elements in Information Processing Proceedings of a Second Symposium Sponsored by the American National Standards Institute and by The National Bureau of Standards 1975 October 23-24 NBS, Gaithersburg, Maryland Hazel E. McEwen, Editor Institute for Computer Sciences and Technology National Bureau of Standards Washington, D.C. 20234 U.S. DEPARTMENT OF COMMERCE, Elliot L. Richardson, Secrefary NATIONAL BUREAU OF STANDARDS, Ernest Ambler, Acfing Direc/or Table of Contents Page Introduction to the Program of the Second National Symposium on The Management of Data Elements in Information Processing ix David V. Savidge, Program Chairman On-Line Tactical Data Inputting: Research in Operator Training and Performance 1 Irving Alderman, Ph.D. "Turning the Corner" on MIS, A Proposed Program of Data Standards in Post-Secondary Education 9 Donald R. Arnold, Ph.D. ASCII - The Data Alphabet That Will Endure 17 Robert W. Bemer Techniques in Developing Standard Procedures for Data Editing 23 George W. Covill An Adaptive File Management Systems 45 Dennis L. Dance and Udo W. Pooch (Given by Dance) A Focus on the Role of the Data Manager 57 Ruth M, Davis, Ph.D. A Proposed Standard Routine for Generating Proposed Standard Check Characters 61 Paul -Andre Desjardins Methodology for Development of Standard Data Elements within Multiple Public Agencies 69 L.
  • Developing Embedded SQL Applications

    Developing Embedded SQL Applications

    IBM DB2 10.1 for Linux, UNIX, and Windows Developing Embedded SQL Applications SC27-3874-00 IBM DB2 10.1 for Linux, UNIX, and Windows Developing Embedded SQL Applications SC27-3874-00 Note Before using this information and the product it supports, read the general information under Appendix B, “Notices,” on page 209. Edition Notice This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at http://www.ibm.com/shop/publications/ order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/ planetwide/ To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 1993, 2012. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Introduction to embedded Include files for COBOL embedded SQL SQL................1 applications .............29 Embedding SQL statements
  • ANSI® Programmer's Reference Manual Line Matrix Series Printers

    ANSI® Programmer's Reference Manual Line Matrix Series Printers

    ANSI® Programmer’s Reference Manual Line Matrix Series Printers 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 Copyright © 1998, 2012 Printronix, LLC All rights reserved. Trademark Acknowledgements ANSI is a registered trademark of American National Standards Institute, Inc. Centronics is a registered trademark of Genicom Corporation. Dataproducts is a registered trademark of Dataproducts Corporation. Epson is a registered trademark of Seiko Epson Corporation. IBM and Proprinter are registered trademarks and PC-DOS is a trademark of International Business Machines Corporation. MS-DOS is a registered trademark of Microsoft Corporation. Printronix, IGP, PGL, LinePrinter Plus, and PSA are registered trademarks of Printronix, LLC. QMS is a registered
  • ANSI® Programmer’S Reference Manual

    ANSI® Programmer’S Reference Manual

    ® ANSI® Programmer’s Reference Manual ANSI® Printers Programmer’s Reference Manual ® Trademark Acknowledgements Printronix, Inc. Unisys MTX, Inc. Memorex Telex Decision Systems InternationalDecision Data, Inc. 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, Inc. Unisys MTX, Inc. Memorex Telex Decision Systems InternationalDecision Data, Inc. 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, Inc.Unisys.MTX, Inc. Memorex Telex. Decision Systems International.Decision Data, Inc. Copyright © 1998, 2010 Printronix, Inc. All rights reserved. Trademark Acknowledgements ANSI is a registered trademark of American National Standards Institute, Inc. Centronics is a registered trademark of Genicom Corporation. Dataproducts is a registered trademark of Dataproducts Corporation. Epson is a registered trademark of Seiko Epson Corporation. IBM and Proprinter are registered trademarks and PC-DOS is a trademark of International Business Machines Corporation. MS-DOS is a registered trademark of Microsoft Corporation. Printronix, IGP, PGL, LinePrinter Plus, and PSA are registered trademarks of Printronix, Inc. QMS is a registered trademark and Code V is a trademark of Quality Micro Systems, Inc.