DOCSLIB.ORG

Troubleshooting Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Troubleshooting Guide DB2 ® DB2 Version 9 for Linux, UNIX, and Windows Troubleshooting Guide GC10-4240-00 DB2 ® DB2 Version 9 for Linux, UNIX, and Windows Troubleshooting Guide GC10-4240-00 Before using this information and the product it supports, be sure to read the general information under Notices. 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 www.ibm.com/shop/publications/order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at 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 International Business Machines Corporation 1993, 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Learning more . .1 Mimicking databases using db2look . .32 Introduction to problem determination . .1 Listing DB2 products installed on your system About first failure data capture(FFDC) . .3 (Linux and UNIX) . .35 First failure data capture information . .3 Monitoring and troubleshooting using db2pd . .37 General First Failure Data Capture (FFDC) . .3 Collecting environment information using About administration notification log files . .5 db2support . .45 Administration notification log . .5 Traces . .47 Setting the error capture level for the Basic trace diagnostics . .47 administration notification log file . .6 DB2 traces . .49 Interpreting administration notification log file DRDA traces . .52 entries . .6 Control Center traces . .61 About DB2 diagnostic log (db2diag.log) files . .8 JDBC trace files . .62 Setting the diagnostic log file error capture level .8 CLI traces . .64 Interpreting the db2diag.log file informational Platform-specific tools . .70 record . .8 Diagnostic tools (Windows) . .70 Interpreting diagnostic log file entries . .9 Diagnostic tools (Linux and UNIX) . .71 db2cos (callout script) output files . .11 Dump Files . .13 Chapter 5. Searching knowledge bases 75 About trap files . .14 How to search effectively for known problems . .75 Trap files . .14 Problem determination resources . .76 Formatting trap files (Windows) . .15 About platform-specific error logs . .15 Chapter 6. Getting fixes . .77 Platform specific error log information . .15 Applying fix packs . .77 System core files (UNIX) . .16 Accessing system core file information (UNIX) .17 Appendix A. DB2 Database technical Accessing event logs (Windows) . .18 information . .79 Exporting event logs (Windows) . .18 Accessing the Dr. Watson log file (Windows) . .19 Overview of the DB2 technical information . .79 Combining DB2 database and OS diagnostics . .19 Documentation feedback . .79 DB2 technical library in hardcopy or PDF format . .80 Ordering printed DB2 books . .82 Chapter 2. Troubleshooting DB2 . .23 Displaying SQL state help from the command line Troubleshooting DB2 . .23 processor . .83 Troubleshooting partitioned database environments 23 Accessing different versions of the DB2 Information Issuing commands in a partitioned database Center . .84 environment . .23 Displaying topics in your preferred language in the DB2 Information Center . .84 Chapter 3. Troubleshooting DB2 Updating the DB2 Information Center installed on Connect . .25 your computer or intranet server . .85 Problem determination . .25 DB2 tutorials . .87 Gathering relevant information . .25 DB2 troubleshooting information . .87 Initial connection is not successful . .26 Terms and Conditions . .88 Problems encountered after an initial connection . .27 Diagnostic tools . .28 Appendix B. Notices . .89 Trademarks . .91 Chapter 4. Tools for troubleshooting 29 Overview of the db2dart tool . .29 Index . .93 Analyzing db2diag.log files using db2diag . .29 Displaying and altering the Global Registry (UNIX) Contacting IBM . .95 using db2greg . .31 Identifying the version and service level of your product . .31 © Copyright IBM Corp. 1993, 2006 iii iv Troubleshooting Guide Chapter 1. Learning more Introduction to problem determination The first step in good problem analysis is to describe the problem completely. Without a problem description, you will not know where to start investigating the cause of the problem. This step includes asking yourself such basic questions as: v What are the symptoms? v Where is the problem happening? v When does the problem happen? v Under which conditions does the problem happen? v Is the problem reproducible? Answering these and other questions will lead to a good description to most problems, and is the best way to start down the path of problem resolution. What are the symptoms?: ″ When starting to describe a problem, the most obvious question is What is the ″ problem? This may seem like a straightforward question; however, it can be broken down into several other questions to create a more descriptive picture of the problem. These questions can include: v Who or what is reporting the problem? v What are the error codes and error messages? v How does it fail? For example: loop, hang, crash, performance degradation, incorrect result. v What is the business impact? Where is the problem happening?: Determining where the problem originates is not always easy, but it is one of the most important steps in resolving a problem. Many layers of technology can exist between the reporting and failing components. Networks, disks, and drivers are only a few components to be considered when you are investigating problems. v Is the problem platform specific, or common to multiple platforms? v Is the current environment and configuration supported? v Is the application running locally on the database server or on a remote server? v Is there a gateway involved? v Does the database reside on individual disks, or on a RAID disk array? These types of questions will help you isolate the problem layer, and are necessary to determine the problem source. Remember that just because one layer is reporting a problem, it does not always mean the root cause exists there. Part of identifying where a problem is occurring is understanding the environment in which it exists. You should always take some time to completely describe the problem environment, including the operating system, its version, all corresponding software and versions, and hardware information. Confirm you are running within an environment that is a supported configuration, as many © Copyright IBM Corp. 1993, 2006 1 problems can be explained by discovering software levels that are not meant to run together, or have not been fully tested together. When does the problem happen?: Developing a detailed time line of events leading up to a failure is another necessary step in problem analysis, especially for those cases that are one-time occurrences. You can most easily do this by working backwards --start at the time an error was reported (as exact as possible, even down to milliseconds), and work backwards through available logs and information. Usually you only have to look as far as the first suspicious event that you find in any diagnostic log, however, this is not always easy to do and will only come with practice. Knowing when to stop is especially difficult when there are multiple layers of technology each with its own diagnostic information. v Does the problem only happen at a certain time of day or night? v How often does it happen? v What sequence of events leads up to the time the problem is reported? v Does the problem happen after an environment change such as upgrading existing or installing new software or hardware? Responding to questions like this will help you create a detailed time line of events, and will provide you with a frame of reference in which to investigate. Under which conditions does the problem happen?: Knowing what else is running at the time of a problem is important for any complete problem description. If a problem occurs in a certain environment or under certain conditions, that can be a key indicator of the problem cause. v Does the problem always occur when performing the same task? v Does a certain sequence of events need to occur for the problem to surface? v Do other applications fail at the same time? Answering these types of questions will help you explain the environment in which the problem occurs, and correlate any dependencies. Remember that just because multiple problems may have occurred around the same time, it does not necessarily mean that they are always related. Is the problem reproducible?: ″ ″ From a problem description and investigation standpoint, the ideal problem is one that is reproducible. With reproducible problems you almost always have a larger set of tools or procedures available to use to help your investigation. Consequently, reproducible problems are usually easier to debug and solve. However, reproducible problems can have a disadvantage: if the problem is of significant business impact, you don’t want it recurring. If possible, recreating
Load more

Recommended publications
  • DB2 UDB for Z/OS Security Target
    DB2 UDB for z/OS Security Target Version 1.3.13 Status: Final Last Update: 2007-12-06 DB2 UDB for z/OS Security Target IBM atsec is a trademark of atsec GmbH IBM, IBM logo, DB2 UDB for z/OS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: • Advanced Function Presentation • AFP • DFS • DFSORT • • IBM • Infoprint • MVS • PR/SM • Print Services Facility • Processor Resource/Systems Manager • RACF • VTAM • z/Architecture • z/OS • z/VM • zSeries Intel and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States, other countries, or both. Java and all Java-based products are trademarks of Sun Microsystems, Inc., in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. This document is provided AS IS with no express or implied warranties. Use the information in this document at your own risk. This document may be reproduced or distributed in any form without prior permission provided the copyright notice is retained on all copies. Modified versions of this document may be freely distributed provided that they are clearly identified as such, and this copyright is included intact. Copyright (c) 2004, 2005 by atsec GmbH and IBM Corporation or its wholly
    [Show full text]
  • Technical Standard DRDA, Version 2, Volume 1: Distributed Relational Database Architecture (DRDA) Document Number: C911
    Technical Standard DRDA, Version 2, Volume 1: Distributed Relational Database Architecture (DRDA) NICAL H S C T A E N T D A R D [This page intentionally left blank] Open Group Technical Standard DRDA, Version 2, Volume 1: Distributed Relational Database Architecture (DRDA) The Open Group December 1999, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. This documentation and the software to which it relates are derived in part from copyrighted materials supplied by International Business Machines. Neither International Business Machines nor The Open Group makes any warranty of any kind with regard to this material, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The Open Group shall not be liable for errors contained herein, or for any direct or indirect, incidental, special, or consequential damages in connection with the furnishing, performance, or use of this material. Open Group Technical Standard DRDA, Version 2, Volume 1: Distributed Relational Database Architecture (DRDA) Document Number: C911 Published in the U.K. by The Open Group, December 1999. Any comments relating to the material contained in this document may be submitted to: The Open Group Apex Plaza Forbury Road Reading Berkshire, RG1 1AX United Kingdom or by Electronic Mail to: [email protected] ii Open Group Technical Standard (1999) Contents Chapter 1 The DRDA Specification................................................................... 1 1.1 The DRDA Reference................................................................................
    [Show full text]
  • Windows Release 8206
    WebFOCUS and ReportCaster Installation and Configuration for Windows Release 8206 July 29, 2020 Active Technologies, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iWay, iWay Software, Parlay, PC/FOCUS, RStat, Table Talk, Web390, WebFOCUS, WebFOCUS Active Technologies, and WebFOCUS Magnify are registered trademarks, and DataMigrator and Hyperstage are trademarks of Information Builders, Inc. Adobe, the Adobe logo, Acrobat, Adobe Reader, Flash, Adobe Flash Builder, Flex, and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Due to the nature of this material, this document refers to numerous hardware and software products by their trademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by their respective companies. It is not this publisher's intent to use any of these names generically. The reader is therefore cautioned to investigate all claimed trademark rights before using any of these names other than to refer to the product described. Copyright © 2019, by Information Builders, Inc. and iWay Software. All rights reserved. Patent Pending. This manual, or parts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc. Contents Preface ......................................................................... 9 Conventions ........................................................................10 Related Publications .................................................................11
    [Show full text]
  • Oracle Database Gateway for DRDA User's Guide Is Included As Part of Your Product Shipment
    Oracle® Database Gateway for DRDA User’s Guide 11g Release 1 (11.1) B31046-01 June 2007 Oracle Database Gateway for DRDA User’s Guide, 11g Release 1 (11.1) B31046-01 Copyright © 2004, 2007, Oracle. All rights reserved. Primary Author: Maitreyee Chaliha Contributing Author: Denis Raphaely, Peter A. Castro The Programs (which include both the software and documentation) contain proprietary information; 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, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. This document is not warranted to be 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. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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).
    [Show full text]
  • Systems Programmer's Guide To
    Front cover Systems Programmer’s Guide to Resource Recovery Services (RRS) Managing, optimizing, and sizing RRS environments Restart and recovery with RRS How exploiters can get the most out of RRS Paola Bari Frank Kyne Alan Murphy ibm.com/redbooks International Technical Support Organization Systems Programmer’s Guide to Resource Recovery Services (RRS) November 2004 SG24-6980-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (November 2004) This edition applies to Version 1, Release 4 of z/OS (product number 5694-A01, 5655-G52). © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . .x Comments welcome. .x Part 1. Resource Recovery Services (RRS) introduction and concepts . 1 Chapter 1. Introduction to Resource Recovery Services (RRS) . 3 1.1 Transactions . 4 1.2 Resource managers and protected resources . 5 1.3 The role of Resource Recovery Services (RRS). 6 1.3.1 Who uses RRS . 7 Chapter 2. Two-phase commit and RRS . 9 2.1 Introduction to two-phase commit . 10 2.2 Two-phase commit as supported by legacy resource managers . 13 2.2.1 CICS . 14 2.2.2 IMS . 15 2.2.3 DB2 . 15 2.3 How RRS works . 16 2.3.1 Registration services. 16 2.3.2 Context services . 17 2.3.3 RRS invocation .
    [Show full text]
  • TRM) Para Telconet Cloud Center
    UNIVERSIDAD TÉCNICA PARTICULAR DE LOJA La Universidad Católica de Loja ÁREA TÉCNICA TÍTULO DE INGENIERO EN INFORMÁTICA Definición de un modelo técnico de referencia (TRM) para Telconet Cloud Center. TRABAJO DE TITULACIÓN AUTOR: Cabrera Burgos, Xavier Antonio. DIRECTOR: Cabrera Silva, Armando Augusto, MSc. CENTRO UNIVERSITARIO GUAYAQUIL 2018 Esta versión digital, ha sido acreditada bajo la licencia Creative Commons 4.0, CC BY-NY- SA: Reconocimiento-No comercial-Compartir igual; la cual permite copiar, distribuir y comunicar públicamente la obra, mientras se reconozca la autoría original, no se utilice con fines comerciales y se permiten obras derivadas, siempre que mantenga la misma licencia al ser divulgada. http://creativecommons.org/licenses/by-nc-sa/4.0/deed.es 2018 APROBACIÓN DEL DIRECTOR DEL TRABAJO DE TITULACIÓN MSc. Armando Augusto Cabrera Silva. DOCENTE DE LA TITULACIÓN De mi consideración: El presente trabajo titulación: “Definición de un modelo de referencia técnica (TRM) para Telconet Cloud Center”, realizado por Xavier Antonio Cabrera Burgos ha sido orientado y revisado durante su ejecución, por cuanto se aprueba la presentación del mismo. Loja, agosto de 2018 f) ………………………………………….. MSc. Cabrera Silva, Armando Augusto ii DECLARACIÓN DE AUTORÍA Y CESIÓN DE DERECHOS “Yo, Cabrera Burgos Xavier Antonio declaro ser autor del presente trabajo de titulación: “Definición de un modelo técnico de referencia (TRM) para Telconet Cloud Center” de la Titulación en Informática, siendo el MSc. Armando Augusto Cabrera Silva director del presente trabajo; y eximo expresamente a la Universidad Técnica Particular de Loja y a sus representantes legales de posibles reclamos o acciones legales. Además, certifico que las ideas, conceptos, procedimientos y resultados vertidos en el presente trabajo investigativo, son de mi exclusiva responsabilidad.
    [Show full text]
  • DB2 for Z/OS: Configuring TLS/SSL for Secure Client/Server Communications
    IBM Information Management Software Redpaper Chris Meyer Paolo Bruni DB2 for z/OS: Configuring TLS/SSL for Secure Client/Server Communications Introduction This IBM® Redpaper™ publication provides information about how to set up and configure IBM DB2® for z/OS® with Transport Layer Security (TLS), the modern version of Secure Sockets Layer (SSL). This configuration is accomplished using the IBM z/OS Communications Server Application Transparent Transport Layer Security (AT-TLS) services. This paper also describes the steps for configuring TLS/SSL support for the IBM Data Server Driver Package (DS Driver) for IBM Data Server Provider for .NET, Open Database Connectivity (ODBC), and call level interface (CLI) clients to access a DB2 for z/OS server. In addition, this paper provides information about configuring that same support for the Java Database Connectivity (JDBC) and Structured Query Language for Java (SQLJ for Type 4 connectivity) clients. The information provided is applicable to DB2 11 for z/OS and DB2 10 for z/OS. Although we use z/OS V2R1 as the reference release in this paper, the instructions are valid on releases as early as z/OS V1R11. Throughout the paper, we reference z/OS Security Server, or IBM Resource Access Control Facility (IBM RACF®) in a variety of contexts. It should be understood that anywhere we mention RACF, it implies any System Authorization Facility (SAF) external security manager. The intended audience for this paper includes network administrators, security administrators, and database administrators who want to set up and configure TLS/SSL support for DB2 for z/OS. This paper provides information about the following topics: Overview of AT-TLS Configuring DB2 for z/OS as a server with TLS/SSL support Configuring DB2 for z/OS as a requester with TLS/SSL support © Copyright IBM Corp.
    [Show full text]
  • IBM Informix Developer's Handbook
    Front cover IBM Informix Developer’s Handbook Learn application development with supported APIs, drivers, and interfaces Understand Informix supported programming environments Follow practical examples to develop an Informix application Whei-Jen Chen Krishna Doddi Manoj Ghogale David Jay Javier Sagrera ibm.com/redbooks International Technical Support Organization IBM Informix Developer’s Handbook October 2010 SG24-7884-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (October 2010) This edition applies to IBM Informix Version 11.5. © Copyright International Business Machines Corporation 2010. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . x Preface . xi The team who wrote this book . xi Acknowledgements . xiii Now you can become a published author, too! . xiii Comments welcome. xiv Stay connected to IBM Redbooks . xiv Chapter 1. Introduction to IBM Informix . 1 1.1 Server options . 2 1.1.1 Informix servers. 2 1.2 Informix tools for developers . 9 1.2.1 Informix Connect . 9 1.2.2 Informix Client Software Development Kit. 9 1.2.3 4GL . 15 1.2.4 Ruby on Rails . 15 1.2.5 Informix DataBlade Developers Kit . 15 1.2.6 Informix Spatial DataBlade . 16 1.2.7 PHP on Informix . 17 1.3 Informix overview . 17 1.3.1 Architecture overview . 18 1.3.2 Informix developer environment . 21 1.3.3 Informix capabilities. 22 Chapter 2. Setting up an Informix development environment . 25 2.1 Server setup .
    [Show full text]
  • IBM Systems - Iseries
    IBM Systems - iSeries UNIX-Type -- XA APIs Version 5 Release 4 IBM Systems - iSeries UNIX-Type -- XA APIs Version 5 Release 4 Note Before using this information and the product it supports, be sure to read the information in “Notices,” on page 45. Sixth Edition (February 2006) This edition applies to version 5, release 4, modification 0 of IBM i5/OS (product number 5722-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. © Copyright International Business Machines Corporation 1998, 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents XA APIs . .1 Example . .20 Restrictions . .2 xa_prepare()— Prepare to Commit an XA Supported Database Interfaces . .2 Transaction Branch (Transaction Scoped Locks) . .21 Considerations for Remote Databases . .3 Parameters . .21 SQL Server Mode . .3 Authorities . .21 User Profiles . .3 Return Value . .21 Autocommit . .4 Error Messages . .22 APIs . .4 Related Information . .23 XA APIs for Transaction Scoped Locks . .4 Example . .23 xa_close()— Close an XA Resource Manager xa_recover()— Recover XA Transaction Branches (Transaction Scoped ,Locks) . .7 (Transaction Scoped Locks) . .23 Parameters . .7 Parameters . .23 Authorities . .7 Authorities . .24 Return Value . .8 Return Value . .24 Error Messages . .8 Error Messages . .24 Related Information . .8 Related Information . .24 Example . .8 Example . .24 xa_commit()— Commit an XA Transaction Branch xa_rollback()— Roll Back an XA Transaction Branch (Transaction Scoped Locks . .9 (Transaction Scoped Locks) . .25 Parameters . .9 Parameters .
    [Show full text]
  • The DRDA Specification
    Technical Standard DRDA, Version 4, Volume 1: Distributed Relational Database Architecture (DRDA) The Open Group ©February 2007, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. This documentation and the softwaretowhich it relates arederived in part from copyrighted materials supplied by International Business Machines. Neither International Business Machines nor The Open Group makes any warranty of any kind with regardtothis material, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The Open Group shall not be liable for errors contained herein, or for any direct or indirect, incidental, special, or consequential damages in connection with the furnishing, performance, or use of this material. Technical Standard DRDA, Version 4, Volume 1: Distributed Relational Database Architecture(DRDA) ISBN: 1-931624-70-4 Document Number: C066 Published in the U.K. by The Open Group, February 2007. Any comments relating to the material contained in this document may be submitted to: The Open Group Thames Tower 37-45 Station Road Reading Berkshire, RG1 1LX United Kingdom or by Electronic Mail to: [email protected] ii Technical Standard (2007) Contents Chapter 1 The DRDA Specification ................................................................ 1 1.1 The DRDA Reference .............................................................................. 2 1.1.1 What it Means to Implement Different Levels of DRDA ............... 2 1.1.2 What it Means to Implement DRDA Level 6 ................................... 3 1.1.3 What it Means to Implement DRDA Level 5 ..................................
    [Show full text]
  • Open Group Standard
    Open Group Standard DRDA, Version 5, Volume 1: Distributed Relational Database Architecture (DRDA) The Open Group ©July 2011, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. This documentation and the softwaretowhich it relates arederived in part from copyrighted materials supplied by International Business Machines. Neither International Business Machines nor The Open Group makes any warranty of any kind with regardtothis material, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The Open Group shall not be liable for errors contained herein, or for any direct or indirect, incidental, special, or consequential damages in connection with the furnishing, performance, or use of this material. Open Group Standard DRDA, Version 5, Volume 1: Distributed Relational Database Architecture(DRDA) ISBN: 1-931624-91-7 Document Number: C112 Published in the U.K. by The Open Group, July 2011. Any comments relating to the material contained in this document may be submitted to: The Open Group Apex Plaza Forbury Road Reading Berkshire, RG1 1AX United Kingdom or by Electronic Mail to: [email protected] ii Open Group Standard (2011) Contents Chapter 1 The DRDA Specification ................................................................ 1 1.1 The DRDA Reference .............................................................................. 2 1.1.1 What it Means to Implement Different Levels of DRDA ..................................................................................................... 2 1.1.2 What it Means to Implement DRDA Level 7 ................................... 3 1.1.3 What it Means to Implement DRDA Level 6 ..................................
    [Show full text]
  • Open Group Standard
    Open Group Standard DRDA, Version 5, Volume 3: Distributed Data Management (DDM) Architecture The Open Group ©July 2011, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. This documentation and the softwaretowhich it relates arederived in part from copyrighted materials supplied by International Business Machines. Neither International Business Machines nor The Open Group makes any warranty of any kind with regardtothis material, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The Open Group shall not be liable for errors contained herein, or for any direct or indirect, incidental, special, or consequential damages in connection with the furnishing, performance, or use of this material. Open Group Standard DRDA, Version 5, Volume 3: Distributed Data Management (DDM) Architecture ISBN: 1-931624-93-3 Document Number: C114 Published in the U.K. by The Open Group, July 2011. Any comments relating to the material contained in this document may be submitted to: The Open Group Apex Plaza Forbury Road Reading Berkshire, RG1 1AX United Kingdom or by Electronic Mail to: [email protected] ii Open Group Standard (2011) Contents Chapter 1 The DRDA Specification ................................................................ 1 1.1 DRDA Reference ....................................................................................
    [Show full text]