2 options
Integrating DB2 Universal Database for iSeries with Microsoft ADO.NET / Hernando Bedoya ... [et al.
- Format:
- Book
- Author/Creator:
- Bedoya, Hernando., Author.
- Series:
- IBM redbooks.
- Redbooks
- Language:
- English
- Subjects (All):
- Database management.
- Microsoft .NET.
- Client/server computing.
- IBM Database 2.
- Physical Description:
- xii, 270 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- Rochester, MN : IBM Corp., International Technical Support Organization, c2005.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Background
- Chapter 1. Introduction to DB2 UDB for iSeries
- 1.1 An integrated relational database
- 1.2 DB2 UDB for iSeries: an overview
- 1.2.1 DB2 UDB for iSeries basics
- 1.3 Connectivity options to DB2 UDB for iSeries
- 1.3.1 Multiplatform connectivity
- 1.3.2 Windows platform connectivity
- 1.4 DB2 UDB for iSeries sample schema
- Chapter 2. Introduction to the Microsoft .NET framework
- 2.1 Description of .NET
- 2.1.1 Architecture
- 2.1.2 Platform support
- 2.2 Common Language Runtime (CLR)
- 2.2.1 Runtime execution environment
- 2.3 Class libraries
- Chapter 3. ADO .NET object hierarchy
- 3.1 Overview of ADO .NET
- 3.1.1 Connection
- 3.1.2 Command
- 3.1.3 DataReader
- 3.1.4 DataAdapter
- 3.1.5 DataSet
- 3.2 Connected mode
- 3.3 Disconnected mode
- Part 2 Providers
- Chapter 4. IBM DB2 UDB for iSeries .NET provider
- 4.1 Introduction
- 4.2 IBM.Data.DB2.iSeries architecture
- 4.2.1 ADO.NET interfaces
- 4.2.2 Host server jobs
- 4.2.3 Supported features
- 4.2.4 Unsupported features
- 4.3 Before we begin
- 4.3.1 PC setup
- 4.3.2 Host setup
- 4.4 Getting started
- 4.4.1 Displaying the technical reference
- 4.4.2 Starting Visual Studio .NET
- 4.4.3 Adding an assembly reference to the provider
- 4.4.4 Adding a namespace directive
- 4.5 Provider basics
- 4.5.1 A simple connection example
- 4.5.2 iDB2Connection and ConnectionString properties
- 4.5.3 iDB2Command properties and methods
- 4.5.4 Using parameters in your SQL statements
- 4.5.5 Calling stored procedures
- 4.5.6 Choosing your execute method
- 4.5.7 Provider data types
- 4.5.8 Handling exceptions
- 4.6 Common tasks
- 4.6.1 A DataReader example.
- 4.6.2 A simple DataAdapter with CommandBuilder example
- 4.6.3 Using transactions
- 4.6.4 Calling a program by wrapping it in a stored procedure
- 4.6.5 Calling a program or CL command using QCMDEXC
- 4.6.6 Choosing between iDB2DataReader and iDB2DataAdapter
- 4.7 Advanced topics
- 4.7.1 Internationalization and support for multiple languages
- 4.7.2 Using large objects (LOBs)
- 4.7.3 Updating DataSets
- 4.7.4 Using iDB2CommandBuilder
- 4.7.5 Using DataLinks
- 4.7.6 Connection pooling
- 4.7.7 Deploying your application
- 4.8 Coding for performance and best practices
- 4.9 Migrating from ADO and OLE DB to ADO.NET
- 4.9.1 ADO objects and how they map to ADO.NET objects
- 4.9.2 ADO recordsets versus ADO.NET DataReaders and DataAdapters
- 4.9.3 Updating tables
- 4.9.4 Mapping OLE DB properties to ADO.NET
- 4.9.5 Examples showing an OLE DB application rewritten to use ADO.NET
- 4.10 Troubleshooting
- 4.10.1 Handle exceptions using try/catch blocks
- 4.10.2 Make sure your server jobs are running
- 4.10.3 Use provider traces via the cwbmptrc utility
- 4.10.4 Enable server-side diagnostics
- 4.10.5 Use communication traces via the cwbcotrc utility
- 4.10.6 Overriding your ConnectionString
- 4.10.7 Gathering information for IBM Support
- 4.11 Writing code for provider independence
- 4.11.1 Writing provider-independent code with ADO.NET 1.0 and 1.1
- 4.11.2 Writing provider-independent code with ADO.NET 2.0
- Chapter 5. IBM DB2 for LUW .NET provider
- 5.1 DB2 Connect overview
- 5.2 Installing and configuring DB2 Connect
- 5.2.1 Host server jobs
- 5.2.2 Prerequisites
- 5.2.3 Installation procedure
- 5.2.4 Connecting to an iSeries database
- 5.3 IBM DB2 Development Add-In overview
- 5.3.1 Registering the IBM DB2 Development Add-In
- 5.3.2 Unregistering the IBM DB2 Development Add-In
- 5.3.3 DB2 Toolbar.
- 5.3.4 DB2 Database Project type
- 5.3.5 IBM Explorer
- 5.4 IBM DB2 data controls
- 5.5 LUW provider features
- 5.5.1 Classes to implement ADO.NET interfaces
- 5.5.2 Data types
- 5.5.3 Unsupported features
- 5.6 Getting started
- 5.6.1 Starting Visual Studio .NET
- 5.6.2 Displaying the technical reference
- 5.6.3 Adding an assembly reference to the provider
- 5.6.4 Adding a namespace directive
- 5.6.5 Using the DB2Connection object and the ConnectionString
- 5.6.6 Using the DB2Command object
- 5.6.7 Using the DB2DataReader object
- 5.6.8 Using the DB2DataAdapter object
- 5.7 Advanced topics
- 5.7.1 Using large objects (LOBs)
- 5.7.2 Using the DB2CommandBuilder object
- 5.7.3 Performing transactions
- 5.8 Best practices
- 5.8.1 Connection pooling
- Chapter 6. Selecting the .NET provider
- 6.1 ODBC .NET Data Provider
- 6.2 OLE DB .NET Data Provider
- 6.3 Provider performance
- 6.4 Conclusions
- Part 3 Scenarios
- Chapter 7. ASP .NET scenario (Web forms)
- 7.1 An overview of ASP.NET
- 7.1.1 ASP .NET Web page (Web form)
- 7.1.2 How does ASP .NET work?
- 7.1.3 Configuration files in ASP .NET
- 7.2 Web controls
- 7.3 Using the IBM DB2 UDB for iSeries .NET provider
- 7.4 Using the IBM DB2 for LUW .NET provider
- Appendix A. Sample programs
- Samples for the IBM DB2 UDB for iSeries .NET provider
- Sample for the IBM DB2 for LUW .NET provider
- Appendix B. Additional material
- Locating the Web material
- Using the Web material
- System requirements for downloading the Web material
- How to use the Web material
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.
- Notes:
- "This edition applies to Version 5, Release 3, Modification 0 of OS/400 (product number 5722-SS1)."
- "April 2005."
- Includes bibliographical references and index.
- OCLC:
- 61446969
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.