IBM DB2 UNIVERSAL DATABASE
UDB 侮欺蚊泗绥恸
Fixpak 16
 
 
(C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001.
    ALL RIGHTS RESERVED.
 
 
  气蜱
 
 
| 弦损祁 DB2 Universal Database Fixpak 16!
| Fixpak 16 嘻浠收
 
  1.0  种杀蚊泗绥恸
| 1.1  FixPak 6 韦侪骜毓
| 1.2  Fixpak 16 韦侪骜毓
  1.3  塄新曦韦侪世荽篁争栈
| 1.4  DB2 龌阵暖 FixPak 牌堑
| 1.5  ≈Web 谡瘫你爬∽区嬉
  1.6  DB2 朔悄浠毓
 
  2.0  ADMINISTRATION GUIDE (欺阵栖你牌脓)
  2.1  Implementing Your Design
|   2.1.1  Creating a Database/Creating a Summary Table
      2.1.1.1  Isolation Levels and Query Optimization Using Summary Tables
       or Replicated Tables
|     2.1.1.2  REFRESH IMMEDIATE
    2.1.2  Optimizing Performance When Data is Placed on RAID Devices
| 2.2  Controlling Database Access
|   2.2.1  DRDA-only Client Authentication
|   2.2.2  Change Password Enablement for EEE
|   2.2.3  Encrypted Passwords
|   2.2.4  Loginretries Option (AIX only)
  2.3  Auditing DB2 Activities
  2.4  Utilities for Moving Data
    2.4.1  LOAD, IMPORT, and EXPORT File Formats/PC/IXF File Formats/Code
     Page Considerations
|   2.4.2  Overview of the LOAD Process (Pending States)
    2.4.3  Load Restriction on Windows NT and OS/2 SMP-enabled Machines
|   2.4.4  Error Scenario for the Autoloader Program on DB2 UDB Enterprise
|    - Extended Edition for Windows NT
|   2.4.5  Changes in Autoloader Authentication Behavior
|   2.4.6  Import/Export of WSF Data Containing BIGINT
  2.5  Recovering a Database
    2.5.1  Backing Up and Restoring Databases on Different Operating
     Systems
    2.5.2  Considerations for Using ADSTAR Distributed Storage Manager
     (ADSM)
|   2.5.3  Configuration Parameters for Database Logging
|   2.5.4  Frequency of Backups and Time Required
    2.5.5  Recovering a Database (Planning to Use the ROLLFORWARD Command)
| 2.6  Using DB2 with an XA-Compliant Transaction Manager
| 2.7  Application Considerations
| 2.8  Understanding the SQL Compiler
  2.9  Operational Performance
|   2.9.1  Managing the Database Buffer Pool
    2.9.2  Managing Multiple Database Buffer Pools
| 2.10  Using the Governor
  2.11  Configuring DB2
|   2.11.1  Encrypted Passwords
    2.11.2  Tuning Configuration Parameters/Optimizing Hash Join
     Performance
|   2.11.3  Database Log Files
|   2.11.4  Trusted Clients and DRDA Use
|   2.11.5  Loginretries Option (AIX only)
    2.11.6  ASLHEAPSZ and Failed Queries Against Large Tables
    2.11.7  INTRA_PARALLEL Setting on an SMP Machine (Windows NT)
| 2.12  HACMP ES for AIX
| 2.13  DB2 Registry and Environment Variables
  2.14  Additional Rah (Run All Hosts) Information (Solaris and AIX only)
| 2.15  Unicode/UCS-2 and UTF-8 Support in DB2 UDB
|   2.15.1  Introduction
|     2.15.1.1  UTF-8
|   2.15.2  UCS-2/UTF-8 Implementation in DB2 UDB
|     2.15.2.1  Code Page/CCSID Numbers
|     2.15.2.2  Creating a UCS-2 Database
|     2.15.2.3  Data Types
|     2.15.2.4  Identifiers
|     2.15.2.5  UCS-2 Literals
|     2.15.2.6  Pattern Matching in a UCS-2 Database
|     2.15.2.7  IMPORT/EXPORT/LOAD Considerations
|     2.15.2.8  Incompatibilities
| 2.16  Using Virtual Interface (VI) Architecture
|   2.16.1  Overview of Virtual Interface Architecture
|   2.16.2  Install DB2 Universal Database Version 5.2 (EEE)
|   2.16.3  Running DB2 UDB V5.2 for Windows NT with GigaNet Interconnect
|     2.16.3.1  Setup Procedure for GigaNet Interconnect
|     2.16.3.2  Implement DB2 to Run Using VI
|   2.16.4  Running DB2 UDB V5.2 for Windows NT with ServerNet Interconnect
|     2.16.4.1  Setup Procedure for ServerNet Interconnect
|     2.16.4.2  Implement DB2 to Run Using VI
 
  3.0  API REFERENCE (欺阵栖你牌脓)
  3.1  sqlecrea - Create Database
  3.2  sqlubkp - Backup Database
  3.3  sqlugtpi - Get Table Partitioning Information
  3.4  sqluhget - Retrieve DDL Information From the History File (New API)
  3.5  sqluhgne - Get Next Recovery History File Entry
  3.6  sqluhops - Open Recovery History File Scan
  3.7  sqluload - Load
  3.8  SQLE-CLIENT-INFO (Connection Settings)
  3.9  SQLFUPD
  3.10  SQLUHINFO (SQLUHADM)
  3.11  sqluvput - Writing Data to Device
 
  4.0   怃圊 WINDOWS 暖 OS/2 艨韬嘻筌祁幔娶
| 4.1  WINDOWS NT 母嘻 DB2START 属却惝沁七睚嘻蜚毹毓丈
  4.2  喧弭 WINDOWS NT 滔 WINDOWS 95 涅芍嘻 SQL 筌祁幔娶 (IBM
       VISUALAGE FOR COBOL)
  4.3  喧弭 JAVA 筌祁幔娶滔 APPLETS
    4.3.1  菝贴 MICROSOFT SDK FOR JAVA 嘻 WINDOWS 艨韬
|   4.3.2  浠嘻诜谆暖腮韦鹇幔娶曦 AND SQLJ 些弭罹嘻 SCRIPT
 
  5.0  喧弭 UNIX 艨韬嘻筌祁幔娶
  5.1  SCO UnixWare 7
|   5.1.1  憔砒竺囚幔施嘻酞戆
    5.1.2  MICRO FOCUS COBOL 岣蛸恸
  5.2  喧弭 Java 筌祁幔娶暖 Applets
    5.2.1  菝贴艨韬〃HP-UX, SCO UnixWare 7
|   5.2.2  CLOSE() 派挝嘻 SILICON GRAPHICS IRIX 宇瘫
    5.2.3  浠嘻诜谆暖腮韦鹇幔娶曦 AND SQLJ 些弭罹嘻 SCRIPT
 
  6.0  CLI GUIDE AND REFERENCE (欺阵栖你牌脓)
  6.1  SQLPREPARE()
  6.2  SQLDISCONNECT()
  6.3  Using Stored Procedures - Programming Stored Procedures To Return
   Result Sets
  6.4  Stored Procedure Catalog Tables
| 6.5  SQLFetchScroll(SQL_FETCH_RELATIVE, -1)
 
  7.0  COMMAND REFERENCE (欺阵栖你牌脓)
  7.1  db2cmd - Open DB2 Command Window
  7.2  db2eva - Event Analyzer
  7.3  db2evmon - Event Monitor Productivity Tool
  7.4  db2look - DB2 Statistics Extraction Tool
  7.5  db2set - DB2 Profile Registry Command
  7.6  db2upd52 - Update Catalog to Support Version 5.2
  7.7  BACKUP DATABASE
  7.8  EXPORT
  7.9  GET DATABASE MANAGER CONFIGURATION
    7.9.1  New Parameter catalog_noauth
|   7.9.2  TRUST_ALLCLNTS Updated
  7.10  IMPORT
  7.11  LIST DATABASE DIRECTORY
  7.12  LOAD
  7.13  RECONCILE
  7.14  RESTORE DATABASE
| 7.15  START DATABASE MANAGER
 
  8.0  EMBEDDED SQL PROGRAMMING GUIDE (欺阵栖你牌脓)
  8.1  Writing User-Defined Functions (Interface between DB2 and a UDF/The
   Arguments Passed from DB2 to a UDF)
  8.2  Programming in C and C++ (Programming Considerations/Host Variables)
    8.2.1  Declaring Host Variables
    8.2.2  Handling Graphic Host Variables (Windows Operating System)
| 8.3  Programming in COBOL (Host Structure Support)
  8.4  Programming in Java (Creating Java UDFs and Stored
   Procedures/Classes for Java Stored Procedures and UDFs)
  8.5  A JDK Problem That Affects JDBC Programs Running under a DBCS Code
   Page on AIX
  8.6  JDBC Sample Applications Restriction on SCO UnixWare 7
| 8.7  JDBC 2.0
| 8.8  Perl Access to DB2 UDB Databases
  8.9  DATALINK Data Type
  8.10  Multithreaded UNIX Applications Working with Code Page and Country
   Code
  8.11  Error Processing for UDF Call Types
    8.11.1  Scratchpad and Final Call Type Arguments for EXTERNAL TABLE
     Functions
|   8.11.2  External UDF Error Processing Model for Scalar Functions
| 8.12  NOT ATOMIC Compound SQL
  8.13  Other Revisions to the Book
    8.13.1  Revisions to Chapter 1
    8.13.2  Revisions to Chapter 4
    8.13.3  Revisions to Chapter 7
    8.13.4  Revisions to Chapter 9
    8.13.5  Revisions to Chapter 15
    8.13.6  Revisions to Sample Programs
    8.13.7  Other File Changes
 
  9.0  区嬉曦艳楝 DB2 诜谆
  9.1  损祁 CCA 艳楝诜谆摊 DB2 腮韦鹇嘻葑详
 
  10.0  毓丈俣澌
  10.1  DBI1768W 氅忘你嘻蜚毹
  10.2  SQL0270N 嘻呢收/抬破韵寝睿
  10.3  SQL0351N 嘻浠氅忘
  10.4  SQL0352N 嘻浠氅忘
  10.5  SQL0357N 嘻浠氅忘
  10.6  SQL0432N 嘻浠氅忘
  10.7  SQL0680N 嘻浠氅忘
  10.8  SQL0903N 嘻抬破韵寝睿
  10.9  SQL0911N 嘻抬破韵寝睿
  10.10  SQL1339N 嘻浠氅忘
  10.11  损祁收葑如睿排呶针砒堍嘻 SQL5048N 托 SQL0901N
| 10.12  浠毓丈 SQL5156N: DBM 艳楝俣戆 TRUST_ALLCLNTS 嘻垣
  10.13  SQL20053N 嘻抬破韵寝睿
  10.14  SQL20056N 嘻浠毓丈牌求
  10.15  SQL30083N 嘻抬破韵寝睿
 
  11.0  矢葳墨宪
  11.1  倾仝如 WINDOWS 95 嘻 NEC PC98 瘼鹇母区嬉 DB2
  11.2  倾仝如 WINDOWS 95 嘻 NEC PC98 瘼鹇母尕劓区嬉 DB2
  11.3  佑琚区嬉
    11.3.1  菰腈叔/腮韦鹇塄新腈叔
    11.3.2  王 OS/2 诜谆嘻诜谆塄新腈叔/菰腈叔
|   11.3.3  DBCS 艨韬逆 OS/2 WARP SERVER V.4 嘻谡瘫你爬腈叔
    11.3.4  DB2 FOR AS/400 容 DB2 UNIVERSAL DATABASE FOR AIX。OS/2。
            滔 WINDOWS NT 嘻 SNA 葙谫
|   11.3.5  倾茄摹远瘼鹇母、TP 秦辎倾 DB2 争梭逆你埔恻岩倌摹嘻
    11.3.6  菰强暑劬堑/DB2 FOR OS/390 喧嘻院七幔娶
  11.4  DB2 UNIVERSAL DATABASE 墨宪 (收葑如睿)
  11.5  DB2 UNIVERSAL DATABASE 墨宪 (佑戢 AIX 母嘻虽如损祁席)
  11.6  损祁争梭 (浠炝骜砧栈拧薮俅腮韦鹇摊争梭、损祁 DB2
  EXTENDED ENTERPRISE EDITION FOR WINDOWS NT/损祁韵填嬉弭嘻
  腚傺损祁席 ID 腈叔) 
| 11.7  NT 母嘻 DB2START 属却惝沁七睚嘻毓丈
  11.8  诜鳟侮欺滔侮裙苊魉
| 11.9  诜 DB2 侮裙 5.0 弄兹摊侮裙 5.2
| 11.10  LOTUS DOMINO GO WEB 腮韦鹇嘻 DB2 侬幔娶蜚毹
  11.11  仝如溶淖嘻筌祁幔娶 (仝如 JAVA 幔娶)
  11.12  DB2 塄新嘻涅诈 (耄似艨韬嘻翥煅)
 
  12.0  DB2 File Manager 矢葳墨宪
| 12.1  诜谆艳楝憔墨暖憔砒
| 12.2  DB2 DATA LINKS MANAGER 嘁挝区嬉倾 DB2 ENTERPRISE -
|  Extended Edition 朔苡母
  12.3  DLFM 戋堋损祁席 ID
  12.4  损祁 NFS 唆囚探肟軎 DLFS 篁争朔苡
  12.5  王 DATALINKS 诜谆嘻宇瘫
  12.6  DLFM 呢收嘻菝弭蛸恸
  12.7  倾篁争戋堋幔娶腮韦鹇母诜轹轺浯溱你沁擀
| 12.8  蕃枪嘻骜砧岣戆 (DL_NUM_BACKUP)
  12.9  DB2 File Manager 沁擀枰侪畀梭
  12.10  嘁挝诜淘棚如莰堋鹇 (CLP) 喧恰托院恃骜砧岣艳楝篁
 
  13.0  侮欺 5.2 逆些驮卮绁嘻≈矢葳墨宪∽收
  13.1  DB2 塄新
  13.2  佑琚区嬉
    13.2.1  OS/2 菰腈叔
      13.2.1.1  偏如嘻诜谆摊腮韦鹇葙葑吞
    13.2.2  NetFinity 排呶幔娶埔恻佤畔 - Windows NT
    13.2.3  Communications Server for Windows NT - 腈友院七幔娶
    13.2.4  喧拧薮骜砧栈嘻损祁席衮 Client Application Enabler 弄兹
    13.2.5  喧 Windows ODBC 嘻损祁席衮 Client Application Enabler 弄兹
    13.2.6  AIX 母 ADSM 喧嘻院七幔娶煲裙
    13.2.7  CS/NT 枳王倾 Windows NT 母嘻胎怅阳睚贴排呶岩埔友嘻
      13.2.7.1  圄卮 CS/NT 散页 Windows NT 韦侪幔娶
    13.2.8  WINDOWS NT 暖 WINDOWS 95 母嘻 DCE 排呶
|   13.2.9  喧嘻 WINDOWS NT 煲裙
    13.2.10  SYSADM 宇嘻仵菝 (UNIX)
  13.3  抬破区嬉曦艳楝散淦
    13.3.1  艳楝 CS/NT 峥≈茄抒龅戋堋幔娶∽(SPM)
      13.3.1.1  王损祁 SNA SPM 嘻厢披骜毓
|   13.3.2  爨 AIX 侮欺 4.1.4 暖 4.1.5 母嘻 NIS 损祁席嘻俾黝
    13.3.3  db2cpic.dll - WINDOWS NT 暖 WINDOWS 95 母嘻瞿膨 SNA 瘼亠
            像幔娶睿
    13.3.4  祁王 Windows NT 嘻 DB2NTMEMSIZE 菝贴篁戆
  13.4  谡瘫你爬嘻 SNAPSHOT 轳迤幔娶
  13.5  诜 Web 囚探 DB2 骜砧
  13.6  倾 RS/6000 SP 母菝贴杲纣肄俣戆
  13.7  倾拧薮骜砧栈艨韬你菝贴 CCA 滔谡瘫你爬 (DB2 UNIVERSAL
        DATABASE EXTENDED ENTERPRISE EDITION FOR AIX)
  13.8  诜鳟侮苊魉 (UNIX)
  13.9  DB2 SNMP 耐蓬堋幔娶
  13.10  侮欺 5.2 逆些驮卮绁嘻≈矢葳墨宪∽收
  13.11  戋堋滔损祁 OS/2 损祁席菝贴篁戋堋
  13.12  倾 SOLARIS 母枳王 EEE 嘻 ADSM 诜谆菝弭 - 损祁 db2profile
  13.13  诜 DB2 FOR OS/390 侮欺 5 葙谫摊 DB2 UNIVERSAL DATABASE 侮欺 5
  13.14  倾 WINDOWS NT 腮韦鹇母艳楝 NETBIOS
  13.15  橇祁卮鹳软蛇 - Windows NT 托 Windows 95
  13.16  仝如 DB2 JDBC APPLET 腮韦鹇宓散 WINDOWS NT 韦侪幔娶
  13.17  探诘骜毓
    13.17.1  罾母尕氅
    13.17.2  DB2 龌阵
    13.17.3  悄峭 PostScript 阵
    13.17.4  篝狺罾母阵
    13.17.5  菝贴牌堑腮韦鹇
    13.17.6  洳掾罾母阵
  13.18  Microsoft Internet Explorer 4.0 HTTP 1.1 菝贴
  13.19  王损祁谡瘫你爬诜肟軎戋堋龌怩嘻蚊泗绥恸
 
  14.0  REPLICATION 牙胁曦俣澌
  14.1  浠排呶嘻仆坪
  14.2  浠毓丈
  14.3  DB2 UDB 侮欺 5.2 嘻鍪探幔娶排呶逆 LONG VARCHAR
| 14.4  DataJoiner Replication Administration Tool README
 
  15.0  DB2 幔娶菝佑牙胁
  15.1  王 Application Developer's Kit
 
  16.0  SQL REFERENCE (欺阵栖你牌脓)
| 16.1  Naming Conventions (cursor-name)
| 16.2  ALTER TABLE
| 16.3  Compound SQL
  16.4  CREATE FUNCTION
    16.4.1  DBINFO
|   16.4.2  Error Processing for UDF Call Types
| 16.5  CREATE TABLE
|   16.5.1  CREATE TABLE Description
|   16.5.2  CREATE TABLE Notes
| 16.6  CREATE TABLESPACE
  16.7  Appendix A. SQL Limits/Database Manager Limits
 
  17.0  SYSTEM MONITOR GUIDE AND REFERENCE (欺阵栖你牌脓)
  17.1  Event Monitors are Created with Local Scope
 
  18.0  浠种吞
| 18.1  真卒 (宴骀/栩友闲知)
| 18.2  喧弭 JAVA 筌祁幔娶暖 APPLETS 收浠
  18.3  WEB 谡瘫你爬滔 NETQUESTION (邛祁 WEB 谡瘫你爬肟軎牌堑洳掾)
  18.4  ≈谡瘫你爬∽嘻宇瘫
| 18.5  ≈Web 谡瘫你爬∽嘻 JAVA DEVELOPMENT KIT 煲裙
 
  19.0  OS/2 侮嘻 HTML 洳掾腮韦鹇〃洳掾 HTML 牌堑
  19.1  倾 OS/2 母区嬉 HTML 洳掾朔苡
    19.1.1  OS/2 母洳掾朔苡嘻强暑劬堑
    19.1.2  倾 OS/2 母艳楝 TCP/IP
    19.1.3   TCP/IP 艳楝
    19.1.4  掾势洳掾朔苡气蜱
    19.1.5  收洳掾腮韦鹇嘻僬胬
    19.1.6  猬鏊洳掾腮韦鹇区嬉蜚毹
  19.2  损祁 HTML 洳掾朔苡
    19.2.1  邛侬滔佤畔洳掾腮韦鹇
    19.2.2  泞鏊杲纣葙罾针洳掾
    19.2.3  势拟摊篁争嘻蜚毹
    19.2.4  邱为洳掾嘁真 (蜚毹 500 圊祈王瑭孳洳掾针)
    19.2.5  邛侬洳掾韦侪幔娶针佝嗔摊蜚毹
  19.3  尕劓区嬉 HTML 洳掾朔苡
    19.3.1  倾 OS/2 母尕劓区嬉洳掾朔苡嘻俾黝
 
  20.0  WINDOWS NT。WINDOWS 95 暖 WINDOWS 98 侮嘻 HTML 洳掾腮韦鹇〃
        洳掾 HTML 牌堑
  20.1  祁挝宇瘫
  20.2  倾 WINDOWS NT。WINDOWS 95。滔 WINDOWS 98 母区嬉 HTML 洳掾朔苡
    20.2.1  洳掾朔苡嘻强暑劬堑
    20.2.2  佤畔强些区嬉嘻洳掾朔苡侮欺
    20.2.3  掾势洳掾朔苡气蜱
    20.2.4  收页洳掾腮韦鹇嘻抬破僬胬
    20.2.5  倾 LAN 葙谫嘻轹轺瘼母区嬉 DB2 UNIVERSAL DATABASE
    20.2.6  猬鏊洳掾腮韦鹇区嬉蜚毹
  20.3  损祁 HTML 洳掾朔苡
    20.3.1  邛侬滔佤畔腮韦鹇
    20.3.2  洳掾针 NETSCAPE 托 INTERNET EXPLORER 你呢邛祁 PROXIES
    20.3.3  倾钗母形缳妾嘻 WINDOWS 95 你洳掾
    20.3.4  邱为洳掾嘁真 (蜚毹 500 圊祈王瑭孳洳掾针)
    20.3.5  势拟摊篁争嘻蜚毹
    20.3.6  邛侬洳掾韦侪幔娶针佝嗔摊蜚毹
  20.4  20.4  尕劓区嬉 HTML 洳掾朔苡
    20.4.1  邱为洳掾朔苡栖诜 WINDOWS NT。WINDOWS 95 托 WINDOWS 98
            尕劓区嬉
    20.4.2  尕劓区嬉塄新靴屿浠怃瘼
 
| 21.0  NETQUESTION 枰梭
| 21.1  倾 UNIX 仆坪母区嬉 IMNSEARCH (NETQUESTION) 嘻俾黝
| 21.2  倾 HPUX-10 母区嬉 NetQuestion
| 21.3  UNIX 仆坪 嘻 NETQUESTION 暖 DB2 CAE
| 21.4  AIX 仆坪母嘻 NETQUESTION DBCS
 
  22.0  SCOHELP 骜毓
  22.1  邱若囚探 SCOhelp
  22.2  损祁傧榨耄似滔 SCOHELP
    22.2.1  损祁乳州袍耄似瞿膨针嘻种直扔庳
    22.2.2  倾腮韦鹇母收邕菝 SCOHELP 耄似
    22.2.3  菝贴 SCOHELP 剀枳种贴诜谆惝沁嘻耄似
    22.2.4  损祁洳掾
  22.3  WEB 谡瘫你爬尕氅滔 SCOHELP
  22.4  Support Level Supplement (SLS) PTF7004A, the UnixWare 7 Language
   Extension Supplement
    22.4.1  院恃鳇你牌滔呕乳婀犭袍耄嘻 LANG.CONF
  22.5  SCOhelp 洳掾啄趴篁争
 
 
| 弦损祁 DB2 Universal Database Fixpak 16—
 
  蕃狻〃  铢衮求形菝贴页尢饬、盆派享篝狺菡髓≈侮欺蚊泗绥恸∽·
 
| 欺 README 篁芍却 DB2 琶捧圊如针烃栖呷蓑逆 Fixpak 16 嘻侮裙骜毓·
| 破岩岂盆菡远浠骜毓唆院釉逆 DB2 侮欺 5.2 侮裙驮圊如嘻 README 篁
| 驮苴醛·
 
| 软王喻域剖佟嘻院釉侮罾劬 "|" 牙泣茄摹煲裙母嘻求如诜侮欺 5.2
| README 篁嘻侮裙逆靴、呢孱孱绱院恃托浠炝·
 
  欺篁争琵涯亩悄塄新嘻肄骜毓〃
 
|      IBM DB2 Universal Database Enterprise Edition, 侮欺 5.2
|      IBM DB2 Universal Database Enterprise - Extended Edition, 侮欺 5.2
|      IBM DB2 Universal Database Personal Edition, 侮欺 5.2
|      IBM DB2 Universal Database Workgroup Edition, 侮欺 5.2
|      IBM DB2 Personal Developer's Edition, 侮欺 5.2
|      IBM DB2 Universal Developer's Edition, 侮欺 5.2
 
  蕃狻〃  VisualAge for Basic 滔 Lotus Approach 拟锹蝰厢王塄新
        艿涅·
 
  亩悄塄新呷蓑魔远杀嘻≈侮欺蚊泗绥恸∽篁 (区嬉页 READDCS.TXT)〃

 
       IBM DB2 Connect Enterprise Edition、侮欺 5.2
       IBM DB2 Connect Personal Edition、侮欺 5.2
 
| DB2 Universal Database 篁争栈你嘻衍髓阵倾侮欺 5.2 针烃栖收浠·
  破辕琵涯〃
 
  o   戋堋墨宪
| o   怃圊 Windows 暖 OS/2 艨韬嘻筌祁幔娶
  o   CLI Guide and Reference
  o   Embedded SQL Programming Guide
  o   Master Index
  o   SQL 墨宪
  o   System Monitor Guide and Reference
  o   Troubleshooting Guide·
 
| 却侮欺 5 曦 5.2 你 DB2 衍髓配友披诎劈卒嘻渫、盆暖侮欺 5.2 披诎
| 劈卒嘻孥茇氅忘 (种杀岩侮欺 5.2 针烃栖收浠嘻阵) 葭琵芍倾≈浠种吞孽
| 苷∽摹阵你·倾 DB2 Universal Database 侮欺 5 暖 DB2 Connect 侮欺 5
| FixPaks 你偏祁嘻浠种吞莘狺页岩侮欺 5.2 嘻披诎劈卒·
 
| 却诶七倾洳掾嘻配黝、铢损祁 DB2 篁争栈你锼宓嘻阵、嘤靴葙茄≈浠种
| 吞孽苷∽暖欺 README 篁你嘻骜毓、苫偏探诘声痨嘻 DB2 骜毓·
 
 
| Fixpak 16 嘻配友收
 
| 欺彗衮氅忘 Fixpak 16 嘻配友收、虽牙砒卮绁菡髓收嘻软弭·
 
| 偏收 EEE 母嘻葑如睿
 
| DB2 戋堋席堍倾偏抬破末萼绱菝贴篁圄卮戆 "DB2CHGPWD_EEE=<boolean>"、
| 唆收 AIX 暖 NT EEE 朔苡母嘻葑如睿·邱腈声痨嘻孥茇骜毓、铢俣镥 2.2.2,
| "Change Password Enablement for EEE"·
 
| 宇 DRDA 嘻诜谆宋拧
 
| DB2 UDB 腮韦鹇堍倾偏盆俅拧 DRDA 诜谆曦 DB2 for MVS 暖 OS/390。
| DB2 for VM 暖 VSE。DB2 for OS/400、盆暖抬破诜谆逆怄嘻拟茄·菡
| 偏诶倾菡髓抬破诜谆亩像溶淖嘻骜砧·盆母驮牙贴诜谆偏炭睾戋、
| 盆仝如诜谆軎嘻宋拧、仍赔诶堍倾木偏盆刹鏊菡髓诜谆宋拧
| 嘻软弭·邱腈声痨嘻孥茇骜毓、铢俣镥 2.2.1, "DRDA-only Client
| Authentication"·
 
| 披亠嘻葑如睿
 
| 呢浠炝俣戆 "AUTHENTICATION" 嘻浠骜砧栈戋堋幔娶艳楝垣 "SERVER_ENCRYPT"·
| "SERVER_ENCRYPT" 堍倾苔却曦 "SERVER" 肄茄嘻耄泗、苔却衮萼绱杲纣惝厥嘻
| 葑如睿披亠嘻浠炝种吞·邱腈声痨嘻孥茇骜毓、 铢俣镥 2.2.3, "Encrypted
| Passwords"·
 
| JDBC 2.0
 
| 欺 Fixpak 蝰厢嘻 JDBC 2.0 侬幔娶排呶 JDBC 2.0 狰爬 API·
嘤仍、寝页
| DB2 Engine 嘻衍髓种吞虽拟贴、驮盆虽拟岩萁知你驮贴屮嘻驮却种吞葭却排
| 呶·邱腈声痨嘻孥茇骜毓、铢俣镥 8.7, "JDBC 2.0"·
 
| NETQUESTION 枰梭
 
| 欺彗邙虞〃
 
| o   倾 UNIX 仆坪母区嬉 IMNSearch (NetQuestion) 嘻俾黝
 
| o   倾 HPUX-10 母区嬉 NetQuestion
 
| o   UNIX 仆坪嘻 NetQuestion 暖 DB2 CAE
 
| o   AIX 仆坪母嘻 NetQuestion DBCS
 
| 邱腈声痨嘻孥茇骜毓、铢俣镥 21.0, "NetQuestion 枰梭"·
 
| 栩友闲排呶
 
| 侵披诎劈卒呢散醛栩友闲排呶·REFRESH IMMEDIATE 蛸恸堍倾偏盆损祁魔·
| 邱腈声痨嘻孥茇骜毓、铢俣镥苌 135 喻嘻 16.2, "ALTER TABLE"、盆暖
| 16.5, "CREATE TABLE"·
 
| UNICODE/UCS-2 暖 UTF-8 排呶
 
| Unicode 求镊罹睿砗漤岩摹辍讨贴羡轩嘻求镊罹睿昃气、琵涯培姨乃蒎枪
| 驮却祈窑脓耄似嘻求镊·ISO 暖 IEC 10646 砗漤 (ISO/IEC 10646) 岩牙
| 贴苔却 2 软镊苴侮欺 (UCS-2) 暖 4 软镊苴侮欺 (UCS-4) 嘻 Multiple-Octet
| Coded Character Set (UCS)·DB2 UDB 排呶 UCS-2、签苫岩属却蓬堋嘻
| Unicode·
 
| 却魔 UCS-2 托 Unicode 罹睿劈卒、ASCII 暖谡瘫求镊木岩胎远软镊苴羡、
| 仍赔些鹨软镊苴页 0·菡筌孚岩 ASCII 僮欺筌祁幔娶暖 ASCII 篁争朔苡
| 嘻俾黝、寝页倾 UCS-2 求入你、嘁嘻 NULL 偏卒淠砒堍倾求入你嘻嵌若
| 氢派·盆隧蚴拟嘻 ASCII 求睿嘻幔娶仍似、摹罪驮蛄嘻 UTF-8 魉咝榻
| 戢挝偏盆祁唆瘫畔菡远俾黝嘻圊祈·DB2 岩烟如 UTF-8·
 
| 邱腈声痨嘻孥茇骜毓、铢俣镥 2.15, "Unicode/UCS-2 and UTF-8 Support
| in DB2 UDB"·
 
| 损祁狃箝孽域 (VI) 岣楝
 
| DB2 UDB 堍倾排呶胎远 VI 岣楝嘻烟如〃摹远唆溶 GigaNet、仍贫摹远唆溶
| ServerNet·邱腈声痨嘻孥茇骜毓、铢俣镥 2.16.3, "Running DB2 UDB V5.2
| for Windows NT with GigaNet Interconnect"·
 
 
  1.0  种直蚊泗绥恸
 
 
| 1.1  FIXPAK 6 韦侪骜毓
 
| DB2 UDB 侮欺 5.2 偏尢窳跽夤暖区嬉、木偏盆散页摹远 FixPak 区嬉倾 DB2
| UDB 侮欺 5.0 煲裙逆母·诶偏盆衮侮欺 5.0 弄兹页苔却 FixPak 6 嘻侮欺
| 5.2·侵散淦朔苡锼祁逆 FixPak 6 嘻 PTF 胬睿悄倾亩闲你〃
 
  +---------------------------------------------------------------------------+
| | 闲 1. DB2 UDB FixPak 6 嘻 PTF 胬睿                                        |
  +--------------------------------------+-------------------------------------+
| | 散淦朔苡                             | DB2 UDB FIXPAK 6 嘻 PTF 胬睿        |
  +--------------------------------------+-------------------------------------+
| | AIX                                  | U459852                             |
  +--------------------------------------+-------------------------------------+
| | HP-UX 10                             | U459854                             |
  +--------------------------------------+-------------------------------------+
| | HP-UX 11                             | U459872                             |
  +--------------------------------------+-------------------------------------+
| | OS/2                                 | WR09073                             |
  +--------------------------------------+-------------------------------------+
| | SCO UnixWare 7                       | U459870                            |
  +--------------------------------------+-------------------------------------+
| | Silicon Graphics IRIX                | U459871                             |
  +--------------------------------------+-------------------------------------+
| | Solaris                              | U459853                             |
  +--------------------------------------+-------------------------------------+
| | Windows 95。Windows 98 暖 Windows    | WR09074                             |
| | NT                                   |                                     |
  +--------------------------------------+-------------------------------------+
| | Windows 3.1 暖 Windows for           | WR09076                             |
| | Workgroups 3.11                      |                                     |
  +--------------------------------------+-------------------------------------+
 
  蕃狻〃  倾 AIX 侮欺 4.2 母仝如≈DB2 File Manager∽腈友 PTF U456886
        嘻薏难垣·
 
  亩悄唆溶 SCO 嘻 PTF 胬睿岩 DB2 UDB 侮欺 5.2 友倾 SCO UnixWare 7
  母仝如驮拟偏托淄嘻〃
 
       ptf7003c
       ptf7010
       ptf7013
 
| 却 DB2 UDB 侮欺 5.2 驮腈逆 SCO PTF 嘻薏浠骜毓偏倾 1.3, "Product
| and Service Technical Library" 你势摊·
 
  仝如 Sun Cluster 菰针腈友亩悄院七幔娶煲裙〃
 
       105786-05     - Sun Cluster 2.x 倾 Solaris 2.6 母驮腈嘻
                       院七幔娶·
       2.1_105458-06 - DB2 驮腈嘻 Sun Cluster 院七幔娶煲裙·
 
 
| 1.2  Fixpak 16 韦侪骜毓
 
| 欺 FixPak 拟卒区嬉倾堍却 DB2 UDB 侮欺 5.0 幔娶睿嘻煲裙逆母·
诶容
| 欧埔恻岩 DB2 UDB 侮欺 5.2 煲裙·页魔友绠摊侮欺 5.2 煲裙、诶偏盆亩
| 绁暖区嬉 FixPak 6·摹瀑区嬉秋 FixPak 6、诶摅偏盆趴祁 Fixpak 16·
 
  +--------------------------------------------------------------------------+
| | 闲 2. DB2 UDB Fixpak 16 嘻 PTF 胬睿                                       |
  +-------------------------------------+-------------------------------------+
| | 散淦朔苡                            | DB2 UDB Fixpak 16 嘻 PTF 胬睿       |
 +-------------------------------------+-------------------------------------+
| | AIX                                 | U478404                             |
  +-------------------------------------+-------------------------------------+
| | HP-UX 10                            | U478406                             |
  +-------------------------------------+-------------------------------------+
| | HP-UX 11                            | U478407                             |
  +-------------------------------------+-------------------------------------+
| | OS/2                                | WR21262                             |
  +-------------------------------------+-------------------------------------+
| | SCO UnixWare 7                      | U478408                             |
  +-------------------------------------+-------------------------------------+
| | Silicon Graphics IRIX               | U478409                             |
  +-------------------------------------+-------------------------------------+
| | Solaris                             | U478405                             |
  +-------------------------------------+-------------------------------------+
| | Windows 95, Windows 98, and Windows | WR21263                             |
| | NT                                  |                                     |
  +-------------------------------------+-------------------------------------+
| | Windows 3.1 and Windows for         | WR21264                             |
| | Workgroups 3.11                     |                                     |
  +-------------------------------------+-------------------------------------+
 
 
 
  1.3  塄新曦韦侪世荽篁争栈
 
  邱腈声痨嘻薏浠 DB2 骜毓 (琵涯群 README 篁圊如逆靴驮圊堍嘻俾黝)、
  铢损祁亩悄 World Wide Web 杲蛇母嘻 Product and Service Technical
  Library〃
 
       http://www.software.ibm.com/data/db2/library
 
 
| 1.4  DB2 龌阵暖 FIXPAK 牌堑
 
| 倾侮欺 5.2 你、楝醛塄新龌阵嘻乃蒎枪阵葭呢收浠·DB2 龌阵偏倾罾母
| 盆 HTML 嘻知娶探诘·乃蒎枪木偏盆 PDF 暖 postscript 嘻知娶探诘·
| 铢俣镥母域嘻 1.3, "Product and Service Technical Library"、盆探诘
| 罾母囚探菡髓阵嘻软弭·铢俣镥≈浠种吞孽苷∽摹阵、破琵芍收浠阵嘻
| 声痨悄泣。悄峭嘻牙泣。盆暖釉跽嘻阵胬·诶偏盆损祁阵胬 SBOF-8921-00、
| 唆釉跽侮欺 5.2 薏浠嘻摹燥声痨龌阵·
 
  强些索墨 read1297.txt。read0398.txt。滔 read0698.txt 岖篁争你
  嘻 FixPak 骜毓呢琵芍倾〃
 
  o   收浠嘻牌堑你、邱为孚阵呢收浠
 
  o   ≈浠种吞孽苷∽摹阵、邱为孚阵栖收浠·
 
  群评、倾阵峭砒针烃栖呷蓑嘻骜毓、签琵涯倾菡髓≈侮欺蚊泗绥恸∽你·
 
 
| 1.5  ≈WEB 谡瘫你爬∽区嬉
 
  ≈Web 谡瘫你爬∽岩 Java 侮欺嘻 DB2 Universal Database Control
  Center (摹辍骜砧栈戋堋闹苔)· 破嘻菝佑岩盆韵填嘻≈DB2 谡瘫你爬∽
  页砑形、偏呷蓑收苔爝吞。赔盆杲纣页你爬嘻戋堋艨韬· ≈Web 谡瘫你
  爬∽岩仝如页损祁 DB2 JDBC 排呶嘻 Java applet·
 
| FixPak 拟淠区嬉≈Web 谡瘫你爬∽、叁淠弄兹堍囚嘻侮欺·邱为属却≈
| Web 谡瘫你爬∽、铢诜亩悄 URL 亩绁破、苫偏探诘〃
 
       http://www.software.ibm.com/data/db2/udb/webcc
 
 
  1.6  DB2 朔悄浠毓
 
  王 DB2 朔悄塄新嘻薏浠骜毓、偏釉镥 "DB2 Family Newsletter"
  (惘恿牌侮)·蛹却嵌若友叔、铢惝著容 1-905-316-4733、虽呷蓑亩悄
  骜毓〃
 
       田秦
       狞瞥秦辎
       声痨庥凫氢蛇
       缳驺胬睿
       气些损祁嘻 DB2 塄新
 
 
  2.0  ADMINISTRATION GUIDE (欺阵栖你牌脓)
 
 
  2.1  IMPLEMENTING YOUR DESIGN
 
 
| 2.1.1  CREATING A DATABASE/CREATING A SUMMARY TABLE
 
 
  2.1.1.1  Isolation Levels and Query Optimization Using Summary Tables or
  Replicated Tables
 
  In general, a summary table or a
  replicated table is used for optimization of a query if the isolation level
  of the summary table or the replicated table is higher than or equal to the
  isolation level of the query.  For example, if
  a query is running under the cursor stability (CS) isolation level, only
  summary tables and replicated tables that are defined under CS or higher
  isolation levels are used for optimization.
 
 
| 2.1.1.2  REFRESH IMMEDIATE
 
| The REFRESH IMMEDIATE option is now supported for summary tables. For more
| information, please see section 16.2, "ALTER TABLE", and section
| 16.5, "CREATE TABLE".
 
 
  2.1.2  OPTIMIZING PERFORMANCE WHEN DATA IS PLACED ON RAID DEVICES
 
  This section describes how to optimize performance when data is placed on
  Redundant Array of Independent Disks (RAID) devices. In general, you should
  do the following for each table space that uses a RAID device:
 
  o   Define a single container for the table space (using the RAID device).
 
  o   Make the EXTENTSIZE of the table space equal to, or a multiple of, the
      RAID stripe size.
 
  o   Ensure that the PREFETCHSIZE of the table space is:
 
      -   the RAID stripe size multiplied by the number of RAID parallel
          devices (or a whole multiple of this product), and
 
      -   a multiple of the EXTENTSIZE.
 
  o   Use the DB2_PARALLEL_IO registry variable (described below) to enable
      parallel I/O for the table space
 
  o   Use the DB2_STRIPED_CONTAINERS registry variable (described below) to
      ensure extent boundaries are aligned in the table space.
 
  DB2_PARALLEL_IO
 
  When reading data from, or writing data to table space containers, DB2 may
  use parallel I/O if the number of containers in the database is greater than
  1. However, there are situations when it would be beneficial to have parallel
  I/O enabled for single container table spaces. For example, if the container
  is created on a single RAID device that is composed of more than one physical
  disk, you may want to issue parallel read and write calls.
 
  To force parallel I/O for a table space that has a single container, you can
  use the DB2_PARALLEL_IO registry variable. This variable can be set to "*"
  (asterisk), meaning every table space, or it can be set to a list of table
  space IDs separated by commas. For example:
 
       db2set DB2_PARALLEL_IO=*        {turn parallel I/O on for all table spaces}
       db2set DB2_PARALLEL_IO=1,2,4,8  {turn parallel I/O on for table spaces 1, 2, 4, and 8}
 
 
  After setting the registry variable, DB2 must be stopped (db2stop), and then
  restarted (db2start), for the changes to take effect.
 
  DB2_STRIPED_CONTAINERS
 
  Currently when creating a DMS table space container (device or file), a
  one-page tag is stored at the beginning of the container. The remaining pages
  are available for data storage by DB2, and are grouped into extent-sized
  blocks.
 
  When using RAID devices for table space containers, it is suggested that the
  table space be created with an extent size that is equal to, or a multiple
  of, the RAID stripe size. However, because of the one-page container tag, the
  extents will not line up with the RAID stripes, and it may be necessary
  during an I/O request to access more physical disks than would be optimal.
 
  DMS table space containers can now be created in such a way that the tag
  exists in its own (full) extent. This avoids the problem described above, but
  it requires an extra extent of overhead within the container. To create
  containers in this fashion, you must set the DB2 registry variable
  DB2_STRIPED_CONTAINERS to "ON", and then stop and restart your instance:
 
       db2set DB2_STRIPED_CONTAINERS=ON
       db2stop
       db2start
 
  Any DMS container that is created (with CREATE TABLESPACE or ALTER
  TABLESPACE) will have new containers with tags taking up a full extent.
  Existing containers will remain unchanged.
 
  To stop creating containers with this attribute, reset the variable, and then
  stop and restart your instance:
 
       db2set DB2_STRIPED_CONTAINERS=
       db2stop
       db2start
 
  The Control Center and the LIST TABLESPACE CONTAINERS command will not show
  whether a container has been created as striped or not. They will continue to
  use "file" or "device", depending on how the container was created. To verify
  that a container was created as striped, you can use the /DTSF option of
  DB2DART to dump table space and container information, and look at the type
  field for the container in question. Also, the query container APIs,
  sqlbftcq( ) and sqlbtcq( ), can be used to create a simple application that
  will display the type.
 
  Definitions for these new types have been added to the sqlutil.h header file:
 
       #define SQLB_CONT_STRIPED_DISK 5      /* DMS: Striped disk */
       #define SQLB_CONT_STRIPED_FILE 6      /* DMS: Striped file */
 
 
| 2.2  CONTROLLING DATABASE ACCESS
 
 
| 2.2.1  DRDA-ONLY CLIENT AUTHENTICATION
 
| In the section "Selecting an Authentication Method for Your Server", two new
| paragraphs are added:
 
| To protect against all clients except DRDA clients from DB2 for MVS and
| OS/390, DB2 for VM and VSE, and DB2 for OS/400, set the "trust_allclnts"
| parameter to DRDAONLY. Only these clients can be trusted to perform
| client-side authentication. All other clients must provide a user ID and
| password to be authenticated by the server.
 
| The "trust_clntauth" parameter is used to determine where the above clients
| are authenticated: if "trust_clntauth" is "client", authentication takes
| place at the client. If "trust_clntauth" is "server", authentication takes
| place at the client when no password is provided and at the server when a
| password is provided.
 
 
| 2.2.2  CHANGE PASSWORD ENABLEMENT FOR EEE
 
| DB2 Administrators may now allow others to change passwords on AIX and
| Windows NT EEE systems through the profile registry variable
| "DB2CHGPWD_EEE=<boolean>".
 
| NOTE:  This is not supported on Sun EEE systems.
 
| The default for this variable is "NOT SET" (disabled). Other values for
| "DB2CHGPWD_EEE" are the standard boolean values used by other DB2 profile
| variables.
 
| The DB2 Administrator is responsible for ensuring that the passwords for all
| nodes are maintained centrally using either a Windows NT Domain Controller on
| Windows NT, or NIS on AIX.
 
| NOTE:  If the passwords are not maintained centrally, enabling the
|        "DB2CHGPWD_EEE" variable will allow for the possibility that passwords
|        may not be consistent across all nodes. That is, if a user uses the
|        "change password" feature, then the user's password will only be
|        changed at the node to which they connect.
 
 
| 2.2.3  ENCRYPTED PASSWORDS
 
| A new "DBM CFG" (database manager configuration) value "SERVER_ENCRYPT" has
| been added for the parameter "AUTHENTICATION". "SERVER_ENCRYPT" now has the
| same rules as "SERVER" authentication, with the added feature that any
| passwords sent over a network will be encrypted. Also, a new value
| "DCS_ENCRYPT" has been added for DB2 Connect support. This value is
| documented in the file READDCS.TXT, available with the following products:
 
|      IBM DB2 Connect Enterprise Edition, Version 5.2
|      IBM DB2 Connect Personal Edition, Version 5.2
 
| The same parameter has been added to the "CATALOG DATABASE" authentication
| clause as an option.
 
| RESTRICTIONS
 
| 1.  In terms of database support, only DB2/390 and DB2 UDB accept an
|     encrypted password for this initial implementation. DB2 UDB support is
|     initially limited to the following platforms:
 
|     o   Windows 95/98
 
|     o   Windows NT
 
|     o   AIX
 
| 2.  No CCA/Discovery Support for the new ENCRYPT versions of authentication
|     is supported.
 
| 3.  No Support in the Control Center.
 
| 4.  No encryption of the new password for change password support.
 
| 5.  No DCE Directory support of the new authentication types SERVER_ENCRYPT
|     and DCS_ENCRYPT.
 
| 6.  No DRDA AS support for encryption.
 
| 7.  Any encryption which occurs will only be for the password - user ID and
|     the remainder of the flow remain unencrypted.
 
 
| 2.2.4  LOGINRETRIES OPTION (AIX ONLY)
 
| DB2 Universal Database on AIX has added the functionality to log failed
| password attempts with the operating system and detect when a client has
| exceeded the number of allowable login tries as specified by the
| "loginretries" parameter.
 
 
  2.3  AUDITING DB2 ACTIVITIES
 
  There is no audit support for summary tables, typed tables, or replicated
  tables.
 
 
  2.4  UTILITIES FOR MOVING DATA
 
 
  2.4.1  LOAD, IMPORT, AND EXPORT FILE FORMATS/PC/IXF FILE FORMATS/CODE PAGE
  CONSIDERATIONS
 
  If you want to load or import an IXF format file containing DBCS data, you
  must have the corresponding conversion files (located in sqllib\conv)
  installed on your client machine. The names of these conversion files contain
  both the source and the target code page numbers; the extension is always
  converting code page 932 to 943.
 
  If your client machine does not have the appropriate conversion files, you
  can copy them from a server machine to the sqllib\conv directory of the
  client machine. Be sure to copy the files from a compatible platform; for
  example, if the client is running on a UNIX based operating system, copy the
  files from a server that is also running on a UNIX based operating system.
 
 
| 2.4.2  OVERVIEW OF THE LOAD PROCESS (PENDING STATES)
 
| In the section "Overview of the LOAD Process", a revision to the paragraph
| discussing pending states is made:
 
| After the LOAD process completes, if:
 
| o   "logretain" or "userexit" is "on", COPY NO (which is the default) is
|     selected and NONRECOVERABLE is not selected; or,
 
| o   "logretain" or "userexit" is "off," COPY YES is selected and
|     NONRECOVERABLE is not selected
 
| then any associated table spaces are placed in a BACKUP PENDING state.
 
| In the section "LOAD Exception Table," two new paragraphs are added:
 
| LOAD, when using the FOR EXCEPTION option, will check for rows that have
| unique index violations. LOAD will not check for constraint or foreign key
| violations other than for unique constraint violations.
 
| A "unique key" is a key that is constrained so that no two of its values are
| equal. The mechanism used to enforce the constraint is called a unique index.
| A primary key is a special case of a unique key. A table cannot have more
| than one primary key.
 
 
  2.4.3  LOAD RESTRICTION ON WINDOWS NT AND OS/2 SMP-ENABLED MACHINES
 
  In DB2 UDB Version 5.2 for Windows NT and DB2 UDB Version 5.2 for OS/2, users
  operating in an SMP environment might occasionally experience a system hang
  during a load operation. This is a known problem that occurs only during
  index creation (the BUILD phase of the load utility) involving large volumes
  of data (on the order of several gigabytes). To avoid this problem, it is
  recommended that existing indexes on a loading table be dropped before
  issuing the LOAD command, and recreated using the CREATE INDEX statement
  after the load operation has completed successfully. An alternative that does
  not require the dropping of indexes is to perform the load operation into a
  staging table that does not have any indexes defined on it. The target table
  can subsequently be updated by issuing an INSERT statement encompassing all
  of the data from the staging table.
 
 
| 2.4.4  ERROR SCENARIO FOR THE AUTOLOADER PROGRAM ON DB2 UDB ENTERPRISE -
| EXTENDED EDITION FOR WINDOWS NT
 
| The following applies to an error scenario for the autoloader program on IBM
| DB2 Universal Database Enterprise - Extended Edition for Windows NT. It
| explains the symptom and nature of the problem, and also a workaround.
 
| When running the autoloader program, "db2atld.exe", on a multi-homed machine,
| that is, a machine with multiple network cards installed, ensure that the
| machine is configured correctly by trying the following operations:
 
| o   When you type the "hostname" command on the machine where the autoloader
|     is started, and also ping this host name from the same machine, the IP
|     address returned should be the same as the result when this host name is
|     pinged from another machine in your DB2 MPP node list. If the machine is
|     not configured correctly, you will see an "SQL6555N" error from the
|     autoloader program, and you will also see the error message, "errno =
|     10061", i.e. connection refused, in the "db2diag.log" file(s) on some of
|     the loading nodes defined by the "OUTPUTNODES" parameter in your
|     autoloader configuration file.
 
| On Windows NT machines, the IP address returned for a local host name is not
| retrieved from the "DNS" or "hosts" file, but from information configured
| locally in the Control Panel network icon.
 
| There is a bug in Windows NT 4.0 where the binding order configured in the
| Control Panel network icon does not influence the IP address order returned
| on a multi-homed machine. See Microsoft Support Online article ID Q171320 to
| resolve this problem. (When you ping a host name, it is the first IP address
| that is returned.)
 
 
| 2.4.5  CHANGES IN AUTOLOADER AUTHENTICATION BEHAVIOR
 
| The concept of a local database connection has been extended for the MPP
| environments to include connections from any node of a given MPP instance.
| That means that even though the instance is configured using AUTHENTICATION
| server, a password will no longer be required if a connection is being
| attempted from one of the nodes defined in the "db2nodes.cfg" file.  The
| Autoloader will make use of this new connection behavior when the
| AUTHENTICATION flag in the "autloader.cfg" file is not set or is set to NO,
| and the password for autoloader is not defined.
 
| With this new database connection behavior, the password is only mandatory
| for autoloader execution if a password is required for remote execution of
| programs in your system. For example, if the ".rhosts" file on a UNIX system
| was not set up properly to enable "rsh" execution, then the password is
| required.
 
 
| 2.4.6  IMPORT/EXPORT OF WSF DATA CONTAINING BIGINT
 
| When exporting "BIGINT" or "DECIMAL" columns to WSF (Work Sheet Format), only
| values that fall in the range of type DOUBLE can be exported accurately.
| Values that do not fall in this range will still be exported to the target
| media. However, loading back these values (via "LOAD" or "IMPORT") may result
| in incorrect data. The end result will vary by platform.
 
 
  2.5  RECOVERING A DATABASE
 
 
  2.5.1  BACKING UP AND RESTORING DATABASES ON DIFFERENT OPERATING SYSTEMS
 
  You cannot back up a database or table space on one operating system and
  restore it to another operating system by using the BACKUP DATABASE and
  RESTORE DATABASE commands. Instead, you move tables from one operating system
  to another by using the db2move command (or by exporting, then importing or
  loading the data). For more information, see "Moving Data Using the db2move
  Tool" in the Administration Guide.
 
 
  2.5.2  CONSIDERATIONS FOR USING ADSTAR DISTRIBUTED STORAGE MANAGER (ADSM)
 
  The current ADSM client on the Windows operating system and OS/2 is
  non-reentrant, and so multiple sessions cannot be created with
  the backup, restore, or load utilities from a single machine.
 
  In a single node configuration, if a user attempts to issue a backup command
  such as:
 
       db2 backup db sample use adsm open 3 sessions
 
  DB2 will detect that multiple sessions are not supported by ADSM, and will return
  SQL2032N. The equivalent scenario also applies to load copies using ADSM.
 
  However, in an MLN configuration on Windows NT, DB2 may not be able to detect
  the use of multiple sessions on a single machine if each logical node attempts
  to create only one session. If multiple logical nodes are being backed up,
  restored, or loaded in parallel using ADSM, DB2 will allow the operation to proceed
  if each node attempts to use a single session, even though the logical nodes actually
  reside on the same physical hardware. This can lead to failed backup attempts,
  and hung load processes, and should not be attempted.
 
 
| 2.5.3  CONFIGURATION PARAMETERS FOR DATABASE LOGGING
 
| The following information should be added:
 
| The total log file size limit is 4 GB. That is, the number of logfiles
| (LOGPRIMARY + LOGSECOND) multiplied by the size of each logfile in bytes
| (LOGFILSIZ * 4096) must be less than 4 GB.
 
 
| 2.5.4  FREQUENCY OF BACKUPS AND TIME REQUIRED
 
| In the section on "Frequency of Backups and Time Required," the following
| information should be added:
 
| If the amount of time needed to apply archived logs when recovering and
| rolling forward a database is a major concern, then you will need to consider
| the cost of having more frequent backups. If your database is very active,
| more logging occurs and therefore more frequent database backups are
| recommended. More frequent database backups reduces the number of archived
| logs you need to apply when rolling forward through archived logs.
 
 
  2.5.5  RECOVERING A DATABASE (PLANNING TO USE THE ROLLFORWARD COMMAND)
 
  You cannot roll forward a partitioned database from a Version 2 client.
 
 
| 2.6  USING DB2 WITH AN XA-COMPLIANT TRANSACTION MANAGER
 
| Within the sub-section 'Using the DB2 Universal Database XA Switch' under the
| 'XA Function Supported' section in this chapter, the last line in "OS/2
| Platform" should be changed to:
 
|      With either method, you must link your application with db2api.lib.
 
  The last line in the "Windows NT Platform" section should be changed to:
 
       With any of these methods, ensure that you link with db2api.lib.
 
| References to "db2app.lib" should be changed to "db2api.lib."
 
 
| 2.7  APPLICATION CONSIDERATIONS
 
| In the section on "Locking," just before the  "Attributes of Locks" section,
| the following paragraph should be added:
 
| You may want to consider defining a monitor that will record when deadlocks
| occur. Use the CREATE EVENT MONITOR statement described in the SQL Reference
| to create the monitor.
 
| In the section on "Using a select-statement," the OPTIMIZE FOR and FETCH
| FIRST example should be modified to show the following:
 
|   SELECT EMPNAME, SALARY FROM EMPLOYEE
|      ORDER BY SALARY DESC
|      FETCH FIRST 100 ROWS ONLY
|      OPTIMIZE FOR 20 ROWS
 
| The change is simply the reversal of the order of the last two lines of the
| example.
 
 
| 2.8  UNDERSTANDING THE SQL COMPILER
 
| In the section on "Hash Join," the following information should be added:
 
| To realize the performance benefits of hash join, it may be necessary to
| change the value of the "sortheap" database configuration parameter, and the
| "sheapthres" database manager configuration parameter.
 
| For decision support queries, hash join access plans use more sort heap space
| than do non-hash join plans. When "sheapthres" is set to be very close to
| "sortheap" (that is, less than a factor of two or three per concurrent
| query), a hash join runs with much less memory than the optimizer
| anticipated. When executing with limited memory, hash joins can be very slow.
| The problem occurs in queries with multiple sorts and hash joins, in which
| the first sorts or hash joins acquire most of the available memory.
 
| The solution is to configure "sheapthres" to be large enough (relative to
| "sortheap").
 
 
  2.9  OPERATIONAL PERFORMANCE
 
 
| 2.9.1  MANAGING THE DATABASE BUFFER POOL
 
| The following information should be added:
 
| The storage associated with the buffer pool is allocated when a database is
| activated or when the first application connects to the database.
| Applications are the primary beneficiaries of the buffer pool; once
| applications are all disconnected, the storage associated with the buffer
| pool is de-allocated.
 
 
  2.9.2  MANAGING MULTIPLE DATABASE BUFFER POOLS
 
  When working on your database design, you may have determined that tables
  with 8KB page sizes were best. As a result, you should create a buffer pool
  with an 8KB page size (along with one or more table spaces with the same page
  size).
 
  If you have chosen to place your tables in an 8KB table space, it is
  recommended that your temporary table spaces have an 8KB page size as well,
  and they should be assigned to the same 8KB page size buffer pool. The
  default buffer pool (IBMDEFAULTBP) or any other 4KB buffer pool to which any
  4KB temporary table spaces are assigned should be kept small, since the
  database manager will favor the 8KB temporary table spaces, and therefore the
  8KB buffer pool.
 
 
| 2.10  USING THE GOVERNOR
 
| In the section on "The Governor Deamon" add the following information:
 
| The note concerned with using the governor as an alternate means to adjust
| agent priorities should have the following information added: "(This note
| does not apply to OS/2 or Windows NT platforms.)"
 
| In the section on the "Governor Configuration File", replace the first and
| second paragraphs of the information under "action/priority" with the
| following:
 
| Specifies a change to the priority of agents working for the application.
| Valid values are from -20 to +20.
 
 
  2.11  CONFIGURING DB2
 
 
| 2.11.1  ENCRYPTED PASSWORDS
 
| The AUTHENTICATION type (authentication) parameter is updated as follows:
 
| A new value, SERVER_ENCRYPT, has been added to this parameter. This value has
| the same rules as SERVER authentication, with the added feature that any
| passwords sent over a network are encrypted. For restrictions on the use of
| this value, see section 2.2.3, "Encrypted Passwords".
 
| A new value, DCS_ENCRYPT, has been added to this parameter. This value has
| been added for support of DB2 Connect. Details on this new value are
| documented in the READDCS.TXT file for the following two products:
 
| o   IBM DB2 Connect Enterprise Edition, Version 5.2
 
| o   IBM DB2 Connect Personal Edition, Version 5.2.
 
 
  2.11.2  TUNING CONFIGURATION PARAMETERS/OPTIMIZING HASH JOIN PERFORMANCE
 
  To realize the performance benefits of hash join, it may be necessary to
  change the value of the SORTHEAP database configuration parameter, and the
  SHEAPTHRES database manager configuration parameter.
 
  Hash join plans use more sort heap space than other join plans. When
  SHEAPTHRES is set to be very close to SORTHEAP (less than a factor of 2 or 3
  per concurrent query), hash join runs with much less memory than the
  optimizer anticipated. When executing with limited memory, hash join can be
  very slow.  The problem occurs in queries with multiple sorts and hash joins,
  in which the first sorts or hash joins acquire most of the available memory.
 
  The solution is to configure SHEAPTHRES to be large enough (relative to
  SORTHEAP).
 
  For more information about hash join, including how to determine whether a
  hash join strategy has been selected, see the description of db2expln in the
  SQL Reference, and the What's New book (Appendix A - System Monitor Guide and
  Reference Updates). See also the description of the new hash join registry
  variable (DB2_HASH_JOIN) below.
 
 
| 2.11.3  DATABASE LOG FILES
 
| The "Size of Log Files (logfilsz)" parameter is updated as follows:
 
| The total log file size limit is 4 GB. That is, the number of logfiles
| (LOGPRIMARY + LOGSECOND) multiplied by the size of each logfile in bytes
| (LOGFILSIZ * 4096) must be less than 4 GB.
 
 
| 2.11.4  TRUSTED CLIENTS AND DRDA USE
 
| The section of the chapter dealing with "Instance Administration," the "Trust
| All Clients (trust_allclnts)" parameter is updated as follows:
 
| The Range of values for the parameter now includes DRDAONLY in addition to NO
| and YES.
 
| The description for the parameter now includes the following two paragraphs:
 
| Setting the "trust_allclnts" parameter to DRDAONLY protects against all
| clients except DRDA clients from DB2 for MVS and OS/390, DB2 for VM and VSE,
| and DB2 for OS/400. Only these clients can be trusted to perform client-side
| authentication. All other clients must provide a user ID and password to be
| authenticated by the server.
 
| The "trust_clntauth" parameter is used to determine where the above clients
| are authenticated: if "trust_clntauth" is "client", authentication takes
| place at the client. If "trust_clntauth" is "server", authentication takes
| place at the client when no password is provided and at the server when a
| password is provided.
 
 
| 2.11.5  LOGINRETRIES OPTION (AIX ONLY)
 
| DB2 Universal Database on AIX has added the functionality to log failed
| password attempts with the operating system and detect when a client has
| exceeded the number of allowable login tries as specified by the
| "loginretries" parameter.
 
 
  2.11.6  ASLHEAPSZ AND FAILED QUERIES AGAINST LARGE TABLES
 
  DB2 can fail while fetching query results from large tables (that is, tables
  with greater than a 4005-character record length and more than 500 columns).
  This can be overcome by increasing the value of the ASLHEAPSZ database
  manager configuration parameter from the default value of 15.
 
 
  2.11.7  INTRA_PARALLEL SETTING ON AN SMP MACHINE (WINDOWS NT)
 
  On Windows NT, on an SMP machine, the INTRA_PARALLEL database manager
  configuration parameter will be set to YES when an instance is created with
  DB2 Version 5.2. With Version 5.0, it would have been set to NO.
 
 
| 2.12  HACMP ES FOR AIX
 
| The section "Cluster Configuration," has an example showing how to create
| containers for a two-node system that is updated as follows:
 
|      CREATE TABLESPACE TS3 MANAGED BY SYSTEM USING
|         ('/TS/cont $N%2, '/TS3/cont $N%2+2')
 
| The following containers would be used:
 
|      /TS3/cont0   - on Node 0
|      /TS3/cont2   - on Node 0
|      /TS3/cont1   - on Node 1
|      /TS3/cont3   - on Node 1
 
| The change was made to be consistent with the 'TS3' subdirectory.
 
 
| 2.13  DB2 REGISTRY AND ENVIRONMENT VARIABLES
 
 
|      Parameter       Operating         Values                    Description
|                      System
|      -------------------------------------------------------------------------------------
|      DB2CHGPWD_EEE   AIX and           Default=NULL              DB2 Administrators can allow non-
|                      Windows NT        Values: YES or NO         administrators to change passwords.
|                      (not supported                              The administrator is responsible for
|                       on Sun EEE)                                ensuring that the passwords for all
|                                                                  database partitions (nodes) are
|                                                                  maintained centrally using either
|                                                                  a Windows NT Domain Controller on
|                                                                  Windows NT, or NIS on AIX. If not
|                                                                  maintained centrally, passwords may
|                                                                  not be consistent across all database
|                                                                  partitions. This could result in a
|                                                                  password only being changed at the
|                                                                  database partition to which the user
|                                                                  connects to make the change.
 
|      Parameter       Operating      Values                       Description
|                      System
|      -------------------------------------------------------------------------------------
|      DB2_GRP_LOOKUP  Windows NT     DEFAULT=null                 Specifies which Windows NT
|                                     Values: local, domain        security mechanism will be
|                                                                  used to enumerate the groups
|                                                                  that a user belongs to.
 
| NOTE:  For FixPak 7, the "db2_grp_lookup" registry variable has been enhanced
|        to support the keyword "domain", in addition to the currently
|        supported keyword "local".
 
|             db2set db2_grp_lookup=domain
 
|        should be set under the following conditions:
 
|        1.  Your machine is not a domain-controller.
 
|        2.  Your machine is in a domain other than the domain where the domain
|            accounts reside. This occurs using the Master Account Domain model
|            where accounts are defined in a domain trusted by the resource
|            domains.
 
|        3.  You have backup domain controllers for the accounts domain.
 
|        This parameter applies to both client and server configurations.
|        Setting this parameter will tell DB2 to use a domain controller in the
|        current domain to locate a controller for the accounts domain.
 
|        PROBLEM BEING SOLVED:
 
|        In order to enumerate groups (and to find out whether you are an
|        administrator), DB2 uses an NT API to find a domain controller for the
|        domain in which the account is defined. It uses an API that tries to
|        find the Primary Domain Controller (PDC) and, failing that, a backup
|        domain controller. If the machine that is running this API is also a
|        domain controller, this will always work. If your machine is not a
|        domain controller, then this methodology will fail when the PDC is
|        down. When "db2_grp_lookup=domain", DB2 will find a domain controller
|        in YOUR domain with which to run the API to determine the domain
|        controller for the accounts domain. This will not fail when the PDC is
|        down.
 
       Parameter       Operating      Values                    Description
                       System
       ------------------------------------------------------------------------------------
       DB2_HASH_JOIN   All            DEFAULT=NO                Specifies hash join as
                                      Values: YES or NO         a possible join method when
                                                                compiling an access plan.
 
|      Parameter            Operating     Values                Description
|                           System
|      ------------------------------------------------------------------------------------
|      DB2_NEW_CORR_SQ_FF   All           DEFAULT=OFF           Affects the selectivity value
|                                         Values: ON or OFF     computed by the SQL optimizer
|                                                               for certain subquery predicates
|                                                               when it is set to ON.  It can be
|                                                               used to improve the accuracy of
|                                                               the selectivity value of equality
|                                                               subquery predicates that use the
|                                                               MIN or MAX aggregate function in
|                                                               the select list of the subquery.
|                                                               For example:
 
|                                                                 SELECT * FROM T  WHERE T.COL =
|                                                                  (SELECT MIN(T.COL) FROM T WHERE ...)
 
|      Parameter       Operating      Values                    Description
|                      System
|      ------------------------------------------------------------------------------------
|      DB2MEMDISCLAIM  AIX            DEFAULT=(not set)        Depending on the workload being executed
|                                     Values: YES or NO        and the pool agents configuration, you
|                                                              may run into a situation where the
|                                                              committed memory for each DB2 agent will
|                                                              stay above 32MB even when the agent is
|                                                              idle. This behavior is expected and
|                                                              usually results in good performance as
|                                                              the memory is kept for fast re-use.
|                                                              However, on a memory constrained system,
|                                                              this may not be a desirable side effect.
|                                                              To avoid this condition issue the
|                                                              following:
 
|                                                                 db2set DB2MEMDISCLAIM=yes
 
|                                                              Disclaiming memory tells the AIX operating
|                                                              system to stop paging the area so that it
|                                                              no longer occupies any real storage.
|                                                              Setting DB2MEMDISCLAIM to YES tells DB2
|                                                              UDB to disclaim some or all memory once
|                                                              freed, depending on DB2MEMMAXFREE. This
|                                                              will ensure that the memory is made
|                                                              readily available for other processes as
|                                                              soon as it is freed. See also
|                                                              DB2MEMMAXFREE.
 
|      Parameter       Operating      Values                    Description
|                      System
|      -------------------------------------------------------------------------------------
|      DB2MEMMAXFREE   AIX            DEFAULT=(not set)         Specifies the amount of free memory that
|                                     Values: 4000000           is retained by each DB2 agent. You may
|                                        to 256000000           set this variable to a value between 4
|                                                               and 256 MB. We recommend that if you use
|                                                               this feature, you specify a value of 8MB:
 
|                                                                  db2set DB2MEMMAXFREE=8000000
 
|                                                               See also DB2MEMDISCLAIM.
 
| There is a new registry variable to tune bufferpools. This is how you use it:
 
| 1.  Create a file
 
| 2.  Set the file as follows:
 
|          db2set DB2BPVARS=<filename>
 
| For example, the file "f:\BPVARSFILE" has the following content:
 
  -----------------------------------------------------------------------------
 
|   # turn on scatter read for raw DMS devices
|   NT_SCATTER_DMSDEVICE=1
 
  -----------------------------------------------------------------------------
 
| You would do the following using this file:
 
|      db2set DB2BPVARS=f:\BPVARSFILE
 
| The currently supported parameter is:
 
|      Parameter            Operating      Values               Description
|                           System
|      -------------------------------------------------------------------------------------
|      NT_SCATTER_DMSDEVICE  NT            DEFAULT=0(OFF)       Can be used to turn scatter
|                                          Values=0(OFF)        read on for DMS device
|                                            or 1(ON)           containers. This can only
|                                                               be enabled (turned ON) if
|                                                               DB2NTNOCACHE is set to ON in
|                                                               the registry. A warning message
|                                                               will be written to the
|                                                               db2diag.log if DB2NTNOCACHE
|                                                               is OFF (or not set), and
|                                                               scatter read will remain
|                                                               disabled. It is recommended for
|                                                               systems with a large amount of
|                                                               sequential prefetching against
|                                                               RAW containers.
 
 
  2.14  ADDITIONAL RAH (RUN ALL HOSTS) INFORMATION (SOLARIS AND AIX ONLY)
 
  The following is to be added to the rah information in Appendix Q.
 
  To enhance performance, rah has been extended to use tree_logic on large
  systems. That is, rah will check how many nodes the list contains, and if
  that number exceeds a threshold value, it constructs a subset of the list and
  sends a recursive invocation of itself to those nodes. At those nodes, the
  recursively invoked rah follows the same logic until the list is small enough
  to follow the standard logic (now the "leaf-of-tree" logic) of sending the
  command to all nodes on the list. The threshold can be specified by
  environment variable RAHTREETHRESH, or defaults to 15.
 
  In the case of a multiple-logical-node-per-physical-node system, db2_all will
  favor sending the recursive invocation to distinct physical nodes, which will
  then rsh to other logical nodes on the same physical node, thus also reducing
  inter-physical-node traffic. (This point applies only to db2_all, not rah,
  since rah always sends only to distinct physical nodes.)
 
  This version of rah has nearly identical syntax and semantics as the old
  version (supplied in the product as rah.sh_old), except for some minor
  restrictions on what options can be used:
 
  o   The user must use ksh (kornshell) as the shell. If the user is using a
      different shell, rah_tree will issue a warning and use non-tree logic.
 
  o   The single quotation mark (') prefix character, requesting echo of the
      command, cannot be honored, and is ignored.
 
  o   When both the < (all-but-me) and > (substitute <> by host index) options
      are specified, the host index is different from what non-tree rah/db2_all
      would have substituted.
 
      NOTE:  The () and ## substitutions should work identically to the old
             rah/db2_all.
 
  o   It is strongly recommended that the user ID setup at all nodes in the
      list be identical; for example, the current working directory from which
      the rah_tree command or the db2_tree command is issued should exist on
      all nodes; the rah_tree executable must be found in the current $PATH on
      all nodes (the one in effect when the rah_tree command is issued); the
      rahwaitfor executable must be found in that path, and so on. Certain
      environment differences between nodes can be tolerated, but many can not.
 
  o   The command to be executed must not start with the characters "-o, -b,
      -d, or -x", because rah_tree will interpret these to be flags.
 
  o   When specifying parallel execution, the order in which hosts return their
      output is likely to be different from the order generated by non-tree
      rah, which tends to return output in list order.
 
  o   Whenever rah_tree or db2_tree is invoked, it compares the number of
      destination nodes with a threshold value, as described above. The
      threshold can be specified by environment variable:
 
           export RAHTREETHRESH=nn
              where nn can be any positive integer
 
      or defaults to 15.
 
 
| 2.15  UNICODE/UCS-2 AND UTF-8 SUPPORT IN DB2 UDB
 
| These two standards are documented here.
 
 
| 2.15.1  INTRODUCTION
 
| The Unicode character encoding standard is a fixed-length, character encoding
| scheme that includes characters from almost all the living languages of the
| world. Unicode characters are usually shown as "U+xxxx" where xxxx is the
| hexadecimal code of the character.
 
| Each character is 16 bits (2 bytes) wide, regardless of the language. While
| the resulting 65 536 code elements are sufficient for encoding most of the
| characters of the major languages of the world, the Unicode standard also
| provides an extension mechanism, that allows for encoding as many as a
| million more characters. This extension reserves a range of code values
| (U+D800 to U+D8FF, known as "surrogates") for encoding some 32-bit characters
| as two successive code elements.
 
| The International Organization for Standardization (ISO) and International
| Electrotechnical Commission (IEC) 10646 standard (ISO/IEC 10646) specifies
| the Universal Multiple-Octet Coded Character Set (UCS) that has a 2-byte
| version (UCS-2) and a 4-byte version (UCS-4). The 2-byte version of this ISO
| standard UCS-2 is identical to Unicode without surrogates. ISO 10646 also
| defines an extension technique, for encoding some UCS-4 codes in a UCS-2
| encoded string.  This extension called UTF-16, is identical to Unicode with
| surrogates.
 
| DB2 UDB supports UCS-2, that is, Unicode without surrogates.
 
 
| 2.15.1.1  UTF-8
 
| With UCS-2 or Unicode encoding, ASCII and control characters are also two
| bytes long, and the lead byte is zero. For example, NULL is U+0000 and
| CAPITAL LETTER A is represented by U+0041. This could be a major problem for
| ASCII-based applications and ASCII file systems, because in a UCS-2 strings,
| extraneous NULLs may appear anywhere in the string. A transformation
| algorithm, known as UTF-8, can be used to circumvent this problem for
| programs that rely on ASCII code being invariant.
 
| UTF-8 (UCS Transformation Format 8), is an algorithmic transformation which
| transforms fixed-length UCS-2 and UCS-4 characters into variable-length byte
| strings. In UTF-8, ASCII characters are represented by their usual
| single-byte codes, but non-ASCII characters in UCS-2 become two or three
| bytes long. In other words, UTF-8 transforms UCS-2 characters to a multi-byte
| codeset, for which ASCII is invariant. The number of bytes for each UCS-2
| character in UTF-8 format can be determined from the following table:
 
|       UCS-2 (hex)     UTF-8 (binary)                 Description
|       ------------    --------------------------     ----------------
|       0000 to 007F    0xxxxxxx                       ASCII
|       0080 to 07FF    110xxxxx 10xxxxxx              up to U+07FF
|       0800 to FFFF    1110xxxx 10xxxxxx 10xxxxxx     other UCS-2
 
|       NOTE: The range D800 to DFFF is to be excluded from treatment
|             by the third row of this table which corresponds to the
|             UCS-4 range 0000 0800 to 0000 FFFF.
 
| In all the above, a series of x's indicate the UCS bit representation of the
| character. For example, U0080 transforms into 11000010 10000000.
 
 
| 2.15.2  UCS-2/UTF-8 IMPLEMENTATION IN DB2 UDB
 
 
| 2.15.2.1  Code Page/CCSID Numbers
 
| Within IBM, the UCS-2 code page has been registered as code page 1200. All
| code pages are defined with growing character sets, that is, when new
| characters are added to a code page, the code page number does not change.
| Code page 1200 always refers to the current version of Unicode/UCS-2, and has
| been used for UCS-2 support in DB2 UDB.
 
| A specific repertoire of the UCS standard, as defined by Unicode 2.0 and
| ISO/IEC 10646-1, has also been registered within IBM as CCSID 13488. This
| CCSID (13488) has been used internally by DB2 UDB for storing graphic string
| data in euc-Japan and euc-Taiwan databases. CCSID 13488 and code page 1200
| both refer to UCS-2, and are handled the same way except for the value of
| their "double-byte" (DBCS) space:
 
|        CP/CCSID        Single Byte (SBCS) space      Double Byte (DBCS) space
|       ---------        ------------------------      ------------------------
|         1200                   N/A                           U+0020
|         13488                  N/A                           U+3000
 
|       NOTE: In a UCS-2 database, U+3000 has no special meaning.
 
| Regarding the conversion tables, since code page 1200 is a superset of CCSID
| 13488, the exact same (superset) tables are used for both.
 
| In IBM, UTF-8 has been registered as CCSID 1208 with growing character set
| (sometimes also referred to as code page 1208). As new characters are added
| to the standard, this number (1208) will not change either. 1208 is used as
| the multi-byte code page number for DB2's UCS-2/UTF-8 support.
 
| DB2 UDB supports UCS-2 as a new multi-byte code page. The MBCS code page
| number is 1208, which is the database code page number, and the code page of
| character string data within the database. The double-byte code page number
| (for UCS-2) is 1200 which is the code page of graphic string data within the
| database. When a database is created in UCS-2/UTF-8, CHAR, VARCHAR, LONG
| VARCHAR, and CLOB data, are stored in UTF-8, and GRAPHIC, VARGRAPHIC, LONG
| VARGRAPHIC, and DBCLOB data, are stored in UCS-2. We will simply refer to
| this as a UCS-2 database.
 
 
| 2.15.2.2  Creating a UCS-2 Database
 
| By default, databases are created in the code page of the application
| creating them. Therefore, if you create your database from a UTF-8 client
| (for example, the UNIVERSAL locale of AIX), or if DB2CODEPAGE environment
| variable on the client is set to 1208, your database will be created as a
| UCS-2 database. Alternatively, you can explicitly specify "UTF-8" as the
| CODESET name, and use any valid two letter TERRITORY code supported by DB2
| UDB. Refer to the Administration Guide, and the appendix on "NLS Support" for
| a complete list of territory codes supported by DB2 UDB.
 
| For example, to create a UCS-2 database from the CLP, with the territory code
| for United States, issue:
 
|     DB2 CREATE DATABASE dbname USING CODESET UTF-8 TERRITORY US
 
| The default collation sequence for a UCS-2 database is IDENTITY, which
| provides UCS-2 code point order. Therefore, by default, all UCS-2/UTF-8
| characters are ordered and compared according to their UCS-2 code point
| sequence.
 
| All cultural-sensitive parameters such as date/time format, decimal
| separator, and others, are based on the current territory of the client.
 
| A UCS-2 database allows connection from every single-byte and multi-byte code
| page supported by DB2 UDB. Code page character conversions between client's
| code page and UTF-8 are automatically performed by the database manager. Data
| in graphic string types, is always in UCS-2 and does not go through code page
| conversions. The Command Line Processor (CLP) environment is an exception. If
| you SELECT graphic string (UCS-2) data from the CLP, the returned graphic
| string data is converted (by the CLP) from UCS-2 to the code page of your
| client environment.
 
| Every client is limited by the character repertoire, the input methods, and
| the fonts supported by its environment, but the UCS-2 database itself accepts
| and stores all UCS-2 characters. Therefore, every client usually works with a
| subset of UCS-2 characters, but the database manager allows the entire
| repertoire of UCS-2 characters.
 
| When characters are converted from a local code page to UTF-8, there is a
| possibility of expansion in the number of bytes. There is no expansion for
| ASCII characters, but other UCS-2 characters expand by a factor of two or
| three. The number of bytes of each UCS-2 character in UTF-8 format can be
| determined from the above table (section about UTF-8).
 
 
| 2.15.2.3  Data Types
 
| All data types supported by DB2 UDB, are also supported in a UCS-2 database.
| In particular, graphic string data, is supported for UCS-2 database and is
| stored in UCS-2/Unicode. Every client, including SBCS clients, can work with
| graphic string data types in UCS-2/Unicode when connected to a UCS-2
| database.
 
| A UCS-2 database is like any MBCS database where character string data is
| measured in number of bytes. When working with character string data in
| UTF-8, one should not assume that each character is one byte. In multi-byte
| UTF-8 encoding, each ASCII character is one byte, but non-ASCII characters
| take two or three bytes each. This should be taken into account when defining
| CHAR fields. Depending on the ratio of ASCII to non-ASCII characters, a CHAR
| field of size n bytes, can contain anywhere from n/3 to n characters.
 
| Using character string UTF-8 encoding versus graphic string UCS-2 data type
| also has an impact on the total storage requirements. For a situation where
| the majority of characters are ASCII, with some non-ASCII characters in
| between, storing UTF-8 data may be a better alternative because the storage
| requirements are closer to one byte per character. On the other hand, for
| situations where the majority of characters are non-ASCII characters that
| expand to three-byte UTF-8 sequences (for example, ideographic characters),
| the UCS-2 graphic-string format may be a better alternative because every
| UCS-2 character requires exactly two bytes, rather than three bytes for each
| corresponding character in UTF-8 format.
 
| SQL scalar functions that operate on character strings, such as LENGTH,
| SUBSTR, POSSTR, MAX, MIN, and the like, in MBCS environments operate on
| number of "bytes" rather than number of "characters." The behaviour is the
| same in a UCS-2 database. For example, the LENGTH of a character string
| field, is the length in the number of bytes not the number of characters. For
| a description of the behaviour of these functions, refer to the DB2 UDB SQL
| Reference.
 
| SQL CHAR data types are supported by C language's "char" data type in user
| programs. SQL GRAPHIC data types are supported by "sqldbchar" in user C
| programs. Note that, for a UCS-2 database, "sqldbchar" data is always in
| big-endian (high byte first) format.  When an application program is
| connected to a UCS-2 database, character string data is converted between the
| application code page and UTF-8 by DB2 UDB, but graphic string data is always
| in UCS-2.
 
 
| 2.15.2.4  Identifiers
 
| In a UCS-2 database, all identifiers are in multi-byte UTF-8.  Therefore, it
| is possible to use any UCS-2 character in identifiers where the use of a
| character in the extended character set (for example, an accented character,
| or a multi-byte character) is allowed by DB2 UDB. Please refer to the
| appendix "Naming Rules" in the Administration Guide for details of which
| identifiers allow use of extended characters.
 
| Clients can enter any character which is supported by their SBCS/MBCS
| environment, and all the characters in the identifiers will be converted to
| UTF-8 by the database manager. Two points need to be taken into account when
| specifying National Language characters in identifiers in a UCS-2 database:
 
| 1.  Each non-ASCII character takes two or three bytes. Therefore, an n-byte
|     identifier, can only hold somewhere between n/3 and n characters,
|     depending the ratio of ASCII to non-ASCII characters. If you have only
|     one or two non-ASCII (for example, accented) characters, the limit is
|     closer to n characters, while for an identifier which is completely
|     non-ASCII (for example, in Japanese), only n/3 characters can be used.
 
| 2.  If identifiers are to be entered from different client environments, they
|     should be defined using the common subset of characters available to
|     those clients. For example, if a UCS-2 database is to be accessed from
|     Latin-1, Arabic, and Japanese environments, all identifiers should
|     realistically be limited to ASCII.
 
 
| 2.15.2.5  UCS-2 Literals
 
| UCS-2 literals can be specified in two ways:
 
| 1.  As a GRAPHIC string constant using the G'...', or N'....' format as
|     described in the SQL Reference, Chapter 3 "Language Elements," the
|     section  "Constants," the subsection "Graphic String Constants." Any
|     literal specified in this way will be converted by the database manager
|     from the application code page to UCS-2.
 
| 2.  As a UCS-2 hexadecimal string, using the UX'....' or GX'....' format. The
|     constant specified between quotes after UX or GX must be a multiple of 4
|     hexadecimal digits. Each four digits represent one UCS-2 code point.
 
| When using the Command Line Processor (CLP), the first method is easier if
| the UCS-2 character exists in the local application code page (for example,
| for entering any code page 850 character from a terminal that is using code
| page 850). The second method should be used for characters which are outside
| the application code page repertoire (for example, for specifying Japanese
| characters from a terminal that is using code page 850).
 
 
| 2.15.2.6  Pattern Matching in a UCS-2 Database
 
| Pattern matching is one area where the behaviour of existing MBCS databases
| is slightly different from the behaviour of a UCS-2 database.
 
| For MBCS databases in DB2 UDB, the current behaviour is as follows: If the
| match-expression contains MBCS data, the pattern can include both SBCS and
| MBCS characters. The special characters in the pattern are interpreted as
| follows:
 
| o   An SBCS underscore refers to one SBCS character.
 
| o   A DBCS underscore refers to one MBCS character.
 
| o   A percent (either SBCS or DBCS) refers to a string of zero or more SBCS
|     or MBCS characters.
 
| If the match-expression contains graphic string DBCS data, the expressions
| contain only DBCS characters. The special characters in the pattern are
| interpreted as follows:
 
| o   A DBCS underscore refers to one DBCS character.
 
| o   A DBCS percent refers to a string of zero or more DBCS characters.
 
| In a UCS-2 database, there is really no distinction between "single-byte" and
| "double-byte" characters; every UCS-2 character occupies two bytes. Although
| the UTF-8 format is a "mixed-byte" encoding of UCS-2 characters, there is no
| real distinction between SBCS and MBCS characters in UTF-8. Every character
| is a UCS-2 character, irrespective of its number of bytes in UTF-8 format.
| When specifying a character string, or a graphic string expression, an
| underscore refers to one UCS-2 characters and a percent refers to a string of
| zero or more UCS-2 characters.
 
| On the client side, the character string expressions are in the code page of
| the client, and will be converted to UTF-8 by the database manager. SBCS
| client code pages, do not have any DBCS percent or DBCS underscore, but every
| supported code page contains a single-byte percent (corresponding to U+0025)
| and a single-byte underscore (corresponding to U+005F). The interpretation of
| special characters for a UCS-2 database is as follows:
 
| o   An SBCS underscore (corresponding to U+0025) refers to one UCS-2
|     character in a graphic string expression, or to one UTF-8 character in a
|     character string expression.
 
| o   An SBCS percent (corresponding to U+005F) refers to a string of zero or
|     more UCS-2 characters in a graphic string expression, or to a string of
|     zero or more UTF-8 characters in a character string expression.
 
| DBCS code pages, additionally support a DBCS percent sign (corresponding to
| U+FF05) and a DBCS underscore (corresponding to U+FF3F). These characters
| have no special meaning for a UCS-2 database.
 
| For the optional "escape-expression" which specifies a character to be used
| to modify the special meaning of the underscore and percent characters, only
| ASCII characters, or characters that expand into a two-byte UTF-8 sequence,
| are supported. If you specify an ESCAPE character which expands to a
| three-byte UTF-8 value, you will get an error message (SQL0130N error,
| SQLSTATE 22019).
 
 
| 2.15.2.7  IMPORT/EXPORT/LOAD Considerations
 
| The DEL, ASC, and PC/IXF file formats are supported for a UCS-2 database as
| described in this section. The WSF format is not supported. Also, autoloader
| is not supported for a UCS-2 database at the present time.
 
| When exporting from a UCS-2 database to an ASCII delimited (DEL) file, all
| character data is converted to the application code page. Both character
| string and GRAPHIC string data are converted to the same SBCS or MBCS code
| page of the client. This is the existing behaviour for the export of any
| database, and cannot be changed because the entire ASCII delimited file can
| have only one code page. Therefore, if you export to an ASCII delimited file,
| only those UCS-2 characters that exist in your application code page would be
| saved. Other characters are replaced with the default substitution character
| for the application code page. For UTF-8 clients (code page 1208) there is no
| data loss because all UCS-2 characters are supported by UTF-8 clients.
 
| When importing from an ASCII file (DEL or ASC) to a UCS-2 database, character
| string data is converted from the application code page to UTF-8, and GRAPHIC
| string data is converted from the application code page to UCS-2.  There is
| no data loss. If you want to import ASCII data that has been saved under a
| different code page, you should switch the data file code page before issuing
| the import command. One way to accomplish this, is to set DB2CODEPAGE to the
| code page of the ASCII data file.
 
| The range of valid ASCII delimiters, for SBCS and MBCS clients is identical
| to what is currently supported by DB2 UDB for these clients. The range of
| valid delimiters for UTF-8 clients is 0x01 to 0x7F, with the usual
| restrictions. Refer to the "IMPORT/EXPORT/LOAD Utility File Formats" appendix
| in the Command Reference for a complete list of these restrictions.
 
| When exporting from a UCS-2 database to a PC/IXF file, character string data
| is converted to the SBCS/MBCS code page of the client. GRAPHIC string data is
| not converted and is stored in UCS-2 (code page 1200). There is no data loss.
 
| When importing from an PC/IXF file to a UCS-2 database, character string data
| is assumed to be in the SBCS/MBCS code page stored in the PC/IXF header and
| GRAPHIC string data is assumed to be in the DBCS code page stored in the
| PC/IXF header. Character string data is converted by the IMPORT utility from
| the code page specified in the PC/IXF header to the code page of the client,
| and then from the client code page to UTF-8 (by the INSERT statement).
| GRAPHIC string data is converted by the IMPORT utility from the DBCS code
| page specified in the PC/IXF header directly to UCS-2 (code page 1200).
 
| LOAD directly places the data into the database and by default, assumes data
| in ASC or DEL files is in the code page of the database. Therefore, by
| default no code page conversion takes place for ASCII files. When the code
| page of the data file has been explicitly specified (using the MODIFIED BY
| codepage=x command parameter), LOAD uses this information to convert from the
| specified code page x into the database code page before loading the data.
| For PC/IXF files, LOAD always converts from the code pages specified in the
| IXF header to the database code page (1208 for CHAR, 1200 for GRAPHIC).
 
| The code page of DBCLOB files (as specified using the MODIFIED BY lobsinfile
| command parameter) is always 1200 for UCS-2. The code page of the CLOB files
| is the same as the code page of the data files being imported, loaded or
| exported. For example, for load or import using PC/IXF format, the CLOB file
| is assumed to be in the code page specified by the PC/IXF header. If the
| DBCLOB file is in ASC or DEL format, for LOAD the CLOB data is assumed to be
| in the code page of the database (unless explicitly specified otherwise using
| the MODIFIED BY codepage=x command parameter), and for IMPORT it is assumed
| to be in the client application code page.
 
| The NOCHECKLENGTHS option is always set to TRUE for a UCS-2 database because
| in a UCS-2 database, any SBCS can be connected to the database for which
| there is no DBCS code pages; and also because character strings in UTF-8
| format usually have different lengths than corresponding lengths in client
| code pages.
 
 
| 2.15.2.8  Incompatibilities
 
| For an application connected to a UCS-2 database, the graphic string data is
| always in UCS-2 (code page 1200). For applications connected to non UCS-2
| databases, the graphic string data is in the applications DBCS code page; or,
| not allowed if the application code page is SBCS. For example, when a 932
| client is connected to a Japanese non UCS-2 database, then the graphic string
| data is in code page 301. But for the 932 client applications connected to a
| UCS-2 database, the graphic string data is in UCS-2.
 
 
| 2.16  USING VIRTUAL INTERFACE (VI) ARCHITECTURE
 
| DB2 UDB now supports two implementations of the VI architecture: One from
| GigaNet and the other from ServerNet. Each is presented in this section.
 
 
| 2.16.1  OVERVIEW OF VIRTUAL INTERFACE ARCHITECTURE
 
| Virtual Interface (VI) Architecture is the inter-node communication protocol
| alternative to TCP/IP in a Windows NT massively parallel processing (MPP)
| environment. VI is a new communication architecture that was developed
| jointly by Intel, Microsoft, and Compaq to improve performance over a System
| Area Network (SAN). For more information on the architecture, visit:
 
|      http://www.viarch.org
 
| There are some similarities between the Public Interconnect which uses as an
| example Ethernet and TCP/IP and the Private Interconnect which uses a Network
| Interface Card and a protocol. The Network Interface Card and protocol used
| in this instance is a GigaNet Network Interface Card and the VI protocol.
 
| VI Architecture has low latency and high bandwidth. In a
| communication-intensive environment, using VI Architecture improves the
| overall system throughput. The greater the number of nodes in the cluster,
| and the greater the amount of data transfered, the greater the benefit from
| using VI Architecture.
 
| DB2 UDB supports VI Architecture implementations that comply with the Virtual
| Interface Architecture Specification, Version 1.0; the Intel Virtual
| Interface (VI) Architecture Developers' Guide, Version 1.0; and pass the
| "Virtual Interface Architecture Conformance Suite." The specification is
| found at:
 
|      http://www.intel.com/design/servers/vi/the_spec/specification.htm
 
| The Developer's Guide and information on the conformance suite is found at:
 
|      http://www.intel.com/design/servers/vi/developer/ia_imp_guide.htm
 
 
| 2.16.2  INSTALL DB2 UNIVERSAL DATABASE VERSION 5.2 (EEE)
 
| Detailed installation information is found in DB2 Enterprise - Extended
| Edition for Windows NT Quick Beginnings.
 
| If you are not sure of the service level of the DB2 UDB product you have
| already installed, you can determine the UDB service level by going into the
| registry:
 
| 1.  Enter regedt32 from a command prompt to edit the registry
 
| 2.  Choose HKEY_LOCAL_MACHINE
 
| 3.  Choose SOFTWARE
 
| 4.  Choose IBM
 
| 5.  Choose DB2
 
| 6.  Choose DB2 UDB Enterprise - Extended Edition
 
| 7.  Choose CurrentVersion
 
| 8.  Record the Service Level
 
| If you contact DB2 Service and Support about VI, the service level will be
| helpful to determine your installed DB2 level of code including any FixPaks.
 
| This product must be installed in each of the partitions/nodes using the
| Virtual Interface Protocol. During the installation procedure, when prompted
| choose "This machine will be an instance owning node" on each of the
| partitions/nodes.
 
| Update the hosts file with the IP address and host name for each of the
| partitions/nodes. The hosts file is found under the
| "\winnt\system32\drivers\etc\" directory on the drive where the operating
| system was installed. The hosts file must be updated on each of the nodes.
 
| Create the partitioned database (MPP) instance using the instance create
| utility. Choose one machine to act as the co-ordinator node. On this machine,
| open a DB2 Command Window and enter:
 
|      db2icrt <instance_name> /mpp /u:<username>,<password>
 
| This machine is then known as the co-ordinator node or the instance-owning
| machine. Node 0 is automatically created on this machine.
 
| On the other partitions/nodes in the database, open a DB2 Command Window and
| enter:
 
|      db2ncrt /n:<node_number> /u:<username>,<password>
|                 /i:<instance_name> /o:<instance_owner_name>
 
| The node_number is used to uniquely identify the database partition server
| within the database environment. The number must be from 1 to 999. The
| instance_owner_name is the computer name of the instance-owning machine
| (co-ordinator node).
 
| Testing the installation and create an index:
 
| 1.  Open a DB2 Command Window.
 
| 2.  Enter "set DB2INSTANCE=<instance_name>"
 
| 3.  Ensure the database manager starts on all nodes by entering: "db2start"
 
| 4.  Create a sample database by entering: "db2sampl"
 
| 5.  Connect to the sample database by entering: "db2 connect to sample"
 
| 6.  Try a few SELECT statements with the sample database.
 
| When problems occur in this environment, you can take action based on the
| type of problem as presented below:
 
| o   Instance creation fails.
 
|     Ensure "c:\profiles" is present and is present with each of the share
|     name "profiles." Ensure all partitions are "pingable" from the
|     co-ordinator node.
 
| o   DB2START fails.
 
|     Review the explanation for the returned error code by using the "db2 ?
|     sqlxxxx" command. There will be a suggested action associated with this
|     error which you should follow.
 
|     A system error may be returned. If this is the case, use a "db2stop" and
|     retry the "db2start". If the problem persists, attempt to reboot on all
|     partitions and then retry.
 
|     Ensure all partitions have the same date, time, and time zone. The time
|     does not need to be identical: within one hour is sufficient.
 
|     Ensure all the partitions are in one domain and that the user name and
|     password used belong to the following groups:
 
|         -   On the domain controller:
 
|         -   Administrators
 
|         -   Domain Administrators
 
|         -   Domain Users
 
|         -   Users
 
|         -   On other machines:
 
|         -   Administrators
 
|         -   Users
 
|     Review the contents of the "Control panel-->Services" to ensure that all
|     the "DB2:<instance_name> -X" services have the correct DB2ADMIN account
|     information.
 
| o   Command line variable has not been initialized:
 
|     Ensure you are running the command in a "DB2 command window." The title
|     of this window is "DB2 CLP."
 
| o   The "rah" command returns immediately without executing the commands
|     specified:
 
|     Run "db2set -g DB2TEMPDIR=C:\TMP" on all machines in the instance. Ensure
|     the DB2 Remote Command Service is started and with the correct DB2ADMIN
|     account information. Finally, ensure "c:\temp" and "c:\tmp" are present.
 
 
| 2.16.3  RUNNING DB2 UDB V5.2 FOR WINDOWS NT WITH GIGANET INTERCONNECT
 
| IBM announced support for Virtual Interface (VI) Architecture with DB2 UDB
| EEE V5.2. The documentation provided no specifics regarding the VI products
| that have been tested with DB2. This document provides specific information
| for GigaNet Interconnect.
 
| To find out about other products adhering to VI Architecture and supported by
| DB2 UDB EEE V5.2, please contact the DB2 UDB support organization at
| http://www.software.ibm.com/data or call 1-800-237-5511 (only in the U.S.A).
 
| To find out about GigaNet products, or to contact GigaNet Service and
| Support, please use the following URL: http://www.giganet.com/
 
 
| 2.16.3.1  Setup Procedure for GigaNet Interconnect
 
| The list of the hardware and software required to setup this environment
| include the following products:
 
| o   GigaNet GNN1000 Network Interface Card
 
| o   GigaNet GNX5000 Switch
 
| o   GigaNet GNCxx11 Copper Interconnect Cables
 
| o   GigaNet cLAN Software, Version 2.0.
 
| The steps required to ensure that GigaNet Interconnect can work with DB2 UDB
| are shown below. Each step is a summary of what is required at each step: all
| of the details associated with each step are not presented here. You should
| also use the referenced documenation at each step which does provide detailed
| instructions and direction needed.
 
| Each GigaNet GNN1000 is packaged with a GigaNet cLAN Software CD-ROM. The
| CD-ROM contains all of the necessary software to set-up the GigaNet
| Interconnect. In addition, the CD-ROM also contains the VI Architecture SDK
| and Adobe Acrobat Reader. These two items are only needed by those
| individuals that are developing VI-enabled applications.
 
| Summary of steps:
 
| 1.  Install Adapter Cards
 
| 2.  Install Switches and Cables
 
| 3.  Install Adapter Drivers
 
| 4.  Install cLAN Management Console
 
| 5.  Test the Interconnect
 
| Here are the steps:
 
| 1.  Install the GigaNet GNN1000 Network Interface Card. Please refer to the
|     GigaNet GNN1000 User Guide for installation instructions.
 
| 2.  Install the GigaNet GNX5000 Switch and Cables. Please refer to the
|     GigaNet GNX5000 User Guide for installation instructions.
 
| 3.  Install the GigaNet GNN1000 Adapter Driver software on each node
|     connected to the GNX5000 Switch. Please refer to the GigaNet GNN1000 User
|     Guide for installation instructions. Here are additional details if you
|     are installing drivers provided by GigaNet:
 
|     a.  Remove any previous version of the GNN1000 Driver already installed.
|         Removal requires the node to be re-booted.
 
|     b.  Use "Start>Setting>Control Panel>Networks>Adapters>Add" to install
|         the driver.
 
|     c.  Click HAVE DISK... and specify the Driver directory on the CD-ROM.
|         For example, if F: is your CD-ROM drive, then you would use
|         "F:\Driver"
 
|     d.  Select "GNN1000 NDIS Adapter" and then click OK.
 
|     e.  Configure Network protocols to complete the installation.
 
|     GigaNet Adapter Driver software is also available on GigaNet's web site,
|     http://www.giganet.com. Please refer to the download and installation
|     instructions found on the support page of GigaNet's web site.
 
|     The installation of the GNN1000 Adapter Driver causes the node to
|     re-boot.
 
| 4.  The GigaNet cLAN Management Console (GMC) can be used to test the
|     integrity of the GigaNet Interconnect. The GigaNet cLAN Management
|     Console is comprised of two parts: the Console, and the Agent. The Agent
|     must be installed on all nodes in the cluster. The Console can be
|     installed on any network node that has access to the nodes in the
|     cluster. The most versatile and recommended installation is that which
|     has both the Console and the Agent installed on each node in the cluster.
 
|     Install the GigaNet cLAN Management Console. Please refer to the GigaNet
|     GNN1000 User Guide for installation instructions and additional
|     information about the cLAN Management Console. Here are additional
|     details on the installation procedure:
 
|     a.  Insert the cLAN Software CD into the CD-ROM drive.
 
|     b.  Wait for the CD automatic installation menu to appear.
 
|     c.  Click on "Install cLAN Management Console."
 
|     d.  Repeat this installation procedure on each remaining node in the
|         cluster.
 
|     GigaNet cLAN Management Console software is also available on GigaNet's
|     web site, http://www.giganet.com. Please refer to the download and
|     installation instructions found on the support page of GigaNet's web
|     site.
 
|     The installation of the cLAN Management Console may cause the node to
|     re-boot.
 
| 5.  Test that the GigaNet Hardware is working. This can be done by doing the
|     following:
 
|     a.  Open the GMC. ("Programs>GigaNet>cLAN Management Console")
 
|     b.  A dialog box is displayed showing all accessible machines in the LAN.
|         Press ESC.
 
|     c.  Select CONSOLE>LOCAL from the menu bar.
 
|     d.  Confirm that all the members in the cluser are shown and that they
|         are all "Active."
 
|     e.  Select UTILITIES>VI THROUGHPUT from the menu bar. This will run a
|         throughput test to check that the data is actually going through the
|         hardware.
 
|     f.  Enter in uppercase letters the computer names of the two nodes you
|         wish to use in the test. Identify the local node as the source node.
 
|     g.  Click START MEASURING. You should see data being transferred at a
|         rate of at least 65 MB per second.
 
|     h.  Click STOP MEASURING to stop the connection test.
 
|     i.  Repeat the test for the other nodes in the cluster by measuring
|         throughput between the local node (Source) and the other nodes
|         (Sink).
 
|     If the connection test does not appear to be working, refer to the
|     troubleshooting sections of the GigaNet GNN1000 User Guide and the
|     GigaNet GNX5000 User Guide.
 
 
| 2.16.3.2  Implement DB2 to Run Using VI
 
| On each database partition server in the instance, set the following DB2
| registry variables and carry out the following tasks:
 
| o   Set DB2_VI_ENABLE=ON
 
| o   Set DB2_VI_DEVICE=nic0
 
| o   Set DB2_VI_VIPL=vipl.dll
 
| o   Enter "db2start" on the MPP instance.
 
| o   Review the db2diag.log file. There should be one message for each
|     partition stating that "VI is enabled."
 
 
| 2.16.4  RUNNING DB2 UDB V5.2 FOR WINDOWS NT WITH SERVERNET INTERCONNECT
 
| IBM announced support for Virtual Interface (VI) Architecture with DB2 EEE
| UDB V5.2. The documentation provided no specifics regarding the VI products
| that have been tested with DB2. This document provides specific information
| for ServerNet Interconnect.
 
| To find out about other products adhering to VI Architecture and supported by
| DB2 UDB EEE V5.2, please contact the DB2 UDB support organization at
| http://www.software.ibm.com/data or call 1-800-237-5511 (only in the U.S.A).
 
| To find out about ServerNet products, or to contact ServerNet Service and
| Support, please use the following URL: http://www.servernet.com/
 
 
| 2.16.4.1  Setup Procedure for ServerNet Interconnect
 
| The list of the hardware and software required to setup this environment
| include the following products:
 
| o   ServerNet PCI Adapter Driver (SPAD), (product ID T0089), version 1.3.5 or
|     later
 
| o   ServerNet Switch 1
 
| o   ServerNet Area Network Manager (SANMan), (product ID T0087), version
|     1.1.3 or later.
 
| The following are the steps required to ensure that ServerNet Interconnect
| can work with DB2 UDB. Each step is a summary of what is required at each
| step: all of the details associated with each step are not presented here.
| You should also use the referenced documenation at each step which does
| provide detailed instructions and direction needed.
 
| The steps shown below also assume that you are only using up to six (6) nodes
| in the cluster. Contact ServerNet if you have a requirement to use more than
| six nodes.
 
| Here are the steps:
 
| 1.  Install the ServerNet Network Interface Card. Please refer to the
|     ServerNet-I Virtual Interface Software Release Document, (product ID
|     N0031) for installation instructions.
 
| 2.  Install the ServerNet Switch 1. Please refer to the ServerNet-I Virtual
|     Interface Software Release Document, (product ID N0031) for installation
|     instructions.
 
| 3.  Uninstall previous ServerNet drivers. (Skip this step if this is your
|     first time installing ServerNet.)
 
|     a.  Open the Network control panel. ("Start>Setting>Control
|         Panel>Network")
 
|     b.  Click on the ADAPTERS TAB.
 
|     c.  Remove Tandem ServerNet PCI Adapter Driver.
 
|     d.  Click on the SERVICES TAB.
 
|     e.  Remove SANMan.
 
|     f.  Click on the PROTOCOLS TAB.
 
|     g.  Remove Tandem ServerNet-I VI Protocol.
 
| 4.  Install the Tandem ServerNet PCI Adapter Driver. Here are additional
|     details if you are installing using the software CD provided by
|     ServerNet:
 
|     a.  Open the Network control panel. ("Start>Setting>Control
|         Panel>Network")
 
|     b.  Click on the ADAPTERS TAB. (The Adapters screen appears.)
 
|     c.  Ensure the new ServerNet driver is placed in a separate drive and/or
|         directory. Then, from the command prompt referencing the correct
|         drive and/or directory, type "ernnn.exe -d" to start the
|         self-extracting program. ("ernnn.exe" is the name of the Engineering
|         Release followed by a number -- ERnnn.EXE -- that identifies the
|         specific version of the ServerNet driver to be installed.)
 
|     d.  Change to the drive and/or directory where the extracted files are
|         located. Change to the "Spad n.n.n \ Free" sub-directory (where
|         "n.n.n" is the specific version of the product). (If you are working
|         in a troubleshooting or a development environment, then change to the
|         "Spad n.n.n \ Checked" sub-directory instead of the "Spad n.n.n \
|         Free" sub-directory.)
 
|     e.  Rename the "oemsetup.multi_node" file to "oemsetup.inf."
 
|     f.  Choose ADD in the Adapters Tab. (The Select Adapters screen appears.)
 
|     g.  Click HAVE DISK.... (The Insert Disk screen appears.)
 
|     h.  Enter the drive and/or directory where the oemsetup.inf file is
|         located.
 
|     i.  Ensure the dialog box shows "Tandem ServerNet PCI Adapter Driver" and
|         then click OK. Ensure the list of adapters now shows the ServerNet
|         adapter. Click CLOSE.
 
|     j.  Choose YES to restart the computer. Or, select NO and continue
|         installing SANMan and the VI Software Developer's Kit (SDK).
 
| 5.  Install SANMan. Here are additional details if you are installing using
|     the software CD provided by ServerNet:
 
|     a.  Open the Network control panel. ("Start>Setting>Control
|         Panel>Network")
 
|     b.  Click on the SERVICES TAB. (The Services screen appears.)
 
|     c.  Ensure the new ServerNet driver is placed in a separate drive and/or
|         directory. Then, from the command prompt referencing the correct
|         drive and/or directory, type "ernnn.exe -d" to start the
|         self-extracting program. ("ernnn.exe" is the name of the Engineering
|         Release followed by a number -- ERnnn.EXE -- that identifies the
|         specific version of the ServerNet driver to be installed.)
 
|     d.  Choose ADD in the Services Tab. (The Select Services screen appears.)
 
|     e.  Change to the drive and/or directory where the extracted files are
|         located. Change to the "SANMan n.n.n \Free" sub-directory (where
|         "n.n.n" is the specific version of the product). (If you are working
|         in a troubleshooting or a development environment, then change to the
|         "SANMan n.n.n \ Checked" sub-directory instead of the "SANMan n.n.n \
|         Free" sub-directory.)
 
|     f.  Determine if the Switch is X or Y by looking at the light on the
|         Switch.  One light says "X," and the one light says  "Y."
 
|     g.  If an X Switch, select X=1 and Y=0. Ensure all cables are connected
|         to the X port on the network cards.
 
|     h.  If a Y Switch, select X=0 and Y=1. Ensure all cables are connected to
|         the Y port on the network cards.
 
|     i.  Provide the port number of the switch to which the network card on
|         the current machine is connected.
 
|     j.  Select "PC" for all six (6) ports.
 
| 6.  Install the Virtual Interface Protocol. Here are additional details if
|     you are installing using the software CD provided by ServerNet:
 
|     a.  Open the Network control panel. ("Start>Setting>Control
|         Panel>Network")
 
|     b.  Click on the PROTOCOLS TAB. (The Network Protocols screen appears.)
 
|     c.  Ensure the new ServerNet driver is placed in a separate drive and/or
|         directory. Then, from the command prompt referencing the correct
|         drive and/or directory, type "ernnn.exe -d" to start the
|         self-extracting program. ("ernnn.exe" is the name of the Engineering
|         Release followed by a number -- ERnnn.EXE -- that identifies the
|         specific version of the ServerNet driver to be installed.)
 
|     d.  Choose ADD in the Protocols Tab. (The Select Network Protocols screen
|         appears.)
 
|     e.  Click HAVE DISK.... (The Insert Disk screen appears.)
 
|     f.  Enter the drive and/or directory where the extracted files are
|         located.
 
| 7.  Test that the ServerNet Hardware is working. There are no test programs
|     available. Instead, simply use DB2 to test the ServerNet hardware.
 
|     If the hardware does not appear to be working, refer to the ServerNet-I
|     Virtual Interface Software Release Document, (product ID N0031) for
|     additional troubleshooting help.
 
 
| 2.16.4.2  Implement DB2 to Run Using VI
 
| On each database partition server in the instance, set the following DB2
| registry variables and carry out the following tasks:
 
| o   Set DB2_VI_ENABLE=ON
 
| o   Set DB2_VI_DEVICE=nic0
 
| o   Set DB2_VI_VIPL=vipl.dll
 
| o   Enter "db2start" on the MPP instance.
 
| o   Review the db2diag.log file. There should be one message for each
|     partition stating that "VI is enabled."
 
 
  3.0  API REFERENCE (欺阵栖你牌脓)
 
 
  3.1  SQLECREA - CREATE DATABASE
 
  To specify the IDENTITY collating sequence when creating a database, specify
  SQL_CS_NONE (which implements a binary collating sequence) in the database
  description block (SQLEDBDESC) structure.
 
 
  3.2  SQLUBKP - BACKUP DATABASE
 
  In the description of the pMediaTargetList parameter (value SQLU_ADSM_MEDIA),
  the sentence "No additional input is required." should be replaced with:
 
       If an SQLU_MEDIA_ENTRY structure is not being used to specify
       a path for the backup image, initialize the MEDIA pointer in
       the SQLU_MEDIA_LIST_TARGETS structure to NULL.
 
 
  3.3  SQLUGTPI - GET TABLE PARTITIONING INFORMATION
 
  The following section is missing from the API description:
 
       Required Connection
          Database
 
 
  3.4  SQLUHGET - RETRIEVE DDL INFORMATION FROM THE HISTORY FILE (NEW API)
 
  There is no callerac parameter available in the sqluhgne API with
  which to retrieve DDL information recorded in the history file. To retrieve this information, a new API has been created:
 
       SQL_API_RC SQL_API_FN
         sqluhget(
           unsigned short Handle,            // IN: Handle returned from sqluhops
           unsigned short CallerAction,      // IN: For special handling of command field
           unsigned long Reserved_1,         // Reserved for future use
           struct sqluhinfo * pHistoryInfo,  // IN/OUT: Pointer to entry data
           struct sqluhadm * pAdminInfo,     // IN/OUT: Pointer to enhanced adminstrative data
           void * pReserved,                 // Reserved for future use
           struct sqlca * pSqlca);           // SQLCA
 
  The parameters of this API have the same meanings as the corresponding
  parameters of the sqluhgne API, with the exception of CallerAction, which is new. The reserved fields of this API, Reserved_1 and pReserved, must be initialized
  to 0 and NULL, respectively. The possible values of CallerAction are:
 
       SQLUH_GET_NEXT_ENTRY
          Retrieves the next matching entry.
          No DDL information is returned to the caller, but the length
          field of the sqluhadm.command structure will be set to the length
          of any DDL field that exists for that entry.
       SQLUH_GET_DDL
          If this action is passed to the API immediately after
          fetching an entry, the DDL data associated with that entry is returned.
          It is the responsibility of the caller to indicate - through
          the sqluhadm.command.length field - the number of bytes
          of memory which have been allocated for DDL data to be
          returned through the sqluhadm.command.data field.
       SQLUH_GET_NEXT_ENTRY_DDL
          Retrieves the next matching entry.
          It also returns any DDL information which has been recorded for the entry.
          The caller must indicate - through the sqluhadm.command.length field -
          the number of bytes of memory which have been allocated for
          the sqluhadm.command.data field.
 
 
  3.5  SQLUHGNE - GET NEXT RECOVERY HISTORY FILE ENTRY
 
  The second parameter of this API, which was "int callerac", is now
  "struct sqluhadm *pAdminInfo". The API definition is:
 
       SQL_API_RC SQL_API_FN
         sqluhgne(
           unsigned short Handle,
           struct sqluhadm * pAdminInfo,
           struct sqluhinfo * pHistoryInfo,
           struct sqlca * pSqlca);
 
 
  3.6  SQLUHOPS - OPEN RECOVERY HISTORY FILE SCAN
 
  The description of the SQLUH_LIST_ADM_ALTER_TABLESPACE caller action
  should be changed to:
 
       Select only the ALTER TABLESPACE records that pass the other
       filters.  The DDL field associated with an entry will not be
       returned.  To retrive the DDL information for an entry,
       sqluhgne must be called with a caller action of SQLUH_GET_DDL
       immediately after the entry is fetched.
 
 
  3.7  SQLULOAD - LOAD
 
  This API affects only the partition to which an application is directly
  connected; the load utility operates on a single database partition only.
 
  The Usage Notes section incorrectly states that "summary tables" that are
  dependent on the tables being loaded are placed in check pending state. It
  should state that "summary tables defined with REFRESH IMMEDIATE", that are
  dependent on the tables being loaded, are placed in check pending state.
 
 
  3.8  SQLE-CLIENT-INFO (CONNECTION SETTINGS)
 
  The valid entries for the SQLE-CLIENT-INFO TYPE element should be changed to:
 
       SQLE_CLIENT_INFO_USERID
       SQLE_CLIENT_INFO_WRKSTNNAME
       SQLE_CLIENT_INFO_APPLNAME
       SQLE_CLIENT_INFO_ACCTSTR
 
 
  3.9  SQLFUPD
 
  Table 46, "Updateable Database Manager Configuration Parameters" has an
  additional entry for a new parameter, catalog_noauth:
 
       Parameter Name   Token                     Token Value   Data Type
       --------------   -----                     -----------   ---------
       catalog_noauth   SQLF_KTN_CATALOG_NOAUTH   314           Uint16
 
 
  3.10  SQLUHINFO (SQLUHADM)
 
  The definition of the SQLUHADM structure should be changed to:
 
       SQL_STRUCTURE sqluhadm
       {
         char           end_time[SQLUH_TIMESTAMP_SZ+1]; // OUT: Completion time stamp of the event
         char           id[SQLUH_ID_SZ+1];              // OUT: Unique identifier of a dropped table
         struct sqlca   event_sqlca;                    // OUT: SQLCA associated with the entry
         struct sqlchar command;                        // IN/OUT: DDL command information
       };
 
  NOTES:
 
  1.  Currently, command data is recorded only for ALTER TABLESPACE events.
 
  2.  It is the responsibility of the caller to initialize the
      sqluhadm.command.length field to the number of bytes of memory which
      have been allocated for this field.
 
  3.  The macro SQLUHADMSIZE(n), defined in sqlutil, is provided to help
      determine how much memory is required for an sqluhadm structure
      with space for n characters of command data.
 
 
  3.11  SQLUVPUT - WRITING DATA TO DEVICE
 
  Change "struct Init_output *," in the "C API Syntax" section to "struct Data
  *,".
 
 
  4.0  怃圊 WINDOWS 暖 OS/2 艨韬嘻筌祁幔娶
 
 
| 4.1  WINDOWS NT 母嘻 DB2START 属却惝沁七睚嘻蜚毹毓丈
 
| 仝如 "db2start" 淘棚 (托损祁 "NET START" 淘棚) 唆邛侬 Windows NT
| 艨韬母嘻骜砧栈戋堋幔娶针、邱为嵌若葑详耐朔苡嘁挝邛侬、鞋孚淘棚拟
| 淠惝沁嵌若伤·损祁席筌孚友摹牺篝宴≈NT 绥堑攀擘∽托 "DB2DIAG.LOG" 、
| 亦亦仝如 "db2start" 哝怄驮绮摊嘻嵌若蜚毹·淠圊祈菡远俾黝嘻韵寝岩、
| Windows NT 艨韬母嘻骜砧栈戋堋幔娶淠烟如页 NT 韦侪幔娶、驮盆邱为恹
| 沙邛侬韦侪幔娶嘻驺、鞋拟淠惝沁蜚毹·
 
 
  4.2  喧弭 WINDOWS NT 滔 WINDOWS 95 涅芍嘻 SQL 筌祁幔娶 (IBM
       VISUALAGE FOR COBOL)
 
  VisualAge COBOL for Windows NT 侮欺 2.2 嘻 "cob2 -dll" 淘棚却俾黝·
  "x:\sqllib\samples\cobol\bldvacbs.bat" 你祁唆喧恰 DLL 嘻韵填淘棚邱
  亩〃
 
       cob2 -dll %1.obj db2api.lib
 
  群 VisualAge COBOL 侮欺惝沁亩悄蜚毹〃
 
       屿蜚毹〃嘁挝怃邛 "E:\sqllib\samples\cobol\db2api.lib"·
 
  群蜚毹衮倾 VisualAge COBOL for Windows NT 嘻苌摹远 FixPak 你
  披盆收七·
  拟绱、倾 FixPak 偏损祁逆些、友尕暑群俾黝、偏盆祁亩悄淘棚唆探蓬
  母虞淘棚〃
 
       ilib  /nol /gi:%1 %1.obj
     ilink  /free /nol /dll  db2api.lib %1.exp %1.obj iwzrwin3.obj
 
 
  4.3  喧弭 JAVA 筌祁幔娶滔 APPLETS
 
 
  4.3.1  菝贴 MICROSOFT SDK FOR JAVA 嘻 WINDOWS 艨韬
 
  却摹远浠艨韬戆、偏牙贴倾 Windows 散淦朔苡母 DB2 SQLJ 损祁
  葬摹辍 Java Development Kit·群艨韬戆频散 DB2JVIEW、破锼祁
  王劓魔 sqlj 逆评嘻驮却 DB2 SQLJ 淘棚 (db2profc。db2profp。
  profdb 滔 profp)·邱为 DB2JVIEW=1、衮损祁 Microsoft SDK for
  Java¨木摅岩氅、邱为诶趟频 "profp"、破衮仝如页 "jview
  sqlj.runtime.profile.util.ProfilePrinter"·邱为 DB2JVIEW=0
  托栖菝贴、衮损祁 Sun JDK¨木摅岩氅、邱为诶趟频 "profp"、破衮
  仝如页 "java sqlj.rutnime.profile.util.ProfilePrinter"·
  "sqlj" 淘棚衮土堠群戆、赔摹贴损祁 Sun JDK 唆仝如·
 
 
| 4.3.2  浠嘻诜谆暖腮韦鹇幔娶曦 AND SQLJ 些弭罹嘻 SCRIPT
 
| 欺蔟卮绁魔摹髓枳 Java 畀梭幔娶嘻驮伉嘻收·竺囚幔施滔 UDF 幔娶
| 呢拧醛远杀嘻诜谆滔腮韦鹇幔娶·菡淼偏诜谆瘼鹇母嘻损祁席诜
| 肟軎囚探腮韦鹇瘼鹇母嘻竺囚幔施滔 UDF·气些淠炭摊爨嘻篁争邱亩〃
 
| DB2STP         堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 DB2SPCLI·
 
| DB2UDF         堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 DB2UDCLI·
 
| STP            堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 STPCLI·
 
| UDF            堍倾岩诜谆幔娶·趟频破嘻腮韦鹇幔娶岩 UDFSRV·
 
| 呢喧恰 Script 篁 "embprep" 唆些弭罹滔葙岣 SQLJ 幔娶·破岂
| "makefile" 趟频、倾 Java 涅芍嘻 SQL 畀梭幔娶母仝如 "db2profc"
| 淘棚·破诈萋骜砧栈。损祁席 ID 滔葑如睿却偏蛸祁嘻趴戆、鞒群筚煞
| 诜谆瘼鹇诜肟軎葙岣摊 DB2 腮韦鹇母嘻骜砧栈·
 
 
  5.0  喧弭 UNIX 艨韬嘻筌祁幔娶
 
 
  5.1  SCO UNIXWARE 7
 
 
| 5.1.1  憔砒竺囚幔施嘻酞戆
 
| 倾 SCO UnixWare 7 你、贴屮倾诜谆幔娶你仍赔栖忘睚憔砒嘻酞戆拟
| 锼祁王诜谆幔娶驮趟频嘻竺囚幔施篁争栈·页魔憔砒酞戆仍衮诜谆
| 幔娶屿浠罹睿嘻贫摹远派挝摅岩损祁罹蛸恸 "-Wl,-Bexport"、破偏
| 憔砒驮却贴屮倾诜谆幔娶你嘻酞戆·菡远蛸恸呢浠炝摊 SCO UnixWare
| 7 C 暖 C++ 嘻 make 篁争你、盆罹畀梭诜谆幔娶 "fillcli" (破淠
| 趟频菡髓耄似嘻竺囚幔施篁争栈 "fillsrv"·孚 make 篁争暖畀梭幔娶
| 软王 "sqllib/samples/c" 暖 "sqllib/samples/cpp" 气蜱你·
 
 
  5.1.2  MICRO FOCUS COBOL 岣蛸恸
 
  倾 "Micro Focus COBOL" 阳姣你、"bldmfcc" Script 篁你嘻岣蛸
  恸 "-lthread" 呢拟锹腈友、寝页昱篁争栈呢索墨 DB2 篁争栈、破岂
  "-ldb2" 蛸恸闲泣·
 
 
  5.2  喧弭 JAVA 筌祁幔娶滔 APPLETS
 
 
  5.2.1  菝贴艨韬〃HP-UX。SCO UNIXWARE 7
 
  堍倾友倾 HP-UX 母喧弭滔仝如 Java、腈友 HP-UX Developer's Kit
  for Java Release 1.1.3 (托 1.1.3 盆母)·
 
  DB2 拟排呶 HP-UX 滔 SCO UnixWare 腮韦鹇母嘻 Java 竺囚幔施滔
  Java 损祁席贴屮酞戆 (UDF)·寝页却群宇瘫、驮盆亩悄 Java 畀梭
  幔娶拟卒枳 HP-UX 滔 SCO UnixWare 母嘻 DB2 骜砧栈仝如〃
 
       DB2Stp.java
       DB2Udf.java
       CatUdf.sqlj
       DropUdf.sqlj
       Stp.sqlj
       Udfsrv.java
 
 
| 5.2.2  CLOSE() 派挝嘻 SILICON GRAPHICS IRIX 宇瘫
 
| 倾 Silicon Graphics IRIX 母、葙罾蝇哌 "close()" 派挝偏卒淠葸醛
| 菝蔌岩呢稀嘻俾黝·友尕暑孚俾黝针、倾拳怩套摄哝怄、铢葙罾蝇哌
| 溶侬蒺·
 
 
  5.2.3  浠嘻诜谆暖腮韦鹇幔娶曦 AND SQLJ 些弭罹嘻 SCRIPT
 
  欺蔟卮绁枳 Java 畀梭幔娶嘻摹髓收·竺囚幔施滔 UDF 幔娶呢拧醛
  远杀嘻诜谆滔腮韦鹇幔娶·菡淼偏诜谆瘼鹇母嘻损祁席诜肟軎
  囚探腮韦鹇瘼鹇母嘻竺囚幔施滔 UDF·气些淠炭摊爨嘻篁争邱亩〃
 
  DB2STP         堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 DB2SPCLI·
 
  DB2UDF         堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 DB2UDCLI·
 
  STP            堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 STPCLI·
 
  UDF            堍倾岩诜谆幔娶·破趟频嘻腮韦鹇幔娶岩 UDFSRV·
 
  呢喧恰 Script 篁 "embprep" 唆些弭罹滔葙岣 SQLJ 幔娶·破岂
  "makefile" 趟频、倾 Java 涅芍嘻 SQL 畀梭幔娶母仝如 "db2profc"
  淘棚·破诈萋骜砧栈。损祁席 ID 滔葑如睿却偏蛸祁嘻趴戆、鞒群筚煞
  诜谆瘼鹇诜肟軎葙岣摊 DB2 腮韦鹇母嘻骜砧栈·
 
 
  6.0  CLI GUIDE AND REFERENCE (欺阵栖你牌脓)
 
 
  6.1  SQLPREPARE()
 
  The description of SQLPrepare() does not indicate that deferred prepare is
  now ON by default.
 
  This means that the processing of the SQL statements passed to the database
  using SQLPrepare() does not take place when the SQLPrepare() function is
  called. Instead, it is processed when SQLExecute() is called.
 
  Minimal error checking is performed by DB2 CLI when SQLPrepare() is called
  (that is, valid function arguments, and so on). The true SQLSTATEs are not
  returned from the prepare until SQLExecute() is called. Your application
  should therefore expect SQLSTATEs from SQLPrepare() after the call to
  SQLExecute(), followed by SQLSTATEs from the SQLExecute() call itself.
 
  For more information see "Deferred Prepare now on by Default" in "Appendix B.
  Migrating Applications", in the section "Changes from Version 2.1.1 to
  5.0.0". This describes how to turn deferred prepare off for Version 2
  programs, as well as a further description of the deferred prepare process.
 
 
  6.2  SQLDISCONNECT()
 
  The description states that cursors are closed by a call to SQLDisconnect().
  This is not the case, however, with stored procedures.
 
  An application should not rely on SQLDisconnect() to close cursors, even if
  it is not a stored procedure. In both cases, the cursor should be closed
  using SQLCloseCursor(), then the statement handle freed with a call to
  SQLFreeHandle() with a HandleType of SQL_HANDLE_STMT.
 
 
  6.3  USING STORED PROCEDURES - PROGRAMMING STORED PROCEDURES TO RETURN
  RESULT SETS
 
  The book indicates that the stored procedures must be run on a remote server.
  This is no longer the case. Stored procedures running on a local server can
  return result sets.
 
  The book indicates that the stored procedure should call SQLFreeStmt() with
  either SQL_DROP or SQL_CLOSE; however, only SQL_CLOSE should be used.
 
 
  6.4  STORED PROCEDURE CATALOG TABLES
 
  All stored procedures should be registered in the new SYSCAT.PROCEDURES and
  SYSCAT.PROCPARMS catalog tables using the CREATE PROCEDURE statement. For
  more information about this SQL statement, see the SQL Reference.
 
  If the stored procedures are not registered using the CREATE PROCEDURE
  statement, CLI or ODBC applications will not know that they exist. For more
  information, see the section "Replacement of the Pseudo Catalog Table for
  Stored Procedures" in the Migration Appendix.
 
 
| 6.5  SQLFETCHSCROLL(SQL_FETCH_RELATIVE, -1)
 
| There is an error in the documentation for SQLFetchScroll() in the version
| 5.0 Call Level Interface Guide and Reference. The table for
| SQL_FETCH_RELATIVE rules should be replaced with the following table:
 
| SQL_FETCH_RELATIVE rules:
 
  +---------------------------------------------------------------------------+
| | Table 3. SQL_FETCH_RELATIVE Rules:                                        |
  +-------------------------------------------+-------------------------------+
| | CONDITION                                 | FIRST ROW OF NEW ROWSET       |
  +-------------------------------------------+-------------------------------+
| | (Before start AND FetchOffset > 0) OR     | -- (a)                        |
| | (After end AND FetchOffset < 0)           |                               |
  +-------------------------------------------+-------------------------------+
| | Before start AND FetchOffset <= 0         | Before start                  |
  +-------------------------------------------+-------------------------------+
| | CurrRowsetStart = 1 AND FetchOffset < 0   | Before start                  |
  +-------------------------------------------+-------------------------------+
| | CurrRowsetStart > 1 AND CurrRowsetStart + | Before start                  |
| | FetchOffset < 1 AND |FetchOffset| >       |                               |
| | RowsetSize                                |                               |
  +-------------------------------------------+-------------------------------+
| | CurrRowsetStart > 1 AND CurrRowsetStart + | 1 (b)                         |
| | FetchOffset < 1 AND |FetchOffset| <=      |                               |
| | RowsetSize                                |                               |
  +-------------------------------------------+-------------------------------+
| | 1 <= CurrRowsetStart + FetchOffset <=     | CurrRowsetStart + FetchOffset |
| | LastResultRow                             |                               |
  +-------------------------------------------+-------------------------------+
| | CurrRowsetStart + FetchOffset >           | After end                     |
| | LastResultRow                             |                               |
  +-------------------------------------------+-------------------------------+
| | After end AND FetchOffset >= 0            | After end                     |
  +-------------------------------------------+-------------------------------+
 
 
  7.0  COMMAND REFERENCE (欺阵栖你牌脓)
 
 
  7.1  DB2CMD - OPEN DB2 COMMAND WINDOW
 
  This command is available on Windows NT, Windows 95, and Windows 98.
 
  The following switches are now supported:
 
       /c   Invoke command.exe with the /c option (that is, execute the command,
            and then terminate.  For example, "db2cmd /c dir" causes the "dir" command
            to be invoked in a command window, and then the command window closes.
 
       /w   Wait until the cmd.exe process ends.
            For example, "db2cmd /c /w dir" invokes the "dir" command, and db2cmd.exe
            does not end until the command window closes.
 
       /i   Run the command window, sharing the same console and inheriting file handles.
            For example, "db2cmd /c /w /i db2 get dbm cfg > myoutput"
            invokes cmd.exe to run the db2 command and to wait for its completion.
            A new console is not assigned, and stdout is piped to file "myoutput".
 
       /t   Instead of using "DB2 CLP" as the title of the command window,
            inherit the title from the invoking window. This is useful
            if you want to set up an icon with a different title that
            invokes "db2cmd /t".
 
  NOTE:  All switches must appear before any commands to be executed. For
         example: db2cmd /t db2
 
  If DB21061E ("Command line environment not initialized.") is returned when
  bringing up the CLP-enabled DB2 window, or running CLP commands on Windows 95
  or Windows 98, the operating system may be running out of environment space.
  Check the config.sys file for the SHELL environment setup parameter, and
  increase its value accordingly. For example:
 
       SHELL=C:\COMMAND.COM C:\ /P /E:32768
 
 
  7.2  DB2EVA - EVENT ANALYZER
 
  The "Command Parameters" section is missing the following description:
 
       -evm evmon-name
          Specifies the name of the event monitor whose traces are to be analyzed.
 
 
  7.3  DB2EVMON - EVENT MONITOR PRODUCTIVITY TOOL
 
  The "-db" and "-evm" keywords are case sensitive.
 
 
  7.4  DB2LOOK - DB2 STATISTICS EXTRACTION TOOL
 
  Option "-a" generates statistics for all users on the database. If used with
  option "-e", it generates the DDL for all user tables in the database, but
  statistics are not generated.
 
  NOTES:
 
  1.  Some DDL characteristics are not extracted by db2look.
 
  2.  If neither -u nor -a is specified, the environment variable USER is used.
      On UNIX based systems, this variable does not have to be explicitly set;
     on Windows NT, however, there is no default value for the USER environment
     variable: on this platform, a user variable in the SYSTEM variables must
     be set, or a "set USER=<username>" must be issued for the session.
 
 
  7.5  DB2SET - DB2 PROFILE REGISTRY COMMAND
 
  The "Command Parameters" section has been changed to:
 
       variable=value
          Sets a specified variable to a specified value.
          To delete a variable, do not specify a value for the specified variable.
          Changes to settings take effect after the instance has been restarted.
       -g
          Accesses the global profile variables.
       -i instance
          Specifies the instance profile to use instead of the current, or default.
       node-number
          Specifies a number listed in the db2nodes.cfg file.
       -all
          Displays all occurrences of the local environment variables as defined in:
            o The environment, denoted by [e]
            o The node level registry, denoted by [n]
            o The instance level registry, denoted by [i]
            o The global level registry, denoted by [g].
       -null
          Sets the value of the variable at the specified registry level to null.
          This avoids having to look up the value in the next registry level,
          as defined by the search order.
       -r instance
          Resets the profile registry for the given instance.
       -n DAS node
          Specifies the remote DB2 administration server node name.
       -u user
          Specifies the user ID to use for the administration server attachment.
       -p password
          Specifies the password to use for the administration server attachment.
       -l
          Lists all instance profiles.
       -lr
          Lists all supported registry variables.
       -v
          Specifies verbose mode.
       -h/-?
          Displays help information. When this option is specified,
          all other options are ignored, and only the help information is displayed.
 
 
  7.6  DB2UPD52 - UPDATE CATALOG TO SUPPORT VERSION 5.2
 
  Although this utility is installed at the server, it can be run at a client;
  to do so, copy the executable from the server to the client.
 
  In an MPP environment, the utility must be run from the catalog node of the
  specified database.
 
 
  7.7  BACKUP DATABASE
 
  To use tape devices, DB2 users on SCO UnixWare 7 need to specify
  BUFFER to be 16. The default value of BUFFER is 1024 pages. If BUFFER is set
  to zero, the database manager configuration parameter BACKBUFSZ must be set
  to 16.
 
 
  7.8  EXPORT
 
  Table 6 ("Valid Delimiters"), and all references to it, should be removed.
  The information contained in the note at the bottom of the table, and the restrictions
  that follow the note, are correct, however.
 
  NOTE:  In a DBCS environment, the pipe (|) character delimiter is not supported.
 
  Replace the section "DB2 Data Links Manager Considerations" in the Usage
  Notes with the following:
 
  To ensure that a consistent copy of the table and the corresponding files
  referenced by the DATALINK columns are copied for export, do the following:
 
 
  1.  To ensure that no update transactions are in progress when the export
      utility is run, issue the command QUIESCE TABLESPACES FOR TABLE tablename
      SHARE.
 
  2.  Issue the EXPORT command.
 
  3.  Run the dlfm_export utility with root authority at each file server.
      Input to the dlfm_export utility is the control file, server_name, which
      is generated by the export utility. The dlfm_export utility must be run
      with root authority in order to successfully archive files to which the
      DLFM administrator may not have access.
 
  4.  To make the table available for updates, issue the command QUIESCE
      TABLESPACES FOR TABLE tablename RESET.
 
  EXPORT is executed as an SQL application. The rows and columns satisfying the
  SELECT statement conditions are extracted from the database. For the DATALINK
  columns, the SELECT statement should not specify any scalar function.  The
  export utility uses APIs to extract parts of the DATALINK value, such as link
  type, file server name, file path name, and comments.
 
  Successful execution of EXPORT results in generation of the following files:
 
  o   An export data file as specified in the EXPORT command. A DATALINK column
      value in this file is in the format described on page 290. When the
      DATALINK column value is the SQL NULL value, handling is the same as that
      for other data types.
 
  o   Control files server_name, which are generated for each file server (on
      the Windows operating system and on OS/2, a single control file,
      ctrlfile.lst, is used by all the file servers). A control file contains
      the URLs for all the files that are to be exported from that file server.
 
  Use the dlfm_export utility to export files from a file server as follows:
 
        Usage: dlfm_export <control file name> [<tar file name>]
        Description:
          <control file name>  This is the file name that was generated by
                               running the export utility on the DB2 client.
          <tar file name>      This is the name of the archive file that will
                               be generated (the default is export.tar
                               in the current working directory).
 
  A corresponding utility called dlfm_import is provided to retrieve and to
  restore files from the archive that dlfm_export generates. This utility must
  be used whether the archived files are being restored on the same or on a
  different file server. Use the dlfm_import utility to retrieve files from the
  archive as follows:
 
        Usage: dlfm_import [<tar file name>]
        Description:
          <tar file name>      This is the name of the archive file that will
                               be used to recover the files (the default is export.tar
                               in the current working directory).
 
  NOTES:
 
  1.  Both dlfm_export and dlfm_import utilities must be run with root
      authority. In the case of dlfm_export, there may be files to be archived
      to which the DLFM administrator does not have access. In the case of
      dlfm_import, root authority is required because the user may want to
      restore the archived files on a different file server, one that may not
      have the same directory structure and user IDs as the file server on
      which the dlfm_export utility was run.
 
  2.  The File Manager does not have to be running in order for the dlfm_export
      and the dlfm_import utilities to run.
 
  3.  When running the dlfm_import utility on a file server other than the one
      on which dlfm_export was run, the files will be restored on the correct
      paths. The files will be owned by root, in case some of the user IDs do
      not exist on the new machine. Before inserting the corresponding DATALINK
      values into the database, it is the administrator's responsibility to
      ensure that all files have the correct permissions and belong to the
      correct user IDs.
 
  EXPORTING BETWEEN INSTANCES
 
  The table below shows how to export DB2 data and the files that are
  referenced by the instance called SystemA to the instance called SystemB.
  SystemA uses file servers DLFM1 and DLFM2. SystemB uses file servers DLFMX
  and DLFMY. The files on DLFM1 will be exported to DLFMX, and the files on
  DLFM2 will be exported to DLFMY.
 
    +-----------------------------------------------------------------------------+
    | InstanceA with File Servers DLFM1 and DLFM2  | Step                          |
    +------------------------------------------------------------------------------+
    | DB2 Data | File1 for DLFM1 | File2 for DLFM2 |                               |
    | on File  |                 |                 |                               |
    +----------+-----------------+-----------------+-------------------------------+
    |          | Run the         | Run the         | 1.Run dlfm_export (as root)  |
    |          | dlfm_export     | dlfm_export     | on both file servers.        |
    |          | command         | command         | This will produce an archive  |
    |          |                 |                 | on both file servers.        |
    +----------+-----------------+-----------------+-------------------------------+
 
    +-----------------------------------------------------------------------------+
    | InstanceB with File Servers DLFMX and DLFMY  | Step                          |
    +------------------------------------------------------------------------------+
    |          | On DLFMX,       | On DLFMY,       | 2. Run dlfm_import (as root) |
    |          | restore from an | restore from an | on both file servers.        |
    |          | archive         | archive         |                               |
    +----------+-----------------+-----------------+-------------------------------+
    |          |                 |                 | 3. Run the IMPORT command on |
    |          |                 |                 | InstanceB, with the parameter |
    |          |                 |                 | DL_URL_REPLACE_PREFIX to      |
    |          |                 |                 | specify the appropriate file  |
    |          |                 |                 | server for each exported file.|
    +----------+-----------------+-----------------+-------------------------------+
 
    +-----------------------------------------------------------------------------+
    | After the import utility is run on InstanceB, InstanceA data and all         |
    | files referenced by DATALINK columns are imported.                          |
    +------------------------------------------------------------------------------+
 
 
  7.9  GET DATABASE MANAGER CONFIGURATION
 
 
  7.9.1  NEW PARAMETER CATALOG_NOAUTH
 
  A new parameter, catalog_noauth, specifies whether users are able to catalog
  and uncatalog databases and nodes, or DCS and ODBC directories, without
  SYSADM authority. The default value (0) for this parameter indicates that
  SYSADM authority is required. When this parameter is set to 1 (yes), SYSADM
  authority is not required.
 
 
| 7.9.2  TRUST_ALLCLNTS UPDATED
 
| "TRUST_ALLCLNTS" as well as "TRUST_CLNTAUTH" are used to determine where
| users are validated for the database environment. By accepting the default
| for "TRUST_ALLCLNTS", all clients are treated as trusted clients. This means
| a level of security is available at the client, and that users can be
| validated at the client. Other options may be used to protect the server
| against certain clients based on their platform or database protocol.
 
 
  7.10  IMPORT
 
  In an MPP environment, if a database was bound using the INSERT BUF option,
  buffered insert will be disabled during any import operation to that database
  if the INSERT_UPDATE is specified.
 
  NOCHECKLENGTHS is supported for both the ASC and the IXF file formats. This
  option does not have to be used with the FORCEIN modifier. If NOCHECKLENGTHS
  is specified, an attempt is made to import each row, even if the source data
  has a column definition that exceeds the size of the target table column.
  Such rows may be successfully imported if code page conversion causes the
  source data to shrink; for example, 4-byte EUC data in the source could
  shrink to 2-byte DBCS data in the target, and require half the space. This
  option is particularly useful if it is known that the source data will fit in
  all cases despite mismatched column definitions.
 
  The current default priority for delimiters is: record delimiter,
  character delimiter, column delimiter. To protect existing customer applications that
  depend on the older priority, a new file type modifier, DELPRIORITYCHAR, has
  been created for the import utility. This modifier reverts the delimiter
  priorities to: character delimiter, record delimiter, column delimiter. The
  syntax is: db2 import ... modified by delprioritychar ...
 
 
  7.11  LIST DATABASE DIRECTORY
 
  There can be a maximum of eight opened database directory scans per process.
  To overcome this restriction for a batch file that issues more than eight
  LIST DATABASE DIRECTORY commands within a single DB2 session, convert the
  batch file into a shell script. The "db2" prefix generates a new DB2 session
  for each command.
 
 
  7.12  LOAD
 
  This command affects only the partition to which a direct connection exists;
  the load utility operates on a single database partition only.
 
  The COPY option is not supported for tables with DATALINK columns.
 
  The REPLACE option is not supported for tables with DATALINK columns.
 
  The NONRECOVERABLE clause should not be used when DATALINK columns with the
  FILE LINK CONTROL attribute are present in - or being added to - the table.
 
  There is a limit on the combination of DATALINK columns and the number of
  DLFMs used. There can be at most 256 unique combinations of DLFMs and
  DATALINK columns in a table. For example, the table can have a maximum
  of 128 DATALINK columns if the number of DLFMs configured is two.
 
  Load copy to tapes is not supported for DB2 servers running on SCO UnixWare 7.
 
  The Usage Notes section incorrectly states that "summary tables" that are
  dependent on the tables being loaded are placed in check pending state. It
  should state that "summary tables defined with REFRESH IMMEDIATE", that are
  dependent on the tables being loaded, are placed in check pending state.
 
  NOCHECKLENGTHS is supported for both the ASC and the IXF file formats. This
  option does not have to be used with the FORCEIN modifier. If NOCHECKLENGTHS
  is specified, an attempt is made to load each row, even if the source data
  has a column definition that exceeds the size of the target table column.
  Such rows may be successfully loaded if code page conversion causes the
  source data to shrink; for example, 4-byte EUC data in the source could
  shrink to 2-byte DBCS data in the target, and require half the space. This
  option is particularly useful if it is known that the source data will fit in
  all cases despite mismatched column definitions.
 
  The current default priority for delimiters is: record delimiter,
  character delimiter, column delimiter. To protect existing customer applications
  that depend on the older priority, a new file type modifier, DELPRIORITYCHAR,
  has been created for the load utility. This modifier reverts the delimiter
  priorities to: character delimiter, record delimiter, column delimiter. The
  syntax is: db2 load ... modified by delprioritychar ... The new option is not
  supported in an MPP environment, nor is it supported by the AutoLoader. Load
  SMP exploitation is disabled when this option is specified (CPU_PARALLELISM
  is forced to a value of 1). The new option is mutually exclusive
  with the "DUMPFILE" feature, and is supported only for the DEL file format.
 
 
  7.13  RECONCILE
 
  There is an error in the description of "DLREPORT filename". There is no
  default value for this parameter.
 
  The file name must be a fully qualified file name. For example:
 
       /home/user/report.out
 
 
  7.14  RESTORE DATABASE
 
  If the WITHOUT DATALINK option is not specified, and the DB2 File Manager
  containing the DATALINK data is unavailable, the restore operation will fail.
 
  If this option is specified, and the DB2 File Manager containing the DATALINK
  data is unavailable, all table spaces which contain tables with DATALINK
  values on the unavailable server are placed in RESTORE PENDING state.
 
  To use tape devices, DB2 users on SCO UnixWare 7 need to specify
  BUFFER to be 16. The default value of BUFFER is 1024 pages. If BUFFER is set
  to zero, the database manager configuration parameter BACKBUFSZ must be set
  to 16.
 
 
| 7.15  START DATABASE MANAGER
 
| When running the "db2start" command (or using the "NET START" command) to
| start the database manager on the Windows NT environment, the command will
| not return any warnings if any communication subsystem failed to start. The
| user should always examine the NT Event Log or the "DB2DIAG.LOG" for any
| errors that may have occurred during the running of "db2start". This occurs
| because the database manager on a Windows NT environment is implemented as an
| NT service, and hence does not return an error if the service is started
| successfully.
 
 
  8.0  EMBEDDED SQL PROGRAMMING GUIDE (欺阵栖你牌脓)
 
 
  8.1  WRITING USER-DEFINED FUNCTIONS (INTERFACE BETWEEN DB2 AND A UDF/THE
  ARGUMENTS PASSED FROM DB2 TO A UDF)
 
  There are two changes to the numbered list under the "dbinfo" argument:
 
  o   Insert a new item 17 in the list. The new item 17 reads as follows:
 
           17. Unique application identifier (appl_id)
 
              This field is a pointer to a C null-terminated string which
              uniquely identifies the application's connection to DB2.
              It is regenerated at each database connect.
 
              The string has a maximum length of 32 characters, and its
              exact format depends on the type of connection established
              between the client and DB2.  Generally it takes the form
 
                <x>.<y>.<ts>
 
              where the <x> and <y> vary by connection type, but the <ts>
              is a 12 character time stamp of the form YYMMDDHHMMSS, which
              is potentially adjusted by DB2 to ensure uniqueness.
 
              Example:  *LOCAL.db2inst.980707130144
 
  o   Change the existing item 17 to item 18, and within this item, change "24
      characters" to "20 characters":
 
           17. Reserved field (resd2)
 
              This field is for future use. It is defined as 20 characters long.
 
 
  8.2  PROGRAMMING IN C AND C++ (PROGRAMMING CONSIDERATIONS/HOST VARIABLES)
 
 
  8.2.1  DECLARING HOST VARIABLES
 
  BIGINTs can now be declared in one of three ways:
 
  o   long long
 
  o   __int64 // (A double underscore precedes "int64".)
 
      This declaration is specific to the Microsoft compiler.
 
  o   sqlint64
 
      This is useful when writing platform-independent applications. The DB2
      UDB sqlsystm.h header file will type define sqlint64 as "__int64" on the
      Windows NT platform when using the Microsoft compiler; otherwise,
      sqlint64 will be type defined as "long long".
 
 
  8.2.2  HANDLING GRAPHIC HOST VARIABLES (WINDOWS OPERATING SYSTEM)
 
  When specifying the WCHARTYPE CONVERT option on a Windows platform, you should note
  that wchar_t on Windows platforms is Unicode. Therefore, if your C/C++ compiler's
  wchar_t is not Unicode, the wcstombs() function call may fail with SQLCODE -1421
  (SQLSTATE=22504). If this happens, you can specify the WCHARTYPE NOCONVERT option,
  and explicitly call the wcstombs() and mbstowcs() functions from within your program.
 
 
| 8.3  PROGRAMMING IN COBOL (HOST STRUCTURE SUPPORT)
 
| The COBOL precompiler supports declarations of group data items in the host
| variable declare section. Among other things, this provides a shorthand for
| referring to a set of elementary data items in an SQL statement. For example,
| the following group data item can be used to access some of the columns in
| the STAFF table of the SAMPLE database:
 
|          01 staff-record.
|              05 staff-id       pic s9(4) comp-5.
|              05 staff-name.
|                  49 l          pic s9(4) comp-5.
|                  49 d          pic x(9).
|              05 staff-info.
|                  10 staff-dept pic s9(4) comp-5.
|                  10 staff-job  pic x(5).
 
| Group data items in the declare section can have any of the valid host
| variable types described above as subordinate data items. This includes all
| numeric and character types, as well as all large object types. THE
| RESTRICTION OF ALLOWING ONLY ONE LEVEL OF GROUP DATA ITEMS HAS BEEN REMOVED,
| AND THEY CAN NOW BE NESTED UP TO 10 LEVELS. Note that you must declare
| VARCHAR character types with the subordinate items at level 49, as in the
| above example. If they are not at level 49, the VARCHAR is treated as a group
| data item with two subordinates, and is subject to the rules of declaring and
| using group data items. In the example above, "staff-info" is a group data
| item, whereas "staff-name" is a VARCHAR. The same principle applies to LONG
| VARCHAR, VARGRAPHIC and LONG VARGRAPHIC. You may declare group data items at
| any level between 02 and 49.
 
| You can use group data items and their subordinates in four ways:
 
| METHOD 1.
 
| The entire group may be referenced as a single host variable in an SQL
| statement:
 
|             EXEC SQL SELECT id, name, dept, job
|               INTO :staff-record
|               FROM staff WHERE id = 10 END-EXEC.
 
| The precompiler converts the reference to staff-record into a list, separated
| by commas, of all the subordinate items declared within staff-record. Each
| elementary item is qualified with the group names of all levels to prevent
| naming conflicts with other items. This is equivalent to the following
| method.
 
| METHOD 2.
 
| The second way of using group data items:
 
|             EXEC SQL SELECT id, name, dept, job
|               INTO
|               :staff-record.staff-id,
|               :staff-record.staff-name,
|               :staff-record.staff-info.staff-dept,
|               :staff-record.staff-info.staff-job
|               FROM staff WHERE id = 10 END-EXEC.
 
| NOTE:  The reference to "staff-id" is qualified with its group name using the
|        prefix "staff-record.", and not "staff-id" of "staff-record" as in
|        pure COBOL.
 
| Assuming there are no other host variables with the same names as the
| subordinates of staff-record, the above statement can also be coded as in
| method 3, eliminating the explicit group qualification.
 
| METHOD 3.
 
| Here, subordinate items are referenced in a typical COBOL fashion, without
| being qualified to their particular group item:
 
|             EXEC SQL SELECT id, name, dept, job
|               INTO
|               :staff-id,
|               :staff-name,
|               :staff-dept,
|               :staff-job
|               FROM staff WHERE id = 10 END-EXEC.
 
| As in pure COBOL, this method is acceptable to the precompiler as long as a
| given subordinate item can be uniquely identified. If, for example,
| "staff-job" occurs in more than one group, the precompiler issues an error
| indicating an ambiguous reference:
 
|             SQL0088N Host variable "staff-job" is ambiguous.
 
| METHOD 4.
 
| To resolve the ambiguous reference, partial qualification of the subordinate
| item can also be used.
 
|             EXEC SQL SELECT id, name, dept, job
|               INTO
|               :staff-id,
|               :staff-name,
|               :staff-info.staff-dept,
|               :staff-info.staff-job
|               FROM staff WHERE id = 10 END-EXEC.
 
| Because a reference to a group item alone, as in method 1, is equivalent to a
| comma-separated list of its subordinates, there are instances where this type
| of reference leads to an error. For example:
 
|             EXEC SQL CONNECT TO :staff-record END-EXEC.
 
| Here, the CONNECT statement expects a single character-based host variable.
| By giving the "staff-record" group data item instead, the host variable
| results in the following precompile-time error:
 
|             SQL0087N Host variable "staff-record" is a structure used where
|                      structure references are not permitted.
 
| Other uses of group items which cause an SQL0087N to occur include PREPARE,
| EXECUTE IMMEDIATE, CALL, indicator variables, and SQLDA references.  Groups
| with only one subordinate are permitted in such situations, as are references
| to individual subordinates, as in method 2, 3 and 4 above.
 
| INDICATOR TABLES
 
| The COBOL precompiler supports the declaration of tables of indicator
| variables, which are convenient to use with group data items. They are
| declared as follows:
 
|        01 <indicator-table-name>.
|            05 <indicator-name> pic s9(4) comp-5
|                                occurs <table-size> times.
 
| For example:
 
|        01 staff-indicator-table.
|            05 staff-indicator pic s9(4) comp-5
|                               occurs 7 times.
 
| This indicator table can be used effectively with the first format of group
| item reference above:
 
|         EXEC SQL SELECT id, name, dept, job
|           INTO :staff-record :staff-indicator
|           FROM staff WHERE id = 10 END-EXEC.
 
| Here, the precompiler detects that "staff-indicator" was declared as an
| indicator table, and expands it into individual indicator references when it
| processes the SQL statement. "staff-indicator"(1) is associated with
| "staff-id" of "staff-record", "staff-indicator"(2) is associated with
| "staff-name" of "staff-record", and so on.
 
| NOTE:  If there are "k" more indicator entries in the indicator table than
|        there are subordinates in the data item (for example, if
|        "staff-indicator" has 10 entries, making "k"=6), the "k" extra entries
|        at the end of the indicator table are ignored.  Likewise, if there are
|        "k" fewer indicator entries than subordinates, the last "k"
|        subordinates in the group item do not have indicators associated with
|        them. NOTE THAT YOU CAN REFER TO INDIVIDUAL ELEMENTS IN AN INDICATOR
|        TABLE IN AN SQL STATEMENT.
 
 
  8.4  PROGRAMMING IN JAVA (CREATING JAVA UDFS AND STORED PROCEDURES/CLASSES
  FOR JAVA STORED PROCEDURES AND UDFS)
 
  In the section "COM.ibm.db2.app.UDF", there is a list of functions that
  return specific DBINFO fields. To this list has been added:
 
       public String getDBapplid() throws Exception
 
 
  8.5  A JDK PROBLEM THAT AFFECTS JDBC PROGRAMS RUNNING UNDER A DBCS CODE PAGE
  ON AIX
 
  When running JDBC programs with JDK 1.1.4 bundled with AIX 4.3.1 under a DBCS
  code page, the DBCS data can not be displayed properly. This is a known
  problem in this version of JDK, and a fix for it (IX78932) is available.
 
 
  8.6  JDBC SAMPLE APPLICATIONS RESTRICTION ON SCO UNIXWARE 7
 
  Because a native method cannot make use of the thread library (libthread.so
  from UnixWare 7; see the UnixWare release notes), DB2 JDBC sample
  applications (DB2Appl, DB2Udf, and DB2Stp) do not work from a Version
  5.2 client on UnixWare 7 connecting to a Version 5 UDB server, or a
  Version 5 client connecting to a FixPak 3 UDB server.
 
 
| 8.7  JDBC 2.0
 
| JDBC 2.0 is the latest version of JDBC from Sun. This version of JDBC has two
| defined parts: the CORE API, and the STANDARD EXTENSION API. The core API has
| been released. For information on its specification, refer to:
 
|      http://www.software.ibm.com/data/db2/java
 
| The standard extension API is currently under review. For information on the
| review version of its specification, you can also visit the web page above.
 
| FEATURES
 
| The JDBC 2.0 driver we ship in this FixPak supports the JDBC 2.0 core API.
| However, due to the unavailability of certain features of the DB2 Engine, not
| all features defined in the specification are supported. Here is a list of
| main features that are supported:
 
| o   Read-only Scrollable Result Set
 
| o   Batch Update (Batch statements and batch prepared statements)
 
| o   LOB support
 
| Here is a list of features that are NOT supported:
 
| o   Updatable Scrollable ResultSet
 
| o   New SQL types (Array, Ref, Distinct, Java Object)
 
| o   Customized SQL type mapping
 
| PREREQUISITE
 
| JDK 1.2
 
| PLATFORM
 
| The JDBC 2.0 driver is currently available only on Windows 95, Windows 98,
| and Windows NT operating systems.
 
| COMPATIBILITY
 
| This version of the specification is backward compatible with the previous
| version (1.22). However, the DB2 JDBC 1.22 driver supports LOB types as an
| extension of the JDBC 1.22 specification, and this extension is not part of
| the new specification's backward compatibility. This means that existing JDBC
| applications that rely on the LOB support of the JDBC 1.22 driver may not
| work with the new driver. To fix the problem, we recommend that you modify
| the application to be compliant with the new specification. However, this
| solution may not be practical for every situation. As a workaround we provide
| a keyword, "JDBCVERSION", that you can set to "122" to tell the JDBC driver
| you want the 1.22 version for DB2 LOB support. The default is "200" for 2.0
| version behavior. You can set this keyword in "db2cli.ini", or pass it in as
| a connection attribute in the "getConnection" property argument.
 
| INSTALLATION
 
| In this FixPak, the JDBC 1.22 driver is still the default driver. The JDBC
| 2.0 driver is included in the "sqllib\java12" directory. To use the JDBC 2.0
| driver, run the "usejdbc2" batch file. This will create an "sqllib\java11"
| directory for the 1.22 driver files. It will also back up the JDBC 1.22
| driver files into this directory, and will copy the JDBC 2.0 driver files
| from the "sqllib\java12" directory into the appropriate directories. To
| switch back to the JDBC 1.22 driver, execute the "usejdbc1" batch file.
 
 
| 8.8  PERL ACCESS TO DB2 UDB DATABASES
 
| Release 0.70 of the DB2 UDB driver (DBD::DB2) for the Perl Database Interface
| (Perl DBI) is now available.
 
| The Perl DBI is an Application Programming Interface (API) that provides
| database access for the Perl language. It defines a set of functions,
| variables, and conventions that provide a consistent database interface
| independent of the actual database being used.
 
| The DBD::DB2 driver works in conjunction with the DBI to access DB2 UDB.
 
| For additional information, see the Web page:
 
|      http://www.software.ibm.com/data/db2/perl/
 
 
  8.9  DATALINK DATA TYPE
 
  Embedded SQL using the DATALINK data type is not supported.
 
 
  8.10  MULTITHREADED UNIX APPLICATIONS WORKING WITH CODE PAGE AND COUNTRY CODE
 
  On AIX, Solaris, HP-UX, SCO UnixWare 7, and Silicon Graphics IRIX , changes
  have been made to the functions that are used for run time querying of the
  code page and country code to be used for a database connection. They are now
  thread safe but can create some lock contention (and resulting performance
  degradation) in a multithreaded application which uses a large number of
  concurrent database connections.
 
  A new environment variable has been created (DB2_FORCE_NLS_CACHE) to
  eliminate the chance of lock contention in multithreaded applications. When
  DB2_FORCE_NLS_CACHE is set to TRUE the code page and country code information
  is saved the first time a thread accesses it. From that point on the cached
  information will be used for any other thread that requests this information.
  By saving this information, lock contention is eliminated and in certain
  situations a performance benefit will be realized.
 
  DB2_FORCE_NLS_CACHE should not be set to true if the application changes
  locale settings between connections. If this is done then the original locale
  information will be returned even after the locale settings have been
  changed. In general, multithreaded applications will not change locale
  settings. This ensures that the application remains thread safe.
 
 
  8.11  ERROR PROCESSING FOR UDF CALL TYPES
 
  8.11.1  SCRATCHPAD AND FINAL CALL TYPE ARGUMENTS FOR EXTERNAL TABLE FUNCTIONS
 
  Changes have been introduced (a) to give the user explicit control over
  scratchpad duration, and (b) to avoid inconsistencies in the duration of
  scratchpads, for table functions written in:
 
  o   C/C++ - until now, scratchpads always survived across CLOSE/OPEN calls to
      the UDF
 
  o   OLE/Java - until now, a fresh scratchpad was always allocated on OPEN
 
  This difference has led to the possibility of getting inconsistent results,
  for example when performing a join.
 
  The following changes have been introduced for User Defined Functions (UDFs)
  which are table functions:
 
  1.  FINAL CALL is now optional for the CREATE FUNCTION statement for table
      functions, as it is for scalar functions. NO FINAL CALL (the default) may
      thus be specified for table functions.
 
  2.  When writing a table function which has a scratchpad, you can elect to
      have the scratchpad be initialized for each OPEN call to the function, by
      specifying NO FINAL CALL, in which case the table function is expected to
      release resources on each CLOSE call.
 
      Or, you can elect to have the scratchpad content be preserved across OPEN
      calls, by specifying FINAL CALL. If you do this, you need not release
      resources during the CLOSE call processing, because a FINAL call will be
      made to the table function at end-of-statement. This FINAL CALL is new
      with this change, as is the balancing FIRST call which takes place before
      the first OPEN call. These two new call types occur only on table
      functions which specify FINAL CALL.
 
  3.  For Java table functions, a change to the execution model needs to be
      understood. The following table explains what happens at each significant
      point in the table function processing of a given statement (the bottom
      part of each box hints what the code might be written to do for a typical
      table function which pulls some information in from the Web). Covered are
      both the NO FINAL CALL and the FINAL CALL cases, assuming SCRATCHPAD in
      both cases, which account for the new rules described above.
 
                      |                              |
      Point     | |    NO FINAL CALL             |    FINAL CALL
      in        | |    LANGUAGE JAVA             |    LANGUAGE JAVA
      scan      | |    SCRATCHPAD                |    SCRATCHPAD
      time      V |                              |
          ------------+------------------------------+------------------------------
      Before the  | No calls.                    | Class constructor is called
      first OPEN  |                              |  (means new scratchpad).
          for the     |                              | UDF Method is called with
      table func. |                              |  "FIRST" call.
                      |                              |- - - - - - - - - - - - - - -
                  |                              | Constructor initializes
                  |                              |  class and scratchpad
                  |                              |  variables.
                      |                              | Method connects to the Web
                  |                              |  Server.
                      |                              |
          ------------+------------------------------+------------------------------
      At each     | Class constructor is called  | UDF Method is called with
      OPEN of the |  (means new scratchpad).     |  "OPEN" call.
          table func. | UDF Method is called with    |
                  |  "OPEN" call.                |
                  |- - - - - - - - - - - - - - - |- - - - - - - - - - - - - - -
                  | Constructor initializes      | Method opens the scan for
                  |  class and scratchpad        |  whatever Web data it wants.
                      |  variables.                  |  (Might be able to avoid
                  | Method connects to the Web   |  reopen after a CLOSE repo-
                  |  Server, and opens the scan  |  sition, depending on what
                  |  for Web data.               |  is saved in scratchpad!)
                  |                              |
          ------------+------------------------------+------------------------------
      At each     | UDF method is called with    | UDF Method is called with
      FETCH for   |  "FETCH" call.               |  "FETCH" call.
          new row of  |- - - - - - - - - - - - - - - |- - - - - - - - - - - - - - -
      table func  | Method fetches and returns   | Method fetches and returns
      data.       |  next row of data, or EOT.   |  next row of data, or EOT.
                      |                              |
          ------------+------------------------------+------------------------------
      At each     | UDF method is called with    | UDF Method is called with
      CLOSE of the|  "CLOSE" call.               |  "CLOSE" call.
          table func. | "close" method is called if  |
                  |  it exists for class.        |
                  |- - - - - - - - - - - - - - - |- - - - - - - - - - - - - - -
                  | Method closes its Web scan   | Method might reposition to
                  |  and disconnects from the    |  the top of the scan, or
                  |  Web Server.                 |  close the scan.  It can
                  | "close" does not need to do  |  save any state in the
                  |  anything.                   |  scratchpad, which will
                  |                              |  persist.
                      |                              |
          ------------+------------------------------+------------------------------
      After the   | No calls.                    | UDF Method is called with
      last CLOSE  |                              |  "FINAL" call.
          of the table|                              | "close" method is called if
      func.       |                              |  it exists for class.
                      |                              |- - - - - - - - - - - - - - -
                  |                              | Method disconnects from the
                  |                              |  Web Server.
                      |                              | "close" does not need to do
                  |                              |  anything.
                      |                              |
          ------------+------------------------------+------------------------------
 
      Some notes on this table:
 
      a.  By "UDF Method" we mean the Java class method which implements the
          UDF; the method identified in the EXTERNAL NAME clause of the CREATE
          FUNCTION statement.
 
      b.  For table functions with NO SCRATCHPAD specified, the calls to the UDF
      method are as indicated in this table, but because the user is not asking
      for any continuity via a scratchpad, DB2 will cause a new object to be
      instantiated before each call, by calling the class constructor. It is
      not clear that table functions with NO SCRATCHPAD (and thus no
      continuity) can do very useful things, but they are supported.
 
      c.  These execution models imply the existence of a new class method
          which provides the call type. This method is provided, as are
          numerous other methods, with DB2 in the COM.ibm.db2.app.UDF class,
          and will be defined as:
 
               public int getCallType () throws Exception
 
      d.  These models are TOTALLY COMPATIBLE with what happens with the other
          UDF languages: C and C++ and OLE.
 
  Defines for the new call types are added to sqludf.h, the UDF include file.
 
  UDB customers who have existing table functions are advised to examine the
  above options and make appropriate changes:
 
  1.  If you depend on the new scratchpad rules implied by FINAL CALL then you
      may have to change your UDF to add the new call types, because with FINAL
      CALL specified, the new calls will be made to the UDF. Also, any
      acquired resources should be freed when the FINAL call is handled by the
      table function.
 
  2.  If you wish to use the rules implied by NO FINAL CALL, you are advised to
      change and rerun your CREATE FUNCTION statement with NO FINAL CALL
      instead of FINAL CALL, so that your UDF will not get the new calls.
      (Depending on how the UDF is written to examine the call-type argument,
      it may or may not give bad results if it receives unexpected calls.)
 
  3.  If you have a Java table function, then you will have to change your
      function to conform to the new execution models in the above table. For
      either execution model (depending on whether you choose FINAL CALL or NO
      FINAL CALL), you will note that additional calls are made to the UDF
      method. This gives additional power to the UDF writer, but means that he
      or she must distinguish the calls. Use of the new getCallType method in
      the parent class included by DB2 provides this capability.
 
  Detailed information changes will appear in the "SQL Reference" and the
  "Embedded SQL Programming Guide" (ESPG) when they are next updated.
  Meanwhile, a "Technote" describing these changes in more detail will be made
  available in the DB2 Technical Library on the World Wide Web. Use the search
  argument "FINAL CALL".
 
  The following sections describe the detailed changes to the "Embedded SQL
  Programming Guide".
 
  In Chapter 6 of the "Embedded
  SQL Programming Guide", under the heading "User-Defined Functions (UDF)", in
  the Example "Table Function Returning Document IDs", "FINAL CALL" should now
  read "NO FINAL CALL", and in the following paragraph note that FINAL CALL
  need not be specified for each table function.
 
  In Chapter 7 of the "Embedded SQL Programming Guide", under the heading
  "Interface between DB2 and a UDF", in the section "The Arguments Passed from
  DB2 to a UDF", in the description for the "scratchpad" argument, the text
  beginning "The actual..." should be replaced by:
 
  For table functions, the scratchpad is initialized as above only for the very
  first call to the UDF if FINAL CALL is specified on the CREATE FUNCTION.
  This "very first call" has type FIRST. After this call, the scratchpad
  content is totally under control of the table function.
 
  If NO FINAL CALL was specified or defaulted, then the scratchpad is
  initialized as above for each OPEN call, and the scratchpad content is
  completely under control of the table function between OPEN calls. (This can
  be very important for a table function used in a join or subquery. If it is
  necessary to maintain the content of the scratchpad across OPEN calls, then
  FINAL CALL must be specified in your CREATE FUNCTION statement. With FINAL
  CALL specified, in addition to the normal OPEN, FETCH and CLOSE calls, the
  table function will also receive FIRST and FINAL calls, for the purpose of
  scratchpad maintenance and resource release.)
 
  Also, in the description of the "call-type" argument, the second sentence
  should be replaced by the following sentence:
 
  For external scalar functions this argument is only present if FINAL CALL is
  specified in the CREATE FUNCTION statement, but for external table functions
  it is ALWAYS present.
 
  After that first paragraph, add the following new paragraph:
 
  Note that even though all the current possible values are listed below, your
  UDF should contain a switch or case statement which explicitly tests for all
  the expected values, rather than containing "if A do AA, else if B do BB,
  else it must be C so do CC" type logic. This is because it is possible that
  additional call types may be added in the future, and if you don't explicitly
  test for condition C you will have trouble when new possibilities are added.
 
  In the same section, where the values for the "call-type" argument are
  explained for Table Functions, the text should be amended as follows:
 
  o   -2 This is the FIRST call, which only occurs if the FINAL CALL keyword
      was specified for the UDF. The scratchpad is set to binary zeros before
      this call.  Argument values are passed to the table function, and it may
      choose to acquire memory or perform other one-time only resource
      initialization. Note that this is not an OPEN call, that call follows
      this one. On a FIRST call the table function should not return any data
      to DB2, but it can set SQL-state and diagnostic-message argument return
      values.
 
  o   -1 This is the OPEN call. The scratchpad will be initialized if NO FINAL
      CALL is specified, but not necessarily otherwise. (The rest of the text
      is unchanged.)
 
  o   0 (unchanged)
 
  o   1 (The first paragraph is unchanged, but the following text should be
      added) During CLOSE, the UDF should release resources acquired, if NO
      FINAL CALL was defined for the UDF. If FINAL CALL was defined, a special
      call (FINAL) is provided for resource release. On a CLOSE call a table
      function should not return a row to DB2, and in fact any SQL-result and
      SQL-result-ind values returned are ignored by DB2 upon return. However,
      the table function may set SQL-state and diagnostic-message argument
      values, which are handled as usual by DB2.
 
  o   2 This is the FINAL call, which balances the FIRST call, and it only
      occurs if FINAL CALL was defined for the external table function. All
      system resources should be freed. This call only occurs once per
      statement. As usual, SQL-state and diagnostic-message argument values may
      be returned, and they are handled as usual by DB2.
 
  Under the heading "Summary of Argument Use", for the argument "scratchpad and
  call-type", add the text ", and optionally FIRST and FINAL" in both cases.
 
  In Chapter 7 of the "Embedded SQL Programming Guide", under the heading
  "Table Function Considerations", under the first bullet, there are now five
  call types instead of three: add FIRST and FINAL to the list.
 
  Also, add a new bullet in this section as well, which should read as follows:
 
  The error processing model for table function calls is as follows:
 
  1.  If FIRST call fails, no further calls are made.
 
  2.  If FIRST call succeeds, FINAL call is made.
 
  3.  If OPEN call fails, no FETCH or CLOSE call is made.
 
  4.  If OPEN call succeeds, then FETCH and CLOSE calls are made.
 
  In the "Weather Table Function" example in Chapter 7, the UDF definition
  should specify NO FINAL CALL, and note that FINAL CALL is no longer mandatory
  for a table function (that is, ignore the statement that says it is
  mandatory).
 
  In Chapter 15 of the "Embedded SQL Programming Guide", entitled "Programming
  in Java", under the heading "Creating Java UDFs and Stored Procedures", the
  second sentence of the second paragraph should be changed to read as follows:
 
  Once you create and register these UDFs and stored procedures, and place the
  Java classes in the correct file location, described in "Where to Put Java
  Classes" on page 514, you can then (for UDFs) reference them in your SQL, or
  (for stored procedures) call them from your application written in any
  supported language.
 
  And the sentence following that one should be removed.
 
  In Chapter 15 of the "Embedded SQL Programming Guide", under the heading
  "Creating and Using Java User-Defined Functions", the fourth sentence of the
  first paragraph should be changed to read:
 
  You can then refer to it in the SQL of your application.
 
  In the subheading "Changing How a Java UDF Runs" under that same heading, the
  first three paragraphs should be replaced with the following five:
 
  Typically, DB2 calls a UDF many times, once for each row of an input or
  result set in a query. If SCRATCHPAD is specified in the CREATE FUNCTION
  statement of the UDF, DB2 recognizes that some "continuity" is needed between
  successive invocations of the UDF, and therefore the implementing Java class
  is not instantiated for each call, but generally speaking once per UDF
  reference per statement. Generally it is instantiated before the first call
  and used thereafter, but may for table functions be instantiated more often--
  see the NO FINAL CALL execution model in the subsection which follows this
  one.
 
  If, however, NO SCRATCHPAD is specified for a UDF, either a scalar or table
  function, then a clean instance is instantiated for each call to the UDF, by
  means of calling the class constructor.
 
  A scratchpad may be useful
  for saving information across calls to a UDF.
  Whereas for C, C++ and OLE UDFs
  the scratchpad is maintained by DB2, in Java the UDF can simply use instance
  variables. For table functions using a scratchpad, you can control when you
  get a new instance by use of the FINAL CALL / NO FINAL CALL option on the
  CREATE FUNCTION statement, as indicated by the execution models in the
  subsection which follows this one.
 
  For scalar functions, you use the same
  instance for the entire statement.
  Another choice you have is to use the DB2
  provided Java methods getScratchpad() and setScratchpad(), in which case you
  will be using the DB2-managed scratchpad. The ability to achieve continuity
  between calls to a UDF by means of a scratchpad, is controlled by the SCRATCHPAD
  / NO SCRATCHPAD option of CREATE FUNCTION, regardless of whether the DB2 scratchpad or
  instance variables are used.
 
  Please note that every
  reference to a Java UDF in a query is treated independently, even if the same
  UDF is referenced multiple times. This is the same as what happens for OLE, C
  and C++ UDFs as well. At the end of a query, if you specify the FINAL CALL
  option for a scalar function then the object's close() method is called. For
  table functions the close() method will always be invoked as indicated in the
  subsection which follows this one.  If you do not define a close() method for
  your UDF class, then a stub function takes over and the event is ignored.
 
  And in the next paragraph, which begins "If you specify the ALLOW PARALLEL
  ...", the last sentence should be removed.
 
  Following the subsection "Changing How a Java UDF Runs", add a new subsection
  at the same level, entitled "Table Function Execution Model for Java", which
  contains the following:
 
  For table functions written in Java, it is important to understand what
  happens at each point in DB2's processing of a given statement which is
  significant to the table function. The table which follows details this
  information. The bottom part of each box hints what the code might be written
  to do for a typical table function which pulls some information in from the
  Web). Covered are both the NO FINAL CALL and the FINAL CALL cases, assuming
  SCRATCHPAD in both cases.
 
                  |                              |
      Point     | |    NO FINAL CALL             |    FINAL CALL
      in        | |    LANGUAGE JAVA             |    LANGUAGE JAVA
      scan      | |    SCRATCHPAD                |    SCRATCHPAD
      time      V |                              |
      ------------+------------------------------+------------------------------
      Before the  | No calls.                    | Class constructor is called
      first OPEN  |                              |  (means new scratchpad).
      for the     |                              | UDF Method is called with
      table func. |                              |  "FIRST" call.
                  |                              |- - - - - - - - - - - - - - -
                  |                              | Constructor initializes
                  |                              |  class and scratchpad
                  |                              |  variables.
                  |                              | Method connects to the Web
                  |                              |  Server.
                  |                              |
      ------------+------------------------------+------------------------------
      At each     | Class constructor is called  | UDF Method is called with
      OPEN of the |  (means new scratchpad).     |  "OPEN" call.
      table func. | UDF Method is called with    |
                  |  "OPEN" call.                |
                  |- - - - - - - - - - - - - - - |- - - - - - - - - - - - - - -
                  | Constructor initializes      | Method opens the scan for
                  |  class and scratchpad        |  whatever Web data it wants.
                  |  variables.                  |  (Might be able to avoid
                  | Method connects to the Web   |  reopen after a CLOSE repo-
                  |  Server, and opens the scan  |  sition, depending on what
                  |  for Web data.               |  is saved in scratchpad!)
                  |                              |
      ------------+------------------------------+------------------------------
      At each     | UDF method is called with    | UDF Method is called with
      FETCH for   |  "FETCH" call.               |  "FETCH" call.
      new row of  |- - - - - - - - - - - - - - - |- - - - - - - - - - - - - - -
      table func  | Method fetches and returns   | Method fetches and returns
      data.       |  next row of data, or EOT.   |  next row of data, or EOT.
                  |                              |
      ------------+------------------------------+------------------------------
      At each     | UDF method is called with    | UDF Method is called with
      CLOSE of the|  "CLOSE" call.               |  "CLOSE" call.
      table func. | "close" method is called if  |
                  |  it exists for class.        |
                  |- - - - - - - - - - - - - - - |- - - - - - - - - - - - - - -
                  | Method closes its Web scan   | Method might reposition to
                  |  and disconnects from the    |  the top of the scan, or
                  |  Web Server.                 |  close the scan.  It can
                  | "close" does not need to do  |  save any state in the
                  |  anything.                   |  scratchpad, which will
                  |                              |  persist.
                  |                              |
      ------------+------------------------------+------------------------------
      After the   | No calls.                    | UDF Method is called with
      last CLOSE  |                              |  "FINAL" call.
      of the table|                              | "close" method is called if
      func.       |                              |  it exists for class.
                  |                              |- - - - - - - - - - - - - - -
                  |                              | Method disconnects from the
                  |                              |  Web Server.
                  |                              | "close" does not need to do
                  |                              |  anything.
                  |                              |
      ------------+------------------------------+------------------------------
 
  Some notes on this table:
 
  1.  By "UDF Method" we mean the Java class method which implements the UDF-
      the method identified in the EXTERNAL NAME clause of the CREATE FUNCTION
      statement.
 
  2.  For table functions with NO SCRATCHPAD specified, the calls to the UDF
      method are as indicated in this table, but because the user is not asking
      for any continuity via a scratchpad, DB2 will cause a new object to be
      instantiated before each call, by calling the class constructor. It is
      not clear that table functions with NO SCRATCHPAD (and thus no
      continuity) can do very useful things, but they are supported.
 
  3.  These execution models imply the existence of a new class method which
      which enables the UDF to identify the call type. This method is provided
      with DB2 in the COM.ibm.db2.app.UDF class, and will be defined as:
 
             public int getCallType () throws Exception
 
  4.  These models are TOTALLY COMPATIBLE with what happens with the other UDF
      languages: C and C++ and OLE.
 
  In Chapter 15 of the "Embedded SQL Programming Guide", under the heading
  "Classes for Java Stored Procedures and UDFs", and further under the
  subheading "COM.ibm.db2.app.UDF", the paragraph describing the "public void
  close()" method should be changed to read as follows:
 
  This method is called by the database for scalar functions at the end of a
  statement evaluation, if the UDF was created with the FINAL CALL option, and
  is analogous to the final call for a C function. For table functions, it is
  called after the CLOSE call to the UDF method (if NO FINAL CALL is coded or
  defaulted), or after the FINAL call (if FINAL CALL is coded). If a Java UDF
  class does not implement this function, a no-op stub function will handle and
  effectively ignore this event.
 
  Immediately following the description for "public void close()", add material
  for the new method "public int getCallType() throws Exception", which reads
  as follows:
 
  This function is used by table function UDF methods to find out the call type
  for a particular call. It returns a value as follows (symbolic defines are
  provided for these values in the Com.ibm.db2.app.UDF class definition):
 
  o   -2 FIRST call
 
  o   -1 OPEN call
 
  o   0 FETCH call
 
  o   1 CLOSE call
 
  o   2 FINAL call
 
 
| 8.11.2  EXTERNAL UDF ERROR PROCESSING MODEL FOR SCALAR FUNCTIONS
 
| In chapter 7, in the section entitled "Other Coding Considerations", and the
| subsection entitled "Hints and Tips", there should be a new item 15 added to
| the list as follows:
 
| The error processing model for scalar UDFs which are defined with the FINAL
| CALL specification is as follows:
 
| 1.  If FIRST call fails, no further calls are made.
 
| 2.  If NORMAL call fails, no further NORMAL calls are made, but the FINAL
|     call is made.
 
| This means that if an error is returned on a FIRST call, the UDF must clean
| up before returning, because no FINAL call will be made.
 
| If FINAL CALL is not specified for the scalar UDF, then only NORMAL calls are
| made, and they cease if an error is returned.
 
| There should also be a new item 16 added to the list as follows:
 
| The error processing model for table functions is defined in the "Table
| Functions Considerations" section of this chapter.
 
 
| 8.12  NOT ATOMIC COMPOUND SQL
 
| DB2-Connect does not support SELECT statements selecting LOB columns in a
| compound SQL block.
 
 
  8.13  OTHER REVISIONS TO THE BOOK
 
  The following changes related to the Embedded SQL Programming Guide have been
  documented in the Release Notes for FixPaks prior to this release.
 
 
  8.13.1  REVISIONS TO CHAPTER 1
 
  In chapter 1 of the ESPG, in the first paragraph
  under the heading "DB2 Bind File Dump Tool-db2bfd", there is a reference to
  "Version 3"; this should be changed to Version 5.
 
 
  8.13.2  REVISIONS TO CHAPTER 4
 
  In chapter 4, the section "Join Strategies in a
  Partitioned Database" has several subsections showing examples of the
  different join strategies. In the pieces of artwork, all occurrences of
  "LINEITEMS" should be changed to "LINEITEM". Also, the subsection "Broadcast
  Inner-Table Joins", has incorrect text in the example shown. The text of the
  example should be:
 
       The LINEITEM table is sent to all database partitions that have the
       ORDERS table. Table queue q3 is broadcast to all database partitions
       of the outer table.
 
 
  8.13.3  REVISIONS TO CHAPTER 7
 
  The following changes pertain to chapter 7:
 
  o   Section OLE Automation UDFs in C++, at the end of the section, in the
      code:
 
           short indicator1,  // input indicator
           short indicator2,  // output indicator
 
      should be changed to
 
           short *indicator1,  // input indicator
           short *indicator2,  // output indicator
 
  o   Section Hints and Tips, item number 4: "reason code 21" should be changed
      to "reason code 34".
 
  o   The following changes pertain to the section entitled "The Arguments
      Passed from DB2 to a UDF":
 
      -   For the SQL-state argument, for the sqlstate 02001, it should read:
 
               02001    Only valid for the FETCH call to table functions, it means
                        there are no more rows in the table.
 
      -   For the dbinfo argument, list item "16. Table function column list
          (tfcolumn)", replace the first paragraph with the following:
 
               If this is a table function, this field is a pointer to an array
               of short integers which is dynamically allocated by DB2.  If
               this is a scalar function, this pointer is null.
 
  o   The following changes pertain to the section entitled "Using LOB Locators
      as Parameters or Results":
 
      -   For the figure showing (function header) declaration of the APIs,
          entitled "DB2 Lob Locator APIs defined in sqludf.h", the descriptions
          of the API parameters have been improved. See the actual sqludf.h
          file for details.
 
      -   There are five APIs described in the section. Where the return codes
          from these APIs are described, "other" is cited as a possibility for
          each API. For each API, the description of "other" should be changed
          to the following:
 
 
               other   Invalid locator or other error (for example, memory error).  The value
                       that is returned for these cases is the SQLCODE corresponding
                       to the error condition.  For example, -423 means invalid
                       locator.  Please note that before returning to the UDF with
                       one of these "other" codes, DB2 makes a judgement as to the
                       severity of the error.  For severe errors, DB2 remembers that
                       the error occurred, and when the UDF returns to DB2, regardless
                       of whether the UDF returns an error SQLSTATE to DB2, DB2
                       takes action appropriate for the error condition.  For
                       non-severe errors, DB2 forgets that the error has occurred,
                       and leaves it up to the UDF to decide whether it can take
                       corrective action, or return an error SQLSTATE to DB2.
 
      -   Three of the five APIs describe a possible return code of -1, meaning
          that the locator passed on the call has already been freed. These
          APIs do not return a -1 return code to the UDF. This condition is
          handled under the "other" return code using SQLCODE -423 (invalid
          locator).
 
      -   In item 1: sqludf_length(), an additional return code value is
          defined:
 
               -3      Bad input value is provided to the API.  This includes:
                       - udfloc_p (address of locator) is zero
                       - return_len_p (address of where to put length) is zero
 
      -   In item 2: sqludf_substr(), an additional return code value is
          defined:
 
               -3      Bad input value is provided to the API.  This includes:
                       - udfloc_p (address of locator) is zero
                       - start is less than 1
                       - length is negative
                       - buffer_p (buffer address) is zero
                       - return_len_p (address of where to put length) is zero
 
      -   In item 3: sqludf_append(), an additional return code value is
          defined:
 
               -3      Bad input value is provided to the API.  This includes:
                       - udfloc_p (address of locator) is zero
                       - length is negative
                       - buffer_p (buffer address) is zero
 
      -   In item 4: sqludf_create_locator(), an additional return code value
          is defined:
 
               -3      Bad input value is provided to the API.  This includes:
                       - udfloc_p (address of locator) is zero
                       - loc_type is not one of the three valid values
                       - loc_p (address of where to put locator) is zero.
 
      -   In item 5: sqludf_free_locator(), an additional return code value is
          defined:
 
               -3      Bad input value is provided to the API.  This includes:
                       - udfloc_p (address of locator) is zero
 
      -   In item 3: sqludf_append(), add the following paragraphs before the
          discussion of return codes:
 
               This API can be used to build very large LOB values in a piecemeal
               manner.  In cases where a large number of appends is used to build
               a result, the performance of this task can be improved by:
               - allocating a large application control heap (APP_CTL_HEAP_SZ is
                 the database manager configuration parameter)
               - doing fewer appends of larger buffers; for example, instead of doing
                 20 appends of 50 bytes each, doing a single 1000 byte append.
 
               SQL applications which build many large LOB values via the
               sqludf_append() API may encounter errors caused by limitations on
               the amount of disk space available.  The chance of these errors
               happening can be reduced by:
               - using larger buffers for the individual appends
               - doing frequent COMMITs between statements
               - in cases where each row of a SELECT statement is building a
                 LOB value via this API, using a CURSOR WITH HOLD and doing COMMITs between rows.
 
      -   In item 5: sqludf_free_locator(), The paragraph beginning
          "Typically..." is incorrect. Replace it with:
 
               Use this API to free any locators that were created with the
               sqludf_create_locator() API, and which were used only for internal
               manipulation.  It is NOT NECESSARY to free locators passed into
               the UDF.  It is NOT NECESSARY to free any locator created by the UDF
               via sqludf_create_locator() if that locator is passed out of the
               UDF as an output.
 
      -   After the enumerated coverage of the individual APIs, add the
          following text:
 
               The following notes apply to the use of these APIs:
               1. A UDF which is defined to return a LOB locator has several
                  possibilities available to it.  It can return:
                  a. an input locator passed to it
                  b. an input locator passed to it which has been appended to
                     via sqludf_append()
                  c. a locator created to via sqludf_create_locator(), and appended
                     to via sqludf_append().
               2. A table function can be defined as returning one or more
                  LOB locators.  Each of them can be any of the possibilities
                  discussed in the preceding item.  It is also valid for such
                  a table function to return the same locator as an output for
                  several table function columns.
               3. A LOB locator passed to a table function as an input argument
                  remains alive for the entire duration of the row generation
                  process.  In fact, the table function can append to a LOB using
                  such a LOB locator while generating one row, and see the
                  appended bytes on a subsequent row.
               4. The internal control mechanisms used to represent a LOB which
                  originated in DB2 as a LOB locator output from a UDF (table
                  or scalar function), take 1950 bytes.  For this reason, and
                  because there are limitations on the size of a row which is
                  input to a sort, a query which attempts to sort multiple
                  such LOBs which originated as UDF LOB locators will be
                  limited to (at most) two such values per row, depending on
                  the sizes of the other columns involved.  The same
                  limitation applies to rows being inserted into a table.
 
 
  8.13.4  REVISIONS TO CHAPTER 9
 
  In chapter 9, in the section "Accessing DRDA
  Servers", the second paragraph in point 1 should read:
 
       For IBM products, consult the IBM SQL Reference, Version 5.2 (S10J-8165), before
       you start coding.
 
 
  8.13.5  REVISIONS TO CHAPTER 15
 
  The following changes pertain to chapter 15:
 
  o   The book states that the user's Java classes must implement the
      interfaces that are provided. However, since the Java library provided in
      "sqllib/java/db2java.zip" contains classes, the user classes must extend
      Java classes of the same name. References to
 
           class ... implements COM.ibm.db2.app.UDF
           { ... }
 
      should be changed to
 
           class ... extends COM.ibm.db2.app.UDF
           { ... }
 
      The same is true for "COM.ibm.db2.app.StoredProc".
 
  o   The book states that new LOB values can be created by UDFs and stored
      procedures by using the following classes/routines:
 
           COM.ibm.db2.app.Blob    public static Blob new() throws Exception;
           COM.ibm.db2.app.Clob    public static Clob new() throws Exception;
 
      These were renamed and moved to the new class COM.ibm.db2.app.Lob as the
      following functions:
 
           COM.ibm.db2.app.Lob    public static Blob newBlob() throws Exception;
           COM.ibm.db2.app.Lob    public static Clob newClob() throws Exception;
 
  o   The Java type mapping table includes the following mappings:
 
           SQL Type           Java Type (UDF)   Java Type (Stored Procedure)
 
           LONG VARCHAR       Clob              Clob
           LONG VARGRAPHIC    Clob              Clob
 
      These should be changed to:
 
           LONG VARCHAR       String            String
           LONG VARGRAPHIC    String            String
 
  The following information should be added after the second paragraph in the
  section "Java UDFs and Stored Procedures":
 
       When creating a stored procedure in the Java
       language, you must use the CREATE PROCEDURE
       statement to register the procedure to the system
       catalog table SYSCAT.PROCEDURES.  For more
           information, refer to the section on the CREATE
           PROCEDURE statement in the SQL Reference.
 
  The following is a limitation of the Java UDF/stored procedure support: On a
  mixed code page database server, Java user-defined functions and stored
  procedures cannot use CLOB type arguments, because random access on character
  boundaries on large mixed code page strings has not yet been implemented.
  Full support for all LOB types is intended for SBCS databases. For mixed
  databases, support is intended for the BLOB and the DBCLOB types. As a
  workaround, applications running on a mixed database system should convert
  CLOB arguments to DBCLOB, LONG VARGRAPH, or LONG VARCHAR types.  For UDFs,
  this can be done with the CAST operator.
 
  In appendix B, which describes the sample programs, references (in table 24)
  to the loblocud, db2uext2, and autoloader samples should be removed. For
  additional information, also refer to 8.13.6, "Revisions to Sample Programs"
  and 8.13.7, "Other File Changes".
 
  In the index, java_heap_sz is incorrectly referred to as java_heap_size.
 
 
  8.13.6  REVISIONS TO SAMPLE PROGRAMS
 
  Revisions to sample programs were made for
  various languages on the following platforms: AIX, HP-UX, OS/2, Solaris,
  Windows NT, and Windows 95. The revisions are to correct some code errors and
  to make better use of API calls within the programs. Some programs have been
  made generic for all platforms:
  before they were only available on specific
  platforms; for example, 'makeapi.sqc'. Also, the interface has been improved
  for several programs to better guide the user on program input, and to give
  more informative output.
  Many redundant files have had their file contents
  deleted, replaced by the comment "This file is not needed". Where a new file
  replaces the redundant file's functionality, a reference to this is also
  provided.
 
  The following is a list of the updated files. Each entry contains the name of
  the file, its language, and the platforms for which it has been changed.
  Where the same file has been revised in more than one language, one file name
  is given with multiple extensions, as in "dbconf.c/.cbl/.f/.for". "COBOL"
  refers to both IBM and Micro Focus COBOL, unless otherwise indicated. "All
  platforms" refers to the following platforms only: AIX, HP-UX, OS/2, Solaris,
  Windows NT, and Windows 95. In some situations, a file may not be available
  on a specific platform; if you are not sure, refer to the README file in the
  appropriate samples directory. The file entry also contains a comment
  describing the nature of the change. The changes are as follows:
 
  adhoc.sqc
            C for all platforms
 
            Fixed memory leak and improved user interface.
 
  blobfile.cmd
            REXX on AIX, OS/2, and Windows NT
 
            The correct file version is now available for OS/2.
 
  dbconf.c/.cbl/.f/.for
            C, COBOL, FORTRAN for all platforms.
 
            Fixed 'version' parameter error in API call. Improved the user
            interface. Recoded Micro Focus COBOL version to make it generic for all
            platforms.
 
  d_dbconf.cbl
            Micro Focus COBOL for all platforms.
 
            Recoded to make generic for all platforms.
 
  d_dbmcon.cbl
            Micro Focus COBOL for all platforms.
 
            Recoded to make generic for all platforms.
 
  da_manip.h/.sqc
            C for all platforms
 
            Redundant files: contents deleted.
 
  dbcat.f/.for
            FORTRAN for all platforms
 
            Fixed 'version' parameter error in API call.
 
  dbmconf.cbl/.cmd
            Micro Focus COBOL for all platforms and REXX on AIX, Windows NT,
            and OS/2
 
            Recoded Micro Focus COBOL version to make it generic for all
            platforms. The correct REXX version is now available for OS/2.
 
  dbinst.for
            FORTRAN for OS/2
 
            Improved user interface.
 
  dbsnap.cbl
            IBM COBOL for all platforms
 
            Fixed 'version' parameter error in API call.
 
  dbstat.sqb
            Micro Focus COBOL for all platforms
 
            Fixed 'version' parameter error in API call.
 
  db_udcs.for
            FORTRAN for OS/2
 
            This program is now available for OS/2 FORTRAN.
 
  ebcdicdb.for
            FORTRAN for OS/2
 
            This program is now available for OS/2 FORTRAN.
 
  fillcli.sqc
            C for all platforms
 
            This is a client program; the server program is fillsrv.sqc. These
            programs have been extensively rewritten, combining the
            functionality of the supporting programs da_manip, system, and
            tabinfo (which are now redundant). The use of APIs, demonstration
            of SQLDA structures, and user interface have all been improved.
 
  fillsrv.sqc
            C for all platforms
 
            This is a server program; the client program is fillcli.sqc (see
            that entry for more information).
 
  inpsrv.def
            Micro Focus on OS/2
 
            Redundant file: contents deleted, as compiler does not need
            definition file for stored procedures.
 
  inpcli.old
            C for all platforms
 
            Redundant file: contents deleted.
 
  inpsrv.old
            C for all platforms
 
            Redundant file: contents deleted.
 
  largevol.sqc
            C for all platforms
 
            This program is AIX-specific: file contents were deleted on the
            HP-UX, OS/2, Solaris, Windows NT, and Windows 95 platforms.
 
  lobeval.cmd
            REXX on AIX, Windows NT and OS/2
 
            The correct version is now available for OS/2.
 
  makeapi.sqc
            C for all platforms
 
            This replaces the specific program files for AIX and OS/2 with a
            generic program file that is now available for all platforms.
 
  monreset.f/.for
            FORTRAN program for all platforms
 
            Fixed 'version' parameter error in API call.
 
  monsz.cbl
            IBM COBOL for all platforms
 
            Fixed 'version' parameter error in API call.
 
  outsrv.def
            Micro Focus COBOL on OS/2.
 
            Redundant file: contents deleted, as compiler does not need
            definition file for stored procedures.
 
  inpcli.old
            C for all platforms
 
            Redundant file: contents deleted.
 
  inpsrv.old
            C for all platforms
 
            Redundant file: contents deleted.
 
  qload.sqb/.sqf/.sqc
            COBOL, FORTRAN, and C for all platforms
 
            Improved interface provides more information and eliminates
            extraneous 'load file' error.
 
  rechist.c/.sqc
            C for all platforms
 
            The non-embedded SQL program rechist.c has been replaced by the
            embedded SQL program rechist.sqc. The new file corrects a database
            connect error that occurred with rechist.c.
 
  sws.cbl
            IBM COBOL for all platforms
 
            Fixed 'version' parameter error in API call.
 
  system.c/.h
            C for all platforms
 
            Redundant files: contents deleted.
 
  tabinfo.c/.h
            C for all platforms
 
            Redundant files: contents deleted.
 
  tabspace.sqb/.sqf
            COBOL and FORTRAN for all platforms
 
            Improves use of APIs to now demonstrate multiple table spaces.
 
  tblsrv.c
            C for all platforms
 
            Corrected error in API call to shared library.
 
 
  8.13.7  OTHER FILE CHANGES
 
  The makefiles, where needed, have been updated to
  reflect the changes described in the previous section. For example, the C
  makefiles no longer create and link in the object files da_manip.obj,
  system.obj and tabinfo.obj for the stored procedure fillsrv.
 
  The OS/2 command files for IBM COBOL and FORTRAN, and their respective
  makefiles, now use a stack size of 64000: the stack size link option for
  COBOL is now "/ST:64000", and for FORTRAN it is now "stack=64000". It was
  found that some of the stored procedure programs needed a larger stack size
  to run correctly.
 
  The following command and batch file changes have been made:
 
  BLDF32.CMD
            FORTRAN for OS/2
 
            Redundant file: contents deleted.
 
  EMBPREP.BAT
            COBOL for Windows NT and Windows 95
 
            The correct version of this file is now available.
 
 
  9.0  区嬉曦艳楝 DB2 诜谆
 
 
  9.1  损祁 CCA 艳楝诜谆摊 DB2 腮韦鹇嘻葑详
 
  邱为诜谆岩倾拟茄王腮韦鹇嘻卮胬艨母、鞋拟淠佝嗔摊肟軎朔苡·
  肟軎朔苡滔啬填谪啄友叔嘻朔苡埔恻软王肄茄卮胬艨母、洳掾谪啄劈
  卒倪卒绐散·

 
  鞒岂 SEARCH 谪啄劈卒惝沁峥诜谆嘻 TCP/IP 配缳妾秦辎、曦圊砒
  TCP/IP 配缳妾秦辎淘棚针岂 DB2 腮韦鹇朔苡惝沁嘻配缳妾秦辎肄茄·
  倾诜谆母、群配缳妾秦辎枳研嘻 IP 软蛇、岩岂艳楝倾诜谆瘼鹇
  母嘻 TCP/IP 腚傺秦辎腮韦鹇 (DNS) 唆暑贴、邱为栖艳楝 DNS、鞋岂
  诜谆配缳妾篁争你嘻枳研圄蜱唆暑贴·邱为却情远刭谫痞艳楝倾
  DB2 腮韦鹇朔苡母、铢睚贴 TCP/IP 却艳楝倾腮韦鹇母、盆享倾圊砒
  配缳妾秦辎淘棚针惝沁七睚嘻配缳妾秦辎、虽睚贴诜谆母嘻 DNS 托
  欺軎配缳妾篁争枳研配缳妾秦辎摊驮友嘻 IP 软蛇·
 
 
  10.0  毓丈俣澌
 
 
  10.1  DBI1768W 氅忘你嘻蜚毹
 
  倾 "侬散" 阳姣亩、枳 "sqllib/profile" 嘻俣澌筌收页
  "sqllib/db2profile"·
 
 
  10.2  SQL0270N 嘻呢收/抬破韵寝睿
 
  毓丈 SQL0270N 嘻亩悄韵寝睿呢孱收〃
 
    倾 "韵寝" 阳姣亩〃
 
       23  REPLICATED 品卒牙贴峥栩友闲知·
 
    倾 "侬散" 阳姣亩〃
 
       23  劓篇 REPLICATED 牙贴、托睚毳 CREATE TABLE 岩闪牙贴
           倾栩友闲知贴屮你·
 
  亩悄胎远韵寝睿呢浠炝容毓丈 SQL0270N〃
 
    倾 "韵寝" 阳姣亩〃
 
       30  岣楝脓形嘻闲知滔渫堠闲嘁挝贴屮王 CREATE SCHEMA
           蒹虞娶·
 
       31  嘁挝盆 500 远盆母嘻牺唆贴屮拧薮躏·
 
    倾 "侬散" 阳姣亩〃
 
       30  枳王倾 CREATE SCHEMA 蒹虞娶评域嘻岣楝脓形渫堠闲托
           岣楝脓形闲知圊砒 CREATE 蒹虞娶·

 
       31  嗟欧拧薮躏你嘻牺戆·
 
 
  10.3  SQL0351N 嘻浠氅忘
 
  毓丈〃倾 select-list 嘻 "<position-number>" 软弭你嘻 LOB 托
        DATALINK 骜砧、嘁挝损祁 DRDA 葑毓潭贴惝厥砒篇·
 
  韵寝〃LOB 托 DATALINK 骜砧、托盆 LOB 托 DATALINK 骜砧页僮鲳
        嘻种直形、嘁挝损祁 DRDA 葑毓潭贴唆惝蛴·"<position-number>"
        岩牙倾 select-list 你、芍 LOB 托 DATALINK 骜砧形嘻镊酌逆软弭·

 
  群蒹虞娶嘁挝莰堋·
 
  侬散〃睚贴倾损祁 DRDA 栖惝厥 LOB 托 DATALINK 骜砧针、呢诜
  input-list 你陉劓菡胎辍骜砧·盆 LOB 骜砧仍似、孳後损祁 CHAR
  (SUBSTR(CLOB)) 唆蛸探垣嘻绀难炮阳·盆 DATALINK 骜砧仍似、
  孳後损祁 DURLCOMPLETE 逆嘻酞戆·
 
       sqlcode:  -351
       sqlstate:  56084
 
 
  10.4  SQL0352N 嘻浠氅忘
 
  毓丈〃倾 input-list 嘻 "<position-number>" 软弭你嘻 LOB 托
  DATALINK 骜砧、嘁挝损祁 DRDA 葑毓潭贴惝厥砒篇·
 
  韵寝〃LOB 托 DATALINK 骜砧嘁挝损祁 DRDA 葑毓潭贴唆惝蛴·
  "<position-number>" 岩牙倾 input-list 你、芍 DATALINK 骜砧
  形嘻镊酌逆软弭·
 
  群蒹虞娶嘁挝莰堋·
 
  侬散〃睚贴倾损祁 DRDA 栖惝厥 LOB 托 DATALINK 骜砧针、呢诜
  input-list 你陉劓菡辍骜砧·贫摹辍派挝岩损祁 DLVALUE 酞戆、
  怄谫喧弭垣·
 
       sqlcode:  -352
       sqlstate:  56084
 
 
  10.5  SQL0357N 嘻浠氅忘
 
  毓丈〃DB2 File Manager "<server-name>" 气些嘁挝损祁·
  韵寝
       睿 = "<reason-code>"·
 
  韵寝〃友囚探 DB2 File Manager "<server-name>" 针、腈友枳
  DATALINK 垣嘻俣澌·DB2 File Manager 气些嘁挝损祁、摹邱韵寝睿
  驮闲泣·
 
       01 DATALINK 垣你嘻 DB2 File Manager 嘁挝损祁·
 
       02 庑如散淦嘻骜砧栈腮韦鹇。争梭。托骜砧栈、栖倾 DATALINK
          垣你盆 DB2 File Manager 披盆圄卮·
 
       03 倾 DB2 File Manager 母、屿浠邛侬擀韵散淦箨弭你托庑如你·
 
       04 DATALINK 垣你嘻 DB2 篁争戋堋幔娶呢倾骜砧栈你圄卮、叁破
          岩摹远栖稀嘻腮韦鹇·
 
       05  曦 DATALINK 垣你嘻 DB2 File Manager 葑详针圊祈蜚毹·

 
  群蒹虞娶嘁挝莰堋·
 
  侬散〃侬散狺韵寝睿仍贴、邱亩驮泣·
 
       01 DB2 File Manager 托葑详岣偏卒你鏊·帷靴锹孳、托亲
          朔苡戋堋席谣骀 DB2 File Manager·邱为俾黝捏嘤囚倾、
          鞋泞鏊筌祁幔娶曦骜砧栈嘻葙罾、岖屿浠葙谫逆靴锹孳·
 
       02 倾 DB2 File Manager 你圄卮骜砧栈腮韦鹇。争梭。托骜砧栈·
 
       03 岖苑 DB2 File Manager 母嘻屿浠邛侬擀韵散淦声醛·
          邱为俾黝捏嘤囚倾、篝宴岩闪声醛母虞韵寝睿 02 牌求驮呷暖
          逆圄卮·菡偏卒岩屿浠邛侬擀韵散淦栖恹沙声醛嘻韵寝逆摹·

 
       04 篝宴骜砧栈呢艳楝嘻 DB2 File Manager 倾杲纣母卒闪损祁·

 
       05 篝宴 DB2 File Manager 滔葑详岣岩闪邛侬·
          邱为俾黝捏嘤囚倾、
          鞋泞鏊筌祁幔娶曦骜砧栈嘻葙罾、岖屿浠葙谫逆靴锹孳·
 
       sqlcode:  -357
       sqlstate:  57050
 
 
  10.6  SQL0432N 嘻浠氅忘
 
  SQL0432N 嘻氅忘呢收页琵涯俣澌形嘻肄茄蜚毹〃

 
  毓丈〃俣戆卮胬拟偏盆却损祁席贴屮嘻形秦辎托俣澌气砗形秦辎
  "<udt-name>"·
 
  韵寝〃暑贴蒹虞娶你嘻俣戆卮胬页苔却损祁席贴屮嘻形 "<udt-name>"、
  托页苔却气砗形 "<udt-name>" 嘻俣澌形、岩拯疸损祁破嘻母亩牌
  仍贴·俣戆卮胬拟偏盆祁损祁席贴屮嘻形托俣澌形散页抬骜砧形、
  劓湘破岩牙贴嘻摹蒎枪 (INSERT 嘻 VALUES 耐苹、托 UPDATE 嘻 SET
  耐苹)、托破损祁 CAST 萁知、忘睚氢诎瘫魉形醛损祁席贴屮嘻种直骜砧
  形托俣澌骜砧形·群蒹虞娶嘁挝莰堋·
 
  侬散〃页俣戆卮胬损祁忘泣诎瘫魉形醛嘻损祁席贴屮种直骜砧形、
  托俣澌骜砧形·贫摹辍派挝岩诎瘫魉形损祁席贴屮种直骜砧形嘻
  牺、醛页抬肄枳筌嘻唆溷骜砧形、托诎瘫魉形俣澌骜砧形嘻牺
  、醛页抬肄枳筌嘻闲泣挝形·

 
       sqlcode:  -432
       sqlstate:  42841
 
  SQLSTATE 42841 嘻牌求呢收页〃
 
       42841  俣戆卮胬嘁挝岩损祁席贴屮嘻形托俣澌形·
 
 
  10.7  SQL0680N 嘻浠氅忘
 
  呢院恃嘻韵寝〃输摹远闲知诈萋嘻薏乃牺戆、岩拯疸闲知熄怄嘻喻
  域乃难仍贴·闲知嘻宇瘫邱亩〃
 
  o   4KB 喻域乃难诈萋 500 远牺
 
  o   8KB 喻域乃难诈萋 1012 远牺·
 
  牺戆偏卒饩砒聿针闲知驮诈萋嘻薏乃戆、孚闲知芍却偏祁唆莰堋蒹
  虞娶嘻聿针闲知熄怄·

 
  浠侬散〃邱为莰堋宴骀针圊祈蜚毹、鞋喧恰摹远驮排呶逆薏乃喻域乃
  难嘻聿针闲知熄怄 (邱为烃栖喧恰嘻驺)·邱为群闲知熄怄呢囚倾、
  鞋诜聿针闲知你探旨摹远托情远牺·

 
 
  10.8  SQL0903N 嘻抬破韵寝睿
 
  毓丈 SQL0903N 嘻韵寝睿 3 呢收页〃
 
       3. 俣曦群闹散尢镊嘻抬你摹远 DB2 File Manager 嘁挝漤蕃 COMMIT·

 
 
  10.9  SQL0911N 嘻抬破韵寝睿
 
  message SQL0911N 却摹远浠嘻韵寝睿〃
 
       72. 墁侬呢孱擀韵、寝页埕帜墁侬逆 DB2 File Manager 嘻肄
           蜚毹·
 
 
  10.10  SQL1339N 嘻浠氅忘
 
  亩悄骜毓呢浠炝容 "韵寝" 阳姣〃
 
       枳王 CLI/ODBC 筌祁幔娶、拟淠惝沁蜚毹苁卮·
       CLI/ODBC 筌祁幔娶偏盆损祁 SQLGetDiagRec。SQLGetDiagField。
       托 SQLError API、唆探诘王输摹远蜚毹嘻收情骜毓·
 
 
  10.11  损祁收葑如睿排呶针砒堍嘻 SQL5048N 托 SQL0901N
 
  邱为倾损祁 DB2 侮欺 5.2 收葑如睿排呶针圊堍毓丈 SQL5048N 托
  SQL0901N、群蜚毹嘻薏偏卒韵寝岩、骜砧栈腮韦鹇嘻侮裙拟排呶骜砧
  栈诜谆嘻侮裙·

 
  菡髓毓丈偏卒岩寝 CONNECT 托 ATTACH 友叔仍惝沁、群友叔牙贴浠
  葑如睿、赔损祁 AUTHENTICATION=CLIENT·邱为岩菡淼、鞋牙秦
  骜砧栈杀秦嘻欺軎骜砧栈气蜱圄蜱栖牙贴 AUTHENTICATION=SERVER·
 
  邱为母虞蜚毹岩寝 CONNECT 托 ATTACH 友叔仍惝沁、群友叔枳 DB2
  Common Server 侮欺 2 托 DDCS 侮欺 2 情损祁席缧绗呷砒浠葑如睿、
  鞋孚骜砧栈杀秦嘻欺軎骜砧栈气蜱圄蜱埔恻牙贴 AUTHENTICATION=CLIENT·
 
 
| 10.12  浠毓丈 SQL5156N〃DBM 艳楝俣戆 TRUST_ALLCLNTS 嘻垣
 
| SQL5156N 骜砧栈戋堋幔娶艳楝俣戆 "TRUST_ALLCLNTS" 嘻垣埔恻岩 NO。
| YES 托 DRDAONLY 嘻抬你摹远·
 
| 韵寝〃艳楝俣戆 "TRUST_ALLCLNTS" 镍萋嘻垣邱亩〃
 
| 1.  NO = 0
 
| 2.  YES = 1
 
| 3.  DRDAONLY = 2
 
| 属却伉嵌若驮友叔嘻收·
 
| 侬散〃铢屿浠呷砒孚淘棚·屿浠呷砒针、铢牙贴 "TRUST_ALLCLNTS" 嘻却真垣·
 
 
  10.13  SQL20053N 嘻抬破韵寝睿
 
  亩悄韵寝睿呢浠炝容毓丈 SQL20053N〃
 
    倾 "韵寝" 阳姣亩〃
 
       6.  倾岣楝脓形渫堠闲怅煲岣楝你、输摹远耐渫堠闲嘻 FROM
           耐苹你嘻闲知托渫堠闲、埔恻损祁 OUTER (邱为耐渫堠闲
           损祁 OUTER)·
 
    倾 "侬散" 阳姣亩〃
 
       6.  邱为菡岩苌摹远损祁 OUTER 嘻耐渫堠闲、鞋收 FROM 耐苹、
           醛拟损祁 OUTER·邱为耐渫堠闲损祁 OUTER、铢衮 OUTER
           索墨耐渫堠闲嘻 FROM 耐苹·
 
 
  10.14  SQL20056N 嘻浠毓丈牌求
 
  亩悄岩 SQL20056N 嘻收浠靴毓丈牌求〃
 
       DB2 File Manager "<server-name>" 母嘻莰堋圊堍蜚毹·韵寝
       睿 = "<reason-code>"·抬破猬鏊骜毓 "<diag-token>"·
 
  蕃狻〃  气些 "<diag-token>" 摹眩菝贴页 "UNKNOWN"·
 
 
  10.15  SQL30083N 嘻抬破韵寝睿
 
  王收葑如睿排呶嘻亩悄韵寝睿 (邱为破岩寝页嘁真嘻损祁席秦辎
  托葑如睿仍坡邗)、呢浠炝容毓丈 SQL30083N〃
 
    倾 "韵寝" 阳姣亩〃
 
       24.  损祁席秦辎暖/托葑如睿嘁真·
            宓收葑如睿寝页损祁席秦辎托韵填葑如睿蜚毹仍坡邗针
            惝沁·

 
 
  11.0  矢葳墨宪
 
 
  11.1  倾仝如 WINDOWS 95 嘻 NEC PC98 瘼鹇母区嬉 DB2
 
  宓诶倾仝如 Windows 95 嘻 NEC PC98 母损祁嘻牌堑呢区嬉魔 DB2 针、
  区嬉散淦倾声醛 96% 针佤畔·友声醛区嬉〃
 
 
  1.  岣手 IMQCRINS.EXE 莰堋·勖岣手菡恸莰堋、铢押 <CRTL><ALT><DELETE>
      唆怃邛≈散淦戋堋幔娶∽·蛸探 IMQCRINS 莰堋虽押摹亩≈岣手∽
      押廒·
 
  2.  宓区嬉声醛针、屿浠邛侬朔苡·
 
 
  11.2  倾仝如 WINDOWS 95 嘻 NEC PC98 瘼鹇母尕劓区嬉 DB2
 
  邱为诶呢倾仝如 Windows 95 嘻 NEC PC98 母损祁嘻牌堑区嬉魔 DB2 、
  尕劓区嬉散淦淠倾破声醛些佤畔·勖声醛尕劓区嬉散淦〃

 
  1.  岣手 UNINSTNQ.EXE 莰堋·勖岣手菡恸莰堋、铢押 <CRTL><ALT><DELETE>
      唆怃邛≈散淦戋堋幔娶∽·蛸探 UNINSTNQ 莰堋虽押摹亩≈岣手∽
      押廒·
 
  2.  诜区嬉 DB2 嘻轹轺瘼纱劓 imnnq_95 气蜱·
 
 
  11.3  佑琚区嬉
 
 
  11.3.1  菰腈叔/腮韦鹇塄新腈叔
 
  寝页 HP 拟锹排呶 NETWARE 塄新、驮盆 IPX/SPX 倾 HP-UX 侮欺
  11.0 母拟莘排呶·
 
 
  11.3.2  王 OS/2 诜谆嘻诜谆塄新腈叔/菰腈叔
 
  友 OS/2 诜谆损祁 DB2、腈友却 ADSTAR Distributed Storage Manager (ADSM)
  侮欺 3 嘻 PTF (幔娶聿针院釉) 3·
 
 
| 11.3.3  DBCS 艨韬逆 OS/2 WARP SERVER V.4 嘻谡瘫你爬腈叔
 
| 邱为诶岩倾 DBCS 艨韬嘻 OS/2 Warp Server 侮欺 4 母仝如 DB2 UDB
| OS/2 S)、鞋押胎亩≈谡瘫你爬∽璺泣苫淠惝沁朔苡蜚毹 SYS3175·
| 嘤仍、孚蜚毹圊祈摹裙盆靴、邱为诶锹押胎亩孚璺泣、≈谡瘫你爬∽苫
| 淠怃邛·
 
| 友佤畔 SYS3175 毓丈砒堍倾苌摹远氢派、铢区嬉 OS/2 FixPak WX03005
| 托收浠侮欺·
 
 
  11.3.4  DB2 FOR AS/400 容 DB2 UNIVERSAL DATABASE FOR AIX。OS/2。
          滔 WINDOWS NT 嘻 SNA 葙谫
 
  诜 DB2 for AS/400 葙谫摊 DB2 Universal Database for AIX 侮欺
  5.2 针、拟排呶损祁 SNA 嘻抹怅阳睚贴·诜 DB2 for AS/400 葙谫
  摊 DB2 Universal Database for OS/2 暖 Windows NT 侮欺 5.2 针、
  倪排呶·
 
 
| 11.3.5  倾茄摹远瘼鹇母、TP 秦辎倾 DB2 争梭逆你埔恻岩倌摹嘻
 
| 倾茄摹远瘼鹇母、TP 秦辎倾 DB2 争梭逆你埔恻岩倌摹嘻·闪鞋、邱为
| 戆远 DB2 争梭苑茄摹远 TP 秦辎、鞋 APPC 暖 TCPIP 葭淠牙姚苌摹
| 远葙罾峥七睚嘻 DB2 争梭、仍赔衮苌抹远葙罾牙姚峥拟七睚嘻 DB2 争
| 梭·
 
 
  11.3.6  菰强暑劬堑/DB2 FOR OS/390 喧嘻院七幔娶
 
  诜 DB2 for OS/390 配缳妾囚探 DB2 Universal Database 腮韦鹇针、
  腈却亩悄 DB2 for OS/390 PTF〃
 
  o   PTF UQ06843 for APAR PQ05771
 
  o   PTF UQ09146 for APAR PQ07537
 
 
  11.4  DB2 UNIVERSAL DATABASE 墨宪 (收葑如睿)
 
  诜 DB2 诜谆收倾 DB2 腮韦鹇母嘻葑如睿、菡恸卒陌宇王亩悄
  DB2 腮韦鹇〃
 
  o   DB2 for OS/390 V5 托 V5 盆母
  o   DB2 Universal Database for AIX V5.2
  o   DB2 Universal Database for OS/2 V5.2
  o   DB2 Universal Database for Windows NT V5.2
 
 
  11.5  DB2 UNIVERSAL DATABASE 墨宪 (佑戢 AIX 母嘻虽如损祁席)
 
  ≈UNIX** 矢葳墨宪∽苌 15 蔟俣澌≈彗龅髡贴戋堋闹苔∽(Nodelock
  Administration Tool, NAT)、破岩 License Use Management
  Administration Runtime Kit (LUM ARK) 嘻摹蒎枪·友佑戢 AIX 母
  嘻虽如损祁席、埔恻倾朔苡母区嬉芍却 NAT 嘻 LUM ARK·倾衍髓
  LUM ARK 侮欺你、NAT 岩偏蛸祁嘻篁争怩·孥茇骜毓铢俣镥 LUM 牌堑·
  诶偏盆谪菥 IBM License Use Management Web 杲谆〃
 
       http://www.software.ibm.com/is/lum
 
  唆亩绁薏浠 LUM ARK 滔砒侮新·页魔派享啬四、 LUM ARK 嘻蕃枪呢
  索墨 DB2 CD 嘻 /cdrom/LUM 气蜱你·
 
 
  11.6  损祁争梭 (浠炝骜砧栈拧薮俅腮韦鹇摊争梭、损祁 DB2
  EXTENDED ENTERPRISE EDITION FOR WINDOWS NT/损祁韵填嬉弭嘻
  腚傺损祁席 ID 腈叔)
 
  ≈DB2 Extended Enterprise Edition for Windows NT 矢葳墨宪∽
  摹阵、氅忘腚傺损祁席秦辎岩喧恰骜砧栈拧薮俅腮韦鹇驮埔友嘻、
  宓 DB2 邛侬页 Windows NT 韦侪幔娶针、友损祁群秦辎唆圄墨·
  拟绱友蚊泗、邱为损祁韵填嬉弭、鞋腚傺损祁席秦辎蹁埔恻苔蕃欺軎
  戋堋宇、闪鞋损祁席嘁挝囚探韵填嬉弭·

 
 
| 11.7  NT 母嘻 DB2START 属却惝沁七睚嘻毓丈
 
| 仝如 "db2start" 淘棚 (托损祁 "NET START" 淘棚) 唆邛侬 Windows NT
| 艨韬母嘻骜砧栈戋堋幔娶针、邱为嵌若葑详耐朔苡嘁挝邛侬、鞋孚淘棚拟
| 淠惝沁嵌若伤·损祁席筌孚友摹牺篝宴≈NT 绥堑攀擘∽托 "DB2DIAG.LOG" 、
| 亦亦仝如 "db2start" 哝怄驮绮摊嘻嵌若蜚毹·淠圊祈菡远俾黝嘻韵寝岩、
| Windows NT 艨韬母嘻骜砧栈戋堋幔娶淠烟如页 NT 韦侪幔娶、驮盆邱为恹
| 沙邛侬韦侪幔娶嘻驺、鞋拟淠惝沁蜚毹·
 
 
  11.8  诜鳟侮欺滔侮裙苊魉
 
  岂王薏孙脓闹苔嘻披诎劈卒、嵌若宴骀蛹屿浠葙岣针淠收佑琚·觯嘤
  呢阼探输摹恸邕诉谳烟唆睚像收靴嘻佑琚容欧滔鳟侮欺驮蛸疱嘻佑琚
  摹淼秋、叁岂王衍髓收淠鹨映蛸疱拟茄佑琚、驮盆拟像偏盆声抢伉
  摊、仍赔友嗔孳损祁席偏卒喧恰嘻嘁宇庳枰侪畀梭、岩拟偏卒嘻·

 
  遘摹宴骀屿浠葙岣容浠佑琚嘻驺、喧倾苊魉侮欺逆些枳驮却屿友嘻
  宴骀仝如 EXPLAIN·邱为菡臌伉、摅淠稀绗破驮隧疸嘻佑琚滔艳楝俣
  戆 (倾鳟侮裙逆亩)·菡淼享卒佘筚煞损祁席杀浠侮欺嘻崭墁唆溷、
  暖擀弭鳟佑琚嘻雾斡 (邱为诶泖友菡淼伉嘻驺)·

 
 
| 11.9  诜 DB2 侮裙 5.0 弄兹摊侮裙 5.2
 
| 却 "db2upd52" 淘棚嘻亩悄骜毓腈友浠炝摊 DB2 侮欺 5.2 烃栖擀浠
| 嘻侵≈矢葳墨宪∽阵你嘻·菡髓阵邱亩〃
 
|      DB2 Extended Enterprise Edition for UNIX 矢葳墨宪
|      DB2 Personal Edition 矢葳墨宪
|      DB2 UDB Enterprise Edition for OS/2 矢葳墨宪
|      DB2 UDB Enterprise Edition for Windows NT 矢葳墨宪
 
| 收浠气蜱闲知骜砧
 
  +------------+--------------------------------------------------------------+
| |            | 邱为诶岩衮 DB2 诜侮欺 5 弄兹摊侮欺 5.2、诶品腈友仝如         |
| |            | DB2UPD52 牙棚·邱为岩衮 DB2 诜侮欺 2 弄兹摊侮欺 5.2、        |
| |            | 鞋骜砧栈苊魉淠收浠骜砧形暖 SYSFUN 昃气·                   |
  +------------+--------------------------------------------------------------+
 
| 盆 DB2 侮欺 5.2 仍似、SYSIBM.SYSDATATYPES 气蜱闲知琵涯浠嘻骜砧形
| "BIGINT"、盆暖 SYSFUN 昃气你抬破肄嘻酞戆·友排呶菡髓浠嘻种吞针、
| 喧诶友弄兹页侮欺 5.2 逆 DB2 争梭驮疬却嘻输摹远骜砧栈薏秋葭友仝如
| DB2UPD52 淘棚·孚淘棚淠浠炝排呶 "BIGINT" 骜砧形嘻浠 SYSFUN 酞戆
| 闲泣挝、邱亩〃
 
| o   衮 "SYSIBM.BIGINT" 浠炝摊 SYSIBM.SYSDATATYPES 气蜱闲知你·
 
| o   衮亩悄酞戆闲泣挝浠炝摊 SYSIBM.SYSFUNCTIONS 闲知你〃
 
|          create function sysfun.abs(bigint) returns bigint ...
|          create function sysfun.absval(bigint) returns bigint ...
|          create function sysfun.ceil(bigint) returns bigint ...
|          create function sysfun.ceiling(bigint) returns bigint ...
|          create function sysfun.floor(bigint) returns bigint ...
|          create function sysfun.mod(bigint,bigint) returns bigint ...
|          create function sysfun.power(bigint,bigint) returns bigint ...
|          create function sysfun.round(bigint,integer) returns bigint ...
|          create function sysfun.sign(bigint) returns bigint ...
|          create function sysfun.trunc(bigint,integer) returns bigint ...
|          create function sysfun.truncate(bigint,integer) returns bigint ...
 
| DB2UPD52 淘棚木淠浠炝 "REAL" 骜砧形摊 SYSIBM.SYSDATATYPES 气蜱
| 闲知你、虽衮 UCASE (SYSFUN.UCASE) 嘻酞戆闲泣挝 (邱为蜍榕嘻驺) 浠
| 炝摊 SYSIBM.SYSFUNCTIONS 闲知你·却 DB2UPD52 淘棚嘻耄挝、铢俣
| 镥 Command Reference、盆探诘孥茇嘻骜毓·
 
| 邱腈 "db2upd52" 淘棚嘻肄骜毓、铢俣镥≈DB2 Universal Database
| for UNIX 矢葳墨宪 侮欺 5.2∽嘻苌 6 蔟 "诜 DB2 侮裙 5.0 弄兹摊
| 侮裙 5.2"·
 
 
| 11.10  LOTUS DOMINO GO WEB 腮韦鹇嘻 DB2 侬幔娶蜚毹
 
| 邱为诶岩损祁 Lotus Domino Go web 腮韦鹇、鞋淠圊祈亩悄蜚毹〃
 
|      java.sql.SQLException: 刭弭艨韬 handle 针圊祈 DB2 侬幔娶蜚毹、rc=-1
 
| 屿浠邛侬 web 腮韦鹇、虽牙贴 db2instance、邱亩〃
 
|      startsrc -e "DB2INSTANCE=yourInstanceName" -s httpd
 
| 铢木睚毳 "httpd.conf" 篁你嘻 CLASSPATH 暖 LD_LIBRARY_PATH 岩闪菝
| 贴七睚 (远杀损祁牙棚 "JavaClassPath" 暖 "JavaLibPath")·铢睚毳破
| 辕岩牙亲埔友嘻 UDB 侮欺 5.2 篁争·
 
 
  11.11  仝如溶淖嘻筌祁幔娶 (仝如 JAVA 幔娶)
 
  DB2 拟排呶 Java 竺囚幔施滔 Java 损祁席贴屮酞戆 (UDF) 倾 HP-UX
  滔 SCO UnixWare 腮韦鹇母囚探 DB2 骜砧栈·
 
 
  11.12  DB2 塄新嘻涅诈 (耄似艨韬嘻翥煅)
 
  祁王 DB2 for Solaris 滔 DB2 for SCO UnixWare 7 嘻呕乳婀犭袍
  耄似艨韬嘻翥煅、呢诜 "pt" 收页 "pt_BR"·
 
 
  12.0  DB2 File Manager 矢葳墨宪
 
 
| 12.1  诜谆艳楝憔墨暖憔砒
 
| 倾区嬉却 FixPak 7 嘻诜谆母驮喧恰嘻≈诜谆艳楝憔砒菝贴篁∽品
| 卒倾木区嬉却 FixPak 7 嘻诜谆母憔墨·
 
 
| 12.2  DB2 DATA LINKS MANAGER 嘁挝区嬉倾 DB2 ENTERPRISE -
| EXTENDED EDITION 朔苡母
 
| DB2 Data Links Manager (摹罪辎逆页 "DB2 File Manager") 品卒曦
| DB2 for AIX Enterprise Edition 摹啬损祁·Data Links Manager 嘁
| 挝倾 AIX 盆评嘻散淦朔苡母曦骜砧栈摹啬损祁、仍赔嘁挝曦 DB2
| Enterprise - Extended Edition (EEE) for AIX 摹啬损祁·DATALINK
| 垣嘁挝牙亲 DB2 EEE 朔苡¨仍赔、DATALINK 骜砧形嘁挝倾 EEE 朔苡
| 母损祁、唆俣澌 DB2 Data Links Manager 母嘻篁争·
 
 
  12.3  DLFM 戋堋损祁席 ID
 
  群侮裙嘻 DLFM 戋堋损祁席 ID 埔恻岩 "dlfm"·
 
 
  12.4  损祁 NFS 唆囚探肟軎 DLFS 篁争朔苡
 
  盆 "READ PERMISSION DATABASE" 蛸恸贴屮逆 DATALINK 牺母嘻 SQL
  SELECT 淠惝沁苔却涅芍倾孚秦辎你逆囚探苁卮嘻 URL 托篁秦·群囚探
  苁卮淠却摹远哝宇、邱 DL_EXPINT 骜砧栈艳楝俣戆驮贴屮嘻·损祁 NFS
  诜谆唆囚探菡淼嘻篁争针、诶偏卒淠圊堍囚探苁卮属却绱哝·菡岩寝
  页 NFS 诜谆声醛矢探·破蒹虞损祁羡篁秦 (饩远 12 远求镊) 偏卒淠
  嗟爰菡远俾黝·
 
  输宓诶孱岂 NFS 诜肟軎嬉绁 DLFS 篁争朔苡针、诶木友琵涯嬉绁蛸恸
  "noac"·梭邱〃
 
       mount -o noac birdcage:/dlink /dlink
 
 
  12.5  王 DATALINKS 诜谆嘻宇瘫
 
  Datalinks 诜谆嘁挝〃
 
  o   倾 Windows 3.1 散淦朔苡母·
  o   倾 DB2 侮欺 5.2 煲裙盆亩 (AIX 嘻诜谆劓评)、破木偏盆岩
      FixPak U453782 侮欺 5.0 托 5.0 盆母·
 
 
  12.6  DLFM 呢收嘻菝弭蛸恸
 
  DLFM 区嬉嘻淘棚呢收页谫炭 dlfm_db 艳楝篁·邱为艳楝篁琵芍区
  嬉蛸恸、鞋损祁篁争你嘻艳楝蛸恸唆蓬咤邕菝垣·群篁争岩偏蛸祁嘻·
  邱为栖牙贴、鞋损祁邕菝垣·淘棚耄挝邱亩〃

 
       dlfm setup [<dlfm_db_config_file>]
 
  亩悄岩畀梭艳楝篁、秦辎页 dlfm_db.cfg〃
 
    # Sample dlfm_db.cfg file for DLFM setup
    # Please note: the equal sign is needed between the option name and the value.
    # Any of the updateable DB2 database configuration parameters can be included in this file.
    # There are also three special DLFM-specific options which the user can specify:
    # DLFM_DB_DIR : directory where the dlfm_db database is to be created
    # DLFM_DB_CATTBL_DIR : directory where the catalog table space is to be located
    # DLFM_DB_TMPTBL_DIR : directory where the temporary table space is to be located
    # If there are no values for these options, or the options are not present,
    # default values are used.
    ####################
    DLFM_DB_DIR=
    DLFM_DB_CATTBL_DIR=
    DLFM_DB_TEMPTBL_DIR=
    LOCKTIMEOUT=60         # Default and recommended value for dlfm_db is 60
    LOGFILSIZ=2001         # Default and recommended value for dlfm_db is 2001
    LOGPRIMARY=6           # Default and recommended value for dlfm_db is 6
    MAXAPPLS=128           # Default and recommended value for dlfm_db is 128
    MAXLOCKS=100           # Default and recommended value for dlfm_db is 100
 
 
  12.7  倾篁争戋堋幔娶腮韦鹇母诜轹轺浯溱你沁擀
 
  欺彗衮氅忘篁争戋堋幔娶腮韦鹇母嘻轹轺浯溱靴邱若仝如擀韵、盆暖
  戋堋席倾排呶菡摔辋擀韵枰侪畀梭针埔恻幼菔嘻蕃枪岈堠·

 
  蕃狻〃倾 DB2 File Manager 母蛹瘼鹇浯溱嘻驺、鞋曦 DB2 File
        Manager 碾侬嘻 DB2 筌祁幔娶偏卒淠宓卩·铢损祁 FORCE
        APPLICATION 淘棚、诎鱼菡淼嘻筌祁幔娶蒺朔苡·倾 DB2
        腮韦鹇母蛹瘼鹇浯溱嘻驺、鞋筌孚木淠损祁 "dlfm shutdown"
        淘棚唆蒺炭爨嘻 DB2 File Manager·
         嘤靴、破辕淠锹裙
        佤畔·
 
  邱为琵芍损祁席骜砧嘻轹轺浯溱、鞋淠葙茄篁争朔苡气蜱怅煲岣楝摹
  啬浯溱·]友诜菡枰侪畀梭沁擀、鞋戋堋席埔恻犒散篁争朔苡贴哝
  蕃枪、唆琵芍损祁席骜砧滔气蜱怅煲岣楝、盆享擀弭·
  擀弭嘻篁争朔苡埔恻像昼气蜱滔篁争驮却、盆暖针怄雒卮·擀弭篁
  争朔苡逆靴、埔恻趴祁倾阼祁篁争朔苡蕃枪逆靴圊祈嘻气蜱收、损
  气蜱岣楝卒佘泣容浯溱针怄龅·倾群抒逆靴、枳王琵芍炭浯轹轺
  篁争嘻驮却闲知、埔恻仝如 RECONCILE 淘棚·却呷蓑狞祁幔娶
  "db2_reconcile_aid" (软王 sqllib\misc) 唆鳇脓群散淦、虽呃虞邱
  亩·
 
  蕃狻〃
 
  1.  倾岣雾梃赔却菝贴 RECOVERY NO 蛸恸嘻篁争、盆亩悄派娶莰堋〃
 
      o   邱为倾篁争朔苡母势拟摊篁争、DATALINK 垣衮菝贴页 NULL·
      o   邱为却势摊篁争、赔破苔却 READ 滔 WRITE PERMISSION FS、
          鞋淠伉摹髓厢披嘻篝宴、唆篁争嘻七睚吞·

      o   邱为却势摊篁争、赔破苔却 WRITE PERMISSION BLOCKED、鞋
          衮篝宴破嘻院恃针怄滔篁争乃难·邱为垣拟苁琴、DATALINK
          垣衮菝贴页 NULL·
 
  2.  倾岣雾梃赔却菝贴 RECOVERY YES 蛸恸嘻篁争、盆亩悄派娶莰堋〃
 
      o   邱为势拟摊篁争、托篁争院恃针怄难王岣针嘻篁争院七针怄、
          鞋衮诜像囚腮韦鹇擀弭篁争嘻七睚侮欺·

      o   邱为篁争院恃针怄乃王岣针嘻篁争院恃针怄、鞋 DATALINK
          垣衮菝贴页 NULL·
 
  3.  剀枳七睚吞、篁争腮韦鹇母莰王栖岣雾梃嘻篁争拟淠蹁韵托篝宴·
 
  蕃枪暖擀弭篁争朔苡
 
  亩悄牙泣岩剀枳 AIX 侮欺 4.1.5、偏卒拟锼琴抬破散淦朔苡·损祁席
  埔恻盆 root 圄墨、倪卒仝如蕃枪托擀弭散淦·

 
  蕃枪
 
  筌盆侮欺 3 inode 知娶犒散蕃枪〃
 
  1.  尕劓嬉绁友蕃枪嘻篁争朔苡·
 
           朔苡竺囚戋堋 --> 篁争朔苡 --> 尕劓嬉绁篁争朔苡
 
  2.  蕃枪篁争朔苡·
 
           朔苡竺囚戋堋 --> 篁争朔苡 --> 蕃枪篁争朔苡
 
      炝庳娶蕃枪岈堠偏祁唆嗟欧擀韵针怄·
      煲裙 0 闲泣声痨蕃枪、煲裙 1 摊 9 闲泣炝庳娶蕃枪·
      煲裙 n 蕃枪品蕃枪诜煲裙 (n-1) 蕃枪靴收嘻篁争·
      煲裙 n 蕃枪逆靴、友阼祁嘻亩摹远蕃枪岩煲裙 (n+1)
      蕃枪·
 
      木偏盆诜淘棚如趟频蕃枪〃
 
           % backup -<level> -uf <backup device> <filesystem>
 
           畀梭〃
              声痨蕃枪损祁〃
                 % backup -0 -u -f/dev/rmt0 /dlfs1
              亩摹远炝庳娶蕃枪损祁〃
                 % backup -1 -u -f/dev/rmt1 /dlfs1
              倾群逆靴嘻炝庳娶蕃枪页〃
                 % backup -2 -u -f/dev/rmt2 /dlfs1
 
  3.  嬉绁运倪蕃枪嘻篁争朔苡·
 
           朔苡竺囚戋堋 --> 篁争朔苡 --> 嬉绁篁争朔苡
 
 
  擀弭
 
  筌损祁强些阼祁嘻蕃枪逆摹仝如擀弭〃
 
  1.  嬉绁友擀弭篁争朔苡嘻嬉弭·
 
           朔苡竺囚戋堋 --> 篁争朔苡 --> 嬉绁篁争朔苡
 
  2.  擀弭篁争朔苡·擀弭淘棚卒佘蛘蕃枪知娶·

 
           朔苡竺囚戋堋 --> 篁争朔苡 --> 擀弭篁争朔苡
 
 
  木偏盆诜淘棚如趟频擀弭·诜友仝如擀弭嘻气蜱 (签苫篁争朔苡嬉弭
  嘻嬉绁龅) 圊砒亩悄淘棚〃

 
       % restore -r -f <backup device>
 
  邱为损祁炝庳娶蕃枪岈堠、鞋擀弭薏浠煲裙 0 蕃枪、嘤靴擀弭倾煲裙
  0 蕃枪靴阼祁嘻煲裙 1 蕃枪·
  擀弭倾煲裙 (n-1) 蕃枪靴阼祁嘻煲裙 n 蕃枪·睚贴篁争朔苡 root
  你嘻篁争 "restoresymtable" 倾炝庳娶蕃枪嘻擀弭逆怄像呀声痨拟·

 
  蚊泗〃倾擀弭哝怄纽损祁 "-M" 蛸恸·"-M" 蛸恸收篁争嘻针怄雒卮、
  醛页擀弭篁争朔苡嘻针怄·

 
  邱为蕃枪托擀弭散淦岩萼绱 ADSM 仝如、鞋倾擀弭散淦逆靴腈友仝如
  inode 嘻声痨蕃枪、倪卒恃煅强些嘻蕃枪·

 
  犒散蕃枪针筌损祁亳祁掼·
 
  品擀弭气蜱
 
  损祁席偏盆迁铞娶氢损祁擀弭淘棚母嘻 "-i" 蛸恸唆擀弭篁争〃

 
       % restore -i -f <backup device>
 
  菡淼淠呷蓑损祁席摹枪蕃枪气蜱托篁争悄泣、虽赔损祁席庑墨迁铞
  娶 Shell·偏损祁 "-h" 蛸恸唆擀弭种贴气蜱·

 
  损篁争朔苡气蜱怅煲岣楝泣容堍如针怄龅
 
  气蜱收淠卮绁倾篁争 (err_log)/fsysadm.log 你、抬你嘻 (err_log)
  岩牙贴倾 /etc/sylog.conf 篁争你嘻蜚毹攀擘气蜱· 群篁争岩厢披嘻、
  拟淠莘桊鏊·  输摹远气蜱绥堑葭却摹远圄蜱· 菝贴篁争嘻吞木淠卮绁· 圄蜱嘻知娶邱亩〃
 
       Time = <timestamp> EUID = <integer>  UID = <integer> GID = <integer> Mode = <octal>
       Action = <CREATE/REMOVE/SETATTR> Object type = <DIR/FILE> Path = <fully qualified name>
 
       抬你〃
 
         Time 岩窑侬嘻针怄 (俅傺针怄)·
         EUID 岩损祁席仝如侬散嘻却真损祁席 ID·
         UID 暖 GID 岩喧恰逆篁争/气蜱嘻损祁席 ID 暖妃苴 ID、
         托院恃吞逆篁争/气蜱嘻损祁席 ID 暖妃苴 ID·
         Mode 岩盆默庑软闲泣篁争/气蜱嘻砑娶·
 
         Action 偏盆岩 CREATE (喧恰篁争/气蜱)。REMOVE (劓篇
         篁争/气蜱) 托 SETATTR (损祁席院恃篁争/气蜱嘻砑娶)·
         
         戊堑形偏盆岩 DIR (气蜱) 托 FILE (篁争)·
         Path 岩声
         痨纣绽嘻篁争/气蜱·
 
  擀弭篁争朔苡逆靴仝如铪痨盆损抬摹映
 
  db2_reconcile_aid 狞祁幔娶呷蓑摹辍瘼瘫、宓篁争腮韦鹇母圊祈轹
  轺坡邗逆靴、枳王曦篁争腮韦鹇母嘻 DATALINK 篁争骜砧偏卒拟摹映
  嘻闲知、群瘼鹇瘫淠篝宴暖仝如铪痨 RECONCILE·耄挝邱亩〃

 
       db2_reconcile_aid -check -db <db_name> [-server_name <fileserver_name>]
          [-reportdir <report_directory>]
 
       抬你〃
          -check:            悄泣偏卒腈友铪痨仍损抬摹映嘻闲知·
                             拟仝如铪痨散淦·
          db_name:           腈友仝如铪痨散淦嘻骜砧栈秦辎·

          fileserver_name:   友仝如铪痨散淦嘻 DLFM 秦辎·邱为栖
                             呷蓑秦辎、衮铪痨驮却篁争腮韦鹇·
          report_directory:  琵芍输摹远铪痨散淦嘻揶伤逆气蜱·仝如
                             铪痨嘻输摹远闲知淠喧恰亩悄知娶嘻篁争〃
                             <tbcshcema>.<tbname>.<ext>、抬你嘻
                             <tbschema> 岩闲知嘻昃气、<tbname> 岩
                             闲知秦辎、仍 <ext> 岩 .ulk 托 .exp·
                             .ulk 篁争你芍却篁争腮韦鹇母栖岣篁争
                             嘻悄泣、仍 .exp 篁争你芍却篁争腮韦鹇
                             母梭评篁争嘻悄泣·邱腈孥茇骜毓、铢俣镥
                             Command Reference 你 RECONCILE 淘棚嘻氅
                             忘·
 
 
| 12.8  蕃枪嘻骜砧岣戆 (DL_NUM_BACKUP)
 
| CONFIGURATION TYPE  骜砧栈
 
| PARAMETER TYPE      偏艳楝
 
| DEFAULT [RANGE]     3 [ 1 - 31 ]
 
| 菡远俣戆岩牙贴≈篁争戋堋幔娶∽像昼蕃枪骜毓逆薏浠蕃枪 (骜砧栈暖
| 闲知熄怄) 嘻戆气·
栖诜骜砧栈岣嘻篁争岩拯疸群垣驮拳怩摊嘻套摄·
| (1) 垣闲泣栖岣嘻篁争岩声醛亩摹远 DB2 蕃枪针驮拳怩摊嘻套摄·
 
| 群俣戆嘻邕菝垣岩 1 远蕃枪·
 
| 群俣戆锼祁王牙贴 "Recovery=Yes 嘻 DATALINK 牺·
 
 
  12.9  DB2 File Manager 沁擀枰侪畀梭
 
  嵌若朔苡、葭偏卒圊祈腈友种贴擀韵煲裙嘻坡真·DB2 File Manager
  枳王戆远擀韵枰侪畀梭趴庑摹辍浠嘻铒縻煲裙·欺彗悄砒戆远偏卒圊
  祈嘻坡真枰侪畀梭、盆暖诜菡髓枰侪畀梭你沁擀驮腈嘻抒·
 
  贴屮
 
       DLFS 篁争朔苡          - 圄卮嘻求欲  (/dlink)
       DLFM 蕃枪气蜱          - 蕃枪篁争嘻气蜱 (/home/dlfm/dlfm_backup)
       DLFM 啬填气蜱          - DLFM 损祁席 ID 嘻啬填气蜱 (/home/dlfm)
       DLFM DB2 骜砧栈        - 琵芍驮却 meta 骜砧嘻 DB2 骜砧栈 (DLFM_DB)
       DB2 骜砧栈             - 琵芍 DATALINK 骜砧形嘻呢圄卮骜砧栈 (CROWN)
 
  浯溱逆些喧仝如嘻绥恸
 
  倾拟茄篁争朔苡母腕弭 DLFM 骜砧栈 (DLFM_DB)。DLFS 篁争朔苡。
  DLFM 蕃枪气蜱。盆暖 DLFM 啬填气蜱·睚贴破辕拟橇祁轹轺·

 
  倾竺囚戋堋幔娶 (邱 IBM 嘻 ADSM) 母蕃枪 DLFS 篁争朔苡滔 DLFM
  蕃枪气蜱·菡淼偏盆倾圊祈嘻绥堑你呷蓑收情像盆诉轹轺咽脞·
  
 
  损骜砧栈曦摹远托情远 DB2 File Manager 肄酊·踱森却胎远骜砧栈
  曦摹远 DB2 File Manager 肄酊¨闪鞋、衍髓擀韵枰侪畀梭淠诘收
  披铒縻·

 
  贴哝仝如 DB2 骜砧栈嘻声痨骜砧栈蕃枪 (盆暖倾 DB2 File Manager 母
  嘻 DLFM_DB 骜砧栈)·
 
  娘臌惟乳淠坡真々
 
  亩悄凭远岩偏卒坡真仍腈友擀韵嘻镊堑〃
 
  o   琵芍却 DATALINK 牺嘻闲知逆 DB2 骜砧栈
 
  o   DB2 File Manager 嘻骜砧栈 (DLFM_DB)
 
  o   DB2 File Manager 嘻 DLFS 篁争朔苡
 
  o   DB2 File Manager 嘻蕃枪气蜱
 
  盆亩拧杀页菡髓镊堑嘻输摹远呷蓑魔 DB2 File Manager 擀韵枰侪
  畀梭·

 
  亩悄擀韵枰侪畀梭偏卒腈友茄针枳 DB2 彗龅滔 DB2 File Manager
  彗龅仝如摹髓散淦·输摹远抒嘻些域淠祁 "DB2:" 托 "DLFM:" 唆
  闲泣友声醛散淦嘻彗龅·

 
  倾驮却畀梭你、DB2 骜砧栈衮辎页 "crown"、琵芍 DATALINK 牺嘻
  DB2 闲知衮辎页 "datalinktable"·
 
  SCENARIO #1A:
 
  坡真〃
 
  DB2 骜砧栈蜍坡托陲酃¨偏损祁 DB2 蕃枪滔攀擘篁·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DB2:                  db2 "擀弭骜砧栈 crown"
       DB2:                  db2 "ROLL-FORWARD 骜砧栈 crown 摊攀擘岣盛"
                                 (阼祁针怄龅沁擀针、喧葭摊攀擘岣盛·)
       DB2:                  db2 "铪痨闲知 datalinktable 损抬摹映"
 
  枰侪畀梭 #1B:
 
  坡真〃
 
  DB2 骜砧栈呢忘睚陲酃¨偏损祁 DB2 蕃枪滔攀擘篁·
 
  沁擀抒〃 睚贴陲酃骜砧栈散淦呢声醛、赔曦孚骜砧栈肄酊嘻驮却
  篁争呢尕劓岣·
 
 
       彗龅                  散淦
 
       DLFM:                 db2 "葙谫摊 dlfm_db"
       DLFM:                 db2 "诜 dfm_bdid 蛸探 dbid。dbname。dbinst。hostname"
       DLFM:                 db2 "收浠 dfm_dbid 菝贴侬散=5
                               抬你 dbid=x'35B3D7BE0006BF7B'"
                                 (菝贴 dbid 岖王些摹抒你嘻垣·)
       DB2:                  db2 "擀弭骜砧栈 crown"
       DB2:                  db2 "ROLL-FORWARD 骜砧栈 crown 摊攀擘岣盛"
                                 (阼祁针怄龅沁擀针、喧葭摊攀擘岣盛·)
       DB2:                  db2 "铪痨闲知 datalinktable损抬摹映"
                                 (埔友嘻)
 
  枰侪畀梭 #2:
 
  坡真〃
 
  DLFM_DB 蜍坡¨偏损祁蕃枪滔 DLFM_DB 骜砧栈嘻驮却攀擘篁·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DLFM:                 db2 "擀弭骜砧栈 dlfm_db"
       DLFM:                 db2 "ROLL-FORWARD 骜砧栈 dlfm_db 摊攀擘岣盛"
 
  枰侪畀梭 #3:
 
  坡真〃
 
  DLFM_DB 蜍坡¨偏损祁 DLFM_DB 骜砧栈嘻蕃枪、叁湘驮却攀擘篁艺偏祁·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DLFM:                 db2 "擀弭骜砧栈 dlfm_db"
       DB2:                  db2 "铪痨闲知 datalinktable 损抬摹映"
 
  枰侪畀梭 #4:
 
  坡真〃
 
  坡篇 DLFS 篁争朔苡·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFS 篁争朔苡·
       DB2:                  db2_recon_aid crown
 
  枰侪畀梭 #5:
 
  坡真〃
 
  坡篇 DLFM 蕃枪气蜱·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFM 蕃枪气蜱·
 
  枰侪畀梭 #6:
 
  坡真〃
 
  坡篇
  DLFS 篁争朔苡¨坡篇 DLFM 蕃枪气蜱·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFM 蕃枪气蜱·
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFS 篁争朔苡·
       DB2:                  db2_recon_aid crown
 
  枰侪畀梭 #7:
 
  坡真〃
 
  DLFM_DB 蜍坡¨偏损祁蕃枪滔 DLFM_DB 骜砧栈嘻驮却攀擘篁· 坡篇
  DLFS 篁争朔苡¨坡篇 DLFM 蕃枪气蜱·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DLFM:                 db2 "擀弭骜砧栈 dlfm_db"
       DLFM:                 db2 "ROLL-FORWARD 骜砧栈 dlfm_db 摊攀擘岣盛"
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFM 蕃枪气蜱·
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFS 篁争朔苡·
                                 (诶腈友气蜱岣楝·)
       DB2:                  db2_recon_aid crown
 
  枰侪畀梭 #8:
 
  坡真〃
 
  DLFM_DB 蜍坡¨偏损祁 DLFM_DB 骜砧栈嘻蕃枪、叁湘驮却攀擘篁艺偏祁· 坡篇
  DLFS 篁争朔苡¨坡篇 DLFM 蕃枪气蜱·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DLFM:                 db2 "擀弭骜砧栈 dlfm_db"
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFM 蕃枪气蜱·
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFS 篁争朔苡·
                                 (诶腈友气蜱岣楝·)
       DB2:                  db2_recon_aid crown
 
  枰侪畀梭 #9:
 
  坡真〃
 
  DB2 骜砧栈蜍坡¨DLFM_DB 蜍坡¨偏损祁蕃枪滔 DLFM_DB 骜砧栈嘻
  驮却攀擘篁·坡篇
  DLFS 篁争朔苡¨坡篇 DLFM 蕃枪气蜱·
 
  沁擀抒〃
 
       彗龅                  散淦
 
       DLFM:                 db2 "擀弭骜砧栈 dlfm_db"
       DLFM:                 db2 "ROLL-FORWARD 骜砧栈 dlfm_db 摊攀擘岣盛"
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFM 蕃枪气蜱·
       DLFM:                 诜竺囚戋堋幔娶擀弭 DLFS 篁争朔苡·
       DB2:                  db2 "擀弭骜砧栈 crown"
       DB2:                  db2 "ROLL-FORWARD 骜砧栈 crown 摊攀擘岣盛"
                                 (阼祁针怄龅沁擀针、喧葭摊攀擘岣盛·)
       DB2:                  db2 "铪痨闲知 datalinktable 损抬摹映"
 
  蕃狻〃ROLL-FORWARD 摊针怄龅  (PIT) 拟淠衮苔却驮却 DATALINK 牺
  (贴屮页 "recovery = no") 嘻闲知腕墨 DataLink_Reconcile_Pending
  (DRP) 雾梃· 剀枳驮却菡淼嘻闲知、铢倾 ROLL-FORWARD 摊 PIT 逆靴咂墨
  摹悄 DATALINK 垣、嘤靴圊砒 SET CONSTRAINTS 蒹虞娶衮闲知腕墨 DRP 你、
  锹仝如铪痨狞祁幔娶·
 
  12.10  嘁挝诜淘棚如莰堋鹇 (CLP) 喧恰托院恃骜砧岣艳楝篁
 
  铢俣澌群淘棚〃
 
       db2 add file manager <hostname> <portnum>
 
  莘俣澌嘻浠狞祁幔娶 db2dlcfg 探蓬· 孚狞祁幔娶嘻耄挝邱亩〃
 
       db2dlcfg -d <database name> -a <action> [-s <server host name>] [-p <port number>] -h
 
       抬你〃
         database name     闲泣骜砧栈嘻秦辎 (埔友软)·
         action            闲泣仝如嘻侬散 (埔友软)〃
                             LIST - 悄泣骜砧栈贴屮嘻驮却 DB2 File Managers·
                             ADD  - 浠炝蓑骜砧栈囚探嘻尢摹 DB2 File Manager·
         server host name  闲泣 DLFM 篁争戋堋幔娶声痨嘻配缳妾秦辎·
         port number       闲泣 DLFM 篁争戋堋幔娶嘻僬胬·
         -h                泣尕氅骜毓·摹瀑牙贴群蛸恸、抬破蛸恸摅淠莘土堠、
                           仍惘泣尕氅·
 
  梭邱〃
 
       db2dlcfg -d SAMPLE -a LIST
       db2dlcfg -d SAMPLE -a ADD -s myhost.mydomain.mycompany.com -p 10001
 
  蛹岩诜母摹侮嘻 DB2 File Manager 苊魉针、铢隧亩悄派娶庑如〃
 
  1.  圊砒 db2stop·
 
  2.  劓篇驮却嘻 datalink.cfg 铒犒篁 (喧像昼摹枪蕃祁)·
 
  3.  盆 db2dlcfg 狞祁幔娶浠炝篁争腮韦鹇嘻派挝、唆屿浠喧恰 datalink.cfg 篁· 
      隧肄茄嘻裙施浠炝篁争腮韦鹇·
 
  梭邱〃
 
       cat datalink.cfg
       1     myfs1.mydomain.mycompany.com 10001
       2     myfs2.mydomain.mycompany.com 10001
       4     myfs2.mydomain.mycompany.com 10001
       (铢蚊泗、苌牡远拟四魔·)
 
       mv datalink.cfg datalink.old
 
       db2dlcfg -d SAMPLE -a ADD -s myfs1.mydomain.mycompany.com -p 10001
       db2dlcfg -d SAMPLE -a ADD -s myfs2.mydomain.mycompany.com -p 10001
       db2dlcfg -d SAMPLE -a ADD -s nullfs.mydomain.mycompany.com -p 10001
       db2dlcfg -d SAMPLE -a ADD -s myfs4.mydomain.mycompany.com -p 10001
       (铢蚊泗、苌牡远岩熄垣·)
 
 
  13.0  侮欺 5.2 逆些驮卮绁嘻≈矢葳墨宪∽收
 
 
  欺彗嘻厢披骜毓曦亩悄 DB2 侮欺 5.0 矢葳墨宪琶捧却〃
 
  o   DB2 UDB Personal Edition 矢葳墨宪 侮欺 5.0
 
  o   DB2 UDB Enterprise Edition for OS/2 矢葳墨宪 侮欺 5.0
 
  o   DB2 UDB Enterprise Edition for Windows NT 矢葳墨宪 侮欺 5.0
 
  o   DB2 UDB Enterprise Edition - Extended for UNIX 侮欺 5.0
 
 
  13.1  DB2 塄新
 
  倾 DB2 琶捧你却枳 DB2 Application Developer's Kit 嘻俣澌·
  欺塄新堍倾却胎辍侮欺、签苫 IBM DB2 Personal Developer's Edition
  Version 5 滔 IBM DB2 Universal Developer's Edition Version 5
  塄新·菡胎辍侮欺惘损祁王 OS/2。Windows NT。Windows 95。滔
  Windows 98·
 
 
  13.2  佑琚区嬉
 
  欺彗嘻收浠曦菰强暑劬堑滔院七幔娶却·
 
 
  13.2.1  OS/2 菰腈叔
 
  倾 "腮韦鹇塄新腈叔" 阳姣你、王 DB2UDB Enterprise 滔 Workgroup
  Edition 嘻亩悄散淦朔苡骜毓筌孚收〃

 
       诜〃                  摊〃
       --------------------         ---------------------------------------------
       OS/2 Warp Server SMP         OS/2 Warp Server Advanced V4、芍 SMP 种吞
 
  倾 "诜谆塄新腈叔" 阳姣你、DB2 Client Application Enabler
  for OS/2。SDK。滔 Net.Data 木筌孚伉三嘻收〃
 
       诜〃                  摊〃
       --------------------         ---------------------------------------------
       OS/2 Warp Server SMP         OS/2 Warp Server Advanced V4、芍 SMP 种吞
 
 
  13.2.1.1  偏如嘻诜谆摊腮韦鹇葙葑吞
 
  喧拟友倾 Windows 95。Windows 98。托 OS/2 诜谆滔腮韦鹇逆怄
  损祁 IPX/SPX 唆葑详·菡辍葙谫拟贴· 曦 Novell 益硕逆靴、始辕
  刹鏊抬韵寝岩 IPX/SPX 葑毓潭贴僭煲裙·俾黝砒倾 Windows 95 滔
  Windows 98 排呶嘻 SPX I 煲裙、盆暖 OS/2 排呶嘻 SPX I 煲裙·宓
  Windows 95 托 Windows 98 潭俑葙谫针、破淠牙贴 SPX I 煲裙葙谫、
  叁倾 Windows 95 托 Windows 98 母、菡琵涯 SPX II 煲裙声痨掼乃
  难排呶·拟绱、宓 OS/2 潭俑 SPX I 葙谫针、拟排呶声痨掼乃难·
 
  Novell 气些七倾怃圊祁王 OS/2 SPX I 葙谫嘻声痨掼乃难排呶、损
  SPX I 葙谫嘻闲泣摹映·菡淼偏踱森倾惝厥湘邕哝嘻拧徐乃难针圊祈葙谫
  苘畔·邱为诶泖稀绗群怃圊争嘻庑轩、偏圃缳驺峥 Novell 骀俾
  SPD147611 嘻庑轩·
 
 
  13.2.2  NetFinity 排呶幔娶埔恻佤畔 - WINDOWS NT
 
  倾弄兹 DB2 UDB 针、"Netfinity 排呶幔娶" 韦侪幔娶衮爨 DB2
  UDB EEE for Windows NT 嘻区嬉·
 
  页魔衮 DB2 UDB EE 弄兹摊 DB2 UDB EEE、倾怃填区嬉 DB2 UDB EEE
  逆些、筌佤畔 "Netfinity 排呶幔娶" 韦侪幔娶·

 
 
  13.2.3  COMMUNICATIONS SERVER FOR WINDOWS NT - 腈友院七幔娶
 
  损祁 DB2 Connect Enterprise Edition for Windows NT 滔 IBM
  Communications Server for Windows NT (CS/NT) 针、蛹友探旨配缳
  妾宴骀 (SQL CANCEL)、诶腈友 DB2 UDB 侮欺 5.2 (托 DB2 UDB
  Extended Enterprise Edition for Windows NT) 暖 APAR 院七幔娶
  JR11529 暖 JR11170 for CS/NT·
 
 
  13.2.4  喧拧薮骜砧栈嘻损祁席衮 Client Application Enabler 弄兹
 
  蛹损祁 DB2 UDB V5.0 Client Application Enabler、宓损祁谡瘫你
  爬葙谫 Extended Enterprise Edition (EEE) 拧薮骜砧栈争梭针淠塄
  祈俾黝·
 
  韵欺蝰 DB2 Connect 滔 UDB 侮欺 5 呷蓑嘻谡瘫你爬、虽栖琵涯戋堋
  拧薮骜砧栈朔苡驮腈嘻戋堋劈卒·

 
  寝群、埔恻弄兹 DB2 诜谆倪卒仝如 UDB EEE 戋堋劈卒·王菡恸
  埔友吞嘻摹髓偏卒嘻牙泣邱亩〃

 
  o   输裙诶孳璺损祁谡瘫你爬唆仝如菡髓劈卒针谡瘫你爬摅淠蒺·

 
  o   肟軎骜砧栈嘻蕃枪滔擀弭偏盆诜淘棚如仝如、叁损祁席嘁挝
      ROLL-FORWARD 骜砧栈·倾 ROLL-FORWARD 哝怄圊祈朔苡蜚毹、
      驮盆埔恻倾诜谆闹散谆苘畔 db2 莰堋虽屿浠怃瘼·
 
      邱为输远尢摹枰彗龅却情远蛞彗龅、鞋 DB2 侮欺 2 诜谆
      拟排呶蕃枪滔擀弭淘棚·
 
  摹罪仍似、邱为诶泖友损祁谡瘫你爬唆戋堋 DB2 UDB EEE 腮韦鹇、
  鞋筌弄兹 Client Application Enabler·群俾黝嘻院七幔娶薏舷岩
  倾苌摹远 FixPak for DB2 UDB V5.0 你呷蓑〃
 
       AIX         U452196
       Solaris     U452197
       HP-UX       U452198
       OS/2        WR09003
       Windows NT  WR09004
       Windows 3.1 WR09006
 
  菡髓院七幔娶偏诜亩悄杲蛇你探诘〃
  "http://www.software.ibm.com/data/db2/db2tech"· 七睚嘻诜谆煲裙、
   木偏盆诜诜谆幔娶怩探诘、破蝰厢王 DB2 UDB 滔 DB2 Connect
   Enterprise Edition 侮欺 5.2·
 
  DB2 UDB FixPak 岩苒褙娶嘻·破辕琵涯 FixPaks 1。2。3。4。5。滔 6。
  盆暖蝰厢王 DB2 UDB EEE for Windows NT 滔 for Solaris 侮欺 5 嘻
  Client Application Enabler 你嘻院七幔娶·
 
 
  13.2.5  喧 Windows ODBC 嘻损祁席衮 Client Application Enabler 弄兹
 
  诜 Windows NT 滔 Windows 95 诜谆损祁 ODBC 筌祁幔娶针、始辕
  喧诶衮 DB2 Client Application Enabler 弄兹容院七幔娶怩煲裙
  WR09014 盆母·
 
  群院七幔娶偏诜亩悄杲蛇探诘〃"http://www.software.ibm.com/data/db2/db2tech"·
  七睚嘻诜谆煲裙、木偏盆诜诜谆幔娶怩探诘、破蝰厢王 DB2 UDB 滔
  DB2 Connect Enterprise Edition 侮欺 5.2·
 
 
  13.2.6  AIX 母 ADSM 喧嘻院七幔娶煲裙
 
  倾 AIX 拧薮骜砧栈艨韬你、倾损祁 ADSM 阼祁罾母闲知熄怄蕃枪逆靴、
  邱为擀弭骜砧栈、DB2 淠坡邗·
 
  抬株雾岩葙罾擀弭坡邗、赔 DB2 争梭你鏊 (菝蔌)、猬鏊毓丈页
  "SIG11sqloEDUCodeTrap"·群俾黝嘻尕暑逆绗岩区嬉 ADSM 诜谆院
  七幔娶怩 2.1.0.6 托收浠侮欺·
 
 
  13.2.7  CS/NT 枳王倾 Windows NT 母嘻胎怅阳睚贴排呶岩埔友嘻
 
  堍倾倾 Windows NT 母、损祁 DB2 Syncpoint Manager (SPM) 劈卒、
  滔 IBM Communications Server V5.01 for Windows NT (CS/NT) 针、
  却排呶损祁 SNA 嘻胎怅阳睚贴·

 
  SNA-based 侮欺嘻 SPM 岩亩悄塄新嘻摹蒎枪〃
 
  o   DB2 Connect Enterprise Edition for AIX
  o   DB2 Connect Enterprise Edition for OS/2
  o   DB2 Connect Enterprise Edition for Windows NT
  o   DB2 UDB Enterprise Edition for AIX
  o   DB2 UDB Enterprise Edition for OS/2
  o   DB2 UDB Enterprise Edition for Windows NT
  o   DB2 UDB Extended Enterprise Edition for AIX
  o   DB2 UDB Extended Enterprise Edition for Windows NT·
 
  SPM 云萋 DB2 UDB Client Application Enabler 萼绱 DB2 Connect EE、
  损祁 SPM 呷蓑嘻 SNA 胎怅阳睚贴骜砧像、唆囚探配缳妾骜砧·

  茄淼氢、配缳妾骜砧栈筌祁幔娶偏盆倾 DB2 UDB 腮韦鹇母囚探骜砧·
 
 
  13.2.7.1  圄卮 CS/NT 散页 Windows NT 韦侪幔娶
 
  区嬉 IBM Communications Server for Windows NT (CS/NT) 逆靴、筌
  衮破圄卮页 Windows NT 韦侪幔娶·邱群宓瘼鹇邛侬针、摅淠溶侬邛侬
  CS/NT·
 
  友圄卮 CS/NT 散页 Windows NT 韦侪幔娶、铢仝如亩悄淘棚·
  嵌蛸抬你逆摹〃
 
       csstart  -a
 
  盆邕菝艳楝篁溶侬邛侬 CS/NT、托席〃
 
       csstart -a c:\ibmcs\private\your.acg
 
  抬你 C:\IBMCS\PRIVATE\YOUR.ACG 岩诶友损祁嘻湘邕菝 CS/NT 艳楝篁秦辎·

 
  亩裙瘼鹇屿浠怃瘼针、衮盆驮友叔嘻艳楝篁溶侬邛侬 CS/NT·

 
 
  13.2.8  WINDOWS NT 暖 WINDOWS 95 母嘻 DCE 排呶
 
  DB2 Universal Database 滔 DB2 Connect 侮欺 5.2 呷蓑亩悄排呶〃
 
  o   Windows NT 暖 Windows 95 母嘻 Gradient DCE CDS
 
  o   Windows NT 母嘻 IBM DCE CDS
 
  木呷蓑魔胎远浠嘻 DLL〃
 
  o   db2dce.grd、锼祁王 Gradient DCE CDS
 
  o   dcedce.ibm、锼祁王 IBM DCE CDS
 
  拯疸邕菝垣、"db2dce.grd" 呢铒犒页 "db2dce.dll"·
 
  蕃狻〃DB2 品淠绁墨 "db2dce.dll"·邱为友损祁 IBM DCE CDS 嘻驺、
        诶埔恻衮 "dcedce.ibm" 铒犒页 "db2dce.dll"·
 
  劓魔损祁 APPC。IPX/SPX。NETBIOS 暖 TCP/IP 嘻堍囚排呶评、气些木
  呷蓑魔损祁 Named Pipes (NPIPE) 杲纣葑毓潭贴嘻 DCE 排呶·三亩
  悄畀梭嘻谡瘫蒹虞娶气些木偏盆牙贴峥苔却 DB_Communication_Protocol
  吞暖亩悄垣嘻 DCE 戊堑〃
 
       NPIPE;Computer_name;Instance_name
 
  孥茇骜毓、铢俣镥 Administration Guide 厢蜱 G·
 
 
| 13.2.9  喧嘻 WINDOWS NT 煲裙
 
  蛹友倾 Windows NT 母衮攀擘卮绁摊芍 DB2 嘻韵填嬉弭、鞋腈却
  Microsoft Service Pack 3 for Windows NT 4.0·
 
| 倾 Microsoft Service Pack 4 你、Windows NT 睚贴嘻卮鹳衮岖王
| 枰脬卮鹳嘻俾黝呢孱院七魔·
 
 
  13.2.10  SYSADM 宇嘻仵菝 (UNIX)
 
  倾 UNIX 嘻矢葳墨宪琶捧你、宓囟铫摊瘼亠像配黝针、淠仵菝损祁
  席属却倾骜砧栈戋堋幔娶艳楝篁你艳楝 SYSADM_GROUP 俣戆·邱为栖
  艳楝 SYSADM_GROUP 俣戆、鞋 SYSADM 妃苴邕菝页争梭疬却席嘻配友
  妃苴·

 
  矢葳墨宪琶捧倾俣澌争梭疬却席嘻配友妃苴针摹眩狺页苔却 SYSADM
  宇·拟绱、邱为诶却艳楝 SYSADM_GROUP 俣戆、鞋筌孚盆琶捧你嘻
  菡髓俣澌、唆牙诶呢贴屮倾骜砧栈戋堋幔娶艳楝篁你嘻 SYSADM 妃苴·

 
 
  13.3  抬破区嬉曦艳楝散淦
 
  欺彗嘻收浠曦区嬉曦艳楝散淦肄·
 
 
  13.3.1  艳楝 CS/NT 峥≈茄抒龅戋堋幔娶∽(SPM)
 
  邱为萼绱 SNA 损祁 SPM、鞋腈友 IBM Communications Server for
  Windows NT 侮欺 5.01·倾 DB2 侮欺 5.2、签萼绱 TCP/IP 排呶 SPM·
  "DB2 Connect Enterprise Edition 矢葳墨宪" 摹阵呃虞 SPM 区嬉·
 
  亩悄厢披嘻牙泣仵菝诶呢艳楝 CS/NT 峥 DB2 Connect·铢俣镥≈DB2
  Connect Enterprise Edition 矢葳墨宪∽摹阵苌 14 蔟·
 
  1.  SPM 友损祁嘻 LU、偏损祁≈CS SNA 彗龅艳楝/艳楝欺軎 LU 6.2∽
      贴屮倾 CS/NT·
 
  2.  LU 埔恻邛祁茄抒龅·偏隧亩悄派娶绠醛群气嘻〃
 
      a.  邛侬 CS/NT 艳楝幔娶·
 
      b.  掾势埔友嘻艳楝篁·
 
      c.  罹蛞群篁争·
 
      d.  洳掾友岂 SPM 损祁嘻 LU 贴屮·诶淠亦摊亩悄贴屮〃

 
               LOCAL_LU=(LU_NAME=SPMNAME
                         LU_ALIAS=SPMNAME
                         LU_SESSION_LIMIT=0
                         NAU_ADDRESS=0
                         ROUTE_TO_CLIENT=0
                         SYNCPOINT_SUPPORT=0)
 
      e.  衮 SYNCPOINT_SUPPORT=0 收页 SYNCPOINT_SUPPORT=1·
 
      f.  竺囚篁争·
 
  3.  浠艳楝·
 
  4.  佤畔 DB2·
 
  5.  睚贴 DB2COMM 圄卮垣琵涯 "APPC"·俣澌≈DB2 Connect EE 矢葳
      墨宪∽苌 24 蔟滔苌 39 蔟·
 
  6.  佤畔虽屿浠邛侬 CS/NT 彗龅·
 
      友群 LU 岩闪呢邛祁茄抒龅排呶、铢篝宴却 CS/NT SNA
      彗龅散淦嘻 "欺軎 LU6.2" 骜毓·群 LU 倾 "茄抒龅排呶" 牺
      你悄泣页 "Yes"·
 
  7.  收浠骜砧栈戋堋幔娶艳楝、菝贴 DIAGLEVEL 页 4〃
 
           update dbm cfg using diaglevel 4
 
      诶腈友邱群菝贴、倪卒佘篝狺偏卒嘻 SPM 肄猬鏊毓丈·

 
  8.  邛侬 DB2·
 
  9.  篝宴 "db2diag.log"·(宓艨韬戆 DB2PATH 滔 DB2INSTANCE
      菝贴页远杀邕菝垣针、偏倾 SQLLIB\DB2 气蜱你势摊群篁争)·
      邱为 SPM 呢恹沙邛侬、诶偏亦摊闲泣呢恹沙邛侬嘻毓丈·
 
      签铢蚊泗、宓 SPM 苌摹裙邛侬针、淠喧恰 "\sqllib\spmlog"
      气蜱·邱为群气蜱拟囚倾、托猬鏊毓丈牙泣 SPM 嘁挝邛侬、
      鞋诶埔恻屿浠篝宴 DB2 滔 CS/NT 艳楝·
 
  DB2 Connect Enterprise Edition 嘻矢葳墨宪琶捧衮莘收浠、盆琵
  涯群厢披骜毓·
 
 
  13.3.1.1  王损祁 SNA SPM 嘻厢披骜毓
 
  1.  倾 DB2 逆些邛侬 CS/NT、菡龅玄屿友·DB2 倾声醛破溶淖嘻邛侬
      幔施逆些、淠岖选 CS/NT 邛侬·寝群、邱为属却倾 DB2 逆些邛侬
      CS/NT、DB2 倾邛侬针淠醛弭雾梃·DB2 枰脬母岩倾岖选 CS/NT
      邛侬·喧诶圄卮 CS/NT 散页 Windows NT 韦侪幔娶·铢俣镥
      13.2.7, "CS/NT 枳王倾 Windows NT 母嘻胎怅阳睚贴排呶岩埔友嘻"·
      嘤靴、CS/NT 衮溶侬邛侬·
 
  2.  拯疸 "DB2 Connect Enterprise Edition 矢葳墨宪" 苌 22 蔟
      菝贴艨韬针、≈Microsoft 墁侬腮韦鹇∽岩≈墁侬莰堋 (TP)
      轳迤幔娶∽·寝群、倾损祁≈Microsoft 墁侬腮韦鹇∽针、拟腈
      友墁侬戋堋幔娶骜砧栈·

 
  DB2 Connect Enterprise Edition 嘻矢葳墨宪琶捧衮莘收浠、盆索
  墨群浠骜毓·
 
 
| 13.3.2  爨 AIX 侮欺 4.1.4 暖 4.1.5 母嘻 NIS 损祁席嘻俾黝
 
| 蕃狻〃 欺彗岩岂琵涯 AIX 侮欺 4.1.4 宇瘫嘻侮欺 5.2 侮欺蚊泗绥恸
|        收浠仍唆嘻·AIX 侮欺 4.1.5 宇瘫强些摅却卮绁·
 
| 倾 AIX 侮欺 4.1.5 托 4.1.5、宓损祁席仝如≈杲纣骜毓朔苡 (NIS)∽
| 唆葑如睿宋拧针、鞋岖摊淘棚如莰堋鹇摹绶针、摅淠拳摊毓丈
| DB21015E·
 
  摅群梭耐仍似、淘棚如莰堋鹇靴軎幔娶嘁挝蛘唆溶 NIS 配腮韦鹇
  嘻 DB2 争梭嘻损祁席 ID·友尕暑群俾黝〃

 
  1.  诜 NIS 配腮韦鹇劓篇损祁席 ID·
 
  2.  倾输摹蒎瘼鹇母嘻 "/etc/passwd" 篁争你、俅傺吞喧恰损祁席
      ID、睚贴倾孚篁争你、群损祁席 ID 岩腕倾 NIS magic cookie
      逆些·magic cookie 亦啬唆三〃
 
           :!::::::
 
 
  13.3.3  DB2CPIC.DLL - WINDOWS NT 暖 WINDOWS 95 母嘻瞿膨 SNA 瘼亠
          像幔娶睿
 
  却髓 SNA 耐朔苡呷蓑席虽拟仝如瞿膨 SNA 瘼亠像幔娶睿·菡偏卒
  淠爨摊损祁亩悄摹远托戆远塄新嘻嘘怕〃
 
  o   DB2 Universal Database (UDB) for Windows NT 侮欺 5
      (驮却院釉侮)·
 
  o   DB2 Connect Enterprise Edition for Windows NT 侮欺 5
 
  o   DB2 Connect Personal Edition 侮欺 5 (倾 Windows 95 托
      Windows NT 母仝如针)·
 
  呢呷蓑摹远浠嘻 DLL、频散 db2cpic2.dll、盆享倾菡髓艨韬你排呶
  瞿膨 SNA 瘼亠像幔娶睿·浠嘻 DLL 韵欺岩蝰厢王 Fixpak 16for
  DB2 Universal Database 侮欺 5 你·破曦韵填嘻 DLL db2cpic.dll
  肄茄、品拟绱破琵涯枳≈探砒裙友骜毓∽(cmesi()) 嘻趟频·
 
  +---------------------------------------------------------------------------+
  | 闲 4. 友损祁葬摹侮嘻 db2cpic.dll々                                        |
  +------------------------+-------------------------+------------------------+
  | 邱为苔却群 SNA 耐朔苡  | 倾 WINDOWS NT 损祁      | 倾 WINDOWS 95 损祁     |
  +------------------------+-------------------------+------------------------+
  | IBM Communications     | db2cpic2.dll (浠)       | db2cpic.dll (鳟)       |
  | Server for Windows NT  |                         |                        |
  +------------------------+-------------------------+------------------------+
  | IBM Personal           | db2cpic2.dll            | db2cpic.dll            |
  | Communications for     |                         |                        |
  | Windows (铢俣镥亩悄    |                         |                        |
  | 蕃狻)                  |                         |                        |
  +------------------------+-------------------------+------------------------+
  | Microsoft SNA Server   | db2cpic.dll             | db2cpic.dll            |
  +------------------------+-------------------------+------------------------+
  | Wall Data RUMBA (蹁却  | db2cpic2.dll            | db2cpic2.dll           |
  | 蝰厢王 DB2 Connect     |                         |                        |
  | Personal Edition 嘻    |                         |                        |
  | 痨琴 SNA 排呶)         |                         |                        |
  |                        |                         |                        |
  +------------------------+-------------------------+------------------------+
 
  邱为 DB2 嘁挝绁墨 db2cpic2.dll、诶摅偏盆倾区嬉破嘻气蜱你仝如亩悄
  淘棚〃
 
       copy db2cpic2.dll db2cpic2.bak
     copy db2cpic.dll db2cpic2.dll
 
  菡淼淠损 db2cpic2.dll 滔 db2cpic.dll 肄茄·
 
  蕃狻〃邱为诶友倾 Windows 95 母损祁瞿膨瘼亠像排呶暖 DB2 UDB
        侮欺 5.0、喧诶损祁 IBM Personal Communications (PComm)
        for Windows 95 侮欺 4.2 (湘侮欺 4.1)·铢衮 db2cpic.dll
        铒犒页 db2cpic.bak、虽衮 db2cpic2.dll 铒犒页 db2cpic.dll·
        菡淠损 db2cpic.dll 曦 db2cpic2.dll 肄茄·
 
 
  13.3.4  祁王 Windows NT 嘻 DB2NTMEMSIZE 菝贴篁戆
 
  倾≈DB2 UDB Extended Enterprise Edition for Windows NT 矢葳墨
  宪琶捧∽你、"谡瘫 DB2 艨韬" 摹牌却蜚毹嘻蒹虞〃
  "DB2NTMEMSIZE 岩祁唆弭咝 DB2 橇祁卮鹳俅阳嘻母宇"·
 
  Windows NT 腈友倾 DLL 啬填菝贴针像昼驮却橇祁卮鹳俅阳、盆像
  侵莰堋嘻软蛇肄刭、虽呷蓑浠嘻菝贴篁戆 DB2NTMEMSIZE、盆云萋
  损祁席倾埔友针倾 Windows NT 母弭咝 DB2 邕菝垣·枳王乃蒎枪雾斡、
  邕菝垣筌呢送佘·
 
  盆亩岩卮鹳俅阳暖抬邕菝乃难嘻悄泣〃
 
 
      卮鹳俅阳            邕菝乃难         弭咝蛸恸
      ----------------------------------------------------------------------------
      骜砧栈狰爬幔娶        16777216 (16MB)  DBMS:[软镊苴戆]
      MPP FCM 盥铐俅        33554432 (32MB)  FCM:[软镊苴戆]
      骜砧栈戋堋 GUI        33554432 (32MB)  DBAT:[软镊苴戆]
      缫麾 DARI             16777216 (16MB)  APLD:[软镊苴戆]
 
  偏盆祁 ':' 拧缫弭咝蛸恸、唆弭咝摹远盆母嘻俅阳·

 
  梭邱、友宇瘫 DBMS 页 (乃尹) 256K、暖宇瘫 FCM 页 (乃尹) 64MB、
  铢损祁〃
 
      db2set DB2NTMEMSIZE=DBMS:256000:FCM:64000000
 
 
  13.4  谡瘫你爬嘻 SNAPSHOT 轳迤幔娶
 
  倾 OS/2、宓诶衮 snapshot 轳迤幔娶嘻真卒璺拾嚯域屿浠铪痨页乓绀
  难针、谡瘫你爬偏蒺仍拟砒堍嵌若蜚毹毓丈·

 
  宓诶枳骜砧栈戊堑托抬嵌摹耐戊堑仝如 snapshot 轳迤幔娶针、嘁挝
  仝如侬散唆恃。收。托纱劓群骜砧栈戊堑 (邱争梭托骜砧栈)·

  (群评、邱为诶轳迤拧薮骜砧栈朔苡、鞋嘁挝擀浠拧薮骜砧栈戊堑嘻
  篝狺嚯域·) 梭邱、邱为诶友劓篇骜砧栈 A 嘻争梭、鞋嘁挝轳迤骜
  砧栈 A·拟绱、邱为诶品轳迤争梭、鞋偏恃骜砧栈 A·

 
  友佤畔枳争梭 (琵涯抬耐戊堑) 嘻驮却轳迤、铢诜孚争梭嘻髌堍劈卒
  闲蛸探 "佤畔驮却轳迤"·诶筌孚佤畔争梭嘻轳迤、盆睚贴淠腕真
  卒轳迤幔娶驮像昼嘻抢蒎髡贴·

 
 
  13.5  诜 WEB 囚探 DB2 骜砧
 
  王损祁 Java 曦 DB2 (争梭嘻 JDBC) 嘻骜毓、铢俣镥杲脬杲纣母
  嘻亩悄杲蛇〃

 
       http://www.software.ibm.com/data/db2/java/
 
 
  13.6  倾 RS/6000 SP 母菝贴杲纣肄俣戆
 
  亩悄骜毓筌浠炝容 "IBM DB2 Universal Database Extended
  Enterprise Edition for AIX 矢葳墨宪" 摹阵苌 6 蔟 "区嬉 DB2
  Universal Database Extended Enterprise Edition" 你抒 1
  "漤蕃区嬉" 岣盛嘻友堇你·群友堇氅忘邱若睚贴杲纣肄俣戆岩菝
  贴倾驮却 SP 彗龅母·
 
  倾牙贴 "诶偏盆损祁 no -a 淘棚唆篝狺杲纣俣戆嘻堍如菝贴" 嘻蕃
  狻逆靴、浠炝亩悄阳姣〃
 
  母虞垣岩俣戆嘻薏难垣·邱为诶呢菝贴杲纣肄俣戆页绀乃垣、鞋
  拟友衮俣戆菝贴页母虞绀难垣·

 
  倾盆 "蛹友篝狺 css0 嘻艳楝" 页怃螭嘻苹耐靴域、浠炝亩悄阳姣〃
 
  邱为诶拟损祁 /tftpboot/tuning/cst 篁唆铪痨朔苡嘻真卒、鞋筌损
  祁亩悄派挝唆菝贴杲纣肄俣戆·

 
 
  13.7  倾拧薮骜砧栈艨韬你菝贴 CCA 滔谡瘫你爬
  (DB2 UNIVERSAL DATABASE EXTENDED ENTERPRISE EDITION FOR AIX)
 
  亩悄骜毓筌浠炝容 "IBM DB2 Universal Database Extended
  Enterprise Edition for AIX 矢葳墨宪" 琶捧苌 6 蔟 "区嬉 DB2
  Universal Database Extended Enterprise Edition" 你抒 8
  "菝贴诜谆艳楝牒煞幔娶滔谡瘫你爬"·
 
  僮王真卒扔庳、喧诶薏秋拟友倾≈戋堋腮韦鹇∽母菝贴 discover=SEARCH、
  群≈戋堋腮韦鹇∽软王配友气蜱彗龅母托谡瘫你爬彗龅母·

 
  蹁却抬破派娶偏倾拟茄潭铪幔娶彗龅逆怄拧厥诜谆友叔·诶偏盆损
  祁诜谆艳楝牒煞幔娶 IMPORT/EXPORT 托琶侬罹气酞戆唆拧厥闹散
  幼荩·贫摹远派挝岩损祁 LoadLeveler 塄新唆萼葑氢拧厥诜谆友
  叔·

 
  邱为彗龅母属却仝如≈戋堋腮韦鹇∽、鞋诶拟偏盆损祁谡瘫你爬嘻
 ≈腮韦鹇葑详菝弭∽劈卒、倾拧薮骜砧栈艨韬你仝如肟軎彗龅区嬉
  (骜砧栈拧薮俅腮韦鹇)·

 
  损祁 TCP/IP 葑毓潭贴排呶谪啄·
 
  倾拧薮骜砧栈艨韬你拟排呶 IPX/SPX 篁争腮韦鹇贴蛇·

 
 
  13.8  诜鳟侮苊魉 (UNIX)
 
  倾 "骜砧栈偏盆苊魉" 阳姣你、咪邙虞埔恻佤畔 DB2 逆靴倪卒
  漤蕃苊魉争梭·菡岩蜚毹嘻·友恹沙仝如 "db2ckmig" 闹苔、埔恻
  仝如骜砧栈戋堋幔娶·倾肄茄阳姣你、铢收亩悄淘棚〃
 
       DB2DIR/instance/db2ckmig -e -a 0 -1 INSTHOME/migration.log
 
  醛页〃
 
       DB2DIR/bin/db2ckmig -e -a 0 -l INSTHOME/migration.log
 
  倾 "苊魉 DB2 争梭" 阳姣你、泣嘻 "db2imigr" 淘棚耄挝岩盆
  "-u fencedID" 散页偏蛸祁嘻俣戆·宓区嬉 DB2 Client Application
  Enabler 逆靴、摅拟腈友 -u 蛸恸¨拟绱、枳抬破驮却 DB2 塄新仍似、
  -u 蛸恸岩埔友嘻·
 
 
  13.9  DB2 SNMP 裙蓬堋幔娶
 
  鳇网杲纣戋堋葑毓潭贴 (SNMP) 塄新琵涯 IBM NetView for AIX 滔
  IBM NetView for OS/2·DB2 萼绱 DB2 SNMP 裙蓬堋幔娶、呷蓑枳
  SNMP 戋堋塄新嘻排呶、菡远裙蓬堋幔娶索墨页 DB2 Server 嘻镊堑
  逆摹·SNMP 戋堋塄新邱 NetView、诈萋怩你戋堋朔苡嘻菰帻镊堑·
  DB2 SNMP 裙蓬堋幔娶诈萋琦戋堋抬破 SNMP 炭戋堋骜溷摹淼唆戋堋
  DB2 腮韦鹇·

 
  王损祁 SNMP 裙蓬堋幔娶嘻菰腈叔邱亩〃
 
  o   倾 OS/2 母〃
      -   TCP/IP 侮欺 2.0 盆母驮呷蓑嘻 DPI 1.1 排呶、托
      -   蝰 OS/2 Warp 摹啬区嬉嘻 Warp Connect 驮呷蓑嘻 DPI 2.0 排呶、托
      -   IBM SystemView Agent 驮呷蓑嘻 DPI 2.0 排呶·
  o   倾 Windows NT 托 AIX 母〃
      -   IBM SystemView Agent 驮呷蓑嘻 DPI 2.0 排呶·
 
 
  13.10  损祁 CCA 艳楝诜谆摊 DB2 腮韦鹇嘻葑详
 
  页魔损祁 IBM Communications Server SNA API Client for Windows
  NT 托 Windows 95 七睚葙谫、诶埔恻倾邛侬嵌若友萼绱 APPC 葙谫嘻
  GUI 筌祁幔娶逆些、强邛侬 APING 筌祁幔娶·菡 GUI 筌祁幔娶琵
  涯≈诜谆艳楝牒煞幔娶∽。≈谡瘫你爬∽、盆暖嵌若嘻 ODBC GUI
  筌祁幔娶·
 
 
  13.11  戋堋滔损祁 OS/2 损祁席菝贴篁戋堋
 
  倾 "损祁席菝贴篁戋堋葑如睿" 阳姣涅、闲知 7 你嘻摹远蕃狻却恃、
  群蕃狻岩王损祁席 ID 滔葑如睿嘻魉咝垣·闲 7. "邕菝损祁席 ID
  滔葑如睿" 嘻蕃狻邙虞邱亩〃
 
       邱为诶嘻傧榨栖砒堍倾群悄泣你、鞋仵菝损祁 USERID 滔 PASSWORD·
       邱为坡邗、铢俣镥 README 篁·
 
  群蕃狻呢拟锹却真、筌土堠破·
 
 
  13.12  倾 SOLARIS 母枳王 EEE 嘻 ADSM 诜谆菝弭 - 损祁 DB2PROFILE
 
  菝贴 ADSM Client for DB2 UDB Extended Enterprise Edition for
  Solaris 针、DSMI_DIR。DSMI_CONFIG。滔 DSMI_LOG ADSM 艨韬戆、
  筌菝贴倾 db2profile 你·邱为菡髓戆品损祁 .profile 托 .kshrc
  憔砒、鞋拟卒损祁王拧薮骜砧栈艨韬你嘻输摹远彗龅·倾 Solaris 母
  嘻 ADSM 诜谆埔恻页侮欺 2.1.0.8 托收浠侮·
 
 
  13.13  诜 DB2 FOR OS/390 侮欺 5 葙谫摊 DB2 UNIVERSAL DATABASE 侮欺 5
 
  亩悄骜毓筌浠炝容氅忘邱若损祁 DB2 闹散谆散页配缳妾筌祁幔娶腮
  韦鹇嘻蔟彗、滔悄泣 DRDA 筌祁幔娶腮韦鹇埔友 PTF 嘻蔟彗〃
 
       邱为友诜 DB2 for OS/390 侮欺 5 葙谫摊 DB2 Universal
       Database 侮欺 5、铢趴祁 DB2 for OS/390 APAR PQ07537
       嘻院七幔娶·

 
 
  13.14  倾 WINDOWS NT 腮韦鹇母艳楝 NETBIOS
 
  倾 Windows NT 母嘻 NetBIOS 拟卒七睚谫拳乃王谫拳盥铐俅嘻骜砧·
  拟绱、诶偏损祁 DB2 圄卮垣 db2nbrecvbuffsize 唆涩韦群俾黝·
 
  诶埔恻衮腮韦鹇母嘻谫拳盥铐俅菝贴页乃王诜谆惝厥嘻薏乃骜砧庳·
  邕菝 RQRIOBLK 乃难岩 32767 软镊苴、叁邕菝腮韦鹇 "谫拳盥铐俅乃
  难" 岩 4096 软镊苴·倾邛侬 DB2 逆些、铢圊砒亩悄淘棚〃
 
       db2set db2nbrecvbuffsize=32768 -g
 
  群淘棚抢傺吞菝贴腮韦鹇嘻谫拳盥铐俅乃难·
 
 
  13.15  橇祁卮鹳软蛇 - WINDOWS NT 托 WINDOWS 95
 
  盆 Windows NT 滔 Windows 95 仍似、倾≈矢葳墨宪∽琶捧嘻 "戋堋
  争梭" 阳姣你、趴祁亩悄院恃骜毓·
 
  邕菝骜砧栈戋堋幔娶橇祁卮鹳软蛇邱骗〃Windows NT 岩 x'20010000'、
  Windows 95 岩 x'90000000'·邱为圊祈橇祁卮鹳软蛇铐殷、鞋偏盆院
  恃菡远垣、唆诎鱼骜砧栈戋堋幔娶争梭衮破嘻橇祁卮鹳刭弭倾拟茄嘻
  软蛇母·损祁 DB2DBMSADDR 圄卮菝贴篁戆唆牙贴软蛇垣、抬畀挢邱亩〃
  Windows NT 岩 x'20010000' 摊 x'B0000000'、Windows 95 岩
  x'80000000' 摊 x'B00000000'、盆 x'4000000' 散页炝庳·梭邱、倾
  Windows 95 母孳孳菡髓垣〃x'840000000'。x'88000000'。x'8C000000'...
 
  DB2DBMSADDR 嘻垣岩牟您庑软知娶、些域属却 0x、仍赔偏损祁 db2set
  菝贴篁圄卮淘棚唆菝贴·
 
  梭邱、蛹友衮 DB2DBMSADDR 菝贴页 x'84000000'、铢损祁亩悄淘棚〃
 
       db2set DB2DBMSADDR=84000000
 
 
  13.16  仝如 DB2 JDBC APPLET 腮韦鹇宓散 WINDOWS NT 韦侪幔娶
 
  倾砗黝 "仝如 Java 筌祁幔娶" - "Java Applets" 逆亩、≈矢葳墨宪∽
  滔≈戋堋墨宪∽胎欺琶捧嘻邙虞邱亩〃
 
       友仝如 applets、铢仝如亩悄侬散〃
 
       1. 倾 Web 腮韦鹇母蛴墨亩悄淘棚唆邛侬 DB2 JDBC applet 腮韦鹇〃
 
         db2jstrt portno
 
         抬你 portno 岩诶牙贴倾 DB2Applt.java 篁争你嘻栖损祁 TCP/IP 僬胬·

 
  群骜毓呢绱针、铢俣镥邱亩〃
 
  DB2 JDBC Applet Server 堍倾偏盆邛侬页 Windows NT 韦侪幔娶、倾
  破偏盆诜谡瘫坪嘻韦侪幔娶你莘损祁逆些、埔恻强圄卮页韦侪幔娶·

 
  友圄卮群韦侪幔娶、铢倾圄墨页戋堋席针仝如亩悄淘棚〃

 
       db2regjdbc  i
 
  友圄卮韦侪幔娶盆种贴损祁席 ID 仝如、铢仝如〃
 
       db2regjdbc i [userid] [password]
 
  友劓篇韦侪幔娶、铢仝如〃
 
       db2regjdbc u
 
  摹瀑圄卮魔韦侪幔娶、破摅偏盆诜谡瘫坪嘻韦侪幔娶你莘邛侬滔佤畔〃

 
  1.  怃邛≈谡瘫坪∽
  2.  押摹亩≈韦侪幔娶∽
  3.  砗忘 "DB2 JDBC Applet Server"·
  4.  倾淘棚软你蛴墨僬胬 (诶倾 DB2Applt.java 篁争你牙贴嘻烃栖
      莘损祁嘻 TCP/IP 僬胬)·押摹亩邛侬·
 
  韦侪幔娶木偏盆菝贴页溶侬邛侬滔佤畔·
 
 
  13.17  探诘骜毓
 
 
  13.17.1  罾母尕氅
 
  配黝 "SQL 尕氅" 尕 SQL 蒹虞娶嘻耄挝、群配黝倾 UNIX 形散淦
  朔苡母嘁挝损祁·
 
 
  13.17.2  DB2 龌阵
 
  倾琵芍 DB2 阵嘻肄骜毓逆闲知偷軎、苌摹远蕃狻你嘻耄似杀求
  悄泣筌琵涯亩悄圄蜱〃

 
       耄似                     杀求
       狮牌                   A
       攀牌                     J
       雩牌                     K
       鳇你牌                 C
       繇你牌                 T
 
 
  13.17.3  悄峭 PostScript 阵
 
  邱为诶伲秋峭砒琶捧、偏衮 PostScript 侮欺尕筇翥虽悄峭·
 
  蕃狻〃牙贴诶友悄峭嘻篁争逆声痨纣绽秦辎·
 
  倾 OS/2 滔 Windows 仆坪母〃
 
  1.  铒犒呢筇翥嘻 PostScript 篁摊朔苡母嘻帻轺·菡髓篁争嘻佾篁
      秦岩 .exe、破辕软王 x:\doc\language\books\ps 气蜱、抬你
      x: 岩蓬闲 CD-ROM 羌轺瘼嘻求凄、language 岩蓬闲耄似嘻麂求
      镊傧睿 (梭邱、EN 蓬闲 English)·
 
  2.  尕筇翥诶友悄峭逆阵驮枳筌嘻篁争·群摹抒驮塄祈嘻岣为岩
      摹远偏悄峭嘻 PostScript 篁、抬佾篁秦页 .psz·
 
  3.  睚贴邕菝峭闲瘼岩却卒陌悄峭煲裙 1 (托茄岖煲裙) 篁争嘻
      PostScript 峭闲瘼·

 
  4.  诜淘棚如蛴墨亩悄淘棚〃
 
           print filename.psz
 
  倾 UNIX-based 仆坪〃
 
  1.  嬉绁 CD-ROM·俣澌≈矢葳墨宪∽琶捧你嘻幔施唆嬉绁 CD-ROM·
 
  2.  咝摊 CD-ROM 母嘻 /cdrom/doc/%L/ps 气蜱、抬你 /cdrom 岩
      CD-ROM 嘻嬉绁龅、%L 岩驮友耄似艨韬嘻秦辎·孚琶捧衮区嬉倾
      强些呷摊嘻气蜱你、虽损祁盆 .ps.Z 散页岣盛嘻篁秦·
 
  3.  损祁亩悄淘棚唆尕筇翥虽悄峭诶腈友嘻琶捧〃
 
      o   倾 AIX 母〃
 
               zcat filename | qprt -P PSPrinter_queue
 
      o   倾 HP-UX。Solaris。托 SCO UnixWare 7 母〃
 
               zcat filename | lp -d PSPrinter_queue
 
      o   倾 Silicon Graphics IRIX 滔 SINIX 母〃
 
              zcat < filename | lp -d PSPrinter_queue
 
 
      抬你 filename 岩呢筇翥 PostScript 篁嘻声痨纣绽秦辎滔佾篁秦、
      PSprinter_queue 岩 PostScript 峭闲瘼蕊悄嘻秦辎·
 
      梭邱、友倾 AIX 母悄峭恿牌侮嘻 UNIX 矢葳墨宪、偏损祁亩悄淘棚〃

 
           zcat /cdrom/doc/en/ps/db2ixe50.ps.Z | qprt -P ps1
 
 
  13.17.4  篝狺罾母阵
 
  欺塄新驮厢嘻琶捧岩饩牌求砗泣耄似 (HTML) 菰欺知娶·菰欺知娶偏
  诶洳掾托鲞骜毓、虽呷蓑曦肄骜毓嘻饩牌求岣·木偏盆损诶
  倾杲谆橇祁篁争栈诘收诈网·

 
  诶偏盆损祁嵌若蜃泅 HTML 侮欺 3.2 萁知嘻鲞鹇唆篝狺罾母阵·
 
  友篝狺罾母阵〃
 
  o   邱为仝如 DB2 戋堋闹苔、鞋损祁≈骜毓你爬∽·
 
  o   损祁 Web 鲞鹇嘻怃邛鳟篁劈卒·诶怃邛嘻杲喻琵芍 DB2 阵
      嘻氅忘滔岣〃

 
      -   倾 UNIX-based 仆坪母、怃邛亩悄杲喻〃
 
               file:/INSTHOME/sqllib/doc/%L/html/index.htm
 
          抬你 %L 岩耄似艨韬秦辎·
                __
 
      -   倾抬破仆坪母、怃邛亩悄杲喻〃
 
               sqllib\doc\html\index.htm
 
          群纣绽岩软王区嬉 DB2 嘻轹轺瘼母·
 
          诶木偏盆押胎亩≈DB2 罾母阵鞒∽璺泣唆怃邛群杲喻·拯疸
          诶损祁嘻朔苡、群璺泣岩倾配友塄新骜砧设托 Windows 怃填
          劈卒闲母·
 
          蕃狻〃品却宓诶栖区嬉≈骜毓你爬∽针、倪卒损祁≈DB2
                罾母阵∽璺泣·

 
 
  13.17.5  菝贴牌堑腮韦鹇
 
  拯疸邕菝、DB2 骜毓淠区嬉倾欺軎朔苡母·菡闲泣腈友囚探 DB2 骜毓
  嘻输摹远末、葭埔恻区嬉肄茄篁争·友损 DB2 骜毓竺囚倾尢摹软弭、
  铢损祁亩悄牙泣〃 
 
  1.  诜欺軎朔苡母嘻 \sqllib\doc\html 铒犒驮却篁争滔裙气蜱摊 Web
      腮韦鹇·输摹欺阵葭却破溶淖嘻裙气蜱、唆琵芍楝醛群阵嘻驮却
      埔友 HTML 滔 GIF 篁争·睚贴气蜱岣楝昴呀拟·

 
  2.  艳楝 web 腮韦鹇、盆享倾浠软弭掾势篁争·邱腈骜毓、铢俣镥
     ≈倾 Web 腮韦鹇母菝贴 DB2 罾母牌堑∽、抬杲蛇邱亩〃
 
           http://www.software.ibm.com/data/pubs/papers/db2html.html
 
  3.  邱为诶损祁 Java 侮嘻骜毓你爬、偏页驮却 HTML 篁争牙贴僮欺 URL·
      诶筌损祁群 URL 唆探诘阵尢·

 
  4.  摹瀑诶卒佘篝狺阵篁争、苫偏盆阵砗泣讦亦嘻配黝、邱〃

 
      o   阵尢
      o   讦祁阵嘻气蜱
      o   讦亦嘻牌蔟、邱 ALTER TABLE 配黝
      o   洳掾闲知·
 
  王菝贴洳掾嘻骜毓、铢俣镥≈浠种吞孽苷∽摹阵·
 
 
  13.17.6  洳掾罾母阵
 
  友倾 HTML 阵你洳掾骜毓、偏仝如亩悄侬散〃
 
  o   倾 HTML 阵嵌摹喻偷軎、押摹亩≈洳掾 DB2 阵∽·损祁洳掾
      闲知唆掾势种贴配黝·
 
  o   倾 HTML 阵嵌摹喻偷軎押摹亩≈啄趴∽·损祁≈啄趴∽唆掾势
      阵你嘻种贴配黝·
 
  o   泣 HTML 阵嘻气蜱托啄趴、嘤靴损祁 Web 鲞鹇嘻掾势劈卒
      唆掾势阵你嘻种贴配黝·
 
  o   损祁 Web 鲞鹇嘻阵劈卒、矢葳沁摊衍种贴配黝·
 
  o   损祁骜毓你爬嘻洳掾劈卒唆掾势种贴配黝·

 
 
  13.18  MICROSOFT INTERNET EXPLORER 4.0 HTTP 1.1 菝贴
 
  气些、Internet Explorer 嘻邕菝菝贴淠曦 DB2 洳掾腮韦鹇铐殷·
  尕暑派娶岩诜 Internet Explorer 嘻庑怅蛸恸你佤祁 HTTP 1.1 菝
  贴垣钮蛸怔 (倾偏囚探牌堑嘻输远诜谆母仝如群侬散)· 铢蚊泗、
  寝页 Internet Explorer 嘻宇瘫、驮盆菡淼嘻莰堋腈友衮朔苡屿浠
  怃瘼、倪卒祈真·
 
  1.  蛸探≈篝狺∽劈卒闲你嘻≈Internet 蛸恸∽·
 
  2.  蛸探≈庑怅∽砗·诶淠亦摊芍却钮蛸怔嘻俅阳悄泣·
 
  3.  倾≈HTTP 1.1 菝贴垣∽俅阳你垡劓≈萼绱 proxy 葙谫损祁 HTTP
      1.1∽暖≈损祁 HTTP 1.1∽钮蛸怔·
 
  4.  蛸探≈睚贴∽·
 
  5.  蒺蒺 Windows 虽屿浠怃瘼、盆浠菝贴垣祈真·
 
 
  13.19  王损祁谡瘫你爬诜肟軎戋堋龌怩嘻蚊泗绥恸
 
  倾情远彗龅母区嬉 DB2 UDB EEE for Windows NT 逆靴、区嬉莰堋品
  艳楝 "争梭疬却彗龅" 醛页潭铪幔娶彗龅、盆享诜诜谆瘼鹇母葑详·
  友损祁谡瘫你爬诜肟軎戋堋龌怩、诶埔恻倾输摹远彗龅母邛祁葑详·
  绠醛群气嘻嘻派挝邱亩〃
 
  1.  倾输摹蒎瘼鹇母像昼 TCP/IP 葙谫僬·梭邱、仵菝输摹蒎瘼鹇母
      偏损祁葙谫僬 4000·

 
  2.  收浠争梭艳楝篁、醛枳抢蒎彗龅损祁群僬胬·倾争梭疬却彗龅
      母、躏墨〃
 
           DB2 update dbm cfg using svcename 4000
 
  3.  艳楝输摹远彗龅唆谫炭 TCP/IP·倾争梭疬却彗龅
      母、躏墨〃
 
           rah "db2set db2comm=TCPIP"
 
  输摹远彗龅倾屿浠邛侬逆靴、衮谫炭墨僬 TCP/IP 葙谫·
 
 
  14.0  REPLICATION 牙胁曦俣澌
 
 
  14.1  浠排呶嘻仆坪
 
  IBM Replication 岩摹燥损祁鳇尢嘻溶侬脓铒犒闹苔怩、卒佘诜唆溷
  式煅骜砧摊气砗母·骜砧偏盆倾亩悄软弭逆怄铒犒〃
 
  o   倾 DB2 for MVS。DB2 for VSE & VM。DB2 Universal Database。
      滔 DB2 for OS/400 骜砧栈腮韦鹇逆怄
 
  o   倾 MVS。VM。VSE。OS/400。AIX。HP-UX。SCO UnixWare 7。
      OS/2。Windows NT。Windows 95。Windows 98。滔 Solaris 岖
      散淦艨韬亩纡仆坪铒犒

 
  o   倾湘 DB2 唆溷滔气砗母铒犒、邱 Oracle。Sybase。Informix。
      滔 Microsoft SQLServer (萼绱 DB2 DataJoiner)·
 
 
  14.2  浠毓丈
 
  倾苌 21 蔟≈IBM 式煅毓丈∽你、蜍榕魔趴祁幔娶嘻胎远毓丈〃

 
       ASN1054S
       趴祁幔娶势拟摊唆溷疬却席 "<src_ownr>"。唆溷闲知 "<src_tbl>"。
       滔唆溷渫堠闲宇贴镊 "<src_view_qual>" 嘻圄卮骜毓·
 
       氅忘
       唆溷闲知圄卮拟七睚托拟声痨·
 
       损祁席沁筌
       陲酃圄卮虽屿伉·虽睚贴圄卮骜毓岩倾圄卮闲知滔纱劓谡瘫闲知你·
 
 
       ASN1055S
       趴祁幔娶势拟摊唆溷疬却席 "<src_ownr>"。唆溷闲知 "<src_tbl>"。
       唆溷渫堠闲宇贴镊 "<src_view_qual>"。气砗疬却席 "<tgt_ownr>"。
       滔气砗闲知 "<tgt_tbl>" 嘻纱劓谡瘫骜毓·
 
       氅忘
       唆溷闲知圄卮拟七睚·
 
       损祁席沁筌
       陲酃贴哝式煅虽屿伉·
 
 
  14.3  DB2 UDB 侮欺 5.2 嘻鍪探幔娶排呶逆 LONG VARCHAR
 
  DB2 UDB 侮欺 5.2 嘻鍪探幔娶堍倾苔却排呶 LONG VARCHAR 骜砧形
  嘻卒陌·浠嘻 Long Field Manager 羡卮蜱呢头鳃、菡髓羡卮蜱琵芍
  倾鍪探枳 LONG VARCHAR 牺驮伉嘻收针驮腈嘻骜毓·

 
  枳腈友浠鍪探劈卒嘻 DB2 UDB 侮欺 5 损祁席仍似、却呷蓑摹远蛸恸
  唆浠炝厢披耐苹摊 ALTER TABLE 蒹虞娶·CREATE TABLE 耄挝拟·
 
  友沙祁浠 LONG VARCHAR 排呶嘻秋莰、埔恻倾 ALTER TABLE 蒹虞娶母
  牙贴 DATA CAPTURE CHANGES INCLUDE LONGVAR COLUMNS 耐苹·
  仝如群 DDL 蒹虞娶针、SYSCAT.TABLES 你嘻 DATA CAPTURE CHANGES
  岩菝贴页 "L"·输宓芍却 INCLUDE LONGVAR 蛸恸悄嘻僮欺闲知收浠针、
  鍪探幔娶摅淠煅墨暖探 Long Field Manager 羡卮蜱·菡髓卮蜱茄
  针琵涯牺嘻栖收浠闲知涅诈滔收浠靴闲知涅诈·

 
  邱为友佤祁浠 LONG VARCHAR 排呶、埔恻倾 ALTER TABLE 蒹虞娶母
  牙贴锼宓嘻 DATA CAPTURE CHANGES 垣·梭邱、诶筌孚品牙贴 "YES"
  托 "NONE" 仍拟厢讧抬破耐苹·
 
  友圄卮 LONG VARCHAR 牺、铢诜谡瘫你爬仝如亩悄侬散〃
 
  1.  倾 "贴屮页式煅唆溷" 狺岌你掾势 "偏祁牺" 派怔·

 
  2.  蛸探 LONG VARCHAR 牺·
 
  宇瘫〃枳王 DELETE 散淦仍似 (IBMSNAP_OPERATION="D")、LONG VARCHAR
        牺垣页 NULL·
 
 
| 14.4  DATAJOINER REPLICATION ADMINISTRATION TOOL README
 
| 弦损祁 DB2 DataJoiner Replication Administration Tool, 侮欺 2.1.1
| (DJRA)·
 
| 欺彗芍却诶区嬉 DJRA 针驮腈嘻骜毓〃
 
| o   王 DJRA
 
| o   区嬉 DJRA
 
| 王 DJRA
 
| DJRA 锼祁王苌摹裙散页 DB2 UDB FixPak 7 for Windows 95。Windows
| 98 暖 Windows NT 你嘻畀梭筌祁幔娶针·破品锼祁王菡髓散淦朔苡·
| DJRA 呷蓑式煅骜砧嘻戋堋酞戆·盆腈友 DataPropagator Relational
| for MVS 侮欺 5 暖 DataPropagatorRelational 侮欺 5 for AS/400 逆
| 戋堋酞戆嘻嘘怕仍似、喧损祁 DJRA·菡胎远仆坪驮腈嘻戋堋酞戆你、
| 却摹髓气些嘁挝倾≈UDB 谡瘫你爬∽你探诘·
 
| 区嬉 DJRA
 
| DJRA 软王气蜱 "\BONUS\REPLICATION" 你·渫吐吞嘻区嬉曦艳楝骜毓
| 偏倾亩悄软蛇嘻 "DataJoiner Planning, installation and
| Configuration Guide" 你探诘〃
 
|      http://www.software.ibm.com/data/datajoiner/booksv2/djxn2m79
 
| 孚砒侮新木偏远杀釉跽 (阵胬页 SC26-915-01)·友悄峭 postscript 崖耸
| 针、铢诜 DataJoiner ftp 杲谆亩绁 "v2ntpic.pdf" 篁争〃
 
|      ftp://ftp.software.ibm.com/ps/products/datajoiner/info/
 
| Replication Administration 埔恻区嬉倾 Windows 95。Windows 98 托
| Windows NT 散淦朔苡母·友区嬉 Replication Administration 侮欺
| 2.1.1 针、铢〃
 
| 1.  怃邛 '始嘻缳妾' 托 'Explorer'
 
| 2.  押摹亩 UDB DB2 CD-ROM
 
| 3.  蛸探 BONUS
 
| 4.  蛸探 REPLICATION
 
| 5.  仝如 DJRA 幔娶·菡淠尕筇翥篁争、虽怃填区嬉幔施·
 
| 区嬉哝怄、诶偏盆牙泣友区嬉 DJRA 嘻气蜱·
诶木偏盆鲞 README.TXT
| 篁、唆宴亦却孚筌祁幔娶嘻薏浠骜毓·
 
 
  15.0  DB2 幔娶菝佑牙胁
 
 
  15.1  王 APPLICATION DEVELOPER'S KIT
 
  VisualAge for Basic 滔 Lotus Approach 拟锹蝰厢王塄新艿涅·
 
 
  16.0  SQL REFERENCE (欺阵栖你牌脓)
 
 
| 16.1  NAMING CONVENTIONS (CURSOR-NAME)
 
| CURSOR-NAME         A long identifier that designates an SQL cursor. For host
|                     compatibility, it supports hyphens as well.
 
 
| 16.2  ALTER TABLE
 
  The ACTIVATE NOT LOGGED INITIALLY clause should not be used when DATALINK
  columns with the FILE LINK CONTROL attribute are being added to the table.
 
| Replace the description of "table-name" with the following:
 
| "table-name"
 
| Identifies the table to be changed. It must be a table described in the
| catalog and must not be a view or catalog table. If it is a summary table,
| alterations are limited to activating not logged initially, changing pctfree,
| locksize or append.
 
 
| 16.3  COMPOUND SQL
 
| The following should be added to the "Rules" section:
 
| DB2-Connect does not support SELECT statements selecting LOB columns in a
| compound SQL block.
 
 
  16.4  CREATE FUNCTION
 
 
  16.4.1  DBINFO
 
  Under both CREATE FUNCTION (External Scalar) and CREATE FUNCTION (External
  Table), there is a list of the information contained in the DBINFO structure
  which is passed to the UDF if the definer specifies DBINFO. The following
  bullet has been added to each of these lists:
 
       Application ID - unique application ID which is established
          for each connection to the database.
 
 
| 16.4.2  ERROR PROCESSING FOR UDF CALL TYPES
 
| In the "CREATE FUNCTION (External Scalar)" section, where the "NO FINAL CALL
| or FINAL CALL" specification is discussed, this sentence should be added to
| the bottom:
 
| A description of the scalar UDF processing of these calls when errors occur
| is included in the Embedded SQL Programming Guide, Chapter 7, "Other Coding
| Considerations" section, under "Hints and Tips".
 
| This updated description is in the section 8.11.2, "External UDF Error
| Processing Model for Scalar Functions".
 
| In the "CREATE FUNCTION (External Table)" section, where the "NO FINAL CALL
| or FINAL CALL" specification is discussed, this sentence should be added to
| the bottom:
 
| A description of the table UDF processing of these calls when errors occur is
| included in the Embedded SQL Programming Guide, Chapter 7, "Table Function
| Considerations" section.
 
| This updated description is in the section 8.11.1, "Scratchpad and Final Call
| Type Arguments for EXTERNAL TABLE Functions".
 
 
| 16.5  CREATE TABLE
 
 
| 16.5.1  CREATE TABLE DESCRIPTION
 
| Add the following to the description of NOT LOGGED INITIALLY:
 
  The NOT LOGGED INITIALLY clause should not be used when DATALINK columns with
  the FILE LINK CONTROL attribute are present in the table.
 
| Replace the description of "FULLSELECT" under "summary-table-definition" with
| the following:
 
| FULLSELECT
 
| Defines the query in which the table is based. The summary-table-options
| specified define attributes of the summary table. The option chosen also
| defines the contents of the fullselect as follows:
 
| When DEFINITION ONLY is specified, any valid fullselect can be specified.
| The data type and nullability attribute are determined from the result
| columns of the select list. Every select list element must have a name.
 
| When REFRESH DEFERRED or REFRESH IMMEDIATE is specified, the fullselect
| cannot include:
 
| o   references to a view, summary table, or typed table in any FROM clause
 
| o   expressions that are a reference type or DATALINK type (or distinct type
|     based on these types)
 
| o   functions that have external action
 
| o   functions that depend on physical characteristics (for example
|     NODENUMBER, PARTITION)
 
| o   table or view references to system objects (explain tables also should
|     not be specified).
 
| Furthermore, when REFRESH IMMEDIATE is specified:
 
| o   the fullselect must be a subselect
 
| o   the subselect cannot include:
 
|     -   functions that are not deterministic
 
|     -   scalar fullselects
 
|     -   predicates with fullselects
 
|     -   special registers
 
| o   a GROUP BY clause must be included in the subselect
 
| o   the select list must have a COUNT(*) function (or COUNT_BIG(*)) and no
|     DISTINCT
 
| o   only SUM (of not nullable columns), COUNT, or COUNT_BIG column functions
|     are allowed in the select list (without DISTINCT) and other select list
|     items must be included in the GROUP BY clause
 
| o   the FROM clause must reference a single base table (tables cannot be
|     summary tables, typed tables, or views)
 
| o   all GROUP BY items must be included in the select list
 
| o   no grouping sets are allowed (including CUBE and ROLLUP) or grouping on
|     constants
 
| o   a HAVING clause is not allowed
 
| o   if in a multiple partition nodegroup, then a partitioning key must be a
|     subset of the group by items.
 
| Replace the description of "REPLICATED" with the following:
 
| REPLICATED
 
| Specifies that the data stored in the table is physically replicated on each
| database partition of the nodegroup of the table space in which the table is
| defined. This means that a copy of all the data in the table exists on each
| of these database partitions. This option can only be specified for a summary
| table defined with REFRESH DEFERRED (SQLSTATE 42997).
 
 
| 16.5.2  CREATE TABLE NOTES
 
| Replace the seventh major bullet under "Notes" with the following:
 
| o   A REFRESH DEFERRED summary table may be used to optimize the processing
|     of queries. In order for this optimization to be able to use a summary
|     table, the fullselect must conform to certain rules in addition to those
|     already described. The fullselect must:
 
|     -   be a subselect with a GROUP BY
 
|     -   not include DISTINCT anywhere in the select list
 
|     -   not include any grouping sets (including CUBE and ROLLUP)
 
|     -   not allow nulls in any grouping columns in the group by clause
 
|     -   not reference any column more than once
 
|     -   not contain more than 32 columns in the group by clause
 
|     -   not include any special registers
 
|     -   not include functions that are not deterministic.
 
|     If the query specified when creating a REFRESH DEFERRED summary table
|     does not conform to these rules, a warning is returned (SQLSTATE 01633).
 
| Add the following new bullet under "Notes":
 
| o   If a summary table is defined with REFRESH IMMEDIATE, it is possible for
|     an error to occur when attempting to apply the change resulting from an
|     insert or update of the underlying table. The error will cause the
|     failure of the insert or update of the underlying table.
 
 
| 16.6  CREATE TABLESPACE
 
| The functionality described in the sub-section "DROPPED TABLE RECOVERY" has
| not been implemented. This sub-section should be deleted from Version 5.2 of
| the SQL Reference.
 
 
  16.7  APPENDIX A. SQL LIMITS/DATABASE MANAGER LIMITS
 
  The limit for the number of tables in a DMS table space has been increased
  from 6648 to 51971. This new limit will automatically apply to any table
  spaces with a page size other than 4KB, and to all newly created 4KB DMS
  table spaces.
 
  For existing 4KB DMS table spaces, the new /ets option of the db2dart utility
  is used to apply the new limit:
 
  1.  Deactivate the database (that is, ensure that no connections to it
      exist).
 
  2.  Invoke: db2dart <dbalias> /ets /tsi <tid>. This will check the specified
      table space for existing table, index, or LONG objects which have
      identifiers that are incompatible with the application of the new limit.
      If none are found, the new limit will be applied to that table space.
      Otherwise, a list of incompatible tables will be provided in the dart
      report.  In this case, those tables must be dropped, and the command run
      successfully, for the new limit to become effective. The tables can be
      recreated and reloaded after the utility has been run successfully on all
      logical nodes. On EEE installations, run this command first on one
      logical node that is a member of the nodegroup in which the table space
      resides. If incompatible tables are identified, drop them, and reissue
      the command. Once you have run the command successfully on one logical
      node, you must run it again on every logical node in the nodegroup in
      which the table space resides (either the db2_all or the db2dart_all
      utility can be used). For information about db2dart options, invoke
      db2dart without any options (the utility can be found in sqllib\misc).
 
  NOTES:
 
  1.  If db2dart /ets is successfully run on a table space, restoring a table
      space backup image taken prior to running dbdart /ets will no longer be
      supported.
 
  2.  If db2dart /ets is successfully run on any table space in a database,
      restoring a database backup image taken prior to running db2dart /ets,
      and rolling forward through the point-in-time when db2dart /ets was run,
      will not be supported.
 
  3.  A database backup must be taken immediately after successfully running
      db2dart /ets (all table spaces on which the tool is successfully run will
      be placed in backup pending state).
 
 
  17.0  SYSTEM MONITOR GUIDE AND REFERENCR (欺阵栖你牌脓)
 
 
  17.1  EVENT MONITORS ARE CREATED WITH LOCAL SCOPE (欺阵栖你牌脓)
 
  The syntax diagram for the CREATE EVENT MONITOR statement shows that by
  default, event monitors are created with global scope. This is incorrect.
  Event monitors are created with local scope by default.
 
 
  18.0  浠种吞
 
 
| 18.1  真卒 (宴骀/栩友闲知)
 
| 欺彗岣盛嘻蕃狻偏盆堠绱·"REFRESH IMMEDIATE" 蛸恸堍倾偏盆损祁魔·
 
 
| 18.2  喧弭 JAVA 筌祁幔娶暖 APPLETS 收浠
 
  堍倾蛹友喧弭滔仝如涅芍嘻 SQL for Java (SQLJ) 幔娶、腈友 Java
  Development Kit (JDK) 侮欺 1.1.4 托收浠侮欺·
 
  欺厢蜱却卮绁摹髓枳 Java 畀梭幔娶嘻收·竺囚幔施滔 UDF 幔娶
  呢拧醛拟茄嘻诜谆滔腮韦鹇幔娶·菡淼偏诜谆瘼鹇母嘻损祁席
  诜肟軎囚探腮韦鹇瘼鹇母嘻竺囚幔施滔 UDF·气些淠炭摊爨嘻幔娶
  邱亩〃
 
  DB2STP         堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 DB2SPCLI·
 
  DB2UDF         堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 DB2UDCLI·
 
  STP            堍倾岩腮韦鹇幔娶·趟频破嘻诜谆幔娶岩 STPCLI·
 
  UDF            堍倾岩诜谆幔娶·破趟频嘻腮韦鹇幔娶岩 UDFSRV·
 
  呢倾 UNIX 仆坪母喧恰 Script 篁 "embprep"、倾 Windows 仆坪母喧
  恰 "embprep.bat"、倾 OS/2 母喧恰 "embprep.cmd"、唆些弭罹滔
  葙岣 SQLJ 幔娶·破岂 "makefile" 趟频、倾 Java 涅芍嘻 SQL 畀梭
  幔娶母仝如 "db2profc" 淘棚·破诈萋骜砧栈。损祁席 ID 滔葑如睿
  却偏蛸祁嘻趴戆、鞒群筚煞诜谆瘼鹇诜肟軎葙岣摊 DB2 腮韦鹇母嘻
  骜砧栈·
 
  盆亩岩枳王 DB2 UDB 侮欺 5.2 嘻 SQLJ 排呶嘻抬破宇瘫〃
 
  o   拟排呶些弭罹蛸恸 "DATETIME"·惘排呶傧脬砗漤苴鳋嘻攀哝
      滔针怄知娶·

 
  o   些弭罹蛸恸 "PACKAGE USING package-name"、牙贴些弭罹鹇
      驮友喧恰嘻骜砧琵秦辎·邱为栖蛴墨秦辎、鞋损祁菝贴篁秦辎 (
      拟芍佾篁秦虽醛乃煅)·薏乃羡轩岩 8 远求镊·寝页 SQLJ 菝
      贴篁秦辎却 _SJProfileN 求盛 (群莰嘻 N 岩菝贴篁喧楝)、驮盆
      菝贴篁秦辎摹贴乓 8 远求镊羡·邕菝骜砧琵秦辎岩岂菝贴篁胬睿
      曦菝贴篁亠睿嘻些 (8 - pfKeyNumLen) 远求镊喧楝仍醛·
 
      抬你嘻 pfKeyNumLen 岩菝贴篁秦辎你嘻菝贴篁亠睿羡轩·邱为菝
      贴篁喧楝嘻羡轩饩绱 7、鞋衮损祁薏靴 7 软戆、仍拟绥强呷砒
      伤·梭邱〃
 
            菝贴篁秦辎                             邕菝骜砧琵秦辎
            ---------------------                  --------------------
            App_SJProfile1                         App_SJP1
            App_SJProfile123                       App_S123
            App_SJProfile1234567                   A1234567
            App_SJProfile12345678                  A2345678
 
  o   宓 java.math.Bigdecimal Java 配缳妾闲泣娶嘁挝祁王 SQL 蒹虞娶
      针、配戆嘻甏漤轩滔难戆软戆倾筌祁幔娶些弭罹哝怄嘁挝损祁·
      邱为诜损祁嘻蒹虞娶母亩牌你亦拟砒唆难戆配戆嘻甏漤轩滔难戆软戆、
      鞋偏损祁 CAST 唆牙贴甏漤轩滔难戆软戆·
 
  o   形 java.math.BigInteger 嘻 Java 戆嘁挝散页 SQL 蒹虞娶
      你嘻配戆·

 
  o   驮却 SQLJ 竺囚幔施埔恻倾 FENCED 砑娶亩仝如·
 
| o   拟排呶 sqlj 蛸恸 "profile"·友溶如菝贴 sqlj 驮塄祈嘻菝贴篁针、
|     铢损祁 "db2profc"·
 
| o   拟排呶 "SET TRANSACTION" 耐苹·
 
| o   拟排呶 "WITH" 耐苹·
 
| o   拟排呶 SQLJ 虐骰席曦 JDBC 岣为菝贴逆怄嘻迁碾散祁吞·
 
| o   Java 配缳妾闲泣娶嘁挝祁王 SQL 蒹虞娶·
 
  衍髓鲞帰鹁鹇拟排呶诜 applet 肄嘻骜溷篁绁墨葙嘻戊堑· 倾孳璺
  绁墨僳髓鲞帰鹁鹇嘻 applet 针、诶淠拳摊亩悄蜚毹毓丈〃
 
       java.lang.ClassNotFoundException: Applt_SJProfile0
 
  贫评、却摹远狞祁幔娶偏盆衮葙菝贴篁魉咝页盆 Java 杀知娶竺
  囚嘻菝贴篁· 孚狞祁幔娶岩辎页
  sqlj.runtime.profile.util.SerProfileToClass 嘻 Java 杀· 破
  淠衮葙嘻菝贴篁骜溷篁狺页蛴墨、仍衮芍却孚菝贴篁嘻 Java 杀
  塄祈页蛴砒· 诶偏盆损祁亩悄淘棚、唆魉咝菝贴篁〃
 
       profconv Applt_SJProfile0.ser
 
         托
 
       java sqlj.runtime.profile.util.SerProfileToClass Applt_SJProfile0.ser
 
  岣为淠喧恰杀 Applt_SJProfile0.class·铢盆 .class 知娶嘻菝
  贴篁唆探蓬 applet 驮损祁逆 .ser 知娶嘻菝贴篁·
 
  剀枳 SQLJ applet、诶腈友 db2java.zip 暖 runtime.zip 篁争·邱
  为蛸疱拟友衮驮却嘻 applet 杀、db2java.zip 暖 runtime.zip
  徐琵倾尢摹嘻 Jar 篁争你、铢衮 db2java.zip 暖 runtime.zip (盆
  葚龅缫怃) 腕墨 "applet" 砗泣你嘻像囚俣戆你· 剀枳拟排呶像囚砗
  泣你逆情远 zip 篁争嘻僳髓鲞帰鹁鹇、铢倾像囚砗泣你牙贴 db2java.zip、
  虽衮苔却 applet 杀嘻 runtime.zip 尕怃倾 web 鲞帰鹁鹇偏盆囚探
  嘻闹散气蜱你·
 
 
  18.3  WEB 谡瘫你爬滔 NETQUESTION (邛祁 WEB 谡瘫你爬肟軎牌堑洳掾)
 
  王倾 UNIX 散淦朔苡母邛祁肟軎牌堑洳掾嘻牙泣拟七睚·
  七睚牙泣偏倾 Web 嘻亩悄杲谆你势摊〃
 
       http://www.software.ibm.com/data/pubs/papers/db2html.html
 
  王 OS/2 滔 Windows 散淦朔苡嘻 "nqmap" 淘棚逆畀梭筌收页〃

 
       nqmap -u DB2ADMEN "http://yourserver/doc/html/" DB2ADMEN
 
  王倾 OS/2 散淦朔苡母罹蛞≈邛侬 HTML 洳掾腮韦鹇∽璺泣吞锍嘻牙泣邱亩〃

 
      1. 倾 DB2 for OS/2 骜砧设你、祁潇珩骗躏押摹亩≈邛侬 HTML
         洳掾腮韦鹇∽璺泣·
         蛸探≈菝贴∽、押摹亩≈幔娶∽砗·
         倾≈偏蛸祁嘻俣戆∽软你、浠炝 CONFIG DB2WEBCC.CNF 摊
         俣戆求入岣盛·押摹亩 OK 蒺破·
      2. 罹蛞 db2init.cmd 篁争·群篁争软王 x:\sqllib\bin\、抬你 x: 
         岩呢区嬉 DB2 嘻轹轺瘼·倾群篁争你掾势琵芍 "DB2SS.EXE" 滔
         "DB2NETQD.EXE" 嘻求如·倾群如如盛浠炝 CONFIG "DB2WEBCC.CNF"·
         (蚊泗、诶腈友祁麂趴胬涯阮篁秦)·竺囚虽岣手·
         铢镥
         王邛祁肟軎牌堑洳掾嘻牙泣逆抬秕蒎枪·

 
  邱为诶泖洳掾抢蒎 DB2 罾母骜毓、埔恻茄针区嬉 DB2 牌堑 (倾
  UNIX 朔苡母辎页 "塄新篁争栈") 滔 Web 谡瘫你爬暖抬罾母尕氅·
  邱为区嬉 Web 谡瘫你爬暖抬尕氅、叁栖区嬉抬秕嘻 DB2 罾母牌堑、
  蛹瑭孳蛸探王戋堋。幔娶菝佑。滔 DB2 Connect 嘻洳掾辍、鞋
  淠塄祈蜚毹睿 24、牙砒栖区嬉僳髓洳掾啄趴·茄淼氢、邱为诶却区
  嬉 DB2 罾母牌堑、叁栖区嬉 Web 谡瘫你爬、鞋瑭孳洳掾 Web 谡瘫
  你爬罾母尕氅针淠塄祈肄茄嘻蜚毹睿·

 
 
  18.4  ≈谡瘫你爬∽嘻宇瘫
 
  盆亩岩≈谡瘫你爬∽嘻宇瘫〃
 
  o   倾≈谡瘫你爬∽艳楝岘卮欺你、拟排呶 audit_buf_sz 艳楝俣戆·

 
  o   倾骜砧栈骜砧设逆亩嘻戊堑淠陉施 (拟琵涯损祁席。妃苴。滔
      闲知熄怄)·菡髓堍倾岩押求凄恹施陉施·
 
  o   拧薮骜砧栈埔恻琵芍摹远盆母嘻炭轳迤彗龅 (惘锼祁王 DB2
      UDB EEE)·
 
 
| 18.5  ≈Web 谡瘫你爬∽嘻 JAVA DEVELOPMENT KIT 煲裙
 
| 倾≈浠种吞∽摹阵嘻苌 45 喻母、倾≈Web 谡瘫∽阳姣你却蜚毹嘻蒹虞·
| 铢堠绱亩悄苹耐你驮呷暖嘻 Java Development Kit 煲裙〃
 
| "破淠诜嵌若排呶 Java Development Kit 1.1.5 嘻 Jaba 邛祁逆 Web
| 鲞鹇仝如·"
 
| 邱腈排呶逆 web 鲞鹇嘻薏浠悄泣暖驮腈嘻 Java Development Kit
| 煲裙、铢俣镥亩悄 web 杲喻〃
 
|      http://www.software.ibm.com/data/db2/udb/webcc/
 
 
  19.0  OS/2 侮嘻 HTML 洳掾腮韦鹇〃      洳掾 HTML 牌堑
 
 
  IBM DB2 Universal Database (DB2 UDB) 罾母牌堑蝰厢王 HTML 洳掾
  腮韦鹇母、潭煞诶掾势骜毓·菡髓侮欺蚊泗绥恸氅忘倾 OS/2 母邱若
  区嬉滔损祁洳掾朔苡·

 
 
  19.1  倾 OS/2 母区嬉 HTML 洳掾朔苡
 
 
  19.1.1 OS/2 母洳掾朔苡嘻强暑劬堑
 
  诶埔恻倾瘼鹇母区嬉 TCP/IP 侮欺 3 托收浠侮·  喧区嬉 OS/2 Warp V4、
  寝页破苔蕃锼宓嘻 TCP/IP 煲裙·邱为诶衮 OS/2 Warp V3 Internet Access Kit
  (IAK) 菝贴页俅傺叵嫌 (local loopback)、仍赔却区嬉薏浠 FixPak、鞋 OS/2 Warp V3
  Internet Access Kit (IAK) 签却真·
 
  诶腈友琦 Netscape 2.02 for OS/2 逆嘻鲞鹇· 邱为 Netscape 鲞鹇
  栖鳗醛诶嘻耄似、鞋损祁 Web Explorer 1.1 托收浠侮· 倾诶损祁嘻鲞鹇你、
   铢睚贴蒺 localhost 嘻 proxy 莰堋·
 
  邱为倾苔却 VisualAge for C++ for OS/2 嘻朔苡母区嬉 DB2 UDB、
  鞋枳王 VisualAge for C++ 塄新、腈友区嬉 CSD6 托收浠侮·
 
 
  19.1.2  倾 OS/2 母艳楝 TCP/IP
 
  品友诶嘻朔苡母却邛祁 TCP/IP 俅傺叵嫌滔 localhost、鞋拟戋却属
  却区嬉杲纣痞、洳掾腮韦鹇葭偏盆绐散·
 
  邛祁俅傺叵嫌〃
 
  1.  怃邛≈OS/2 TCP/IP∽骜砧设·
 
  2.  怃邛≈TCP/IP 艳楝∽岘卮欺·
 
  3.  篝狺≈杲纣∽喻域·
 
  4.  倾 "艳楝嘻孽域" 悄泣怔、砗忘 "叵嫌孽域"·
 
  5.  邱为栖蛸探 "邛祁孽域" 钮蛸怔、铢堍倾蛸探破·
 
  6.    "IP 软蛇" 岩 127.0.0.1 赔 "裙杲纣锾艴" 岩熄契·
 
  倾朔苡母邛祁 localhost〃
 
  1.  友篝宴岩闪邛祁 localhost、铢倾 OS/2 淘棚如蛴墨
        "ping localhost"·
 
      o   邱为却惝沁骜砧、闲泣却邛祁 localhost、诶偏盆堠绱亩域
          嘻抒 2 滔 3、牺谫纥摊抒 4·
 
      o   邱为惝沁 "localhost 栖稀"、托淘棚弭、鞋闲泣栖邛祁
          localhost·铢纥容抒 2·
 
  2.  邱为诶岩倾杲纣母、铢睚贴却邛祁叵嫌 (loopback) (铢俣镥母虞
      "邛祁俅傺叵嫌")·
 
  3.  邱为诶拟倾杲纣母、铢仝如亩悄抒唆邛祁 localhost〃
 
      a.  倾 MPTN\BIN\SETUP.CMD 淘棚篁你、浠炝亩悄如摊抬破
          ifconfig 如靴域〃
 
               ifconfig lo 127.0.0.1
 
          蕃狻〃蛹诶苔蕃 Internet Access Kit 嘻 OS/2 Warp、偏浠
                炝群如摊 \STARTUP.CMD 仍湘 MPTN\BIN\SETUP.CMD·
                邱为群篁争拟囚倾、鞋埔恻喧恰破·
 
      b.  倾 TCP/IP 艳楝骜砧设你、铢仝如亩悄抒〃
 
          1)  纥容 "艳楝秦辎尕蔚韦侪幔娶喻域"·
 
          2)  倾 "属却秦辎腮韦鹇嘻配缳妾秦辎艳楝" 闲知你、
              浠炝摹恸圄蜱、衮 "IP 软蛇" 菝贴页 127.0.0.1、
              虽衮 "配缳妾秦辎" 菝贴页 localhost·
 
          蕃狻〃邱为倾 "艳楝 LAN 秦辎尕蔚韦侪幔娶" 喻域母、
                却诶瘼鹇嘻配缳妾秦辎、鞋宓诶衮 IP 软蛇 127.0.0.1
                菝贴页 localhost 针、埔恻浠炝群秦辎散页杀秦·
 
      c.  蛸探 "纥容秦辎腮韦鹇逆些强掾势 HOSTS 悄泣" 悄泣怔·
 
          蕃狻〃群抒岩伤猥 OS/2、宓破掾势配缳妾 (邱 localhost) 针、
                筌损祁倾瘼鹇母势摊嘻配缳妾软蛇、仍湘篝宴秦辎腮韦鹇· 
                邱为配缳妾栖贴屮倾瘼鹇母、OS/2 淠损祁诶艳楝嘻秦辎腮
                韦鹇掾势配缳妾·
 
      d.  蒺 TCP/IP 艳楝、嘤靴屿浠邛侬朔苡·
 
      e.  诶筌孚偏盆 ping localhost 仍拟埔葙谫摊杲纣母·
 
  4.  配缳妾秦辎岩闪七睚·倾 OS/2 淘棚如母蛴墨 "hostname"·
      惝沁嘻配缳妾秦辎筌苁琴 TCPIP 艳楝岘卮欺嘻≈配缳妾秦辎∽喻
      域母嘻秦辎、赔埔恻难王 32 远求镊·邱为配缳妾秦辎拟苁琴菡
      髓劬堑、鞋倾配缳妾秦辎喻域母收七破·埔友针、倾 CONFIG.SYS
      (SET HOSTNAME=<correct_name>) 你收七破·倾仝如埔友嘻收
      逆靴、铢屿浠邛侬·
 
 
  19.1.3   TCP/IP 艳楝
 
  押摹亩 "邛侬 HTML 洳掾腮韦鹇" 璺泣、群璺泣软王 DB2 for OS/2
  骜砧设·邱为砒堍蜚毹毓丈、鞋栖七睚艳楝 TCP/IP·
  铢隧澌 19.1.2, "倾 OS/2 母艳楝 TCP/IP" 你嘻牙泣、盆睚贴呢七睚艳楝 TCP/IP·
  邱为收菝贴、鞋屿浠邛侬 OS/2·

 
 
  19.1.4  掾势洳掾朔苡气蜱
 
  洳掾朔苡岩竺囚倾破溶淖嘻气蜱亩、寝页破偏卒莘抬破塄新损祁·梭
  邱、邱为诶倾轹轺瘼 G 区嬉 DB2 UDB 盆暖洳掾朔苡、靴唆拇倾轹轺
  瘼 H 区嬉 VisualAge for Java、鞋品区嬉摹远洳掾朔苡 -- 苌摹远
  区嬉嘻朔苡·
 
  欺牌堑嘻衍髓牙泣腈友诶牙贴群气蜱嘻软弭· 友掾势群气蜱、铢倾
  OS/2 淘棚如蛴墨群淘棚〃
 
       echo %IMNNLPSSRV%
 
 
  19.1.5  收洳掾腮韦鹇嘻僬胬
 
  洳掾腮韦鹇岩牙贴容葙谫僬 49213、群胬睿饩砒牙贴峥 TCP/IP 嘻狞
  祁葙谫僬·邱为诶却贫摹远塄新损祁群葙谫僬、诶偏盆沙祁亩悄抒
  唆收洳掾腮韦鹇葙谫僬〃

 
  1.  倾洳掾朔苡气蜱你罹蛞 HTTPD.CNF 篁、虽衮僬胬收页诶稀绗偏
      祁嘻僬胬、薏秋倾 49000 盆母·
 
  2.  纥容 DB2 UDB 气蜱、嘤靴倾 %DB2PATH%/doc/html 气蜱你损祁
      牌求罹蛞鹇唆罹蛞 DB2SRCH.HTM 篁争·收亩域摹如、醛页诶
      倾强些抒你蛸探嘻葙谫僬〃
 
           <form action="http://localhost:49213/cgi-bin/db2sr*xx.exe" method="POST">
 
           抬你〃
              *       岩 D 蓬闲 DBCS、S 蓬闲 SBCS
              xx      岩蓬闲忐煅欺牌堑驮祁耄似嘻麂求镊杀求
              49213   岩蓬闲 localhost 嘻浠葙谫僬
 
  3.  佤畔虽邛侬洳掾腮韦鹇、派挝岩倾 DB2 for OS/2 骜砧设你押
      胎亩孚璺泣·
 
 
  19.1.6 猬鏊洳掾腮韦鹇区嬉蜚毹
 
  邱为诶倾区嬉洳掾腮韦鹇针谫拳摊蜚毹毓丈、铢诜 OS/2 淘棚如蛴墨
  亩悄淘棚、虽蜃擐破惝沁嘻牙泣〃
 
       SNIFFLE /P
 
  铢睚贴诶倾声醛靴却屿浠邛侬朔苡·
 
 
  19.2  损祁 HTML 洳掾朔苡
 
 
  19.2.1 邛侬滔佤畔洳掾腮韦鹇
 
  倾区嬉洳掾朔苡靴、破淠倾诶屿浠怃瘼逆靴溶侬邛侬·
 
  邱为洳掾腮韦鹇邛侬针属却圊祈蜚毹、叁诶倾鲞鹇你圊堍亩悄蜚毹
  毓丈、鞋押摹亩 "佤畔 HTML 洳掾腮韦鹇" 璺泣、嘤靴押摹亩 "邛侬
  HTML 洳掾腮韦鹇" 璺泣·
 
       圊祈杲纣蜚毹〃嘁挝葙谫摊腮韦鹇·
       腮韦鹇偏卒宓瘼托嘁挝葙母·
       帷靴孳後锹葙谫摹裙·
 
  声醛洳掾逆靴、铢佤畔洳掾腮韦鹇唆拳沁破损祁嘻卮鹳·友佤畔破、
  铢押胎亩≈DB2 for OS/2∽骜砧设你嘻 "佤畔 HTML 洳掾腮韦鹇" 璺
  泣·
 
 
  19.2.2 泞鏊杲纣葙罾针洳掾
 
  邱为诶拟倾杲纣母 (梭邱、邱为诶损祁钗母形缳妾、虽赔聿针诜 LAN
  葙谫麾怃)、鞋埔恻邛祁 localhost 倪卒洳掾牌堑·仝如群散淦嘻牙
  泣卮绁倾 19.1.2, "倾 OS/2 母艳楝 TCP/IP" 你嘻抒你·
 
 
  19.2.3  势拟摊篁争嘻蜚毹
 
  洳掾朔苡洳掾邕强贴屮嘻啄趴·拟铫诶区嬉嘻岩娘臌 DB2 UDB 塄新、
  菡髓啄趴抢蒎葭淠蝰洳掾朔苡仍区嬉· 寝群、宓诶仝如洳掾针、却髓
  岣为淠惝沁 "势拟摊篁争" 蜚毹毓丈、寝页菡髓岣为岩王栖区嬉倾
  诶朔苡母嘻塄新·
 
 
  19.2.4  邱为洳掾嘁真 (蜚毹 500 圊祈王瑭孳洳掾针)
 
  邱为呢区嬉洳掾腮韦鹇、叁倾洳掾牌堑针砒堍蜚毹、鞋篝宴亩悄恸气〃
 
  1.  篝宴洳掾朔苡岩闪区嬉七睚·艨韬戆 IMNNLPSSRV 筌牙亲洳掾
      朔苡气蜱 (铢俣镥 "19.1.4 掾势洳掾朔苡气蜱")·
 
  2.  洳掾朔苡气蜱筌琵芍菡髓篁争〃
 
      o   DB2SRSxx.EXE 托 DB2SRDxx.EXE 偏仝如篁 (些席岩祁王 SBCS
          牌堑、靴席岩祁王 DBCS 牌堑)·xx 岩忐煅牌堑驮祁耄似嘻麂
          求镊杀求·梭邱、DB2SRSEN.EXE 岩恿牌侮 SBCS 牌堑嘻偏仝
          如篁¨DB2SRDCN 岩鳇 你牌 DBCS 牌堑嘻偏仝如篁·
 
      o   DB2HEAD.HTM 暖 DB2FOOT.HTM·邱为菡髓篁争拟囚倾、鞋仝如
          DB2NETQ.CMD 唆菝贴啄趴圄卮、暖铒犒篁争摊洳掾朔苡气蜱你·

 
  3.  洳掾朔苡筌倾塄新牌堑你圄卮·趟频群淘棚唆悄泣呢倾洳掾朔苡你
      圄卮嘻抢蒎牌堑〃
 
           NQMAP -A
 
      DB2 UDB 嘻牌堑辎页 DB2ADMxx。DB2APDxx。托 DB2CONxx、抬
      你 xx 岩忐煅牌堑驮祁耄似嘻麂求镊杀求·菡髓秦辎淠砒堍
      倾 NQMAP 惝沁嘻秦辎悄泣你·
 
      邱为篁争拟囚倾、鞋偏卒岩 TCP/IP 栖七睚区嬉、托啄趴呢溱
      浯·些席偏损祁 SNIFFLE /P 唆尕暑、靴席偏孱岂屿浠区嬉牌
      堑唆尕暑·
 
 
  19.2.5 邛侬洳掾韦侪幔娶针佝嗔摊蜚毹
 
  邱为圊堍群蜚毹〃
 
       HS0410: 邛侬洳掾韦侪幔娶针佝嗔摊蜚毹·佤畔韦侪幔娶、虽屿浠
               邛侬破·押 Enter ...
 
       (却针苑群蜚毹岩 EHS0411、叁牌求肄茄·
       群毓丈砒堍倾抢悌颦栎母·)
 
  诶嘻配缳妾秦辎溶诜仝如区嬉靴偏卒呢收、诶埔恻屿浠卮蜱破·纥容
  NetQuestion 气蜱、虽蛴墨〃
 
       type netq.cfg
 
  盆宴亦 NetQuestion 驮损祁嘻配缳妾秦辎·邱为诶呢收配缳妾秦辎、
  梭邱倾艳楝 DHCP 滔 DDNS 针、鞋蛴墨〃
 
       netqinit <data-path>
 
       Example:  netqinit d:\netqos2\data
 
 
  19.3 尕劓区嬉 HTML 洳掾朔苡
 
  尕劓区嬉 DB2 for OS/2 逆靴、洳掾朔苡蹁岩昼倾帻轺母·铢仝如
  UNINSTNQ.CMD 唆劓篇破·
 
 
  19.3.1 倾 OS/2 母尕劓区嬉洳掾朔苡嘻俾黝
 
  邱为仝如 UNINSTNQ.CMD 叁洳掾朔苡蹁岩嘁挝尕劓区嬉、鞋韵寝偏卒岩〃

 
  o   TCP/IP 栖七睚艳楝·
 
  o   DB2 UDB 托贫摹远塄新七倾损祁洳掾朔苡、寝群嘁挝劓篇破·
 
  1.  铢隧澌苌 147 喻母嘻 19.1.2, " 倾 OS/2 母艳楝 TCP/IP" 阳姣嘻
      牙泣、盆睚贴七睚氢艳楝 TCP/IP、赔盆七睚艳楝嘻 TCP/IP 菝贴唆
      啬填菝贴洳掾腮韦鹇·邱为却收艳楝、摹贴友屿浠邛侬朔苡·
 
  2.  友刹鏊葬髓塄新捏倾洳掾朔苡你圄卮、铢圊砒亩悄淘棚〃
 
           NQMAP -A
 
      邱为群淘棚栖惝沁嵌若啄趴、鞋纥摊抒 6·
 
      邱为群悄泣琵芍拟王 DB2 UDB 嘻啄趴 (签苫、抬秦辎怃螭拟
      岩 "DB2")、鞋劓篇洳掾腮韦鹇·
 
      邱为破却琵芍嵌若 DB2 啄趴篁秦 (DB2ADMxx。DB2APDxx。DB2CONxx)、
      鞋 DB2 UDB 嘁挝探旨圄卮啄趴、仍鹨映洳掾朔苡尕劓区嬉坡邗·邱为
      DB2 UDB 拟七睚尕劓区嬉、淠圊祈母虞谂拾 (梭邱、SQLLIB 骜砧设莘
      纱劓)·倾菡辍谂斡亩、诶埔恻琶侬探旨圄卮啄趴、虽损祁亩悄抒唆
      劓篇洳掾朔苡气蜱·
 
      a.  圊砒群淘棚、盆睚贴洳掾腮韦鹇七倾仝如〃
 
               NETQ START SERVER           //for SBCS
               IMQSS.EXE -START DBCSHELP   //for DBCS
 
      b.  枳输摹远啄趴篁圊砒群淘棚〃
 
               NQMAP -D <index_name>
 
      c.  枳输摹远啄趴篁圊砒群淘棚〃
 
               NQDELET <index_name>        //for SBCS
               TMDELET <index_name>        //for DBCS
 
      d.  佤畔洳掾腮韦鹇〃
 
               NETQ STOP SERVER            //for SBCS
               IMQSS.EXE -STOP DBCSHELP    //for DBCS
 
      e.  圊砒 "NQMAP -A" 虽属却昼亩嵌若 DB2 啄趴 (DB2xxxxx)·
          邱为却、铢酊峋 IBM 韦侪末赞·
 
      f.  圊砒亩悄淘棚、唆嘁抬破啄趴倾散祁你·
 
               NQCOUNTI <search system directory>  //for SBCS
               TMCOUNTI <search system directory>  //for DBCS
 
          蕃狻〃邱为诶拟稀绗区嬉软弭、铢俣镥 19.1.4, "掾势洳掾朔苡
                气蜱"·
 
          o   邱为群淘棚惝沁嘻骜砧牙砒、却摹远托情远啄趴捏倾散祁你、
              鞋洳掾朔苡嘁挝劓篇、寝页抬破塄新捏倾圄卮你·拟友仝如
              抬秕抒·
 
          o   邱为洳掾朔苡惝沁 "0 啄趴散祁你"、鞋仝如 UNINSTNQ.CMD·
              (铢土堠群毓丈〃"SYS0016: 群气蜱嘁挝莘劓篇"·) 群洳
              掾朔苡气蜱呢莘劓篇·邱为破蹁倾、鞋铢葙峋 IBM 韦侪末赞·
 
      g.  UNINSTNQ.CMD 声醛逆靴、铢仝如亩悄抒〃
 
          1)  诜区嬉哝怄驮喧恰嘻蕃枪你擀弭 CONFIG.SYS·
 
              蕃狻〃区嬉喧恰呢罹胬嘻蕃枪、阼祁 config.xyz 知娶、抬你
                    xyz 岩 000 摊 100 畀挢涅苌摹远偏祁嘻胬睿·
                     蕃枪苔
                    却区嬉针嘻针怄滔攀哝雒卮·区嬉哝怄却喧恰胎远蕃枪〃 
                    摹远岩王 DB2 UDB 区嬉、摹岩王洳掾朔苡区嬉·
 
              o   蛹品友劓篇洳掾朔苡菝贴、铢损祁苌抹远蕃枪·
 
              o   蛹友劓篇 DB2 UDB 滔洳掾朔苡菝贴、铢损祁苌摹远蕃枪·
 
          2)  劓篇洳掾朔苡嘻气蜱暖抬驮却耐气蜱·
 
              a)  纥容 %TMP%/NETQ 气蜱·
 
              b)  纱劓 NETQ 气蜱你薹秕嘻篁争·
 
              c)  纱劓 NETQ 气蜱·
 
              d)  屿浠邛侬·
 
 
  20.0  WINDOWS NT。WINDOWS 95 暖 WINDOWS 98 侮嘻 HTML 洳掾腮韦鹇〃
        洳掾 HTML 牌堑
 
 
  IBM DB2 Universal Database (DB2 UDB) 罾母牌堑蝰厢王 HTML 洳掾
  朔苡母、潭煞诶掾势骜毓· 菡髓侮欺蚊泗绥恸氅忘邱若倾 Windows NT。
  Windows 95。滔 Windows 98 母区嬉滔损祁洳掾朔苡·
 
  洳掾朔苡岩岂洳掾趴筱滔洳掾腮韦鹇驮苴醛·洳掾朔苡岩竺囚倾破溶淖
  嘻气蜱亩、寝页破偏卒莘抬破塄新损祁·
 
 
  20.1  祁挝宇瘫
 
  群洳掾朔苡拟排呶 Windows 3.1·
 
  群洳掾朔苡拟枳 Thin Clients 邛祁· 邱为友洳掾抬牌堑、淠谫拳摊
  杲纣蜚毹·
 
 
  20.2 倾 WINDOWS NT。WINDOWS 95。滔 WINDOWS 98 母区嬉 HTML 洳掾朔苡
 
 
  20.2.1  洳掾朔苡嘻强暑劬堑
 
  腈友亩悄强暑劬堑〃
 
  o   倾 Windows NT 4.0、友诘摊薏孙嘻真为、筌区嬉 Service Pack 3·
      邱腈孥茇骜毓、铢俣镥
      http://www.microsoft.com/ntserver/info/servicepack3.htm·
 
  o   诶腈友琦 Netscape 3.0 逆嘻鲞鹇·倾诶损祁嘻鲞鹇你、铢睚
      贴蒺 localhost 嘻 proxy 莰堋·
 
  o   瘼鹇母埔恻区嬉却 TCP/IP 侮欺 3 托收浠侮·埔恻区嬉滔艳楝破、
      倪卒损 DB2 UDB 洳掾朔苡七睚绐散·
 
      倾 Windows 95、埔恻隧亩悄派娶邛祁 TCP/IP〃
 
      -   枳 LAN 刭谫痞艳楝仍似〃
 
          -   诶埔恻盆却真嘻配缳妾滔腚傺秦辎唆邛祁 DNS·
 
          -   LAN DNS 埔恻衮 "localhost" 尕蔚页 127.0.0.1·
 
          -   诶嘁挝倾泞鏊 LAN 刭谫痞艳楝逆亩仝如·
 
      -   枳怼谫刭谫痞艳楝仍似〃
 
          -   埔恻佤祁 DNS·
 
          -   埔恻溶侬探诘 TCP/IP 软蛇·
 
              蕃狻〃苫损品剀枳摹远 TCP/IP 刭谫痞仍收、菡髓
                    艳楝蛸恸衮锼祁王驮却 TCP/IP 刭谫痞·蛹属
                    却屿浠艳楝、诶衮嘁挝茄针损祁 LAN 滔怼谫菡
                    辍刭谫痞·
 
          诶嘻杲脬杲纣韦侪蓑筌谆 (ISP) 嘻怼谫杲纣 TCP/IP 吞锍、
          埔恻邱 ISP 驮牙泣唆艳楝·怼谫杲纣 TCP/IP 吞锍、衮弭咝
          怼谫刭谫痞 TCP/IP 吞锍、靴席岩萼绱 Windows 95 谡瘫坪
          你嘻 "杲纣" 璺泣唆艳楝·怼谫刭谫痞 TCP/IP 吞锍埔恻邱
          母虞派娶艳楝、倪淠圊祈吞锍弭咝·倾怼谫刭谫痞 TCP/IP
          吞锍你邛祁 DNS、托倾怼谫刭谫痞 TCP/IP 吞锍你菝贴 IP
          软蛇、葭淠嫩銎 ISP 嘻怼谫杲纣艳楝、寝群埔恻踱森·
 
      枳 Windows NT 4.0 仍似、母域胎辍嘻 TCP/IP 艳楝葭却真·邱为
      岩倾尢瘼母仝如、鞋拟腈友抬破胎远刭谫痞、木偏盆邛祁 MS Loopback
      刭谫痞·
 
 
  20.2.2 佤畔强些区嬉嘻洳掾朔苡侮欺
 
  邱为贫摹远塄新强些呢区嬉洳掾朔苡 (梭邱 VisualAge for Java)、鞋
  埔恻佤畔洳掾腮韦鹇·友佤畔洳掾腮韦鹇、押摹亩≈怃填∽劈卒闲嘻
  DB2 劈卒闲恸气你嘻 "佤畔 HTML 洳掾腮韦鹇"·
 
 
  20.2.3  掾势洳掾朔苡气蜱
 
  洳掾朔苡岩竺囚倾破溶淖嘻气蜱亩、寝页破偏卒莘抬破塄新损祁· 梭
  邱、邱为诶倾轹轺瘼 G 区嬉 DB2 UDB 盆暖洳掾朔苡、靴唆拇倾轹轺
  瘼 H 区嬉 VisualAge for Java、鞋品区嬉摹远洳掾朔苡 -- 苌摹远
  区嬉嘻朔苡·
 
  欺牌堑嘻衍髓牙泣腈友诶牙贴群气蜱嘻软弭· 友掾势群气蜱、铢损祁
  群淘棚〃
 
       echo %IMNINSTSRV%
 
 
  20.2.4 收页洳掾腮韦鹇嘻抬破僬胬
 
  洳掾腮韦鹇岩牙贴容葙谫僬 49213、群胬睿饩砒牙贴峥 TCP/IP 嘻狞
  祁葙谫僬·邱为诶却贫摹远塄新损祁群葙谫僬、诶偏盆沙祁亩悄抒
  唆收洳掾腮韦鹇葙谫僬〃

 
  1.  倾洳掾朔苡气蜱你罹蛞 HTTPD.CNF 篁、虽衮僬胬收页诶稀绗偏
      祁嘻僬胬、薏秋倾 49000 盆母·
 
  2.  圊砒亩悄淘棚唆刹鏊 <db2path> 嘻软弭〃
 
 
           DB2SET DB2PATH
 
  3.  纥容 DB2 UDB 气蜱、嘤靴倾 <db2path>/doc/html 气蜱你、损祁
      牌求罹蛞鹇唆罹蛞 DB2SRCH.HTM 篁争·收亩域摹如、醛页诶倾
      强些抒你蛸探嘻葙谫僬〃
 
           <form action="http://localhost:49213/cgi-bin/db2sr*xx.exe" method="POST">
 
           抬你〃
             *       岩 D 蓬闲 DBCS、S 蓬闲 SBCS
             xx      岩蓬闲忐煅欺牌堑驮祁耄似嘻麂求镊杀求
             49213   岩蓬闲 localhost 嘻浠葙谫僬
 
  4.  佤畔虽邛侬洳掾腮韦鹇·友佤畔洳掾腮韦鹇针、铢押摹亩≈怃填∽
      劈卒闲嘻 DB2 劈卒闲恸气你嘻 "佤畔 HTML 洳掾腮韦鹇"·友邛侬
      洳掾腮韦鹇针、铢押摹亩≈怃填∽劈卒闲嘻 DB2 劈卒闲恸气你嘻
      "邛侬 HTML 洳掾腮韦鹇"·
 
 
  20.2.5  倾 LAN 葙谫嘻轹轺瘼母区嬉 DB2 UNIVERSAL DATABASE
 
  邱为诶倾 Windows 95 母嘻 LAN 葙谫轹轺瘼母区嬉 DB2 UDB、仍倾
  Windows 95 母仝如 AUTOEXEC.BAT 逆些栖屿浠葙谫群轹轺瘼嘻驺、朔
  苡艨韬衮嘁挝菝贴抬艨韬戆·洳掾朔苡岩萼绱是裙篁 (IMNENV.BAT)
  菝贴艨韬戆、群是裙篁软王洳掾朔苡气蜱 (梭邱、F:\IMNNQ_95)·
  友踱怃菡远俾黝、铢诜洳掾朔苡气蜱你铒犒 IMNENV.BAT 摊贫摹远倾仝
  如 AUTOEXEC.BAT 逆些摅呢葙谫嘻轹轺瘼/气蜱·
  嘤靴院恃
  AUTOEXEC.BAT 盆倾邛侬针趟频群是裙篁·梭邱、邱为铒犒 IMNENV.BAT
  摊 C:\WINDOWS\IMNNQ 你、诶摅偏呢浠炝亩悄摹如摊 AUTOEXEC.BAT 你〃
 
       IF EXIST C:\WINDOWS\IMNNQ\IMNENV.BAT CALL IMNENV.BAT
 
 
  20.2.6 猬鏊洳掾腮韦鹇区嬉蜚毹
 
  邱为倾 DB2 UDB 区嬉哝怄圊祈坡邗嘻洳掾腮韦鹇区嬉托啬填菝贴、鞋
  DB2 UDB 区嬉散淦衮声醛·亩域衮潭煞猬鏊圊祈嘻雾斡滔筌阼探嘻
  侬散·
 
  宴亦 <temp>\imnnq\install 气蜱 (抬你嘻 <temp> 岩朔苡嘻 %TEMP%
  气蜱), 唆掾势 IMNNQ.ERR 篁争·邱为破拟囚倾、鞋屿浠怃瘼虽屿浠区
  嬉孚塄新·邱为 IMNNQ.ERR 囚倾、鞋盆亩岩偏卒砒堍嘻涅诈〃
 
 
  HTML Search Server for Windows NT, Windows 95, and Windows Documentation H157
 
 
       1 - 群牙砒堍如 PATH 糯羡、浠炝洳掾腮韦鹇摊 PATH 你、淠鹨映
           痨远 PATH 莘旨劓·
           蕃狻〃  Windows NT 4.0 嘻宇瘫岩 512¨Windows 95 嘻宇瘫
           岩 255·
           喧仝如亩悄抒〃
           a) 收秦 AUTOEXEC.BAT 篁争你嘻 PATH 戆 (PATHGOOD)、竺
           囚收靴屿浠怃瘼·
           b) 诜 <temp>\imnnq\install 劓篇 IMNNQ.ERR 篁·
           c) 屿浠仝如塄新区嬉、唆七睚区嬉洳掾朔苡·
           d) 琴索 PATHGOOD 戆曦 PATH 戆、靴席岩岂薏浠区嬉散淦
           驮喧恰·
 
       2 - 縻恸蜚毹、铢酊峋 IBM 韦侪末赞·
 
       3 - 轹轺熄怄拟送蜚毹·铢睚贴容欧却 4.5MB 轹轺熄怄蓑洳掾朔苡
           损祁、仍赔却送佘熄怄 Windows 95 嘻 AUTOEXEC.BAT 唆收·
 
  邱为 IMNNQ.ERR 琵芍摹毓丈、氅 XXX.EXE 拟囚倾、鞋势拟摊洳掾朔苡偏
  仝如篁·孳後屿浠仝如洳掾朔苡区嬉/啬填菝幔娶·铢俣镥 20.3.4, "邱
  为洳掾嘁真 (蜚毹 500 圊祈王瑭孳洳掾针)"·
 
 
  20.3  损祁 HTML 洳掾朔苡
 
 
  20.3.1  邛侬滔佤畔腮韦鹇
 
  倾区嬉洳掾朔苡靴、破淠倾诶屿浠怃瘼逆靴溶侬邛侬·
 
  邱为洳掾腮韦鹇邛侬针属却圊祈蜚毹、叁诶倾鲞鹇你圊堍亩悄蜚毹
  毓丈、鞋押摹亩 "佤畔 HTML 洳掾腮韦鹇" 璺泣、嘤靴倾≈怃填∽劈
  卒闲嘻 DB2 劈卒闲恸气你押摹亩 "邛侬 HTML 洳掾腮韦鹇"·
 
       圊祈杲纣蜚毹〃嘁挝葙谫摊腮韦鹇·
       腮韦鹇偏卒宓瘼托嘁挝葙母·
       帷靴孳後锹葙谫摹裙·
 
  声醛洳掾逆靴、铢佤畔洳掾腮韦鹇唆拳沁破损祁嘻卮鹳·友佤畔破针、
  铢押摹亩≈怃填∽劈卒闲嘻 DB2 劈卒闲恸气你嘻 "佤畔 HTML 洳掾腮韦
  鹇"·
 
 
  20.3.2 洳掾针 NETSCAPE 托 INTERNET EXPLORER 你呢邛祁 PROXIES
 
  邱为损祁 Netscape 托 Internet Explorer 虽琶侬邛祁 proxies、鞋偏
  鞒岂院恃 proxy 骜毓唆披葳洳掾·
 
       倾 Netscape 3〃
       --------------
         1. 蛸探蛸恸 - 杲纣夼秋菝贴·
         2. 押摹亩 Proxies 砗·
         3. 押摹亩≈琶侬 Proxy 艳楝∽蛸疱你嘻≈篝狺∽·
         4. 倾 "No proxies for" 派怔、躏墨〃
              localhost:49213
            邱为群莰蹁却抬破圄蜱、铢祁葚胬俅缫·
         5. 押摹亩≈睚贴∽、唆蒺≈琶侬 Proxy 艳楝∽狺岌·
         6. 押摹亩≈睚贴∽、唆岣手≈夼秋菝贴∽狺岌·
 
       倾 Netscape 4 (Communicator) 你〃
       -----------------------------
         1. 蛸探罹蛞 - 夼秋菝贴·
         2. 倾≈辍∽瘗你押胎亩≈庑怅∽·
         3. 倾≈庑怅∽耐瘗你押摹亩≈Proxies∽·
         4. 押摹亩≈琶侬 Proxy 艳楝∽蛸疱你嘻≈篝狺∽·
         5. 倾 "梭评雾斡... 枳王盆群页怃螭嘻腚傺秦辎、
            纽损祁 proxy 腮韦鹇" 派怔、躏墨〃
              localhost:49213
            邱为群莰蹁却抬破圄蜱、铢祁葚胬俅缫·
         6. 押摹亩≈睚贴∽、唆蒺≈琶侬 Proxy 艳楝∽狺岌·
         7. 押摹亩≈睚贴∽、唆岣手≈夼秋菝贴∽狺岌·
 
       倾 Internet Explorer 3 你〃
       -----------------------
         1. 蛸探≈篝狺 - 蛸恸∽·
         2. 蛸探≈葙谫∽·
         3. 倾 "梭评雾斡... 枳王盆群页怃螭嘻腚傺秦辎、
            纽损祁 proxy 腮韦鹇" 派怔、躏墨〃
              localhost:49213
            邱为群莰蹁却抬破圄蜱、铢祁葚胬俅缫·
         4. 蛸探 "枳俅傺 (intranet) 软蛇纽损祁 proxy 腮韦鹇" 派怔·
         5. 押摹亩≈睚贴∽、唆岣手≈蛸恸∽狺岌·
 
       倾 Internet Explorer 4 你〃
       -----------------------
         1. 蛸探≈篝狺... Internet 蛸恸∽·
         2. 蛸探≈葙谫∽砗·
         3. 蛸探≈枳俅傺 (Intranet) 囚探堠绱 proxy 腮韦鹇∽钮蛸怔·
            蕃狻〃 邱为诶损祁 proxy 托 socks 葙谫、仍赔呢蛸探≈损祁
            Proxy 腮韦鹇囚探 Internet∽钮蛸怔、倪卒损祁群钮蛸怔·
         4. 蛸探 "庑怅" 押廒·
         5. 躏墨〃
              localhost:49213
            倾 "梭评雾斡... 枳王盆群页怃螭嘻软蛇、纽损祁 proxy 腮韦
            鹇" 派怔·
            邱为群莰蹁却抬破圄蜱、铢祁拧胬唆俅缫浠嘻圄蜱·
         6. 蛸探≈睚贴∽、唆岣手≈蛸恸∽砗·
 
 
  HTML Search Server for Windows NT, Windows 95, and Windows Documentation H159
 
 
  20.3.3 倾钗母形缳妾嘻 WINDOWS 95 你洳掾
 
  秦辎腮韦鹇〃
 
  邱为损祁钗母形、破摹罪岩葙谫摊 LAN 散页泞鏊嘻怃圊仆坪、鞋仝如
  洳掾针偏卒淠却哨·友恹沙洳掾、诶腈友倾 TCP/IP 艳楝你佤祁秦
  辎腮韦鹇 IP 软蛇·咝苹驺氅、诶腈友胎远 TCP/IP 艳楝--摹远岩峥
  葙谫嘻散淦损祁、贫摹远岩峥泞鏊嘻散淦损祁·
 
  倾 Windows 95 你祁王情屿 TCP/IP 艳楝嘻薏孙院七幔娶〃
 
  Windows 95 品诈萋诶却尢摹 TCP/IP 艳楝· 拟绱、倾杲脬杲纣母却橇
  岁菰狞祁幔娶偏祁、诶牙贴摹辍盆母嘻菝贴、嘤靴拯疸葙谫雾梃
  收破辕 (曦 LAN 葙谫托泞鏊)· TCPSwitch 岩菡髓幔娶抬你逆摹·
 
  Socks 腮韦鹇滔 proxies〃
 
  邱为损祁 Netscape 3、赔怼墨区抢杲蛇、盆 proxy 托 socks 腮韦鹇
  囚探 internet、倾诶偏盆洳掾逆些、诶腈友倾 Netscape 纱劓菡髓菝
  贴·菡岩 Netscape 3 嘻摹远淄龅--Netscape Communicator 嘻 "牺
  谫葙谫" 菝贴偏院七群淄龅·
 
 
  20.3.4  邱为洳掾嘁真 (蜚毹 500 圊祈王瑭孳洳掾针)
 
  邱为塄新区嬉却真、叁洳掾嘁真、鞋瑭孳亩悄抒〃

 
  1.  篝宴洳掾朔苡岩闪区嬉七睚·诶筌孚菝贴艨韬戆 IMNINST 滔
      IMNINSTSRV、仍赔 IMNINSTSRV 筌牙亲洳掾朔苡气蜱 (铢俣镥
      20.2.3, "掾势洳掾朔苡气蜱")·
 
  2.  洳掾朔苡气蜱筌琵芍菡髓篁争〃
 
      o   DB2SRSxx 托 DB2SRDxx 偏仝如篁 (些席岩祁王 SBCS 牌堑、
          靴席岩祁王 DBCS 牌堑)·xx 岩忐煅牌堑驮祁耄似嘻麂求镊
          杀求·梭邱、DB2SRSEN 岩恿牌侮 SBCS 牌堑嘻偏仝如篁¨
          DB2SRDCN 岩鳇 你牌 DBCS 牌堑嘻偏仝如篁·
 
      o   DB2HEAD.HTM 暖 DB2FOOT.HTM
 
  3.  睚贴洳掾朔苡呢倾塄新牌堑你圄卮·
      趟频群淘棚唆悄泣呢倾洳掾
      朔苡你圄卮嘻抢蒎牌堑〃
 
           NQMAP -A              //for SBCS
           TMMAP -A              //for DBCS
 
      DB2 UDB 嘻牌堑辎页 DB2ADMxx。DB2APDxx。托 DB2CONxx、抬
      你 xx 岩忐煅牌堑驮祁耄似嘻麂求镊杀求·菡髓秦辎淠砒堍
      倾 NQMAP (托 TMMAP) 惝沁嘻秦辎悄泣你·
 
      损祁 NQMAP (托 TMMAP) 淘棚呷蓑嘻啄趴悄泣、诶偏盆祁亩悄
      淘棚探诘王输摹远啄趴嘻抬破忘茇〃
 
           IMNIXSTA <index_name>  //for SBCS
           IMQIXSTA <index_name>  //for SBCS
 
      群淘棚呷蓑忘茇、邱啄趴雾梃滔啄趴你嘻牌堑戆·
 
      邱为母虞雾斡逆摹拟苁琴、偏屿浠仝如 DB2 UDB 塄新区嬉幔娶·
      邱为倌摹拟苁琴嘻雾斡岩淄欧 DB2SRCH.EXE。DB2HEAD.HTM。滔
      DB2FOOT.HTM、鞋偏诜气蜱 <db2path>\misc 铒犒摊洳掾朔苡嘻气
      蜱 (梭邱、E:\IMNNQ_NT)·塄新区嬉幔娶衮屿浠仝如洳掾腮韦鹇
      嘻区嬉滔啬填菝贴·
 
 
  20.3.5  势拟摊篁争嘻蜚毹
 
  洳掾朔苡洳掾邕强贴屮嘻啄趴·拟铫诶区嬉嘻岩娘臌 DB2 UDB 塄新、
  菡髓啄趴抢蒎葭淠蝰洳掾朔苡仍区嬉· 寝群、宓诶仝如洳掾针、却髓
  岣为淠惝沁 "势拟摊篁争" 蜚毹毓丈、寝页菡髓岣为岩王栖区嬉倾
  诶朔苡母嘻塄新、托王诶蛸疱拟友倾区嬉哝怄区嬉嘻牌堑·
 
 
  20.3.6  邛侬洳掾韦侪幔娶针佝嗔摊蜚毹
 
  邱为圊堍群蜚毹〃
 
       EHS0410: 邛侬洳掾韦侪幔娶针佝嗔摊蜚毹·佤畔韦侪幔娶、虽屿浠
               邛侬破·押 Enter ...
 
       (却针苑群蜚毹岩 EHS0411、叁牌求肄茄·
       群毓丈砒堍倾抢悌颦栎母·)
 
  诶嘻配缳妾秦辎溶诜仝如区嬉靴偏卒呢收、诶埔恻屿浠卮蜱破·纥容
  NetQuestion 气蜱、虽蛴墨〃
 
       type netq.cfg
 
  盆宴亦 NetQuestion 驮损祁嘻配缳妾秦辎·邱为诶呢收配缳妾秦辎、
  梭邱倾艳楝 DHCP 滔 DDNS 针、鞋蛴墨〃
 
       netqinit <data-path>
 
       Example:  netqinit c:\imnnq_nt\data
 
 
  HTML Search Server for Windows NT, Windows 95, and Windows Documentation H161
 
 
  20.4  尕劓区嬉 HTML 洳掾朔苡
 
  蕃狻〃尕劓区嬉 DB2 UDB 塄新逆些、洳掾朔苡埔恻佤畔·友佤畔
          洳掾朔苡、押摹亩≈怃填∽劈卒闲嘻 DB2 劈卒闲恸气你嘻
          "佤畔 HTML 洳掾腮韦鹇"·
 
  洳掾朔苡盆 DB2 UDB 塄新尕劓区嬉、抬散挝岩押摹亩≈怃填∽劈卒闲
  嘻 DB2 劈卒闲恸气你嘻 "尕劓区嬉"·
 
 
  20.4.1 邱为洳掾朔苡栖诜 WINDOWS NT。WINDOWS 95 托 WINDOWS 98
         尕劓区嬉
 
  邱为洳掾朔苡栖尕劓区嬉、抬韵寝页〃
 
  o   DB2 UDB 托贫摹远塄新七倾损祁洳掾朔苡、寝群嘁挝劓篇破·
 
  o   洳掾朔苡尕劓区嬉栖邱邕哝罪仝如·
 
  友刹鏊葬髓塄新捏倾洳掾朔苡你圄卮、铢圊砒亩悄淘棚〃
 
       NQMAP -A            //for SBCS
       TMMAP -A            //for DBCS
 
  邱为群淘棚栖惝沁嵌若啄趴、鞋纥摊抒 6·
 
  邱为群悄泣琵芍拟王 DB2 UDB 嘻啄趴 (签苫、抬秦辎怃螭拟岩 "DB2")、
  鞋劓篇洳掾腮韦鹇·
 
  邱为破却琵芍嵌若 DB2 啄趴篁秦 (DB2ADMxx。DB2APDxx。DB2CONxx)、
  鞋 DB2 UDB 嘁挝探旨圄卮啄趴、仍鹨映洳掾朔苡尕劓区嬉坡邗·邱为
  DB2 UDB 拟七睚尕劓区嬉、淠圊祈母虞谂拾 (梭邱、SQLLIB 骜砧设莘
  纱劓)·倾菡辍谂斡亩、诶埔恻琶侬探旨圄卮啄趴、虽损祁亩悄抒唆
  劓篇洳掾朔苡气蜱·
 
  1.  圊砒群淘棚、盆睚贴洳掾腮韦鹇七倾仝如〃
 
           IMNSS START SERVER          //for SBCS
           IMQSS.EXE -START DBCSHELP   //for DBCS
 
  2.  枳输摹远啄趴篁圊砒群淘棚〃
 
           NQMAP -D <index_name>       //for SBCS
           TMMAP -D <index_name>       //for DBCS
 
  3.  枳输摹远啄趴篁圊砒群淘棚〃
 
           NQDELET <index_name>        //for SBCS
           TMDELET <index_name>        //for DBCS
 
  4.  佤畔洳掾腮韦鹇〃
 
           IMNSS STOP SERVER           //for SBCS
           IMQSS.EXE -STOP DBCSHELP    //for DBCS
 
  5.  圊砒 "NQMAP -A" (托 "TMMAP -A") 虽属却昼亩嵌若 DB2 啄趴
      (DB2xxxxx)·邱为却、铢酊峋 IBM 韦侪末赞·
 
  6.  圊砒亩悄淘棚、唆嘁抬破啄趴倾散祁你·
 
           NQCOUNTI <search system directory>  //for SBCS
           TMCOUNTI <search system directory>  //for DBCS
 
  蕃狻〃邱为诶拟稀绗区嬉软弭、铢俣镥 20.2.3 "掾势洳掾朔苡气蜱"·
 
  o   邱为群淘棚惝沁嘻骜砧牙砒、却摹远托情远啄趴捏倾散祁你、鞋洳掾
      朔苡嘁挝劓篇、寝页抬破塄新捏倾圄卮你·铢纽仝如抬秕嘻抒·
 
  o   邱为洳掾朔苡惝沁 "0 啄趴散祁你"、铢仝如 UNINSTNQ.EXE·邱为洳
      掾朔苡捏栖尕劓区嬉、偏孳後盆琶侬派娶劓篇塄新〃
 
      1.  劓篇软王亩悄气蜱亩嘻圄卮圄蜱〃
 
               \\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\NetQuestion
 
          劓篇群圄蜱、琵涯抬驮却嘻耐气蜱·
 
      2.  劓篇洳掾朔苡嘻气蜱暖抬驮却耐气蜱 (梭邱、D:\IMNNQ_NT)·
 
      3.  劓篇艨韬戆 IMNINST 滔 IMNINSTSRV、虽诜 PATH 艨韬戆
          你劓篇洳掾朔苡纣绽·邱为捏栖尕劓区嬉洳掾朔苡、铢葙峋
          IBM 韦侪末赞·
 
 
  20.4.2 尕劓区嬉塄新靴屿浠怃瘼
 
  DB2 UDB 尕劓区嬉逆靴、倾仝如贫摹远区嬉逆些摹贴友屿浠怃瘼·韵
  寝岩却髓洳掾朔苡 DLL 淠莘散淦朔苡像昼、牺摊亩摹裙屿怃瘼针倪淠
  劓篇·邱为倾屿浠怃瘼逆些圊祈洳掾朔苡区嬉、鞋浠区嬉嘻洳掾朔苡
  DLL 衮倾亩摹裙屿怃瘼针莘纱劓、损塄祈嘻洳掾朔苡嘁挝损祁·
 
 
| 21.0  NETQUESTION 枰梭
 
 
| 21.1  倾 UNIX 仆坪母区嬉 IMNSEARCH (NETQUESTION) 嘻俾黝
 
| 倾衍髓艨韬你、强些区嬉托尕劓区嬉嘻 IMNSearch (NetQuestion) 镊堑
| 偏盆屿浠区嬉·鳇仍似逆、孚镊堑腈友却种直嘻损祁席 ID 暖妃苴 ID
| 秦辎、倪卒七睚区嬉·佧仍 (葑讦岩栖声抢劓篇 IMNSearch 针)、摹托抬
| 破嘻菡髓 ID 拟囚倾·倾抬破谂斡亩、却针苑损祁席属却驮腈嘻囚探、
| 仍嘁挝倾区嬉针恹沙氢喧恰菡髓妃苴 ID 暖损祁席 ID·菡胎辍谂斡葭岩寝
| 页嘁挝七睚区嬉 IMNSearch 镊堑驮葸醛嘻·
 
| 苌摹裙倾瘼鹇母区嬉 IMNSEARCH 针嘻俾黝
 
| 邱为诶倾区嬉 IMNSearch 镊堑针绮摊俾黝、仍赔诶拇属却区嬉些摹侮
| 嘻塄新、铢声抢劓篇孚镊堑逆靴、锹屿浠区嬉·铢蚊泗—菡琵涯强劓篇
| "imnadm" 损祁席 ID 暖妃苴 ID、锹屿浠区嬉·
 
| 倾呢区嬉托强些区嬉贫摹远 IMNSEARCH 镊堑嘻谂斡亩区嬉 IMNSEARCH 针、
| 绮摊俾黝
 
| 邱为诶倾区嬉 IMNSearch 镊堑针绮摊俾黝、仍赔诶呢区嬉魔杀嘻侮欺
| 嘻 IMNSearch 镊堑 (托绱篇咪区嬉绱破)、铢纽劓篇堍却嘻 IMNSearch
| 镊堑·
虐逆、铢篝宴亦亦岩闪却摹远秦辎页 imnadm 嘻妃苴 ID·邱为
| 却嘻驺、诶偏盆〃
 
| 1.  喧恰 imnadm 损祁席 ID、嘤靴屿浠区嬉 IMNSearch 镊堑
 
| 2.  纱劓 imnadm 妃苴 ID、嘤靴屿浠区嬉 IMNSearch 镊堑
 
| 倾 AFS/DCE 托 NIS/NIS+ 艨韬你区嬉 IMNSERACH 针绮摊俾黝
 
| 倾怩你戋堋损祁席 ID 暖妃苴 ID 嘻艨韬亩 (木摅岩氅、岂阪戋堋损
| 祁席倾腮韦鹇喧恰 ID、嘤靴锹拧厥孚 ID 骜毓摊诜谆瘼鹇)、损祁席
| 埔恻强喧恰 "imnadm"损祁席 ID 暖妃苴 ID、嘤靴锹区嬉 IMNSearch
| 喧恰镊堑·寝页损祁 IMNSearch 镊堑嘻驮却塄新葭淠橇祁菡髓损祁席 ID
| 暖妃苴 ID、驮盆友强仝如菡远抒、锹区嬉损祁孚镊堑嘻苌摹远塄新·
| 尕劓区嬉损祁 IMNSearch 镊堑嘻薏靴摹远塄新逆靴、鞋筌孚淠劓篇孚损祁
| 席 ID 暖妃苴 ID·
 
 
| 21.2  倾 HPUX-10 母区嬉 NETQUESTION
 
| 区嬉 DB2 Universal Database 侮欺 5.2 for HP-UX 10 针、诶偏卒淠
| 圊堍 NetQuestion 嘁挝诜塄新 CD-ROM 区嬉·诶淠圊堍诶孳璺洳掾 DB2
| 牌堑针、诶淠拳摊摹鞋 "腮韦鹇蛙岷葙罾" 嘻毓丈·铢篝宴亦亦诶岩闪
| 盆亩悄淘棚唆区嬉 NetQuestion〃
 
|      swlist -l product | grep -i imn
 
| 邱为属却惝沁嵌若毓丈、鞋闲泣烃栖区嬉 NetQuestion·
 
| 倾菡辍谂斡亩、诶埔恻盆琶侬派娶区嬉 NetQuestion·铢蚊泗—诶埔恻
| 邛侬、倪卒区嬉 NetQuestion·
 
| 铢衮痨远 "/NetQ" 气蜱诜区嬉 CD-ROM 你铒犒摊诶欺宋嘻帻轺你·铒犒
| 声醛逆靴、鞋诶欺軎嘻 "/NetQ/hpux10" 气蜱你筌孚却亩悄篁争〃
| "IMNSearch"。"IMNSearchB"。"IMNpkgadd"。"IMNpkgaddB"。"imnbinstall"
| 暖 "imninstall"·铢蛴墨〃
 
|      imninstall
 
| 邛侬 NetQuestion 区嬉 script·铢隧澌嚯域母牙泣、品区嬉 DBCS 洳掾
| 趴筱、托葭区嬉 SBCS 暖 DBCS 洳掾趴筱·
 
| 殛陉尕
 
| 邱为 "imninstall" 惝沁 "swcopy 坡邗、铢俣镥 swcopy 嘻琶侬喻域"
| 嘻蜚毹、鞋偏卒岩衍髓曦 DB2 拟肄嘻抬破篁争朔苡嘁挝嬉绁朔苡·
| 倾菡远谂斡亩、诶埔恻 (邛侬针) 衮亩悄蛸恸浠炝摊输摹远砒堍嘻
| "swcopy"。"swremove" 托 "swinstall"、唆罹蛞 "/NetQ/hpux10/IMNpkgadd"
| 嘻欺軎崖耸〃
 
|      -x mount_all_filesystems=false
 
|
 
 
| 21.3  UNIX 仆坪 嘻 NETQUESTION 暖 DB2 CAE
 
| 罾母牌堑托 NetQuestion 葭属却蝰厢倾 UNIX 塄新 CD (品芍却 Client
| Application Enabler) 母·嘤仍、邱为诜 EE 托 EEE 塄新 CD 区嬉 CAE、
| 鞋诶木偏盆蛸疱区嬉罾母牌堑¨倾区嬉孚牌堑针、淠溶侬区嬉 NetQuestion·
 
 
| 21.4  AIX 仆坪母嘻 NETQUESTION DBCS
 
| DB2 Universal Database 侮欺 5.2 for AIX 淠损祁 NetQuestion 麂
| 软镊苴求怩 (DBCS) 洳掾趴筱、叁邱为衍髓抬破煲裙嘻 NetQuestion
| 呢囚倾 AIX 散淦朔苡母、鞋破衮嘁挝七讦绐散·
 
| 梭邱、邱为攀牌。雩牌。鳇你牌托繇你牌嘻 DB2 UDB V5.2 岩区嬉
| 倾呢区嬉却 VisualAge C++ Professional 侮欺 4.0 for AIX 逆 DBCS
| 牌堑嘻嵌若 AIX 散淦朔苡母、托邱为破呢区嬉倾呢区嬉却 DBCS 欺傧尕
| 氅嘻 AIX 4.3 散淦朔苡母、鞋诶衮嘁挝损祁 NetQuestion、唆洳掾嵌若
| 呢区嬉嘻 DB2 DBCS 牌堑·菡远俾黝岩寝页抬破 NetQuestion 怃圊嘻塄
| 新驮损祁嘻洳掾 CGI 曦 DB2 UDB 侮欺 5.2 for AIX 蝰厢嘻洳掾 CGI 拟
| 肄诈·
 
| 友收七菡远俾黝针、诶埔恻仝如亩悄抒、盆收浠嘻洳掾 CGI 唆弭咝
| "/var/docsearch/cgi-bin/" 暖 "/usr/docsearch/cgi-bin/" 你嘻洳
| 掾 CGi〃
 
| 1.  诜亩悄杲蛇亩绁收浠嘻洳掾 CGI (辎逆页 "db2srdbcs") 摊
      "/var/docsearch/cgi-bin" 暖 "/usr/docsearch/cgi-bin"〃
 
|          ftp.software.ibm.com/ps/products/db2/info
 
|     菡淠恃煅菡髓气蜱你堍囚嘻 "db2srdbcs" 篁争·
 
| 2.  佤畔暖邛侬 DB2 DBCS 洳掾趴筱、菡远收倪淠祈真、邱亩〃
 
|     o   友佤畔洳掾趴筱针、铢蛴墨〃
 
|              usr/IMNSearch/bin imqss -stop dbcshelp.
 
|     o   友邛侬洳掾趴筱针、铢蛴墨〃
 
|              usr/IMNSearch/bin imqss -start dbcshelp.
 
 
  22.0  SCOHELP 骜毓
 
 
  呷蓑魔亩悄 SCOhelp 骜毓〃
 
  o   22.1, "邱若囚探 SCOhelp"
  o   22.2, "损祁傧榨耄似滔 SCOhelp"
  o   22.3, "Web 谡瘫你爬尕氅滔 SCOhelp".
  o   22.4, "Support Level Supplement (SLS) PTF7004A, the UnixWare 7 Language
      Extension Supplement".
 
 
  22.1  邱若囚探 SCOHELP
 
  诶偏沙祁亩悄摹辍派娶唆囚探 SCOhelp〃
 
  o   诜淘棚如〃倾淘棚如圊砒淘棚 "scohelp" (/usr/bin/X11/scohelp)·

 
  o   诜 CDE 证母戋堋幔娶〃怃邛 "尕氅" 劈卒闲 (倾谡瘫坪嘻尕氅
      璺泣母派)、嘤靴蛸探 SCO 尕氅·
 
  o   诜 Panorama 证母戋堋幔娶〃怃邛 "Root" 劈卒闲、嘤靴蛸探
      ≈尕氅∽·
 
 
  22.2  损祁傧榨耄似滔 SCOHELP
 
 
  22.2.1  损祁乳州袍耄似瞿膨针嘻种直扔庳
 
  抬你、"UnixWare 7 Update 1 (7.0.1)" CD-ROM 呷蓑魔≈乳州袍耄似
  瞿膨∽(esle) 嘻院七幔娶· 亩悄 DB2 幔施倾 LANG 菝贴页 "es" 针
  拟淠散祁、劓湘区嬉魔 UnixWare 7 Update 1〃
 
  o   喧恰争梭 (摹罪托 DAS 争梭)〃页魔友踱森菡远俾黝、铢倾喧恰
      争梭逆些强衮 LANG 菝贴页 "en" 托 "C"、嘤靴倾喧恰孚争梭针、
      锹衮破菝沁 "es"· 菡木闲泣邱为衮 LANG 菝页 "es" 嘻驺、诶嘁
      挝损祁 DB2 区嬉幔娶 (db2setup) 唆喧恰争梭·
 
  o   仝如 db2ishut 淘棚·锹席、页魔友踱森菡远俾黝、铢倾仝如
      DB2ishut 逆些强衮 LANG 菝贴页 "en" 托 "C"、嘤靴倾破声醛针、
      锹衮破菝沁 "es"·
 
  o   仝如 db2istrt: 群淘棚岩祁唆邛侬 DB2 腮韦鹇、仍赔岩岂
      /etc/rc.db2 script 趟频嘻·喧恰苌摹远争梭针、亩悄菡摹如
      倾闹散谆屿浠邛侬针淠浠炝摊 /etc/inittab 篁争你、唆溶侬
      邛侬 DB2 韦侪幔娶〃
 
           db:234:once:/etc/rc.db2 > /dev/console 2>&1 # Autostart DB2 Services
 
  邱为 LANG 嘻邕菝垣页 "es"、筌孚衮 /etc/inittab 篁争你嘻菡摹如
  砗页蕃狻·屿浠邛侬声醛针、铢盆 root 嘻宋枪圄墨、嘤靴衮 LANG 菝
  贴页 "en" 托 "C"、锹仝如 /etc/rc.db2·铢倾 DB2 邛侬逆靴、衮
  LANG 菝沁 "es"·
 
  铢蚊泗〃呢区嬉 UnixWare 7 Update 1 唆院七≈乳州袍耄似瞿膨∽嘻
  俾黝针、菡髓俾黝摅淠旨坡·诶筌孚倾 etc/inittab 篁争你探旨菡摹
  如嘻蕃狻 (uncomment out)、盆享 DB2 韦侪幔娶淠倾亩摹裙屿浠邛侬
  针溶侬邛侬〃
 
       db:234:once:/etc/rc.db2 > /dev/console 2>&1 # Autostart DB2 Services
 
 
  22.2.2  倾腮韦鹇母收邕菝 SCOHELP 耄似
 
  邱为泖友倾腮韦鹇母收 SCOhelp 拯疸邕菝垣惝沁嘻耄似、铢罹蛞
  /usr/ns-home/httpd-scohelphttp/config/lang.conf、虽菝贴
  DocumentRoot 页驮友嘻邕菝耄似·梭邱〃
 
       DocumentRoot /usr/lib/scohelp/fr
 
  摹瀑收、摅埔恻盆亩悄淘棚屿浠邛侬 web 腮韦鹇〃
 
       /usr/ns-home/httpd-scohelphttp/restart
 
  邱为菡淼伉嘁真、鞋孳後佤畔 web 腮韦鹇、嘤靴盆亩悄淘棚屿浠邛侬破〃

 
       /usr/ns-home/httpd-scohelphttp/stop
       /usr/ns-home/httpd-scohelphttp/start
 
 
  22.2.3  菝贴 SCOHELP 剀枳种贴诜谆惝沁嘻耄似
 
  拟茄诜谆偏盆 SCOhelp 盆拟茄耄似惝沁骜毓·
 
  SCOhelp 腮韦鹇损祁 *httpAcceptLanguage 骜溷、唆暑贴倾谫拳友叔
  针友损祁葬摹辍耄似·诶偏盆隧亩悄派娶、衮 *httpAcceptLanguage
  菝贴醛驮腈嘻耄似〃
 
  o   Netscape 3〃罹蛞 Netscape app-defaults 篁 (畀梭逆摹软王
      /usr/X/lib/app-defaults) 虽披墨群如〃
 
           *httpAcceptLanguage: fr, en
 
  o   Netscape 4〃蛸探≈罹蛞∽劈卒闲恸气、嘤靴蛸≈夼秋菝贴∽·
      诜瘗雾篝狺嚯域你蛸探≈鹨趴鹇∽、嘤靴蛸≈耄似∽·浠炝驮腈
      嘻耄似、虽睚贴破软王悄泣你苌摹远软弭·

 
  邱为苫损菝贴 *httpAcceptLanguage 、SCOhelp 捏泣恿牌嘻驺、孳
  後诜悄泣你劓篇恿牌·
 
 
  22.2.4  损祁洳掾
 
  蚊泗、鳇你牌滔呕乳婀犭袍耄属却洳掾劈卒·
 
  诶偏盆押摹亩 SCOhelp 洳掾嚯域母嘻≈蛸恸∽押廒、唆蛸探友洳掾
  嘻情辍耄似·淠泣砒呢区嬉嘻耄似悄泣¨铢蛸探友洳掾嘻耄似苴·
 
 
  22.3  WEB 谡瘫你爬尕氅滔 SCOHELP
 
  Web 谡瘫你爬尕氅滔 DB2 阵逆怄属却牺谫岣 (损祁 SCOhelp 泣)·
  损祁 22.1 ≈邱若囚探 SCOhelp∽驮呃虞嘻派挝逆摹、唆仝如 SCOhelp
  暖囚探 DB2 阵·
 
  SCO DB2 Web 谡瘫你爬尕氅属却洳掾劈卒·
 
 
  22.4  SUPPORT LEVEL SUPPLEMENT (SLS) PTF7004A, UNIXWARE 7 LANGUAGE
  EXTENSION SUPPLEMENT
 
  "Support Level Supplement (SLS) PTF7004A" 偏诜亩悄 SCO FTP
  谆坪探诘〃
  ftp://ftp.sco.com/SLS/ Download the files ptf7004a.Z and
  ptf7004a.txt
 
  PTF7004A "SCOhelp 涅 Verity 洳掾趴筱嘻艳楝俾黝、盆暖侵辍狞祁
  幔娶滔 SCOadmin 戋堋幔娶嘻欺娜脓俾黝·" 邱为诶友篝狺 DB2 牌堑、
  鞋腈友区嬉群 SLS·王孥茇骜毓、铢俣镥 ptf7004a.txt·
 
 
  22.4.1  院恃鳇你牌滔呕乳婀犭袍耄嘻 LANG.CONF
 
  摹瀑区嬉魔 PTF7004A、倾诶盆鳇你牌托呕乳婀犭袍耄唆损祁 SCOhelp
  逆些、埔恻强罹蛞 /usr/ns-home/httpd-scohelphttp/config/lang.conf
  篁争、伉亩悄收〃

 
  1.  院恃 LocalizedDocRoot 悄泣你嘻亩悄胎如、虽浠炝 "_BR" 滔
      "_CN" 摊裙气蜱秦辎岣盛、邱亩驮泣〃
 
           LocalizedDocRoot pt_PT.ISO8859-1 /usr/lib/scohelp/pt_BR
           LocalizedDocRoot zh_ZH.ISO8859-1 /usr/lib/scohelp/zh_CN
 
  2.  院恃 zh 嘻侵辍耄似杀秦〃睚贴 zh 嘻侵辍耄似杀秦却枳研摊
      zh_ZH.ISO8859-1 (zh 滔 ZH 逆怄岩偷罾、拟岩注仕胬)·菡摭
      如嘻涅诈邱亩〃
 
            LanguageAlias zh zh_ZH.ISO8859-1
 
      群垣苁琴群如〃
 
            LocalizedDocRoot zh_ZH.ISO8859-1 /usr/lib/scohelp/zh_CN
 
  伉魔菡髓收逆靴、铢隧澌苌 170 喻母嘻 22.2.2, "倾腮韦鹇母收邕菝
  SCOhelp 耄似∽驮虞、唆屿浠邛侬 (托佤畔靴邛侬) web 腮韦鹇·
 
 
  22.5  SCOHELP 洳掾啄趴篁争
 
  SCOhelp 衮驮却洳掾啄趴篁争竺囚倾
  /usr/lib/scohelp/<lang>/_SearchIndex/parts 气蜱你·
 
  菡髓篁争嘻乃难衮蝰後诶区嬉塄新仍瞿乃、叁拟淠蝰後诶劓篇
  塄新仍难 (损祁堍如 UnixWare 7 狞祁幔娶)·菡辍谂斡锼祁王
  DB2 滔抬破塄新·
 
  邱为诶纱劓菡髓篁争、鞋 SCOhelp 洳掾劈卒淠坡真·