¦¸Ý÷¦`úNù’ôæ

IBM(R) DB2(R) Universal Database
¦¸Ý÷¦`úNù’ôæ

¦¸¾¯ 7.2 / ¦¸¾¯ 7.1 FixPak 3

(C) Copyright International Business Machines Corporation 2000, 2001. All
rights reserved.
Note to U.S. government Users -- Documentation related ...
  ------------------------------------------------------------------------

¾¨ì

   * ¾¨ì

   * w¦‹ùØ¾× DB2 Universal Database ¦¸¾¯ 7­I

  ------------------------------------------------------------------------

îSõO¯í¦ó

   * îSõO¯í¦ó
        o 1.1 DB2 UDB ¦¸¾¯ 7 ¦§Ýsù£îS¸Ò
             + 1.1.1 µ„«LÏõ¨‚ÏJ¸MóÏè
                  + 1.1.1.1 µ„«L¨‚ÏJ
                  + 1.1.1.2 µ„«LæJ¶I
             + 1.1.2 ÏŠ®KÆ¾šîS¸Ò
                  + 1.1.2.1 ¸£Æû‹úà¬ãÝ­
                  + 1.1.2.2 Ýr®ªü]¸wðÔ
                  + 1.1.2.3 æLÇ”ÇCÝƒ
             + 1.1.3 ¨‹óšÝ­Žæõiïœ¾š
             + 1.1.4 Ï„ï¸õèüN¦§ªê©e¸Ò
             + 1.1.5 ¾iÝsù£¦§Ï†¾¢
        o 1.2 ¦ç¾[¦§¾ýðn Solaris ðž÷¬hÝ÷
        o 1.3 Supported CPUs on DB2 Version 7 for Solaris
        o 1.4 ús¬W÷`¶IÝšÏ·ü×÷ˆ©’©w¦§øíÇD
        o 1.5 ýó¶…ïµô­æo¾Ö¦§¨—¯~
        o 1.6 Red Flag Linux ¦§ÏÏÏ†¯yù¾·“ûãðž¾¨æ{Ý­
        o 1.7 Ýp¦G¾iýóøœÝ­§Ø§Ñóö¾¬üsñæ­A®h DB2 Ýw÷Óú|ÏÏ¶_
        o 1.8 Ï‚Ï†¸M¶ý‚ÏÏÏ† Linux ·“ûãÏõ DB2 for Linux ¦§¦ç¾[¯yù¾·“ûãü]¸w
        o 1.9 Microsoft Internet Explorer ÏW¦§ññùŒÏÏÏáøíÇD
        o 1.10 Ýb Windows ·“ûãÏÏ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏ× Sybase Ïõô­¦§Ïœªê©e
        o 1.11 ññùŒÏÏÏá¾\î…ªy¾½
        o 1.12 Netscape CD Ïœ·H¦ç¸¢ DB2 UDB
        o 1.13 XML Readme ·¦§¨—¯~
        o 1.14 Linux for S/390 ÏW¾iî…¦§÷ˆ©’ªy¾½
        o 1.15 Windows 2000 ÏW¦§ DB2 UDB

   * «uÏWÏ†¾¢ (HTML­BPDF ¯P­uújïM­v)
        o 2.1 Windows 2000 õ@ú~ùtý×¸ãÏ„ï¸¦§ Web ¶sŽìóû
        o 2.2 Ýb Solaris ùtý×ÏUújïM DB2 üs«u÷ˆøT
        o 2.3 Ïµï® NetQuestion for OS/2 ¾HùØ¾× TCP/IP
        o 2.4 ñãøÒ Netscape ©ýœ¾Ö¦§¨—¯~øT©õ
        o 2.5 UNIX ùtý×ÏW Adobe Acrobat Reader ¦§ª[§c¯íùD
        o 2.6 SQL Reference ôÔïœù¥Ï@ðà PDF ·

  ------------------------------------------------------------------------

Ýw÷Ó¯Pª[§c

   * Ï@î‰Ýw÷Ó÷ˆøT
        o 3.1 ÏU÷¸ãÝüÏ„ï¸¦§ DB2 ñqŽíî÷¦§Ýw÷Ó©M¾¢
        o 3.2 Ýb Windows 2000 ÏWÝw÷Ó DB2
        o 3.3 Ç”¸¢úõýÏ¦¡¾HîSõO¬ÔÝsøØ¸w÷q¦§ýó¶…øíÇD
        o 3.4 Windows 2000 ¦§ IPX/SPX üq®Hù¢¸wÏ„ï¸
        o 3.5 Ïî DB2 ®eÏ@¦¸Ïõ®e¾ìøñÏŒ DB2 æ{õ€
        o 3.6 ðYÏwÝw÷Óù„¾Ý DB2 ýœ®~­A«ÑÝbÝw÷Ó DB2 Ïõ® øäÝ‘ db2iupdt
        o 3.7 ü]¸w Linux ·“ûã¾HøäÝ‘ DB2 ññùŒÏÏÏá
        o 3.8 DB2 Universal Database Enterprise Edition Ï× DB2 Connect
          Enterprise Edition for Linux on S/390
        o 3.9 DB2 Universal Database Enterprise - Extended Edition for UNIX
          õ™ütÏJ¦—
        o 3.10 HP-UX ¦§ shmseg ©™Ïáø¥¬’
        o 3.11 ýó¶… IBM Visual ðš·xññùŒ÷ˆ©’©w
        o 3.12 Ýsù£ðš·xññùŒ÷ˆ©’©w

   * DB2 Data Links Manager õ™ütÏJ¦—
        o 4.1 Dlfm ¦§ñãøÒ¾½ñ¥øT©õ­Gù£ño afsfid Ýrð§©æo¾Ö¨—¯~
        o 4.2 ü]¸wü’¾ö®OÝs·¦§ Tivoli Storage Manager ÇçõO
        o 4.3 DFS ñqŽíî÷ñãøÒæ{Ý­¦§§Ø§Ñ¦ô­¯íùD
        o 4.4 §ÒúçÝb AIX ¦§÷ˆ©’Çæý·©ž§èýzæ{Ý­® §íæ{õ€
        o 4.5 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G DCE-DFS ·“ûã÷Þ¦§
          ÇB¾~Ýw÷Ó¦`úNù’ôæ
        o 4.6 ¾½ñ¥¦§ "dlfm add_prefix" ®¾O
        o 4.7 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G ùØ¾× db2setup Ï«
          ¾×æ{Ý­Ýb AIX ÏWÝw÷Ó DB2 Data Links Manager
        o 4.8 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­GDCE-DFS ® ÷mÝw÷Óõ@
          ú~
        o 4.9 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G ùØ¾× Smit ùàÏƒøÒ
          Ýw÷Ó DB2 Data Links Manager
        o 4.10 Ýw÷Ó¸Mª[§c DB2 Data Links ¦§ DFS ñqŽíî÷ñãøÒæ{Ý­
        o 4.11 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for Solaris
        o 4.12 øwû‹ AIX ÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ¦k
        o 4.13 øwû‹ Solaris õ@ú~·“ûãÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ
          ¦k
        o 4.14 øwû‹ Windows NT ÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ¦k
        o 4.15 ü’¾ö AIX ÏW¦§øO¨ì·©žùtý×
        o 4.16 Ýb Windows NT ÏW÷ˆ©’ÇæýÏÏ¦§ Administrator ÷sýåñM¾×v
        o 4.17 ñN Data Links File System Filter (DLFF) Ýw÷Ó¦§øO÷ïŒùüÞÏ™
             + 4.17.1 ÝbÝw÷Ó® øO÷øT©õ
        o 4.18 ùØ¾× SMIT ÷¥øœÝw÷Ó DLFM Ï÷¾¢¾iî…ú|øœ¾hÇB¾~¦§·©žôø
        o 4.19 ô}¸lÏõ®e/ùM¸w¾Dûq÷œÝW§ë
        o 4.20 ùØ¾× DLFM­Gñq DB2 ÷ˆ©’©wñÓñ¢ DB2 Data Links Manager ® ¦§ýMøœ
          øÒõ@
        o 4.21 DLFM1001E (ús¦§¨—¯~øT©õ)
        o 4.22 DLFM ü]¸wª[§c·¨‹ôæ
        o 4.23 Ýb AIX ÏWøäÝ‘ Data Links/DFS Script dmapp_prestart ©æo¾Ö¨—
          ¯~
        o 4.24 Tivoli Space Manager ¯P Data Links óÆÝX
             + 4.24.1 ¾\î…ððùŒ
        o 4.25 ýŽ 4 üû Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX
             + 4.25.1 Ï@î‰Ýw÷Ó¦`úNù’ôæ
                  + 4.25.1.1 ñq DB2 File Manager ¦¸¾¯ 5.2 ýó¶…ù DB2 Data
                    Links Manager ¦¸¾¯ 7

   * Ýw÷Ó¯Pª[§c÷¾R÷ˆ©’
        o 5.1 ýŽ 5 üû Ýb UNIX õ@ú~ùtý×ÏWÝw÷Ó DB2 ñqŽíî÷
             + 5.1.1 HP-UX ©™Ïáæ{Ý­ª[§cø¥¬’
        o 5.2 ýŽ 12 üû øäÝ‘ñzÝêÏv¦§·ü¾×æ{Ý­
             + 5.2.1 ùØ¾× Run-Time Client üsæý÷ˆ©’©wÏ«¾×æ{Ý­
             + 5.2.2 UNIX ñqŽíî÷ùØ¾× ODBC Ýsù£ DB2
        o 5.3 ýŽ 24 üû ü]÷mµpÝXùtý×ùàÝsù£Ýhð®÷ˆ©’ùàú«
             + 5.3.1 µpÝXùtý×
                  + 5.3.1.1 ððùŒ
             + 5.3.2 Ýw÷Ó DB2 Relational Connect
                  + 5.3.2.1 Ýb Windows NT Ý›¦AóûÏWÝw÷Ó DB2 Relational
                    Connect
                  + 5.3.2.2 Ýb AIX­BLinux Ï× Solaris õ@ú~·“ûãÝ›¦AóûÏWÝw÷Ó
                    DB2 Relational Connect
        o 5.4 ýŽ 26 üû Ýsù£ Oracle ÷ˆ©’ùàú«
             + 5.4.1 Ï†¾¢¨—¯~
        o 5.5 Ýsù£ Sybase ÷ˆ©’ùàú« (ús¬Wüû÷`)
             + 5.5.1 ús¬W Sybase ÷ˆ©’ùàú«ÝšµpÝXÝ›¦Aóû
                  + 5.5.1.1 ùB’J 1­Gü]¸w·“ûãš¬’ùÇõ¢úsü]¸w·æn¨ì
                  + 5.5.1.2 ùB’J 2­GñN DB2 ÇæýÝš Sybase ñqŽíî÷ün‚ (ôÔ AIX
                    ¯P Solaris)
                  + 5.5.1.3 ùB’J 3­Gð®úsùØ¾× DB2 ©žùã
                  + 5.5.1.4 ùB’J 4­G®¾áùÇü]¸wÏôðñ·©ž
                  + 5.5.1.5 ùB’J 5­G®¾á¾~¬h
                  + 5.5.1.6 ùB’J 6­G¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’
                  + 5.5.1.7 ùB’J 7­G®¾áÝ›¦Aóû
                  + 5.5.1.8 ¨‹¾×¦§­GùB’J 8­Gü]¸w CONNECTSTRING Ý›¦Aóû¨‹ôæ
                  + 5.5.1.9 ùB’J 9­G®¾áùØ¾×¦Þû‹ªM
                  + 5.5.1.10 ùB’J 10­G®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW
             + 5.5.2 ®¸w Sybase Ýr«Xðô
        o 5.6 ùØ¾× ODBC Ýsù£ Microsoft SQL Server ÷ˆ©’ùàú« (ús¬Wüû÷`)
             + 5.6.1 ús¬W Microsoft SQL Server ÷ˆ©’ùàú«ÝšµpÝXÝ›¦Aóû
                  + 5.6.1.1 ùB’J 1­Gü]¸w·“ûãš¬’ (ôÔ AIX)
                  + 5.6.1.2 ùB’J 2­GøäÝ‘ Shell Script (ôÔ AIX)
                  + 5.6.1.3 ùB’J 3­G¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’
                  + 5.6.1.4 ùB’J 4­Gð®úsùØ¾× DB2 ©žùã (ôÔ AIX)
                  + 5.6.1.5 ùB’J 5­G®¾á¾~¬h
                  + 5.6.1.6 ùB’J 6­G®¾áÝ›¦Aóû
                  + 5.6.1.7 ùB’J 7­G®¾áùØ¾×¦Þû‹ªM
                  + 5.6.1.8 ùB’J 8­G®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW
                  + 5.6.1.9 ùB’J 9­G¨‹¾×¦§­G·•ño ODBC øl¶š
             + 5.6.2 «’ªd Microsoft SQL Server Ýr«Xðô

  ------------------------------------------------------------------------

§èýz

   * Administration Guide: Planning (æLÏÏÏ†¦¸)
        o 6.1 Chapter 8. Physical Database Design
             + 6.1.1 Partitioning Keys
        o 6.2 Designing Nodegroups
        o 6.3 Chapter 9. Designing Distributed Databases
             + 6.3.1 Updating Multiple Databases
        o 6.4 Chapter 13. High Availability in the Windows NT Environment
             + 6.4.1 Need to Reboot the Machine Before Running DB2MSCS
               Utility
        o 6.5 Chapter 14. DB2 and High Availability on Sun Cluster 2.2
        o 6.6 Veritas Support on Solaris
        o 6.7 Appendix B. Naming Rules
             + 6.7.1 Notes on Greater Than 8-Character User IDs and Schema
               Names
             + 6.7.2 User IDs and Passwords
        o 6.8 Appendix D. Incompatibilities Between Releases
             + 6.8.1 Windows NT DLFS Incompatible with Norton's Utilities
             + 6.8.2 SET CONSTRAINTS Replaced by SET INTEGRITY
        o 6.9 Appendix E. National Language Support
             + 6.9.1 National Language Versions of DB2 Version 7
                  + 6.9.1.1 Control Center and Documentation Filesets
             + 6.9.2 Locale Setting for the DB2 Administration Server
             + 6.9.3 DB2 UDB Supports the Baltic Rim Code Page (MS-1257) on
               Windows Platforms
             + 6.9.4 Deriving Code Page Values
             + 6.9.5 Country Code and Code Page Support
             + 6.9.6 Character Sets

   * Administration Guide: Implementation(æLÏÏÏ†¦¸)
        o 7.1 Adding or Extending DMS Containers (New Process)
        o 7.2 Chapter 1. Administering DB2 using GUI Tools
        o 7.3 Chapter 3. Creating a Database
             + 7.3.1 Creating a Table Space
                  + 7.3.1.1 Using Raw I/O on Linux
             + 7.3.2 Creating a Sequence
             + 7.3.3 Comparing IDENTITY Columns and Sequences
             + 7.3.4 Creating an Index, Index Extension, or an Index
               Specification
        o 7.4 Chapter 4. Altering a Database
             + 7.4.1 Adding a Container to an SMS Table Space on a
               Partition
             + 7.4.2 Altering an Identity Column
             + 7.4.3 Altering a Sequence
             + 7.4.4 Dropping a Sequence
             + 7.4.5 Switching the State of a Table Space
             + 7.4.6 Modifying Containers in a DMS Table Space
        o 7.5 Chapter 5. Controlling Database Access
             + 7.5.1 Sequence Privileges
             + 7.5.2 Data Encryption
        o 7.6 Chapter 8. Recovering a Database
             + 7.6.1 How to Use Suspended I/O
             + 7.6.2 Incremental Backup and Recovery
                  + 7.6.2.1 Restoring from Incremental Backup Images
             + 7.6.3 Parallel Recovery
             + 7.6.4 Backing Up to Named Pipes
             + 7.6.5 Backup from Split Image
             + 7.6.6 On Demand Log Archive
             + 7.6.7 Log Mirroring
             + 7.6.8 Cross Platform Backup and Restore Support on Sun
               Solaris and HP
             + 7.6.9 DB2 Data Links Manager Considerations/Backup Utility
               Considerations
             + 7.6.10 DB2 Data Links Manager Considerations/Restore and
               Rollforward Utility Considerations
             + 7.6.11 Restoring Databases from an Offline Backup without
               Rolling Forward
             + 7.6.12 Restoring Databases and Table Spaces, and Rolling
               Forward to the End of the Logs
             + 7.6.13 DB2 Data Links Manager and Recovery Interactions
             + 7.6.14 Detection of Situations that Require Reconciliation
        o 7.7 Appendix C. User Exit for Database Recovery
        o 7.8 Appendix D. Issuing Commands to Multiple Database Partition
          Servers
        o 7.9 Appendix I. High Speed Inter-node Communications
             + 7.9.1 Enabling DB2 to Run Using VI

   * Administration Guide: Performance (æLÏÏÏ†¦¸)
        o 8.1 Chapter 3. Application Considerations
             + 8.1.1 Specifying the Isolation Level
             + 8.1.2 Adjusting the Optimization Class
             + 8.1.3 Dynamic Compound Statements
        o 8.2 Chapter 4. Environmental Considerations
             + 8.2.1 Using Larger Index Keys
        o 8.3 Chapter 5. System Catalog Statistics
             + 8.3.1 Collecting and Using Distribution Statistics
             + 8.3.2 Rules for Updating Catalog Statistics
             + 8.3.3 Sub-element Statistics
        o 8.4 Chapter 6. Understanding the SQL Compiler
             + 8.4.1 Replicated Summary Tables
             + 8.4.2 Data Access Concepts and Optimization
        o 8.5 Chapter 8. Operational Performance
             + 8.5.1 Managing the Database Buffer Pool
             + 8.5.2 Managing Multiple Database Buffer Pools
        o 8.6 Chapter 9. Using the Governor
        o 8.7 Chapter 13. Configuring DB2
             + 8.7.1 Sort Heap Size (sortheap)
             + 8.7.2 Sort Heap Threshold (sheapthres)
             + 8.7.3 Maximum Percent of Lock List Before Escalation
               (maxlocks)
             + 8.7.4 Configuring DB2/DB2 Data Links Manager/Data Links
               Access Token Expiry Interval (dl_expint)
             + 8.7.5 MIN_DEC_DIV_3 Database Configuration Parameter
             + 8.7.6 Application Control Heap Size (app_ctl_heap_sz)
             + 8.7.7 Database System Monitor Heap Size (mon_heap_sz)
             + 8.7.8 Maximum Number of Active Applications (maxappls)
             + 8.7.9 Recovery Range and Soft Checkpoint Interval (softmax)
             + 8.7.10 Track Modified Pages Enable (trackmod)
             + 8.7.11 Change the Database Log Path (newlogpath)
             + 8.7.12 Location of Log Files (logpath)
             + 8.7.13 Maximum Storage for Lock List (locklist)
        o 8.8 Appendix A. DB2 Registry and Environment Variables
             + 8.8.1 Table of New and Changed Registry Variables
        o 8.9 Appendix C. SQL Explain Tools

   * Administering Satellites Guide and Reference(æLÏÏÏ†¦¸)
        o 9.1 Setting up Version 7.2 DB2 Personal Edition and DB2 Workgroup
          Edition as Satellites
             + 9.1.1 Prerequisites
                  + 9.1.1.1 Installation Considerations
             + 9.1.2 Configuring the Version 7.2 System for Synchronization
             + 9.1.3 Installing FixPak 2 or Higher on a Version 6
               Enterprise Edition System
                  + 9.1.3.1 Upgrading Version 6 DB2 Enterprise Edition for
                    Use as the DB2 Control Server
             + 9.1.4 Upgrading a Version 6 DB2 Control Center and Satellite
               Administration Center

   * Command Reference(æLÏÏÏ†¦¸)
        o 10.1 db2batch - Benchmark Tool
        o 10.2 db2cap (new command)
             + db2cap - CLI/ODBC Static Package Binding Tool
        o 10.3 db2ckrst (new command)
             + db2ckrst - Check Incremental Restore Image Sequence
        o 10.4 db2gncol (new command)
             + db2gncol - Update Generated Column Values
        o 10.5 db2inidb - Initialize a Mirrored Database
        o 10.6 db2look - DB2 Statistics Extraction Tool
        o 10.7 db2updv7 - Update Database to Version 7 Current Fix Level
        o 10.8 New Command Line Processor Option (-x, Suppress printing of
          column headings)
        o 10.9 True Type Font Requirement for DB2 CLP
        o 10.10 ADD DATALINKS MANAGER
        o 10.11 ARCHIVE LOG (new command)
             + Archive Log
        o 10.12 BACKUP DATABASE
             + 10.12.1 Syntax Diagram
             + 10.12.2 DB2 Data Links Manager Considerations
        o 10.13 BIND
        o 10.14 CALL
        o 10.15 DROP DATALINKS MANAGER (new command)
             + DROP DATALINKS MANAGER
        o 10.16 EXPORT
        o 10.17 GET DATABASE CONFIGURATION
        o 10.18 GET ROUTINE (new command)
             + GET ROUTINE
        o 10.19 GET SNAPSHOT
        o 10.20 IMPORT
        o 10.21 LIST HISTORY
        o 10.22 LOAD
        o 10.23 PING (new command)
             + PING
        o 10.24 PUT ROUTINE (new command)
             + PUT ROUTINE
        o 10.25 RECONCILE
        o 10.26 REORGANIZE TABLE
        o 10.27 RESTORE DATABASE
             + 10.27.1 Syntax
             + 10.27.2 DB2 Data Links Manager Considerations
        o 10.28 ROLLFORWARD DATABASE
        o 10.29 Documentation Error in CLP Return Codes

   * Data Movement Utilities Guide and Reference(æLÏÏÏ†¦¸)
        o 11.1 Chapter 2. Import
             + 11.1.1 Using Import with Buffered Inserts
        o 11.2 Chapter 3. Load
             + 11.2.1 Pending States After a Load Operation
             + 11.2.2 Load Restrictions and Limitations
             + 11.2.3 totalfreespace File Type Modifier
        o 11.3 Chapter 4. AutoLoader
             + 11.3.1 rexecd Required to Run Autoloader When Authentication
               Set to YES

   * Replication ®®n¯Pø¥ÝãÏƒ¾U
        o 12.1 õê¬gÏ×®D IBM Ý›¦Aóû
        o 12.2 Ýb Windows 2000 ÏW¦§õê¬g
        o 12.3 ·xÝs SQL ·©ž©¦§Ïw¦ó¨—¯~
        o 12.4 DB2 §–@
        o 12.5 Web ÏW¦§ Data Difference Utility
        o 12.6 ýŽ 3 üû ÷ˆ©’õê¬gûˆøÔ«dùã
             + 12.6.1 õê¬gûˆøÔ
        o 12.7 ýŽ 5 üû õê¬güWû§
             + 12.7.1 ¦¡©‘Ï×¦«Ž‘ÝW§ë
             + 12.7.2 DATALINK õê¬g
             + 12.7.3 LOB ððùŒ
             + 12.7.4 üWû§õê¬g
        o 12.8 ýŽ 6 üû ü]¸wõê¬g·“ûã
             + 12.8.1 ·HüBõ¢ús (Update-anywhere) ¾ìùMñ›¾¢
             + 12.8.2 ü]¸wõê¬g·“ûã
        o 12.9 ýŽ 8 üû øíÇDõP¶_
        o 12.10 ýŽ 9 üû AS/400 ¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­
        o 12.11 ýŽ 10 üû OS/390 ¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­
             + 12.11.1 DB2 DataPropagator for OS/390 ¦§¾ìùMñ›¾¢
             + 12.11.2 OS/390 ÏW¦§ UNICODE ¸M ASCII «s«XÏŠ¦k
                  + 12.11.2.1 ¨‹óš«s«XÏŠ¦k
                  + 12.11.2.2 ü]¸w«s«XÏŠ¦k
        o 12.12 ýŽ 11 üû UNIX ¾ð¾x¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­
             + 12.12.1 Ýb UNIX ¸M Windows ÏWü]¸w­u¶^ù£æ{Ý­­v¸M­uÏè¾×æ{Ý­­v
               ¦§·“ûãš¬’
        o 12.13 ýŽ 14 üû ¦¡©‘æý§c
        o 12.14 ýŽ 15 üû ¶^ù£æ{Ý­¸MÏè¾×æ{Ý­øT©õ
        o 12.15 ¦ç¨ì A. ñq·ü¾×æ{Ý­Ï§ñãøÒ¶^ù£æ{Ý­¸MÏè¾×æ{Ý­

   * System Monitor Guide and Reference(æLÏÏÏ†¦¸)
        o 13.1 db2ConvMonStream

   * Troubleshooting Guide(æLÏÏÏ†¦¸)
        o 14.1 Starting DB2 on Windows 95, Windows 98, and Windows ME When
          the User Is Not Logged On
        o 14.2 Chapter 2. Troubleshooting the DB2 Universal Database Server

   * Ýb 64 ÝÏ÷¦§¾ð¾xÏWùØ¾× DB2 Universal Database
        o 15.1 ýŽ 5 üû ª[§c
             + 15.1.1 LOCKLIST
             + 15.1.2 shmsys:shminfo_shmmax
        o 15.2 ýŽ 6 üû ððùŒ

   * XML Extender Administration and Programming(æLÏÏÏ†¦¸)

   * MQSeries
        o 17.1 Ýw÷Ó¯Pª[§c DB2 MQSeries Function
             + 17.1.1 Ýw÷Ó MQSeries
             + 17.1.2 Ýw÷Ó MQSeries AMI
             + 17.1.3 ñã¾× DB2 MQSeries Function
        o 17.2 MQSeries ô€øT¬ÓÝ­
        o 17.3 øT©õæý§c
        o 17.4 MQSeries ¾\î…úõ’[
             + 17.4.1 ððùŒ
             + 17.4.2 ¨—¯~«X
        o 17.5 ¾×¦kûˆøÔÏƒ¾U
             + 17.5.1 ø•¾¯ô€øT
             + 17.5.2 ô€øeøT©õ
             + 17.5.3 ¶^ù£øT©õ
             + 17.5.4 ·ü¾×æ{Ý­û‹·ü¾×æ{Ý­üsñæ
                  + 17.5.4.1 Request/Reply üq®H
                  + 17.5.4.2 æoõG/ðqó\
        o 17.6 enable_MQFunctions
             + enable_MQFunctions
        o 17.7 disable_MQFunctions
             + disable_MQFunctions

  ------------------------------------------------------------------------

§èýzÏuùÆ

   * ññùŒÏÏÏá
        o 18.1 §èýz DB2 Server for VSE & VM Ý›¦Aóûî…ÏO
        o 18.2 Java 1.2 Ï„ï¸ññùŒÏÏÏá
        o 18.3 Ýb Windows õ@ú~ùtý×ÏUùØ¾×«uÏW¯­¸£¦§­uæL©Žñô©|­v¨—¯~
        o 18.4 OS/2 ùtý×ÏU¦§ Java ññùŒÏÏÏá
        o 18.5 Ýb Windows õ@ú~ùtý×ÏõýõøÒÏ‚¯x·Óæ›ÏwõûÝùÏuõ@¦§­u·©ž¸éæïÝs
          ù£­v¨—¯~
        o 18.6 ÝhÝ÷mõ¢úsï£÷åüsñæ
        o 18.7 DB2 for OS/390 ¦§ññùŒÏÏÏá
        o 18.8 OS/390 ññùŒÏÏÏá¾ýðn¦§ðž¾¨æ{Ý­
        o 18.9 ­u®¾á¦ô­¬h­vû‹÷š©¦§šõ¢
        o 18.10 DB2 ññùŒÏÏÏá¦§§ÇÇ›ñ’÷¥
        o 18.11 UNIX ùtý×ññùŒÏÏÏá¦§§ÇÇ›ñ’÷¥
        o 18.12 OS/2 ¾iî…¦§ Infopop øíÇD
        o 18.13 jdk11_path ª[§cø¥¬’¦§¯­¸£
        o 18.14 ùØ¾×­uScript ÏÏÏá­v¸×­uýõøÒÏ‚¯x­v©æo¾Ö¦§ Solaris ùtý×¨—¯~
          (SQL10012N)
        o 18.15 DPREPL.DFT ·©ž¦§¯­¸£
        o 18.16 ñãøÒÝhðàññùŒÏÏÏá applet
        o 18.17 ññùŒÏÏÏá¾H Applet øäÝ‘©¦§«uÏW¯­¸£
        o 18.18 Ýb Applet ¬ãÝ­ (Windows 95) ÏUøäÝ‘ññùŒÏÏÏá
        o 18.19 ùØ¾×Ïj¦§ªd÷áæý¦G

   * ÷ˆøTÏÏÏá
        o 19.1 Ýb Windows õ@ú~ùtý×ÏU¦§­uæL©Žñô©|­v¨—¯~
        o 19.2 ú¡ Netscape Ïwô}ñã©­AÝb Netscape Navigator ÏÏô}ñã¾~ü­ Web
          Çæý(UNIX ùtý×)
        o 19.3 ñãøÒ­u÷ˆøTÏÏÏá­v¦§øíÇD

   * §‰’F
        o 20.1 Ýb®¾á÷ˆ©’©w§‰’Fü]¸w¶X¾RÏjÏp
        o 20.2 MQSeries ¯ýõU§‰’F
        o 20.3 OLE DB ¯ýõU§‰’F

  ------------------------------------------------------------------------

Business Intelligence

   * Business Intelligence ñÑó€®ó
        o 21.1 ÷gûLðžðq¦§ Business Intelligence ñÑó€®ó

   * ÷ˆ©’ðš·xÏÏÏá§èýzÏƒ¾U
        o 22.1 §ÇÇ›ñ’÷¥
        o 22.2 ü]÷m Excel ªøðš·xùàú«
        o 22.3 ¸w÷qÏ×øäÝ‘æ{õ€
        o 22.4 ôž¾Xïyðz÷ˆ©’û‹÷š
        o 22.5 ªø Submit OS/390 JCL Ïuõ@Ýˆªyæ{Ý­ (VWPMVS) ¸w÷qðÔ
        o 22.6 šõ¢÷ˆ©’ðš·x«dùã¦ç¨ì
        o 22.7 ÷ˆ©’ðš·xÏÏÏáøT©õ
        o 22.8 Ýb DB2 OLAP Integration Server ÏÏ®¾á©ª[ùÇ÷ÏJ÷ˆ©’
        o 22.9 ñN Classic Connect ¯P÷ˆ©’ðš·xÏÏÏáúføtùØ¾×
        o 22.10 ÷ˆ©’ðš·xÏÏÏá·“ûãæý§c
        o 22.11 ùØ¾× Invert ¶…ï®æ{Ý­
        o 22.12 ¾H DB2 ¦¸¾¯ 7 ðš·x¾Nýzæ{Ý­Ýsù£ DB2 ¦¸¾¯ 5 ÷ˆ©’
             + 22.12.1 ýó¶… DB2 ¦¸¾¯ 5 Ý›¦Aóû
             + 22.12.2 šõ¢¾Nýzæ{Ý­ª[§c
                  + 22.12.2.1 UNIX ðš·x¾Nýzæ{Ý­
                  + 22.12.2.2 Microsoft Windows NT­BWindows 2000 ¸M OS/2 ðš
                    ·x¾Nýzæ{Ý­
        o 22.13 IBM ERwin ïyðz÷ˆ©’ù£¾Xæ{Ý­
             + 22.13.1 Ï§©e
             + 22.13.2 ün‚¯íùD
             + 22.13.3 æ{Ý­·
             + 22.13.4 ®¾á¬Ñ¾š¯yù¾·
             + 22.13.5 ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆ©’ðš·xÏÏÏá­v
             + 22.13.6 ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆøT®ª¨ì§èýzæ{Ý­­v
             + 22.13.7 §ÇÇ›ñ’÷¥
             + 22.13.8 ERwin ¯P DB2 ÷ˆ©’ðš·xÏÏÏá¦§û‹ªM
                  + 22.13.8.1 ERwin ¯P÷ˆøT®ª¨ì§èýzæ{Ý­¦§û‹ªM
        o 22.14 ¨z¨‹­u÷ˆ©’ðš·xÏÏÏá­v¦§ÝW§ë¯PÝõ}
             + 22.14.1
                  + 22.14.1.1 ø•¾¯ðnùD
                  + 22.14.1.2 Trillium ün‚ùtý×Ï÷¾¢
                  + 22.14.1.3 ñN­uTrillium õ†Ý÷ùtý×­v¯P­u÷ˆ©’ðš·xÏÏÏá­vúføt
                    ùØ¾×
                  + 22.14.1.4 ôžÏJ Trillium ïyðz÷ˆ©’
                  + 22.14.1.5 û‹ªMïyðz÷ˆ©’
                  + 22.14.1.6 ððùŒ
             + 22.14.2 ¬ô¬g Trillium õ†Ý÷ùtý× JCL ·
             + 22.14.3 Ýb UNIX ¸M Windows ÏW¬ô¬g Trillium õ†Ý÷ùtý× Script
               ·
             + 22.14.4 ¸w÷q Trillium õ†Ý÷ùtý×ùB’J
             + 22.14.5 ùØ¾×­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­
             + 22.14.6 ¨—¯~üBýzñ`Ý­
                  + 22.14.6.1 ¨—¯~Ý^¶Ñ«X
                  + 22.14.6.2 Ï‚¯x·
        o 22.15 MQ Series ¯P­u÷ˆ©’ðš·xÏÏÏá­v¦§óÆÝX
             + 22.15.1 ®¾á MQSeries øT©õ¦§úõýÏ¦¡
                  + 22.15.1.1 ø•¾¯ðnùD
                  + 22.15.1.2 ððùŒ
                  + 22.15.1.3 ®¾á MQSeries øT©õ¦§úõýÏ¦¡
             + 22.15.2 ôžÏJ MQSeries øT©õ¸M XML ïyðz÷ˆ©’
                  + 22.15.2.1 ø•¾¯ðnùD
                  + 22.15.2.2 ððùŒ
                  + 22.15.2.3 ôžÏJ MQSeries øT©õ¯P XML ïyðz÷ˆ©’
                  + 22.15.2.4 ùØ¾× MQSeries ùØ¾×¦Þ¸w÷qæ{Ý­
                  + 22.15.2.5 ¨—¯~Ý^¶Ñ«X
                  + 22.15.2.6 ¨—¯~Ï‚¯x·
        o 22.16 Microsoft OLE DB ¯P­u÷ˆ©’ýõøÒ¦AøÔ­vÏ„ï¸
             + 22.16.1 ®¾á OLE DB ¦¡©‘ù‡¬’¦§úõýÏ¦¡
             + 22.16.2 ®¾á DTS ÷ˆ©’¾]¦§úõýÏ¦¡
        o 22.17 ¬Wôq COMMIT úføt replace ùØ¾×
        o 22.18 Ï÷¾¢øl¶š÷ˆ©’·ÝW
        o 22.19 AIX Ï× Solaris õ@ú~·“ûãÏW Sybase ùàú«¯íðn¦§ OPEN CLIENT
        o 22.20 «dùãæn¨ìõ¢¾¨
        o 22.21 ýŽ 3 üû ü]¸wðš·xùàú«
             + 22.21.1 û‹ªM Microsoft Access ÏÏ¦§ü’õ¥¨ìŽ‘ÝÝšðš·xùàú«
        o 22.22 ýŽ 10 üû §–@ðš·x÷ˆ©’©w
             + 22.22.1 Çæý¦¡©‘Ýš DB2 UDB RUNSTATS æ{Ý­¦§ùB’JÝ÷Çç®ª
        o 22.23 ûwü]ðš·xññùŒ÷ˆ©’©w
        o 22.24 ðš·xññùŒ÷ˆ©’©w§èýzæ›æ­
        o 22.25 šõ¢õ@¾×ÏÏðš·xññùŒ÷ˆ©’©w
        o 22.26 ®¾á¸Mø_¸lü]¸wðš·xññùŒ÷ˆ©’©w
        o 22.27 ®¾á¦¸¾¯¦§ SQL ùB’J
        o 22.28 Ýb­uæ{õ€¬ã®ª­væ›æ­ÏÏ­Ašõ¢ùàú«¸×¾¬Ñ
        o 22.29 ús¬W¯­¸£Ýš­u÷ˆ©’ðš·xÏÏÏá­v¦®¾¢
        o 22.30 øäÝ‘­u«dùãÏ§©e­v
        o 22.31 «s¨Š Create DDL SQL üîðzÝ­
        o 22.32 ýó¶… Visual Warehouse øàú~·Óæ›
        o 22.33 ®¾á¾¬Ñ¦¡©‘Ï×¾Dðnµ„
        o 22.34 ùØ¾× Merant ODBC XøÒæ{Ý­
        o 22.35 ús® ODBC XøÒæ{Ý­
        o 22.36 ¸w÷q OS/2 ÷ˆ©’©wÏÏ¦§ðš·xùàú«¸×¾¬Ñ
        o 22.37 §Òúçðš·xññùŒ÷ˆ©’©w¦§¦ª§A
        o 22.38 ùØ¾× SQL ¯ýõUæ{Ý­¯P TBC_MD «dùã÷ˆ©’©w
        o 22.39 ùØ¾× FormatDate ù‡¬’
        o 22.40 šõ¢¯yù¾ü]¸w
        o 22.41 ùØ¾×­uýœ¾Öµ„ðÔ¦¡©‘­v¶…ï®æ{Ý­
        o 22.42 §–@÷ˆ©’©wüsñæ
        o 22.43 ü]¸w¯ú§í­u÷ˆ©’ðš·xÏÏÏá­vñqŽíî÷
        o 22.44 ¸w÷q DB2 for VM ðš·xùàú«
        o 22.45 ¸w÷q DB2 for VM ¸× DB2 for VSE ¾¬Ñ¦¡©‘
        o 22.46 ñã¾×Ýü¸wªý÷û¦§Ç¥õOÝrÏ„ï¸
        o 22.47 Data Joiner ¨—¯~®¾XüsæýøíÇD
        o 22.48 ÷ˆ©’ðš·xÏÏÏáü]¸w¸MøäÝ‘õê¬g
        o 22.49 §ÇÇ›ñ’÷¥îæüZ
        o 22.50 Ýsù£ùàú«¸M¾¬Ñ·
        o 22.51 Ï„ï¸¦§®D IBM ÷ˆ©’©wùàú«¦§ús¬Wù’ôæ
        o 22.52 Ýb÷ˆ©’ðš·xÏÏÏáÏÏÏƒøÒ®¾á÷ˆ©’ùàú«
        o 22.53 ùØ¾× Common Warehouse Metadata Interchange (CWMI) ôžÏJÏ×ôž
          ¾Xïyðz÷ˆ©’
             + 22.53.1 ¶ýÏô
             + 22.53.2 ôžÏJïyðz÷ˆ©’
             + 22.53.3 ÝbøäÝ‘ôžÏJÏ«¾×æ{Ý­Ïõ® õ¢úsïyðz÷ˆ©’
             + 22.53.4 ôž¾Xïyðz÷ˆ©’
        o 22.54 OS/390 Runstats Ï«¾×æ{Ý­ùB’J
        o 22.55 OS/390 ÷ÏJÏ«¾×æ{Ý­ùB’J
        o 22.56 Common Warehouse Metamodel (CWM) XML Ï„ï¸
        o 22.57 üBýz¬ã®ªýœ¾Öóû
        o 22.58 §ä¾¬ã®ªýœ¾Öóû
        o 22.59 ¾ýðn¨‚ÏJŽ‘Ý
        o 22.60 ­u÷ˆ©’ðš·xÏÏÏá­væo©g¾x¾[ñj¾\î…
        o 22.61 ÝCÝLùB’J÷ˆøTù·©ž

   * Data Warehouse Center Application Integration Guide(æLÏÏÏ†¦¸)
        o 23.1 Additional metadata templates
             + 23.1.1 Commit.tag
                  + 23.1.1.1 Tokens
                  + 23.1.1.2 Examples of values
             + 23.1.2 ForeignKey.tag
                  + 23.1.2.1 Tokens
                  + 23.1.2.2 Examples of values
             + 23.1.3 ForeignKeyAdditional.tag
                  + 23.1.3.1 Tokens
                  + 23.1.3.2 Examples of values
             + 23.1.4 PrimaryKey.tag
                  + 23.1.4.1 Tokens
                  + 23.1.4.2 Examples of values
             + 23.1.5 PrimaryKeyAdditional.tag
                  + 23.1.5.1 Tokens
                  + 23.1.5.2 Examples of values

   * ÷ˆ©’ðš·xÏÏÏá«uÏW¯­¸£
        o 24.1 ¸w÷qõê¬g¦§¦¡©‘¸×úõýÏ¦¡
        o 24.2 øäÝ‘ùÆÝü AS/400 ¾Nýzæ{Ý­¦§ Essbase VWPs
        o 24.3 ùØ¾×Ï«õG÷ˆ©’ðš·xÏÏÏáïyðz÷ˆ©’æ›æ­Ï×ÏwæýÝX¦§Ï§©eæ›æ­
        o 24.4 ¾~ùàµ„
        o 24.5 õê¬gæõøO¾¯
        o 24.6 ôžÏJ¬Ñ¾š¯yù¾
        o 24.7 ús¬W÷ˆ©’¦§Çæý
        o 24.8 ôžÏJ¦¡©‘
        o 24.9 RUNSTATS ¸M REORGANIZE TABLE «uÏW¯­¸£ôøÝX
        o 24.10 ­uüq¦ó­vðôðñ­A­uðš·xÏ§©e­v¯P­uñ’æ{­væõøO¾¯
        o 24.11 ­u¾Nýzæ{Ý­§í­væõøO¾¯¦§¾Nýzæ{Ý­¬ãýåŽ‘Ý

   * DB2 OLAP Starter Kit
        o 25.1 OLAP Server §“î÷
        o 25.2 Ï„ï¸¦§õ@ú~ùtý×¦AøÔæ{Ý­æ¾î
        o 25.3 õûÝù DB2 OLAP Starter Kit Ýb UNIX ÏW¦§Ýw÷Ó
        o 25.4 ª[§c OLAP Starter Kit ¦§ ODBC
             + 25.4.1 Ýb UNIX ùtý×ª[§c÷ˆ©’ùàú«
                  + 25.4.1.1 ª[§c ODBC ·“ûãš¬’
                  + 25.4.1.2 «s¨Š odbc.ini ·©ž
                  + 25.4.1.3 ús¬W÷ˆ©’ùàú«ù odbc.ini ·
                  + 25.4.1.4 ODBC ¦§ DB2 ü]¸wðÔ«dùã
                  + 25.4.1.5 ODBC ¦§ Oracle ü]¸wðÔ«dùã
             + 25.4.2 Ýb UNIX ùtý×ÏWª[§c OLAP ïyðz÷ˆ©’®ª¨ì
             + 25.4.3 Ýb Windows ùtý×ÏWª[§c÷ˆ©’ùàú«
             + 25.4.4 Ýb Windows ùtý×ÏWª[§c OLAP ïyðz÷ˆ©’®ª¨ì
             + 25.4.5 Ýbñzª[§c÷ˆ©’ùàú«Ïõ® 
        o 25.5 ñq OLAP Starter Kit ©…ÏW§èýzæ{Ý­ænÏJ
             + 25.5.1 Starter Kit ænÏJ«dùã
        o 25.6 ÝêÝ‘®¾á¸Mª[§c OLAP Starter Kit ¦§«dùã÷ˆ©’©w
        o 25.7 ýó¶…·ü¾×æ{Ý­Ýš OLAP Starter Kit ¦¸¾¯ 7.2
        o 25.8 Ïw¦óøíÇD¯PððùŒ
        o 25.9 OLAP ÷å§ƒ¦¡¬Wîqôø EQD ·©ž¨•¾½

   * ÷ˆøT®ª¨ì§èýzæ{Ý­§èýzÏƒ¾U
        o 26.1 ÷ˆøT®ª¨ì§èýzæ{Ý­ø_¸lü]¸wÏ«¾×æ{Ý­
             + 26.1.1
             + 26.1.2 ¦¸vøíÇD
             + 26.1.3 Ýw÷ÓøíÇD
        o 26.2 ¾H DB2 ¦¸¾¯ 7 ÷ˆøT®ª¨ì§èýzæ{Ý­Ýsù£ DB2 ¦¸¾¯ 5 ÷ˆøT®ª¨ì
        o 26.3 ü]÷m÷ˆøT®ª¨ì
        o 26.4 ¯Pù„¾Ýýœ®~¾‘ï®ïyðz÷ˆ©’
        o 26.5 ùØ¾× flgnxoln ®¾O¾‘ï®ïyðz÷ˆ©’
        o 26.6 ùØ¾× MDISDGC ®¾O¾‘ï®ïyðz÷ˆ©’
        o 26.7 ¸I¾sæ{Ý­

   * Information Catalog Manager Programming Guide and Reference(æLÏÏÏ†¦¸)
        o 27.1 Information Catalog Manager Reason Codes

   * ÷ˆøT®ª¨ì§èýzæ{Ý­ùØ¾×Ïƒ¾U

   * ÷ˆøT®ª¨ì§èýzæ{Ý­­G«uÏWøT©õ
        o 29.1 øT©õ FLG0260E
        o 29.2 øT©õ FLG0051E
        o 29.3 øT©õ FLG0003E
        o 29.4 øT©õ FLG0372E
        o 29.5 øT©õ FLG0615E

   * ÷ˆøT®ª¨ì§èýzæ{Ý­­G«uÏW¯­¸£
        o 30.1 Web ÷ˆøT®ª¨ì§èýzæ{Ý­

   * DB2 Warehouse Manager Ýw÷ÓÏƒ¾U
        o 31.1 ðš·x¶…ï®æ{Ý­¦§ün‚¯íùD
        o 31.2 SAP R/3 Connector
             + 31.2.1 Ýw÷Ó¾ìùMñ›¾¢
        o 31.3 Web Connector
             + 31.3.1 Ýw÷Ó¾ìùMñ›¾¢

   * Query Patroller Administration Guide(æLÏÏÏ†¦¸)
        o 32.1 DB2 Query Patroller Client is a Separate Component
        o 32.2 Migrating from Version 6 of DB2 Query Patroller Using
          dqpmigrate
        o 32.3 Enabling Query Management
        o 32.4 Location of Table Space for Control Tables
        o 32.5 New Parameters for dqpstart Command
        o 32.6 New Parameter for iwm_cmd Command
        o 32.7 New Registry Variable: DQP_RECOVERY_INTERVAL
        o 32.8 Starting Query Administrator
        o 32.9 User Administration
        o 32.10 Creating a Job Queue
        o 32.11 Using the Command Line Interface
        o 32.12 Query Enabler Notes
        o 32.13 DB2 Query Patroller Tracker may Return a Blank Column Page
        o 32.14 Query Patroller and Replication Tools
        o 32.15 Appendix B. Troubleshooting DB2 Query Patroller Clients

  ------------------------------------------------------------------------

·ü¾×æ{Ý­ô}æo

   * Administrative API Reference (æLÏÏÏ†¦¸)
        o 33.1 db2ArchiveLog (new API)
             + db2ArchiveLog
        o 33.2 db2ConvMonStream
        o 33.3 db2DatabasePing (new API)
             + db2DatabasePing - Ping Database
        o 33.4 db2HistData
        o 33.5 db2HistoryOpenScan
        o 33.6 db2XaGetInfo (new API)
             + db2XaGetInfo - Get Information for Resource Manager
        o 33.7 db2XaListIndTrans (new API that supercedes sqlxphqr)
             + db2XaListIndTrans - List Indoubt Transactions
        o 33.8 db2GetSnapshot - Get Snapshot
        o 33.9 Forget Log Record
        o 33.10 sqlaintp - Get Error Message
        o 33.11 sqlbctcq - Close Tablespace Container Query
        o 33.12 sqlubkp - Backup Database
        o 33.13 sqlureot - Reorganize Table
        o 33.14 sqlurestore - Restore Database
        o 33.15 Documentation Error Regarding AIX Extended Shared Memory
          Support (EXTSHM)
        o 33.16 SQLFUPD
             + 33.16.1 locklist
        o 33.17 SQLEDBDESC
        o 33.18 SQLFUPD Documentation Error

   * ·ü¾×æ{Ý­ô}æoÏƒ¾U
        o 34.1 ýŽ 1 üû ¶ýÏô
             + 34.1.1 Ï„ï¸ün‚
             + 34.1.2 «dùãæ{Ý­
        o 34.2 ýŽ 3 üû ô}æo DB2 ·ü¾×æ{Ý­¦§Ï@î‰÷ˆøT
             + 34.2.1 ô}æo·©ž­Bmake ·¸M¨—¯~·Óªd¦§Ï«¾×æ{Ý­
        o 34.3 ýŽ 4 üû ô}æo Java Applets ¸M·ü¾×æ{Ý­
             + 34.3.1 ü]¸w·“ûã
                  + 34.3.1.1 OS/2 ÏW¦§ JDK ¬hÝ÷
                  + 34.3.1.2 HP-UX ÏW¦§ Java2
        o 34.4 ýŽ 5 üû ô}æo SQL æ{õ€
             + 34.4.1 ü]¸w SQL æ{õ€·“ûã
             + 34.4.2 ü]¸w«sŽôóû·“ûãš¬’
             + 34.4.3 Ýêðq«sŽô®¾O
             + 34.4.4 ®OîdÏÏô­·
             + 34.4.5 ü’¾ö¸Mï_÷m
             + 34.4.6 ®¾á SQL æ{õ€
             + 34.4.7 ¸I¾s·xÝsæ{õ€
             + 34.4.8 Ï·øeÏw«sŽô¦§ SQL æ{õ€
        o 34.5 ýŽ 7 üû ô}æo HP-UX ·ü¾×æ{Ý­
             + 34.5.1 HP-UX C
             + 34.5.2 HP-UX C++
        o 34.6 ýŽ 9 üû ô}æo OS/2 ·ü¾×æ{Ý­
             + 34.6.1 VisualAge C++ for OS/2 ¦¸¾¯ 4.0
        o 34.7 ýŽ 10 üû ô}æo PTX ·ü¾×æ{Ý­
             + 34.7.1 ptx/C++
        o 34.8 ýŽ 12 üû ô}æo Solaris ·ü¾×æ{Ý­
             + 34.8.1 SPARCompiler C++
        o 34.9 ýŽ 13 üû ®÷m Windows 32 ÝÏ÷õ@ú~ùtý×¦§·ü¾×æ{Ý­
             + 34.9.1 VisualAge C++ ¦¸¾¯ 4.0

   * Application Development Guide(æLÏÏÏ†¦¸)
        o 35.1 Chapter 2. Coding a DB2 Application
             + 35.1.1 Activating the IBM DB2 Universal Database Project and
               Tool Add-ins for Microsoft Visual C++
        o 35.2 Chapter 6. Common DB2 Application Techniques
             + 35.2.1 Generating Sequential Values
                  + 35.2.1.1 Controlling Sequence Behavior
                  + 35.2.1.2 Improving Performance with Sequence Objects
                  + 35.2.1.3 Comparing Sequence Objects and Identity
                    Columns
        o 35.3 Chapter 7. Stored Procedures
             + 35.3.1 DECIMAL Type Fails in Linux Java Routines
             + 35.3.2 Using Cursors in Recursive Stored Procedures
             + 35.3.3 Writing OLE Automation Stored Procedures
        o 35.4 Chapter 12. Working with Complex Objects: User-Defined
          Structured Types
             + 35.4.1 Inserting Structured Type Attributes Into Columns
        o 35.5 Chapter 13. Using Large Objects (LOBs)
             + 35.5.1 Large object (LOBs) support in federated database
               systems
                  + 35.5.1.1 How DB2 retrieves LOBs
                  + 35.5.1.2 How applications can use LOB locators
                  + 35.5.1.3 Restrictions on LOBs
                  + 35.5.1.4 Mappings between LOB and non-LOB data types
             + 35.5.2 Tuning the system
        o 35.6 Part 5. DB2 Programming Considerations
             + 35.6.1 IBM DB2 OLE DB Provider
        o 35.7 Chapter 20. Programming in C and C++
             + 35.7.1 C/C++ Types for Stored Procedures, Functions, and
               Methods
        o 35.8 Chapter 21. Programming in Java
             + 35.8.1 Java Method Signature in PARAMETER STYLE JAVA
               Procedures and Functions
             + 35.8.2 Connecting to the JDBC Applet Server
        o 35.9 Appendix B. Sample Programs

   * CLI Guide and Reference(æLÏÏÏ†¦¸)
        o 36.1 Binding Database Utilities Using the Run-Time Client
        o 36.2 Using Static SQL in CLI Applications
        o 36.3 Limitations of JDBC/ODBC/CLI Static Profiling
        o 36.4 ADT Transforms
        o 36.5 Chapter 3. Using Advanced Features
             + 36.5.1 Writing Multi-Threaded Applications
             + 36.5.2 Scrollable Cursors
                  + 36.5.2.1 Server-side Scrollable Cursor Support for
                    OS/390
             + 36.5.3 Using Compound SQL
             + 36.5.4 Using Stored Procedures
                  + 36.5.4.1 Writing a Stored Procedure in CLI
                  + 36.5.4.2 CLI Stored Procedures and Autobinding
        o 36.6 Chapter 4. Configuring CLI/ODBC and Running Sample
          Applications
             + 36.6.1 Configuration Keywords
        o 36.7 Chapter 5. DB2 CLI Functions
             + 36.7.1 SQLBindFileToParam - Bind LOB File Reference to LOB
               Parameter
             + 36.7.2 SQLNextResult - Associate Next Result Set with
               Another Statement Handle
                  + 36.7.2.1 Purpose
                  + 36.7.2.2 Syntax
                  + 36.7.2.3 Function Arguments
                  + 36.7.2.4 Usage
                  + 36.7.2.5 Return Codes
                  + 36.7.2.6 Diagnostics
                  + 36.7.2.7 Restrictions
                  + 36.7.2.8 References
        o 36.8 Appendix D. Extended Scalar Functions
             + 36.8.1 Date and Time Functions
        o 36.9 Appendix K. Using the DB2 CLI/ODBC/JDBC Trace Facility

   * øT©õø¥ÝãÏƒ¾U
        o 37.1 ù£ñoøT©õ¯P SQLSTATE ¯­¸£
        o 37.2 Ýb DB2 Connect šõ¢¦§ SQLCODE ð®úsû‹ªM
        o 37.3 ús¦§¯Pšõ¢¦§øT©õ
             + 37.3.1 ¸I¾s¬hÝ÷Ïôðñ (CLI) øT©õ
             + 37.3.2 DB2 øT©õ
             + 37.3.3 DBI øT©õ
             + 37.3.4 ÷ˆ©’ðš·xÏÏÏá (DWC) øT©õ
             + 37.3.5 SQL øT©õ
        o 37.4 õ¢¾¨ SQLSTATES

   * SQL Reference(æLÏÏÏ†¦¸)
        o 38.1 SQL Reference is Provided in One PDF File
        o 38.2 Chapter 3. Language Elements
             + 38.2.1 Naming Conventions and Implicit Object Name
               Qualifications
             + 38.2.2 DATALINK Assignments
             + 38.2.3 Expressions
                  + 38.2.3.1 Syntax Diagram
                  + 38.2.3.2 OLAP Functions
                  + 38.2.3.3 Sequence Reference
        o 38.3 Chapter 4. Functions
             + 38.3.1 Enabling the New Functions and Procedures
             + 38.3.2 Scalar Functions
                  + 38.3.2.1 ABS or ABSVAL
                  + 38.3.2.2 DECRYPT_BIN and DECRYPT_CHAR
                  + 38.3.2.3 ENCRYPT
                  + 38.3.2.4 GETHINT
                  + 38.3.2.5 IDENTITY_VAL_LOCAL
                  + 38.3.2.6 LCASE and UCASE (Unicode)
                  + 38.3.2.7 MQPUBLISH
                  + 38.3.2.8 MQREAD
                  + 38.3.2.9 MQRECEIVE
                  + 38.3.2.10 MQSEND
                  + 38.3.2.11 MQSUBSCRIBE
                  + 38.3.2.12 MQUNSUBSCRIBE
                  + 38.3.2.13 MULTIPLY_ALT
                  + 38.3.2.14 REC2XML
                  + 38.3.2.15 ROUND
                  + 38.3.2.16 WEEK_ISO
             + 38.3.3 Table Functions
                  + 38.3.3.1 MQREADALL
                  + 38.3.3.2 MQRECEIVEALL
             + 38.3.4 Procedures
                  + 38.3.4.1 GET_ROUTINE_SAR
                  + 38.3.4.2 PUT_ROUTINE_SAR
        o 38.4 Chapter 5. Queries
             + 38.4.1 select-statement/syntax diagram
             + 38.4.2 select-statement/fetch-first-clause
        o 38.5 Chapter 6. SQL Statements
             + 38.5.1 Update of the Partitioning Key Now Supported
                  + 38.5.1.1 Statement: ALTER TABLE
                  + 38.5.1.2 Statement: CREATE TABLE
                  + 38.5.1.3 Statement: DECLARE GLOBAL TEMPORARY TABLE
                    PARTITIONING KEY (column-name,...)
                  + 38.5.1.4 Statement: UPDATE
             + 38.5.2 Larger Index Keys for Unicode Databases
                  + 38.5.2.1 ALTER TABLE
                  + 38.5.2.2 CREATE INDEX
                  + 38.5.2.3 CREATE TABLE
             + 38.5.3 ALTER SEQUENCE
                  + ALTER SEQUENCE
             + 38.5.4 ALTER TABLE
             + 38.5.5 Compound SQL (Embedded)
             + 38.5.6 Compound Statement (Dynamic)
                  + Compound Statement (Dynamic)
             + 38.5.7 CREATE FUNCTION (Source or Template)
             + 38.5.8 CREATE FUNCTION (SQL Scalar, Table or Row)
             + 38.5.9 CREATE METHOD
                  + CREATE METHOD
             + 38.5.10 CREATE SEQUENCE
                  + CREATE SEQUENCE
             + 38.5.11 CREATE TRIGGER
                  + CREATE TRIGGER
             + 38.5.12 CREATE WRAPPER
             + 38.5.13 DECLARE CURSOR
             + 38.5.14 DELETE
             + 38.5.15 DROP
             + 38.5.16 GRANT (Sequence Privileges)
                  + GRANT (Sequence Privileges)
             + 38.5.17 INSERT
             + 38.5.18 SELECT INTO
             + 38.5.19 SET ENCRYPTION PASSWORD
                  + SET ENCRYPTION PASSWORD
             + 38.5.20 SET transition-variable
                  + SET Variable
             + 38.5.21 UPDATE
        o 38.6 Chapter 7. SQL Procedures now called Chapter 7. SQL Control
          Statements
             + 38.6.1 SQL Procedure Statement
                  + SQL Procedure Statement
             + 38.6.2 FOR
                  + FOR
             + 38.6.3 Compound Statement changes to Compound Statement
               (Procedure)
             + 38.6.4 RETURN
                  + RETURN
             + 38.6.5 SIGNAL
                  + SIGNAL
        o 38.7 Appendix A. SQL Limits
        o 38.8 Appendix D. Catalog Views
             + 38.8.1 SYSCAT.SEQUENCES

   * IBM DB2 ·xÝsæ{õ€®÷móû
        o 39.1 Java 1.2 Ï„ï¸·xÝsæ{õ€®÷móû
        o 39.2 DB2 ·xÝsæ{õ€¦§¯ú§íøœ¨—
        o 39.3 Ýb Windows­BOS/2 ¸× UNIX ¾ð¾xÏWô}æo SQL æ{õ€
        o 39.4 Ýb Solaris ¾ð¾xùØ¾× DB2 ·xÝsæ{õ€®÷móû
        o 39.5 Ïw¦óøíÇD¯PððùŒ
        o 39.6 Ýbµc‚ÏÏÏ†¯yù¾·“ûãÏUùØ¾× DB2 ·xÝsæ{õ€®÷móû
        o 39.7 UNIX (AIX­BSun Solaris­BLinux) Ýw÷Ó¯P·xÝsæ{õ€®÷móû
        o 39.8 ®÷m OS/390 ¦§ SQL ·xÝsæ{õ€
        o 39.9 øœ¨— SQL ·xÝsæ{õ€
        o 39.10 ôž¾X Java ·xÝsæ{õ€
        o 39.11 Ýb OS/390 ÏWï­ÏJ·xÝsæ{õ€
        o 39.12 ÝbÏuõ@î÷Ý›¦AóûÏÏü]¸w SQL ·xÝsæ{õ€¦§®÷m¨‹ôæ
        o 39.13 ÝêøÒï_ús OS/390 ÏW·xÝsæ{õ€®÷m¦§ WLM Ýõ}¦ô­
        o 39.14 Ýb OS/390 ô}æo Java ·xÝsæ{õ€
        o 39.15 ªø MQ Series ¯P OLE DB ®÷m DB2 ¦¡©‘ùØ¾×¦Þ¸w÷q¾\î… (UDF)

   * Unicode õ¢ús
        o 40.1 ¶ýÏô
             + 40.1.1 DB2 Unicode ÷ˆ©’©wÏ×·ü¾×æ{Ý­
             + 40.1.2 Ï†¾¢õ¢ús
        o 40.2 SQL Reference(æLÏÏÏ†¦¸)
             + 40.2.1 Chapter 3 Language Elements
                  + 40.2.1.1 Promotion of Data Types
                  + 40.2.1.2 Casting Between Data Types
                  + 40.2.1.3 Assignments and Comparisons
                  + 40.2.1.4 Rules for Result Data Types
                  + 40.2.1.5 Rules for String Conversions
                  + 40.2.1.6 Expressions
                  + 40.2.1.7 Predicates
             + 40.2.2 Chapter 4 Functions
                  + 40.2.2.1 Scalar Functions
        o 40.3 CLI Guide and Reference(æLÏÏÏ†¦¸)
             + 40.3.1 Chapter 3. Using Advanced Features
                  + 40.3.1.1 Writing a DB2 CLI Unicode Application
             + 40.3.2 Appendix C. DB2 CLI and ODBC
                  + 40.3.2.1 ODBC Unicode Applications
        o 40.4 Data Movement Utilities Guide and Reference(æLÏÏÏ†¦¸)
             + 40.4.1 Appendix C. Export/Import/Load Utility File Formats

  ------------------------------------------------------------------------

üsñæù¾Dûq÷œùtý×

   * üsñæ·“ûã÷¾R÷ˆ©’
        o 41.1 Ýb VM ·“ûãÏUÝw÷Ó·ü¾×æ{Ý­Ý›¦Aóû
        o 41.2 CLI/ODBC/JDBC ª[§c PATCH1 ¸M PATCH2 ü]¸wðÔ

  ------------------------------------------------------------------------

Ï@î‰÷ˆøT

   * Ï@î‰÷ˆøT
        o 42.1 DB2 Universal Database Business Intelligence õ™ütóŽì
        o 42.2 DB2 Everywhere Ïwõ‹ªø DB2 Everyplace
        o 42.3 ú’û®¯íùD
        o 42.4 ÷åûØñq DB2 Run-time Client üsæýóðP­uõ„Ïœùüsæý·©ž­v¨—¯~
        o 42.5 Search ñïîµ (Search Discovery)
        o 42.6 HP-UX 11 ¦§øOóÑ‚æ›æ­
        o 42.7 dlfm client_conf ¾½©Ž©ùØ¾×¦ÞÏõøÒõ@
        o 42.8 ®šÏ™ùœ¦§ù’¾¢­G«’¯sñ`ónæ{Ý­Ýb dlfm øñÏŒ©ùSÝüøñÏŒ
        o 42.9 ÷¥øœÝw÷Ó DB2 DFS ñqŽíî÷ñãøÒæ{Ý­
        o 42.10 Windows NT ñqŽíî÷ùðÏ·‡Çã
        o 42.11 Ýb®¾áÏlæ{õ€© AutoLoader ¾iî…ú|ú¡ñ¬
        o 42.12 DATALINK ï_÷m
        o 42.13 Windows NT (CS/NT) ¦§ IBM Communications Ý›¦Aóû¸w÷qùØ¾×¦Þ
          ID ¸MüqÝ‘«X
             + 42.13.1 ÷`¶I¸w÷q
        o 42.14 µpÝXùtý×¦§ððùŒ
        o 42.15 DataJoiner ððùŒ
        o 42.16 Windows NT ¦§õ’õBùàÏ†÷ˆøT®ª¨ì§èýzæ{Ý­
        o 42.17 Microsoft SNA Server ¸M SNA Ýhî÷õ¢ús (ùƒô¾ªq«T¸w) Ï„ï¸
        o 42.18 ñãøÒ Windows Ïõ® æL¦kñãøÒ DB2 ¦§ SNA SPM
        o 42.19 DB2 §èýzÝ›¦Aóû¦§¯yù¾·“ûãü]¸w
        o 42.20 ñô©|æL©Ž
        o 42.21 Windows NT Ï× Windows 2000 ÏW¦§ DB2 ¦AøÔñbÏ ¯íùD
        o 42.22 Ýb¦¸¾¯ 6 ÏÏ®¾á¦§ Query Patroller ùØ¾×¦Þ¾½¾hÏF EXECUTE ñM¾×
          v
        o 42.23 Query Patroller ððùŒ
        o 42.24 ¯íðn«T¸w¸ãÝüú|Ýb÷ˆ©’ðš·xÏÏÏá(DWC)ÏÏùØ¾×¦§ùØ¾×¦Þ¸w÷qæ{Ý­
        o 42.25 ÷ˆ©’ðš·xÏÏÏá¸R¾OÝ‘ôž¾X¦§ús¨‹ôæ
        o 42.26 Backup Services APIs (XBSA)
        o 42.27 OS/390 ¾Nýzæ{Ý­
             + 42.27.1 Ýw÷Óúõ’[
             + 42.27.2 Ýw÷Ó¸£ýà
             + 42.27.3 ü]÷mÇB¾~¦§¾Nýzæ{Ý­ù‡¬’
             + 42.27.4 ¾×Žýæoæ{Ý­ñ’æ{ðš·xùB’J (XTClient)
             + 42.27.5 ¶…ï®æ{Ý­
             + 42.27.6 Ýsù£ DB2 ùtÝCÏõ¾~¦§÷ˆ©’©w
             + 42.27.7 øäÝ‘ DB2 for OS/390 Ï«¾×æ{Ý­
             + 42.27.8 õê¬g
             + 42.27.9 ¾Nýzæ{Ý­øO÷
        o 42.28 Windows NT ÏW¦§ñqŽíî÷§íõ™ù£
        o 42.29 Enterprise Edition UNIX CD-ROM ¦§÷å¾×ýœ®~
        o 42.30 DB2 Connect Enterprise Edition UNIX CD-ROM ¦§÷å¾×ýœ®~
        o 42.31 ñÓñ¢ Data Links Manager
        o 42.32 ùØ¾× SMIT ÷¥øœÝw÷Ó DLFM Ï÷¾¢¾iî…ú|øœ¾hÇB¾~¦§·©žôø
        o 42.33 Ýb Windows 2000 ÏWùØ¾× CLP ©æo¾Ö¨—¯~ SQL1035N
        o 42.34 SQL ¯ýõUæ{Ý­¦§¾[ñj¾\î…
        o 42.35 Linux ÏW¦§ DB2 ¦§ Gnome ¸M KDE ©…ðñóÆÝX
        o 42.36 Ýb Windows 2000 Terminal Server §èýz¬ãÝ­ÏUøäÝ‘ DB2
        o 42.37 ü’¾ö¯Pï_÷m®¾O¦§«uÏW¯­¸£
        o 42.38 "Warehouse Manager" ·üªø "DB2 Warehouse Manager"

  ------------------------------------------------------------------------

¦ç¾[÷ˆøT

   * ¦ç¾[÷ˆøT
        o 43.1 DB2 Universal Database ¸M DB2 Connect «uÏWÏ„ï¸
        o 43.2 DB2 Magazine

  ------------------------------------------------------------------------

¦ç¨ì

   * ¦ç¨ì A. ¦`úNù’ôæ
        o A.1 øà¬Ñ

  ------------------------------------------------------------------------

w¦‹ùØ¾× DB2 Universal Database ¦¸¾¯ 7­I

æ—:
     ü]¸wÝr®ªªøü‘ôZ¾HÏŠ®K·Óæ›­u¦¸Ý÷¦`úNù’ôæ­v­C

DB2 Universal Database ¯P DB2 Connect Ï„ï¸§“î÷ú|¸wïµõ¢ús­C «Ñ÷äÝš­G
http://www.ibm.com/software/data/db2/udb/winos2unix/support­A¾Hù£ñoüÞús¦§÷ˆ
øT­C

¾¯·©ž¾]õtÏUÝC¦§ýœ®~÷ˆøT­FÝb DB2 ¦§Ïƒ¾UÝL¯s©­A¸|æL¦kù£ñoüoü­¾ö¦§÷ˆøT­G

   IBM DB2 Universal Database Personal Edition­A¦¸¾¯ 7.2
   IBM DB2 Universal Database Workgroup Edition­A¦¸¾¯ 7.2
   IBM DB2 Universal Database Enterprise Edition­A¦¸¾¯ 7.2
   IBM DB2 Data Links Manager­A¦¸¾¯ 7.2
   IBM DB2 Universal Database Enterprise - Extended Edition­A¦¸¾¯ 7.2
   IBM DB2 Query Patroller­A¦¸¾¯ 7.2
   IBM DB2 Personal Developer's Edition­A¦¸¾¯ 7.2
   IBM DB2 Universal Developer's Edition­A¦¸¾¯ 7.2
   IBM DB2 Data Warehouse Manager­A¦¸¾¯ 7.2
   IBM DB2 Relational Connect­A¦¸¾¯ 7.2

¾tÝüÏ@ðà­u¦¸Ý÷¦`úNù’ôæ­v·©žªø READCON.TXT­A üoðà·©žïœù¥ÏUÝCýœ®~¦§÷ˆøT­G

   IBM DB2 Connect Personal Edition­A¦¸¾¯ 7.2
   IBM DB2 Connect Enterprise Edition­A¦¸¾¯ 7.2

­uúsîS¸ÒÏôýÑ­vÏ@©¥ÏÏ¾]õtü­¾ö¦§ DB2 ¦¸¾¯ 7.2 ¾Dðn¬W¾[¦§úõ’[­CðYñzùSÝü­uúsîS
¸ÒÏôýÑ­v¦§¦¸¾¯ 7.2­A «ÑÝš
http://www.ibm.com/software/data/db2/udb/winos2unix/support ·Óæ›¸×ÏU÷­C

æ—:
     Ýbðôðñ¾¦ø¬¦§ðžðqÝC (|) ªO¦¡¾š÷àÝ‘Ýê­u¦¸¾¯¦`úNù’ôæ­výŽÏ@¦¸Ïõ® ÝbÝû¬hÝ÷
     ÏÏÝüüQús¬W¸×ðžõ‹­C

  ------------------------------------------------------------------------

îSõO¯í¦ó

  ------------------------------------------------------------------------

îSõO¯í¦ó

  ------------------------------------------------------------------------

1.1 DB2 UDB ¦¸¾¯ 7 ¦§Ýsù£îS¸Ò

DB2 UDB ùtÝCýœ®~¾]ªAÏFÏ@ù€ìÝ‘øÒÏœ®KÏHÏh©e¸”ùØ¾×¦§îS¸Ò­Cüoù€îS¸ÒªO­G

   * ¸”¸¢¨‚ÏJ¸MóÏè¦§µ„«LîS¸Ò
   * ¬WñjÏ§©eÆ¾š¦§îS¸Ò
   * ðæ©Ž¸Mæ›ŽñŽæ¾šÏõïœ¾š¨‹ôæ
   * Ï„ï¸õèüN¦§ªê©e¸Ò
   * õ@ú~ùtý×ªê©e¦§Ýsù£îS¸Ò
   * ¾iÝsù£Ï†¾¢Ïõ©‘Ý­

1.1.1 µ„«LÏõ¨‚ÏJ¸MóÏè

1.1.1.1 µ„«L¨‚ÏJ

¾uðnùØ¾×µ„«L®K¾i¾Hóèõ@ DB2 ññùŒÏÏÏá­C ¾\î…¦¡ôæ¾¸MññùŒôæïœù¥Ýsù£µ„­AìùØ¾×
¦Þ¾i¾H¦«ñæñqµ„«LñãøÒññùŒôæ¸×¨‹ù£ªYÏ@¾\î…¦¡ôæ¾­C ÝbññùŒôæ¸×ªO¾\î…¦¡Ï§¾Xý{¦§
Ýsù£µ„æeÝü¸ü«u­A¾HÏŠ®KõéðÞ¦§¨‰Ç¥­C

1.1.1.2 µ„«LæJ¶I

Ýb UNIX õ@ú~ùtý×Ï§­Aµ„«LæJ¶I¦§Ý÷m¾Hø¦®G®žÆ¾š­AÆ¾šæ›æ­Ï§÷àøØüB¸¢õ@¾×ÏÏ­A
ùØ¾×¦Þ¦§®”µ„ú|ýœ¾Ö¬vT­C

1.1.2 ÏŠ®KÆ¾šîS¸Ò

DB2 ññùŒÏÏÏáÝüÏ@ù€îS¸Ò­A¾i¾H¬WñjùØ¾×¦ÞÏôðñ­A¾HÏ×õ‹æ«©zæ›ùØ¾×¦Þû‹ûq÷œùØ¾×¦§
î…ÏO­C üoù€¬Wñj¦§¾\î…¾‡Ï„ï¸¸£Æû‹úà¦§ü]¸wðÔ­A¾HÏ×ªø®ÔÏ ôqùð¸wøæ¦§Ýr®ªÏ§©e­C

1.1.2.1 ¸£Æû‹úà¬ãÝ­

ññùŒÏÏÏáÏôðñÏ„ï¸¾¥õ@ú~ùtý×¸ãïœù¥¦§¸£Æû‹úà¬ãÝ­¨‹ôæ­C ùØ¾×¦Þ¾i¾Hü]¸wðIï§ÇCÝƒ
¸M®eï§ÇCÝƒ­AùØ¾Ýõ×ÝùñjîP¦§û‹Ï¤­C

1.1.2.2 Ýr®ªü]¸wðÔ

ññùŒÏÏÏáÏôðñÏûü\ùØ¾×¦ÞÝê¾\î…¦¡¸Mû‹÷šæ›æ­Ï§¨‹ù£Ï†Ýr¦§ÇCÝƒ­BÏjÏp¸MÝr®ª­C

1.1.2.3 æLÇ”ÇCÝƒ

ùØ¾×¦ÞÏœ¯íðn¾hÏ·¨‰ÇCÝƒ¾HùØ¾×Ýûýœ®~¦§ÝUôæ¾\î…­C

1.1.3 ¨‹óšÝ­Žæõiïœ¾š

ùØ¾×¦Þ¾i¾H¨‹óšµnðæŽæ¾š¸×æ›ŽñŽæ¾š­C

1.1.4 Ï„ï¸õèüN¦§ªê©e¸Ò

DB2 ññùŒÏÏÏáÏôðñ¸M¨Çûä¦ù£óû·ü¾×æ{Ý­ªê©e­AùãÝpüzûLµnðæÝsù£­C Ýb·ü¾×æ{Ý­¬ãÝ­
Ï§­AññùŒÏÏÏáÏôðñÝüÏ@ù€îS¸Ò­A¾i¾H·øõUæ›¯ëùØ¾×¦Þñoù¨Ç¾£ûäÏW¦§÷ˆøT­C

1.1.5 ¾iÝsù£¦§Ï†¾¢

DB2 ùtÝCýœ®~ÏõÏ†¾¢ªø HTML ©‘Ý­­C üo¾iìùØ¾×¦Þ¾H¶sŽìóûÏÏ¦§üáÝnü]¸wùà·Óæ›Ï†
¾¢­C ¾ÝÏ]©eü\¨Çûä¦ù£óû¸Mù„¾Ýù¢õUõèüN¦§ùØ¾×­C
  ------------------------------------------------------------------------

1.2 ¦ç¾[¦§¾ýðn Solaris ðž÷¬hÝ÷

øœÏFÝC¾šÝbDB2 for UNIX õ™ütÏJ¦—Ïƒ¾UÏ§¦§ðž÷æ{Ý­Ïõ¾~­A µëÝC¾šÏF DB2
Universal Database ¦¸¾¯ 7 for Solaris ¦¸¾¯ 2.6 ¸ã¯íðn¦§ 106285-02 ¸×õ¢ús¦§
ðž÷æ{Ý­­C
  ------------------------------------------------------------------------

1.3 Supported CPUs on DB2 Version 7 for Solaris

UltraSparc Ïõ®e¦§ CPU ¦¸¾¯ùÇÏœÏ„ï¸­C
  ------------------------------------------------------------------------

1.4 ús¬W÷`¶IÝšÏ·ü×÷ˆ©’©w¦§øíÇD

Ýbús¬W÷`¶IÝšÏ·ü×÷ˆ©’©w©­AðYÝû÷ˆ©’©wÝüÏ@ðà¸×ÝhðàðôÏjÏp®Dûwü]ðÔ­]4 KB­^¦§ùt
ý×¬Ô©¦¡©‘¦ô­­A ñz¾iî…ú|ñoù¨—¯~øT©õ­G "SQL6073N ús¬W÷`¶Iõ@ú~¾½ñ¥"¸MÏ@ðà
SQLCODE­Cú|æo¾Öüo§ñ­õ×ªOÝ]ªøÝb®¾á÷`¶I©­A¾uÝü IBMDEFAULTBP «w«ŽÝ·ªO¾H 4
KB ¦§ðôÏjÏpÝsÝb­C

ùãÝp­Añz¾i¾HùØ¾× db2start ®¾O­Aús¬W÷`¶IÝš¾®e¦§Ï·ü×÷ˆ©’©wÏÏ­C

   DB2START NODENUM 2 ADDNODE HOSTNAME newhost PORT 2

Ýp¦GÏ·ü×÷ˆ©’©w¦§¬Ô©¦¡©‘¦ô­ÏõðôÏjÏpªøûwü]ðÔ­Aæý¦Gú|ô€Ý^ÏUÝC¦§øT©õ­G

   SQL6075W ô}¸l÷ˆ©’©w§èýzæ{Ý­õ@ú~ÏwôôõQõûÝùús¬W÷`¶I­C
        Ýû÷`¶Iðnæ¾ù¸ãÝü¦§÷`¶IüœøñÏŒ­AæM® ÏSÝAñãøÒ©Ï~Ýüõ@¾×­C

ÝìªO­AÝp¦GÏ·ü×÷ˆ©’©w¦§ùtý×¬Ô©¦¡©‘¦ô­ÏõðôÏjÏp®Dûwü]ðÔ­A®hô€Ý^¦§øT©õªO­G

   SQL6073N ús¬W÷`¶Iõ@ú~¾½ñ¥­CSQLCODE = "<-902>"

¾tÏ@ðàªêÝ¦§«dùã­A¾×ús÷`¶I¯­¸£ÏƒøÒõ¢ús db2nodes.cfg ·©žÏõ® ­A ñz¾i¾HùØ¾×
ADD NODE ®¾O­C Ýb«s¨Š÷à·ùÇû‹Ï·ü×÷ˆ©’©w (ùtý×¬Ô©¦¡©‘¦ô­ªøûwü]ðôðñÏjÏp)
øäÝ‘ ADD NODE ®¾OÏõ® ­A ú|ô€Ý^ÏUÝCøT©õ­G

      DB20000I ADD NODE ®¾OôôõQõûÝù­C

ÝìªO­AÝp¦GÏ·ü×÷ˆ©’©w¦§ùtý×¬Ô©¦¡©‘¦ô­ÏõðôÏjÏp®Dûwü]ðÔ­A®hô€Ý^¦§øT©õªO­G

   SQL6073N ús¬W÷`¶Iõ@ú~¾½ñ¥­CSQLCODE = "<-902>"

ªøÏFµžõKæo¾ÖÏWðz¦§øíÇD­A«ÑøäÝ‘­G

   DB2SET DB2_HIDDENBP=16

Ýbæo¾X db2start ¸× ADD NODE ®¾OÏõ®e­C Ýûæn¨ìš¬’ú|ùØ DB2 øt÷m 16 ðô¦§µ“¶Ç
«w«ŽÝ·­AÝàùCÏ@ðô¸ãùØ¾×¦§ðôÏjÏpùÇ®Dûwü]ðÔ­C üo¾iùØ ADD NODE õ@ú~ôôõQõûÝù­C

¾tÏ@ðà¾iµžõKüoÇçøíÇDæo¾Ö¦§ÏŠ¦k­A ªOû‹ ADD NODE ¸× db2start ®¾O®¸w WITHOUT
TABLESPACES Ïl¾y­C ÝbÝûÏõ® ­Añz¾ýôúõQ¾× CREATE BUFFERPOOL üîðzÝ­ùà®¾á«w«Ž
Ý·­A ùÇ¾BõQ¾× ALTER TABLESPACE üîðzÝ­ñNùtý×¬Ô©¦¡©‘¦ô­¸M«w«ŽÝ·ªêÇ”µp­C

Ýbús¬W÷`¶IÝšý{Ýs÷`¶I÷sýå©­AðYÝû÷`¶I÷sýåÝüÏ@ðà¸×ÝhðàðôÏjÏp®Dûwü]ðÔ (4 KB)
¦§¦¡©‘¦ô­­A ñz¾iî…ú|ñoù¨—¯~øT©õ­G"SQL0647N «w«ŽÝ· "" ¾®eÏœÝbõ@¾×ÏÏ­C"­C
ú|æo¾Öüo§ñ­õ×ªOÝ]ªø®¾áÝbús÷`¶I¾BðôÏjÏp®Dûwü]ðÔ¦§«w«ŽÝ·ùÇ¾¬ªø¦¡©‘¦ô­ñã
øÒ­C

ùãÝp­Añz¾i¾HùØ¾× ALTER NODEGROUP üîðzÝ­ús¬W÷`¶IÝš÷`¶I÷sýå­G

   DB2START
   CONNECT TO mpp1
   ALTER NODEGROUP ng1 ADD NODE (2)

Ýp¦G÷`¶I÷sýåÝüðôÏjÏpªøûwü]ðÔ¦§¦¡©‘¦ô­­Aæý¦Gú|ô€Ý^ÏUÝC¦§øT©õ­G

   SQL1759W ð®úsÏ·øt÷`¶I÷sýå¾ýôúšõ¢÷`¶I÷sýå "<ng1>" Ï§¦®¾¢¦§÷ˆ©’¸wÝ­A
¾Hù™ÏJús¬W÷`¶I­A
   ¸×ñ’øœñÓñ¢÷`¶I­C

ÝìªO­AÝp¦G÷`¶I÷sýå¦§¦¡©‘¦ô­ÏõðôÏjÏp®Dûwü]ðÔ­A®hô€Ý^¦§øT©õªO­G

   SQL0647N «w«ŽÝ· "" ¾®eÏœÝbõ@¾×ÏÏ­C

Ï@ðà¾iµžõKÝûøíÇD¦§ÏŠ¦kªOªøùCÏ@ðàðôÏjÏp®¾á«w«ŽÝ·­A ùÇÝbæo¾X ALTER NODEGROUP
üîðzÝ­Ïõ®e­Að®úsüsñæÝš÷ˆ©’©w­G

   DB2START
   CONNECT TO mpp1
   CREATE BUFFERPOOL bp1 SIZE 1000 PAGESIZE 8192
   CONNECT RESET
   CONNECT TO mpp1
   ALTER NODEGROUP ng1 ADD NODE (2)

ýŽÏGðàµžõKøíÇD¦§ÏŠ¦k­A«ÑøäÝ‘­G

   DB2SET DB2_HIDDENBP=16

æo¾X db2start ®¾O¾HÏ× CONNECT ¸M ALTER NODEGROUP üîðzÝ­Ïõ®e­C

ùØ¾× ALTER TABLESPACE üîðzÝ­ús¬W¦¡©‘¦ô­Ýš÷`¶I­A¾tÏ@ðàøíÇDú|æo¾Ö­C ùãÝp­G

   DB2START
   CONNECT TO mpp1
   ALTER NODEGROUP ng1 ADD NODE (2) WITHOUT TABLESPACES
   ALTER TABLESPACE ts1 ADD ('ts1') ON NODE (2)

üoÏ@ùtÝC®¾O¸MüîðzÝ­ú|ýœ¾Ö¨—¯~øT©õ SQL0647N­]Ýà®DûwïµøT©õ SQL1759W­^­C

ñì¾¨«TÝaõûÝùÝûšõ¢­A¾ýôúÝb ALTER NODEGROUP... WITHOUT TABLESPACES üîðzÝ­Ïõ
® ­Að®úsüsñæÝš÷ˆ©’©w­C

   DB2START
   CONNECT TO mpp1
   ALTER NODEGROUP ng1 ADD NODE (2) WITHOUT TABLESPACES
   CONNECT RESET
   CONNECT TO mpp1
   ALTER TABLESPACE ts1 ADD ('ts1') ON NODE (2)

¾tÏ@ðàµžõKøíÇD¦§ÏŠ¦k­A«ÑøäÝ‘­G

   DB2SET DB2_HIDDENBP=16

æo¾X db2start ®¾O¾HÏ× CONNECT­B ALTER NODEGROUP ¸M ALTER TABLESPACE üîðzÝ­
Ïõ®e­C
  ------------------------------------------------------------------------

1.5 ýó¶…ïµô­æo¾Ö¦§¨—¯~

ýó¶…ïµô­­AõYùØýó¶…Ýù¾\­A¨—¯~ôæ¾Ïïú|¾Xý{Ýb db2diag.log ·©žÏ§ ­]÷ˆ©’©w¾¬ýó
¶…­^­CÝû©­A¾iÏ¸¾H¸¨ýÏ­C
  ------------------------------------------------------------------------

1.6 Red Flag Linux ¦§ÏÏÏ†¯yù¾·“ûãðž¾¨æ{Ý­

Ýp¦GñzùØ¾×­u¶ý‚ÏÏÏ†ªä§X Linux Ý›¦Aóû¦¸¾¯ 1.1­v­A «Ñª½÷á­uªä§X­v¾Hù£ño¶ý‚
ÏÏÏ†¯yù¾·“ûãðž¾¨æ{Ý­­CùSÝü¦¸¾¯ 1.1 ¦§¶ý‚ÏÏÏ†¯yù¾·“ûãðž¾¨æ{Ý­­A DB2 ïNæL¦k
¨‰Ç¥¶ý‚ÏÏÏ†¦§Ýr«XðôªO 1386­C
  ------------------------------------------------------------------------

1.7 Ýp¦G¾iýóøœÝ­§Ø§Ñóö¾¬üsñæ­A®h DB2 Ýw÷Óú|ÏÏ¶_

ÝbÝw÷Ó DB2 ¦§ïµô­­AÝp¦Gûq÷œ¦§¾iýóøœÝ­§Ø§Ñóö¾¬üsñæ­A ®hÝb¨‹ù£Ýw÷ÓÇç®ªÏõ® ­A
Ýw÷Óæ{Ý­¾iî…ú|ÏÏ¶_­C ðYðn÷¥ùMÝûøíÇD­AÝbøäÝ‘Ýw÷Óæ{Ý­©®¸w -a ¨‹ôæ­G

   setup.exe -a

  ------------------------------------------------------------------------

1.8 Ï‚Ï†¸M¶ý‚ÏÏÏ† Linux ·“ûãÏõ DB2 for Linux ¦§¦ç¾[¯yù¾·“ûãü]¸w

ú¡ñzðnÝbÏ‚Ï†¸×¶ý‚ÏÏÏ† Linux ùtý×ÏWùØ¾× Java GUI ÏuùÆ­]ùãÝp­uññùŒÏÏÏá­v­^
©­A ®h¯íðnÇB¾~¦§¯yù¾·“ûãü]¸w­C ðYùSÝüüoôæü]¸w®hæL¦k¾¨«TÆ¾šÏ‚Ï†¸×ÏÏÏ†Ýr
Ï÷­C «ÑÝbñz¦§ùØ¾×¦Þü]¸w·÷Þ¾[ÏJÏUÝCü]¸w­A ¸×¦ÞÝbùCðà­uññùŒÏÏÏá­v¸I¾sÏõ®eñq
®¾OÝ‘øäÝ‘Ýûü]¸w­C

   øwû‹Ï‚Ï†ùtý×­G
      export LC_ALL=ja_JP

   øwû‹¶ý‚ÏÏÏ†ùtý×­G
     export LC_ALL=zh_CN

  ------------------------------------------------------------------------

1.9 Microsoft Internet Explorer ÏW¦§ññùŒÏÏÏáøíÇD

üoªO Internet Explorer Ýw¾ç¸Ò¨‹ôæü]¸w¸ãüyÝù¦§øíÇD­C ­uññùŒÏÏÏá­vùØ¾×¾¬Çñ÷p
¦§ jar­AÝ]ÝûÝsù£ùtý×÷ˆøTüQÝw¾ç§èýzæ{Ý­øñ¾×ÏF­C

ðYðn©›øœüoðàøíÇD­A«Ñð®úsøt÷m IE ¦§Ýw¾ç¸Ò¨‹ôæ­AÝpÏU¸ã¾š­G

  1. ¨‹ù£·Óæ›¾\î…¦¡ (IE4) ¸×ÏuùÆ¾\î…¦¡ (IE5) ÏW¦§ Internet ¨‹ôæ­C
  2. Ýb­uÝw¾ç¸Ò­vðôðñ­A¨‹ù£®H¾“¦§§“î÷øØø­C
  3. ®”Ï@ÏUús¬W§“î÷...­C
  4. ñN­uññùŒÏÏÏá Web Ý›¦Aóû­vús¬Wù®H¾“¦§§“î÷ýMü‘­C Ýp¦GññùŒÏÏÏá Web Ý›¦A
     óûÝbªêÝP¦§§“øÏÏ­A¾iî…¾uôúðnñN Web Ý›¦AóûÝW§ë¾[ÏJõY¾i (Ïœõt§“øÝW§ë)­C
     ùãÝp­G

        http://ccWebServer.ccWebServerDomain
        http://ccWebServer

  5. ®”Ï@ÏU«T¸w­C
  6. ®”Ï@ÏUü]¸w...­C
  7. ñýøÒùÏUÏŠ¦§ Java --> Java vðð­AÝA¨‹ù£Ýêðq­C
  8. ®”Ï@ÏU Java Ýêðqü]¸w...­C
  9. ¨‹ù£­u«s¨Šü\¾iv­vðôðñ­C
 10. ñýøÒùÏUÏŠ¦§­u¾¬ÇñÝW¦§Ï§©e --> øäÝ‘¾¬ÇñÝW¦§Ï§©e --> ù„¾Ý¾¬ÇñÝW¦§ü\¾iv
     --> ùtý×÷ˆøT­v­AÝA¨‹ù£ñãøÒ­C
 11. ®”Ï@ÏUùCðàô}ñãæ›æ­¦§«T¸w­C

  ------------------------------------------------------------------------

1.10 Ýb Windows ·“ûãÏÏ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏ× Sybase Ïõô­¦§Ïœªê©e

­u÷ˆøT®ª¨ì§èýzæ{Ý­­v¦¸¾¯ 7 ¸M Sybase Open Client Ýw÷ÓÝbÝPÏ@¾x Windows NT ¸×
Windows 2000 óöóûú|üyÝù¨—¯~­A ¾B Sybase Ï«¾×æ{Ý­ú|øñÏŒûBõ@­Cú|¾Xý{ÇçÝÏUÝC
¦§¨—¯~øT©õ­G

   æL¦kø_¸l LIBTCL.DLL­C«Ñ«T¸w SYBASE ·“ûã
   š¬’Ïw¾¨«Tü]¸w­C

µžõKüo§ñ­ûã¦§ÏŠ¦kªOñq Windows ·“ûãø¥¬’ÏÏñN·“ûãø¥¬’ LC_ALL øœ¾h­C LC_ALL ªO
Ï@ðà¯yù¾·“ûã§Ççø¥¬’­C ¯yù¾·“ûã§ÇçªO¾¯ÏgÏ’ñ`Ý­¸ãùØ¾×¦§¸£Æ¦§ñ`¬’­A ¾H®¸w
æ{Ý­ðnùØ¾×¦§¯yù¾·“ûã÷ˆøT¦§ü­¾ö­C ¯yù¾·“ûã ®¦§ªOÝaøØ(¸×øˆ©a)­Aæ{Ý­¦§ªYù€ÏŠ
ðñ¾iøwû‹ÝaøØÝêðq­C ¯yù¾·“ûãªêÇ”øØø¾]ªA­A ùãÝpÏ‚ïµ©‘Ý­¸×üfû“ý÷û¦§Æ¾š©‘
Ý­­C LC_ALL ú|¬vT¸ãÝü¦§¯yù¾·“ûãîS¸wÝ‘ªø (¸ãÝü§Çç)­C

Ýp¦GñzñN LC_ALL ·“ûãø¥¬’øœ¾h­Aüo¬Ó ICM ïN¾i¸M Sybase ÝP©ÝsÝb Windows NT ¾ð
¾xÏW­A ÏUÝCóöî…ú|æL¦kûBõ@­G

   * ÷ˆøT®ª¨ìùØ¾×¦Þ
   * ÷ˆøT®ª¨ì§èýz¦Þ
   * ÷ˆøT®ª¨ì§èýzæ{Ý­

  ------------------------------------------------------------------------

1.11 ññùŒÏÏÏá¾\î…ªy¾½

¾iñN FixPak 2 Ïè¾×ù DB2 Ý›¦Aóû­A ®hû‹¸¢¶¶¦¸¦§ññùŒÏÏÏáñqŽíî÷­A·ü÷àÏœú|ÝüÝû
üB¸ãïyðz¦§øíÇD­CæMÝà­AÝb DB2 ¦¸¾¯ 7.2­A ¶¶¦¸ññùŒÏÏÏáñqŽíî÷ïX¾G¾½¾hÏF¸ãÝü¦§
¾\î…­C üo÷Þ¸ã¯­¦§¶¶¦¸ªO®¾“Ý¢¦¸¾¯ 6 FixPak 6 ¾H®e¦§ñqŽíî÷­A ¾HÏ×¾“Ý¢¦¸¾¯ 7
FixPak 2 ¾H®e¦§ñqŽíî÷­C¦¸¾¯ 5 ¦§ñqŽíî÷ùÇÏœù¬vT­C

®Žü¦§ðž¾¨ÏŠÝ­ªOÏî¾“Ý¢ùù¬vT¦§ñqŽíî÷­C¦¸¾¯ 6 ñqŽíî÷¾ýôúÏîù FixPak 6
¸×õ¢ús¦¸¾¯­A ¦¸¾¯ 7 ñqŽíî÷¾ýôúÏîù FixPak 2 ¸×õ¢ús¦¸¾¯­C
  ------------------------------------------------------------------------

1.12 Netscape CD Ïœ·H¦ç¸¢ DB2 UDB

Netscape CD ÏœÝA·H¦ç¸¢ DB2 UDB­C«Ññq http://www.netscape.com­A·•ù£ Netscape
ýœ®~­C
  ------------------------------------------------------------------------

1.13 XML Readme ·¦§¨—¯~

Ýb DB2 XML Extender ¦¸¾¯ 7.1 README.TXT ·¦§­u¦`úNù’ôæ­vÏÏïœù­G

     3. DB2 UDB ¦§ûwü]¦¸¾¯ªO DB2 UDB ¦¸¾¯ 7.1­CðYñzðnÝb AIX ¯P Solaris ùØ¾×
     DB2 UDB ¦¸¾¯ 6.1­A «Ñ«T¸wñz·ü÷à¯P DB2 UDB ¦¸¾¯ 6.1 ©žùãÏ× DB2 UDB ¦¸¾¯
     6.1 ·©ž©wÏ@ø_øäÝ‘­C

üoªOÏœ¾¨«T¦§­CDB2 XML Extender ôÔÝb DB2 ¦¸¾¯ 7.1 ¯P 7.2 üQÏ„ï¸­C

·©ž readme.aix­Breadme.nt ¯P readme.sun ¸ãÝC¾š¦§ün‚¯íùDªø­G

   * DB2 UDB 6.1 (FP1_U465423) ¸×¾HÏW (AIX)
   * DB2 Universal Database ¦¸¾¯ 6.1 ¸×¾HÏW (Ýw÷Ó FixPak 3) (NT)
   * DB2 UDB ¦¸¾¯ 6.1 (FixPak FP1_U465424) ¸×¾HÏW (Sun)

üoªOÏœ¾¨«T¦§­CDB2 XML Extender ¯íðn DB2 ¦¸¾¯ 7.1 ¸× 7.2­C
  ------------------------------------------------------------------------

1.14 Linux for S/390 ÏW¾iî…¦§÷ˆ©’ªy¾½

ðYÝb Linux for S/390 (ÏwÝw÷Ó 2.2 ùtÝC©™Ïáæ{Ý­) ùØ¾× DB2­A÷à Linux ûq÷œÏW¦§
¾i¾× RAM ¬’ôqððùŒñNú|Ïp¸¢ 1 GB­CððùŒ RAM ù 1 GB î…µžõKÝ] Linux ©™Ïáæ{Ý­¨—
¯~üyÝù¦§¾iî…¸Ò DB2 ÷ˆ©’ªy¾½­C

üo¾uæo¾Ö¸¢ DB2 Ýb Linux for S/390­AÏœæo¾Ö¸¢ Linux on Intel­C

ñz¾iñq
http://www10.software.ibm.com/developerworks/opensource/linux390/alpha_src.html
ù£ño©™Ïáðž÷æ{Ý­¾Hì RAM ¾iùØ¾×ôWûL 1 GB­C
  ------------------------------------------------------------------------

1.15 Windows 2000 ÏW¦§ DB2 UDB

ÝbóÆðà­u¦¸¾¯¦`úNù’ôæ­vÏÏ­AÏZóA¾×¸¢ Windows NT ¦§ø¥Ýã÷ˆ©’ (øœ®D¾tÝü®¸w) ¸|
óA¾×¸¢ Windows 2000­C
  ------------------------------------------------------------------------

«uÏWÏ†¾¢ (HTML­BPDF ¯P­uújïM­v)

  ------------------------------------------------------------------------

2.1 Windows 2000 õ@ú~ùtý×¸ãÏ„ï¸¦§ Web ¶sŽìóû

õéðÞ®ŽüñzÝb Windows 2000 ÏWùØ¾× Microsoft Internet Explorer­C

ðYñzùØ¾× Netscape­A«Ñ¦`úNÏUÝCù’ôæ­G

   * ùØ¾× Netscape ú|ì Windows 2000 ÏW¦§ DB2 üs«u÷ˆøTújïMîà©÷–¦›­C
     Netscape ñNùØ¾×¸ãÝü¾i¾×¦§ CPU ÷ˆú«­AùÇ¾BÝ¾GªOÏœ¸£«TÝaøäÝ‘­C ú¡üÞ® ô€
     Ý^újïMæý¦G©­AõéðÞ®ŽüñzÝbïœ¾XújïMÏõ® ­AÝb¾tÏ@ðàæ›æ­ÏW®”Ï@ÏU¾Hšõ¢æJ
     ¶I­C ñææêú|ÝbÝXýz¦§©ô­ôq÷Þô€Ý^újïMæý¦G­C
   * ñz¾iî…ú|¦`úNù­Gú¡ñzðnùD¦§¯­¸£¾¨«TÝaÆ¾šÝbÏ@ðà Netscape ¶sŽìóûæ›æ­Ï§­A
     æMÝà­AÝp¦G¶sŽìóûæ›æ­Ï@¦«ô}ñãæê­A¾Bæy® ÏSñqÏœÝP¦§­uññùŒÏÏÏá­vü­¾öðnùD¯­
     ¸£­A ®h¶sŽìóû÷ÞÏœú|Ýü¾“Ý¢õ‹š­C ðYÇ”üª¶sŽìóûæ›æ­ùÇÝAÝ÷ðnùD¯­¸£­AñNú|¾X
     ý{¾¨«T¦§¯­¸£­C ñz¾iüzûL 2.4, ñãøÒ Netscape ©ýœ¾Ö¦§¨—¯~øT©õ ÷Þ¦§ÏUÝCùB
     ’Jùàðž¾¨üoðàøíÇD­C ñzÏ]¾i¾HÝbðnùD­uññùŒÏÏÏá­v¯­¸£Ïõ®eÇ”üª¶sŽìóûæ›æ­­A
     ¾HµžõKüoðàøíÇD­C
   * ðnùD­uññùŒÏÏÏá­v¦§¯­¸£­A¸×¦Þ­u÷ˆøTÏÏÏá­v¦§¾DÇD©­Añz¾iî…ú|Ýªù¨—¯~øT
     ©õ­C ðnðž¾¨üoðàøíÇD­A«Ñ¨¡ï` 2.4, ñãøÒ Netscape ©ýœ¾Ö¦§¨—¯~øT©õ ÷Þ¦§ùB
     ’J­C

  ------------------------------------------------------------------------

2.2 Ýb Solaris ùtý×ÏUújïM DB2 üs«u÷ˆøT

Ýp¦GñzÝüÝb Solaris ùtý×ÏUújïM DB2 üs«u÷ˆøT¦§øíÇD­A «Ñ·Óªdùtý×Ýb /etc/system
Ï§¦§©™Ïáæ{Ý­ø¥¬’­C¾HÏUªO DB2 újïMùtý×¸ã¯í©™Ïáæ{Ý­ø¥¬’¦§üÞÏpðÔ­A
NetQuestion­G

   semsys:seminfo_semmni 256
   semsys:seminfo_semmap 258
   semsys:seminfo_semmns 512
   semsys:seminfo_semmnu 512
   semsys:seminfo_semmsl 50
   shmsys:shminfo_shmmax 6291456
   shmsys:shminfo_shmseg 16
   shmsys:shminfo_shmmni 300

ñìü]¸w©™Ïáæ{Ý­ø¥¬’­AÝb /etc/system Ïõ® ús¬WÏUÝC®¾O­G

   set <semaphore_name> = value

ñìùØ¾“Ý¢ús®¸×šõ¢¦§ðÔ¾Ö©Ž­Añz¾ýôúð®úsñãøÒùtý×­C
  ------------------------------------------------------------------------

2.3 Ïµï® NetQuestion for OS/2 ¾HùØ¾× TCP/IP

Ïµï®g NetQuestion ¾HÝb OS/2 ùtý×ÏWùØ¾× TCP/IP ¦§®¾šÏœõûóÆ­C üoù€®¾š¦§
*.cfg ·Ý÷mªO NetQuestion Ýw÷Ó¾¨ì¦§÷ˆ©’Ý÷¾¨ì­C ñz¾i¾H¨‚ÏJÏUÝCù„ÏÏÏ@ôæ®
¾OùàùM¸w NetQuestion Ýw÷Ó¾¨ì­G

   echo %IMNINSTSRV%   //óA¾× SBCS Ýw÷Ó
   echo %IMQINSTSRV%   //óA¾× DBCS Ýw÷Ó

  ------------------------------------------------------------------------

2.4 ñãøÒ Netscape ©ýœ¾Ö¦§¨—¯~øT©õ

ú¡ñzñãøÒ Netscape ©­AÝp¦Gñzæoý{ÏUÝC¦§¨—¯~øT©õ­G

   õ„Ïœù<·©ž÷“©|>Ïõ·©ž (¸×ªOù„ÏÏ¦§Ï÷¾¢)­C
   ·ÓªdùÇ«T¸w÷“©|¸M·ÝW¦§¾¨«T¸Ò­A¾HÏ×¸ãÝü¾ýðn¦§·©ž©wªøÝü©Ž¸Ò­C
   æL¦kô}ñã "D:\Program Files\SQLLIB\CC\..\doc\html\db2help\XXXXX.htm"

ñz·ü÷àøäÝ‘ÏUÝCùB’J­A¾Hõ¢¾¨Ýb Windows NT­B95 ¸× 98 ÏW¦§üoðàøíÇD («Ñø¥ó\¾HÏU
ùB’J­A¾HÏF÷¥ÝpÝ¢Ýb Windows 2000 ÏWøäÝ‘)­G

  1. ñq­uô}¸l­v¾\î…¦¡­A¨‹ù£­uæ{Ý­ôø­v-->­uWindows ·©žµ`§è­v­CõY¾iô}ñã
     ­uWindows ·©žµ`§è­v­C
  2. ñq­uWindows ·©žµ`§è­v¨‹ù£­u·Óæ›­v-->­u÷ˆ©’õù¨‹ôæ­v­CõY¾iô}ñã­u÷ˆ©’õù
     ¨‹ôæ­væõøO¾¯­C
  3. ®”Ï@ÏU·©žÇç®ª¬Ñã­Cô}ñã­u·©žÇç®ª­vðô­C
  4. Ýbæn¨ì·©žÇç®ªŽ‘ÝÏÏ¨‹ù£ Netscape Hypertext Document­AùÇ®”Ï@ÏU­u«s¨Š­v
     ­C õY¾iô}ñã­u«s¨Š­v·©žÇç®ªæ›æ­­C
  5. ¨‹ù£øÒõ@Ž‘ÝÏÏ¦§ô}ñã­C
  6. ®”Ï@ÏU«s¨Š®”ôs­CÇç®ªæ›æ­¦§«s¨ŠøÒõ@ô}ñã­C
  7. ù£©›ùØ¾× DDE ¦§ÏŽ¨‹©­C
  8. Ýb¾×ùàøäÝ‘øÒõ@¦§·ü¾×æ{Ý­Ž‘ÝÏÏ­A «Ñ«T¸w "%1" ¾Xý{ÝbÝrÝˆ¦§üÞ® ðñ (¾]ªA
     Ïè÷û¾HÏ×ýŽÏ@ðàÏè÷ûÏõ®e¦§¦©‘)­C

ðYÝb Windows 2000 ÏWæoý{¨—¯~øT©õ­Añz·ü÷àøäÝ‘ÏUÝCùB’J­G

  1. ñqô}¸l¾\î…¦¡­A¨‹ù£ Windows ·©žµ`§è­CõY¾iô}ñã­uWindows ·©žµ`§è­v­C
  2. ñq­uWindows ·©žµ`§è­v­A¨‹ù£ÏuùÆ --> ÷ˆ©’õù¨‹ôæ­CõY¾iô}ñã­u÷ˆ©’õù¨‹
     ôæ­væõøO¾¯­C
  3. ®”Ï@ÏU·©žÇç®ª¬Ñã­C
  4. Ýb­u·©žÇç®ª­vðôÏW­BÏwæn¨ì¦§·©žÇç®ª Ž‘ÝÏÏ­Añj«åÆ¾š­GHTM Netscape
     Hypertext Document­AÝA®”Ï@ÏUôiô¾ ­CõY¾iô}ñã­u«s¨Š·©žÇç®ª­væ›æ­­C
  5. ñj«åÆ¾šøÒõ@Ž‘ÝÏÏ¦§­uô}ñã­v­C
  6. ®”Ï@ÏU«s¨Š®”ôs­CõY¾iô}ñã­u«s¨ŠÇç®ª¦§øÒõ@­væ›æ­­C
  7. ù£©›ùØ¾× DDE ¦§ÏŽ¨‹©­C
  8. Ýb¾×ùàøäÝ‘øÒõ@¦§·ü¾×æ{Ý­Ž‘ÝÏÏ­A «Ñ«T¸w "%1" ¾Xý{ÝbÝrÝˆ¦§üÞ® ðñ (¾]ªA
     Ïè÷û¾HÏ×ýŽÏ@ðàÏè÷ûÏõ®e¦§¦©‘)­C
  9. ®”Ï@ÏU«T¸w­C
 10. øwû‹ HTML Netscape Hypertext Document ¸M SHTML Netscape Hypertext
     Document ·©žÇç®ªð®«’ùB’J 4 ù 8­C

  ------------------------------------------------------------------------

2.5 UNIX ùtý×ÏW Adobe Acrobat Reader ¦§ª[§c¯íùD

Ýb UNIX ®ª¾ð¾x­AAcrobat Reader ¾uïœù¥ð^Ï†¦¸­Cñì¾Hð^Ï†¾H¾~¦§¯yù¾·“ûãô}ñã PDF
·©ž­A ùtý×ú|ô€Ý^¨—¯~øT©õ­CøT©õ®¾X PDF ·©ž¦§Ýr®ªÝsù£¸×÷¥·œµYýœ¾Ö¨—¯~­AÝì
ªO­Aûˆ¯éÏWªOÝ]ªøð^Ï†¦¸¦§ Acrobat Reader æL¦kÝb®Dð^Ï†¯yù¾·“ûã¦§ UNIX ÏÏøä
Ý‘­C

ñì·Óæ›Ýû PDF ·©ž­AñãøÒð^Ï†¦¸¦§ Acrobat Reader ®e­A¾ìøäÝ‘ÏUÝCù„ÏÏÏ@ôæùB’J­A
Ïµï®Ýšð^Ï†¦§¯yù¾·“ûã­G

   * «s¨Š Acrobat Reader ¦§ñãøÒ script­AÝbñãøÒ script Ï§­A #!/bin/sh üîðzÝ­
     Ïõ® ús¬WÏUÝC®¾O­G

     LANG=C;export LANG

     üo¬Ó¦§÷š­Aú¡ Acrobat Reader üQù„¾Ý¦§·ü¾×æ{Ý­ñãøÒ­AÝpüQ Netscape óÏèóû
     ¸×·ü¾×æ{Ý­¯­¸£¾\î…¦¡ñãøÒ©­Aú|ýœ¾Ö¾¨«T¦§Ý‘ªø­C
   * Ýb¸R¾Oïœ¾šÏ§¨‚ÏJ LANG=C­AñN Acrobat Reader ¦§·ü¾×æ{Ý­·“ûãü]¸wªøð^Ï†­C

ôiÏ@ùB÷ˆøT­A«Ñüs«u Adobe ùtý× (http://www.Adobe.com)­C
  ------------------------------------------------------------------------

2.6 SQL Reference ôÔïœù¥Ï@ðà PDF ·

ùC¾¯©¥Žy¦§­uùØ¾× DB2 ·©ž©w­v¦ç¨ìÏÏ­A®¾X SQL Reference ªø PDF ©‘Ý­¾BÝüùƒ
¾U­CThis is incorrect.

µ”æMÝCÝL¦§©¥ŽyÝüùƒ¾U­AÝà¾Bùƒ¾Uªêû‹·ü¦§©¥÷ûüœ¾¨«T­AÝìªO¾uÝüÏ@ðà PDF ·©ž­A¾Ý
¾]õtÏFùƒ¾U­CPDF ·ÝWªO db2s0x70­C
  ------------------------------------------------------------------------

Ýw÷Ó¯Pª[§c

ü­¾ö¾¨ì

   * Ï@î‰Ýw÷Ó÷ˆøT
        o 3.1 ÏU÷¸ãÝüÏ„ï¸¦§ DB2 ñqŽíî÷¦§Ýw÷Ó©M¾¢
        o 3.2 Ýb Windows 2000 ÏWÝw÷Ó DB2
        o 3.3 Ç”¸¢úõýÏ¦¡¾HîSõO¬ÔÝsøØ¸w÷q¦§ýó¶…øíÇD
        o 3.4 Windows 2000 ¦§ IPX/SPX üq®Hù¢¸wÏ„ï¸
        o 3.5 Ïî DB2 ®eÏ@¦¸Ïõ®e¾ìøñÏŒ DB2 æ{õ€
        o 3.6 ðYÏwÝw÷Óù„¾Ý DB2 ýœ®~­A«ÑÝbÝw÷Ó DB2 Ïõ® øäÝ‘ db2iupdt
        o 3.7 ü]¸w Linux ·“ûã¾HøäÝ‘ DB2 ññùŒÏÏÏá
        o 3.8 DB2 Universal Database Enterprise Edition Ï× DB2 Connect
          Enterprise Edition for Linux on S/390
        o 3.9 DB2 Universal Database Enterprise - Extended Edition for UNIX
          õ™ütÏJ¦—
        o 3.10 HP-UX ¦§ shmseg ©™Ïáø¥¬’
        o 3.11 ýó¶… IBM Visual ðš·xññùŒ÷ˆ©’©w
        o 3.12 Ýsù£ðš·xññùŒ÷ˆ©’©w

   * DB2 Data Links Manager õ™ütÏJ¦—
        o 4.1 Dlfm ¦§ñãøÒ¾½ñ¥øT©õ­Gù£ño afsfid Ýrð§©æo¾Ö¨—¯~
        o 4.2 ü]¸wü’¾ö®OÝs·¦§ Tivoli Storage Manager ÇçõO
        o 4.3 DFS ñqŽíî÷ñãøÒæ{Ý­¦§§Ø§Ñ¦ô­¯íùD
        o 4.4 §ÒúçÝb AIX ¦§÷ˆ©’Çæý·©ž§èýzæ{Ý­® §íæ{õ€
        o 4.5 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G DCE-DFS ·“ûã÷Þ¦§
          ÇB¾~Ýw÷Ó¦`úNù’ôæ
        o 4.6 ¾½ñ¥¦§ "dlfm add_prefix" ®¾O
        o 4.7 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G ùØ¾× db2setup Ï«
          ¾×æ{Ý­Ýb AIX ÏWÝw÷Ó DB2 Data Links Manager
        o 4.8 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­GDCE-DFS ® ÷mÝw÷Óõ@
          ú~
        o 4.9 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G ùØ¾× Smit ùàÏƒøÒ
          Ýw÷Ó DB2 Data Links Manager
        o 4.10 Ýw÷Ó¸Mª[§c DB2 Data Links ¦§ DFS ñqŽíî÷ñãøÒæ{Ý­
        o 4.11 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for Solaris
        o 4.12 øwû‹ AIX ÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ¦k
        o 4.13 øwû‹ Solaris õ@ú~·“ûãÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ
          ¦k
        o 4.14 øwû‹ Windows NT ÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ¦k
        o 4.15 ü’¾ö AIX ÏW¦§øO¨ì·©žùtý×
        o 4.16 Ýb Windows NT ÏW÷ˆ©’ÇæýÏÏ¦§ Administrator ÷sýåñM¾×v
        o 4.17 ñN Data Links File System Filter (DLFF) Ýw÷Ó¦§øO÷ïŒùüÞÏ™
             + 4.17.1 ÝbÝw÷Ó® øO÷øT©õ
        o 4.18 ùØ¾× SMIT ÷¥øœÝw÷Ó DLFM Ï÷¾¢¾iî…ú|øœ¾hÇB¾~¦§·©žôø
        o 4.19 ô}¸lÏõ®e/ùM¸w¾Dûq÷œÝW§ë
        o 4.20 ùØ¾× DLFM­Gñq DB2 ÷ˆ©’©wñÓñ¢ DB2 Data Links Manager ® ¦§ýMøœ
          øÒõ@
        o 4.21 DLFM1001E (ús¦§¨—¯~øT©õ)
        o 4.22 DLFM ü]¸wª[§c·¨‹ôæ
        o 4.23 Ýb AIX ÏWøäÝ‘ Data Links/DFS Script dmapp_prestart ©æo¾Ö¨—
          ¯~
        o 4.24 Tivoli Space Manager ¯P Data Links óÆÝX
             + 4.24.1 ¾\î…ððùŒ
        o 4.25 ýŽ 4 üû Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX
             + 4.25.1 Ï@î‰Ýw÷Ó¦`úNù’ôæ
                  + 4.25.1.1 ñq DB2 File Manager ¦¸¾¯ 5.2 ýó¶…ù DB2 Data
                    Links Manager ¦¸¾¯ 7

   * Ýw÷Ó¯Pª[§c÷¾R÷ˆ©’
        o 5.1 ýŽ 5 üû Ýb UNIX õ@ú~ùtý×ÏWÝw÷Ó DB2 ñqŽíî÷
             + 5.1.1 HP-UX ©™Ïáæ{Ý­ª[§cø¥¬’
        o 5.2 ýŽ 12 üû øäÝ‘ñzÝêÏv¦§·ü¾×æ{Ý­
             + 5.2.1 ùØ¾× Run-Time Client üsæý÷ˆ©’©wÏ«¾×æ{Ý­
             + 5.2.2 UNIX ñqŽíî÷ùØ¾× ODBC Ýsù£ DB2
        o 5.3 ýŽ 24 üû ü]÷mµpÝXùtý×ùàÝsù£Ýhð®÷ˆ©’ùàú«
             + 5.3.1 µpÝXùtý×
                  + 5.3.1.1 ððùŒ
             + 5.3.2 Ýw÷Ó DB2 Relational Connect
                  + 5.3.2.1 Ýb Windows NT Ý›¦AóûÏWÝw÷Ó DB2 Relational
                    Connect
                  + 5.3.2.2 Ýb AIX­BLinux Ï× Solaris õ@ú~·“ûãÝ›¦AóûÏWÝw÷Ó
                    DB2 Relational Connect
        o 5.4 ýŽ 26 üû Ýsù£ Oracle ÷ˆ©’ùàú«
             + 5.4.1 Ï†¾¢¨—¯~
        o 5.5 Ýsù£ Sybase ÷ˆ©’ùàú« (ús¬Wüû÷`)
             + 5.5.1 ús¬W Sybase ÷ˆ©’ùàú«ÝšµpÝXÝ›¦Aóû
                  + 5.5.1.1 ùB’J 1­Gü]¸w·“ûãš¬’ùÇõ¢úsü]¸w·æn¨ì
                  + 5.5.1.2 ùB’J 2­GñN DB2 ÇæýÝš Sybase ñqŽíî÷ün‚ (ôÔ AIX
                    ¯P Solaris)
                  + 5.5.1.3 ùB’J 3­Gð®úsùØ¾× DB2 ©žùã
                  + 5.5.1.4 ùB’J 4­G®¾áùÇü]¸wÏôðñ·©ž
                  + 5.5.1.5 ùB’J 5­G®¾á¾~¬h
                  + 5.5.1.6 ùB’J 6­G¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’
                  + 5.5.1.7 ùB’J 7­G®¾áÝ›¦Aóû
                  + 5.5.1.8 ¨‹¾×¦§­GùB’J 8­Gü]¸w CONNECTSTRING Ý›¦Aóû¨‹ôæ
                  + 5.5.1.9 ùB’J 9­G®¾áùØ¾×¦Þû‹ªM
                  + 5.5.1.10 ùB’J 10­G®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW
             + 5.5.2 ®¸w Sybase Ýr«Xðô
        o 5.6 ùØ¾× ODBC Ýsù£ Microsoft SQL Server ÷ˆ©’ùàú« (ús¬Wüû÷`)
             + 5.6.1 ús¬W Microsoft SQL Server ÷ˆ©’ùàú«ÝšµpÝXÝ›¦Aóû
                  + 5.6.1.1 ùB’J 1­Gü]¸w·“ûãš¬’ (ôÔ AIX)
                  + 5.6.1.2 ùB’J 2­GøäÝ‘ Shell Script (ôÔ AIX)
                  + 5.6.1.3 ùB’J 3­G¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’
                  + 5.6.1.4 ùB’J 4­Gð®úsùØ¾× DB2 ©žùã (ôÔ AIX)
                  + 5.6.1.5 ùB’J 5­G®¾á¾~¬h
                  + 5.6.1.6 ùB’J 6­G®¾áÝ›¦Aóû
                  + 5.6.1.7 ùB’J 7­G®¾áùØ¾×¦Þû‹ªM
                  + 5.6.1.8 ùB’J 8­G®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW
                  + 5.6.1.9 ùB’J 9­G¨‹¾×¦§­G·•ño ODBC øl¶š
             + 5.6.2 «’ªd Microsoft SQL Server Ýr«Xðô

  ------------------------------------------------------------------------

Ï@î‰Ýw÷Ó÷ˆøT

  ------------------------------------------------------------------------

3.1 ÏU÷¸ãÝüÏ„ï¸¦§ DB2 ñqŽíî÷¦§Ýw÷Ó©M¾¢

ðYðnÏU÷¸ãÝüÏ„ï¸¦§ DB2 ñqŽíî÷¦§Ýw÷Ó©M¾¢­A¾]ªA¸ãÝü¦¸¾¯ 7 Ïõ®e¦§ñqŽíî÷­A «Ñüs
«uù IBM DB2 Client Application Enabler Pack ¦§§“ðô­Aù„§“õ}ªø­G
http://www.ibm.com/software/data/db2/db2tech/clientpak.html
  ------------------------------------------------------------------------

3.2 Ýb Windows 2000 ÏWÝw÷Ó DB2

Ýb Windows 2000 ÏW­AÝw÷ÓÝb®e¦¸ DB2 ÏõÏW©­A¸×ªOð®úsÝw÷Óý{Ý‘¦¸¾¯©­A «Ñ«T¸w
ñN¸ãÝü DB2 ¦AøÔ¦§Ý^ï_¨‹ôæü]¸wªø­uTake No Action­v­C
  ------------------------------------------------------------------------

3.3 Ç”¸¢úõýÏ¦¡¾HîSõO¬ÔÝsøØ¸w÷q¦§ýó¶…øíÇD

÷ˆ©’©wýó¶…Ïõ® ­AÝp¦GîSõO¬ÔÝsøØ USER ¸× CURRENT SCHEMA üQ¾×ùà¸w÷qúõýÏ¦¡¦«
Ž‘­A®húõýÏ¦¡ú|šÝùæL¦kùØ¾×­C ùãÝp­G

   create view v1 (c1) as values user

Ýb¦¸¾¯ 5­AUSER ¸M CURRENT SCHEMA ¦§÷ˆ©’Çç®ªªO CHAR(8)­C Ýê¦¸¾¯ 6 ø_­A¾ÝðÞüQ
¸w÷qªø VARCHAR(128)­C ¾¯«dùãÏÏ­AÝp¦GúõýÏ¦¡ªO¾¥¦¸¾¯ 5 ¸ã®¾á­A¦«Ž‘ cl ¦§÷ˆ©’
Çç®ª®hªø CHAR­C ýó¶…Ïõ® ùØ¾×úõýÏ¦¡­A¾Ýú|ÝbøäÝ‘©ô­«sŽô­AÝìªO­A¾Ýú|Ý]ªø÷ˆ©’
Çç®ªÏœýÝà¾½ñ¥­C

÷¥ùMÏŠ©žªO¸¤ñ¢ùÇð®ús®¾á÷àúõýÏ¦¡­C ÝbñÓñ¢úõýÏ¦¡Ïõ®e­Aªd÷á SYSCAT.VIEWS ®ª¨ì
úõýÏ¦¡ùà¶^ù£¾×ùà®¾áúõýÏ¦¡¦§¯y¦k­C ùãÝp­G

select text from syscat.views where viewname='<>'

  ------------------------------------------------------------------------

3.4 Windows 2000 ¦§ IPX/SPX üq®Hù¢¸wÏ„ï¸

Ýû÷ˆøTªOø¥úà­uõ™ütÏJ¦—­vÏ@©¥¦§­uÝw÷Ó­vüoÏ@üû¦§­u¾iî…¦§¾DñqüsñæûˆøÔ­vüoÏ@
÷`­C

ÏwÏ«õG¦§üq®Hù¢¸wÏ„ï¸ûØ¦¡ùÇÏœõû¾ç¾¨«T­C ÏœÏ„ï¸ùØ¾× IPX/SPX üsñæ OS/2 ¸× UNIX
®ªÝ›¦Aóû¦§ Windows 2000 ñqŽíî÷­C Ï]ÏœÏ„ï¸ùØ¾× IPX/SPX üsñæ Windows 2000 Ý›
¦Aóû¦§ OS/2 ¸× UNIX ®ªñqŽíî÷­C
  ------------------------------------------------------------------------

3.5 Ïî DB2 ®eÏ@¦¸Ïõ®e¾ìøñÏŒ DB2 æ{õ€

Ýû÷ˆøTªOø¥úà­uDB2 for Windows õ™ütÏJ¦—­vÏ@©¥ÏÏ¦§ýó¶…÷ˆøT­C

ðYñzðnÏîÝb Windows óöóûÏWøäÝ‘¦§®eÏ@¦¸ DB2­A Ýw÷Óæ{Ý­¸ãïœù¥¦§Žæõi¾]õtÏFñN
DB2 DLL ®OîdÝbøOóÑ‚¦§æ{õ€ÝC¾š­C ÝbÝû©­Añz¾i¾HñNÝC¾š÷Þ¦§æ{õ€¾HÏƒøÒÏŠÝ­øñ
ÏŒ­A¸×¦ÞìÝw÷Óæ{Ý­ÝêøÒÇ”ñ¬üoù€æ{õ€­C ®ŽüñzÝbÝw÷ÓÏõ®eÏƒøÒøñÏŒ¸ãÝü DB2 æ{
õ€­A¾HµžõKªy¾½÷ˆ©’­C ðn«T¸w DB2 æ{õ€ÏœÝbøäÝ‘ÏÏ¦§üÞù×ÏŠÝ­ªOüzûL­uWindows ¦A
øÔ­væeðñùà·Óæ›ùtý×¦§æ{õ€­C Ýb­uWindows ¦AøÔ­væeðñÏÏ­A«Ñ«T¸wùSÝüøäÝ‘ DB2 ¦A
øÔ­B OLAP ¦AøÔ­B¸×÷ˆ©’ðš·x¦AøÔ­C

æ—:
     Windows ¾ð¾xÏWÏ@Ý÷¾uî…øäÝ‘Ï@§¦¸¾¯¦§ DB2­C ùãÝp­AñzæL¦kÝbÝP¬Ó¦§
     Windows óöóûÏWÝP©øäÝ‘ DB2 ¦¸¾¯ 7 ¸M DB2 ¦¸¾¯ 6­CðYñzðnñN DB2 ¦¸¾¯ 7
     Ýw÷ÓÝbÏwÝw÷Ó DB2 ¦¸¾¯ 6 ¦§óöóûÏW­A Ýw÷Óæ{Ý­ú|ÝbÝw÷Óïµô­õRøœ DB2 ¦¸¾¯
     6­C«Ñø¥úàóAú¡¦§õ™ütÏJ¦—Ïƒ¾U­A ¾Hù£ñoñq DB2 ¦§®eÏ@¦¸ùàýó¶…¦§ªêÇ”÷ˆøT­C

  ------------------------------------------------------------------------

3.6 ðYÏwÝw÷Óù„¾Ý DB2 ýœ®~­A«ÑÝbÝw÷Ó DB2 Ïõ® øäÝ‘ db2iupdt

ÏUÝC÷ˆøTÝbñz¦§­uõ™ütÏJ¦—­vÝw÷ÓÏ†¾¢ÏÏÏwïœù¥­C

Ýb UNIX ®ªùtý×ÏWÝw÷Ó DB2 UDB ¦¸¾¯ 7 ©­AðYÏwÝw÷Ó DB2 ýœ®~­A ñz¯íðnøäÝ‘
db2iupdt ®¾O­A¾Hõ¢úsñzðnùØ¾×¾¯ýœ®~úsîS¸Ò¦§©žùã­CÝüù€îS¸ÒðnÝbøäÝ‘üoðà®¾OÏõ
® Ï~î…ùØ¾×­C
  ------------------------------------------------------------------------

3.7 ü]¸w Linux ·“ûã¾HøäÝ‘ DB2 ññùŒÏÏÏá

Ýû÷ˆøTÏ§õt¸¢­uõ™ütÏJ¦—­vÏ@©¥¦§­uÝw÷Ó DB2 ññùŒÏÏÏá­vüoÏ@üû­C

¶öô} Linux ¦§ DB2 Ýw÷Óæ{Ý­ùÇÝ^ùýž§íóöæ›æ­Ïõ® ­A «Ñµ„ÏJÏUÝC®¾O­Bü]¸w¾¨«T¦§
·“ûã­A¾HøäÝ‘ DB2­uññùŒÏÏÏá­v­G

   su -l <©žùãÝW§ë>
   export JAVA_HOME=/usr/jdk118
   export DISPLAY=<óöóûÝW§ë>:0

æM® ­Aô}ñã¾tÏ@ðàýž§íóöæ›æ­ùÇµ„ÏJ­G

   su root
   xhost +<óöóûÝW§ë>

Ç”üª÷àýž§íóöæ›æ­­A¦ÐÝ^ñzænÏJªø©žùãó™Ýü¦Þ ID ¦§ýž§íóö­A ùÇµ„ÏJ®¾O­G

   db2cc

¾HñãøÒ­uññùŒÏÏÏá­v­C
  ------------------------------------------------------------------------

3.8 DB2 Universal Database Enterprise Edition Ï× DB2 Connect Enterprise
Edition for Linux on S/390

DB2 Universal Database Enterprise Edition Ï× DB2 Connect Enterprise Edition
ý{Ýb¾iÝb Linux/390 ÏWùØ¾×ÏF­C ÝbÝw÷Ó Linux ù S/390 óöóûÏWÏõ®e­A ñz·ü÷àðnúN
Ç¥ùün‚Ï×æw‚¦§¯íùD­G

æw‚

S/390 9672 Generation 5 ¸×¾HÏW­AMultiprise 3000­C

ün‚

   * SuSE Linux v7.0 for S/390 ¸× Turbolinux Server 6 for zSeries Ï× S/390
   * ©™Ïá¬hÝ÷ 2.2.16­Aõt S/390 ðž÷æ{Ý­ («ÑùœÏUðz)
   * glibc 2.1.3
   * libstdc++ 6.1

Linux/390 ¯íðnÏUÝCðž÷æ{Ý­­G

   * Ýû©Ïœ¯íðnðž÷æ{Ý­­C

ðY¯íüÞús¦§õ¢ús÷ˆøT­A«ÑÝš http://www.software.ibm.com/data/db2/linux §“î÷­C

æ—:

  1. ¾uÏ„ï¸ 32 ÝÏ÷¦§ Intel-based Linux Ï× Linux/390­C

  2. Linux/390 ¦§ DB2 ¦¸¾¯ 7 ¾¬ïœù¥ÏUÝCôæ¾­G
        o DB2 UDB Enterprise - Extended Edition
        o DB2 Extenders
        o Data Links Manager
        o DB2 Administrative Client
        o šõ¢üqÝ‘«XÏ„ï¸
        o LDAP Ï„ï¸

  ------------------------------------------------------------------------

3.9 DB2 Universal Database Enterprise - Extended Edition for UNIX õ™ütÏJ¦—

ýŽ 5 üû­uÝb Linux ÏWÝw÷Ó¸Mª[§c DB2 Universal Database­v®¾X Linux EEE ¶Oôø
ÏÏ¦§ùCÏ@ðàûˆ‚÷`¶I¾ýôúùÆü’ªêÝP¦§ kernel­Bglibc Ï× libstdc++ ¬hÝ÷­C

DB2 EEE for Linux ÷å¾×¦¸¾iñqÏUÝC§“î÷ÏU÷­G
http://www6.software.ibm.com/dl/db2udbdl/db2udbdl-p
  ------------------------------------------------------------------------

3.10 HP-UX ¦§ shmseg ©™Ïáø¥¬’

ñz¦§­uõ™ütÏJ¦—­vÏ@©¥ÏÏïœù¥ÝüÇ”õ¢ús HP-UX ©™Ïáª[§cø¥¬’¦§÷ˆøTÏœ¾¨«T­C ·ü÷à¸¨
ýÏ HP-UX ¦§ shmseg ©™Ïáø¥¬’¦§®ŽüðÔ­C

·üõ‹¾×ûwü]¦§ HP-UX ðÔ (120)­C
  ------------------------------------------------------------------------

3.11 ýó¶… IBM Visual ðš·xññùŒ÷ˆ©’©w

DB2 Universal Database for Windows õ™ütÏJ¦—ïœù¥ÝüÇ” Windows NT ¸M Windows
2000 ôiÝ‘ DB2 Universal Database ¦¸¾¯ 7 ù†®ªÝw÷Óïµô­­AÝpÝ¢ýó¶…õ@¾×ÏÏðš·xññ
ùŒ÷ˆ©’©w¦§÷ˆøT­CÝp¦Gðnýó¶…Ï@ðà¾HÏW¦§ðš·xññùŒ÷ˆ©’©w­A ®h¾ýôúùØ¾×ðš·xññùŒ÷ˆ©’
©w§èýzæ›æ­ôiÝ‘¦ç¾[÷ˆ©’©w¦§ýó¶…­CÏ@Ý÷¾uî…ÝüÏ@ðàðš·xññùŒ÷ˆ©’©wõ@¾×­Cð®úsænÏJ
÷ˆ©’ðš·xÏÏÏá©­AÝp¦GÏWÏ@ðà÷ˆ©’©wÏœªOñzðnùØ¾×¦§÷ˆ©’©w­A ®h¾ýôúùØ¾×ðš·xññùŒ÷ˆ
©’©w§èýzæ›æ­ùàôiÝ‘ænøOñz¸ãðnùØ¾×¦§÷ˆ©’©w­C
  ------------------------------------------------------------------------

3.12 Ýsù£ðš·xññùŒ÷ˆ©’©w

¸¢ Windows NT Ýw÷Ó DB2 ¦¸¾¯ 7­A®¾á DB2 ¦¸¾¯ 7 ðš·xññùŒ÷ˆ©’©w¸Mðš·xÝ›¦Aóû­C
Ýp¦GñzÝüÝWªø Visual Warehouse ¦§ðš·xññùŒ÷ˆ©’©w­A «ÑñNõtÝüðš·xññùŒ÷ˆ©’©w¦§
DB2 Ý›¦AóûÏîù DB2 ¦¸¾¯ 7­Aðš·xññùŒ÷ˆ©’©w¦§ïyðz÷ˆ©’ú|ýó¶…­A ¾Hù¥ DB2 ¦¸¾¯
7 ÷ˆ©’ðš·xÏÏÏá¸ãùØ¾×­CñìŽ~Ž•ùØ¾×¦¸¾¯ 7­A«Ñýó¶…¸ãÝü¦§ðš·xññùŒ÷ˆ©’©w­C DB2 ¦¸
¾¯ 7 Ýw÷Óïµô­­Aõ@¾×ÏÏ¦§ðš·xññùŒ÷ˆ©’©w¦§ïyðz÷ˆ©’ú|ýó¶…ù¦¸¾¯ 7­Cñìýó¶…¦ç¾[ðš
·xññùŒ÷ˆ©’©w¦§ïyðz÷ˆ©’­A«ÑùØ¾×ðš·xññùŒ÷ˆ©’©wýó¶…Ï«¾×æ{Ý­­C¸¢ Windows NT­A¨‹
ù£ô}¸l --> æ{Ý­ôø --> IBM DB2 --> ðš·xññùŒ÷ˆ©’©w§èýz­AôiÝ‘ñãøÒ­CÝüÇ”ðš·xññ
ùŒ÷ˆ©’©w¦§ýó¶…­A«Ñø¥ó\Windows DB2 Universal Database õ™ütÏJ¦—
  ------------------------------------------------------------------------

DB2 Data Links Manager õ™ütÏJ¦—

  ------------------------------------------------------------------------

4.1 Dlfm ¦§ñãøÒ¾½ñ¥øT©õ­Gù£ño afsfid Ýrð§©æo¾Ö¨—¯~

øwû‹Ýb DCE-DFS ·“ûã÷ÞøäÝ‘¦§ Data Links Manager­AÝp¦G dlfm Ý]ÏUÝC¨—¯~ñãøÒ¾½
ñ¥­A «Ñª½÷á IBM ¦AøÔÏÏÏá­G

   ù£ño afsfid Ýrð§©æo¾Ö¨—¯~

ú¡ùØ¾× "dlfm add_prefix" ænøOù Data Links Manager ¦§ DFS ·©žôøüQõRøœ©­A
ñNú|æo¾Ö¨—¯~­C
  ------------------------------------------------------------------------

4.2 ü]¸wü’¾ö®OÝs·¦§ Tivoli Storage Manager ÇçõO

ñì®¸wü’¾ö®OÝs·ùØ¾×ù§Ï@ðà TSM §èýzÇçõO­A«Ñü]¸w DLFM_TSM_MGMTCLASS DB2 æn¨ì
ôæ¾Ï@ðàóAú¡¦§§èýzÇçõOÝW§ë­C
  ------------------------------------------------------------------------

4.3 DFS ñqŽíî÷ñãøÒæ{Ý­¦§§Ø§Ñ¦ô­¯íùD

DFS ñqŽíî÷ñãøÒæ{Ý­ªø¨‹¾×¦§Ï÷¾¢­Añz¾i¾HÝb DB2 Universal Database ñqŽíî÷¸×Ý›
¦AóûÝw÷Óïµô­õ@¨‹óš­C µ”æM DFS ñqŽíî÷ñãøÒæ{Ý­øäÝ‘©ùÇÏœ¯íðn DB2 UDB ñqŽíî÷¸×
Ý›¦Aóû­A ÝìªO­AÝw÷Ó DFS ñqŽíî÷ñãøÒæ{Ý­Ïõ®eñz¾ýôúÝw÷Ó DB2 Universal Database
ñqŽíî÷­C øœÏF DFS ñqŽíî÷ñãøÒæ{Ý­Ýr«X¯íðn 2 MB ¦§§Ø§Ñ¦ô­¾~­A ÝbÝw÷Ó DFS ñq
Žíî÷ñãøÒæ{Ý­ªø DB2 øäÝ‘©ô­ñqŽíî÷Ýw÷Ó¦§Ï@ü­¾ö©­A ñz·ü÷à¾t¾~®Oîd 40 MB ¦§ÇB
¾~§Ø§Ñ¦ô­­C Ýw÷Ó DFS ñqŽíî÷ñãøÒæ{Ý­ªø DB2 §èýzñqŽíî÷¸× DB2 Ý›¦AóûÝw÷ÓÏõÏ@
ü­¾ö©­Añz¯íðnõ¢Ýh¦§§Ø§Ñ¦ô­­C ÝüÇ” DB2 Universal Database ýœ®~¸ã¯íðn¦§§Ø§Ñ
¦ô­­A÷âýà÷ˆøT«Ñø¥ó\ DB2 for UNIX õ™ütÏJ¦—Ïƒ¾U­C
  ------------------------------------------------------------------------

4.4 §ÒúçÝb AIX ¦§÷ˆ©’Çæý·©ž§èýzæ{Ý­® §íæ{õ€

dlfm see ®¾O¦§¨‚¾XÝüšõ¢­C æo¾XÝû®¾Oùà§ÒúçÝb AIX ¦§÷ˆ©’Çæý·©ž§èýzæ{Ý­® 
§íæ{õ€­Aæý¦G¯PÏUÝC¸ã¾šÇçÝ­G

     PID     PPID     PGID   RUNAME    UNAME        ETIME DAEMON NAME
   17500    60182    40838     dlfm     root        12:18 dlfm_copyd_(dlfm)
   41228    60182    40838     dlfm     root        12:18 dlfm_chownd_(dlfm)
   49006    60182    40838     dlfm     root        12:18 dlfm_upcalld_(dlfm)
   51972    60182    40838     dlfm     root        12:18 dlfm_gcd_(dlfm)
   66850    60182    40838     dlfm     root        12:18 dlfm_retrieved_(dlfm)
   67216    60182    40838     dlfm     dlfm        12:18 dlfm_delgrpd_(dlfm)
   60182        1    40838     dlfm     dlfm        12:18 dlfmd_(dlfm)

DLFM SEE ðnùDÝù¾\­C

ªA¸úÏ§¦§ÝW§ëªø dlfm ©žùã¦§ÝW§ë­A¾¯ùãÝW§ëªø "dlfm"­C
  ------------------------------------------------------------------------

4.5 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G DCE-DFS ·“ûã÷Þ¦§ÇB¾~Ýw÷Ó¦`
úNù’ôæ

Ýb­uÝw÷Ó¾ìùMñ›¾¢­vøØªq÷Þ­A·ü÷àús¬W¦§ús÷ˆøT­G

   ñzÏ]¾ýôúÝw÷Ó e-fix for DFS 3.1­A¸×¦Þ PTF ôø 1 (šÝù¾i¾×©)­C
   ¾iÝb¾HÏU§“î÷õ„ù e-fix ¦§÷ˆøT­G
   http://www.transarc.com/Support/dfs/datalinks/efix_dfs31_main_page.html

¾HÏ×­G

   ¾ýôúÝbÝw÷Ó Data Links Manager Ïõ®eøäÝ‘ dfs ñqŽíî÷­C
   ùØ¾× db2setup ¸× smitty­C

Ýb­uKeytab ·©ž­vøØªq÷Þ­AÝüðà¨—¯~·ü÷àõ¢¾¨ªø­G

   õtÝü¾D‚¸MüqÝ‘«X÷ˆøT¦§ keytab ·©ž­A·ü÷à§ëªø datalink.ktb ¸M ....

¾¨«T¦§ÝW§ë­Gdatalink.ktb ªO¾×ÝbÏUðñ¦§«dùãÏÏ­C ­uKeytab ·©ž­vøØªq·ü÷àýóù
­uDCE-DFS ® ÷mÝw÷Óõ@ú~­vÏõÏU­A Ý]ªø DLMADMIN ©žùã®¾á® ­Aüoðà·©žÏ~î…®¾á­C

Ýb­uData Links File Manager Ý›¦Aóû¯PñqŽíî÷­vÏÏ­A «Ñ¦`úN­A¾ýôúÝb Data Links
Manager ñqŽíî÷Ïõ®e¾ìÝw÷Ó Data Links Manager Ý›¦Aóû­C

·ü÷àús¬W­uü’¾ö¾¨ì­vüû÷`­G

   ðYü’¾öÏŠ¦kªOøwû‹¾¯§í·©žùtý×­A
   üo¾ýôúªO DFS ·©žùtý×÷Þ¦§¾¨ì­C
   «Ñ«T¸w DFS §èýz¦ÞÏw®¾áÝû DFS ·©žôø­C
   Ýû·©žôø·ü÷àÏœªO DMLFS ·©žôø­C

  ------------------------------------------------------------------------

4.6 ¾½ñ¥¦§ "dlfm add_prefix" ®¾O

øwû‹Ýb DCE/DFS ·“ûã÷ÞøäÝ‘¦§ Data Links Manager­A dlfm add_prefix ®¾O¾iî…ú|
¾½ñ¥­AÝàÝ^¶Ñ«Xªø -2061 (ü’¾ö¾½ñ¥)­CðYæo¾ÖÝû¦ª¦p­A«ÑøäÝ‘ÏUÝCùB’J­G

  1. æo¾X dlfm stop ®¾OùàøñÏŒ Data Links Manager ¦§ñ`ónæ{Ý­æ{õ€­C
  2. æo¾X dlfm stopdbm ®¾OùàøñÏŒ DB2 æ{õ€­C
  3. æo¾X dce_login root ®¾Oùàù£ño dce root ¯{Çã­C
  4. æo¾X dlfm startdbm ®¾OùàñãøÒ DB2 æ{õ€­C
  5. æo¾X dlfm add_prefix®¾OùàænøO Data Links Manager ¦§·©žôø­C
  6. æo¾X dlfm start ®¾OùàñãøÒ Data Links Manager ñ`ónæ{Ý­æ{õ€­C

  ------------------------------------------------------------------------

4.7 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G ùØ¾× db2setup Ï«¾×æ{Ý­Ýb
AIX ÏWÝw÷Ó DB2 Data Links Manager

Ýb­uÏw®¾á DB2 ÷ˆ©’©w DLFM_DB­vøØªqÏÏ­ADLFM_DB ùÇÏœªO®¾áÝb DCE_DFS ·“ûã
ÏÏ­C¾ýôú¾H® ÷mÝw÷ÓùB’JùàøäÝ‘­C

Ýb­uDMAPP ¦§ DCE-DFS ûw¾ìñãøÒæn¨ì­vøØªqÏÏ­AùB’J 2 ·ü÷àšõ¢ÝpÏU­G

   2. ús¬W®¾Où /opt/dcelocal/tcl/user_cmd.tcl­A¾H«T¸w DFS ñãøÒ©Ï]ñãøÒÏF DMAPP­C

  ------------------------------------------------------------------------

4.8 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­GDCE-DFS ® ÷mÝw÷Óõ@ú~

·ü÷àús¬WÏUÝC­uõûÝù Data Links Manager Ýw÷Ó­vüû÷`­G

Ýb Data Links Manager Ý›¦AóûÏW­A¾ýôúøäÝ‘ÏUÝCùB’J­A¾HõûÝùÝw÷Ó­G

  1. Ýb­uÝw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­vüoüû¦§­uDCE-DFS ·“ûã¦§
     ÇB¾~Ýw÷Ó¦`úNù’ôæ­vüo÷`÷Þ­A ñN keytab ·®¾áªø­uKeytab ·©ž­vÏõÏU¦§úõ
     ðn­C
  2. ¾H root ùðÏ·­A¨‚ÏJÏUÝC®¾O¾HñãøÒ DMAPP­G

        stop.dfs all
        start.dfs all

  3. ÝpÏUÝCùB’J­AùØ¾× dce root ¯{ÇãùàøäÝ‘ "dlfm setup"­C
       a. ¾H Data Links Manager ¦§ DLMADMIN §èýz¦ÞænÏJ­C
       b. ¾H root ùðÏ·­Aæo¾X dce_login­C
       c. ¨‚ÏJ®¾O­Gdlfm setup­C

Ýb Data Links Manager ñqŽíî÷ÏW­A¾ýôúøäÝ‘ÏUÝCùB’J­A¾HõûÝùÝw÷Ó­G

  1. Ýb­uÝw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­vüoüû¦§­uDCE-DFS ·“ûã¦§
     ÇB¾~Ýw÷Ó¦`úNù’ôæ­vüo÷`÷Þ­A ñN keytab ·®¾áªø­uKeytab ·©ž­vÏõÏU¦§úõ
     ðn­C
  2. ¾H root ùðÏ·­A¨‚ÏJÏUÝC®¾O¾HñãøÒ DMAPP­G

        stop.dfs all
        start.dfs all

  ------------------------------------------------------------------------

4.9 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­G ùØ¾× Smit ùàÏƒøÒÝw÷Ó DB2
Data Links Manager

©éóé­uSMIT ® ÷mÝw÷Óõ@ú~­vüû÷`­Aðžõ‹ùB’J 7 ¾H®¾X "dce_login root" ®¾O¾ýôú
Ýb "dlfm setup" Ïõ®eæo¾X­C Ïœ¯íðnùB’J 11­C ÝbùB’J 6 (dlfm server_conf) ¸MùB
’J 8 (dlfm client_conf) õûÝù©­Aú|ÝêøÒøäÝ‘ÝûùB’J­C Ï]«ÑýóøœùB’J 12 (dlfm
start)­C ðYðnõûÝùÝw÷Ó­A«ÑøäÝ‘ÏUÝCùB’J­G

  1. Ýb­uÝw÷Ó¸Mª[§c DB2 Data Links Manager for AIX­vüoüû¦§­uDCE-DFS ·“ûã¦§
     ÇB¾~Ýw÷Ó¦`úNù’ôæ­vüo÷`÷Þ­A ñN keytab ·®¾áªø­uKeytab ·©ž­vÏõÏU¦§úõ
     ðn­C
  2. ¾H root ùðÏ·­A¨‚ÏJÏUÝC®¾O¾HñãøÒ DMAPP­G

        stop.dfs all
        start.dfs all

  ------------------------------------------------------------------------

4.10 Ýw÷Ó¸Mª[§c DB2 Data Links ¦§ DFS ñqŽíî÷ñãøÒæ{Ý­

Ýb­uª[§c DFS ñqŽíî÷ñãøÒæ{Ý­­vüû÷`÷Þ­AñNÏUÝC÷ˆøT¾[ùùB’J 2­G

   øäÝ‘ "secval" ®¾Oüqñ`ú|õûÝùª[§c­C
   ÏœûL­AÏ]¾iî…¯íðnð®úsñãøÒóöóû­C
   ðYÝbÝsù£ READ PERMISSION DB ·©ž©æoý{øíÇD­A
   «Ñð®úsñãøÒÝw÷Ó DB2 DFS ñqŽíî÷ñãøÒæ{Ý­¦§óöóû­C

  ------------------------------------------------------------------------

4.11 Ýw÷Ó¸Mª[§c DB2 Data Links Manager for Solaris

ÝbÝw÷Ó DB2 Data Links Manager for Solaris Ïõ® ¾ýôúøäÝ‘ÏUÝCøÒõ@­G

  1. ñNÏUÝCÏTÝ‘ús¬Wù /etc/system ·©ž­G

     set dlfsdrv:glob_mod_pri=0x100800
     set dlfsdrv:glob_mesg_pri=0xff
     set dlfsdrv:ConfigDlfsUid=UID

     ù„ÏÏ UID ¾N¦¡ id dlfm ¦§ùØ¾×¦Þ ID­C
  2. ð®úsô}óö­A¾HùØšõ¢¾Ö©Ž­C

  ------------------------------------------------------------------------

4.12 øwû‹ AIX ÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ¦k

øœÏF Disk Copy ¸M XBSA Ïõ¾~­AñzÏ]¾i¾HùØ¾× Tivoli Storage Manager (TSM) ùàü’
¾öÝ¸¢ Data Links Ý›¦Aóû÷Þ¦§·©ž­C

ðYðnñN Tivoli Storage Manager õ@ªø®OÝsÝ›¦Aóû­G

  1. Ýb Data Links Ý›¦AóûÏWÝw÷Ó Tivoli Storage Manager­C ÷âýà÷ˆøT­A«Ñø¥Ýã
     Tivoli Storage Manager¦§ýœ®~Ï†¾¢­C
  2. ¾H Tivoli Storage Manager Ý›¦Aóûùàæn¨ì Data Links Ý›¦AóûñqŽíî÷·ü¾×æ{
     Ý­­C ÷âýà÷ˆøT­A«Ñø¥Ýã Tivoli Storage Manager¦§ýœ®~Ï†¾¢­C
  3. ñNÏUÝC·“ûãš¬’ús¬Wù Data Links Manager §èýz¦Þ¦§ db2profile ¸×
     db2cshrc script ·­G

        (øwû‹ Bash­BBourne ¸× Korn shell)
        export DSMI_DIR=/usr/tivoli/tsm/client/api/bin
        export DSMI_CONFIG=$HOME/tsm/dsm.opt
        export DSMI_LOG=$HOME/dldump
        export PATH=$PATH:$DSMI_DIR

        (øwû‹ C shell)
        setenv DSMI_DIR /usr/tivoli/tsm/client/api/bin
        setenv DSMI_CONFIG ${HOME}/tsm/dsm.opt
        setenv DSMI_LOG ${HOME}/dldump
        setenv PATH=${PATH}:$DSMI_DIR


  4. «Ñ«T¸w dsm.sys TSM ùtý×¨‹ôæ·Ý¸¢ $DSMI_DIR ¾¨ì÷Þ­C
  5. «Ñ«T¸w dsm.opt TSM ùØ¾×¦Þ¨‹ôæ·Ý¸¢ INSTHOME/tsm ¾¨ì÷Þ­A ÝbÝû
     INSTHOME ªO Data Links Manager §èýz¦Þ¦§ø_¸l¾¨ì­C
  6. ñN PASSWORDACCESS ¨‹ôæü]¸wªøýœ¾Ö­AÝb
     /usr/tivoli/tsm/client/api/bin/dsm.sys Tivoli Storage Manager ùtý×¨‹ôæ
     ·÷Þ­C
  7. ùØ¾×ýœ¾Ö¨‹ôæÝbýŽÏ@Ý÷ñãøÒ Data Links ·©ž§èýzæ{Ý­Ïõ®e­A æn¨ì TSM üqÝ‘
     «X­C ùØ¾×üoðàÏŠ¦k­A ú¡ Data Links ·©ž§èýzæ{Ý­ô}¸l TSM Ý›¦Aóû¦§üs«u
     ©­AñzÏœ¯íðnïœù¥üqÝ‘«X­C ÷âýà÷ˆøT­A«Ñø¥Ýã TSM ¦§ýœ®~Ï†¾¢­C
  8. ñN DLFM_BACKUP_TARGET æn¨ìš¬’ü]¸wù TSM­C ÝbÝûùã÷ÞñN¸¨ýÏ
     DLFM_BACKUP_DIR_NAME æn¨ìš¬’¦§ðÔ­C üo¬Óú|ñãøÒ Tivoli Storage Manager
     ¦§ü’¾ö¨‹ôæ­C

     æ—:

       1. ðYñzÝbøäÝ‘©ô­÷Þ­Ašõ¢ TSM ¸M§Ø§ÑÏõô­¦§ DLFM_BACKUP_TARGET æn¨ìš
          ¬’ü]¸w­Añz·ü÷àûŒŽñü’¾ö®OÝs·Ïœú|ýóùüÞ¦¤®¸w¦§®OÝsÝ÷m­CùãÝp­AðY
          ñz¾Hü]¸wù TSM ¦§ DLFM_BACKUP_TARGET æn¨ìðÔùàñãøÒ Data Links ·©ž
          §èýzæ{Ý­­A ùÇñNæn¨ìðÔšõ¢ù§Ø§ÑÝ÷m­A®h¸ãÝüüÞ¦¤®OÝs¦§·©žñN·xÝsÝb
          §Ø§Ñ¦§úsÝ÷m÷Þ­C¾ì®e®OÝsù TSM ¦§·©žñNÏœú|ýóùús¦§§Ø§ÑÝ÷m­C

       2. ðYðn÷mï®ûwü]¦§ TSM §èýzÇçõO­A¾i¾HùØ¾×Ï@ðà§ëªø DLFM_TSM_MGMTCLASS
          ¦§úsæn¨ìš¬’­CðYÝûæn¨ìš¬’§–®—Ýb¾¬ü]¸w¦§¦ª§A­AñææêñNú|ùØ¾×ûwü]¦§
          TSM §èýzÇçõO­C
  9. ¨‚ÏJ dlfm stop ®¾OùàøñÏŒ Data Links ·©ž§èýzæ{Ý­­C
 10. ¨‚ÏJ dlfm start ®¾OùàñãøÒ Data Links ·©ž§èýzæ{Ý­­C

  ------------------------------------------------------------------------

4.13 øwû‹ Solaris õ@ú~·“ûãÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ¦k

øœÏF Disk Copy ¸M XBSA Ïõ¾~­AñzÏ]¾i¾HùØ¾× Tivoli Storage Manager (TSM) ùàü’
¾öÝ¸¢ Data Links Ý›¦Aóû÷Þ¦§·©ž­C

ðYðnñN Tivoli Storage Manager õ@ªø®OÝsÝ›¦Aóû­G

  1. Ýb Data Links Ý›¦AóûÏWÝw÷Ó Tivoli Storage Manager­C ÷âýà÷ˆøT­A«Ñø¥Ýã
     Tivoli Storage Manager¦§ýœ®~Ï†¾¢­C
  2. ¾H Tivoli Storage Manager Ý›¦Aóûùàæn¨ì Data Links Ý›¦AóûñqŽíî÷·ü¾×æ{
     Ý­­C ÷âýà÷ˆøT­A«Ñø¥Ýã Tivoli Storage Manager¦§ýœ®~Ï†¾¢­C
  3. ñNÏUÝC·“ûãš¬’ús¬Wù Data Links Manager §èýz¦Þ¦§ db2profile ¸×
     db2cshrc script ·­G

        (øwû‹ Bash­BBourne ¸× Korn shell)
        export DSMI_DIR=/opt/tivoli/tsm/client/api/bin
        export DSMI_CONFIG=$HOME/tsm/dsm.opt
        export DSMI_LOG=$HOME/dldump
        export PATH=$PATH:/opt/tivoli/tsm/client/api/bin

        (øwû‹ C shell)
        setenv DSMI_DIR /opt/tivoli/tsm/client/api/bin
        setenv DSMI_CONFIG ${HOME}/tsm/dsm.opt
        setenv DSMI_LOG ${HOME}/dldump
        setenv PATH=${PATH}:/opt/tivoli/tsm/client/api/bin


  4. «Ñ«T¸w dsm.sys TSM ùtý×¨‹ôæ·Ý¸¢ /opt/tivoli/tsm/client/api/bin ¾¨ì
     ÷Þ­C
  5. «Ñ«T¸w dsm.opt TSM ùØ¾×¦Þ¨‹ôæ·Ý¸¢ INSTHOME/tsm ¾¨ì÷Þ­A ÝbÝû
     INSTHOME ªO Data Links Manager §èýz¦Þ¦§ø_¸l¾¨ì­C
  6. ñN PASSWORDACCESS ¨‹ôæü]¸wªøýœ¾Ö­AÝb
     /opt/tivoli/tsm/client/api/bin/dsm.sys Tivoli Storage Manager ùtý×¨‹ôæ
     ·÷Þ­C
  7. ùØ¾×ýœ¾Ö¨‹ôæÝbýŽÏ@Ý÷ñãøÒ Data Links ·©ž§èýzæ{Ý­Ïõ®e­A æn¨ì TSM üqÝ‘
     «X­C ùØ¾×üoðàÏŠ¦k­A ú¡ Data Links ·©ž§èýzæ{Ý­ô}¸l TSM Ý›¦Aóû¦§üs«u
     ©­AñzÏœ¯íðnïœù¥üqÝ‘«X­C ÷âýà÷ˆøT­A«Ñø¥Ýã TSM ¦§ýœ®~Ï†¾¢­C
  8. ñN DLFM_BACKUP_TARGET æn¨ìš¬’ü]¸wù TSM­C ÝbÝûùã÷ÞñN¸¨ýÏ
     DLFM_BACKUP_DIR_NAME æn¨ìš¬’¦§ðÔ­C üo¬Óú|ñãøÒ Tivoli Storage Manager
     ¦§ü’¾ö¨‹ôæ­C

     æ—:

       1. ðYñzÝbøäÝ‘©ô­÷Þ­Ašõ¢ TSM ¸M§Ø§ÑÏõô­¦§ DLFM_BACKUP_TARGET æn¨ìš
          ¬’ü]¸w­A ñz·ü÷àûŒŽñü’¾ö®OÝs·Ïœú|ýóùüÞ¦¤®¸w¦§®OÝsÝ÷m­CùãÝp­AðY
          ñz¾Hü]¸wù TSM ¦§ DLFM_BACKUP_TARGET æn¨ìðÔùàñãøÒ Data Links ·©ž
          §èýzæ{Ý­­A ùÇñNæn¨ìðÔšõ¢ù§Ø§ÑÝ÷m­A®h¸ãÝüüÞ¦¤®OÝs¦§·©žñN·xÝsÝb
          §Ø§Ñ¦§úsÝ÷m÷Þ­C¾ì®e®OÝsù TSM ¦§·©žñNÏœú|ýóùús¦§§Ø§ÑÝ÷m­C

       2. ðYðn÷mï®ûwü]¦§ TSM §èýzÇçõO­A¾i¾HùØ¾×Ï@ðà§ëªø DLFM_TSM_MGMTCLASS
          ¦§úsæn¨ìš¬’­CðYÝûæn¨ìš¬’§–®—Ýb¾¬ü]¸w¦§¦ª§A­AñææêñNú|ùØ¾×ûwü]¦§
          TSM §èýzÇçõO­C
  9. ¨‚ÏJ dlfm stop ®¾OùàøñÏŒ Data Links ·©ž§èýzæ{Ý­­C
 10. ¨‚ÏJ dlfm start ®¾OùàñãøÒ Data Links ·©ž§èýzæ{Ý­­C

  ------------------------------------------------------------------------

4.14 øwû‹ Windows NT ÏW¦§ DB2 Data Links Manager ¨‹óšü’¾öÏŠ¦k

ùCú¡ DATALINK ðÔï­ÏJùÆÝü DATALINK ¦«Ž‘¦§¦¡©‘© (¸w÷qªøÝ^ï_)­A ú|Ýwñ’ Data
Links Ý›¦Aóû¦§ªêû‹·ü DATALINK ·©ž­A¾Hü’¾öù®OÝsÝ›¦Aóû­C¾®eùà¯­­ADisk Copy
(ûwü]ÏŠ¦k) ¸M Tivoli Storage Manager ªOÏ„ï¸·©žü’¾öù®OÝsÝ›¦Aóû¦§ùƒ§¨‹ôæ­C
¾¬ùà¦§ DB2 Data Links Manager for Windows NT ¦¸Ý÷ñNÏ„ï¸ù„¾Ýù¥·üøà¦§ü’¾öïC‚
¸Mün‚­C

Disk Copy (ûwü]ÏŠ¦k)

     Ýb DB2 Ý›¦AóûÏW¨‚ÏJ backup ®¾O©­A üoðà®¾O¾i«T¸w÷ˆ©’©w÷Þ¦§Çæý·©žú|
     Ýb Data Links Ý›¦AóûÏWü’¾öù DLFM_BACKUP_DIR_NAME ·“ûãš¬’¸ã®¸w¦§¾
     ¨ì­C üoðàš¬’¦§ûwü]ðÔªO c:\dlfmbackup­A ÝbÝû c:\ ¦¡¾š Data Links
     Manager ¦§ü’¾öÝw÷Ó§Ø§Ñóö­C

     ðYðnñNÝûš¬’ü]¸wù c:\dlfmbackup­A«Ñ¨‚ÏJÏUÝC®¾O­G

        db2set -g DLFM_BACKUP_DIR_NAME=c:\dlfmbackup


     DLFM_BACKUP_DIR_NAME ·“ûãš¬’®¸w¦§Ý÷mÏœî… Ý¸¢ùØ¾× Data Links­u·©ž
     ùtý×ûL¶oóû­v¦§·©žùtý×ÏW­AÝà¯íðn¦§¦ô­¾i¾×¸¢ñz®¸wæûü’¾ö·¦§¾¨ì÷Þ­C

     ÝP©­A«Ñ«T¸w DLFM_BACKUP_TARGET š¬’÷g¾¥¨‚ÏJÏUÝC®¾OÏwü]¸wªø LOCAL­G

        db2set -g DLFM_BACKUP_TARGET=LOCAL

     ü]¸w¸×šõ¢üoù€š¬’Ïõ® ­A«ÑùØ¾× dlfm stop ¸M dlfm start ®¾OùàøñÏŒùÇð®
     úsñãøÒ Data Links ·©ž§èýzæ{Ý­­C

Tivoli Storage Manager

     ðYðnñN Tivoli Storage Manager õ@ªø®OÝsÝ›¦Aóû­G
       1. Ýb Data Links Ý›¦AóûÏWÝw÷Ó Tivoli Storage Manager­C ÷âýà÷ˆøT­A«Ñ
          ø¥Ýã Tivoli Storage Manager¦§ýœ®~Ï†¾¢­C
       2. ¾H Tivoli Storage Manager Ý›¦Aóûùàæn¨ì Data Links Ý›¦AóûñqŽíî÷·ü
          ¾×æ{Ý­­C ÷âýà÷ˆøT­A«Ñø¥Ýã Tivoli Storage Manager¦§ýœ®~Ï†¾¢­C
       3. ®”Ï@ÏUô}¸l­AæM® ¨‹ù£ü]¸w --> ññùŒ¾x --> ùtý×­C õYú|ô}ñã­uùtý×Ï§
          ©e­væ›æ­­C ¨‹ù£·“ûã¬Ñã­A ùÇ¨‚ÏJÏUÝC·“ûãš¬’¸Mû‹·üðÔ­G

           š¬’                    ðÔ
           DSMI_DIR                c:\tsm\baclient
           DSMI_CONFIG             c:\tsm\baclient\dsm.opt
           DSMI_LOG                c:\tsm\dldump
       4. «Ñ«T¸w dsm.sys TSM ùtý×¨‹ôæ·Ý¸¢ c:\tsm\baclient ¾¨ì÷Þ­C
       5. «Ñ«T¸w dsm.opt TSM ùØ¾×¦Þ¨‹ôæ·Ý¸¢ c:\tsm\baclient ¾¨ì÷Þ­C
       6. ñN PASSWORDACCESS ¨‹ôæü]¸wªøýœ¾Ö­A Ýb c:\tsm\baclient\dsm.sys
          Tivoli Storage Manager ùtý×¨‹ôæ·÷Þ­C
       7. ùØ¾×ýœ¾Ö¨‹ôæÝbýŽÏ@Ý÷ñãøÒ Data Links ·©ž§èýzæ{Ý­Ïõ®e­A æn¨ì TSM
          üqÝ‘«X­C ùØ¾×üoðàÏŠ¦k­A ú¡ Data Links ·©ž§èýzæ{Ý­ô}¸l TSM Ý›¦Aóû
          ¦§üs«u©­AñzÏœ¯íðnïœù¥üqÝ‘«X­C ÷âýà÷ˆøT­A«Ñø¥Ýã TSM ¦§ýœ®~Ï†¾¢­C
       8. ùØ¾×ÏUÝC®¾OñN DLFM_BACKUP_TARGET ·“ûãš¬’ü]¸wù TSM­G

             db2set -g DLFM_BACKUP_TARGET=TSM

          ÝbÝûùã÷ÞñN¸¨ýÏ DLFM_BACKUP_DIR_NAME ·“ûãš¬’¦§ðÔ­C üo¬Óú|ñãøÒ
          Tivoli Storage Manager ¦§ü’¾ö¨‹ôæ­C

          æ—:

            1. ðYñzÝbøäÝ‘©ô­÷Þ­Ašõ¢ TSM ¸M LOCAL Ïõô­¦§
               DLFM_BACKUP_TARGET ·“ûãš¬’ü]¸w­Añz·ü÷àûŒŽñü’¾ö®OÝs·Ïœú|ýó
               ùüÞ¦¤®¸w¦§®OÝsÝ÷m­CùãÝp­AðYñz¾Hü]¸wù TSM ¦§
               DLMF_BACKUP_TARGET ·“ûãš¬’ùàñãøÒ Data Links ·©ž§èýzæ{Ý­­A
               ùÇñNù„ðÔšõ¢ù LOCAL­A®h¸ãÝüüÞ¦¤®OÝs¦§·©žñN·xÝsÝb§Ø§Ñ¦§úsÝ
               ÷m÷Þ­C¾ì®e®OÝsù TSM ¦§·©žñNÏœú|ýóùús¦§§Ø§ÑÝ÷m­C

            2. ðYðn÷mï®ûwü]¦§ TSM §èýzÇçõO­A¾i¾HùØ¾×Ï@ðà§ëªø
               DLFM_TSM_MGMTCLASS ¦§ús·“ûãš¬’­CðYÝûš¬’§–®—Ýb¾¬ü]¸w¦§¦ª
               §A­AñææêñNú|ùØ¾×ûwü]¦§ TSM §èýzÇçõO­C
       9. ¨‚ÏJ dlfm stop ®¾OùàøñÏŒ Data Links ·©ž§èýzæ{Ý­­C
      10. ¨‚ÏJ dlfm start ®¾OùàñãøÒ Data Links ·©ž§èýzæ{Ý­­C

  ------------------------------------------------------------------------

4.15 ü’¾ö AIX ÏW¦§øO¨ì·©žùtý×

©¥ÏÏ¯­¸£¾ýôúøñÏŒ Data Links Manager­A Ýà¶ö«uü’¾ö·ü÷àùÞóé·©žùtý×ùà¯sõ@­C ÏU
ÝCÏŠ¦køœ¾høñÏŒ Data Links Manager ¦§¯íùD­A ¾Dðnøwû‹¯íðn÷–ø¦¾i¾×¸Ò¦§ùØ¾×¦Þ­C

  1. Ýsù£ CLI ùàú«· quiesce.c Ï× Shell Script online.sh­Cüoù€·©žÝ¸¢
     /samples/dlfm ¾¨ì­C
  2. «sŽô quiesce.c­G

        xlC -o quiesce  -L$HOME/sqllib/lib -I$HOME/sqllib/include -c quiesce.c

  3. ¾H root ùðÏ·­AÝbùÆÝü DLFS ·©žùtý×¦§÷`¶IÏWøäÝ‘ Script­C

shell script online.sh øýü]ñzÝb Data Link Manager ÷`¶IÏWùÆÝü®ª¨ìæn¨ì (øwû‹
¾H Data Link Manager ùàæn¨ì¦§ùCðà÷ˆ©’©w)­CÏ]øýü] /etc/filesystems ùÆÝü DLFS
·©žùtý×¦§õûóÆæn¨ì­Cshell script øäÝ‘ÏUÝCøÒõ@­G

   * ·RÏŒ÷ˆ©’©w÷Þ¦§¸ãÝü¦¡©‘­Aüoù€÷ˆ©’©w¾H Data Links Manager ùàæn¨ì­Cüo¬Óú|
     øñÏŒ¸ãÝüús¦§ª­øÒ­C
   * ñN·©žùtý×¾Høá¦·©žùtý×ùà÷¥øœ÷Ó÷¸×ð®ús÷Ó÷­C
   * øäÝ‘·©žùtý×ü’¾ö­C
   * ñN·©žùtý×¾H¦ù£/¬gÏJ·©žùtý×ùà÷¥øœ÷Ó÷¸×ð®ús÷Ó÷­C
   * ð®ü] DB2 ¦¡©‘­FÏ]ïNªO­A÷¥øœ·RÏŒ¦ª§A­C

¾ýôúðžõ‹ Script ¾HóAÝXñz¦§·“ûã­AÝpÏU¸ã¾š­G

  1. ¨‹ù£ü’¾ö®¾O­AùÇ¸¤÷m¸¢ script ¦§ do_backup ù‡¬’­C
  2. ü]¸w Script Ï§¦§ÏUÝC·“ûãš¬’­G
        o DLFM_INST­Gü]¸wüoðàù DLFM ©žùãÝW§ë­C
        o PATH_OF_EXEC­Gü]¸wüoðàù "quiesce" ¾iøäÝ‘·¸ãÝb¦§÷“©|­C

¾HÏUÝC®¾O¸I¾s script­G

   online.sh <filesystem_name>

  ------------------------------------------------------------------------

4.16 Ýb Windows NT ÏW÷ˆ©’ÇæýÏÏ¦§ Administrator ÷sýåñM¾×v

Ýb Windows NT ÏW­Aû‹¸¢Ïjü­Ï·¦§ù‡¬’­AÏ@ðàµäŽí¸¢ Adminstrator ÷sýå¦§ùØ¾×¦Þ Ç”
¸¢ùØ¾× DataLink ùàÇæý¦§·©ž¸M UNIX ÏW¦§ root ùØ¾×¦ÞÝüªêÝP¦§ñM¾×v­C ÏUðñ¦§
¦¡©‘ñNùƒ¦ÞøæÏFÏ¤÷–­C

 õ@ú~                    Unix (root)              Windows NT
                                                  (Administrator)
 õ¢ÝW                    ªO                       ªO
 Ïœ¯íýøO¾iÝsù£·©ž      ªO                       ªO
 õRøœ                    ªO                       õ_ («ÑªíÏUðñ¦§¯­¸£)
 õ¢ús                    ªO                       õ_ («ÑªíÏUðñ¦§¯­¸£)

æ—:
     NTFS ÏœÏûü\üoù€õ@ú~Ýbøá¦·©žÏWøäÝ‘­C Administrator ùØ¾×¦Þ¾i¾HôôõQõûÝù
     üoù€õ@ú~­A ÏŠ¦kªøñã¾×·©ž¦§¬gÏJü\¾iv­C

  ------------------------------------------------------------------------

4.17 ñN Data Links File System Filter (DLFF) Ýw÷Ó¦§øO÷ïŒùüÞÏ™

ñz¾i¾Hšõ¢ dlfs_cfg ·©ž­A ñN Data Links File System Filter (DLFF) Ýw÷Ó¦§øO
÷ïŒùüÞÏ™­Cdlfs_cfg ·©žú|ô€ù strload ñ`Ý­ùà÷ÏJXøÒæ{Ý­Ï×ª[§cø¥¬’­C ·©ž
¦§Ý÷mÝb /usr/lpp/db2_07_01/cfg/ ¾¨ì­C üzûLý÷ûÇæý­AÏ]¾iÝb /etc ¾¨ìõ„ù
üoðà·©ž­C dlfs_cfg ·©ž¦§©‘Ý­ÝpÏU­G

    d 'driver-name' 'vfs number' 'dlfm id' 'global message priority'
      'global module priority' - 0 1


ù„ÏÏ­G

d
     d ø¥¬’®¸wðn÷ÏJXøÒæ{Ý­­C

driver-name
     driver-name ªOðn÷ÏJ¦§XøÒæ{Ý­¦§õûóÆ÷“©|­CùãÝp­A DB2 ¦¸¾¯ 7 ¦§õûóÆ÷“©|
     ªO /usr/lpp/db2_07_01/bin/dlfsdrv­CXøÒæ{Ý­ÝW§ëªO dlfsdrv­C

vfs number
     üoªO DLFS Ýb /etc/vfs ÏÏ¦§ vfs ôæ¾­C

dlfm id
     üoªO DataLinks Manager §èýz¦Þ¦§ùØ¾×¦Þ ID­C

global message priority
     üoªO¬søøT©õ·u¾ìôôõ€

global module priority
     üoªO¬sø¬ãýå·u¾ìôôõ€

0 1
     0 1 ªO¾×ùà®¾áÝûXøÒæ{Ý­®D«’¯s÷`¶I¦§÷–Ïp¬’Ýr­C ÷`¶IÝW§ëªOñN÷–Ïp¬’Ýr¦ç
     ¾[ùüQ«’¯s¦§XøÒæ{Ý­÷`¶IÝW§ëùà®¾á¦§­C Ïœ¾iæûôWûL 5 ðà¾HÏW¦§÷–Ïp¬’Ýr
     (0-4)­C

ý{ûˆÏÏ¦§«dùã¾iî…ÝpÏU­G

    d /usr/lpp/db2_07_01/bin/dlfsdrv 14,208,255,-1 - 0 1


ú|øO÷¦§øT©õªOùÞóé global message priority Ï× global module priority ¦§ü]¸w
ðÔÝà¸w­C ðYðnñNøO÷ïŒùüÞÏ™­Añz¾i¾Hšõ¢ global message priority ¦§ðÔ­C

Ýü 4 ðàøT©õ·u¾ìôôõ€¾i¾HùØ¾×­G

     #define LOG_EMERGENCY      0x01
     #define LOG_TRACING        0x02
     #define LOG_ERROR          0x04
     #define LOG_TROUBLESHOOT   0x08

Ïjü­¾ö DLFF ÏÏ¦§øT©õùØ¾× LOG_TROUBLESHOOT õ@ªøøT©õ·u¾ìôôõ€­C üo÷ÞªOÏ@ù€ï·¾N
ª[§c«dùã­G

Ýp¦Gñzîu¦§¯íðn§•®‘(emergency)øT©õÏ×¨—¯~øT©õ­A «ÑñN dlfs_cfg øt÷m·ÏÏ¦§¬sø
øT©õ·u¾ìôôõ€ü]¸wªø 5 (1+4)­G

       d /usr/lpp/db2_07_01/bin/dlfsdrv 14,208,5,-1 - 0 1


Ýp¦G¾u¯íðn¨—¯~øT©õ­A«ÑñN¬søøT©õ·u¾ìôôõ€ü]¸wªø 4­G

       d /usr/lpp/db2_07_01/bin/dlfsdrv 14,208,4,-1 - 0 1


Ýp¦GñzÏœ¯íðn DLFS øO÷­A ®hñN¬søøT©õ·u¾ìôôõ€ü]¸wªø 0­G

       d /usr/lpp/db2_07_01/bin/dlfsdrv 14,208,0,-1 - 0 1


4.17.1 ÝbÝw÷Ó® øO÷øT©õ

Ýp¦GñzÝbÝw÷ÓÏõ® ¯íðnøO÷§•®‘­B¨—¯~Ï×§ÇÇ›ñ’÷¥øT©õ­A ñz¾ýôúðžõ‹ dlfs_cfg ·
©ž­C dlfs_cfg ·©ž¦§Ý÷mÝb/usr/lpp/db2_07_01/cfg ¾¨ì­C ¬søøT©õ·u¾ìôôõ€¾ý
ôúü]¸wªø 255 (üÞÏj·u¾ìôôõ€) ú| 13 (8+4+1)­C ñN·u¾ìôôõ€ü]¸wªø 13 (8+4+1) ú|
øO÷§•®‘­B¨—¯~Ï×§ÇÇ›ñ’÷¥÷ˆøT­C

Ýbü]¸w¬søøT©õ·u¾ìôôõ€Ïõ® ­A÷¥øœ÷Ó÷ DLFS ûL¶o·©žùtý×­A ùÇð®ús÷ÏJ dlfsdrv
XøÒæ{Ý­¾HÝb÷ÏJ©ùØ¾×ús¦§·u¾ìôôõ€ðÔ­C Ýbð®ús÷ÏJ dlfsdrv XøÒæ{Ý­Ïõ® ­A ¾ý
ôúð®ús÷Ó÷ DLFS ûL¶o·©žùtý×­C

æ—:
     ¦«ùÝA®žšõ¢ dlfs_cfg ·©ž­A ¾“Ý¢® Ž•¦§ dlfsdrv XøÒæ{Ý­÷ÏJú|ùØ¾×ªêÝP
     dlfs_cfg ü]¸wðÔ­C

  ------------------------------------------------------------------------

4.18 ùØ¾× SMIT ÷¥øœÝw÷Ó DLFM Ï÷¾¢¾iî…ú|øœ¾hÇB¾~¦§·©žôø

ÝbñqÝw÷Ó Data Links Manager ¦§ AIX óöóûÏW÷¥øœÝw÷Ó DB2 (¦¸¾¯ 5­B6 ¸× 7) Ïõ
®e­A «Ñ¨¡ï`ÏUÝCùB’J­G

  1. ¾H root ¦§ùðÏ·­AùØ¾×ÏUÝC®¾Oü’¾ö /etc/vfs­G

     cp -p /etc/vfs /etc/vfs.bak

  2. ÷¥øœÝw÷Ó DB2­C
  3. ¾H root ¦§ùðÏ·­A¾×ùB’J 1 ¸ãøæ¦§ü’¾öù£¾N /etc/vfs­G

     cp -p /etc/vfs.bak /etc/vfs

  ------------------------------------------------------------------------

4.19 ô}¸lÏõ®e/ùM¸w¾Dûq÷œÝW§ë

ñz¾ýôúùM¸wùCÏ@¾x DB2 Ý›¦AóûÏ×÷ˆ©’ÇæýÝ›¦Aóû¦§ÝW§ë­Cñz¾ýôúðn¦óûDüoù€¾Dûq÷œÝW
§ë­AÏ~î…‡ÇãÝw÷Óõ@ú~­C Ýbüsñæù­uDB2 Data Links ·©ž§èýzæ{Ý­­v©­ADB2 UDB
Ý›¦Aóûú|Ï§ü­ô€øeÏUÝC÷ˆøTù DLFM­G

   * ÷ˆ©’©wÝW§ë
   * ©žùãÝW§ë
   * ¾Dûq÷œÝW§ë

æM®  DLFM ú|ñNÝû÷ˆøT¯P¾Ý¦§Ï§ü­¦¡©‘õ@Ï¤û‹­A ¾HùM¸wªOõ_©eü\üs«uÝù¾á­C¾uÝü÷ˆ©’
©wÝW§ë­B©žùãÝW§ë¸M¾Dûq÷œÝW§ë¦§ýåÝXüœÏwùØ¾× dlfm add_db ®¾Oæ—¾Uù DLFM ©­A
üs«uÏ~ú|Ýù¾á­CÝb dlfm add_db ®¾OÏÏùØ¾×¦§¾Dûq÷œÝW§ë¾ýôú¸M DB2 UDB Ý›¦Aóû ¸ã
Ï§ü­ô€øe¦§¾Dûq÷œÝW§ëõû¾çªêý­C

ùØ¾×¾HÏUÝCÏŠÝ­¸ãñoù¦§¾Dûq÷œÝW§ë­G

  1. Ýb DB2 Ý›¦AóûÏW¨‚ÏJ hostname ®¾O­CùãÝp­AÝû®¾O¾iî…ú|ô€Ý^ db2server­C
  2. ©éóéñz¦§¾ð¾x­AøäÝ‘ÏUÝCù„ÏÏÏ@ôæ­G
        o Ýb AIX ÏW­A¨‚ÏJ host db2server ®¾O­Aù„ÏÏ db2server ªO¾ì®eùB’JÏÏ
          ¸ãñoù¦§ÝW§ë­C üoðà®¾O·ü÷àú|ô€Ý^ÇçÝÏUÝC¦§¨‚¾X­G

             db2server.services.com is 9.11.302.341,  Aliases:  db2server

        o Ýb Windows NT ÏW­A¨‚ÏJ nslookup db2server ®¾O­Aù„ÏÏ db2server ªO
          ¾ì®eùB’JÏÏ¸ãñoù¦§ÝW§ë­C üoðà®¾O·ü÷àú|ô€Ý^ÇçÝÏUÝC¦§¨‚¾X­G

             Ý›¦Aóû­Gdnsserv.services.com
             Ýõ}­G9.21.14.135
             ÝW§ë­Gdb2server.services.com
             Ýõ}­G9.21.51.178

        o Ýb Solaris ÏW­A¨‚ÏJ cat /etc/hosts | grep 'hostname'­CÝp¦G¾Dûq÷œ
          ÝW§ëÝb /etc/hosts ÏÏ®¸w©Ïœõt¯ƒøÝW§ë­A ®hüoðà®¾O·ü÷àú|ô€Ý^ÇçÝ
          ÏUÝC¦§¨‚¾X­G

          9.112.98.167 db2server loghost

          Ýp¦G¾Dûq÷œÝW§ë®¸w©õt¯ƒøÝW§ë­A®h®¾Oú|ô€Ý^ÇçÝÏUÝC¦§¨‚¾X­G

          9.112.98.167 db2server.services.com loghost

ÝbùØ¾× dlfm add_db ®¾Oæ—¾U DB2 UDB ÷ˆ©’©w©«Ñ¾× db2server.services.com õ@
ªø¾Dûq÷œÝW§ë­C Ýp¦GÝb dlfm add_db ®¾OÏÏùØ¾×¾“Ý¢ù„¾Ý¦§õOÝW­A ®h DB2 Ý›¦Aóû
Ï§ü­ù DLFM ¦§üs«uú|¾½ñ¥­C

ðYðnñN Data Links Ý›¦Aóûæ—¾Uù DB2 ÷ˆ©’©w­A ¾iùØ¾× DB2 "add datalinks
manager for database database_alias using node hostname port port_number"
®¾O­C

hostname ªO Data Links Ý›¦Aóû¦§ÝW§ë­CÝbÝû®¾OÏÏ¾iùØ¾×¾“Ý¢ Data Links Ý›¦Aóû
¦§Ýü©ŽõOÝW­C ø¥úàÝû Data Links Ý›¦Aóû¦§ DATALINK ðÔ¾ýôú¾× URL ðÔùà®¸w
hostname­F ¾‡õYÝb®ªœ URL ðÔæû DATALINK ¦«Ž‘©­A¾ýôúùØ¾× "add datalinks
manager" ®¾OÏÏ¸ãùØ¾×¦§ÝW§ë­C ùØ¾×ÏœÝP¦§õOÝWñNú|üyÝù SQL üîðzÝ­¾½ñ¥­C
  ------------------------------------------------------------------------

4.20 ùØ¾× DLFM­Gñq DB2 ÷ˆ©’©wñÓñ¢ DB2 Data Links Manager ® ¦§ýMøœøÒõ@

ú¡ùØ¾× DROP DATALINKS MANAGER ®¾Oñq÷ˆ©’©wñN DB2 Data Links Manager ñÓñ¢
©­A ®¾O¾¯ùðÏœú|ýMøœÇ”¸¢ DB2 Data Links Manager ¦§ªêÇ”÷ˆøT­CùØ¾×¦Þ¾i¾H¸£«T
Ýaø_¸l÷¥øœÇæý¾“Ý¢Çæýù÷ˆ©’©w¦§·©ž­A ¾HÏ×ü’¾ö÷ˆøT¦§¸UõœÝªôø­C üo¾i¾HùØ¾×
dlfm drop_dlm ®¾OùàõûÝù­Cüoðà®¾Oú|ñNîS¸w÷ˆ©’©w¦§¸ãÝü÷ˆøT®DÝPùB¦§õRøœ­CDB2
Data Links Manager ¾ýôúÝbøäÝ‘ÏÏ­AÝû®¾OÏ~ú|Ýù¾\­C ®Dñ`ð®ðn­GÝû®¾O¾uÝbñÓñ¢
DB2 Data Links Manager Ïõ® Ï~î…ùØ¾×­F õ_®h­AñNú|¾½¾hÇ”¸¢ DB2 Data Links
Manager ¦§ð®ðn÷ˆøT­A¾BæL¦kÝ^ï_­C

ðYðnû‹îS¸w÷ˆ©’©wø_¸l÷¥øœÇæýüBýzæ{õ€Ï×ü’¾ö÷ˆøT¦§¸UõœÝªôø­G

  1. ¾H­uData Links ·©ž§èýzæ{Ý­­v§èýz¦ÞùðÏ·ænÏJùtý×­C
  2. æo¾XÏUÝC®¾O­G

        dlfm drop_dlm database instance hostname

        ù„ÏÏ­G

            database ªO¯ú§í DB2 UDB ÷ˆ©’©w¦§ÝW§ë­F
            instance ªO÷ˆ©’©w¸ãÝb¦§©žùã­F
            hostname ªO÷ˆ©’©w¸ãÝb¦§ DB2 UDB Ý›¦Aóû¦§¾Dûq÷œÝW§ë­C

  3. æn¾X­C

ðY¯íõûóÆ¦§¾×¦kûˆøÔ«dùã­AÆ¾š·ü÷àÝpÝ¢ùØ¾×Ýû®¾O¦§ÏWÏUÏ†­A«Ñø¥ó\ Command
Reference­C

ÏwªøÝû®¾O®¾áÏFÏ@ðàús¦§¨—¯~«X («Ñø¥ó\4.21, DLFM1001E (ús¦§¨—¯~øT©õ))­C
  ------------------------------------------------------------------------

4.21 DLFM1001E (ús¦§¨—¯~øT©õ)

DLFM1001E: Ýb drop_dlm üBýzæ{õ€©æo¾Ö¨—¯~­C

ðÝ]­G

Data Links Manager æL¦kû‹®¸w¦§÷ˆ©’©wø_¸l÷¥øœÇæýÏ×¸UõœÝªôøüBýzæ{õ€­C üo¾i
î…Ý]ªøÏUÝC¾“Ï@ðÝ]Ýàæo¾Ö­G

   * Data Links Manager ÏœÝbøäÝ‘ÏÏ­C
   * ®¾OÏÏ®¸w¦§÷ˆ©’©w­B©žùãÏ×¾Dûq÷œÝW§ë¦§ýåÝXæL©Ž­C
   * Ýb Data Links Manager ¦§¾“Ï@Ï÷¾¢¦AøÔ¾½ñ¥­C

øÒõ@­G

«ÑøäÝ‘ÏUÝCùB’J­G

  1. «T¸w Data Links Manager ÝbøäÝ‘ÏÏ­CñãøÒ Data Links Manager­AÝp¦G¾ÝÏœÝb
     øäÝ‘ÏÏ­C
  2. «T¸w÷ˆ©’©w­B©žùãÏ×¾Dûq÷œÝW§ë¦§ýåÝX¸w÷qÏ@ðàÏwæ—¾U¦§÷ˆ©’©w­Cñz¾iÝb Data
     Links Manager ÏWùØ¾× "dlfm list registered databases" ®¾OùàûFù¾¦§­C
  3. Ýp¦G¨—¯~ÏïæMæo¾Ö­A«Ñø¥úà db2diag.log ·©žÏÏ¦§÷ˆøT­A ·ÓªdªOõ_Ýü¾“Ý¢Ï÷¾¢
     ¦AøÔ (ùãÝp­AConnection Management Service­B Transaction Management
     Service æ¾æ¾) ¾½ñ¥­C¦`úN db2diag.log ÏÏ¦§¨—¯~«X­A ùÇñŽù£¨—¯~«X¸üÏU¸ã®
     Žü¦§óAú¡øÒõ@­C

  ------------------------------------------------------------------------

4.22 DLFM ü]¸wª[§c·¨‹ôæ

dlfm setup dlfm.cfg ¨‹ôæÏwüQøœ¾h­CÝbÏ†¾¢ÏÏðYÝüïœÏ×­A«ÑÏ¸¾H¸¨ýÏ­C
  ------------------------------------------------------------------------

4.23 Ýb AIX ÏWøäÝ‘ Data Links/DFS Script dmapp_prestart ©æo¾Ö¨—¯~

Ýp¦G®¾O

/usr/sbin/cfgdmepi  -a "/usr/lib/drivers/dmlfs.ext"

¾½ñ¥­AÝàÝ^¶Ñ«Xªø 1 (ÝbñzøäÝ‘ Data Links/DFS Script dmapp_prestart)­A«ÑÝw÷Ó
DFS 3.1 ptfset1 ùàðž¾¨ cfgdmepi­C
  ------------------------------------------------------------------------

4.24 Tivoli Space Manager ¯P Data Links óÆÝX

DB2 Data Links Manager ý{ÝbÏwùÆÝü Tivoli Space Manager ¾\î…ÏW¦§·u¶I­C
Tivoli Space Manager Hierarchical Storage Manager (HSM) ñqŽíî÷æ{Ý­ ú|ÝêøÒñN
ÝX©‘·©žýó¶…Ýš·xÝs‚­A¾H§–@¾¯§í·©žùtý×ÏWîS¸w¬hÝ÷¦§¾i¾×¦ô­­C ú¡Ýsù£ýó¶…¦§
·©ž©­Aú|ÝêøÒð®ús¸I¾süoù€·©ž­AÝà¾B©eü\ùØ¾×¦Þýó¶…Ï×ð®ús¸I¾sîS¸w¦§·©ž­C

û‹¸¢¸ãùØ¾×·©žùtý×Ï§õt¯íðn¸wïµýóÝšýŽÏT¬h·xÝs‚ (ù„ÏÏ¦§·©žùtý×¦ô­¯íðnÝbÏ@
î‰ø•¶ÝÏW§èýz) ¦§Ïj®ª·©žÏõ®ÔÏ Ýàù¾­AüoðàúsîS¸Ò®šÝü·øõU­C Tivoli Space
Manager ¾®eïœù¥Ï@ù€ÏŠ¦kùà§èýzü\Ýh®ÔÏ ¦§ýŽÏT¬h·xÝs‚­C Tivoli Space Manager
¦§ DB2 Data Links Manager ús¾\î…ïœù¥õ¢Ïj¦§¬u¸Òùà§èýz DATALINK ·©ž¦ô­­C
Tivoli Space Manager ©eü\¸wïµ«åóÆ Data Links §èýz¦§·©žùtý×øt÷m­A µžõK¾¨ñ`
ùØ¾×ïµô­Ý]ýù¾GÝàóðP·©žùtý×ô¤§­¦§ðú·I­AÝàÏœ¯íðnÝb¸ãÝü·©ž¾iî…·xÝs¸¢ù„ÏÏ¦§
DB2 Data Links Manager ·©žùtý×ÏÏûw¾ìøt÷mùªøö¦§¦ô­­C

ús¬W Data Links ¯P HSM Ï„ï¸ù·©žùtý×

     ¾H Hierarchical Storage Management (HSM) ænøO·©žùtý×©­A «Ñ¾ì¾H HSM
     ænøOÝA¾H DataLinks File Manager ænøO­C
       1. ænøO HSM ©­A«ÑùØ¾×®¾O "dsmmigfs add /fs"­C
       2. ænøO DLM ©­A«ÑùØ¾×®¾O "dlfmfsmd/fs"­C

     ·©žùtý×¦§ Data Links Ï„ï¸üzûLÏUÝCæn¨ì­AÏØªMÝb HSM ·©žùtý×¦§
     /etc/filesystems Ïõªq÷ùÏÏ­G

        vfs = dlfs
        mount = false
        options = rw,Basefs=fsm
        nodename = -

ús¬W Data Links Ï„ï¸ùý{Ýs¦§ HSM ·©žùtý×
     ænøO DLM ©­A«ÑùØ¾×®¾O "dlfmfsmd/fs"­C

ús¬W HSM Ï„ï¸ùý{Ýs¦§ Data Links ·©žùtý×
       1. ænøO HSM ©­A«ÑùØ¾×®¾O "dsmmigfs add /fs"­C
       2. ænøO DLM ©­A«ÑùØ¾×®¾O "dlfmfsmd/fs"­C

ñq Data Links-HSM ·©žùtý×ýóøœ Data Links Ï„ï¸
     ýóøœ Data Links Ï„ï¸©­A«ÑùØ¾×®¾O "dlfmfsmd -j /fs"­C

ñq Data Links-HSM ·©žùtý×ýóøœ HSM Ï„ï¸
       1. ýóøœ HSM Ï„ï¸­A«ÑùØ¾×®¾O "dsmmigfs remove /fs"­C
       2. ýóøœ Data Links Ï„ï¸ªO "dlfmfsmd -j /fs"­C
       3. ænøO DLM ©­A«ÑùØ¾×®¾O "dlfmfsmd/fs"­C

ñq Data Links-HSM ·©žùtý×ýóøœ Data Links ¯P HSM Ï„ï¸
       1. ýóøœ HSM Ï„ï¸­A«ÑùØ¾×®¾O "dsmmigfs remove /fs"­C
       2. ýóøœ Data Links Ï„ï¸©­A«ÑùØ¾×®¾O "dlfmfsmd -j/fs"­C

4.24.1 ¾\î…ððùŒ

¾¯¾\î…Ýš¾®eôÔÏ„ï¸Ýb AIX ÏWùØ¾×­C

FC (Read permission DB) Çæý·¦§¨‹óš¸Òýó¶… (dsmmigrate) Ï×ù£Ý^¾u·ü¾¥ root
ùØ¾×¦ÞõûÝù­C
     Ýb Read Permission DB ·©žªø DataLink Manager Administrator (dlfm) ¦§
     ñ­¦pÏU­A¨‹óš¸Òýó¶…¾uî…¾¥·©žó™Ýü¦ÞøäÝ‘­CðYðnÝsù£üoÇç®ª·©ž­A ®h¯íðn¾D
     ûq÷œ÷ˆ©’©w§í¦§ýøO­C øáÏ@Ïœ¯íðnýøO¦§ùØ¾×¦Þªø root ùØ¾×¦Þ­Croot ùØ¾×¦Þ
     û‹ Read Permission DB ·©žøäÝ‘¨‹óš¸Òýó¶…Ï×ù£Ý^Ï¤÷–©e¸”­CôÔÝbýŽÏ@Ý÷ýó¶…
     ©­A dlfm ùØ¾×¦ÞÏ~î…ùØ¾×Ýü©Ž¦§ýøOýó¶… FC ·©ž­CðYÝbù£Ý^Ïõ® ûµ÷åýŽÏGÝ÷
     ýó¶…­A Ýûõ@ú~ú|¾½ñ¥­Aô€Ý^¨—¯~øT©õ "ANS1028S Ï§ü­æ{Ý­¨—¯~­C «Ñµpæ÷®ÔÏ 
     ¦AøÔ¾N¦¡­C" ®D root ùØ¾×¦ÞæL¦kû‹ FC ·©žøäÝ‘ dsmmigrate­CÏ@î‰Ýàù¾­AÝû
     ððùŒû‹Ýsù£·©žÝ›¦AóûÏW·©ž ¦§§èýz¦Þ¬vTÏœÏj­C

stat ¸M statfs ùtý×¸I¾sú|ñN Vfs Çç®ªÆ¾šªø fsm­AÝà®DÆ¾šªø dlfs­A µ”æM dlfs
÷Ó÷Ýb fsm ÏõÏW­C
     ÏWðzÝ‘ªø¾N¦¡ dsmrecalld ñ`ónæ{Ý­¦§¾¨ñ`¾\î…­Aù„Ýb·©žùtý×ÏWøäÝ‘ statfs
     ùà·Óªdù„ Vfs Çç®ªªOõ_ªø fsm­C

ðY·©ž¦§üÞÏp inode ÷û«Xªø FC (Read permission DB) Çæý¦§÷û«X­A ®h®¾O
"dsmls" ÏœÆ¾š¾“Ý¢¨‚¾X
     dsmls ®¾OÇçÝ ls ®¾O­Aù„ÝC¾š¾¥ TSM §èýz¦§·©ž­C Ïœ¯íðnùØ¾×¦ÞøÒõ@

  ------------------------------------------------------------------------

4.25 ýŽ 4 üû Ýw÷Ó¸Mª[§c DB2 Data Links Manager for AIX

4.25.1 Ï@î‰Ýw÷Ó¦`úNù’ôæ

4.25.1.1 ñq DB2 File Manager ¦¸¾¯ 5.2 ýó¶…ù DB2 Data Links Manager ¦¸¾¯ 7

ùB’J 3 ÏÏ¦§÷ˆøTÏœ¾¨«T­CùB’J 3 ·üÝpÏU¸ã¾š­G

"3. ¾H DLFM §èýz¦Þùð¾ö­AøäÝ‘ /usr/lpp/db2_07_01/adm/db2dlmmg ®¾O­C
  ------------------------------------------------------------------------

Ýw÷Ó¯Pª[§c÷¾R÷ˆ©’

  ------------------------------------------------------------------------

5.1 ýŽ 5 üû Ýb UNIX õ@ú~ùtý×ÏWÝw÷Ó DB2 ñqŽíî÷

5.1.1 HP-UX ©™Ïáæ{Ý­ª[§cø¥¬’

®Žüü]¸w HP-UX ©™Ïáæ{Ý­ø¥¬’¨—¯~®¾X msgmbn Ï× msgmax ·ü÷àü]¸wªø 65535 ¸×õ¢
ø¦­Cùƒðàø¥¬’üœ·ü÷àü]¸wªø 65535­C
  ------------------------------------------------------------------------

5.2 ýŽ 12 üû øäÝ‘ñzÝêÏv¦§·ü¾×æ{Ý­

5.2.1 ùØ¾× Run-Time Client üsæý÷ˆ©’©wÏ«¾×æ{Ý­

Run-Time Client Ïœî…¾×ùàüsæý÷ˆ©’©wÏ«¾×æ{Ý­ (ôžÏJ­Bôž¾X­Bð®ýå­B¸R¾OÝ‘üBýz
óû)­A ¾B DB2 CLI ú|Ýb÷ˆ©’©w¾i¾HùØ¾×·©žÏõ®eñN·©žüsæýùùCÏ@ðà÷ˆ©’©w­C ñz¾ý
ôúõ‹¾× DB2 Administration Client ¸× DB2 Application Development Client­C

Ýb÷ˆ©’©w¾i¾HùØ¾×üoù€÷ˆ©’©wÏ«¾×æ{Ý­¸M DB2 CLI üsæý·©žÏõ®e­A¾ýôúñN÷à÷ˆ©’©w¸M
¾ÝðÞÏõô­ôiÝ‘üsñæ­C §“÷“·“ûãÏU­AÝp¦GñzùØ¾×ÏœÝPõ@ú~ùtý×¦§Ýhð®ñqŽíî÷­A¸×ªOÏœÝP
¦§ DB2 ¦¸¾¯¸×¦AøÔæ{Ý­æ¾î­Añz¾ýôúøùÏWüsæýÝUðàõ@ú~ùtý×¸M DB2 ¦¸¾¯ýåÝX¦§Ï«¾×
æ{Ý­­C

5.2.2 UNIX ñqŽíî÷ùØ¾× ODBC Ýsù£ DB2

ÝbýŽ 12 üû (­uøäÝ‘ñzÝêÏv¦§·ü¾×æ{Ý­­v) ÏÏïœù­A ¾H ODBC ñqŽíî÷·ü¾×æ{Ý­¸×
ODBC SDK ùàÝw÷Ó ODBC XøÒæ{Ý­§èýzæ{Ý­­A ®h¯íðnõ¢ús odbcinst.ini­C üo¬Ó¦§¯­
¦kÏœÏà¾¨«T­CÝ]ªø­Aú¡ñzÝw÷Ó Merant ODBC XøÒæ{Ý­§èýzæ{Ý­ýœ®~©­A®hÏœ¯íðnõ¢ús
odbcinst.ini­C
  ------------------------------------------------------------------------

5.3 ýŽ 24 üû ü]÷mµpÝXùtý×ùàÝsù£Ýhð®÷ˆ©’ùàú«

5.3.1 µpÝXùtý×

DB2 µpÝXùtý×ªOÏ@§ DBMS ¦§îS©¡Çç®ª­C µpÝXùtý×¾iìñzªd÷áùÇ¶^ù£ÝÝbù„¾L DBMS
ÏW¦§÷ˆ©’­AùãÝp Oracle­BSybase Ï× Microsoft SQL Server­C SQL üîðzÝ­¾i¾Hø¥úà
Ýhð® DBMS ¸×ü‘Ï@üîðzÝ­ÏÏ¦§ðàõO÷ˆ©’©w­C ùãÝp­Añz¾i¾HæýÝXÝÝb DB2 Universal
Database ¦¡©‘­BOracle ¦¡©‘Ï× Sybase úõýÏ¦¡ÏÏ¦§÷ˆ©’­C Ï„ï¸¦§ DBMS ¾]ªA
Oracle­BSybase­BMicrosoft SQL Server (for Windows NT) Ï× DB2 Universal
Database ùtÝC¦§Ýùð– (Ýp DB2 for OS/390­BDB2 for AS/4000 Ï× DB2 for
Windows)­C

DB2 µpÝXùtý×¾]õtùÆÝü DB2 ©žùã¦§Ý›¦Aóû (÷ˆ©’©wñN¾HµpÝX÷ˆ©’©wÝ›¦A) ¾HÏ×Ï@ðà¸×
Ýhðà÷ˆ©’ùàú«­C µpÝX÷ˆ©’©w¾]õtÇ¥õO÷ˆ©’ùàú«Ï×ù„¸Ò«Š¦§¾¨ìæn¨ì­C ÷ˆ©’ùàú«¾]õt
DBMS Ï×÷ˆ©’­CDB2 Universal Database Ýüüq®Hù¢¸w­A§ëªø¾~¬h­Añz¾i¾HùØ¾×ùàÝsù£
üoù€÷ˆ©’ùàú«­C ¾~¬hªOÏ@§óöùŒ­AµpÝXÝ›¦Aóû¾×ÝûóöùŒùàüq®HÏ×¶^ù£÷ˆ©’ùàú«¦§÷ˆ
©’­C ¬ÒÝWªO¾×ùàø¥úàÝÝb÷ˆ©’ùàú«ÏÏ¦§¦¡©‘¯PúõýÏ¦¡­C ·ü¾×æ{Ý­üsñæùµpÝX÷ˆ©’
©w­AïNûü¾“Ý¢ù„¾L DB2 ÷ˆ©’©w­C ñzùØ¾×¦§¾~¬hªO¾H DB2 Universal Database ¾¨Ýb
øäÝ‘¦§¾ð¾xªøùÞóé­C

ÝbµpÝXùtý×ü]¸wÏõ® ­A¾i¾HÝsù£÷ˆ©’ùàú«ÏÏ¦§÷ˆøT­AõYùØÝbÏ@ðàÏj®ª÷ˆ©’©wÏÏ­C ùØ¾×
¦ÞÏ×·ü¾×æ{Ý­ô€øeªd÷áÝšÏ@ðàµpÝX÷ˆ©’©w­A¾Ýñq÷ˆ©’ùàú«¶^ù£÷ˆ©’­C

DB2 µpÝXùtý×Ýbü­¾öððùŒÏUóèõ@­CÏ·ïýÝ­ðnùDððùŒÝb DB2 ¦¸¾¯ 7 ÏÏôiÝ‘øá¦õ@ú~­C
Ýû¾~­AñzÏœî…øäÝ‘¯P¬ÒÝWªêÏØ¦§Ï«¾×æ{Ý­õ@ú~ (ûü LOAD­BREORG­BREORGCHK­BIMPORT
­BRUNSTATS æ¾æ¾)­C ÝìªO­Añz¾i¾HùØ¾×üzüqóöî…­AùØ¾×¯P÷à÷ˆ©’ùàú«ªêÇ”¦§ SQL ¾×
¯y­AñN DDL Ï× DML üîðzÝ­¦«ñæïœ¾XÝš DBMS­C

5.3.1.1 ððùŒ

¦¸¾¯ 7.2 ¦§ús¾~¬h (Ýp Linux Ï× Solaris ÏW¦§ Oracle­B AIX Ï× Solaris ÏW¦§
Sybase Ï× NT Ï× AIX ÏW¦§ Microsoft SQL Server) Ïœ¾i¾×¸¢ FixPak 3­Fñz¾ýôúµÒ
ôR DB2 Relational Connect ¦¸¾¯ 7.2­C

5.3.2 Ýw÷Ó DB2 Relational Connect

¾¯÷`ïœù¥ÝbÝ›¦AóûÏWÝw÷Ó DB2 Relational Connect ¦§®¾O­AñzñN¾H÷àÝ›¦Aóûõ@ªøµp
ÝXùtý×Ý›¦Aóû­C

5.3.2.1 Ýb Windows NT Ý›¦AóûÏWÝw÷Ó DB2 Relational Connect

ÝbñzñN DB2 Relational Connect Ýw÷ÓÝbñz¦§ Windows NT µpÝXÝ›¦AóûÏõ®e­G

   * «Ñ«T¸wµpÝXÝ›¦AóûÏWÝüÝw÷Ó DB2 Universal Database Enterprise Edition ¸×
     DB2 Universal Database Enterprise -- Extended Edition­C ðYñz¾ï§ƒñN DB2
     ùtÝC÷ˆ©’©wù™ÏJñz¦§Ï·ïýÝ­ðnùDÏÏ­A®hú¡ñzÝw÷Ó DB2 Universal Database ©­A
     ñz¾ýôú¨‹ù£ Distributed Join for DB2 ÷ˆ©’ùàú«¨‹ôæ­C ðYðn‡ÇãÏwûˆÝ‘Ýû¨‹
     ôæ­A«Ñ·Óªd FEDERATED ø¥¬’ªOü]¸wªø YES­C ñz¾i¾Hæo¾X GET DATABASE
     MANAGER CONFIGURATION ®¾O·ÓªdÝûü]¸w­A¾Ýú|Æ¾š¸ãÝüø¥¬’Ï×ù„ý{Ý‘ü]¸wðÔ­C
   * «Ñ«T¸wñzÏwÝbµpÝXÝ›¦AóûÏWÝw÷Ó÷ˆ©’ùàú«¦§ñqŽíî÷ün‚ (Ýp Sybase Open
     Client)­C

  1. ¾HñzªøÏFøäÝ‘Ýw÷Ó¸ã®¾á¦§ùØ¾×¦ÞñbÏ ænÏJùtý×­C
  2. Ç”üª¾“Ý¢øäÝ‘ÏÏ¦§æ{Ý­­AÝw÷Óæ{Ý­Ï~î…ùÞúàðnùDùàõ¢ús·©ž­C
  3. ¸I¾sÝw÷Óæ{Ý­­Cñz¾i¾HÝêøÒÏŠÝ­¸×¾HÏHÏuÏŠÝ­ùà¸I¾sÝw÷Óæ{Ý­­C ðYÝw÷Óæ{Ý­æL
     ¦kÝêøÒñãøÒ­A¸×ñzúQðn¾HÏœÝP¦§¯yù¾øäÝ‘Ýw÷Ó­A«Ñ¾HÏHÏuÏŠÝ­¸I¾sÝw÷Óæ{Ý­­C
        o ðYðnÝêøÒ¸I¾sÝw÷Óæ{Ý­­A«ÑñN DB2 Relational Connect CD ï­ÏJ§Ø§Ñóö
          ÏÏ­CÝêøÒøäÝ‘îS¸Òú|ÝêøÒñãøÒÝw÷Óæ{Ý­­C ùM¸wùtý×¯yù¾­AùÇñãøÒ÷à¯yù¾¦§
          Ýw÷Óæ{Ý­­C
        o ÝêÝ‘¸I¾sÝw÷Óæ{Ý­­G

            a. ®”Ï@ÏUô}¸l­A¨‹ù£øäÝ‘¨‹ôæ­C
            b. Ýbô}ñãŽ‘ÝÏÏ­A¨‚ÏJÏUÝC®¾O­G

               x:\setup /i language

               ù„ÏÏ­G

               x:
                    ¾N¦¡ñz¦§ CD-ROM ¾£§Ñóö­C

               language
                    ¾N¦¡ñz¯yù¾¦§øˆ«X (Ýp EN ªOð^Ï†)­C
            c. ®”Ï@ÏU«T¸w­C

     õYú|ô}ñãÝw÷Óæo©g¾x­C
  4. ®”Ï@ÏUÝw÷Ó­Aô}¸lÝw÷Óæ{õ€­C
  5. ¨¡ï`Ýw÷Óæ{Ý­ÏÏ¦§ïœ¾š­C

     ú¡æ{Ý­õûÝù©­ADB2 Relational Connect ¯Pù„¾Ý DB2 ýœ®~ñNú|Ýw÷ÓÝbñz¦§Ýw÷Ó
     ¾¨ìÏÏ­C

5.3.2.2 Ýb AIX­BLinux Ï× Solaris õ@ú~·“ûãÝ›¦AóûÏWÝw÷Ó DB2 Relational
Connect

ÝbñzñN DB2 Relational Connect Ýw÷ÓÝbñz¦§ AIX­BLinux Ï× Solaris õ@ú~·“ûãµpÝX
Ý›¦AóûÏõ®e­G

   * «Ñ«T¸wµpÝXÝ›¦AóûÏWÝüÝw÷Ó DB2 Universal Database Enterprise Edition ¸×
     DB2 Universal Database -- Extended Edition­C ðYñz¾ï§ƒñN DB2 ùtÝC÷ˆ©’©w
     ù™ÏJñz¦§Ï·ïýÝ­ðnùDÏÏ­A®hú¡ñzÝw÷Ó DB2 Universal Database ©­Añz¾ýôú¨‹ù£
     Distributed Join for DB2 ÷ˆ©’ùàú«¨‹ôæ­C ðYðn‡ÇãÏwûˆÝ‘Ýû¨‹ôæ­A«Ñ·Óªd
     FEDERATED ø¥¬’ªOü]¸wªø YES­C ñz¾i¾Hæo¾X GET DATABASE MANAGER
     CONFIGURATION ®¾O·ÓªdÝûü]¸w­A¾Ýú|Æ¾š¸ãÝüø¥¬’Ï×ù„ý{Ý‘ü]¸wðÔ­C
   * «Ñ«T¸wñzÏwÝbµpÝXÝ›¦AóûÏWÝw÷Ó÷ˆ©’ùàú«¦§ñqŽíî÷ün‚ (Ýp Sybase Open
     Client)­C

ðYðnñN DB2 Relational Connect Ýw÷ÓÝbñz¦§ AIX­BLinux Ï× Solaris õ@ú~·“ûãÝ›¦A
óû­A «ÑùØ¾× db2setup Ï«¾×æ{Ý­­G

  1. ¾H©évððùØ¾×¦ÞænÏJ­C
  2. ï­ÏJùÇ÷Ó÷ñz¦§ DB2 ýœ®~ CD-ROM­CÝüÇ”÷Ó÷ CD-ROM ¦§÷ˆøT­A «Ñø¥ó\AIX õ™
     ütÏJ¦—­C
  3. ¨‚ÏJ cd /cdrom ®¾O (ù„ÏÏ cdrom ªOñz¦§ýœ®~ CD-ROM ¦§÷Ó÷¶I)­A¾Hšõ¢÷Ó
     ÷ CD-ROM ¦§¾¨ì­C
  4. ¨‚ÏJ ./db2setup ®¾O­CÝbïXÏ·Žµ® ­A õYú|ô}ñã­uDB2 Ýw÷ÓÏ«¾×æ{Ý­­væ›æ­­C
  5. ¨‹ù£Ýw÷Ó­CõYú|ô}ñã­uÝw÷Ó DB2 V7­væ›æ­­C
  6. óÏèÝšñzñqŽíî÷¦§ DB2 Relational Connect ýœ®~­AùãÝp­A Relational
     Connect for Sybase­AùÇ®”¦©‘µ„¾H¨‹ù£­Cú¡ñz¨‹ù£¨‹ôæ©­Aù„©€Ç„õYú|¾Xý{ªP
     ÷û­C
  7. ¨‹ù£«T¸w­C õYú|ô}ñã­u®¾á DB2 ¦AøÔ­væ›æ­­C
  8. ñz¾i¾H¨‹óš®¾á DB2 ©žùã­C¨‹ù£«T¸w­C õYú|ô}ñã­u§Kðnü›õiÝw÷Ó­væ›æ­­Cú|Ýê
     øÒÝw÷Óùƒðàôæ¾­G Oracle ¦§Ï·ïýÝ­æýÝXÏ× DB2 Relational Connect ¦§­uýœ®~
     ¬ÑøO­v­C­uýœ®~¬ÑøO­vªO¾ýðn¦§­A¾iìñzüsñæù Sybase ÷ˆ©’ùàú«­C
  9. ¨‹óšŽ~Ž•øäÝ‘­C õYú|¾Xý{Ï@æ›æ­­A®¾XüoªOñzøñÏŒ Relational Connect ¦§üÞ
     ® óöú|­C ¨‹óš«T¸w¾HŽ~Ž•øäÝ‘Ýw÷Ó­C¾iî…ðn¦ ïXÏ·Žµ¦§©ô­Ï~î…õûÝùÝw÷Ó­C
 10. ú¡üq¦ó¾Xý{©­A®¾XÝw÷ÓÏwôôõQõûÝù­A«Ñ¨‹ù£«T¸w­C­u§Kðnü›õi­v¾Xý{©­A®¾X
     ðçÏ@ðàÝw÷Ó¨‹ôæ¦§Ýù¾\¸×¾½ñ¥­F«ÑÝAÝ÷¨‹ù£«T¸w­C

     ú¡Ýw÷ÓõûÝù©­ADB2 Relational Connect ¯Pù„¾Ý DB2 ýœ®~ñNÝw÷ÓÝb¾¨ìÏÏ­CÝb
     AIX ÏW­AÝûªø /usr/lpp/db2_07_01 ¾¨ì­CÝb Solaris ÏW­A Ýûªø
     /opt/IBMdb2/V7.1 ¾¨ì­CÝb Linux ÏW­A Ýûªø /usr/IBMdb2/V7.1 ¾¨ì­C

  ------------------------------------------------------------------------

5.4 ýŽ 26 üû Ýsù£ Oracle ÷ˆ©’ùàú«

øœÏFÏ„ï¸ AIX Ï× Windows NT ÏW¦§¾~¬h­ADB2 Universal Database Ï]Ï„ï¸ Linux Ï×
Solaris õ@ú~·“ûãÏW¦§ Oracle ¾~¬h­C ÝûÏ„ï¸ðð¸¢ Oracle ¦¸¾¯ 8­C ðYðnÝsù£üoù€
¾ð¾x¦§¾~¬h­Añz¯íðnï­ÏJ V7.2 DB2 Relational Connect CD­AùÇ¨‹ù£ DB2
Relational Connect for Oracle ÷ˆ©’ùàú«­C

Ï@¾ûñzÝw÷ÓÏF DB2 Relational Connect­Añz¾i¾HñN Oracle ÷ˆ©’ùàú«ús¬WùµpÝXÝ›¦A
óûÏÏ­G

  1. Ýb DB2 µpÝXÝ›¦AóûÏWÝw÷ÓÏ×ª[§c Oracle ñqŽíî÷ün‚­C
  2. ðžõ‹ db2dj.ini ·©žùÇæo¾X db2set ®¾O­A¾Hü]¸w÷ˆ©’ùàú«·“ûãš¬’­C
  3. û‹¸¢ UNIX ¾ð¾xÏWøäÝ‘¦§ DB2 µpÝXÝ›¦Aóû­A«ÑøäÝ‘ djxlink Script­AñN
     Oracle SQL*Net ¸× Net8 ·©ž©wÇæý«s¨Šùñz¦§ DB2 µpÝXÝ›¦Aóû­C
  4. «T¸wÏwõ¢ús SQL*Net ¸× Net8 tnsnames.ora ·©ž­C
  5. ð®úsùØ¾× DB2 ©žùã­C
  6. ®¾á¾~¬h­C
  7. ¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’­C
  8. ®¾áÝ›¦Aóû­C
  9. ®¾áùØ¾×¦Þû‹ªM­C
 10. ®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW­C

ÝüÇ”üoù€ùB’J¦§®¾š­A¾]ªAü]¸w·“ûãš¬’­A¾iùœ¸¢­uýŽ 26 üû­v­C ü]÷mµpÝXùtý×ùàÝs
ù£ DB2 Ýw÷Ó¯Pª[§c÷¾R÷ˆ©’ÏÏ¦§ Oracle ÷ˆ©’ùàú«­C

5.4.1 Ï†¾¢¨—¯~

Ýb"ús¬W Oracle ÷ˆ©’ùàú«ÝšµpÝXùtý×"ªq÷ùÝüÏUÝC¨—¯~­G

   * æ{õ€ÏÏ¨•§|ÏFÏ@ðàùB’J­C¾¨«T¦§ùB’Jªø­G
       1. ø¥Ýã Oracle ïœù¥¦§Ï†¾¢­AÝb DB2 µpÝXÝ›¦AóûÏWÝw÷ÓÏ×ª[§c Oracle ñqŽí
          î÷ün‚­C
       2. ðžõ‹ db2dj.ini ·©žùÇæo¾X db2set ®¾O­A ¾Hü]¸w÷ˆ©’ùàú«·“ûãš¬’­C
          db2set ®¾Oú|¾×ñz¦§ü]¸wðÔõ¢ús DB2 ü]¸w·æn¨ì­C

          ÝüÇ”ü]¸w·“ûãš¬’¦§÷âýà®¾š¾iùœ¸¢­uýŽ 26 üû­v­Cü]÷m¶öÝXùtý×ùàÝsù£
          DB2 Ýw÷Ó¯Pª[§c÷¾R÷ˆ©’ÏÏ¦§ Oracle ÷ˆ©’ùàú«­C
       3. û‹¸¢ UNIX ¾ð¾xÏWøäÝ‘¦§ DB2 µpÝXÝ›¦Aóû­A«ÑøäÝ‘ djxlink Script­A ñN
          Oracle SQL*Net ¸× Net8 ·©ž©wÇæý«s¨Šùñz¦§ DB2 µpÝXÝ›¦Aóû­C ©éóé
          ñz¦§¾ð¾x­Adjxlink Script ¦§Ý÷mÝb­G

               /usr/lpp/db2_07_01/bin on AIX

               /opt/IBMdb2/V7.1/bin Solaris

               /usr/IBMdb2/V7.1/bin Linux

          ¾uÝüÝb DB2 µpÝXÝ›¦AóûÏWÝw÷Ó Oracle ¦§ñqŽíî÷ün‚Ïõ® ­AÏ~øäÝ‘Ýû
          Script­C
   * Ï†¾¢®¾Xðnü]¸w­G

     DB2_DJ_INI = sqllib/cfg/db2dj.ini

     üoªOÏœ¾¨«T¦§­A·ü÷àü]¸wÝpÏU­G

     DB2_DJ_INI = $INSTHOME/sqllib/cfg/db2dj.ini

  ------------------------------------------------------------------------

5.5 Ýsù£ Sybase ÷ˆ©’ùàú« (ús¬Wüû÷`)

ÝbñzñN Sybase ÷ˆ©’ùàú«ús¬WÝšµpÝXÝ›¦AóûÏõ®e­Añz¾ýôúñN Sybase Open Client ün
‚Ýw÷ÓùÇª[§cÝb DB2 µpÝXÝ›¦AóûÏW­C «Ñø¥ó\Ï†¾¢ÏÏ¦§Ýw÷Óæ{õ€­Aù„·H¦çÝb Sybase
÷ˆ©’©wün‚ÏÏ­A¾Hù£ñoÝpÝ¢Ýw÷Ó Open Client ün‚¦§îS¸w¸£ýà­C Ý]ªøªOÝw÷Ó¦§Ï@ü­
¾ö­A«Ñ«T¸w¾]ªAÏF®ª¨ì·xÝsæ{õ€Ï× Sybase Open Client ·©ž©w­C

ðYðnü]¸wµpÝXÝ›¦Aóû­A¾HÝsù£·xÝsÝb Sybase ÷ˆ©’ùàú«¦§÷ˆ©’­Añz¾ýôú­G

  1. Ýw÷Ó DB2 Relational Connect ¦¸¾¯ 7.2­C «Ñø¥ó\5.3.2, Ýw÷Ó DB2
     Relational Connect­C
  2. ús¬W Sybase ÷ˆ©’ùàú«Ýšñz¦§µpÝXÝ›¦AóûÏÏ­C
  3. ®¸w Sybase Ýr«Xðô­C

¾¯üûøQ«žùB’J 2 Ï× 3­C

¾¯üû¦§®¾š¾iÏè¾×Ýb Windows NT­BAIX Ï× Solaris õ@ú~·“ûã­CîS¸w¾ð¾x¦§ÏœÝPüBü’
æ—¸¢ù„æo¾Ö¦§ÝaÏŠ­C

5.5.1 ús¬W Sybase ÷ˆ©’ùàú«ÝšµpÝXÝ›¦Aóû

ðYðnús¬W Sybase ÷ˆ©’ùàú«ÝšµpÝXÝ›¦Aóû­Añz¾ýôú­G

  1. ü]¸w·“ûãš¬’ùÇõ¢úsü]¸w·æn¨ì­C
  2. ñN DB2 ÇæýÝš Sybase ñqŽíî÷ün‚ (ôÔ AIX ¯P Solaris)
  3. ð®úsùØ¾× DB2 ©žùã­C
  4. ®¾áùÇü]¸wÏôðñ·©ž­C
  5. ®¾á¾~¬h­C
  6. ¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’­C
  7. ®¾áÝ›¦Aóû­C
  8. ¨‹¾×¦§­Gü]¸w CONNECTSTRING Ý›¦Aóû¨‹ôæ­C
  9. ®¾áùØ¾×¦Þû‹ªM­C
 10. ®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW­C

¾¯÷`ñNû‹üoù€ùB’Jõ@÷âýà¦§÷¥Ž·­C

5.5.1.1 ùB’J 1­Gü]¸w·“ûãš¬’ùÇõ¢úsü]¸w·æn¨ì

ðžõ‹ db2dj.ini ·©žùÇæo¾X db2set ®¾O­A ¾Hü]¸w÷ˆ©’ùàú«·“ûãš¬’­Cdb2dj.ini
·©ž¾]õtÏFÝw÷ÓÝbµpÝXÝ›¦AóûÏW¦§ Sybase ñqŽíî÷ün‚Ïõª[§c÷ˆøT­Cdb2set ®¾Oú|¾×
ñz¦§ü]¸wðÔõ¢ús DB2 ü]¸w·æn¨ì­C

ÝbÏ·ü×¦§÷ˆ©’©wùtý×ÏÏ­Añz¾i¾HùØ¾×îS©¡©žùãÏÏ¦§¸ãÝü÷`¶IÏõü‘Ï@ db2dj.ini ·©ž­A
¸×ùØ¾×îS©¡©žùãÏÏ¦§Ï@¸×Ýhðà÷`¶IÏõøáÏ@¦§ db2dj.ini ·©ž­C ¾¬Ï·ü×¦§÷ˆ©’©wùtý×
ÏÏ­AùCÏ@©žùãôÔ¾iÝüÏ@ðà db2dj.ini ·©ž­C

ðYðnü]¸w·“ûãš¬’­G

  1. «s¨ŠÝÝb sqllib/cfg ¦§·©ž db2dj.ini­AùÇü]¸wÏUÝC·“ûãš¬’­G

      SYBASE="<sybase home directory>"


     ù„ÏÏ <sybase home directory> ªO Sybase ñqŽíî÷Ýw÷Ó¦§¾¨ì­C
  2. ¾H Sybase ·“ûãš¬’ùàõ¢ús DB2 ©žùã¦§ .profile ·©ž­C ñz¾i¾Hæo¾XÏUÝC®¾O
     ùàøäÝ‘ÝûøÒõ@­G

     export PATH="$SYBASE/bin:$PATH"
     export SYBASE="<sybase home directory>"

     ù„ÏÏ <sybase home directory> ªO Sybase ñqŽíî÷Ýw÷Ó¦§¾¨ì­C
  3. ðnøäÝ‘ DB2 ©žùã .profile­A«Ñ¨‚ÏJ­G

     . .profile

  4. æo¾X db2set ®¾O­A¾×ñz¦§šõ¢ùàõ¢ús DB2 ü]¸w·æn¨ì­C Ýû®¾O¦§¯y¦k
     db2set­AªO¾Hñz¦§÷ˆ©’©wùtý×æý§cªøùÞóé­C ðYñz¾¨ÝbÏUÝC¾“Ý¢÷ˆ©’©wùtý×æý§c
     ÏÏùØ¾× db2dj.ini ·©ž­AÏ~¯íðnÝûùB’J­G

     ðYñz¾¨Ýb¾¬Ï·ü×÷ˆ©’©wùtý×ÏÏùØ¾× db2dj.ini ·©ž­A ¸×ñzðn db2dj.ini ·©ž
     ôÔÏè¾×¸¢¾®e¦§÷`¶I­A«Ñæo¾X­G

     db2set DB2_DJ_INI = sqllib/cfg/db2dj.ini

     ðYñz¾¨ÝbÏ·ü×÷ˆ©’©wùtý×ÏÏùØ¾× db2dj.ini ·©ž­A ¸×ñzðn db2dj.ini ·©žÏÏ
     ¦§ðÔÏè¾×¸¢Ýû©žùã¦§¸ãÝü÷`¶I­A«Ñæo¾X­G

     db2set -g DB2_DJ_INI = sqllib/cfg/db2dj.ini

     ðYñz¾¨ÝbÏ·ü×÷ˆ©’©wùtý×ÏÏùØ¾× db2dj.ini ·©ž­A ¸×ñzðn db2dj.ini ·©žÏÏ
     ¦§ðÔÏè¾×¸¢îS¸w¦§÷`¶I­A«Ñæo¾X­G

     db2set -i INSTANCEX  3 DB2_DJ_INI = sqllib/cfg/node3.ini

     ù„ÏÏ­G

     INSTANCEX
          ¾N¦¡©žùãÝW§ë­C

     3
          ¾N¦¡ÝC¾šÝb db2nodes.cfg ·©ž¦§÷`¶I÷û«X­C

     node3.ini
          ¾N¦¡ db2dj.ini ·©ž¦§ðžõ‹Ï×õ¢ÝW¦¸¾¯­C

5.5.1.2 ùB’J 2­GñN DB2 ÇæýÝš Sybase ñqŽíî÷ün‚ (ôÔ AIX ¯P Solaris)

ðYðnñã¾×Ýsù£ Sybase ÷ˆ©’ùàú«­ADB2 µpÝXÝ›¦Aóû¾ýôúÇæý«s¨ŠÝšñqŽíî÷·©ž©w­CÇ
æý«s¨Šæ{õ€¾HµpÝXÝ›¦AóûñNüq®H¦§÷ˆ©’ùàú«ùà®¾áùCÏ@ðà÷ˆ©’ùàú«¦§¾~¬h­Cú¡ñzøäÝ‘
djxlink Script ©­A®¾á¾~¬h·©ž©w­C ðYðnæo¾X djxlink Script Çç®ª­G

djxlink

5.5.1.3 ùB’J 3­Gð®úsùØ¾× DB2 ©žùã

ðYðn«T¸w·“ûãš¬’ü]¸w¸¢æ{Ý­ÏÏ­A«Ñð®úsùØ¾× DB2 ©žùã­C ú¡ñzð®úsùØ¾×©žùã©­Aï_
ús DB2 ©žùã¾Hñæùñz¸ãõ@¦§šõ¢­C

æo¾XÏUÝC®¾O¾Hð®úsùØ¾× DB2 ©žùã­G

Ýb DB2 for Windows NT Ý›¦AóûÏW­G

     NET STOP instance_name
     NET START instance_name

Ýb DB2 for AIX Ï× Solaris Ý›¦AóûÏW­G

     db2stop
     db2start

5.5.1.4 ùB’J 4­G®¾áùÇü]¸wÏôðñ·©ž

ðYðn®¾áùÇü]¸wÏôðñ·©ž­Añz¾ýôú®¾á·©žùÇùØ·©ž¾iÝsù£­C

  1. ùØ¾× Sybase ïœù¥¦§Ï«¾×æ{Ý­ùà®¾áÏôðñ·©ž­Aù„¾]ªAúQÝsù£¦§¸ãÝü Sybase
     Open Server ¦§÷ˆ©’­C«Ñø¥ó\ Sybase ¦§Ýw÷ÓÏ†¾¢­A¾Hù£ñoÝüÇ”ùØ¾×ÝûÏ«¾×æ{Ý­
     ¦§÷âýà÷ˆøT­C

     Windows NT üqñ`ñNÝû·©ž¸RÝWªø sql.ini­C ñNñzðŠ®¾á¦§·©ž­Añq sql.ini
     ð®ús¸RÝWªø interfaces­A ªø¬s¾×¸¢¸ãÝü¾ð¾x¦§·©ž¸RÝW­C ðYñz¨‹óšÏœðnñN
     sql.ini ð®ús¸RÝWªø interfaces­A ñz¾ýôúùØ¾× IFILE ø¥¬’¸× CONNECTSTRING
     ¨‹ôæ­Aù„ÝbùB’J 8 ÏÏÝü¯­¸£­C

     Ýb AIX Ï× Solaris ùtý×ÏW­AÝû·©žªO¸RÝWªø <instance
     home>/sqllib/interfaces­C
  2. ìÏôðñ·©ž¾iÝsù£ DB2­C

     Ýb DB2 for Windows NT Ý›¦AóûÏW­G
          ñN·©ž¸¤÷mÝb DB2 ©žùã¦§ %DB2PATH% ¾¨ì­C

     Ýb DB2 for AIX Ï× Solaris Ý›¦AóûÏW­G
          ñN·©ž¸¤÷mÝb DB2 ©žùã¦§ $HOME/sqllib ¾¨ì­CùØ¾× ln ®¾O­AÇæýùñq
          DB2 ©žùã¦§ $HOME/sqllib ¾¨ìÏõ·©ž­CùãÝp­G

          ln -s -f /home/sybase/interfaces  /home/db2djinst1/sqllib

5.5.1.5 ùB’J 5­G®¾á¾~¬h

ùØ¾× CREATE WRAPPER üîðzÝ­ùà®¸w¾~¬h­Aù„ñN¾×ùàÝsù£ Sybase ÷ˆ©’ùàú«­C¾~¬hªO
Ï@§óöùŒ­AµpÝXÝ›¦Aóû¾×ÝûóöùŒùàüq®HÏ×¶^ù£÷ˆ©’ùàú«¦§÷ˆ©’­C DB2 ¾]ªAùƒðà
Sybase ¾~¬h­GCTLIB Ï× DBLIB­C ÏUÝC«dùãÆ¾š CREATE WRAPPER üîðzÝ­­G

CREATE WRAPPER CTLIB

ù„ÏÏ CTLIB ªO Sybase Open Client ün‚ùØ¾×¦§ûwü]¾~¬hÝW§ë­CCTLIB ¾~¬h¾iùØ¾×¸¢
Windows NT­BAIX Ï× Solaris Ý›¦Aóû­C

ñz¾i¾H¾×ñz¨‹óš¦§ÝW§ëùàù£¾Nûwü]¾~¬hÝW§ë­C ÝìªO­AðYñzüo¯•øæ­AñzÏ]¾ýôú¾]õt
CREATE WRAPPER üîðzÝ­¦§µpÝXÝ›¦AóûÏõ LIBRARY ø¥¬’Ï×¾~¬h·©ž©w¦§ÝW§ë­C «Ñø¥ó\
DB2 SQL Reference ÏÏ¦§ CREATE WRAPPER üîðzÝ­­A¾Hù£ñoÝüÇ”¾~¬hñ`Ý­©wÝW§ë¦§÷â
ýà÷ˆøT­C

5.5.1.6 ùB’J 6­G¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’

ðYðnÝbÝsù£ Sybase ÷ˆ©’ùàú«©¬Wôi©Žî…­A«Ñü]¸w DB2_DJ_COMM ·“ûãš¬’­CÝûš¬’ú|
õP¶_ªOõ_ðnÝbµpÝXÝ›¦Aóûø_¸lü]¸w©­A÷ÏJ¾~¬h­C ü]¸w DB2_DJ_COMM ·“ûãš¬’¾H¾]
ªA¾~¬h·©ž©w­A ¯PñzÝb®eÏ@ùB’J®¸w¦§¾~¬hªêý­FùãÝp­G

Ýb DB2 for Windows NT Ý›¦AóûÏW­G

     db2set DB2_DJ_COMM='ctlib.dll'

Ýb DB2 for AIX Ý›¦AóûÏW­G

     db2set DB2_DJ_COMM='libctlib.a'

Ýb DB2 for Solaris Ý›¦AóûÏW­G

     db2set DB2_DJ_COMM='libctlib.so'

«Ñ«T¸wæ¾÷û (=) ¦§ùƒÇ„üœùSÝü¦©‘­C

«Ñø¥ó\ DB2 SQL Reference­A¾Hù£ñoÝüÇ”¾~¬hñ`Ý­©wÝW§ë¦§÷âýà÷ˆøT­C «Ñø¥ó\
Administration Guide­A¾Hù£ñoÝüÇ” DB2_DJ_COMM ·“ûãš¬’¦§÷ˆøT­C

5.5.1.7 ùB’J 7­G®¾áÝ›¦Aóû

ùØ¾× CREATE SERVER üîðzÝ­ùà¸w÷qùCÏ@ðàúQðnñqù„ÏÏÝsù£÷ˆ©’ùàú«¦§ Sybase Ý›¦A
óû­A ùãÝp­G

CREATE SERVER SYBSERVER TYPE SYBASE VERSION 12.0 WRAPPER CTLIB
OPTIONS (NODE 'sybnode', DBNAME'sybdb')

ù„ÏÏ­G

SYBSERVER
     ¾N¦¡ñz®¸wæû Sybase Ý›¦Aóû¦§ÝW§ë­CÝûÝW§ë¾ýôúªOøáÏ@¦§­C

SYBASE
     ¾N¦¡ñzðnª[§cÝsù£¦§÷ˆ©’ùàú«Çç®ª­CSybase ªOøáÏ@ÝüÏ„ï¸¦§÷ˆ©’ùàú«­C

12.0
     ¾N¦¡ñzðnÝsù£¦§ Sybase ¦¸¾¯­CÏ„ï¸¦§¦¸¾¯Ýü 10.0­B11.0­B11.1­B11.5­B11.9
     Ï× 12.0­C

CTLIB
     ¾N¦¡ñzÝb CREATE WRAPPER üîðzÝ­ÏÏ®¸w¦§¾~¬hÝW§ë­C

'sybnode'
     ¾N¦¡ SYBSERVER ñ`ón¦§÷`¶IÝW§ë­CÝbÏôðñ·©žÏÏù£ño÷`¶IðÔ­C ÝûðÔÝüøØÏ·ÏjÏp
     ¬g­C

     µ”æM÷`¶IÝW§ëªO®¸wªø¨‹ôæ­AÝìÝûªø Sybase ÷ˆ©’ùàú«¸ã¯í¦§­C«Ñø¥ó\ DB2 SQL
     Reference­A¾Hù£ñoù„¾L¨‹ôæ¦§÷ˆøT­C

'sybdb'
     ¾N¦¡ñzúQðnÝsù£¦§ Sybase ÷ˆ©’©wÝW§ë­C

5.5.1.8 ¨‹¾×¦§­GùB’J 8­Gü]¸w CONNECTSTRING Ý›¦Aóû¨‹ôæ

®¸wûO©µ{ªðÔ­BÏôðñ·©ž¦§÷“©|¯PÝW§ëÏ×Ïôðñ·©ž¦§Ï·®ÒÏjÏp­C Sybase Open
Client ùØ¾×ûO©µ{ªðÔùàõÇ¶_øäÝ‘©ô­Ïà¦›¦§ªd÷á¯PÝ^·ü­Cñz¾i¾HùØ¾× CREATE
SERVER OPTION DDL üîðzÝ­¦§ CONNECTSTRING ¨‹ôæ­Aü]¸w DB2 ¦§µ{ªðÔ­CùØ¾×
CONNECTSTRING ùà®¸w­G

   * SQL ªd÷á¦§ûO©ïµô­­C
   * ænÏJÝ^·ü¦§ûO©ïµô­­C
   * ÝW§ëÏôðñ¦§÷“©|ÝW§ë­C
   * Ï·®ÒÏjÏp­C

   .-;-------------------------------.
   V                                 |
>>----+---------------------------+--+-------------------------><
      +-TIMEOUT-- = --ª¡----------+
      +-LOGIN_TIMEOUT-- = --ª¡----+
      +-IFILE-- = --"string"------+
      +-PACKET_SIZE-- = --ÝÏ÷ýå--+
      '-;-------------------------'


TIMEOUT
     ®¸w DB2 Universal Database æ¾®í¾“Ý¢ SQL üîðzÝ­¦§ Sybase Open Client
     ÏõÝ^·ü¦§ª¡¬’­Cseconds ðÔÝb DB2 Universal Database óÆ¬’«dü•ÏÏ­AªOÏ@ðà¾¨
     óÆ¬’­Cñz®¸w¦§ûO©ðÔªOùÞóéñzùØ¾×¦§¾~¬h­C Windows NT­BAIX Ï× Solaris Ý›
     ¦Aóûüœ¾i¾HõQ¾× DBLIB ¾~¬h­CDBLIB ¾~¬h¦§ûwü]ðÔªO 0­C Ýb Windows NT­BAIX
     Ï× Solaris Ý›¦AóûÏW­ADBLIB ¦§ûwü]ðÔú|ùØ DB2 Universal Database æLððïµ
     Ýaæ¾®íÝ^·ü­C

LOGIN_TIMEOUT
     ®¸w DB2 Universal Database æ¾®í Sybase Open Client ÏõÝ^·üænÏJðnùD¦§ª¡
     ¬’­Cûwü]ðÔ¯P TIMEOUT ªêÝP­C

IFILE
     ®¸w Sybase Open Client Ïôðñ·©ž¦§÷“©|ÝW§ë­C Ýb string ÏÏÇ¥õO¦§÷“©|¾ý
     ôú¾H¶—Ïè÷û (") õtªA­C Ýb Windows NT Ý›¦AóûÏW­Aûwü]ðÔªO %DB2PATH%­C Ýb
     AIX Ï× Solaris Ý›¦AóûÏW­Aûwü]ðÔªO sqllib/interfaces­AÝbñz¦§ DB2
     Universal Database ©žùã¦§ø_¸l¾¨ìÏÏ­C

PACKET_SIZE
     ®¸wÏôðñ·©ž¦§Ï·®ÒÏjÏp (ÝÏ÷ýå)­C ðY÷ˆ©’ùàú«ÏœÏ„ï¸®¸w¦§Ï·®ÒÏjÏp­Aüs«u
     ñNú|¾½ñ¥­C ú¡ùCÏ@ðàøO¨ìüœ®šÏj© (ùãÝp­AñNÝC¬’ï­ÏJÏj®ª¦¡©‘ÏÏ)­A¬W¾[Ï·®Ò
     ÏjÏp¾i¸£ÆÝa¬W¾[©Žî…­C ÝÏ÷ýåÏjÏpªOÏ@ðà¬’ðÔ­C«Ñø¥ó\ Sybase ø¥ÝãÏƒ¾U¾H
     ù£ño÷âýà÷ˆøT­C

«dùã­G

Ýb Windows NT Ý›¦AóûÏW­AùØ¾×ÏUÝC®¾O­AñNûO©ðÔü]¸wªø 60 ª¡­AùÇñNÏôðñ·©žü]
¸wÝš C:\etc\interfaces ÏÏ­G

CREATE SERVER OPTION connectstring FOR SERVER sybase1
SETTING 'TIMEOUT=60;LOGIN_TIMEOUT=5;IFILE="C:\etc\interfaces";'


Ýb AIX ¯P Solaris Ý›¦AóûÏW­AùØ¾×ÏUÝC®¾O­AñNûO©ðÔü]¸wªø 60 ª¡­AùÇñNÏôðñ·
©žü]¸wÝš /etc/interfaces ÏÏ­G

CREATE SERVER OPTION connectstring FOR SERVER sybase1
SETTING 'TIMEOUT=60;PACKET_SIZE=4096;IFILE="/etc/interfaces";'


5.5.1.9 ùB’J 9­G®¾áùØ¾×¦Þû‹ªM

ðYµpÝXÝ›¦AóûÏÏ¦§ùØ¾×¦Þ ID ¯PüqÝ‘«X­A¯P Sybase ÏÏ¦§ùØ¾×¦Þ ID ¯PüqÝ‘«XÏœÝP­A
«ÑùØ¾× CREATE USER MAPPING üîðzÝ­­AùØ¾¯§íùØ¾×¦Þ ID ¯P Sybase ÷ˆ©’ùàú«ÏÏ¸w÷q
¦§ùØ¾×¦Þ ID ¯PüqÝ‘«XªêÏªû‹ªM­FùãÝp­G

CREATE USER MAPPING FOR DB2USER SERVER SYBSERVER
OPTIONS ( REMOTE_AUTHID 'sybuser', REMOTE_PASSWORD 'dayl1te')

ù„ÏÏ­G

DB2USER
     ¾N¦¡ñz¾×ùàû‹ªMùØ¾×¦Þ ID (¸w÷q¸¢ Sybase ÷ˆ©’ùàú«ÏÏ) ¦§¾¯§íùØ¾×¦Þ ID­C

SYBSERVER
     ¾N¦¡ñzÝb CREATE SERVER üîðzÝ­ÏÏ¸w÷q¦§ Sybase ÷ˆ©’ùàú«ÝW§ë­C

'sybuser'
     ¾N¦¡ñzðnû‹ªM DB2USER ¦§ Sybase ÷ˆ©’ùàú«¦§ùØ¾×¦Þ ID­CÝûðÔÝüøØÏ·ÏjÏp¬g­C

'dayl1te'
     ¾N¦¡¯P 'sybuser' ªêÇ”¦§üqÝ‘«X­CÝûðÔÝüøØÏ·ÏjÏp¬g­C

«Ñø¥ó\ DB2 SQL Reference­A¾Hù£ñoù„¾L¨‹ôæ¦§÷âýà÷ˆøT­C

5.5.1.10 ùB’J 10­G®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW

®¸wÝbñz¦§ Sybase ÷ˆ©’ùàú«ÏÏ¦§ùCÏ@ðàúõýÏ¦¡¸×¦¡©‘¦§¬ÒÝW­C ú¡ñzªd÷á Sybase ÷ˆ
©’ùàú«©­AñNùØ¾×üoù€¬ÒÝW­C Sybase ¬ÒÝWÝüøØÏ·ÏjÏp¬g­CñN§ä¾Ï×¦¡©‘ÝW§ë¾H¶—Ïè
÷û (") õtªA­CÏUÝC«dùãÆ¾š CREATE NICKNAME üîðzÝ­­G

CREATE NICKNAME SYBSALES FOR SYBSERVER."salesdata"."europe"

ù„ÏÏ­G

SYBSALES
     ¾N¦¡ Sybase ¦¡©‘¸×úõýÏ¦¡¦§ñM¾×¬ÒÝW­C

SYBSERVER."salesdata"."europe"
     ¾N¦¡¨¡ï`ÏUÝC©‘Ý­¦§ÏTü­Ï·Ç¥õOÝr­G

     data_source_name."remote_schema_name"."remote_table_name"

øwû‹ñzúQðn®¾á¬ÒÝW¦§ùCÏ@ðà¦¡©‘¸×úõýÏ¦¡­Að®«’ÝûùB’J­C ú¡ñz®¾á¬ÒÝW©­ADB2 ñN
ùØ¾×üs«uùàªd÷á÷ˆ©’ùàú«®ª¨ì­C Ýûªd÷áú|ï£÷åüsñæù÷ˆ©’ùàú«¦§¦ª§A­C ðYüs«uæL¦k
ûBõ@­Añzú|ñæÝªùÏ@ðà¨—¯~øT©õ­C

«Ñø¥ó\ DB2 SQL Reference­A¾Hù£ñoÝüÇ” CREATE NICKNAME üîðzÝ­¦§÷âýà÷ˆøT­CÝüÇ”
Ï@î‰¬ÒÝWÏ×‡Çã÷ˆ©’Çç®ªû‹ªM¦§÷âýà÷ˆøT­A«Ñø¥ó\ DB2 Administration Guide­C

5.5.2 ®¸w Sybase Ýr«Xðô

ÝûùB’JôÔÝb DB2 µpÝXÝ›¦AóûÏ× Sybase Ý›¦AóûøäÝ‘ÏœÝP¦§Ýr«Xðô©Ï~¯íðn­CùØ¾×¯P
DB2 ªêÝP¦§Ýr«XôøÏõ÷ˆ©’ùàú«Ïœ¯íðn¶…ï®­C ÏUÝC¦¡©‘ïœù¥ Ï@î‰­uøˆ©a¯yù¾Ï„ï¸
(NLS)­vÝr«Xðô¦§ÝPæ¾ Sybase ¨‹ôæ­C ñz¦§ Sybase ÷ˆ©’ùàú«ª[§c¾ýôú¯Pù„¯yúNªê
ý­A¸×¦ÞñqŽíî÷æ{Ý­«X¾ýôúî…øöø¯ï£Ïœý¦§¯yúN­AùÇñNù„¬Ñ¾šªø¨—¯~­B¸×ùØ¾×ù„¾¯ùð
¦§¯yúNùàû‹ªM÷ˆ©’­C ðYñqð¸lÝr«Xðôù¾¬ÑÝr«Xðô­Aüœõ„Ïœù¶…ï®¦¡­A®h DB2 ú|æo
¾X¨—¯~øT©õ­C «Ñø¥ó\ñz¦§ Sybase Ï†¾¢¾Hù£ño÷âýà÷ˆøT­C

¦¡ 1. ­uSybase Ýr«Xðô­v¨‹ôæ
 Ýr«Xðô         ÝPæ¾ Sybase ¨‹ôæ
 850            cp850
 897            sjis
 819            iso_1
 912            iso_2
 1089           iso_6
 813            iso_7
 916            iso_8
 920            iso_9
  ------------------------------------------------------------------------

5.6 ùØ¾× ODBC Ýsù£ Microsoft SQL Server ÷ˆ©’ùàú« (ús¬Wüû÷`)

ÝbñzñN Microsoft SQL Server ÷ˆ©’ùàú«ús¬WÝš DB2 µpÝXÝ›¦AóûÏõ®e­A ñz¾ýôúñN
ODBC XøÒæ{Ý­Ýw÷ÓùÇª[§cÝbµpÝXÝ›¦AóûÏW­C «Ñø¥ó\Ï†¾¢ÏÏ¦§Ýw÷Óæ{õ€­Aù„·H¦çÝb
ODBC XøÒæ{Ý­­A¾Hù£ñoÝpÝ¢Ýw÷Ó ODBC XøÒæ{Ý­¦§îS¸w¸£ýà­C

ðYðnü]¸wµpÝXÝ›¦Aóû¾HÝsù£·xÝsÝb Microsoft SQL Server ÷ˆ©’ùàú«¦§÷ˆ©’­Añz¾ý
ôú­G

  1. ÝbµpÝXÝ›¦AóûÏWÝw÷ÓùÇª[§c ODBC XøÒæ{Ý­­C «Ñø¥ó\Ï†¾¢ÏÏ¦§Ýw÷Óæ{õ€­Aù„·H
     ¦çÝb ODBC XøÒæ{Ý­­A¾Hù£ñoÝpÝ¢Ýw÷Ó ODBC XøÒæ{Ý­¦§îS¸w¸£ýà­C

     Ýb DB2 for Windows NT Ý›¦AóûÏW­G
          ùØ¾× ODBC ÷Ó÷m§èýzæ{Ý­ª[§cùtý× DSN­C

     Ýb DB2 for AIX Ý›¦AóûÏW­G
          Ýw÷Ó MERANT ïœù¥¦§øäÝ‘§¦¸¾¯­A®¸w MERANT ·©ž©w¾¨ìªø LIBPATH ÏÏ
          ¦§ýŽÏ@ðàæn¨ì­AùÇü]¸w .odbc.ini ·©ž­CÝbø_¸l¾¨ì®¾á .odbc.ini ø_
          ¸l¾¨ì­C
  2. Ýw÷Ó DB2 Relational Connect ¦¸¾¯ 7.2­C «Ñø¥ó\5.3.2, Ýw÷Ó DB2
     Relational Connect­C
  3. ús¬W Microsoft SQL Server ÷ˆ©’ùàú«Ýšñz¦§µpÝXÝ›¦AóûÏÏ­C
  4. ®¸w Microsoft SQL Server Ýr«Xðô­C

¾¯üûøQ«žùB’J 3 Ï× 4­C

¾¯üû¦§®¾š¾iÏè¾×Ýb Windows NT Ï× AIX ¾ð¾x­C îS¸w¾ð¾x¦§ÏœÝPüBü’æ—¸¢ù„æo¾Ö¦§
ÝaÏŠ­C

5.6.1 ús¬W Microsoft SQL Server ÷ˆ©’ùàú«ÝšµpÝXÝ›¦Aóû

ÝbñzÝw÷Ó ODBC XøÒæ{Ý­Ï× DB2 Relational Connect Ïõ® ­AùØ¾×ÏUÝCùB’J­AñN
Microsoft SQL Server ÷ˆ©’ùàú«ús¬Wùñz¦§ÏÏ­G

  1. ü]¸w·“ûãš¬’ (ôÔ AIX)­C
  2. øäÝ‘ Shell Script (ôÔ AIX)­C
  3. ¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’­C
  4. ð®úsùØ¾× DB2 ©žùã (ôÔ AIX)­C
  5. ®¾á¾~¬h­C
  6. ®¾áÝ›¦Aóû­C
  7. ®¾áùØ¾×¦Þû‹ªM­C
  8. ®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW­C
  9. ¨‹¾×¦§­G·•ño ODBC øl¶š­C

ÏUÝCÝU÷`ñNû‹üoù€ùB’Jõ@÷âýà¦§÷¥Ž·­C

5.6.1.1 ùB’J 1­Gü]¸w·“ûãš¬’ (ôÔ AIX)

ðžõ‹ db2dj.ini ·©žùÇæo¾X db2set ®¾O­A ¾Hü]¸w÷ˆ©’ùàú«·“ûãš¬’­Cdb2dj.ini
·©ž¾]õt÷ˆøT¾¦§­A¾Hüsñæ Microsoft SQL Server ÷ˆ©’ùàú«­Cdb2set ®¾Oú|¾×ñz¦§
ü]¸wðÔõ¢ús DB2 ü]¸w·æn¨ì­C

ÝbÏ·ü×¦§÷ˆ©’©wùtý×ÏÏ­Añz¾i¾HùØ¾×îS©¡©žùãÏÏ¦§¸ãÝü÷`¶IÏõü‘Ï@ db2dj.ini ·©ž­A
¸×ùØ¾×îS©¡©žùãÏÏ¦§Ï@¸×Ýhðà÷`¶IÏõøáÏ@¦§ db2dj.ini ·©ž­C ¾¬Ï·ü×¦§÷ˆ©’©wùtý×
ÏÏ­AùCÏ@©žùãôÔ¾iÝüÏ@ðà db2dj.ini ·©ž­C

ðYðnü]¸w·“ûãš¬’­G

  1. «s¨ŠÝÝb sqllib/cf$HOME/sqllib/cfg/g ¦§·©ž db2dj.ini­AùÇü]¸wÏUÝC·“ûã
     š¬’­G

     ODBCINI=$HOME/.odbc.ini
     DJX_ODBC_LIBRARY_PATH=<path to the Merant driver>/lib
     LIBPATH=<path to the Merant driver>/lib
     DB2ENVLIST=LIBPATH


æo¾X db2set ®¾O­A¾×ñz¦§šõ¢ùàõ¢ús DB2 ü]¸w·æn¨ì­Cdb2set ¦§¯y¦k­AªO¾Hñz¦§
÷ˆ©’©wùtý×æý§cªøùÞóé­C

   * ðYñz¾¨Ýb¾¬Ï·ü×÷ˆ©’©wùtý×ÏÏùØ¾× db2dj.ini ·©ž­A ¸×ðYñzÝbÏ·ü×¦§÷ˆ©’©wùt
     ý×ÏÏùØ¾× db2dj.ini ·©ž­A¾Bñzðn db2dj.ini ·©žÏÏ¦§ðÔôÔÏè¾×¸¢¾®e¦§÷`
     ¶I­A«Ñæo¾XÏUÝC®¾O­G

db2set DB2_DJ_INI=<path to ini file>/db2dj.ini

   * ðYñz¾¨ÝbÏ·ü×÷ˆ©’©wùtý×ÏÏùØ¾× db2dj.ini ·©ž­A ¸×ñzðn db2dj.ini ·©žÏÏ
     ¦§ðÔÏè¾×¸¢Ýû©žùã¦§¸ãÝü÷`¶I­A«Ñæo¾XÏUÝC®¾O­G

     db2set -g DB2_DJ_INI=<path to ini file>/db2dj.ini

   * ðYñz¾¨ÝbÏ·ü×÷ˆ©’©wùtý×ÏÏùØ¾× db2dj.ini ·©ž­A ¸×ñzðn db2dj.ini ·©žÏÏ
     ¦§ðÔÏè¾×¸¢îS¸w¦§÷`¶I­A«Ñæo¾XÏUÝC®¾O­G

     db2set -i INSTANCEX  3 DB2_DJ_INI=$HOME/sqllib/cfg/node3.ini

     ù„ÏÏ­G

     INSTANCEX
          ¾N¦¡©žùãÝW§ë­C

     3
          ¾N¦¡ÝC¾šÝb db2nodes.cfg ·©ž¦§÷`¶I÷û«X­C

     node3.ini
          ¾N¦¡ db2dj.ini ·©ž¦§ðžõ‹Ï×õ¢ÝW¦¸¾¯­C

5.6.1.2 ùB’J 2­GøäÝ‘ Shell Script (ôÔ AIX)

djxlink.sh Shell Script ÇæýñqŽíî÷·©ž©wÝš¾~¬h·©ž©w­C ðYðnøäÝ‘ Shell
Script­G

djxlink

5.6.1.3 ùB’J 3­G¨‹¾×¦§­Gü]¸w DB2_DJ_COMM ·“ûãš¬’

ðYñzæoý{ù„¦ ôOûLÝh¦§©ô­ùàÝsù£ Microsoft SQL Server ÷ˆ©’ùàú«­A ñz¾i¾HÝbµpÝX
Ý›¦Aóûø_¸lü]¸w­AÝà®DÝbñzûµ÷åÝsù£÷ˆ©’ùàú«©­Aü]¸w DB2_DJ_COMM ·“ûãš¬’ùàÏU÷
¾~¬h­A ÝpÝû®K¾i¬Wôi©Žî…­C ü]¸w DB2_DJ_COMM ·“ûãš¬’¾H¾]ªA¾~¬h·©ž©w­A¯PñzÝb
ýŽ 5 ùB’J®¸w¦§¾~¬hªêý­CùãÝp­G

Ýb DB2 for Windows NT Ý›¦AóûÏW­G

     db2set DB2_DJ_COMM=djxmssql3.dll

Ýb DB2 for AIX Ý›¦AóûÏW­G

     db2set DB2_DJ_COMM=libmssql3.a

«Ñ«T¸wæ¾÷û (=) ¦§ùƒÇ„üœùSÝü¦©‘­C

«Ñø¥ó\ DB2 SQL Reference­A¾Hù£ñoÝüÇ”¾~¬hñ`Ý­©wÝW§ë¦§÷âýà÷ˆøT­C

5.6.1.4 ùB’J 4­Gð®úsùØ¾× DB2 ©žùã (ôÔ AIX)

ðYðn«T¸w·“ûãš¬’ü]¸w¸¢æ{Ý­ÏÏ­A«Ñð®úsùØ¾× DB2 ©žùã­C ú¡ñzð®úsùØ¾×©žùã©­Aï_
ús DB2 ©žùã¾Hñæùñz¸ãõ@¦§šõ¢­C æo¾XÏUÝC®¾O­Að®úsùØ¾× DB2 ©žùã­G

db2stop
db2start

5.6.1.5 ùB’J 5­G®¾á¾~¬h

DB2 Universal Database Ýüùƒ§üq®Hù¢¸w­A§ëªø¾~¬h­Añz¾i¾HùØ¾×ùàÝsù£ Microsoft
SQL Server ÷ˆ©’ùàú«­C¾~¬hªOÏ@§óöùŒ­AµpÝXÝ›¦Aóû¾×ÝûóöùŒùàüq®HÏ×¶^ù£÷ˆ©’ùàú«
¦§÷ˆ©’­C ñzùØ¾×¦§¾~¬hªO¾H DB2 Universal Database ¾¨ÝbøäÝ‘¦§¾ð¾xªøùÞóé­C ùØ
¾×¦¡ 2 õ@ªø®®n­A¾H¨‹ù£óAú¡¦§¾~¬h­C

¦¡ 2. ODBC XøÒæ{Ý­
 ODBC XøÒæ{Ý­                        ¾ð¾x            ¾~¬hÝW§ë
 ODBC 3.0 (¸×õ¢ús¦¸¾¯) XøÒæ{Ý­       Windows NT      DJXMSSQL3
 MERANT DataDirect Connect ODBC 3.6   AIX             MSSQLODBC3
 XøÒæ{Ý­

ùØ¾× CREATE WRAPPER üîðzÝ­ùà®¸w¾~¬h­Aù„ñN¾×ùàÝsù£ Microsoft SQL Server ÷ˆ
©’ùàú«­C ÏUÝC«dùãÆ¾š CREATE WRAPPER üîðzÝ­­G

CREATE WRAPPER DJXMSSQL3

ù„ÏÏ DJXMSSQL3 ªO DB2 for Windows NT Ý›¦Aóû (ùØ¾× ODBC 3.0 XøÒæ{Ý­) ÏWùØ¾×
¦§ûwü]¾~¬hÝW§ë­C ðYñzÝü DB2 for AIX Ý›¦Aóû­Añz¾i¾H®¸w MSSQLODBC3 ¾~¬hÝW
§ë­C

ñz¾i¾H¾×ñz¨‹óš¦§ÝW§ëùàù£¾Nûwü]¾~¬hÝW§ë­C ÝìªO­AðYñzüo¯•øæ­Añz¾ýôú¾]õt
CREATE WRAPPER üîðzÝ­¦§µpÝXÝ›¦Aóû¾ð¾xÏõ LIBRARY ø¥¬’Ï×¾~¬h·©ž©w¦§ÝW§ë­C ùã
Ýp­G

Ýb DB2 for Windows NT Ý›¦AóûÏW­G

     CREATE WRAPPER wrapper_name LIBRARY 'djxmssql3.dll'

     ù„ÏÏ wrapper_name ªOñzúQðnïœù¥æû¾~¬h¦§ÝW§ë­A Ýà 'djxmssql3.dll' ªOñ`Ý­
     ©wÝW§ë­C

Ýb DB2 for AIX Ý›¦AóûÏW­G

     CREATE WRAPPER wrapper_name LIBRARY 'libmssql3.a'

     ù„ÏÏ wrapper_name ªOñzúQðnïœù¥æû¾~¬h¦§ÝW§ë­A Ýà 'libdjxmssql.a' ªOñ`Ý­
     ©wÝW§ë­C

«Ñø¥ó\ DB2 SQL Reference ÏÏ¦§ CREATE WRAPPER üîðzÝ­­A¾Hù£ñoÝüÇ”¾~¬hñ`Ý­©wÝW
§ë¦§÷âýà÷ˆøT­C

5.6.1.6 ùB’J 6­G®¾áÝ›¦Aóû

ùØ¾× CREATE SERVER üîðzÝ­ùà¸w÷qñzúQðnüsñæ¦§ùCÏ@ðà Microsoft SQL Server ÷ˆ©’
ùàú«­CùãÝp­G

CREATE SERVER sqlserver TYPE MSSQLSERVER VERSION 7.0 WRAPPER djxmssql3
OPTIONS (NODE 'sqlnode', DBNAME 'database_name')

ù„ÏÏ­G

sqlserver
     ¾N¦¡ñz®¸wæû Microsoft SQL Server Ý›¦Aóû¦§ÝW§ë­C ÝûÝW§ë¾ýôúªOøáÏ@¦§­C

MSSQLSERVER
     ¾N¦¡ñzðnª[§cÝsù£¦§÷ˆ©’ùàú«Çç®ª­C

7.0
     ¾N¦¡ñzðnÝsù£¦§ Microsoft SQL Server ¦¸¾¯­CDB2 Universal Database Ï„ï¸
     Microsoft SQL Server ¦¸¾¯ 6.5 ¯P 7.0­C

DJXMSSQL3
     ¾N¦¡ñzÝb CREATE WRAPPER üîðzÝ­ÏÏ¸w÷q¦§¾~¬hÝW§ë­C

'sqlnode'
     ¾N¦¡ø¥úà Microsoft SQL Server ¦§ùtý× DSN ÝW§ë­CÝûðÔÝüøØÏ·ÏjÏp¬g­Cñzðn
     Ýsù£¦§ Microsoft SQL Server ¦¸¾¯­C DB2 Universal Database Ï„ï¸
     Microsoft SQL Server ¦¸¾¯ 6.5 ¯P 7.0­C

     µ”æM÷`¶IÝW§ë (ùtý× DSN ÝW§ë) ªO®¸wªø CREATE SERVER üîðzÝ­ÏÏ¦§¨‹ôæ­AÝì
     Ýûªø Microsoft SQL Server ÷ˆ©’ùàú«¸ã¯í¦§­C

     «Ñø¥ó\ DB2 SQL Reference­A¾Hù£ñoñz¾i¾HùØ¾× CREATE WRAPPER üîðzÝ­¦§ù„¾L
     ¨‹ôæ­C

'database_name'
     ¾N¦¡ñzðnüsñæ¦§÷ˆ©’©wÏõÝW§ë­C

     µ”æM÷ˆ©’©wÝW§ëªO®¸wªø CREATE SERVER üîðzÝ­ÏÏ¦§¨‹ôæ­AÝìÝûªø Microsoft
     SQL Server ÷ˆ©’ùàú«¸ã¯í¦§­C

5.6.1.7 ùB’J 7­G®¾áùØ¾×¦Þû‹ªM

ðYµpÝXÝ›¦AóûÏÏ¦§ùØ¾×¦Þ ID ¯PüqÝ‘«X­A¯P Microsoft SQL Server ÏÏ¦§ùØ¾×¦Þ ID
¯PüqÝ‘«XÏœÝP­A«ÑùØ¾× CREATE USER MAPPING üîðzÝ­­AùØ¾¯§íùØ¾×¦Þ ID ¯P
Microsoft SQL Server ÷ˆ©’ùàú«ÏÏ¸w÷q¦§ùØ¾×¦Þ ID ¯PüqÝ‘«XªêÏªû‹ªM­FùãÝp­G

CREATE USER MAPPING FOR db2user SERVER server_name
OPTIONS (REMOTE_AUTHID 'mssqluser', REMOTE_PASSWORD 'dayl1te')

ù„ÏÏ­G

db2user
     ¾N¦¡ñz¾×ùàû‹ªMùØ¾×¦Þ ID (¸w÷q¸¢ Microsoft SQL Server ÷ˆ©’ùàú«ÏÏ) ¦§¾¯
     §íùØ¾×¦Þ ID­C

server_name
     ¾N¦¡ñzÝb CREATE SERVER üîðzÝ­ÏÏ¸w÷q¦§Ý›¦AóûÝW§ë­C

'mssqluser'
     ¾N¦¡ Microsoft SQL Server ÷ˆ©’ùàú«¦§ùØ¾×¦Þ ID­Añzðn¾×Ýûùàû‹ªM
     db2user­C ÝûðÔÝüøØÏ·ÏjÏp¬g­C

'dayl1ite'
     ¾N¦¡¯P 'mssqluser' ªêÇ”¦§üqÝ‘«X­CÝûðÔÝüøØÏ·ÏjÏp¬g­C

«Ñø¥ó\ DB2 SQL Reference­A¾Hù£ñoñz¾i¾HùØ¾× CREATE USER MAPPING üîðzÝ­¦§ù„¾L
¨‹ôæ­C

5.6.1.8 ùB’J 8­G®¾á¦¡©‘¯PúõýÏ¦¡¦§¬ÒÝW

®¸wñzúQðnÝsù£¦§ Microsoft SQL Server ÷ˆ©’ùàú«ÏÏ­AùCÏ@ðàúõýÏ¦¡Ï×¦¡©‘Ïõ¬Ò
ÝW­C ú¡ñzªd÷á Microsoft SQL Server ÷ˆ©’ùàú«©­AñNùØ¾×üoù€¬ÒÝW­C ùØ¾× CREATE
NICKNAME üîðzÝ­ùà®¸w¬ÒÝW­C ¬ÒÝWÝüøØÏ·ÏjÏp¬g­CÏUÝC«dùãÆ¾š CREATE NICKNAME
üîðzÝ­­G

CREATE NICKNAME mssqlsales FOR server_name.salesdata.europe

ù„ÏÏ­G

mssqlsales
     ¾N¦¡ Microsoft SQL Server ¦¡©‘¸×úõýÏ¦¡¦§ñM¾×¬ÒÝW­C

server_name.salesdata.europe
     ¾N¦¡¨¡ï`ÏUÝC©‘Ý­¦§ÏTü­Ï·Ç¥õOÝr­G

     data_source_server_name.remote_schema_name.remote_table_name

     ®ŽüñzÝb¦§ remote_schema_name Ï× remote_table_name ü­¾öùØ¾×¶—Ïè÷û­C

ú¡ñz®¾á¬ÒÝW©­ADB2 ú|ûµ÷åÝsù£÷ˆ©’ùàú«®ª¨ì¦¡©‘ (Microsoft SQL Server ø¥úàüo
ù€¦¡©‘õ@ªøùtý×¦¡©‘)­Cüoú|ï£÷åüsñæù÷ˆ©’ùàú«¦§¦ª§A­CðYüs«u¾½ñ¥­Añzú|ñæÝªùÏ@
ðà¨—¯~øT©õ­C

øwû‹ñzúQðn®¾á¬ÒÝW¦§¸ãÝü÷ˆ©’©w¦¡©‘Ï×úõýÏ¦¡­Að®«’ÝûùB’J­C

ÝüÇ” CREATE NICKNAME üîðzÝ­¦§÷âýà÷ˆøT­A«Ñø¥ó\ DB2 SQL Reference­C ÝüÇ”Ï@î‰
¬ÒÝWÏ×‡Çã÷ˆ©’Çç®ªû‹ªM¦§÷âýà÷ˆøT­A «Ñø¥ó\ DB2 Administration Guide­C

5.6.1.9 ùB’J 9­G¨‹¾×¦§­G·•ño ODBC øl¶š

ðYñzÝsù£÷ˆ©’ùàú«©ûJùøíÇD­Añz¾i¾Hù£ño ODBC øl¶š÷ˆøT­A¾HÏ·¦RùÇ÷¥ùMüoù€øí
ÇD­C ðYðn«T¸w ODBC øl¶š¦§ûBõ@¾¨ñ`­A«ÑùØ¾×­uODBC ÷ˆ©’ùàú«§èýz¦Þ­vïœù¥¦§øl¶š
ÏuùÆ­CñãøÒøl¶šú|¬vTùtý×©Žî…­AÝ]Ýûú¡ñzÏw÷¥ùMøíÇD©­A·ü÷àÇ”üªøl¶š­C

5.6.2 «’ªd Microsoft SQL Server Ýr«Xðô

Microsoft SQL Server Ï„ï¸ü\Ýh DB2 UDB Ï„ï¸¦§Ï@î‰­uøˆ©a¯yù¾Ï„ï¸ (NLS)­vÝr«X
ðô¨‹ôæ­C ùØ¾×¯P DB2 ªêÝP¦§Ýr«XôøÏõ÷ˆ©’ùàú«Ïœ¯íðn¶…ï®­C ¦¡©‘ 3 ÝC¾š DB2
Universal Database Ï× Microsoft SQL Server õ­ÝüÏ„ï¸¦§Ýr«Xðô­C

¦¡ 3. DB2 UDB Ï× Microsoft SQL Server Ýr«Xðô¨‹ôæ
 Ýr«Xðô         Ï„ï¸¦§¯yù¾
 1252           ISO Ýrôø
 850            Ýh§¯yù¾
 437            ð^Ï†
 874            ©ä¯y
 932            Ï‚Ï†
 936            ¶ý‚ÏÏÏ†
 949            µ£¯y
 950            µc‚ÏÏÏ†
 1250           ¾Dðn¬éªw¯y
 1251           ïæ¸âÏã¯y
 1253           õ’Çó¯y
 1254           ÏgÝåù„¯y
 1255           õ’õBùàÏ†
 1256           ¦¸âõB¯y

ú¡ DB2 µpÝXÝ›¦Aóû¯P Microsoft SQL Server øäÝ‘ÏœÝP¦§­uøˆ©a¯yù¾Ï„ï¸ (NLS)­vÝr
«Xðô©­Añz¦§ Microsoft SQL Server ÷ˆ©’ùàú«ª[§c¾ýôú¯Pù„¯yúNªêý­A¸×¦ÞñqŽíî÷
æ{Ý­«X¾ýôúî…øöø¯ï£Ïœý¦§¯yúN­AùÇñNù„¬Ñ¾šªø¨—¯~­B¸×ùØ¾×ù„¾¯ùð¦§¯yúNùàû‹ªM÷ˆ
©’­CðYñqð¸lÝr«Xðôù¾¬ÑÝr«Xðô­Aüœõ„Ïœù¶…ï®¦¡­A®h DB2 ú|æo¾X¨—¯~øT©õ­C «Ñ
ø¥ó\ñz¦§ Microsoft SQL Server Ï†¾¢­A¾Hù£ño÷âýà÷ˆøT­C
  ------------------------------------------------------------------------

§èýz

ü­¾ö¾¨ì

   * Administration Guide: Planning (æLÏÏÏ†¦¸)
        o 6.1 Chapter 8. Physical Database Design
             + 6.1.1 Partitioning Keys
        o 6.2 Designing Nodegroups
        o 6.3 Chapter 9. Designing Distributed Databases
             + 6.3.1 Updating Multiple Databases
        o 6.4 Chapter 13. High Availability in the Windows NT Environment
             + 6.4.1 Need to Reboot the Machine Before Running DB2MSCS
               Utility
        o 6.5 Chapter 14. DB2 and High Availability on Sun Cluster 2.2
        o 6.6 Veritas Support on Solaris
        o 6.7 Appendix B. Naming Rules
             + 6.7.1 Notes on Greater Than 8-Character User IDs and Schema
               Names
             + 6.7.2 User IDs and Passwords
        o 6.8 Appendix D. Incompatibilities Between Releases
             + 6.8.1 Windows NT DLFS Incompatible with Norton's Utilities
             + 6.8.2 SET CONSTRAINTS Replaced by SET INTEGRITY
        o 6.9 Appendix E. National Language Support
             + 6.9.1 National Language Versions of DB2 Version 7
                  + 6.9.1.1 Control Center and Documentation Filesets
             + 6.9.2 Locale Setting for the DB2 Administration Server
             + 6.9.3 DB2 UDB Supports the Baltic Rim Code Page (MS-1257) on
               Windows Platforms
             + 6.9.4 Deriving Code Page Values
             + 6.9.5 Country Code and Code Page Support
             + 6.9.6 Character Sets

   * Administration Guide: Implementation(æLÏÏÏ†¦¸)
        o 7.1 Adding or Extending DMS Containers (New Process)
        o 7.2 Chapter 1. Administering DB2 using GUI Tools
        o 7.3 Chapter 3. Creating a Database
             + 7.3.1 Creating a Table Space
                  + 7.3.1.1 Using Raw I/O on Linux
             + 7.3.2 Creating a Sequence
             + 7.3.3 Comparing IDENTITY Columns and Sequences
             + 7.3.4 Creating an Index, Index Extension, or an Index
               Specification
        o 7.4 Chapter 4. Altering a Database
             + 7.4.1 Adding a Container to an SMS Table Space on a
               Partition
             + 7.4.2 Altering an Identity Column
             + 7.4.3 Altering a Sequence
             + 7.4.4 Dropping a Sequence
             + 7.4.5 Switching the State of a Table Space
             + 7.4.6 Modifying Containers in a DMS Table Space
        o 7.5 Chapter 5. Controlling Database Access
             + 7.5.1 Sequence Privileges
             + 7.5.2 Data Encryption
        o 7.6 Chapter 8. Recovering a Database
             + 7.6.1 How to Use Suspended I/O
             + 7.6.2 Incremental Backup and Recovery
                  + 7.6.2.1 Restoring from Incremental Backup Images
             + 7.6.3 Parallel Recovery
             + 7.6.4 Backing Up to Named Pipes
             + 7.6.5 Backup from Split Image
             + 7.6.6 On Demand Log Archive
             + 7.6.7 Log Mirroring
             + 7.6.8 Cross Platform Backup and Restore Support on Sun
               Solaris and HP
             + 7.6.9 DB2 Data Links Manager Considerations/Backup Utility
               Considerations
             + 7.6.10 DB2 Data Links Manager Considerations/Restore and
               Rollforward Utility Considerations
             + 7.6.11 Restoring Databases from an Offline Backup without
               Rolling Forward
             + 7.6.12 Restoring Databases and Table Spaces, and Rolling
               Forward to the End of the Logs
             + 7.6.13 DB2 Data Links Manager and Recovery Interactions
             + 7.6.14 Detection of Situations that Require Reconciliation
        o 7.7 Appendix C. User Exit for Database Recovery
        o 7.8 Appendix D. Issuing Commands to Multiple Database Partition
          Servers
        o 7.9 Appendix I. High Speed Inter-node Communications
             + 7.9.1 Enabling DB2 to Run Using VI

   * Administration Guide: Performance (æLÏÏÏ†¦¸)
        o 8.1 Chapter 3. Application Considerations
             + 8.1.1 Specifying the Isolation Level
             + 8.1.2 Adjusting the Optimization Class
             + 8.1.3 Dynamic Compound Statements
        o 8.2 Chapter 4. Environmental Considerations
             + 8.2.1 Using Larger Index Keys
        o 8.3 Chapter 5. System Catalog Statistics
             + 8.3.1 Collecting and Using Distribution Statistics
             + 8.3.2 Rules for Updating Catalog Statistics
             + 8.3.3 Sub-element Statistics
        o 8.4 Chapter 6. Understanding the SQL Compiler
             + 8.4.1 Replicated Summary Tables
             + 8.4.2 Data Access Concepts and Optimization
        o 8.5 Chapter 8. Operational Performance
             + 8.5.1 Managing the Database Buffer Pool
             + 8.5.2 Managing Multiple Database Buffer Pools
        o 8.6 Chapter 9. Using the Governor
        o 8.7 Chapter 13. Configuring DB2
             + 8.7.1 Sort Heap Size (sortheap)
             + 8.7.2 Sort Heap Threshold (sheapthres)
             + 8.7.3 Maximum Percent of Lock List Before Escalation
               (maxlocks)
             + 8.7.4 Configuring DB2/DB2 Data Links Manager/Data Links
               Access Token Expiry Interval (dl_expint)
             + 8.7.5 MIN_DEC_DIV_3 Database Configuration Parameter
             + 8.7.6 Application Control Heap Size (app_ctl_heap_sz)
             + 8.7.7 Database System Monitor Heap Size (mon_heap_sz)
             + 8.7.8 Maximum Number of Active Applications (maxappls)
             + 8.7.9 Recovery Range and Soft Checkpoint Interval (softmax)
             + 8.7.10 Track Modified Pages Enable (trackmod)
             + 8.7.11 Change the Database Log Path (newlogpath)
             + 8.7.12 Location of Log Files (logpath)
             + 8.7.13 Maximum Storage for Lock List (locklist)
        o 8.8 Appendix A. DB2 Registry and Environment Variables
             + 8.8.1 Table of New and Changed Registry Variables
        o 8.9 Appendix C. SQL Explain Tools

   * Administering Satellites Guide and Reference(æLÏÏÏ†¦¸)
        o 9.1 Setting up Version 7.2 DB2 Personal Edition and DB2 Workgroup
          Edition as Satellites
             + 9.1.1 Prerequisites
                  + 9.1.1.1 Installation Considerations
             + 9.1.2 Configuring the Version 7.2 System for Synchronization
             + 9.1.3 Installing FixPak 2 or Higher on a Version 6
               Enterprise Edition System
                  + 9.1.3.1 Upgrading Version 6 DB2 Enterprise Edition for
                    Use as the DB2 Control Server
             + 9.1.4 Upgrading a Version 6 DB2 Control Center and Satellite
               Administration Center

   * Command Reference(æLÏÏÏ†¦¸)
        o 10.1 db2batch - Benchmark Tool
        o 10.2 db2cap (new command)
             + db2cap - CLI/ODBC Static Package Binding Tool
        o 10.3 db2ckrst (new command)
             + db2ckrst - Check Incremental Restore Image Sequence
        o 10.4 db2gncol (new command)
             + db2gncol - Update Generated Column Values
        o 10.5 db2inidb - Initialize a Mirrored Database
        o 10.6 db2look - DB2 Statistics Extraction Tool
        o 10.7 db2updv7 - Update Database to Version 7 Current Fix Level
        o 10.8 New Command Line Processor Option (-x, Suppress printing of
          column headings)
        o 10.9 True Type Font Requirement for DB2 CLP
        o 10.10 ADD DATALINKS MANAGER
        o 10.11 ARCHIVE LOG (new command)
             + Archive Log
        o 10.12 BACKUP DATABASE
             + 10.12.1 Syntax Diagram
             + 10.12.2 DB2 Data Links Manager Considerations
        o 10.13 BIND
        o 10.14 CALL
        o 10.15 DROP DATALINKS MANAGER (new command)
             + DROP DATALINKS MANAGER
        o 10.16 EXPORT
        o 10.17 GET DATABASE CONFIGURATION
        o 10.18 GET ROUTINE (new command)
             + GET ROUTINE
        o 10.19 GET SNAPSHOT
        o 10.20 IMPORT
        o 10.21 LIST HISTORY
        o 10.22 LOAD
        o 10.23 PING (new command)
             + PING
        o 10.24 PUT ROUTINE (new command)
             + PUT ROUTINE
        o 10.25 RECONCILE
        o 10.26 REORGANIZE TABLE
        o 10.27 RESTORE DATABASE
             + 10.27.1 Syntax
             + 10.27.2 DB2 Data Links Manager Considerations
        o 10.28 ROLLFORWARD DATABASE
        o 10.29 Documentation Error in CLP Return Codes

   * Data Movement Utilities Guide and Reference(æLÏÏÏ†¦¸)
        o 11.1 Chapter 2. Import
             + 11.1.1 Using Import with Buffered Inserts
        o 11.2 Chapter 3. Load
             + 11.2.1 Pending States After a Load Operation
             + 11.2.2 Load Restrictions and Limitations
             + 11.2.3 totalfreespace File Type Modifier
        o 11.3 Chapter 4. AutoLoader
             + 11.3.1 rexecd Required to Run Autoloader When Authentication
               Set to YES

   * Replication ®®n¯Pø¥ÝãÏƒ¾U
        o 12.1 õê¬gÏ×®D IBM Ý›¦Aóû
        o 12.2 Ýb Windows 2000 ÏW¦§õê¬g
        o 12.3 ·xÝs SQL ·©ž©¦§Ïw¦ó¨—¯~
        o 12.4 DB2 §–@
        o 12.5 Web ÏW¦§ Data Difference Utility
        o 12.6 ýŽ 3 üû ÷ˆ©’õê¬gûˆøÔ«dùã
             + 12.6.1 õê¬gûˆøÔ
        o 12.7 ýŽ 5 üû õê¬güWû§
             + 12.7.1 ¦¡©‘Ï×¦«Ž‘ÝW§ë
             + 12.7.2 DATALINK õê¬g
             + 12.7.3 LOB ððùŒ
             + 12.7.4 üWû§õê¬g
        o 12.8 ýŽ 6 üû ü]¸wõê¬g·“ûã
             + 12.8.1 ·HüBõ¢ús (Update-anywhere) ¾ìùMñ›¾¢
             + 12.8.2 ü]¸wõê¬g·“ûã
        o 12.9 ýŽ 8 üû øíÇDõP¶_
        o 12.10 ýŽ 9 üû AS/400 ¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­
        o 12.11 ýŽ 10 üû OS/390 ¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­
             + 12.11.1 DB2 DataPropagator for OS/390 ¦§¾ìùMñ›¾¢
             + 12.11.2 OS/390 ÏW¦§ UNICODE ¸M ASCII «s«XÏŠ¦k
                  + 12.11.2.1 ¨‹óš«s«XÏŠ¦k
                  + 12.11.2.2 ü]¸w«s«XÏŠ¦k
        o 12.12 ýŽ 11 üû UNIX ¾ð¾x¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­
             + 12.12.1 Ýb UNIX ¸M Windows ÏWü]¸w­u¶^ù£æ{Ý­­v¸M­uÏè¾×æ{Ý­­v
               ¦§·“ûãš¬’
        o 12.13 ýŽ 14 üû ¦¡©‘æý§c
        o 12.14 ýŽ 15 üû ¶^ù£æ{Ý­¸MÏè¾×æ{Ý­øT©õ
        o 12.15 ¦ç¨ì A. ñq·ü¾×æ{Ý­Ï§ñãøÒ¶^ù£æ{Ý­¸MÏè¾×æ{Ý­

   * System Monitor Guide and Reference(æLÏÏÏ†¦¸)
        o 13.1 db2ConvMonStream

   * Troubleshooting Guide(æLÏÏÏ†¦¸)
        o 14.1 Starting DB2 on Windows 95, Windows 98, and Windows ME When
          the User Is Not Logged On
        o 14.2 Chapter 2. Troubleshooting the DB2 Universal Database Server

   * Ýb 64 ÝÏ÷¦§¾ð¾xÏWùØ¾× DB2 Universal Database
        o 15.1 ýŽ 5 üû ª[§c
             + 15.1.1 LOCKLIST
             + 15.1.2 shmsys:shminfo_shmmax
        o 15.2 ýŽ 6 üû ððùŒ

   * XML Extender Administration and Programming(æLÏÏÏ†¦¸)

   * MQSeries
        o 17.1 Ýw÷Ó¯Pª[§c DB2 MQSeries Function
             + 17.1.1 Ýw÷Ó MQSeries
             + 17.1.2 Ýw÷Ó MQSeries AMI
             + 17.1.3 ñã¾× DB2 MQSeries Function
        o 17.2 MQSeries ô€øT¬ÓÝ­
        o 17.3 øT©õæý§c
        o 17.4 MQSeries ¾\î…úõ’[
             + 17.4.1 ððùŒ
             + 17.4.2 ¨—¯~«X
        o 17.5 ¾×¦kûˆøÔÏƒ¾U
             + 17.5.1 ø•¾¯ô€øT
             + 17.5.2 ô€øeøT©õ
             + 17.5.3 ¶^ù£øT©õ
             + 17.5.4 ·ü¾×æ{Ý­û‹·ü¾×æ{Ý­üsñæ
                  + 17.5.4.1 Request/Reply üq®H
                  + 17.5.4.2 æoõG/ðqó\
        o 17.6 enable_MQFunctions
             + enable_MQFunctions
        o 17.7 disable_MQFunctions
             + disable_MQFunctions

  ------------------------------------------------------------------------

Administration Guide: Planning (æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

6.1 Chapter 8. Physical Database Design

6.1.1 Partitioning Keys

In the "Nodegroup Design Considerations" subsection of the "Designing
Nodegroups" section , the following text from the "Partitioning Keys"
sub-subsection stating the points to be considered when defining
partitioning keys should be deleted only if DB2_UPDATE_PART_KEY=ON:

Note:
     If DB2_UPDATE_PART_KEY=OFF, then the restrictions still apply.

Note:
     In FixPak 3 and later, the default value will be ON.

   * You cannot update the partitioning key column value for a row in the
     table.
   * You can only delete or insert partitioning key column values.

  ------------------------------------------------------------------------

6.2 Designing Nodegroups

Within the section titled "Designing Nodegroups," the subsection titled
"Nodegroup Design Considerations," and the subsection titled "Replicated
Summary Tables," disregard the last sentence of the second paragraph:

The REPLICATED keyword can only be specified for a summary table that is
defined with the REFRESH DEFERRED option.
  ------------------------------------------------------------------------

6.3 Chapter 9. Designing Distributed Databases

6.3.1 Updating Multiple Databases

In the section "Updating Multiple Databases", the list of setup steps has
an inaccuracy. Step 4, which now reads as follows:

   Precompile your application program to specify a type 2 connection
   (that is, specify CONNECT 2 on the PRECOMPILE PROGRAM command), and
   one-phase commit (that is, specify SYNCPOINT ONEPHASE on the
   PRECOMPILE PROGRAM command), as described in the Application
   Development Guide.

should be changed to:

   Precompile your application program to specify a type 2 connection
   (that is, specify CONNECT 2 on the PRECOMPILE PROGRAM command), and
   two-phase commit (that is, specify SYNCPOINT TWOPHASE on the
   PRECOMPILE PROGRAM command), as described in the Application
   Development Guide.

  ------------------------------------------------------------------------

6.4 Chapter 13. High Availability in the Windows NT Environment

6.4.1 Need to Reboot the Machine Before Running DB2MSCS Utility

The DB2MSCS utility is used to perform the required setup to enable DB2 for
failover support under the Microsoft Cluster Service environment. For the
DB2MSCS utility to run successfully, the Cluster Service must be able to
locate the resource DLL, db2wolf.dll, which resides under the
%ProgramFiles%\SQLLIB\bin directory.

The DB2 UDB Version 7 Installation Program sets the PATH system environment
variable to point to the %ProgramFiles%\SQLLIB\bin directory. However, it
is not required that you reboot the machine after installation if you are
running on the Windows 2000 operating system.

If you want to run the DB2MSCS utility, you must reboot the machine so that
the PATH environment variable is updated for the Cluster Service.
  ------------------------------------------------------------------------

6.5 Chapter 14. DB2 and High Availability on Sun Cluster 2.2

DB2 Connect is supported on Sun Cluster 2.2 if:

   * The protocol to the host is TCP/IP (not SNA)
   * Two-phase commit is not used. This restriction is relaxed if the user
     configures the SPM log to be on a shared disk (this can be done
     through the spm_log_path database manager configuration parameter),
     and the failover machine has an identical TCP/IP configuration (the
     same host name, IP address, and so on).

  ------------------------------------------------------------------------

6.6 Veritas Support on Solaris

DB2 now supports Veritas, which provides cluster support for DB2 High
Availability on Solaris.

Description
     Brings online, takes offline, and monitors a DB2 UDB instance.

Entry Points

     Online
          Use db2start to bring up instance.

     Offline
          Use db2stop to bring down instance.

     Monitor
          Determines if specified DB2 instance is up. Uses appropriate
          process monitoring and (optional) database monitoring.

     Clean
          Removes DB2 instance resources.

 Attribute          Type         Definition
 probeDatabase      string       Database to be monitored
 instanceOwner      string       Instance owner name
 instanceHome       string       Home directory of instance owner
 probeTable         string       Table in probeDatabase to monitor
 monitorLevel       integer      1 implies process monitoring, 2 implies
                                 db mon
 nodeNumber         integer      Nodenumber of instance to start (unset is
                                 EE)

Type Defninition

     type DB2UDB (
         static int CleanTimeout = 240
         static int MonitorTimeout = 30
         static int OfflineTimeout = 240
         static int OnlineRetryLimit = 2
         static int OnlineTimeout = 120
         static int OnlineWaitLimit = 1
         static int RestartLimit = 3
         static int ToleranceLimit = 1
         static str ArgList[] =
     { probeDatabase, instanceOwner, instanceHome, probeTable, monitorLevel,
     nodeNumber }
         NameRule = resource.db2udb
         str probeDatabase
         str instanceOwner
         str instanceHome
         str probeTable
         int monitorLevel
         int nodeNumber
     )

Sample Configuration

     DB2UDB db2_resource_n0 (
         probeDatabase = sample
         probeTable = vcstable
         instanceOwner = stevera
         instanceHome = "/export/home/stevera"
         monitorLevel = 2
         )


Installation
        o Create the directory /opt/VRTSvcs/bin/DB2UDB.
        o Copy the files online, offline, monitor, clean, DB2UDBAgent into
          /opt/VRTSvcs/bin/DB2UDB and ensure that they are marked
          executable.
        o Copy the file db2udb.type.cf into /etc/VRTSvcs/conf/config.
        o Stop the cluster (for example, hastop -all).
        o Add the line include db2udb.type.cf into the file main.cf after
          the line include types.cf
        o Verify the cluster configuration is valid with
          /opt/VRTSvcs/bin/hacf -verify /etc/VRTSvcs/conf/config

     You are now ready to create the DB2 resources necessary to control DB2
     instances.

  ------------------------------------------------------------------------

6.7 Appendix B. Naming Rules

6.7.1 Notes on Greater Than 8-Character User IDs and Schema Names

   * DB2 Version 7 products on Windows 32-bit platforms support user IDs
     that are up to 30 characters long. However, because of native support
     of Windows NT and Windows 2000, the practical limit for user ID is 20
     characters.
   * DB2 Version 7 supports non-Windows 32-bit clients connecting to
     Windows NT and Windows 2000 with user IDs longer than 8 characters
     when user ID and password are being specified explicitly. This
     excludes connections using Client or DCE authentication.
   * DCE authentication on all platforms continues to have the 8-character
     user ID limit.
   * The authid returned in the SQLCA from a successful CONNECT or ATTACH
     is truncated to 8 characters. The SQLWARN fields contain warnings when
     truncation occurs. For more information, refer to the description of
     the CONNECT statement in the SQL Reference.
   * The authid returned by the command line processor (CLP) from a
     successful CONNECT or ATTACH is truncated to 8 characters. An ellipsis
     (...) is appended to the authid to indicate truncation.
   * DB2 Version 7 supports schema names with length up to 30 bytes, with
     the following exceptions:
        o Tables with schema names longer than 18 bytes cannot be
          replicated.
        o User defined types (UDTs) cannot have schema names longer than 8
          bytes.

6.7.2 User IDs and Passwords

Within the section titled "User IDs and Passwords," change the reference to
"A through Z" to:

Single-byte uppercase and lowercase Latin letters (A...Z, a...z). Support
for other letters and characters depends on the code page being used. See
the appendix titled "National Language Support (NLS)" for more information
on code page support.
  ------------------------------------------------------------------------

6.8 Appendix D. Incompatibilities Between Releases

6.8.1 Windows NT DLFS Incompatible with Norton's Utilities

The Windows NT Data Links File System is incompatible with Norton
Utilities. When a file is deleted from a drive controlled by DLFS, a kernel
exception results: error 0x1E (Kernel Mode Exception Not Handled). The
exception being 0xC00000005 (Access Violation). This access violation
happens because the Norton Utilities driver gets loaded after the DLFS
filter driver gets loaded.

A temporary work-around is to load the DLFSD driver, after the Norton
Utilities driver is loaded. This work-around can be done by changing the
DLFSD driver startup to manual. Click on Start and select Settings-->
Control Panel-->Devices-->DLFSD and set it to manual.

A batch file, that can be added to the startup folder, can be created which
loads the DLFSD driver and the DLFM Service on system startup. The contents
of the batch file are as follows:

   net start dlfsd
   net start "dlfm service"

Name this batch file start_dlfs.bat, and copy it into the
C:\WINNT\Profiles\Administrator\Start Menu\Programs\Startup directory.

Only the administrator has the privilege to load the DLFS filter driver and
the DLFM service.

6.8.2 SET CONSTRAINTS Replaced by SET INTEGRITY

The SET CONSTRAINTS statement has been replaced by the SET INTEGRITY
statement. For backwards compatibility, both statements are accepted in DB2
UDB V7.
  ------------------------------------------------------------------------

6.9 Appendix E. National Language Support

6.9.1 National Language Versions of DB2 Version 7

DB2 Version 7 is available in English, French, German, Italian, Spanish,
Brazilian Portuguese, Japanese, Korean, Simplified Chinese, Traditional
Chinese, Danish, Finnish, Norwegian, Swedish, Czech, Dutch, Hungarian,
Polish, Turkish, Russian, Bulgarian, and Slovenian.

On UNIX-based platforms, the DB2 product messages and library can be
installed in several different languages. The DB2 installation utility lays
down the message catalog file sets into the most commonly used locale
directory for a given platform as shown in the following tables. ¦¡ 4
provides information for AIX, HP-UX, and Solaris. Table 5 provides information
for Linux, Linux/390, SGI, and Dynix.

Table 4. AIX, HP-UX, Solaris
 Operating SystemAIX            HP-UX                   Solaris
 Language        Locale    Cde  Locale             Cde  Locale        Cde
                           Pg                      Pg                 Pg
 French          fr_FR     819  fr_FR.iso88591     819  fr            819

                 Fr_FR     850  fr_FR.roman8       1051
 German          de_DE     819  de_DE.iso88591     819  de            819

                 De_DE     850  de_DE.roman8       1051
 Italian         it_IT     819  it_IT.iso88591     819  it            819

                 It_IT     850  it_IT.roman8       1051
 Spanish         es_ES     819  es_ES.iso88591     819  es            819

                 Es_ES     850  es_ES.roman8       1051
 Brazilian Portu-pt_BR     819                          pt_BR         819
 guese
 Japanese        ja_JP     954  ja_JP.eucJP        954  ja            954

                 Ja_JP     932
 Korean          ko_KR     970  ko_KR.eucKR        970  ko            970
 Simplified      zh_CN     1383 zh_CN.hp15CN       1383 zh            1383
 Chinese
                 Zh_       1386
                 CN.GBK
 Traditional     zh_TW     964  zh_TW.eucTW        964  zh_TW         964
 Chinese
                 Zh_TW     950  zh_TW.big5         950  zh_TW.BIG5    950
 Danish          da_DK     819  da_DK.iso88591     819  da            819

                 Da_DK     850  da_DK.roman8       1051
 Finnish         fi_FI     819  fi_FI.iso88591     819  fi            819

                 Fi_FI     850  fi_FI.roman8       1051
 Norwegian       no_NO     819  no_NO.iso88591     819  no            819

                 No_NO     850  no_NO.roman8       1051
 Sweden          sv_SE     819  sv_SE.iso88591     819  sv            819

                 Sv_SE     850  sv_SE.roman8       1051
 Czech           cs_CZ     912
 Hungarian       hu_HU     912
 Polish          pl_PL     912
 Dutch           nl_NL     819

                 Nl_NL     850
 Turkish         tr_TR     920
 Russian         ru_RU     915
 Bulgarian       bg_BG     915  bg_BG.iso88595     915
 Slovenian       sl_SI     912  sl_SI.iso88592     912  sl_SI         912

Table 5. Linux, Linux/390, SGI, Dynix
 Operating    Linux            Linux/390      SGI            Dynix
 System
 Language     Locale      Cde  Locale    Cde  Locale     Cde Locale    Cde
                          Pg             Pg              Pg            Pg
 French       fr          819  fr        819                 fr        819
 German       de          819  de        819                 de        819
 Italian                                                     es        819
 Spanish
 Brazilian
 Portuguese
 Japanese     ja_JP.ujis  954  ja_JP.ujis954                 ja_JP.EUC 954
 Korean       ko          970  ko        970  ko_KO.euc  970
 Simplified   zh          1386 zh        1386
 Chinese      zh_CN.GBK        zh_CN.GBK
 Traditional  zh_TW.Big5  950  zh_TW.Big5950
 Chinese
 Danish
 Finnish
 Norwegian
 Sweden
 Czech
 Hungarian
 Polish
 Dutch                                                       nl        819
 Turkish
 Russian
 Bulgarian
 Slovenian

If your system uses the same code pages but different locale names than
those provided above, you can still see the translated messages by creating
a link to the appropriate message directory.

For example, if your AIX machine default locale is ja_JP.IBM-eucJP and the
code page of ja_JP.IBM-eucJP is 954, you can create a link from
/usr/lpp/db2_07_01/msg/ja_JP.IBM-eucJP to /usr/lpp/db2_07_01/msg/ja_JP by
issuing the following command:

ln -s /usr/lpp/db2_07_01/msg/ja_JP /usr/lpp/db2_07_01/msg/ja_JP.IBM-eucJP

After the execution of this command, all DB2 messages come up in Japanese.

6.9.1.1 Control Center and Documentation Filesets

The Control Center, Control Center Help and documentation filesets are
placed in the following directories on the target workstation:

   * DB2 for AIX:
        o /usr/lpp/db2_07_01/cc/%L
        o /usr/lpp/db2_07_01/java/%L
        o /usr/lpp/db2_07_01/doc/%L
        o /usr/lpp/db2_07_01/qp/$L
        o /usr/lpp/db2_07_01/spb/%L
   * DB2 for HP-UX:
        o /opt/IBMdb2/V7.1/cc/%L
        o /opt/IBMdb2/V7.1/java/%L
        o /opt/IBMdb2/V7.1/doc/%L
   * DB2 for Linux:
        o /usr/IBMdb2/V7.1/cc/%L
        o /usr/IBMdb2/V7.1/java/%L
        o /usr/IBMdb2/V7.1/doc/%L
   * DB2 for Solaris:
        o /opt/IBMdb2/V7.1/cc/%L
        o /usr/IBMdb2/V7.1/java/%L
        o /opt/IBMdb2/V7.1/doc/%L

Control Center file sets are in Unicode code page. Documentation and
Control Center help file sets are in a browser-recognized code set. If your
system uses a different locale name than the one provided, you can still
run the translated version of the Control Center and see the translated
version of help by creating links to the appropriate language directories.

For example, if your AIX machine default locale is ja_JP.IBM-eucJP, you can
create links from /usr/lpp/db2_07_01/cc/ja_JP.IBM-eucJP to
/usr/lpp/db2_07_01/cc/ja_JP and from /usr/lpp/db2_07_01/doc/ja_JP.IBM-eucJP
to /usr/lpp/db2_07_01/doc/ja_JP by issuing the following commands:

   * ln -s /usr/lpp/db2_07_01/cc/ja_JP
     /usr/lpp/db2_07_01/cc/ja_JP.IBM-eucJP
   * ln -s /usr/lpp/db2_07_01/doc/ja_JP
     /usr/lpp/db2_07_01/doc/ja_JP.IBM-eucJP

After the execution of these commands, the Control Center and help text
come up in Japanese.

Note:
     The Web Control Center is not supported running natively on Linux/390
     or NUMA-Q. It can be used from a client workstation to manage
     databases on these platforms.

6.9.2 Locale Setting for the DB2 Administration Server

Please ensure that the locale of the DB2 Administration Server instance is
compatible to the locale of the DB2 instance. Otherwise, the DB2 instance
cannot communicate with the DB2 Administration Server.

If the LANG environment variable is not set in the user profile of the DB2
Administration Server, the DB2 Administration Server will be started with
the default system locale. If the default system locale is not defined, the
DB2 Administration Server will be started with code page 819. If the DB2
instance uses one of the DBCS locales, and the DB2 Administration Server is
started with code page 819, the instance will not be able to communicate
with the DB2 Administration Server. The locale of the DB2 Administration
Server and the locale of the DB2 instance must be compatible. For example,
on a Simplified Chinese Linux system, "LANG=zh_CN" should be set in the DB2
Administration Server's user profile.

6.9.3 DB2 UDB Supports the Baltic Rim Code Page (MS-1257) on Windows
Platforms

DB2 UDB supports the Baltic Rim code page, MS-1257, on Windows 32-bit
operating systems. This code page is used for Latvian, Lithuanian, and
Estonian.

6.9.4 Deriving Code Page Values

Within the section titled "Deriving Code Page Values," change the first
paragraph, from:

However, it is not necessary to set the DB2CODEPAGE registry variable,
because DB2 will determine the appropriate code page value from the
operating system.

to: Normally, you do not need to set the DB2CODEPAGE registry variable
because DB2 automatically derives the code page information from the
operating system.

6.9.5 Country Code and Code Page Support

Within the section titled "Country Code and Code Page Support," add the
following information to the table:

 Code                        Country
 Page   Group  Code-Set  Tr.  Code Locale           OS        Country Name
 ----   -----  --------  --   ---  -----           ----      ---------------
 943     D-1   IBM-943   JP   81   ja_JP.PCK        Sun       Japan

6.9.6 Character Sets

Within the section titled "Character Sets" and the subsection "Character
Set for Identifiers," replace the last two sentences in the first paragraph
with the following:

Use special characters #, @, and $ with care in an NLS environment because
they are not included in the NLS host (EBCDIC) invariant character set.
Characters from the extended character set can also be used, depending on
the code page that is being used. If you are using the database in a
multiple code page environment, you must ensure that all code pages support
any elements from the extended character set you plan to use.
  ------------------------------------------------------------------------

Administration Guide: Implementation(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

7.1 Adding or Extending DMS Containers (New Process)

DMS containers (both file containers and raw device containers) which are
added (during tablespace creation or after) or extended are now done so in
parallel through the prefetchers. To achieve an increase in parallelism of
these create / resize container operations, one can increase the number of
prefetchers running in the system. The only process which is not done in
parallel is the logging of these actions and, in the case of creating
containers, the tagging of the containers.

Note:
     Parallelism of the CREATE TABLESPACE / ALTER TABLESPACE (with respect
     to adding new containers to an existing tablespace) will no longer
     increase when the number of prefetchers equals the number of
     containers being added.

  ------------------------------------------------------------------------

7.2 Chapter 1. Administering DB2 using GUI Tools

Within the section titled "The Alert Center", remove the last two sentences
in the section.

Within the section titled "Performance Monitor", remove the second bullet
item from the "Define performance variables" list in the subsection
"Monitoring Performance at a Point in Time."

Also later in this same subsection, the last few paragraphs in the section
should be rewritten as follows:

For each, a variety of performance variables can be monitored. The
Performance Variable Reference Help, available from the Help menu of any
Snapshot Monitor window, provides a description of all the performance
variables. These variables are organized into categories. The following
categories exist:

   * Instance: Agents, Connections, Sort
   * Database: Lock and Deadlock, Buffer Pool and I/O, Connections, Sort,
     SQL Statement Activity
   * Table: Table
   * Table space: Buffer Pool and I/O
   * Database Connections: Buffer Pool and I/O, Lock and Deadlock, Sort,
     SQL Statement Activity

For detailed information on how to generate snapshots, see the online help.

In this same section, remove the last sentence in the subsection titled
"Action Required When an Object Appears in the Alert Center."
  ------------------------------------------------------------------------

7.3 Chapter 3. Creating a Database

7.3.1 Creating a Table Space

7.3.1.1 Using Raw I/O on Linux

Linux has a pool of raw device nodes that must be bound to a block device
before raw I/O can be performed on it. There is a raw device controller
that acts as the central repository of raw to block device binding
information. Binding is performed using a utility named raw, which is
normally supplied by the Linux distributor.

Before you set up raw I/O on Linux, you require the following:

   * one or more free IDE or SCSI disk partitions
   * Linux kernel 2.4.0 or later (However, some Linux distributions offer
     raw I/O on 2.2 kernels.)
   * a raw device controller named /dev/rawctl or /dev/raw. If not, create
     a symbolic link:

     # ln -s /dev/your_raw_dev_ctrl /dev/rawctl

   * the raw utility, which is usually provided with the Linux distribution
   * DB2 Version 7.1 FixPak 3 or later

Note:
     Of the distributions currently supporting raw I/O, the naming of raw
     device nodes is different:

     Distribution  Raw device nodes      Raw device controller
     ------------  --------------------  ---------------------
     RedHat 6.2    /dev/raw/raw1 to 255  /dev/rawctl
     SuSE 7.0      /dev/raw1 to 63       /dev/raw

     DB2 supports either of the above raw device controllers, and most
     other names for raw device nodes. Raw devices are not supported by DB2
     on Linux/390.

To configure raw I/O on Linux:

In this example, the raw partition to be used is /dev/sda5. It should not
contain any valuable data.

Step  Calculate the number of 4 096-byte pages in this partition, rounding
  1.  down if necessary. For example:
  
        # fdisk /dev/sda
        Command (m for help): p

        Disk /dev/sda: 255 heads, 63 sectors, 1106 cylinders
        Units = cylinders of 16065 * 512 bytes

           Device Boot   Start    End    Blocks   Id  System
        /dev/sda1            1    523   4200997   83  Linux
        /dev/sda2          524   1106   4682947+   5  Extended
        /dev/sda5          524   1106   4682947   83  Linux

        Command (m for help): q
        #


      The number of pages in /dev/sda5 is

      num_pages = floor( ((1106-524+1)*16065*512)/4096 )
      num_pages = 11170736

Step   Bind an unused raw device node to this partition. This needs to be
  2.   done every time the machine is rebooted, and requires root access.
       Use raw -a to see which raw device nodes are already in use:

      # raw /dev/raw/raw1 /dev/sda5
      /dev/raw/raw1: bound to major 8, minor 5

Step  Set global read permissions on the raw device controller and the
  3.  disk partition. Set global read and write permissions on the raw
      device:

      # chmod a+r /dev/rawctl
      # chmod a+r /dev/sdb1
      # chmod a+rw /dev/raw/raw1

Step  Create the table space in DB2, specifying the raw device, not the
  4.  disk partition. For example:
  
      CREATE TABLESPACE dms1
      MANAGED BY DATABASE
      USING (DEVICE '/dev/raw/raw1' 11170736)

Table spaces on raw devices are also supported for all other page sizes
supported by DB2.

7.3.2 Creating a Sequence

Following the section titled "Defining an Identity Column on a New Table,"
add the following section, "Creating a Sequence":

A sequence is a database object that allows the automatic generation of
values. Sequences are ideally suited to the task of generating unique key
values. Applications can use sequences to avoid possible concurrency and
performance problems resulting from the generation of a unique counter
outside the database.

Unlike an identity column attribute, a sequence is not tied to a particular
table column nor is it bound to a unique table column and only accessible
through that table column.

A sequence can be created, or altered, so that it generates values in one
of these ways:

   * Increment or decrement monotonically without bound
   * Increment or decrement monotonically to a user-defined limit and stop
   * Increment or decrement monotonically to a user-defined limit and cycle
     back to the beginning and start again

The following is an example of creating a sequence object:

   CREATE SEQUENCE order_seq
      START WITH 1
      INCREMENT BY 1
      NOMAXVALUE
      NOCYCLE
      CACHE 24

In this example, the sequence is called order_seq. It will start at 1 and
increase by 1 with no upper limit. There is no reason to cycle back to the
beginning and restart from 1 because there is no assigned upper limit. The
number associated with the CACHE parameter specifies the maximum number of
sequence values that the database manager preallocates and keeps in memory.

The sequence numbers generated have the following properties:

   * Values can be any exact numeric data type with a scale of zero. Such
     data types include: SMALLINT, BIGINT, INTEGER, and DECIMAL.
   * Consecutive values can differ by any specified integer increment. The
     default increment value is 1.
   * Counter value is recoverable. The counter value is reconstructed from
     logs when recovery is required.
   * Values can be cached to improve performance. Preallocating and storing
     values in the cache reduces synchronous I/O to the log when values are
     generated for the sequence. In the event of a system failure, all
     cached values that have not been committed are never used and
     considered lost. The value specified for CACHE is the maximum number
     of sequence values that could be lost.

If a database that contains one or more sequences is recovered to a prior
point in time, then this could cause the generation of duplicate values for
some sequences. To avoid possible duplicate values, a database with
sequences should not be recovered to a prior point in time.

Sequences are only supported in a single node database.

There are two expressions used with a sequence.

The PREVVAL expression returns the most recently generated value for the
specified sequence for a previous statement within the current session.

The NEXTVAL expression returns the next value for the specified sequence. A
new sequence number is generated when a NEXTVAL expression specifies the
name of the sequence. However, if there are multiple instances of a NEXTVAL
expression specifying the same sequence name within a query, the counter
for the sequence is incremented only once for each row of the result.

The same sequence number can be used as a unique key value in two separate
tables by referencing the sequence number with a NEXTVAL expression for the
first table, and a PREVVAL expression for any additional tables.

For example:

   INSERT INTO order (orderno, custno)
      VALUES (NEXTVAL FOR order_seq, 123456);
   INSERT INTO line_item (orderno, partno, quantity)
      VALUES (PREVVAL FOR order_seq, 987654, 1)

The NEXTVAL or PREVVAL expressions can be used in the following locations:

   * INSERT statement, VALUES clause
   * SELECT statement, SELECT list
   * SET assignment statement
   * UPDATE statement, SET clause
   * VALUES or VALUES INTO statement

7.3.3 Comparing IDENTITY Columns and Sequences

Following the new section titled "Creating a Sequence", add the following
section:

While there are similarities between IDENTITY columns and sequences, there
are also differences. The characteristics of each can be used when
designing your database and applications.

An identity column has the following characteristics:

   * An identity column can be defined as part of a table only when the
     table is created. Once a table is created, you cannot alter it to add
     an identity column. (However, existing identity column characteristics
     may be altered.)
   * An identity column automatically generates values for a single table.
   * When an identity column is defined as GENERATED ALWAYS, the values
     used are always generated by the database manager. Applications are
     not allowed to provide their own values during the modification of the
     contents of the table.

A sequence object has the following characteristics:

   * A sequence object is a database object that is not tied to any one
     table.
   * A sequence object generates sequential values that can be used in any
     SQL statement.
   * Since a sequence object can be used by any application, there are two
     expressions used to control the retrieval of the next value in the
     specified sequence and the value generated previous to the statement
     being executed. The PREVVAL expression returns the most recently
     generated value for the specified sequence for a previous statement
     within the current session. The NEXTVAL expression returns the next
     value for the specified sequence. The use of these expressions allows
     the same value to be used across several SQL statements within several
     tables.

While these are not all of the characteristics of these two items, these
characteristics will assist you in determining which to use depending on
your database design and the applications using the database.

7.3.4 Creating an Index, Index Extension, or an Index Specification

Within the section titled "Creating an Index, Index Extension, or an Index
Specification", add the following note in the paragraph beginning with the
sentence: "Any column that is part of an index key is limited to 255
bytes."

æ—:
     The DB2_INDEX_2BYTEVARLEN registry variable can be used to allow
     columns with a length greater than 255 bytes to be specified as part
     of an index key.

  ------------------------------------------------------------------------

7.4 Chapter 4. Altering a Database

Under the section "Altering a Table Space", the following new sections are
to be added:

7.4.1 Adding a Container to an SMS Table Space on a Partition

You can add a container to an SMS table space on a partition (or node) that
currently has no containers.

The contents of the table space are rebalanced across all containers.
Access to the table space is not restricted during the rebalancing. If you
need to add more than one container, you should add them all at the same
time.

To add a container to an SMS table space using the command line, enter the
following:

   ALTER TABLESPACE <name>
      ADD ('<path>')
      ON NODE (<partition_number>)

The partition specified by number, and every partition (or node) in the
range of partitions, must exist in the nodegroup on which the table space
is defined. A partition_number may only appear explicitly or within a range
in exactly one on-nodes-clause for the statement.

The following example shows how to add a new container to partition number
3 of the nodegroup used by table space "plans" on a UNIX based operating
system:

   ALTER TABLESPACE plans
      ADD ('/dev/rhdisk0')
      ON NODE (3)

Following the section titled "Changing Table Attributes," add the following
sections:

7.4.2 Altering an Identity Column

Modify the attributes of an existing identity column with the ALTER TABLE
statement. For more information on this statement, including its syntax,
refer to the SQL Reference.

There are several ways to modify an identity column so that it has some of
the characteristics of sequences.

There are some tasks that are unique to the ALTER TABLE and the identity
column:

   * RESTART resets the sequence associated with the identity column to the
     value specified implicitly or explicitly as the starting value when
     the identity column was originally created.
   * RESTART WITH <numeric-constant> resets the sequence associated with
     the identity column to the exact numeric constant value. The numeric
     constant could be any positive or negative value with no non-zero
     digits to the right of any decimal point that could be assigned to the
     identity column.

7.4.3 Altering a Sequence

Modify the attributes of an existing sequence with the ALTER SEQUENCE
statement. For more information on this statement, including its syntax,
refer to the SQL Reference.

The attributes of the sequence that can be modified include:

   * Changing the increment between future values
   * Establishing new minimum or maximum values
   * Changing the number of cached sequence numbers
   * Changing whether the sequence will cycle or not
   * Changing whether sequence numbers must be generated in order of
     request
   * Restarting the sequence

There are two tasks that are not found as part of the creation of the
sequence. They are:

   * RESTART. Resets the sequence to the value specified implicitly or
     explicitly as the starting value when the sequence was created.
   * RESTART WITH numeric-constant. Resets the sequence to the exact
     numeric constant value. The numeric constant can be any positive or
     negative value with no non-zero digits to the right of any decimal
     point.

After restarting a sequence or changing to CYCLE, it is possible to
generate duplicate sequence numbers. Only future sequence numbers are
affected by the ALTER SEQUENCE statement.

The data type of a sequence cannot be changed. Instead, you must drop the
current sequence and then create a new sequence specifying the new data
type.

All cached sequence values not used by DB2 are lost when a sequence is
altered.

7.4.4 Dropping a Sequence

To delete a sequence, use the DROP statement. For more information on this
statement, including its syntax, refer to the SQL Reference.

A specific sequence can be dropped by using:

   DROP SEQUENCE sequence_name

where the sequence_name is the name of the sequence to be dropped and
includes the implicit or explicit schema name to exactly identify an
existing sequence.

Sequences that are system-created for IDENTITY columns cannot be dropped
using the DROP SEQUENCE statement.

Once a sequence is dropped, all privileges on the sequence are also
dropped.

7.4.5 Switching the State of a Table Space

The SWITCH ONLINE clause of the ALTER TABLESPACE statement can be used to
move table spaces in an OFFLINE state to an ONLINE state if the containers
associated with that table space have become accessible. The table space is
moved to an ONLINE state while the rest of the database is still up and
being used.

An alternative to the use of this clause is to disconnect all applications
from the database and then to have the applications connect to the database
again. This moves the table space from an OFFLINE state to an ONLINE state.

To switch the table space to an ONLINE state using the command line, enter:

   ALTER TABLESPACE <name>
      SWITCH ONLINE

7.4.6 Modifying Containers in a DMS Table Space

DMS tables spaces are now created and resized in parallel, which offers a
performance benefit. The degree of parallelism is equal to the number of
prefetchers plus 1.
  ------------------------------------------------------------------------

7.5 Chapter 5. Controlling Database Access

Following the section titled "Index Privileges," add the following section:

7.5.1 Sequence Privileges

The creator of a sequence automatically receives the USAGE privilege. The
USAGE privilege is needed to use NEXTVAL and PREVVAL expressions for the
sequence. To allow other users to use the NEXTVAL and PREVVAL expressions,
sequence privileges must be granted to PUBLIC. This allows all users to use
the expressions with the specified sequence.

Following the section titled "Monitoring Access to Data Using the Audit
Facility," add the following section:

7.5.2 Data Encryption

One part of your security plan may involve encrypting your data. To do
this, you can use encryption and decryption built-in functions: ENCRYPT,
DECRYPT_BIN, DECRYPT_CHAR, and GETHINT. For more information on these
functions, including their syntax, refer to the SQL Reference section of
the Release Notes.

The ENCRYPT function encrypts data using a password-based encryption
method. These functions also allow you to encapsulate a password hint. The
password hint is embedded in the encrypted data. Once encrypted, the only
way to decrypt the data is by using the correct password. Developers that
choose to use these functions should plan for the management of forgotten
passwords and unusable data.

The result of the ENCRYPT functions is the same data type as the first
argument.

Only VARCHARs can be encrypted.

The declared length of the result is one of the following:

   * The length of the data argument plus 42 when the optional hint
     parameter is specified.
   * The length of the data argument plus 10 when the optional hint
     parameter is not specified.

The DECRYPT_BIN and DECRYPT_CHAR functions decrypt data using
password-based decryption.

The result of the DECRYPT_BIN and DECRYPT_CHAR functions is the same data
type as the first argument.

The declared length of the result is the length of the original data.

The GETHINT function returns an encapsulated password hint. A password hint
is a phrase that will help data owners remember passwords. For example, the
word "Ocean" can be used as a hint to remember the password "Pacific".

The password that is used to encrypt the data is determined in one of two
ways:

   * Password Argument. The password is a string that is explicitly passed
     when the ENCRYPT function is invoked. The data is encrypted and
     decrypted with the given password.
   * Special Register Password. The SET ENCRYPTION PASSWORD statement
     encrypts the password value and sends the encrypted password to the
     database manager to store in a special register. ENCRYPT, DECRYPT_BIN
     and DECRYPT_CHAR functions invoked without a password parameter use
     the value in the ENCRYPTION PASSWORD special register.

     The initial or default value for the special register is an empty
     string.

Valid lengths for passwords are between 6 and 127 inclusive. Valid lengths
for hints are between 0 and 32 inclusive.

When the ENCRYPTION PASSWORD special register is set from the client, the
password is encrypted at the client, sent to the database server, and then
decrypted. To ensure that the password is not left readable, it is also
re-encrypted at the database server. DECRYPT_BIN and DECRYPT_CHAR functions
must decrypt the special register before use. The value found in the
ENCRYPTION PASSWORD is also not left readable. Gateway security is not
supported.
  ------------------------------------------------------------------------

7.6 Chapter 8. Recovering a Database

7.6.1 How to Use Suspended I/O

In Chapter 8."Recovering a Database", the following new section on using
the suspended I/O function is to be added:

Note:
     The information below about the db2inidb utility supercedes the
     information in the Version 7.2 What's New book.

db2inidb is a new tool shipped with DB2 that can perform crash recovery and
put a database in rollforward pending state.

Suspended I/O supports continuous system availability by providing a full
implementation for online split mirror handling, that is, splitting a
mirror without shutting down the database. If a customer cannot afford
doing offline or online backups on a large database, backups or system
copies can be done from a mirror image by using suspended I/O and split
mirror.

Depending on how the storage devices are being mirrored, the uses of
db2inidb will vary. The following uses assume that the entire database is
mirrored consistently through the storage system.

In a multi-node environment, the db2inidb tool must be run on every
partition before the split image can be used from any of the partitions.
The db2inidb tool can be run on all partitions simultaneously.

  1. Making a Clone Database

     The objective here is to have a clone of the primary database to be
     used for read-only purposes. The following procedure describes how a
     clone database may be made:
       a. Suspend I/O on the primary system by entering the following
          command:

               db2 set write suspend for database

       b. Use the operating system level command to split the mirror from
          the primary database.
       c. Resume I/O on primary system by entering the following command:

               db2 set write resume for database

          After running the command, the database on the primary system
          should be back to a normal state.
       d. Attach to the mirrored database from another machine.
       e. Start the database instance by entering the following command:

               db2start

       f. Start the DB2 crash recovery by entering the following command:

          db2inidb database_name AS  SNAPSHOT

          Note:
               This command will rollback the changes made by transactions
               that are inflight at the time of the split.

     You can also use this process for an offline backup, but if restored
     on the primary system, this backup cannot be used to roll forward,
     because the log chain will not match.
  2. Using the Split Mirror as a Standby Database

     As the mirrored (standby) database is continually rolling forward
     through the logs, new logs that are being created by the primary
     database, are constantly fetched from the primary system. The
     following procedure describes how the split mirror can be used as a
     standby database:
       a. Suspend I/O writes on the primary database.
       b. Split the mirror from the primary system.
       c. Resume the I/O writes on the primary database so that the primary
          database goes back to normal processing.
       d. Attach the mirrored database to another instance.
       e. Place the mirror in roll-forward pending and roll forward the
          mirror. Run the db2inidb tool (db2inidb <db_alias> as standby) to
          remove the suspend write state and to place the mirrored database
          in a roll-forward pending state.
       f. Copy logs by setting up a user exit program to retrieve log files
          from the primary system to ensure that the latest logs will be
          available for this mirrored database.
       g. Roll forward the database to the end of the logs.
       h. Go back to step f and repeat this process until the primary
          database is down.

  3. Using the Split Mirror as a Backup Image

     The following procedure describes how to use the mirrored system as a
     backup image to restore over the primary system:
       a. Use operating system commands to copy the mirrored data and logs
          on top of the primary system.
       b. Start the database instance by entering the following command:

               db2start

       c. Run the following command to place the mirrored database in a
          roll-forward pending state and to remove the suspend write state.

          db2inidb database_alias AS MIRROR

       d. Roll forward the database to the end of the logs.

7.6.2 Incremental Backup and Recovery

In Chapter 8,"Recovering a Database," the following is a new section about
incremental backup and recovery:

As the size of databases, and particularly warehouses, continues to expand
into the terabyte and petabyte range, the time and hardware resources
required to back up and recover these databases are also growing
substantially. Full database and table space backups are not always the
best approach when dealing with large databases, because the storage
requirements for multiple copies of such databases are enormous. Consider
the following issues:

   * When a small percentage of the data in a warehouse changes, it should
     not be necessary to back up the entire database.
   * Appending table spaces to existing databases and then taking only
     table space backups is risky, because data outside of the backed up
     table spaces may change.

DB2 now supports incremental backup and recovery (but not of long field or
large object data). An incremental backup is a backup image that contains
only pages that have been updated since the previous backup was taken. In
addition to updated data and index pages, each incremental backup image
also contains all of the initial database meta-data (such as database
configuration, table space definitions, database history, and so on) that
is normally stored in full backup images.

Two types of incremental backup are supported:

   * Incremental. An incremental backup image is a copy of all database
     data that has changed since the most recent successful full backup
     operation. This is also known as a cumulative backup image, because a
     series of incremental backups taken over time will each have the
     contents of the previous incremental backup image. The predecessor of
     an incremental backup image is always the most recent successful full
     backup of the same object.
   * Delta. A delta, or incremental delta, backup image is a copy of all
     database data that has changed since the last successful backup (full,
     incremental, or delta) of the table space in question. This is also
     known as a differential, or non-cumulative, backup image. The
     predecessor of a delta backup image is the most recent successful
     backup containing a copy of each of the table spaces in the delta
     backup image.

The key difference between incremental and delta backup images is their
behavior when successive backups are taken of an object that is continually
changing over time. Each successive incremental image contains the entire
contents of the previous incremental image, plus any data that has changed,
or is new, since the previous backup was produced. Delta backup images
contain only the pages that have changed since the previous image was
produced.

Combinations of database and table space incremental backups are permitted,
in both online and offline modes of operation. Be careful when planning
your backup strategy, because combining database and table space
incremental backups implies that the predecessor of a database backup (or a
table space backup of multiple table spaces) is not necessarily a single
image, but could be a unique set of previous database and table space
backups taken at different times.

To rebuild the database or the table space to a consistent state, the
recovery process must begin with a consistent image of the entire object
(database or table space) to be restored, and must then apply each of the
appropriate incremental backup images in the order described below (see the
"Restore Method" section).

To enable the tracking of database updates, DB2 supports a new database
configuration parameter, TRACKMOD, which can have one of two accepted
values:

   * NO. Incremental backup is not permitted with this configuration.
     Database page updates are not tracked or recorded in any way.
   * YES. Incremental backup is permitted with this configuration. When
     update tracking is enabled, the change becomes effective at the first
     successful connection to any database in the instance. A full database
     backup is necessary before an incremental backup can be taken.

The default TRACKMOD setting for existing databases is NO; for new
databases, it is YES.

The granularity of the tracking is at the table space level for both SMS
and DMS table spaces.

Although minimal, the tracking of updates to the database can have an
impact on the run-time performance of transactions that update or insert
data.

7.6.2.1 Restoring from Incremental Backup Images

A restore operation from incremental backup images always consists of the
following steps:

  1. Identifying the incremental target image.The DBA must first determine
     the final image to be restored, and request an incremental restore
     operation from the DB2 restore utility. This image is known as the
     target image of the incremental restore, because it will be the last
     image to be restored. An incremental restore command against this
     image may initiate the creation of a new database with the
     configuration and table space definitions from this target image. The
     incremental target image is specified using the TAKEN AT parameter in
     the RESTORE DATABASE command.
  2. Restoring the most recent full database or table space image to
     establish a baseline against which each of the subsequent incremental
     backup images can be applied.
  3. Restoring each of the required full or table space incremental backup
     images, in the order in which they were produced, on top of the
     baseline image restored in Step 2.
  4. Repeating Step 3 until the target image from Step 1 is read a second
     time. The target image is accessed twice during a complete incremental
     restore operation. During the first access, only initial data is read
     from the image; none of the user data is read. The complete image is
     read and processed only during the second access.

     The target image of the incremental restore operation must be accessed
     twice to ensure that the database is initially configured with the
     correct history, database configuration, and table space definitions
     for the database that will be created during the restore operation. In
     cases where a table space has been dropped since the initial full
     database backup image was taken, the table space data for that image
     will be read from the backup images but ignored during incremental
     restore processing.

For example:

   1. db2 restore database sample incremental taken at <ts>

      where:
        <ts> points to the last incremental backup image to be restored

   2. db2 restore database sample incremental taken at <ts1>

      where:
        <ts1> points to the initial full database (or table space) image

   3. db2 restore database sample incremental taken at <tsX>

      where:
        <tsX> points to each incremental backup image in creation sequence

   4. Repeat Step 3, restoring each incremental backup image up to and including image <ts>

In cases where a database restore operation is being attempted, and table
space incremental backup images have been produced, the table space images
must be restored in the chronological order of their backup time stamps.

7.6.3 Parallel Recovery

DB2 now uses multiple agents to perform both crash recovery and database
rollforward recovery. You can expect better performance during these
operations, particularly on symmetric multi-processor (SMP) machines; using
multiple agents during database recovery takes advantage of the extra CPUs
that are available on SMP machines.

The new agent type introduced by this enhancement is db2agnsc. DB2 chooses
the number of agents to be used for database recovery based on the number
of CPUs on the machine. For SMP machines, the number of agents used is
(number of CPUs + 1). On a machine with a single CPU, three agents are used
for more efficient reading of logs, processing of log records, and
prefetching of data pages.

DB2 distributes log records to these agents so that they can be reapplied
concurrently, where appropriate. The processing of log records is
parallelized at the page level (log records on the same data page are
processed by the same agent); therefore, performace is enhanced, even if
all the work was done on one table.

7.6.4 Backing Up to Named Pipes

Support is now available for database backup to (and database restore from)
local named pipes on UNIX based systems. Both the writer and the reader of
the named pipe must be on the same machine. The pipe must exist and be
located on a local file system. Because the named pipe is treated as a
local device, there is no need to specify that the target is a named pipe.
Following is an AIX example:

  1. Create a named pipe:
      mkfifo /u/dbuser/mypipe

  2. Use this pipe as the target for a database backup operation:
      db2 backup db sample to /u/dbuser/mypipe

  3. Restore the database:
      db2 restore db sample into mynewdb from /u/dbuser/mypipe

7.6.5 Backup from Split Image

DB2 now supports a full offline database backup on the split mirrored copy
of a database. Online backup is not supported and is not necessary because
the database, which is in rollforward pending state, is unavailable. When a
split mirrored backup image is restored, it must be rolled forward because
there may have been active transactions when the split occurred.

Note:
     For DB2 Version 7.1 FixPak 3 and DB2 Version 7.2 this support will be
     limited to databases that contain DMS table spaces only. If an attempt
     is made to back up a database after a split and the database contains
     any SMS table spaces, the backup will fail.

Once a database has been split, the db2inidb utility must be used to
specify one of the following options:

   * Snapshot. This initiates crash recovery, making the database
     consistent. A new log chain starts, and the database will not be able
     to roll forward through any of the logs from the original database.
     The database is available for any operation, including backup.
   * Standby. This places the database in rollforward pending state. Crash
     recovery is not performed, and the database remains inconsistent.
   * Mirror. This causes a mirrored copy of the database to replace the
     original database. The database is placed in rollforward pending
     state, and the WRITE SUSPEND state is turned off. Crash recovery is
     not performed, and the database remains inconsistent.

Following are some usage scenarios:

   * Making a database clone.

     The objective here is to have a read-only clone of the primary
     database that can be used, for example, to create reports. To do this,
     follow these steps:
       1. Suspend I/O on the primary system:

             db2 set write suspend for database

       2. Split the mirror. Use operating system level commands to split
          the mirror from the primary database.
       3. Resume I/O on the primary system:

             db2 set write resume for database

          The database on the primary system should now be back to a normal
          state.
       4. Mount the split mirrors of the database to another host.
       5. Start the instance:

             db2start

       6. Start DB2 crash recovery:

             db2inidb <db_name> as snapshot

          You can also use this process for an offline backup, but if
          restored on the primary system, this backup cannot be used to
          roll forward, because the log chain will not match.
   * Using the split mirror as a standby database.

     The idea here is that the mirrored (standby) database is continually
     rolling forward through the logs, and even new logs that are being
     created by the primary database are continually fetched from the
     primary system. To use the split mirror as a standby database, follow
     these steps:
       1. Suspend I/O on the primary system:

             db2 set write suspend for database

       2. Split the mirror. Use operating system level commands to split
          the mirror from the primary database.
       3. Resume I/O on the primary system:

             db2 set write resume for database

          The database on the primary system should now be back to a normal
          state.
       4. Mount the split mirrors of the database to another host.
       5. Remove the suspend write state and put the mirrored database in
          rollforward pending state.

           db2inidb <db_name> as standby

       6. Copy logs. Set up a user exit program to retrieve log files from
          the primary system's archive location, so that the latest logs
          will be available for this mirrored database.
       7. Rollforward the mirror to the end of the logs.

             db2 rollforward db <db_name> to end of logs

       8. Repeat the process from step 6 until the primary database is
          down.
   * Using the split mirror to recover the primary system.

     The following procedure describes how to use the mirrored system as a
     backup image to restore the primary system:
       1. Copy over. Use operating system commands to copy the mirrored
          data and logs on top of the primary system.
       2. Start the instance:

             db2start

       3. Put the restored mirror in rollforward pending state and roll the
          mirror forward to the end of the logs:

             db2inidb <dbname> as mirror

   * Taking a backup without performing crash recovery.

     Performing an offline backup on the split mirror without performing
     crash recovery means that you can restore this backup image on top of
     the primary system. To do this, follow these steps:
       1. Suspend I/O on the primary system:

             db2 set write suspend for database

       2. Split the mirror. Use operating system level commands to split
          the mirror from the primary database.
       3. Resume I/O on the primary system:

             db2 set write resume for database

          The database on the primary system should now be back to a normal
          state.
       4. Mount the split mirrors of the database to another host.
       5. Start the instance:

             db2start

       6. Put the mirrored database in rollforward pending state:

             db2inidb <db_name> as standby

       7. Invoke a database backup operation:

             db2 backup database <db_name>

          This results in an implicit database connection, but does not
          initiate DB2 crash recovery.

7.6.6 On Demand Log Archive

DB2 now supports the closing (and, if the user exit option is enabled, the
archiving) of the active log for a recoverable database at any time. This
allows you to collect a complete set of log files up to a known point, and
then to use these log files to update a standby database.

Note:
     On demand log archiving does not guarantee the log files will be
     archived immediately; it truncates the log file and issues an archive
     request, but it is still subject to delays associated with the user
     exit program

You can initiate on demand log archiving by invoking the new DB2 ARCHIVE
LOG command, or by calling the new db2ArchiveLog API.

7.6.7 Log Mirroring

In Chapter 8,"Recovering a Database," the following new section on using
the suspended I/O function is to be added:

DB2 now supports log mirroring at the database level. Mirroring log files
helps protect a database from:

   * Accidental deletion of an active log
   * Data corruption caused by hardware failure

If you are concerned that your active logs may be damaged (as a result of a
disk crash), you should consider using a new DB2 registry variable,
DB2_NEWLOGPATH2, to specify a secondary path for the database to manage
copies of the active log, mirroring the volumes on which the logs are
stored.

The DB2_NEWLOGPATH2 registry variable allows the database to write an
identical second copy of log files to a different path. It is recommended
that you place the secondary log path on a physically separate disk
(preferably one that is also on a different disk controller). That way, the
disk controller cannot be a single point of failure.

Note:
     Because Windows NT and OS/2 do not allow "mounting" a device under an
     arbitrary path name, it is not possible (on these platforms) to
     specify a secondary path on a separate device.

DB2_NEWLOGPATH2 can be enabled (set to 1) or disabled (set to 0). The
default value is zero. If this variable is set to 1, the secondary path
name is the current value of the LOGPATH variable concatenated with the
character 2. For example, in an SMP environment, if LOGPATH is
/u/dbuser/sqllogdir/logpath, the secondary log path will be
/u/dbuser/sqllogdir/logpath2. In an MPP environment, if LOGPATH is
/u/dbuser/sqllogdir/logpath, DB2 will append the node indicator to the path
and use /u/dbuser/sqllogdir/logpath/NODE0000 as the primary log path. In
this case, the secondary log path will be
/u/dbuser/sqllogdir/logpath2/NODE0000.

When DB2_NEWLOGPATH2 is first enabled, it will not actually be used until
the current log file is completed on the next database startup. This is
similar to how NEWLOGPATH is currently used.

If there is an error writing to either the primary or secondary log path,
the database will mark the failing path as "bad", write a message to the
db2diag.log file, and write subsequent log records to the remaining "good"
log path only. DB2 will not attempt to use the "bad" path again until the
current log file is completed. When DB2 needs to open the next log file, it
will verify that this path is valid, and if so, will begin to use it. If
not, DB2 will not attempt to use the path again until the next log file is
accessed for the first time. There is no attempt to synchronize the log
paths, but DB2 keeps information about access errors that occur, so that
the correct paths are used when log files are archived. If a failure occurs
while writing to the remaining "good" path, the database abends.

7.6.8 Cross Platform Backup and Restore Support on Sun Solaris and HP

Support is now available for cross platform backup and restore support
between Sun Solaris and HP. When you transfer the backup image between
systems, you must transfer it in binary mode. On the target system, the
database must be created with the same code page/territory as the system on
which the original database was created.

7.6.9 DB2 Data Links Manager Considerations/Backup Utility Considerations

Replace the second paragraph in this section with:

   When files are linked, the Data Links servers schedule them to be copied
   asynchronously to an archive server such as ADSM, or to disk.
   When the backup utility runs, DB2 ensures that all files scheduled
   for copying have been copied. At the beginning of backup processing,
   DB2 contacts all Data Links servers that are specified in the DB2
   configuration file. If a Data Links server has one or more linked files
   and is not running, or stops running during the backup operation, the backup
   will not contain complete DATALINK information. The backup operation
   will complete successfully. Before the Data Links server can be marked
   as available to the database again, backup processing for all outstanding
   backups must complete successfully. If a backup is initiated when there
   are already twice the value of num_db_backups (see below) outstanding
   backups waiting to be completed on the Data Links server, the backup
   operation will fail. That Data Links server must be restarted
   and the outstanding backups completed before additional backups are allowed.

7.6.10 DB2 Data Links Manager Considerations/Restore and Rollforward
Utility Considerations

Replace paragraphs beginning with:

   When you restore a database or table space and do not specify
   the WITHOUT DATALINK...

   and

   When you restore a database or table space and you do specify
   the WITHOUT DATALINK option...

with:

   When you restore a database or table space, the following conditions
   must be satisfied for the restore operation to succeed:

   o If any Data Links Server recorded in the backup file is not running,
     the restore operation will still complete successfully.

     Tables with DATALINK column information that are affected by the missing
     Data Links server will be put into datalink reconcile pending state
     after the restore operation (or the rollforward operation, if used) completes.
     Before the Data Links servers can be marked as available to the database
     again, this restore processing must complete successfully.

   o If any Data Links Server recorded in the backup file stops running during
     the restore operation, the restore operation will fail. The restore can
     be restarted with the Data Links Server down (see above).

   o If a previous database restore operation is still incomplete on any
     Data Links server, subsequent database or table space restore operations
     will fail until those Data Links servers are restarted, and the incomplete
     restore is completed.

   o Information about all DATALINK columns that are recorded in the backup
     file must exist in the appropriate Data Links servers' registration tables.

     If all the information about the DATALINK columns is not recorded
     in the registration tables, the table with the missing DATALINK column
     information is put into datalink reconcile not possible state after
     the restore operation (or the roll-forward operation, if used) completes.

     If the backup is not recorded in the registration tables, it may mean
     that the backup file that is provided is earlier than the value for
     num_db_backups and has already been "garbage collected". This means that
     the archived files from this earlier backup have been removed and cannot
     be restored. All tables that have DATALINK columns are put into datalink
     reconcile pending state.

     If the backup is not recorded in the registration tables, it may mean that
     backup processing has not yet been completed because the Data Links server
     is not running. All tables that have DATALINK columns are put into datalink
     reconcile pending state. When the Data Links server is restarted,
     backup processing will be completed before restore processing.

     The table remains available to users, but the values in the DATALINK
     columns may not reference the files accurately (for example, a file
     may not be found that matches a value for the DATALINK column). If you
     do not want this behavior, you can put the table into check pending state
     by issuing the "SET CONSTRAINTS for tablename TO DATALINK RECONCILE PENDING"
     statement.

If, after a restore operation, you have a table in datalink reconcile not
possible state, you can fix the DATALINK column data in one of the ways
suggested under "Removing a Table from the Datalink_Reconcile_Not_Possible
State".

The note at the bottom of the first paragraph remains the same.

Add the following at the end of this section:

   It is strongly recommended that the datalink.cfg file be archived
   to cover certain unusual recovery cases, since the datalink.cfg file
   in the database backup image only reflects the datalink.cfg as of
   the backup time. Having the latest datalink.cfg file is required
   to cover all recovery cases. Therefore, the datalink.cfg file must
   be backed up after every ADD DATALINKS MANAGER or DROP DATALINKS MANAGER
   command invocation. This would help to retrieve the latest
   datalink.cfg file, if the latest datalink.cfg file is not available on disk.

   If the latest datalink.cfg file is not available on disk, replace
   the existing datalink.cfg file (restored from a backup image) with the latest
   datalink.cfg file that was archived before running a rollforward operation.
   Do this after the database is restored.

7.6.11 Restoring Databases from an Offline Backup without Rolling Forward

You can only restore without rolling forward at the database level, not the
table space level. To restore a database without rolling forward, you can
either restore a nonrecoverable database (that is, a database that uses
circular logging), or specify the WITHOUT ROLLING FORWARD parameter on the
RESTORE DATABASE command.

If you use the restore utility with the WITHOUT DATALINK option, all tables
with DATALINK columns are placed in datalink reconcile pending (DRP) state,
and no reconciliation is performed with the Data Links servers during the
restore operation.

If you do not use the WITHOUT DATALINK option, and a Data Links server
recorded in the backup file is no longer defined to the database (that is,
it has been dropped using the DROP DATALINKS MANAGER command), tables that
contain DATALINK data referencing the dropped Data Links server are put in
DRP state by the restore utility.

If you do not use the WITHOUT DATALINK option, all the Data Links servers
are available, and all information about the DATALINK columns is fully
recorded in the registration tables, the following occurs for each Data
Links server recorded in the backup file:

   * All files linked after the backup image that was used for the database
     restore operation are marked as unlinked (because they are not
     recorded in the backup image as being linked).
   * All files that were unlinked after the backup image, but that were
     linked before the backup image was taken, are marked as linked
     (because they are recorded in the backup image as being linked). If
     the file was subsequently linked to another table in another database,
     the restored table is put into the datalink reconcile pending state.

Note:
     The above cannot be done if the backup image that was used for the
     database restore operation was taken when at least one Data Links
     server was not running, since the DATALINK information in the backup
     is incomplete. The above is also not done if the backup image that was
     used for the database restore operation was taken after a database
     restore with or without rollforward. In both cases, all tables with
     DATALINK columns are placed in datalink reconcile pending state, and
     no reconciliation is performed with the Data Links servers during the
     restore operation.

7.6.12 Restoring Databases and Table Spaces, and Rolling Forward to the End
of the Logs

If you restore, then roll forward the database or table space to the end of
the logs (meaning that all logs are provided), a reconciliation check is
not required unless at least one of the Data Links servers recorded in the
backup file is not running during the restore operation. If you are not
sure whether all the logs were provided for the roll-forward operation, or
think that you may need to reconcile DATALINK values, do the following:

  1. Issue the SQL statement for the table (or tables) involved:

        SET CONSTRAINTS FOR tablename TO DATALINK RECONCILE PENDING

     This puts the table into datalink reconcile pending state and check
     pending state.
  2. If you do not want a table to be in check pending state, issue the
     following SQL statement:

        SET CONSTRAINTS FOR tablename IMMEDIATE CHECKED

     This takes the table out of check pending state, but leaves it in
     datalink reconcile pending state. You must use the reconcile utility
     to take the table out of this state.

It may happen that the backup file contains DATALINK data that refers to a
DB2 Data Links Manager (that is, a DB2 Data Links Manager was registered to
the database when the backup was taken) that has been dropped from the
database. For each table space being rolled forward that contains at least
one table with DATALINK data referencing the dropped DB2 Data Links
Manager, all tables are put in DRP state by the rollforward utility.

7.6.13 DB2 Data Links Manager and Recovery Interactions

The following table shows the different types of recovery that you can
perform, the DB2 Data Links Manager processing that occurs during restore
and roll-forward processing, and whether you need to run the Reconcile
utility after the recovery is complete:
 Type of Recovery DB2 Data Links Manager      DB2 Data Links Manager      Reconcile
                  Processing during Restore   Processing during
                                              Rollforward
 Non-recoverable database (logretain=NO)
 Database restore Fast reconcile is performed N/A                         Can be optionally
 of a complete                                                            run if problem with
 backup, all Data                                                         file links is
 Links Servers up                                                         suspected
 Database restore Tables put in               N/A                         Required
 using WITHOUT    Datalink_Reconcile _Pending
 DATALINK option  state
 Database restore Fast reconcile is performed NA                          Required for tables
 of a complete    only on those tables in                                 in table spaces
 backup, at least table spaces that do not                                with links to the
 one Data Links   have links to a Data Links                              Data Links server
 server down      server that is down, other                              that is down
                  tables put in
                  Datalink_Reconcile_Pending
                  state
 Database restore Fast reconcile is not       NA                          Required
 of an incomplete performed, all tables with
 backup, all Data DATALINK columns put in
 Links servers up Datalink_Reconcile_Pending
                  state
 Recoverable database (logretain=YES)
 Database restore Fast reconcile is performed N/A                         Optional
 using WITHOUT
 ROLLING FORWARD
 option, using a
 complete backup,
 all Data Links
 servers up
 Database restore Tables put in               N/A                         Required
 using WITHOUT    Datalink_Reconcile _Pending
 ROLLING FORWARD  state
 and WITHOUT
 DATALINK options,
 using a complete
 or incomplete
 backup, Data
 Links servers up
 or down
 Database restore Fast reconcile is performed N/A                         Required on tables
 using WITHOUT    only on those tables in                                 in table spaces
 ROLLING FORWARD  table spaces that do not                                with links to the
 option, using a  have links to the Data                                  Data Links servers
 complete backup, Links servers that are                                  that are down
 at least one Datadown, other tables put in
 Links server downDatalink_Reconcile_Pending
                  state
 Database restore Fast reconcile is not       N/A                         Required
 using WITHOUT    performed, all tables with
 ROLLING FORWARD  DATALINK columns put into
 option, using an Datalink_Reconcile_Pending
 incomplete       state
 backup, Data
 Links servers up
 or down
 Database restore No action                   No action                   Optional
 and roll forward
 to end of logs,
 using a complete
 backup, all Data
 Links servers up
 Database restore No action                   No action                   Optional
 and roll forward
 to end of logs,
 using a complete
 backup, at least
 one Data Links
 server down
 during roll
 forward
 processing
 Database restore No action                   All tables with DATALINK    Required for all
 and roll forward                             columns put into            tables with
 to end of logs,                              Datalink_Reconcile_Pending  DATALINK columns
 using a complete                             state
 or an incomplete
 backup, any Data
 Links server down
 during restore
 Database restore No action                   No action                   Optional
 and roll forward
 to end of logs,
 using an
 incomplete
 backup, all Data
 Links servers up
 during restore
 Database restore No action                   All tables in table spaces  Required
 and roll forward                             with links to a Data Links
 to end of logs,                              server where the backup is
 using a complete                             unknown put in
 or an incomplete                             Datalink_Reconcile_Pending
 backup, all Data                             state
 Links servers up,
 backup unknown at
 any Data Links
 server
 Table space      No action                   No action                   Optional
 restore and roll
 forward to end of
 logs, using a
 complete backup,
 all Data Links
 servers up
 Table space      No action                   No action                   Optional
 restore and roll
 forward to end of
 logs, using a
 complete backup,
 at least one Data
 Links server down
 during roll
 forward
 processing
 Table space      No action                   All tables in table spaces  Required for tables
 restore and roll                             with links to any Data      in table spaces
 forward to end of                            Links server that is down   with links to any
 logs, using a                                put into                    Data Links server
 complete or an                               Datalink_Reconcile_Pending  that is down
 incomplete                                   state
 backup, any Data
 Links server down
 during restore
 processing
 Table space      No action                   No action                   Optional
 restore and roll
 forward to end of
 logs, using an
 incomplete
 backup, all Data
 Links servers up
 Database restore No action                   Tables put in               Required
 and roll forward                             Datalink_Reconcile _Pending
 to a point in                                state
 time, using a
 complete or an
 incomplete
 backup, Data
 Links servers up
 or down during
 restore and/or
 roll forward
 processing
 Table space      No action                   Tables put in               Required
 restore and roll                             Datalink_Reconcile _Pending
 forward to a                                 state
 point in time,
 using a complete
 or an incomplete
 backup, Data
 Links servers up
 or down during
 restore and/or
 rollfoward
 processing
 Database restore Tables put in               N/A                         Optional, but
 to a different   Datalink_Reconcile                                      tables in
 database name,   _Not_Possible state                                     Datalink_Reconcile
 alias, hostname,                                                         _Not_Possible state
 or instance with                                                         must be manually
 no roll forward                                                          fixed
 (NOTE1)
 Database restore No action                   Tables put in               Optional, but
 to a different                               Datalink_Reconcile          tables in
 database name,                               _Not_Possible state         Datalink_Reconcile
 alias, hostname                                                          _Not_Possible state
 or instance, and                                                         must be manually
 roll forward                                                             fixed
 Database restore Tables put in               No action                   Required
 from an unusable Datalink_Reconcile _Pending
 backup (image hasstate
 been
 garbage-collected
 on the Data Links
 server) with no
 roll forward
 (NOTE1), with or
 without WITHOUT
 DATALINK option
 Database restore No action                   Tables put in               Required
 from an unusable                             Datalink_Reconcile _Pending
 backup (image has                            state
 been
 garbage-collected
 on the Data Links
 server), and roll
 forward, with or
 without WITHOUT
 DATALINK option
 Table space      No action                   Tables put in               Required
 restore from an                              Datalink_Reconcile _Pending
 unusable backup                              state
 (image has been
 garbage-collected
 on the Data Links
 server), and roll
 forward

Note:

  1. A restore using an offline backup and the WITHOUT ROLLING FORWARD
     option (logretain is on), or a restore using an offline backup
     (logretain is off).

  2. A complete backup is a backup taken when all required Data Links
     servers were running. An incomplete backup is a backup taken when at
     least one required Data Links server was not running.

  3. Fast reconcile processing will not be performed if the backup image
     that was used for the database restore operation was taken after a
     database restore, with or without rollforward. In this case, all
     tables with DATALINK columns are put in Datalink_Reconcile_Pending
     state.

7.6.14 Detection of Situations that Require Reconciliation

Following are some situations in which you may need to run the reconcile
utility:

   * The entire database is restored and rolled forward to a point in time.
     Because the entire database is rolled forward to a committed
     transaction, no tables will be in check pending state (due to
     referential constraints or check constraints). All data in the
     database is brought to a consistent state. The DATALINK columns,
     however, may not be synchronized with the metadata in the DB2 Data
     Links Manager, and reconciliation is required.

     In this situation, tables with DATALINK data will already be in DRP
     state. You should invoke the reconcile utility for each of these
     tables.
   * A particular Data Links server running the DB2 Data Links Manager
     loses track of its metadata. This can occur for different reasons. For
     example:
        o The Data Links server was cold started.
        o The Data Links server metadata was restored to a back-level
          state.
     In some situations, such as during SQL UPDATEs and DELETEs, DB2 may be
     able to detect a problem with the metadata in a Data Links server. In
     these situations, the SQL statement would fail. You would put the
     table in DRP state by using the SET CONSTRAINTS statement, then run
     the reconcile utility on that table.
   * A file system is not available (for example, because of a disk crash)
     and is not restored to the current state. In this situation, files may
     be missing.
   * A DB2 Data Links Manager is dropped from a database, and there are
     DATALINK FILE LINK CONTROL values referencing that DB2 Data Links
     Manager. You should run the reconcile utility on such tables.

  ------------------------------------------------------------------------

7.7 Appendix C. User Exit for Database Recovery

Under the section "Archive and Retrieve Considerations", the following
paragraph is no longer true and should be removed from the list:

   A user exit may be interrupted if a remote client loses its connection
   to the DB2 server. That is, while handling the archiving of logs
   through a user exit, one of the other SNA-connected clients dies
   or powers off resulting in a signal (SIGUSR1) being sent to the server.
   The server passes the signal to the user exit causing an interrupt.
   The user exit program can be modified to check for an interrupt
   and then continue.

The Error Handling section has a Notes list that should replace the
contents of Note 3 with the following information:

   * User exit program requests are suspended for five minutes. During this
     time, all requests are ignored including the log file request that
     caused the return code.

     Following the five minute suspension in processing requests, the next
     request is processed. If no error occurs with the processing of this
     request, then processing of new user exit program requests continues
     and DB2 will reissue the archive request for the log files that either
     failed to archive previously, or were suspended. If a return code of
     greater than 8 is generated during the retry, requests are suspended
     for an additional five minutes. The five minute suspensions continue
     until the problem is corrected or the database is stopped and
     restarted.

     Once all applications disconnect from the database and the database is
     reopened, DB2 will issue the archive request for any log file that
     might not have been successfully archived in the previous use of the
     database.

     If the user exit program fails to archive log files, your disk can be
     filled with log files and performance may be degraded because of extra
     work to format these log files. Once the disk becomes full, the
     database manager will not accept further application requests for
     database changes.

     If the user exit program was called to retrieve log files,
     roll-forward recovery is suspended but not stopped unless a stop was
     specified in the ROLLFORWARD DATABASE utility. If a stop was not
     specified, you can correct the problem and resume recovery.

  ------------------------------------------------------------------------

7.8 Appendix D. Issuing Commands to Multiple Database Partition Servers

At the bottom of the section "Specifying the Command to Run", add the
following:

When you run any korn-shell shell-script which contains logic to read from
stdin in the background, you should explicitly redirect stdin to a source
where the process can read without getting stopped on the terminal (SIGTTIN
message). To redirect stdin, you can run a script with the following form:

   shell_script </dev/null &

if there is no input to be supplied.

In a similar way, you should always specify </dev/null when running db2_all
in the background. For example:

   db2_all ";run_this_command" </dev/null &

By doing this you can redirect stdin and avoid getting stopped on the
terminal.

An alternative to this method, when you are not concerned about output from
the remote command, is to use the "daemonize" option in the db2_all prefix:

   db2_all ";daemonize_this_command" &

  ------------------------------------------------------------------------

7.9 Appendix I. High Speed Inter-node Communications

The following section has been updated:

7.9.1 Enabling DB2 to Run Using VI

Detailed installation information is found in DB2 Enterprise - Extended
Edition for Windows Quick Beginnings.

After completing the installation of DB2 as documented in DB2 Enterprise -
Extended Edition for Windows õ™ütÏJ¦—, set the following DB2 registry
variables and carry out the following tasks on each database partition
server in the instance:

   * Set DB2_VI_ENABLE=ON

     Use the db2set command to modify the value for the registry variable.
     Use the db2_all command to run the db2set command on all database
     partition servers in the instance. You must be logged on with a user
     account that is a member of the Administrators group to run the
     db2_all command.

     In the following example, the ; character is placed inside the double
     quotation marks to allow the request to run concurrently on all the
     database partition servers in the instance:

        db2_all ";db2set DB2_VI_ENABLE=ON"

     For more information about the db2_all command, see "Issuing Commands
     to Multiple Database Partition Servers" in the Administration Guide:
     Implementation.
   * Set DB2_VI_DEVICE=nic0

     For example:

        db2_all ";db2set DB2_VI_DEVICE=nic0"

     Note:
          With Synfinity Interconnect, this variable should be set
          DB2_VI_DEVICE=VINIC. The device name (VINIC) must be in upper
          case.
   * Set DB2_VI_VIPL=vipl.dll

     For example:

        db2_all ";db2set DB2_VI_VIPL=vipl.dll"

     Note:
          The value used in the example is the default for the registry
          variable. For more information on the registry variables, see
          Administration Guide: Performance.
   * Enter db2start on the MPP instance.
   * Review the db2diag.log file. There should be one message for each
     partition stating that "VI is enabled."
   * Fast Communications Manager (FCM) configuration parameters may need to
     be updated. Should you encounter a problem as a result of resource
     constraints involving FCM, you should raise the values of the FCM
     configuration parameters. If you are moving from another high speed
     interconnect environment where you have increased the values for the
     FCM configuration parameters, you may need to lower these values.
     Also, on Windows NT, you may be required to set the DB2NTMEMSIZE
     registry variable to override the DB2 defaults. Refer to
     Administration Guide: Performance for more information on the registry
     variables.

  ------------------------------------------------------------------------

Administration Guide: Performance (æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

8.1 Chapter 3. Application Considerations

8.1.1 Specifying the Isolation Level

Within the section titled "Specifying the Isolation Level", add the
following paragraphs:

In addition to setting the isolation level at the package-level when
preparing or binding an application, you can set an isolation level at the
statement-level. A statement-level isolation level is specified using the
WITH-clause.

The following SQL statements support statement-level isolation:

   * SELECT statement
   * SELECT INTO
   * Searched DELETE
   * INSERT
   * Searched UPDATE
   * DECLARE CURSOR

There are some conditions associated with the use of statement-level
isolation:

   * The WITH-clause cannot be used on subqueries
   * The WITH UR option only applies to read-only operations. If it is used
     in other situations, the statement is automatically changed from "UR"
     to "CS".
   * The default isolation level for a statement is the isolation level of
     the package in which the statement is bound.
   * The statement-level isolation level overrides the isolation level
     specified for the package in which the statement appears.

8.1.2 Adjusting the Optimization Class

Within the section titled "Adjusting the Optimization Class", replace the
current level 2 information with the following:

2 -
     This class directs the optimizer to use a degree of optimization which
     significantly improves upon that of class 1, while keeping the
     compilation cost significantly lower than classes 3 and above for
     complex queries. In particular:
        o All available statistics, including both frequency and quantile
          non-uniform distribution statistics, are utilized.
        o All of the query rewrite rules are applied including the routing
          of queries to summary tables, except computationally intensive
          rules which are applicable only in very rare cases.
        o Greedy join enumeration is used.
        o A wide range of access methods are considered, including list
          prefetch and summary table routing.
        o The star join strategy is considered, if applicable.

     Optimization class 2 is quite similar to class 5 except that it uses
     Greedy join enumeration rather than Dynamic Programming. This class
     has the most optimization of all the optimization classes that use the
     Greedy join enumeration algorithm, which considers fewer alternatives
     for complex queries, and therefore consumes less compilation time than
     classes 3 and above. It is therefore recommended for very complex
     queries in a decision support or online analytic processing (OLAP)
     environment. In such cases, there is a good chance the same query is
     executed infrequently, so that its access plan is unlikely to remain
     in the cache until the next occurrence of the query.

8.1.3 Dynamic Compound Statements

This new section should be added after the section titled "Compound SQL":

A dynamic compound statement groups other SQL statements together into an
executable block. Within the dynamic compound statement you can declare SQL
variables, declare conditions associated with SQLSTATEs, and have one or
more SQL procedural statements. If an error occurs in the dynamic compound
statement, all prior SQL statements are rolled back and the remaining SQL
statements in the dynamic compound statement are not processed.

The dynamic compound statement can be embedded in a trigger, SQL function,
SQL method, or issued through the use of dynamic SQL statements. This
executable statement can be dynamically prepared. No privileges are
required to invoke the statement but the authorization ID associated with
the statement must have the necessary privileges to invoke the embedded SQL
statements within the compound statement.

Variables are present in the sub-statements in the variable declaration.
Conditions are present in the sub-statements based on the SQLSTATE values
of the condition declaration. Dynamic compound statements are compiled by
DB2 as a single statement. This statement can be used effectively for short
scripts involving little control flow logic but significant data flow. For
larger constructs with nested complex control flow, you should consider
using SQL procedures.

There are several control flow logic statements that can be used within the
dynamic compound statement. These include: the FOR statement, the IF
statement, the ITERATE statement, and the WHILE statement. Details about
these statements, and the other supported statements, are found in the SQL
Reference.
  ------------------------------------------------------------------------

8.2 Chapter 4. Environmental Considerations

Following the section titled "Using the Index Advisor", add the following
section:

8.2.1 Using Larger Index Keys

It is possible to allow columns with a length greater than 255 bytes to be
specified as part of an index key. The DB2_INDEX_2BYTEVARLEN registry
variable allows for the use of 2 bytes instead of 1 to store the length of
an index key.

There are several SQL statements affected by changes to the registry
variable. They are:

   * CREATE TABLE. Primary, foreign, and unique keys with variable key
     parts can have a size greater than 255 bytes.
   * CREATE INDEX. All indexes, including unique indexes and include
     columns, having variable key parts can have a size greater than 255
     bytes.
   * ALTER TABLE. Primary, foreign, and unique keys with variable key parts
     can have a size greater than 255 bytes. All indexes, including unique
     indexes and include columns, having variable key parts can have a size
     greater than 255 bytes.

     The foreign key restriction to 255 bytes is removed no matter what the
     value of the registry variable. The truth-condition for the primary
     key corresponding to the foreign key enforces any restriction or
     limit.

To convert existing indexes to use larger index keys: drop the indexes, set
the DB2_INDEX_2BYTEVARLEN registry variable to ON, and then recreate the
indexes (using the larger columns).

For more information on the SQL statements, including syntax descriptions,
refer to the SQL Reference.
  ------------------------------------------------------------------------

8.3 Chapter 5. System Catalog Statistics

8.3.1 Collecting and Using Distribution Statistics

In the subsection called "Example of Impact on Equality Predicates", there
is a discussion of a predicate C <= 10. The error is stated as being -86%.
This is incorrect. The sentence at the end of the paragraph should read:

   Assuming a uniform data distribution and using formula (1), the number of
   rows that satisfy the predicate is estimated as 1, an error of -87.5%.

In the subsection called "Example of Impact on Equality Predicates", there
is a discussion of a predicate C > 8.5 AND C <= 10. The estimate of the r_2
value using linear interpolation must be changed to the following:

          10 - 8.5
   r_2 *= ---------- x (number of rows with value > 8.5 and <= 100.0)
          100 - 8.5
          10 - 8.5
   r_2 *= ---------- x (10 - 7)
          100 - 8.5
          1.5
   r_2 *= ---- x (3)
          91.5
   r_2 *= 0

The paragraph following this new example must also be modified to read as
follows:

   The final estimate is r_1 + r_2 *= 7,
   and the error is only -12.5%.

8.3.2 Rules for Updating Catalog Statistics

Within the section titled "Rules for Updating Column Statistics", the last
bulleted-list item in the first list item should be replaced by the
following:

HIGH2KEY must be greater than LOW2KEY whenever there are more than 3
distinct values in the corresponding column. In the case of 3 or less
distinct values in the column, HIGH2KEY can be equal to LOW2KEY.

8.3.3 Sub-element Statistics

In FixPak 1, an option is provided to collect and use sub-element
statistics. These are statistics about the content of data in columns when
the data has a structure in the form of a series of sub-fields or
sub-elements delimited by blanks.

For example, suppose a database contains a table DOCUMENTS in which each
row describes a document, and suppose that in DOCUMENTS there is a column
called KEYWORDS containing a list of relevant keywords relating to this
document for text retrieval purposes. The values in KEYWORDS might be as
follows:

   'database simulation analytical business intelligence'
   'simulation model fruitfly reproduction temperature'
   'forestry spruce soil erosion rainfall'
   'forest temperature soil precipitation fire'

In this example, each column value consists of 5 sub-elements, each of
which is a word (the keyword), separated from the others by one blank.

For queries that specify LIKE predicates on such columns using the %
match_all character:

   SELECT .... FROM DOCUMENTS WHERE KEYWORDS LIKE '%simulation%'

it is often beneficial for the optimizer to know some basic statistics
about the sub-element structure of the column, namely:

SUB_COUNT
     The average number of sub-elements.

SUB_DELIM_LENGTH
     The average length of each delimiter separating each sub-element,
     where a delimiter, in this context, is one or more consecutive blank
     characters.

In the KEYWORDS column example, SUB_COUNT is 5, and SUB_DELIM_LENGTH is 1,
because each delimiter is a single blank character.

In FixPak 1, the system administrator controls the collection and use of
these statistics by means of an extension to the DB2_LIKE_VARCHAR registry
variable. This registry variable affects how the DB2 UDB optimizer deals
with a predicate of the form:

   COLUMN LIKE '%xxxxxx'

where xxxxxx is any string of characters; that is, any LIKE predicate whose
search value starts with a % character. (It may or may not end with a %
character). These are referred to as "wildcard LIKE predicates" below. For
all predicates, the optimizer has to estimate how many rows match the
predicate. For wildcard LIKE predicates, the optimizer assumes that the
COLUMN being matched has a structure of a series of elements concatenated
together to form the entire column, and estimates the length of each
element based on the length of the string, excluding leading and trailing %
characters. The new syntax is:

   db2set  DB2_LIKE_VARCHAR=[Y|N|S|num1][,Y|N|num2]

   where
   - the first term (preceding the comma) means the following,
      but only for columns that do not have positive
      sub-element statistics
      S                 Use the algorithm as used in DB2 Version 2.
      N                 Use a fixed-length sub-element algorithm.
      Y    (default)    Use a variable-length sub-element algorithm
                        with a default value for the algorithm parameter.
      num1              Use a variable-length sub-element algorithm,
                        and use num1 as the algorithm parameter.

   - the second term (following the comma) means:
      N    (default)    Do not collect or use sub-element statistics.
      Y                 Collect sub-element statistics. Use a
                        variable-length sub-element algorithm that
                        uses those statistics, together with a default
                        value for the algorithm parameter in the case of columns
                        with positive sub-element statistics.
      num2              Collect sub-element statistics. Use a
                        variable-length sub-element algorithm that
                        uses those statistics, together with num2 as
                        the algorithm parameter in the case of columns with
                        positive sub-element statistics.

If the value of DB2_LIKE_VARCHAR contains only the first term, no
sub-element statistics are collected, and any that have previously been
collected are ignored. The value specified affects how the optimizer
calculates the selectivity of wildcard LIKE predicates in the same way as
before; that is:

   * If the value is S, the optimizer uses the same algorithm as was used
     in DB2 Version 2, which does not presume the sub-element model.
   * If the value is N, the optimizer uses an algorithm that presumes the
     sub-element model, and assumes that the COLUMN is of a fixed length,
     even if it is defined as variable length.
   * If the value is Y (the default) or a floating point constant, the
     optimizer uses an algorithm that presumes the sub-element model and
     recognizes that the COLUMN is of variable length, if so defined. It
     also infers sub-element statistics from the query itself, rather than
     from the data. This algorithm involves a parameter (the "algorithm
     parameter") that specifies how much longer the element is than the
     string enclosed by the % characters.
   * If the value is Y, the optimizer uses a default value of 1.9 for the
     algorithm parameter.
   * If the value is a floating point constant, the optimizer uses the
     specified value for the algorithm parameter. This constant must lie
     within the range of 0 to 6.2.

If the value of DB2_LIKE_VARCHAR contains two terms, and the second is Y or
a floating point constant, sub-element statistics on single-byte character
set string columns of type CHAR, VARCHAR, GRAPHIC, or VARGRAPHIC are
collected during a RUNSTATS operation and used during compilation of
queries involving wildcard LIKE predicates. The optimizer uses an algorithm
that presumes the sub-element model and uses the SUB_COUNT and
SUB_DELIM_LENGTH statistics, as well as an algorithm parameter, to
calculate the selectivity of the predicate. The algorithm parameter is
specified in the same way that the inferential algorithm is specified, that
is:

   * If the value is Y, the optimizer uses a default value of 1.9 for the
     algorithm parameter.
   * If the value is a floating point constant, the optimizer uses the
     specified value for the algorithm parameter. This constant must lie
     within the range of 0 to 6.2.

If, during compilation, the optimizer finds that sub-element statistics
have not been collected on the column involved in the query, it will use
the "inferential" sub-element algorithm; that is, the one used when only
the first term of DB2_LIKE_VARCHAR is specified. Thus, in order for the
sub-element statistics to be used by the optimizer, the second term of
DB2_LIKE_VARCHAR must be set both during RUNSTATS and compilation.

The values of the sub-element statistics can be viewed by querying
SYSIBM.SYSCOLUMNS. For example:

   select substr(NAME,1,16), SUB_COUNT, SUB_DELIM_LENGTH
      from sysibm.syscolumns where tbname = 'DOCUMENTS'

The SUB_COUNT and SUB_DELIM_LENGTH columns are not present in the
SYSSTAT.COLUMNS statistics view, and therefore cannot be updated.

Note:
     RUNSTATS may take longer if this option is used. For example, RUNSTATS
     may take between 15 and 40% longer on a table with five character
     columns, if the DETAILED and DISTRIBUTION options are not used. If
     either the DETAILED or the DISTRIBUTION option is specified, the
     percentage overhead is less, even though the absolute amount of
     overhead is the same. If you are considering using this option, you
     should assess this overhead against improvements in query performance.

  ------------------------------------------------------------------------

8.4 Chapter 6. Understanding the SQL Compiler

The following sections require changes:

8.4.1 Replicated Summary Tables

The following information will replace or be added to the existing
information already in this section:

Replicated summary tables can be used to assist in the collocation of
joins. For example, if you had a star schema where there is a large fact
table spread across twenty nodes, then the joins between the fact table and
the dimension tables are most efficient if these tables are collocated.

By placing all of the tables in the same nodegroup, at most there would one
dimension table partitioned correctly for a collocated join. All other
dimension tables would not be able to be used in a collocated join because
the join column(s) on the fact table would not correspond to the fact
table's partitioning key.

For example, you could have a table called FACT (C1, C2, C3, ...)
partitioned on C1; and a table called DIM1 (C1, dim1a, dim1b, ...)
partitioned on C1; and a table called DIM2 (C2, dim2a, dim2b, ...)
partitioned on C2; and so on.

From this example, you could see that the join between FACT and DIM1 is
perfect because the predicate DIM1.C1 = FACT.C1 would be collocated. Both
of these tables are partitioned on column C1.

The join between DIM2 with the predicate WHERE DIM2.C2 = FACT.C2 cannot be
collocated because FACT is partitioned on column C1 and not on column C2.

In this case, it would be good to replicate DIM2 in the fact table's
nodegroup. In this way we can do the join locally on each partition.

Note:
     The replicated summary tables discussion here has to do with
     intra-database replication. Inter-database replication has to do with
     subscriptions, control tables, and data located in different databases
     and on different operating systems. If you are interested in
     inter-database replication refer to the Replication ®®n¯Pø¥ÝãÏƒ¾U for
     more information.

When creating a replicated summary table, the source table could be a
single-node nodegroup table or a multi-node nodegroup table. In most cases,
the table is small and can be placed in a single-node nodegroup. You may
place a limit on the data to be replicated by specifying only a subset of
the columns from the table, or by limiting the number of rows through the
predicates used, or by using both methods when creating the replicated
summary table.

Note:
     The data capture option is not required for replicated summary tables
     to function.

The replicated summary table could also be created in a multi-node
nodegroup. The nodegroup is the same as the nodegroup in which you have
placed your large tables. In this case, copies of the source table are
created on all of the partitions of the nodegroup. Joins between a large
fact table and the dimension tables have a better chance of being done
locally in this environment rather than having to broadcast the source
table to all partitions.

Indexes on replicated tables are not created automatically. Indexes are
created and may be different from those identified in the source table.

Note:
     You cannot create unique indexes (or put on any constraints) on the
     replicated tables. This will prevent constraint violations that are
     not present on the source tables. These constraints are disallowed
     even if there is the same constraint on the source table.

After using the REFRESH statement, you should run RUNSTATS on the
replicated table as you would any other table.

The replicated tables can be referenced directly within a query. However,
you cannot use the NODENUMBER() predicate with a replicated table to see
the table data on a particular partition.

To see if a created replicated summary table was used (given a query that
referenced the source table), you can use the EXPLAIN facility. First, you
would ensure the EXPLAIN tables existed. Then, you would create an explain
plan for the SELECT statement you are interested in. Finally, you would use
db2exfmt utility to format the EXPLAIN output.

The access plan chosen by the optimizer may or may not use the replicated
summary table depending on the information that needs to be joined. Not
using the replicated summary table could occur if the optimizer determined
that it would be cheaper to broadcast the original source table to the
other partitions in the nodegroup.

8.4.2 Data Access Concepts and Optimization

The section "Multiple Index Access" under "Index Scan Concepts" has
changed.

Add the following information before the note at the end of the section:

To realize the performance benefits of dynamic bitmaps when scanning
multiple indexes, it may be necessary to change the value of the sort heap
size (sortheap) database configuration parameter, and the sort heap
threshold (sheapthres) database manager configuration parameter.

Additional sort heap space is required when dynamic bitmaps are used in
access plans. When sheapthres is set to be relatively close to sortheap
(that is, less than a factor of two or three times per concurrent query),
dynamic bitmaps with multiple index access must work with much less memory
than the optimizer anticipated.

The solution is to increase the value of sheapthres relative to sortheap.

The section "Search Strategies for Star Join" under "Predicate Terminology"
has changed.

Add the following information at the end of the section:

The dynamic bitmaps created and used as part of the Star Join technique
uses sort heap memory. See Chapter 13, "Configuring DB2" in the
Administration Guide: Performance manual for more information on the Sort
Heap Size (sortheap) database configuration parameter.
  ------------------------------------------------------------------------

8.5 Chapter 8. Operational Performance

8.5.1 Managing the Database Buffer Pool

Within the section titled "Managing the Database Buffer Pool", add the
following information after the paragraph that begins "When creating the
buffer pool, by default the page size is 4 KB.":

When working with Windows 2000, buffer pool sizes up to 64 GB in size are
supported less the size of DB2 and the operating system. (This assumes that
DB2 is the primary product on the system.) This support is available
through Microsoft Address Windowing Extensions (AWE).

Although AWE can be used with buffer pools of any size, if you require AWE
use on larger buffer pools there are other recommended Windows products.
Windows 2000 Advanced Server provides support for up to 8 GB of memory.
Windows 2000 Data Center Server provides support for up to 64 GB of memory.

DB2 and Windows 2000 must be configured correctly to support AWE buffer
pools. The buffer pool that will take advantage of AWE must exist in the
database.

To have a 3 GB user space allocated, use the /3GB Windows 2000 boot option.
This allows a larger AWE window size to be used. To enable access to more
than 4 GB of memory via the AWE memory interface, use the /PAE Windows 2000
boot option. To verify that you have the correct boot option selected,
under Control, select System, then select "Startup and Recovery". From the
drop-down list you can see the available boot options. If the boot option
(/3GB or /PAE) you want is selected, then you are ready to proceed to the
next task in setting up AWE support. If the option you want is not
available for selection, you must add the option to the boot.ini file on
the system drive. The boot.ini file contains a list of actions to be done
when the operating system is started. Add /3GB, or /PAE, or both (separated
by blanks) at the end of the list of existing parameters. Once you have
saved this changed file, you can verify and select the correct boot option
as mentioned above.

Windows 2000 also has to be modified to associate the "lock pages in
memory"-right with the user under which DB2 is installed. To set the "lock
pages in memory"-right, once you have logged on to Windows 2000 as the user
who installed DB2, under the Start menu on Windows 2000 select the
"Administrative Tools" folder, and then the "Local Security Policy"
program. Under the local policies, you can select the user rights
assignment for the "lock pages in memory"-right.

DB2 requires the setting of the DB2_AWE registry variable. To set this
registry variable correctly, you will need to know the buffer pool ID of
the buffer pool you wish to allow support of AWE. You also need to know the
number of physical pages and the address window pages to allocate. The
number of physical pages to allocate should be some value less than the
total available physical pages. The actual number chosen will depend on
your working environment. For example, if you have an environment where
only DB2 and database applications are used on your system, then you can
choose to have from one-half to one GB less than the total size of the
physical pages as the value used with the DB2_AWE variable. If you have an
environment where other non-database applications are using the system,
then you will have to increase the value you subtract from the total to
allow more physical pages for those other applications. The number used in
the DB2_AWE registry variable is the number of physical pages to be used in
support of AWE and for use by DB2. The upper limit on the address window
pages is 1.5 GB, or 2.5 GB when the /3GB Windows 2000 boot option is in
effect.

For information on setting the DB2 registry variable DB2_AWE, see the table
of new and changed registry variables in "Appendix A. DB2 Registry and
Environment Variables" later in this section.

8.5.2 Managing Multiple Database Buffer Pools

Within the section titled "Managing Multiple Database Buffer Pools", add
the following paragraph after the paragraph that begins "When working with
your database design, you may have determined that tables with 8 KB page
sizes are best.":

When working with Windows 2000, the DB2_AWE registry variable can be used
to override the buffer pool size settings in the catalog and configuration
files. Use of this registry variable allows buffer pool sizes of up to
approximately 64 GB.

Within the same section, replace the paragraph just before the note with
the following:

The reason for allowing the database manager to start with minimal-sized
values is to allow you to connect to the database. You can then reconfigure
the buffer pool sizes, or perform other critical tasks, with the goal of
restarting the database with correct buffer pool sizes. Do not consider
operating the database for an extended time in such a state.

Within the section titled "Reorganizing Catalogs and User Tables", the last
sentence (with a short list) in the paragraph that begins "The REORG
utility allows you to specify a temporary table space..." can be replaced
by:

Using the same table space to reorganize tables is faster but greater
logging occurs and there must be enough space for the reorganized table. If
you specify a temporary table space, it is generally recommended that you
specify an SMS temporary table space. A DMS temporary table space is not
recommended since you can only have on REORG in progress using this type of
table space.

Within the section titled "Extending Memory", add the following paragraph
after the third paragraph in this section:

When allocating Windows 2000 Address Windowing Extensions (AWE) buffer
pools using the DB2_AWE registry variable, the extended storage cache
cannot be used.
  ------------------------------------------------------------------------

8.6 Chapter 9. Using the Governor

Within the section titled "Creating the Governor Configuration File", the
first sentence in the first paragraph following the schedule action
discussion should be replaced with:

If more than one rule applies to an application, all of the rules are
applied. Depending on the rule and the limits being set, the action
associated with the rule limit encountered first is the action that is
first to be applied.
  ------------------------------------------------------------------------

8.7 Chapter 13. Configuring DB2

The following parameters require changes:

8.7.1 Sort Heap Size (sortheap)

The "Recommendation" section has changed. The information here should now
read:

When working with the sort heap, you should consider the following:

   * Appropriate indexes can minimize the use of the sort heap.
   * Hash join buffers and dynamic bitmaps (used for index ANDing and Star
     Joins) use sort heap memory. Increase the size of this parameter when
     these techniques are used.
   * Increase the size of this parameter when frequent large sorts are
     required.
   * ... (the rest of the items are unchanged)

8.7.2 Sort Heap Threshold (sheapthres)

The second last paragraph in the description of this parameter has changed.
The paragraph should now read:

Examples of those operations that use the sort heap include: sorts, dynamic
bitmaps (used for index ANDing and Star Joins), and operations where the
table is in memory.

The following information is to be added to the description of this
parameter:

There is no reason to increase the value of this parameter when moving from
a single-node to a multi-node environment. Once you have tuned the database
and database manager configuration parameters on a single node (in a DB2
EE) environment, the same values will in most cases work well in a
multi-node (in a DB2 EEE) environment.

The Sort Heap Threshold parameter, as a database manager configuration
parameter, applies across the entire DB2 instance. The only way to set this
parameter to different values on different nodes or partitions, is to
create more than one DB2 instance. This will require managing different DB2
databases over different nodegroups. Such an arrangement defeats the
purpose of many of the advantages of a partitioned database environment.

8.7.3 Maximum Percent of Lock List Before Escalation (maxlocks)

The following change pertains to the Recommendation section of the "Maximum
Percent of Lock List Before Escalation (maxlocks)" database configuration
parameter.

Recommendation: The following formula allows you to set maxlocks to allow
an application to hold twice the average number of locks:

   maxlocks = 2 * 100 / maxappls

Where 2 is used to achieve twice the average and 100 represents the largest
percentage value allowed. If you have only a few applications that run
concurrently, you could use the following formula as an alternative to the
first formula:

   maxlocks = 2 * 100 / (average number of applications running
concurrently)

One of the considerations when setting maxlocks is to use it in conjunction
with the size of the lock list (locklist). The actual limit of the number
of locks held by an application before lock escalation occurs is:

   maxlocks * locklist * 4096 / (100 * 36)

Where 4096 is the number of bytes in a page, 100 is the largest percentage
value allowed for maxlocks, and 36 is the number of bytes per lock. If you
know that one of your applications requires 1000 locks, and you do not want
lock escalation to occur, then you should choose values for maxlocks and
locklist in this formula so that the result is greater than 1000. (Using 10
for maxlocks and 100 for locklist, this formula results in greater than the
1000 locks needed.)

If maxlocks is set too low, lock escalation happens when there is still
enough lock space for other concurrent applications. If maxlocks is set too
high, a few applications can consume most of the lock space, and other
applications will have to perform lock escalation. The need for lock
escalation in this case results in poor concurrency.

You may use the Database System Monitor to help you track and tune this
configuration parameter.

8.7.4 Configuring DB2/DB2 Data Links Manager/Data Links Access Token Expiry
Interval (dl_expint)

Contrary to the documentation, if dl_expint is set to "-1", the access
control token expires. The workaround for this is to set dl_expint to its
maximum value, 31536000 (seconds). This corresponds to an expiration time
of one year, which should be adequate for all applications.

8.7.5 MIN_DEC_DIV_3 Database Configuration Parameter

The addition of the MIN_DEC_DIV_3 database configuration parameter is
provided as a quick way to enable a change to computation of the scale for
decimal division in SQL. MIN_DEC_DIV_3 can be set to YES or NO. The default
value for MIN_DEC_DIV_3 is NO.

The MIN_DEC_DIV_3 database configuration parameter changes the resulting
scale of a decimal arithmetic operation involving division. If the value is
NO, the scale is calculated as 31-p+s-s'. Refer to the SQL Reference,
Chapter 3, "Decimal Arithmetic in SQL" for more information. If set to YES,
the scale is calculated as MAX(3, 31-p+s-s'). This causes the result of
decimal division to always have a scale of at least 3. Precision is always
31.

Changing this database configuration parameter may cause changes to
applications for existing databases. This can occur when the resulting
scale for decimal division would be impacted by changing this database
configuration parameter. Listed below are some possible scenarios that may
impact applications. These scenarios should be considered before changing
the MIN_DEC_DIV_3 on a database server with existing databases.

   * If the resulting scale of one of the view columns is changed, a view
     that is defined in an environment with one setting could fail with
     SQLCODE -344 when referenced after the database configuration
     parameter is changed. The message SQL0344N refers to recursive common
     table expressions, however, if the object name (first token) is a
     view, then you will need to drop the view and create it again to avoid
     this error.
   * A static package will not change behavior until the package is
     rebound, either implicitly or explicitly. For example, after changing
     the value from NO to YES, the additional scale digits may not be
     included in the results until rebind occurs. For any changed static
     packages, an explicit rebind command can be used to force a rebind.
   * A check constraint involving decimal division may restrict some values
     that were previously accepted. Such rows now violate the constraint
     but will not be detected until the one of the columns involved in the
     check constraint row is updated or the SET INTEGRITY command with the
     IMMEDIATE CHECKED option is processed. To force checking of such a
     constraint, perform an ALTER TABLE command in order to drop the check
     constraint and then perform an ALTER TABLE command to add the
     constraint again.

Note:
     DB2 Version 7 also has the following limitations:
       1. The command GET DB CFG FOR DBNAME will not display the
          MIN_DEC_DIV_3 setting. The best way to determine the current
          setting is to observe the side-effect of a decimal division
          result. For example, consider the following statement:

          VALUES (DEC(1,31,0)/DEC(1,31,5))

          If this statement returns sqlcode SQL0419N, then the database
          does not have MIN_DEC_DIV_3 support or it is set to OFF. If the
          statement returns 1.000, then MIN_DEC_DIV_3 is set to ON.
       2. MIN_DEC_DIV_3 does not appear in the list of configuration
          keywords when you run the following command: ? UPDATE DB CFG

8.7.6 Application Control Heap Size (app_ctl_heap_sz)

The text for this parameter should now read:

For partitioned databases and non-partitioned databases with
intra-parallelism enabled (intra_parallel=ON), this is the size of the
shared memory area allocated for the application control heap. For
non-partitioned databases where intra-parallelism is disabled
(intra_parallel=OFF), this is the maximum private memory that will be
allocated for the heap. There is one application control heap per
connection per partition.

The application control heap is required primarily for sharing information
between agents working on behalf of the same request, and, in a partitioned
database environment, for storing executable sections representing SQL
statements. Usage of this heap is minimal for non-partitioned databases
when running queries with a degree of parallelism less than or equal to 1.

This heap is also used to store descriptor information for declared
temporary tables. The descriptor information for all declared temporary
tables that have not been explicitly dropped is kept in this heap's memory
and cannot be dropped until the declared temporary table is dropped.

The "Recommendation" portion remains unchanged.

8.7.7 Database System Monitor Heap Size (mon_heap_sz)

The default for the OS/2 and Windows NT Database server with local and
remote clients and Satellite database server with local clients has changed
from 24 to 32. The range is unchanged.

8.7.8 Maximum Number of Active Applications (maxappls)

The upper range limit for all platforms has changed from 64 000 to 60 000.
The default value is unchanged.

8.7.9 Recovery Range and Soft Checkpoint Interval (softmax)

The unit of measure is changed to the percentage of the size of one primary
log file.

8.7.10 Track Modified Pages Enable (trackmod)

Configuration Type: Database

Parameter Type: Configurable

Default [Range]: Off [ On; Off ]

When this parameter is set to ON, the database manager will track which
pages in the database have changed since the most recent full backup was
taken. This allows the backup utility to determine which pages should be
included in an incremental backup without having to examine every page
individually. For SMS tablespaces, the granularity of this tracking is at
the tables pace level. For DMS table spaces, the granularity is at the
extent level for data and index pages and at the table space level for
other page types. After setting this parameter to ON, you must take a full
database backup in order to have a baseline against which incremental
backups can be taken.

8.7.11 Change the Database Log Path (newlogpath)

Configuration Type: Database

Parameter Type: Configurable

Default [Range]: Null [ any valid path or device]

Related Parameters: Location of Log Files (logpath); Database is Consistent
(database_consistent)

This parameter allows you to specify a string of up to 242 bytes to change
the location where the log files are stored. The string can point to either
a path name, or to a raw device. If the string points to a path name, it
must be a fully qualified path name, not a relative path name.

Note:
     In a partitioned database environment, the node number is
     automatically appended to the path. This is done to maintain the
     uniqueness of the path in multiple logical node configurations.

To specify a device, specify a string that the operating system identifies
as a device. For example, on Windows NT,

\\.\d: or \\.\PhysicalDisk5

Note:
     You must have Windows NT Version 4.0 with Service Pack 3 installed to
     be able to write logs to a device.

On UNIX-based platforms,

/dev/rdblog8

Note:
     You can only specify a device on AIX, Windows 2000, Windows NT,
     Solaris, HP-UX, NUMA-Q, and Linux platforms.

The new setting does not become the value of logpath until both of the
following occur:

   * The database is in a consistent state, as indicated by the
     database_consistent parameter.
   * All users are disconnected from the database.

When the first new connection is made to the database, the database manager
will move the logs to the new location specified by logpath.

There might be log files in the old log path. These log files might not
have been archived. You might need to archive these log files manually.
Also, if you are running replication on this database, replication might
still need the log files from before the log path change. If the database
is configured with the User Exit Enable (userexit) database configuration
parameter set to "Yes", and if all the log files have been archived either
by DB2 automatically or by yourself manually, then DB2 will be able to
retrieve the log files to complete the replication process. Otherwise, you
can copy the files from the old log path to the new log path.

Recommendation:
     Ideally, the log files will be on a physical disk which does not have
     high I/O. For instance, avoid putting the logs on the same disk as the
     operating system or high volume databases. This will allow for
     efficient logging activity with a minimum of overhead such as waiting
     for I/O.

You can use the database system monitor to track the number of I/Os related
to database logging.

For more information, refer to the following monitor element descriptions
in the System Monitor Guide and Reference:

   * log_reads (number of log pages read)
   * log_writes (number of log pages written)

The preceding data elements return the amount of I/O activity related to
database logging. You can use an operating system monitor tool to collect
information about other disk I/O activity, then compare the two types of
I/O activity.

8.7.12 Location of Log Files (logpath)

Configuration Type: Database

Parameter Type: Informational

Related Parameters: Change the Database Log Path (newlogpath)

This parameter contains the current path being used for logging purposes.
You cannot change this parameter directly as it is set by the database
manager after a change to the newlogpath parameter becomes effective. When
a database is created, the recovery log file for it is created in a
subdirectory of the directory containing the database. The default is a
subdirectory named SQLOGDIR under the directory created for the database.

8.7.13 Maximum Storage for Lock List (locklist)

The maximum value is increased from 60 000 to 524 288.
  ------------------------------------------------------------------------

8.8 Appendix A. DB2 Registry and Environment Variables

The following registry variables are new or require changes:

8.8.1 Table of New and Changed Registry Variables

Table 6. Registry Variables
 Variable Name                  Operating      Values
                                System
 Description
 DB2MAXFSCRSEARCH               All            Default=5

                                               Values: -1, 1 to 33554
 Specifies the number of free space control records to search when adding
 a record to a table. The default is to search five free space control
 records. Modifying this value allows you to balance insert speed with
 space reuse. Use large values to optimize for space reuse. Use small
 values to optimize for insert speed. Setting the value to -1 forces the
 database manager to search all free space control records.
 DLFM_TSM_MGMTCLASS             AIX, Windows   Default: the default TSM
                                NT, Solaris    management class

                                               Values: any valid TSM
                                               management class
 Specifies which TSM management class to use to archive and retrieve
 linked files. If there is no value set for this variable, the default TSM
 management class is used.
 DB2_CORRELATED_PREDICATES      All            Default=YES

                                               Values: YES or NO
 The default for this variable is YES. When there are unique indexes on
 correlated columns in a join, and this registry variable is YES, the
 optimizer attempts to detect and compensate for correlation of join
 predicates. When this registry variable is YES, the optimizer uses the
 KEYCARD information of unique index statistics to detect cases of
 correlation, and dynamically adjusts the combined selectivities of the
 correlated predicates, thus obtaining a more accurate estimate of the
 join size and cost.
 DB2_VI_DEVICE                  Windows NT     Default=null

                                               Values: nic0 or VINIC
 Specifies the symbolic name of the device or Virtual Interface Provider
 Instance associated with the Network Interface Card (NIC). Independent
 hardware vendors (IHVs) each produce their own NIC. Only one (1) NIC is
 allowed per Windows NT machine; Multiple logical nodes on the same
 physical machine will share the same NIC. The symbolic device name
 "VINIC" must be in upper case and can only be used with Synfinity
 Interconnect. All other currently supported implementations use "nic0" as
 the symbolic device name.
 DB2_SELECTIVITY                ALL            Default=NO

                                               Values: YES or NO
 This registry variable controls where the SELECTIVITY clause can be used.
 See the SQL Reference, Language Elements, Search Conditions for complete
 details on the SELECTIVITY clause.

 When this registry variable is set to YES, the SELECTIVITY clause can be
 specified when the predicate is a basic predicate where at least one
 expression contains host variables.
 DB2_UPDATE_PART_KEY            ALL            Default=YES

                                               Values: YES or NO
 For FixPak 3 and later, the default value is YES. This registry variable
 specifies whether or not update of the partitioning key is permitted.
 DB2_BLOCK_ON_LOG_DISK_FULL     ALL            Default=NO

                                               Values: YES or NO
 This DB2 registry variable can be set to prevent "disk full" errors from
 being generated when DB2 cannot create a new log file in the active log
 path.

 Instead, DB2 attempts to create the log file every 5 minutes until it
 succeeds. After each attempt, DB2 writes a message to the db2diag.log
 file. The only way that you can confirm that your application is hanging
 because of a log disk full condition is to monitor the db2diag.log file.

 Until the log file is successfully created, any user application that
 attempts to update table data will not be able to commit transactions.
 Read-only queries may not be directly affected; however, if a query needs
 to access data that is locked by an update request, or a data page that
 is fixed in the buffer pool by the updating application, read-only
 queries will also appear to hang.
 DB2_INDEX_2BYTEVARLEN          All            Default=NO

                                               Values: YES or NO
 This registry variable allows columns with a length greater than 255
 bytes to be specified as part of an index key. Indexes already created
 before turning this registry variable YES will continue to have the 255
 key limit restriction. Indexes created after turning this registry
 variable YES will behave as a two-byte index even when the registry
 variable is turned NO again.

 Several SQL statements are affected by changes to this registry variable
 including CREATE TABLE, CREATE INDEX, and ALTER TABLE. For more
 information on these statements, refer to the changes documented for the
 SQL Reference.
 DB2_FORCE_FCM_BP               AIX            Default=NO

                                               Values: YES or NO
 Specifies from where the fast communications manager (FCM) resources are
 allocated. The resources may be allocated from either the database
 manager shared memory segment or a separate one. With multiple logical
 nodes on the same machine, this registry variable should be used. On a
 partitioned database system with symmetric multi-processing (SMP)
 enabled, the setting of this registry variable has no effect on how
 communication takes place. In this case, communication is always through
 shared memory. However, it does affect the number of shared memory
 segments DB2 will use.
 DB2_AWE                        Windows 2000   Default=Null

                                               Values: <entry>[;
                                               <entry>;...] where
                                               <entry>=<buffer pool ID>,
                                               <number of physical pages>,
                                               <number of address windows>
 Allows DB2 UDB on Windows 2000 to allocate buffer pools that use up to 64
 GB of memory. Windows 2000 must be configured correctly to support
 Address Windowing Extensions (AWE) buffer pools. This includes
 associating the "lock pages in memory"-right with the user on Windows
 2000 and setting this registry variable on DB2. In setting this variable
 you need to know the buffer pool ID that is to be used for AWE support.
 You also need to determine the number of physical pages to allocate and
 the number of address windows.

 For information on determining the number of physical pages to allocate
 and the number of address windows, see the section on "Managing the
 Database Buffer Pool" found in "Chapter 8. Operational Performance"
 earlier in this section.

 Note:
      If AWE support is enabled, extended storage (ESTORE) cannot be used
      for any of the buffer pools in the database. The buffer pools
      referenced by this variable must already exist in
      SYSIBM.SYSBUFFERPOOLS.

 DB2_STPROC_LOCKUP_FIRST        All            Default=NO

                                               Values: YES or NO
 This registry variable has been renamed from DB2_DARI_LOOKUP_ALL.
 DB2MEMDISCLAIM                 AIX            Default=YES

                                               Values: YES or NO
 On AIX, memory used by DB2 processes may have some associated paging
 space. This paging space may remain reserved, even when the associated
 memory has been freed. The reservation of the paging space depends on the
 AIX system's tunable virtual memory management allocation policy. This
 registry variable controls whether DB2 agents explicitly request that AIX
 disassociate the reserved paging space from the freed memory.

 A setting of "YES" results in smaller paging space requirements, and
 possibly less disk activity from paging. A setting of "NO" results in
 greater paging space requirements, and possibly more disk activity from
 paging. In some situations, such as if paging space is plentiful, and if
 real memory is so plentiful that paging never occurs, then a setting of
 NO will provide a small performance improvement.
 DB2MEMMAXFREE                  All            Default=8 388 608 bytes

                                               Values: 0 to 232-1 bytes

 This registry variable controls the maximum amount of unused memory in
 bytes retained by DB2 processes.
 DB2_ANTIJOIN                   All            Default=NO in a EEE
                                               environment

                                               Default=YES in a non-EEE
                                               environment

                                               Values: YES or NO
 For DB2 Universal Database EEE environments: When YES is specified, the
 optimizer will search for opportunities to transform NOT EXISTS
 subqueries into anti-joins which can be processed more efficiently by
 DB2. For non-EEE environments: When NO is specified, the optimizer will
 limit the opportunities to transform NOT EXISTS subqueries into
 anti-joins.
 NEWLOGPATH2                    UNIX           Default=NO

                                               Values: YES or NO
 This parameter allows you to specify whether a secondary path should be
 used to implement dual logging. The path that will be used is generated
 by appending the character '2' to the current value of 'LOGPATH'.

 DB2DOMAINLIST                Windows NT     Default=Null

                                             Values: one or more valid
                                             Windows NT domains (comma
                                             separating each)
 Defines one or more Windows NT domains. Only users belonging to these
 domains will have their connection or attachment requests accepted.

 This registry variable should only be used under a pure Windows NT domain
 environment with DB2 servers and clients running DB2 Universal Database
 Version 7.1 (or later).
 DB2_LIKE_VARCHAR             All            Default=Y,N

                                             Values: Y, N, S, floating
                                             point constant between 0 and
                                             6.2
 Controls the collection and use of sub-element statistics. These are
 statistics about the content of data in columns when the data has a
 structure in the form of a series of sub-fields or sub-elements delimited
 by blanks.

 This registry variable affects how the optimizer deals with a predicate
 of the form:

    COLUMN LIKE '%xxxxxx%'

 where the xxxxxx is any string of characters.

 The syntax showing how this registry variable is used is:

    db2set DB2_LIKE_VARCHAR=[Y|N|S|num1] [,Y|N|S|num2]

 where

    * The term preceding the comma, or the only term to the right of the
      predicate, means the following but only for columns that do not have
      positive sub-element statistics:
         o S - The optimizer estimates the length of each element in a
           series of elements concatenated together to form a column based
           on the length of the string enclosed in the % characters.
         o Y - The default. Use a default value of 1.9 for the algorithm
           parameter. Use a variable-length sub-element algorithm with the
           algorithm parameter.
         o N - Use a fix-length sub-element algorithm.
         o num1 - Use the value of num1 as the algorithm parameter with
           the variable length sub-element algorithm.
    * The term following the comma means the following:
         o N - The default. Do not collect of use sub-element statistics.
         o Y - Collect sub-element statistics. Use a variable-length
           sub-element algorithm that uses the collected statistics
           together with the 1.9 default value for the algorithm parameter
           in the case of columns with positive sub-element statistics.
         o num2 - Collect sub-element statistics. Use a variable-length
           sub-element algorithm that uses the collected statistics
           together with the value of num2 as the algorithm parameter in
           the case of columns with positive sub-element statistics.
 DB2_PINNED_BP                AIX, HP-UX     Default=NO

                                             Values: YES or NO
 This variable is used to hold the database global memory (including
 buffer pools) associated with the database in the main memory on some AIX
 operating systems. Keeping this database global memory in the system main
 memory allows database performance to be more consistent.

 If, for example, the buffer pool was swapped out of the system main
 memory then database performance would deteriorate. The reduction of disk
 I/O by having the buffer pools in system memory improves database
 performance. If you have other applications that require more of the main
 memory, you will want to allow the database global memory, depending on
 the system main memory requirements, to be swapped out of main memory.

 When working with HP-UX in a 64-bit environment, in addition to modifying
 this registry variable, the DB2 instance group must be given the MLOCK
 privilege. This is done by having a user with root access rights do the
 following:

   1. Add the DB2 instance group to the /etc/privgroup file. For example,
      if the DB2 instance group belongs to db2iadm1 group then the
      following line must be added to the /etc/privgroup file:

      db2iadm1 MLOCK
   2. Issue the following command:

      setprivgrp -f /etc/privgroup
 DB2_RR_TO_RS                 All            Default=NO

                                             Values: YES or NO
 Next key locking guarantees Repeatable Read (RR) isolation level by
 automatically locking the next key for all INSERT and DELETE statements
 and the next higher key value above the result set for SELECT statements.
 For UPDATE statements that alter key parts of an index, the original
 index key is deleted and the new key value is inserted. Next key locking
 is done on both the key insertion and key deletion. Next key locking is
 required to guarantee ANSI and SQL92 standard RR, and is the DB2 default.

 If your application appears to stop or hang, you should examine snapshot
 information for your application. If the problem appears to be with next
 key locking, you can set the DB2_RR_TO_RS registry variable on based on
 two conditions. You can turn DB2_RR_TO_RS on if none of your applications
 rely on Repeatable Read (RR) behavior and if it is acceptable for scans
 to skip over uncommitted deletes. The skipping behavior affects the RR,
 Read Stability (RS), and Cursor Stability (CS) isolation levels. (There
 is no row locking for Uncommitted Read (UR) isolation level.)

 When DB2_RR_TO_RS is on, RR behavior cannot be guaranteed for scans on
 user tables because next key locking is not done during index key
 insertion and deletion. Catalog tables are not affected by this option.

 The other change in behavior is that with DB2_RR_TO_RS on, scans will
 skip over rows that have been deleted but not committed, even though the
 row may have qualified for the scan.
  ------------------------------------------------------------------------

8.9 Appendix C. SQL Explain Tools

The section titled "Running db2expln and dynexpln" should have the last
paragraph replaced with the following:

To run db2expln, you must have SELECT privilege to the system catalog views
as well as EXECUTE authority for the db2expln package. To run dynexpln, you
must have BINDADD authority for the database, the schema you are using to
connect to the database must exist or you must have the EXPLICIT_SCHEMA
authority for the database, and you must have any privileges needed for the
SQL statements being explained. (Note that if you have SYSADM or DBADM
authority, you will automatically have all these authorization levels.)
  ------------------------------------------------------------------------

Administering Satellites Guide and Reference(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

9.1 Setting up Version 7.2 DB2 Personal Edition and DB2 Workgroup Edition
as Satellites

The sections that follow describe how to set up Windows-based Version 7.2
DB2 Personal Edition and DB2 Workgroup Edition systems so that they can be
used as fully functional satellites in a satellite environment. For
information about the terms and concepts used in the information that
follows, refer to the Administering Satellites Guide and Reference. You can
find this book at the following URL:

  http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/v6pubs.d2w/en_main

For Technotes that supplement the information in the Administering
Satellites Guide and Reference, refer to the following URL:

  http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/browse.d2w/
  report?type=tech5udb&tech5udb=Y

9.1.1 Prerequisites

To set up either DB2 Personal Edition or DB2 Workgroup Edition as
satellites, you require the following:

  1. A DB2 control server

     The DB2 control server is a DB2 Enterprise Edition system that runs on
     Windows NT or AIX, and has the Control Server component installed. The
     DB2 Enterprise Edition system that you use must be at Version 6 with
     FixPak 2 or higher, or Version 7 at any FixPak level.
        o If you have a Version 6 Enterprise Edition system that you want
          to use as the DB2 control server, see 9.1.3, Installing FixPak 2
          or Higher on a Version 6 Enterprise Edition System.
        o If you are using Version 7 and do not have the Control Server
          component installed, install this component, re-install any
          FixPaks that you have already installed, then create the DB2
          control server instance and satellite control database. Refer to
          the Administering Satellites Guide and Reference for instructions
          on creating these objects.

     Note:
          If you are installing a Version 7.2 Enterprise Edition system on
          Windows NT for use as the DB2 control server, and you want to
          perform a response file installation, see the Technote entitled
          DB2 Control Server Response File Keywords for information about
          the keywords to specify in the response file.
  2. The DB2 control server instance and the satellite control database

     The DB2 control server instance is typically called DB2CTLSV, and the
     satellite control database is called SATCTLDB. The DB2 control server
     instance and the satellite control database are on the Enterprise
     Edition system, and, on Windows NT, are automatically created when you
     install DB2 with the Control Server component. If you install DB2 on
     AIX, see the Administering Satellites Guide and Reference for
     information about creating the DB2 control server instance and the
     satellite control database.
  3. The Satellite Administration Center

     The Satellite Administration Center is the set of GUI tools that you
     use to set up and administer the satellite environment. You access
     this set of tools from the DB2 Control Center. For more information
     about Satellite Administration Center and the satellite environment,
     see the Administering Satellites Guide and Reference, and the online
     help that is available from the Satellite Administration Center. If
     you are running a Version 6 DB2 Control Center, see 9.1.4, Upgrading a
     Version 6 DB2 Control Center and Satellite Administration Center.

     If you have not already used the Satellite Administration Center to
     set up the satellite environment and to create the object that
     represents the new satellite in the Satellite Administration Center,
     you should do so before installing the satellite. For more
     information, see the description of how to set up and test a satellite
     environment in the Administering Satellites Guide and Reference.
  4. A Version 7.2 Personal Edition or Workgroup Edition system that you
     want to use as a satellite.

9.1.1.1 Installation Considerations

When you install either DB2 Personal Edition or DB2 Workgroup Edition, you
do not have to select any special component to enable either system to
synchronize. If you intend to perform a response file installation, see
Performing a Response File Installation for the keywords that you should
specify when installing the Version 7.2 system. If you are performing an
interactive installation of your Version 7.2 system, see 9.1.2, Configuring
the Version 7.2 System for Synchronization after you finish installing DB2
for values that you must set at the Version 7.2 system to enable it to
synchronize.

Performing a Response File Installation

If you are performing a response file installation of Version 7.2 DB2
Personal Edition or DB2 Workgroup Edition, you can set the following
keywords in the response file.

If you decide to not specify one or more of these keywords during the
response file installation, see 9.1.2, Configuring the Version 7.2 System
for Synchronization for additional steps that you must perform after
installing DB2 to enable the Version 7.2 system to synchronize. You can
also use the instructions in this section if you want to change any values
that were specified during the response file installation.

db2.db2satelliteid
     Sets the satellite ID on the system.
     Note:
          If you do not specify this keyword, the satellite ID is
          automatically set to the user ID that was used to install DB2. If
          you want to use this user ID as the satellite ID, you do not have
          to specify a value for this keyword.

db2.db2satelliteappver
     Sets the application version on the system.
     Note:
          If you do not specify this keyword, the application version on
          the satellite is automatically set to V1R0M00. If you want to use
          this value as the application version, you do not have to specify
          a value for this keyword.

db2.satctldb_username
     Sets the user name to be used for the system to connect to the
     satellite control database.

db2.satctldb_password
     Sets the password that the user name passes to the DB2 control server
     when the user name connects to the satellite control database.

After you complete the response file installation, the Version 7.2 system
is ready to synchronize. You should issue the db2sync -t command on the
satellite to verify that the values specified on the satellite are correct,
and that the satellite can connect to the satellite control database.

For additional information about performing a response file installation,
refer to the Administering Satellites Guide and Reference.

Note:

  1. In Version 7, user IDs and passwords are required for the creation of
     all services on Windows NT and Windows 2000. These user IDs and
     passwords are specified in the response file by keyword pairs. The
     first keyword pair found in the response file becomes the default user
     ID and password for all services, unless you provide an override for a
     service by specifying the specific keyword pair for that service.

     In Version 6, the admin.userid and the admin.password keywords could
     be specified during a response file installation of DB2 Satellite
     Edition to specify the user ID and password that would be used by the
     Remote Command Service. For Version 7.2 Personal Edition and Workgroup
     Edition, if you specify these keywords, they are used for the DB2DAS00
     instance on the Version 7.2 system. For a DB2 Version 7.2 system, the
     Remote Command Service will use the user ID and password that is used
     by the DB2 instance on the system. If you do not specify values for
     db2.userid and db2.password, the defaulting rule described above
     applies.

  2. In Version 6, you could create a database when installing DB2
     Satellite Edition using a response file installation. You cannot
     create a database during a response file installation on the Version
     7.2 Personal Edition or Workgroup Edition system that you intend to
     use as a satellite. The following keywords (which are described in the
     Administering Satellites Guide and Reference), are not supported:
        o db2.userdb_name
        o db2.userdb_recoverable
        o db2.userdb_rep_src

9.1.2 Configuring the Version 7.2 System for Synchronization

If you install the Version 7.2 system interactively, several values must be
set on the DB2 Personal Edition or DB2 Workgroup Edition system after
installing DB2 before the system can synchronize.

Note:
     You can use execute an operating system script on the system to set
     all values at the satellite except for the user ID and password that
     the satellite uses to connect to the satellite control database (see
     step 4).

  1. Set the satellite ID by using the db2set command.

     If you install DB2 Personal Edition or DB2 Workgroup Edition
     interactively, the satellite ID is automatically set to the user ID
     that was used to install DB2. If you want to use this user ID as the
     satellite ID, you do not have to perform this step. For information
     about setting the satellite ID, see the Administering Satellites Guide
     and Reference.
  2. Set the application version on the satellite by using the db2sync -s
     command.

     If you install DB2 Personal Edition or DB2 Workgroup Edition
     interactively, the application version on the satellite is
     automatically set to V1R0M00. If you want to use this value as the
     application version, you do not have to perform this step.

     You can use the db2sync -g command on the satellite to view the
     current setting of the application version. If you want to change this
     value, issue the db2sync -s command. You are prompted to provide a new
     value for the application version. For more information about setting
     the application version, see the Administering Satellites Guide and
     Reference.
  3. Issue the catalog node and catalog database commands on the satellite
     to catalog the DB2 control server instance and the satellite control
     database, SATCTLDB, at the satellite.

     You can also use the db2sync -t command on the satellite to open the
     DB2 Synchronizer application in test mode. If the SATCTLDB database is
     not cataloged at the satellite when you issue the command, the Catalog
     Control Database window opens. You can either use the DB2 discovery
     feature that is available from the Catalog Control Database window to
     catalog the DB2 control server and the SATCTLDB database, or you can
     type the hostname and server name in this window. You will also be
     prompted to specify the user ID and password that the satellite will
     use to connect to the satellite control database, as described in step
     4.
     Note:
          After you install Version 7.2 DB2 Personal Edition or DB2
          Workgroup Edition interactively, the DB2 Synchronizer does not
          start automatically in test mode (as was the case for Version 6
          DB2 Satellite Edition).
  4. Issue the db2sync -t command on the satellite to:
        o Specify the user ID and the password that the satellite will use
          to connect to the satellite control database

          If synchronization credentials are not already stored at the
          satellite, the Connect to Control Database window opens. You must
          use this window to specify the user ID and password the satellite
          will use to connect to the satellite control database.
        o Verify the values that are set on the satellite are correct
        o Verify that the satellite can connect to the satellite control
          database

After you complete these configuration tasks, the Version 7.2 system is
ready to synchronize.

9.1.3 Installing FixPak 2 or Higher on a Version 6 Enterprise Edition
System

The sections that follow describe the tasks that you must perform to
upgrade a Version 6 Enterprise Edition system on Windows NT or AIX for use
as a DB2 control server. If you are using a Version 6 DB2 Control Center,
also perform the steps in 9.1.4, Upgrading a Version 6 DB2 Control Center
and Satellite Administration Center to verify that you have the correct
level of the DB2 Control Center and the Satellite Administration Center to
administer the satellite environment.

9.1.3.1 Upgrading Version 6 DB2 Enterprise Edition for Use as the DB2
Control Server

For a Version 6 DB2 Enterprise Edition system to be used as the DB2 control
server, it must be installed with the Control Server component, and DB2
Enterprise Edition should be at the FixPak 2 service level, or higher.
Depending on whether the DB2 control server component is installed, and the
service level of DB2 Enterprise Edition, you will have to perform one of
the following tasks:

   * Install the DB2 control server component to an existing DB2 Enterprise
     Edition V6.1 system and install FixPak 2 or higher. Then update the
     satellite control database (SATCTLDB) on the system.
   * Upgrade an already installed DB2 control server to the FixPak 2 level
     or higher.

Use the information that follows to identify which of the two preceding
tasks you need to perform, and the steps that apply to your situation. The
following is a summary of the steps that you will perform.

  1. First, assess the current state of your DB2 Enterprise Edition
     installation. You will determine whether the Control Server component
     is installed, and the service level of DB2.
  2. Second, based on the state information that you obtain, you will
     determine what needs to be done.
  3. Third, you will perform the necessary steps to upgrade DB2 Enterprise
     Edition.

The DB2 control server can only run on DB2 Enterprise Edition for Windows
NT and AIX. Continue with the instructions that are appropriate for your
platform:

   * Upgrading DB2 Enterprise Edition on Windows NT
   * Upgrading DB2 Enterprise Edition on AIX

Upgrading DB2 Enterprise Edition on Windows NT

Use the information in the sections that follow to determine the current
service level of your Version 6 DB2 Enterprise Edition system, and the
steps that you need to perform to update the system to the FixPak 2 service
level or higher. You will need to perform the steps of one or more of the
following sections:

   * Assessing DB2 Enterprise Edition on Windows NT
   * Determining What Needs to Be Done
   * Installing the Control Server Component on Windows NT
   * Installing FixPak 2 or Higher on Windows NT
   * Upgrading the SATCTLDB on Windows NT

Assessing DB2 Enterprise Edition on Windows NT

If you have DB2 Enterprise Edition installed on Windows NT, perform the
following steps:

  1. Check whether the Control Server component is installed. Use the
     Registry Editor to display the list of installed components:
       a. Enter regedit at a command prompt.
       b. Under the HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\Components registry
          key, check whether the Control Server is listed. If it is not
          listed, the control server is not installed.
  2. Determine the service level of DB2 Enterprise Edition. Issue the
     db2level command from a command prompt. Use the table that follows to
     interpret the output:

      Values of Key Fields in the db2level output           Your DB2
      Release         Level        Informational Tokens     system is at:

      SQL06010        01010104     db2_v6, n990616          Version 6.1
                                                            base
      SQL06010        01020104     DB2 V6.1.0.1, n990824,   Version 6.1
                                   WR21136                  plus FixPak 1
      SQL06010        01030104     DB2 V6.1.0.6, s991030,   Version 6.1
                                   WR21163 or DB2 V6.1.0.9, plus FixPak 2
                                   s000101, WR21173

     Note:
          If the level is greater than 01030104, your system is at a higher
          FixPak than FixPak 2.
  3. Record the information that you find, and continue at Determining What
     Needs to Be Done.

Determining What Needs to Be Done

Using the information that you have gathered, find the row in the following
table that applies to your situation, and follow the steps that are
required to prepare your DB2 Enterprise Edition system to support the DB2
control server at the FixPak 2 level or higher.

Sections that follow the table provide instructions for performing the
required steps. Consider checking off each step as you perform it. Only
perform the steps that apply to your situation.

 Control Server          Service Level of DB2     Steps required to
 Component Installed     Enterprise Edition       prepare your DB2
                         System                   Enterprise Edition
                                                  system
 No                      Version 6.1 base, or     Perform the following
                         Version 6.1 plus FixPak  steps:
                         1, or Version 6.1 plus
                         FixPak 2 or higher         1. Installing the
                                                       Control Server
                                                       Component on
                                                       Windows NT
                                                    2. Installing FixPak 2
                                                       or Higher on
                                                       Windows NT
                                                    3. Upgrading the
                                                       SATCTLDB on Windows
                                                       NT
 Yes                     Version 6.1 base, or     Perform the following
                         Version 6.1 plus FixPak  steps:
                         1
                                                    1. Installing FixPak 2
                                                       or Higher on
                                                       Windows NT
                                                    2. Upgrading the
                                                       SATCTLDB on Windows
                                                       NT
 Yes                     Version 6.1, plus FixPak Perform the following
                         2 or higher              step:

                                                    1. Upgrading the
                                                       SATCTLDB on Windows
                                                       NT

Installing the Control Server Component on Windows NT

To install the Control Server component on Windows NT:

  1. Ensure that all database activity on the system is complete before
     proceeding.
  2. Insert the DB2 Universal Database Enterprise Edition Version 6.1 CD in
     the CD drive.

     If the installation program does not start automatically, run the
     setup command in the root of the CD to start the installation process.
  3. When prompted, shut down all the processes that are using DB2.
  4. On the Welcome window, select Next.
  5. On the Select Products window, ensure that DB2 Enterprise Edition is
     selected.
  6. On the Select Installation Type panel, click Custom.
  7. On the Select Components panel, ensure that the Control Server
     component is selected, and click Next.
     Note:
          If you select other components that are not already installed on
          your system, these components will be installed too. You cannot
          alter the drive or directory in which DB2 is installed.
  8. On the Configure DB2 Services panels, you can modify the protocol
     values and the start-up options for the Control Server instance, or
     take the default values. Either modify the defaults and click Next, or
     click Next to use the defaults.
  9. Click Next on the Start Copy files window to begin the installation
     process.
 10. When the file copying process is complete, you have the option of
     rebooting your system. You should reboot now. The changes made to the
     system for the Control Server do not take effect until the system is
     rebooted.

When the installation process is complete and you have rebooted the system,
the satellite control database (SATCTLDB) that was created as part of the
Control Server installation must be cataloged in the DB2 instance if you
want to use the DB2 Control Center and Satellite Administration Center
locally on the system. To catalog the SATCTLDB database:

  1. Open a DB2 Command Window by selecting Start>Programs>DB2 for Windows
     NT>Command Window
  2. Ensure that you are in the db2 instance.

     Issue the set command and check the value of db2instance. If the value
     is not db2, issue the following command:

        set db2instance=db2

  3. Catalog the db2ctlsv instance by entering the following command:

        db2 catalog local node db2ctlsv instance db2ctlsv

  4. Catalog the SATCTLDB database by entering the following command

        db2 catalog database satctldb at node db2ctlsv

  5. Commit the cataloging actions by entering the following command:

        db2 terminate

  6. Close the DB2 Command Window.

Installing FixPak 2 or Higher on Windows NT

To upgrade an existing Version 6 DB2 Enterprise Edition system on Windows
NT to FixPak 2 or higher, either:

   * Download the latest FixPak for DB2 Enterprise Edition for Windows NT
     V6.1 from the Web, along with its accompanying readme. The FixPak can
     be downloaded by following the instructions at URL:

     http://www-4.ibm.com/software/data/db2/db2tech/version61.html

     Install the FixPak following the instructions in the readme.txt file.
   * Use a DB2 Universal Database, Version 6.1 FixPak for Windows NT CD
     that is at FixPak 2 level or higher, and follow the instructions in
     the readme.txt file in the WINNT95 directory on the CD to complete the
     installation.

Upgrading the SATCTLDB on Windows NT

To upgrade the SATCTLDB database on Windows NT

  1. Determine the level of the SATCTLDB database:
       a. Log on with a user ID that has local administrative authority on
          the Windows NT system.
       b. Open a DB2 Command Window by selecting Start>Programs>DB2 for
          Windows NT>Command Window.
       c. Connect to the SATCTLDB by entering the following command

             db2 connect to satctldb

       d. Determine if the trigger I_BATCHSTEP_TRGSCR exists in the
          database by issuing the following query:

             db2 select name from sysibm.systriggers where name='I_BATCHSTEP_TRGSCR'

          Record the number of rows that are returned.
       e. Enter the following command to close the connection to the
          database:

             db2 connect reset

          If step 1d returned one row, the database is at the correct
          level. In this situation, skip step 2, and continue at step 3. If
          zero (0) rows are returned, the database is not at the correct
          level, and must be upgraded, as described in step 2, before you
          can perform step 3.
  2. To upgrade the SATCTLDB database, perform the following steps. Enter
     all commands in the DB2 Command Window:
       a. Switch to the directory <db2path>\misc, where <db2path> is the
          install drive and path, for example c:\sqllib.
       b. Ensure that you are in the db2ctlsv instance.

          Issue the set command and check the value of db2instance. If the
          value is not db2ctlsv, issue the following command:

             set db2instance=db2ctlsv

       c. Drop the SATCTLDB database by entering the following command:

             db2 drop database satctldb

       d. Create the new SATCTLDB database by entering the following
          command:

             db2 -tf satctldb.ddl  -z satctldb.log

       e. Issue the following command:

             db2 terminate

  3. Bind the db2satcs.dll stored procedure to the SATCTLDB database.
     Perform the following steps:
       a. Connect to the SATCTLDB database by entering the following
          command

             db2 connect to satctldb

       b. Switch to the directory <db2path>\bnd, where <db2path> is the
          install drive and path, for example c:\sqllib.
       c. Issue the bind command, as follows:

             db2 bind db2satcs.bnd

  4. Enter the following command to close the connection to the database:

        db2 connect reset

  5. Close the DB2 Command Window.

Upgrading DB2 Enterprise Edition on AIX

Use the information in the sections that follow to determine the current
service level of your Version 6 DB2 Enterprise Edition system, and the
steps that you need to perform to update the system to the FixPak 2 service
level, or higher. You will need to perform the steps of one or more of the
following sections:

   * Assessing DB2 Enterprise Edition on AIX
   * Determining What Needs to Be Done
   * Installing the Control Server Component on AIX
   * Installing FixPak 2 or Higher on AIX
   * Upgrading the SATCTLDB Database on AIX

Assessing DB2 Enterprise Edition on AIX

If you have Version 6 DB2 Enterprise Edition installed on AIX, perform the
following steps:

  1. Check whether the Control Server component is installed. Enter the
     following command:

        lslpp -l | grep db2_06_01.ctsr

     If no data is returned, the Control Server component is not installed.
  2. Determine the service level of the DB2 Enterprise Edition. Log on as a
     DB2 instance owner, and issue the db2level command. Use the table that
     follows to interpret the output:

      Values of Key Fields in the db2level output           Your DB2
      Release         Level        Informational Tokens     system is at:

      SQL06010        01010104     db2_v6, n990616          Version 6.1
                                                            base
      SQL06010        01020104     DB2 V6.1.0.1, n990824,   Version 6.1
                                   U465423                  plus FixPak 1
      SQL06010        01030104     DB2 V6.1.0.6, s991030,   Version 6.1
                                   U468276 or DB2 V6.1.0.9, plus FixPak 2
                                   s000101, U469453

     Note:
          If the level is greater than 01030104, your system is at a higher
          FixPak than FixPak 2.
  3. Record the information that you find, and continue at Determining What
     Needs to Be Done.

Determining What Needs to Be Done

Using the information that you have gathered, find the row in the following
table that applies to your situation, and follow the steps that are
required to prepare your Version 6 DB2 Enterprise Edition system to support
the DB2 control server at the FixPak 2 level.

Sections that follow the table provide instructions for performing the
required steps. Consider checking off each step as you perform it. Only
perform the steps that apply to your situation.

 Control Server          Service Level of DB2     Steps required to
 Component Installed     Enterprise Edition       prepare your DB2
                         System                   Enterprise Edition
                                                  system
 No                      Version 6.1 base, or     Perform the following
                         Version 6.1 plus FixPak  steps:
                         1, or Version 6.1 plus
                         FixPak 2 or higher         1. Installing the
                                                       Control Server
                                                       Component on AIX
                                                    2. Installing FixPak 2
                                                       or Higher on AIX
                                                    3. Upgrading the
                                                       SATCTLDB Database
                                                       on AIX
 Yes                     Version 6.1 base, or     Perform the following
                         Version 6.1 plus FixPak  steps:
                         1
                                                    1. Installing FixPak 2
                                                       or Higher on AIX
                                                    2. Upgrading the
                                                       SATCTLDB Database
                                                       on AIX
 Yes                     Version 6.1, plus FixPak Perform the following
                         2 or higher              step:

                                                    1. Upgrading the
                                                       SATCTLDB Database
                                                       on AIX

Installing the Control Server Component on AIX

To install the Control Server component on AIX

  1. Log on as a user with root authority.
  2. Insert the DB2 Universal Database Enterprise Edition Version 6.1 CD in
     the CD drive.
  3. Change to the directory where the CD is mounted, for example, cd
     /cdrom.
  4. Type the following command to start the DB2 installer:

        ./db2setup

  5. When the DB2 Installer window opens, use the tab key to select the
     Install option, and press Enter.
  6. Locate the Enterprise Edition line and use the tab key to select the
     Customize option beside it. Press Enter.
  7. Select the DB2 Control Server component, tab to OK, and press Enter.
  8. Follow the instructions on the remaining windows to complete the
     installation of the DB2 Control Server component.

When the installation process is complete, create the DB2CTLSV instance and
the SATCTLDB database. To perform these tasks, follow the detailed
instructions in "Setting up the DB2 Control Server on AIX" in Chapter 13 of
the Administering Satellites Guide and Reference.

Installing FixPak 2 or Higher on AIX

To upgrade an existing DB2 Enterprise Edition system AIX to FixPak 2 or
higher, either:

   * Download the latest FixPak for DB2 Enterprise Edition for AIX V6.1
     from the Web, along with its accompanying Fixpak.Readme. The FixPak
     can be downloaded by following the instructions at URL:

     http://www-4.ibm.com/software/data/db2/db2tech/version61.html

     Install the FixPak following the instructions in the Fixpak.Readme
     file.
   * Use a DB2 Universal Database, Version 6.1 FixPak for AIX CD that is at
     FixPak 2 level or higher, and follow the instructions in the readme
     directory on the CD to complete the installation.

Ensure that you have updated the DB2CTLSV instance by running the db2iupdt
command as instructed in the FixPak.Readme file.

Upgrading the SATCTLDB Database on AIX

To upgrade the SATCTLDB database on AIX:

  1. Determine the level of the SATCTLDB database:
       a. Log in as db2ctlsv.
       b. Ensure that the database server has been started. If the server
          is not started, issue the db2start command.
       c. Connect to the SATCTLDB database by entering the following
          command:

             db2 connect to satctldb

       d. Determine if the trigger I_BATCHSTEP_TRGSCR exists in the
          database by issuing the following query:

             db2 "select name from sysibm.systriggers where name='I_BATCHSTEP_TRGSCR'"

          Record the number of rows that are returned.
       e. Enter the following command to close the connection to the
          database:

             db2 connect reset

          If step 1d returned one row, the database is at the correct
          level. In this situation, skip step 2, and continue at step 3. If
          zero (0) rows are returned, the database is not at the correct
          level, and must be upgraded, as described in step 2, before you
          can perform step 3.
  2. To upgrade the SATCTLDB database to the FixPak 2 level, perform the
     following steps. Enter all commands in the DB2 Command Window:
       a. Switch to the $HOME/sqllib/misc directory.
       b. Drop the SATCTLDB database by entering the following command:

             db2 drop database satctldb

       c. Create the new SATCTLDB database by entering the following
          command:

             db2 -tf satctldb.ddl  -z $HOME/satctldb.log

       d. Issue the following command:

             db2 terminate

  3. Bind the db2satcs.dll stored procedure to the SATCTLDB database.
     Perform the following steps:
       a. Connect to the SATCTLDB database by entering the following
          command

             db2 connect to satctldb

       b. Switch to the directory $HOME/sqllib/bnd.
       c. Issue the bind command, as follows:

             db2 bind db2satcs.bnd

  4. Enter the following command to close the connection to the database:

        db2 connect reset

9.1.4 Upgrading a Version 6 DB2 Control Center and Satellite Administration
Center

To use a Version 6 DB2 Control Center and Satellite Administration Center
with a Version 6 DB2 control server and satellite control database
(SATCTLDB) that have been upgraded to FixPak 2 or higher, the tools must
also be upgraded to FixPak 2 or higher.

If the DB2 Control Center and Satellite Administration Center are running
on the same system as the DB2 control server, they were upgraded when the
DB2 Enterprise Edition system was upgraded to FixPak 2. However, if you run
these tools on another system, you must upgrade this system to the FixPak 2
level or higher.

To upgrade this system to FixPak 2 or higher:

   * Download the latest FixPak for your product at the V6.1 level from the
     Web, along with its accompanying readme. FixPaks can be downloaded by
     following the instructions at URL:

       http://www-4.ibm.com/software/data/db2/db2tech/version61.html

     Install the FixPak following the instructions in the readme file.
   * Use a DB2 Universal Database, Version 6.1 FixPak CD for the operating
     system that you are running that is at FixPak 2 level or higher, and
     follow the instructions in the readme to complete the installation.

  ------------------------------------------------------------------------

Command Reference(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

10.1 db2batch - Benchmark Tool

The last sentence in the description of the PERF_DETAIL parameter should
read:

   A value greater than 1 is only valid on DB2 Version 2 and DB2 UDB servers,
   and is not currently supported on host machines.

  ------------------------------------------------------------------------

10.2 db2cap (new command)

db2cap - CLI/ODBC Static Package Binding Tool

Binds a capture file to generate one or more static packages. A capture
file is generated during a static profiling session of a CLI/ODBC/JDBC
application, and contains SQL statements that were captured during the
application run. This utility processes the capture file so that it can be
used by the CLI/ODBC/JDBC driver to execute static SQL for the application.

For more information on how to use static SQL in CLI/ODBC/JDBC
applications, see the Static Profiling feature in the CLI Guide and
Reference.

Authorization

   * Access privileges to any database objects referenced by SQL statements
     recorded in the capture file.
   * Sufficient authority to set bind options such as OWNER and QUALIFIER
     if they are different from the connect ID used to invoke the db2cap
     command.
   * BINDADD authority if the package is being bound for the first time;
     otherwise, BIND authority is required.

Command Syntax

>>-db2cap----+----+--bind--capture-file----d--database_alias---->
             +--h-+
             '--?-'

>-----+--------------------------------+-----------------------><
      '--u--userid--+---------------+--'
                    '--p--password--'


Command Parameters

-h/-?
     Displays help text for the command syntax.

bind capture-file
     Binds the statements from the capture file and creates one or more
     packages.

-d database_alias
     Specifies the database alias for the database that will contain one or
     more packages.

-u userid
     Specifies the user ID to be used to connect to the data source.

     Note:
          If a user ID is not specified, a trusted authorization ID is
          obtained from the system.

-p password
     Specifies the password to be used to connect to the data source.

Usage Notes

The command must be entered in lowercase on UNIX platforms, but can be
entered in either lowercase or uppercase on Windows operating systems and
OS/2.

This utility supports a number of user-specified bind options that can be
found in the capture file. For performance and security reasons, the file
can be examined and edited with a text editor to change these options.

The SQLERROR(CONTINUE) and the VALIDATE(RUN) bind options can be used to
create a package.

When using this utility to create a package, static profiling must be
disabled.

The number of packages created depends on the isolation levels used for the
SQL statements that are recorded in the capture file. The package name
consists of up to a maximum of the first seven characters of the package
keyword from the capture file, and one of the following single-character
suffixes:

   * 0 - Uncommitted Read (UR)
   * 1 - Cursor Stability (CS)
   * 2 - Read Stability (RS)
   * 3 - Repeatable Read (RR)
   * 4 - No Commit (NC)

To obtain specific information about packages, the user can:

   * Query the appropriate SYSIBM catalog tables using the COLLECTION and
     PACKAGE keywords found in the capture file.
   * View the capture file.

  ------------------------------------------------------------------------

10.3 db2ckrst (new command)

db2ckrst - Check Incremental Restore Image Sequence

Queries the database history and generates a list of timestamps for the
backup images required for an incremental restore. A simplified restore
syntax for a manual incremental restore is also generated.

Authorization

None

Required Connection

None

Command Syntax

>>-db2ckrst----d--database name----t--timestamp----------------->

>-----+---------------------+---+-----------------------------+->
      |     .-database---.  |   |     .--------------------.  |
      '--r--+-tablespace-+--'   |     V                    |  |
                                '--n-----tablespace name---+--'

>-----+----+---------------------------------------------------><
      +--h-+
      +--u-+
      '--?-'


Command Parameters

-d database namefile-name
     Specifies the alias name for the database that will be restored.

-t timestamp
     Specifies the timestamp for a backup image that will be incrementally
     restored.

-r
     Specifies the type of restore that will be executed. The default is
     database.

     Note:
          If tablespace is chosen and no table space names are given, the
          utility looks into the history entry of the specified image and
          uses the table space names listed to do the restore.

-n tablespace name
     Specifies the name of one or more table spaces that will be restored.

     Note:
          If a database restore type is selected and a list of table space
          names is specified, the utility will continue as a tablespace
          restore using the table space names given.

-h/-u/-?
     Displays help information. When this option is specified, all other
     options are ignored, and only the help information is displayed.

Examples

db2ckrst -d mr -t 20001015193455 -r database
db2ckrst -d mr -t 20001015193455 -r tablespace
db2ckrst -d mr -t 20001015193455 -r tablespace -n tbsp1 tbsp2

> db2 backup db mr

Backup successful. The timestamp for this backup image is : 20001016001426

> db2 backup db mr incremental

Backup successful. The timestamp for this backup image is : 20001016001445

> db2ckrst -d mr -t 20001016001445

Suggested restore order of images using timestamp 20001016001445 for database mr.
===================================================================
  db2 restore db mr incremental taken at 20001016001445
  db2 restore db mr incremental taken at 20001016001426
  db2 restore db mr incremental taken at 20001016001445
===================================================================

> db2ckrst -d mr -t 20001016001445 -r tablespace -n userspace1
Suggested restore order of images using timestamp 20001016001445 for database mr.
===================================================================
  db2 restore db mr tablespace ( USERSPACE1 ) incremental taken at 20001016001445
  db2 restore db mr tablespace ( USERSPACE1 ) incremental taken at 20001016001426
  db2 restore db mr tablespace ( USERSPACE1 ) incremental taken at 20001016001445
===================================================================

Usage Notes

The database history must exist in order for this utility to be used. If
the database history does not exist, specify the HISTORY FILE option in the
RESTORE command before using this utility.

If the FORCE option of the PRUNE HISTORY command is used, it will be
possible to delete entries that are required for recovery from the most
recent, full database backup image. The default operation of the PRUNE
HISTORY command prevents required entries from being deleted. It is
recommended that the FORCE option of the PRUNE HISTORY command not be used.

It is recommended that you keep good records of your backups and use this
utility as a guide.
  ------------------------------------------------------------------------

10.4 db2gncol (new command)

db2gncol - Update Generated Column Values

Updates generated columns in tables that are in check pending mode and have
limited log space. This tool is used to prepare for a SET INTEGRITY
statement on a table that has columns which are generated by expressions.

Authorization

One of the following

   * sysadm
   * dbadm

Command Syntax

>>-db2gncol----d--database----s--schema_name----t--table_name--->

>-----c--commit_count----+---------------------------+---------->
                         '--u--userid---p--password--'

>-----+-----+--------------------------------------------------><
      '--h--'


Command Parameters

-d database
     Specifies an alias name for the database in which the table is
     located.

-s schema_name
     Specifies the schema name for the table. The schema name is case
     sensitive.

-t table_name
     Specifies the table for which new column values generated by
     expressions are to be computed. The table name is case sensitive.

-c commit_count
     Specifies the number of rows updated between commits. This parameter
     influences the size of the log space required to generate the column
     values.

-u userid
     Specifies a user ID with system administrator or database
     administrator privileges. If this option is omitted, the current user
     is assumed.

-p password
     Specifies the password for the specified user ID.

-h
     Displays help information. When this option is specified, all other
     options are ignored, and only the help information is displayed.

Usage Notes

Using this tool instead of the FORCE GENERATED option on the SET INTEGRITY
statement may be necessary if a table is large and the following conditions
exist:

   * All column values must be regenerated after altering the generation
     expression of a generated column.
   * An external UDF used in a generated column was changed, causing many
     column values to change.
   * A generated column was added to the table.
   * A large load or load append was performed that did not provide values
     for the generated columns.
   * The log space is too small due to long-running concurrent transactions
     or the size of the table.

This tool will regenerate all column values that were created based on
expressions. While the table is being updated, intermittent commits are
performed to avoid using up all of the log space. Once db2gncol has been
run, the table can be taken out of check pending mode using the SET
INTEGRITY statement.
  ------------------------------------------------------------------------

10.5 db2inidb - Initialize a Mirrored Database

In a split mirror environment, this command is used to initialize a
mirrored database for different purposes.

Authorization
     Must be one of the following:
        o sysadm
        o sysctrl
        o sysmaint

Required Connection
     None

Command Syntax

     >>-db2inidb----database_alias----AS----+-SNAPSHOT-+------------><
                                            +-STANDBY--+
                                            '-MIRROR---'


     Command Parameters

     database_alias
          Specifies the alias of the database to be initialized.

     SNAPSHOT
          Specifies that the mirrored database will be initialized as a
          clone of the primary database. This database is read only.

     STANDBY
          Specifies that the database will be placed in roll forward
          pending state. New logs from the primary database can be fetched
          and applied to the standby database. The standby database can
          then be used in place of the primary database if it goes down.

     MIRROR
          Specifies that the mirrored database is to be used as a backup
          image which can be used to restore the primary database.

  ------------------------------------------------------------------------

10.6 db2look - DB2 Statistics Extraction Tool

The syntax diagram should appear as follows:

>>-db2look---d--DBname----+--------------+---+-----+---+-----+-->
                          '--u--Creator--'   '--s--'   '--g--'

>-----+-----+---+-----+---+-----+---+-----+---+-----+----------->
      '--a--'   '--h--'   '--r--'   '--c--'   '--p--'

>-----+------------+---+-------------------+-------------------->
      '--o--Fname--'   '--e--+----------+--'
                             '--t Tname-'

>-----+-------------------+---+-----+---+-----+----------------->
      '--m--+----------+--'   '--l--'   '--x--'
            '--t Tname-'

>-----+---------------------------+---+-----+------------------><
      '--i--userid---w--password--'   '--f--'


The -td x parameter has been added following the -c parameter. Its
definition is as follows:

Specifies the statement delimiter for SQL statements generated by db2look.
If this option is not specified, the defaults is the semicolon ';'. It is
recommened that this option be used if the -e option is specified. In this
case, the extracted objects may contain triggers or SQL routines.

The following example will also be added:

Generate the DDL statements for objects created by all users in the
database DEPARTMENT. The db2look output is sent to file db2look.sql:

db2look -d department -a -e -td % -o db2look.sql
db2 -td% -f db2look.sql

  ------------------------------------------------------------------------

10.7 db2updv7 - Update Database to Version 7 Current Fix Level

This command updates the system catalogs in a database to support the
current FixPak in the following ways:

   * Enables the use of the new built-in functions (ABS, DECRYPT_BIN,
     DECRYPT_CHAR, ENCRYPT, GETHINT, MULTIPLY_ALT, and ROUND).
   * Enables the use of the new built-in procedures (GET_ROUTINE_SAR and
     PUT_ROUTINE_SAR).
   * Adds or applies corrections to WEEK_ISO and DAYOFWEEK_ISO functions on
     Windows and OS/2 databases.
   * Applies a correction to table packed descriptors for tables migrated
     from Version 2 to Version 6.
   * Creates the view SYSCAT.SEQUENCES.

Authorization
     sysadm

Required Connection
     Database. This command automatically establishes a connection to the
     specified database.

Command Syntax

     >>-db2updv7----d---database_name-------------------------------->

     >-----+---------------------------+---+-----+------------------><
           '--u--userid---p--password--'   '--h--'


Command Parameters

     -d database-name
          Specifies the name of the database to be updated.

     -u userid
          Specifies the user ID.

     -p password
          Specifies the password for the user.

     -h
          Displays help information. When this option is specified, all
          other options are ignored, and only the help information is
          displayed.

Example
     After installing the FixPak, update the system catalog in the sample
     database by issuing the following command:

     db2updv7 -d sample

Usage Notes
     This tool can only be used on a database running DB2 Version 7.1 or
     Version 7.2 with at least FixPak 2 installed. If the command is issued
     more than once, no errors are reported and each of the catalog updates
     is applied only once.

     To enable the new built-in functions, all applications must disconnect
     from this database and the database must be deactivated if it has been
     activated.

  ------------------------------------------------------------------------

10.8 New Command Line Processor Option (-x, Suppress printing of column
headings)

A new option, -x, tells the command line processor to return data without
any headers, including column names. The default setting for this command
option is OFF.
  ------------------------------------------------------------------------

10.9 True Type Font Requirement for DB2 CLP

To correctly display the national characters for single byte (SBCS)
languages correctly from the DB2 command line processor (CLP) window,
change the font to True Type.
  ------------------------------------------------------------------------

10.10 ADD DATALINKS MANAGER

The required authorization level for this command is one of the following:

   * sysadm
   * sysctrl
   * sysmaint

The following usage note should be added:

This command is effective only after all applications have been
disconnected from the database. The DB2 Data Links Manager being added must
be completely set up and running for this command to be successful. The
database must also be registered on the DB2 Data Links Manager using the
dlfm add_db command. The maximum number of DB2 Data Links Managers that can
be added to a database is 16.
  ------------------------------------------------------------------------

10.11 ARCHIVE LOG (new command)

Archive Log

Closes and truncates the active log file for a recoverable database. If
user exit is enabled, issues an archive request.

Authorization

One of the following:

   * sysadm
   * sysctrl
   * sysmaint
   * dbadm

Required Connection

This command automatically establishes a connection to the specified
database. If a connection already exists, an error is returned.

Command Syntax

>>-ARCHIVE LOG FOR----+-DATABASE-+--database-alias-------------->
                      '-DB-------'

>-----+---------------------------------------+----------------->
      '-USER--username--+------------------+--'
                        '-USING--password--'

>-------| On Node clause |-------------------------------------><

On Node clause

|---ON----+-| Node List clause |-------------------------+------|
          '-ALL NODES--+-------------------------------+-'
                       '-EXCEPT--| Node List clause |--'

Node List clause

                  .-,-----------------------------------.
                  V                                     |
|---+-NODE--+--(-----node number--+------------------+--+---)---|
    '-NODES-'                     '-TO--node number--'


Command Parameters

DATABASE database-alias
     Specifies the alias of the database whose active log is to be
     archived.

USER username
     Identifies the user name under which a connection will be attempted.

USING password
     Specifies the password to authenticate the user name.

ON ALL NODES
     Specifies that the command should be issued on all nodes in the
     db2nodes.cfg file. This is the default if a node clause is not
     specified.

EXCEPT
     Specifies that the command should be issued on all nodes in the
     db2nodes.cfg file, except those specified in the node list.

ON NODE/ON NODES
     Specifies that the logs should be archived for the specified database
     on a set of nodes.

node number
     Specifies a node number in the node list.

TO node number
     Used when specifying a range of nodes for which the logs should be
     archived. All nodes from the first node number specified up to and
     including the second node number specified are included in the node
     list.

Usage Notes

This command can be used to collect a complete set of log files up to a
known point. The log files can then be used to update a standby database.

This function can only be executed when there is no database connection to
the specified database. This prevents a user from executing the command
with uncommitted transactions. As such, the ARCHIVE LOG command will not
forcibly commit the user's incomplete transactions. If a database
connection to the specified database already exists and this command is
executed, the command will terminate and return an error. If another
application has transactions in progress with the specified database when
this command is executed, there will be a slight performance degradation
since the command flushes the log buffer to disk. Any other transactions
attempting to write log records to the buffer will have to wait until the
flush is complete.

If used in an MPP environment, a subset of nodes may be specified by using
a node clause. If the node clause is not specified, the default behaviour
for this command is to close and archive the active log on all nodes.

Using this command will cause a database to lose a portion of its LSN
space, and thereby hasten the exhaustion of valid LSNs.
  ------------------------------------------------------------------------

10.12 BACKUP DATABASE

10.12.1 Syntax Diagram

The syntax diagram for BACKUP DATABASE will be updated to reflect the new
INCREMENTAL parameter and the optional DELTA argument. Specifying the
INCREMENTAL option alone will result in a cumulative backup image being
produced. The optional DELTA argument can be used to specify the production
of a non-cumulative backup image.

>>-BACKUP----+-DATABASE-+---database-alias---------------------->
             '-DB-------'

>-----+---------------------------------------+----------------->
      '-USER--username--+------------------+--'
                        '-USING--password--'

>-----+--------------------------------------------+------------>
      |                .-,------------------.      |
      |                V                    |      |
      '-TABLESPACE--(-----tablespace-name---+---)--'

>-----+---------+---+--------------------------+---------------->
      '-ONLINE--'   '-INCREMENTAL--+--------+--'
                                   '-DELTA--'

>-----+-------------------------------------------------------+->
      +-USE TSM--+-------------------------------+------------+
      |          '-OPEN--num-sessions--SESSIONS--'            |
      |     .-,--------.                                      |
      |     V          |                                      |
      +-TO----+-dir-+--+--------------------------------------+
      |       '-dev-'                                         |
      '-LOAD--library-name--+-------------------------------+-'
                            '-OPEN--num-sessions--SESSIONS--'

>-----+-----------------------------+--------------------------->
      '-WITH--num-buffers--BUFFERS--'

>-----+----------------------+---+-----------------+------------>
      '-BUFFER--buffer-size--'   '-PARALLELISM--n--'

>----+-------------------+-------------------------------------><
     '-WITHOUT PROMPTING-'


10.12.2 DB2 Data Links Manager Considerations

If one or more Data Links servers are configured for the database, the
backup operation will succeed, even if a Data Links server is not
available. When the Data Links server restarts, backup processing will be
completed on that Data Links server before it becomes available to the
database again.

Note:
     If there are twice as many backups still waiting for an unavailable
     Data Links server as are retained in the history file for the database
     (database configuration parameter num_db_backups), the backup
     operation will fail.

  ------------------------------------------------------------------------

10.13 BIND

The command syntax for DB2 should be modified to show the federated
parameter as follows:

FEDERATED--+--NO--+--
           '-YES--'


FEDERATED
     Specifies whether a static SQL statement in a package references a
     nickname or a federated view. If this option is not specified and a
     static SQL statement in the package references a nickname or a
     federated view, a warning is returned and the package is created.

     NO
          A nickname or federated view is not referenced in the static SQL
          statements of the package. If a nickname or federated view is
          encountered in a static SQL statement during the prepare or bind
          of this package, an error is returned and the package is not
          created.

     YES
          A nickname or federated view can be referenced in the static SQL
          statements of the package. If no nicknames or federated views are
          encountered in static SQL statements during the prepare or bind
          of the package, no errors or warnings are returned and the
          package is created.

Note:
     In Version 7 FixPak 2, an SQL1179W warning message is generated by the
     server when precompiling a source file or binding a bind file without
     specifying a value for the FEDERATED option. The same message is
     generated when the source file or bind file includes static SQL
     references to a nickname. There are two exceptions:
        o For clients that are at an earlier FixPak than Version 7 FixPak 2
          or for downlevel clients, the sqlaprep() API does not report this
          SQL1179W warning in the message file. The Command Line Processor
          PRECOMPILE command also does not output the warning in this case.
        o For clients that are at an earlier FixPak than Version 7 FixPak 2
          or for downlevel clients, the sqlabndx API does report this
          SQL1179W warning in the message file. However, the message file
          also incorrectly includes an SQL0092N message indicating that no
          package was created. This is not correct as the package is indeed
          created. The Command Line Processor BIND command returns the same
          erroneous warning.

  ------------------------------------------------------------------------

10.14 CALL

The syntax for the CALL command should appear as follows:

                        .-,---------------.
                        V                 |
>>-CALL--proc-name---(-----+-----------+--+---)----------------><
                           '-argument--'


The description of the argument parameter has been changed to:

   Specifies one or more arguments for the stored procedure.
   All input and output arguments must be specified in the order
   defined by the procedure. Output arguments are specified
   using the "?" character. For example, a stored procedure foo
   with one integer input parameter and one output parameter
   would be invoked as "call foo (4, ?)".

Note:

  1. When invoking this utility from an operating system prompt, it may be
     necessary to delimit the command as follows:

        "call DEPT_MEDIAN (51)"

     A single quotation mark (') can also be used.

  2. The stored procedure being called must be uniquely named in the
     database.

  3. The stored procedure must be cataloged. If an uncataloged procedure is
     called, a DB21036 error message is returned.

  4. A DB21101E message is returned if not enough parameters are specified
     on the command line, or the command line parameters are not in the
     correct order (input, output), according to the stored procedure
     definition.

  5. There is a maximum of 1023 characters for a result column.

  6. LOBS and binary data (FOR BIT DATA, VARBINARY, LONGVARBINARY, GRAPHIC,
     VARGAPHIC, or LONGVARGRAPHIC) are not supported.

  7. CALL supports result sets.

  8. If an SP with an OUTPUT variable of an unsupported type is called, the
     CALL fails, and message DB21036 is returned.

  9. The maximum length for an INPUT parameter to CALL is 1024.

  ------------------------------------------------------------------------

10.15 DROP DATALINKS MANAGER (new command)

DROP DATALINKS MANAGER

Drops a DB2 Data Links Manager from the list of registered DB2 Data Links
Managers for a specified database.

Authorization

One of the following:

   * sysadm
   * sysctrl
   * sysmaint

Command Syntax

>>-DROP DATALINKS MANAGER FOR----+-DATABASE-+--dbname---USING--->
                                 '-DB-------'

>----name------------------------------------------------------><


Command Parameters

DATABASE dbname
     Specifies a database name.

USING name
     Specifies the name of the DB2 Data Links Manager server as shown by
     the LIST DATALINKS MANAGER command.

Examples

Example 1

Dropping a DB2 Data Links Manager micky.almaden.ibm.com from database TEST
under instance validate residing on host bramha.almaden.ibm.com when some
database tables have links to micky.almaden.ibm.com. It is extremely
important that the following steps be taken when dropping a DB2 Data Links
Manager.

  1. Take a database backup for database TEST.
  2. If there are any links to micky.almaden.ibm.com, unlink them:

       a. Log on with a user ID belonging to SYSADM_GROUP and obtain an
          exclusive mode connection the the database TEST.

             connect to test in exclusive mode

          Ensure that this is the only connection to test using that user
          ID. This will prevent any new links from being created.
       b. Obtain a list of all FILE LINK CONTROL DATALINK columns and the
          tables containing them in the database.

          select tabname, colname from syscat.columns where substr(dl_features,2,1)='F'

       c. For each FILE LINK CONTROL DATALINK column in the list, issue SQL
          SELECT to determine if links to micky.almaden.ibm.com exist. For
          example, for a DATALINK column c in table t, the SELECT statement
          would be:

             select count(*) from t where dlurlserver(t.c) = 'MICKY.ALMADEN.IBM.COM'

       d. For each FILE LINK CONTROL DATALINK column containing such links,
          issue SQL UPDATE to unlink values which are links to
          micky.almaden.ibm.com. For example, for a DATALINK column c in
          table t, the UPDATE statement would be:

          update t set t.c = null where dlurlserver(t.c)='MICKY.ALMADEN.IBM.COM'

          If t.c is not nullable, the following can be used instead:

          update t set t.c = dlvalue('') where dlurlserver(t.c)='MICKY.ALMADEN.IBM.COM'

       e. Commit this SQL UPDATE:

          commit

  3. Issue the DROP DATALINKS MANAGER command:

        drop datalinks manager for db test using node micky.almaden.ibm.com

  4. Terminate the exclusive mode connection to make the changes effective
     and to allow other connections to the database:

        terminate

  5. Initiate unlink processing and garbage collection of backup
     information for TEST on micky.almaden.ibm.com. As DB2 Data Links
     Manager Administrator, issue the following command on
     micky.almaden.ibm.com:

        dlfm drop_dlm test validate bramha.almaden.ibm.com

     This will unlink any files that are still linked to database TEST,
     just in case the user has missed unlinking them before invoking step
     3. If micky.almaden.ibm.com has backup information (for example,
     archive files, metadata) for files previously linked to database TEST,
     this command will initiate garbage collection of that information. The
     actual unlinking and garbage collection will be performed
     asynchronously.

Example 2

Deleting DATALINK values that are links to files on a DB2 Data Links
Manager called micky.almaden.ibm.com, when the Manager has already been
dropped from database TEST. This may be required if steps in Example 1 were
not followed while dropping micky.almaden.ibm.com. SQL DELETE, SELECT, and
UPDATE statements will not be successful for such DATALINK values
(SQL0368). The user must run a reconcile operation for each table that
contains such DATALINK values. Each DATALINK value that was a link to
micky.almaden.ibm.com will be updated to NULL or a zero-length DATALINK
value. Any row containing such a value will be inserted into the exception
table (if one was specified). However, the DATALINK value will not include
the prefix name. The prefix name in the original DATALINK value is no
longer obtainable by the system, because micky.almaden.ibm.com has been
dropped. For example, if the original DATALINK value was
'http://host.com/dlfs/x/y/a.b' and '/dlfs' is the prefix name, the DATALINK
value in the exception table will contain 'http://host.com/x/y/a.b'. The
files referenced by these DATALINK values will continue to remain in linked
state on the DB2 Data Links Manager. The dlfm drop_dlm command can be
issued on micky.almaden.ibm.com to initiate unlink processing for these
files. If micky.almaden.ibm.com has backup information (for example,
archive files, metadata) for files previously linked to database TEST, this
command will initiate garbage collection of that information. The actual
unlinking and garbage collection will be performed asynchronously.

Example 3

Multiple incarnations of a DB2 Data Links Manager micky.almaden.ibm.com for
a database TEST. This scenario demonstrates that a DB2 Data Links Manager
can be re-registered after being dropped, and that it is then treated as a
completely new DB2 Data Links Manager. The following steps are only
 illustrative of a scenario that is possible. If, as recommended, the steps
in Example 1 are followed for dropping micky.almaden.ibm.com, links to the
older incarnation of micky.almaden.ibm.com will not exist; that is, one
will not see error SQL0368 in step 7 below.

  1. Register micky.almaden.ibm.com to database TEST:

        add datalinks manager for db test using node micky.almaden.ibm.com port 14578

  2. Create links to files on micky.almaden.ibm.com:

        connect to test
        create table t(c1 int, c2 datalink linktype url file link control mode
        db2options)
        insert into t values(1, dlvalue('file://micky.almaden.ibm.com/pictures/
        yosemite.jpg'))
        commit
        terminate

  3. Drop micky.almaden.ibm.com from database TEST:

        drop datalinks manager for db test using micky.almaden.ibm.com

  4. Select DATALINK values:

        connect to test
        select * from t
        terminate

     The user will see:

        SQL0368 The DB2 Data Links Manager "MICKY.ALMADEN.IBM.COM"
           is not registered to the database. SQLSTATE=55022.

  5. Register micky.almaden.ibm.com to database TEST again:

        add datalinks manager for db test using node micky.almaden.ibm.com port 14578

  6. Insert more DATALINK values:

        connect to test
        insert into t values(2, dlvalue('file://micky.almaden.ibm.com/pictures/
        tahoe.jpg'))
        commit


  7. Select DATALINK values:

        select c2 from t where c1 = 2

     is successful because the value being selected is a link to the
     currently registered incarnation of micky.almaden.ibm.com.

        select c2 from t where c1 = 1

     returns:

        SQL0368 The DB2 Data Links Manager "MICKY.ALMADEN.IBM.COM"
           is not registered to the database. SQLSTATE=55022.

     because the value being selected is a link to the incarnation of
     micky.almaden.ibm.com which was dropped in step 3 above.

Usage Notes

The effects of the DROP DATALINKS MANAGER command cannot be rolled back. It
is extremely important to follow the steps outlined in Example 1 when using
the DROP DATALINKS MANAGER command.

This command is effective only after all applications have been
disconnected from the database.

Upon successful completion of the command, the user is informed (DB210201I)
that no processing has been done on the DB2 Data Links Manager. Before
dropping a DB2 Data Links Manager, the user must ensure that the database
does not have any links to files on that DB2 Data Links Manager. If links
do exist in the database after a DB2 Data Links Manager has been dropped,
the user must run the reconcile utility to get rid of them. The reconcile
utility will set these links to NULL (if the DATALINK column is nullable),
or to a zero-length DATALINK value.

Files corresponding to links between a database and a dropped DB2 Data
Links Manager remain in linked state. That is, they are inaccessible to
operations like read, write, rename, delete, change of permissions, or
change of ownership.

Archived copies of unlinked files on the DB2 Data Links Manager will not be
garbage collected by this command. However, users can explicitly initiate
unlink processing and garbage collection using the dlfm drop_dlm command on
the DB2 Data Links Manager.

It is recommended that a database backup be taken before dropping a DB2
Data Links Manager. In addition, ensure that all replication subscriptions
have replicated all changes involving this DB2 Data Links Manager.

If a backup was taken before the DB2 Data Links Manager was dropped from a
database, and that backup image is used to restore after that DB2 Data
Links Manager was dropped, restore or rollforward processing may put
certain tables in datalink reconcile pending (DRP) state.
  ------------------------------------------------------------------------

10.16 EXPORT

In the section "DB2 Data Links Manager Considerations", Step 3 of the
procedure to ensure that a consistent copy of the table and the
corresponding files referenced by DATALINK columns are copied for export
should read:

   3. Run the dlfm_export utility at each Data Links server. Input to the
      dlfm_export utility is the control file name, which is generated by the
      export utility. This produces a tar (or equivalent) archive of the files listed
      within the control file. For Distributed File Systems (DFS), the dlfm_export
      utility will get the DCE network root credentials before archiving the files
      listed in the control file. dlfm_export does not capture the ACLs information
      of the files that are archived.

In the same section, the bullets following "Successful execution of EXPORT
results in the generation of the following files" should be modified as
follows:

The second sentence in the first bullet should read:

   A DATALINK column value in this file has the same format
   as that used by the import and load utilities.

The first sentence in the second bullet should read:

   Control files server_name, which are generated for
   each Data Links server. (On the Windows NT operating system,
   a single control file, ctrlfile.lst, is used by all Data Links
   servers. For DFS, there is one control file for each cell.)

The following sentence should be added to the paragraph before Table 5:

   For more information about dlfm_export, refer to the "Data Movement
   Utilities Guide and Reference" under "Using Export to move DB2 Data
   Links Manager Data".

  ------------------------------------------------------------------------

10.17 GET DATABASE CONFIGURATION

The description of the DL_TIME_DROP configuration parameter should be
changed to the following:

   Applies to DB2 Data Links Manager only. This parameter specifies
   the number of days files would be retained on an archive server
   (such as a TSM server) after a DROP DATABASE command is issued.

The new parameter TRACKMOD will be added to the GET DATABASE CONFIGURATION
command. The syntax will appear as follows:

>>-GET----+-DATABASE-+---+-CONFIGURATION-+--FOR----------------->
          '-DB-------'   +-CONFIG--------+
                         '-CFG-----------'

                                .-NO--.
>----database-alias---TRACKMOD--+-YES-+------------------------><


The parameter description will be added as follows:

TRACKMOD
     Indicates whether DB2 should track modified pages in the database in
     order to allow incremental backups to be taken.

     OFF
          Specifies that changed pages should not be tracked. This is the
          default for databases created prior to Version 7.1, FixPak 3.

     ON
          Specifies that changed pages should be tracked. When this
          parameter is set, incremental backups of the database can be
          made. This is the default for databases created with Version 7.1,
          FixPak 3 or later.

  ------------------------------------------------------------------------

10.18 GET ROUTINE (new command)

GET ROUTINE

Retrieves a routine SQL Archive (SAR) file for a specified SQL routine.

Authorization

dbadm

Required Connection

Database. If implicit connect is enabled, a connection to the default
database is established.

Command Syntax

>>-GET ROUTINE--INTO---file_name----FROM----+-----------+------->
                                            '-SPECIFIC--'

>-------PROCEDURE----routine_name------------------------------><


Command Parameters

INTO file-name
     Names the file where routine SQL archive (SAR) is stored.

FROM
     Indicates that start of the specification of the routine to be
     retrieved.

SPECIFIC
     The specified routine-name is given as a specific name.

PROCEDURE
     The routine is an SQL procedure.

routine-name
     The name of the procedure. If SPECIFIC is specified then it is the
     specific name of the procedure. If the name is not qualified with a
     schema name, the CURRENT SCHEMA is used as the schema name of the
     routine. The routine-name must be an existing procedure that is
     defined as an SQL procedure.

Examples

     GET ROUTINE INTO procs/proc1.sar FROM PROCEDURE myappl.proc1;

  ------------------------------------------------------------------------

10.19 GET SNAPSHOT

The description for the FCM FOR ALL NODES parameter should appear as
follows:

Provides Fast Communication Manager (FCM) statistics between the node
against which the GET SNAPSHOT command was issued and the other nodes in
the EEE instance.
  ------------------------------------------------------------------------

10.20 IMPORT

In the section "DB2 Data Links Manager Considerations", the following
sentence should be added to Step 3:

   For Distributed File Systems (DFS), update the cell name
   information in the URLs (of the DATALINK columns) from the
   exported data for the SQL table, if required.

The following sentence should be added to Step 4:

   For DFS, define the cells at the target configuration
   in the DB2 Data Links Manager configuration file.

The paragraph following Step 4 should read:

   When the import utility runs against the target database,
   files referred to by DATALINK column data are linked on
   the appropriate Data Links servers.

  ------------------------------------------------------------------------

10.21 LIST HISTORY

The CREATE TABLESPACE parameter will be added to the LIST HISTORY command.
The syntax diagram will appear as follows:

>>-LIST HISTORY----+-------------------+------------------------>
                   +-BACKUP------------+
                   +-ROLLFORWARD-------+
                   +-ALTER TABLESPACE--+
                   +-DROPPED TABLE-----+
                   +-LOAD--------------+
                   +-RENAME TABLESPACE-+
                   '-CREATE TABLESPACE-'

>-----+-ALL--------------------------------+-------------------->
      +-SINCE--timestamp-------------------+
      '-CONTAINING--+-_schema.objectname-+-'
                    '-_objectname--------'

>----FOR--+----------+---database-alias------------------------><
          +-DATABASE-+
          '-DB-------'


The parameter description will be added as follows:

CREATE TABLESPACE
     Lists all CREATE TABLESPACE and DROP TABLESPACE operations.

The Usage Notes will be updated as follows:

The following symbols will be added to the Operation section of the report:

   * A - Create tablespace
   * O - Drop tablespace
   * U - Unload

The symbols under the Type section of the report will be reorganized as
follows:

   * Backup Types
        o F - Offline
        o N - Online
        o I - Incremental Offline
        o O - Incremental Online
        o D - Delta Offline
        o E - Delta Online
   * Rollforward Types
        o E - End of log
        o P - Point in time
   * Load Types
        o I - Insert
        o R - Replace
   * Alter tablespace Types
        o C - Add containers
        o R - Rebalance
   * Quiesce Types
        o S - Quiesce Share
        o U - Quiesce Update
        o X - Quiesce Exclusive
        o Z - Quiesce Reset

  ------------------------------------------------------------------------

10.22 LOAD

In the section "DB2 Data Links Manager Considerations", add the following
sentence to Step 1 of the procedure that is to be performed before invoking
the load utility, if data is being loaded into a table with a DATALINK
column that is defined with FILE LINK CONTROL:

   For Distributed File Systems (DFS), ensure that the DB2 Data Links Managers
   within the target cell are registered.

The following sentence should be added to Step 5:

   For DFS, register the cells at the target configuration
   referred to by DATALINK data (to be loaded) in the DB2
   Data Links Manager configuration file.

In the section "Representation of DATALINK Information in an Input File",
the first note following the parameter description for urlname should read:

   Currently "http", "file", "unc", and "dfs" are permitted as a schema name.

The first sentence of the second note should read:

   The prefix (schema, host, and port) of the URL
   name is optional. For DFS, the prefix refers to the
   schema cellname filespace-junction portion.

In the DATALINK data examples for both the delimited ASCII (DEL) file
format and the non-delimited ASCII (ASC) file format, the third example
should be removed.

The DATALINK data examples in which the load or import specification for
the column is assumed to be DL_URL_DEFAULT_PREFIX should be removed and
replaced with the following:

Following are DATALINK data examples in which the load or import
specification for the column is assumed to be DL_URL_REPLACE_PREFIX
("http://qso"):

   * http://www.almaden.ibm.com/mrep/intro.mpeg

     This sample URL is stored with the following parts:
        o schema = http
        o server = qso
        o path = /mrep/intro.mpeg
        o comment = NULL string
   * /u/me/myfile.ps

     This is stored with the following parts:
        o schema = http
        o server = qso
        o path = /u/me/myfile.ps
        o comment = NULL string

  ------------------------------------------------------------------------

10.23 PING (new command)

PING

Tests the network response time of the underlying connectivity between a
client and a database server where DB2 Connect is used to establish the
connection.

Authorization

None

Required Connection

Database

Command Syntax

                           .-time-.
                      .-1--+------+---------------------.
>>-PING---db_alias----+-+-----------------------------+-+------><
                        '-number_of_times--+-------+--'
                                           +-times-+
                                           '-time--'


Command Parameters

db_alias
     Specifies the database alias for the database on a DRDA server that
     the ping is being sent to.

     Note:
          This parameter, although mandatory, is not currently used. It is
          reserved for future use. Any valid database alias name can be
          specified.

number of times
     Specifies the number of iterations for this test. The value must be
     between 1 and 32767 inclusive. The default is 1. One timing will be
     returned for each iteration.

Examples

To test the network response time for the connection to the host database
server hostdb once:

   db2 ping hostdb 1
or:
   db2 ping hostdb

The command will display output that looks like this:

   Elapsed time: 7221 microseconds

To test the network response time for the connection to the host database
server hostdb 5 times:

   db2 ping hostdb 5
or:
   db2 ping hostdb 5 times

The command will display output that looks like this:

   Elapsed time: 8412 microseconds
   Elapsed time: 11876 microseconds
   Elapsed time: 7789 microseconds
   Elapsed time: 10124 microseconds
   Elapsed time: 10988 microseconds

Usage Notes

A database connection must exist before invoking this command, otherwise an
error will result.

The elapsed time returned is for the connection between the client and a
DRDA server database via DB2 Connect.
  ------------------------------------------------------------------------

10.24 PUT ROUTINE (new command)

PUT ROUTINE

Uses the specified routine SQL Archive (SAR) file to define a routine in
the database.

Authorization

dbadm

Required Connection

Database. If implicit connect is enabled, a connection to the default
database is established.

Command Syntax

>>-PUT ROUTINE----FROM----file-name----------------------------->

>-----+---------------------------------------+----------------><
      '-OWNER--new-owner--+----------------+--'
                          '-USE REGISTERS--'


Command Parameters

FROM file-name
     Names the file where routine SQL archive (SAR) is stored.

OWNER new-owner
     Specifies a new authorization-name for the routine that will be used
     for authorization checking of the routine. The new-owner must have the
     necessary privileges for the routine to be defined. If the OWNER
     clause is not specified, the authorization-name that originally
     defined the routine is used.

USE REGISTERS
     Indicates that the CURRENT SCHEMA and CURRENT PATH special registers
     are used to define the routine. If this clause is not specified, the
     settings for the default schema and SQL path are the settings used
     when the routine was originally defined. CURRENT SCHEMA is used as the
     schema name for unqualified object names in the routine definition
     (including the name of the routine) and CURRENT PATH is used to
     resolve unqualified routines and data types in the routine definition.

Examples

     PUT ROUTINE FROM procs/proc1.sar;

Usage Notes

No more than one procedure can be concurrently installed under a given
schema.
  ------------------------------------------------------------------------

10.25 RECONCILE

The following usage note should be added to the command description:

During reconciliation, attempts are made to link files which exist
according to table data, but which do not exist according to Data Links
Manager metadata, if no other conflict exists. A required DB2 Data Links
Manager is one which has a referenced DATALINK value in the table.
Reconcile tolerates unavailability of a required DB2 Data Links Manager as
well as those that are configured to the database but are not part of the
table data.

If an exception table is not specified, the exception report file
(filename.exp) will have the host name, file name, column ID, and reason
code for each of the DATALINK column values for which file references could
not be re-established. If the file reference could not be re-established
because the DB2 Data Links Manager itself was dropped from the database
using the DROP DATALINKS MANAGER command, the file name reported in the
exception report file is not the full file name; that is, the prefix part
is missing. In the exception table for the DATALINK values whose DB2 Data
Links Manager is dropped or is not available, the file name in the DATALINK
value is not the full file name. The prefix part is missing. For example,
if the original DATALINK value was 'http://host.com/dlfs/x/y/a.b', the
value reported in the exception table will be 'http://host.com/x/y/a.b';
that is, the prefix name 'dlfs' will not be included. The exception report
file in this case will have 'x/y/a.b'; that is, the prefix name 'dlfs' will
not be included.

At the end of the reconciliation process, the table is taken out of
datalink reconcile pending (DRP) state only if reconcile processing is
complete on all the required DB2 Data Links Managers. If reconcile
processing is pending on any of the required DB2 Data Links Managers
(because they were unavailable), the table will remain, or be placed, in
DRP state.

The following should be added to the list of possible violations:

   00010-DB2 Data Links Manager referenced by the DATALINK value
      has been dropped from the database using the DROP DATALINKS
      MANAGER command. In this case, the corresponding DATALINK value
      in the exception table will not contain the prefix name.
      For example, if the original DATALINK value was
      'http://host.com/dlfs/prfx/x/y/a.b', and '/dlfs/prfx' is
      the prefix name, the exception table will contain
      'http://host.com/x/y/a.b'.

  ------------------------------------------------------------------------

10.26 REORGANIZE TABLE

The following sentence will be added to the Usage Notes:

REORGANIZE TABLE cannot use an index that is based on an index extension.
  ------------------------------------------------------------------------

10.27 RESTORE DATABASE

10.27.1 Syntax

The following option will be added to the syntax of the RESTORE DATABASE
command after the TABLESPACE/TABLESPACE ONLINE/HISTORY FILE options:

>>-+-------------------------+---------------------------------><
   '-INCREMENTAL--+-------+--'
                  '-ABORT-'


The parameter descriptions will be added as follows:

INCREMENTAL
     Results in a manual cumulative restore of the database. The user will
     issue each of the restore commands.

     ABORT
          This parameter should be used to terminate an incremental restore
          before successful completion.

The following examples will also be added:

The following is a sample weekly incremental backup strategy with a
recoverable database. A full backup is scheduled once per week, a delta
every day, plus an incremental mid-week:

   (Sun)        backup db kdr use adsm
   (Mon)        backup db kdr online incremental delta use adsm
   (Tue)        backup db kdr online incremental delta use adsm
   (Wed)        backup db kdr online incremental use adsm
   (Thu)        backup db kdr online incremental delta use adsm
   (Fri)        backup db kdr online incremental delta use adsm
   (Sat)        backup db kdr online incremental use adsm

For a manual database restore of images created above on Friday morning,
issue the following commands:

   restore db kdr incremental taken at (Thu)
   restore db kdr incremental taken at (Sun)
   restore db kdr incremental taken at (Wed)
   restore db kdr incremental taken at (Thu)

Note:
     Any RESTORE command of the form db2 restore db <name> will perform a
     full database restore, regardless of whether the image being restored
     is a database image or a table space image. Any RESTORE command of the
     form db2 restore db <name> tablespace will perform a table space
     restore of the table spaces found in the image. Any RESTORE command in
     which a list of table spaces is provided will perform a restore of
     whatever table spaces were explicitly listed.

10.27.2 DB2 Data Links Manager Considerations

The second paragraph in the section entitled "DB2 Data Links Manager
Considerations" should be replaced with:

   If one or more Data Links servers are configured for the database,
   the restore operation will succeed, even if a Data Links server is not available.
   When the Data Links server restarts, restore processing will be completed
   on that Data Links server before it becomes available to the database again.
   NOTE: If a database restore operation is still waiting for an unavailable
   Data Links server, any subsequent database or table space restore operations
   will fail.

  ------------------------------------------------------------------------

10.28 ROLLFORWARD DATABASE

The second paragraph in the section entitled "DB2 Data Links Manager
Considerations" should be replaced with:

   If one or more Data Links servers are configured for the database,
   the rollforward operation will succeed, even if a Data Links server is not available.
   When the Data Links server restarts, rollforward processing will be completed
   on that Data Links server before it becomes available to the database again.

  ------------------------------------------------------------------------

10.29 Documentation Error in CLP Return Codes

In the Command Line Processor Return Codes section of Chapter 2, the second
paragraph should appear as follows:

For example, the following Bourne shell script executes the GET DATABASE
MANAGER CONFIGURATION command, then inspects the CLP return code:

   db2 get database manager configuration
   if [ "$?" = "0" ]
   then echo "OK!"
   fi

  ------------------------------------------------------------------------

Data Movement Utilities Guide and Reference(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

11.1 Chapter 2. Import

11.1.1 Using Import with Buffered Inserts

The note at the end of this section should read:

Note:
     In all environments except EEE, the buffered inserts feature is
     disabled during import operations in which the INSERT_UPDATE parameter
     is specified.

  ------------------------------------------------------------------------

11.2 Chapter 3. Load

11.2.1 Pending States After a Load Operation

The first two sentences in the last paragraph in this section have been
changed to the following:

   The fourth possible state associated with the load process (check pending state)
   pertains to referential and check constraints, DATALINKS constraints,
   AST constraints, or generated column constraints. For example, if an existing table
   is a parent table containing a primary key referenced by a foreign key
   in a dependent table, replacing data in the parent table places both tables (not the
   table space) in check pending state.

11.2.2 Load Restrictions and Limitations

The following restrictions apply to generated columns and the load utility:

   * It is not possible to load a table having a generated column in a
     unique index unless the generated column is an "include column" of the
     index or the generatedoverride file type modifier is used. If this
     modifier is used, it is expected that all values for the column will
     be supplied in the input data file.
   * It is not possible to load a table having a generated column in the
     partitioning key unless the generatedoverride file type modifier is
     used. If this modifier is used, it is expected that all values for the
     column will be supplied in the input data file.

11.2.3 totalfreespace File Type Modifier

The totalfreespace file type modifier (LOAD) has been modified to accept a
value between 0 and 2 147 483 647.
  ------------------------------------------------------------------------

11.3 Chapter 4. AutoLoader

11.3.1 rexecd Required to Run Autoloader When Authentication Set to YES

In the Autoloader Options section the following note will be added to the
AUTHENTICATION and PASSWORD Parameters description:

In a Linux environment, if you are running the autoloader with the
authentication option set to YES, rexecd must be enabled on all machines.
If rexecd is not enabled the following error message will be generated:

   openbreeze.torolab.ibm.com: Connection refused
   SQL6554N  An error occurred when attempting to remotely execute a process.

The following error messages will be generated in the db2diag.log file:

   2000-10-11-13.04.16.832852   Instance:svtdbm   Node:000
   PID:19612(db2atld)   Appid:
   oper_system_services  sqloRemoteExec   Probe:31

  ------------------------------------------------------------------------

Replication ®®n¯Pø¥ÝãÏƒ¾U

  ------------------------------------------------------------------------

12.1 õê¬gÏ×®D IBM Ý›¦Aóû

ùØ¾× DataJoiner ¦¸¾¯ 2 ¸×õ¢ús¦¸ùàõê¬g÷ˆ©’Ýš®D IBM Ý›¦Aóû­A ¸×Ýê®D IBM Ý›¦A
óûõê¬g÷ˆ©’­AÝp Informix­BMicrosoft SQL Server­BOracle­BSybase­B Sybase SQL
Anywhere­C ñzÏœ¾i¾HùØ¾×ÝûÇç®ªõê¬g¦§Ç”µpÝ­üsñæù‡¬’­AÝ]ªø DB2 Relational
Connect ¦¸¾¯ 7 ùSÝüõ¢ús¦§î…ÏO­Cû‹ý{Ýs¦§ DB2 ¸M DataJoiner ¦¸¾¯¸ãÝü¦§¾ð¾x
­]AS/400­BOS/2­BOS/390­BUNIX Ï× Windows­^­Añz¾ýôúùØ¾× DJRA­]DataJoiner õê¬g
§èýz­^ùà§èýzîS©¡¦§õê¬g­C
  ------------------------------------------------------------------------

12.2 Ýb Windows 2000 ÏW¦§õê¬g

DB2 DataPropagator ¦¸¾¯ 7 ¯P Windows 2000 õ@ú~ùtý×ªê©e­C
  ------------------------------------------------------------------------

12.3 ·xÝs SQL ·©ž©¦§Ïw¦ó¨—¯~

ðYÝb DB2 Connect Personal Edition ÏÏùØ¾×­uññùŒÏÏÏá­v­AñzæL¦k·xÝs SQL ·©ž­C
ðY÷åûØ·xÝs SQL ·©ž­AñzñNÝªùÏ@®h®¾š DAS ÏœÝbõ@¾×ÏÏ¦§¨—¯~øT©õ­Aù’ûˆÏW DAS
ùSÝüõ@¾×­AÝ]ªø¾ÝùÇùSÝü·H DB2 Connect PE ¾Xüf­C
  ------------------------------------------------------------------------

12.4 DB2 §–@

®Žüñzøwû‹Ýbõê¬g·“ûãÏÏùØ¾×¦§ÝU§ DB2 ýœ®~Ýw÷ÓüÞús¦§ DB2 §–@­C
  ------------------------------------------------------------------------

12.5 Web ÏW¦§ Data Difference Utility

ñz¾i¾Hñq Web ÏU÷ Data Difference utility (DDU)­A§“õ}ÝpÏU­G
ftp://ftp.software.ibm.com/ps/products/datapropagator/fixes/­C DDU ªOÏ@ðà«d
ùãÏ«¾×æ{Ý­­Aù¥ñzÏ¤÷–ªêÝP·©ž¦§ùƒðàÏœÝP¦¸¾¯­A¾HÏ×ýœ¾Ö¨‚¾X·ùàÆ¾š¦¸¾¯Ïõô­¦§
©týõ­C÷âýà÷ˆøT­A«Ñø¥ó\Ýû«dùãÏ«¾×æ{Ý­¸ã¦ç¦§ README ·­C
  ------------------------------------------------------------------------

12.6 ýŽ 3 üû ÷ˆ©’õê¬gûˆøÔ«dùã

12.6.1 õê¬gûˆøÔ

«Ñø¥ó\ DataPropagator §“î÷¦§ Library ðôðñ
(http://www.ibm.com/software/data/dpropr/) ¾Hù£ñoÏœÝP¦§ús÷ˆ©’õê¬gûˆøÔ«dùã­C
¨¡úàûˆøÔ«dùãÏÏ¦§ùB’J­Añq AIX ÏW¦§ Oracle ÷ˆ©’©wõê¬gùàú«¦¡©‘ñNšõ¢«’¯sù DB2
for Windows NT ÏW÷ˆ©’©wÏÏ¦§¾¬Ñ¦¡©‘­C ù§ðàûˆøÔ«dùãùØ¾× DB2 DataJoiner
Replication Administration (DJRA) ÏuùÆ­B¶^ù£Žýæoù‡Ý­­BÏè¾×æ{Ý­Ï× DB2
DataJoiner­C

Ýb©¥¦§ýŽ 44 ðô­AùB’J 6 ÏÏÝüÇ”®¾áüqÝ‘«X·©ž¦§®¾š·ü÷àÝpÏU­G

ùB’J 6­G®¾áüqÝ‘«X·©ž

Ý]ªøÏè¾×æ{Ý­¯íðnüsñæùùàú«Ý›¦Aóû­Añz¾ýôú®¾áÏ@ðàüqÝ‘«X·©žùàøæùØ¾×¦ÞùðÏ·‡
Çã­C «Ñ«T¸w¾×ùàøäÝ‘Ïè¾×æ{Ý­¦§ùØ¾×¦Þ ID ¾i¾H¦ù£üqÝ‘«X·©ž­C

ðYðn®¾áüqÝ‘«X·©ž­G

  1. ñq Windows NT ®¾Oïœ¾šæ›æ­­Ašõ¢¾¨ìù C:\scripts­C
  2. ÝbÝû¾¨ìÏÏ®¾áÏ@ðà¾søæ DEPTQUAL.PWD ¦§ús·©ž­C ñz¾i¾HùØ¾×¾“Ý¢Ï†Ýr«s¨Š
     æ{Ý­ùà®¾áüoðà·©ž­AÏ¤Ýp Notepad­C üqÝ‘«X·©ž¦§¸RÝW§Dùãªø
     applyqual.pwd­F ù„ÏÏ applyqual ÝrÝˆªOøØÏ·ÏjÏp¬g¦§­A ¾ýôúýÝXñzÝb®¾á¸w
     ïµõê¬gü]¸w©¸ã¾×¦§Ïè¾×ðð¸wÏ÷¦§Ýr‚¸MðÔ­C ÝbÝûûˆøÔ«dùãÏÏ­AÏè¾×ðð¸wÏ÷ªO
     DEPTQUAL­C

     æ—:
          Ï]Ï„ï¸ DB2 DataPropagator ¦¸¾¯ 5 ¾Hùà¦§·©ž¸RÝW§Dùã­C
  3. üqÝ‘«X·©ž¦§Ï§©e©‘Ý­ÝpÏU­G

     SERVER=server USER=userid PWD=password

     ù„ÏÏ­G

     Ý›¦Aóû
          ®ùàú«­B¾¬Ñ¸×ññùŒÝ›¦Aóû¦§ÝW§ë­A¾ýôú¯P¸wïµõê¬gü]¸w¦¡©‘ÏÏ¸ãÆ¾š¦§
          õû¾çÏ@ðP­C ÝbÝûûˆøÔ«dùãÏÏ­Aüoù€ÝW§ëªø SAMPLE Ï× COPYDB­C

     userid
          ñzðpû§¾×ùà§èýz÷àîS¸w÷ˆ©’©w¦§ùØ¾×¦Þ ID­C ðYªO Windows NT Ï× UNIX
          õ@ú~ùtý×­AüoðàðÔªOøØÏ·ÏjÏp¬g¦§­C

     password
          ¯PùØ¾×¦Þ ID ªêÇ”¦§üqÝ‘«X­C ðYªO Windows NT Ï× UNIX õ@ú~ùtý×­A®hüo
          ðàðÔÝüøØÏ·ÏjÏp¬g­C
     «ÑÏœðnÝbüoðà·©žÏÏ¾[ÏJ¦¾åÝ‘¸×æ—÷¥Ý‘­C ôÔús¬WÝ›¦AóûÝW§ë­BùØ¾×¦Þ ID ¸M
     üqÝ‘«X÷ˆøT­C
  4. üqÝ‘«X·©ž¦§Ï§©eªíø_ùà·ü÷àÇçÝ­G

     SERVER=SAMPLE USER=subina PWD=subpw
     SERVER=COPYDB USER=subina PWD=subpw

Ç”¸¢ DB2 ùðÏ·‡Çã¯PóöñK®O@¦§÷âýà÷ˆøT­A«Ñø¥ó\IBM DB2 Administration Guide­C
  ------------------------------------------------------------------------

12.7 ýŽ 5 üû õê¬güWû§

12.7.1 ¦¡©‘Ï×¦«Ž‘ÝW§ë

õê¬gÏœÏ„ï¸¦¡©‘Ï×¦«Ž‘ÝW§ëÏÏ¦§¦¾å­C

12.7.2 DATALINK õê¬g

Ýb Solaris ÏW­ADATALINK õê¬g¾iõ@ªø¦¸¾¯ 7.1 FixPak 1 ¦§Ï@ü­¾ö­C ¾Ý¯íðnÏ@ðà
FTP ñ`ónæ{Ý­­AÝbùàú«Ï×¾¬Ñ DATALINK ·©žùtý×ÏÏøäÝ‘­A ùÇÏ„ï¸ MDTM (modtime)
®¾O­AùàÆ¾šæû¸w·©ž¦§®eÝ÷ðžõ‹©ô­­CÝp¦Gñz¾×¦§ªO¦¸¾¯ 2.6 ¦§ Solaris õ@ú~ùt
ý×­A¸×¾“Ý¢Ïœ¾]ªA MDTM ¦§ FTP Ï„ï¸­A ®hñz¯íðn¦ç¾[¦§ün‚­AÏ¤Ýp WU-FTPD­C

ñzÏœî…Ýb AS/400 ¸Mù„¾L¾ð¾xÏõô­¦§ DB2 ÷ˆ©’©wõê¬g DATALINK ¦«Ž‘­C

Ýb AS/400 ¾ð¾xùSÝüÏ„ï¸ DATALINK ðÔ­uæ—÷¥­vŽí¸Ò¦§õê¬g­C

øäÝ‘ AIX 4.2 ©­AÝbñzøäÝ‘ûwü]¦§ùØ¾×¦Þ÷ä¾Xæ{Ý­ (ASNDLCOPY) Ïõ®e­A¾ýôúÝw÷Ó
APAR IY03101 (AIX 4210-06 ®Žü§–@ AIX 4.2.1) ¦§ PTF­C üoðà PTF ¾]ªAÏF FTP
ñ`ónæ{Ý­Ï§ "modtime/MDTM" ®¾O¦§ Y2Kðž¾¨æ{Ý­­C ñì‡Çã÷àðž¾¨æ{Ý­­A«Ñ·Óªd¾¥
"modtime <file>" ®¾O¸ãô€Ý^ùà¦§®eÝ÷ðžõ‹©ô­­Aù„ÏÏ <file> ªø 2000 Ý~ 1 Ï‰ 1
Ï‚Ïõ® ¸ãðžõ‹¦§·©ž­C

Ýp¦G¾¬Ñ¦¡©‘ªO¾~ü­ CCD ¦¡©‘­ADB2 DataPropagator ú|¸I¾s ASNDLCOPY ñ`Ý­õê¬g
DATALINK ·©ž­C Ç”¸¢ ASNDLCOPY ¸M ASNDLCOPYDF ¦§ùØ¾×­A«Ñø¥ó\ÝUæ{Ý­ð¸l«X¦§
õ€ù¾­C The following restrictions apply:

   * Ï§ü­ CCD ¦¡©‘õtÝü DATALINK ®¾šý­AÝìùSÝü DATALINK ðÔ­C
   * ·œµY¾~ü­ CCD ¦¡©‘õtÝü DATALINK ðÔ­C
   * ®D·œµY CCD ¾¬Ñ¦¡©‘Ïœî…Ýü DATALINK ¦«Ž‘­C
   * ùàú«¸M¾¬ÑÝ›¦AóûªêÝP©­A¸wïµõê¬gü]¸wÏœî…Ýü DATALINK ¦«Ž‘¦§Ýùð–­C

12.7.3 LOB ððùŒ

·œµYÏ§ü­ CCD ¦¡©‘Ïœî…¸M LOB ¦«Ž‘¸M LOB ®¾šýÝüÇ”µp­C

12.7.4 üWû§õê¬g

ÝbýŽ 65 ðô­A­uüsüq¸Ò­v·ü÷à¾]ªAÏUÝCñ­õ×­G

Ýp¦GÏè¾×æ{Ý­¸MññùŒÝ›¦AóûÏœî…üsñæ­AÏè¾×æ{Ý­ú|ýžÏŒ­C

ùØ¾× AS/400 ¦§÷ˆ©’øØô“­A«Ñ«T¸wô­ûjïµô­¸ãõê¬g¦§÷ˆ©’µ`ôqÏœôW¾X 4 ÝÒ÷UÝC¬’­AÏœ
î…Ýp¾¯©¥Ï§ 69 ðôÏÏ¸ãïœ¦§ 4 MB­C
  ------------------------------------------------------------------------

12.8 ýŽ 6 üû ü]¸wõê¬g·“ûã

12.8.1 ·HüBõ¢ús (Update-anywhere) ¾ìùMñ›¾¢

Ýp¦GñzðnùØ¾×«ŽªÐø¯ï£¸M¸wïµõê¬gü]¸wÏ§ÝhûF 150 ðà¦§¸wïµõê¬gü]¸wÝùð–ùàü]¸w·HüB
õ¢úsõê¬g­A ®h¾ýôúøäÝ‘ÏUÝC¦§ DDL­A¾H®¾áññùŒÝ›¦Aóû¦§ ASN.IBMSNAP_COMPENSATE
¦¡©‘­C

   CREATE TABLE ASN.IBMSNAP_COMPENSATE (
           APPLY_QUAL char(18) NOT NULL,
           MEMBER SMALLINT,
           INTENTSEQ CHAR(10) FOR BIT DATA,
           OPERATION CHAR(1));

12.8.2 ü]¸wõê¬g·“ûã

ýŽ 95 ðô­A­uÝêÝ‘ü]¸w CD ¦¡©‘­BîµÏè¸M¦¡©‘¦ô­ÝW§ë­v¯­¸£­G DPREPL.DFT ·©žÏœ
ªOÝ¸¢ \sqllib\bin ¾¨ì­A ïNªOÝ¸¢ \sqllib\java ¾¨ì­C üoªOÏœ¾¨«T¦§­A
DPREPL.DFT Ý¸¢ \sqllib\cc ¾¨ì­C

ýŽ 128 ðô­A®OîdððùŒ¯­¸£­Güîðzú¡­u¶^ù£æ{Ý­­vúxô}óö¸×ùØ¾×­u¶^ù£æ{Ý­­võRõ‹®¾O
©­AÏ~ùØ¾×®OîdððùŒùàõRõ‹ÝC¬’­CðY¾HÝêøÒõRõ‹¨‹ôæñãøÒ­u¶^ù£æ{Ý­­v­A®h¾ÝÏœú|ùØ
¾×®OîdððùŒùàõRõ‹ÝC¬’­C
  ------------------------------------------------------------------------

12.9 ýŽ 8 üû øíÇDõP¶_

õê¬gÏ·¦Ræ{Ý­Ýb Windows 32 ÝÏ÷ùtý×¸M AIX ÏWøäÝ‘­C ñìÝb AIX ÏWøäÝ‘Ï·¦Ræ{Ý­­A
«Ñ«T¸w PATH ·“ûãš¬’Ï§ sqllib/bin ¾¨ì¾Xý{Ýb /usr/local/bin ®e­A ¾HµžõK¸M
/usr/local/bin/analyze æo¾Ö«ŽªÐ­C

õê¬gÏ·¦Ræ{Ý­Ýüùƒðà¦ç¾[¨‹¾×¦§Ç”µ„Ýr­G CT ¸M ATT­C

CT=n
     ¾uÆ¾š¶^ù£øl¶š¦¡©‘Ï§ n Ï¥Ïõ® ¦§æn¨ì­C ÝûÇ”µ„Ýrªø¨‹¾×¦§­C ðYñzùSÝü®¸w
     ÝûÇ”µ„Ýr­Aù„ûwü]ðÔªø 7 Ï¥­C

AT=n
     ¾uÆ¾šÏè¾×øl¶š¦¡©‘Ï§ n Ï¥Ïõ® ¦§æn¨ì­C ÝûÇ”µ„Ýrªø¨‹¾×¦§­C ðYñzùSÝü®¸w
     ÝûÇ”µ„Ýr­Aù„ûwü]ðÔªø 7 Ï¥­C

«dùã­G

analyze mydb1 mydb2 f=mydirectory ct=4 at=2 deepcheck q=applyqual1

ÏUÝCªø­uõê¬gÏ·¦Ræ{Ý­­vÏõüÞúsÇ”µ„Ýr÷ˆøT­G

deepcheck
     ®¸wÏ·¦Ræ{Ý­øäÝ‘÷–õûóÆ¦§Ï·¦R¾]ªAÏUÝC÷ˆøT­GCD ¸M UOW õRõ‹÷ˆøT­B DB2 for
     OS/390 ¦¡©‘¦ô­Ï·ü×¸M·œµYýà÷`­BÇ”¸¢¸wïµõê¬gü]¸w¦§¾¬ÑîµÏèÏõÏ·¦R­B ¸wïµ
     õê¬g©ô­­A¾HÏ×¸wïµõê¬gü]¸w SQL üîðzÝ­¨—¯~­C Ï·¦R¾]ªA¸ãÝü¦§Ý›¦Aóû­C Ýû
     Ç”µ„Ýrªø¨‹¾×¦§­C

lightcheck
     ®¸wÝêü›õiÏÏøœ¾hÏUÝC÷ˆøT­GASN.IBMSNAP_SUBS_COLS ¦¡©‘¸ãÝü¦«Ž‘¸£ýà­B ¸w
     ïµõê¬g¨—¯~­BÏœüW®h­B¨•§|­AÏœ¾¨«T¸×æL©Ž¦§îµÏè­C Ýû÷ˆøTÏÏ¦§µYïŒ·xÝs÷ˆú«
     ¸Mýœ¾ÖÏ@ðà÷–Ïp¦§ HTML ¨‚¾X·­C ÝûÇ”µ„Ýr¸M deepcheck Ç”µ„ÝrªêÏªñ’¾÷­C

AS/400 ¾ð¾x¦§ PTF õê¬gÝüÏ·¦Ræ{Ý­ÏuùÆ­Cüoù€ÏuùÆÝªôøÝüÇ”õê¬g·“ûã¦§÷ˆøT­AÝP
©­Aýœ¾ÖÏ@ðàô€øeù IBM ¦AøÔÏÏÏá¾N¦¡¦§ HTML ·©ž­A¾H¯ýõUøíÇD¦§ùM¸w­C ñìñoù
AS/400 ÏuùÆ­AÏU÷óAú¡¦§ PTF (ùãÝp­Aýœ®~ 5769DP2 ïNôúÏU÷ PTF SF61798 ¸×õ¢ús
¦§¦¸¾¯)­C

ús¬WÏUÝCøíÇD¸M÷¥ùMÏŠ©žÝš­u§ÇÇ›ñ’÷¥­vÏ@÷`ÏÏ­G

   øíÇD­GùSÝüõê¬gšõ¢¦§ñ­¦pÏU­AÏè¾×æ{Ý­õ×Ýùøjø‚­F
   Ïè¾×øl¶š¦¡Æ¾š STATUS=2­C
   ¸wïµõê¬gü]¸w¾]ªAÝhðàùàú«¦¡©‘­CðYðnõ‹ôiü]¸wÏÏü‘Ï@ùàú«¦¡©‘¦§¬”¶IüBýz­A
   ïNú|ªø÷àùàú«¦¡©‘¸w÷qÏ@ðàÏ§ü­ CCD ¦¡©‘ (ÝìªOÝbÏœÝP¦§¸wïµõê¬gü]¸wÏÏ)­C
   ú|û‹ùàú«¦¡©‘øæ¾Xšõ¢­AÝìýóÏJÏ§ü­ CCD ¦¡©‘¦§­uÏè¾×­væ{õ€ú|®DÝPùB¦§øäÝ‘
   (ùãÝp­AÏè¾×æ{Ý­¾iî…¸|¾¬ñãøÒ¸×ù’¾¢¸|¾¬Žýæoæ¾)­Cñqùàú«¦¡©‘õê¬gõ¢úsù
   ¾¬Ñ¦¡©‘¦§Ïè¾×æ{Ý­ú|ôiÏJøjø‚­AÝ]ªø¾ÝÝbæ¾®íÏ§ü­ CCD ¦¡©‘üQõ¢ús­C
   ðYðnøñÏŒøjø‚­AñãøÒÏ§ü­ CCD ¦¡©‘¦§Ïè¾×æ{Ý­ (¸×Žýæoú|óðPõê¬gæo¾Ö¦§ù’¾¢)­C
   Ïè¾×æ{Ý­ú|ýóÏJÏ§ü­ CCD ¦¡©‘­AùÇ©eü\ï`·“ÏÏ¦§Ïè¾×æ{Ý­üBýz¸ãÝüùàú«¦¡©‘ùà¦§šõ¢­C
   õtÝüùàú«¦¡©‘¦§¸wïµõê¬gü]¸wú|æo¾ÖÇçÝ¦§¦ª¦p­Aù„ÏÏÏ§ü­ CCD
   ¦¡©‘¾¥Ýhð®¦§Ïè¾×æ{Ý­ýóÏJ­C

  ------------------------------------------------------------------------

12.10 ýŽ 9 üû AS/400 ¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­

Ýb 178 ðô­A­uÏuõ@§èýz¦§ü’æ—­v·üÝpÏU¸ã¾š­G

ñz¾i¾Hšõ¢ûwü]¸w÷q¸×ïœù¥ðàÏH¸w÷q­C
®¾áðàÏHÏlùtý×¯­¸£­A¾ýôúï·Ïlùtý× QZSNDPR ¸RÝW­AùÇ¾BÝb QDPR ¾H¾~¦§·©ž©w®¾á­C
ÝüÇ”¸w÷q¦§šõ¢­A÷âýà÷ˆ©’«Ñø¥ó\­uOS/400 Ïuõ@§èýz V4R3­v­C

ús¬WÏUÝCÝš­u‡Çã¸MÝêÝ‘ü]¸w AS/400 ÏU DB2 DataPropagator ¦§Ýw÷Ó­v(ýŽ 178
ðô)­G

   Ýp¦GÝ]ªøø¦ôq¦§ýõøÒÝàÝü¶ˆ¸wŽv¦õ¦§øíÇD­A®hñz¾iñNûwü]¦§æ¾®íûO©ðÔñq 30 ¬W¾[ù 120­C
   ñz¾iÝbùCÝ÷¶^ù£Ïuõ@ô}¸l©šõ¢Ïuõ@­A¸×ñz¾iùØ¾×ÏUÝCæ{õ€ùàšõ¢¸ãÝüÝbÏlùtý×ÏÏøäÝ‘¦§
   Ïuõ@¦§ûwü]æ¾®íûO©ðÔ­G
   1. æo¾XÏUÝC®¾O­Að®«’ QGPL/QBATCHI ¾H®¾áús¦§ÇçõO¦®¾¢­G

         CRTDUPOBJ OBJ(QBATCH) FROMLIB(QGPL) OBJTYPE(*CLS) TOLIB(QDPR) NEWOBJ(QZSNDPR)

   2. šõ¢üÞús®ÇçõO¦§æ¾®íûO©ðÔ (ùãÝp­Ašõ¢Ýš 300 ª¡):

      CHGCLS CLS(QDPR/QZSNDPR) DFTWAIT(300)

   3. õQ¾×ús®ÇçõOõ¢úsÏlùtý×¯­¸£ QDPR/QZSNDPR Ï§¦§÷“©|æn¨ì­G
      CHGRTGE SBSD(QDPR/QZSNDPR) SEQNBR(9999) CLS(QDPR/QZSNDPR)

ýŽ 194 ðô¦§­uùØ¾×õRøœýõøÒÏ‚¯xñæÝªóûæýõ“ñ`Ý­­v·üù™ÏJüoðà¾yÏl­G ðYñzýóøœõRøœ
ýõøÒÏ‚¯xñæÝªóûæýõ“ñ`Ý­­A«Ñ«T¸w¾×¸¢ùàú«¦¡©‘¦§¸ãÝüýõøÒÏ‚¯xªãÝü DLTRCV(*NO)­C

Ýb 195 ðô­AADDEXITPGM ®¾Oø¥¬’·ü¦ù£ÏUÝC¸ã¾š­G

   ADDEXITPGM EXITPNT(QIBM_QJO_DLT_JRNRCV)
                FORMAT(DRCV0100)
                PGM(QDPR/QZSNDREP)
                PGMNBR(*LOW)
                CRTEXITPNT(*NO)
                PGMDTA(65535 10 QSYS)

  ------------------------------------------------------------------------

12.11 ýŽ 10 üû OS/390 ¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­

ÝbýŽ 10 üûÏÏõ¢úsÏUÝCªq÷ù­G

12.11.1 DB2 DataPropagator for OS/390 ¦§¾ìùMñ›¾¢

ñz¾ýôúùÆü’ DB2 for OS/390 ¦¸¾¯ 5­BDB2 for OS/390 ¦¸¾¯ 6 ¸× DB2 for OS/390
¦¸¾¯ 7­AÏ~î…øäÝ‘ DB2 DataPropagator for OS/390 ¦¸¾¯ 7 (V7)­C

12.11.2 OS/390 ÏW¦§ UNICODE ¸M ASCII «s«XÏŠ¦k

DB2 DataPropagator for OS/390 V7 Ï„ï¸ UNICODE ¸M ASCII «s«XÏŠ¦k­C ðYðnô}æo
ús¦§«s«XÏŠ¦k­Añz¾ýôúùÆü’ DB2 for OS/390 V7­A Ýà¾B¾ýôúÏƒøÒ®¾á¸×¶…ï® DB2
DataPropagator ùàú«­B¾¬ÑÏ×ññùŒ¦¡©‘­A õéðÞñNú|ÝbÏUÝCÝU÷`ÏÏ¯­¸£­CÏœûL­AõYùØ
ñzùSÝüðžõ‹¾“Ý¢«s«XÏŠ¦k­Añzý{Ýs¦§ õê¬g·“ûãñNùØ¾× DB2 DataPropagator for
OS/390 V7­C

12.11.2.1 ¨‹óš«s«XÏŠ¦k

ðYñz¦§ùàú«­BCD Ï×¾¬Ñ¦¡©‘ùØ¾×ªêÝP¦§«s«XÏŠ¦k­Añz¾i¾HñNõê¬g·“ûãÏÏ¦§÷ˆ©’¶…ï®¯í
ùDðøÝšüÞõC­C û‹¦¡©‘¨‹óš«s«XÏŠ¦k©­A«Ñ¨¡ï`ü‘Ï@ CCSID üW®h­G ¦¡©‘¦ô­ÏÏ¦§ÝrÏ÷
÷ˆ©’¾i¾H¾× ASCII­BUNICODE ¸× EBCDIC ùà«s«X­C ¦¡©‘¦ô­Ï§¦§¸ãÝü¦¡©‘¾ýôúùØ¾×ªê
ÝP¦§«s«XÏŠ¦k­CSQL üîðzÝ­ÏÏ¸ãÝü¦¡©‘¦§«s«XÏŠ¦k¾ýôúªêÝP­CÝP©­AñzÝb·Óæ›Ï×æýÝX
ÏÏ¸ã¾×¦§¾çü­¦¡©‘¾ýôúªêÝP¦§«s«XÏŠ¦k­C

ðY¾¬¨¡ï`ü‘Ï@ CCSID üW®h­A®hÝbüsæý¸×øäÝ‘ïµô­­ADB2 ñNú|ø¯ï£ûHüWùÇô€Ý^ SQLCODE
-873­Cðçù€¦¡©‘·ü÷àªO ASCII ¸× UNICODE­Aæ›ñz¦§¾D/ñqª[§cÝà¸w­C îSõOÝa­Aú¡¨‹óš
¦¡©‘¦§«s«XÏŠ¦k©­A«Ñ¨¡ï`üoù€üW®h­G

   * DB2 for OS/390 ÏW¦§ùàú«¸×¾¬Ñ¦¡©‘¾i¾HªO EBCDIC­BASCII ¸× UNICODE­C ¾Ý
     ðÞ¾i¾HÝbùØ¾×¾“Ý¢Ï„ï¸¦§ DBMS (DB2 ùtÝC­A¸×ùÆÝü DataJoiner ¦§®D DB2 ùt
     ÝC) ÏÏªêÝP¸×ÏœÝP«s«XÏŠ¦k¦§¦¡©‘Ïõô­«’¯s­C
   * Ýb DB2 for OS/390 ùàú«Ý›¦AóûÏW­AªêÝPÝ›¦AóûÏW¸ãÝü CD­BUOW­BænøOÏ×õRõ‹ññ
     ùŒ¦¡©‘¾ýôúùØ¾×ªêÝP¦§«s«XÏŠ¦k­Cªø«T®OÏ@ðP¸Ò­A«ÑøÔ¾ý¸£«T®¸w«s«XÏŠ¦k­C
   * ªêÝPññùŒÝ›¦AóûÏW¦§¸ãÝüññùŒ¦¡©‘ (ASN.IBMSNAP_SUBS_xxxx) ¾ýôúùØ¾×ªêÝP¦§
     «s«XÏŠ¦k­C
   * ù„¾ÝññùŒ¦¡©‘¾iùØ¾×¾“Ý¢«s«XÏŠ¦k­FÏœûL­A®Žü ASN.IBMSNAP_CRITSEC ¦¡©‘®O
     îd EBCDIC­C

12.11.2.2 ü]¸w«s«XÏŠ¦k

ðYðnû‹¦¡©‘®¸wóAú¡¦§«s«XÏŠ¦k­A«Ñðžõ‹¾×ùàýœ¾Ö¦¡©‘¦§ SQL­G

   * ¾HóAú¡¦§«s«XÏŠ¦k®¾áús¦§ùàú«¸M¾¬Ñ¦¡©‘­A ¸×šõ¢ý{Ýs¾¬ÑÏ×ùàú«¦¡©‘¦§«s
     «XÏŠ¦k­C®Žüñzšõ¢ý{Ýs¦¡©‘¦§«s«XÏŠ¦kÏõ®eøñÏŒ­u¶^ù£æ{Ý­­v¸M­uÏè¾×æ{
     Ý­­v­AæM® ¾HõNô}óöÏŠÝ­ñãøÒ­u¶^ù£æ{Ý­­vùÇð®úsñãøÒ­uÏè¾×æ{Ý­­v­Cšõ¢ý{Ýs
     ¦¡©‘¦§«s«XÏŠ¦k­G
       1. ùØ¾× Reorg Ï«¾×æ{Ý­«’¯sý{Ýs¦§¦¡©‘­C
       2. ñÓñ¢ý{Ýs¦§¦¡©‘­C
       3. ®¸wús«s«XÏŠ¦kùàð®®¦¡©‘­C
       4. ùØ¾× Load Ï«¾×æ{Ý­ñNð¸l÷ˆ©’÷ÏJús¦¡©‘ÏÏ­C

     ÝüÇ” Load ¸M Reorg Ï«¾×æ{Ý­¦§÷âýà÷ˆøT­A«Ñø¥ó\ DB2 Universal Database
     for OS/390 Utility Guide and Reference­C
   * ¾HóAú¡¦§«s«XÏŠ¦k®¾áúsññùŒ¦¡©‘¸×ðžõ‹ý{Ýs¦¡©‘¦§«s«XÏŠ¦k­C

     DPCNTL.MVS ·Ó¦ç¸¢ DB2 for OS/390 ¦§ sqllib\samples\repl ÏÏ­A ¾Ý¾]õt®
     ¾áññùŒ¦¡©‘¦§¬’ðà CREATE TABLE üîðzÝ­­Cû‹¸¢¾ýôúªO ASCII ¸× UNICODE ¦§¦¡
     ©‘Ýàù¾­]ùãÝp ASN.IBMSNAP_REGISTER ¸M ASN.IBMSNAP_PRUNCNTL­^­A «Ñ¾[ÏJ
     CCSID ASCII ¸× CCSID UNICODE Ç”µ„Ýr­AÝpÏUÝC«dùã¸ã¾š­C

     CREATE TABLE ASN.IBMSNAP_PRUNCNTL (
       TARGET_SERVER      CHAR( 18)              NOT NULL,
       TARGET_OWNER       CHAR( 18)              NOT NULL,
       TARGET_TABLE       CHAR( 18)              NOT NULL,
       SYNCHTIME          TIMESTAMP,
       SYNCHPOINT         CHAR( 10)              FOR BIT DATA,
       SOURCE_OWNER       CHAR( 18)              NOT NULL,
       SOURCE_TABLE       CHAR( 18)              NOT NULL,
       SOURCE_VIEW_QUAL   SMALLINT               NOT NULL,
       APPLY_QUAL         CHAR( 18)              NOT NULL,
       SET_NAME           CHAR( 18)              NOT NULL,
       CNTL_SERVER        CHAR( 18)              NOT NULL,
       TARGET_STRUCTURE   SMALLINT               NOT NULL,
       CNTL_ALIAS         CHAR(  8)
             )  CCSID UNICODE
     DATA CAPTURE CHANGES
                IN TSSNAP02;

     ðYðnðžõ‹ý{Ýs¦§ññùŒ¦¡©‘¸M CD ¦¡©‘­A«ÑùØ¾× Reorg ¸M Load Ï«¾×æ{Ý­­C
   * ú¡®¾áúsõê¬gùàú«¸×¸wïµõê¬gü]¸w©­A«Ñðžõ‹§èýzÏuùÆ¸ãýœ¾Ö¦§ SQL ·©ž­A ¾H
     ®¸wóAú¡¦§«s«XÏŠ¦k­CÝû SQL ·©žùÆÝü¬’ðà CREATE TABLE üîðzÝ­­A ¾i¾×ùàÏ·
     õOøwû‹õê¬gùàú«Ï×¸wïµõê¬gü]¸w®¾á CD ¸M¾¬Ñ¦¡©‘­C «ÑÝbóAú¡Ý÷m¾[ÏJÇ”µ„
     Ýr CCSID ASCII ¸× CCSID UNICODE­C ùãÝp­G

     CREATE TABLE   user1.cdtable1 (
       employee_name   varchar,
       employee_age    decimal
         )  CCSID UNICODE;

     DB2 UDB for OS/390 SQL Reference ¾]õt CCSID ¦§÷âýà÷ˆøT­C

  ------------------------------------------------------------------------

12.12 ýŽ 11 üû UNIX ¾ð¾x¦§¶^ù£æ{Ý­¸MÏè¾×æ{Ý­

12.12.1 Ýb UNIX ¸M Windows ÏWü]¸w­u¶^ù£æ{Ý­­v¸M­uÏè¾×æ{Ý­­v¦§·“ûãš¬’

ðYñzùØ¾×ûwü]Ýr«XðôðÔ¾H¾~¦§Ýr«Xðô®¾áùàú«÷ˆ©’©w­A«ÑñN DB2CODEPAGE ·“ûãš¬’ü]
ªø÷àÝr«Xðô­C ÝüÇ”ü]¸w DB2CODEPAGE Ïõ®eù£ñoÝr«XðôðÔ¦§÷âýà÷ˆøT­A«Ñø¥ó\ DB2
Administration Guide­C­u¶^ù£æ{Ý­­v¾ýôúÝb¯P÷ˆ©’©w (¶^ù£æ{Ý­Ýêù„ÏÏ¶^ù£÷ˆ©’)
ªêÝP¦§Ýr«XðôÏÏøäÝ‘­CDB2 ñq­u¶^ù£æ{Ý­­vøäÝ‘¸ãÝb¦§õ@¾×ÏÏ·“ûãù£ño­u¶^ù£æ{Ý­­v
Ýr«Xðô­CðY¾¬ü]¸w DB2CODEPAGE­ADB2 ú|ñqõ@ú~ùtý×ù£ñoÝr«XðôðÔ­C ðYñz®¾á÷ˆ©’©w
©ªOùØ¾×ûwü]Ýr«Xðô­A®hðl¾ÖÝêõ@ú~ùtý×¦§ðÔû‹­u¶^ù£æ{Ý­­vÝàù¾ªO¾¨«TðÔ­C
  ------------------------------------------------------------------------

12.13 ýŽ 14 üû ¦¡©‘æý§c

Ýb 339 ðô­AýK¾[ÏUÝC¾yÏlÝšðÔªø 2 ¦§ STATUS ¦«Ž‘¯­¸£­G

   Ýp¦GñzùØ¾×Ï§ü­ CCD ¦¡©‘­A¾B®—Ž•ÝbÏè¾×øl¶š¦¡¦§¦ª§A¦«Ž‘ÏÏñoù "2" ðÔ­A
   «ÑÝš­uýŽ 8 üû­GøíÇDõP¸w­vø¥úà­uøíÇD­GùSÝüõê¬gšõ¢¦§ñ­¦pÏU­AÏè¾×æ{Ý­õ×Ýùøjø‚­F
   Ïè¾×øl¶š¦¡Æ¾š STATUS=2­v­C

  ------------------------------------------------------------------------

12.14 ýŽ 15 üû ¶^ù£æ{Ý­¸MÏè¾×æ{Ý­øT©õ

øT©õ ASN0017E ·üõ‹ªø­G

ASN0017E

­u¶^ù£æ{Ý­­væoý{ŽYð®¦§Ï§ü­¨—¯~­AæL¦kæo¾X¾¨«T¦§¨—¯~øT©õ­C ñ`Ý­ÝW§ëªø
routine­CÝ^¶Ñ«Xªø return_code­C

ús¬WÏUÝC÷ˆ©’ÝšøT©õ ASN1027S­G

ASN1027S

®¸wÏàÝhÏj®ª¦®¾¢ (LOB) ¦«Ž‘­C¨—¯~«Xªø <error_code>­C

¯­¸£­Gû‹¸wïµõê¬gü]¸wÝùð–®¸wÏFÏàÝhÏj®ª¦®¾¢ (BLOB­BCLOB ¸× DBCLOB) ¦«Ž‘­C¾i
©eü\¦§üÞÏj¦«Ž‘¬’ªø 10­C

ùØ¾×¦ÞÝ^·ü­GÝê¸wïµõê¬gü]¸wÝùð–øœ¾hûLÝh¦§Ïj®ª¦®¾¢¦«Ž‘­C

øT©õ ASN1048E ·üÝpÏU¸ã¾š­G

ASN1048E

­uÏè¾×æ{Ý­­vï`·“¦§øäÝ‘¾½ñ¥­C÷âýà÷ˆ©’­A«Ñø¥ó\Ïè¾×øl¶š¦¡­G<text>

¯­¸£­G­uÏè¾×æ{Ý­­vï`·“¾½ñ¥­CÝbøT©õÏÏ­A <text> ¸w÷q <target_server>­B
<target_owner­B target_table­Bstmt_number> Ï× <cntl_server>­C

ùØ¾×¦ÞÝ^·ü­G·Óªd¬f©™øl¶š¦¡©‘¦§ APPERRM Ž‘Ý­A ¾H«T¸w­uÏè¾×æ{Ý­­vï`·“¦§¾½ñ¥
ðÝ]­C
  ------------------------------------------------------------------------

12.15 ¦ç¨ì A. ñq·ü¾×æ{Ý­Ï§ñãøÒ¶^ù£æ{Ý­¸MÏè¾×æ{Ý­

Ýb 399 ðô­A¨—¯~¾Xý{Ýb«dùãñ`Ý­¦§¯­¸£Ï§­A÷à«dùãñ`Ý­ñãøÒ¶^ù£æ{Ý­¸MÏè¾×æ{Ý­­A
ÝìªO­A«dùã¦§Ýr«XªO¾¨«T¦§­C«dùã¦§® ¾bü­¯PÏè¾×æ{Ý­ø¥¬’ÝüÇ”­Aµ”æM¯­¸£¦¡¾š¾Ý¸M
¶^ù£æ{Ý­ø¥¬’ÝüÇ”­C

ñz¾i¾HÝê¾HÏU¾¨ì·•ñoÏè¾×æ{Ý­¸M¶^ù£æ{Ý­¦§«dùãÏ×ÝUÝê¦§ make ·­G

   For NT - sqllib\samples\repl
   For UNIX - sqllib/samples/repl

  ------------------------------------------------------------------------

System Monitor Guide and Reference(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

13.1 db2ConvMonStream

In the Usage Notes, the structure for the snapshot variable datastream type
SQLM_ELM_SUBSECTION should be sqlm_subsection.
  ------------------------------------------------------------------------

Troubleshooting Guide(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

14.1 Starting DB2 on Windows 95, Windows 98, and Windows ME When the User
Is Not Logged On

For a db2start command to be successful in a Windows 95, Windows 98, or
Windows Millennium Edition (ME) environment, you must either:

   * Log on using the Windows logon window or the Microsoft Networking
     logon window
   * Issue the db2logon command (see note (NOTE_1) for information about
     the db2logon command).

In addition, the user ID that is specified either during the logon or for
the db2logon command must meet DB2's requirements (see note (NOTE2)).

When the db2start command starts, it first checks to see if a user is
logged on. If a user is logged on, the db2start command uses that user's
ID. If a user is not logged on, the db2start command checks whether a
db2logon command has been run, and, if so, the db2start command uses the
user ID that was specified for the db2logon command. If the db2start
command cannot find a valid user ID, the command terminates.

During the installation of DB2 Universal Database Version 7 on Windows 95,
Windows 98, and Windows ME, the installation software, by default, adds a
shortcut to the Startup folder that runs the db2start command when the
system is booted (see note (NOTE_1) for more information). If the user of
the system has neither logged on nor issued the db2logon command, the
db2start command will terminate.

If you or your users do not normally log on to Windows or to a network, you
can hide the requirement to issue the db2logon command before a db2start
command by running commands from a batch file as follows:

  1. Create a batch file that issues the db2logon command followed by the
     db2start.exe command. For example:

       @echo off
       db2logon  db2local /p:password
       db2start
       cls
       exit

  2. Name the batch file db2start.bat, and store it in the /bin directory
     that is under the drive and path where you installed DB2. You store
     the batch file in this location to ensure that the operating system
     can find the path to the batch file.

     The drive and path where DB2 is installed is stored in the DB2
     registry variable DB2PATH. To find the drive and path where you
     installed DB2, issue the following command:

       db2set  -g  db2path

     Assume that the db2set command returns the value c:\sqllib. In this
     situation, you would store the batch file as follows:

       c:\sqllib\bin\db2start.bat

  3. To start DB2 when the system is booted, you should run the batch file
     from a shortcut in the Startup folder. You have two options:
        o Modify the shortcut that is created by the DB2 installation
          program to run the batch file instead of db2start.exe. In the
          preceding example, the shortcut would now run the db2start.bat
          batch file. The shortcut that is created by DB2 installation
          program is called DB2 - DB2.lnk, and is located in
          c:\WINDOWS\Start Menu\Programs\Start\DB2 - DB2.lnk on most
          systems.
        o Add your own shortcut to run the batch file, and delete the
          shortcut that is added by the DB2 installation program. Use the
          following command to delete the DB2 shortcut:

            del  "C:\WINDOWS\Start Menu\Programs\Startup\DB2 - DB2.lnk"

          If you decide to use your own shortcut, you should set the close
          on exit attribute for the shortcut. If you do not set this
          attribute, the DOS command prompt is left in the task bar even
          after the db2start command has successfully completed. To prevent
          the DOS window from being opened during the db2start process, you
          can create this shortcut (and the DOS window it runs in) set to
          run minimized.
          Note:
               As an alternative to starting DB2 during the boot of the
               system, DB2 can be started prior to the running of any
               application that uses DB2. See note (NOTE5) for details.

If you use a batch file to issue the db2logon command before the db2start
command is run, and your users occasionally log on, the db2start command
will continue to work, the only difference being that DB2 will use the user
ID of the logged on user. See note (NOTE_1) for additional details.

Note:

  1. The db2logon command simulates a user logon. The format of the
     db2logon command is:

       db2logon userid  /p:password

     The user ID that is specified for the command must meet the DB2 naming
     requirements (see note (NOTE2) for more information). If the command
     is issued without a user ID and password, a window opens to prompt the
     user for the user ID and password. If the only parameter provided is a
     user ID, the user is not prompted for a password; under certain
     conditions a password is required, as described below.

     The user ID and password values that are set by the db2logon command
     are only used if the user did not log on using either the Windows
     logon window or the Microsoft Networking logon window. If the user has
     logged on, and a db2logon command has been issued, the user ID from
     the db2logon command is used for all DB2 actions, but the password
     specified on the db2logon command is ignored

     When the user has not logged on using the Windows logon window or the
     Microsoft Networking logon window, the user ID and password that are
     provided through the db2logon command are used as follows:
        o The db2start command uses the user ID when it starts, and does
          not require a password.
        o In the absence of a high-level qualifier for actions like
          creating a table, the user ID is used as the high-level
          qualifier. For example:
            1. If you issue the following: db2logon db2local
            2. Then issue the following: create table tab1

               The table is created with a high-level qualifier as
               db2local.tab1.

          You should use a user ID that is equal to the schema name of your
          tables and other objects.
        o When the system acts as client to a server, and the user issues a
          CONNECT statement without a user ID and password (for example,
          CONNECT TO TEST) and authentication is set to server, the user ID
          and password from the db2logon command are used to validate the
          user at the remote server. If the user connects with an explicit
          user ID and password (for example, CONNECT TO TEST USER userID
          USING password), the values that are specified for the CONNECT
          statement are used.

  2. In Version 7, the user ID that is either used to log on or specified
     for the db2logon command must conform to the following DB2
     requirements:
        o It cannot be any of the following: USERS, ADMINS, GUESTS, PUBLIC,
          LOCAL, or any SQL reserved word that is listed in the SQL
          Reference.
        o It cannot begin with: SQL, SYS or IBM
        o Characters can include:
             + A through Z (Windows 95, Windows 98, and Windows ME support
               case-sensitive user IDs)
             + 0 through 9
             + @, #, or $

  3. You can prevent the creation of the db2start shortcut in the Startup
     folder during a customized interactive installation, or if you are
     performing a response file installation and specify the
     DB2.AUTOSTART=NO option. If you use these options, there is no
     db2start shortcut in the Startup folder, and you must add your own
     shortcut to run the db2start.bat file.

  4. On Windows 98 and Windows ME an option is available that you can use
     to specify a user ID that is always logged on when Windows 98 or
     Windows ME is started. In this situation, the Windows logon window
     will not appear. If you use this option, a user is logged on and the
     db2start command will succeed if the user ID meets DB2 requirements
     (see note (NOTE2) for details). If you do not use this option, the
     user will always be presented with a logon window. If the user cancels
     out of this window without logging on, the db2start command will fail
     unless the db2logon command was previously issued, or invoked from the
     batch file, as described above.

  5. If you do not start DB2 during a system boot, DB2 can be started by an
     application. You can run the db2start.bat file as part of the
     initialization of applications that use DB2. Using this method, DB2
     will only be started when the application that will use it is started.
     When the user exits the application, a db2stop command can be issued
     to stop DB2. Your business applications can start DB2 in this way, if
     DB2 is not started during the system boot.

     To use the DB2 Synchronizer application or call the synchronization
     APIs from your application, DB2 must be started if the scripts that
     are download for execution contain commands that operate either
     against a local instance or a local database. These commands can be in
     database scripts, instance scripts, or embedded in operating system
     (OS) scripts. If an OS script does not contain Command Line Processor
     commands or DB2 APIs that use an instance or a database, it can be run
     without DB2 being started. Because it may be difficult to tell in
     advance what commands will be run from your scripts during the
     synchronization process, DB2 should normally be started before
     synchronization begins.

     If you are calling either the db2sync command or the synchronization
     APIs from your application, you would start DB2 during the
     initialization of your application. If your users will be using the
     DB2 Synchronizer shortcut in the DB2 for Windows folder to start
     synchronization, the DB2 Synchronization shortcut must be modified to
     run a db2sync.bat file. The batch file should contain the following
     commands to ensure that DB2 is running before synchronization begins:

       @echo off
       db2start.bat
       db2sync.exe
       db2stop.exe
       cls
       exit

     In this example, it is assumed that the db2start.bat file invokes the
     db2logon and db2start commands as described above.

     If you decide to start DB2 when the application starts, ensure that
     the installation of DB2 does not add a shortcut to the Startup folder
     to start DB2. See note (NOTE3) for details.

  ------------------------------------------------------------------------

14.2 Chapter 2. Troubleshooting the DB2 Universal Database Server

Under the "Locking and Deadlocks" section, under the "Applications Slow or
Appear to Hang" subsection, change the description under "Lock waits or
deadlocks are not caused by next key locking" to :

Next key locking guarantees Repeatable Read (RR) isolation level by
automatically locking the next key for all INSERT and DELETE statements and
the next higher key value above the result set for SELECT statements. For
UPDATE statements that alter key parts of an index, the original index key
is deleted and the new key value is inserted. Next key locking is done on
both the key insertion and key deletion. It is required to guarantee ANSI
and SQL92 standard RR, and is the DB2 default.

Examine snapshot information for the application. If the problem appears to
be with next key locking, you can set the DB2_RR_TO_RS option on if none of
your applications rely on Repeatable Read (RR) behavior and it is
acceptable for scans to skip over uncommitted deletes.

When DB2_RR_TO_RS is on, RR behavior cannot be guaranteed for scans on user
tables because next key locking is not done during index key insertion and
deletion. Catalog tables are not affected by this option.

The other change in behavior is that with DB2_RR_TO_RS on, scans will skip
over rows that have been deleted but not committed, even though the row may
have qualified for the scan.

For example, consider the scenario where transaction A deletes the row with
column1=10 and transaction B does a scan where column1>8 and column1<12.

With DB2_RR_TO_RS off, transaction B will wait for transaction A to commit
or rollback. If it rolls back, the row with column1=10 will be included in
the result set of transaction B's query.

With DB2_RR_TO_RS on, transaction B will not wait for transaction A to
commit or rollback. It will immediately receive query results that do not
include the deleted row.

Do not use this option if you require ANSI and SQL92 standard RR or if you
do not want scans to skip uncommitted deletes.
  ------------------------------------------------------------------------

Ýb 64 ÝÏ÷¦§¾ð¾xÏWùØ¾× DB2 Universal Database

  ------------------------------------------------------------------------

15.1 ýŽ 5 üû ª[§c

15.1.1 LOCKLIST

ÏUÝC÷ˆøT·ü÷à¾[ù­u¦¡ 2­v­C

ø¥¬’         Ïõ®e¦§ÏWðð               ý{Ý‘¦§ÏWðð
LOCKLIST     60000                    524288

15.1.2 shmsys:shminfo_shmmax

Ýb 64 ÝÏ÷ Solaris õ@ú~ùtý×ÏW¦§ DB2 ùØ¾×¦Þ·üæ›¯íðn¬W¾[ /etc/system ÏÏ
"shmsys:shminfo_shmmax" ¦§ðÔ­A ¾Høt÷mÏj¦§÷ˆ©’©wÝ@¾×øOóÑ‚ýå­C DB2 for UNIX
õ™ütÏJ¦— ©¥ÏÏ®Žüø¥¬’¾iü]ªø "óöóûÏÏûˆ‚ RAM ¦§ 90%­Aü‘ÝªøÝÏ÷ýå"­C üoôæ®
Žüû‹¸¢ 64 ÝÏ÷ªIÝ‘Ï@¬ÓÝü©Ž­C

æMÝà­AÝb DB2 for UNIX õ™ütÏJ¦— ©¥ÏÏ¦§ÏUÝC®ŽüÝüøíÇD­G û‹¸¢ó™ÝüôWûL 4 GB RAM
¦§ 32 ÝÏ÷ùtý×Ýàù¾ (Ýb Solaris õ@ú~ùtý×ÏWµ`Ý@üÞÝh¾iù 64 GB)­A Ýp¦GùØ¾×¦ÞñN
shmmax ðÔü]¸wªøÏ@ðàÏj¸¢ 4 GB ¦§¬’Ýr­A ùÇ¾BªOùØ¾× 32 ÝÏ÷¦§©™Ïá­AÝà©™Ïá¾uú|
ªíù¬’Ýr¦§®  32 ÝÏ÷­A Ýü©ú|üyÝù shmmax ¦§ðÔ®Dñ`¦§Ïp­C
  ------------------------------------------------------------------------

15.2 ýŽ 6 üû ððùŒ

¾®eÝb 64 ÝÏ÷¦§õ@ú~ùtý×ÏWùSÝü LDAP Ï„ï¸­C

32 ÝÏ÷Ï× 64 ÝÏ÷¦§÷ˆ©’©wæL¦k®¾áÝbªêÝP¦§÷“©|ÏW­C ùãÝp­AÝp¦GÝüÏ@ðà 32 ÝÏ÷
¦§÷ˆ©’©wÝ¸¢ <somepath>­A®h­G

   db2 create db <somedb> on <somepath>

Ýp¦GªOñq 64 ÝÏ÷¦§©žùãæo¾X®¾O­Aú|ñoùüo¬Ó¦§¨—¯~øT©õ "SQL10004C Ýsù£÷ˆ©’©w
¾¨ì©æo¾Ö I/O ¨—¯~­C"
  ------------------------------------------------------------------------

XML Extender Administration and Programming(æLÏÏÏ†¦¸)

Release Notes for the IBM DB2 XML Extender can be found on the DB2 XML Web
site: http://www-4.ibm.com/software/data/db2/extenders/xmlext/library.html
  ------------------------------------------------------------------------

MQSeries

¾¯÷`¯­¸£ÝpÝ¢ùØ¾× DB2 Ï× MQSeries ùà®§cæýÝXô€øT¯P÷ˆ©’©wÝsù£¦§·ü¾×æ{Ý­­C ¾¯
÷`¦§æJ¶IÝbÏ@ùtÝC¦§¾\î…­A¯P­uùØ¾×¦Þ¸w÷q¦§¾\î… (UDF)­vÇçÝ­A¾Ý¾iî…ÏwÝb DB2
Universal Database ¦¸¾¯ 7.2 ÏÏ¨‹¾×¸ÒÝañã¾×­C ùØ¾×üoù€ø•¾¯¦§¾\î…­A¾iî…¾i¾HÏ„
ï¸Ïj«dü•¦§·ü¾×æ{Ý­­Añq¶ýÝ­ù’¾¢üq¦óù÷ˆ©’ðš·x­C

ÝüÇ”÷ˆ©’ðš·x·ü¾×æ{Ý­¦§÷âýà÷ˆøT­A«Ñø¥ó\22.15, MQ Series ¯P­u÷ˆ©’ðš·xÏÏÏá­v¦§
óÆÝX­C
  ------------------------------------------------------------------------

17.1 Ýw÷Ó¯Pª[§c DB2 MQSeries Function

¾¯÷`¯­¸£ÝpÝ¢ª[§c DB2 ·“ûã¾HùØ¾× DB2 MQSeries Function­C ¾uðnñzÝù¾\õûÝùÏUÝC
æ{õ€­AïN¾i¾Hñq SQL ùØ¾× DB2 MQSeries Function­C Ç”¸¢üoù€¾\î…¦§¯­¸£­A«ÑÝš
­u¦¸¾¯¦`úNù’ôæ­v¦§ SQL Reference Ï@÷`­C Ç”¸¢¦ç¾[÷ˆøT­A¾]ªAüÞús¦§Ï†¾¢­Bïœ¾š
Ï×îæüZ­A«ÑÝš http://www.ibm.com/software/data/integration/MQSeries­C

ª[§c¯Pñã¾× DB2 MQSeries Function ¦§ø•¾¯æ{õ€ªø­G

  1. Ýw÷Ó MQSeries­C
  2. Ýw÷Ó MQSeries AMI­C
  3. ñã¾×¯Pª[§c DB2 MQSeries Function

Ýû¾~­AðYðnùØ¾× DB2 MQSeries Function ïœù¥¦§æoõG/ðqó\¾\î…­AñzÏ]¾ýôúÝw÷Ó
MQSeries Integrator ¸× MQSeries Publish/Subscribe Function­C Ç”¸¢ MQSeries
Integrator ¦§÷ˆøT­A«ÑÝš
http://www.ibm.com/software/ts/mqseries/integrator­CÇ”¸¢ MQSeries
Publish/Subscribe ¾\î…¦§÷ˆøT­A«ÑÝš§Çç 3 ÏU¦§
http://www.ibm.com/software/ts/mqseries/txppacs­C

17.1.1 Ýw÷Ó MQSeries

ýŽÏ@ðàùB’J«Ñ«T¸w MQSeries ¦¸¾¯ 5.2 ÏwÝw÷Ó¸¢ñz¦§ DB2 Ý›¦AóûÏW­CðYñzÏwÝw÷ÓÝû
¦¸¾¯¦§ MQSeries­A«Ñ÷äÝšÏUÏ@ùB’J­uÝw÷Ó MQSeriesy AMI­v­C DB2 ¦¸¾¯ 7.2 ¾]ªA
DB2 ùØ¾×¦§ MQSeries Ý›¦AóûÏõø’¾¯­C Ýw÷Ó MQSeries ¸×Ïîý{Ýs¦§ MQSeries Ýw÷Ó
ÏõîS¸w¾ð¾x®¾O­A¾iÝbîS¸w¦§¾ð¾x­uõ™ütÏJ¦—­v©¥ŽyÏÏõ„ù­Aù„ÝÝb
http://www.ibm.com/software/ts/mqseries/library/manuals­C«Ñ«T¸wú¡ñzôiÝ‘Ýw÷Ó
æ{õ€©­Aðnü]¸wûwü]ÝŒÝC§èýzæ{Ý­­C

17.1.2 Ýw÷Ó MQSeries AMI

ÏUðàùB’JªOÝw÷Ó MQSeries ·ü¾×æ{Ý­ô€øTÏôðñ (AMI)­C üoªO MQSeries æ{Ý­ü]ðpÏôðñ
¦§ø’·ÝW­A¾Ýïœù¥§èýzÏ×æ{Ý­ü]ðpÏ@ðàýMú­¦§ûj¶ö­C DB2 MQSeries Function ¯íðnÝû
Ïôðñ¦§Ýw÷Ó­CðY MQSeries AMI ÏwÝw÷ÓÝbñz¦§ DB2 Ý›¦AóûÏW­A«Ñ÷äÝšÏUÏ@ùB’J ­uñã
¾× DB2 MQSeries Function­v­CðY¸|¾¬Ýw÷Ó MQSeries AMI­A®hñz¾i¾Hñq DB2 7.2 ïœ
ù¥¦§Ýw÷Ó©M÷Óün‚ùàÝw÷Ó­A¸×ñq MQSeries Ï„ï¸©M÷Óün‚§“î÷
http://www.ibm.com/software/ts/mqseries/txppacs­AÏU÷ AMI ø’¾¯­C ñz¾i¾HÝb
­u§Çç 3 - ýœ®~ø’·ÝW­vÏUõ„ù AMI­CªøÏFÏŠ®Kø_ùœ­A õéðÞïœù¥ñz DB2 ¦§
MQSeries AMI Ïõø’¾¯­CÝû·©žÝÝb sqllib/cfg ¾¨ìÏÏ­CÝû·©ž¦§ÝW§ëªOõ@ú~ùtý×ªê
ùÞôæ­G
 AIX ¦¸¾¯ 4.3 Ï×õ¢ús¦¸¾¯             ma0f_ax.tar.Z
 HP-UX                               ma0f_hp.tar.Z
 Solaris õ@ú~·“ûã                    ma0f_sol7.tar.Z
 Windows 32 ÝÏ÷                     ma0f_nt.zip

¨¡ï` AMI Readme ·ÏÏ¶ýðz¦§¾¨ñ` AMI Ýw÷Óæ{õ€­A÷à·Ýb·œµYÝw÷ÓªMûü·ÏÏ­C

17.1.3 ñã¾× DB2 MQSeries Function

ÝbÝûùB’Jïµô­­AñzñNª[§cùÇñã¾× DB2 MQSeries Function ¦§÷ˆ©’©w­C
enable_MQFunctions Ï«¾×æ{Ý­ªOÏ@ðà¬u¸Ò¦§®¾O­Aú|¾ì·ÓªdÏwü]¸wóAú¡¦§ MQSeries
·“ûã­AæM® Ýw÷ÓùÇ®¾á DB2 MQSeries ¾\î…¦§ûwü]ª[§c­A¾Hüoù€¾\î…ñã¾×®¸w¦§÷ˆ©’
©w­AùÇ«T¯{ª[§cûBõ@¾¨ñ`­C

  1. øwû‹ Windows NT ¸× Windows 2000­A«ÑÝšùB’J 5­C
  2. Ýb UNIX ü]¸w÷sýå­GðYñzÝb UNIX ÏWñã¾×üoù€¾\î…­Añz¾ýôú¾ìñN DB2 ©žùãó™Ýü
     ¦Þ (üqñ`ªO de2inst1) Ï×¯Pûj¶ö UDF ªêÇ”¦§ùØ¾×¦Þ ID (üqñ`ªO db2fenc1)­A
     ús¬Wù MQSeries ÷sýå mqm ÏÏ­C DB2 ¾\î…¯íðnÝûü]¸w¾HÝsù£ MQSeries­C
  3. Ýb UNIX ÏWü]¸w DB2 ·“ûãš¬’­GñN AMT_DATA_PATH ·“ûãš¬’ús¬Wù DB2 µA÷¥
     ¦§ÝC¾šÏÏ­C ñz¾i¾H«s¨Š·©ž $INSTHOME/sqllib/profile.env­AñN
     AMT_DATA_PATH ús¬WÝš DB2ENVLIST­CÏ]¾iùØ¾× db2set ®¾O­C
  4. Ýb UNIX ÏW­Að®úsñãøÒ÷ˆ©’©w©žùã­GðYðnì·“ûãš¬’šõ¢¾Ö©Ž­A¾ýôúð®úsñãøÒ÷ˆ
     ©’©w©žùã­C
  5. Ýb UNIX ÏWñN¾¨ìšõ¢ªø $INSTHOME/sqllib/cfg­AÝb Windows ÏWñN¾¨ìšõ¢ªø
     %DB2PATH%/cfg­C
  6. øäÝ‘®¾O enable_MQFunctions ¾Hª[§cùÇñã¾× DB2 MQSeries ¾\î…¦§÷ˆ©’©w­C«Ñ
     ø¥ó\17.6, enable_MQFunctions­A¾Hù£ñoÝû®¾O¦§õûóÆ¯­¸£­CÏUÝCïœù¥Ï@ù€Ï@î‰
     «dùã­C ÝbÝù¾\õûÝùÏõ® ­AñNñã¾×®¸w¦§÷ˆ©’©wùÇï£÷åª[§c­C
  7. ðYðnùØ¾×­u¸R¾OÝ‘üBýzóû­vï£÷åüoù€¾\î…­A«ÑÝbñzüsñæùÏwñã¾×¦§÷ˆ©’©w©­Aæo
     ¾XÏUÝC®¾O­G

     values DB2MQ.MQSEND('a test')
     values DB2MQ.MQRECEIVE()

     ýŽÏ@ðàüîðzÝ­ñNô€øeøT©õ "a test" Ýš DB2MQ_DEFAULT_Q ÝŒÝC­AÝàýŽÏGðà®hñN
     ù„ñæÝªÝ^ùà­C

æ—:
     øäÝ‘ enable_MQFunctions ¦§æý¦G­AñN®¾áûwü] MQSeries ·“ûã­CñN®¾á
     MQSeries ÝŒÝC§èýzæ{Ý­ DB2MQ_DEFAULT_MQM Ï×ûwü]ÝŒÝC DB2MQ_DEFAULT_Q­CðY
     ·©ž amt.xml­Bamthost.xml Ï× amt.dtd ÏwÏœÝsÝb¸¢ AMT_DATA_PATH ®ÝV¦§¾
     ¨ì©­AñN®¾áüoù€·©ž­C ðY amthost.xml ·©žÏœÝsÝb­A¾BÏœ¾]õt
     connectionDB2MQ ¦§¸w÷q­A®hú|ñNÝ‘ús¬WùÝüóAú¡÷ˆøT¦§·©žÏÏ­Cðùà¦§·©žÏõ
     ø’¾¯ñNüQ·xÝsªø DB2MQSAVE.amthost.xml­C

  ------------------------------------------------------------------------

17.2 MQSeries ô€øT¬ÓÝ­

DB2 MQSeries ¾\î…Ï„ï¸ÏT§ô€øT¬ã®ª­G÷ˆ©’ûØ­BæoõG/ðqó\ (p/s) Ï×ðnùD/Ý^¶Ñ
(r/r)­C

¾H÷ˆ©’ûØùàô€øe¦§øT©õú|ô€øeùü‘Ï@¾¦§Ýa­A¾BÏœûwïµÝ^¶Ñ­C Ýb p/s ¬ã®ªÏÏ­AÏ@¸×
ÝhðàÏ«¾ª¦ÞñNøT©õô€øeÝšÏ«õG¦AøÔæ{Ý­­AÏ·øeøT©õÝšÏ@¸×Ýhðà¾×Ï ­C ðnùD/Ý^¶Ñ¯P÷ˆ
©’ûØªêÝ­AÝìô€øe¦ÞûwïµñæÝªÝ^·ü­C
  ------------------------------------------------------------------------

17.3 øT©õæý§c

MQSeries ¾¯ùðÏœú|ðnùD¸×Ï„ï¸¾“Ý¢ù„ô€øe¦§øT©õÏõîS©¡æý§c­C

ù„¾Ýýœ®~Ýp MQSeries Integrator (MQSI)­AïNú|ïœù¥¾H C­BCOBOL ¸× XML ÝrÝˆõ×Ýù
¦§øT©õÏõÏ„ï¸­C Ýb MQSI ÏÏ¦§æý§cøT©õªO¾¥øT©õ·xÝs©w¸w÷q­CXML øT©õüqñ`ÝüÏ@ðàÝê
Ý‘¯­¸£¦§øT©õæý§c­A¾B¾iî…Ï]üzûL·xÝs©wùà§èýz­CøT©õÏ]¾iî…ªOùSÝüæý§c¦§­A¯íðnùØ
¾×¦Þæ{Ý­«Xùàð†¦R¸×®§cøT©õÏ§©e­CüoÇçøT©õ¸û¸ûªOÏœõû¾ç¦§æý§c­AÏ]ïNªO¯­­A¾ÝðÞ
ùØ¾×ÝÏ÷ýåÝ÷m¸×¸T¸w¦§¸wªý÷ûùàÏ·ûjøT©õÏÏ¦§Ž‘Ý­C­uMQSeries ¯ýõU§‰’F­vïœù¥
üo§Ïœõû¾çæý§c¦§øT©õÏõÏ„ï¸­C üzûLªYù€ús¾\î…­AñN XML øT©õÏ„ï¸ïœù¥æû DB2 XML
¶X¾RÏ÷­C
  ------------------------------------------------------------------------

17.4 MQSeries ¾\î…úõ’[

MQSeries ¾\î…ôø¾¥ DB2 UDB ¦¸¾¯ 7.2 ïœù¥­A¾iì SQL üîðzÝ­¾]ªAô€øTõ@ú~­C üo¦¡
¾šÝûÏ„ï¸¾iùØ¾×¸¢¾H¾“Ý¢Ï„ï¸¯yù¾¬ô¬g¦§·ü¾×æ{Ý­­AùãÝp­AùØ¾×¾“Ý¢÷ˆ©’©wÏôðñ¦§ C
­BJava­BSQL­CÏUÝCÆ¾š¦§¸ãÝü«dùãõ­Ýb SQL ÏÏ­C ¾i¾H¾×¸ãÝü¬Ñú€ÏŠÝ­­Añqù„¾Læ{Ý­
ü]ðp¯yù¾ùØ¾×Ýû SQL­C ÏWðz¦§¸ãÝü MQSeries ô€øT¬ÓÝ­üœÏwÏ„ï¸­C ÝüÇ” MQSeries
¾\î…¦§÷âýà÷ˆøT­A«Ñø¥ó\­u¦¸¾¯¦`úNù’ôæ­v¦§ SQL Reference Ï@÷`­C

Ýbø•¾¯ª[§cÏÏ­AMQSeries Ý›¦AóûªOÝÝb¯P DB2 Ï@ø_¦§÷ˆ©’©wÝ›¦AóûóöóûÏÏ­C
MQSeries ¾\î…Ýw÷ÓÝb DB2ÏW­AùÇïœù¥û‹ MQSeries Ý›¦Aóû¦§Ýsù£vðð­C DB2 ñqŽíî÷
¾iÝÝb¾iÝsù£ DB2 Server ¦§¾“Ý¢óöóûÏW­C ÝhðàñqŽíî÷¾iÝP©üzûL÷ˆ©’©wÝsù£
MQSeries ¾\î…­C üzûLïœù¥¦§¾\î…­ADB2 ñqŽíî÷¾iÝb SQL üîðzÝ­Ï§øäÝ‘ô€øTõ@ú~­C
üoù€ô€øTõ@ú~¾iì DB2 ·ü¾×æ{Ý­Ýb¾ÝðÞÏõô­üq®H­A¸×¯Pù„¾L MQSeries ·ü¾×æ{Ý­üq
®H­C

enable_MQFunctions ®¾OªO¾×ùàñã¾× MQSeries ¾\î…¦§ DB2 ÷ˆ©’©w­C ¾ÝñNÝêøÒ®¾á
¶ýÝ­ûwü]ª[§c­AñqŽíî÷·ü¾×æ{Ý­ú|ùØ¾×÷àª[§c­AÏœ¯íðn§èýzøÒõ@­C ðYðnù£ño¯­¸£­A«Ñ
ø¥ó\ enable_MQFunctions Ï× disable_MQFunctions­C ûwü]ª[§cïœù¥·ü¾×æ{Ý­ü]ðp©v
Ï@ðàõ™ütñãøÒ¦§ÏŠ¦k­AÏ×Ï@ðàõ¢¶ý¸”¦§ô}æoÏôðñ­C ðYÝü¯íðn­A¾i¬W¾[ª[§cù„¾L¦§¾\
î…­C

«dùã 1­GðYðnùØ¾×ûwü]ª[§cùàô€øe¶ýÝ­øT©õ­ASQL üîðzÝ­ÝpÏU­G

VALUES DB2MQ.MQSEND('simple message')

üoú|ñNøT©õ simple message ô€øeÝš MQSeries ÝŒÝC§èýzæ{Ý­Ï×ûwü]ª[§c®¸w¦§ÝŒ
ÝC­C

MQSeries ¦§­u·ü¾×æ{Ý­ô€øTÏôðñ (AMI)­v­AÝbô€øTª­øÒÏ×®¸wù§ù€ª­øÒ¦§ô€øeÏŠÝ­Ïõ
¸w÷qÏõô­­Aïœù¥ýMú­¦§ûj¶ö­Cüoù€¸w÷q®OîdÝb¾~ü­·xÝs©w·©žÏÏ­AùÇùØ¾× AMI §èýzÏu
ùÆùà§èýz­Cüo¾iì AMI ·ü¾×æ{Ý­©e¸”æo©iùÇ§–@­CDB2 ïœù¥¦§ MQSeries ¾\î…ªO¾H
AMI MQSeries ÏôðñªøùÞóé­CAMI Ï„ï¸¾~ü­ª[§c·¦§ùØ¾×­A÷à·§ëªø­uAMI ·xÝs©w­v­A
¾H·xÝsª[§c÷ˆøT­C ûwü]ª[§c¾]ªA MQSeries AMI ·xÝs©wª[§c­A¾HùØ¾× DB2­C

MQSeries AMI ¦§ùƒðà¾Dðnúõ¸·­A¦AøÔæ{Ý­¶IÏ×ð®h­AüQ¶…¯¬Ýš DB2 MQSeries ¾\î…
ÏÏ­C ¦AøÔæ{Ý­¶IªOè¨Šýž¶I­AõYøT©õ¾iî…ô€øe¸×ñæÝª¦§¶I­C Ýb AMI ·xÝs©wÏÏ­AùCÏ@
ðà¦AøÔæ{Ý­¶IªO¾H MQSeries ÝŒÝCÝW§ëÏ×ÝŒÝC§èýzæ{Ý­ùà¸w÷q­C ð®h¸w÷q¦AøÔæ{Ý­¨‹
ôæ¦§®~«Š­Aù„·üùØ¾×¸¢æû¸w¦§ô€øTõ@ú~­C ¾Dðn¦§¦AøÔæ{Ý­®~«Š¾]ªAøT©õ·u¾ìôôõ€Ï×®—
Ž•¸Ò­C ïœù¥ûwü]¦AøÔæ{Ý­¶IÏ×ð®h¸w÷q­A¾B¾iî…¾¥æo©i¦ÞùØ¾×­A¾HôiÏ@ùB¶ýÏ’·ü¾×æ{
Ý­­C «dùã 1 ¾i¾HÏUÝCÏŠÝ­ð®¬g­A¾H¸£«TÝa®¸wûwü]¦AøÔæ{Ý­¶IÏ×ð®hÝW§ë­G

«dùã 2­G

VALUES DB2MQ.MQSEND('DB2.DEFAULT.SERVICE', 'DB2.DEFAULT.POLICY', 'simple message')

ÝŒÝC¾iî…¾¥Ý›¦Aóû¦§Ï@¸×Ýhðà·ü¾×æ{Ý­¦AøÔ­AÝàÝŒÝCÏ×·ü¾×æ{Ý­õYñ`ón¸¢÷àÝ›¦Aóû
ÏÏ­C Ýbü\Ýhª[§cÏÏ­AÝhð®ÝŒÝCñNüQ¸w÷qªøÏ„ï¸ÏœÝP¦§·ü¾×æ{Ý­Ï×¾¦§­C Ý]ªøüoðàýz
¾¥­AÝbôiÝ‘ MQSeries ðnùD©­A÷gñ`¸w÷qÏœÝP¦§¦AøÔæ{Ý­¶IªO®šð®ðn¦§­C ÝbÏUÝC«dùã
ÏÏÝü¯­¸£­G

«dùã 3­G

VALUES DB2MQ.MQSEND('ODS_Input', 'simple message')

æ—:
     ÝbÝû«dùãÏÏ­A¾¬®¸wð®h­AÝìñNùØ¾×ûwü]ð®h­C

17.4.1 ððùŒ

MQSeries ïœù¥øT©õõ@ú~Ï×÷ˆ©’©wõ@ú~¦§î…ÏO­A¾HÝbü‘Ï@Ïuõ@ü‘Ï÷ÏÏæýÝX­Aõ@ªøüQ®O@
¾‘¸”­C Unix Ï× Windows ÏW¦§ MQSeries ¾\î…ð¾¯ÏœÏ„ï¸Ýû¾\î…­C

ú¡ùØ¾×ô€øe¸×ñæÝª¾\î…©­AÏ@ðàøT©õ¦§üÞÏj¦›®žªO 4000 ðàÝrÏ÷­C üoÏ]ªOùØ¾×
MQPublish ùàÏ«¾ªøT©õ¦§üÞÏjøT©õÏjÏp­C

17.4.2 ¨—¯~«X

ñz¾iÝb­uMQSeries ·ü¾×æ{Ý­ô€øTÏôðñÏƒ¾U­v¦§¦ç¨ì B ÏÏ­Aõ„ù MQSeries ¾\î…ô€Ý^
¦§Ý^¶Ñ«X­C
  ------------------------------------------------------------------------

17.5 ¾×¦kûˆøÔÏƒ¾U

MQSeries Function ¾iùØ¾×¸¢Ïj«dü•¦§ûˆøÔÏƒ¾U­C ¾¯÷`ñNøQ«žÏ@ù€üÞïôûM¦§ûˆøÔ­A¾]
ªA­uø•¾¯ô€øT­v­B­u·ü¾×æ{Ý­üsñæ­vÏ×­u÷ˆ©’Ï«¾ª­v­C

17.5.1 ø•¾¯ô€øT

ú¡¸ãÝü÷ˆ©’©w·ü¾×æ{Ý­üsñæùªêÝP¦§ DB2 Ý›¦Aóû©­Aú|æo¾Ö MQSeries DB2 ¾\î…¦§øT
©õÏõüÞø•¾¯õ×Ý­­CñqŽíî÷¾iî…ªO÷ˆ©’©wÝ›¦Aóû¦§¾¯§í¸×Ï·ïýÝb§“÷“·“ûãÏÏ­C

Ýb¶ýÝ­ûˆøÔ«dùãÏÏ­AñqŽíî÷ A ¸I¾s MQSEND ¾\î…­Aô€øeùØ¾×¦Þ¸w÷qÝšûwü]¦AøÔæ{Ý­Ý
÷m­C MQSeries ¾\î…·H® ú|Ýb÷ˆ©’©wÝ›¦Aóû¦§ DB2 Ï§øäÝ‘­C æy® ­AñqŽíî÷ B ¸I¾s
MQRECEIVE ¾\î…­Aýóøœûwü]¦AøÔæ{Ý­¸w÷q¦§ÝŒÝCÏÏÏõüÞÝðøO÷øO¨ì¦§øT©õ­AùÇñNù„ô€
Ý^ñqŽíî÷­C ÝP¬Ó¦§­AøäÝ‘Ýûõ@ú~¦§ MQSeries ¾\î…¾¥ DB2 øäÝ‘­C

÷ˆ©’©wñqŽíî÷¾i¾H¾×ü\ÝhÏŠÝ­ùàùØ¾×¶ýÝ­ô€øT­Cô€øT¦§ªYù€Ï@î‰¾×¦kÝpÏU­G

   * ÷ˆ©’Ýªôø -- ¾HùàÝêÏ@¸×Ýhðà¾iî…ÏœÝP¦§÷ˆøTùàú«Ïõõ×Ý­ñæÝª÷ˆøT­C ÷ˆøTùàú«
     ¾iî…ªOøàú~·ü¾×æ{Ý­Ýp SAP­A¸×ýå¶ïÏ§ü­æo©i¦§·ü¾×æ{Ý­­C üoÇç÷ˆ©’¾iñqÝŒÝC
     ñæÝª­AùÇ·xÝsÝb÷ˆ©’©w¦¡©‘ÏÏ­A¾Hù¥ôiÏ@ùB¦§üBýz¸×Ï·¦R­C
   * Ïuõ@ðtýÏ·øe -- Ïuõ@ðnùDÏ«¾ª¸¢ÝŒÝC­A¾¥ªêÝP·ü¾×æ{Ý­¦§Ýhðà©žùãÝ@¾×­C ú¡
     ©žùãü’õïøäÝ‘Ï@ù€Ïuõ@©­A¾Ýú|ñqÝŒÝCü¯§íñæÝªùøT©õ­A¾]õtðnøäÝ‘¦§Ïuõ@ðn
     ùD­C ùØ¾×ÝûõèüN­AÝhðà©žùã¾i¾HÝ@¾×·xÝsðnùDÏõü‘Ï@ÝŒÝC¸ã¾N¦¡¦§Ïuõ@ðtý­C
   * ·ü¾×æ{Ý­®H÷û -- ÝbïXðàæ{õ€ÝXõ@¦§ñ­¦pÏÏ­AøT©õüqñ`¾×ùàù¢«åù„Ýù¦G­C üoù€
     øT©õ¾iî…¾]õtÏuõ@ðnøäÝ‘¦§®¾O¸×ðnùD­C üqñ`­Aüo§®H÷ûªOü‘ÝV¦§­FÏ]ïNªO
     ¯­­Aø_¸løT©õ¦§Ï@ÏŠùÇÏœûwïµÝ^·ü­C «Ñø¥ó\17.5.4.1, Request/Reply üq®H­A
     ¾Hù£ño÷âýà÷ˆøT­C
   * ·ü¾×æ{Ý­üq¦ó -- üq¦ó¯P®H÷ûÇçÝ­A÷ˆ©’ñq¦¸læ{Ý­ô€øe¾X­A¾BÏœûwïµÝ^·ü­C
     ÝìªO­Aüq¦óüqñ`¾]õtÇ”¸¢Ïwæo¾ÖÏõú~øÔù’¾¢¦§÷ˆ©’­C 17.5.4.2, æoõG/ðqó\ ªO
     üq¦ó¦§õ¢ôiô¾Ïõõ×Ý­­C

ÏUÝCûˆøÔ«dùã¶X¾RÏFÏWðz¯­¸£¦§¶ýÝ­ûˆøÔ«dùã­A¾Hî€ÏJ¯ú§íô€øT­C Ï]ïNªO¯­­AøT©õÝb
óöóû A ¯Póöóû B Ïõô­ô€øe­C ùB’Jôôõ€ÝpÏU­G

  1. DB2 ñqŽíî÷øäÝ‘ MQSEND ¸I¾s­A®¸wÏw¸w÷q¦§¾¬Ñ¦AøÔæ{Ý­­A¾H¾N¦¡óöóû B ¦§
     ¯ú§íÝŒÝC­C
  2. MQSeries DB2 ¾\î…øäÝ‘ûˆ¯é¦§ MQSeries õ@ú~¾Hô€øeøT©õ­C Ýbóöóû A ÏW¦§
     MQSeries Ý›¦AóûñæùøT©õÏ×®OÇã­AñNù„ô€øeÝš¦AøÔæ{Ý­¶I¸w÷qÏ×óöóû A ¦§ý{Ý‘
     MQSeries ª[§c¸ã¸w÷q¦§¾¦§Ýa­C Ý›¦AóûùM¸wüoªOóöóû B ÏW¦§ÝŒÝC­C æM® ¾Ýú|
     ûµ÷åñNøT©õô€øeÝšóöóû B ¦§ MQSeries Ý›¦Aóû­AùÇÝb¯íðn©üzüqÝað®÷å­C
  3. óöóû B ÏW¦§ MQSeries Ý›¦AóûñæÝªùàÝêóöóû A ÏõÝ›¦Aóû¦§øT©õ­AùÇñNù„¸¤÷mÝb
     óöóû B ¦§¾¦§ÝaÝŒÝC­C
  4. óöóû B ÏW¦§ MQSeries ñqŽíî÷ðnùDÝŒÝC¦§üÞÝðøO÷øO¨ìÏõøT©õ­C

17.5.2 ô€øeøT©õ

ùØ¾× MQSEND­ADB2 ùØ¾×¦Þ¸×æo©i¦Þ¾i¨‹óšðnô€øe¦§÷ˆ©’­Aðnô€øe¦§Ý÷m­AÏ×ðnô€øe¦§
©ô­­C Ýbú~ªÏÏ­Aüoüqñ`¾søæ "Send and Forget"­A¦¡¾šô€øe¦Þ¾uðnô€øeøT©õ­AÝàùÞ
óé MQSeries ¦§¯¬øeüq®Hù¢¸w®OÇã­A«T®OøT©õ¾iùûF¾¦§Ýa­C ÏUÝC«dùãú|û‹Ýûõ@¯­
¸£­C

«dùã 4­GðYðn¾Hð®h highPriority ùàñNùØ¾×¦Þ¸w÷qÝrÝˆô€øeÝš¦AøÔæ{Ý­¶I
myplace­G

VALUES DB2MQ.MQSEND('myplace','highPriority','test')

Ýbüo÷Þ­Að®h highPriority ø¥úà AMI ·xÝs©w¸ã¸w÷q¦§ð®h­AñN MQSeries ·u¾ìôôõ€
ü]¸wªøüÞø¦¬hÝ÷­A Ï]¾iî…«åóÆù„¾L¦AøÔæ{Ý­¦§®~«Š­AùãÝp®—Ž•¸Ò­C

øT©õÏ§©e¾iî…¾¥ SQL ¦§¾“Ý¢¬Ñú€ÏÏoýåÝXÏ×ùØ¾×¦Þ®¸w¦§÷ˆ©’ýåÝXÝàÝù­C üo¾]ªAñ_
¦ª¾\î…­BûB§ƒÏlÏ×ñjùŒ¶…®ª­C ùãÝp­Aïœù¥Ï@¦¡©‘ EMPLOYEE­AÝü VARCHAR ¦«Ž‘
LASTNAME­BFIRSTNAME Ï× DEPARTMENT­Aøwû‹ùCÏ@ðà DEPARTMENT 5LGA ÏÏ¦§ð–Ïuô€øe
¾]õtÝû÷ˆøTÏõøT©õ­Añz¾iøäÝ‘ÏUÝC­G

«dùã 5­G

SELECT DB2MQ.MQSEND(LASTNAME || ' ' || FIRSTNAME || ' ' || DEPARTMENT)
FROM EMPLOYEE
   WHERE DEPARTMENT = '5LGA'

ðYÝû¦¡©‘Ï]ÝüÏ@ðàõûóÆ¦§ AGE ¦«Ž‘­A¾Ý¾iî…Ï]ú|üQù™ÏJ­AÝpÏU¸ã¾š­G

«dùã 6­G

SELECT DB2MQ.MQSEND(LASTNAME || ' ' || FIRSTNAME || ' ' || DEPARTMENT|| ' ' || ch
ar(AGE))
   FROM EMPLOYEE
      WHERE DEPARTMENT = '5LGA'

üÞ® ­AÏUÝC«dùãÆ¾šÝpÝ¢ùØ¾×¾“Ý¢Ýü©Ž¦§ SQL ¦¡¾šÝ­ùàðl¾ÖøT©õÏ§©e­C ïœù¥ýŽÏGðà
¦¡©‘ DEPT­Aù„¾]õt VARCHAR ¦«Ž‘ DEPT_NO Ï× DEPT_NAME­A¾iô€øe¾]õtð–Ïu
LASTNAME Ï× DEPT_NAME ¦§øT©õ­G

«dùã 7­G

SELECT DB2MQ.MQSEND(e.LASTNAME || ' ' || d.DEPTNAME) FROM EMPLOYEE e, DEPT d
   WHERE e.DEPARTMENT = d.DEPTNAME

17.5.3 ¶^ù£øT©õ

MQSeries DB2 ¾\î…¾iñæÝª¸×¦ù£øT©õ­C ¦ù£¯PñæÝªÏõô­¦§ÏœÝPüB­AÝb¸¢¦ù£ô€Ý^ÝŒ
ÝCÏõüÞÝðøO÷øO¨ì¦§øT©õ­AÏœ¯íñqÝŒÝCýóøœ­AÝàñæÝªõ@ú~ú|ùØøT©õñqÝŒÝCýóøœ­C ùØ¾×
ñæÝªõ@ú~ùà¶^ù£¦§øT©õ­AôÔ¾i¾H¶^ù£Ï@Ý÷­AÝàùØ¾×¦ù£õ@ú~ùà¶^ù£¦§øT©õ­A¾iÝhÝ÷¶^
ù£ªêÝPøT©õ­C ÏUÝC«dùãú|û‹Ýûõ@¯­¸£­G

«dùã 8­G

VALUES DB2MQ.MQREAD()

Ýû«dùãùØ¾×¦AøÔæ{Ý­ð®h¦§ûwü]®~«Š­Aô€Ý^ VARCHAR ÝrÝˆ­A÷àÝrÝˆ¾]õtûwü]¦AøÔæ{Ý­
¸w÷q¦§ÝŒÝCÏõüÞÝðøO÷øO¨ì¦§øT©õ­C ð®ðnù’ôæ­G«Ñ¦`úNðYùSÝü¾iù¥¦ù£¦§øT©õ­AñNô€
Ý^Ï@ðà NULL ðÔ­C Ýûõ@ú~Ïœú|šõ¢ÝŒÝC­C

«dùã 9­G

VALUES DB2MQ.MQRECEIVE('Employee_Changes')

ÏWðz«dùãÆ¾šÝpÝ¢ùØ¾×ûwü]ð®h­AñNøT©õñq Employee_Changes ¦AøÔæ{Ý­¸w÷q¦§ÝŒÝC
ÏõüÞÝðøO÷øO¨ìýóøœ­C

DB2 ¦§Ï@ðà®Dñ`ÝüÏO¦§¾\î…­AªOñqùØ¾×¦Þ¸w÷q (¸× DB2 ïœù¥¦§) ¾\î…­Aýœ¾Ö¦¡©‘¦§î…
ÏO­C ñz¾i¾Hô}æoÝû¦¡©‘¾\î…­AìÝŒÝCÏ§©e¾iõ@ªø DB2 ¦¡©‘­C ÏUÝC«dùã¯­¸£üoðàüÞ¶ý
¸”¦§õ×Ý­­G

«dùã 10­G

SELECT t.* FROM table ( DB2MQ.MQREADALL()) t

Ýûªd÷áô€Ý^Ï@¦¡©‘­A¾¥¸ãÝüûwü]¦AøÔæ{Ý­¸w÷qÏõÝŒÝC¦§¸ãÝüøT©õÏ×ÝüÇ”üoù€øT©õ¦§ïy
ðz÷ˆ©’¸ãýåÝù­C ú¡ô€Ý^¦§¦¡©‘æý§cÏõõûóÆ¸w÷qªO¸w÷q¸¢¦ç¨ìÏÏ­A®hýŽÏ@¦«Ž‘ú|ÏØªMøT
©õÏ§©e­Aù„ól¦«Ž‘®h¾]õtïyðz÷ˆ©’­C ðY¾uðnô€Ý^øT©õ­A¾ið®ús¬ô¬g«dùã­G

«dùã 11­G

SELECT t.MSG FROM table (DB2MQ.MQREADALL()) t

¦¡©‘¾\î…ô€Ý^¦§¦¡©‘¯P÷ˆ©’©w¦«ñæ¶^ù£¦§¦¡©‘ªêÝP­C üo¦¡¾šñz¾i¾H¾×¬s¦x¦§ÏŠ¦kùØ¾×
Ýû¦¡©‘­C ùãÝp­Añz¾i¾HæýÝXÏ@¦¡©‘¯P¾tÏ@¦¡©‘¦§Ï§©e­A¸×ðp§ƒÝŒÝCÏÏ¦§øT©õ¬’ôq­G

«dùã 12­G

SELECT t.MSG, e.LASTNAME
   FROM table (DB2MQ.MQREADALL() ) t, EMPLOYEE e
      WHERE t.MSG = e.LASTNAME

«dùã 13­G

SELECT COUNT(*) FROM table (DB2MQ.MQREADALL()) t

ñz¾i¾HüzûL¦¡©‘¾\î…ùà®¾áúõýÏ¦¡­A¾Hµ“¶Ç¦¡©‘ùàú«ªOÝŒÝC¦§ù’ûˆ­C ùãÝp­AÏUÝC«dùã
üzûL¦AøÔæ{Ý­ NEW_EMPLOYEES ¸ãø¥úà¦§ÝŒÝC­Aùà®¾áÝWªø NEW_EMP ¦§úõýÏ¦¡­G

«dùã 14­G

CREATE VIEW NEW_EMP (msg) AS
   SELECT t.msg FROM table (DB2MQ.MQREADALL()) t

ÝbÝû©žùãÏÏ­AúõýÏ¦¡ôÔ¾H¾]õtóÆðàøT©õ¦§ü‘Ï@¦«Ž‘ùà¸w÷q­C ðYøT©õªO¶ýÝ­¦§ª[§c­Aùã
Ýp¾]õt¸T¸w¦›®ž¦§ùƒðàŽ‘Ý­A ®h¾Ýú|¦«ñæÝV®e¾HùØ¾× DB2 Ï§®¾\î…­AñNøT©õð†¦RÝš
ùƒ¦«Ž‘ÏÏ­C ùãÝp­AðYñz¦óûDô€øeÝšîS©¡ÝŒÝC¦§øT©õüœ¾]õtÏ@ðà 18 ÝÏ÷¦§¸mÏ¢­Aù„® 
®hªOÏ@ðà 18 ÝÏ÷¦§ÝWÝr­A®hñz¾i¾H¸w÷qÏ@ðàúõýÏ¦¡­A¾]õtùCÏ@ðàðàõO¦«Ž‘¦§Ž‘Ý­A
ùãÝp­G

«dùã 15­G

CREATE VIEW NEW_EMP2 AS
   SELECT left(t.msg,18) AS LNAME, right(t.msg,18) AS FNAME
   FROM table(DB2MQ.MQREADALL()) t

­uDB2 ·xÝsæ{õ€®÷móû­v¦§úsîS¸Ò­uMQSeries ¯ýõU§‰’F­v­A¾i¾×ùà®¾áús¦§ DB2 ¦¡
©‘¾\î…Ï×úõýÏ¦¡­Aù„ñNÝü¸wªý÷û¦§øT©õæý§cû‹ªMÝš¦«Ž‘­C

üÞ® ­Aüqñ`ðnñNÏ@¸×ÝhðàøT©õÏ§©e·xÝsÝb÷ˆ©’©wÏÏ­C üo¾iùØ¾× SQL ¦§õûóÆ¾\î…ùàõû
Ýù­A¾Hóèõ@ùÇ·xÝsøT©õÏ§©e­C üÞ¶ý¸”¦§«dùã¾iî…ªO­G

«dùã 16­G

INSERT INTO MESSAGES
   SELECT t.msg FROM table (DB2MQ.MQRECEIVEALL()) t

ïœù¥¾]õt VARCHAR(2000) ü‘Ï@¦«Ž‘¦§¦¡©‘ MESSAGES­AÏWðz¦§üîðzÝ­ú|ñqûwü]¦AøÔæ{
Ý­ÝŒÝC­AñNøT©õï­ÏJ¦¡©‘ÏÏ­C ¾iðžû½ÝûõèüN­A¾Hý[¯\ñ­¦p¦§¬s¦x§Çç­C

17.5.4 ·ü¾×æ{Ý­û‹·ü¾×æ{Ý­üsñæ

·ü¾×æ{Ý­óÆÝXªOü\Ýh÷¥ùMÏŠ©ž¦§Ï@î‰Ï÷î·­C Ïœ«žñNµÒôR¦§·ü¾×æ{Ý­óÆÝXùý{Ýs¦§ø•¶Ý
ª[§cÏÏ­A¸×¾uñNúsô}æo¦§·ü¾×æ{Ý­óÆÝXùý{Ýs·“ûãÏÏ­AõéðÞüqñ`ú|ðñû‹ôøÏÏÏlùtý×Ïõ
ÏœÝPôøÝX¦§õ@ú~­A¾H§cÝùõûóÆ¦§Ïuõ@­C MQSeries üqñ`üQæ›ªøóÆÝX·ü¾×æ{Ý­¦§ø•¾¯Ïu
ùÆ­C ¾iÝbÏjü­¾öæw‚­Bün‚Ï×¯yù¾·“ûãÏÏÝsù£­AMQSeries ïœù¥¾‘Ïªüsñæ·ü¾×æ{Ý­¦§
ÏœÝPôøÝXÏõÏŠ¦k­C

Ýû÷`ñNøQ«žü­¾ö·ü¾×æ{Ý­óÆÝXûˆøÔÏ×ÝpÝ¢¾H DB2 ùàùØ¾×¾ÝðÞ­C Ý]ªø¾DÇDªêú¡¬s¦x­A
­u·ü¾×æ{Ý­óÆÝX­v¦§¬s¦xøQ«žôWôVÏFÝûÏuõ@¦§«dü•­C Ý]Ýû­Að®¶IôÔÝbùƒðà¶ýü‘¦§¾D
ÇD­GRequest/Reply üq®H­AÏ× MQSeries Integrator Ï× Publish/Subscribe­C

17.5.4.1 Request/Reply üq®H

­uRequest/Reply (R/R)­vüq®HÏŠ¦kªOüÞïôûM¦§õèüN­AÏ@ðà·ü¾×æ{Ý­¾iÝV¾tÏ@ðà·ü¾×æ{
Ý­ðnùD¦AøÔ­C øäÝ‘ÝûøÒõ@¦§ù„ÏÏÏ@§ÏŠ¦k­AªOìðnùDæ{Ý­ñNøT©õô€øeÝšðnùDøäÝ‘ªYù€
Ïuõ@¦§¦AøÔïœù¥æ{Ý­­CÏ@¾ûÏuõ@ÏwõûÝù­Aù¥·üæ{Ý­¾iùM¸wñNæý¦G (¸×õûÝù«T¯{) ô€Ý^
ðnùDóû­C ÝìùØ¾×ÏWðz¦§ø•¾¯ô€øTõèüN­AïNÏœî…üsñæô€øe¦ÞðnùD¯P¦AøÔïœù¥æ{Ý­Ý^·ü­C
øœ®DðnùDæ{Ý­ÝbŽ~Ž•øäÝ‘Ïõ®e­A¾ìæ¾®íÝ^¶Ñ­Aõ_®hªYù€óöùŒ¾ýôú¾×ùàæýÝXùCÏ@ðàÝ^¶Ñ
Ï×ù„ðnùD­CMQSeries ÏœñjùŒæo©iæ{Ý­®¾áüoÇçóöùŒ­AÝàªOïœù¥Ï@ðàªêÇ” ID­AùØ¾‘ï®
üB¦§øT©õÝüªêÇ”¸Ò­C

ú¡Ýüü\ÝhÏŠ¦k¾iù¥ÝûóöùŒùØ¾×©­AüÞ¶ý¸”¦§ÏŠ¦kªOìðnùDóû¾×Ïw¦ó¦§ªêÇ” ID ùà¬Ñ¾š
øT©õ­AùãÝpÏUÝC¸ã¾š­G

«dùã 17­G

DB2MQ.MQSEND ('myRequester','myPolicy','SendStatus:cust1','Req1')

ÝûüîðzÝ­ñNüÞýžø¥¬’ Req1 ús¬WÝšÏWðz¦§ MQSEND üîðzÝ­ÏÏ­A¾H®¾XðnùD¦§ªêÇ” ID­C

ðYðnñæÝªÝûîS¸wðnùD¦§Ý^¶Ñ­A¾iùØ¾×ªêû‹·ü¦§ MQRECREIVE üîðzÝ­­A¨‹óš¸ÒÝañæÝª®
¾š¦§¦AøÔæ{Ý­¸ã¸w÷q¦§ýŽÏ@ðàøT©õ­Aù„¯PÏUÝCªêÇ” ID ªêý­G

«dùã 18­G

DB2MQ.MQRECEIVE('myReceiver','myPolicy','Req1')

ðY¦AøÔðnùD¦§·ü¾×æ{Ý­Ýœ«uÏÏ­A¾BðnùDóûÝbÝ^¶Ñô€øeÏõ®e­Aæo¾XÏWðz¦§ MQRECEIVE­A
®hñNõ„Ïœù¯PªêÇ” ID ýÝX¦§øT©õ­C

ðYðnñæÝª¦AøÔæ{Ý­ðnùDÏ×ªêÇ” ID­AùØ¾×ÏUÝC¦§üîðzÝ­­G

«dùã 19­G

SELECT msg, correlid FROM table (DB2MQ.MQRECEIVEALL('aServiceProvider','myPolicy',1)) t

üoú|ô€Ý^¦AøÔæ{Ý­ aServiceProvider ¦§ýŽÏ@ðàðnùDÏõøT©õÏ×ªêÇ” ID­C

Ï@¾ûøäÝ‘ÏF¦AøÔæ{Ý­­A¾Ýú|ñNÝ^¶ÑøT©õô€øeæû aReauester ¯­¸£¦§ÝŒÝC­C Ýbüoïµô­­A
¦AøÔðnùDæ{Ý­Ïïú|øäÝ‘ù„¾Lõ@ú~­C ù’ûˆÏW­AùÇÏœ®OÇãø_¸l¦AøÔæ{Ý­ðnùDú|Ýbü]¸w©ô­
Ï§Ý^·ü­C ÝpÝPüoÇç¦§·ü¾×æ{Ý­¬hÝ÷ûO©­A¾ýôú¾¥æo©iæ{Ý­ùà§èýz­FðnùDæ{Ý­¾ýôú«÷á
ø¯ï£Ý^¶Ñ¦§ñ­¦p­C

üo§©ô­¨W¾á®DÝPùBüBýz¦§·u¶I­AªOðnùDæ{Ý­Ï×¦AøÔù¥·üæ{Ý­ªOõû¾ç¨W¾áÝaøäÝ‘­C üo
¾i¾×¸¢óAÝX¦§·“ûã­A·ü¾×æ{Ý­ôÔú|¶_Ž•Ýaüsñæ­AÏ]¾i¾×¸¢õ¢õ†Ý÷óÝV¦§·“ûã­AÝhð®ðn
ùD¸×Ý^¶Ñú|ÝbüBýzæ{õ€®e¾ì¯Eôøø_ùà­C üo§ôøÝX‚üqñ`¾×¸¢÷ˆ©’ðš·x·“ûã­A¾H¸wïµÝa
õ¢ús÷ˆ©’ðš·x¸×õ@ú~÷ˆ©’·xÝs­C

17.5.4.2 æoõG/ðqó\

¶ýÝ­÷ˆ©’¾X¦¸®~

·ü¾×æ{Ý­óÆÝXÏÏ¦§¾tÏ@ðàÏ@î‰ûˆøÔ«dùã­AªOÏ@·ü¾×æ{Ý­üq¦óù„¾L·ü¾×æ{Ý­ÝüÇ”¨ü«¦§
ù’¾¢­C ñz¾i©e¸”ÝañNøT©õô€øeùÝŒÝC­A÷àÝŒÝC¾¥¾tÏ@ðà·ü¾×æ{Ý­§Òúç­C øT©õÏ§©e¾i
¾HªOùØ¾×¦Þ¸w÷qÝrÝˆ­A¸×¾i¾Hñq÷ˆ©’©w¦«Ž‘ùà¬ô¬g­C ¶ýÝ­øT©õ¸û¸ûªO¯íðnùØ¾×
MQSEND ¾\î…ùàô€øe¦§øT©õ­C ú¡üoÇçøT©õ¯íðnÝP©ô€øeùÝhðàñæÝª¦Þ©­A¾i¾HùØ¾×
MQSeries AMI ¦§­uÏ·øeýMü‘­vóöî…­C

Ï·øeýMü‘ªOùØ¾× AMI §èýzÏuùÆùà¸w÷q­CÏ·øeýMü‘¾]õtðàõO¦AøÔæ{Ý­¦§ýMü‘­C ô€øeù
Ï·øeýMü‘¦§øT©õ­Aú|¶…¯¬ùÝûýMü‘ÏÏ¸ã¸w÷q¦§ùCÏ@ðà¦AøÔæ{Ý­­C ú¡Ïw¦óÏ@ù€¦AøÔæ{Ý­
Ï@¦«û‹ùCðàøT©õÝü¨ü«©­AüoªOîSõOÝü¾×¦§¾\î…­C ÏUÝC«dùãÆ¾šô€øeøT©õÝšÏ·øeýMü‘
interestedParties­G

«dùã 20­G

DB2MQ.MQSEND('interestedParties','information of general interest');

ú¡îS©¡¦AøÔæ{Ý­·üñæÝª¦§øT©õ¯íðnõ¢ÝhññùŒ©­A®h¯íðn Publish/Subscribe î…ÏO­C
Publish/Subscribe ùtý×üqñ`ïœù¥Ï@ðà¾i«åóÆ¦§­BÝw¾ç¦§·“ûã­Aü\ÝhðqÏ ¾iÝbù„ÏÏæn
øO­A¾HñqÝhðàÏ«¾ª¦ÞñæÝªøT©õ­C ðYðnÏ„ï¸Ýûî…ÏO­A¾iùØ¾× MQPublish Ïôðñ­A¯P
MQSeries Integrator ¸× MQ Series Publish/Subscribe óöî…üsñæ­C

MQPublish ¾iìùØ¾×¦Þ¨‹¾×¸ÒÝa®¸w¯PøT©õªêÇ”¦§¾DÇD­C ¾DÇD¾iì¾×Ï õ¢ýMú­Ýa®¸w
ðnñæù¦§øT©õ­C ùB’Jôôõ€ÝpÏU­G

  1. MQSeries §èýz¦Þª[§c MQSeries Integrator æoõG/ðqó\¾\î…­C
  2. úP¨ü«¦§·ü¾×æ{Ý­Ýb MQSI ª[§c¸ã¸w÷q¦§ðqó\¶Iðqó\­A¨‹¾×¸ÒÝa®¸wù„Ýü¨ü«¦§
     ¾DÇD­C ùCÏ@ðà¾×Ï ¨‹ù£ªêÇ”¦§¾DÇD­AùÇ¾i¾HõQ¾× MQSeries Integrator V2 Ïõ
     ¾HÏ§©eªøø•¶Ý¦§ðqó\õèüN­C ð®ðnù’ôæ­G«Ñ¦`úN­A¦AøÔæ{Ý­ÝW§ë¾N¦¡¦§ÝŒÝCÝü¸w
     ÷q¾×Ï ­C
  3. DB2 ·ü¾×æ{Ý­Ï«¾ª¦AøÔæ{Ý­¶I Weather ¦§øT©õ­C øT©õ®¾XÏ¥©ÐªO Sleet­A¾Bù„
     ¾DÇDªø Austin­AÝ]Ýûüq¦óÝü¨ü«¦§¾×Ï ­Aõi¦ó Austin ¦§Ï¥©ÐªO Sleet­C
  4. ûˆ¯éÏ«¾ªøT©õ¦§óöùŒªO¾¥ DB2 ïœù¥¦§ MQSeries ¾\î…ùàüBýz­C ùØ¾×¦AøÔæ{Ý­ÝW
     §ë Weather­AñNøT©õô€øeÝš MQSeries Integrator­C
  5. MQSI ñq Weather ¦AøÔæ{Ý­ñæùøT©õ­AøäÝ‘ MQSI ª[§c¸w÷q¦§¾“Ý¢üBýzæ{õ€­A
     ùÇùM¸wù„§­úN¦§ðqµÒ­CæM®  MQSI ú|ñNøT©õ¶…¯¬Ýšù„ýÝX¦§ú€®hÏõ¾×Ï ÝŒÝC­C
  6. Ïwðqó\ Weather ¦AøÔæ{Ý­­AùÇÝb Austin ænøOüáÝn¦§·ü¾×æ{Ý­­AñNÝbñæÝª¦AøÔ
     æ{Ý­ÏÏñæÝªùøT©õ Sleet­C

ðYðnùØ¾×¸ãÝüûwü]ðÔÏ× NULL ¾DÇDùàÏ«¾ªÝû÷ˆ©’­Añz¾iùØ¾×ÏUÝCüîðzÝ­­G

«dùã 21­G

SELECT DB2MQ.MQPUBLISH(LASTNAME || ' ' || FIRSTNAME || ' ' || DEPARTMENT|| ' ' ||cha
r(AGE))
   FROM EMPLOYEE
      WHERE DEPARTMENT = '5LGA'

õûóÆ¦§®¸w¸ãÝüø¥¬’ùÇ¶ýÏ’øT©õ­AùØù„ôÔ¾]õt LASTNAME­AüîðzÝ­¾iî…ÝpÏU¸ã¾š­G

«dùã 22­G

SELECT DB2MQ.MQPUBLISH('HR_INFO_PUB', 'SPECIAL_POLICY', LASTNAME,
   'ALL_EMP:5LGA', 'MANAGER')
   FROM EMPLOYEE
      WHERE DEPARTMENT = '5LGA'

ÝûüîðzÝ­ùØ¾× SPECIAL_POLICY ¦AøÔæ{Ý­­AñNøT©õÏ«¾ªÝš HR_INFO_PUB Ï«õG¦AøÔæ{Ý­
ÏÏ­C øT©õ®¾Xô€øe¦ÞªO MANAGER ¾DÇD­C ¾DÇDÝrÝˆ¯­¸£¾i®¸wùØ¾×­u­G­vüsñæ¦§Ýhð®
¾DÇD­C ÝbÝû«dùãÏÏ­AùØ¾×üoùƒðà¾DÇD¾iì¾×Ï ænøO ALL_EMP ¸×¾uænøO 5LGA­A¾HñæÝª
üoù€øT©õ­C

ðYðnñæÝªÏ«¾ª¦§øT©õ­Añz¾ýôú¾ìñNñz¦§üáÝnænøOÝbøT©õÏÏ­A øT©õ¾]õtæû¸w¦§¾DÇDùÇ®
¾XøT©õ·ü÷àô€øe¦§¾×Ï ¦AøÔæ{Ý­ÏõÝW§ë­C ð®ðnù’ôæ­G«Ñ¦`úN AMI ¾×Ï ¦AøÔæ{Ý­Ýü¸w
÷qÏ·øt§èýzùtý×¦AøÔæ{Ý­Ï×ñæÝª¦Þ¦AøÔæ{Ý­­C Ï·øt§èýzùtý×¦AøÔæ{Ý­ªO¾×Ï ¯Pæo¾ª/
ðqó\Ï·øt§èýzùtý×üq®H¦§ÏŠÝ­­A ÝàñæÝª¦Þ¦AøÔæ{Ý­ªOýÝXðqó\ðnùDñNô€øe¦§ÝaÏŠ­C 7
ÏUÝCüîðzÝ­Ýb¾DÇD ALL_EMP ÏÏænøOüáÝn­C

«dùã 23­G

DB2MQ.MQSUBSCRIBE('aSubscriber', 'ALL_EMP')

Ï@¾ûðqó\ÏF·ü¾×æ{Ý­­A¾H¾DÇD ALL_EMP Ï«¾ª¦§øT©õ­AñN¶…¯¬ù¾×Ï ¦AøÔæ{Ý­¸ã¸w÷q¦§
ñæÝª¦Þ¦AøÔæ{Ý­ÏÏ­C Ï@ðà·ü¾×æ{Ý­¾i¾HÝüÝhð®¦§ùÇÝ‘ðqó\­CðYðnù£ñoýÝXñz¦§ðqó\¦§
øT©õ­Añz¾i¾HùØ¾×¾“Ý¢¬Ñú€¦§øT©õ¶^ù£¾\î…­CùãÝp­AðY¾×Ï ¦AøÔæ{Ý­ aSubscriber ñN
ñæÝª¦Þ¦AøÔæ{Ý­¸w÷qªø aSubscriberReceiver­AÝà®DÏUÝCüîðzÝ­­A®hñNú|®Dî}Ça¸ÒÝa
¦ù£ýŽÏ@ðàøT©õ­G

«dùã 24­G

DB2MQ.MQREAD('aSubscriberReceiver')

ðYðnùM¸w¾HÏUðnÏ«¾ª¦§øT©õ¯P¾DÇD­Añz¾i¾HùØ¾×ù„ÏÏÏ@§¦¡©‘¾\î…­C ÏUÝCüîðzÝ­ú|ñæ
Ýª aSubscriberReceiver ¦§®eÏððàøT©õ­AùÇÆ¾šøT©õ¯P¾DÇD­G

«dùã 25­G

SELECT t.msg, t.topic FROM table (DB2MQ.MQRECEIVEALL('aSubscriberReceiver',5)) t

ðYðn¾H¾DÇD ALL_EMP ùà¦ù£¸ãÝüøT©õ­Añz¾i¾H¬vT SQL ¦§î…ÏO­A«Ñæo¾X­G

«dùã 26­G

SELECT t.msg FROM table (DB2MQ.MQREADALL('aSubscriberReceiver')) t
   WHERE t.topic = 'ALL_EMP'

æ—:
     ð®ðn¦§ªOñz¾ýôúý ÷¥ðY MQRECEIVEALL ùØ¾×ððùŒ­AÝà®DùØ¾×óÆðàÝŒÝC­A ®hùÇ®D
     ¾uÝüù§ù€øT©õú|Ï«¾ª¾DÇD ALL_EMP­C üoªOÝ]ªøøäÝ‘¦¡©‘¾\î…® ­AÏ~Ïè¾×ððùŒ­C

ú¡ñzÏœÝAÝü¨ü«ðqó\îS©¡¾DÇD©­Añz¾ýôúùØ¾×üîðzÝ­­A¸£«TÝaù£©›ðqó\­AùãÝp­G

«dùã 27­G

DB2MQ.MQUNSUBSCRIBE('aSubscriber', 'ALL_EMP')

Ï@¾ûæo¾XÝûüîðzÝ­­AæoõG/ðqó\Ï·øt§èýzùtý×ñNÏœÝAô€øeýÝXðqó\¦§øT©õ­C

ÝêøÒÏ’Ï«õG

÷ˆ©’©wô€øT¦§¾tÏ@ðàð®ðnõèüNªOÝêøÒÏ’Ï«¾ª­C ùØ¾× DB2 ÏÏ¦§Žýæoù‡Ý­óöî…­Añz¾i¾H
ÝêøÒÏ«¾ªøT©õ­Aõ@ªøŽýæoù‡Ý­¸I¾s¦§Ï@ü­¾ö­C ú¡ù„¾L¦§ÝêøÒ÷ˆ©’Ï«¾ªõèüNÝsÝb©­AŽý
æoæ{Ý­ø•¶Ý¦§ÏŠ¦k¾iì§èýz¦Þ¸×ô}æo¦ÞÝê¾¥Ýa®§cøT©õÏ§©e­AùÇ¬u¸ÒÝa¸w÷qŽýæoøÒ
õ@­C«Ñ¦`úN­A¾“Ý¢Žýæoù‡Ý­¦§ùØ¾×­Aüœ¾ýôúæû¾IøäÝ‘·Wýv¯PÝù¾¯¦§ôO¾×­C ÏUÝC«dùã¯­
¸£Žýæoù‡Ý­ÝpÝ¢ùØ¾× MQSeries DB2 ¾\î…­C

ÏUÝC«dùãÆ¾šùCÝ÷ôñ¾×úsð–Ïu©­AÏ«¾ªøT©õªO®š©e¸”¦§­C ¾“Ý¢ðqó\ HR_INFO_PUB ¦A
øÔæ{Ý­ùÇÝb NEW_EMP ÏÏænøOüáÝn¦§ùØ¾×¦Þ¸×·ü¾×æ{Ý­­AñNú|ñæÝªùÏ@øT©õ­A¾]ªAùCÏ@
ðàúsð–Ïu¦§Ï‚ïµ­BÝW§ëÏ×ü­¦—­C

«dùã 28­G

CREATE TRIGGER new_employee AFTER INSERT ON employee REFERENCING NEW AS n
      FOR EACH ROW MODE DB2SQL
      VALUES DB2MQ.MQPUBLISH('HR_INFO_PUB&',  'NEW_EMP',
      current date || ' ' || LASTNAME || ' ' || DEPARTMENT)

  ------------------------------------------------------------------------

17.6 enable_MQFunctions

enable_MQFunctions

ñã¾×®¸w¦§÷ˆ©’©wÏõ DB2 MQSeries ¾\î…­AùÇ‡Çã DB2 MQSeries ¾\î…¾i¾HóAú¡Ýaøä
Ý‘­C ðY¾¬Ýw÷Ó¯Pª[§c MQSeries ¸M MQSeries AMI­A®¾OñNú|¾½ñ¥­C

ñ¶v

ÏUÝCù„ÏÏÏ@ôæ­G

   * sysadm
   * dbadm
   * ðY¾\î…¦§µ“õt¸×¸£«T¦§§ä¾ÝW§ëÏœÝsÝb­A®h IMPLICIT_SCHEMA Ýb÷ˆ©’©wÏW­C
   * ðY§ä¾ÝW§ë DB2MQ ÝsÝb­A®h CREATEIN ñM¾×vÝb§ä¾ÏW­C

®¾O¯y¦k

>>-enable_MQFunctions----n--database----u--userid--------------->

>-----p--password----+--------+---+-------------+--------------><
                     '-force--'   '-noValidate--'


®¾Oø¥¬’

-n database
     ®¸wðnñã¾×¦§÷ˆ©’©wÝW§ë­C

-u userid
     ®¸wùØ¾×¦Þ ID ¾Hüsñæù÷ˆ©’©w­C

-p password
     ®¸wùØ¾×¦Þ ID ¦§üqÝ‘«X­C

-force
     ®¸wð®úsÝw÷Óïµô­æoý{¦§Žæõi·üüQ¸¨ýÏ­C

-noValidate
     ®¸w DB2 MQSeries ¾\î…¦§‡ÇãñNÏœøäÝ‘­C

«dùã

ÝbÏUÝC«dùãÏÏ­AÏw®¾á DB2MQ ¾\î…­CùØ¾×¦Þüs«uù÷ˆ©’©w SAMPLE­C ÏwùØ¾×ûwü]§ä¾
DB2MQ­C

   enable_MQFunctions -n sample -u user1 -p password1

¾×¦k¦`úNù’ôæ

DB2 MQ ¾\î…ÝbÝû®¾OÝêøÒ®¾á¦§§ä¾ DB2MQ ÏUøäÝ‘­C

øäÝ‘®¾OÏõ®e­G

   * «T¸wÏwÝw÷Ó MQ ¯P AMI­A¾B MQSeries ¦¸¾¯ªO 5.2 ¸×õ¢ús¦¸¾¯­C
   * «T¸wÏw¸w÷q·“ûãš¬’ $AMT_DATA_PATH­C
   * ñN¾¨ìšõ¢ªø DB2PATH ¦§ cfg Ý÷¾¨ì­C

Ýb UNIX ÏW­G

   * ùØ¾× db2set­AñN AMT_DATA_PATH ús¬WÝš DB2ENVLIST­C
   * «T¸w¯P UDF øäÝ‘ªêÇ”¦§ùØ¾×¦ÞñbÏ ªO mqm ÷sýå¦§Ýùð–­C
   * «T¸wðn¸I¾sÝû®¾O¦§ùØ¾×¦ÞªO mqm ÷sýå¦§Ýùð–­C

æ—:
     MQSeries 5.2 ÏœÏ„ï¸ ATX 4.2­C

  ------------------------------------------------------------------------

17.7 disable_MQFunctions

disable_MQFunctions

øñ¾×®¸w¦§÷ˆ©’©wÏõ DB2 MQSeries ¾\î…­C

ñ¶v

ÏUÝCù„ÏÏÏ@ôæ­G

   * sysadm
   * dbadm
   * ðY¾\î…¦§µ“õt¸×¸£«T¦§§ä¾ÝW§ëÏœÝsÝb­A®h IMPLICIT_SCHEMA Ýb÷ˆ©’©wÏW­C
   * ðY§ä¾ÝW§ë DB2MQ ÝsÝb­A®h CREATEIN ñM¾×vÝb§ä¾ÏW­C

®¾O¯y¦k

>>-disable_MQFunctions----n--database----u--userid-------------->

>-----p--password----------------------------------------------><


®¾Oø¥¬’

-n database
     ®¸w÷ˆ©’©wÝW§ë­C

-u userid
     ®¸w¾×ùàüsñæ÷ˆ©’©w¦§ùØ¾×¦Þ ID­C

-p password
     ®¸wùØ¾×¦Þ ID ¦§üqÝ‘«X­C

«dùã

ÝbÏUÝC«dùãÏÏ­AÏwøñ¾×÷ˆ©’©w SAMPLE ¦§ DB2MQ ¾\î…­C

   disable_MQFunctions -n sample -u user1 -p password1

  ------------------------------------------------------------------------

§èýzÏuùÆ

ü­¾ö¾¨ì

   * ññùŒÏÏÏá
        o 18.1 §èýz DB2 Server for VSE & VM Ý›¦Aóûî…ÏO
        o 18.2 Java 1.2 Ï„ï¸ññùŒÏÏÏá
        o 18.3 Ýb Windows õ@ú~ùtý×ÏUùØ¾×«uÏW¯­¸£¦§­uæL©Žñô©|­v¨—¯~
        o 18.4 OS/2 ùtý×ÏU¦§ Java ññùŒÏÏÏá
        o 18.5 Ýb Windows õ@ú~ùtý×ÏõýõøÒÏ‚¯x·Óæ›ÏwõûÝùÏuõ@¦§­u·©ž¸éæïÝs
          ù£­v¨—¯~
        o 18.6 ÝhÝ÷mõ¢úsï£÷åüsñæ
        o 18.7 DB2 for OS/390 ¦§ññùŒÏÏÏá
        o 18.8 OS/390 ññùŒÏÏÏá¾ýðn¦§ðž¾¨æ{Ý­
        o 18.9 ­u®¾á¦ô­¬h­vû‹÷š©¦§šõ¢
        o 18.10 DB2 ññùŒÏÏÏá¦§§ÇÇ›ñ’÷¥
        o 18.11 UNIX ùtý×ññùŒÏÏÏá¦§§ÇÇ›ñ’÷¥
        o 18.12 OS/2 ¾iî…¦§ Infopop øíÇD
        o 18.13 jdk11_path ª[§cø¥¬’¦§¯­¸£
        o 18.14 ùØ¾×­uScript ÏÏÏá­v¸×­uýõøÒÏ‚¯x­v©æo¾Ö¦§ Solaris ùtý×¨—¯~
          (SQL10012N)
        o 18.15 DPREPL.DFT ·©ž¦§¯­¸£
        o 18.16 ñãøÒÝhðàññùŒÏÏÏá applet
        o 18.17 ññùŒÏÏÏá¾H Applet øäÝ‘©¦§«uÏW¯­¸£
        o 18.18 Ýb Applet ¬ãÝ­ (Windows 95) ÏUøäÝ‘ññùŒÏÏÏá
        o 18.19 ùØ¾×Ïj¦§ªd÷áæý¦G

   * ÷ˆøTÏÏÏá
        o 19.1 Ýb Windows õ@ú~ùtý×ÏU¦§­uæL©Žñô©|­v¨—¯~
        o 19.2 ú¡ Netscape Ïwô}ñã©­AÝb Netscape Navigator ÏÏô}ñã¾~ü­ Web
          Çæý(UNIX ùtý×)
        o 19.3 ñãøÒ­u÷ˆøTÏÏÏá­v¦§øíÇD

   * §‰’F
        o 20.1 Ýb®¾á÷ˆ©’©w§‰’Fü]¸w¶X¾RÏjÏp
        o 20.2 MQSeries ¯ýõU§‰’F
        o 20.3 OLE DB ¯ýõU§‰’F

  ------------------------------------------------------------------------

ññùŒÏÏÏá

  ------------------------------------------------------------------------

18.1 §èýz DB2 Server for VSE & VM Ý›¦Aóûî…ÏO

DB2 Universal Database ¦¸¾¯ 7 ­uññùŒÏÏÏá­v¬Wñjû‹ DB2 Ý›¦Aóû for VSE ¸M VM
÷ˆ©’©w¦§Ï„ï¸­C­uññùŒÏÏÏá­v·Óæ›¸ãÝü VSE ¸M VM ÷ˆ©’©w¦®¾¢¦§ DB2 Ý›¦Aóû­C ÝP©
Ï]Ï„ï¸®¾áîµÏè­Bð®ýåîµÏè­Bõ¢úsý×ðpðÔ¸Mð®úsüsæý®¾O­C ð®ýåîµÏè¸Mð®úsüsæý¯íðn
·xÝsæ{õ€­AÝà÷à·xÝsæ{õ€øäÝ‘¸¢ VSE ¸M VM ¾Dûq÷œÏW¦§ DB2 Ý›¦Aóû­C Ýû·xÝsæ{õ€¾¥
ññùŒÏÏÏá¸ãïœù¥­AóA¾×¸¢ VSE ¸M VM ÏU DB2 Ý›¦Aóû¦§ VSE ¸M VM îS¸Ò­C

óÆÝXññùŒÏÏÏá©eü\ùØ¾×¦Þ§èýz DB2­AæL«ž DB2 Ý›¦AóûøäÝ‘¸¢ù§Ï@ðà¾ð¾x­CVSE ¸M VM
¦®¾¢¦§ DB2 Ý›¦AóûÆ¾šÝbññùŒÏÏÏá¾Dæ›æ­­AøœÏF DB2 Universal Database ¦®¾¢­C
¨‹ù£¦®¾¢©­Aú|¸I¾s§èýzüoù€¦®¾¢¦§ªêû‹·üøÒõ@¸MÏ«¾×æ{Ý­­C «dùã­AùØ¾×¦Þ¾i¾HÝC¾š
îSõO÷ˆ©’©w¦§îµÏè­A¨‹ù£ù„ÏÏ¦§Ï@ðàîµÏèùÇñNÏõð®ýå­C ùØ¾×¦ÞÏ]¾i¾HÝC¾š÷ˆ©’©w¦§¦¡
©‘­AùÇøäÝ‘õ¢úsý×ðpðÔ­A¸×¸w÷q¦¡©‘ªøõê¬gùàú«­C

ÝüÇ”ª[§cññùŒÏÏÏá­AùÇÝb VSE ¸M VM ¦®¾¢¦§ DB2 Ý›¦AóûøäÝ‘§èýzõ@ú~¦§÷ˆøT­A«Ñø¥
úà DB2 Connect User's Guide¸×Ýw÷Ó¯Pª[§c÷¾R­C
  ------------------------------------------------------------------------

18.2 Java 1.2 Ï„ï¸ññùŒÏÏÏá

ùØ¾× Java 1.2 ÏÏ¦§¶—ÝVÏ„ï¸­AññùŒÏÏÏá¾i¾HÏ„ï¸¶—ÝV¯yù¾­AÝp¦¸âõB¯y¸Mõ’õBùà
¯y­C ÝûÏ„ï¸¾u¾i¾×¸¢ Windows NT ¾ð¾x­C

ñì¨‰Ç¥¸MùØ¾× Java 1.2­AññùŒÏÏÏáðnôiÝ‘Ýw÷Ó­G

  1. JDK 1.2.2 Ýb DB2 UDB CD ¦§ DB2\bidi\NT ¾¨ìÏU­C
     ibm-inst-n122p-win32-x86.exe ªOÝw÷Óæ{Ý­­A ibm-jdk-n122p-win32-x86.exe
     ªO JDK Ï·øe­CñNùƒðà·©ž«’¯sùæw§ÑÏW¦§¬Ô©¾¨ìÏÏ­A æM® ñq÷à¾¨ìøäÝ‘Ýw÷Ó
     æ{Ý­­C
  2. ñN¾ÝÝw÷ÓÝb <DB2PATH>\java\Java12 ÏU­A<DB2PATH> ªO DB2 ¦§Ýw÷Ó÷“©|­C
  3. JDK/JRE Ýw÷Óïœ¾š©­AÏœðn¨‹ù£ JDK/JRE ªøùtý× VM­C

Java 1.2 Ýw÷ÓÝù¾\® ­A¾H¾¨ñ`ÏŠÝ­ñãøÒññùŒÏÏÏá©ú|ùØ¾× Java 1.2­C

ñìøñÏŒùØ¾× Java 1.2­A«ÑÝb <DB2PATH>\java\Java12 ÏU÷¥øœÝw÷Ó JDK/JRE­A¸×õ¢õ‹
<DB2PATH>\java\Java12 Ý÷¾¨ì¦§ÝWÝr­C

æ—:
     ÏœðnýVýc <DB2PATH>\java\Java12 ¸M <DB2PATH>\Java12­C <DB2PATH>\Java12
     ªO DB2 Ýw÷Ó¦§Ï@ü­¾ö­AùÇ¾B¾]ªA Java 1.2 ¦§ JDBC Ï„ï¸­C

  ------------------------------------------------------------------------

18.3 Ýb Windows õ@ú~ùtý×ÏUùØ¾×«uÏW¯­¸£¦§­uæL©Žñô©|­v¨—¯~

ùØ¾×ññùŒÏÏÏá«uÏW¯­¸£­Añz¾iî…ú|ûJùüo¬Ó¦§¨—¯~­G­uæL©Ž¦§ñô©|­v­CÝp¦GñzüÞ¦¤Ýw
÷ÓÏFús¦§ Web ¶sŽìóû¸× Web ¶sŽìóûús¦¸­A«Ñ«T¸w HTML ¸M HTM Ï†¾¢¸Mõ¢õ‹ûL¦§¶sŽì
óûªêæýÝX­C «Ñø¥ó\æ›æ­¯­¸£¾DÇD­uô}ñã·©ž©šõ¢æ{Ý­¦§ñãøÒ­v­C
  ------------------------------------------------------------------------

18.4 OS/2 ùtý×ÏU¦§ Java ññùŒÏÏÏá

ññùŒÏÏÏá¾ýôúÝw÷ÓÝb HPFS ©‘Ý­Ï’¦§§Ø§ÑóöÏW­C
  ------------------------------------------------------------------------

18.5 Ýb Windows õ@ú~ùtý×ÏõýõøÒÏ‚¯x·Óæ›ÏwõûÝùÏuõ@¦§­u·©ž¸éæïÝsù£­v¨—¯~

Ýb DB2 Universal Database for Windows NT ÏW­A Ýb÷åûØô}ñãýõøÒÏ‚¯xùà·Óæ›Ýb
­uScript ÏÏÏá­v¸ã®¾á¦§Ïuõ@¸£ýà©­Aæo¾Ö­u·©ž¸éæïÝsù£­v¦§¨—¯~­C Ïuõ@¦ª§AÆ
¾šõûÝù­C ðY­uScript ÏÏÏá­vÏÏ®¾á¦§Ïuõ@õtÝü START ®¾O­A®Kú|æo¾Öüo¬Ó¦§Ý‘ªø­C
ªøÏFµžõKüo¬Ó¦§Ý‘ªø­A«ÑÝbõ†Ý÷·¸MÏuõ@Ï§­A ùØ¾× START/WAIT ®¾O­AÝàÏœðnùØ¾×
START ®¾O­C
  ------------------------------------------------------------------------

18.6 ÝhÝ÷mõ¢úsï£÷åüsñæ

ÝhÝ÷mõ¢úsï£÷åüsñæÝb¦¸¾¯ 7 ­uññùŒÏÏÏá­v¦§¾\î…­Aªø¾¬Ñ©žùã¦§¦¸¾¯¸ãððùŒ­C­u¯ú
§í­vï£÷åüsñæ¾\î…ñìøäÝ‘¦§¾¬Ñ©žùã­A ÝšÏ™¯íðn¦¸¾¯ 7­C ñìÝb¦¸¾¯ 6 øäÝ‘ÝhÝ÷mõ¢
úsï£÷åüsñæ¾\î…­A«ÑÝb¾¬Ñ©žùãÏÏïœùññùŒÏÏÏá­AùÇÝbù§ù…øäÝ‘¾Ý­C
  ------------------------------------------------------------------------

18.7 DB2 for OS/390 ¦§ññùŒÏÏÏá

õQ¾×OS/390 ¦§ DB2 UDB ññùŒÏÏÏáùà§èýzñ¶vÏ«¾×æ{Ý­¦§ùØ¾×­C û‹¸¢ OS/390 ¦§ DB2
UDB­AÏ«¾×æ{Ý­ù‡¬’ªO¨W¾áÝüôôõ€îS¸Ò¦§Ï÷î·­AÝb¾ÝüQ DB2 ññùŒÏÏÏá§èýzÏõ®e­A¾ýôú
ñ¶v¸MÝw÷ÓÝb·“ûãÏ§­C

÷ˆ©’©w DB2 for OS/390 Ïlùtý×­AññùŒÏÏÏáú|¸w÷q "CC390" ÷ˆ©’©w­Aõ@ªøññùŒÏÏÏá¦§
Ï§ü­Ï„ï¸­C «ÑÏœðnðžõ‹Ýû÷ˆ©’©w­C

µ”æMÝbññùŒÏÏÏá¾¨ì¸×÷ˆøTÏÏÏáõ@ú~÷ˆøTÏÏ­AùSÝüîSõOïœù DB2 for OS/390 ¦¸¾¯
7.1­AÝìªO­A÷àÏ†¾¢Ï„ï¸ OS/390 ¦¸¾¯ 7.1 DB2 ¦§ù‡¬’­C ®šÝh DB2 for OS/390 ¦¸¾¯
6 ¦§îS©¡ù‡¬’­A¸M DB2 for OS/390 ¦¸¾¯ 7.1 ªêÇ”­CÝüù€ DB2 for OS/390 ¦¸¾¯ 7.1
¦§îS©¡ù‡¬’­AÝb¾¨ìÏÏùSÝü¦¸¾¯ÝW§ë­C ÝbññùŒÏÏÏáª[§c DB2 for OS/390 ¦¸¾¯ 7.1
Ïlùtý×Ïõ® ­Aû‹¸ãÝü÷à¦¸¾¯¦§Ï†¾¢üœÝüÝsù£vðð­C

ñìÝêññùŒÏÏÏáÝsù£¸MùØ¾× Generate DDL ù‡¬’­A«ÑÝw÷Ó Generate DDL ù‡¬’­G

   * Ç”¸¢¦¸¾¯ 5­AùØ¾× DB2 for OS/390 ¦¸¾¯ 5 ùàÝw÷Ó DB2Admin­C
   * Ç”¸¢¦¸¾¯ 6­AÝw÷ÓÏp¦§æ{Ý­ü]ðp¾[ñj¾\î…­Aû‹¸¢ DB2 for OS/390 ¦¸¾¯ 7.1 §è
     ýzîS¸ÒÝàù¾ïNÝp PTF î‰­C
   * Ç”¸¢¦¸¾¯ 7.1­AGenerate DDL ù‡¬’ªø¨W¾á¸w¯—Ïõ DB2 for OS/390 ¦¸¾¯ 7.1 §è
     ýzîS¸ÒÏõÏ@ü­¾ö­C

ñìñqññùŒÏÏÏáÝsù£·xÝsæ{õ€®÷móû­AÝbñãøÒ DB2 UDB ññùŒÏÏÏá©­A¾ýôúôiÝ‘Ýw÷Ó­C
¾ÝªO DB2 ·ü¾×æ{Ý­ô}æoñqŽíî÷¦§Ï@ü­¾ö­C

ñìÝbÏuõ@î÷ªø OS/390 Ïlùtý×«s¾ DB2­A«Ñ¨‹óšùØ¾×ñqŽíî÷ª[§c¯ýõUæ{Ý­ÏuùÆ­C

  1. Ýb­uùàú«­vðôðñ­A®¸wÝêÝ‘ª[§c¯P÷ˆ©’©w¦§üs«uôˆôs­C
  2. Ýb­uüq®Hù¢¸w­vðôðñ­AõûÝùóAú¡¦§üq®H÷ˆøT­C
  3. Ýb­u÷ˆ©’©w­vðôðñ­A¸¢÷ˆ©’©wÝW§ëŽ‘Ý®¸wÏlùtý×ÝW§ë­C
  4. Ýb­u÷`¶I¨‹ôæ­vðôðñ­A¨‹ù£ª[§c÷`¶I¨‹ôæ (¨‹¾×¦§)ÏŽ¨‹©­C
  5. Ýbõ@ú~ùtý×Ž‘Ý¨‹ù£­uMVS/ESA, OS/390­v­C
  6. ®”Ï@ÏUõûÝù­A¾HõûÝùª[§c­C

ðYðnüzûLûhûDóöóûùà«s¾ DB2 for OS/390 Ïlùtý×­A «Ñ¨¡ï`ÏWðzûhûDóöóû¦§ùB’J
1-6­CæM® ­G

  1. ÝbñqŽíî÷óöóû­AñãøÒññùŒÏÏÏá­C
  2. Ýb­uùtý×­v÷ˆ©’õùÏW®”Ï@ÏUú’û®¾kµ„­AÝA¨‹ù£ús¬W­C
  3. Ýb­uús¬Wùtý×­vû‹÷š©Ï§­AÝbùtý×ÝW§ëŽ‘Ýµ„ÏJûhûDóöóûÝW§ë­C
  4. Ýb¯ú§í©žùãŽ‘Ýµ„ÏJ DB2DAS00­C
  5. øwû‹ TCP/IP üq®Hù¢¸w (Ýb­uüq®Hù¢¸w­vø¥¬’÷Þ)­A «ÑÝb¾Dûq÷œÝW§ëŽ‘Ý®¸wûh
     ûDóöóû¦§¾Dûq÷œÝW§ë­C
  6. Ýb¦AøÔæ{Ý­ÝW§ëµ„ÏJ 523­C
  7. ®”Ï@ÏU«T¸wùàús¬Wùtý×­C ñz·ü÷à¾i¾HÝbùtý×÷ˆ©’õùÏUðñªíùús¬W¦§ûhûDóöóû­C
  8. ©iô}ûhûDóöóûÝW§ë­C
  9. Ýb­u©žùã­v÷ˆ©’õùÏW®”Ï@ÏUú’û®¾kµ„­AÝA¨‹ù£ús¬W­C
 10. Ýb­uús¬W©žùã­vû‹÷š©ÏÏ­A®”Ï@ÏUï_ús­A ÝC¾XûhûDóöóûÏW¾i¾×¦§©žùã­C Ýp¦Gûh
     ûDóöóûªø Windows NT ùtý×­A®hú|Ýb©žùã DB2 ÏU«s¾ DB2 for OS/390 Ïlùt
     ý×­C
 11. ¨‹ù£©žùã­C Ýû©žùãú|ÝêøÒô¤¬güq®Hù¢¸wø¥¬’­C
 12. ®”Ï@ÏU«T¸wùàús¬W©žùã­C
 13. ô}ñã©žùã÷ˆ©’õù­A¾i¾HªíùðŠÏ~ús¬W¦§©žùã­C
 14. ©iô}©žùã­C
 15. Ýb÷ˆ©’©w÷ˆ©’õùÏW®”Ï@ÏUú’û®¾kµ„­A ÝA¨‹ù£ús¬W­C
 16. ®”Ï@ÏUï_ús­AÆ¾šûhûDóöóûÏW¦§¾¯§í÷ˆ©’©w­C Ýp¦GñzðnÝb­uús¬W÷ˆ©’©w­vû‹÷š
     ©ÏÏús¬W DB2 Ïlùtý×­A «Ñ¸¢­u÷ˆ©’©wÝW§ë­vŽ‘Ýµ„ÏJÏlùtý×ÝW§ë­C ¨‹ôæ­G¨‚
     ÏJÏlùtý× (¸×ªO÷ˆ©’©w) ¦§¾¯§íõOÝW­C
 17. ®”Ï@ÏU«T¸w­C

ý{Ýb­AñzÏw÷gÝù¾\ÝaÝbññùŒÏÏÏáús¬WÏlùtý×­C ô}ñã÷ˆ©’©w©­Aú|Æ¾š DB2 for
OS/390 Ïlùtý×­C

"ññùŒÏÏÏá 390" üû÷`¦§ýŽÏ@ðàªq÷ù®¾X­G

OS/390 ¦§ DB2 UDB ññùŒÏÏÏá¾iìñz§èýzÏwñ¶v IBM DB2 Ï«¾×æ{Ý­¦§ùØ¾×­C
ðYªø DB2 UDB for OS/390 ðàõOðqµÒîS¸Ò¦§Ï÷¾¢ÏÏ¦§Ï«¾×æ{Ý­ù‡¬’­A

Ýb¾¥ DB2 ññùŒÏÏÏá§èýzÏõ®e­A¾ýôú÷gûLñ¶v¾BÝw÷ÓÝb·“ûãÏÏ­C

Ýûüû÷`·üõ‹ªø­G

OS/390 ¦§ DB2 ññùŒÏÏÏá¾iìñz§èýzÏwñ¶v IBM DB2 Ï«¾×æ{Ý­¦§ùØ¾×­C
ðYªøðàõOðqµÒýœ®~¦§Ï÷¾¢ÏÏ¦§Ï«¾×æ{Ý­ù‡¬’¾ýôú÷gûLñ¶v¾BÝw÷ÓÝb·“ûãÏÏ­A
Ï~î…¾¥ DB2 ññùŒÏÏÏáùà§èýz­C

  ------------------------------------------------------------------------

18.8 OS/390 ññùŒÏÏÏá¾ýðn¦§ðž¾¨æ{Ý­

ñN APAR PQ36382 Ïè¾×ù DB2 for OS/390 ¦¸¾¯ 5 ¸M DB2 for OS/390 ¦¸¾¯ 6 ¦§
390 « î…îS¸Ò­AùØ¾× DB2 UDB ññùŒÏÏÏá¦¸¾¯ 7 ùàøäÝ‘üoù€Ïlùtý×¦§Ï«¾×æ{Ý­­C

Ïè¾× APAR ÝšÏUÝC¦§ FMID­G

   DB2 for OS/390 Version 5 390 Enablement: FMID JDB551D
   DB2 for OS/390 Version 6 390 Enablement: FMID JDB661D

  ------------------------------------------------------------------------

18.9 ­u®¾á¦ô­¬h­vû‹÷š©¦§šõ¢

"<<" Ï× ">>" ®”ôsÏwÝê­u®¾á¦ô­¬h­vû‹÷š©ÏÏøœ¾h­C
  ------------------------------------------------------------------------

18.10 DB2 ññùŒÏÏÏá¦§§ÇÇ›ñ’÷¥

Ýb­uõ™ütÏJ¦—­vÏ@©¥¦§­uññùŒÏÏÏá¦§Ýw÷Ó¯Pª[§c­vÏ@üûÏÏ­Aù„­u§ÇÇ›ñ’÷¥÷ˆøT­v Ï@÷`
ú|õiôDñzÝbñN­uññùŒÏÏÏá­v¾×ªø applet ©ðYæo¾ÖøíÇD­A·üÝpÝ¢ñq¸R¾Oæ›æ­ ÏÏð®ü]ñz
ñqŽíî÷¶sŽìóû¦§ CLASSPATH­C ¾¯÷`¾‡ú|¯­¸£ÝpÝ¢ñq®eðz¦§¸R¾Oæ›æ­ñãøÒ¶sŽìóû­A Ýì
®o¾¬ïœù¥ñãøÒ¶sŽìóû¦§®¾O­C ðYðnñãøÒ Internet Explorer­A«Ñµ„ÏJ start
iexplore­A æM® ®” Enter µ„­C ðYðnñãøÒ Netscape­A«Ñµ„ÏJ start netscape­AæM® 
®” Enter µ„­C üoù€®¾O®Yøýü]¶sŽìóûÏwü]Ýbñz¦§ PATH ÏÏ­C ÝpðYÏœæM­A«ÑñNù„¾[ÏJ
ñz¦§ PATH ÏÏ­A ¸×ªOÏµï®ù¶sŽìóû¦§Ýw÷Ó¾¨ì­Að®úsæo¾X start ®¾O­C
  ------------------------------------------------------------------------

18.11 UNIX ùtý×ññùŒÏÏÏá¦§§ÇÇ›ñ’÷¥

Ýp¦GñzæL¦kÝb UNIX ®ªùtý×ñãøÒññùŒÏÏÏá­A®hü]¸w JAVA_HOME ·“ûãš¬’®ÝV Java Ï·
øe­G

   * Java Ýw÷ÓÝb /usr/jdk118­A«Ñü]¸w JAVA_HOME ù /usr/jdk118­C
   * û‹¸¢ sh­Bksh­Bbash shell­G

        ôž¾X JAVA_HOME=/usr/jdk118.

   * û‹¸¢ csh ¸× tcsh shell­G

        setenv JAVA_HOME /usr/jdk118

  ------------------------------------------------------------------------

18.12 OS/2 ¾iî…¦§ Infopop øíÇD

Ýp¦GñzªOÝb OS/2 ÏWøäÝ‘ññùŒÏÏÏá­AùØ¾×÷¥¦R®ž 1024x768 Ï× 256 Ýƒ­A ùÇñã¾×ÏF
WorkPlace Shell Palette Awareness­A®hôW¾Xý{Ý‘æ›æ­Ç„©¦§ Infopop ú|¾Hô¶ÝƒÏ†
ÝrÆ¾šÝbô¶ÝƒðIï§ÏU­C ñìðž¾¨ÝûøíÇD­Ašõ¢Æ¾šü]¸wªø 256 Ýƒ¾HÏW­A¸×øñÏŒùØ¾×
Workplace Shell Palette Awareness­C
  ------------------------------------------------------------------------

18.13 jdk11_path ª[§cø¥¬’¦§¯­¸£

ÝbññùŒÏÏÏá¯­¸£Ï§­AJDK 1.1 Ýw÷Ó÷“©| (jdk11_path) ª[§cø¥¬’¦§¯­¸£­A ¸¢Ïl¬ÑÇDÏè
¾×ÝšÏUÏ™ÏFÏ@Ý‘­C ­uÏè¾×Ýš­vÏUõûóÆ¦§ÝC¾šªø­G

   * ¾¯§í¸M¯ú§íñqŽíî÷¦§÷ˆ©’©wÝ›¦Aóû
   * ñqŽíî÷
   * ùÆÝü¾¯§íñqŽíî÷¦§÷ˆ©’©wÝ›¦Aóû
   * ùÆÝü¾¯§íÏ×¯ú§íñqŽíî÷¦§Ï·ü×÷ˆ©’©wÝ›¦Aóû
   * ùÆÝü¾¯§íñqŽíî÷¦§«ÇªP÷ˆ©’©wÝ›¦Aóû

  ------------------------------------------------------------------------

18.14 ùØ¾×­uScript ÏÏÏá­v¸×­uýõøÒÏ‚¯x­v©æo¾Ö¦§ Solaris ùtý×¨—¯~
(SQL10012N)

Ýb¨‹ù£­uScript ÏÏÏá­v¸×­uýõøÒÏ‚¯x­vÏÏ¦§ Solaris ùtý×©­A¾iî…ú|æo¾ÖÏUÝC¨—
¯~­G

   SQL10012N - ú¡÷ÏJ®¸w¦§·©ž©w "/udbprod/db2as/sqllib/function/unfenced/
   db2scdar!ScheduleInfoOpenScan"©­AñæÝªù®Dûwïµ¦§õ@ú~ùtý×¨—¯~­C
   SQLSTATE=42724­C

üoªO¾¥¸¢ Solaris øäÝ‘ÇæýóûÏÏ¦§¨—¯~¸ãóðP­Cñz¾u¯íÏè¾×ÏUÝC¦§ðž÷æ{Ý­­AõY¾iõ¢
¾¨ÝûøíÇD­G

   105490-06 (107733 ý^ùOÏF 105490) for Solaris 2.6

  ------------------------------------------------------------------------

18.15 DPREPL.DFT ·©ž¦§¯­¸£

Ýb­uññùŒÏÏÏá­vÏÏ­A­uÏuùÆü]¸w­væõøO¾¯Ïõ­uõê¬g­vðô¦§¯­¸£ùB’J 5d ¬gûD­G

   ñN·©ž·xÝsù­uññùŒÏÏÏá­v¦§Ïuõ@¾¨ì (ùãÝp­ASQLLIB\BIN)­A
   ÝpÝûÏ@ùà­Aùtý×¾i¾HùØ¾×ù„õ@ªøûwü]·©ž­C

·üõ‹¬gªø­G

   ñN·©ž·xÝsù­uññùŒÏÏÏá­v¦§Ïuõ@¾¨ì (SQLLIB\CC)­A
   ÝpÝûÏ@ùà­Aùtý×¾i¾HùØ¾×ù„õ@ªøûwü]·©ž­C

  ------------------------------------------------------------------------

18.16 ñãøÒÝhðàññùŒÏÏÏá applet

ñzÏœî…ÝbÏ@¾xóöóûÏWÝP©ñãøÒÏ@ðà¾HÏW¦§ññùŒÏÏÏá applet­CüoôæððùŒóA¾×¸¢¸ãÝüÏ„ï¸
¶sŽìóû¸ãøäÝ‘¦§ññùŒÏÏÏá applet­C
  ------------------------------------------------------------------------

18.17 ññùŒÏÏÏá¾H Applet øäÝ‘©¦§«uÏW¯­¸£

ú¡­uññùŒÏÏÏá­vªO¾H applet ÏŠÝ­øäÝ‘©­AF1 µ„¾uî…øöÝbùÆÝü Infopop ¾\î…¦§æ›æ­
¸×æõøO¾¯ÏÏûBõ@­C

ñz¾i¾HÝbÏUÝCÏ÷¾¢ÏÏ®” F1 µ„­A¾s¾X Infopop­G

   * DB2 Universal Database for OS/390
   * §‰’F

øœÏWðzùƒôæ¾H¾~¦§­uññùŒÏÏÏá­vÏ÷¾¢ªãæL¦kùØ¾× F1 µ„¾s¾X¯­¸£­C Ýû©ðYðnÆ¾šù„¾Ý
Ï÷¾¢¦§¯­¸£­A«ÑùØ¾×­u¯­¸£­v®”ôs¸×­u¯­¸£­vÏU¸â¾\î…¦¡­C
  ------------------------------------------------------------------------

18.18 Ýb Applet ¬ãÝ­ (Windows 95) ÏUøäÝ‘ññùŒÏÏÏá

ðY®¸w¦§ùØ¾×¦Þ ID ¸MñK«XæL©Ž­A®KæL¦kô}ñã­uScript ÏÏÏá­v­C ænÏJ­uññùŒÏÏÏá­v
©­A«Ñ«T¸wùØ¾×¦Þ ID ¸MñK«XªOõ_Ýü©Ž­C
  ------------------------------------------------------------------------

18.19 ùØ¾×Ïj¦§ªd÷áæý¦G

ù„ÏŠ®KùØ¾×¦Þýœ¾Öô€Ý^ÏjôqÝC¬’¦§ªd÷á­CÏœÏàóAÝXùØ¾×¦Þ¾×ùàûwï£ûˆ¯éô€Ý^¦§ÝC¬’­C
Ç”¸¢¾iî…ô€Ý^¬’¾HÏdðp¸×¬’¾H÷UðpÝC¬’¦§ªd÷á­AÝüÏUÝCùƒðàøíÇD­G

  1. ¯íðn¦ ôO®šÝh©ô­Ï~î…ù£ñoæý¦G­C
  2. ¯íðnÏjôq¦§ñqŽíî÷øOóÑ‚Ï~î…®OÝsæý¦G­C

ªøÏFùØüoðàüBýzõ¢¾[®KõQ­ADB2 ñNÏjôqæý¦GôøÏ·ü×Ýùü\ÝhÏ—ªq­C ¾HÏ@Ý÷Ï@ðàÏ—ªq¦§ÏŠ
Ý­¶^ù£Ï×Æ¾šªd÷áæý¦G­C

æý¦GÝpÏU­G

  1. ú¡ªd÷á¦§ýŽÏ@ðàÏ—ªq¾i¾H·Óæ›­AÝP©Ïw¶^ù£ü¥ólÏ—ªq©­Aú|ïŒÏ™Æ¾š©ô­­C
  2. ú¡Ýb¾“Ý¢©®¸w©ô­ÏWñqŽíî÷ôÔ·xÝsªd÷áæý¦G¦§Ï@ðàÏ—ªq­Aú|ïŒÏ™ñqŽíî÷¦§øOóÑ
     ‚¯íùD­C

ññùŒøOóÑ‚ÏÏ¦§ªd÷áæý¦GÝC¬’­G

  1. ô}ñã­uÏuùÆü]¸w­væõøO¾¯¦§­uÏ@î‰­vðôðñ­C
  2. ÝbüÞÏjðÔøØªqÏÏ­A¨‹ù£­G
        o «dùãÏ§©e­A¾iððùŒ­u«dùãÏ§©e­væ›æ­ÏÏÆ¾š¦§æý¦GÝC¬’­C Ýb¨‚ÏJŽ‘ÝÏÏ®
          ¸wæý¦Gôø¦§Ï—ªqÏjÏp (ÝC¬’)­C
        o ¸R¾OÏÏÏá­A¾iððùŒ­u¸R¾OÏÏÏá­v¦§­uªd÷áæý¦G­vðôðñÏWÆ¾š¦§æý¦GÝC¬’­C
          Ýb¨‚ÏJŽ‘ÝÏÏ®¸wæý¦Gôø¦§Ï—ªqÏjÏp (ÝC¬’)­C

ú¡ùØ¾×­u«dùãÏ§©e­væ›æ­¸×­u¸R¾OÏÏÏá­v¦§­uªd÷áæý¦G­vðôðñÏW¦§ªd÷áæý¦G©­A øOóÑ
‚ÏÏÝC¬’Ž‘Ý®¾š®OîdÝbøOóÑ‚ÏÏ¦§ªd÷áÝC¬’­C Ýû¬’¾æïÏœú|Ïj¸¢üÞÏjðÔü]¸w­C®”Ï@
ÏUÏUÏ@ùB­A¶^ù£Ýšæý¦Gôø¦§ÏUÏ@ðàÏ—ªq­C ú¡ÏUÏ@ùB®Dõ@¾×ÏÏ©­A¦¡¾šñzÏwùûFæý¦Gôø
õ·§í­C
  ------------------------------------------------------------------------

÷ˆøTÏÏÏá

  ------------------------------------------------------------------------

19.1 Ýb Windows õ@ú~ùtý×ÏU¦§­uæL©Žñô©|­v¨—¯~

ùØ¾×÷ˆøTÏÏÏá­Añzú|æoý{ÝpÏU¦§¨—¯~­G­uæL©Žñô©|­v­C Ýp¦GñzüÞ¦¤Ýw÷ÓÏFús¦§ Web
¶sŽìóû¸× Web ¶sŽìóûús¦¸­A«Ñ«T¸w HTML ¸M HTM Ï†¾¢¸Mõ¢õ‹ûL¦§¶sŽìóûªêæýÝX­C «Ñ
ø¥ó\æ›æ­¯­¸£¾DÇD­uô}ñã·©ž©šõ¢æ{Ý­¦§ñãøÒ­v­C
  ------------------------------------------------------------------------

19.2 ú¡ Netscape Ïwô}ñã©­AÝb Netscape Navigator ÏÏô}ñã¾~ü­ Web Çæý(UNIX
ùtý×)

Ýp¦GÏw÷gô}ñã Netscape Navigator­AùÇÆ¾š¾¯§í DB2 HTML Ï†¾¢¸×¾~ü­§“î÷­A ÷åûØ
ñq­u÷ˆøTÏÏÏá­vô}ñã¾~ü­§“î÷ñNóðP Netscape æo¾Ö¨—¯~­C ¨—¯~ú|ïœù "Netscape
õ„ÏœùÝW§ëªø <external site> ¦§·©ž¸×¾¨ì"­C

ðYðn÷¥ùMüoðàøíÇD­A«ÑÝbô}ñã¾~ü­§“î÷Ïõ®e­AÇ”üªô}ñã¦§ Netscape ¶sŽìóû­C
Netscape ñNð®úsñãøÒùÇø_¸l¾~ü­§“î÷­C

«Ñ¦`úN­AõQ¾×Ïwô}ñã¦§ Netscape ùàô}ñã¾¯§í DB2 HTML Ï†¾¢Ïœú|æo¾Öüoðà¨—¯~­C
  ------------------------------------------------------------------------

19.3 ñãøÒ­u÷ˆøTÏÏÏá­v¦§øíÇD

ÝbªYù€ùtý×ÏW­AðYñzùØ¾×­uô}¸l¾\î…¦¡­v­B­uýŽÏ@ðàùB’J­v¸× db2ic ®¾Oùà¸I¾s­u÷ˆ
øTÏÏÏá­v­AñãøÒüt®žú|®Dñ`§C­C ðYûJùüoðàøíÇD­A«ÑñãøÒ­uññùŒÏÏÏá­v­A æM® ¨‹ù£
¯­¸£ --> ÷ˆøTÏÏÏá­C
  ------------------------------------------------------------------------

§‰’F

  ------------------------------------------------------------------------

20.1 Ýb®¾á÷ˆ©’©w§‰’Fü]¸w¶X¾RÏjÏp

¾i¾HùØ¾×®¾á÷ˆ©’©w§‰’Fùàü]¸wús®÷ˆ©’©wÏõùØ¾×¦Þ¦¡©‘¦ô­¦§ (ÏœªO¾¨ì¸×¬Ô©¦¡
©‘¦§¦¡©‘¦ô­) ¶X¾RÏjÏp¸Mûw¾ìïœù£ÏjÏpø¥¬’­C¾uÝüú¡ùØ¾×¦Þ¦¡©‘¦ô­Ýb­uùØ¾×¦Þ¦¡
©‘­v§‰’F®¸wÝšÏ™Ï@ðàøt÷møØ©­AÏ~ú|ñã¾×ÝûîS¸Ò­C
  ------------------------------------------------------------------------

20.2 MQSeries ¯ýõU§‰’F

DB2 ¦¸¾¯ 7.2 ïœù¥ús¦§ MQSeries ¯ýõU§‰’F­CÝû§‰’F®¾áÏ@ðà¦¡©‘ù‡¬’­A ùØ¾× DB2
MQSeries Functions ùà¦ù£ MQSeries ÝŒÝC­A DB2 MQSeries Functions ¾‡ªø¦¸¾¯
7.2 ÏÏ¦§ús¾\î…­C ©éóéñz¦§ü]¸w­AÝû§‰’F¾iñNùCÏ@®h MQSeries øT©õæ›ªøÏ@ðàÝü¸wª
ý÷û¦§ÝrÝˆ­A ¸×Ï@ðà¸T¸w¦›®ž¦§¦«Ž‘ÝrÝˆ­C ®¾á¦§¦¡©‘ù‡¬’¾i©éóéñz¦§ü]¸wùàð†¦R
ÝrÝˆ­A ñNùCÏ@®h MQSeries øT©õô€Ý^ÝùÏ@ÝC¦¡©‘ù‡¬’­C Ýû§‰’F¾‡¾iìñzÝb¦¡©‘ù‡¬’
ÏõÏW®¾áúõýÏ¦¡­AûwŽì MQSeries øT©õ¸M¦¡©‘ù‡¬’æý¦G­C üoðà§‰’F¾iñq­u·xÝsæ{õ€®
÷móû­v¸×­u÷ˆ©’ðš·xÏÏÏá­vùàñãøÒ­C

¾¯§‰’F¦§¯íùDªø­G

   * MQSeries ¦¸¾¯ 5.2
   * MQSeries ·ü¾×æ{Ý­ô€øTÏôðñ (AMI)
   * DB2 MQSeries Function

Ç”¸¢üoù€¯íùD¦§÷âýà÷ˆøT­A«Ñø¥ó\MQSeries­C

Ç”¸¢«dùã¯P MQSeries ¯ýõU§‰’F¦§ñÑó€®ó­A«Ñ÷äÝš
http://www.ibm.com/software/data/db2/udb/ide ¦§ñÑó€®óªq÷ù­C
  ------------------------------------------------------------------------

20.3 OLE DB ¯ýõU§‰’F

Ýû§‰’Fù¢õUñz®¾áÏ@ðà¦¡©‘ù‡¬’­AñqÏ„ï¸ Microsoft OLE DB ¬Ñú€¦§¾tÏ@ðà÷ˆ©’©wïœ
ù¥¦Þùà¦ù£÷ˆ©’­C ¾t¾~­Añz¾i®¾áÏ@ðà DB2 ¦¡©‘­A¾¥ OLE DB ¦¡©‘ù‡¬’ùàïœù¥ü’õï
¦§÷ˆ©’­A ñz¾‡¾i®¾á OLE DB ¦¡©‘ù‡¬’¦§úõýÏ¦¡­Cüoðà§‰’F¾iñq­u·xÝsæ{õ€®÷móû­v
¸×­u÷ˆ©’ðš·xÏÏÏá­vùàñãøÒ­C

¾¯§‰’F¦§¯íùDªø­G

   * OLE DB ïœù¥¦Þ (Ýp Oracle ¸× Microsoft SQL Server)
   * OLE DB Ï„ï¸¾\î…

Ç”¸¢«dùã¯P OLE DB ¯ýõU§‰’F¦§ñÑó€®ó­A«Ñ÷äÝš
http://www.ibm.com/software/data/db2/udb/ide ¦§ñÑó€®óªq÷ù­C
  ------------------------------------------------------------------------

Business Intelligence

ü­¾ö¾¨ì

   * Business Intelligence ñÑó€®ó
        o 21.1 ÷gûLðžðq¦§ Business Intelligence ñÑó€®ó

   * ÷ˆ©’ðš·xÏÏÏá§èýzÏƒ¾U
        o 22.1 §ÇÇ›ñ’÷¥
        o 22.2 ü]÷m Excel ªøðš·xùàú«
        o 22.3 ¸w÷qÏ×øäÝ‘æ{õ€
        o 22.4 ôž¾Xïyðz÷ˆ©’û‹÷š
        o 22.5 ªø Submit OS/390 JCL Ïuõ@Ýˆªyæ{Ý­ (VWPMVS) ¸w÷qðÔ
        o 22.6 šõ¢÷ˆ©’ðš·x«dùã¦ç¨ì
        o 22.7 ÷ˆ©’ðš·xÏÏÏáøT©õ
        o 22.8 Ýb DB2 OLAP Integration Server ÏÏ®¾á©ª[ùÇ÷ÏJ÷ˆ©’
        o 22.9 ñN Classic Connect ¯P÷ˆ©’ðš·xÏÏÏáúføtùØ¾×
        o 22.10 ÷ˆ©’ðš·xÏÏÏá·“ûãæý§c
        o 22.11 ùØ¾× Invert ¶…ï®æ{Ý­
        o 22.12 ¾H DB2 ¦¸¾¯ 7 ðš·x¾Nýzæ{Ý­Ýsù£ DB2 ¦¸¾¯ 5 ÷ˆ©’
             + 22.12.1 ýó¶… DB2 ¦¸¾¯ 5 Ý›¦Aóû
             + 22.12.2 šõ¢¾Nýzæ{Ý­ª[§c
                  + 22.12.2.1 UNIX ðš·x¾Nýzæ{Ý­
                  + 22.12.2.2 Microsoft Windows NT­BWindows 2000 ¸M OS/2 ðš
                    ·x¾Nýzæ{Ý­
        o 22.13 IBM ERwin ïyðz÷ˆ©’ù£¾Xæ{Ý­
             + 22.13.1 Ï§©e
             + 22.13.2 ün‚¯íùD
             + 22.13.3 æ{Ý­·
             + 22.13.4 ®¾á¬Ñ¾š¯yù¾·
             + 22.13.5 ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆ©’ðš·xÏÏÏá­v
             + 22.13.6 ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆøT®ª¨ì§èýzæ{Ý­­v
             + 22.13.7 §ÇÇ›ñ’÷¥
             + 22.13.8 ERwin ¯P DB2 ÷ˆ©’ðš·xÏÏÏá¦§û‹ªM
                  + 22.13.8.1 ERwin ¯P÷ˆøT®ª¨ì§èýzæ{Ý­¦§û‹ªM
        o 22.14 ¨z¨‹­u÷ˆ©’ðš·xÏÏÏá­v¦§ÝW§ë¯PÝõ}
             + 22.14.1
                  + 22.14.1.1 ø•¾¯ðnùD
                  + 22.14.1.2 Trillium ün‚ùtý×Ï÷¾¢
                  + 22.14.1.3 ñN­uTrillium õ†Ý÷ùtý×­v¯P­u÷ˆ©’ðš·xÏÏÏá­vúføt
                    ùØ¾×
                  + 22.14.1.4 ôžÏJ Trillium ïyðz÷ˆ©’
                  + 22.14.1.5 û‹ªMïyðz÷ˆ©’
                  + 22.14.1.6 ððùŒ
             + 22.14.2 ¬ô¬g Trillium õ†Ý÷ùtý× JCL ·
             + 22.14.3 Ýb UNIX ¸M Windows ÏW¬ô¬g Trillium õ†Ý÷ùtý× Script
               ·
             + 22.14.4 ¸w÷q Trillium õ†Ý÷ùtý×ùB’J
             + 22.14.5 ùØ¾×­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­
             + 22.14.6 ¨—¯~üBýzñ`Ý­
                  + 22.14.6.1 ¨—¯~Ý^¶Ñ«X
                  + 22.14.6.2 Ï‚¯x·
        o 22.15 MQ Series ¯P­u÷ˆ©’ðš·xÏÏÏá­v¦§óÆÝX
             + 22.15.1 ®¾á MQSeries øT©õ¦§úõýÏ¦¡
                  + 22.15.1.1 ø•¾¯ðnùD
                  + 22.15.1.2 ððùŒ
                  + 22.15.1.3 ®¾á MQSeries øT©õ¦§úõýÏ¦¡
             + 22.15.2 ôžÏJ MQSeries øT©õ¸M XML ïyðz÷ˆ©’
                  + 22.15.2.1 ø•¾¯ðnùD
                  + 22.15.2.2 ððùŒ
                  + 22.15.2.3 ôžÏJ MQSeries øT©õ¯P XML ïyðz÷ˆ©’
                  + 22.15.2.4 ùØ¾× MQSeries ùØ¾×¦Þ¸w÷qæ{Ý­
                  + 22.15.2.5 ¨—¯~Ý^¶Ñ«X
                  + 22.15.2.6 ¨—¯~Ï‚¯x·
        o 22.16 Microsoft OLE DB ¯P­u÷ˆ©’ýõøÒ¦AøÔ­vÏ„ï¸
             + 22.16.1 ®¾á OLE DB ¦¡©‘ù‡¬’¦§úõýÏ¦¡
             + 22.16.2 ®¾á DTS ÷ˆ©’¾]¦§úõýÏ¦¡
        o 22.17 ¬Wôq COMMIT úføt replace ùØ¾×
        o 22.18 Ï÷¾¢øl¶š÷ˆ©’·ÝW
        o 22.19 AIX Ï× Solaris õ@ú~·“ûãÏW Sybase ùàú«¯íðn¦§ OPEN CLIENT
        o 22.20 «dùãæn¨ìõ¢¾¨
        o 22.21 ýŽ 3 üû ü]¸wðš·xùàú«
             + 22.21.1 û‹ªM Microsoft Access ÏÏ¦§ü’õ¥¨ìŽ‘ÝÝšðš·xùàú«
        o 22.22 ýŽ 10 üû §–@ðš·x÷ˆ©’©w
             + 22.22.1 Çæý¦¡©‘Ýš DB2 UDB RUNSTATS æ{Ý­¦§ùB’JÝ÷Çç®ª
        o 22.23 ûwü]ðš·xññùŒ÷ˆ©’©w
        o 22.24 ðš·xññùŒ÷ˆ©’©w§èýzæ›æ­
        o 22.25 šõ¢õ@¾×ÏÏðš·xññùŒ÷ˆ©’©w
        o 22.26 ®¾á¸Mø_¸lü]¸wðš·xññùŒ÷ˆ©’©w
        o 22.27 ®¾á¦¸¾¯¦§ SQL ùB’J
        o 22.28 Ýb­uæ{õ€¬ã®ª­væ›æ­ÏÏ­Ašõ¢ùàú«¸×¾¬Ñ
        o 22.29 ús¬W¯­¸£Ýš­u÷ˆ©’ðš·xÏÏÏá­v¦®¾¢
        o 22.30 øäÝ‘­u«dùãÏ§©e­v
        o 22.31 «s¨Š Create DDL SQL üîðzÝ­
        o 22.32 ýó¶… Visual Warehouse øàú~·Óæ›
        o 22.33 ®¾á¾¬Ñ¦¡©‘Ï×¾Dðnµ„
        o 22.34 ùØ¾× Merant ODBC XøÒæ{Ý­
        o 22.35 ús® ODBC XøÒæ{Ý­
        o 22.36 ¸w÷q OS/2 ÷ˆ©’©wÏÏ¦§ðš·xùàú«¸×¾¬Ñ
        o 22.37 §Òúçðš·xññùŒ÷ˆ©’©w¦§¦ª§A
        o 22.38 ùØ¾× SQL ¯ýõUæ{Ý­¯P TBC_MD «dùã÷ˆ©’©w
        o 22.39 ùØ¾× FormatDate ù‡¬’
        o 22.40 šõ¢¯yù¾ü]¸w
        o 22.41 ùØ¾×­uýœ¾Öµ„ðÔ¦¡©‘­v¶…ï®æ{Ý­
        o 22.42 §–@÷ˆ©’©wüsñæ
        o 22.43 ü]¸w¯ú§í­u÷ˆ©’ðš·xÏÏÏá­vñqŽíî÷
        o 22.44 ¸w÷q DB2 for VM ðš·xùàú«
        o 22.45 ¸w÷q DB2 for VM ¸× DB2 for VSE ¾¬Ñ¦¡©‘
        o 22.46 ñã¾×Ýü¸wªý÷û¦§Ç¥õOÝrÏ„ï¸
        o 22.47 Data Joiner ¨—¯~®¾XüsæýøíÇD
        o 22.48 ÷ˆ©’ðš·xÏÏÏáü]¸w¸MøäÝ‘õê¬g
        o 22.49 §ÇÇ›ñ’÷¥îæüZ
        o 22.50 Ýsù£ùàú«¸M¾¬Ñ·
        o 22.51 Ï„ï¸¦§®D IBM ÷ˆ©’©wùàú«¦§ús¬Wù’ôæ
        o 22.52 Ýb÷ˆ©’ðš·xÏÏÏáÏÏÏƒøÒ®¾á÷ˆ©’ùàú«
        o 22.53 ùØ¾× Common Warehouse Metadata Interchange (CWMI) ôžÏJÏ×ôž
          ¾Xïyðz÷ˆ©’
             + 22.53.1 ¶ýÏô
             + 22.53.2 ôžÏJïyðz÷ˆ©’
             + 22.53.3 ÝbøäÝ‘ôžÏJÏ«¾×æ{Ý­Ïõ® õ¢úsïyðz÷ˆ©’
             + 22.53.4 ôž¾Xïyðz÷ˆ©’
        o 22.54 OS/390 Runstats Ï«¾×æ{Ý­ùB’J
        o 22.55 OS/390 ÷ÏJÏ«¾×æ{Ý­ùB’J
        o 22.56 Common Warehouse Metamodel (CWM) XML Ï„ï¸
        o 22.57 üBýz¬ã®ªýœ¾Öóû
        o 22.58 §ä¾¬ã®ªýœ¾Öóû
        o 22.59 ¾ýðn¨‚ÏJŽ‘Ý
        o 22.60 ­u÷ˆ©’ðš·xÏÏÏá­væo©g¾x¾[ñj¾\î…
        o 22.61 ÝCÝLùB’J÷ˆøTù·©ž

   * Data Warehouse Center Application Integration Guide(æLÏÏÏ†¦¸)
        o 23.1 Additional metadata templates
             + 23.1.1 Commit.tag
                  + 23.1.1.1 Tokens
                  + 23.1.1.2 Examples of values
             + 23.1.2 ForeignKey.tag
                  + 23.1.2.1 Tokens
                  + 23.1.2.2 Examples of values
             + 23.1.3 ForeignKeyAdditional.tag
                  + 23.1.3.1 Tokens
                  + 23.1.3.2 Examples of values
             + 23.1.4 PrimaryKey.tag
                  + 23.1.4.1 Tokens
                  + 23.1.4.2 Examples of values
             + 23.1.5 PrimaryKeyAdditional.tag
                  + 23.1.5.1 Tokens
                  + 23.1.5.2 Examples of values

   * ÷ˆ©’ðš·xÏÏÏá«uÏW¯­¸£
        o 24.1 ¸w÷qõê¬g¦§¦¡©‘¸×úõýÏ¦¡
        o 24.2 øäÝ‘ùÆÝü AS/400 ¾Nýzæ{Ý­¦§ Essbase VWPs
        o 24.3 ùØ¾×Ï«õG÷ˆ©’ðš·xÏÏÏáïyðz÷ˆ©’æ›æ­Ï×ÏwæýÝX¦§Ï§©eæ›æ­
        o 24.4 ¾~ùàµ„
        o 24.5 õê¬gæõøO¾¯
        o 24.6 ôžÏJ¬Ñ¾š¯yù¾
        o 24.7 ús¬W÷ˆ©’¦§Çæý
        o 24.8 ôžÏJ¦¡©‘
        o 24.9 RUNSTATS ¸M REORGANIZE TABLE «uÏW¯­¸£ôøÝX
        o 24.10 ­uüq¦ó­vðôðñ­A­uðš·xÏ§©e­v¯P­uñ’æ{­væõøO¾¯
        o 24.11 ­u¾Nýzæ{Ý­§í­væõøO¾¯¦§¾Nýzæ{Ý­¬ãýåŽ‘Ý

   * DB2 OLAP Starter Kit
        o 25.1 OLAP Server §“î÷
        o 25.2 Ï„ï¸¦§õ@ú~ùtý×¦AøÔæ{Ý­æ¾î
        o 25.3 õûÝù DB2 OLAP Starter Kit Ýb UNIX ÏW¦§Ýw÷Ó
        o 25.4 ª[§c OLAP Starter Kit ¦§ ODBC
             + 25.4.1 Ýb UNIX ùtý×ª[§c÷ˆ©’ùàú«
                  + 25.4.1.1 ª[§c ODBC ·“ûãš¬’
                  + 25.4.1.2 «s¨Š odbc.ini ·©ž
                  + 25.4.1.3 ús¬W÷ˆ©’ùàú«ù odbc.ini ·
                  + 25.4.1.4 ODBC ¦§ DB2 ü]¸wðÔ«dùã
                  + 25.4.1.5 ODBC ¦§ Oracle ü]¸wðÔ«dùã
             + 25.4.2 Ýb UNIX ùtý×ÏWª[§c OLAP ïyðz÷ˆ©’®ª¨ì
             + 25.4.3 Ýb Windows ùtý×ÏWª[§c÷ˆ©’ùàú«
             + 25.4.4 Ýb Windows ùtý×ÏWª[§c OLAP ïyðz÷ˆ©’®ª¨ì
             + 25.4.5 Ýbñzª[§c÷ˆ©’ùàú«Ïõ® 
        o 25.5 ñq OLAP Starter Kit ©…ÏW§èýzæ{Ý­ænÏJ
             + 25.5.1 Starter Kit ænÏJ«dùã
        o 25.6 ÝêÝ‘®¾á¸Mª[§c OLAP Starter Kit ¦§«dùã÷ˆ©’©w
        o 25.7 ýó¶…·ü¾×æ{Ý­Ýš OLAP Starter Kit ¦¸¾¯ 7.2
        o 25.8 Ïw¦óøíÇD¯PððùŒ
        o 25.9 OLAP ÷å§ƒ¦¡¬Wîqôø EQD ·©ž¨•¾½

   * ÷ˆøT®ª¨ì§èýzæ{Ý­§èýzÏƒ¾U
        o 26.1 ÷ˆøT®ª¨ì§èýzæ{Ý­ø_¸lü]¸wÏ«¾×æ{Ý­
             + 26.1.1
             + 26.1.2 ¦¸vøíÇD
             + 26.1.3 Ýw÷ÓøíÇD
        o 26.2 ¾H DB2 ¦¸¾¯ 7 ÷ˆøT®ª¨ì§èýzæ{Ý­Ýsù£ DB2 ¦¸¾¯ 5 ÷ˆøT®ª¨ì
        o 26.3 ü]÷m÷ˆøT®ª¨ì
        o 26.4 ¯Pù„¾Ýýœ®~¾‘ï®ïyðz÷ˆ©’
        o 26.5 ùØ¾× flgnxoln ®¾O¾‘ï®ïyðz÷ˆ©’
        o 26.6 ùØ¾× MDISDGC ®¾O¾‘ï®ïyðz÷ˆ©’
        o 26.7 ¸I¾sæ{Ý­

   * Information Catalog Manager Programming Guide and Reference(æLÏÏÏ†¦¸)
        o 27.1 Information Catalog Manager Reason Codes

   * ÷ˆøT®ª¨ì§èýzæ{Ý­ùØ¾×Ïƒ¾U

   * ÷ˆøT®ª¨ì§èýzæ{Ý­­G«uÏWøT©õ
        o 29.1 øT©õ FLG0260E
        o 29.2 øT©õ FLG0051E
        o 29.3 øT©õ FLG0003E
        o 29.4 øT©õ FLG0372E
        o 29.5 øT©õ FLG0615E

   * ÷ˆøT®ª¨ì§èýzæ{Ý­­G«uÏW¯­¸£
        o 30.1 Web ÷ˆøT®ª¨ì§èýzæ{Ý­

   * DB2 Warehouse Manager Ýw÷ÓÏƒ¾U
        o 31.1 ðš·x¶…ï®æ{Ý­¦§ün‚¯íùD
        o 31.2 SAP R/3 Connector
             + 31.2.1 Ýw÷Ó¾ìùMñ›¾¢
        o 31.3 Web Connector
             + 31.3.1 Ýw÷Ó¾ìùMñ›¾¢

   * Query Patroller Administration Guide(æLÏÏÏ†¦¸)
        o 32.1 DB2 Query Patroller Client is a Separate Component
        o 32.2 Migrating from Version 6 of DB2 Query Patroller Using
          dqpmigrate
        o 32.3 Enabling Query Management
        o 32.4 Location of Table Space for Control Tables
        o 32.5 New Parameters for dqpstart Command
        o 32.6 New Parameter for iwm_cmd Command
        o 32.7 New Registry Variable: DQP_RECOVERY_INTERVAL
        o 32.8 Starting Query Administrator
        o 32.9 User Administration
        o 32.10 Creating a Job Queue
        o 32.11 Using the Command Line Interface
        o 32.12 Query Enabler Notes
        o 32.13 DB2 Query Patroller Tracker may Return a Blank Column Page
        o 32.14 Query Patroller and Replication Tools
        o 32.15 Appendix B. Troubleshooting DB2 Query Patroller Clients

  ------------------------------------------------------------------------

Business Intelligence ñÑó€®ó

  ------------------------------------------------------------------------

21.1 ÷gûLðžðq¦§ Business Intelligence ñÑó€®ó

FixPak 2 ¾]ªAÏFðžðqûL¦§ Business Intelligence ñÑó€®óÏ×÷ˆ©’ðš·xÏÏÏá«dùã÷ˆ
©’©w (õ¢¾¨ÏFü\Ýh¦¸¾¯ 7.1 ÏÏ¸ãÝsÝb¦§øíÇD)­CªøÏFÏè¾×ðžðqûL¦§÷ˆ©’ðš·xÏÏÏá«dùã
÷ˆ©’©w­A «ÑøäÝ‘ÏUÝCù’ôæ­G

Ýp¦Gñz¸|¾¬Ýw÷Ó«dùã÷ˆ©’©w­A«ÑùØ¾×­uýŽÏ@ðàùB’J­væo©g¾xùà®¾áús¦§«dùã÷ˆ©’©w­C
®”Ï@ÏU ô}¸l­A ¨‹ù£ æ{Ý­ôø --> IBM DB2 --> ýŽÏ@ðàùB’J­C

Ýp¦GñzÝb¾ì®eÏwÝw÷ÓÏF«dùã÷ˆ©’©w­A«ÑñN«dùã÷ˆ©’©w DWCTBC­BTBC_MD Ï× TBC ñÓñ¢­C
Ýp¦Gñzû‹«dùã÷ˆ©’©wús¬WÏF¾“Ý¢ðn®OÝs¦§÷ˆ©’­A«ÑÝbñÓñ¢÷ˆ©’©wÏõ®eñN÷ˆ©’ü’¾ö­CðY
ðnñÓñ¢üoÏTðà«dùã÷ˆ©’©w­G

  1. ô}ñã DB2 ¸R¾Oæ›æ­­A®”Ï@ÏUô}¸l­A ÝA¨‹ù£ æ{Ý­ôø --> IBM DB2 --> ¸R¾Oæ›æ­
     ­C
  2. Ýb DB2 ¸R¾Oæ›æ­ÏÏ­Aµ„ÏJÏUÝCÏTÝ‘¸R¾O (µ„ÏJùCÏ@Ý‘® ®” Enter)­G

     db2 drop database dwctbc

     db2 drop database tbc_md

     db2 drop database tbc

  3. Ç”üª DB2 ¸R¾Oæ›æ­­C
  4. ùØ¾×­uýŽÏ@ðàùB’J­væo©g¾xùà®¾áús¦§«dùã÷ˆ©’©w­C®”Ï@ÏU ô}¸l­A ¨‹ù£ æ{Ý­
     ôø --> IBM DB2 --> ýŽÏ@ðàùB’J­C

  ------------------------------------------------------------------------

÷ˆ©’ðš·xÏÏÏá§èýzÏƒ¾U

  ------------------------------------------------------------------------

22.1 §ÇÇ›ñ’÷¥

÷ˆ©’ðš·xÏÏÏá§ÇÇ›ñ’÷¥÷ˆøTýóÝš DB2 Troubleshooting Guide­C
  ------------------------------------------------------------------------

22.2 ü]÷m Excel ªøðš·xùàú«

Ýb­uýŽ 3 üû ü]¸wðš·xùàú«­v¦§­uÝb Windows NT ÏWü]÷m®D DB2 ÷ˆ©’©wðš·xùàú« ­v
ÏÏ­AÝüÇ” Microsoft Excel ¦§ªq÷ùîÒÏ™Ï@ðàùB’J­Cús¦§ùB’JÆ¾šÝb¾HÏU¦§ùB’J 3 Ïõ
ÏÏ­C

Ýp¦Gñz¾¨ÝbùØ¾× Microsoft Excel 95/97 ODBC XøÒæ{Ý­Ýsù£ Excel ÷å§ƒ¦¡­Añz¾ýôú
ªø÷å§ƒ¦¡ÏÏ¦§ùCðàÏuõ@¦¡®¾áÏ@ðàÏw¸RÝW¦§¦¡©‘­CðYðnªøùCÏ@ðàÏuõ@¦¡®¾áÏw¸RÝW¦§
¦¡©‘­G

  1. ¨‹ù£ñzðn¦§¦«Ž‘¸MóŒÝC­C
  2. ®”Ï@ÏU Excel ---> ï­ÏJ ---> ÝW§ë ---> ¸w÷q­C
  3. «Ñ«T¯{­u¸w÷qÝW§ë­væ›æ­¦§­uø¥úà­vŽ‘Ý¾]õtÏFñzÝbùB’J 1 ÏÏ¸ã¨‹ù£¦§÷ˆ©’
     ©‘­C Ýp¦GùSÝü­A«Ñ®”Ï@ÏU­uø¥úà­vŽ‘ÝüÞ¾kÇ„¦§ûØ¾š­Aùà¾]õt¸ãÝüñzÏw¨‹ù£¦§
     ÷ˆ©’©‘­C
  4. ªøÏw¬ÑøO¦§÷ˆ©’¨‚ÏJÝW§ë (¸×ùØ¾×ûwü]ÝW§ë)­C
  5. ®”Ï@ÏU­u«T¸w­v­C

  ------------------------------------------------------------------------

22.3 ¸w÷qÏ×øäÝ‘æ{õ€

Ýb­uýŽ 5 üû ¸w÷qÏ×øäÝ‘æ{õ€­v¦§­uñq÷ˆ©’ðš·xÏÏÏá¾~ñãøÒùB’J­vÏÏ­A «Ñ¦`úNùÝbðš
·xÝ›¦AóûÏuõ@î÷Ï×¾Nýzæ{Ý­§íÏW¯íðn JDK 1.1.8 ¸×õ¢ús¦§¦¸¾¯­A Ýp¦GñzñãøÒ¦§ùB’J
Ýü¶—ÝÏ÷ýå¦§ÝW§ë­C
  ------------------------------------------------------------------------

22.4 ôž¾Xïyðz÷ˆ©’û‹÷š

ÝbýŽ 12 üû­uôž¾XÏ×ôžÏJ÷ˆ©’ðš·xÏÏÏáïyðz÷ˆ©’­v¦§­uñNïyðz÷ˆ©’ôž¾XÝš¬Ñ¾š¯yù¾
·­vüoÏ@÷`ÏÏ­AùB’J 5 ·üÝpÏU¸ã¾š­G

Ýp¦GñzÏœúQôž¾X¯Pñz¾¨ôž¾XÏõæ{õ€ªêÇ”¦§©æ{¦¡÷ˆøT­A «ÑýMøœù™ÏJ©æ{¦¡ÏŽ¨‹©­C
  ------------------------------------------------------------------------

22.5 ªø Submit OS/390 JCL Ïuõ@Ýˆªyæ{Ý­ (VWPMVS) ¸w÷qðÔ

Ýb 180 ðô­A­u¸w÷q Submit OS/390 JCL Ïuõ@Ýˆªyæ{Ý­­v(VWPMVS) üû÷`Ï§ùB’J 8­A
¯­¸£Ýb JES ·©žÝPÏ@ðà¾¨ìÏU¸w÷q .netrc ·©ž­C÷àæ{Ý­®o®¾áÏF .netrc ·©ž­C
Ýp¦Güoðà·©žÏœÝsÝb­A÷àæ{Ý­ú|Ýbø_¸l¾¨ìÏU®¾á¾Ý­C Ýp¦G .netrc ·©žÏw÷gÝsÝb­A
®h÷àæ{Ý­ú|õ¢õ‹ý{Ýs·¦§·ÝWùÇ®¾áús·©ž­Cæ{Ý­õûÝùüBýzæ{õ€©­Aús®¾á¦§ .netrc
·©žú|üQõRøœ­AÝAõƒðùà¦§·©ž¦§·ÝWõ¢õ‹ªø .netrc­C
  ------------------------------------------------------------------------

22.6 šõ¢÷ˆ©’ðš·x«dùã¦ç¨ì

   * Ýb÷ˆ©’ðš·x«dùã¦ç¨ìÏ§­A­u·Óæ›¸Mðžõ‹«dùãïyðz÷ˆ©’­vÏ@÷`ÏÏ­Aùàú«¦¡©‘¦§ÝC¾š
     Ï§õt GEOGRAPHIES¦¡©‘­C
   * Ýb÷ˆ©’ðš·x«dùã¦ç¨ì¦§­uïœ¦@ùB’J­vÏ@÷`ÏÏ­Aïœ¦@ýœ®~¬ãÝ­æ{õ€Ï§­AÏUÝCüîðzÝ­
     ªOÏœ¾¨«T¦§­AÝ]ªø¾¬Ñ¦¡©‘ªOÝbñzïœ¦@ï£÷å¬ãÝ­ùB’J©¸ã®¾á­G

     ÷ˆ©’ðš·xÏÏÏáô}¸l®¾á¾¬Ñ¦¡©‘­AùÇÆ¾šôi®žæ›æ­­C

  ------------------------------------------------------------------------

22.7 ÷ˆ©’ðš·xÏÏÏáøT©õ

Ýb Microsoft Windows NT Ï× Windows 2000 ÏW­A­u÷ˆ©’ðš·xÏÏÏá­vú|ñNù’¾¢øO÷Ýb
ùtý×¦§ù’¾¢Ï‚¯xÏÏ­Cù„ù’¾¢ ID ú|û‹·üù­u÷ˆ©’ðš·xÏÏÏá­v¦§øT©õ«XÏW­CÝüÇ”­u÷ˆ©’
ðš·xÏÏÏá­vøT©õ¦§÷ˆøT­A«Ñø¥ó\ øT©õø¥ÝãÏƒ¾U­C
  ------------------------------------------------------------------------

22.8 Ýb DB2 OLAP Integration Server ÏÏ®¾á©ª[ùÇ÷ÏJ÷ˆ©’

ýŽ 315 ðô¦§ûØ 20 Ýü¯~­CÏUÝC®¾OÏ~ªO¾¨«T­G

"C:\IS\bin\olapicmd" < "C:\IS\Batch\my_script.script" >
"C:\IS\Batch\my_script.log"

ðY÷“©|ÏÏ¦§¾¨ìÝW§ëÏÏõtÝü¦¾å (Ýp­GProgram Files)­Añz¾ýôúùØ¾×¶—Ïè÷ûªAÝ¡
"C:\IS\bin\olapicmd"­C
  ------------------------------------------------------------------------

22.9 ñN Classic Connect ¯P÷ˆ©’ðš·xÏÏÏáúføtùØ¾×

   * Ýb­u¦ç¨ì F ñN Classic Connect ¯P÷ˆ©’ðš·xÏÏÏáúføtùØ¾×­vÏÏ­A ýŽ 359 ðô¦§
     ­uÝw÷Ó CROSS ACCESS ODBC XøÒæ{Ý­­vüû÷`¦§Ï§©eÏwõ‹ªøÏUÝCñâðz­G

        øäÝ‘ DB2 Warehouse Manager ¦¸¾¯ 7 ¦§ÝêðqÝw÷Ó­A¾HÝw÷Ó CROSS ACCESS ODBC
        XøÒæ{Ý­­AùÇ¨‹ù£­uClassic Connect XøÒæ{Ý­­vÏ÷¾¢­CÝûXøÒæ{Ý­ÏœŽí¸¢ DB2
        Warehouse Manager ¬Ñú€Ýw÷Ó¦§Ï@ü­¾ö­C
        CROSS ACCESS ODBC XøÒæ{Ý­ú|üQÝw÷Óù SQLLIB ¾¨ì¦§ ODBC32 Ïl¾¨ìÏÏ­C
        ÝbÝw÷ÓõûÝù® ­Añz¾ýôúÝêÝ‘ñNXøÒæ{Ý­¦§÷“©| (ùãÝp­AC:\Program Files\SQLLIB\
        ODBC32)¾[ù PATH ùtý×·“ûãš¬’­CÝp¦GñzÏwÝw÷Óù„¾Ý¦¸¾¯¦§ CROSS ACCESS ODBC
        XøÒæ{Ý­­Aõƒ ...\SQLLIB\ODBC32\ ÷“©|¸¤ùù„¾Ý¦¸¾¯÷“©|¦§®eðñ­Cõ@ú~ùtý×ú|ùØ
        ¾×¾]ªA CROSS ACCESS ODBC XøÒæ{Ý­¦§÷“©|ÏÏ¦§ýŽÏ@ðà¾¨ì­C

   * ÏUÝCæ{õ€·ü÷àðn¾[ù ­u¦ç¨ì F ñN Classic Connect ¯P÷ˆ©’ðš·xÏÏÏáúføtùØ
     ¾×­vÏÏ­G

     Ýw÷Ó Classic Connect ODBC XøÒæ{Ý­­G
       1. ï­ÏJ Warehouse Manager CD-ROM ù¾£§ÑóöÏÏ­C æo©g¾xïNú|ô}ñã­C
       2. ®”Ï@ÏUæo©g¾x¦§Ýw÷Ó­C
       3. Ýb­u¨‹ù£ýœ®~­væ›æ­ÏÏ­A«Ñ«T¸w¨‹ù£ÏF DB2 Warehouse Manager ÏŽ¨‹©­A
          æM® ®”Ï@ÏUÏUÏ@ùB­C
       4. Ýb­u¨‹ù£Ýw÷ÓÇç®ª­væ›æ­ÏÏ­A«Ñ¨‹ù£ÝêðqÝw÷Ó­A æM® ®”Ï@ÏUÏUÏ@ùB­C
       5. Ýb­u¨‹ù£Ï÷¾¢­væ›æ­ÏÏ­A¨‹ù£ Classic Connect XøÒæ{Ý­Ï× ðš·x¾Nýzæ{
          Ý­­AýMøœ¸ãÝüù„¾Ý¦§ÏŽ¨‹©­AæM® ®”Ï@ÏUÏUÏ@ùB­C
       6. Ýb­uô}¸l«’¯s·©ž­væ›æ­­A«’ªdñz¦§¨‹óš­CÝp¦Gñzðnšõ¢¾“Ý¢¨‹ôæ­A «Ñ®”
          ÏWÏ@ùBÝ^ùðnšõ¢¨‹ôæ¦§æ›æ­­C®”Ï@ÏUÏUÏ@ùB­Aô}¸lÝw÷Ó­C

  ------------------------------------------------------------------------

22.10 ÷ˆ©’ðš·xÏÏÏá·“ûãæý§c

ÝbýŽ 371 ðô¦§­u¦ç¨ì G ÷ˆ©’ðš·xÏÏÏá·“ûãæý§c­vÏÏ­A ¦¡©‘ÏÏÝüÏ@ðàÏœ¾¨«T¦§ôæ¾­C
C:\Program Files\SQLLIB\ODBC32ùÇùSÝü¾[ù PATH ·“ûãš¬’­C PATH ·“ûãš¬’¸ãøæ
¦§øáÏ@õ¢úsªø C:\Program Files\SQLLIB\BIN­C
  ------------------------------------------------------------------------

22.11 ùØ¾× Invert ¶…ï®æ{Ý­

©¥ÏÏïœù Invert ¶…ï®æ{Ý­¾i¾H©éóéø¥¬’ùà®¾á¾¬Ñ¦¡©‘­A ÝìªO¾ÝùSÝüïœùýœ¾Ö¦§¾
¬Ñ¦¡©‘Ïœú|Ýüïµñ‘¦§¨‚¾X¦«Ž‘­A¾ýôúÝb¾¬Ñ¦¡©‘ÏÏ¸£¾å¦§®¾áüoù€¦«Ž‘­C
  ------------------------------------------------------------------------

22.12 ¾H DB2 ¦¸¾¯ 7 ðš·x¾Nýzæ{Ý­Ýsù£ DB2 ¦¸¾¯ 5 ÷ˆ©’

DB2 ¦¸¾¯ 7 ðš·x¾Nýzæ{Ý­¾¥ DB2 ¦¸¾¯ 7 Ýw÷Óæ{õ€ª[§c­A Ï„ï¸û‹ DB2 ¦¸¾¯ 6 ¸M
DB2 ¦¸¾¯ 7 ÷ˆ©’¦§Ýsù£­CñìÝsù£ DB2 ¦¸¾¯ 5 ¦§÷ˆ©’­Añz¾ýôúñŽù£ÏUÝCù„ÏÏÏ@ôæÏŠ
¦k­G

   * ýó¶… DB2 ¦¸¾¯ 5 Ý›¦Aóû Ýš DB2 ¦¸¾¯ 6 ¸× DB2 ¦¸¾¯ 7­C
   * ¸¢óAú¡¦§õ@ú~ùtý×ÏÏðžõ‹¾Nýzæ{Ý­ª[§c­A¾i¾HÝsù£ DB2 ¦¸¾¯ 5 ¦§÷ˆ©’­C

DB2 ¦¸¾¯ 7 ðš·x¾Nýzæ{Ý­ÏœÏ„ï¸ DB2 ¦¸¾¯ 2 ¸×Ïõ®e¦¸¾¯÷ˆ©’¦§Ýsù£­C

22.12.1 ýó¶… DB2 ¦¸¾¯ 5 Ý›¦Aóû

ÝüÇ”ýó¶…ýó DB2 ¦¸¾¯ 5 Ý›¦Aóû¦§÷ˆøT­A«Ñø¥ó\õ@ú~ùtý×¦§ DB2 Universal Database
õ™ütÏJ¦—­C

22.12.2 šõ¢¾Nýzæ{Ý­ª[§c

ÏUÝC÷ˆøT¯­¸£ÝpÝ¢šõ¢ÝUõ@ú~ùtý×Ïõ¾Nýzæ{Ý­ª[§c­C ýó¶… DB2 Ý›¦AóûÝš DB2 ¦¸¾¯ 6
¸×õ¢ús¦¸©­Aøœ¾hª[§c¦§šõ¢­C

22.12.2.1 UNIX ðš·x¾Nýzæ{Ý­

ü]¸w UNIX ðš·x¾Nýzæ{Ý­­ACLI ¸× ODBC Ýsù£®¾Oû‹ DB2 ¦¸¾¯ 5 Ïõ÷ˆ©’¦§Ýsù£­G

  1. Ýw÷Ó DB2 ¦¸¾¯ 6 øäÝ‘©ô­ñqŽíî÷­CÝêÏUÝC URL ¨‹ù£ñqŽíî÷ÏU÷­A¾i¾Hñoùøä
     Ý‘©ô­ñqŽíî÷­G

     http://www.ibm.com/software/data/db2/udb/support

  2. õ¢úsðš·x¾Nýzæ{Ý­ª[§c·­ADB2INSTANCE ·“ûãš¬’®ÝV DB2 ¦¸¾¯ 6 ©žùã­C
  3. «s¾ DB2 ¦¸¾¯©žùã¦§¸ãÝü÷ˆ©’©w­AÝsù£ðš·x¾Nýzæ{Ý­­C
  4. æo¾X¾Nýzñ`ónæ{Ý­æ{õ€ ID ¦§õRøœ®¾O­AøñÏŒ¾Nýzñ`ónæ{Ý­æ{õ€­C¾Nýzñ`ónæ{Ý­
     ñNÝêøÒð®úsñãøÒ­CõRøœæ{õ€¯íðnÝü root vðð­C

22.12.2.2 Microsoft Windows NT­BWindows 2000 ¸M OS/2 ðš·x¾Nýzæ{Ý­

ü]¸w Microsoft NT­BWindows 2000 ¸× OS/2 ðš·x¾Nýzæ{Ý­­AÝsù£ DB2 ¦¸¾¯ 5 ¦§÷ˆ
©’­C

  1. ÝbùSÝüÝw÷Ó DB2 ¦¸¾¯ 7.2 ðš·x¾Nýzæ{Ý­¦§Ïuõ@î÷­AÝw÷Ó DB2 Connect
     Enterprise Edition ¦¸¾¯ 6­C

     DB2 Connect Enterprise Edition ªO DB2 Universal Database Enterprise
     Edition ¸M DB2 Universal Database Enterprise - Extended Edition ¦§Ï@ü­
     Ï·­CÝp¦GÝw÷Óüoù€ DB2 ýœ®~¦§¦¸¾¯ 6­AæLôú¾t¾~Ýw÷Ó DB2 Connect­C
     ððùŒ:
          ÝbªêÝP¦§ Windows NT ¸× OS/2 Ïuõ@î÷­AÏœî…Ýw÷Ó DB2 Ýhð®¦¸¾¯­C ñz¾i
          ¾HÝbù„¾Ý Windows NT Ïuõ@î÷­B OS/2 Ïuõ@î÷¸× UNIX Ïuõ@î÷ÏWÝw÷Ó DB2
          Connect­C
  2. ª[§cðš·x¾Nýzæ{Ý­¸M DB2 Connect ¦¸¾¯ 6­AÝsù£ DB2 ¦¸¾¯ 5 ¦§÷ˆ©’­C÷âýà÷ˆ
     øT­A«Ñø¥ó\ DB2 Connect ùØ¾×Ïƒ¾U­C¾HÏUªø¾ýðnùB’J¦§úõ’[­G
       a. Ýb DB2 ¦¸¾¯ 5 ùtý×­AùØ¾× DB2 ¸R¾OÝ‘üBýzóû«s¾¦¸¾¯ 5 ¦§÷ˆ©’©w­AÝs
          ù£ðš·x¾Nýzæ{Ý­­C
       b. Ýb DB2 Connect ùtý×­AùØ¾× DB2 ¸R¾OÝ‘üBýzóûôiÝ‘«s¾­G
             + DB2 ¦¸¾¯ 5 ùtý×¦§ TCP/IP ÷`¶I
             + DB2 ¦¸¾¯ 5 ùtý×¦§÷ˆ©’©w
             + DB2 ¦¸¾¯ 5 ùtý×¦§ DCS æn¨ìôæ¾
       c. ¸¢ðš·x¾Nýzæ{Ý­Ïuõ@î÷­AùØ¾× DB2 ¸R¾OÝ‘üBýzóûôiÝ‘«s¾­G
             + DB2 Connect ùtý×¦§ TCP/IP ÷`¶I
             + DB2 Connect ùtý×¦§÷ˆ©’©w

     ÝüÇ”«s¾÷ˆ©’©w¦§÷ˆøT­A«Ñø¥ó\ DB2 Universal Database Ýw÷Ó¯Pª[§c÷¾R
  3. ¸¢ðš·x¾Nýzæ{Ý­Ïuõ@î÷­AñN DB2 CLI ©M÷Óün‚¸MüzûL DB2 Connect ¸ãÝsù£¦§ÝU
     ðà÷ˆ©’©wôiÝ‘üsæý­C

     ÏUÝC DB2 ®¾Oïœù¥üsæýù v5database ¦§«dùã­A Ï@ðàøýü]¸Ò¦§ DB2 ¦¸¾¯ 5 ¦§
     ÷ˆ©’©w­C ùØ¾× DB2 ¸R¾OÝ‘üBýzóûæo¾XÏUÝC®¾O­Cdb2cli.lst Ï× db2ajgrt ¦§
     Ý÷mÝb \sqllib\bnd ¾¨ìÏÏ­C

     db2 connect to v5database user userid using password
     db2 bind db2ajgrt.bnd
     db2 bind @db2cli.lst blocking all grant public

     ù„ÏÏ userid ªO v5database ¦§ùØ¾×¦Þ ID­A Ýà password ªOùØ¾×¦Þ ID ¦§üqÝ‘
     «X­C

     db2cli.list üQüsæýù DB2 ¦¸¾¯ 5 ÷ˆ©’©w©­Aú|æo¾Ö¨—¯~­Cæo¾Ö¨—¯~­AªOÝ]ªø
     Ýûª[§cùÇÏœÏ„ï¸Ïj®ª¦®¾¢­Cüoôæ¨—¯~Ïœú|¬vTðš·x¾Nýzæ{Ý­û‹ DB2 ¦¸¾¯ 5 ÷ˆ©’
     ©w¦§Ýsù£­C

     ¯íðnÝü DB2 Universal Database ¦¸¾¯ 5 ¦§ FixPak 14 (¸¢ 2000 Ý~ 6 Ï‰æo
     Ý‘)­A Ï~î…üzûL DB2 Connect ùàÝsù£ DB2 ¦¸¾¯ 5 ¦§÷ˆ©’­C«Ñø¥úà FixPak Ï§
     ¦§ APAR «s÷û JR14507­C

  ------------------------------------------------------------------------

22.13 IBM ERwin ïyðz÷ˆ©’ù£¾Xæ{Ý­

22.13.1 Ï§©e

ün‚¯íùD

æ{Ý­·

®¾á¬Ñ¾š¯yù¾·

ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆ©’ðš·xÏÏÏá­v

ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆøT®ª¨ì§èýzæ{Ý­­v

§ÇÇ›ñ’÷¥

ERwin ù­u÷ˆ©’ðš·xÏÏÏá­vû‹ªM

ERwin ù­u÷ˆøT®ª¨ì§èýzæ{Ý­­vû‹ªM

¾¯÷`¯­¸£ÝpÝ¢ùØ¾× IBM ERwin Metadata Extract Program ùàñq ER1 ·ù£¾Xïyðz÷ˆ
©’­A¾HÏ×®¾á­uDB2 ÷ˆ©’ðš·xÏÏÏá­v¸×­u÷ˆøT®ª¨ì§èýzæ{Ý­ (DataGuide)­v¬Ñ¾š¯yù¾
·­C

ïyðz÷ˆ©’ù£¾Xæ{Ý­ú|ù£¾X¸ãÝüûˆ‚¦®¾¢ (Ýp·xÝs¸¢¨‚ÏJ ER1 ·ÏÏ¦§÷ˆ©’©w­B¦¡©‘Ï×¦«
Ž‘)­A ùÇ¾BñNïyðz÷ˆ©’¬ã®ª¬gÏJ­u÷ˆ©’ðš·xÏÏÏá­v¸×­u÷ˆøT®ª¨ì§èýzæ{Ý­­v¬Ñ¾š¯yù¾
·ÏÏ­C®¾á¦®¾¢Ïõô­ (Ýp÷ˆ©’©w¸M¦¡©‘Ïõô­­A¾HÏ×¦¡©‘¸Mûˆ‚Ïõô­) ¦§¸ãÝüû‹·üÇ”®Y
¬Ñã©­AÏ]ú|¶^ù£Ï×®¾á¾¥ûˆ‚Ï×Ží¸ÒýåÝù¦§­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏõè¨Š¬ã®ª­Cû‹
Ïœõt÷ˆ©’©w¦§¦¡©‘Ýàù¾­Aú|®¾áÏ@ðàÝWªø DATABASE ¦§ûwü]÷ˆ©’©w­Cû‹Ïœõt§ä¾¦§¦¡
©‘Ýàù¾­Aú|ùØ¾×ûwü]§ä¾ USERID­Cû‹¬ã®ªÝW§ëÝàù¾­Aú|ùØ¾× ER1 ·ÝW­CÝüÇ” ER1 Ží
¸Òû‹ªMÝš­u÷ˆ©’ðš·xÏÏÏá­v¸×­u÷ˆøT®ª¨ì§èýzæ{Ý­­v¦§÷âýà÷ˆøT­A«Ñø¥ó\­uERwin ¯P
DB2 ÷ˆ©’ðš·xÏÏÏá¦§û‹ªM­v¸M­uERwin ¯P÷ˆøT®ª¨ì§èýzæ{Ý­¦§û‹ªM­v­C

ïyðz÷ˆ©’ù£¾Xæ{Ý­Ï„ï¸ùÆÝüÇ”µpÝ­÷ˆ©’©w¦§¸ãÝü ER1 ¬ã®ª­A ¾]ªA DB2­BInformix­B
Oracle­BSybase­BODBC ÷ˆ©’ùàú«Ï× Microsoft SQL Server­C

22.13.2 ün‚¯íùD

ùtý×¯íýÝXÏUÝC¦§ün‚¯íùD¾HøäÝ‘ïyðz÷ˆ©’ù£¾Xæ{Ý­­G

   * Windows NT 4.0 ¸×¾HÏW
   * ERwin 3.5.2 (÷ÓÝü Service Pack 3 Build 466)

ùtý×¯íýÝXÏUÝC¦§ün‚¯íùD¾HôžÏJ ERwin ¬Ñ¾š¯yù¾·­G

÷ˆ©’ðš·xÏÏÏá­G
     IBM DB2 Universal Database ¦¸¾¯ 7.2

÷ˆøT®ª¨ì§èýzæ{Ý­­G
     IBM DB2 Warehouse Manager ¦¸¾¯ 7.2

¬ã¦O¬Ñ¾š¯yù¾· (.tag) ¾ýôúÝ¸¢ VWS_TEMPLATES ·“ûãš¬’¸ã®¾š¦§¾¨ìÏÏ­C

Çç®ª¬Ñ¾š¯yù¾· (.typ) ¾ýôúÝ¸¢ DGWPATH ·“ûãš¬’¸ã®¾š¦§¾¨ìÏÏ­C

22.13.3 æ{Ý­·

ïyðz÷ˆ©’ù£¾Xæ{Ý­Ýw÷ÓÝb IBM DB2 ¾¨ì¦§ sqllib\bin Ý÷¾¨ìÏÏ­C Ýûæ{Ý­ñNÏUÝC·
©žÝw÷Óùñz¦§¾¨ìÏÏ­G

flgerwin.exe
     ¾Dðn¦§ýó¶…æ{Ý­

erwext.dll
     ¬Ñ¾š¯yù¾·ýœ¾Öóû DLL

cdmerwsn.dll
     ERwin API ¾~¬hÇçõO DLL

ðYðnñãøÒù£¾Xæ{Ý­­A«Ññq®¾Oïœ¾šÏWæo¾X flgerwin ®¾O­C

22.13.4 ®¾á¬Ñ¾š¯yù¾·

ðYðn®¾á­u÷ˆ©’ðš·xÏÏÏá­v¸×­u÷ˆøT®ª¨ì§èýzæ{Ý­­v¬Ñ¾š¯yù¾·­A «ÑøäÝ‘
flgerwin.exe æ{Ý­ùÇïœù¥ùƒðà¾Dðnø¥¬’­CýŽÏ@ðàø¥¬’ªøïyðz÷ˆ©’Ýêù„ÏÏù£¾X¦§ ER1
·­CýŽÏGðàø¥¬’ªø¨‚¾X¬Ñ¾š¯yù¾·¦§ÝW§ë­CùÞûwü]­Aù£¾Xæ{Ý­ñN MERGE ø¥¬’¾[ÏJ­u÷ˆ
©’ðš·xÏÏÏá­v¬Ñ¾š¯yù¾·ÏÏ­C

®¾O¯y¦kªø­G

        flgerwin inputFile.er1 outputFile.tag [-dwc] [-icm] [ -m] [-u] [-a] [-d]

®¾áªP¦ª§ä¾¦§®¾O¯y¦kªø­G

        flgerwin inputFile.er1 outputFile.tag [-dwc] [-starschema]

-dwc
     «Ñ®¾á­u÷ˆ©’ðš·xÏÏÏá­v¬Ñ¾š¯yù¾·­Cñz¾iùØ¾× -dwc ¦§¨‹¾×¸Òø¥¬’ -m ¯P
     -starschema­C

-icm
     «Ñ®¾á­u÷ˆøT®ª¨ì§èýzæ{Ý­­v¬Ñ¾š¯yù¾·­C -icm ¾i¾×¦§¨‹¾×¸Òø¥¬’ªø -m­B-u
     ­B-a Ï× -d­C

-starschema
     «Ñ®¾á ERwin ¬ã®ªªP¦ª§ä¾¬Ñ¾š¯yù¾·­C

-m
     ®¸w¦®¾¢ÏW¦§øÒõ@ªø MERGE­C

-u
     ®¸w¦®¾¢ÏW¦§øÒõ@ªø UPDATE­C

-a
     ®¸w¦®¾¢ÏW¦§øÒõ@ªø ADD­C

-d
     ®¸w¦®¾¢ÏW¦§øÒõ@ªø DELETE­C

ïyðz÷ˆ©’ù£¾Xæ{Ý­ùØ¾×¦§ªOïyðz÷ˆ©’Ýà®D÷ˆ©’­CõûÝù ERwin ¬Ñ¾š¯yù¾·ôžÏJ® Ï×ùØ¾×
¾¬Ñ¦¡ ©‘Ïõ®e­Añz¾ýôúýÝXüqÝ‘«XÏ×ùØ¾×¦Þ ID­CñNïyðz÷ˆ©’¯Pý{Ýs¦§÷ˆ©’©w÷ˆ©’ÝX
ù™­G

ÝbÏ§©e --> ÷ˆ©’©w --> ùØ¾×¦Þ ID ÏUšõ¢­u÷ˆ©’ðš·xÏÏÏá­vùØ ¾×¦Þ ID ¸MüqÝ‘«X­A
ùØýÝXÏwÝXù™¦§÷ˆ©’©wùØ¾×¦Þ ID ¸MüqÝ‘«X­C

üzûLïyðz÷ˆ©’ù£¾Xæ{Ý­­Añz¾i¾HôžÏJ¬Ñ¾š¯yù¾·õ@ªø¾¬Ñ­C ÝbüÞúsôžÏJ¦§ïyðz÷ˆ©’
ÏÏ­A¸|¾¬ýóÏJÏ@ù€¦¡©‘­Cñz¾i¾H¾×è¨Š¸×ûˆ‚¦¡¾š¦k·Óæ›üoù€ ¦¡©‘­AæM® ®¾áÏ@ðàðš
·xùB’JùàýóÏJñq ERwin ôžÏJ¦§¦¡©‘¸w÷q­C

¨‚ÏJ ER1 ·©ž¾ýôúüB¸¢¾i¬gÏJ¦ª§A­CøäÝ‘ïyðz÷ˆ©’ù£¾Xæ{Ý­® ­A ER1 ·©žõYšÝùøá
¦¦ª§A­CðYðnšõ¢ªø¦ù£/¬gÏJ¬ãÝ­­A«ÑùØ¾×ÝpÏU¸ã«dùã¸ã¾š¦§®¾O­G

attrib -r erwinsimplemode.er1

ù„ÏÏ­Aerwinsimplemode.er1 ªO ERwin î¶Ï†Ýr·¦§ÝW§ë­C

ðY ER1 ·©žÏwùØ¾×¸¢ý{Ý‘ ERwin ô¾ªqõ@ú~ÏÏ­A¸×ø¯ï£ùªYðà¨—¯~¦ª¦p­A ®hïyðz÷ˆ©’
ù£¾Xæ{Ý­¾Høá¦¦ª§A·xÝs ER1 ·©ž­CðY ER1 ·©žüB¸¢øá¦¦ª§A­A ñzú|ÝªùÏ@ðàýõñ`
æ{Ý­ýžÏŒ¨—¯~øT©õ­Cïyðz÷ˆ©’ù£¾Xæ{Ý­ú|Æ¾š¾®eüBýz¦§¦¡©‘ÝW§ë­C ú¡ïyðz÷ˆ©’ù£¾X
æ{Ý­õûÝùüBýz©­Añzú|ÝªùÏ@®hø¥ÝãøT©õ­C

ú¡ñz¶€¾¥ñN§–®ž¦¡©‘ÝêøÒæýÝXÝùù’ûˆ¦¡©‘ùà®¾áªP¦ª§ä¾©­A ¯íðnÏ@ªq©ô­Ï~î…õûÝù
üBýzæ{õ€­AÝà¸ã¯íðn¦§©ô­æ›ñzùØ¾×¦§¦¡©‘¬’¾Ýà¸w­C ÝbüBýzæ{õ€ïµô­­AÝêøÒæýÝXÝ‘
ªø§¤Ýƒ­C·xÝsÏõ® ­AÝêøÒæýÝXÝ‘ú|šÝùô¶Ýƒ­C

ùØ¾×ÝêøÒýœ¾Ö¦§ððùŒÝW§ëùà«T®OððùŒÝW§ëªOøáÏ@¦§­C

ÝbüBýzæ{õ€ïµô­­Añzú|ÝªùøT©õ "æoý{ð®«’¦§¦«Ž‘­C ¦«Ž‘ñNæL¦küQù£¾X­C" üoªOÏ@ðà
ø¥ÝãøT©õ­AùÇÏœ¬vTù£¾Xæ{Ý­¦§ôôõQõûÝù­C ú¡¾~ùàµ„¦§ûˆ‚ÝW§ë¯P¾®e¸ãüBýz¦¡©‘ÏÏ
¦§¦«Ž‘Ïõûˆ‚ÝW§ëªêÝP©­Aú|Æ¾šÝûøT©õ­C

22.13.5 ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆ©’ðš·xÏÏÏá­v

ñz¾i¾HôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆ©’ðš·xÏÏÏá­v­Cñz¾i¾HùØ¾×­u÷ˆ©’ðš·xÏÏÏá­v¸×¸R¾O
Ý‘­C

ðYðnùØ¾×­u÷ˆ©’ðš·xÏÏÏá­vôžÏJ¬Ñ¾š¯yù¾·­A«Ñ­G

  1. ®”Ï@ÏU ô}¸l --> æ{Ý­ôø --> IBM DB2 --> ññùŒÏÏÏá­CõYú|ô}ñã DB2­uññùŒÏÏ
     Ïá­v­C
  2. ô}ñã­u÷ˆ©’ðš·xÏÏÏá­vùÇænÏJ­C
  3. Ýbðš·xÏW®”Ï@ÏU¾kµ„­CõYú|ô}ñã­uôžÏJ­væ›æ­­C
  4. ®”Ï@ÏU ôžÏJïyðz÷ˆ©’ -> ERwin­CõY¾iô}ñãôžÏJïyðz÷ˆ©’æ›æ­­C
  5. Ýb¨‚ÏJ·Ž‘ÝÏÏ­Aµ„ÏJ¨‚ÏJ¬Ñ¾š¯yù¾·¦§ÝW§ë­AùÇ®”Ï@ÏU«T¸w­C
  6. ÏŽ¨‹ù£¾XªP¦ª§ä¾ÏŽ¨‹©­A¾H¸w÷q ERwin ªP¦ª§ä¾ïyðz÷ˆ©’¬ã®ªªøðš·x§ä¾­C

õûÝùôžÏJÏõ® ­Añz¾i¾H®”Ï@ÏU·Óæ› --> ï_ús¾H·Óæ›ús¦§ùB’J­C

ðYðnùØ¾×¸R¾OÝ‘ôžÏJ¬Ñ¾š¯yù¾·­A«Ñ­G

        iwh2imp2 tag-filename log-pathname
target-control-db userid password

tag-filename
     ¬Ñ¾š¯yù¾·¦§õûóÆ÷“©|¸M·©žÝW§ë­C

log-pathname
     Ï‚¯x·¦§õûóÆ÷“©|ÝW§ë­C

target-control-db
     ôžÏJ¦§¾¬Ñ÷ˆ©’©wÝW§ë­C

userid
     ¾×ùàÝsù£ññùŒ÷ˆ©’©w¦§ùØ¾×¦Þ ID­C

password
     ¾×ùàÝsù£ññùŒ÷ˆ©’©w¦§üqÝ‘«X­C

ðYðnšõ¢ DB2 ÷ˆ©’©w¸w÷qùØù„Ýùªø­u÷ˆ©’ðš·xÏÏÏá­vÏÏ¦§Ï@ðàùàú«­A ñz¾i¾Hšõ¢¬Ñ
¾š¯yù¾·­G

   * øwû‹ñzðnõ@ªøùàú«¦§ùCÏ@ðà÷ˆ©’©w­AñN ISWH ¬Ñ¾šñq ISWH(Y) šõ¢ªø
     ISWH(N)­C
   * øwû‹ñzðnõ@ªøùàú«¦§ùCÏ@ðà÷ˆ©’©w­AñNÇ”®Y¬Ñ¾šñq :RELTYPE.TYPE(LINK)
     SOURCETYPE(SCGTARIR) TARGETYPE(DATABASE) šõ¢ªø :RELTYPE.TYPE(LINK)
     SOURCETYPE(SCGSRCIR) TARGETYPE(DATABASE)­C

ôžÏJ¬Ñ¾š¯yù¾·® ­Añzú|ÝªùÏUÝCøT©õ­G

Message: DWC13238E The object of type "COLUMN" identified by "DBNAME(___)
OWNER(___) TABLE(___) COLUMNS(___)" is defined twice in the tag language
file.

üoªOÏ@ðàø¥ÝãøT©õ­Añz¦§ôžÏJÏwôôõQõûÝù­C ðYñzó™Ýü¦§ûˆ‚ùÆÝüÝPÝW¦§¾~ùàµ„­A¸×ó™
Ýü¦§ûˆ‚ùÆÝüù§I¶_¬vT¦§ÇçÝÏw¸RÝW¦«Ž‘­A ¸×ù„¾ÝÇçÝ¦§ñ­¦p­Añzú|ÝªùÝûøT©õ­C
·Óªdñz¦§¬ã®ªªOõ_Ýüð®«’¦§¦«Ž‘ÝW§ë­A æM® ôiÝ‘óAú¡¦§«åóÆ­C

22.13.6 ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆøT®ª¨ì§èýzæ{Ý­­v

ôžÏJ¬Ñ¾š¯yù¾·ù­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÝüùƒðàÏŠ¦k­C ñz¾i¾HùØ¾×­u÷ˆøT®ª¨ì§èýz
¦Þ­v¸×ùØ¾×®¾OÝ‘­C

ùØ¾×­u÷ˆøT®ª¨ì§èýz¦Þ­vùàôžÏJ¬Ñ¾š¯yù¾·­G

  1. ®”Ï@ÏUô}¸l --> æ{Ý­ôø --> DB2 --> ÷ˆøT®ª¨ì§èýzæ{Ý­­C
  2. ®”Ï@ÏU®ª¨ì --> ôžÏJ­CõYú|ô}ñã­uôžÏJ­væ›æ­­C
  3. ®”Ï@ÏUïMõ„ùàújïM¬Ñ¾š¯yù¾·­AæM® ®”Ï@ÏUôžÏJ­C

õûÝùôžÏJÏõ® ­Añz¾i¾H®”ùƒÏU¾DÝ©ûØ¾š­Aüoú|ô}ñãÏ@ðàæ›æ­­AÆ¾š¸ãÝüôžÏJ¦§¬ã®ªÏ×
÷ˆ©’©w­C

ðYðnùØ¾×¸R¾OÏôðñôžÏJ¬Ñ¾š¯yù¾·­A«Ñ¨‚ÏJÏUÝC®¾O­G

DGUIDE /USERID userid /PASSWORD password
 /DGNAME dgname /IMPORT filename /LOGFILE
filename /ADMIN /RESTART (B|C)

/USERID
     ¾×ùàÝsù£ññùŒ÷ˆ©’©w¦§ùØ¾×¦Þ ID­C

/PASSWORD
     ùØ¾×¦Þ ID ¦§üqÝ‘«X­C

/DGNAME
     ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÝW§ë­C

/IMPORT
     ¬Ñ¾š¯yù¾·¦§õûóÆ÷“©|¸M·©žÝW§ë­C

/LOGFILE
     Ï‚¯x·¦§õûóÆ÷“©|ÝW§ë­C

/ADMIN
     ®¾šñz¾H§èýz¦Þùð¾öænÏJ­C

/RESTART
     ®¾šôžÏJñNñq¬Ñ¾š¯yù¾·ô}·YüBñãøÒ (¨‹ôæ B)­A¸×ñqÏWÏ@ðà«T¸w¶IñãøÒ (¨‹ôæ
     C­Aûwü]ðÔ)­C

22.13.7 §ÇÇ›ñ’÷¥

ðYñzÝªù¨—¯~øT©õ­A«ÑÝbÝûüB¦§øT©õÏÏõ„ù÷¥ùM¨—¯~¾iñŽù£¦§øÒõ@­C

¨•¾½¦§ ER1 ¨‚ÏJ·¸×¬Ñ¾š¨‚¾X·­C

ïyðz÷ˆ©’ù£¾Xæ{Ý­¯íðnîS¸wÝ÷õ€¦§ùƒðàø¥¬’­C ýŽÏ@ðàø¥¬’ªø ER1 ·ÝW­AýŽÏGðàø¥¬’
ªø¬Ñ¾š¨‚¾X·ÝW§ë­C ðY®¸wý{Ýs¦§¬Ñ¾š¯yù¾·ÝW§ë­A®h·©žú|üQõ‹¬g­C

Windows ùtý×ýõñ`æ{Ý­ýžÏŒ­C

¨‚ÏJ ER1 ·¾iî…üB¸¢øá¦¦ª§A­CðY·xÝs ER1 ·©æo¾ÖøíÇD­AÝà¾Bïyðz÷ˆ©’ù£¾Xæ{Ý­
ñN÷à ·©ž÷m¸¢øá¦¬ãÝ­ÏÏ­A®hú|æo¾ÖÝûñ­¦p­C«ÑÝb®¾O Shell ÏÏæo¾XÏUÝC®¾O­G

attrib -r inputFile.er1

¶€¾HñN ER1 ·©ž¦ª§Ašõ¢ªø¦ù£/¬gÏJ­C

æL¦kô}ñã¬Ñ¾š¯yù¾·­C

·Óªdùtý×ÏÏÝüæLüyÝù·©žæL¦kÝbý{Ý‘§Ø§Ñóöô}ñã¸×®¾á¦§¾“Ý¢øíÇD­C

õ„Ïœù¬ã¦O·¦§÷“©|­C

¾¬ü]¸w·“ûãš¬’ VWS_TEMPLATES­C·Óªd­u÷ˆ©’ðš·xÏÏÏá­vªOõ_ÏwÝw÷Ó­C

õ„ÏœùÇç®ª·¦§÷“©|­C

¾¬ü]¸w·“ûãš¬’ DGWPATH­C·Óªd­u÷ˆ©’ðš·xÏÏÏá­vªOõ_ÏwÝw÷Ó­C

¾¬Ï„ï¸¦§Ý›¦Aóû¦¸¾¯­G...

ñzûµ÷åÝêù„ÏÏù£¾X¦§¨‚ÏJ ER1 ··xÝsÝbÏœùæ{Ý­Ï„ï¸¦§¾¬ÑÝ›¦AóûÏW­C «ÑñãøÒ
ERwin­Bô}ñã ER1 ·­AæM® ®”Ï@ÏUÝ›¦Aóû --> ¾¬ÑÝ›¦Aóû­A¾HÏ×óAú¡¦§¦¸¾¯ [«Ñø¥ó\
ün‚¯íùD]­C·xÝs ER1 ·­C

Ïœ¸£¦§ ERwAPI ¨—¯~­C

æo¾Ö ERwin API ¨—¯~­Aæ{Ý­æL¦kù£ño¨—¯~¦§ªêÇ”÷ˆøT­C «Ñ«T¸w ERwin 3.5.2 ÏwÝw
÷Ó­Cñz¾ýôúænøO ERwin API­C

ðYðnænøO ERwin API­A«ÑñqÝw÷Ó ERwin æ{Ý­·¸ãÝb¦§¾¨ìøäÝ‘ÏUÝC®¾O­G regsvr32
er2api32.dll­C ñzú|ªíùøT©õ "DllRegisterServer in er2api32.dll succeeded"­C
ñz¾i¾Hñq­u÷ˆ©’ðš·xÏÏÏá­vñãøÒù£¾Xæ{Ý­­A¸×ñq®¾O Shell æo¾X flgerwin ®¾Oùàñã
øÒù£¾Xæ{Ý­­C

ù£¾Xæ{Ý­¨—¯~­G...

·Óªd¨—¯~øT©õùÇñŽù£óAú¡øÒõ@­CüoüÞÝü¾iî…ªOÏ§ü­ù£¾Xæ{Ý­¨—¯~­A «ÑÝV IBM ú~øÔ¾N
¦¡ü›õiøíÇD­C

Ïœ¸£¦§ù£¾Xæ{Ý­¨—¯~­C

æo¾ÖÏœ¸£¦§¨—¯~­CüoüÞÝü¾iî…ªOÏ§ü­¨—¯~­A«ÑÝV IBM ú~øÔ¾N¦¡ü›õiøíÇD­C

ù£¾Xæ{Ý­Ý]¨—¯~ÝàýžÏŒ­C

æo¾ÖæL¦kôôõQõûÝùù£¾Xæ{Ý­¦§¨—¯~­C «Ñø¥ó\¦ç¾[¦§¨—¯~øT©õ¾H÷¥ùMøíÇD­A¸×µpæ÷ IBM
ú~øÔ¾N¦¡­C

22.13.8 ERwin ¯P DB2 ÷ˆ©’ðš·xÏÏÏá¦§û‹ªM

¾¯÷`¯­¸£¾Dðn ERwin ¦®¾¢Ží¸ÒÝpÝ¢û‹·üù­u÷ˆ©’ðš·xÏÏÏá­v¬Ñ¾š­G

÷ˆ©’©w - WarehouseDatabase.tag ¸× SourceDatabase.tag

 ERwin               ¸R¾OÝ‘¬Ñ¾š                  ÷ˆ©’ðš·xÏÏÏá
 ûØ÷¥ÝW§ë            NAME                        ðš·xùàú«¸×ðš·x¾¬Ñ¦§ÝW§ë
 ûØ÷¥õ@¦Þ            RESPNSBL                    µpæ÷
 ÷ˆ©’©wÝW§ë          DBNAME                      ÷ˆ©’©wÝW§ë
 ÷ˆ©’©w¦¸¾¯          DBTYPE                      ÷ˆ©’©wÇç®ª
 ûØ÷¥¯­¸£            SHRTDESC                    ¯­¸£

¦¡©‘ - Table.tag

 ERwin                ¸R¾OÝ‘¬Ñ¾š                  ÷ˆ©’ðš·xÏÏÏá
 ¦¡©‘ÝW§ë             NAME                        ¦¡©‘ÝW§ë
 ¦¡©‘ÝW§ë             TABLES                      ¦¡©‘ÝW§ë
 ÷ˆ©’©wÝW§ë           DBNAME                      æL
 ¦¡©‘ó™Ýü¦Þ           OWNER                       ¦¡©‘§ä¾
 ¦¡©‘æ—÷¥             SHRTDESC                    ¯­¸£

¦«Ž‘ - Column.tag

 ERwin                ¸R¾OÝ‘¬Ñ¾š                  ÷ˆ©’ðš·xÏÏÏá
 ¦«Ž‘ÝW§ë             NAME                        ¦«Ž‘ÝW§ë
 ÷ˆ©’Çç®ª             NATIVEDT                    ÷ˆ©’Çç®ª
 ¦›®ž                 LENGTH                      ¦›®ž
 Ïp¬’Ý¬’             SCALE                       Ïp¬’Ý¬’
 Null ¨‹ôæ            NULLABLE                    ñæù¦ðÔ (ÏŽ¨‹©)
 Ý÷m                 POSNO                       æL
 ¾Dðnµ„               KEYPOSNO                    æL
 ÷ˆ©’©wÝW§ë           DBNAME                      æL
 ¦¡©‘ó™Ýü¦Þ           OWNER                       æL
 ¦¡©‘ÝW§ë             TABLES                      æL
 ¦«Ž‘æ—÷¥             SHRTDESC                    ¯­¸£

22.13.8.1 ERwin ¯P÷ˆøT®ª¨ì§èýzæ{Ý­¦§û‹ªM

¾¯÷`¯­¸£¾Dðn ERwin ¦®¾¢Ží¸ÒÝpÝ¢û‹·üù­u÷ˆøT®ª¨ì§èýzæ{Ý­­v¬Ñ¾š­G

÷ˆ©’©w - Database.tag

 ERwin             ¸R¾OÝ‘¬Ñ¾š               ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏôðñ
 ûØ÷¥ÝW§ë          NAME                     ÷ˆ©’©wÝW§ë
 ûØ÷¥õ@¦Þ          RESPNSBL                 ÷ˆ©’©wó™Ýü¦Þ
 ÷ˆ©’©wÝW§ë        DBNAME                   ÷ˆ©’©wÝW§ë
 ÷ˆ©’©w¦¸¾¯        DBTYPE                   ÷ˆ©’©wÇç®ª
 ûØ÷¥¯­¸£          SHRTDESC                 ¶ýæu¦§¯­¸£

¦¡©‘ - TableOrView.tag

 ERwin              ¸R¾OÝ‘¬Ñ¾š               ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏôðñ
 ¦¡©‘ÝW§ë           NAME                     ¦¡©‘ÝW§ë
 ¦¡©‘ÝW§ë           TABLES                   ¦¡©‘ÝW§ë
 ÷ˆ©’©wÝW§ë         DBNAME                   ÷ˆ©’©wÝW§ë
 ¦¡©‘ó™Ýü¦Þ         OWNER                    ¦¡©‘ó™Ýü¦Þ
 ¦¡©‘æ—÷¥           SHRTDESC                 ¶ýæu¦§¯­¸£
 ERwin API          TABLVIEW                 ¸w÷q¾N¦¡Ï@ðàúõýÏ¦¡

¦«Ž‘ - ColumnOrField.tag

 ERwin              ¸R¾OÝ‘¬Ñ¾š               ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏôðñ
 ¦«Ž‘ÝW§ë           NAME                     ¦«Ž‘ÝW§ë
 ÷ˆ©’Çç®ª           DATATYPE                 ¦«Ž‘¦§÷ˆ©’Çç®ª
 ¦›®ž               LENGTH                   ¦«Ž‘¦§¦›®ž
 Ïp¬’Ý¬’           SCALE                    ¦«Ž‘¦§Ïp¬’Ý¬’
 Null ¨‹ôæ          NULLS                    ¦«Ž‘¾iõ_ªø¦ðÔ (?)
 Ý÷m               POSNO                    ¦«Ž‘Ý÷m
 ¾Dðnµ„             KEYPOSNO                 ¾Dðnµ„ÏÏ¦«Ž‘¦§Ý÷m
 ERwin API          ISKEY                    ¦«Ž‘ªOõ_ªøµ„¦§Ï@ü­¾ö (?)
 ERwin API          UNIQKEY                  ¦«Ž‘ªOõ_ªøøáÏ@µ„ (?)
 ÷ˆ©’©wÝW§ë         DBNAME                   ÷ˆ©’©wÝW§ë
 ¦¡©‘ó™Ýü¦Þ         OWNER                    ¦¡©‘ó™Ýü¦Þ
 ¦¡©‘ÝW§ë           TABLES                   ¦¡©‘ÝW§ë
 ¦«Ž‘æ—÷¥           SHRTDESC                 ¶ýæu¦§¯­¸£
 ERwin              ISTEXT                   ÷ˆ©’ªOõ_ªøÏ†Ýr (?)
 ERwin API          IDSRES                   ÷ˆ©’¦§÷¥¦R®ž

¬ã®ª - Model.tag

 ERwin              ¸R¾OÝ‘¬Ñ¾š              ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏôðñ
 ER1 ·ÝW           NAME                    ¬ã®ªÝW§ë
 ûØ÷¥õ@¦Þ           RESPNSBL                ôiÏ@ùB÷ˆøT...
 ûØ÷¥¯­¸£           SHRTDESC                ¶ýæu¦§¯­¸£

ûˆ‚ - Entity.tag

 ERwin             ¸R¾OÝ‘¬Ñ¾š              ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏôðñ
 ûˆ‚ÝW§ë          NAME                    ûˆ‚ÝW§ë
 ¦çæ—              SHRTDESC                ¶ýæu¦§¯­¸£
 ¸w÷q              LONGDESC                ÷âýà¯­¸£
 ûˆ‚ó™Ýü¦Þ        RESPNSBL                ôiÏ@ùB÷ˆøT...

Ží¸Ò - Attribute.tag

 ERwin             ¸R¾OÝ‘¬Ñ¾š              ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏôðñ
 ¦®¾¢ÝW§ë          NAME                    ¦®¾¢ÝW§ë
 ¦çæ—              SHRTDESC                ¶ýæu¦§¯­¸£
 ¸w÷q              LONGDESC                ÷âýà¯­¸£
 ÷ˆ©’Çç®ª          DATATYPE                Ýùð–¦§÷ˆ©’Çç®ª
 ¦›®ž              LENGTH                  Ýùð–¦§¦›®ž
  ------------------------------------------------------------------------

22.14 ¨z¨‹­u÷ˆ©’ðš·xÏÏÏá­v¦§ÝW§ë¯PÝõ}

22.14.1

ùØ¾×­u÷ˆ©’ðš·xÏÏÏá­v¸M­uTrillium ün‚ùtý×­vùà¨z¨‹ÝW§ë¯PÝõ}÷ˆ©’­C
­uTrillium ün‚ùtý×­vªOÏ@ðàÝW§ë¯PÝõ}¨z¨‹ýœ®~­A ¾i¾Hð®ús©‘Ý­Ï’­B¬Ñú€Ï’Ï×‡
ÇãÝW§ë¸MÝõ}÷ˆ©’­C¶€¾¥ñqùØ¾×¦Þ¸w÷qæ{Ý­ñãøÒ­uTrillium õ†Ý÷ùtý×­væ{Ý­­Añz¾i¾H
Ýb­u÷ˆ©’ðš·xÏÏÏá­vÏÏùØ¾×­uTrillium ün‚ùtý×­v­C ú¡ñzñq­uTrillium õ†Ý÷ùtý×­v
Script ¸× JCL ôžÏJïyðz÷ˆ©’©­Aú|ñNùØ¾×¦Þ¸w÷qæ{Ý­ús¬WÝš­uðš·x­vóÐ¦ªæý§cÏÏ­C

­u÷ˆ©’ðš·xÏÏÏá­vÏwïœù¥¯P Vality and Evolutionary Technologies, Inc ¦§ÏuùÆÏõ
óÆÝX­C

22.14.1.1 ø•¾¯ðnùD

   * ñz¾ýôúÝbðš·x¾Nýzæ{Ý­§í¸×¯ú§í¾Dûq÷œÏWÝw÷Ó­uTrillium ün‚ùtý×­v­C
   * Ýb UNIX ¸M Windows ¾ð¾xÏW­A¾ýôúñN­uTrillium ün‚ùtý×­v¦§ bin ¾¨ì÷“©|
     ús¬WÝšùtý×·“ûãš¬’ PATH ÏÏ­AÏ~î…ñã¾×¾Nýzæ{Ý­æ{õ€ùàøäÝ‘­uTrillium õ†Ý÷
     ùtý×­væ{Ý­­C Ýb UNIX ÏW­AñãøÒ vwdaemon æ{õ€Ïõ®e­A¾ýôúñN PATH š¬’¾[ÏJ
     IWH.environment ·ÏÏ­A¾HõûÝùøäÝ‘­C
   * ùØ¾×¦Þ¾ýôúùÆü’ Trillium ün‚¦§ùØ¾×ñ`Ç¥­C

ÏU¦¡Æ¾šün‚¯íùD­C

 õ@ú~ùtý×                             ¾ýðn¦§ün‚
 UNIX                                 Trillium ün‚ùtý× ¦¸¾¯ 4.0

                                      ­u÷ˆ©’ðš·x§èýzæ{Ý­­v¦¸¾¯ 7.2 ðš·x¾N
                                      ýzæ{Ý­
 Windows NT ¯P Windows 2000           Trillium ün‚ùtý× ¦¸¾¯ 4.0

                                      ­u÷ˆ©’ðš·x§èýzæ{Ý­­v¦¸¾¯ 7.2 ðš·x¾N
                                      ýzæ{Ý­

                                      ¾H¯ú§íÝsù£Ýàù¾­A¾Dûq÷œ¾ýôúÝw÷Ó ftpd
                                      ¸M rexecd ñ`ónæ{Ý­­C
 OS/390                               Ýw÷ÓÝb¯ú§í OS/390 ¾Dûq÷œ¦§­uTrillium
                                      ün‚ùtý×­v¦¸¾¯ 4.0

                                      Ýw÷ÓÝb UNIX­BWindows NT ÏW¦§­u÷ˆ©’ðš
                                      ·x§èýzæ{Ý­­v¦¸¾¯ 7.2 ðš·x¾Nýzæ{Ý­

                                      ¾ýôúÝw÷Ó TCP/IP 3.2 (¸×¾HÏW)

                                      ôÔÏ„ï¸ªø¯ú§í¾Dûq÷œ¦§ OS/390 õ@ú~ùtý×

22.14.1.2 Trillium ün‚ùtý×Ï÷¾¢

­uTrillium ün‚ùtý×­v¾¥¾|ðà¾DðnÏ÷¾¢ýåõ@­G ¶…ï®óû­Bð†¦Róû­Bgeocoder Ï×Ï€øt
óû­CùØ¾×üoù€Ï÷¾¢ªøÏ@ýå¾\î…­A ¾HøäÝ‘ÝW§ë¯PÝõ}¨z¨‹õ@ú~­Cñz¾i¾Hñq­uTrillium
õ†Ý÷ùtý×­v(Ï@ðàùØ¾×¦Þ¸w÷qæ{Ý­) øäÝ‘üoù€Ï÷¾¢­C

¶…ï®óû
     ùØ¾×¶…ï®óûùà¬Ñú€Ï’Ï×ñNùàú«÷ˆ©’¶…ï®Ýù®¸w¦§¨‚¾X©‘Ý­­C

ð†¦Róû
     ùØ¾×ð†¦Róûùà÷¥ŽôÝW§ë¸MÝõ}ùàú«÷ˆ©’­A¾HÏ×®¾áùàú«÷ˆ©’ªêÇ”¦§ïyðz÷ˆ©’­C

Ýaýz«s«Xæ{Ý­ (Geocoder)
     ùØ¾× geocoder ñNùàú«÷ˆ©’¯Pôl¯¬¦AøÔæ{Ý­÷ˆ©’øæÏ¤÷–­A ¾Hïœù¥¾“Ý¢¨•§|÷ˆ
     øT­AùãÝpñH¾¢¦Þ¸× ZIP+4 Ýr«X­Cgeocoder Ï]¾iüzûL­uªøˆý×ðp«åªd­v ÷ˆ©’ùà
     øäÝ‘Ï¤û‹õ@ú~­C

Ï€øtóû
     ùØ¾×Ï€øtóûùàÏ¤÷–ÇçÝÝW§ë¸MÝõ}¾HÇ¥õOð®«’øO¨ì­C ñz¾i¾HùØ¾×Ï€øtóûøäÝ‘ø¥
     úàÏ¤û‹­A¾HÏ¤÷–Ï@ðàøO¨ì¯PÏ@ýåøO¨ì­C

22.14.1.3 ñN­uTrillium õ†Ý÷ùtý×­v¯P­u÷ˆ©’ðš·xÏÏÏá­vúføtùØ¾×

Ýb­u÷ˆ©’ðš·xÏÏÏá­vÏÏ­Añz¾i¾HôžÏJ­uTrillium õ†Ý÷ùtý×­vïyðz÷ˆ©’Ï×®¾áùØ¾×¦Þ¸w
÷qæ{Ý­ùB’J­CÝûùB’Jú|¸I¾s¾¯§íðš·x¾Nýzæ{Ý­§í¸×¯ú§íðš·x¾Nýzæ{Ý­§íÏW¦§
­uTrillium õ†Ý÷ùtý×­vScript­C Ýb­u÷ˆ©’ðš·xÏÏÏá­vÏÏ­A­uTrillium õ†Ý÷ùtý×­v
Script ªOÏ@ðàùÆÝüùàú«Ï×¾¬Ñ·¦§ùB’J­Cùàú«·ªO¾×¸¢ýŽÏ@ðà­uTrillium õ†Ý÷ùt
ý×­v¸R¾O¦§¨‚ÏJ÷ˆ©’·­C ¾¬Ñ·ªO Script ÏÏüÞ® Ï@ðà Trillium ¸R¾O¸ã®¾á¦§¨‚¾X
÷ˆ©’·­C æM® ­A¾i«’¯sÝûùB’JÝš¾tÏ@ðàüBýzæ{õ€­Aúføtù„¾ÝùB’JùØ¾×­C

ÏUûØÆ¾š­uTrillium õ†Ý÷ùtý×­v¨‚ÏJÏ×¨‚¾X÷ˆ©’·¯P­u÷ˆ©’ðš·xÏÏÏá­vÏÏùàú«Ï×¾¬Ñ
·Ïõô­¦§Ç”®Y­C

ûØ 1. «dùã Trillium Script ·

REM Running the converter
pfcondrv -parmfile c:\tril40\us_proj\parms\pfcondrv.par
REM Running the parser
pfprsdrv -parmfile c:\tril40\us_proj\parms\pfprsdrv.par
REM Running the Matcher
cfmatdrv -parmfile c:\tril40\us_proj\parms\pfmatdrv.par


ûØ 2. pfcondrv.par ·¦§Ï§©e

INP_FNAME01 c:\tril40\us_proj\data\convinp
INP_DDL01   c:\tril40\us_proj\dict\input.ddl


ûØ 3. pfmatdrv.par ·¦§Ï§©e

OUT_DDNAME  c:\tril40\us_proj\data\maout
DDL_OUT_FNAME  c:\tril40\us_proj\dict\parseout.ddl

ûØ 4. ­uTrillium õ†Ý÷ùtý×­vùB’J¸w÷q

c:\Tril40\us_proj\data\convinp (source file) ->
Trillium Batch System Step -> c:\tril40\us_proj\data\maout (target file)

22.14.1.4 ôžÏJ Trillium ïyðz÷ˆ©’

ðYðnôžÏJ Trillium ïyðz÷ˆ©’ù­u÷ˆ©’ðš·xÏÏÏá­v­G

  1. ®¾á­uTrillium õ†Ý÷ùtý× Script­v¸× JCL­Cñz¾i¾HùØ¾×¾“Ý¢ Script ¸× JCL
     ¬ô¬gÏuùÆùà®¾á Script ¸× JCL ·­C
  2. ¾Hú’û®¾kµ„®”Ï@ÏUðš·x­AæM® ®”Ï@ÏUôžÏJïyðz÷ˆ©’ -> Trillium­Aô}ñã
     ­uTrillium õ†Ý÷ùtý×­væ›æ­­C
  3. Ýb Script ¸× JCL Ž‘ÝÏÏ­Aµ„ÏJñzðnøäÝ‘¦§­uTrillium õ†Ý÷ùtý×­vScript ¸×
     JCL ·ÏõÝW§ë­C
  4. Ýb¨‚ÏJ·Ž‘ÝÏÏ­Aµ„ÏJýŽÏ@Ý÷Ýb®¸w¦§ Script ¸× JCL ·ÏÏøäÝ‘Ïõ­uTrillium
     õ†Ý÷ùtý×­væ{Ý­¦§¨‚ÏJ÷ˆ©’·ÝW§ë­C
  5. Ýb¨‚ÏJ DDL Ž‘ÝÏÏ­Aµ„ÏJ¯­¸£¨‚ÏJ÷ˆ©’·¦§¨‚ÏJ DDL ·ÏõÝW§ë­CÝû·©ž¾ýôú¾i
     Ýbðš·x¾Nýzæ{Ý­§íùØ¾×­C
  6. Ýb¨‚¾X·Ž‘ÝÏÏ­Aµ„ÏJ Script ¸× JCL ·ÏÏüÞ® Ï@ðà­uTrillium õ†Ý÷ùtý×­væ{
     Ý­¦§¨‚¾X÷ˆ©’·ÝW§ë­C
  7. Ýb¨‚¾X DDL Ž‘ÝÏÏ­Aµ„ÏJ¯­¸£¨‚¾X÷ˆ©’·¦§¨‚¾X DDL ·ÏõÝW§ë­CÝû·©ž¾ýôú¾i
     Ýbðš·x¾Nýzæ{Ý­§íùØ¾×­C
  8. ¨‹¾×¦§­GÝb¨‚¾X¨—¯~·Ž‘ÝÏÏ­A µ„ÏJñzðnùØ¾×¦§¨‚¾X¨—¯~·ÝW§ë­CÝû¨—¯~·ú|
     ñq­uTrillium õ†Ý÷ùtý×­væ{Ý­¶^ù£øäÝ‘ïµ¨—¯~­Cüoù€¨—¯~øO¨ì¸¢ stderr Ï‚¯x
     ÏÏ­C¾H¾¯§í¾Dûq÷œÝàù¾­AðYñz¾¬ÝbÝû®¸wÝW§ë­A ®hú|®¾áûwü]¨‚¾X¨—¯~·­CÝü
     Ç”¨‚¾X¨—¯~·¦§÷âýà÷ˆøT­A«Ñø¥ó\¾DÇD­u¨—¯~üBýzñ`Ý­­v­C
  9. ®”Ï@ÏUüs«u¬Ñã­C
 10. ðYñzôžÏJ¦§ Trillium ïyðz÷ˆ©’Ý¸¢ðš·x¾Nýzæ{Ý­§íÏW­A «Ñ®”Ï@ÏU¾¯§í¾Dûq÷œ
     ­C

     ðYñzôžÏJ¦§ Trillium ïyðz÷ˆ©’ÏœªOÝ¸¢ðš·x¾Nýzæ{Ý­§íÏW­A «Ñ®”Ï@ÏU¯ú§í¾D
     ûq÷œ­AæM® ®¸w¯ú§í¾Dûq÷œ­C «Ñø¥ó\¾¯÷`æy® ïœù¦§¾DÇD­u®¸w¯ú§í¾Dûq
     ÷œ­v­C
 11. ®”Ï@ÏU«T¸w­A¾HôžÏJ Trillium ïyðz÷ˆ©’ùÇÇ”üª÷àæõøO¾¯­C
 12. ðY Script ¸× JCL ÏœªOñqûwü]¾Nýzæ{Ý­§íøäÝ‘­A«ÑÝb­uÏ§©e­væõøO¾¯ÏÏ®¸w¾×
     ¸¢­uTrillium õ†Ý÷ùtý×­vùB’J¦§ðš·x¾Nýzæ{Ý­§í­C

ôžÏJõ@ú~õûÝù® ­AÏUÝCðš·x¦®¾¢ú|ús¬WÝš­uðš·x­vóÐ¦ªæý§cÏÏ­C

   * Trillium õ†Ý÷ùtý× scriptName ¬ã¦O­A ù„ÏÏ scriptName ªO Script ¸× JCL
     ·¦§ÝW§ë­C
   * ­uTrillium õ†Ý÷ùtý×­vüBýzæ{õ€­C
   * øäÝ‘ùØ¾×¦Þ¸w÷qæ{Ý­¦§­uTrillium õ†Ý÷ùtý×­vùB’J­C
   * ôžÏJïyðz÷ˆ©’©®¸w¦§ðš·x·©žùàú«Ï×¾¬Ñ­C·©žùàú«Ï×·©ž¾¬Ñªø¸T¸w·©ž­C
   * ­uTrillium õ†Ý÷ùtý×­væ{Ý­÷sýå­C

®¸w¯ú§í¾Dûq÷œ

ðYðn®¸w¯ú§í¾Dûq÷œ­A«Ñ­G

  1. ®”Ï@ÏU¯ú§í¾Dûq÷œ­AæM® µ„ÏJõtÝüñzôžÏJ¦§ïyðz÷ˆ©’Ïõ¯ú§íùtý×¦§ TCP/IP ¾Dûq
     ÷œÝW§ë­CðY¨‹ù£­u¯ú§í¾Dûq÷œ­v­A®h¾¬Ñ·üQ®¾áªø¾¯§í·©ž­A Ý]ªø¯ú§í¾¬Ñ
     ·ÏœùÏ„ï¸­Cñz¾i¾Hús¬W FTP ùB’JùàùØ¯ú§í·©žÝùªø®¸w¦§¾¯§í¾¬Ñ·­C
  2. Ýb¯ú§íõ@ú~ùtý×ýMü‘ÏÏ­A®”Ï@ÏUñzÝsù£¦§¯ú§í¾Dûq÷œÏõõ@ú~ùtý×­C
  3. Ýb¯ú§íùØ¾×¦Þ ID Ž‘ÝÏÏ­Aµ„ÏJñzÝsù£¦§¯ú§í¾Dûq÷œÏõùØ¾×¦Þ ID­C
  4. ÝbüqÝ‘«X¨‹ôæýMü‘ÏÏ­A¨‹ù£¾×¸¢¸ãðnÝsù£¦§¯ú§í¾Dûq÷œÏõüqÝ‘«X¨‹ôæ­G

     Ïœ¯íðnüqÝ‘«X
          ®¸wÝsù£¯ú§í¾Dûq÷œ¦§ïyðz÷ˆ©’Ïœ¯íðnüqÝ‘«X­C

     ¶^ù£üqÝ‘«X
          ®¸wñqùØ¾×¦Þ¸w÷qæ{Ý­¶^ù£üqÝ‘«X­C

          ÝbüqÝ‘«Xæ{Ý­Ž‘ÝÏÏ­Aµ„ÏJñN¶^ù£üqÝ‘«X¦§üqÝ‘«Xæ{Ý­ÝW§ë­C Ýûæ{Ý­¾ýôú
          Ý¸¢ðš·x¾Nýzæ{Ý­§í­AùÇ¾BñNüqÝ‘«X¬gÏJ¨‚¾X·¦§ýŽÏ@Ý‘ÏÏ­C

          Ýbæ{Ý­ø¥¬’Ž‘ÝÏÏ­Aµ„ÏJüqÝ‘«Xæ{Ý­¦§ø¥¬’­C ýŽÏ@ðàø¥¬’¾ýôúªO¬gÏJüqÝ‘
          «X¦§¨‚¾X·­C

     æy® ¨‚ÏJüqÝ‘«X
          ®¸wæy® ÝA¨‚ÏJüqÝ‘«X­C

          ÝbøäÝ‘­uTrillium õ†Ý÷ùtý×­væ{Ý­¦§ùB’JÏõ­uÏ§©e­væõøO¾¯ÏÏ­A¨‚ÏJüqÝ‘
          «X­C

22.14.1.5 û‹ªMïyðz÷ˆ©’

ªøÏF®¾áùàú«¸M¾¬Ñ·¦§ïyðz÷ˆ©’­ATrillium ú|¦ù£ Trillium DDL ·­C Ýû DDL ·
ú|¶…ï®ÝùÏUÝC­u÷ˆ©’ðš·xÏÏÏá­v÷ˆ©’Çç®ª­G

 UNIX­BWindows NT Ï×õ@ú~ùtý×¦§ DDL ÷ˆ
 ©’Çç®ª                              ðš·x÷ˆ©’Çç®ª
 ASCII CHARACTER                     CHARACTER(n)

 ASCII NUMERIC

 EBCDIC CHARACTER

 EBCIDIC NUMERIC
 ù„¾ÝÇç®ª                            NUMERIC
 æ—:
      øáÝü­uTrillium ün‚ùtý×­vÝb OS/390 õ@ú~ùtý×ÏWøäÝ‘­AEBCDIC CHARACTER
      ¸M EBCIDIC NUMERIC ÷ˆ©’Çç®ªÏ~ùùÏ„ï¸­C

š¬’ n ¾N¦¡ÝrÝˆÏÏ¦§ÝrÏ÷¬’­C

22.14.1.6 ððùŒ

ñz¾i¾HüzûL­u÷ˆ©’ðš·xÏÏÏá­vÏÏ¦§ôžÏJïyðz÷ˆ©’õ@ú~Ï× Trillium DDL­A Ýb¨‚ÏJÏ×¨‚
¾X DDL ·ÏÏ®¸wÏ@ù€ð®|Ž‘Ý­C ÏœûL­Aªêû‹·ü¦§ðš·xùàú«Ï×ðš·x¾¬Ñ·©žÏœî…Ýb
­u÷ˆ©’ðš·xÏÏÏá­vÏÏúføt SQL ùB’J¸×«dùãÏ§©eùØ¾×­C Ý]ªøôžÏJïyðz÷ˆ©’õ@ú~ú|¸¨ýÏ
ôVûLóÆðàøO¨ì¦§ð®|Ž‘Ý­A¸ã¾HñzÏï¾i®¸wüoù€Ž‘Ý­A Ýì¾ÝðÞÝbæý¦Gùàú«Ï×¾¬Ñ·ÏÏ
Ïœî…ú¡õ@¦«Ž‘ùØ¾×­C

ðY®¸wÏF¨—¯~·­A®h Script ¦§ÝW§ëÏœî…¾]õt¾“Ý¢¦©‘­C

22.14.2 ¬ô¬g Trillium õ†Ý÷ùtý× JCL ·

ðYðn¬ô¬g Trillium õ†Ý÷ùtý× JCL ·­AÏUÝC¯íùD¾ýôúýÝX­C

   * Ïuõ@ÝW§ë¾ýôúªOùØ¾×¦Þ ID ¾[ÏWÏ@ðàÝrÏ÷­C
   * Ïuõ@¾ýôú¯¬øeÝšÏw®Oîd¨‚¾XÇçõOÏÏ­C
   * øäÝ‘­uTrillium õ†Ý÷ùtý×­væ{Ý­¦§ùCÏ@ðàÏuõ@ùB’J­A ¾ýôúù™ÏJ¸w÷q¾ÇÏ[÷ˆ©’ôø
     ¦§ SYSTERM DD üîðzÝ­­CÝû÷ˆ©’ôø¾]õt­uTrillium õ†Ý÷ùtý×­væ{Ý­¦§¨—¯~­Cïœ
     ¾X JCL Ïõ®e­AÝû÷ˆ©’ôøú|ÝêøÒüQõRøœ­C ÝüÇ”¨—¯~üBýzñ`Ý­Ï×ü›õi¦§÷âýà÷ˆøT­A
     «Ñø¥ó\¾DÇD­u¨—¯~üBýzñ`Ý­­v­C

ú¡ Script ¸× JCL Ýb¯ú§í¾Dûq÷œÏWøäÝ‘©­A¾ýôú®¸w¨‚¾X¨—¯~·­F õ_®h­A¨—¯~øT©õ
Ïœú|üQøO¨ìÏ×ô€øeÝš­u÷ˆ©’ðš·xÏÏÏá­v­C Ýb UNIX ¸× Windows ÏW­A¶^ù£¨—¯~øT©õüÞ
¶ýü‘¦§ÏŠ¦kªO¬ô¬g¾tÏ@ðà¸I¾s­uTrillium õ†Ý÷ùtý×­vScript ¦§ Script­AùÇñN¬Ñú€¨—
¯~ô€øeÝš¨‚¾X·­C

ûØ 5. ù™ÏJ SYSTERM DD üîðzÝ­¦§Ïuõ@ùB’J«dùã

//SYSTERM  DD UNIT=&UNIT,
//            DISP=(MOD,CATLG,KEEP),
//            SPACE=(400,(20,20),,,ROUND),
//            DSN=&PROJPREF.&TRILVER.&PROJECT.STDERR;

22.14.3 Ýb UNIX ¸M Windows ÏW¬ô¬g Trillium õ†Ý÷ùtý× Script ·

ðY­uTrillium õ†Ý÷ùtý×­vScript ¸×ø¥¬’·¾]õt¨‚ÏJ·¦§ªêû‹÷“©|­A ùØ¾×¦Þ¾ýôúñN
Script ·ô}·Y¦§ cd üîðzÝ­¸¤÷mù Script ·¦§¾¨ìÏÏ­C

22.14.4 ¸w÷q Trillium õ†Ý÷ùtý×ùB’J

Ýb¸w÷q­uTrillium õ†Ý÷ùtý×­vùB’JÏõ®e­Añz¾ýôúñN¸ãðnùØ¾×¦§ Trillium ïyðz÷ˆ©’ôž
ÏJüBýzæ{õ€ÏÏ­Cús¬W­uTrillium õ†Ý÷ùtý×­vùB’JÝšüBýzæ{õ€ÏÏ­G

  1. ô}ñãüBýzæ{õ€¬ã®ªýœ¾ÖóûÏÏ¦§üBýzæ{õ€­C
  2. ®”Ï@ÏU¨‹¾×øØÏW¦§ Trillium õ†Ý÷ùtý×ûØ¾š­C
  3. ®”Ï@ÏU Trillium õ†Ý÷ùtý×æ{Ý­ -> programName­Aù„ÏÏ programName ªOñzðnùØ
     ¾×¦§­uTrillium õ†Ý÷ùtý×­væ{Ý­ÝW§ë­C
  4. ®”Ï@ÏUæe¾ªÏWñzðnÆ¾šùB’J¸ãÝb¦§Ý÷m­C
  5. õûÝù DB2 Universal Database ¯­¸£ÏÏ¾DÇD­u¸w÷qÏ@ðàøäÝ‘ùØ¾×¦Þ¸w÷qæ{Ý­¦§ùB
     ’J­vÏ§¦§ùB’J­C

22.14.5 ùØ¾×­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­

­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­·H¦ç¸¢ Windows NT ¸M UNIX ¦§­uDB2 ÷ˆ©’ðš
·xÏÏÏá­v¦¸¾¯ 7.2 ÏÏ­CñzôžÏJ Trillium ïyðz÷ˆ©’©¸ã®¾á¦§­uTrillium õ†Ý÷ùt
ý×­vùB’J­AñNøäÝ‘­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­­C ùØ¾×¦Þ¸w÷qæ{Ý­ú|¸I¾s
­uTrillium õ†Ý÷ùtý×­vScript ¸× JCL­CÏU¦¡¾]õt¾×¸¢­uTrillium õ†Ý÷ùtý×­vScript
¸× JCL ¦§ø¥¬’­G

 ø¥¬’                                ðÔ
 ¯ú§í¾Dûq÷œ                             * localhost ªøûwü]ðÔ­CðY­uTrillium
                                          õ†Ý÷ùtý×­vÝw÷ÓÝbðš·x¾Nýzæ{Ý­§í­A
                                          ®hùØ¾×ÝûðÔ­C
                                        * ðY­uTrillium õ†Ý÷ùtý×­vÝw÷ÓÝb¯ú
                                          §íõ@ú~ùtý×ÏW­A®hùØ¯ú§í¾Dûq÷œÝW
                                          §ë­C

 Script ¸× JCL                       Script ¸× JCL ¦§ÝW§ë
 ¯ú§íõ@ú~ùtý×                        ¯ú§í¾Dûq÷œÏWõ@ú~ùtý×¦§ÝW§ë­C ðY¯ú§í¾D
                                     ûq÷œø¥¬’ªø localhost­A®hùtý×ÏœüBýzÝû
                                     ø¥¬’­C Ýü©ŽðÔªø­G

                                        * MVS for OS/390 õ@ú~ùtý×
                                        * UNIX for AIX­BSUN Solaris­BHP-UX
                                          Ï× NUMA/Q õ@ú~ùtý×
                                        * WIN for Windows NT ¸× 2000 õ@ú~
                                          ùtý×
 ¯ú§íùØ¾×¦Þ ID                       ó™ÝüøäÝ‘¯ú§í¸R¾O¦§vððÏõùØ¾×¦Þ ID­CðY
                                     RemotehostName ¦§ðÔªø localhost­A®hùt
                                     ý×ÏœüBýzÝûø¥¬’­C
 üqÝ‘«X¨‹ôæ                          ù£ñoüqÝ‘«X¦§ÏŠ¦k­CÝü©ŽðÔªø­G

                                     ENTERPASSWORD
                                          ðYüqÝ‘«XÝbÏUÏ@ðàø¥¬’ô€¯¬­A®hùØ¾×
                                          ÝûðÔ­C

                                     PASSWORDNOTREQUIRED
                                          ðYÏœ¯íðnüqÝ‘«X­A®hùØ¾×ÝûðÔ­C

                                     GETPASSWORD
                                          ðYæ{Ý­ÝW§ëÝbÏUÏ@ðàø¥¬’ô€¯¬­A®hùØ
                                          ¾×ÝûðÔ­C

                                     ððùŒ­G

                                        * Ýûæ{Ý­¾ýôúÝ¸¢¾Nýzæ{Ý­§í­BñNüqÝ‘
                                          «X¬gÏJ¨‚¾X·¦§ýŽÏ@Ý‘ÏÏ­A ¾HÏ×Ýb
                                          ôôõQøäÝ‘® ô€Ý^ 0­C
                                        * üqÝ‘«Xø¥¬’ðÔ¾ýôúªOüqÝ‘«Xæ{Ý­¦§ÝW
                                          §ë­C
                                        * æ{Ý­ø¥¬’ðÔ¾ýôúªO¾H¶—Ïè÷ûªAÝ¡¦§Ýr
                                          Ýˆ­C
                                        * ÝrÝˆÏÏýŽÏ@ðàø¥¬’¾ýôúªO¬gÏJüqÝ‘«X
                                          ¸ãÝb¦§¨‚¾X·ÝW§ë­C
 üqÝ‘«X                              Ýü©ŽðÔªøüqÝ‘«X¸×üqÝ‘«Xæ{Ý­ÝW§ë­CüqÝ‘
                                     «Xæ{Ý­¾ýôúÝ¸¢ðš·x¾Nýzæ{Ý­§í­C
 æ{Ý­ø¥¬’                            üqÝ‘«Xæ{Ý­¦§ø¥¬’­C
 ¨‚¾X¨—¯~·                          ¨‚¾X¨—¯~·¦§ÝW§ë­C
 æ—:
      Ýû¦¡©‘ÏÏ¸ãÝüø¥¬’¦§÷ˆ©’Çç®ªªø CHARACTER­C

22.14.6 ¨—¯~üBýzñ`Ý­

Ýb Windows NT Ï× UNIX õ@ú~ùtý×ÏW­A­uTrillium õ†Ý÷ùtý×­væ{Ý­ñN¨—¯~øT©õ¬gÏJ¬Ñ
ú€¨—¯~ (stderr) ·ÏÏ­AÝàÝb OS/390 õ@ú~ùtý×ÏW­AªO¬gÏJ SYSTERM ÷ˆ©’ôøÏÏ­C

ðYðn¶^ù£ Windows NT ¸× UNIX õ@ú~ùtý×¦§­uTrillium õ†Ý÷ùtý×­væ{Ý­¨—¯~­A ¾ýôú
ñN¬Ñú€¨—¯~ð®úsóÝVÝš¨‚¾X¨—¯~·­C

ðYðn¶^ù£ OS/390 õ@ú~ùtý×¦§­uTrillium õ†Ý÷ùtý×­væ{Ý­¨—¯~­A JCL ¾ýôúù™ÏJ
SYSTERM DD üîðzÝ­­C

ðYÝb­uôžÏJïyðz÷ˆ©’­væ›æ­ÏÏ®¸w¨‚¾X¨—¯~·ÝW­Añz¾ýôúð®úsóÝV¸×ñN¬Ñú€¨—¨‚¾X·x
ÝsÝš¨—¯~·ÏÏ­C ­u÷ˆ©’ðš·xÏÏÏá­vú|¦ù£Ýû·©žùÇô€Ý^Ï§õt ERROR ÝrÝˆ¦§¸ãÝüÝ‘ªø
¨—¯~øT©õ­C ¸ãÝü­uTrillium õ†Ý÷ùtý×­væ{Ý­¨—¯~øT©õüœ¾]õt ERROR ÝrÝˆ­C

ðYðš·x¾Nýzæ{Ý­§íÏWøäÝ‘¦§ Script ¸× JCL ÏÏ¾¬®¸w¨‚¾X¨—¯~·­A ®h­u÷ˆ©’ðš·xÏÏ
Ïá­vú|ÝêøÒ®¾áÏ@ðà·ÝWùÇñN¬Ñú€¨—¯~¨‚¾Xð®úsóÝVÝš÷à·©ž­C ðYæoý{¾“Ý¢¨—¯~­A®h
Ïœú|õRøœ¨—¯~·­C¨—¯~··xÝs¸¢·“ûãš¬’ VWS_LOGGING ¸ã®¸w¦§¾¨ìÏÏ­C ÷à·ÝWªø
tbsudp-date- time.err­Aù„ÏÏ date ªO®¾á·©ž¦§ùtý×Ï‚ïµ­AÝà time ªO®¾á·©ž¦§
ùtý×©ô­­C ÏUÝC·ÝWÆ¾š¨‚¾X¨—¯~·ÝW¦§©‘Ý­­G

 tbsudp-021501-155606.err

22.14.6.1 ¨—¯~Ý^¶Ñ«X

 ¨—¯~«X                              ¯­¸£
 0                                   Ýù¾\©
 4                                   Žæõi­GüqÝ‘«X·©ž¾iî…æL¦k©›øœ­A¸×
                                     ­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­Ýs
                                     ù£¬ÔÝs·©æo¾ÖÏ§ü­¨—¯~­C

                                     «Ñ·ÓªdüqÝ‘«X·©ž¦ª§A­A¸×·“ûãš¬’
                                     VWS_LOGGING ¸ã®¸w¾¨ìÏU®¾á¦§¸ãÝü¬Ô
                                     Ýs·¦ª§A­C
 8                                   ø¥¬’ðÔ¸×¬’¾Ïœ¾¨«T­C «Ñø¥ÝãÏ‚¯x·¸×Ï†
                                     ¾¢ùàù£ño¾¨«T¯y¦k­C
 12                                  ­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­üz
                                     ûL FTP üsñæ¯ú§í¾Dûq÷œ©æo¾ÖøíÇD­C ·Ó
                                     ªd FTP üs«u¸×¾Dûq÷œÝW§ë­BùØ¾×¦Þ ID Ï×
                                     üqÝ‘«X­C
 16                                  ­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­æL
                                     ¦k®¾áÏ‚¯x¸×Ï§ü­·©ž­C

                                     ·ÓªdùØ¾×¦ÞÝüæL¾¨«Tñ¶vÏ×§Ø§Ñ¦ô­ªOõ_
                                     Ïw§­­C
 20                                  æL¦køäÝ‘ OS/390 JCL­A¸×­uTrillium õ†
                                     Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­üzûL FTP ñq
                                     OS/390 õRøœ¸×ù£ño·©ž©æo¾Ö¨—¯~­C

                                     ·Óªd JESLogFile ùàõ„¾X¨—¯~ðÝ]­C
 48                                  õ„Ïœù·“ûãš¬’ VWS_LOGGING ¸×æL¦k®¾á
                                     Ï‚¯x·­C «Ñø¥ÝãÏ‚¯x·¾Hù£ño÷âýà÷ˆøT­C
 56                                  æL¦køäÝ‘ Windows NT ¸× UNIX Script­A
                                     ¸×­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­
                                     üsñæ¯ú§í¾Dûq÷œ©æo¾Ö¨—¯~­C·Óªdüs«u¸×
                                     ¾Dûq÷œÝW§ë­BùØ¾×¦Þ ID Ï×üqÝ‘«X­C
 500                                 Script ¸× JCL ·ô€Ý^¨—¯~­A¸×¾¬ô€Ý^¨—
                                     ¯~­AÝì¨—¯~·¾]õt÷ˆ©’­C «Ñø¥ÝãÏ‚¯x·¾H
                                     ù£ño÷âýà÷ˆøT­CÝb OS/390 ÏW­A¾‡«Ñø¥ó\
                                     JESLogFile­C

22.14.6.2 Ï‚¯x·

ú¡­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­øäÝ‘©­A­u÷ˆ©’ðš·xÏÏÏá­vñN¸ãÝüôE¶_÷ˆøT
·xÝsÝbÏ‚¯x·ÏÏ­C÷àÏ‚¯x·ÝW§ëªø tbsudp-date-time.log­A ù„ÏÏ date ªO®¾á·©ž
¦§ùtý×Ï‚ïµ­AÝà time ªO®¾á·©ž¦§ùtý×©ô­­C ÷àÏ‚¯x·®¾á¸¢¾Nýzæ{Ý­§íÏW¾¥·“ûã
š¬’ VWS_LOGGING ¸ã®¸w¦§¾¨ìÏÏ­C ðY­uTrillium õ†Ý÷ùtý×­vùØ¾×¦Þ¸w÷qæ{Ý­ôôõQ
øäÝ‘­A®hú|õRøœ÷àÏ‚¯x·­C
  ------------------------------------------------------------------------

22.15 MQ Series ¯P­u÷ˆ©’ðš·xÏÏÏá­v¦§óÆÝX

ý{Ýb­A­u÷ˆ©’ðš·xÏÏÏá­v¾iìñzÝsù£ MQSeries øT©õÝŒÝC¦§÷ˆ©’­Aõ@ªøÏ@ðà DB2 ÷ˆ©’
©wúõýÏ¦¡­Cïœù¥§‰’Fùà®¾á DB2 ¦¡©‘ù‡¬’Ï×ù¥ñzÝbù„ÏÏÝsù£÷ˆ©’¦§ DB2 úõýÏ¦¡­CùC
Ï@ðà MQSeries øT©õüQæ›ªøÏ@ðàÝü¸wªý÷û¦§ÝrÝˆ­A ù„©éóéñz¦§üW©‘ùàð†¦RùÇô€Ý^ªø
Ï@ðàæý¦GÝC­CÝû¾~­AŽí¸¢ XML Ï†¾¢¦§ MQSeries øT©õ¾iÝsù£ªøðš·xùàú«­CùØ¾×­u÷ˆ©’
ðš·xÏÏÏá­v­Añz¾i¾Hñq MQSeries øT©õÝŒÝCÏ×­uDB2 XML ¶X¾RÏ÷Ï†¾¢Ýsù£¸w÷q
(DAD)­v·ôžÏJïyðz÷ˆ©’­C

22.15.1 ®¾á MQSeries øT©õ¦§úõýÏ¦¡

22.15.1.1 ø•¾¯ðnùD

DB2 Universal Database ¦¸¾¯ 7.2.

DB2 Warehouse Manager ¦¸¾¯ 7.2

MQSeries Ï„ï¸­CÝüÇ” MQSeries ¯íùD¦§÷âýà÷ˆøT­A«Ñø¥ó\MQSeries­C ÝüÇ”ü]¸wðš·x
ùàú«¦§÷ˆøT­A«Ñø¥ó\ùØ¾×¦Þ¸w÷q¦§ù‡¬’ÏõÝw÷ÓøØªq­C

22.15.1.2 ððùŒ

   * ú¡«s¾ðš·xùàú«÷ˆ©’©w©­Aú|Ýb¾Nýzæ{Ý­óöóûÏW«s¾÷ˆ©’©wõOÝW­C ÏœûL­Aú¡®
     ¾á MQSeries ¸M XML úõýÏ¦¡©­A­u÷ˆ©’ðš·xÏÏÏá­vøýü]÷ˆ©’©wõOÝWÏ]¸w÷q¸¢ñq
     Žíî÷óöóûÏW­AùÇñNûµ÷åùØ¾×ðš·xùàú«÷ˆ©’©wùØ¾×¦Þ ID ¸MüqÝ‘«Xùàüsñæ¾Ý­C ðY
     ôôõQõûÝù­A®hú|¸I¾s§‰’Fù¥ñz®¾áúõýÏ¦¡­CðY¾½ñ¥¦§÷š­A®hú|Æ¾šÏ@®hŽæõiøT
     ©õ­AÝàñz¾ýôúÝb§‰’FÏÏ«s¾¸×¨‹óš¾tÏ@ðà÷ˆ©’©wõOÝW­C
   * «Ñø¥ó\­u¦¸¾¯¦`úNù’ôæ­v¦§ SQL Reference øØªq­A¾Hù£ño MQ øT©õ¦§üÞÏj¦›
     ®ž­C

22.15.1.3 ®¾á MQSeries øT©õ¦§úõýÏ¦¡

®¾á MQSeries øT©õ¦§úõýÏ¦¡­G

  1. ñq­u÷ˆ©’ðš·xÏÏÏá­væ›æ­ÏÏ­A©iô}ðš·xùàú«óÐ¦ªæý§c­C
  2. ©iô}¾]õtúõýÏ¦¡¦§ðš·xùàú«­C
  3. ¾Hú’û®¾kµ„®”Ï@ÏUúõýÏ¦¡÷ˆ©’õù­AæM® ®”Ï@ÏUû‹ MQSeries øT©õ®¾á...­C

     õYú|ô}ñã MQSeries §‰’F­CõûÝùÝû§‰’F® ­Aú|Ýb­u÷ˆ©’ðš·xÏÏÏá­vÏÏ®¾áÏ@ðàús
     úõýÏ¦¡­C ú¡¨‹¸wúõýÏ¦¡® ­A®Kú|Ýsù£ MQSeries ÝŒÝC­AùÇ¾BÝb§‰’FÏÏ©éóéñz¦§
     üW©‘­A ñNùCÏ@ðàøT©õð†¦RªøÝü¸wªý÷û¦§ÝrÝˆ­C

22.15.2 ôžÏJ MQSeries øT©õ¸M XML ïyðz÷ˆ©’

22.15.2.1 ø•¾¯ðnùD

DB2 Universal Database ¦¸¾¯ 7.2.

DB2 XML Extender ¦¸¾¯ 7.2.

MQSeries Ï„ï¸­CÝüÇ” MQSeries ¯íùD¦§÷âýà÷ˆøT­A«Ñø¥ó\MQSeries­C ÝüÇ”ü]¸wðš·x
ùàú«¦§÷ˆøT­A«Ñø¥ó\ùØ¾×¦Þ¸w÷q¦§ù‡¬’ÏõÝw÷ÓøØªq­C

22.15.2.2 ððùŒ

ðY¾¬Ñ¦¡©‘Ï§ÝsÝb¾Dðn¸×¾~ùàµ„­A®hôžÏJú|¾½ñ¥­C ÝbôžÏJÏõ®e­Añz¾ýôúÏƒøÒõRøœ­u÷ˆ
©’ðš·x­vÏÏüoù€µ„ðÔ¦§¸w÷q­C

22.15.2.3 ôžÏJ MQSeries øT©õ¯P XML ïyðz÷ˆ©’

ðYðnôžÏJ MQSeries ïyðz÷ˆ©’ù­u÷ˆ©’ðš·xÏÏÏá­v­G

  1. ú€ü’ðš·x¾¬Ñ÷ˆ©’©w­G
        o ñz¾ýôú¸w÷qðš·x¾¬Ñ§í¾HÏ×ænøO¸Mñã¾×¶…ï®æ{Ý­­C
        o ñz¾ýôúû‹ DB2 XML Extender ñã¾×ðš·x¾¬Ñ§í­C÷âýà÷ˆøT­A«Ñø¥ó\ DB2
          XML Extender ¦¸¾¯ 7.2 ¦¸¾¯¦`úNù’ôæ­C
        o ®¾á XML Extender ÷ˆ©’Ýsù£¸w÷q (DAD) ·­A®¾š­u÷ˆ©’ðš·xÏÏÏá­vÝpÝ¢
          ñN XML Ï†¾¢Ï§©eû‹ªMùðš·x¦¡©‘­CùØ¾× DAD ·û‹÷ˆ©’©wñã¾× XML ôøÝX­C
          ÷âýà÷ˆøT­A«Ñø¥ó\ DB2 XML Extender ¦¸¾¯ 7.2 ¦¸¾¯¦`úNù’ôæ­C
  2. ¾Hú’û®¾kµ„®”Ï@ÏUðš·x­AæM® ®”Ï@ÏUôžÏJïyðz÷ˆ©’ -> MQSeries­Aô}ñãôžÏJïyðz
     ÷ˆ©’æ›æ­­C
  3. Ýb AMI ¦AøÔæ{Ý­Ž‘ÝÏÏ­Aµ„ÏJô€øe¸×¶^ù£øT©õ¸ãÝb¦§¦AøÔæ{Ý­¶I­C
  4. Ýb AMI ð®hŽ‘ÝÏÏ­Aµ„ÏJô€øTùtý×¾×ùàøäÝ‘õ@ú~¦§ð®h­C
  5. Ýb DAD ·©žŽ‘ÝÏÏ­Aµ„ÏJ DB2 XML Extender DAD ·¦§ÝW§ë­A¸×®”Ï@ÏUªëýÏý
     ÷û (...) ùàújïM·©ž¾H¨‹ù£­CÝû·©ž¾ýôúªO¾¯§í·©ž­C
  6. Ýbðš·x¾¬Ñ§íŽ‘ÝÏÏ­AñqýåÝX©ýMü‘ÏÏ¨‹ù£øäÝ‘ùB’J¸ãÝb¦§ðš·x¾¬Ñ§íÝW§ë­Cðš
     ·x¾¬Ñ§í¾ýôúÏwõûÝù¸w÷q­C
  7. Ýb§ä¾Ž‘ÝÏÏ­Aµ„ÏJ¾×ùà¸w÷q DAD · (Ïœõt qualifer) ÏÏ¦¡©‘ÝW§ë¦§§ä¾ÝW
     §ë­Cûwü]§ä¾ñŽ¾×ñz¾ì®e¸ã¨‹ù£ðš·x¾¬Ñ§í¦§ænÏJùØ¾×¦Þ ID­C
  8. ¨‹óš¾¬Ñ¨‹ôæ­G

     ðYðnÝûùB’JÝbøäÝ‘ïµù£¾N¾¬Ñ¦¡©‘Ï§©e­A«Ñ®”Ï@ÏUù£¾N¦¡©‘Ï§©eôˆôs­C

     ðYðnÝûùB’JÝbøäÝ‘ïµýK¾[ù¾¬Ñ¦¡©‘Ï§©e­A«Ñ®”Ï@ÏUýK¾[¦¡©‘Ï§©eôˆôs­C
  9. ®”Ï@ÏU«T¸w­C

     ñNÇ”üª­uôžÏJïyðz÷ˆ©’­væ›æ­­C

ôžÏJõ@ú~õûÝù® ­AÏUÝCðš·x¦®¾¢ú|ús¬WÝš­uðš·x­vóÐ¦ªæý§cÏÏ­C

   * ÝWªø MQSeries ¸M XML ¦§¾DÝ©øØø­C
   * ÝWªø MQSeries ¸M XML ¦§üBýzæ{õ€­C
   * ÝWªø MQSeries ¸M XML ¦§ùØ¾×¦Þ¸w÷qæ{Ý­÷sýå­C
   * ¯­¸£¸¢ DAD ·ÏÏ¸ãÝüðš·x¾¬Ñ§í¦¡©‘¦§¸w÷q­C
   * <ServiceName>.<DAD file base name>.<Warehouse target Name> step.
   * <ServiceName>.<DAD file base name> program template.

ðYðš·x¾¬Ñ¾Nýzæ{Ý­§í¯P¾¯§íóöóûÏœÝP­Añz¾ýôúšõ¢ùB’Jø¥¬’­G

  1. ¾Hú’û®¾kµ„®”Ï@ÏUùB’J­AæM® ¨‹ù£Ï§©e­C ®”Ï@ÏUÏ§©eæõøO¾¯ÏÏ¦§ø¥¬’¬Ñã­C
  2. ñN DAD ·ø¥¬’¦§ÝW§ëšõ¢ªø¯ú§íðš·x¾¬Ñ¾Nýzæ{Ý­§íÏWªêÝP DAD ·¦§ÝW§ë­C
  3. «Ñ«T¸w­uüBýzæ{õ€¨‹ôæ­v¬ÑãÏÏ¦§­u¾Nýzæ{Ý­§í­v¾]õtûwïµ¦§¾Nýzæ{Ý­§í­C

22.15.2.4 ùØ¾× MQSeries ùØ¾×¦Þ¸w÷qæ{Ý­

MQSeries ¸M XML ·xÝsæ{õ€§ëªø MQXMLXF­A ¾Ý·H¦ç¸¢ Windows NT ¸M UNIX ¦§­uDB2
÷ˆ©’ðš·xÏÏÏá­v¦¸¾¯ 7.2 ÏÏ­C ñzôžÏJ MQSeries ¸M XML ïyðz÷ˆ©’©¸ã®¾á¦§ùB’Jú|
øäÝ‘Ýû·xÝsæ{õ€­C ÏU¦¡ïyðzù„ø¥¬’­G

 ø¥¬’                                 ðÔ
 MQSeries ServiceName                 øT©õô€øeÝš¸×ñqù„ÏÏ¶^ù£¾Xùà¦§¦AøÔæ{Ý­
                                      ¶IÝW§ë­C
 MQSeries PolicyName                  ô€øTùtý×¾×ùàøäÝ‘õ@ú~¦§ð®hÝW§ë­C
 DAD ·ÝW                             DB2 XML Extender DAD ·¦§ÝW§ë
 TargetTableList                      ¾Hür¶IøØûj¦§ùB’JÏõ¾¬Ñ¦¡©‘ýMü‘
 ¨‹ôæ                                 REPLACE ¸× APPEND
 RUN ID                               ùB’J¦¸¾¯÷û«X (óA¾×øO÷)
 æ—:
      Ýû¦¡©‘ÏÏ¸ãÝüø¥¬’¦§÷ˆ©’Çç®ªªø CHARACTER­C

ðY¨‹ôæùÆÝüðÔ REPLACE­A®h·xÝsæ{õ€ú|õRøœ¾¬Ñ¦¡©‘ÏÏ¸ãÝüÝC­C ÷à·xÝsæ{õ€Ï]ú|¸I¾s
DB2 XML Extender ·xÝsæ{õ€­Aøwû‹¸ãÝüý{Ýs¦§ MQSeries øT©õÝb¾¬Ñ¦¡©‘ÏÏ¨‚ÏJ÷ˆ
©’­C

22.15.2.5 ¨—¯~Ý^¶Ñ«X

ú¡øäÝ‘ÝûùB’J©­A·xÝsæ{õ€ú|ô€Ý^¨—¯~«X SQLCODE -443 ¸M SQLSTATE 38600­C ðYðn
ôE¶_¨—¯~­A«Ñø¥ó\ÏU¦¡ÏÏ¾iî…¦§ôE¶_Ï†Ýr­C
 ¨—¯~«X                               ¯­¸£
 AMIRC=xxxxx;<Ï‚¯x·ÝW§ë>             xxxxx ªOùàÝê AMI ¬h¦§Ý^¶Ñ«X­C ÷âýà÷ˆ
                                      øT­A«Ñø¥ó\ MQSeries Ï†¾¢­C<Ï‚¯x·ÝW
                                      §ë> ®¾šÏ‚¯x·¦§Ý÷m­C
 XMLRC=xxxxx;<Ï‚¯x·ÝW§ë>             xxxxx ªOùàÝê DB2 XML Extender ¦§Ý^¶Ñ
                                      «X­C ÝüÇ”Ý^¶Ñ«X¦§¯­¸£­A«Ñø¥ó\ DB2
                                      XML Extender Ï†¾¢­C <Ï‚¯x·ÝW§ë> ®
                                      ¾šÏ‚¯x·¦§Ý÷m­C
 SQLCODE=xxxxx;<Ï‚¯x·ÝW§ë>           xxxxx ªOøäÝ‘ SQL ðnùD©ô€Ý^¦§®Dûs
                                      SQLCODE­C <Ï‚¯x·ÝW§ë> ®¾šÏ‚¯x·¦§
                                      Ý÷m­C

ðYªO¸ãÝü¨—¯~­A«Ñø¥ó\Ï‚¯x·¾Hù£ño÷âýà÷ˆøT­C

22.15.2.6 ¨—¯~Ï‚¯x·

ú¡ MQXMLXF øäÝ‘©­A­u÷ˆ©’ðš·xÏÏÏá­vñN¸ãÝüôE¶_÷ˆøT·xÝsÝbÏ‚¯x·ÏÏ­C Ï‚¯x·ÝW
§ëªø mqxf<nnnnnnnn>.log­Aù„ÏÏ <nnnnnnnn> ªOô€¯¬Ýš·xÝsæ{õ€¦§ RunID­C­u÷ˆ©’ðš
·xÏÏÏá­vú|Ýb VWS_LOGGING ·“ûãš¬’¸ã®¾š¦§¾¨ìÏÏ®¾á÷à·©ž­C ðY¾¬¸w÷qÝû·“ûã
š¬’­A®hú|Ýb¬Ô©¾¨ìÏÏ®¾áÏ‚¯x·­C

ðYðnùØ VWS_LOGGING ·“ûãš¬’¾Xý{Ýb Unix ¾ð¾x¦§·xÝsæ{õ€ÏÏ­Añz·ü÷àÝb db2start
¸R¾OÏõ®e­AùØ¾× db2set ¸R¾OùàñN VWS_LOGGING ús¬WÝš DB2ENVLIST ·“ûãš¬’ÏÏ­C
ÏUûØªø·“ûã¸R¾O«dùã­C

ûØ 6. ·“ûãš¬’¸R¾O«dùã

db2set DB2ENVLIST="AMT_DATA_PATH VWS_LOGGING"

ðYùB’JôôõQøäÝ‘­AñNõRøœÏ‚¯x·­C
  ------------------------------------------------------------------------

22.16 Microsoft OLE DB ¯P­u÷ˆ©’ýõøÒ¦AøÔ­vÏ„ï¸

ý{Ýb­A­u÷ˆ©’ðš·xÏÏÏá­v¾iìñzÝsù£ OLE DB ïœù¥¦Þ¦§÷ˆ©’­Aõ@ªøÏ@ðà DB2 ÷ˆ©’©wúõ
ýÏ¦¡­Cñz¾i¾HùØ¾×­u÷ˆ©’ðš·xÏÏÏá­vïœù¥¦§ OLE DB ¯ýõU§‰’F­A ®¾á DB2 OLE DB ¦¡
©‘ù‡¬’Ï×ù¥ñzÝbù„ÏÏÝsù£÷ˆ©’¦§ DB2 úõýÏ¦¡­C

Microsoft Data Transformation Services (DTS) ¾iìñzÝb OLE DB ùàú«¸M¾¬ÑÏõô­
¨‚ÏJ­Bôž¾XÏ×¶…ï®÷ˆ©’­A¾H®÷m÷ˆ©’ðš·x¸M÷ˆ©’ÏÏÏá­C DTS ·H Microsoft SQL
Server Ýw÷Ó­C¸ãÝü DTS õ@ú~·xÝsÝb DTS ÷ˆ©’¾]ÏÏ­Añz¾i¾HùØ¾× Microsoft OLE DB
Provider for DTS Packages ùàøäÝ‘Ï× Ýsù£ DTS ÷ˆ©’¾]­CÝ]ªøñz¾i¾HÝsù£ DTS ÷ˆ©’
¾]õ@ªø OLE DB ùàú«­A¸ã¾HÏ]¾i¾HüzûL OLE DB ¯ýõU§‰’F­A¾Hû‹ OLE DB ÷ˆ©’ùàú«¸ã
¾×¦§ªêÝPÏŠÝ­­Aû‹ DTS ÷ˆ©’¾]®¾áúõýÏ¦¡­C ú¡ñzÝbøäÝ‘ïµÝsù£úõýÏ¦¡©­Aú|øäÝ‘
DTS ÷ˆ©’¾]­AÝà¾B DTS ÷ˆ©’¾]ÏÏõ@ú~¦§¾¬Ñ¦¡©‘šÝù®¾á¦§úõýÏ¦¡­C

Ýb­u÷ˆ©’ðš·xÏÏÏá­vÏÏ®¾áúõýÏ¦¡Ïõ® ­Añz¾i¾HûüùØ¾×ù„¾Ý¾“Ý¢úõýÏ¦¡Ï@¬ÓÝaùØ¾×
¾Ý­C ùãÝp­Añz¾i¾HÝb SQL ùB’JÏÏñN DB2 ¦¡©‘¯P OLE DB ùàú«æýÝXÝbÏ@ø_­C ú¡ñzùØ
¾× SQL ùB’JÏÏ®¾á¦§úõýÏ¦¡©­Aú|¸I¾s DTS ïœù¥¦ÞùÇøäÝ‘ DTS ÷ˆ©’¾]­C

ün‚¯íùD­G

   * DB2 Universal Database for Windows NT ¦¸¾¯ 7.2­AÝpðš·x¾¬Ñ§í÷ˆ©’©w
   * DB2 Warehouse Manager ¦¸¾¯ 7.2
   * ðYðš·x¾¬Ñ§í÷ˆ©’©wÏwÝb¦¸¾¯ 7.2 Ïõ®e®¾á­Añz¾ýôúÝbÝw÷Ó DB2 UDB for
     Windows NT ¦¸¾¯ 7.2 Ïõ® ­AøäÝ‘ db2updv7 ¸R¾O
   * ú¡«s¾ðš·xùàú«÷ˆ©’©w©­Aú|Ýbðš·x¾Nýzæ{Ý­§íÏW«s¾÷ˆ©’©wõOÝW­C ÏœûL­Aú¡
     ñãøÒ§‰’F©­A­u÷ˆ©’ðš·xÏÏÏá­vú|øýü]÷ˆ©’©wõOÝWÏ]¸w÷qÝbñqŽíÏuõ@î÷ÏW­A ùÇ
     ñNûµ÷åùØ¾×ðš·xùàú«÷ˆ©’©wùØ¾×¦Þ ID ¸MüqÝ‘«Xùàüsñæ¾Ý­C ðYüsñæÝù¾\­A®h§‰
     ’Fú|ñãøÒù¥ñz®¾áúõýÏ¦¡­CðYüsñæ¾½ñ¥­A ®hú|Æ¾šÏ@®hŽæõiøT©õ­AÝàñz¾ýôúÝb
     §‰’FÏÏ«s¾¸×¨‹óš¾tÏ@ðà÷ˆ©’©wõOÝW­C
   * ðYðnÇ¥õO DTS ÷ˆ©’¾]ÏÏîS¸w¦§¦¡©‘­Añz¾ýôúÝb®¾á¾¬Ñ¦¡©‘¦§ DataPumpTask
     Ïõ­uÏuõ@ªyæ{Ï§©e­væ›æ­¦§­u¨‹ôæ­v¬ÑãÏÏ­A¨‹ù£ DSO ÝCôøïœù¥¦ÞÏŽ¨‹©­C ðY
     ô}ñãÝhð® DSO ÝCôøïœù¥¦ÞŽí¸Ò­A®hôÔú|ùØ¾×ýŽÏ@ðà¨‹ù£¦§ùB’Jæý¦G­C ú¡¨‹ù£ªY
     úõýÏ¦¡® ­Aú|ô€Ý^ù„¾¬Ñ¦¡©‘¦§ÝCôø­AÝì¸¨ýÏñzÝb® Ž•ùB’JÏÏ®¾á¦§ù„¾Ý¸ãÝüÝC
     ôø­C
   * ú¡û‹§‰’F¨‚ÏJ¦¡©‘ÝW§ë©­A«ÑùØ¾×ùB’JÝW§ë­A ù„Æ¾š¸¢÷àõ@ú~¦§­uÏuõ@ªyæ{Ï§
     ©e­væõøO¾¯Ïõ­u¨‹ôæ­vðôðñÏÏ­C
   * DTS ÷ˆ©’¾]üsñæÝrÝˆ¯P dtsrun ¸R¾O¦§¯y¦kªêÝP­C

22.16.1 ®¾á OLE DB ¦¡©‘ù‡¬’¦§úõýÏ¦¡

®¾á OLE DB ¦¡©‘ù‡¬’¦§úõýÏ¦¡­G

  1. ñq­u÷ˆ©’ðš·xÏÏÏá­væ›æ­ÏÏ­A©iô}ðš·xùàú«óÐ¦ªæý§c­C
  2. ©iô}¾]õtúõýÏ¦¡¦§ðš·xùàú«­C
  3. ¾Hú’û®¾kµ„®”Ï@ÏUúõýÏ¦¡÷ˆ©’õù­AæM® ®”Ï@ÏUû‹ OLE DB ¦¡©‘ù‡¬’®¾á­C

     õYú|ô}ñã OLE DB ¯ýõU§‰’F­C Ýû§‰’Fú|üvùBÏèóñzõûÝùÝbðš·xùàú«÷ˆ©’©wÏÏ®
     ¾áúsúõýÏ¦¡¦§õ@ú~­C

22.16.2 ®¾á DTS ÷ˆ©’¾]¦§úõýÏ¦¡

ðYðnªø DTS ÷ˆ©’¾]®¾áúõýÏ¦¡­G

  1. ñq­u÷ˆ©’ðš·xÏÏÏá­væ›æ­ÏÏ­A©iô}ðš·xùàú«óÐ¦ªæý§c­C
  2. ©iô}¾]õtúõýÏ¦¡¦§ðš·xùàú«­C
  3. ¾Hú’û®¾kµ„®”Ï@ÏUúõýÏ¦¡÷ˆ©’õù­AæM® ®”Ï@ÏU Microsoft OLE DB Provider for
     DTS Packages­C

     õYú|ô}ñã OLE DB ¯ýõU§‰’F­CÝû§‰’Fú|üvùBÏèóñzõûÝùÝbðš·xùàú«÷ˆ©’©wÏÏ®¾á
     úsúõýÏ¦¡¦§õ@ú~­C

ÝüÇ” DTS ¦§÷âýà÷ˆøT­A«Ñø¥ó\ Microsoft Platform SDK 2000 Ï†¾¢­A ù„Ï§©eªøÝpÝ¢
®÷müsñæ DTS ïœù¥¦Þ©§‰’F¯íðn¦§ïœù¥¦ÞÝrÝˆÏõ÷âýà¯­¸£­C
  ------------------------------------------------------------------------

22.17 ¬Wôq COMMIT úføt replace ùØ¾×

Ýb¾·‚Çç®ªªø Replace ¦§ùB’JÏÏ­AøáÝüï­ÏJús÷ˆ©’©­AÏ~ú|ùØ¾×¬Wôq«T¸w­C Ýbü‘Ï@
«T¸w«dü•Ï§­Að¸l÷ˆ©’ú|üQõRøœ­CðYñz¯íðnõRøœ÷ˆ©’ÝàÏœýœ¾ÖÏ‚¯xøO¨ì­A «ÑÝbøäÝ‘ùÆ
Ýü¦ç¾[¾·‚Çç®ª¦§ SQL ùB’JÏõ®e­AøäÝ‘÷ÏJ¦¾å·©ž¦§ùB’J­C

  ------------------------------------------------------------------------

22.18 Ï÷¾¢øl¶š÷ˆ©’·ÝW

­u÷ˆ©’ðš·xÏÏÏá­vÝb Windows NT ÏW¬ô¬güoù€·©ž­G

AGNTnnnn.Log ¾]õtøl¶š÷ˆøT­Cnnnn ªøðš·x¾Nýzæ{Ý­¦§¬’Ýræ{õ€ ID­A ©éóéõ@ú~ùt
ý×­A¾Ý¾i¾HªO 4 ¸× 5 Ý¬’­C

AGNTnnnn.Set ¾]õt¾Nýzæ{Ý­¦§·“ûãü]¸w­Cnnnn ªøðš·x¾Nýzæ{Ý­¦§¬’Ýræ{õ€ ID­A©éóé
õ@ú~ùtý×­A¾Ý¾i¾HªO 4 ¸× 5 Ý¬’­C

ûwü]¾¨ìªø x:\program files\sqllib\logging­A ù„ÏÏ x ªOÝw÷Ó DB2 ¸ãÝb¦§§Ø§Ñ
óö­C
  ------------------------------------------------------------------------

22.19 AIX Ï× Solaris õ@ú~·“ûãÏW Sybase ùàú«¯íðn¦§ OPEN CLIENT

ÝbýŽ 3 üû­uü]÷mðš·xùàú«­v­AÝb AIX ÏŠðñ¦§¦¡©‘ 3­uAIX ÏWÏ„ï¸¦§÷ˆ©’ùàú«¦§üsñæ
¯íùD­v¾HÏ× Solaris õ@ú~·“ûãÏŠðñ¦§¦¡©‘ 4­uSolaris õ@ú~·“ûãÏWÏ„ï¸¦§÷ˆ©’ùàú«¦§
üsñæ¯íùD­vÏÏ­A­uÝpÝ¢üsñæ­G­v¦«Ž‘ÏÏ¦§ Sybase æn¨ì·ü÷à¾]õt¾tÏ@ðàÇB¾~¦§ùB’J­C
ù„¾ÝùB’JÆ¾šÝb¾HÏU¦§ùB’J 3 ÏÏ­C

3. Ýw÷Ó OPEN CLIENT

«Ñ¦`úN­GÝb Windows NT ¸× Windows 2000 ¾ð¾xÏWüsñæ Sybase ùàú«­A ¯íðn OPEN
CLIENT­C
  ------------------------------------------------------------------------

22.20 «dùãæn¨ìõ¢¾¨

Ýb Data Warehouse Center §èýzÏƒ¾UÏ@©¥¦§­uýŽ 3 üû ü]¸wðš·xùàú«­vÏÏÇ”¸¢
Driver Ží¸Ò¦§÷“©|ùÇÏœ¾¨«T­CÏUÝC÷“©|Ï~ªO¾¨«T¦§­G

ûØ 6

Driver=/home/db2_07_01/3.6/odbc/lib/ivinf12.so


ûØ 8

 Driver=/home/db2_07_01/3.6/odbc/lib/ivsyb1112.so

ûØ 10

Driver=/home/db2_07_01/3.6/lib/ivor814.so

ûØ 11

 Driver=/home/db2_07_01/3.6/odbc/lib/ivmsss14.so

  ------------------------------------------------------------------------

22.21 ýŽ 3 üû ü]¸wðš·xùàú«

22.21.1 û‹ªM Microsoft Access ÏÏ¦§ü’õ¥¨ìŽ‘ÝÝšðš·xùàú«

Microsoft Access ÷ˆ©’©w¦§ü’õ¥¨ìŽ‘ÝÝb÷ˆ©’ðš·xÏÏÏáÏÏªO¾HôWûL 1GB ¦«Ž‘ÏjÏp¦§
LONG VARCHAR ÷ˆ©’Çç®ªùà¦¡¾š­C ðYðnÏ„ï¸ûˆ¯é¦§ùtý×ª[§c­A÷ˆ©’ðš·xÏÏÏáú|§I¶_ôW
ûL 128 KB ¦§ðÔ­C ðYðnµžõKÝbðš·xùàú«ÏÏ§I¶_ü’õ¥¨ìŽ‘ÝðÔ­A «ÑñzÝbùB’JÏÏùØ¾×¦¡
©‘Ïõ®e­A¾ìñNñæÝªü’õ¥¨ìŽ‘Ý÷ˆ©’¦§¦«Ž‘÷ˆ©’Çç®ªñq LONG VARCHAR šõ¢ªø CLOB­C
Ýp¦GñzùSÝüšõ¢¦«Ž‘¦§÷ˆ©’Çç®ª­A¾“Ý¢Ïj¸¢ 128 KB ¦§ðÔüœú|üQ§I¶_­C

OS/390 Ï× OS/400 ¯íðnÏ„ï¸ CLOB ÷ˆ©’Çç®ª¦§ DRDA­C OS/390 ñq DB2 ¦¸¾¯ 6 ô}¸l
Ï„ï¸ CLOB ÷ˆ©’Çç®ª­C OS/400 ñq¦¸¾¯ 4­BùÆÝü DB FixPak 4 ¦§¦¸Ý÷ 4 ¸×õ¢ús¦¸¾¯
(PTF SF99104) ô}¸lÏ„ï¸ CLOB ÷ˆ©’Çç®ª­C ðYªO OS/400­AÝw÷Ó§Ø§Ñ¦¸¾¯ 4­A1999 Ý~
2 Ï‰ ¦§¦¸Ý÷ 4­AÏ]Ï„ï¸ CLOB ÷ˆ©’Çç®ª­C
  ------------------------------------------------------------------------

22.22 ýŽ 10 üû §–@ðš·x÷ˆ©’©w

22.22.1 Çæý¦¡©‘Ýš DB2 UDB RUNSTATS æ{Ý­¦§ùB’JÝ÷Çç®ª

RUNSTATS æ{Ý­¦§ùB’JÝ÷Çç®ªÝêðš·x¾¬Ñ¦ù£ùÇ¬gÏJðš·x¾¬Ñ­CÝb¸w÷qÝûùB’J¦§ðÔÏõ
®e­A «Ñ¾ìñN¾¬ÑÇæýù­uæ{õ€¬ã®ª­væ›æ­¦§ùB’JÝ÷Çç®ª­C
  ------------------------------------------------------------------------

22.23 ûwü]ðš·xññùŒ÷ˆ©’©w

Ýb Windows NT ¸× Windows 2000 Ýw÷Ó DB2 ¦§ïµô­­A Ýp¦GÝb Windows NT ùtý×æn¨ì
ÏÏùSÝüÇ¥õOõ@¾×ÏÏ¦§ðš·xññùŒ÷ˆ©’©w­A DB2 ú|Ýb÷ˆ©’ðš·xÏÏÏá®¾á¸Mø_¸lü]¸wûwü]ðš
·xññùŒ÷ˆ©’©w­CõQ¾×ø_¸lü]¸wæ{õ€­A÷ˆ©’ðš·xÏÏÏá®¾áññùŒ¦¡©‘­A¾H·xÝs÷ˆ©’ðš·xÏÏ
Ïáïyðz÷ˆ©’­C

ûwü]ðš·xññùŒ÷ˆ©’©w¦§ÝW§ëªø DWCTRLDB­CænÏJ©­A÷ˆ©’ðš·xÏÏÏá®¸w DWCTRLDB ªøðš
·xññùŒ÷ˆ©’©wûwü]ðÔ­Cñìªdªíðš·xññùŒ÷ˆ©’©w¦§ÝW§ë­A®”Ï@ÏU÷ˆ©’ðš·xÏÏÏá­uænÏJ­v
æ›æ­¦§ôiô¾®”ôs­C
  ------------------------------------------------------------------------

22.24 ðš·xññùŒ÷ˆ©’©w§èýzæ›æ­

ðš·xññùŒ÷ˆ©’©w§èýzæ›æ­Ýb Windows NT ¸× Windows 2000 Ýw÷Óù†®ª DB2 ïµô­ôiÝ‘Ýw
÷Ó­CõQ¾×Ýûæ›æ­šõ¢õ@¾×ÏÏ¦§ðš·xññùŒ÷ˆ©’©w­B®¾á¸Mø_¸lü]¸wús®ðš·xññùŒ÷ˆ©’©w
­Býó¶… IBM Visualðš·x¸ãùØ¾×¦§ðš·xññùŒ÷ˆ©’©w­CÏUÝCøQ«žÏWðz¦§ª­øÒ­C

ùØ¾×ðš·xññùŒ÷ˆ©’©w§èýzæ›æ­®eøñÏŒðš·xÝ›¦Aóû­C
  ------------------------------------------------------------------------

22.25 šõ¢õ@¾×ÏÏðš·xññùŒ÷ˆ©’©w

Ýp¦GñzðnùØ¾×õ@¾×ÏÏ¦§ðš·xññùŒ÷ˆ©’©w¾H¾~¦§ðš·xññùŒ÷ˆ©’©w­A«ÑùØ¾×ðš·xññùŒ÷ˆ©’
©w§èýzæ›æ­ñN÷à÷ˆ©’©wænøOªøõ@¾×ÏÏ¦§ññùŒ÷ˆ©’©w­CænÏJ÷ˆ©’ðš·xÏÏÏá©­A®¸wõ@¾×
ÏÏðš·xññùŒ÷ˆ©’©w¾H¾~¦§ÝW§ë­Añzú|ñoù¨—¯~¦§øT©õ­A¯­¸£ñz¸ã®¸w¦§÷ˆ©’©w¸Mðš·x
Ý›¦Aóû¸ã®¸w¦§÷ˆ©’©wÏœªêýÝX­C

ænøO÷ˆ©’©w­G

  1. ®”Ï@ÏUô}¸l --> æ{Ý­ôø --> IBM DB2 --> ðš·xññùŒ÷ˆ©’©w
  2. Ýbús®ññùŒ÷ˆ©’©wŽ‘ÝÏÏ­A¨‚ÏJñzðnùØ¾×¦§ññùŒ÷ˆ©’©wÏõÝW§ë­C
  3. Ýb§ä¾Ž‘ÝÏÏ­A¨‚ÏJ÷ˆ©’©w¯íðn¦§§ä¾ÝW§ë­C
  4. ÝbùØ¾×¦Þ ID Ž‘ÝÏÏ­A¨‚ÏJÝsù£÷ˆ©’©w¸ã¯íðn¦§ùØ¾×¦Þ ID ÝW§ë­C
  5. ÝbüqÝ‘«XŽ‘ÝÏÏ­A¨‚ÏJùØ¾×¦Þ ID ¦§üqÝ‘«X­C
  6. Ýb‡ÇãñK«XŽ‘ÝÏÏ­AÝAÏ@Ý÷¨‚ÏJüqÝ‘«X­C
  7. ®”Ï@ÏU«T¸w­C

     æ›æ­®O®—ô}ñã­CøT©õŽ‘ÝÆ¾šæn¨ìæ{õ€¦§¦ª§AøT©õ­C
  8. æ{õ€õûÝù® ­AÇ”üªæ›æ­­C

  ------------------------------------------------------------------------

22.26 ®¾á¸Mø_¸lü]¸wðš·xññùŒ÷ˆ©’©w

Ýp¦Gñzðn®¾áûwü]ðÔ¾H¾~¦§ðš·xññùŒ÷ˆ©’©w­A«ÑÝbÝw÷Óæ{õ€ïµô­®¾á­A¸×ªOÝbðš·xññ
ùŒ÷ˆ©’©w§èýzæ›æ­ôiÝ‘Ýw÷ÓÏõ® ®¾á­CùØ¾×Ýw÷Óæ{õ€Ýb¯Pðš·xÝ›¦AóûªêÝP¸MÏœÝP¦§Ïu
õ@î÷ÏW®¾á÷ˆ©’©w­C

ñìšõ¢Ýw÷Óïµô­¸ã®¾áðš·xññùŒ÷ˆ©’©wÝW§ë­A«ÑøäÝ‘ÝêðqÝw÷Ó­AùÇšõ¢¸w÷q¾¯§íðš·x
ññùŒ÷ˆ©’©wæ›æ­Ï§¦§ÝW§ë­CÝw÷Óæ{õ€¾Hñz¸ã®¸w¦§ÝW§ë®¾á÷ˆ©’©w­Aø_¸lü]¸w÷ˆ©’ðš
·xÏÏÏá¸ãùØ¾×¦§÷ˆ©’©w­AænøO÷ˆ©’©wªøõ@¾×ÏÏðš·xññùŒ÷ˆ©’©w­C

ñìÝbÏwÝw÷Óðš·xÝ›¦Aóû¾H¾~¦§Ïuõ@î÷®¾áðš·xññùŒ÷ˆ©’©w­A«ÑÝbÝêðqÝw÷Óïµô­­A¨‹ù£
ðš·x¾¯§íññùŒ÷ˆ©’©w­CÝw÷Óæ{õ€ñN®¾á÷à÷ˆ©’©w­CÝw÷ÓõûÝù® ­A«Ñ®”úà22.25, šõ¢õ@
¾×ÏÏðš·xññùŒ÷ˆ©’©wÏ§¦§ùB’J­AÝbðš·xÝ›¦AóûÏuõ@î÷ùØ¾×ðš·xññùŒ÷ˆ©’©w§èýzæ›æ­­C
Ýw÷Óïµô­­A«Ñ®¸w÷ˆ©’©wÝW§ë­C ø_¸lü]¸w÷ˆ©’ðš·xÏÏÏá¸ãùØ¾×¦§÷ˆ©’©w­AænøO÷à÷ˆ©’
©wªøõ@¾×ÏÏðš·xññùŒ÷ˆ©’©w­C

ñìÝbÝw÷Óæ{õ€® ®¾á¸Mø_¸lü]¸wðš·xññùŒ÷ˆ©’©w­A«Ñ¸¢ðš·xÝ›¦AóûÏuõ@î÷ùØ¾×ðš·xññ
ùŒ÷ˆ©’©w§èýzæ›æ­­CÝp¦Gús®¦§ðš·xññùŒ÷ˆ©’©wÏœÝbðš·xÝ›¦AóûÏuõ@î÷­A®h¾ýôú¾ìÝb
ðš·xÝ›¦AóûÏuõ@î÷®¾á÷à÷ˆ©’©wùÇñN¾Ý«sÏJ¾¨ì­C¨¡ï` 22.25, šõ¢õ@¾×ÏÏðš·xññùŒ
÷ˆ©’©wÏ§¦§ùB’J­C Ýw÷Óïµô­­A«Ñ®¸w÷ˆ©’©wÝW§ë­C

ænÏJ÷ˆ©’ðš·xÏÏÏá©­A®”Ï@ÏUôiô¾®”ôs­AùÇ¨‚ÏJõ@¾×ÏÏðš·xññùŒ÷ˆ©’©wÝW§ë­C
  ------------------------------------------------------------------------

22.27 ®¾á¦¸¾¯¦§ SQL ùB’J

Ýb®¾á¦¸¾¯¦§ SQL ùB’J©­Aø•¸¢ùØ¾×ñ­¦p­A ñz¾iî…ú|Ýã¬{Ýb¦¸¾¯¦«Ž‘®¾á®DøáÏ@¦§
îµÏè­A¾H¬WôiõRøœ¦¸¾¯¦§©Žî…­Cû‹¸¢Ïjôqðš·x¦¡©‘«ÑÝã¬{ùüoÏ@¶I­AÝ]ªøï­ÏJÏ™ôq¦§
ÝC¬’ú|¬vTùï­ÏJ¦§©Žî…­C
  ------------------------------------------------------------------------

22.28 Ýb­uæ{õ€¬ã®ª­væ›æ­ÏÏ­Ašõ¢ùàú«¸×¾¬Ñ

Ýb­uæ{õ€¬ã®ª­væ›æ­ÏÏ­AÝp¦Gšõ¢ÏFùàú«¸×¾¬Ñ­AñNú|ÝêøÒ·xÝs¸ãøæ¦§šõ¢­CÝp¦Gñz
øæÏF¾“Ý¢ù„¾Ý¦§šõ¢(Ï¤Ýpús¬WùB’J)­Añz¾ýôú¸£«TÝa·xÝsšõ¢­A¾HûFù¾ÇÏ[šõ¢¦§¾
¦§­CðYðn·xÝsšõ¢­A«Ñ®”Ï@ÏU "æ{õ€ --> ·xÝs"­C
  ------------------------------------------------------------------------

22.29 ús¬W¯­¸£Ýš­u÷ˆ©’ðš·xÏÏÏá­v¦®¾¢

Ýb÷ˆ©’ðš·xÏÏÏáÏÏ­A¸¢æõøO¾¯¦§¯­¸£Ž‘Ý­Añz¾i¾H®¸wÝhûF 254 ðàÝrÏ÷­CÝûüÞÏjðÔù£
¾NÏF«uÏW¯­¸£ÏÏ¸ã®¸w¦§üÞÏj¦›®ž­C
  ------------------------------------------------------------------------

22.30 øäÝ‘­u«dùãÏ§©e­v

   * ñzæL¦kÝù¾\ÝaøäÝ‘Ýbî¶Ï†Ýr·ùàú«ùØ¾× AS/400 ¾Nýzæ{Ý­¦§­u«dùãÏ§©e­vðnùD­C
     µ”æMñz¾i¾H®¾áî¶Ï†Ýr·ùàú«­A ùÇ¾›ûØùØ¾× AS/400 ¾Nýzæ{Ý­æo¾X«dùãÏ§©eðn
     ùD­AÝìªOüoôæðnùDú|¾½ñ¥­C
   * Ýbû‹æ{õ€¬ã®ªýœ¾ÖóûÏÏ¦§ðš·x¾¬ÑøäÝ‘­u«dùãÏ§©e­v©­A¾iî…ú|Ýªù¨—¯~øT©õ­C
     üoðà¨—¯~¯Pðš·xùàú«­Bðš·x¾¬Ñ­Bæ{õ€ùB’J¦§¾Nýzæ{Ý­§íÏõ¾i¾×¸ÒÝüÇ”­C Ï@ðà
     ùB’J¾i¾×¦§¾Nýzæ{Ý­§íÏõÝC¦¡­AªOðš·xùàú« IR ¾Nýzæ{Ý­§í­Bðš·x¾¬Ñ IR ¾Nýz
     æ{Ý­§í­BÝûîSõOùB’J¾i¾×¦§¾Nýzæ{Ý­§í¾‘ôø® ¸ãñoù¦§æý¦G (¸ã®¦§ùB’Jªø¾Nýz
     æ{Ý­§íÏ§©eæõøO¾¯¦§üÞ® Ï@ðô¸ã¨‹¦§ùB’J)­CùãÝp­A·Óæ›øäÝ‘ FTP Put æ{Ý­
     (VWPRCPY) ¦§æ{õ€¦§­u«dùãÏ§©e­v­C¾Nýzæ{Ý­§í¸w÷q¦§¾Nýzæ{Ý­§í¨‹ù£æ{õ€ÏÏ¸ã
     ùØ¾×¦§ùB’J­Cú¡ñzû‹¾¬Ñ·øäÝ‘­u«dùãÏ§©e­v­Aüqñ`ùØ¾×¨‹ù£ÝC¾šÏÏ¦§ýŽÏ@ðà¾N
     ýzæ{Ý­§í­CÝìªO­A÷ˆ©’©w§–@õ@ú~ú|¬vT¾Nýzæ{Ý­§íÝC¾š¦§Ý÷õ€­CÝp¦G¨‹ù£¦§¾N
     ýzæ{Ý­§í¯Pùàú«¸×¾¬Ñ·¦§ùtý×ÏœÝP­A«dùãÏ§©eñN¾½ñ¥­C

  ------------------------------------------------------------------------

22.31 «s¨Š Create DDL SQL üîðzÝ­

¸¢ô}æo¬ãÝ­ÏU­A«s¨Š¾¬Ñ¦¡©‘¦§ Create DDL SQL üîðzÝ­©­A ú|ªíùÏUÝC¾OÏHøgïb¦§
øT©õ­G" Create DDL SQL üîðzÝ­¦§¾“Ý¢šõ¢ñNÏœÏØªMÝb¦¡©‘¸w÷q¸×ûˆ¯é¦§¦¡©‘ÏW­Cðn
Ž~Ž•ôš­H"

šõ¢ú|ÏØªMÝbûˆ¯éûˆ‚¦§¦¡©‘ÏW­C¸¨ýÏ÷àøT©õ­AŽ~Ž•šõ¢ Create DDL üîðzÝ­­C

Ýbô}æo¬ãÝ­ùB’JÏÏ­AÝûøT©õ¦§ðž¾¨¦¸·üÝpÏU¸ã¾š­G"Create DDL SQL üîðzÝ­¦§¾“Ý¢š
õ¢ñNÏœÏØªMÝb¦¡©‘¸w÷qÏÏ­CðnŽ~Ž•ôš­H"

û‹¸¢ï£÷å¸×¾Öýœ¬ãÝ­ÏÏ¦§ùB’J­AÝûøT©õªO¾¨«T¦§­CñNùB’JÏîùï£÷å¬ãÝ­©­Aú|®¾á
ûˆ‚¦§¾¬Ñ¦¡©‘­C÷ˆ©’ðš·xÏÏÏáÏœú|šõ¢÷à¦¡©‘­C
  ------------------------------------------------------------------------

22.32 ýó¶… Visual Warehouse øàú~·Óæ›

Ýp¦GðnñN Visual Warehouse ïyðz÷ˆ©’ÝPùBÏ’Ïõøàú~·Óæ›ýó¶…Ýš÷ˆ©’ðš·xÏÏÏá©­A ñz
¾iÝbýó¶…ðš·xññùŒ÷ˆ©’©wÏõ®eñNøàú~·Óæ›ïœ¦@Ýš­u¾Öýœ­v¦ª§A­CÝp¦Gøàú~·Óæ›Ýb­u¾Ö
ýœ­v¦ª§A­A ¾Ý¦§ñ’æ{ïNú|ýó¶…Ýš÷ˆ©’ðš·xÏÏÏá­CÝp¦Gøàú~·Óæ›ÏœÝb­u¾Öýœ­v¦ª§A­A
¾ÝïNú|ýó¶…Ýš­uï£÷å­v¦ª§A­AÝàùSÝüñ’æ{­CÏœ¾iñNýó¶…ùB’Jïœ¦@Ýš­u¾Öýœ­v¦ª§A­Cñz
¾ýôú¾ìÝb÷ˆ©’ðš·xÏÏÏáÝAÝ÷®¾áÝPùBÏ’ùB’J­A æM® õRøœýó¶…ùB’J­C
  ------------------------------------------------------------------------

22.33 ®¾á¾¬Ñ¦¡©‘Ï×¾Dðnµ„

÷ˆ©’ðš·xÏÏÏá®¾áÝûùB’J¦§¾¬Ñ¦¡©‘® ­AùÇùSÝüýœ¾ÖÝû¾¬Ñ¦¡©‘¦§¾Dðnµ„­CªYù€¶…ï®
æ{Ý­­A Ýp Moving Average­Aú|ùØ¾×¸ãýœ¾Ö¦§¦¡©‘ùàøæªøùàú«¦¡©‘­Aù„ùàú«¦¡©‘Ï]ôú
ðn¾Dðnµ„­CÝbñzùØ¾×¾H¶…ï®æ{Ý­ýœ¾Ö¦§¦¡©‘Ïõ®e­A «Ñ¾ìÝb DB2 ññùŒÏÏÏá¦§¦¡©‘ÏW®”
ú’û®¾kµ„ùà¸w÷qÝû¦¡©‘¦§¾Dðnµ„­A æM® ®”Ï@ÏUšõ¢­C
  ------------------------------------------------------------------------

22.34 ùØ¾× Merant ODBC XøÒæ{Ý­

Ýp¦GðnÝsù£ Windows NT ÏW¦§ Microsoft SQL Server­A «ÑùØ¾× Merant ODBC XøÒæ{
Ý­ùà«T¯{ù„ùtý×÷“©|ªOõ_¾]õt sqllib\odbc32 ¾¨ì­C
  ------------------------------------------------------------------------

22.35 ús® ODBC XøÒæ{Ý­

Ýp¦GñzñNùØ¾×ÏwÇæýÝšÝsù£ Merant ODBC ùàú«¦§÷ˆ©’ðš·xÏÏÏá AIX ¸× Sun ¾Nýzæ{
Ý­­AùÇ¾BñNÝsù£ DB2 ÷ˆ©’©w­A «Ñšõ¢ .odbc.ini ·©žÏÏ DB2 ùàú«øØªq¦§
­uDriver=­vŽí¸ÒðÔ­AÝpÏU¸ã¾š­G

AIX­GXøÒæ{Ý­ÝW§ëªø /usr/lpp/db2_07_01/lib/db2_36.o

AIX ¦§«dùã ODBC ùàú«æn¨ì­G

[SAMPLE] Driver=/usr/lpp/db2_07_01/lib/db2_36.o
Description=DB2 ODBC Database
Database=SAMPLE

Sun­GXøÒæ{Ý­ÝW§ëªø /opt/IBMdb2/V7.1/lib/libdb2_36.so

Sun ¦§«dùã ODBC ùàú«æn¨ì­G

[SAMPLE] Driver=/opt/IBMdb2/V7.1/lib/libdb2_36.so
Description=DB2 ODBC Database
Database=SAMPLE

  ------------------------------------------------------------------------

22.36 ¸w÷q OS/2 ÷ˆ©’©wÏÏ¦§ðš·xùàú«¸×¾¬Ñ

¸w÷q OS/2 ÷ˆ©’©w¦§ðš·xùàú«¸×ðš·x¾¬Ñ® ­A «Ñ¾×Ïj¬gÝr¾·µ„ÏJ÷ˆ©’©wÝW§ë­C
  ------------------------------------------------------------------------

22.37 §Òúçðš·xññùŒ÷ˆ©’©w¦§¦ª§A

DB2 ññùŒÏÏÏá¸×¸R¾OÝ‘üBýzóû¾iî…ú|®¾Xðš·xññùŒ÷ˆ©’©wªOõ_ÝüÏœÏ@ðP¦§¦ª§A­CÝû¦ª
§A®¾Xðš·xÝ›¦AóûùSÝüæo¾X¾Ýø_¸l¦§ñãøÒùðš·xÏ‚¯xóû­C
  ------------------------------------------------------------------------

22.38 ùØ¾× SQL ¯ýõUæ{Ý­¯P TBC_MD «dùã÷ˆ©’©w

Ýb TBC_MD ÷ˆ©’©wÏÏ¸ãõt¦§÷ˆ©’ðš·x«dùãÏÏ­AñzÏœ¾i¾HùØ¾× SQL ¯ýõUæ{Ý­ùàšõ¢
Select Scenario SQL ùB’JÏÏ¦§ SQL­A Ý]ªø SQL ªOÝb SQL ¯ýõUæ{Ý­ýœ¾ÖÏõ® «s¨Š
¦§­C
  ------------------------------------------------------------------------

22.39 ùØ¾× FormatDate ù‡¬’

ðYðnùØ¾× FormatDate ù‡¬’­A«ÑÝb­uÏ§©e­væõøO¾¯¦§­uSQL üîðzÝ­­vðôÏW­A®”Ï@ÏU®
÷m SQL­AùàôiÝ‘ SQL ùB’J­C

FormatDate ù‡¬’¦§¨‚¾XªO÷ˆ©’Çç®ª varchar(255)­C ñzÏœ¾iñq Function
Parameters-FormatData ðôðñÏÏ¦§§ÇçÝC¾š­A ¨‹ù£Ï‚ïµ­B©ô­­B¸×Ï‚ïµ/©ô­ùàšõ¢
÷ˆ©’­C
  ------------------------------------------------------------------------

22.40 šõ¢¯yù¾ü]¸w

Ýb AIX ¸M Solaris õ@ú~·“ûãÏÏ­A Ýw÷Óæ{õ€ú|ªø÷ˆøT®ª¨ìü]¸wðnÏ«õG¦§¯yù¾­A ùÇôž
¾Xù OLAP óÆÝXÝ›¦Aóû­CÝp¦GñzúQÝbÝw÷Ó©ùØ¾×üoù€¯yù¾ù‡¬’­A «Ñ¨‚ÏJÏUÝC®¾O (Ï@
óÆÝ‘) ¾H®K®¾áünÇæý­C

Ýb AIX

      /usr/bin/ln -sf  /usr/lpp/db2_07_01/msg/locale/flgnxolv.str


      /usr/lpp/db2_07_01/bin/flgnxolv.str

     ¯yù¾·“ûã
          ¯yù¾¦§¯yù¾·“ûã (locale) ÝW§ë¦§©‘Ý­ªø xx_yy

Ýb Solaris õ@ú~·“ûã

     /usr/bin/ln -sf  /opt/IBMdb2/V7.1/msg/locale/flgnxolv.str

     /opt/IBMdb2/V7.1/bin/flgnxolv.str

     ¯yù¾·“ûã
          ¯yù¾¦§¯yù¾·“ûã (locale) ÝW§ë¦§©‘Ý­ªø xx_yy

  ------------------------------------------------------------------------

22.41 ùØ¾×­uýœ¾Öµ„ðÔ¦¡©‘­v¶…ï®æ{Ý­

ú¡ñzùØ¾×­uýœ¾Öµ„ðÔ¦¡©‘­v¶…ï®æ{Ý­¦§õ¢úsµ„ðÔ¦«Ž‘¦§ðÔ¨‹ôæ©­A ¶…ï®æ{Ý­ôÔõ¢ús¦¡
©‘ÏÏùSÝüðÔ¦§ÝC­C(Ï]ïNªO­AðÔªø NULL)­Cú¡ñzÝb¦¡©‘ÏÏï­ÏJù„¾ÝóŒÝC©­A øœ®Dñzð®
úsøäÝ‘¶…ï®æ{Ý­­Aõ_®hµ„ðÔªø¦ðÔ­C

ªøÏFµžõKÝûøíÇD­A«ÑøäÝ‘ÏUÝCøÒõ@­G

   * Ýbø_¸løäÝ‘¶…ï®æ{Ý­Ïõ® ­A«ÑùØ¾×ù£¾N¾çü­ðÔ¨‹ôæ¾H®¾á¸ãÝüóŒÝC¦§ðÔ­C

  ------------------------------------------------------------------------

22.42 §–@÷ˆ©’©wüsñæ

ú¡ DB2 Ý›¦Aóû§èýz¦§÷ˆ©’©wÏwøñÏŒ¸×ð®úsñãøÒ©­A ðš·xÝ›¦AóûùÇÏœú|§–@¾¯§í¸×¯ú
§í÷ˆ©’©w¦§üsñæ­CðYñzðnøñÏŒ¸×ð®úsñãøÒ DB2­A«ÑÏ@ù™øñÏŒ¸×ð®úsñãøÒðš·xÝ›¦Aóû­C
  ------------------------------------------------------------------------

22.43 ü]¸w¯ú§í­u÷ˆ©’ðš·xÏÏÏá­vñqŽíî÷

ú¡ñzÝbùÆÝüðš·xÝ›¦Aóû¦§ù„¾ÝÏuõ@î÷ÏW­A Ýw÷Ó DB2 §èýzñqŽíî÷¯P÷ˆ©’ðš·xÏuùÆùàü]
¸w÷ˆ©’ðš·xÏÏÏá§èýzñqŽíî÷©­A ñz¾ýôúús¬Wðš·xÏÏÏá¸ãÝC¦§ TCP/IP øÐ÷ûù¦AøÔæ{Ý­
·©žæûñqŽíÏuõ@î÷­C«ÑÝb¦AøÔæ{Ý­·©žús¬WÏUÝCôæ¾­G

 vwkernel        11000/tcp

  ------------------------------------------------------------------------

22.44 ¸w÷q DB2 for VM ðš·xùàú«

ú¡ñzªø DB2 for VM ÷ˆ©’©w (ñq DRDA ûhûDÝsù£) ¸w÷qðš·xùàú«©­A CLOB ¯P BLOB
÷ˆ©’Çç®ªÝüùØ¾×ððùŒ­G

   * ñzÏœî…ùØ¾×«dùãÏ§©eù‡¬’ùà·Óæ› CLOB ¯P BLOB ÷ˆ©’¦§÷ˆ©’Çç®ª­C
   * ñzÏœî…ùØ¾×ùÆ SQL ùB’J¦§ CLOB ¯P BLOB ÷ˆ©’Çç®ª¦§¦«Ž‘­C

ÝûððùŒªO DB2 for VM ¦¸¾¯ 5.2 Ý›¦Aóû¦§Ïw¦óððùŒ­Aù„æL¦kùØ¾× DRDA ô€¨‚ LOB ¦®
¾¢Ýš DB2 ¦¸¾¯ 7 ñqŽíî÷­C
  ------------------------------------------------------------------------

22.45 ¸w÷q DB2 for VM ¸× DB2 for VSE ¾¬Ñ¦¡©‘

ú¡ñzÝb÷ˆ©’ðš·xÏÏÏá¸w÷q DB2 for VM ¸× DB2 for VSE ¾¬Ñ¦¡©‘©­A «ÑÏ¨‹ù£ñ¶¯P
Ï«¾×vððÏŽ¨‹©­CDB2 for VM ¯P DB2 for VSE ùÇ¾¬Ï„ï¸÷ˆ©’ðš·xÏÏÏáýœ¾Ö¦§ GRANT
®¾O¯y¦k­C
  ------------------------------------------------------------------------

22.46 ñã¾×Ýü¸wªý÷û¦§Ç¥õOÝrÏ„ï¸

ñã¾×¾iÏ„ï¸ Sybase ¯P Microsoft Windows NT ¦§ SQL Server Ýü¸wªý÷û¦§Ç¥õOÝr
©­G«Ñ¨‹ù£ ODBC Driver Setup æõøO¾¯ôiô¾ðôðñ¦§ Enable Quoted Identifiers ÏŽ
¨‹­C

ñã¾×¾iÏ„ï¸ UNIX ¦§ Sybase ¦§Ýü¸wªý÷û¦§Ç¥õOÝr©­A «Ñ«s¨Š .odbc.ini ·ÏÏ¦§
Sybase ÷ˆ©’ùàú«¾]ªAüsñæŽí¸Ò EQI=1­C
  ------------------------------------------------------------------------

22.47 Data Joiner ¨—¯~®¾XüsæýøíÇD

ùØ¾× DataJoiner ¯P DB2 7.1 ¦¸ + FixPak 2 ¸×õ¢ús¦¸¾¯¦§®ÔÏ ¾iî…ú|ñoùÏ@ðà¨—¯~
øT©õ­A®¾XüsæýÝüøíÇD­C

ùãÝp­AÝbùØ¾× DataJoiner ùàú«¯P÷ˆ©’ðš·xÏÏÏá 7.2 ¦¸¾Nýzæ{Ý­©­Añz¾iî…ú|æo¾ÖÇ
æý¨—¯~­G

DWC07356E øwû‹ùB’J "?" ¦§ ¦¸¾¯ "0"­AÇç®ª importTableNames ¦§®¾OÏõ¾Nýzæ{Ý­üBýzæ{õ€¾½ñ¥­C
SQL0001N üsæý¸×®e÷m«sŽô¾¬î…ôôõQõûÝù­C
SQL0001N õ„Ïœù NULLID.SQLL6D05 ©M÷Óün‚­CSQLSTATE=51002 RC = 7356  RC2 = 8600

ðYðnõ¢¾¨÷àøíÇD­A«Ñús¬WÏUÝCÝ‘Ýš db2cli.ini ·©ž­G

[COMMON]
DYNAMIC=1

Ýb UNIX ùtý×ÏW­Adb2cli.ini ·©žªOÝÝb .../sqllib/cfg ¾¨ì­C Ýb Windows NT
ÏW­Adb2cli.ini ·©žªOÝÝb .../sqllib ¾¨ì­C
  ------------------------------------------------------------------------

22.48 ÷ˆ©’ðš·xÏÏÏáü]¸w¸MøäÝ‘õê¬g

  1. ôiÝ‘÷ˆ©’ðš·xÏÏÏáü]¸w¸MøäÝ‘õê¬g­Aõê¬gññùŒ¦¡©‘¾ýôúÝbðš·xññùŒ÷ˆ©’©w¸Mðš·x
     ¾¬Ñ÷ˆ©’©wÏ§­C

     õê¬g¯íðnõê¬gññùŒ¦¡©‘ÝsÝb¸¢ññùŒ¸M¾¬Ñ÷ˆ©’©wÏ§­CÝb ASN §ä¾ÏÏ¾i¾Hõ„ùõê
     ¬gññùŒ¦¡©‘­A¾ÝðÞô}¸l¸¢ IBMSNAP­C Ýp¦GññùŒ¦¡©‘ùÇÏœÝsÝb­Aú¡ñzüzûLññùŒÏÏ
     Ïáùà¸w÷qõê¬gùàú«©­Aõê¬gññùŒ¦¡©‘ú|Ýb÷ˆ©’©wÏ§ÝêøÒ®¾á­Cü’æ—­GññùŒ¦¡©‘Ï]
     Ï@¸wÝsÝb¸¢¾¬Ñ DB ÏÏ­C ñìñoùÝb¾¬Ñ DB ¸ã®¾áññùŒ¦¡©‘­A«ÑùØ¾×ññùŒÏÏÏá
     ®¾áõê¬gùàú«­AæM® ÝAýóøœõê¬gùàú«­A¾uîdÏUññùŒ¦¡©‘­C ¸×¦Þ­AùØ¾× DJRA
     (Data Joiner Replication Administration) ýœ®~ùà¸w÷qññùŒ¦¡©‘­C
  2. Ýw÷Ó¸MùØ¾× DJRA

     ñìùØ¾× DJRA ùà¸w÷qññùŒ¦¡©‘­A®h¾ýôú¾ìôiÝ‘Ýw÷Ó­CDJRA ô€øeªø DB2 ¦§Ï@ü­
     ¾ö­CñìÝw÷Ó DJRA­A«Ñ÷äÝš d:\sqllib\djra ¾¨ì­AùÇ®”Ï@ÏU djra.exe ©M÷Óün
     ‚­CñN DJRA Ýw÷Óùñz¦§ùtý×­CÏõ® ­AñìÝb Windows NT ¦§ô}¸l¾\î…¦¡Ýsù£
     DJRA­A«Ñ®”Ï@ÏU Windows NT ¨‹óš¦§ DB2­A¨‹ù£õê¬g­A¨‹ù£õê¬g§èýzÏuùÆ­CDJRA
     Ïôðñ¸MÏ@î‰¦§ NT ·ü¾×æ{Ý­ÏœÏàªêÝP­C¸ãøäÝ‘¦§ùCÏ@ðàù‡¬’­A¾Ý®¾áÏ@ýåðnøäÝ‘
     ¦§ SQL­AÝìªO®oùSÝü¾høäÝ‘­CùØ¾×¦Þ¾ýôúÝêÝ‘·xÝs¸ãýœ¾Ö¦§ SQL­AæM® ­A¨‹ù£øä
     Ý‘ SQL ù‡¬’ôiÝ‘øäÝ‘­C
  3. ü]¸wøäÝ‘¶^ù£æ{Ý­¸MÏè¾×æ{Ý­

     ¾¨Ýbï£÷åÏÏ¦§ùtý×­AÝüÇ”ÝpÝ¢ª[§cùtý×ùàøäÝ‘¶^ù£æ{Ý­¸MÏè¾×æ{Ý­¦§®¾O­A«Ñø¥
     ó\ Replication ®®n¸Mø¥ÝãÏƒ¾U­Cüsæý¶^ù£¸MÏè¾×æ{Ý­ÏÏñNüQùØ¾×¦§ÝUðà÷ˆ©’
     ©w­C¦`úN­AñzÏœ¯íðn®¾áüqÝ‘«X·©ž­C÷ˆ©’ðš·xÏÏÏáú|ªø¸wïµõê¬gÏŠÝ­ÝêøÒ®¾á
     üqÝ‘«X·©ž­C
  4. ¸w÷qññùŒÏÏÏáÏ§õê¬gùàú«

     ùØ¾×ññùŒÏÏÏá¸w÷qõê¬gùàú«­C÷ˆ©’ðš·xÏÏÏáÏ„ï¸Ïð§õê¬g®ªÇç­GùØ¾×¦Þø’¾¯­A©
     ô­¶I­Aø•¾¯¯Eôø­Ašõ¢¯Eôø¸M¬Ô÷m¦¡©‘ (CCD ¦¡©‘)­CùØ¾×¦Þø’¾¯­B©ô­¶I¸M·œ
     µY¬Ô÷m¦¡©‘¦§®ªÇç­A¯íðnõê¬gùàú«¦¡©‘ÝüÏ@ðà¾Dðnµ„­Cù„¾Ýõê¬g®ªÇç®hÏœ¯íðn­C
     ¨‹óšüQ¸w÷qªøõê¬gùàú«¦§¨‚ÏJ¦¡©‘©­A«ÑøOñoüoÏ@¶I­Cûˆ¯éÏW­Aõê¬gùàú«ªOð¸l
     ùàú«¦¡©‘¸M®¾áÏõ CD ¦¡©‘ (šõ¢÷ˆ©’) ¦§¸w÷q­A÷ˆ©’šõ¢ýóøÒÝš¾¬Ñ¦¡©‘®e®O
     îdÝb CD ¦¡©‘Ï§­C ÝbññùŒÏÏÏáÏ§¸w÷qõê¬gùàú«­AASN.IBMSNAP_REGISTER ú|¬gÏJ
     Ï@ôæøO¨ì­A¾H¸w÷q÷àùàú«¸M¾Ý¦§ CD ¦¡©‘­CCD ¦¡©‘ÝbÝPÏ@©ô­Ï§®¾á­AÝìªO­A
     ô}¸l©¾Ý÷Þ·YùSÝü÷ˆ©’­C¸w÷qõê¬gùàú«­Añz¾i¾H¨‹óš¾uù™ÏJ® ûü¦«Ž‘­A¸×¨‹óšù™
     ÏJ®eûü¸M® ûü¦«Ž‘­CüzûLññùŒÏÏÏáõê¬gùàú«Ïôðñ¦§ÏŽ¨‹©ùà¨‹ôæ­Cñz¸ã¨‹óš¦§®e
     ûü¸M® ûü¦«Ž‘ú|¶…ï®Ýšús® CD ¦¡©‘Ï§¸ã®¾á¦§¦«Ž‘­CCD ¦¡©‘Ï§­A® ûü¦«Ž‘¸M
     ð¸lùàú«¦¡©‘¦«Ž‘ÝW§ëÝPÝW­C® ûü¦«Ž‘ÝW§ë¦§ýŽÏ@ðàÝrÏ÷ªø X­C
  5. ôžÏJõê¬gùàú«Ýš÷ˆ©’ðš·xÏÏÏá

     Ï@¾ûÝbññùŒÏÏÏá®¾áõê¬gùàú«­Añz¾i¾HñN¾ÝôžÏJ÷ˆ©’ðš·xÏÏÏá­CôžÏJùàú«©­A«Ñ
     «T¸w®”Ï@ÏU­u¾i¾Hõê¬g¦§¦¡©‘­vÏŽ¨‹©­CüoõiôDÏF÷ˆ©’ðš·xÏÏÏáªíªí
     ASN.IBMSNAP_REGISTER ¦¡©‘Ï§¦§øO¨ì­AÝüù§ù€¦¡©‘üQ¸w÷qªøõê¬gùàú«­C
  6. Ýb÷ˆ©’ðš·xÏÏÏáÏ§¸w÷qõê¬gùB’J

     Ýbæ{õ€¬ã®ªýœ¾ÖóûÏÏ­A¨‹ù£Ïð§õê¬g®ªÇçÏÏ¦§Ï@§­Gø•¾¯¯Eôø­Bšõ¢¯Eôø­B©ô­
     ¶I­B¬Ô÷m¦¡©‘­BùØ¾×¦Þø’¾¯­Cñì¸w÷qø•¾¯¯Eôø¸×šõ¢¯Eôøõê¬gÇç®ª­A«Ñø¥ó\¾HÏU
     ÝüÇ”ÝpÝ¢Ýb÷ˆ©’ðš·xÏÏÏáÝw÷Óø•¾¯¯Eôø¸×šõ¢¯Eôøõê¬g­Cªøõê¬gÇç®ª¨‹ù£óAú¡¦§
     õê¬gùàú«­CÝpÏW¸ã¯­­AùØ¾×¦Þø’¾¯­B©ô­¶I¸M·œµY¬Ô÷m¦¡©‘¦§õê¬g®ªÇç¯íðn¨‚ÏJ
     ùàú«ÝüÏ@ðà¾Dðnµ„­Cüsñæõê¬gùàú«Ýšõê¬gùB’J­Cô}ñãõê¬gùB’J¦§Ï§©e­C÷äÝšø¥¬’
     ¬Ñã­C¨‹ù£¸ãðn¦§¦«Ž‘­C ¨‹ù£ÏŽ¨‹©ùà®¾á¾¬Ñ¦¡©‘­C¨‹ù£ðš·x¾¬Ñ­C ÷äÝšüB
     ýzæ{õ€¨‹ôæùÇô¤¬gø¥¬’­C®”­u«T¸w­v­C
  7. ñãøÒ¶^ù£æ{Ý­

     DOS æ›æ­Ï§­A«Ñ¨‚ÏJ­GASNCCP source-database COLD PRUNE

     COLD ø¥¬’®¾š COLD ¦§ñãøÒ­AùÇõRøœÝsÝb¸¢ CD ¦¡©‘¦§¾“Ý¢÷ˆ©’­CPRUNE ø¥¬’
     ®¾š¶^ù£æ{Ý­§–@ IBMSNAP_PRUNCNTL ¦¡©‘­Cì¶^ù£æ{Ý­Ž~Ž•øäÝ‘­Cðnøh¾X©­A
     «ÑõQ¾× DOS æ›æ­Ï§¦§ Ctrl-Break ÏU¾OøñÏŒ­C¦`úN­AñãøÒÏè¾×æ{Ý­®e«ÑñãøÒ¶^
     ù£æ{Ý­­C
  8. õê¬gùB’JÏîùï£÷å (Promote-To-Test)

     Ý^ù÷ˆ©’ðš·xÏÏÏá­Aû‹¸¢¸w÷q¦§õê¬gùB’J­AñNùB’JÏîù­uï£÷å­v¬ãÝ­­Cüoù€ú|
     üyÝù¸wïµõê¬gÏŠÝ­÷ˆøT¬gÏJõê¬gññùŒ¦¡©‘­CñzñNªíùús¬WÝš IBMSNAP_SUBS_SET
     ­BIBMSNAP_SUBS_MEMBR­BIBMSNAP_SUBS_COLS­B IBMSNAP_SUBS_EVENT¦§øO¨ì­A¾H
     Ï„ï¸¸wïµõê¬g­C ¾¬Ñ¦¡©‘Ï]ú|Ýb¾¬Ñ÷ˆ©’©wÏÏ®¾á­CðYõê¬gÇç®ªªøùØ¾×¦Þø’¾¯
     ­B©ô­¶I­B·œµY¬Ô÷m¦¡©‘­A¾¬Ñ¦¡©‘¯íðnÏ@ðà¾Dðnµ„­C÷äÝšññùŒÏÏÏáùà®¾á¾Dðn
     µ„­C¦`úN­AÝbÏœÝP¦§¦«Ž‘÷Þ­AÝüù€õê¬g¾¬Ñ¦¡©‘Ï]¯íðnøáÏ@îµÏè­CÝr«XÝsÝb¸¢÷ˆ
     ©’ðš·xÏÏÏáÏÏ­AÝb¦¡©‘®¾á©­A¾Ýú|®¾áüoù€øáÏ@îµÏè­A¸ã¾H­AñzÏœ¯íðnÝêÏv®
     ¾áüoù€îµÏè­C¦`úN­AÝp¦GÝbññùŒÏÏÏáÏ§¸w÷q¾Dðnµ„­AÝP©­A¦«Ž‘ÏÏÏwÝüÏ@ðàøáÏ@
     îµÏè­Aú¡ñzÝb®¾á¾Dðnµ„©Ý^ô€Ý^ŽæõiøT©õ­C¸¨ýÏÝûŽæõiøT©õ­C
  9. õê¬gùB’JÏîù¾Öýœ (Promote-To-Production)

     ÝbÏîù¾Öýœïµô­­AÏœú|øæ¾“Ý¢¸wïµõê¬gÏŠÝ­šõ¢­Cüoõû¾ç¸Mù„¾ÝùB’J¦§­u÷ˆ©’
     ðš·xÏÏÏá­võ@ú~ªêÝP­C
 10. øäÝ‘õê¬gùB’J

     õê¬gùB’JüQïœ¦@ªøï£÷å¬ãÝ­® ïN¾i¾HøäÝ‘­Cùàú«¦¡©‘ôiÝ‘¾“¾išõ¢®e­A«Ñ¾ìøäÝ‘
     Ï@Ý÷­C÷äÝš­uÏuõ@ôiÝ‘ÏÏ­v(Work-in-Progress;WIP) üû÷`­A¨‹ù£õê¬gùB’J­Cøä
     Ý‘¾Ý­CùB’JøäÝ‘©­AIBMSNAP_SUBS_EVENT ¦¡©‘Ï§¦§ù’¾¢øO¨ìú|õ¢ús­A
     IBMSNAP_SUBS_SET ¦§¸wïµõê¬gøO¨ìªø® ÷mõ@¾×ÏÏ­C¸wïµõê¬gøùÏWøäÝ‘­C¸wïµõê
     ¬gøäÝ‘©­A¾Nýzæ{Ý­¸I¾sÏè¾×æ{Ý­üBýzõ@¾×ÏÏ¦§¸wïµõê¬g­C Ïõ® ­Aõ¢úsð¸lùà
     ú«¦¡©‘­A¸ãšõ¢¦§÷ˆ©’ñNýóÝš CD ¦¡©‘­CÝp¦GøäÝ‘ÏUÝCõê¬gùB’J­AÏè¾×æ{Ý­ÝAÏ@
     Ý÷øäÝ‘­Ašõ¢÷ˆ©’ñNñq CD ¦¡©‘ýóøÒù¾¬Ñ¦¡©‘­C
 11. õê¬gùB’Jðøîùï£÷å (Demote-To-Test)

     Ýbðøîùï£÷åïµô­­AÏœú|øæ¾“Ý¢¸wïµõê¬gÏŠÝ­šõ¢­Cüoõû¾ç¸Mù„¾ÝùB’J¦§­u÷ˆ©’
     ðš·xÏÏÏá­võ@ú~ªêÝP­C
 12. õê¬gùB’Jðøîùô}æo (Demote-to-Development)

     ú¡ñzñNõê¬gùB’Jðøîùô}æo©­A¸wïµõê¬g÷ˆøTú|Ýêõê¬gññùŒ¦¡©‘Ï§ýóøœ­Cðøîù
     ¾ÖýœõûÝù® ­AîS¸w¸wïµõê¬gÏœú|Ýbõê¬gññùŒ¦¡©‘Ï§îdÏUøO¨ì­C¾¬Ñ¦¡©‘Ï]ú|ÝbÝû
     üQøœ¾h­CCD ¦¡©‘ú|óAú¡Ýa®OîdÏUùà­AÝ]ªø¾ÝŽí¸¢õê¬gùàú«¦§¸w÷q­C
 13. ÝpÝ¢Ýb÷ˆ©’ðš·xÏÏÏáü]¸wø•¾¯¯Eôø¸×šõ¢¯Eôø­C
        o ¨‚ÏJ¦¡©‘­C¨‹óš¾i¾HüQ GROUP BY üîðzÝ­ùØ¾×¦§¨‚ÏJ¦¡©‘­C ùãÝp­AùØ¾×õt
          Ýüüoù€¦«Ž‘¦§¨‚ÏJ¦¡©‘­GSALES­AREGION­ADISTRICT­C
        o õê¬gùB’J­C¨‹óšø•¾¯¸×šõ¢¯Eôø­Cô}ñãùB’JÏ§©e­C
             + ÝbÏè¾×æ{Ý­øäÝ‘©­A¾Ý¾ýôúøäÝ‘ÇçÝ SELECT SUM(SALES), REGION,
               DISTRICT GROUP BY REGION, DISTRICT ¦§ SELECT üîðzÝ­­C Ý]Ýû­A
               Ýb¨‹ù£¦§¨‚¾X¦«Ž‘ÏÏ­Añz¾ýôú¨‹óš REGION­BDISTRICT Ï×Ï@ðàðp§ƒ¦«
               Ý‘ SUM(SALES)­CùØ¾×ús¬Wðp§ƒ¦«Ý‘®”ôs­C «dùãÏÏ«Ñ¨‚ÏJ
               SUM(SALES) ¸¢­u¦¡¾šÝ­­vŽ‘Ý­C·xÝs¾Ý­C
             + WHERE Ïl¾y­CÝüÏ@ôæõê¬g¯íùD­G Ýbñzü]¸w¾u¯í GROUP BY Ïl¾y¦§õê
               ¬gùB’J©­A ¾ýôúïœù¥ DUMMY WHERE Ïl¾y (Ï¤Ýp 1=1)­CÏœðnñN
               "WHERE" üoðàÝr¾[ù WHERE Ïl¾yÏÏ­CÝ]Ýû­Aø•¾¯¯Eôø¦§÷ˆ©’ðš·xÏÏ
               Ïá GUI Ï§­A¾uÝüÏ@ðà WHERE Ïl¾y¨‚ÏJŽ‘Ý­CÝbÝûŽ‘ÝÏÏ­AùãÝp­G
               ¨‚ÏJ­G 1=1 GROUP BY REGION, DISTRICT ù­ušõ¢¯Eôø­v­A Ýü
               ­uWHERE Ïl¾y­v¸M­uGROUP BY ­vùƒðà¨‚ÏJŽ‘Ý­G ­uWHERE Ïl¾y­vŽ‘
               Ý¨‚ÏJ­G 1=1­A­uGROUP BY­vŽ‘Ý¨‚ÏJ­G GROUP BY REGION, DIST
               RICT
             + ü]¸wü¥ÏU¦§ùB’JÏ§©e­AïNÝpñzü]¸wù„¾Ýõê¬gÇç®ªÏ@î‰­C®”­u«T¸w­v¾H
               ·xÝsùB’J­AùÇ®¾á¾¬Ñ¦¡©‘¦®¾¢­C
        o ô}ñã¾¬Ñ¦¡©‘¦®¾¢­Cõ¢õ‹ðp§ƒ¦«Ý‘¦¡¾šÝ­¦§¨‚¾X¦«Ž‘ÝW§ëÝùªøÝü©Ž¦§¦«Ž‘
          ÝW§ë­AùÇ¾B®¸w¦«Ž‘¦§Ýü©Ž¦§÷ˆ©’Çç®ª­C·xÝs¾¬Ñ¦¡©‘¦®¾¢­C
        o Ýbõê¬gùB’JøäÝ‘ïœ¦@ï£÷å (Promote-to-Test)­C®¾á¾¬Ñ¦¡©‘­CÏœ¯íðn¾D
          ðnµ„­C
        o øäÝ‘ùB’JÝpù„¾Ýõê¬gùB’Jî‰­C

  ------------------------------------------------------------------------

22.49 §ÇÇ›ñ’÷¥îæüZ

   * ô}ñãÏè¾×æ{Ý­¦§øl¶š­AÝbðš·xÏ§©eæeðñü]¸w¾Nýzæ{Ý­ðÔ = 4­C¾Nýzæ{Ý­ô}ñãû‹Ïè
     ¾×æ{Ý­õûóÆ¦§øl¶š­Aú¡¾Nýzæ{Ý­øl¶š = 4 ©­C

     Ýp¦GÝb CD ¦¡©‘ÏÏùSÝü¾“Ý¢÷ˆ©’­A®h®š¾iî…ªO¶^ù£æ{Ý­ùSÝüñãøÒ­A¸×®¾ášõ¢÷ˆ
     ©’¦§ð¸lùàú«¦¡©‘ùSÝüõ¢ús­C
   * ñ’æ{æõøO¾¯Ïõüq¦óðôðñ¦§ôl¾¢Ý›¦AóûŽ‘ÝÝê«uÏW¯­¸£ÏÏ¨•§|ÏF­C
   * ôl¾¢Ý›¦Aóû¯íðnÏ„ï¸ ESMTP­A÷ˆ©’ðš·xÏÏÏáüq¦óÏ~î…Ïuõ@­CÝb­uô}ñãÏuõ@ôiÝ‘
     ÏÏ­væ›æ­¦§¯­¸£ÏÏ­A®”Ï@ÏU "ðš·x --> Ïuõ@ôiÝ‘ÏÏ"­A ÝàÏœªO "ðš·xÏÏÏá -->
     Ïuõ@ôiÝ‘ÏÏ"­C

  ------------------------------------------------------------------------

22.50 Ýsù£ùàú«¸M¾¬Ñ·

ÏUÝC¦¡©‘ÝC¾š­A÷ˆ©’ðš·xÏÏÏá¸ãÏ„ï¸¦§ùàú«¸M¾¬Ñ·Ïõ¦¸¾¯Ï×¦¸Ý÷­C

¦¡ 7. IBM ðš·xùàú«¸ãÏ„ï¸¦§¦¸¾¯¸M¦¸Ý÷
 ùàú«                                 ¦¸¾¯­ç¦¸Ý÷
 IMS                                  5.1
 DB2 Universal Database for Windows NT5.2 - 7.1
 DB2 Universal Database               5.2 - 7.1
 Enterprise-Extended Edition
 DB2 Universal Database for OS/2      5.2 - 7.1
 DB2 Universal Database for AS/400    3.7 - 4.5
 DB2 Universal Database for AIX       5.2 - 7.1
 DB2 Universal Database for Solaris   5.2 - 7.1
 Operating Environment
 DB2 Universal Database for OS/390    4.1 - 7.1
 DB2 DataJoiner                       2.1.1
 DB2 for VM                           5.3.4 ¸×õ¢ús¦¸
 DB2 for VSE                          7.1

 ùàú«                     Windows NT               AIX
 Informix                 7.2.2 - 8.2.1            7.2.4 - 9.2.0
 Oracle                   7.3.2 - 8.1.5            8.1.5
 Microsoft SQL Server     7.0
 Microsoft Excel          97
 Microsoft Access         97
 Sybase                   11.5                     11.9.2

¦¡ 8. IBM ðš·x¾¬Ñ·¸ãÏ„ï¸¦§¦¸¾¯¸M¦¸Ý÷
 ¾¬Ñ                                 ¦¸¾¯­ç¦¸Ý÷
 DB2 Universal Database for Windows NT6 - 7
 DB2 Universal Database               6 - 7
 Enterprise-Extended Edition
 DB2 Universal Database for OS/2      6 - 7
 DB2 Universal Database for AS/400    3.1-4.5
 DB2 Universal Database for AIX       6 -7
 DB2 Universal Database for Solaris   6 -7
 Operating Environment
 DB2 Universal Database for OS/390    4.1 - 7
 DB2 DataJoiner                       2.1.1
 DB2 DataJoiner/Oracle                8
 DB2 for VM                           3.4 - 5.3.4
 DB2 for VSE                          3.2, 7.1
 CA/400                               3.1.2
  ------------------------------------------------------------------------

22.51 Ï„ï¸¦§®D IBM ÷ˆ©’©wùàú«¦§ús¬Wù’ôæ

ÏU¦¡¸ãÝC­AªOû‹¸ãÏ„ï¸Ïõ®D IBM ÷ˆ©’©wùàú«¦§ús¬Wôæ¾­G

 ÷ˆ©’©w                   õ@ú~ùtý×                ÷ˆ©’©wñqŽíî÷¯íùD
 Informix                 AIX                     Informix-Connect ¯P
                                                  ESQL/C ¦¸¾¯ 9.1.4 ¸×õ¢ús
                                                  ¦¸
 Informix                 Solaris õ@ú~·“ûã        Informix-Connect ¯P
                                                  ESQL/C ¦¸¾¯ 9.1.3 ¸×õ¢ús
                                                  ¦¸
 Informix                 Windows NT              Informix-Connect for
                                                  Windows Platforms 2.x ¸×
                                                  Informix-Client Software
                                                  Developer's Kit for
                                                  Windows Platforms 2.x
 Oracle 7                 AIX                     Oracle7 SQL*Net Ï×
                                                  Oracle7 SQL*Net Ý@¾×·©ž
                                                  ©w (õQ¾× genclntsh
                                                  script ¸ã®¾á)
 Oracle 7                 Solaris õ@ú~·“ûã        Oracle7 SQL*Net Ï×
                                                  Oracle7 SQL*Net Ý@¾×·©ž
                                                  ©w (õQ¾× genclntsh
                                                  script ¸ã®¾á)
 Oracle 7                 Windows NT              SQL*Net ý{Ý‘¦¸¾¯¦§¾¨«T
                                                  DLL­A¾~¾[ OCIW32.DLL­C
                                                  ùãÝp­ASQL*Net 2.3 ¯íùØ¾×
                                                  ORA73.DLL­BCORE35. DLL­B
                                                  NLSRTL32.DLL­B
                                                  CORE350.DLL Ï×
                                                  OCIW32.DLL­C
 Oracle 8                 AIX                     Oracle8 Net8 Ï× Oracle8
                                                  SQL*Net Ý@¾×·©ž©w (õQ¾×
                                                  genclntsh8 script ¸ã®
                                                  ¾á)
 Oracle 8                 Solaris õ@ú~·“ûã        Oracle8 Net8 Ï× Oracle8
                                                  SQL*Net Ý@¾×·©ž©w (õQ¾×
                                                  genclntsh8 script ¸ã®
                                                  ¾á)
 Oracle 8                 Windows NT              ðYðnÝsù£¯ú§íæ¾îªø 8.0.3
                                                  ¦¸¾HÏW¦§ Oracle8 ÷ˆ©’©w
                                                  Ý›¦Aóû­Añz®KôúÝw÷Ó
                                                  Oracle Net8 Client ¦¸¾¯
                                                  7.3.4.x­B8.0.4 ¸×õ¢ús
                                                  ¦¸­C

                                                  Ýb Intel ùtý×ÏW­Añz¾ýôú
                                                  Ýbñz¦§÷“©|ÏÏÝw÷Ó Oracle
                                                  Net8 Client ¦§ ¾¨«T DLL
                                                  (Ýp­GOra804.DLL­B
                                                  PLS804.DLL Ï× OCI.DLL)­C
 Sybase                   AIX                     Ýb®D DCE ·“ûãÏÏ (ibsyb15
                                                  ODBC XøÒæ{Ý­)­G
                                                       libct ·©ž©w

                                                  Ýb DCE ·“ûãÏÏ (ibsyb1115
                                                  ODBC XøÒæ{Ý­)­G
                                                       Sybase 11.1 ñqŽíî÷
                                                       ·©ž©w libct_r

 Sybase                   Solaris õ@ú~·“ûã        Ýb®D DCE ·“ûãÏÏ (ibsyb15
                                                  ODBC XøÒæ{Ý­)­G
                                                       libct ·©ž©w

                                                  Ýb DCE ·“ûãÏÏ (ibsyb1115
                                                  ODBC XøÒæ{Ý­)­G
                                                       Sybase 11.1 ñqŽíî÷
                                                       ·©ž©w libct_r

 Sybase                   Windows NT              Sybase Open
                                                  Client-Library 10.0.4 ¸×
                                                  õ¢ús¦¸Ï×óAú¡¦§ Sybase
                                                  Net-Library­C
  ------------------------------------------------------------------------

22.52 Ýb÷ˆ©’ðš·xÏÏÏáÏÏÏƒøÒ®¾á÷ˆ©’ùàú«

ú¡ùØ¾× Relational Connect Ï× "Create Nickname" üîðzÝ­ùà®¾á÷ˆ©’ùàú«©­A û‹
¸¢Ýb÷ˆ©’ðš·xÏÏÏáÏÏôžÏJ¦¡©‘¦§ªêÇ”ù‡¬’­A÷à÷ˆ©’ùàú«ñNæL¦kùØ¾×­CðYðnñN÷ˆ©’ùàú«
¾×õ@ùàú«¦¡©‘¸×¾¬Ñ¦¡©‘­A«ÑøäÝ‘ÏUÝCùB’J­G

  1. ¸w÷qùàú«-¾¬Ñ­AÝàÏœôžÏJ¾“Ý¢¦¡©‘­C
  2. ©iô}÷ˆ©’ðš·xÏÏÏá¾Dæ›æ­¦§ðš·xùàú«/¾¬ÑóÐ¦ªæý§c­A ùÇÝb¸ãñìùàú«-¾¬Ñ¦§"¦¡
     ©‘"ÏW®”Ï@ÏUú’û®¾kµ„­C
  3. ®”Ï@ÏU¸w÷q­C
  4. ùØ¾×ô}ñã¦§æõøO¾¯¸w÷q÷ˆ©’ùàú«­A ùÇ«T¸wªøùCÏ@ðà÷ˆ©’ùàú«¸w÷qÏF¦«Ž‘­C

ðY¯í÷âýà÷ˆøT­A«Ñø¥ó\­u÷ˆøTÏÏÏá­vÏÏ¦§"¸w÷qðš·xùàú«¦¡©‘"¸×"¸w÷qðš·x¾¬Ñ¦¡©‘
"­C
  ------------------------------------------------------------------------

22.53 ùØ¾× Common Warehouse Metadata Interchange (CWMI) ôžÏJÏ×ôž¾Xïyðz÷ˆ©’

22.53.1 ¶ýÏô

øœÏF¾®eÏ„ï¸¦§¬Ñ¾š¯yù¾·©ž­A÷ˆ©’ðš·xÏÏÏáý{ÝbÏ]¾i¾HôžÏJÏ×ôž¾Xïyðz÷ˆ©’ùýÝX
Common Warehouse Metamodel (CWM) ¬Ñú€¦§ XML ·©ž­A ¾HÏ×ñq XML ·©žôžÏJÏ×ôž
¾Xïyðz÷ˆ©’­CôžÏJÏ×ôž¾Xüoù€ùÞúà CWM ¦§ XML ·©ž ïNªO¸ã®¦§ Common Warehouse
Metadata Interchange (CWMI)­C

ñz¾i¾HñqÏUÝC÷ˆ©’ðš·xÏÏÏá¦®¾¢ôžÏJÏ×ôž¾Xïyðz÷ˆ©’­G

   * ðš·xùàú«
   * ðš·x¾¬Ñ
   * ¾DÝ©øØø­A¾]ªAæ{õ€­Bùàú«­B¾¬ÑÏ×ùB’J
   * ùØ¾×¦Þ¸w÷qæ{Ý­

CWMI ôžÏJÏ×ôž¾XÏ«¾×æ{Ý­¾®eÏœÏ„ï¸îS¸wÇç®ª¦§ïyðz÷ˆ©’­A¾]ªA­G ñ’æ{­Bðš·x§ä¾
­Bñô©|ùB’J­Bð®|Ç”®Y­BùØ¾×¦ÞÏ×÷sýå­C

÷ˆ©’ðš·xÏÏÏáú|®¾áÏ@ðà¾]õtôžÏJÏ×ôž¾Xæ{õ€æý¦G¦§Ï‚¯x·­Cüqñ`Ï‚¯x·ú|®¾áÝb
x:\program files\sqllib\logging ¾¨ì (ù„ÏÏ x: ªOÝw÷Ó DB2 ¦§§Ø§Ñóö)­A¸×ªOñz
®¸wÝb VWS_LOGGING ·“ûãš¬’¦§¾¨ì­CÏ‚¯x·ªOî¶Ï†Ýr¦§­Fñz¾i¾H¾×¾“Ý¢Ï†Ýr«s¨Šæ{
Ý­ùà·Óæ›¾Ý­C

22.53.2 ôžÏJïyðz÷ˆ©’

ñz¾i¾HÝb÷ˆ©’ðš·xÏÏÏáÏÏôžÏJïyðz÷ˆ©’­A¸×¦Þñq¸R¾OÝ‘ôžÏJïyðz÷ˆ©’­C

üzûLôžÏJæ{õ€¸ã®¾á¦§ús¦®¾¢ú|®ªœæûûwü]¦§÷ˆ©’ðš·xÏÏÏáÝw¾ç÷sýå­CðY¯í÷âýà÷ˆ
øT­A«Ñø¥ó\¦¸¾¯¦`úNù’ôæÏÏ¦§­uÝbôžÏJ® õ¢úsóöñK®O@­v­C

Ýp¦GªOôžÏJÇ”¸¢ªYùB’J¦§ïyðz÷ˆ©’­A®h¾i¾HñNÝhðà·©ž¯PùB’JªêÇ”µp­CÇ”¸¢ùB’J¦§ïy
ðz÷ˆ©’ú|·xÝsÝb XML ·©žÏÏ­A ÝìªOÝü©ùB’Jú|ÝüªêÇ”µp¦§÷ˆ©’ªO·xÝsªø BLOB­CBLOB
ïyðz÷ˆ©’¦§·ÝW¯P XML ·©žªêÝP­A ÝìªO¾ÝªOÝbðàõO¦§·©žÏÏ­Aù„ø’·ÝWªø¬’Ýr­C¸ã
ÝüªêÇ”¦§ùB’J·©žÝbôžÏJ©¾ýôúÝbªêÝP¦§¾¨ìÏÏ­C

ú¡ùB’JÝbï£÷å¸×¾Öýœ¬ãÝ­©õ¢úsùB’J

ùB’J¾ýôúÝbô}æo¬ãÝ­ÏÏ­A÷ˆ©’ðš·xÏÏÏáÏ~î…õ¢úsùB’J¦§ïyðz÷ˆ©’­CÝp¦GùB’JªOÝbï£÷å
¸×¾Öýœ¬ãÝ­­A ®hÝbôžÏJïyðz÷ˆ©’Ïõ®eñNùB’Jðøîªøô}æo¬ãÝ­­G

  1. ænÏJ÷ˆ©’ðš·xÏÏÏá­C
  2. Ýbðnðøî¦§ùB’JÏW®”Ï@ÏUú’û®¾kµ„­AÝA®”Ï@ÏU¬ãÝ­­C
  3. ®”Ï@ÏUô}æo­C

ý{ÝbùB’JïNÝbô}æo¬ãÝ­ÏF­CÝbôžÏJïyðz÷ˆ©’Ïõ® ­AÝAñNùB’Jšõ¢Ý^ï£÷å¸×¾Öýœ¬ãÝ­­C

ñq÷ˆ©’ðš·xÏÏÏáôžÏJ÷ˆ©’

ñz¾i¾HÝb÷ˆ©’ðš·xÏÏÏáÏõÏÏôžÏJïyðz÷ˆ©’­G

  1. ænÏJ÷ˆ©’ðš·xÏÏÏá­C
  2. ®”Ï@ÏU¾¦æ­©‘ÏÏ¦§ðš·x­C
  3. ®”Ï@ÏU ¨‹ù£¦§ -> ôžÏJïyðz÷ˆ©’ -> ¾‘ï®·©ž...­C
  4. Ýb­uôžÏJïyðz÷ˆ©’­væ›æ­ÏÏ­A®¸w¾]õtðnôžÏJ¦§ïyðz÷ˆ©’¦§·ÝW­Cñz¾i¾Hµ„ÏJ·
     ÝW¸×¾×¶sŽìùàõ„·©ž­C
        o Ýp¦Gñz¦óûDÝ÷m­A®h«Ñµ„ÏJõûóÆ¦§÷“©|¸MðnôžÏJ¦§·©žÝW§ë­C«Ñ«T¸w¾[ÏW
          .xml ø’·ÝW­A ¾H®¸wðn¾H XML ©‘Ý­ùàôžÏJïyðz÷ˆ©’­C
        o ðYðn¾×¶sŽìùàõ„·©ž­G

            a. ®”Ï@ÏU (...) ®”ôs­C
            b. Ýb­u·©ž­væ›æ­ÏÏ­AñN·©žÇç®ªšõ¢ªø XML­C
            c. ýóÝš¾¨«T¦§¾¨ì­AÝA¨‹ù£ðnôžÏJ¦§·©ž­C

               æ—:
                    ·©ž¾ýôúªø .xml ø’·ÝW­C
            d. ®”Ï@ÏU«T¸w­C
  5. ÝbôžÏJïyðz÷ˆ©’æ›æ­ÏÏ­A ®”Ï@ÏU«T¸wùàõûÝù­CÝb÷ˆ©’ðš·xÏÏÏáôžÏJ·©ž©ú|Æ
     ¾šôi®žæ›æ­­C

ùØ¾×¸R¾OÝ‘ùàôžÏJïyðz÷ˆ©’

ñzÏ]¾i¾HùØ¾×¸R¾OÝ‘ùàôžÏJïyðz÷ˆ©’­CÏUÝCªøôžÏJ¦§®¾O¯y¦k­G

CWMImport XML_file dwcControlDB dwcUserId dwcPW [PREFIX = DWCtbschema]
 XML_file                             ðnôžÏJ¦§ XML ·©ž¦§õûóÆ÷“©|¸M·©žÝW
                                      §ë (¾]ªA§Ø§ÑóöÏ×¾¨ì)­CÝûø¥¬’ªO¾ýðn
                                      ¦§­C
 dwcControlDB                         ïyðz÷ˆ©’¸ãðnôžÏJ¦§ðš·xññùŒ÷ˆ©’©wÝW
                                      §ë­CÝûø¥¬’ªO¾ýðn¦§­C
 dwcUserId                            ñz¾×ùàænÏJðš·xññùŒ÷ˆ©’©w¦§ùØ¾×¦Þ
                                      ID­CÝûø¥¬’ªO¾ýðn¦§­C
 dwcPW                                ñz¾×ùàænÏJðš·xññùŒ÷ˆ©’©w¦§ùØ¾×¦ÞüqÝ‘
                                      «X­CÝûø¥¬’ªO¾ýðn¦§­C
 [PREFIX=DWCtbschema]                 ÷ˆ©’ðš·xÏÏÏáùtý×¦¡©‘¦§÷ˆ©’©w§ä¾ÝW
                                      §ë­A Ýü©ªO®¦¡©‘Ýrð§­CÝp¦GùSÝü®¸w
                                      ðÔæû PREFIX=­A®hûwü]§ä¾ÝW§ëªø IWH­C
                                      Ýûø¥¬’ªO¾i¨‹¾×¦§­C

22.53.3 ÝbøäÝ‘ôžÏJÏ«¾×æ{Ý­Ïõ® õ¢úsïyðz÷ˆ©’

ÝbôžÏJ® õ¢úsóöñK®O@

õ@ªøÝw¾çÏW¦§Ýãôq­A÷ˆ©’ðš·xÏÏÏáÏœú|ôžÏJ¸×ôž¾XüqÝ‘«X­Cñz¾ýôúæ›¯íðnÝbús¦®¾¢ÏW
õ¢úsüqÝ‘«X­CðY¯íôžÏJ¦`úNù’ôæ¦§÷âýà÷ˆøT­A «Ñø¥ó\÷ˆ©’ðš·xÏÏÏá§èýzÏƒ¾U¦§ýŽ 12
üû­uôž¾X¸MôžÏJ÷ˆ©’ðš·xÏÏÏáïyðz÷ˆ©’­v­C

ÝbôžÏJïyðz÷ˆ©’©­A¸ãÝü¦®¾¢üœú|®ªœæûûwü]Ýw¾ç÷sýå­Cñz¾i¾Hšõ¢¾iÝsù£¦®¾¢¦§÷s
ýå­G

  1. ænÏJ÷ˆ©’ðš·xÏÏÏá­C
  2. Ýb¾]õtðnšõ¢¦§¦®¾¢¦§÷ˆ©’õùÏW®”Ï@ÏUú’û®¾kµ„­C
  3. ®”Ï@ÏUÏ§©e­AÝA®”Ï@ÏUóöñK®O@¬Ñã­C
  4. ñq¨‹ù£¦§ðš·x÷sýåÝC¾šÏÏñN÷sýåøœ¾h­A ¸×¦Þñq¾i¾×¦§ðš·x÷sýåÝC¾šÏÏús¬W÷s
     ýå­C
  5. ®”Ï@ÏU«T¸w­C

22.53.4 ôž¾Xïyðz÷ˆ©’

ñz¾i¾HÝb÷ˆ©’ðš·xÏÏÏáÏÏôž¾Xïyðz÷ˆ©’­A¸×¦Þñq¸R¾OÝ‘ôž¾Xïyðz÷ˆ©’­C

ü­¾öùB’J¦§ïyðz÷ˆ©’ªO·xÝsªø BLOB­CBLOB ïyðz÷ˆ©’ú|ôž¾XùðàõO·©žÏÏ­A ù„·ÝW¯P
ùB’J¦§ XML ·©žªêÝP­AÝìªOø’·ÝWªO¬’Ýr (.1­B.2 æ¾æ¾)­C

ñq÷ˆ©’ðš·xÏÏÏáôž¾X÷ˆ©’

ñz¾i¾HÝb÷ˆ©’ðš·xÏÏÏáÏõÏÏôž¾Xïyðz÷ˆ©’­G

  1. ænÏJ÷ˆ©’ðš·xÏÏÏá­C
  2. ®”Ï@ÏU¾¦æ­©‘ÏÏ¦§ðš·x­C
  3. ®”Ï@ÏU ¨‹ù£¦§ -> ôž¾Xïyðz÷ˆ©’ -> ¾‘ï®·©ž­C
  4. Ýb­uôž¾Xïyðz÷ˆ©’­væ›æ­ÏÏ­A®¸wñN¾]õtôž¾X¦§ïyðz÷ˆ©’¦§·ÝW­Cñz¾i¾H¨‚ÏJ·
     ÝW¸×¾×¶sŽìùàõ„·©ž­G
        o Ýp¦Gñz¦óûDõûóÆ¦§÷“©|Ï×ðnùØ¾×¦§·ÝW­A «Ñ¨‚ÏJù·ÝW¨‚ÏJŽ‘Ý­C«Ñ«T¸w
          ¾[ÏW .xml ø’·ÝW­A ¾H®¸wðn¾H XML ©‘Ý­ùàôž¾Xïyðz÷ˆ©’­C
        o ðYðn¾×¶sŽìùàõ„·©ž­G

            a. ®”Ï@ÏU (...) ®”ôs­C
            b. Ýb·©žæ›æ­ÏÏ­AñN·©žÇç®ªšõ¢ªø XML­C
            c. ýóÝš¾¨«T¦§¾¨ì­AÝA¨‹ù£ðnôž¾X¦§·©ž­C

               æ—:
                    ¾“Ý¢ñz¸ã¨‹ù£¦§ý{Ýs·©žú|üQôž¾X¦§ïyðz÷ˆ©’¶Ñ¬g­C
            d. ®”Ï@ÏU«T¸w­C
  5. ú¡­uôž¾Xïyðz÷ˆ©’­væ›æ­Æ¾šÏF¾¨«T¦§·ÝW­A Ýb¾i¾×¦§¦®¾¢ÝC¾šÏÏ®”Ï@ÏUðnôž
     ¾Xù„ïyðz÷ˆ©’¦§¦®¾¢­C
  6. ®”Ï@ÏU > ý÷ûñN¨‹ù£¦§¦®¾¢ñq ¾i¾×¦§¦®¾¢ÝC¾šÏÏýóøÒù¨‹ù£¦§¦®¾¢ÝC¾š­Cð®«’
     ¾HÏWùB’J­A¦«ù¸ãÝüðnôž¾X¦§¦®¾¢üœÝC¾šÝb¨‹ù£¦§¦®¾¢ÝC¾šÏÏ­C
  7. ®”Ï@ÏU«T¸w­C

÷ˆ©’ðš·xÏÏÏáú|®¾áÏ@ðà¨‚ÏJ·©ž (¾Ý¾]õt¯Pðnôž¾X¦§÷ˆ©’ðš·xÏÏÏá¦®¾¢¦§ªêÇ”÷ˆ
øT)­AæM® ôž¾XÝüÇ”ù§ù€¦®¾¢¦§ïyðz÷ˆ©’­C Ýb÷ˆ©’ðš·xÏÏÏáôž¾Xïyðz÷ˆ©’©ú|Æ¾šôi
®žæ›æ­­C

ú¡ôž¾Xæ{õ€õûÝù©­AñNú|ÝªùÝüÇ”ôž¾Xæ{õ€¦§ø¥ÝãøT©õ­CÝ^¶Ñ«X 0 ¦¡¾šôž¾XÝù¾\­Cñz
Ï]¾i¾H·Óæ›Ï‚¯x·­A¾Hù£ño÷âýà÷ˆøT­C

ùØ¾×¸R¾OÝ‘ùàôž¾Xïyðz÷ˆ©’

Ýbñq¸R¾OÝ‘ôž¾Xïyðz÷ˆ©’Ïõ®e­Añz¾ýôú¾ì®¾áÏ@ðà¨‚ÏJ·©ž­C¨‚ÏJ·ªOÏ@ðàø’·ÝWªø
.INP ¦§Ï†Ýr·­A ¾Ýú|ùÞúàðnôž¾X¦§¦®¾¢Çç®ªÝC¾X¸ãÝü¦®¾¢­Cú¡ñzÝb÷ˆ©’ðš·xÏÏÏáÏõ
ÏÏôž¾X©­A ¨‚ÏJ·ªOÝêøÒ®¾á¦§­AÝìªOñq¸R¾OÝ‘ôž¾X­Añz¾ýôú¾ì®¾á¨‚ÏJ·­Cñz¾i¾H
ùØ¾×¾“Ý¢Ï†Ýr«s¨Šæ{Ý­ùà®¾á¨‚ÏJ·­Cµ„ÏJ¸ãÝü¦§¦®¾¢ÝW§ë (¯PÆ¾šÝb÷ˆ©’ðš·xÏÏÏá
ÏÏ¦§ÝW§ëªêÝP)­C«Ñ«T¸w·©žªO®¾áÝbÏ@ðà¾i¦¬g¦§¾¨ìÏÏ­Cú¡ñzøäÝ‘ôž¾XÏ«¾×æ{Ý­
©­A ÷ˆ©’ðš·xÏÏÏáú|ñN XML ·©ž¬gÏJù¨‚ÏJ·¸ãÝb¦§ªêÝP¾¨ìÏÏ­C

ÏUÝCªøÏ@ðà«dùã¨‚ÏJ·­G

<PROC>
ñÑó€®óù’ûˆ¦¡©‘æ{õ€
<IR>
ñÑó€®ó·©žùàú«
ñÑó€®ó¾¬Ñ
<UDP>
ús®æ{Ý­÷sýå

Ýb <PROC> (æ{õ€) øØªq­AÝC¾X¸ãÝüðnôž¾X¦§æ{õ€­CÝb <IR> (÷ˆøT÷ˆú«) øØªq­AÝC¾X
¸ãÝüðnôž¾X¦§ðš·xùàú«Ï×¾¬Ñ­C ÷ˆ©’ðš·xÏÏÏáú|ÝêøÒù™ÏJ¯Püoù€ùàú«Ï×¾¬ÑªêÇ”µp¦§
¦¡©‘¸M¦«Ž‘­CÝb <UDP> (ùØ¾×¦Þ¸w÷qæ{Ý­) øØªq­A ÝC¾X¸ãÝüðnôž¾X¦§æ{Ý­÷sýå­C

ðYðnôž¾Xïyðz÷ˆ©’­AÝb DOS ïœ¾šý÷ûÏU¨‚ÏJÏUÝC®¾O­G

CWMExport INPcontrol_file dwcControlDB dwcUserID dwcPW [PREFIX=DWCtbschema]

 INPcontrol_file                      ¾]õtðnôž¾X¦®¾¢¦§ .INP ·©ž¦§õûóÆ÷“©|
                                      ¸M·©žÝW§ë (¾]ªA§Ø§ÑóöÏ×¾¨ì)­CÝûø¥
                                      ¬’ªO¾ýðn¦§­C
 dwcControlDB                         ðnñqù„ôž¾X¦§ðš·xññùŒ÷ˆ©’©wÝW§ë­CÝûø¥
                                      ¬’ªO¾ýðn¦§­C
 dwcUserID                            ñz¾×ùàænÏJðš·xññùŒ÷ˆ©’©w¦§ùØ¾×¦Þ
                                      ID­CÝûø¥¬’ªO¾ýðn¦§­C
 dwcPW                                ñz¾×ùàænÏJðš·xññùŒ÷ˆ©’©w¦§üqÝ‘«X­CÝû
                                      ø¥¬’ªO¾ýðn¦§­C
 [PREFIX=DWCtbschema]                 ÷ˆ©’ðš·xÏÏÏáùtý×¦¡©‘¦§÷ˆ©’©w§ä¾ÝW
                                      §ë­A Ýü©ªO®¦¡©‘Ýrð§­CÝp¦GùSÝü®¸w
                                      ðÔæû PREFIX=­A®hûwü]ðÔªø IWH­CÝûø¥¬’
                                      ªO¾i¨‹¾×¦§­C
  ------------------------------------------------------------------------

22.54 OS/390 Runstats Ï«¾×æ{Ý­ùB’J

Ýb DWC ÏÏ¸w÷q OS/390 Runstats Ï«¾×æ{Ý­ùB’J©­AùØ¾×¦Þ·ü÷à¦óûDÏUÝCÝ¸¢­uùB’J
Ï§©eû‹÷š©­v¦§­uø¥¬’­v¬ÑãÏÏ¦§Ï§©e­C ðYªO¦¡©‘¦ô­Ž‘Ý­AùØ¾×¦Þ·ü÷à¾HÏj¬g¨‚ÏJ
ÝW§ë­CÝp¦G¦¡©‘¦ô­ÏœÝb÷ˆ©’©w DSNDB04 ÏÏ­A ®h¯íðn¾H÷ˆ©’©w¾]õt¾Ýùà¸w÷q¦¡©‘¦
ô­ÝW§ë­CùãÝp­A¨‚ÏJ SAMPLE.EMPLOYEE­C¯­¸£¾®eÏœîAÏ×ÝûŽ‘Ý­C
  ------------------------------------------------------------------------

22.55 OS/390 ÷ÏJÏ«¾×æ{Ý­ùB’J

Ýb DWC ÏÏ¸w÷q OS/390 ÷ÏJÏ«¾×æ{Ý­ùB’J©­AùØ¾×¦Þ·ü÷à¦óûDÏUÝCÝ¸¢­uùB’JÏ§©eû‹
÷š©­v¦§­uø¥¬’­v¬ÑãÏÏ¦§Ï§©e­C ªøÏFðnì÷ÏJî…øöøäÝ‘­AùØ¾×¦ÞÏ@¸wðn¨‹ù£­uôi
ô¾­v®”ôs­Cõ_®hñNæL¦k®¾á÷ÏJüîðzÝ­¦§ INTO Ïl¾y­AÝbøäÝ‘÷ÏJ©ñNú|¾½ñ¥­C

Ýû¾~­AFixPak 3 ¾]õt¦§ðž¾¨æ{Ý­¾iøœ¾h÷ÏJ÷ˆ©’ôøÝW§ë®e® ¦§¶—Ïè÷û­CÏ™ÏFÝûðž¾¨æ{
Ý­­AñNæL¦køäÝ‘÷ÏJ­C
  ------------------------------------------------------------------------

22.56 Common Warehouse Metamodel (CWM) XML Ï„ï¸

¦¸¾¯ 7.2 CWM ÏuùÆôøùØ¾× Java Development Kit (JDK) 1.2.2 ¸× 1.3­C

ý{Ýb­Añz¾i¾HôžÏJÏ×ôž¾XÏUÝC CWM XML ¦®¾¢­G

ù„¾ÝüBýzæ{õ€¦§ñô©|ùB’J

ú¡ñzôž¾XõtÝüªYùB’J¦§üBýzæ{õ€­AÝà÷àùB’J¯P¾tÏ@üBýzæ{õ€ÏÏ¦§ùB’JÝüÇ”®Y (Ï@ðàñô
©|)­A üoùƒðàüBýzæ{õ€üœú|üQôž¾X¾Bù„Ç”®Yú|ùù§–@­C

Ýüñ›¾¢Ýaô¾Ý­ñ’ÝCÇ”®Y

ý{Ýb­Añz¾i¾HôžÏJÏ×ôž¾XùB’JÏõô­ÏœÝP¦§ô¾Ý­ñ’ÝCÇ”®Y­A¾]ªA CHILD­BSUCCESS­B
FAILURE Ï× UNCONDITIONAL­C

ðš·xùàú«õ@ªøúõýÏ¦¡¦®¾¢

ý{Ýb­Aú¡ñzôž¾X©­Añz¾i¾HñNðš·xùàú«¸w÷qªøúõýÏ¦¡¦®¾¢­C úõýÏ¦¡¦®¾¢¦§üBýzÏŠÝ­¯P
¦¡©‘¦®¾¢ªêÝP­C

SQLDataType ¾×¸¢¦«Ž‘¸MŽ‘Ý

ý{Ýb­Añz¾i¾HñN SQLDataType ¾×¸¢¦«Ž‘¸MŽ‘Ý­C

ªêÝP¦¡©‘¦§Ýhð®ªêÇ”ÝW§ë

ÝbôžÏJ¸×ôž¾Xïµô­­Añz¾i¾HÝüÝhð®ªêÇ”ÝW§ë­AªêÝP¦¡©‘¦§ùCÏ@ðàÝW§ëüœÝüÝêÏv¦§¦«Ž‘
û‹ªM­C

ús¦§ SAP ¸M WebSphere Site Analyzer (WSA) ùàú«Ï„ï¸

ús¬Wús¦§ùàú«Ï„ï¸¬ÑãÏõ® ­Aý{Ýbñz¾i¾Hôž¾X·xÝs¸¢ðš·xÏÏ¦§ SAP ¸M WSA ÷ˆøT­C
  ------------------------------------------------------------------------

22.57 üBýz¬ã®ªýœ¾Öóû

ñz¾i¾H«åóÆüBýz¬ã®ªýœ¾Öóû¨‹¾×øØÏjÏp­AùØ¾ÝýÝXñz¦§¨ÇûäÏjÏp­C ¨‹¾×øØÏW¦§ûØ¾šú|
ÝêøÒð®ús¸wÝÝšÝh¦«Ž‘¨‹¾×øØ­C

ú¡ñz®”Ï@ÏUªYðà¨‹¾×øØûØ¾š©­Añzú|Ýb¨‹¾×øØ¦®¾¢ÏWªíùÏ@ðà¬ÑÇD­C

ý{Ýb­Añz¾i¾H¶€¾¥¨‹ù£úõýÏ¦¡¾\î…¦¡ÏÏ¦§Æ¾šú~øÔÝW§ë¨‹ôæ­AùÞúà¦¡©‘¸M·©ž¦®¾¢¦§
ú~øÔÝW§ëùà·Óæ›¾ÝðÞ­C ñz¾‡¾i¶€¾¥¨‹ù£µY¸¤¨‹ôæùà«åóÆÝÒÏ·Ï¤ü]¸w­A¾HÏ×µYÏp¸×¸¤Ïj
üBýzæ{õ€úõýÏ¦¡­C

ðY¦®¾¢Ýb¨‹¾×øØÏ§ð®|­Añz¾i¾H®”Ï@ÏU¦®¾¢ñN¾ÝðÞ¸âÝš¨Çûäü¯§í­C Ýû¾~­A¦®¾¢ÝW§ëú|
¸ûÏUõ‚Ýùü\ÝhÝC¾H÷`ªë¨‹¾×øØ¦ô­­C

ñzý{Ýb¾i¾HùØ¾×õRøœµ„ùàýóøœ¦®¾¢­Cú¡·xÝsªYðàüBýzæ{õ€©­AÏ]ú|·xÝs¦¡©‘šõ¢­C ¨‹
óšÝ‘ªøÏœªOÝêøÒ¦§­CðYðnñqðš·xùàú«¸×¾¬ÑÏ×üBýzæ{õ€ÏÏýóøœªYðà¦¡©‘­B·©ž¸× úõýÏ
¦¡­Añz¾i¾H®”Ï@ÏUú’û®¾kµ„­AæM® ¨‹ù£ñqùàú«ýóøœøÒõ@ (ðY¦®¾¢Ý¸¢ðš·xùàú«ÏÏ)­A¸×
¨‹ù£ñq¾¬ÑýóøœøÒõ@ (ðY¦®¾¢Ý¸¢ðš·x¾¬ÑÏÏ)­C

ý{Ýb­Aï†¬ÑÆ¾š¨‹¾×øØ¨‹óš¦ª§A­CÝû¾~­A¦ª§AÝ‘Æ¾šï†¬Ñ¸ãÝb¦§¦®¾¢ÝW§ë­C
  ------------------------------------------------------------------------

22.58 §ä¾¬ã®ªýœ¾Öóû

ý{Ýb­Añz¾i¾HñN§ä¾¬ã®ªýœ¾ÖóûÏ§¦¡©‘µYÝšüÞÏpÏ×¸¤ÝšüÞÏj­C ú¡ñzñN¦¡©‘µYÝšüÞÏp
©­A¾ÝšÝùûØ¾š­CªøÏFõ¢§‰«TÆ¾š­A ñz¾i¾H®¾áÏ@ðàªP¦ª§ä¾õG÷m­C
  ------------------------------------------------------------------------

22.59 ¾ýðn¨‚ÏJŽ‘Ý

ý{Ýb­A­u÷ˆ©’ðš·xÏÏÏá­vû‹¾ýðn¦§Ž‘ÝÆ¾šªäÝƒÇ„©­C ªäÝƒÇ„©ïœ¨“ñz¸w÷q­u÷ˆ©’ðš
·xÏÏÏá­v¦®¾¢¸ã¯í¦§¾ýðn÷ˆøT­AùãÝp÷ˆ©’©wÝW§ë­BùØ¾×¦Þ ID ¸×üqÝ‘«X­C ú¡ñz¨‚ÏJ¾ý
ðn¦§÷ˆøT® ­AÇ„©®Kú|©›¾½­C
  ------------------------------------------------------------------------

22.60 ­u÷ˆ©’ðš·xÏÏÏá­væo©g¾x¾[ñj¾\î…

ú¡ñzñqæo©g¾x®¾á­u÷ˆ©’ðš·xÏÏÏá­v¦®¾¢©­Aú|©iô}óÏèóÐ¦ªæý§c­AÆ¾šús¦®¾¢¦§Ý
÷m­C
  ------------------------------------------------------------------------

22.61 ÝCÝLùB’J÷ˆøTù·©ž

ý{Ýb­Añz¾i¾HñNùB’J¦§ªêÇ”÷ˆøT (ùãÝp¾DÝ©øØø­Bùàú«¦¡©‘ÝW§ëÏ×¾¬Ñ¦¡©‘ÝW§ë) ÝC
ÝLÝšÏ†Ýr·­CðYðnÝCÝLùB’J÷ˆøTÝš·©ž­A «Ñ¾Hú’û®¾kµ„®”Ï@ÏUüBýz¬ã®ªýœ¾ÖóûÏÏ¦§ùB
’JûØ¾š­B®”Ï@ÏUÝCÝL --> ÝCÝLÝš·©ž­AæM® ®¸wñzðnÝCÝL÷ˆøT¦§·©žÝW§ë­C
  ------------------------------------------------------------------------

Data Warehouse Center Application Integration Guide(æLÏÏÏ†¦¸)

In Chapter 5. Metadata Templates, Table 16 describes Column tag tokens. The
information in the manual should state that "*ColumnPositionNumber" should
start with "1". The manual incorrectly gives "0" as the starting character.

Later in Chapter 5, in Table 42, the TableTypeIfFile token is required if
the type specified for the DatabaseType token in the corresponding
SourceDataBase.tag is ISV_IR_FFLan. If it is not specified, an error will
be detected.

In Chapter 6. Data Warehouse Center metadata, the description of the POSNO
column object property should be changed to:

   An index, starting with 1, of the column
   or field in the row of the table or file.

In Chapter 8. Information Catalog Manager object types, the directory where
you can find the .TYP files, which include the tag language for defining an
object type, has been changed to \SQLLIB\DGWIN\TYPES.
  ------------------------------------------------------------------------

23.1 Additional metadata templates

In Chapter 5, Metadata Templates, the following metadata templates should
be included.

Table 9. New Metadata templates supplied with the Data Warehouse Center
 Template                   Description        See:
 commit.tag                                    23.1.1, "Commit.tag"
 Foreignkey.tag                                23.1.2, ForeignKey.tag
 Foreignkeyadditional.tag                      23.1.3,
                                               ForeignKeyAdditional.tag
 Primarykey.tag                                23.1.4, PrimaryKey.tag
 Primarykeyadditional.tag                      23.1.5,
                                               PrimaryKeyAdditional.tag

23.1.1 Commit.tag

Use this template to improve performance when you are using large tag
language files. A commit template can be inserted between any of the groups
of templates described here. A commit template cannot be inserted between
templates within a group. For example, it is valid to insert a commit
template between AgentSite.tag and VWPGroup.tag but invalid to insert a
commit tag between VWPProgramTemplate.tag and
VWPProgramTemplateParameter.tag. If commit templates are used incorrectly,
import may report an error.

   * AgentSite.tag
   * VWPGroup.tag
   * VWPProgramTemplate.tag, VWPProgramTemplateParameter.tag
   * SourceDatabase.tag
   * WarehouseDatabase.tag
   * Table.tag, Column.tag
   * SubjectArea.tag
   * Process.tag
   * Step.tag, StepInputTable.tag, StepOutputTable.tag,
     StepVWPOutputTable.tag, StepVWPProgramInstance.tag,
     VWPProgramInstanceParameter.tag
   * StepCascade.tag
   * StarSchema.tag, StarSchemaInputTable.tag
   * PrimaryKey.tag, PrimaryKeyAdditional.tag
   * ForeignKey.tag, ForeignKeyAdditional.tag

The use of the commit template is optional.

23.1.1.1 Tokens

Table 10 provides information about each token in the template.

Table 10. Commit.tag tokens
 Token                 Description            Allowed values
                          Relationship parameters
 *CurrentCheckPointID++An index, starting     A numeric value.
                       with 0, that increases
                       each time it is
                       substituted in a
                       token.

                       This token is
                       required.

23.1.1.2 Examples of values

Table 11 provides example values for each token to illustrate the kind of
metadata you might provide for each token.

Table 11. Example values for Commit.tag tokens
 Token                                Example value
 *CurrentCheckPointID++               1

23.1.2 ForeignKey.tag

Use this template to define foreign key constraints on tables. The
ForeignKey.tag template defines the relationships to the table and the
column on which the constraint is being defined. This template also defines
the relationships to the table and column of the primary key that is being
referred to. Before you use the ForeignKey.tag template, you must define
the primary key constraint (using the PrimaryKey.tag template) and the
tables and columns (using the Table.tag and Column.tag templates) on which
you want to define the foreign key constraint.

23.1.2.1 Tokens

Table 12 provides information about each token in the template.

Table 12. ForeignKey.tag tokens
 Token                    Description           Allowed values
                             Entity parameters
 *ConstraintName          The name of the       A text string, up to 80
                          constraint.           bytes in length.

                          The name must be
                          unique within a
                          table or field.

                          This token is
                          required.
 *ForeignColumnKeyName    Name of the column    A text string, up to 254
                          on which the foreign  bytes in length.
                          key constraint is
                          being defined.
 *ForeignKeyID            The key that          A numeric value.
                          uniquely identifies
                          the foreign key. The
                          key must be unique
                          from all other keys
                          in the tag language
                          file.

                          Tip: Finish
                          processing the
                          ForeignKey.tag
                          template before
                          increasing the value
                          of the key.

                          This token is
                          required.
 *MapID                   An arbitrary number   A numeric value.
                          that is unique from
                          all other keys in
                          the interchange
                          file.

                          Tip: Finish
                          processing the
                          ForeignKey.tag
                          template before
                          increasing the value
                          of this token.

                          This token is
                          required.
 *PrimaryColumnKeyName    The column name of    A text string, up to 80
                          the referenced        bytes in length.
                          column.
 *ReferencedPrimaryKeyID  The key that          A numeric value.
                          uniquely identifies
                          the primary key. The
                          key must be unique
                          from all other keys
                          in the tag language
                          file.

                          Tip: Finish
                          processing the
                          ForeignKey.tag
                          template before
                          increasing the value
                          of the key.

                          This token is
                          required.
                          Relationship parameters
 *DatabaseName            The business name of  A text string, up to 40
                          the warehouse source  bytes in length.
                          or warehouse target.

                          This token is
                           required.
 *ForeignTablePhysicalNameThe database-defined  A text string, up to 254
                          name of the physical  bytes in length.
                          table containing the
                          foreign keys that
                          reference the keys
                          in other tables.
 *PrimaryTablePhysicalNameThe database-defined  A text string, up to 80
                          name of the physical  bytes in length.
                          table containing the
                          keys that are
                          referenced by the
                          foreign keys.
 *PrimaryTableOwner       The owner,            A text string, up to 128
                          high-level            bytes in length.
                          qualifier,
                          collection, or
                          schema of the table
                          that contains the
                          primary key column
                          that is being
                          referenced.

                          This token is
                          required.
 *ForeignTableOwner       The owner,            A text string, up to 128
                          high-level            bytes in length.
                          qualifier,
                          collection, or
                          schema of the table
                          that contains the
                          foreign key
                          constraint column.

                          This token is
                          required.

23.1.2.2 Examples of values

Table 13 provides example values for each token to illustrate the kind of
metadata that you might provide for each token.

Table 13. Example values for ForeignKey.tag tokens
 Token                                Example value
 *ConstraintName                      Department
 *DatabaseName                        Finance Warehouse
 *ForeignColumnKeyName                Country_code
 *ForeignKeyID                        07011
 *ForeignTablePhysicalName            Geography
 *MapID                               02568
 *PrimaryColumnKeyName                State_code
 *Referenced PrimaryKeyID             Name
 *PrimaryTablePhysicalName            City
 *PrimaryTableOwner                   DB2ADMIN
 *ForeignTableOwner                   IWH

23.1.3 ForeignKeyAdditional.tag

Use this template to define a composite foreign key. Before you use the
ForeignKeyAdditional.tag template, you must define a constraint (using the
ForeignKey.tag template) on the first column. You can then add columns by
using this template for each column that you want to add.

23.1.3.1 Tokens

Table 14 provides information about each token in the template.

Table 14. ForeignKeyAdditional.tag tokens
 Token                    Description               Allowed values
                             Entity parameters
 *ForeignColumnKeyName    The name of the column on A text string, up to
                          which the foreign key     80 bytes in length.
                          constraint is being
                          defined.
 *ForeignKeyID            The key that uniquely     A numeric value.
                          identifies the foreign
                          key. The key must be
                          unique from all other
                          keys in the tag language
                          file.

                          Tip: Finish processing
                          the ForeignKey.tag
                          template before
                          increasing the value of
                          the key.

                          This token is required.
 *MapID                   An arbitrary number that  A numeric value.
                          is unique from all other
                          keys in the interchange
                          file.

                          Tip: Finish processing
                          the
                          ForeignKeyAdditional.tag
                          template before
                          increasing the value of
                          this token.

                          This token is required.
 *MapSeqNo                A number signifying each  Unique, increasing,
                          additional column added   consecutive number
                          as part of a composite    starting at 2.
                          key to the foreign key
                          constraint.
 *PrimaryColumnKeyName    The column name of the    A text string, up to
                          referenced column.        80 bytes in length.
                          Relationship parameters
 *DatabaseName            The business name of the  A text string, up to
                          warehouse source or       40 bytes in length.
                          warehouse target.

                          This token is required.
 *ForeignTablePhysicalNameThe database-defined name A text string, up to
                          of the physical table     80 bytes in length.
                          containing the foreign
                          keys that reference the
                          keys in other tables.
 *PrimaryTablePhysicalNameThe database-defined name A text string, up to
                          of the physical table     80 bytes in length.
                          containing the keys that
                          are referenced by the
                          foreign keys.
 *PrimaryTableOwner       The owner, high-level     A text string, up to
                          qualifier, collection, or 128 bytes in length.
                          schema of the table that
                          contains the primary key
                          column that is being
                          referenced.

                          This token is required.
 *ForeignTableOwner       The owner, high-level     A text string, up to
                          qualifier, collection, or 128 bytes in length.
                          schema of the table that
                          contains the foreign key
                          constraint column.

                          This token is required.

23.1.3.2 Examples of values

Table 15 provides example values for each token to illustrate the kind of
metadata that you might provide for each token.

Table 15. Example values for ForeignKeyAdditional.tag tokens
 Token                                Example value
 *DatabaseName                        Finance Warehouse
 *ForeignColumnKeyName                Country_code
 *ForeignKeyID                        07011
 *ForeignTablePhysicalName            Geography
 *MapID                               22578
 *MapSeqNo                            2
 *PrimaryColumnKeyName                State_code
 *PrimaryTablePhysicalName            City
 *PrimaryTableOwner                   DB2ADMIN
 *ForeignTableOwner                   IWH

23.1.4 PrimaryKey.tag

Use this template to define primary key constraints on tables. The template
also defines the relationships to the table and the column on which the
constraint is being defined. Before you use the PrimaryKey.tag template,
you must define the tables and columns (using the Table.tag and Column.tag
templates) on which you want to define the primary key constraint.

23.1.4.1 Tokens

Table 16 provides information about each token in the template.

Table 16. PrimaryKey.tag tokens
 Token                 Description                  Allowed values
                             Entity parameters
 *ColumnName           The name of the       A text string, up to 80 bytes
                       column or field.      in length.

                       The name must be
                       unique within a
                       table or field.

                       This token is
                       required.
 *MapID                An arbitrary number   A numeric value.
                       that is unique from
                       all other keys in
                       the interchange
                       file.

                       Tip: Finish
                       processing the
                       PrimaryKey.tag
                       template before
                       increasing the value
                       of this token.

                       This token is
                       required.
 *PrimaryKeyID         The key that          A numeric value.
                       uniquely identifies
                       the primary key. The
                       key must be unique
                       from all other keys
                       in the tag language
                       file.

                       Tip: Finish
                       processing the
                       ForeignKey.tag
                       template before
                       increasing the value
                       of the key.

                       This token is
                       required.
                          Relationship parameters
 *DatabaseName         The business name of  A text string, up to 40 bytes
                       the warehouse source  in length.
                       or warehouse target.

                       This token is
                       required.
 *TableOwner           The owner,            A text string, up to 128
                       high-level            bytes in length.
                       qualifier,
                       collection, or
                       schema of the table
                       that contains the
                       column.

                       This token is
                       required.
 *TablePhysicalName    The physical name of  A text string, up to 80 bytes
                       the table or file     in length.
                       that contains the
                       column as defined to
                       the database manager
                       or file system.

                       This token is
                       required.

23.1.4.2 Examples of values

Table 17 provides example values for each token to illustrate the kind of
metadata that you might provide for each token.

Table 17. Example values for PrimaryKey.tag tokens
 Token                                Example value
 *ColumnName                          Country_code
 *DatabaseName                        Finance Warehouse
 *MapID                               54627
 *PrimaryKeyID                        74622
 *TableOwner                          DB2ADMIN
 *TablePhysicalName                   GEOGRAPHY

23.1.5 PrimaryKeyAdditional.tag

Use this template to define a composite primary key. Before you use the
PrimaryKeyAdditional.tag template, you must define a constraint on the
first column by using the PrimaryKey.tag template. Any additional columns
can then be added using this template. The template also relates the
additional primary keys to the first primary key which is defined using
PrimaryKey.tag.

23.1.5.1 Tokens

Table 18 provides information about each token in the template.

Table 18. PrimaryKeyAdditional.tag tokens
 Token                 Description               Allowed values
                             Entity parameters
 *ColumnName           The name of the column or A text string, up to 80
                       field.                    bytes in length.

                       The name must be unique
                       within a table or field.

                       This token is required.
 *FirstPrimaryKeyID    The key that uniquely     A numeric value.
                       identifies the primary
                       key. The key must be
                       unique from all other
                       keys in the tag language
                       file.

                       Tip: Finish processing
                       the ForeignKey.tag
                       template before
                       increasing the value of
                       the key.

                       This token is required.
 *MapID                An arbitrary number that  A numeric value.
                       is unique from all other
                       keys in the interchange
                       file.

                       Tip: Finish processing
                       the
                       PrimaryKeyAdditional.tag
                       template before
                       increasing the value of
                       this token.

                       This token is required.
 *MapSeqNo             A number signifying each  Unique, increasing,
                       additional column added   consecutive number
                       as part of a composite    starting at 2.
                       key to the primary key
                       constraint.
                          Relationship parameters
 *DatabaseName         The business name of the  A text string, up to 40
                       warehouse source or       bytes in length.
                       warehouse target.

                       This token is required.
 *TableOwner           The owner, high-level     A text string, up to 15
                       qualifier, collection, or bytes in length.
                       schema of the table that
                       contains the column.

                       This token is required.
 *TablePhysicalName    The physical name of the  A text string, up to 80
                       table or file that        bytes in length.
                       contains the column as
                       defined to the database
                       manager or file system.

                       This token is required.

23.1.5.2 Examples of values

Table 19 provides example values for each token to illustrate the kind of
metadata that you might provide for each token.

Table 19. Example values for PrimaryKeyAdditional.tag tokens
 Token                                Example value
 *ColumnName                          Country_code
 *DatabaseName                        Finance Warehouse
 *MapID                               99542
 *MapSeqNo                            2
 *FirstPrimaryKeyID                   07801
 *TableOwner                          DB2ADMIN
 *TablePhysicalName                   GEOGRAPHY
  ------------------------------------------------------------------------

÷ˆ©’ðš·xÏÏÏá«uÏW¯­¸£

  ------------------------------------------------------------------------

24.1 ¸w÷qõê¬g¦§¦¡©‘¸×úõýÏ¦¡

ùØ¾× DB2 ññùŒÏÏÏá¸w÷qõê¬g¦§¦¡©‘¸×úõýÏ¦¡Ïõ® ­AÏ~î…üQ÷ˆ©’ðš·xÏÏÏáú¡õ@õê¬gùàú«
ùØ¾×­C
  ------------------------------------------------------------------------

24.2 øäÝ‘ùÆÝü AS/400 ¾Nýzæ{Ý­¦§ Essbase VWPs

øäÝ‘ùÆÝü AS/400 ¾Nýzæ{Ý­¦§ Essbase VWPs­AARBORLIB ¸M ARBORPATHB ¾ýôúüQü]¸w
ªø *sys ·“ûãš¬’­CùØ¾×¦Þ ID ¾ýôúÝü *jobctl vððÏ~î…ôiÝ‘ü]¸w­Cüoù€·“ûãš¬’¯í
ðn®ÝVÏwÝw÷Ó Essbase ¦§·©ž©w­C
  ------------------------------------------------------------------------

24.3 ùØ¾×Ï«õG÷ˆ©’ðš·xÏÏÏáïyðz÷ˆ©’æ›æ­Ï×ÏwæýÝX¦§Ï§©eæ›æ­

Ýbõ@ú~¯­¸£¦§ùB’J 10 ÏÏ­AÝüÏ@ðà«dùã¦ª§AªOüo¬Ó¦§­G Ýp¦Gñz®¸wððùŒðÔ 1 (ððùŒóÐ
¦ªæý§c¬hÝ÷¦§¦®¾¢) ùÇÏ«õGüBýzæ{õ€­A ®h¾uÏ«õG¯PÆ¾š÷àüBýzæ{õ€¦§ 1 ùB’J­C Ýb¸ã
Ýü¦ª¦pÏU­AÝû«dùãªOÏœ¾¨«T¦§­CùB’J 8 ýŽÏGðàôæ¾ý÷û¦§ôæ¾ÏÏ­AýŽÏ@ôæüîðzÝ­ªOÏœ
¾¨«T¦§­C¾Ý·ü÷àªø­u®”Ï@ÏU¦«Ž‘¬hÝ÷¾Hýœ¾Ö÷ˆøT®ª¨ìùàú«¦«Ž‘¸M¾¬Ñ¦«Ž‘Ïõô­¦§¶…ï®
¦®¾¢­v­C
  ------------------------------------------------------------------------

24.4 ¾~ùàµ„

­u¾~ùàµ„­vÝb«uÏW¯­¸£¦§÷ˆ©’·üªø­uðš·x¾~ùàµ„­v­C
  ------------------------------------------------------------------------

24.5 õê¬gæõøO¾¯

­u¸w÷qõê¬gæõøO¾¯­vÝb«uÏW¯­¸£¦§÷ˆ©’·üªø­uõê¬gùB’JæõøO¾¯­v­C
  ------------------------------------------------------------------------

24.6 ôžÏJ¬Ñ¾š¯yù¾

ôžÏJ¬Ñ¾š¯yù¾«uÏW¯­¸£­Gôæ¾ý÷ûÝC¾šÆ¾šñ`æo¾Ö¦§ð®ðn¨—¯~­Aù„ÏÏÏ@ôæªø­uôžÏJ¦§
¬Ñ¾š¯yù¾·©žùSÝüóAú¡Ýaôž¾X­v­C Ýûôæ¾ÏœóA¾×¸¢Ï@î‰¨‚ÏJ¨—¯~¦§ÝC¾š­C
  ------------------------------------------------------------------------

24.7 ús¬W÷ˆ©’¦§Çæý

Ýb«uÏW¯­¸£¦§"ús¬W÷ˆ©’"¾DÇDÏÏ­A ­uús¬Wùàú«¦¡©‘ùæ{õ€­vÏ×­uús¬W¾¬Ñ¦¡©‘ùæ{
õ€­v¾DÇD¦§ÇæýÏÏ¶_­Cñz¾i¾HÝb¯­¸£îµÏèÏÏõ„ùüoù€¾DÇD­C
  ------------------------------------------------------------------------

24.8 ôžÏJ¦¡©‘

¯­¸£¾DÇD­uôžÏJùàú«¦¡©‘Ï×úõýÏ¦¡ùðš·xùàú«ÏÏ­vÏ× ­uôžÏJ¾¬Ñ¦¡©‘ùðš·x¾¬ÑÏÏ­v
û‹¸¢÷U¾×ÝrÏ÷ÝüæêÏœ¾¨«T¦§ïyðz­C¾yÏlªø­G

   ùãÝp­AXYZ* ú|ô€Ý^§ä¾ªO¾Hüoù€ÝrÏ÷ô}·Y¦§¦¡©‘Ï×úõýÏ¦¡­C

·üõ‹ªø­G

   ùãÝp­AXYZ% ú|ô€Ý^§ä¾ªO¾Hüoù€ÝrÏ÷ô}·Y¦§¦¡©‘Ï×úõýÏ¦¡­C

  ------------------------------------------------------------------------

24.9 RUNSTATS ¸M REORGANIZE TABLE «uÏW¯­¸£ôøÝX

üoù€Ï«¾×æ{Ý­¦§«uÏW¯­¸£­A®¾šðnøäÝ‘ý×ðp¦§¦¡©‘­A¸×ªO¯íðnð®ýå¦§¦¡©‘­A¾ýôú¸Mùà
ú«Ï×¾¬ÑÇæý­C¾¥¸¢ùB’J¬gÏJùàú«­Añz¾u¯íðnÇæýùB’J¸Mùàú«­C
  ------------------------------------------------------------------------

24.10 ­uüq¦ó­vðôðñ­A­uðš·xÏ§©e­v¯P­uñ’æ{­væõøO¾¯

Ýb­uðš·xÏ§©e­væõøO¾¯¦§­uüq¦ó­vðôÏÏ¬gûD­G

   ­uô€øe¦Þ­v¨‚ÏJŽ‘Ý¦§ø_¸lü]¸wðÔªø <current user's logon ID> ÝrÝˆ­C

·üšõ¢ªø­G

  ­uô€øe¦Þ­v¨‚ÏJŽ‘Ý¦§ø_¸lü]¸wðÔªø <current logon user email address> ÝrÝˆ­C

Ýb­uñ’æ{­væõøO¾¯¦§­uüq¦ó­vðôÏÏ­Aô€øe¦Þú|ø_¸lü]¸wÝù­uðš·xÏ§©e­væõøO¾¯ÏÏ¦§ü]
¸wðÔ­CðYæLü]¸wðÔ­A®Kú|ñN÷àðÔü]¸wÝù¾®eænÏJÏõùØ¾×¦Þ¦§ûqÏlôl¾¢Ýaõ}­CðYõ„Ïœù
÷àænÏJùØ¾×¦Þ¦§ûqÏlôl¾¢Ýaõ}­A®Kú|ñNù„ü]¸wªøænÏJùØ¾×¦Þ¦§ùØ¾×¦Þ ID­C
  ------------------------------------------------------------------------

24.11 ­u¾Nýzæ{Ý­§í­væõøO¾¯¦§¾Nýzæ{Ý­¬ãýåŽ‘Ý

ðš·x¾Nýzñ`ónæ{Ý­ýœ¾Öðš·x¾Nýzæ{Ý­©­A­u¾Nýzæ{Ý­§í­væõøO¾¯¦§¾Nýzæ{Ý­¬ãýåŽ‘Ý
ïœù¥øäÝ‘æ{Ý­¦§ÝW§ë­CÏœðnšõ¢Ž‘Ý¦§ÝW§ë­Aøœ®D IBM ðnùDñzðnüo¯•øæ­C
  ------------------------------------------------------------------------

DB2 OLAP Starter Kit

IBM DB2 OLAP Starter Kit 7.2 ÝbÏ@ù€õ@ú~ùtý×ÏW¬W¾[ Oracle­BMS-SQL­BSybase Ï×
Informix Ç”µpÝ­÷ˆ©’©w§èýzùtý× (RDBMS) ¦§Ï„ï¸­C ¦¸¾¯ 7.2 ¾]õt¸ãÝüÏ„ï¸¦§
RDBMS ¦§ Script ¸MÏuùÆ­A¾]ªA DB2­C ¾ÝðÞÝüÏ@ù€ððùŒ­A÷âýà÷ˆøT«Ñø¥ó\25.8, Ïw¦ó
øíÇD¯PððùŒ­C

DB2 OLAP Starter Kit for DB2 Universal Database ¦¸¾¯ 7.2 ¦§¦AøÔæ{Ý­æ¾îªêú¡
¸¢ Hyperion Essbase 6.1 ðž÷æ{Ý­ 2 ¾[ÏW Hyperion Integration Server 2.0 ðž
÷æ{Ý­ 2­C
  ------------------------------------------------------------------------

25.1 OLAP Server §“î÷

ðY¯í DB2 OLAP Starter Kit üÞús¦§Ýw÷ÓÏ×ùØ¾×îæüZ­A «ÑüyüX DB2 OLAP Server §“
î÷¦§ Library §“ðô­G

http://www.ibm.com/software/data/db2/db2olap/library.html
  ------------------------------------------------------------------------

25.2 Ï„ï¸¦§õ@ú~ùtý×¦AøÔæ{Ý­æ¾î

OLAP Starter Kit for Version 7.2 ¦§Ý›¦AóûÏ÷¾¢Ï„ï¸ÏUÝCõ@ú~ùtý×¸M¦AøÔæ{Ý­æ¾
î­G

   * Ýw÷Ó SP 5 ¦§ Windows NT 4.0 ¯P Windows 2000
   * AIX ¦¸¾¯ 4.3.3 ¸×¾HÏW
   * Solaris õ@ú~ùtý×¦¸¾¯ 2.6­B7 ¯P 8 (Sun OS 5.6­B5.7 ¸× 5.8)

ñqŽíî÷Ï÷¾¢øäÝ‘¸¢ Windows 95­BWindows 98­BWindows NT 4.0 SP5 ¯P Windows
2000­C
  ------------------------------------------------------------------------

25.3 õûÝù DB2 OLAP Starter Kit Ýb UNIX ÏW¦§Ýw÷Ó

Ýw÷Ó DB2 OLAP Starter Kit «ÑùÞúà DB2 Universal Database for UNIX ¦§Ýw÷Óø•¾¯
æ{õ€ôiÝ‘­C ýœ®~·©žú|¾¥Ýw÷Óæ{Ý­¸¤ùùtý×¾¨ì­G (AIX: /usr/lpp/db2_07_01­F
Solaris: /opt/IBMdb2/V7.1)­C

®¾á©žùã¦§ô¾ªq­Aú|®¾áùƒðà DB2 OLAP ¾¨ì (essbase ¯P is) Ý¸¢©žùãùØ¾×¦Þø_¸l
¾¨ìÏU sqllib¦§¾¨ìÏU­CÝPÏ@©ô­óöóûôÔÏûü\øäÝ‘Ï@ðà OLAP Ý›¦Aóû©žùã­C ðYðnõû
ÝùÝw÷Ó­AùØ¾×¦Þ¾ýôúÏƒøÒü]¸w is/bin ¾¨ì­A Ý]ªø¾ÝæL¦kÇæýùùtý×¦§ is/bin ¾
¨ì­C¾Ý¾ýôúÇæýù©žùã¦§ø_¸l¾¨ìÏU¦§¾i¬gÏJ¾¨ì­C

ðYðnõûÝùÝb Solaris ÏW¦§Ýw÷Ó­A«Ñ¾H©žùã ID ænÏJÏµï®ù sqllib/is ¾¨ì­A æM® ¨‚
ÏJÏUÝC®¾O­G

rm bin
mkdir bin
cd bin
ln -s /opt/IBMdb2/V7.1/is/bin/ismesg.mdb ismesg.mdb
ln -s /opt/IBMdb2/V7.1/is/bin/olapicmd olapicmd
ln -s /opt/IBMdb2/V7.1/is/bin/olapisvr olapisvr
ln -s /opt/IBMdb2/V7.1/is/bin/essbase.mdb essbase.mdb
ln -s /opt/IBMdb2/V7.1/is/bin/libolapams.so libolapams.so

  ------------------------------------------------------------------------

25.4 ª[§c OLAP Starter Kit ¦§ ODBC

IBM DB2 OLAP Starer Kit 7.2 ¯íðnÏ@ðà ODBC.ini ·©ž­A ì ODBC õ@ú~ñq OLAP
Integration Server üsñæÝšÇ”µpÝ­÷ˆ©’ùàú«¸M­uOLAP ïyðz÷ˆ©’®ª¨ì­v­C

   * Ýb Windows ùtý×ÏW­AÝû·©žÝ¸¢ùtý×æn¨ì¦§
     HKEY_LOCAL_MACHINE/SOFTWARE/ODBC Ï§­C «ÑùØ¾× ODBC Data Source
     Administrator ùà·xÝsÝüÇ”ÝpÝ¢üsñæÝšÇ”µpÝ­÷ˆ©’ùàú«¦§÷ˆøT­C
   * Ýb UNIX ùtý×ÏW­AÝw÷Óæ{Ý­®¾áÏ@ðà¬ã®ª· odbc.ini­Cñì·xÝsÝüÇ”ÝpÝ¢üsñæÝš
     Ç”µpÝ­÷ˆ©’ùàú«¦§÷ˆøT­A«ÑùØ¾×ñzüáÝn¦§«s¨Šóûùà«s¨ŠÝû·©ž­C

Ýû ODBC.ini ·©ž¾¥ ODBC ün‚©M¾¢ïœù¥­A¾‡Ï§õt¸¢ Microsoft Office ün‚Ï§­CÇ”
¸¢¾iÝw÷Ó ODBC XøÒæ{Ý­¸× ODBC §èýzæ{Ý­¦§·ü¾×æ{Ý­¦§÷âýà÷ˆøT­A«ÑüyüXÏUÝC§“
î÷­G http://support.microsoft.com/support/kb/articles/Q113/1/08.asp­C

AIX óöóûÏW¦§ Oracle ùØ¾×¦Þ­Gñìª[§c ODBC for Oracle­Añz¾ýôúõ¢ús ODBC.ini ·
©žùà®ÝV MERANT 3.6 XøÒæ{Ý­­C

Ýb¦¸¾¯ 7.2 ÏÏ­AOLAP Starter Kit §èýz ODBC üs«uùàüsñæÝšÇ”µpÝ­÷ˆ©’ùàú«¸M
­uOLAP ïyðz÷ˆ©’®ª¨ì­v­CªøÏFÏ„ï¸üoù€ ODBC üsñæ­A OLAP Starter Kit Ýb Windows
NT 4.0­BWindows 2000­BAIX Ï× Solaris ÏWùØ¾× ODBC XøÒæ{Ý­­C

   * DB2 Universal Database ¦¸¾¯ 6 ÷ˆ©’©wñqŽíî÷­G Ýb Windows NT 4.0 SP5 ¸×
     Windows 2000­BAIX 4.3.3 Ï× Solaris õ@ú~ùtý× 2.6­B7 ¸× 8 (Sun OS 5.6­B
     5.7 ¸× 5.8)ÏWªO DB2 ¦¸¾¯ 6 ODBC XøÒæ{Ý­­C
   * DB2 Universal Database 7.1 ÷ˆ©’©wñqŽíî÷­G Ýb Windows NT 4.0 SP5 ¸×
     Windows 2000­BAIX 4.3.3 Ï× Solaris õ@ú~ùtý× 2.6­B7 ¸× 8 (Sun OS 5.6­B
     5.7 ¸× 5.8) ÏWªO DB2 ¦¸¾¯ 7 ODBC XøÒæ{Ý­­C
   * Oracle 8.04 ¸M 8i SQL*Net 8.0 ÷ˆ©’©wñqŽíî÷­G Ýb Windows NT 4.0 SP5 ¸×
     Windows 2000­BAIX 4.3.3­BSolaris õ@ú~ùtý× 2.6­B7 ¸× 8 (Sun OS 5.6­B5.7
     ¸× 5.8) ÏWªO MERANT 3.6 ODBC XøÒæ{Ý­­C
   * MS SQL Server 6.5.201 (Ïœ¯íðn­u÷ˆ©’©wñqŽíî÷­v)­GÝb Windows NT 4.0 SP5
     ¸× Windows 2000 ÏWªO MS SQL Server 6.5 ODBC XøÒæ{Ý­­C
   * MS SQL Server 7.0 (Ïœ¯íðn­u÷ˆ©’©wñqŽíî÷­v)­GÝb Windows NT 4.0 SP5 ¸×
     Windows 2000 ÏWªO MS SQL Server 7.0 ODBC XøÒæ{Ý­­C

25.4.1 Ýb UNIX ùtý×ª[§c÷ˆ©’ùàú«

Ýb AIX ¸M Solaris ÏW­Añz¾ýôúÏƒøÒü]¸w ODBC ¦§·“ûãš¬’­AùÇ«s¨Š odbc.ini ·©ž
ùàª[§cÇ”µpÝ­÷ˆ©’ùàú«¸M­uOLAP ïyðz÷ˆ©’®ª¨ì­v­CðYñzús¬W¸×šõ¢XøÒæ{Ý­¸×÷ˆ©’ùà
ú«­A «ÑøÔ¾ý«s¨Š odbc.ini ·©ž­C

25.4.1.1 ª[§c ODBC ·“ûãš¬’

Ýb UNIX ùtý×ÏW­Añz¾ýôúü]¸w·“ûãš¬’Ï~î…Ýsù£ ODBC ©™ÏáÏ÷¾¢­CStarter Kit ø_¸l
¾¨ìÏÏïœù¥ is.sh ¸M is.csh Shell Script ùàü]¸w¾ýðn¦§š¬’­C ÝbùØ¾× ODBC ùàüs
ñæ÷ˆ©’ùàú«Ïõ®e­Añz¾ýôúøäÝ‘ù„ÏÏÏ@ðà Script­C û‹¸¢ñz¾×ùàøäÝ‘ OLAP Starter Kit
¦§ùØ¾×¦ÞÝW§ë­Añz·ü÷àÝbænÏJ Script ÏÏ¾]õtüoù€ Script­C

25.4.1.2 «s¨Š odbc.ini ·©ž

ñì¸¢ odbc.ini ·©žÏÏª[§c÷ˆ©’ùàú«­Añz¾ýôúús¬W ODBC ÷ˆ©’ùàú«¦§ÝW§ë¸M¯­¸£­A Ýb
ñzøwû‹Ýû÷ˆ©’ùàú«ÝW§ë¸ã®¾á¦§øØªqÏÏïœù¥ ODBC XøÒæ{Ý­÷“©|­B·ÝWÏ×ù„¾LXøÒæ{
Ý­ü]¸wðÔ­C Ýw÷Óæ{Ý­Ýb ISHOME ¾¨ìÏÏÝw÷ÓÏ@ðà«dùã· odbc.ini­C Ýû·©ž¾]õtüq¾×
ODBC üsñæ¸M¸ãÏ„ï¸¦§ ODBC XøÒæ{Ý­¦§ª[§c÷ˆøT­C «ÑùØ¾×Ýû·©žøæªøø_¶I­AñNñzùØ
¾×¦§ ODBC XøÒæ{Ý­û‹ªMÝšÇ”µpÝ­÷ˆ©’ùàú«¸M­uOLAP ïyðz÷ˆ©’®ª¨ì­v­C

ðYñzùØ¾×¦§·©žÏœªO odbc.ini­A «ÑñN ODBCINI ·“ûãš¬’ü]¸wÝùñzùØ¾×¦§·ÝW­C

25.4.1.3 ús¬W÷ˆ©’ùàú«ù odbc.ini ·

  1. ÝbøäÝ‘ OLAP Starter Kit Ý›¦Aóû¦§ùtý×ÏW­A«ÑùØ¾×«¥Ýp vi ¦§Ï†Ýr«s¨Šæ{Ý­ùà
     ô}ñã odbc.ini ·©ž­C
  2. õ„ù [ODBC Data Sources] ªøð§¦§øØªq­Aús¬WÏ@Ý‘÷ˆ©’ùàú«ÝW§ë¸M¯­¸£­A ùã
     Ýp­G mydata=data source for analysis­CªøÏFµžõKýVýc­A÷ˆ©’ùàú«¦§ÝW§ë·ü÷à
     ýÝX RDBMS ÏÏ¦§÷ˆ©’©wÝW§ë­C
  3. ús¬WÏ@Ý‘¾HÏŠªA¸úõtªAús÷ˆ©’ùàú«¦§ÝW§ë­AùãÝp [mydata]­AÝb·©žÏÏús¬WÏ@ðà
     ús¦§øØªq­C
  4. Ýb÷ˆ©’ùàú«ÝW§ëñæÏUùà¦§ïXÝ‘ÏÏ­Aús¬WÝû÷ˆ©’ùàú«ÝW§ëÏ×¾“Ý¢¾ýðn¦§ ODBC XøÒ
     æ{Ý­÷ˆøT¸ã¯í¦§ ODBC XøÒæ{Ý­ÏõõûóÆ÷“©|¸M·©žÝW§ë­C ©éóéÏUÝCïX÷`¸ã¾š¦§
     «dùãùàû‹ªMÝšñz RDBMS ÏW¦§÷ˆ©’ùàú«­C «Ñ«T¸w ODBC XøÒæ{Ý­·©ž«TûˆÝsÝb¸¢
     ñzÝb Driver= ü]¸wÏÏ®¸w¦§Ý÷m­C
  5. ú¡ñz«s¨Š odbc.ini õûÝù® ­A«Ñ·xÝs·©ž­Aæýõ“Ï†Ýr«s¨Šæ{Ý­­C

25.4.1.4 ODBC ¦§ DB2 ü]¸wðÔ«dùã

ÏUÝC«dùãÆ¾šÝpÝ¢«s¨Š odbc.ini­AùØ¾× IBM DB2 ð¸l ODBC XøÒæ{Ý­ùàüsñæÝš AIX
ÏW¦§ DB2 Universal Database ¦¸¾¯ 6.1 ¦§Ç”µpÝ­÷ˆ©’ùàú« db2data­C Ýb vi «s¨Š
óûÏÏ­AùØ¾× $ODBCINI ®¾Oùà«s¨Š odbc.ini­A ùÇï­ÏJÏUÝCüîðzÝ­­G

     [ODBC Data Sources]
     db2data=DB2 Source Data on AIX
     ...
     [db2data]
     Driver=/home/db2inst1/sqllib/lib/db2.o
     Description=DB2 Data Source - AIX, native

25.4.1.5 ODBC ¦§ Oracle ü]¸wðÔ«dùã

¾HÏU«dùã¯­¸£ÝpÝ¢«s¨Š odbc.ini­AùØ¾× MERANT Version 3.6 ODBC XøÒæ{Ý­ùàüsñæ
Ýš Oracle ¦¸¾¯ 8 (Ýb Solaris) ¦§Ç”µpÝ­÷ˆ©’ùàú« oradata­C Ýû«dùãÏÏ­ALogonID
¸M Password ¾H OLAP Starter Kit ùØ¾×¦ÞÝW§ë¸MüqÝ‘«X¦§ûˆ¯éðÔùàô¤ÏJ­C

     [ODBC Data Sources]
     oradata=Oracle8 Source Data on Solaris
     ...
     [myoracle] Driver=
     /export/home/users/dkendric/is200/odbclib/ARor815.so
     Description=my oracle source

25.4.2 Ýb UNIX ùtý×ÏWª[§c OLAP ïyðz÷ˆ©’®ª¨ì

Ýb AIX ¸M Solaris ÏWª[§c OLAP Metadata Catalog ÇçÝª[§cÏ@ðà÷ˆ©’ùàú«­C ðYðn
OLAP Metadata Catalog ÷ˆ©’©w­A«ÑÝb odbc.ini ·©žÏÏús¬WÏ@ðà÷ˆ©’ùàú«ÝW§ë¸MøØ
ªq­A Ýp 25.4.1.2, «s¨Š odbc.ini ·©ž ¸ãðz­CÏœ¯íðnù„¾Ýšõ¢­C

ñz¾ýôú¾ìÝbÏ„ï¸¦§ RDBMS ÏÏ®¾áÏ@ðà­uOLAP ïyðz÷ˆ©’®ª¨ì­v÷ˆ©’©w­A Ï~î…ñN¾Ýª[§c
Ýù ODBC ÷ˆ©’ùàú«­C

¾HÏU«dùã¯­¸£ÝpÝ¢«s¨Š odbc.ini­AùØ¾×ð¸l ODBC XøÒæ{Ý­ùàüsñæÝš DB2 ¦¸¾¯ 6.1
(Ýb Solaris ÏW) ¦§­uOLAP ïyðz÷ˆ©’®ª¨ì­vTBC_MD­C

     [ODBC Data Sources]
     ocd6a5a=db2 v6
     ...
     [ocd6a5a]
     Driver=/home/db2instl/sqllib/lib/db2.0
     Description=db2

25.4.3 Ýb Windows ùtý×ÏWª[§c÷ˆ©’ùàú«

ñì¸¢ Windows NT ¸× Windows 2000 ùtý×ÏWª[§cÇ”µpÝ­÷ˆ©’ùàú«­A ñz¾ýôúñãøÒ­uODBC
§èýzæ{Ý­­v­AæM® ®¾áüs«uùàüsñæÝšñzðn¾×ùà®¾á OLAP ¬ã®ª¸M metaoutline ¦§÷ˆ©’
ùàú«­Cñq Windows ññùŒ¾xøäÝ‘­uODBC §èýzæ{Ý­­vÏ«¾×æ{Ý­­CÏUÝC«dùã®¾áÏ@ðà DB2
÷ˆ©’ùàú«­Fù„¾L RDBMS ¦§û‹÷š©ú|ÏœÝP­C

ñìùØ¾×­uODBC §èýzæ{Ý­­vùàª[§cÇ”µpÝ­÷ˆ©’ùàú«­A«ÑõûÝùÏUÝCùB’J­G

  1. Ýb Windows ©…ÏW§èýzæ{Ý­­Aô}ñã­uññùŒ¾x­væ›æ­­C
  2. Ýb­uññùŒ¾x­væ›æ­ÏÏ­AøäÝ‘ÏUÝCù„ÏÏÏ@ôæùB’J­G
       a. Ýb Windows NT ÏW­A®”ùƒÏU ODBC ûØ¾š­A ô}ñã­uODBC ÷ˆ©’ùàú«§èýzæ{
          Ý­­vû‹÷š©­C
       b. Ýb Windows 2000­A®”ùƒÏUùtý×§èýzÏuùÆûØ¾š­A ÝA®”ùƒÏU÷ˆ©’ùàú« (ODBC)
          ûØ¾š­A ô}ñã­uODBC ÷ˆ©’ùàú«§èýzð–­vû‹÷š©­C
  3. Ýb­uODBC ÷ˆ©’ùàú«§èýzæ{Ý­­vû‹÷š©ÏÏ­A®”Ï@ÏUùtý×÷ˆú«ùàú«ÝW§ë¬Ñã­C
  4. ®”Ï@ÏUús¬Wùàô}ñã­u®¾áús÷ˆ©’ùàú«­vû‹÷š©­C
  5. Ýb­uODBC §èýzæ{Ý­­v¦§­u®¾áús÷ˆ©’ùàú«­vû‹÷š©¦§XøÒæ{Ý­ÝC¾š©ÏÏ­A¨‹ù£
     óAú¡¦§XøÒæ{Ý­­AùãÝp IBM DB2 ODBC XøÒæ{Ý­­A ®”Ï@ÏUõûÝùùàô}ñã­uODBC
     IBMDB2 XøÒæ{Ý­ - ús¬W­vû‹÷š©­C
  6. Ýb­uODBC IBM DB2 XøÒæ{Ý­ - ús¬W­vû‹÷š©ÏÏ­AÝb÷ˆ©’©wõOÝWÏU¸âÝC¾šÏÏ­A¨‹
     ù£ñz¦§Ç”µpÝ­ùàú« (ùãÝp­AÝû«dùã·ü¾×æ{Ý­ÏÏ¦§ TBC) ¦§÷ˆ©’©wÝW§ë­C
  7. Ýb¯­¸£Ï†Ýr©ÏÏ­A¨‚ÏJ¨‹¾×¦§¯­¸£ùà¦¡¾šñzðnÝpÝ¢ùØ¾×ÝûXøÒæ{Ý­­A®”Ï@ÏUús¬W
     ­C ùãÝp­A¨‚ÏJÏUÝCÏ†Ýrùà¯­¸£ My Business ÷ˆ©’©w­G

     Customers, products, markets

     ñz¾i¨‚ÏJÏUÝCÏ†Ýrùà¯­¸£«dùã·ü¾×æ{Ý­÷ˆ©’©w­G

     Sample relational data source

     üoù€¯­¸£¾iÝbñzñq OLAP Starter Kit Desktop üs«u©­Aù¢õUñzÇ¥õO¾i¨‹óš¦§÷ˆ
     ©’ùàú«­C
  8. ®”Ï@ÏU­u«T¸w­vùà¦ÐÝ^­uODBC ÷ˆ©’ùàú«§èýzð–­vû‹÷š©­C ñz¨‚ÏJ¦§÷ˆ©’ùàú«ÝW
     §ëÏ×ñzû‹ªM¦§XøÒæ{Ý­Æ¾šÝbùtý×÷ˆú«ùàú«ÝW§ë¬Ñã¦§ùtý×÷ˆ©’ùàú«ÝC¾š©ÏÏ­C

ñì«s¨Š÷ˆ©’ùàú«¦§ª[§c÷ˆøT­G

  1. ¨‹ù£÷ˆ©’ùàú«ÝW§ë­A®”Ï@ÏUª[§cùàô}ñã­uODBC IBM DB2 - ús¬W­vû‹÷š©­C
  2. ðž¾¨ñzðnšõ¢¦§¾“Ý¢÷ˆøT­C
  3. ®”ùƒÝ÷«T¸w¾Hæýõ“­C

25.4.4 Ýb Windows ùtý×ÏWª[§c OLAP ïyðz÷ˆ©’®ª¨ì

ñì¸¢ Windows NT ¸× Windows 2000 ÏWª[§c­uOLAP ïyðz÷ˆ©’®ª¨ì­v­A «ÑñãøÒ­uODBC
§èýzæ{Ý­­v­AæM® ®¾áüs«uùàüsñæÝšõtÝü­uOLAP ïyðz÷ˆ©’®ª¨ì­v÷ˆ©’©w¦§÷ˆ©’ùàú«­C

ÏUÝC«dùã®¾áÏ@ðà DB2 ÷ˆ©’ùàú«­Fù„¾L RDBMS ¦§û‹÷š©ú|ÏœÝP­C ñì®¾á­uOLAP ïy
ðz÷ˆ©’®ª¨ì­v¦§÷ˆ©’ùàú«­A«ÑõûÝùÏUÝCùB’J­G

  1. Ýb©…ÏW§èýzæ{Ý­­Aô}ñã­uññùŒ¾x­væ›æ­­C
  2. Ýb­uññùŒ¾x­væ›æ­ÏÏ­AøäÝ‘ÏUÝCù„ÏÏÏ@ôæùB’J­G
       a. Ýb Windows NT ÏW­A®”ùƒÏU ODBC ûØ¾š­A ô}ñã­uODBC ÷ˆ©’ùàú«§èýzæ{
          Ý­­vû‹÷š©­C
       b. Ýb Windows 2000­A®”ùƒÏUùtý×§èýzÏuùÆûØ¾š­A ÝA®”ùƒÏU÷ˆ©’ùàú« (ODBC)
          ûØ¾š­A ô}ñã­uODBC ÷ˆ©’ùàú«§èýzð–­vû‹÷š©­C
  3. Ýb­uODBC ÷ˆ©’ùàú«§èýzæ{Ý­­vû‹÷š©ÏÏ­A®”Ï@ÏUùtý×÷ˆú«ùàú«ÝW§ë¬Ñã­C
  4. ®”Ï@ÏUús¬Wùàô}ñã­u®¾áús÷ˆ©’ùàú«­vû‹÷š©­C
  5. Ýb­uODBC §èýzæ{Ý­­v¦§­u®¾áús÷ˆ©’ùàú«­vû‹÷š©¦§XøÒæ{Ý­ÝC¾š©ÏÏ­A¨‹ù£
     óAú¡¦§XøÒæ{Ý­­AùãÝp IBM DB2 ODBC XøÒæ{Ý­­A ®”Ï@ÏUõûÝùùàô}ñã­uODBC
     IBMDB2 XøÒæ{Ý­ - ús¬W­vû‹÷š©­C
  6. Ýb­uODBC IBM DB2 XøÒæ{Ý­ - ús¬W­vû‹÷š©ÏÏ­A Ýb÷ˆ©’©wõOÝWÏU¸âÝC¾šÏÏ­A
     ¨‹ù£ñz¦§­uOLAP ïyðz÷ˆ©’®ª¨ì­v(ùãÝp­AÝû«dùã·ü¾×æ{Ý­ÏÏ¦§ TBC_MD) ¦§÷ˆ©’
     ©wÝW§ë­C¨‹ù£¦§÷ˆ©’©wÝW§ëú|ÝêøÒÆ¾šÝb÷ˆ©’ùàú«ÝW§ëÏ†Ýr©ÏÏ­C
  7. ðYñzðnšõ¢÷ˆ©’ùàú«¦§ÝW§ë­A«Ñ¨‹ù£÷ˆ©’ùàú«ÝW§ëÏ†Ýr©ÏÏÆ¾š¦§ÝW§ë­A¨‚ÏJús
     ¦§ÝW§ëùà¦¡¾šñzðnÝpÝ¢ùØ¾×ÝûXøÒæ{Ý­­A®”Ï@ÏUús¬W­C ùãÝp­Añz¾i¨‚ÏJÏUÝCÝW
     §ëùà¦¡¾šñzðnùØ¾×ÝûXøÒæ{Ý­ùàüsñæÝšýŽÏ@ðà­uOLAP ïyðz÷ˆ©’®ª¨ì­v­G

     OLAP Catalog first

     ñz¾i¨‚ÏJÏUÝCÝW§ëùà¦¡¾šñzðnüsñæÝš«dùã·ü¾×æ{Ý­­uOLAP ïyðz÷ˆ©’®ª¨ì­v÷ˆ©’
     ©w­G

      TBC_MD

  8. Ýb¯­¸£Ï†Ýr©ÏÏ­A¨‚ÏJ¯­¸£ùà¦¡¾šñzðnÝpÝ¢ùØ¾×ÝûXøÒæ{Ý­­C ùãÝp­Añz¾i¨‚ÏJ
     ÏUÝCÏ†Ýrùà¯­¸£­uOLAP ïyðz÷ˆ©’®ª¨ì­v­G

     My first models and metaoutlines

     ñz¾i¨‚ÏJÏUÝCÏ†Ýrùà¯­¸£«dùã·ü¾×æ{Ý­­uOLAP ïyðz÷ˆ©’®ª¨ì­v÷ˆ©’©w­G

     Sample models and metaoutlines

     üoù€¯­¸£¾iÝbñzñq OLAP Starter Kit Desktop üsñæÝš­uOLAP ïyðz÷ˆ©’®ª¨ì­v
     ©­A ù¢õUñzÇ¥õOúQðn¨‹óš¦§®ª¨ì­C
  9. ®”Ï@ÏU­u«T¸w­vùà¦ÐÝ^­uODBC ÷ˆ©’ùàú«§èýzð–­vû‹÷š©­C ñz¨‚ÏJ¦§÷ˆ©’ùàú«ÝW
     §ëÏ×ñzû‹ªM¦§XøÒæ{Ý­Æ¾šÝbùtý×÷ˆú«ùàú«ÝW§ë¬Ñã¦§ùtý×÷ˆ©’ùàú«ÝC¾š©ÏÏ­C

ñì«s¨Š÷ˆ©’ùàú«¦§ª[§c÷ˆøT­G

  1. ¨‹ù£÷ˆ©’ùàú«ÝW§ë­A®”Ï@ÏUª[§cùàô}ñã­uODBC IBM DB2 - ús¬W­vû‹÷š©­C
  2. ðž¾¨ñzðnšõ¢¦§¾“Ý¢÷ˆøT­C
  3. ®”ùƒÝ÷«T¸w¾Hæýõ“­C

25.4.5 Ýbñzª[§c÷ˆ©’ùàú«Ïõ® 

Ýbª[§cÇ”µpÝ­÷ˆ©’ùàú«¸M­uOLAP ïyðz÷ˆ©’®ª¨ì­vÏõ® ­AõY¾iñq OLAP Starter Kit ùà
üsñæ­CæM® ¾i¾H®¾á­Bðžõ‹Ï×·xÝs OLAP ¬ã®ª¸M metaoutline­C

Ýb¸I¾s SQL Server ÷ˆ©’©wïµô­­ASQL Server ODBC XøÒæ{Ý­¾iî…ú|ûO©­C «Ñ¸¢÷ˆ©’
©w®DÝœ«u©ð®÷å­C¬W¾[XøÒæ{Ý­ûO©ïµô­¾iµžõKÝûøíÇD­C ÷âýà÷ˆøT­A«Ñø¥ó\ñz¸ãùØ¾×
¦§XøÒæ{Ý­¦§ ODBC Ï†¾¢­C

Ç”¸¢ ODBC üsñæøíÇD¯P÷¥ùMÏŠ©ž­A«Ñø¥ó\ OLAP Integration Server System
Administrator's Guide­C
  ------------------------------------------------------------------------

25.5 ñq OLAP Starter Kit ©…ÏW§èýzæ{Ý­ænÏJ

ùØ¾× OLAP Starter Kit ©…ÏW§èýzæ{Ý­ùà®¾á OLAP ¬ã®ª¸M Metaoutline­A«ÑñNñqŽí
î÷ün‚üsñæùùƒðàÝ›¦Aóû­GDB2 OLAP óÆÝXÝ›¦Aóû¸M DB2 OLAP Ý›¦Aóû­CænÏJû‹÷šïœ¾š
©…ÏW§èýzæ{Ý­üsñæùüoùƒðàÝ›¦Aóû¦§¾ýðn÷ˆøT­CÝbû‹÷š¦§¾¦Ç„­A«Ñ¨‚ÏJÝüÇ” DB2 OLAP
óÆÝXÝ›¦Aóû¦§÷ˆøT­CÝbû‹÷š¦§¾kÇ„­A«Ñ¨‚ÏJÝüÇ” DB2 OLAP Ý›¦Aóû¦§÷ˆøT­C

ñìüsñæù DB2 OLAP óÆÝXÝ›¦Aóû­G

   * Ý›¦Aóû­G¨‚ÏJóÆÝXÝ›¦Aóû¦§¾Dûq÷œÝW§ë¸× IP Ýõ}­C Ýp¦GñzÏwÝw÷ÓóÆÝXÝ›¦Aóû
     ¸M©…ÏW§èýzæ{Ý­¸¢ÝPÏ@ðàÏuõ@î÷­Aù†®ª¦§ðÔªø "localhost" ¸× "127.0.0.1"­C
   * OLAP ïyðz÷ˆ©’¾¨ì­Güsñæ OLAP óÆÝXÝ›¦Aóû­A¾ýôú®¸wïyðz÷ˆ©’¾¨ì­C OLAP
     óÆÝXÝ›¦Aóû·xÝsÝüÇ” OLAP ¬ã®ª¸MÝWªø Metadata Catalog Ç”µpÝ­÷ˆ©’©w¸ã®¾á
     ¦§ metaoutline ¦§÷ˆøT­C ÝûÇ”µpÝ­÷ˆ©’©w¾ýôúænøOæû ODBC­C ¾¨ì÷ˆ©’©wÝüÏ@
     ýå OLAP óÆÝXÝ›¦Aóûî…¨‰Ç¥¦§Ç”µpÝ­¦¡©‘­C ÝbænÏJû‹÷šÏÏ­A®¸wóÆÝXÝ›¦Aóû­A
     ùÇ©iô} OLAP ïyðz÷ˆ©’¾¨ìŽ‘Ý¦§ÏU¸â¾\î…¦¡­A ñz¾i¾Hªíù OLAP óÆÝXÝ›¦Aóû
     ¸ã¦óûD¦§ ODBC ÷ˆ©’ùàú«ÝW§ëÏõÝC¦¡­C ¨‹óšõtÝüïyðz÷ˆ©’®ª¨ì¦¡©‘¦§ ODBC ÷ˆ
     ©’©w­C
   * ùØ¾×¦ÞÝW§ë¸MüqÝ‘«X­GùØ¾×ñzÝbæeðñ¸ã®¸w¦§ùØ¾×¦ÞÝW§ë¸MüqÝ‘«X­AOLAP óÆÝX
     Ý›¦AóûñN¯Pïyðz÷ˆ©’¾¨ìüsæý­C üoªOænÏJñbÏ ­AÝsÝb¸¢Ý›¦Aóû (ÏœªOñqŽíî÷­A
     øœ®DÝ›¦Aóû¸MñqŽíî÷ÝbÝPÏ@¾xóöóûøäÝ‘)­CùØ¾×¦ÞÝW§ë¾ýôúªø®¾á OLAP ïyðz÷ˆ
     ©’¾¨ì¦§ùØ¾×¦Þ­C õ_®h­AOLAP óÆÝXÝ›¦AóûñNõ„Ïœù¾¨ì÷ˆ©’©wÏ§¦§Ç”µpÝ­¦¡
     ©‘­AÝ]ªø¦¡©‘§ä¾¦§ÝW§ëÏœÏ@¬Ó­C

DB2 OLAP Ý›¦Aóû÷ˆøTªø¨‹¾×¦§­A¸ã¾H­AÝbænÏJû‹÷š¦§¾kÇ„Ïõ¨‚ÏJŽ‘Ý¾iî…ªO¦¾å¦§­C
ÝìªO­AÝüù€©…ÏW§èýzæ{Ý­¸M§èýzæ{Ý­¦§õ@ú~¯íðn¸M DB2 OLAP Ý›¦Aóûüsñæ­C Ýp¦Gñzõƒ
üoù€Ž‘Ý¦ÏUùà­Aú¡óÆÝXÝ›¦Aóû¯íðn¸M DB2 OLAP Ý›¦Aóûüsñæ¾HõûÝùñz¸ãðnùD¦§õ@ú~
©­A©…ÏW§èýzæ{Ý­ú|ÝAÏ@Ý÷Æ¾šænÏJû‹÷š­C ®ŽüñzÝbænÏJû‹÷š¦§ DB2 OLAP Ý›¦AóûŽ‘
Ýô¤ÏJ÷ˆ©’­C

ñìüsñæù DB2 OLAP Ý›¦Aóû­G

   * Ý›¦Aóû­G¨‚ÏJ DB2 OLAP Ý›¦Aóû¦§¾Dûq÷œÝW§ë¸× IP Ýõ}­C Ýp¦GñzÝbøäÝ‘ OLAP
     Starter Kit­A®h OLAP Ý›¦Aóû¸MóÆÝXÝ›¦AóûªêÝP­C Ýp¦GóÆÝXÝ›¦Aóû¸M OLAP Ý›
     ¦AóûÝw÷ÓÝbÏœÝP¦§¾Dûq÷œ­A«Ñ¨‚ÏJ¸w÷q¸¢ OLAP óÆÝXÝ›¦AóûÏ§¦§¾Dûq÷œÝW§ë¸×
     IP Ýõ}­C
   * ùØ¾×¦ÞÝW§ë¸MüqÝ‘«X­GùØ¾×ñzÝbæeðñ¸ã®¸w¦§ùØ¾×¦ÞÝW§ë¸MüqÝ‘«X­A OLAP óÆÝX
     Ý›¦AóûñN¯P DB2 OLAP Ý›¦Aóûüsæý­C ÝûùØ¾×¦ÞÝW§ë¸MüqÝ‘«X¾ýôúÏw÷g¸w÷qÝb
     DB2 OLAP Ý›¦AóûÏ§­C OLAP Ý›¦AóûÝêõ@ú~ùtý×¾t¾~Ýa§èýz¾Ý¸ãó™Ýü¦§ùØ¾×¦ÞÝW
     §ë¸MüqÝ‘«X­C

25.5.1 Starter Kit ænÏJ«dùã

ÏUÝC«dùãøýü]­AÝb OLAP Starter Kit Ýw÷Óïµô­­Añz®¾áÏF OLAP «dùã­A ùÇ¨‹ù£ÏF
db2admin õ@ªø§èýz¦ÞùØ¾×¦Þ ID­Apassword ªø§èýz¦ÞüqÝ‘«X­C

   * OLAP óÆÝXÝ›¦Aóû­GÝ›¦AóûªO localhost­A OLAP ïyðz÷ˆ©’¾¨ìªO TBC_MD­AùØ¾×
     ¦ÞÝW§ëªO db2admin­AüqÝ‘«XªO password
   * DB2 OLAP Ý›¦Aóû­GÝ›¦AóûªO localhost­AùØ¾×¦ÞÝW§ëªO db2admin

  ------------------------------------------------------------------------

25.6 ÝêÝ‘®¾á¸Mª[§c OLAP Starter Kit ¦§«dùã÷ˆ©’©w

Ýw÷Ó OLAP Starter Kit ©­A«dùã÷ˆ©’©wú|ÝêøÒ®¾á­CÏUÝC®¾š÷¥Žô­A¾ýðn©­AÝpÝ¢
ÝêÝ‘Ýw÷Ó¾¨ì¸M«dùã÷ˆ©’©w­C

  1. Ýbæ›æ­ÏU­A®”Ï@ÏU ô}¸l -->æ{Ý­ôø-->DB2 for Windows NT--> ¸R¾Oæ›æ­­A¾Hô}
     ñã­u¸R¾OÏÏÏá­væ›æ­­C
  2. ®¾á¾¨ì÷ˆ©’©w­G
       a. ¨‚ÏJ db2 create db OLAP_CAT
       b. ¨‚ÏJ db2 connect to OLAP_CAT
  3. ®¾á÷ˆ©’©wÏ§¦§¦¡©‘­G
       a. óŽì \SQLLIB\IS\ocscript\ocdb2.sql
       b. ¨‚ÏJ db2 -tf ocdb2.sql
  4. ®¾á«dùãùàú«÷ˆ©’©w­G
       a. ¨‚ÏJ db2 connect reset
       b. ¨‚ÏJ db2 create db TBC
       c. ¨‚ÏJ db2 connect to TBC
  5. ®¾á÷ˆ©’©wÏ§¦§¦¡©‘­G
       a. óŽì \SQLLIB\IS\samples\
       b. «’¯s tbcdb2.sql ù \SQLLIB\samples\db2sampl\tbc
       c. «’¯s lddb2.sql ù \SQLLIB\samples\db2sampl\tbc
       d. óŽì \SQLLIB\samples\db2sampl\tbc
       e. ¨‚ÏJ db2 -tf tbcdb2.sql
       f. ¨‚ÏJ db2 - vf lddb2.sql ­A¾H÷ÏJ«dùãùàú«÷ˆ©’ù¦¡©‘Ï§­C
  6. ®¾á«dùã¾¨ì÷ˆ©’©w­G
       a. ¨‚ÏJ db2 connect reset
       b. ¨‚ÏJ db2 create db TBC_MD
       c. ¨‚ÏJ db2 connect to TBC_MD
  7. ®¾á÷ˆ©’©wÏ§¦§¦¡©‘­G
       a. óŽì \SQLLIB\IS\samples\tbc_md
       b. «’¯s ocdb2.sql ù \SQLLIB\samples\db2sampl\tbcmd
       c. «’¯s lcdb2.sql ù \SQLLIB\samples\db2sampl\tbcmd
       d. óŽì \SQLLIB\samples\db2sampl\tbcmd
       e. ¨‚ÏJ db2 -tf ocdb2.sql
       f. ¨‚ÏJ db2 -vf lcdb2.sql­A¾H÷ÏJ«dùãïyðz÷ˆ©’ù¦¡©‘­C
  8. ª[§c ODBC for TBC_MD, TBC, AND OLAP_CAT­G
       a. ®”Ï@ÏUô}¸l-->ü]¸w-->ññùŒ¾x­A¾Hô}ñã NT ññùŒ¾x
       b. ñqÝC¾šÏÏ¨‹ù£ ODBC (¸× ODBC ÷ˆ©’ùàú«)­C
       c. ¨‹ù£­uùtý× DSN­v¬Ñã­C
       d. ®”Ï@ÏU­uús¬W­v­C ®¾áús¦§÷ˆ©’ùàú«æ›æ­ô}ñã­C
       e. ñqÝC¾šÏÏ¨‹ù£ IBM DB2 ODBC DRIVER­C
       f. ®”Ï@ÏU­uõûÝù­v­C ODBC IBM D2 XøÒæ{Ý­ - ús¬Wæ›æ­ô}ñã­C
       g. Ýb÷ˆ©’ùàú«ÝW§ëŽ‘ÝÏÏ­A¨‚ÏJ÷ˆ©’ùàú« (OLAP_CAT) ¦§ÝW§ë­C
       h. Ýb÷ˆ©’©wõOÝWŽ‘ÝÏÏ­A¨‚ÏJõOÝW­A¸×ªO®”Ï@ÏU­ä­AùÇÝbÝC¾šÏÏ¨‹ù£
          OLAP_CAT­C
       i. ®”Ï@ÏU­u«T¸w­v­C
       j. û‹¸¢ TBC_MD ¸M TBC ÷ˆ©’©w­A«Ñð®«’¾HÏWùB’J­C

  ------------------------------------------------------------------------

25.7 ýó¶…·ü¾×æ{Ý­Ýš OLAP Starter Kit ¦¸¾¯ 7.2

Ýw÷Óæ{Ý­Ïœð®úsÝw÷Ó OLAP Starter Kit «dùã·ü¾×æ{Ý­­B÷ˆ©’©wÏ×÷ˆ©’·­C ñz¦§ý{Ýs
·ü¾×æ{Ý­¸M÷ˆ©’©wÏœù¬vT­C æMÝà­AÝbÝw÷ÓÏõ®e­AüÞÝn¾ìü’¾öñz¦§·ü¾×æ{Ý­¸M÷ˆ©’
©w­C

ñz¦§·ü¾×æ{Ý­Ýbô}ñã©ú|ÝêøÒýó¶…Ýš¦¸¾¯ 7.2­C
  ------------------------------------------------------------------------

25.8 Ïw¦óøíÇD¯PððùŒ

¾¯ªq÷ùÝC¾š DB2 OLAP Starter Kit ¦§Ïw¦óððùŒ­C

Windows ¾ð¾x¦§ Informix RDBMS ¸M Merant XøÒæ{Ý­¦§ªê©e¸Ò
     ªøÏFì Windows ¾ð¾x¦§ Merant XøÒæ{Ý­î…øö¸M Informix RDBMS Ï@ø_ûBõ@­A
     PATH üîðzÝ­ÏÏ¾ýôúús¬WÏUÝCùƒðàôæ¾­G
        o C:\Informix
        o C:\Informix\bin

     üoùƒðàôæ¾¾ýôúÝ¸¢ PATH ¦§ô}·Y­C

OLAP ¬ã®ªÏÏ¦§§–®ž¸MªêÇ” Metaoutline Ïõô­¾iî…¦§ÏœÏ@ðPñ­õ×
     ÝbªYù€ñ­¦pÏU­Añz®¾á¦§§–®žÝb OLAP ¬ã®ªÏÏæLªêû‹·ü¦§§–®ž­C ÝbÏUÝCûˆøÔÏÏ
     ú|æo¾Öüoù€ñ­õ×­G

       1. ®¾áùÇ·xÝsÏ@ðàús¦§ OLAP ¬ã®ª­C
       2. ©éóéÝû¬ã®ªùà®¾áÏ@ðà metaoutline­AÝìùÇ¾¬·xÝs metaoutline­C
       3. ¦ÐÝ^ OLAP ¬ã®ª­AõRøœù„ÏÏÏ@ðà metaoutline §–®ž¸ãùÞ¨…¦§§–®ž­C
       4. ¦ÐÝ^ metaoutline­Aô}ñã­BÇ”üª­AÝAð®úsô}ñã­Cmetaoutline ñN¾]õtÏ@ðà
          §–®ž­AÝû§–®žÝb OLAP ¬ã®ªÏÏæLªêû‹·ü¦§§–®ž­C

     OLAP Starter Kit æL¦køØÏ·üo§ñ­¦pÏU®¾á¦§ÏœÏ@ðP§–®ž¸M metaoutlin ÏÏ¦§
     ùØ¾×¦Þ¸w÷q§–®ž­C Ý]Ýû­AÏœÏ@ðP§–®žú|Æ¾šÝb metaoutline ÏÏ­AÝì
     metaoutline æ›¾ÝªøÏ@ðàùØ¾×¦Þ¸w÷q§–®ž­AÝ]ªø OLAP ¬ã®ªÏÏæLªêû‹·ü¦§§–®žÝs
     Ýb­C

Ýb Windows 2000 ¾ð¾xÏW­ATMP ¦§·“ûãš¬’ü]¸wóðPÝùð–¸M÷ˆ©’÷ÏJ¾½ñ¥
     Ý]ªø Windows 2000 ¸M Windows NT Ïõô­­ATMP ¦§ûwü]ùtý×¸MùØ¾×¦Þ·“ûãš¬’ü]
     ¸wÝü¸ã©týõ­A ú¡ OLAP Starter Kit Ýb Windows 2000 ¾ð¾xÏWøäÝ‘©­AÝùð–¸M
     ÷ˆ©’÷ÏJú|¾½ñ¥­C üyÝù¦§¨—¯~øT©õõiôDùØ¾×¦ÞæL¦k®¾á¬ÔÝs·­C ñz¾iñŽù£ÏUÝC
     ùB’Jùà÷¥ùMÝû Windows 2000 ¦§ððùŒ­G

       1. ®¾áÏ@ðà¾¨ì C:\TEMP
       2. ñNùtý×¸MùØ¾×¦Þ¦§·“ûãš¬’ TMP ü]¸wªø TMP=C:\TEMP

Ýw÷Ó ODBC Ïœù£¾Ný{Ýs¦§ Merant XøÒæ{Ý­
     ý{Ýs¦§ 3.6 Merant ODBC XøÒæ{Ý­Ïœ·HÝûÝw÷ÓÝàõ¢ús­C ðYñzñq OLAP Starter
     Kit ¦¸¾¯ 7.1 ðž¾¨©M¾¢ 2 ¸×õ¢ø¦¦¸¾¯ùàÏî­A ñz·ü÷àŽ~Ž•ùØ¾×¾ì®eÝw÷Ó¦§
     ODBC XøÒæ{Ý­

Ýb UNIX ¾ð¾xÏWùØ¾× Merant Informix ODBC XøÒæ{Ý­
     ñì¸¢ UNIX ¾ð¾xÏWùØ¾× Merant Informix ODBC XøÒæ{Ý­­Añz¾ýôúøäÝ‘ÏUÝCù„ÏÏ
     Ï@ôæøÒõ@­G
        o ÝbñãøÒ Starter Kit Ïõ®e­AñN LANG ·“ûãš¬’ü]ªø en_US­CùãÝp­AðYªO
          korn shell­A«Ñµ„ÏJ­G

          export LANG='en_US'

          ùCÝ÷ñãøÒ OLAP Starter Kit ©ªãü]¸wÝûš¬’­C
        o ðYñz¦§ LANG ·“ûãš¬’Ïwü]¸wÝùÏœÝPðÔ­A «Ñ¸¢Ýw÷ÓÏõ® ®¾áÏUÝCý÷ûÇ
          æý­G

          ln -s $ISHOME/locale/en_US $ISHOME/locale/$LANG

ýVÝX OLAP ñqŽíî÷¸MÝ›¦Aóû¦§¦AøÔæ{Ý­æ¾î
     IBM ®ŽüñzñN DB2 OLAP Starter Kit ¦§ñqŽíî÷¸MÝ›¦AóûÏ÷¾¢®O®—ÝbªêÝP¦¸¾¯¸M
     ðž¾¨©M¾¢¬hÝ÷­C ÝìÝbªYù€¦ª¦pÏU­Añz¾iýVÝXñqŽíî÷¸MÝ›¦AóûÏ÷¾¢¦§¦AøÔæ{Ý­æ¾
     î­G

     ùØ¾×ÝPÏ@¦¸¾¯ÝìÏœÝP¦AøÔæ{Ý­æ¾î¦§ñqŽíî÷¸MÝ›¦Aóû
          IBM ÏœÏ„ï¸¸M®ŽüÝP©ùØ¾×÷–ús¦§ñqŽíî÷¸M÷–¶¶¦§Ý›¦Aóû­C ÏœûL­Aµ”æM
          IBM ÏœÏ„ï¸­AñzÏï¾iÝP©ùØ¾×÷–¶¶¦§ñqŽíî÷¸M÷–ús¦§Ý›¦Aóû­C ñz¾iî…ú|óD
          ûJÏ@ù€øíÇD­CùãÝp­G
             + ùàÝêÝ›¦Aóû¦§øT©õ¾iî…Ïœ¾¨«T­Cñz¾iÏîñqŽíî÷¦§ message.MDB ·
               ©žùàýÝXÝ›¦Aóû¦§¬hÝ÷­AõY¾i÷¥ùMÝûøíÇD­C
             + ús¦§Ý›¦AóûîS¸ÒùSÝüõ@¾×­Cú¡ñzûµ÷åùØ¾×úsîS¸Ò©­AñqŽíî÷­BÝ›¦Aóû
               ¸×ùƒ¦Þ¾iî…¾½©Ž­C
             + ñqŽíî÷¾iî…æL¦kóAú¡ÝaüsñæÝ›¦Aóû­C

     ÝbÝPÏ@ðà¦¸¾¯ÏÏùØ¾×Ýhð®Ý›¦Aóû¸Mü‘Ï@ñqŽíî÷
          ðYñz¯íðnñNÏ@ðàñqŽíî÷üsñæÝšÏœÝPóöóû¸×õ@ú~ùtý×ÏW¦§ïXðà OLAP Ý›¦A
          óû­AIBM ®Žüñzüoù€Ý›¦Aóû¾çü­ùØ¾×ªêÝP¦¸¾¯¸M¦AøÔæ{Ý­æ¾î­C ñz¦§ñqŽí
          î÷ÝšÏ™·ü÷à¯PüÞõC¬hÝ÷¦§Ý›¦AóûªêÝP­C ðYñzóDûJøíÇD­A®h¾iî…¯íðnùØ¾×Ïœ
          ÝPñqŽíî÷óöóûùàøtÝXóAú¡¦§¾Dûq÷œ­A ¸×ñN¸ãÝüñqŽíî÷¸MÝ›¦AóûÏîÝùªêÝP
          ¦§¦AøÔæ{Ý­æ¾î­C

     ýVÝXÏœÝP¦¸¾¯¦§ñqŽíî÷¸MÝ›¦Aóû
          IBM ÏœÏ„ï¸ÝP©ùØ¾× OLAP Starter Kit ñqŽíî÷¸MÝ›¦Aóû¦¸¾¯ 7.1 ¯PñqŽí
          î÷¸MÝ›¦Aóû¦¸¾¯ 7.2­Cú¡ IBM OLAP ýœ®~Ïîªø÷–ús¦¸¾¯¬hÝ÷©­A §“÷“õ¢
          ús¸M÷ˆ©’©‘Ý­šõ¢üqñ`ðnùDñqŽíî÷¸MÝ›¦AóûªøªêÝP¦§¦¸¾¯¬hÝ÷­C

     ýVÝX IBM ýœ®~ (DB2 OLAP Starter Kit) ¸M Hyperion ýœ®~ (Hyperion
     Essbase ¸M Hyperion Integration Server)
          IBM ÏœÏ„ï¸ýVÝX IBM ¦§ OLAP ñqŽíî÷¸MÝ›¦Aóû¯P Hyperion Solutions ¦§
          OLAP ñqŽíî÷¸MÝ›¦Aóû­Cµ”æMýVÝXüoù€Ï÷¾¢ÝbªYù€ñ­¦pÏU¾i¾HûBõ@­A ÝìîS
          ¸ÒÏW¦§ü­¾ö©týõ¾iî…ú|üyÝùøíÇD­C

  ------------------------------------------------------------------------

25.9 OLAP ÷å§ƒ¦¡¬Wîqôø EQD ·©ž¨•¾½

Ýb DB2 OLAP Starter Kit ÏÏ¦§÷å§ƒ¦¡¬WîqôøùÆÝü Query Designer (EQD) Ï÷¾¢­C
EQD «uÏW¯­¸£¾\î…¦¡ÏÏ¸ãõt¦§ñÑó€®ó®”ôs­AÏœú|Æ¾š¾“Ý¢Ï§©e­C ù„¸ã·üÆ¾š¦§ñÑõö
ªø OLAP Spreadsheet Add-in User's Guide for Excel ¦§ýŽ 2 üû­A¾HÏ× OLAP
Spreadsheet Add-in User's Guide for 1-2-3­C EQD ñÑó€®óÏÏ¦§¸ãÝü÷ˆøT­A¾i¾H
ñq­u÷ˆøTÏÏÏá­vüoù€©¥Žy¦§ HTML ¦¸Ï× PDF ¦¸ªdù­C
  ------------------------------------------------------------------------

÷ˆøT®ª¨ì§èýzæ{Ý­§èýzÏƒ¾U

  ------------------------------------------------------------------------

26.1 ÷ˆøT®ª¨ì§èýzæ{Ý­ø_¸lü]¸wÏ«¾×æ{Ý­

26.1.1

ùØ¾×ø_¸lü]¸w÷ˆøT®ª¨ì§èýzæ{Ý­ (ICM) Ï«¾×æ{Ý­­A ñzý{Ýb¾i¾HõQ¾×ÏUÝC®¾O­AýK¾[
SQL üîðzÝ­Ýš CREATE TABLE üîðzÝ­¦§æýõ·­G

CREATEIC \DBTYPE dbtype \DGNAME dgname \USERID userid \PASSWORD password
\KA1 userid \TABOPT "directory:\tabopt.file"

ñz¾i¾HñqÝw÷Ó DB2 ¦§¾¨ì­AÝb CREATEIC Ï«¾×æ{Ý­ÏÏ®¸w TABOPT Ç”µ„Ýr­C TABOPT
Ç”µ„ÝrÏõ® ¦§ðÔªO tabopt.file­A·©žÝW§ëªOõtÝüõûóÆ¦§÷“©|­CÝp¦G¾¨ìÝW§ëÝü¦
¾å­A «Ñ¾HÏè÷ûªAÝ¡÷àÝW§ë­Ctabopt.file ·©ž¦§Ï§©e¾ýôúõtÝü÷ˆøT­AÏ~î…ýK¾[Ýš
CREATE TABLE üîðzÝ­­Cñz¾i¾HùØ¾×ÏUÝC¾“Ï@§ SQL üîðzÝ­¬gÏJÝû tabopt.file ·
©ž­CICM Ï«¾×æ{Ý­ñN¦ù£Ýû·©ž­AæM® ñN¾ÝýK¾[ù CREATE TABLE üîðzÝ­­C

¦¡ 20. SQL üîðzÝ­
 IN MYTABLESPACE             ¾Hù„ MYTABLESPACE ÷ˆ©’®¾á¦¡©‘
 DATA CAPTURE CHANGES        ¾H¶X¾R©‘Ý­®¾á¦¡©‘ùÇøO÷ SQL šõ¢
 IN ACCOUNTING INDEX IN      ¾Hù„ ACCOUNTING ÷ˆ©’Ï× ACCOUNT_IDX îµÏè®¾á¦¡
 ACCOUNT_IDX                 ©‘

Ï§©e·©ž¦§üÞÏjðÔÏjÏpªO 1000 ü‘Ï@ÝÏ÷ýåÝrÏ÷­C

üoðàús¾\î…¾uî…Ýb Windows Ï× UNIX ùtý×ÏWùØ¾×­C

26.1.2 ¦¸vøíÇD

Ýp¦GñzñoùÏFÏUÝCøT©õ­G

FLG0083E­GñzùSÝü­uIBM ÷ˆøT®ª¨ì§èýzæ{Ý­ø_¸lü]¸w­vÏ«¾×æ{Ý­¦§Ýü©Žñ¶v­C
«Ñª½÷áñzú¡Ýa¦§ün‚÷góPøà¸× IBM ú~øÔ¾N¦¡­C

ñz¾ýôúµÒôR DB2 Warehouse Manager ¸× IBM DB2 OLAP Server­A ùÇÝw÷Ó­u÷ˆøT®ª¨ì
§èýzæ{Ý­­vÏ÷¾¢­Aú¡ÏÏ¾]õtÏF­u÷ˆøT®ª¨ìø_¸lü]¸w­vÏ«¾×æ{Ý­­C

26.1.3 Ýw÷ÓøíÇD

ðYñzÝbÝw÷ÓÏF DB2 Warehouse Manager ¸× IBM DB2 OLAP Server Ïõ® ­AÏSÝbªêÝP¦§
Ïuõ@î÷ÏWÝw÷Ó ù„¾Ý­u÷ˆøT®ª¨ì§èýzæ{Ý­§èýz¦Þ­vÏ÷¾¢ (õQ¾× DB2 Universal
Database CD-ROM)­A ®Kú|¶Ñ¬gðÝü¦§÷ˆøT®ª¨ìø_¸lü]¸wÏ«¾×æ{Ý­­CÝû©­Añz¾i¾Hñq
\sqllib\bin ¾¨ìÏU­Aõ„¾X createic.bak ¯P flgnmwcr.bak ·©ž­AñNù„Ï·õOõ¢ÝWªø
createic.exe Ï× flgnmwcr.exe­C

ðYñzðn¾t¾~Ýw÷Ó DB2 Universal Database ÏW¦§­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏ÷¾¢­A®hüoù€
Ï÷¾¢ Ïœî…Ýw÷ÓÝb Data Warehouse Manager ¸ãÝw÷Ó¦§ÝPÏ@ü­Ïuõ@î÷ÏW­Cñz¾i¾Hø¥ó\
­uDB2 Warehouse Manager Ýw÷ÓÏƒ¾U­v¦§ýŽ 3 üû­uÝw÷Ó÷ˆøT®ª¨ì§èýzæ{Ý­Ï÷¾¢­v­Aªd
ªíôiÏ@ùB¦§÷ˆøT­C
  ------------------------------------------------------------------------

26.2 ¾H DB2 ¦¸¾¯ 7 ÷ˆøT®ª¨ì§èýzæ{Ý­Ýsù£ DB2 ¦¸¾¯ 5 ÷ˆøT®ª¨ì

¾¥ DB2 ¦¸¾¯ 7 Ýw÷Óæ{õ€¸ãª[§c¦§ DB2 ¦¸¾¯ 7 ÷ˆøT®ª¨ì§èýzæ{Ý­Ý÷Ï÷¾¢­AÏ„ï¸Ýsù£
·xÝsÝb DB2 ¦¸¾¯ 6 ¸M DB2 ¦¸¾¯ 7 ÷ˆ©’©w¦§÷ˆøT®ª¨ì­Cðžõ‹Ý÷Ï÷¾¢¦§ª[§c­AÝsù£·x
ÝsÝb DB2 ¦¸¾¯ 5 ÷ˆ©’©w¦§÷ˆøT®ª¨ì­CDB2 ¦¸¾¯ 7 ÷ˆøT®ª¨ì§èýzæ{Ý­Ý÷Ýù¾öùÇÏœÏ„ï¸
Ýsù£ DB2 ¦¸¾¯ 2 ¸×Ïõ®e¦¸¾¯¦§÷ˆ©’­C

ü]¸w÷ˆøT®ª¨ì§èýz¦Þ­AÝs÷ˆøT®ª¨ì¦§÷ˆøT®ª¨ìùØ¾×¦Þ¸M÷ˆøT®ª¨ìø_¸lü]¸wÏ«¾×æ{Ý­­A
·xÝsÝb DB2 ¦¸¾¯ 5 ÷ˆ©’©w­G

  1. ÝbùSÝüÝw÷Ó DB2 ¦¸¾¯ 7 ÷ˆøT®ª¨ì§èýzæ{Ý­¦§Ïuõ@î÷­AÝw÷Ó DB2 Connect
     Enterprise Edition ¦¸¾¯ 6­C

     DB2 Connect Enterprise Edition ªO DB2 Universal Database Enterprise
     Edition ¸M DB2 Universal Database Enterprise - Extended Edition ¦§Ï@ü­
     Ï·­C Ýp¦GÝw÷Óüoù€ DB2 ýœ®~¦§¦¸¾¯ 6­AæLôú¾t¾~Ýw÷Ó DB2 Connect­C
     ððùŒ:
          ÝbªêÝP¦§ Windows NT ¸× OS/2 Ïuõ@î÷­AÏœî…Ýw÷Ó DB2 Ýhð®¦¸¾¯­Cñz¾i¾H
          Ýbù„¾Ý Windows NT Ïuõ@î÷­B OS/2 Ïuõ@î÷¸× UNIX Ïuõ@î÷ÏWÝw÷Ó DB2
          Connect­C
  2. ª[§c÷ˆøT®ª¨ì§èýzæ{Ý­¸M DB2 Connect ¦¸¾¯ 6­AÝsù£ DB2 ¦¸¾¯ 5 ¦§÷ˆ©’­C÷â
     ýà÷ˆøT­A«Ñø¥ó\ DB2 Connect ùØ¾×Ïƒ¾U­C¾HÏUªø¾ýðnùB’J¦§úõ’[­G
       a. Ýb DB2 ¦¸¾¯ 5 ùtý×­AùØ¾× DB2 ¸R¾OÝ‘üBýzóû«s¾¦¸¾¯ 5 ¦§÷ˆ©’©w­AÝs
          ù£÷ˆøT®ª¨ì§èýzæ{Ý­­C
       b. Ýb DB2 Connect ùtý×­AùØ¾× DB2 ¸R¾OÝ‘üBýzóûôiÝ‘«s¾­G
             + DB2 ¦¸¾¯ 5 ùtý×¦§ TCP/IP ÷`¶I
             + DB2 ¦¸¾¯ 5 ùtý×¦§÷ˆ©’©w
             + DB2 ¦¸¾¯ 5 ùtý×¦§ DCS æn¨ìôæ¾
       c. Ýb÷ˆøT®ª¨ì§èýzæ{Ý­¦§Ïuõ@î÷­AùØ¾× DB2 ¸R¾OÝ‘üBýzóûôiÝ‘«s¾­G
             + DB2 Connect ùtý×¦§ TCP/IP ÷`¶I
             + DB2 Connect ùtý×¦§÷ˆ©’©w

     ÝüÇ”«s¾÷ˆ©’©w¦§÷ˆøT­A«Ñø¥ó\ DB2 Universal Database Ýw÷Ó¯Pª[§c÷¾R
  3. ¸¢÷ˆøT®ª¨ì§èýzæ{Ý­¦§ðš·x­AñN DB2 CLI ©M÷Óün‚¸MüzûL DB2 Connect ¸ãÝsù£
     ¦§ÝUðà÷ˆ©’©wôiÝ‘üsæý­C

     ÏUÝC DB2 ®¾Oïœù¥üsæýù v5database ¦§«dùã­A Ï@ðàøýü]¸Ò¦§ DB2 ¦¸¾¯ 5 ¦§
     ÷ˆ©’©w­CùØ¾× DB2 ¸R¾OÝ‘üBýzóûæo¾XÏUÝC®¾O­Cdb2cli.lst Ï× db2ajgrt ¦§Ý
     ÷mÝb \sqllib\bnd ¾¨ìÏÏ­C

     db2 connect to v5database user ùØ¾×¦Þ ID using üqÝ‘«X
     db2 bind db2ajgrt.bnd
     db2 bind @db2cli.lst blocking all grant public

     ùØ¾×¦Þ ID ªO v5database ¦§ùØ¾×¦Þ­A üqÝ‘«XªO®ùØ¾×¦Þ ID ¦§üqÝ‘«X­C

     db2cli.list üQüsæýù DB2 ¦¸¾¯ 5 ÷ˆ©’©w©­Aú|æo¾Ö¨—¯~­Cæo¾Ö¨—¯~­AªOÝ]ªø
     Ýûª[§cùÇÏœÏ„ï¸Ïj®ª¦®¾¢­Cüoôæ¨—¯~Ïœú|¬vTðš·x¾Nýzæ{Ý­û‹ DB2 ¦¸¾¯ 5 ÷ˆ©’
     ©w¦§Ýsù£­C

     ¯íðnÝü DB2 Universal Database ¦¸¾¯ 5 ¦§ FixPak 14 (¸¢ 2000 Ý~ 6 Ï‰æo
     Ý‘)­A Ï~î…üzûL DB2 Connect ùàÝsù£ DB2 ¦¸¾¯ 5 ¦§÷ˆ©’­C«Ñø¥úà FixPak Ï§
     ¦§ APAR «s÷û JR14507­C

  ------------------------------------------------------------------------

26.3 ü]÷m÷ˆøT®ª¨ì

ÝbýŽ 1 üûýŽ 1 ªq¦§ùB’J 2­uü]÷m÷ˆøT®ª¨ì­vïœù­G

   ú¡ñzÝw÷ÓÏF DB2 Warehouse Manager ¸× DB2 OLAP Server­A
   õYú|Ýb DB2 Universal Database for Windows NT ÏÏ®¾áûwü]¦§÷ˆøT®ª¨ì­C

üoðàüîðzÝ­ªOÏœ¾¨«T¦§­Cñz¾ýôú¸w÷qús¦§÷ˆøT®ª¨ì­C÷âýà÷ˆøT­A«Ñø¥ó\­u®¾á÷ˆøT®ª
¨ì­vü­¾ö­C
  ------------------------------------------------------------------------

26.4 ¯Pù„¾Ýýœ®~¾‘ï®ïyðz÷ˆ©’

ÝbýŽ 6 üû­u¯Pù„¾Ýýœ®~¾‘ï®ïyðz÷ˆ©’­v¦§­uÇ¥õOðnÏ«õG¦§ OLAP ¦®¾¢­vøØªq­A ÝbýŽ
ÏGªqÝüÏ@ðà¾yÏlïœù­G

   ú¡ñzÏ«õG DB2 OLAP óÆÝXÝ›¦Aóûïyðz÷ˆ©’©­A
   ú|Ýb÷ˆøT®ª¨ì¦§­uÝhð®§–®ž÷ˆ©’©wô­¦§§–®ž­v¯P OLAP
   óÆÝXÝ›¦Aóû¦§¦¡©‘¦®¾¢ô­®¾áÇæýÇ”®Y­C

üoªq¯­¸£·üÝpÏU¸ã¾š­G

   ú¡ñzÏ«õG DB2 OLAP óÆÝXÝ›¦Aóûïyðz÷ˆ©’©­A
   ú|Ýb÷ˆøT®ª¨ì­uÝhð®§–®ž÷ˆ©’©w¦®¾¢Ï×¦¡©‘¦®¾¢ÏÏ¦§§–®ž­v
   Ïõô­®¾áÇæýÇ”®Y­C

üoÏ@¾yÏ]¾Xý{Ýb¦ç¨ì C ­uïyðz÷ˆ©’û‹ªM­v¦§­u÷ˆøT®ª¨ì§èýzæ{Ý­¯P OLAP Ý›¦Aóûô­¦§
ïyðz÷ˆ©’û‹ªM­vøØªq­C
  ------------------------------------------------------------------------

26.5 ùØ¾× flgnxoln ®¾O¾‘ï®ïyðz÷ˆ©’

ÝbýŽ 6 üû­u¾‘ï®ïyðz÷ˆ©’­vÏÏÝüÏ@ðàªq÷ù¦§¬ÑÇDªO ­uÇ¥õOðnÏ«õG¦§ OLAP ¦®¾¢­v­C
Ýbªq÷ù¦§üÞ® ðñÝüùØ¾× flgnxoln ®¾OùàÏ«õG OLAP Ý›¦Aóûïyðz÷ˆ©’ù÷ˆøT®ª¨ì¦§«d
ùã­CÝû«dùãÆ¾š db2olap.ctl ¸M db2olap.ff ·©ž¦§¾¨ìªø x:\Program
Files\sqllib\logging­A üoªOÏœ¾¨«T¦§­C¾¨ì·ü÷àÝpýŽ 87 ðô¸ã¯­­G x:\Program
Files\sqllib\exchange­C
  ------------------------------------------------------------------------

26.6 ùØ¾× MDISDGC ®¾O¾‘ï®ïyðz÷ˆ©’

ýŽ 6 üû­u¯Pù„¾Ýýœ®~¾‘ï®ïyðz÷ˆ©’­v¦§­uñNýÝX MDIS ¦§ïyðz÷ˆ©’¶…ï®ù¬Ñ¾š¯yù¾
·­v(ýŽ 89 ðô)­CñzÏœ¾i¾Hñq MS-DOS ¸R¾Oïœ¾šÏUæo¾X MDISDGC ®¾O­AÝà·ü÷àñq DB2
¸R¾Oæ›æ­ÏÏæo¾X÷à®¾O­C÷àüû÷`¦§ýŽÏ@¾y¬gûD­G­uñN MDIS ©‘Ý­¦§ïyðz÷ˆ©’¶…ï®Ýù¬Ñ
¾š¯yù¾·­vÏÏ¾‡ïœùñz¾ý ñq MS-DOS ¸R¾Oïœ¾šæo¾X DGMDISC ®¾O­Cñz¾ýôúñq DB2 ¸R
¾Oæ›æ­ÏÏæo¾X DGMDISC ®¾O­C
  ------------------------------------------------------------------------

26.7 ¸I¾sæ{Ý­

­u÷ˆøT®ª¨ì§èýzÏƒ¾U­vÏÏü­Ï·¦§«dùãÏÏ¦§®¾O¾]õtÏF Program Files ¦§¾¨ìÝW§ë­Cú¡
ñz¸I¾sÏ@ðà¾]õt Program Files ¾¨ìÝW§ë¦§®¾O©­A ñz¾ýôúñNæ{Ý­¸I¾s¾]Ýb¶—Ïè÷û
Ï§­C ùãÝpÝb¦ç¨ì B ­uûw¾ì¸w÷q¦§÷ˆøT®ª¨ì§èýzæ{Ý­¦®¾¢Çç®ª­v ¦§­u¾Hûw¾ì¸w÷q¦§¦®
¾¢Çç®ªø_¸lü]¸wñz¦§÷ˆøT®ª¨ì­vªq÷ùÏÏÝüÏ@ðà«dùã­CÝp¦GñzùØ¾×üo÷Þ ¦§«dùã­Aú¡ñzñq
DOS ïœ¾šý÷ûøäÝ‘¾Ý©ú|ñoù¨—¯~øT©õ­CÏUÝCªO¾¨«T¦§«dùã­G

   "X:Program Files\SQLLIB\SAMPLES\SAMPDATA\DGWDEMO"
   /T userid password dgname

  ------------------------------------------------------------------------

Information Catalog Manager Programming Guide and Reference(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

27.1 Information Catalog Manager Reason Codes

In Appendix D: Information Catalog Manager reason codes, some text might be
truncated at the far right column for the following reason codes: 31014,
32727, 32728, 32729, 32730, 32735, 32736, 32737, 33000, 37507, 37511, and
39206. If the text is truncated, please see the HTML version of the book to
view the complete column.
  ------------------------------------------------------------------------

÷ˆøT®ª¨ì§èýzæ{Ý­ùØ¾×Ïƒ¾U

ÝbýŽ 2 üû­AÝüÏ@ðàªq÷ù§ëªø­uænøOÝ›¦Aóû÷`¶I¯P¯ú§í÷ˆøT®ª¨ì­v­CÝûøØªqÝC¾XÏFñzÝb
ùØ¾×­u÷ˆøT®ª¨ì§èýzæ{Ý­­vænøO¯ú§í÷ˆøT®ª¨ì©¾iñq­uDB2 ññùŒÏÏÏá­v õûÝù¦§ùB’J­C
üoðàüû÷`¦§üÞ® Ï@ðàªq÷ùïœùÝbñq­uDB2 ññùŒÏÏÏá­võûÝùüoù€ùB’JÏõ®  (ús¬Wùtý×­B
ús¬W©žùãÏ×ús¬W÷ˆ©’©w)­AÝbô}ñã­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏõ®e¾ýôúÇ”üª ­uññùŒÏÏ
Ïá­v­Cüoôæ÷ˆøTùÇÏœ¾¨«T­CÝbô}ñã­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏõ®eùÇÏœ¯íðnÇ”üª ­uññùŒÏÏ
Ïá­v­C

ÝP¬Ó¦§ðž¾¨Ï]óA¾×¸¢­uænøOÝ›¦Aóû÷`¶IÏ×¯ú§í÷ˆøT®ª¨ì­võ@ú~¦§«uÏW¯­¸£­A¾HÏ×­uæn
øO Ý›¦Aóû÷`¶IÏ×÷ˆøT®ª¨ì­væ›æ­¦§«uÏW¯­¸£­C
  ------------------------------------------------------------------------

÷ˆøT®ª¨ì§èýzæ{Ý­­G«uÏWøT©õ

  ------------------------------------------------------------------------

29.1 øT©õ FLG0260E

øT©õ¯­¸£¦§ýŽÏG¾y·üªø­G

   ¨—¯~üyÝù÷ˆøT®ª¨ì¾½ñ¥¦§ rollback­C
   ÷ˆøT®ª¨ì¦§¦ª¦pÏœÇð¸w­AÝìªO­AùSÝü¯süy¾“Ý¢¦§šõ¢­C

  ------------------------------------------------------------------------

29.2 øT©õ FLG0051E

øT©õ¯­¸£Ï§¦§ýŽÏGôæ¾ý÷û·üªø­G

   ÷ˆøT®ª¨ìõtÝüÏàÝh¦®¾¢¸×¦®¾¢Çç®ª­C

§èýz¦ÞÝ^·üªø­G

   ùØ¾×ôžÏJù‡¬’ñq¾®e÷ˆøT®ª¨ìõRøœü­¾ö¦®¾¢¸×¦®¾¢Çç®ª­C

  ------------------------------------------------------------------------

29.3 øT©õ FLG0003E

øT©õ¯­¸£·üªø­G

   ÷ˆøT®ª¨ì¾ýôúÝbùØ¾×®eôiÝ‘ænøO­C
  ÷ˆøT®ª¨ì¾iî…ænøO¨—¯~­C

  ------------------------------------------------------------------------

29.4 øT©õ FLG0372E

øT©õ¯­¸£¦§ýŽÏ@¾y·üªø­G

   ATTACHMENT-IND ðÔªø¦®¾¢¸ã¸¨ýÏ­AÝ]ªø÷à¦®¾¢ªO Attachment ¦®¾¢­C

  ------------------------------------------------------------------------

29.5 øT©õ FLG0615E

øT©õ¦§ýŽÏG¾y·üªø­G

   ­u÷ˆøT®ª¨ì§èýzæ{Ý­­vûJù®Dûwïµ¦§÷ˆ©’©w¨—¯~­A
   ¸×¦ÞÝb¾®e¦§¾¨ì¸×÷“©|÷Þõ„Ïœùüsæý·­C

  ------------------------------------------------------------------------

÷ˆøT®ª¨ì§èýzæ{Ý­­G«uÏW¯­¸£

÷ˆøT®ª¨ìæ›æ­­G¨‹ù£¦§¾\î…¦¡ô}ñãôæ¾¦§«uÏW¯­¸£¨—¯~Ýa¯­­uô}ñã¨‹ù£¦§¦®¾¢­v­C¾Ý
·ü÷à¯­­uô}ñã¸w÷qújïMæ›æ­­v­C
  ------------------------------------------------------------------------

30.1 Web ÷ˆøT®ª¨ì§èýzæ{Ý­

ùØ¾×Ý¸¢ DB2 UDB for OS/390 system ¦§÷ˆøT®ª¨ì­AùSÝüÏœøØÏ·ÏjÏp¬gújïM¦§¾\î…­C
¶ýÝ­újïM¸Môiô¾újïM¦§ñ­¦püœªOÝpÝû­C«uÏW¯­¸£ùÇùSÝü÷¥Žô­Aû‹¸¢¶ýÝ­újïM­ADB2 UDB
for OS/390 ÷ˆøT®ª¨ì¦§¸ãÝüújïMªøøØÏ·ÏjÏp¬g¦§­CÝû¾~­A¸ãÝüÏ·ýå§Çç¦®¾¢üœ¾i¾H¶X
¾R­AõYùØ¾ÝðÞÏœªOø•¶Ý¦®¾¢­C
  ------------------------------------------------------------------------

DB2 Warehouse Manager Ýw÷ÓÏƒ¾U

  ------------------------------------------------------------------------

31.1 ðš·x¶…ï®æ{Ý­¦§ün‚¯íùD

Ýbñzðpû§ðnùØ¾×ðš·x¶…ï®æ{Ý­¦§÷ˆ©’©wÏW­A¾ýôú¾ìÝw÷Ó Java Developer's Kit (JDK)
¦¸¾¯ 1.1.8 (¸×¾HÏW)­C
  ------------------------------------------------------------------------

31.2 SAP R/3 Connector

ñq SAP R/3 øàú~¦®¾¢Ž‘Ýû‹ªM¦«Ž‘ù DB2 ¦¡©‘©­A Ýüù€ýœ¾Ö¦§¦«Ž‘ÝW§ë¾iî…ú|ôWûL
30 ÝrÏ÷­CÝbÝûñ­¦pÏU­A ýœ¾Ö¦§¦«Ž‘ÝW§ë¾uú|ÏØªM SAP Ž‘ÝÝW§ë¦§®e 30 ðàÝr­CðYýœ
¾Ö¦§ÝW§ëùÇ®Dñz¸ãðn¦§­Añz¾i¾HùØ¾×­uÏ§©e­væõøO¾¯šõ¢¦¡©‘­C

31.2.1 Ýw÷Ó¾ìùMñ›¾¢

ü]¸w RFC_INI ·“ûãš¬’­CùãÝp­A Set RFC_INI=c:\rfcapl.ini­C Ýbü]¸wš¬’Ïõ® ­A
«ÑñzøÔ¾ýð®úsñãøÒûq÷œ­C
  ------------------------------------------------------------------------

31.3 Web Connector

ðYñzÝbøäÝ‘ Web Connector æo¾ÖøíÇD­AIBM ¦AøÔæ{Ý­¾iî…ú|ðnùDñzô€øe Connector
¦§øl¶š­C

ðYðnñã¾× Web Connector ¦§øl¶š­A«ÑñN Warehouse Center ¾Nýzæ{Ý­¦§øl¶šü]¸wªøÏj
¸¢ 0­Cøl¶š·¦§ÝW§ëªø WSApid.log­A ù„ÏÏæ{õ€ ID ªO¾Nýzæ{Ý­¦§ Windows æ{õ€
ID­Cøl¶š·ú|®¾á¸¢ \sqllib\logging ¾¨ìÏU­C

31.3.1 Ýw÷Ó¾ìùMñ›¾¢

«ÑÝw÷Ó Java øäÝ‘·“ûã (JRE) ¸× Java Virtual Machine (JVM) ¦¸¾¯ 1.2.2 (¸×¾H
ÏW)­AùÇñN¾Ýü]Ýùñz¦§ûwü]­CðYðn®¾á JRE ¦¸¾¯õ@ªøñz¦§ûwü]­A«ÑñN 1.2.2 JRE ¦§÷“
©|ús¬Wùñz¦§ùtý× PATH š¬’ÏÏ (Ýp C:\JDKs\IBM\java12\bin;)­CÝbšõ¢ûwü] JRE
Ïõ® ­A«ÑñzøÔ¾ýð®úsñãøÒûq÷œ­CðYñz¾¬Ýw÷Ó Java­A ñz¾i¾HñqÝw÷Ó Data Warehouse
Connector ¦§ CD ùàÝw÷Ó­C
  ------------------------------------------------------------------------

Query Patroller Administration Guide(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

32.1 DB2 Query Patroller Client is a Separate Component

The DB2 Query Patroller client is a separate component that is not part of
the DB2 Administration client. This means that it is not installed during
the installation of the DB2 Administration Client, as indicated in the
Query Patroller Installation Guide. Instead, the Query Patroller client
must be installed separately.

The version and level of the Query Patroller client and the Query Patroller
server must be the same.
  ------------------------------------------------------------------------

32.2 Migrating from Version 6 of DB2 Query Patroller Using dqpmigrate

The dqpmigrate command must be used if the Version 7 Query Patroller Server
was installed over the Version 6 Query Patroller Server. For FixPak 2 or
later, you do not have to run dqpmigrate manually as the installation of
the FixPak runs this command for you. Without using this command, the
existing users defined in v6 have no EXECUTE privileges on several new
stored procedures added in Version 7.

Note:
     dqpmigrate.bnd is found in the sqllib/bnd directory and dqpmigrate.exe
     is found in the sqllib/bin directory.

To use dqpmigrate manually to grant the EXECUTE privileges, perform the
following after installing the FixPak:

  1. Bind the /sqllib/bnd/dqpmigrate.bnd package file to the database where
     the Query Patroller server has been installed by entering the
     following command:

     db2 bind dqpmigrate.bnd

  2. Execute dqpmigrate by entering the following:

     dqpmigrate dbalias userid passwd

  ------------------------------------------------------------------------

32.3 Enabling Query Management

In the "Getting Started" chapter under "Enabling Query Management", the
text should read:

   You must be the owner of the data base, or you must have SYSADM,
   SYSCTRL, or SYSMAINT authority to set database configuration parameters.

  ------------------------------------------------------------------------

32.4 Location of Table Space for Control Tables

In Chapter 1, System Overview, under DB2 Query Patroller Control Tables,
the following text is to be added at the end of the section's first
paragraph:

The table space for the DB2 Query Patroller control tables must reside in a
single-node nodegroup, or DB2 Query Patroller will not function properly.
  ------------------------------------------------------------------------

32.5 New Parameters for dqpstart Command

In Chapter 2, Getting Started, under Starting and Stopping DB2 Query
Patroller, the following text is to be added following the last paragraph:

New Parameters for the dqpstart command:

RESTART parameter:
     Allows the user to replace the host name and/or the node type of the
     specified node in the dqpnodes.cfg file. DB2 Query Patroller will be
     started on this node.

     Note:
          Before running the DQPSTART command with the RESTART parameter,
          ensure the following:

            1. DB2 Query Patroller is already stopped on the host that is
               going to be replaced.
            2. DB2 Query Patroller is not already running on the new host.
     The syntax is as follows:

     dqpstart nodenum node_num restart hostname server | agent | none

ADDNODE parameter:
     Allows the user to add a new node to the dqpnodes.cfg file. DB2 Query
     Patroller will be started on this node after the new node entry is
     added to the dqpnodes.cfg file. The syntax is as follows:

     dqpstart nodenum node_num addnode hostname server | agent | none

DROPNODE parameter:
     Allows the user to drop a node from the dqnodes.cfg file. DB2 Query
     Patroller will be stopped on this node before the node entry is
     dropped from the dqpnodes.cfg file. The syntax is as follows:

     dqpstop nodenum node_num dropnode

  ------------------------------------------------------------------------

32.6 New Parameter for iwm_cmd Command

A new -v parameter has been added to the iwm_cmd command to allow the user
to recover the status of the jobs that were running on the node specified.
Only jobs on an inactive node are allowed to be recovered. This command
should be issued when there is a node failure and there are some jobs
running on that node or being cancelled at the time. Jobs that were in
"Running" state will be resubmitted and set back to "Queued" state. Jobs
that were in "Cancelling" state will be set to "Cancelled" state.

The partial syntax is as follows:

>>-iwm_cmd----+---------------------------------+--------------->
              '--u--user_id--+---------------+--'
                             '--p--password--'

>-----v--node_id_to_recover------------------------------------><


node_id_to_recover
     Specifies the node on which the jobs are to be recovered.

  ------------------------------------------------------------------------

32.7 New Registry Variable: DQP_RECOVERY_INTERVAL

There is a new registry variable called DQP_RECOVERY_INTERVAL which is used
to set the interval of time in minutes that the iwm_scheduler searches for
recovery files. The default is 60 minutes.
  ------------------------------------------------------------------------

32.8 Starting Query Administrator

In the "Using QueryAdministrator to Administer DB2 Query Patroller"
chapter, instructions are provided for starting QueryAdministrator from the
Start menu on Windows. The first step provides the following text:

   If you are using Windows, you can select DB2
   Query Patroller --> QueryAdministrator
   from the IBM DB2 program group.

The text should read:

   DB2 Query Patroller --> QueryAdmin.

  ------------------------------------------------------------------------

32.9 User Administration

In the "User Administration" section of the "Using QueryAdministrator to
Administer DB2 Query Patroller" chapter, the definition for the Maximum
Elapsed Time parameter indicates that if the value is set to 0 or -1, the
query will always run to completion. This parameter cannot be set to a
negative value. The text should indicate that if the value is set to 0, the
query will always run to completion.

The Max Queries parameter specifies the maximum number of jobs that the DB2
Query Patroller will run simultaneously. Max Queries must be an integer
within the range of 0 to 32767.
  ------------------------------------------------------------------------

32.10 Creating a Job Queue

In the "Job Queue Administration" section of the "Using QueryAdministrator
to Administer DB2 Query Patroller" chapter, the screen capture in the steps
for "Creating a Job Queue" should be displayed after the second step. The
Information about new Job Queue window opens once you click New on the Job
Queue Administration page of the QueryAdministrator tool.

References to the Job Queues page or the Job Queues tab should read Job
Queue Administration page and Job Queue Administration tab, respectively.
  ------------------------------------------------------------------------

32.11 Using the Command Line Interface

For a user with User authority on the DB2 Query Patroller system to submit
a query and have a result table created, the user may require CREATETAB
authority on the database. The user does not require CREATETAB authority on
the database if the DQP_RES_TBLSPC profile variable is left unset, or if
the DQP_RES_TBLSPC profile variable is set to the name of the default table
space. The creation of the result tables will succeed in this case because
users have the authority to create tables in the default table space.
  ------------------------------------------------------------------------

32.12 Query Enabler Notes

   * When using third-party query tools that use a keyset cursor, queries
     will not be intercepted. In order for Query Enabler to intercept these
     queries, you must modify the db2cli.ini file to include:

        [common]
        DisableKeySetCursor=1

   * For AIX clients, please ensure that the environment variable LIBPATH
     is not set. Library libXext.a, shipped with the JDK, is not compatible
     with the library in the /usr/lib/X11 subdirectory. This will cause
     problems with the Query Enabler GUI.

  ------------------------------------------------------------------------

32.13 DB2 Query Patroller Tracker may Return a Blank Column Page

FixPak 3 includes a fix for the DB2 Query Patroller Tracker. The Tracker
will now correctly report queries which hit no columns. An example of such
a query is "SELECT COUNT(*) FROM ...". Since this kind of query does not
hit any column in the table, the Tracker will present a blank page for the
column page. This blank column page is not a defect.
  ------------------------------------------------------------------------

32.14 Query Patroller and Replication Tools

Query Patroller Version 7 will intercept the queries of the replication
tools (asnapply, asnccp, djra and analyze) and cause these tools to
malfunction. A workaround is to disable dynamic query management when
running these tools.
  ------------------------------------------------------------------------

32.15 Appendix B. Troubleshooting DB2 Query Patroller Clients

In Appendix B, Troubleshooting DB2 Query Patroller Clients, section: Common
Query Enabler Problems, problem #2, the text of the first bullet is
replaced with:

   Ensure that the path setting includes jre.

  ------------------------------------------------------------------------

·ü¾×æ{Ý­ô}æo

ü­¾ö¾¨ì

   * Administrative API Reference (æLÏÏÏ†¦¸)
        o 33.1 db2ArchiveLog (new API)
             + db2ArchiveLog
        o 33.2 db2ConvMonStream
        o 33.3 db2DatabasePing (new API)
             + db2DatabasePing - Ping Database
        o 33.4 db2HistData
        o 33.5 db2HistoryOpenScan
        o 33.6 db2XaGetInfo (new API)
             + db2XaGetInfo - Get Information for Resource Manager
        o 33.7 db2XaListIndTrans (new API that supercedes sqlxphqr)
             + db2XaListIndTrans - List Indoubt Transactions
        o 33.8 db2GetSnapshot - Get Snapshot
        o 33.9 Forget Log Record
        o 33.10 sqlaintp - Get Error Message
        o 33.11 sqlbctcq - Close Tablespace Container Query
        o 33.12 sqlubkp - Backup Database
        o 33.13 sqlureot - Reorganize Table
        o 33.14 sqlurestore - Restore Database
        o 33.15 Documentation Error Regarding AIX Extended Shared Memory
          Support (EXTSHM)
        o 33.16 SQLFUPD
             + 33.16.1 locklist
        o 33.17 SQLEDBDESC
        o 33.18 SQLFUPD Documentation Error

   * ·ü¾×æ{Ý­ô}æoÏƒ¾U
        o 34.1 ýŽ 1 üû ¶ýÏô
             + 34.1.1 Ï„ï¸ün‚
             + 34.1.2 «dùãæ{Ý­
        o 34.2 ýŽ 3 üû ô}æo DB2 ·ü¾×æ{Ý­¦§Ï@î‰÷ˆøT
             + 34.2.1 ô}æo·©ž­Bmake ·¸M¨—¯~·Óªd¦§Ï«¾×æ{Ý­
        o 34.3 ýŽ 4 üû ô}æo Java Applets ¸M·ü¾×æ{Ý­
             + 34.3.1 ü]¸w·“ûã
                  + 34.3.1.1 OS/2 ÏW¦§ JDK ¬hÝ÷
                  + 34.3.1.2 HP-UX ÏW¦§ Java2
        o 34.4 ýŽ 5 üû ô}æo SQL æ{õ€
             + 34.4.1 ü]¸w SQL æ{õ€·“ûã
             + 34.4.2 ü]¸w«sŽôóû·“ûãš¬’
             + 34.4.3 Ýêðq«sŽô®¾O
             + 34.4.4 ®OîdÏÏô­·
             + 34.4.5 ü’¾ö¸Mï_÷m
             + 34.4.6 ®¾á SQL æ{õ€
             + 34.4.7 ¸I¾s·xÝsæ{õ€
             + 34.4.8 Ï·øeÏw«sŽô¦§ SQL æ{õ€
        o 34.5 ýŽ 7 üû ô}æo HP-UX ·ü¾×æ{Ý­
             + 34.5.1 HP-UX C
             + 34.5.2 HP-UX C++
        o 34.6 ýŽ 9 üû ô}æo OS/2 ·ü¾×æ{Ý­
             + 34.6.1 VisualAge C++ for OS/2 ¦¸¾¯ 4.0
        o 34.7 ýŽ 10 üû ô}æo PTX ·ü¾×æ{Ý­
             + 34.7.1 ptx/C++
        o 34.8 ýŽ 12 üû ô}æo Solaris ·ü¾×æ{Ý­
             + 34.8.1 SPARCompiler C++
        o 34.9 ýŽ 13 üû ®÷m Windows 32 ÝÏ÷õ@ú~ùtý×¦§·ü¾×æ{Ý­
             + 34.9.1 VisualAge C++ ¦¸¾¯ 4.0

   * Application Development Guide(æLÏÏÏ†¦¸)
        o 35.1 Chapter 2. Coding a DB2 Application
             + 35.1.1 Activating the IBM DB2 Universal Database Project and
               Tool Add-ins for Microsoft Visual C++
        o 35.2 Chapter 6. Common DB2 Application Techniques
             + 35.2.1 Generating Sequential Values
                  + 35.2.1.1 Controlling Sequence Behavior
                  + 35.2.1.2 Improving Performance with Sequence Objects
                  + 35.2.1.3 Comparing Sequence Objects and Identity
                    Columns
        o 35.3 Chapter 7. Stored Procedures
             + 35.3.1 DECIMAL Type Fails in Linux Java Routines
             + 35.3.2 Using Cursors in Recursive Stored Procedures
             + 35.3.3 Writing OLE Automation Stored Procedures
        o 35.4 Chapter 12. Working with Complex Objects: User-Defined
          Structured Types
             + 35.4.1 Inserting Structured Type Attributes Into Columns
        o 35.5 Chapter 13. Using Large Objects (LOBs)
             + 35.5.1 Large object (LOBs) support in federated database
               systems
                  + 35.5.1.1 How DB2 retrieves LOBs
                  + 35.5.1.2 How applications can use LOB locators
                  + 35.5.1.3 Restrictions on LOBs
                  + 35.5.1.4 Mappings between LOB and non-LOB data types
             + 35.5.2 Tuning the system
        o 35.6 Part 5. DB2 Programming Considerations
             + 35.6.1 IBM DB2 OLE DB Provider
        o 35.7 Chapter 20. Programming in C and C++
             + 35.7.1 C/C++ Types for Stored Procedures, Functions, and
               Methods
        o 35.8 Chapter 21. Programming in Java
             + 35.8.1 Java Method Signature in PARAMETER STYLE JAVA
               Procedures and Functions
             + 35.8.2 Connecting to the JDBC Applet Server
        o 35.9 Appendix B. Sample Programs

   * CLI Guide and Reference(æLÏÏÏ†¦¸)
        o 36.1 Binding Database Utilities Using the Run-Time Client
        o 36.2 Using Static SQL in CLI Applications
        o 36.3 Limitations of JDBC/ODBC/CLI Static Profiling
        o 36.4 ADT Transforms
        o 36.5 Chapter 3. Using Advanced Features
             + 36.5.1 Writing Multi-Threaded Applications
             + 36.5.2 Scrollable Cursors
                  + 36.5.2.1 Server-side Scrollable Cursor Support for
                    OS/390
             + 36.5.3 Using Compound SQL
             + 36.5.4 Using Stored Procedures
                  + 36.5.4.1 Writing a Stored Procedure in CLI
                  + 36.5.4.2 CLI Stored Procedures and Autobinding
        o 36.6 Chapter 4. Configuring CLI/ODBC and Running Sample
          Applications
             + 36.6.1 Configuration Keywords
        o 36.7 Chapter 5. DB2 CLI Functions
             + 36.7.1 SQLBindFileToParam - Bind LOB File Reference to LOB
               Parameter
             + 36.7.2 SQLNextResult - Associate Next Result Set with
               Another Statement Handle
                  + 36.7.2.1 Purpose
                  + 36.7.2.2 Syntax
                  + 36.7.2.3 Function Arguments
                  + 36.7.2.4 Usage
                  + 36.7.2.5 Return Codes
                  + 36.7.2.6 Diagnostics
                  + 36.7.2.7 Restrictions
                  + 36.7.2.8 References
        o 36.8 Appendix D. Extended Scalar Functions
             + 36.8.1 Date and Time Functions
        o 36.9 Appendix K. Using the DB2 CLI/ODBC/JDBC Trace Facility

   * øT©õø¥ÝãÏƒ¾U
        o 37.1 ù£ñoøT©õ¯P SQLSTATE ¯­¸£
        o 37.2 Ýb DB2 Connect šõ¢¦§ SQLCODE ð®úsû‹ªM
        o 37.3 ús¦§¯Pšõ¢¦§øT©õ
             + 37.3.1 ¸I¾s¬hÝ÷Ïôðñ (CLI) øT©õ
             + 37.3.2 DB2 øT©õ
             + 37.3.3 DBI øT©õ
             + 37.3.4 ÷ˆ©’ðš·xÏÏÏá (DWC) øT©õ
             + 37.3.5 SQL øT©õ
        o 37.4 õ¢¾¨ SQLSTATES

   * SQL Reference(æLÏÏÏ†¦¸)
        o 38.1 SQL Reference is Provided in One PDF File
        o 38.2 Chapter 3. Language Elements
             + 38.2.1 Naming Conventions and Implicit Object Name
               Qualifications
             + 38.2.2 DATALINK Assignments
             + 38.2.3 Expressions
                  + 38.2.3.1 Syntax Diagram
                  + 38.2.3.2 OLAP Functions
                  + 38.2.3.3 Sequence Reference
        o 38.3 Chapter 4. Functions
             + 38.3.1 Enabling the New Functions and Procedures
             + 38.3.2 Scalar Functions
                  + 38.3.2.1 ABS or ABSVAL
                  + 38.3.2.2 DECRYPT_BIN and DECRYPT_CHAR
                  + 38.3.2.3 ENCRYPT
                  + 38.3.2.4 GETHINT
                  + 38.3.2.5 IDENTITY_VAL_LOCAL
                  + 38.3.2.6 LCASE and UCASE (Unicode)
                  + 38.3.2.7 MQPUBLISH
                  + 38.3.2.8 MQREAD
                  + 38.3.2.9 MQRECEIVE
                  + 38.3.2.10 MQSEND
                  + 38.3.2.11 MQSUBSCRIBE
                  + 38.3.2.12 MQUNSUBSCRIBE
                  + 38.3.2.13 MULTIPLY_ALT
                  + 38.3.2.14 REC2XML
                  + 38.3.2.15 ROUND
                  + 38.3.2.16 WEEK_ISO
             + 38.3.3 Table Functions
                  + 38.3.3.1 MQREADALL
                  + 38.3.3.2 MQRECEIVEALL
             + 38.3.4 Procedures
                  + 38.3.4.1 GET_ROUTINE_SAR
                  + 38.3.4.2 PUT_ROUTINE_SAR
        o 38.4 Chapter 5. Queries
             + 38.4.1 select-statement/syntax diagram
             + 38.4.2 select-statement/fetch-first-clause
        o 38.5 Chapter 6. SQL Statements
             + 38.5.1 Update of the Partitioning Key Now Supported
                  + 38.5.1.1 Statement: ALTER TABLE
                  + 38.5.1.2 Statement: CREATE TABLE
                  + 38.5.1.3 Statement: DECLARE GLOBAL TEMPORARY TABLE
                    PARTITIONING KEY (column-name,...)
                  + 38.5.1.4 Statement: UPDATE
             + 38.5.2 Larger Index Keys for Unicode Databases
                  + 38.5.2.1 ALTER TABLE
                  + 38.5.2.2 CREATE INDEX
                  + 38.5.2.3 CREATE TABLE
             + 38.5.3 ALTER SEQUENCE
                  + ALTER SEQUENCE
             + 38.5.4 ALTER TABLE
             + 38.5.5 Compound SQL (Embedded)
             + 38.5.6 Compound Statement (Dynamic)
                  + Compound Statement (Dynamic)
             + 38.5.7 CREATE FUNCTION (Source or Template)
             + 38.5.8 CREATE FUNCTION (SQL Scalar, Table or Row)
             + 38.5.9 CREATE METHOD
                  + CREATE METHOD
             + 38.5.10 CREATE SEQUENCE
                  + CREATE SEQUENCE
             + 38.5.11 CREATE TRIGGER
                  + CREATE TRIGGER
             + 38.5.12 CREATE WRAPPER
             + 38.5.13 DECLARE CURSOR
             + 38.5.14 DELETE
             + 38.5.15 DROP
             + 38.5.16 GRANT (Sequence Privileges)
                  + GRANT (Sequence Privileges)
             + 38.5.17 INSERT
             + 38.5.18 SELECT INTO
             + 38.5.19 SET ENCRYPTION PASSWORD
                  + SET ENCRYPTION PASSWORD
             + 38.5.20 SET transition-variable
                  + SET Variable
             + 38.5.21 UPDATE
        o 38.6 Chapter 7. SQL Procedures now called Chapter 7. SQL Control
          Statements
             + 38.6.1 SQL Procedure Statement
                  + SQL Procedure Statement
             + 38.6.2 FOR
                  + FOR
             + 38.6.3 Compound Statement changes to Compound Statement
               (Procedure)
             + 38.6.4 RETURN
                  + RETURN
             + 38.6.5 SIGNAL
                  + SIGNAL
        o 38.7 Appendix A. SQL Limits
        o 38.8 Appendix D. Catalog Views
             + 38.8.1 SYSCAT.SEQUENCES

   * IBM DB2 ·xÝsæ{õ€®÷móû
        o 39.1 Java 1.2 Ï„ï¸·xÝsæ{õ€®÷móû
        o 39.2 DB2 ·xÝsæ{õ€¦§¯ú§íøœ¨—
        o 39.3 Ýb Windows­BOS/2 ¸× UNIX ¾ð¾xÏWô}æo SQL æ{õ€
        o 39.4 Ýb Solaris ¾ð¾xùØ¾× DB2 ·xÝsæ{õ€®÷móû
        o 39.5 Ïw¦óøíÇD¯PððùŒ
        o 39.6 Ýbµc‚ÏÏÏ†¯yù¾·“ûãÏUùØ¾× DB2 ·xÝsæ{õ€®÷móû
        o 39.7 UNIX (AIX­BSun Solaris­BLinux) Ýw÷Ó¯P·xÝsæ{õ€®÷móû
        o 39.8 ®÷m OS/390 ¦§ SQL ·xÝsæ{õ€
        o 39.9 øœ¨— SQL ·xÝsæ{õ€
        o 39.10 ôž¾X Java ·xÝsæ{õ€
        o 39.11 Ýb OS/390 ÏWï­ÏJ·xÝsæ{õ€
        o 39.12 ÝbÏuõ@î÷Ý›¦AóûÏÏü]¸w SQL ·xÝsæ{õ€¦§®÷m¨‹ôæ
        o 39.13 ÝêøÒï_ús OS/390 ÏW·xÝsæ{õ€®÷m¦§ WLM Ýõ}¦ô­
        o 39.14 Ýb OS/390 ô}æo Java ·xÝsæ{õ€
        o 39.15 ªø MQ Series ¯P OLE DB ®÷m DB2 ¦¡©‘ùØ¾×¦Þ¸w÷q¾\î… (UDF)

   * Unicode õ¢ús
        o 40.1 ¶ýÏô
             + 40.1.1 DB2 Unicode ÷ˆ©’©wÏ×·ü¾×æ{Ý­
             + 40.1.2 Ï†¾¢õ¢ús
        o 40.2 SQL Reference(æLÏÏÏ†¦¸)
             + 40.2.1 Chapter 3 Language Elements
                  + 40.2.1.1 Promotion of Data Types
                  + 40.2.1.2 Casting Between Data Types
                  + 40.2.1.3 Assignments and Comparisons
                  + 40.2.1.4 Rules for Result Data Types
                  + 40.2.1.5 Rules for String Conversions
                  + 40.2.1.6 Expressions
                  + 40.2.1.7 Predicates
             + 40.2.2 Chapter 4 Functions
                  + 40.2.2.1 Scalar Functions
        o 40.3 CLI Guide and Reference(æLÏÏÏ†¦¸)
             + 40.3.1 Chapter 3. Using Advanced Features
                  + 40.3.1.1 Writing a DB2 CLI Unicode Application
             + 40.3.2 Appendix C. DB2 CLI and ODBC
                  + 40.3.2.1 ODBC Unicode Applications
        o 40.4 Data Movement Utilities Guide and Reference(æLÏÏÏ†¦¸)
             + 40.4.1 Appendix C. Export/Import/Load Utility File Formats

  ------------------------------------------------------------------------

Administrative API Reference (æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

33.1 db2ArchiveLog (new API)

db2ArchiveLog

Closes and truncates the active log file for a recoverable database. If
user exit is enabled, issues an archive request.

Authorization

One of the following:

   * sysadm
   * sysctrl
   * sysmaint
   * dbadm

Required Connection

This API automatically establishes a connection to the specified database.
If a connection to the specified database already exists, the API will
return an error.

Version

db2ApiDf.h

C API Syntax

 /* File: db2ApiDf.h */
 /* API:  Archive Active Log */
 SQL_API_RC SQL_API_FN
    db2ArchiveLog (
       db2Uint32 version,
       void *pDB2ArchiveLogStruct,
       struct sqlca * pSqlca);

 typedef struct
 {
    char                *piDatabaseAlias;
    char                *piUserName;
    char                *piPassword;
    db2Uint16           iAllNodeFlag;
    db2Uint16           iNumNodes;
    SQL_PDB_NODE_TYPE   *piNodeList;
    db2Uint32           iOptions;
 }

Generic API Syntax

 /* File: db2ApiDf.h */
 /* API:  Archive Active Log */
 SQL_API_RC SQL_API_FN
    db2gArchiveLog (
       db2Uint32 version,
       void *pDB2ArchiveLogStruct,
       struct sqlca * pSqlca);

 typedef struct
 {
    db2Uint32           iAliasLen;
    db2Uint32           iUserNameLen;
    db2Uint32           iPasswordLen;
    char                *piDatabaseAlias;
    char                *piUserName;
    char                *piPassword;
    db2Uint16           iAllNodeFlag;
    db2Uint16           iNumNodes;
    SQL_PDB_NODE_TYPE   *piNodeList;
    db2Uint32           iOptions;
 }

API Parameters

version
     Input. Specifies the version and release level of the variable passed
     in as the second parameter, pDB2ArchiveLogStruct.

pDB2ArchiveLogStruct
     Input. A pointer to the db2ArchiveLogStruct structure.

pSqlca
     Output. A pointer to the sqlca structure.

iAliasLen
     Input. A 4-byte unsigned integer representing the length in bytes of
     the database alias.

iUserNameLen
     A 4-byte unsigned integer representing the length in bytes of the user
     name. Set to zero if no user name is used.

iPasswordLen
     Input. A 4-byte unsigned integer representing the length in bytes of
     the password. Set to zero if no password is used.

piDatabaseAlias
     Input. A string containing the database alias (as cataloged in the
     system database directory) of the database for which the active log is
     to be archived.

piUserName
     Input. A string containing the user name to be used when attempting a
     connection.

piPassword
     Input. A string containing the password to be user when attempting a
     connection.

iAllNodeFlag
     MPP only. Input. Flag indicating whether the operation should apply to
     all nodes listed in the db2nodes.cfg file. Valid values are:

     DB2ARCHIVELOG_NODE_LIST
          Apply to nodes in a node list that is passed in piNodeList.

     DB2ARCHIVELOG_ALL_NODES
          Apply to all nodes. piNodeList should be NULL. This is the
          default value.

     DB2ARCHIVELOG_ALL_EXCEPT
          Apply to all nodes except those in the node list passed in
          piNodeList.

iNumNodes
     MPP only. Input. Specifies the number of nodes in the piNodeList
     array.

piNodeList
     MPP only. Input. A pointer to an array of node numbers against which
     to apply the archive log operation.

iOptions
     Input. Reserved for future use.

  ------------------------------------------------------------------------

33.2 db2ConvMonStream

In the Usage Notes, the structure for the snapshot variable datastream type
SQLM_ELM_SUBSECTION should be sqlm_subsection.
  ------------------------------------------------------------------------

33.3 db2DatabasePing (new API)

db2DatabasePing - Ping Database

Tests the network response time of the underlying connectivity between a
client and a database server. This API can be used by an application when a
host database server is accessed via DB2 Connect either directly or through
a gateway.

Authorization

None

Required Connection

Database

Version

db2ApiDf.h

C API Syntax

      /* File: db2ApiDf.h */
   /* API: Ping Database */
   /* ... */


   SQL_API_RC SQL_API_FN
     db2DatabasePing (
         db2Uint32     versionNumber,
         void         *pParmStruct,
         struct sqlca *pSqlca);
   /* ... */

   typedef SQL_STRUCTURE db2DatabasePingStruct
   {
     char          iDbAlias[SQL_ALIAS_SZ + 1];
     db2Uint16     iNumIterations;
     db2Uint32    *poElapsedTime;
   }

Generic API Syntax

   /* File: db2ApiDf.h */
   /* API: Ping Database */
   /* ... */
   SQL_API_RC SQL_API_FN
     db2gDatabasePing (
         db2Uint32     versionNumber,
         void         *pParmStruct,
         struct sqlca *pSqlca);
   /* ... */

   typedef SQL_STRUCTURE db2gDatabasePingStruct
   {
     db2Uint16     iDbAliasLength;
     char          iDbAlias[SQL_ALIAS_SZ];
     db2Uint16     iNumIterations;
     db2Uint32    *poElapsedTime;
   }

API Parameters

versionNumber
     Input. Version and release of the DB2 Universal Database or DB2
     Connect product that the application is using.

     Note:
          Constant db2Version710 or higher should be used for DB2 Version
          7.1 or higher.

iDbAliasLength
     Input. Length of the database alias name.

     Note:
          This parameter is not currently used. It is reserved for future
          use.

iDbAlias
     Input. Database alias name.

     Note:
          This parameter is not currently used. It is reserved for future
          use.

iNumIterations
     Input. Number of test request iterations. The value must be between 1
     and 32767 inclusive.

poElapsedTime
     Output. A pointer to an array of 32-bit integers where the number of
     elements is equal to iNumIterations. Each element in the array will
     contain the elapsed time in microseconds for one test request
     iteration.

     Note:
          The application is responsible for allocating the memory for this
          array prior to calling this API.

pSqlca
     Output. A pointer to the sqlca structure. For more information about
     this structure, see the Administrative API Reference.

Usage Notes

A database connection must exist before invoking this API, otherwise an
error will result.

This function can also be invoked using the PING command. For a description
of this command, see the Command Reference.
  ------------------------------------------------------------------------

33.4 db2HistData

The following entries should be added to Table 11. Fields in the
db2HistData Structure:
 Field Name               Data Type               Description
 oOperation               char                    See Table 12.
 oOptype                  char                    See Table 13.

The following table will be added following Table 11.

Table 12. Valid event values for oOperation in the db2HistData Structure
 Value Description C Definition                 COBOL/FORTRAN Definition
  A    add         DB2HISTORY_OP_ADD_TABLESPACE DB2HIST_OP_ADD_TABLESPACE
       tablespace
  B    backup      DB2HISTORY_OP_BACKUP         DB2HIST_OP_BACKUP
  C    load-copy   DB2HISTORY_OP_LOAD_COPY      DB2HIST_OP_LOAD_COPY
  D    dropped     DB2HISTORY_OP_DROPPED_TABLE  DB2HIST_OP_DROPPED_TABLE
       table
  F    roll        DB2HISTORY_OP_ROLLFWD        DB2HIST_OP_ROLLFWD
       forward
  G    reorganize  DB2HISTORY_OP_REORG          DB2HIST_OP_REORG
       table
  L    load        DB2HISTORY_OP_LOAD           DB2HIST_OP_LOAD
  N    rename      DB2HISTORY_OP_REN_TABLESPACE DB2HIST_OP_REN_TABLESPACE
       tablespace
  O    drop        DB2HISTORY_OP_DROP_TABLESPACEDB2HIST_OP_DROP_TABLESPACE
       tablespace
  Q    quiesce     DB2HISTORY_OP_QUIESCE        DB2HIST_OP_QUIESCE
  R    restore     DB2HISTORY_OP_RESTORE        DB2HIST_OP_RESTORE
  S    run         DB2HISTORY_OP_RUNSTATS       DB2HIST_OP_RUNSTATS
       statistics
  T    alter       DB2HISTORY_OP_ALT_TABLESPACE DB2HIST_OP_ALT_TBS
       tablespace
  U    unload      DB2HISTORY_OP_UNLOAD         DB2HIST_OP_UNLOAD

The following table will also be added.

Table 13. Valid oOptype values db2HistData Structure
 oOperationoOptype   Description           C/COBOL/FORTRAN Definition
 B             F     Offline               DB2HISTORY_OPTYPE_OFFLINE
               N     Online                DB2HISTORY_OPTYPE_ONLINE
               I     Incremental offline   DB2HISTORY_OPTYPE_INCR_OFFLINE
               O     Incremental online    DB2HISTORY_OPTYPE_INCR_ONLINE
               D     Delta offline         DB2HISTORY_OPTYPE_DELTA_OFFLINE
               E     Delta online          DB2HISTORY_OPTYPE_DELTA_ONLIN
 F             E     End of log            DB2HISTORY_OPTYPE_EOL
               P     Point in time         DB2HISTORY_OPTYPE_PIT
 L             I     Insert                DB2HISTORY_OPTYPE_INSERT
               R     Replace               DB2HISTORY_OPTYPE_REPLACE
 Q             S     Quiesce share         DB2HISTORY_OPTYPE_SHARE
               U     Quiesce update        DB2HISTORY_OPTYPE_UPDATE
               X     Quiesce exclusive     DB2HISTORY_OPTYPE_EXCL
               Z     Quiesce reset         DB2HISTORY_OPTYPE_RESET
 R             F     Offline               DB2HISTORY_OPTYPE_OFFLINE
               N     Online                DB2HISTORY_OPTYPE_ONLINE
               I     Incremental offline   DB2HISTORY_OPTYPE_INCR_OFFLINE
               O     Incremental online    DB2HISTORY_OPTYPE_INCR_ONLINE
 T             C     Add containers        DB2HISTORY_OPTYPE_ADD_CONT
               R     Rebalance             DB2HISTORY_OPTYPE_REB
  ------------------------------------------------------------------------

33.5 db2HistoryOpenScan

The following value will be added to the iCallerAction parameter.

DB2HISTORY_LIST_CRT_TABLESPACE
     Select only the CREATE TABLESPACE and DROP TABLESPACE records that
     pass the other filters.

  ------------------------------------------------------------------------

33.6 db2XaGetInfo (new API)

db2XaGetInfo - Get Information for Resource Manager

Extracts information for a particular resource manager once an xa_open call
has been made.

Authorization

None

Required Connection

Database

Version

sqlxa.h

C API Syntax

    /* File: sqlxa.h */
    /* API: Get Information for Resource Manager */
    /* ... */
    SQL_API_RC SQL_API_FN
    db2XaGetInfo (
       db2Uint32 versionNumber,
       void * pParmStruct,
       struct sqlca * pSqlca);

    typedef SQL_STRUCTURE db2XaGetInfoStruct
    {
      db2int32 iRmid;
      struct sqlca oLastSqlca;
    } db2XaGetInfoStruct;

API Parameters

versionNumber
     Input. Specifies the version and release level of the structure passed
     in as the second parameter, pParmStruct.

pParmStruct
     Input. A pointer to the db2XaGetInfoStruct structure.

pSqlca
     Output. A pointer to the sqlca structure. For more information about
     this structure, see the Administrative API Reference.

iRmid
     Input. Specifies the resource manager for which information is
     required.

oLastSqlca
     Output. Contains the sqlca for the last XA API call.

     Notes:
          Only the sqlca that resulted from the last failing XA API can be
          retrieved.

  ------------------------------------------------------------------------

33.7 db2XaListIndTrans (new API that supercedes sqlxphqr)

db2XaListIndTrans - List Indoubt Transactions

Provides a list of all indoubt transactions for the currently connected
database.

Scope

This API affects only the node on which it is issued.

Authorization

One of the following:

   * sysadm
   * dbadm

Required Connection

Database

Notes

db2ApiDf.h

C API Syntax

    /* File: db2ApiDf.h */
    /* API: List Indoubt Transactions */
    /* ... */
    SQL_API_RC SQL_API_FN
    db2XaListIndTrans (
       db2Uint32 versionNumber,
       void * pParmStruct,
       struct sqlca * pSqlca);

    typedef SQL_STRUCTURE db2XaListIndTransStruct
    {
      db2XaRecoverStruct * piIndoubtData;
      db2Uint32            iIndoubtDataLen;
      db2Uint32            oNumIndoubtsReturned;
      db2Uint32            oNumIndoubtsTotal;
      db2Uint32            oReqBufferLen;
    } db2XaListIndTransStruct;

    typedef SQL_STRUCTURE db2XaRecoverStruct
    {
      sqluint32      timestamp;
      SQLXA_XID      xid;
      char           dbalias[SQLXA_DBNAME_SZ];
      char           applid[SQLXA_APPLID_SZ];
      char           sequence_no[SQLXA_SEQ_SZ];
      char           auth_id[SQL_USERID_SZ];
      char           log_full;
      char           connected;
      char           indoubt_status;
      char           originator;
      char           reserved[8];
    } db2XaRecoverStruct;

API Parameters

versionNumber
     Input. Specifies the version and release level of the structure passed
     in as the second parameter, pParmStruct.

pParmStruct
     Input. A pointer to the db2XaListIndTransStruct structure.

pSqlca
     Output. A pointer to the sqlca structure. For more information about
     this structure, see the Administrative API Reference.

piIndoubtData
     Input. A pointer to the application supplied buffer where indoubt data
     will be returned. The indoubt data is in db2XaRecoverStruct format.
     The application can traverse the list of indoubt transactions by using
     the size of the db2XaRecoverStruct structure, starting at the address
     provided by this parameter.

     If the value is NULL, DB2 will calculate the size of the buffer
     required and return this value in oReqBufferLen. oNumIndoubtsTotal
     will contain the total number of indoubt transactions. The application
     may allocate the required buffer size and issue the API again.

oNumIndoubtsReturned
     Output. The number of indoubt transaction records returned in the
     buffer specified by pIndoubtData.

oNumIndoubtsTotal
     Output. The Total number of indoubt transaction records available at
     the time of API invocation. If the piIndoubtData buffer is too small
     to contain all the records, oNumIndoubtsTotal will be greater than the
     total for oNumIndoubtsReturned. The application may reissue the API in
     order to obtain all records.

     Notes:
          This number may change between API invocations as a result of
          automatic or heuristic indoubt transaction resynchronisation, or
          as a result of other transactions entering the indoubt state.

oReqBufferLen
     Output. Required buffer length to hold all indoubt transaction records
     at the time of API invocation. The application can use this value to
     determine the required buffer size by calling the API with
     pIndoubtData set to NULL. This value can then be used to allocate the
     required buffer, and the API can be issued with pIndoubtData set to
     the address of the allocated buffer.

     Notes:
          The required buffer size may change between API invocations as a
          result of automatic or heuristic indoubt transaction
          resynchronisation, or as a result of other transactions entering
          the indoubt state. The application may allocate a larger buffer
          to account for this.

timestamp
     Output. Specifies the time when the transaction entered the indoubt
     state.

xid
     Output. Specifies the XA identifier assigned by the transaction
     manager to uniquely identify a global transaction.

dbalias
     Output. Specifies the alias of the database where the indoubt
     transaction is found.

applid
     Output. Specifies the application identifier assigned by the database
     manager for this transaction.

sequence_no
     Output. Specifies the sequence number assigned by the database manager
     as an extension to the applid.

auth_id
     Output. Specifies the authorization ID of the user who ran the
     transaction.

log_full
     Output. Indicates whether or not this transaction caused a log full
     condition. Valid values are:

     SQLXA_TRUE
          This indoubt transaction caused a log full condition.

     SQLXA_FALSE
          This indoubt transaction did not cause a log full condition.

connected
     Output. Indicates whether or not the application is connected. Valid
     values are:

     SQLXA_TRUE
          The transaction is undergoing normal syncpoint processing, and is
          waiting for the second phase of the two-phase commit.

     SQLXA_FALSE
          The transaction was left indoubt by an earlier failure, and is
          now waiting for resynchronisation from the transaction manager.

indoubt_status
     Output. Indicates the status of this indoubt transaction. Valid values
     are:

     SQLXA_TS_PREP
          The transaction is prepared. The connected parameter can be used
          to determine whether the transaction is waiting for the second
          phase of normal commit processing or whether an error occurred
          and resynchronisation with the transaction manager is required.

     SQLXA_TS_HCOM
          The transaction has been heuristically committed.

     SQLXA_TS_HROL
          The transaction has been heuristically rolled back.

     SQLXA_TS_MACK
          The transaction is missing commit acknowledgement from a node in
          a partitioned database.

     SQLXA_TS_END
          The transaction has ended at this database. This transaction may
          be re-activated, committed, or rolled back at a later time. It is
          also possible that the transaction manager encountered an error
          and the transaction will not be completed. If this is the case,
          this transaction requires heuristic actions, because it may be
          holding locks and preventing other applications from accessing
          data.

Usage Notes

A typical application will perform the following steps after setting the
current connection to the database or to the partitioned database
coordinator node:

  1. Call db2XaListIndTrans with piIndoubtData set to NULL. This will
     return values in oReqBufferLen and oNumIndoubtsTotal.
  2. Use the returned value in oReqBufferLen to allocate a buffer. This
     buffer may not be large enough if there are additional indoubt
     transactions because the initial invocation of this API to obtain
     oReqBufferLen. The application may provide a buffer larger than
     oReqBufferLen.
  3. Determine if all indoubt transaction records have been obtained. This
     can be done by comparing oNumIndoubtsReturned to oNumIndoubtTotal. If
     oNumIndoubtsTotal is greater than oNumIndoubtsReturned, the
     application can repeat the above steps.

See Also

"sqlxhfrg - Forget Transaction Status", "sqlxphcm - Commit an Indoubt
Transaction", and "sqlxphrl - Roll Back an Indoubt Transaction" in the
Administrative API Reference.
  ------------------------------------------------------------------------

33.8 db2GetSnapshot - Get Snapshot

The syntax for the db2GetSnapshot API should be as follows:

   int db2GetSnapshot(  unsigned char version;
   db2GetSnapshotData *data,
   struct sqlca *sqlca);

   The parameters described in data are:
   typedef struct db2GetSnapshotData{
      sqlma             *piSqlmaData;
      sqlm_collected    *poCollectedData
      void                      *poBuffer;
      db2uint32         iVersion;
      db2int32          iBufferSize;
      db2uint8          iStoreResult;
   db2uint16            iNodeNumber;
   db2uint32            *poOutputFormat;

   }db2GetSnapshotData;

  ------------------------------------------------------------------------

33.9 Forget Log Record

The following information will be added to Appendix F following the MPP
Subordinator Prepare section.

This log record is written after a rollback of indoubt transactions or
after a commit of two-phase commit. The log record is written to mark the
end of the transaction and releases any log resources held. In order for
the transaction to be forgotten, it must be in a heuristically completed
state.

Table 21. Forget Log Record Structure
 Description              Type                          Offset (Bytes)
 Log header               LogManagerLogRecordHeader         0(20)
 time                     sqluint64                         20(8)
 Total Length: 28 bytes
  ------------------------------------------------------------------------

33.10 sqlaintp - Get Error Message

The following usage note is to be added to the description of this API:

   In a multi-threaded application, sqlaintp must be attached to a valid context;
   otherwise, the message text for SQLCODE -1445 cannot be obtained.

  ------------------------------------------------------------------------

33.11 sqlbctcq - Close Tablespace Container Query

Load is not a valid Authorization level for this API.
  ------------------------------------------------------------------------

33.12 sqlubkp - Backup Database

For the BackupType parameter the SQLUB_FULL value will be replaced by the
SQLUB_DB. A backup of all tablespaces in the database will be taken.

To support the new incremental backup functionality the SQLUB_INCREMENTAL
and SQLUB_DELTA parameters will also be added. An incremental backup image
is a copy of all database data which has changed since the most recent
successful, full backup. A delta backup image is a copy of all database
data that has changed since the most recent successful backup of any type
  ------------------------------------------------------------------------

33.13 sqlureot - Reorganize Table

The following sentence will be added to the Usage Notes:

REORGANIZE TABLE cannot use an index that is based on an index extension.
  ------------------------------------------------------------------------

33.14 sqlurestore - Restore Database

For the RestoreType parameter the SQLUD_FULL value will be replaced by the
SQLUD_DB. A restore of all table spaces in the database will be taken. This
will be run offline.

To support the new incremental restore functionality the SQLUD_INCREMENTAL
parameter will also be added.

An incremental backup image is a copy of all database data which has
changed since the most recent successful full backup.
  ------------------------------------------------------------------------

33.15 Documentation Error Regarding AIX Extended Shared Memory Support
(EXTSHM)

In "Appendix E. Threaded Applications with Concurrent Access", Note 2
should now read:

2. By default, AIX does not permit 32-bit applications to attach to more
than 11 shared memory segments per process, of which a maximum of 10 can be
used for local DB2 connections.

To use EXTSHM with DB2, do the following:

In client sessions:

export EXTSHM=ON

When starting DB2:

export EXTSHM=ON
db2set DB2ENVLIST=EXTSHM
db2start

On EEE, also add the following lines to sqllib/db2profile:

EXTSHM=ON
export EXTSHM

  ------------------------------------------------------------------------

33.16 SQLFUPD

33.16.1 locklist

The name of the token has changed from SQLF_DBTN_LOCKLIST to
SQLF_DBTN_LOCK_LIST. The locklist parameter has been changed from a
SMALLINT to a 64-bit unsigned INTEGER. The following addition should be
made to the table of Updatable Database Configuration Parameters.
 Parameter Name     Token              Token Value       Data Type
 locklist           SQLF_DBTN_LOCK_LIST704               Uint64

The new maximum for this parameter is 524 288.
  ------------------------------------------------------------------------

33.17 SQLEDBDESC

Two values will be added to the list of valid values for SQLDBCSS (defined
in sqlenv). They are:

SQL_CS_SYSTEM_NLSCHAR
     Collating sequence from system using the NLS version of compare
     routines for character types.

SQL_CS_USER_NLSCHAR
     Collating sequence from user using the NLS version of compare routines
     for character types.

  ------------------------------------------------------------------------

33.18 SQLFUPD Documentation Error

In "Chapter 3. Data Structures", Table 53. Updatable Database Configuration
Parameters incorrectly lists the token value for dbheap as 701. The correct
value is 58.
  ------------------------------------------------------------------------

·ü¾×æ{Ý­ô}æoÏƒ¾U

  ------------------------------------------------------------------------

34.1 ýŽ 1 üû ¶ýÏô

34.1.1 Ï„ï¸ün‚

æ—:
     PHP­CPHP ¾iùØ¾×ªøñq Web ®ª·ü¾×æ{Ý­Ýsù£ DB2 ¦§ÏŠ¦k­C PHP ªOÏ@§Ý›¦Aóû§í
     ­BÏ§ïO HTML ¦§¾‘ÏªÝ­¾ð¾x Script ¯yù¾­C ¾ÝÏ„ï¸ùØ¾× Unified-ODBC Ýsù£ÏŠ
     ¦k¦§ DB2 Ýsù£­Aù„ÏÏùØ¾×¦Þ¬hÝ÷ PHP ùØ¾× ODBC ¸I¾s¯P DB2 üq®H­C¯P¬Ñú€
     ODBC ÏœÝP¦§ªO­AUnified-ODBC ÏŠ¦k¦«ñæ¯P DB2 CLI ¬hüq®H­AÝàÏœüzûL ODBC
     ¬h­C ÝüÇ” PHP úføtùØ¾× DB2 ¦§÷âýà÷ˆøT­A«Ñø¥ÝãÏUÝC¦§ DB2 Ï„ï¸§“î÷­G
     www.ibm.com/software/data/db2/udb/winos2unix/support­C

AIX

ÝC¾š¦§ C Ï× C++ «sŽôóû¦§¦¸¾¯·üªøÏUÝC­G

   IBM C Ï× C++ «sŽôóû­AóA¾× AIX ¦¸¾¯ 3.6.6­]óA¾×¸¢ 64 ÝÏ÷¦§¦¸¾¯ 3.6.6.3­^
   IBM C for AIX 4.4
   IBM VisualAge C++ ¦¸¾¯ 4.0

æ—:
     «ÑñqÏUÝC§“õ}ÏU÷üoù€«sŽôóû¦¸¾¯¦§üÞús FixPak

        http://www.ibm.com/software/ad/vacpp/service/csd.html

Micro Focus COBOL «sŽôóû¸ãÝC¾š¦§¦¸¾¯·üªø­G

   AIX 4.2.1

   Micro Focus COBOL ¦¸¾¯ 4.0.20 (PRN 12.03 ¸×õ¢ús¦§¦¸¾¯)
   Micro Focus COBOL ¦¸¾¯ 4.1.10 (PRN 13.04 ¸×õ¢ús¦§¦¸¾¯)

   AIX 4.3

   Micro Focus COBOL Server Express ¦¸¾¯ 1.0

æ—:
     ÝüÇ” Micro Focus COBOL ·xÝsæ{õ€Ï× AIX 4.3 ÏW¦§ UDF ¦§ DB2Ï„ï¸÷ˆøT­A «Ñ
     üyüX DB2 Application Development §“ðô­G

        http://www.ibm.com/software/data/db2/udb/ad

ðYðnùØ¾× IBM XL Fortran for AIX ¦¸¾¯ 5.1.0 «sŽôóûùàô}æo 64 ÝÏ÷·ü¾×æ{Ý­­A
«ÑÝb«sŽôÏ×ÇæýùB’JÏÏùØ¾× "-q64" ¨‹ôæ­C «Ñ¦`úNÝû«sŽôóûÝb¾ì®e¦¸¾¯©ùÇÏœÏ„ï¸
64 ÝÏ÷·ü¾×æ{Ý­­C

HP-UX

C++ «sŽôóû¸ãÝC¾š¦§¦¸¾¯ªø­G

   HP aC++­A¦¸¾¯ A.03.25

æ—:
     HP ÏœÏ„ï¸¾Hús­B¶¶«sŽôóûùà«sŽô¦§¦®¾¢Ïõô­¦§ÏGôiÝªê©e¸Ò­AÝ]ÝûüoñNð½ùØ®
     ¾á C++ ·ü¾×æ{Ý­¦§ð®ús«sŽô­A¾HÝsù£ HP-UX ÏW¦§ DB2­C Ï]¾ýôú®¾á C++ ·ü¾×
     æ{Ý­¾HüBýzüoðàús«sŽôóû¦§ýõñ`¦ª¦p­C

     üoªO aCC ¶…ýó®®n¦§ URL­Ghttp://www.hp.com/esy/lang/cpp/tguide­C C++
     ¦§Ïœªê©eü­¾ö¾iÝbÏUÝC§“î÷ÏÏõ„ù­G

        http://www.hp.com/esy/lang/cpp/tguide/transcontent.html#RN.CVT.1.2
        http://www.hp.com/esy/lang/cpp/tguide/transcontent.html#RN.CVT.3.3

     C ¯P C++ ü­¾ö¾iÝbÏUÝC§“î÷ÏÏõ„ù­G

        http://www.hp.com/esy/lang/cpp/tguide/transcontent.html#RN.CVT.3.3.1

     µ”æM C ¸M aCC ªê©e­Aú¡ùØ¾×ùƒ§ÏœÝP¦§¦®¾¢Çç®ª©­A õtÝü "main" ¦§¦®¾¢¾ý
     ôú¾H aCC «sŽô­AÝàüÞýž¾iøäÝ‘·¾ýôú¾H aCC ùàÇæý­C

Linux

DB2 for Linux Ï„ï¸ÏUÝC REXX ¦¸¾¯­G

   Object REXX Interpreter for Linux ¦¸¾¯ 2.1

Linux/390

DB2 for Linux/390 ¾uÏ„ï¸ Java­BC Ï× C++­C

OS/2

C/C++ «sŽôóû¸ãÝC¾š¦§¦¸¾¯ªø­G

   IBM VisualAge C++ for OS/2 ¦¸¾¯ 3.6.5 Ï×¦¸¾¯ 4.0

æ—:
     «ÑñqÏUÝC§“õ}ÏU÷üoù€«sŽôóû¦¸¾¯¦§üÞús FixPak

        http://www.ibm.com/software/ad/vacpp/service/csd.html

ÝüÇ”üoù€ VisualAge C++ «sŽôóû¦§¾¬ùà¦AøÔÏ„ï¸ððùŒ­A«Ñø¥ó\ÏUÝC§“õ}¦§ús¯DøØªq­G

   http://www-4.ibm.com/software/ad/vacpp/

Solaris

Micro Focus COBOL «sŽôóû¸ãÝC¾š¦§¦¸¾¯·üªø­G

   Micro Focus COBOL Server Express ¦¸¾¯ 1.0

Windows 32 ÝÏ÷õ@ú~ùtý×

IBM VisualAge C++ «sŽôóû¸ãÝC¾š¦§¦¸¾¯ªø­G

    IBM VisualAge C++ óA¾×¸¢ Windows ¦¸¾¯ 3.6.5 ¸M 4.0

æ—:
     «ÑñqÏUÝC§“õ}ÏU÷üoù€«sŽôóû¦¸¾¯¦§üÞús FixPak

        http://www.ibm.com/software/ad/vacpp/service/csd.html

ÝüÇ”üoù€ VisualAge C++ «sŽôóû¦§¾¬ùà¦AøÔÏ„ï¸ððùŒ­A«Ñø¥ó\ÏUÝC§“õ}¦§ús¯DøØªq­G

   http://www-4.ibm.com/software/ad/vacpp/

Micro Focus COBOL «sŽôóû¸ãÝC¾š¦§¦¸¾¯·üªø­G

   Micro Focus COBOL ¦¸¾¯ 4.0.20
   Micro Focus COBOL Net Express ¦¸¾¯ 3.0

34.1.2 «dùãæ{Ý­

ÏUÝCÏ§©e·ü÷àús¬Wù­u¦®¾¢üsæý¸MÏ§ïO«dùã­vÏ@÷`ÏÏ­G

salarycltvc
     Visual C++ DB2 CLI «dùã§ë Visual Basic ·xÝsæ{õ€ªø salarysrv­C

SALSVADO
     «dùã OLE ÝêøÒÏ’·xÝsæ{õ€ (SALSVADO) ¸M SALCLADO ñqŽíî÷­A Ýb 32 ÝÏ÷¦§
     Visual Basic ¸M ADO ÏUøäÝ‘­Aðp§ƒ¦¡©‘ staff2 ¦§¾ðõ­µ~÷ˆ­C

ÏUÝCÏ§©e·ü÷àús¬Wù­uÏ‚¯x§èýzùØ¾×¦Þ÷ä¾Xæ{Ý­«dùã­vÏ@÷`ÏÏ­G

¸¢ AIX ùØ¾× 3.1.6 ¸×õ¢ø¦¬hÝ÷¦§ ADSM API ñqŽíî÷Ïõ·ü¾×æ{Ý­¾ýôú¾¥ xlc_r ¸×
xlC_r «sŽôóû¸I¾sùà®¾á­A Ýà®D¾¥ xlc ¸× xlC ùà®¾á­AõYùØ÷à·ü¾×æ{Ý­ªøü‘Ï@øäÝ‘
§­C Ýû«T®O·©ž©wªøøäÝ‘§¦§Ýw¾ç­C üoóA¾×¸¢­uÏ‚¯x§èýzùØ¾×¦Þ÷ä¾Xæ{Ý­«dùã­v­A
db2uext2.cadsm­C

Ýp¦Gñz¦§·ü¾×æ{Ý­ªO¾¥®DøäÝ‘§Ýw¾ç·©ž©wùà«sŽô­Añz¾i¾HÏè¾×¸T¸w·Ó‡ IC21925E
¸×üsñæ·ü¾×æ{Ý­ïœù¥¦Þ­C ¸T¸w·Ó‡¾i¾×¸¢ index.storsys.ibm.com ø×ÝWFTP Ý›¦A
óû­C üoú|ùØño ADSM API ¬hÝ÷Ý^ù 3.1.3­C
  ------------------------------------------------------------------------

34.2 ýŽ 3 üû ô}æo DB2 ·ü¾×æ{Ý­¦§Ï@î‰÷ˆøT

34.2.1 ô}æo·©ž­Bmake ·¸M¨—¯~·Óªd¦§Ï«¾×æ{Ý­

¦¡©‘ 16 Ï§ bldevm ¦§æn¨ì·ü÷àüQ¦ù£ªø­G

bldevm
     ù’¾¢§Òúçæ{Ý­«dùãæ{Ý­­Aevm (¾uóA¾×¸¢ AIX­BOS/2 ¸M Windows 32 ÝÏ÷õ@ú~ùt
     ý×)­C

¦¡©‘ 17 ·ü÷à¾]ªAÏUÝCæn¨ì­G

bldmevm
     ù’¾¢§Òúçæ{Ý­«dùãæ{Ý­­Aevm­AÏ× Microsoft Visual C++ «sŽôóû­C

bldvevm
     ù’¾¢§Òúçæ{Ý­«dùãæ{Ý­­Aevm­A¾[ÏW VisualAge Visual C++ «sŽôóû­C

  ------------------------------------------------------------------------

34.3 ýŽ 4 üû ô}æo Java Applets ¸M·ü¾×æ{Ý­

34.3.1 ü]¸w·“ûã

ðYñzÝbÏ„ï¸¦§¾ð¾xÏWùØ¾× IBM JDK 1.1.8 ùà®÷m SQLJ æ{Ý­­A ®h¯íðn 1999 Ý~ 11
Ï‰ 24 Ï‚­]¸×Ïõ® ­^¦§ JDK ô}æoÏ‚ïµ­Cõ_®hñzú|Ýb«sŽôïµô­Ýªù JNI ¨—¯~øT©õ­C

ðYñzÝbÏ„ï¸¦§¾ð¾xÏWùØ¾× IBM JDK 1.2.2 ùà®÷m SQLJ æ{Ý­­A®h¯íðn 2000 Ý~ 4 Ï‰
17 Ï‚­]¸×Ïõ® ­^¦§ JDK ®÷mÏ‚ïµ­Cõ_®h­Añzú|Ýb«sŽôïµô­ÝªùæL©Ž¦§ Java Çç®ª­C

øwû‹Ý÷üû÷` AIX­BHP-UX­BLinux Ï× Solaris­A ù£¾N JDBC 2.0 ¦§÷ˆøTÝpÏU­G

ùØ¾× Java ·ü¾×æ{Ý­¦§ JDBC 2.0 XøÒæ{Ý­

JDBC 1.22 XøÒæ{Ý­ªO¸ãÝüõ@ú~ùtý×ûwü]¦§XøÒæ{Ý­­C ñìùØ¾× JDBC 2.0 ¦§úsîS¸Ò­A
ñz¾ýôúÝw÷Ó JDK 1.2 Ï„ï¸­C õQ¾× JDBC 2.0 ¦§úsîS¸ÒùàøäÝ‘·ü¾×æ{Ý­Ïõ®e­Añz¾ýôú
Ýê sqllib/java12 ¾¨ìæo¾X usejdbc2 ®¾Oùàü]¸w·“ûã­C õ’ñ‘·ü¾×æ{Ý­¾i¾HÏ@¦«ùØ
¾× JDBC 2.0 XøÒæ{Ý­­AñzñoÝã¬{ús¬WÏUÝCÏ§©eùænÏJü]¸w·­AÝp .profile­A¸×Ýš
Shell ø_¸lü]¸w script­AÝp .bashrc­B.cshrc ¸× .kshrc­G

   . sqllib/java12/usejdbc2

«T¸wÝû®¾O¸¤÷mÝbøäÝ‘ db2profile ¦§®¾OÏõ® ­AÝ]ªø usejdbc2 ·ü÷àÝb db2profile
Ïõ® øäÝ‘­C

ñì¸ûÝ^Ïµï®Ýš JDBC 1.22 XøÒæ{Ý­­A«ÑÝb sqllib/java12 ¾¨ìÏUøäÝ‘ÏUÝC®¾O­G

   . usejdbc1

ùØ¾× Java ·xÝsæ{õ€¸M UDF ¦§ JDBC 2.0 XøÒæ{Ý­

ñìùØ¾× Java ·xÝsæ{õ€¸M UDF ¦§ JDBC 2.0 XøÒæ{Ý­­Añz¾ýôúü]¸w©žùãûj¶öùØ¾×¦Þ¦§
·“ûã­C ûwü]¦§ûj¶öùØ¾×¦Þ ID ªO db2fenc1­C ñìü]¸wûj¶öùØ¾×¦Þ ID ¦§·“ûã­A«ÑøäÝ‘
ÏUÝCùB’J­G

  1. ús¬WÏUÝCÏ§©eÝšûj¶öùØ¾×¦Þ ID ü]¸w·­AÝp .profile­A¸×Ýšûj¶öùØ¾×¦Þ ID
     Shell ø_¸lü]¸w script­AÝp .bashrc­B.cshrc ¸× .kshrc­G

        . sqllib/java12/usejdbc2

  2. Ýê CLP æo¾XÏUÝC®¾O­G

        db2set DB2_USE_JDK12=1

ñì¸ûÝ^Ïµï®ÝšÏ„ï¸ Java UDFs ¸M·xÝsæ{õ€¦§ JDBC 1.22 XøÒæ{Ý­­A«ÑøäÝ‘ÏUÝCùB
’J­G

  1. Ýbûj¶öùØ¾×¦Þ ID ü]¸w·­AÝp .profile­A¸×Ýêûj¶öùØ¾×¦Þ ID Shell ø_¸lü]¸w
     script­AÝp .bashrc­B.cshrc ¸× .kshrcÏ§ñN¾HÏUÝ‘ÝCýóøœ­G

        . sqllib/java12/usejdbc2

  2. Ýê CLP æo¾XÏUÝC®¾O­G

        db2set DB2_USE_JDK12=

õ’ñ‘·ü¾×æ{Ý­¾i¾HÏ@¦«ùØ¾× JDBC 2.0 XøÒæ{Ý­­Añz¾i¾Hús¬W¾HÏUÝ‘ÝCÝšænÏJü]¸w
·­AÝp .profile­A¸×Ýš Shell ø_¸lü]¸w script­AÝp .bashrc­B.cshrc ¸× .kshrc­G

   . sqllib/java12/usejdbc2

«T¸wÝû®¾O¸¤÷mÝbøäÝ‘ db2profile ¦§®¾OÏõ® ­AÝ]ªø usejdbc2 ·ü÷àÝb db2profile
Ïõ® øäÝ‘­C

HP-UX

Ýb DB2 for HP-UX (õt JDK 1.1) ÏW­AÏœÏ„ï¸ Java ·xÝsæ{õ€Ï×ùØ¾×¦Þ¸w÷q¦§ù‡¬’­C

Silicon Graphics IRIX

ú¡ùØ¾× -o32 ¦®¾¢Çç®ªùà®÷m SQLJ ·ü¾×æ{Ý­ùÇùØ¾×ùÆÝü JDK 1.2.2 ¦§ Java JIT «s
Žôóû©­AðY SQLJ ¶…ï®æ{Ý­Ý]Ï·øØªq¨—¯~Ýà¾½ñ¥­A«Ñûµ÷å¾Hüoðà®¾OùàÇ”ñ¬ JIT «sŽô
óû­G

   export JAVA_COMPILER=NONE

Ýb Silicon Graphics IRIX ÏWô}æo Java SQLJ æ{Ý­©¯íðn JDK 1.2.2­C

Windows 32 ÝÏ÷õ@ú~ùtý×

ùØ¾× Java ·xÝsæ{õ€¸M UDF ¦§ JDBC 2.0 XøÒæ{Ý­

ñìùØ¾× Java ·xÝsæ{õ€¸M UDF ¦§ JDBC 2.0 XøÒæ{Ý­­Añz¾ýôúøäÝ‘ÏUÝCùB’Jùàü]¸w·“
ûã­G

  1. Ýb sqllib\java12 ¾¨ìÏUæo¾XÏUÝC®¾O­G

        usejdbc2

  2. Ýê CLP æo¾XÏUÝC®¾O­G

        db2set DB2_USE_JDK12=1

ñì¸ûÝ^Ïµï®ÝšÏ„ï¸ Java UDFs ¸M·xÝsæ{õ€¦§ JDBC 1.22 XøÒæ{Ý­­A«ÑøäÝ‘ÏUÝCùB
’J­G

  1. Ýb sqllib\java12 ¾¨ìÏUæo¾XÏUÝC®¾O­G

        usejdbc2

  2. Ýê CLP æo¾XÏUÝC®¾O­G

        db2set DB2_USE_JDK12=

34.3.1.1 OS/2 ÏW¦§ JDK ¬hÝ÷

øäÝ‘ 1999 Ý~ 9 Ï‰Ïõ®eæo¦¡¦§ JDK 1.1.8 ¦¸¦§ OS/2 æL¦kÆ¾šªYù€øT©õ­C «Ñ«T¸wñz
ùÆÝüüÞús¦§ JDK 1.1.8 ¦¸­C

34.3.1.2 HP-UX ÏW¦§ Java2

ðYðnøäÝ‘ Java2 ·xÝsæ{õ€­A¾ýôúšõ¢Ý@¾×·©ž©w÷“©|­AÝpÏU¸ã¾š­G

export SHLIB_PATH=$JAVADIR/jre/lib/PA_RISC:$JAVADIR/
jre/lib/PA_RISC/classic:$HOME/sqllib/lib:/usr/lib:$SHLIB_PATH

$JAVADIR ªO Java2 SDK ¦§Ý÷m­C
  ------------------------------------------------------------------------

34.4 ýŽ 5 üû ô}æo SQL æ{õ€

34.4.1 ü]¸w SQL æ{õ€·“ûã

ÏUÝCªOÇ”¸¢Ýb­uÝw÷Ó­vÏÏü]¸w DB2 ·“ûã®¾š¦§¦ç¾[¯­¸£­C

ðY¯í SQL æ{õ€Ï„ï¸­Añz¾ýôúÝbÝ›¦AóûÏWÝw÷Ó­u·ü¾×æ{Ý­ô}æoñqŽíî÷ (Application
Development Client)­v­CðY¯íÝw÷Ó­u·ü¾×æ{Ý­ô}æoñqŽíî÷­v¦§ªêÇ”÷ˆøT­A «Ñø¥úàóA
¾×ñz¦§¾ð¾x¦§ õ™ütÏJ¦— ©¥Žy­CðY¯íñz¾ð¾xÏÏ DB2 Ï„ï¸¦§ C Ï× C++ «sŽôóû¦§ªêÇ”÷ˆ
øT­A «Ñø¥ó\­u¾ð¾xÏ„ï¸¦§ün‚­v­C

æ—:
     Ýb OS/2 FAT ·©žùtý×ÏW­A­uSQL æ{õ€­v¦§§ä¾ÝW§ëððùŒªøÏKðàÝrÏ÷¾HÏU­C §ä
     ¾ÝW§ëðY¦›¸¢ÏKðàÝrÏ÷­A®h¾ýôúùØ¾× HPFS ·©žùtý×­C

«sŽôóûª[§c¾¥ùƒü­Ï·ýåÝù­G ü]¸w«sŽôóû¦§·“ûãš¬’Ï×¸w÷q«sŽô®¾O­C ·“ûãš¬’ïœù¥
«sŽôóû¦§ÏGôiÝ·(bin)­B·©ž©w(lib)Ï×ù™ÏJ·¦§÷“©|­C «sŽô®¾OªO DB2 ñN¾×ùà«s
Žô SQL æ{õ€¸ãýœ¾Ö¦§ C ·©ž¦§õûóÆ®¾O­C

34.4.2 ü]¸w«sŽôóû·“ûãš¬’

Ýb OS/2­BWindows Ï× UNIX õ@ú~ùtý×ÏWøt÷m·“ûãÝüÏœÝP¦§üW®h­A ÝpÏU¸ã¾š­C Ýbü­Ï·
¦§ñ­¦pÏU­AÏœ¯íðnõ@ª[§c­FÝbù„¾Ýñ­õ×©­A DB2_SQLROUTINE_COMPILER_PATH DB2 æn
¨ìš¬’¾ýôúü]¸wªø®ÝVÏ@ðà óAú¡¦§ü]¸w·“ûãš¬’¦§¾iøäÝ‘ Script­C

æ—:
     ñz¾iùØ¾× db2set ®¾O¸×ùØ¾×­u·xÝsæ{õ€®÷móû­v¦§ ­uSQL ·xÝsæ{õ€®÷m¨‹
     ôæ­vû‹÷š©ùàü]¸wüoðà DB2 æn¨ìš¬’¦§ðÔ­CùØ¾×­uSQL ·xÝsæ{õ€®÷m¨‹ôæ­vû‹
     ÷š© Ïœ¯íðnûˆ¯éÝsù£÷ˆ©’©wÝ›¦Aóû­A÷ˆ©’©wÝ›¦AóûÏ]Ïœ¾×ð®úsñãøÒ¾HùØšõ¢¾Ö
     ©Ž­C

Ýb OS/2 ÏW­G

øwû‹ IBM VisualAge C++ for OS/2 ¦¸¾¯ 3.6­G

   db2set DB2_SQLROUTINE_COMPILER_PATH="c:\ibmcxxo\bin\setenv.cmd"

øwû‹ IBM VisualAge C++ for OS/2 ¦¸¾¯ 4­G

   db2set DB2_SQLROUTINE_COMPILER_PATH="c:\ibmcpp40\bin\setenv.cmd"

æ—:
     üoù€®¾OªOøýü] C++ «sŽôóûªOÝw÷ÓÝb C: §Ø§ÑóöÏW­C Ýp¦G¯íðn­Ašõ¢§Ø§Ñóö¸×
     ÷“©|ùàÏØªMñzùtý×ÏW C++ «sŽôóû¦§Ý÷m­C

Ýb Windows 32 ÝÏ÷õ@ú~ùtý×ÏW­AÝp¦G«sŽôóû¦§·“ûãš¬’ªOü]¸wªø SYSTEM š¬’­A ®h
Ïœ¯íðnõ@¾“Ý¢øt÷m­C õ_®h­A«ÑñN DB2_SQLROUTINE_COMPILER_PATH DB2 æn¨ìš¬’ü]¸w
ªø­G

øwû‹ Microsoft Visual C++ ¦¸¾¯ 5.0­G

      db2set DB2_SQLROUTINE_COMPILER_PATH="c:\devstudio\vc\bin\vcvars32.bat"

øwû‹ Microsoft Visual C++ ¦¸¾¯ 6.0­G

      db2set DB2_SQLROUTINE_COMPILER_PATH="c:\Micros~1\vc98\bin\vcvars32.bat"

øwû‹ IBM VisualAge C++ for Windows ¦¸¾¯ 3.6­G

      db2set DB2_SQLROUTINE_COMPILER_PATH="c:\ibmcxxw\bin\setenv.bat"

øwû‹ IBM VisualAge C++ for Windows ¦¸¾¯ 4­G

      db2set DB2_SQLROUTINE_COMPILER_PATH="c:\ibmcppw40\bin\setenv.bat"

æ—:
     üoù€®¾OªOøýü] C++ «sŽôóûªOÝw÷ÓÝb C: §Ø§ÑóöÏW­C Ýp¦G¯íðn­Ašõ¢§Ø§Ñóö¸×
     ÷“©|ùàÏØªMñzùtý×ÏW C++ «sŽôóû¦§Ý÷m­C

Ýb UNIX õ@ú~ùtý×ÏW­ADB2 ú|ÝbñzýŽÏ@Ý÷«sŽô·xÝsæ{õ€©ýœ¾Ö¾iøäÝ‘¦§ Script ·
$HOME/sqllib/function/routine/sr_cpath (¾]õt«sŽôóû·“ûãš¬’¦§ûwü]ðÔ)­C ñz¾i
«s¨ŠÝû·©ž­AÝp¦Gûwü]ðÔÏœóA¾×¸¢ñz¦§«sŽôóû­C ¾t¾~­Añz¾iñN
DB2_SQLROUTINE_COMPILER_PATH DB2 æn¨ìš¬’ü]ªø¾]õt¾tÏ@ðà¾iøäÝ‘ Script ¦§õûóÆ
÷“©|ÝW§ë­AÝb Script Ï§®¸wïµñ‘¦§ðÔ («ÑªíÏWðñ¦§«dùã)­C

34.4.3 Ýêðq«sŽô®¾O

Application Development Client ¦§Ýw÷Óïœù¥ÏFÏ@ðàûwü]¦§«sŽô®¾O­A ÝšÏ™¾i¾×¸¢
ùCðà¾ð¾xÏWÏ„ï¸¦§«sŽôóûÏõÏ@­G

   AIX­GIBM C Set++ for AIX ¦¸¾¯ 3.6.6
   Solaris­GSPARCompiler C++ ¦¸¾¯ 4.2 Ï× 5.0
   HP-UX­GHP-UX C++ ¦¸¾¯ A.12.00
   Linux­GGNU/Linux g++ ¦¸¾¯ egcs-2.90.27 980315 (egcs-1.0.2 release)
   PTX­Gptx/C++ ¦¸¾¯ 5.2
   OS/2­GIBM VisualAge C++ for OS/2 ¦¸¾¯ 3
   Windows NT Ï× Windows 2000­GMicrosoft Visual C++ ¦¸¾¯ 5.0 Ï× 6.0

ðYðnùØ¾×ù„¾Ý«sŽôóû­A¸×ðnÝêðqûwü]®¾O­A ñz¾ýôúñN
DB2_SQLROUTINE_COMPILE_COMMAND DB2 æn¨ìš¬’ü]ªøÝpÏU¦§®¾O­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=compilation_command

ù„ÏÏ compilation_command ªO C ¸× C++ «sŽô®¾O­A ¾]ªA®¾á·xÝsæ{õ€¸ã¯í¦§¨‹ôæ
Ï×ø¥¬’­C

Ýb«sŽô®¾OÏÏ­A«ÑùØ¾×Ç”µ„Ýr SQLROUTINE_FILENAME ùàù£¾N¸ãýœ¾Ö¦§ SQC­BC­BPDB­B
DEF­BEXP­B øT©õÏ‚¯xÏ×Ý@¾×·©ž©w·©ž¦§·ÝW­CôÔøwû‹ AIX­AùØ¾×
SQLROUTINE_ENTRY Ç”µ„Ýrùàù£¾Næn¨ìÝW§ë­C

æ—:
     ñz¾iùØ¾× db2set ®¾O¸×ùØ¾×­u·xÝsæ{õ€®÷móû­v¦§ ­uSQL ·xÝsæ{õ€®÷m¨‹
     ôæ­vû‹÷š©ùàü]¸wüoðà DB2 æn¨ìš¬’¦§ðÔ­CùØ¾×­uSQL ·xÝsæ{õ€®÷m¨‹ôæ­vû‹
     ÷š© Ïœ¯íðnûˆ¯éÝsù£÷ˆ©’©wÝ›¦Aóû­A÷ˆ©’©wÝ›¦AóûÏ]Ïœ¾×ð®úsñãøÒ¾HùØšõ¢¾Ö
     ©Ž­C

ÏUÝCªO C ¸× C++ «sŽôóûÝbÏ„ï¸¦§Ý›¦Aóû¾ð¾x¦§ DB2_SQLROUTINE_COMPILE_COMMAND
ûwü]ðÔ­C

AIX

ùØ¾× IBM C for AIX ¦¸¾¯ 3.6.6­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=xlc -H512 -T512 \
   -I$HOME/sqllib/include SQLROUTINE_FILENAME.c -bE:SQLROUTINE_FILENAME.exp \
   -e SQLROUTINE_ENTRY -o SQLROUTINE_FILENAME -L$HOME/sqllib/lib -lc -ldb2

ùØ¾× IBM C Set++ for AIX ¦¸¾¯ 3.6.6­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=xlC -H512 -T512 \
   -I$HOME/sqllib/include SQLROUTINE_FILENAME.c -bE:SQLROUTINE_FILENAME.exp \
   -e SQLROUTINE_ENTRY -o SQLROUTINE_FILENAME -L$HOME/sqllib/lib -lc -ldb2

ðYùSÝüü]¸w DB2_SQLROUTINE_COMPILE_COMMAND DB2 ænøOš¬’­A®hüoªOûwü]«sŽô®
¾O­C

æ—:
     ðYðnÝb AIX ÏW«sŽô 64 ÝÏ÷ SQL æ{õ€­AñN -q64 ¨‹ôæús¬WùÏWðñ¦§®¾O­C

ùØ¾× IBM VisualAge C++ for AIX ¦¸¾¯ 4­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND="vacbld"

ðYñzÝb vacbld ®¾OÏõ® ùSÝü®¸wª[§c·­ADB2 ú|Ýbð§Ý÷®¾á SQL æ{õ€©­A ®¾áÏU
ÝCûwü]¦§ª[§c·­C

   $HOME/sqllib/function/routine/sqlproc.icc

ðYñzðnùØ¾×ÝêÏv¦§ª[§c·­A¾iÝbü]¸w DB2_SQLROUTINE_COMPILE_COMMAND ¦§ DB2 ænøO
ðÔ©­A ®¸wñzðnùØ¾×¦§ª[§c·­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND="vacbld
   %DB2PATH%/function/sqlproc.icc"

HP-UX

ùØ¾× HP C «sŽôóû¦¸¾¯ A.11.00.03­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=cc +DAportable +ul -Aa +z \
   -I$HOME/sqllib/include -c SQLROUTINE_FILENAME.c; \
   ld -b -o SQLROUTINE_FILENAME SQLROUTINE_FILENAME.o \
   -L$HOME/sqllib/lib -ldb2

ùØ¾× HP-UX C++ ¦¸¾¯ A.12.00­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=CC +DAportable +a1 +z -ext \
   -I$HOME/sqllib/include -c SQLROUTINE_FILENAME.c; \
   ld -b -o SQLROUTINE_FILENAME SQLROUTINE_FILENAME.o \
   -L$HOME/sqllib/lib -ldb2

ðYùSÝüü]¸w DB2_SQLROUTINE_COMPILE_COMMAND DB2 ænøOš¬’­A®hüoªOûwü]«sŽô®
¾O­C

Linux

ùØ¾× GNU/Linux gcc ¦¸¾¯ 2.7.2.3­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=cc \
   -I$HOME/sqllib/include SQLROUTINE_FILENAME.c \
   -shared -o SQLROUTINE_FILENAME -L$HOME/sqllib/lib -ldb2

ùØ¾× GNU/Linux g++ ¦¸¾¯ egcs-2.90.27 980315 (egcs-1.0.2 ¦¸Ý÷)­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=g++ \
   -I$HOME/sqllib/include SQLROUTINE_FILENAME.c \
   -shared -o SQLROUTINE_FILENAME -L$HOME/sqllib/lib -ldb2

ðYùSÝüü]¸w DB2_SQLROUTINE_COMPILE_COMMAND DB2 ænøOš¬’­A®hüoªOûwü]«sŽô®
¾O­C

PTX

ùØ¾× ptx/C ¦¸¾¯ 4.5­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=cc -KPIC \
   -I$HOME/sqllib/include SQLROUTINE_FILENAME.c \
   -G -o SQLROUTINE_FILENAME.so -L$HOME/sqllib/lib -ldb2 ; \
   cp SQLROUTINE_FILENAME.so SQLROUTINE_FILENAME

ùØ¾× ptx/C++ ¦¸¾¯ 5.2­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=c++ -KPIC \
   -D_RWSTD_COMPILE_INSTANTIATE=0
   -I$HOME/sqllib/include SQLROUTINE_FILENAME.c \
   -G -o SQLROUTINE_FILENAME.so -L$HOME/sqllib/lib -ldb2 ; \
   cp SQLROUTINE_FILENAME.so SQLROUTINE_FILENAME

ðYùSÝüü]¸w DB2_SQLROUTINE_COMPILE_COMMAND DB2 ænøOš¬’­A®hüoªOûwü]«sŽô®
¾O­C

OS/2

ùØ¾× IBM VisualAge C++ for OS/2 ¦¸¾¯ 3­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND="icc -Ge- -Gm+ -W2
   -I%DB2PATH%\include SQLROUTINE_FILENAME.c
   /B\"/NOFREE /NOI /ST:64000\" SQLROUTINE_FILENAME.def
   %DB2PATH%\lib\db2api.lib"

ðYùSÝüü]¸w DB2_SQLROUTINE_COMPILE_COMMAND DB2 ænøOš¬’­A®hüoªOûwü]«sŽô®
¾O­C

ùØ¾× IBM VisualAge C++ for OS/2 ¦¸¾¯ 4­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND="vacbld"

ðYñzÝb vacbld ®¾OÏõ® ùSÝü®¸wª[§c·­ADB2 ú|Ýbð§Ý÷®¾á SQL æ{õ€©­A ®¾áÏU
ÝCûwü]¦§ª[§c·­C

   %DB2PATH%\function\routine\sqlproc.icc

ðYñzðnùØ¾×ÝêÏv¦§ª[§c·­A¾iÝbü]¸w DB2_SQLROUTINE_COMPILE_COMMAND ¦§ DB2 ænøO
ðÔ©­A ®¸wñzðnùØ¾×¦§ª[§c·­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND="vacbld
   %DB2PATH%\function\sqlproc.icc"

Solaris

ùØ¾× SPARCompiler C ¦¸¾¯ 4.2 ¸M 5.0­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=cc -xarch=v8plusa -Kpic \
   -I$HOME/sqllib/include SQLROUTINE_FILENAME.c \
   -G -o SQLROUTINE_FILENAME -L$HOME/sqllib/lib \
   -R$HOME/sqllib/lib -ldb2

ùØ¾× SPARCompiler C++ ¦¸¾¯ 4.2 ¸M 5.0­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=CC -xarch=v8plusa -Kpic \
   -I$HOME/sqllib/include SQLROUTINE_FILENAME.c \
   -G -o SQLROUTINE_FILENAME -L$HOME/sqllib/lib \
   -R$HOME/sqllib/lib -ldb2

ðYùSÝüü]¸w DB2_SQLROUTINE_COMPILE_COMMAND DB2 ænøOš¬’­A®hüoªOûwü]«sŽô®
¾O­C

æ—:

  1. -xarch=v8plusa «sŽôóû¨‹ôæÏwús¬Wùûwü]«sŽôóû®¾O­CÝüÇ”ªøÝ¢ús¬WÝû¨‹ôæ¦§
     ýà÷`­A«Ñø¥ó\34.8, "ýŽ 12 üû ô}æo Solaris ·ü¾×æ{Ý­"­C

  2. ðYðnÝb Solaris ÏW«sŽô 64 ÝÏ÷ SQL æ{õ€­Aù£©› -xarch=v8plusa ¨‹ôæ­AùÇñN
     -xarch=v9 ¨‹ôæús¬WùÏWðñ¦§®¾O­C

Windows NT ¸M Windows 2000

æ—:
     Windows 98 ¸× Windows 95 ÏœÏ„ï¸ SQL æ{õ€­C

ùØ¾× Microsoft Visual C++ ¦¸¾¯ 5.0 ¸M 6.0­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=cl -Od -W2 /TC -D_X86_=1
   -I%DB2PATH%\include SQLROUTINE_FILENAME.c /link -dll
   -def:SQLROUTINE_FILENAME.def /out:SQLROUTINE_FILENAME.dll
   %DB2PATH%\lib\db2api.lib

ðYùSÝüü]¸w DB2_SQLROUTINE_COMPILE_COMMAND DB2 ænøOš¬’­A®hüoªOûwü]«sŽô®
¾O­C

ùØ¾× IBM VisualAge C++ for Windows ¦¸¾¯ 3.6­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND="ilib /GI
   SQLROUTINE_FILENAME.def &icc -Ti -Ge- -Gm+ -W2
   -I%DB2PATH%\include SQLROUTINE_FILENAME.c
   /B\"/ST:64000 /PM:VIO /DLL\" SQLROUTINE_FILENAME.exp
   %DB2PATH%\lib\db2api.lib"

ùØ¾× IBM VisualAge C++ for Windows ¦¸¾¯ 4­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND="vacbld"

ðYñzÝb vacbld ®¾OÏõ® ùSÝü®¸wª[§c·­ADB2 ú|Ýbð§Ý÷®¾á SQL æ{õ€©­A ®¾áÏU
ÝCûwü]¦§ª[§c·­C

   %DB2PATH%\function\routine\sqlproc.icc

ðYñzðnùØ¾×ÝêÏv¦§ª[§c·­A¾iÝbü]¸w DB2_SQLROUTINE_COMPILE_COMMAND ¦§ DB2 ænøO
ðÔ©­A ®¸wñzðnùØ¾×¦§ª[§c·­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND="vacbld
   %DB2PATH%\function\sqlproc.icc"

ðYðnô€Ý^ûwü]«sŽôóû¨‹ôæ­A¾HÏUÝC®¾OñN DB2_SQLROUTINE_COMPILE_COMMAND ¦§ DB2
ænøOðÔ ü]¸wªø NULL­G

   db2set DB2_SQLROUTINE_COMPILE_COMMAND=

34.4.4 ®OîdÏÏô­·

ú¡ SQL æ{õ€ùSÝüÝù¾\®¾á©­Añz¾ýôúÏƒøÒõRøœüQ¾ ñ¢¦§ÏÏô­·­Cüoù€·©žÝ¸¢ÏUÝC¾
¨ì÷Þ­G

UNIX
     $DB2PATH/function/routine/sqlproc/$DATABASE/$SCHEMA/tmp

     ÝbÝû $DB2PATH ªO®¾á©žùã¦§¾¨ì­A$DATABASE ªO÷ˆ©’©wÝW§ë­A Ýà $SCHEMA ªO
     ¾×ùà®¾á SQL æ{õ€¦§§ä¾ÝW§ë­C

OS/2 ¸M Windows
     %DB2PATH%\function\routine\sqlproc\%DATABASE%\%SCHEMA%\tmp

     ù„ÏÏ %DB2PATH% ¾N¦¡®¾á©žùã¦§¾¨ì­A%DATABASE% ¾N¦¡÷ˆ©’©wÝW§ë­A Ýà
     %SCHEMA% ¾N¦¡¾×ùà®¾á SQL æ{õ€¦§§ä¾ÝW§ë­C

34.4.5 ü’¾ö¸Mï_÷m

Ýb®¾á SQL æ{õ€©­Aýœ¾Ö¦§Ý@¾×·©ž©w/DLL Ï]ú|®OîdÝb®ª¨ì¦¡©‘ÏÏ­A Ýp¦Gýœ¾Ö¦§Ý@
¾×·©ž©w/DLL Ïp¸¢ 2 MB­C Ýbü’¾öÏ×ï_÷m÷ˆ©’©w©­A¾“Ý¢ýœ¾Ö¦§Ý@¾×·©ž©w/DLL Ïp
¸¢ 2 MB ¦§ SQL æ{õ€ú|ùØ¾× ®ª¨ì¦¡©‘ÏÏ¸ã®Oîd¦§¦¸¾¯ùàøæü’¾öÏ×ï_÷m­C Ýp¦GñzÝüýœ
¾Ö¦§Ý@¾×·©ž©w/DLL Ïj¸¢ 2 MB ¦§ SQL æ{õ€­A «Ñ«T¸wñzÏ]¾×÷ˆ©’©wü’¾öÏ×ï_÷mùàøæ
·©žùtý×¦§ü’¾öÏ×ï_÷m­C Ýp¦GùSÝü­Añz¾ýôúùØ¾× syscat.procedures ®ª¨ì¦¡©‘ÏÏ¦§
ùàú«ÝêÝ‘ð®® SQL æ{õ€¦§Ý@¾×·©ž©w/DLL­C

æ—:
     Ýb÷ˆ©’©wÝ^ï_©­A¸ãÝü·©žùtý×ÏWŽí¸¢üQÝ^ï_÷ˆ©’©w¦§ SQL æ{õ€¾iøäÝ‘·ú|üQ
     ýóøœ­C Ýp¦GîµÏè®¾áª[§cø¥¬’ (indexrec) ü]ªø RESTART­AïNú|ñq®ª¨ì¦¡©‘¶^
     ù£¸ãÝü SQL æ{õ€¾iøäÝ‘·­A ùÇ¸¢ÏUÝ÷üsñæ©¸¤Ý^·©žùtý×­C õ_®h­ASQL ¾iøä
     Ý‘·ú|Ýb SQL æ{õ€ýŽÏ@Ý÷øäÝ‘©¶^ù£­C

¾iøäÝ‘·ú|üQ¸¤Ý^ùÏUÝC¾¨ì­G

UNIX
     $DB2PATH/function/routine/sqlproc/$DATABASE

     ÝbÝû $DB2PATH ªO®¾á©žùã¦§¾¨ì­AÝà $DATABASE ªO¾×ùà®¾á SQL æ{õ€¦§÷ˆ©’
     ©wÝW§ë­C

OS/2 ¸M Windows
     %DB2PATH%\function\routine\sqlproc\%DATABASE%

     ù„ÏÏ %DB2PATH% ¾N¦¡®¾á©žùã¦§¾¨ì­A Ýà %DATABASE% ¾N¦¡¾×ùà®¾á SQL æ{
     õ€¦§÷ˆ©’©wÝW§ë­C

34.4.6 ®¾á SQL æ{õ€

ñN÷ˆ©’©w§èýzæ{Ý­¦§ª[§cø¥¬’ KEEPDARI ü]¸wªø 'NO'­A¾H®÷m SQL æ{õ€­C ðY SQL
æ{õ€Ï@¾ûøäÝ‘©§–®—÷ÏJ¦ª§A­Aðn¾HÝPÝWñÓñ¢¸Mð®®·xÝsæ{õ€©¾iî…ú|óDûJøíÇD­A Ýp
ÝP·©ž©wæL¦kï_ús­AÝà¾iøäÝ‘·æL¦kñq·©žùtý×ñÓñ¢­Cú¡ñzûµ÷åï_ðšõ¢¸×ñÓñ¢÷ˆ©’
©w©Ï]ú|óDûJøíÇD­AÝ]ªøæL¦kõRøœ¾iøäÝ‘·­C

«Ñø¥ó\­u·ü¾×æ{Ý­ô}æoÏƒ¾U­AýŽ 2 üû ü]¸w­v¦§­uõ¢ús÷ˆ©’©w§èýzæ{Ý­ª[§c·­v­A¾H
ù£ñoü]¸w KEEPDARI ø¥¬’¦§÷âýà÷ˆøT­C

æ—:
     SQL æ{õ€ÏœÏ„ï¸ÏUÝCø¥¬’¦§÷ˆ©’Çç®ª­G
        o LONG VARGRAPHIC
        o ÏGôiÝÏj®ª¦®¾¢ (BLOB)
        o ÝrÏ÷Ïj®ª¦®¾¢ (CLOB)
        o ¶—ÝÏ÷ýåÏj®ª¦®¾¢ (DBCLOB)

34.4.7 ¸I¾s·xÝsæ{õ€

­uùØ¾×¸I¾s®¾O­vÏÏ¦§ýŽÏ@ªq·ü÷à¦ù£­G

ñìùØ¾×¸I¾s®¾O­A«Ñ¨‚ÏJ·xÝsæ{õ€ÝW§ë­A¾HÏ× IN ¸× INOUT ¦§ø¥¬’­AµëÝüüQæ›ªøùCÏ@
ðà¨‚¾Xø¥¬’ÏõÝ÷m®Oîdý÷û '?'­C ðYðnù£ño CALL ®¾O¦§÷âýà¯y¦k­A«Ñø¥ó\10.14,
"CALL"­C

34.4.8 Ï·øeÏw«sŽô¦§ SQL æ{õ€

æ—:
     ðYðnÝb DB2 Ý›¦AóûÏõô­Ï·øeÏw«sŽô¦§ SQL æ{õ€­A ñz¾ýôúû‹¸¢ùCÏ@ðàú|õ@ªøÏw
     «sŽô SQL æ{õ€¦§ùàú« (¸×¾¬Ñ) ¦§ DB2 Ý›¦AóûøäÝ‘ÏUÝCùB’J­G

      ùB’J    Ýw÷Ó FixPak 3
      1.

      ùB’J    æo¾X db2updv7 ®¾O¾Hñã¾× DB2 ùàù£¾XÏ×Ýw÷ÓÏw«sŽô¦§ SQL æ{õ€­G
      2.
                   db2updv7 -d database_name

ú¡ñz¸w÷qÏ@ðà SQL æ{õ€©­A¾Ýú|¶…ï®ªøÏ@ðà C æ{Ý­­Bûw¾ì«sŽôûL­B û‹¾¬Ñ÷ˆ©’©wüs
æý­B«sŽôùÇÇæý¾H®¾áÏ@ðàÝ@¾×·©ž©w­C «sŽôÏ×Çæý¦§ùB’J¯íðnÝb÷ˆ©’©wÝ›¦Aóûóöóû
ÏWÝü¾i¾×¦§ C ¸× C++ «sŽôóû­CæMÝà­AñzÝb¸w÷q SQL æ{õ€©­A ñz¾iñN¾Ý¾HÏw«sŽô¦§
õ×Ý­Ï·øeùÝbªêÝP¾ð¾xÏWøäÝ‘¦§ DB2 ÷ˆ©’©w­A ÝàÏœ¯íðn¾iÝsù£ C ¸× C++ «sŽôóû­C
DB2 ©eü\ùØ¾×¦ÞñqÏ@ðà÷ˆ©’©wù£¾XÏw«sŽôõ×Ý­¦§ SQL æ{õ€­A ¾HÏ×Ýw÷ÓÏw«sŽôõ×Ý­¦§
SQL æ{õ€ù¾tÏ@ðà÷ˆ©’©w­C

DB2 ïœù¥ÏF®¾OÝ‘ÏôðñÏ×æ{Ý­ü]ðpÏôðñùàøäÝ‘ù£¾XÏ×Ýw÷Óõ@ú~­C®¾OÝ‘Ïôðñ¾¥ùƒðà
CLP ®¾OýåÝù­G GET ROUTINE Ï× PUT ROUTINE­Cæ{Ý­ü]ðpÏôðñ¾¥ùƒðàÏ§®·xÝsæ{õ€ýå
Ýù­GGET_ROUTINE_SAR Ï× PUT_ROUTINE_SAR­CÝüÇ”®¾OÝ‘Ïôðñ¦§÷âýà÷ˆøT­A«Ñø¥úà
Command Reference­CÝüÇ”æ{Ý­ü]ðpÏôðñ¦§÷âýà÷ˆøT­A «Ñø¥úà SQL Reference­C

ðYðnñqÏ@ðà÷ˆ©’©wÝ›¦AóûÏ·øeÏw«sŽô¦§ SQL æ{õ€ù¾tÏ@ðà÷ˆ©’©wÝ›¦Aóû­A «ÑøäÝ‘ÏU
ÝCùB’J­G

 ùB’J  1. ô}æo·ü¾×æ{Ý­­A¾]ªA¸w÷qªø·ü¾×æ{Ý­ü­Ï·¦§ SQL æ{õ€­C

 ùB’J  2. Ýbï£÷åæ{õ€® ­AñNùCÏ@ðàæ{õ€¦§Ïw«sŽô¦¸¾¯ù£¾XùÏ@ðàÏœÝP¦§·©ž­C ðY
          ¯í÷âýà÷ˆøT­A«Ñø¥úà Command Reference ÏÏ¦§ GET ROUTINE ®¾O¸×
          SQL Reference ÏÏ¦§ GET_ROUTINE_SAR ·xÝsæ{õ€­C

 ùB’J  3. ÝbùCÏ@¾xÝ›¦AóûÏWÝw÷ÓùCÏ@ðàæ{õ€¦§Ïw«sŽô¦¸¾¯­A ñz¾iæo¾X PUT
          ROUTINE ®¾O­A¸×¸I¾s PUT_ROUTINE_SAR ·xÝsæ{õ€ (ùØ¾× 2 ¸ã®¾á¦§
          ·©ž)­CùCÏ@ðà÷ˆ©’©wÝ›¦Aóû¦§õ@ú~ùtý×Ï× DB2 ¬hÝ÷¾ýôúªêÝP­C
  ------------------------------------------------------------------------

34.5 ýŽ 7 üû ô}æo HP-UX ·ü¾×æ{Ý­

34.5.1 HP-UX C

Ýb­uÝhð®øäÝ‘§·ü¾×æ{Ý­­vÏ§­Abldmt Script ·¾¥ÏœÝP¦§«sŽô¨‹ôæðž¾¨­C ús¦¸¾¯Ýb
sqllib/samples/c ¾¨ìÏU­C

34.5.2 HP-UX C++

Ýb®÷m Script ÏÏ­AHP aC++ «sŽôóû¦§ C++ «sŽôóûš¬’ CC üQù£¾Nªø aCC­C ®÷m
Script ¦§ðž¾¨¦¸Ýb sqllib/samples/cpp ¾¨ìÏU­C

"+u1" «sŽô¨‹ôæ·ü÷à¸M aCC «sŽôóûÏ@ø_¾×ùà®÷m·xÝsæ{õ€Ï× UDF­C Ýû¨‹ôæ©eü\¾¬«å
óÆ¦§÷ˆ©’Ýsù£­C¦çÝb DB2 for HP-UX ÏÏ¦§«dùã®÷m Script­B bldsrv ¸M bldudf­A¾H
Ï×«dùã makefile ¸|¾¬¾×Ýû¨‹ôæõ¢ús­CÝbùØ¾×®e·ü÷àðnðžõ‹¾ÝðÞùà¾[ÏJüoðà¨‹ôæ­C üo
÷ÞªO bldsrv Ï× bldudf Script ¦§ús«sŽôùB’J­G

   aCC +DAportable +u1 -Aa +z -ext -I$DB2PATH/include -c $1.C

Ýb­uÝhð®øäÝ‘§·ü¾×æ{Ý­­vÏ§­Abldmt Script ·¾¥ÏœÝP¦§«sŽô¨‹ôæðž¾¨­C ús¦¸¾¯Ýb
sqllib/samples/cpp ¾¨ìÏU­C
  ------------------------------------------------------------------------

34.6 ýŽ 9 üû ô}æo OS/2 ·ü¾×æ{Ý­

34.6.1 VisualAge C++ for OS/2 ¦¸¾¯ 4.0

øwû‹ OS/2 ¸M Windows­AùØ¾× set ®¾OÝàÏœùØ¾×Ýû÷`ÏÏ¦§ export ®¾O­CùãÝp­Aset
CLI=tbinfo­C

Ýb­uDB2 CLI ·ü¾×æ{Ý­­v¦§Ý÷üû÷`­u®÷mùÇøäÝ‘Ï§õt¦§ SQL ·ü¾×æ{Ý­­v÷Þ­A øwû‹
OS/2 ¸M Windows­A¾ýôúùØ¾× cliapi.icc ·Ýà®D cli.icc ·­A Ý]ªøÏ§õt¦§ SQL ·ü
¾×æ{Ý­¯íðn¾¥ cliapi.icc Çæý¦§ db2api.lib ·©ž©w­C
  ------------------------------------------------------------------------

34.7 ýŽ 10 üû ô}æo PTX ·ü¾×æ{Ý­

34.7.1 ptx/C++

·©ž©w¯íðn¾H -shared ¨‹ôæÇæý­A¾H®÷m·xÝsæ{õ€¸MùØ¾×¦Þ¸w÷qù‡¬’­C Ýb
sqllib/samples ¾¨ì÷Þ­Amakefile­B ®÷m scripts bldsrv ¸M bldudf Ïwõ¢úsù™ÏJ
üoðà¨‹ôæ­A ÝpÝPÏUÝC bldsrv ¦§ÇæýùB’J­G

   c++ -shared -G -o $1 $1.o -L$DB2PATH/lib -ldb2

  ------------------------------------------------------------------------

34.8 ýŽ 12 üû ô}æo Solaris ·ü¾×æ{Ý­

34.8.1 SPARCompiler C++

¸¢ Solaris øäÝ‘ C/C++ ·ü¾×æ{Ý­¸M SQL æ{õ€¦§øíÇD

ùØ¾× Sun WorkShop Compiler C/C++­AÝp¦Gñz÷Iù¾iøäÝ‘·ñæÝªùÏUÝC¨—¯~øT©õ©­G

  1. ýŽÏ@Ý‘¯y¦k¨—¯~: `('ûwïµ¦§
  2. ksh: <·ü¾×æ{Ý­ÝW§ë>: Ïœî…øäÝ‘ (·ü¾×æ{Ý­ÝW§ëªø¾iøäÝ‘·ÝW§ë)

ñz¾iî…ûJù¦§øíÇDªO­A«sŽôóûÝbÇæý libdb2.so ©­AùSÝüýœ¾ÖÝü©Ž¦§¾iøäÝ‘·­C ®
Žüðž¾¨ÏŠ¦k­Aús¬WÏUÝC«sŽôóû¨‹ôæÝš«sŽô¸MÇæý®¾O­G

   -xarch=v8plusa

«dùã­Aú¡«sŽô«dùã·ü¾×æ{Ý­ dynamic.sqc­G

   embprep dynamic sample
   embprep utilemb sample
   cc -c utilemb.c -xarch=v8plusa -I/export/home/db2inst1/sqllib/include
   cc -o dynamic dynamic.c utilemb.o -xarch=v8plusa -I/export/home/db2inst1/sqllib/include \
      -L/export/home/db2inst1/sqllib/lib -R/export/home/db2inst1/sqllib/lib -l db2

æ—:

  1. ðYñzÝb Solaris ÏWùØ¾× SQL æ{õ€­AùÇüzûL DB2_SQLROUTINE_COMPILE_COMMAND
     ü]¸w·š¬’ùàùØ¾×ÝêÏv¦§«sŽôÝrÝˆ­A«Ñ«T¸wñzÏwñNÏWðz¦§«sŽôóû¨‹ôæù™ÏJ­C ûw
     ü]¦§«sŽôóû®¾O¾]ªAÝû¨‹ôæ­G

        db2set DB2_SQLROUTINE_COMPILE_COMMAND="cc -# -Kpic  -xarch=v8plusa -I$HOME/sqllib/include \
           SQLROUTINE_FILENAME.c -G -o SQLROUTINE_FILENAME -L$HOME/sqllib/lib -R$HOME/sqllib/lib -ldb2

  2. ðYðnÝb Solaris ÏW«sŽô 64 ÝÏ÷ SQL æ{õ€­Aù£©› -xarch=v8plusa ¨‹ôæ­AùÇñN
     -xarch=v9 ¨‹ôæús¬WùÏWðñ¦§®¾O­C

  ------------------------------------------------------------------------

34.9 ýŽ 13 üû ®÷m Windows 32 ÝÏ÷õ@ú~ùtý×¦§·ü¾×æ{Ý­

34.9.1 VisualAge C++ ¦¸¾¯ 4.0

øwû‹ OS/2 ¸M Windows­AùØ¾× set ®¾OÝàÏœùØ¾×Ýû÷`ÏÏ¦§ export ®¾O­CùãÝp­Aset
CLI=tbinfo­C

Ýb­uDB2 CLI ·ü¾×æ{Ý­­v¦§Ý÷üû÷`­u®÷mùÇøäÝ‘Ï§õt¦§ SQL ·ü¾×æ{Ý­­v÷Þ­A øwû‹
OS/2 ¸M Windows­A¾ýôúùØ¾× cliapi.icc ·Ýà®D cli.icc ·­A Ý]ªøÏ§õt¦§ SQL ·ü
¾×æ{Ý­¯íðn¾¥ cliapi.icc Çæý¦§ db2api.lib ·©ž©w­C
  ------------------------------------------------------------------------

Application Development Guide(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

35.1 Chapter 2. Coding a DB2 Application

35.1.1 Activating the IBM DB2 Universal Database Project and Tool Add-ins
for Microsoft Visual C++

Before running the db2vccmd command (step 1), please ensure that you have
started and stopped Visual C++ at least once with your current login ID.
The first time you run Visual C++, a profile is created for your user ID,
and that is what gets updated by the db2vccmd command. If you have not
started it once, and you try to run db2vccmd, you may see errors like the
following:

   "Registering DB2 Project add-in ...Failed! (rc = 2)"

  ------------------------------------------------------------------------

35.2 Chapter 6. Common DB2 Application Techniques

35.2.1 Generating Sequential Values

Generating sequential values is a common database application development
problem. The best solution to that problem is to use sequence objects and
sequence expressions in SQL. Each sequence object is a uniquely named
database object that can be accessed only by sequence expressions. There
are two sequence expressions: the PREVVAL expression and the NEXTVAL
expression. The PREVVAL expression returns the most recently generated
value for the specified sequence for a previous statement. The NEXTVAL
sequence expression increments the value of the sequence object and returns
the new value of the sequence object.

To create a sequence object, issue the CREATE SEQUENCE statement. For
example, to create a sequence object called id_values using the default
attributes, issue the following statement:

CREATE SEQUENCE id_values

To display the current value of the sequence object, issue a VALUES
statement using the PREVVAL expression:

VALUES PREVVAL FOR id_values

1
-----------
          1

            1 record(s) selected.

You can repeatedly retrieve the current value of the sequence object, and
the value that the sequence object returns does not change until you issue
a NEXTVAL expression. In the following example, the PREVVAL expression
returns a value of 1, until the NEXTVAL expression increments the value of
the sequence object:

VALUES PREVVAL FOR id_values

1
-----------
          1

            1 record(s) selected.

VALUES PREVVAL FOR id_values

1
-----------
          1

            1 record(s) selected.

VALUES NEXTVAL FOR id_values

1
-----------
          2

            1 record(s) selected.

VALUES PREVVAL FOR id_values

1
-----------
          2

            1 record(s) selected.

To update the value of a column with the next value of the sequence object,
include the NEXTVAL expression in the UPDATE statement, as follows:

UPDATE staff
  SET id = NEXTVAL FOR id_values
  WHERE id = 350

To insert a new row into a table using the next value of the sequence
object, include the NEXTVAL expression in the INSERT statement, as follows:

INSERT INTO staff (id, name, dept, job)
  VALUES (NEXTVAL FOR id_values, 'Kandil', 51, 'Mgr')

For more information on the PREVVAL and NEXTVAL expressions, refer to the
SQL Reference.

35.2.1.1 Controlling Sequence Behavior

You can tailor the behavior of sequence objects to meet the needs of your
application. You change the attributes of a sequence object when you issue
the CREATE SEQUENCE statement to create a new sequence object, and when you
issue the ALTER SEQUENCE statement for an existing sequence object.
Following are some of the attributes of a sequence object that you can
specify:

Data type
     The AS clause of the CREATE SEQUENCE statement specifies the numeric
     data type of the sequence object. The data type, as specified in the
     "SQL Limits" appendix of the SQL Reference, determines the possible
     minimum and maximum values of the sequence object. You cannot change
     the data type of a sequence object; instead, you must drop the
     sequence object by issuing the DROP SEQUENCE statement and issuing a
     CREATE SEQUENCE statement with the new data type.

Start value
     The START WITH clause of the CREATE SEQUENCE statement sets the
     initial value of the sequence object. The RESTART WITH clause of the
     ALTER SEQUENCE statement resets the value of the sequence object to a
     specified value.

Minimum value
     The MINVALUE clause sets the minimum value of the sequence object.

Maximum value
     The MAXVALUE clause sets the maximum value of the sequence object.

Increment value
     The INCREMENT BY clause sets the value that each NEXTVAL expression
     adds to the sequence object. To decrement the value of the sequence
     object, specify a negative value.

Sequence cycling
     The CYCLE clause causes the value of a sequence object that reaches
     its maximum or minimum value to return to its start value on the
     following NEXTVAL expression.

For example, to create a sequence object called id_values that starts with
a value of 0, has a maximum value of 1000, increments by 2 with each
NEXTVAL expression, and returns to its start value when the maximum value
is reached, issue the following statement:

CREATE SEQUENCE id_values
  START WITH 0
  INCREMENT BY 2
  MAXVALUE 1000
  CYCLE

For more information on the CREATE SEQUENCE and ALTER SEQUENCE statements,
refer to the SQL Reference.

35.2.1.2 Improving Performance with Sequence Objects

Like identity columns, using sequence objects to generate values generally
improves the performance of your applications in comparison to alternative
approaches. The alternative to sequence objects is to create a
single-column table that stores the current value and incrementing that
value with either a trigger or under the control of the application. In a
distributed environment where applications concurrently access the
single-column table, the locking required to force serialized access to the
table can seriously affect performance.

Sequence objects avoid the locking issues that are associated with the
single-column table approach and can cache sequence values in memory to
improve DB2 response time. To maximize the performance of applications that
use sequence objects, ensure that your sequence object caches an
appropriate amount of sequence values. The CACHE clause of the CREATE
SEQUENCE and ALTER SEQUENCE statements specifies the maximum number of
sequence values that DB2 generates and stores in memory.

If your sequence object must generate values in order, without introducing
gaps in that order due to a system failure or database deactivation, use
the ORDER and NO CACHE clauses in the CREATE SEQUENCE statement. The NO
CACHE clause guarantees that no gaps appear in the generated values at the
cost of some of your application's performance because it forces your
sequence object to write to the database log every time it generates a new
value.

35.2.1.3 Comparing Sequence Objects and Identity Columns

Although sequence objects and identity columns appear to serve similar
purposes for DB2 applications, there are a number of important differences:

   * An identity column automatically generates values for a column in a
     single table. A sequence object generates sequential values that can
     be used in any SQL statement.
   * An identity column generates values that are guaranteed to be unique.
     Including the CYCLE clause in a CREATE SEQUENCE or ALTER SEQUENCE
     statement enables that sequence object to generate duplicate values.

  ------------------------------------------------------------------------

35.3 Chapter 7. Stored Procedures

35.3.1 DECIMAL Type Fails in Linux Java Routines

This problem occurs because the IBM Developer Kit for Java does not create
links for its libraries in the /usr/lib directory. The security model for
DB2 routines does not allow them to access libraries outside of the
standard system libraries. To enable DECIMAL support in Java routines on
Linux, perform the following steps:

  1. Create symbolic links from the IBM Developer Kit for Java libraries to
     /usr/lib/ by issuing the following command with root authority:

     For IBM Developer Kit for Java 1.1.8:

        ln -sf /usr/jdk118/lib/linux/native_threads/* /usr/lib/

     For IBM Developer Kit for Java 1.3:

        ln -sf /opt/IBMJava2-13/jre/bin/*.so /usr/lib/

  2. Issue the ldconfig command to update the list of system-wide
     libraries.

35.3.2 Using Cursors in Recursive Stored Procedures

To avoid errors when using SQL Procedures or stored procedures written in
embedded SQL, close all open cursors before issuing a recursive CALL
statement.

For example, assume the stored procedure MYPROC contains the following code
fragment:

   OPEN c1;
   CALL MYPROC();
   CLOSE c1;

DB2 returns an error when MYPROC is called because cursor c1 is still open
when MYPROC issues a recursive CALL statement. The specific error returned
by DB2 depends on the actions MYPROC performs on the cursor.

To successfully call MYPROC, rewrite MYPROC to close any open cursors
before the nested CALL statement as shown in the following example:

OPEN c1;
CLOSE c1;
CALL MYPROC();

Close all open cursors before issuing the nested CALL statement to avoid an
error.

35.3.3 Writing OLE Automation Stored Procedures

The last sentence in the following paragraph is missing from the second
paragraph under section "Writing OLE automation Stored Procedures":

   After you code an OLE automation object, you must register the
   methods of the object as stored procedures using the CREATE
   PROCEDURE statement. To register an OLE automation stored
   procedure, issue a CREATE PROCEDURE statement with the LANGUAGE
   OLE clause. The external name consists of the OLE progID identifying
   the OLE automation object and the method name separated
   by ! (exclamation mark). The OLE automation object needs to be
   implemented as an in-process server (.DLL).

  ------------------------------------------------------------------------

35.4 Chapter 12. Working with Complex Objects: User-Defined Structured
Types

35.4.1 Inserting Structured Type Attributes Into Columns

The following rule applies to embedded static SQL statements: To insert an
attribute of a user-defined structured type into a column that is of the
same type as the attribute, enclose the host variable that represents the
instance of the type in parentheses, and append the double-dot operator and
attribute name to the closing parenthesis. For example, consider the
following situation:

   - PERSON_T is a structured type that includes the attribute NAME
     of type VARCHAR(30).
   - T1 is a table that includes a column C1 of type VARCHAR(30).
   - personhv is the host variable declared for type PERSON_T in the
     programming language.

The proper syntax for inserting the NAME attribute into column C1 is:

   EXEC SQL INSERT INTO T1 (C1) VALUES ((:personhv)..NAME)

  ------------------------------------------------------------------------

35.5 Chapter 13. Using Large Objects (LOBs)

35.5.1 Large object (LOBs) support in federated database systems

DB2 supports three types of large objects (LOBs): character large objects
(CLOBs), double-byte character large objects (DBCLOBs) and binary large
objects (BLOBs). For general information about DB2 LOB support, see the
following DB2 books:

   * DB2 Application Development Guide(æLÏÏÏ†¦¸)
   * DB2 SQL Reference(æLÏÏÏ†¦¸)
   * DB2 Administration Guide: Planning(æLÏÏÏ†¦¸)

In a federated database system, you can access and manipulate LOBs at
remote data sources. Because LOBs can be very large, transferring LOBs from
a remote data source can be time consuming. The DB2 federated database
attempts to minimize transferring LOB data from the data sources, and also
attempts to deliver requested LOB data directly from the data source to the
requesting application without materializing the LOB at DB2.

This section discusses:

   * How DB2 retrieves LOBs
   * How applications can use LOB locators
   * Restrictions on LOBs
   * Mappings between LOB and non-LOB data types
   * Tuning the system

35.5.1.1 How DB2 retrieves LOBs

DB2 federated systems use two mechanisms to retrieve LOBs: LOB streaming
and LOB materialization.

LOB streaming

In LOB streaming, LOB data is retrieved in stages. DB2 uses LOB streaming
for data in result sets of queries that are completely pushed down. For
example, consider the following query:

SELECT empname, picture FROM orc_emp_table WHERE empno = '01192345'

where picture represents a LOB column and orc_emp_table represents a
nickname referencing an Oracle table containing employee data. The DB2
query processor marks the picture column for streaming if it decides to run
the entire query at the Oracle data source. At execution time, if DB2 notes
that a LOB is marked for streaming, it retrieves the LOB in stages from the
data source. DB2 then transfers the data to the application memory space.

LOB materialization

In LOB materialization, the remote LOB data is retrieved by DB2 and stored
locally at the federated server. DB2 uses LOB materialization when:

   * The LOB column cannot be deferred or streamed.
   * A function must be applied to a LOB column locally, before the data is
     transferred. This happens when DB2 compensates for functions not
     available at a remote data source. For example, Microsoft SQL Server
     does not provide a SUBSTR function for LOB columns. To compensate, DB2
     materializes the LOB column locally and applies the DB2 SUBSTR
     function to the retrieved LOB.

35.5.1.2 How applications can use LOB locators

Applications can request LOB locators for LOBs stored in remote data
sources. A LOB locator is a 4-byte value stored in a host variable that a
program can use to refer to a LOB value (or LOB expression) held in the
database system. Using a LOB locator, a program can manipulate the LOB
value as if the LOB value was stored in a regular host variable. The
difference in using the LOB locator is that there is no need to transport
the LOB value from the server to the application (and possibly back again).
See the DB2 Application Development Guide for additional information about
LOB locators.

DB2 can retrieve LOBs from remote data sources, store them at DB2, and then
issue a LOB locator against the stored LOB. LOB locators are released when:

   * Applications issue "FREE LOCATOR" SQL statements.
   * Applications issue COMMIT statements.
   * DB2 is restarted.

35.5.1.3 Restrictions on LOBs

When using and retrieving LOBs, consider that:

   * DB2 is unable to bind remote LOBs to a file reference variable.
   * LOBs are not supported in pass-through mode.

35.5.1.4 Mappings between LOB and non-LOB data types

There are a few cases in which you can map a DB2 LOB data type to a non-LOB
data type at a data source. When you need to create a mapping between a
column with a DB2 LOB type and its counterpart column at a data source, it
is recommended that you use a LOB data type as a counterpart if at all
possible.

To create a mapping, use the create type mapping DDL statement. For
example:

CREATE TYPE MAPPING my_oracle_lob FROM sysibm.clob TO SERVER TYPE oracle TYPElong

where:

my_oracle_lob
     Is the name of the type mapping.

sysibm.clob
     Is the DB2 CLOB data type.

oracle
     Is the type of server you are connecting to.

long
     Is the Oracle data type counterpart.

35.5.2 Tuning the system

If an application that retrieves remote LOBs returns an error message
indicating there is not enough system resources to process the statement,
increase the value of the application heap size parameter, APPLHEAPSZ, in
the database configuration file. For example:

 DB2 UPDATE DB CFG FOR EMPLOYEE USING APPLHEAPSZ 512

where EMPLOYEE is the name of the database you are tuning and 512 is the
value of the application heap size parameter.
  ------------------------------------------------------------------------

35.6 Part 5. DB2 Programming Considerations

35.6.1 IBM DB2 OLE DB Provider

Installing IBM DB2 Version 7.1 FixPak 1 or later corrects the condition
that caused DB2 to issue the following error:

   Test connection failed because of an error in initializing provider.
   The IBM OLE DB Provider is not available at this time. Please refer to
   the readme file for more information.

For more information on using the IBM OLE DB Provider for DB2, please refer
to http://www.ibm.com/software/data/db2/udb/ad/v71/oledb.html.
  ------------------------------------------------------------------------

35.7 Chapter 20. Programming in C and C++

The following table supplements the information included in chapter 7,
"Stored Procedures", chapter 15, "Writing User-Defined Functions and
Methods", and chapter 20, "Programming in C and C++". The table lists the
supported mappings between SQL data types and C data types for stored
procedures, UDFs, and methods.

35.7.1 C/C++ Types for Stored Procedures, Functions, and Methods

Table 22. SQL Data Types Mapped to C/C++ Declarations
 SQL Column Type       C/C++ Data Type        SQL Column Type Description
 SMALLINT              sqlint16               16-bit signed integer
 (500 or 501)
 INTEGER               sqlint32               32-bit signed integer
 (496 or 497)
 BIGINT                sqlint64               64-bit signed integer
 (492 or 493)
 REAL                  float                  Single-precision floating
 (480 or 481)                                 point
 DOUBLE                double                 Double-precision floating
 (480 or 481)                                 point
 DECIMAL(p,s)          Not supported.         To pass a decimal value,
 (484 or 485)                                 define the parameter to be
                                              of a data type castable from
                                              DECIMAL (for example CHAR or
                                              DOUBLE) and explicitly cast
                                              the argument to this type.
 CHAR(n)               char[n+1] where n is   Fixed-length,
 (452 or 453)          large enough to hold   null-terminated character
                       the data               string

                       1<=n<=254
 CHAR(n) FOR BIT DATA  char[n+1] where n is   Fixed-length character
 (452 or 453)          large enough to hold   string
                       the data

                       1<=n<=254
 VARCHAR(n)            char[n+1] where n is   Null-terminated varying
 (448 or 449) (460 or  large enough to hold   length string
 461)                  the data

                       1<=n<=32 672
 VARCHAR(n) FOR BIT    struct {               Not null-terminated varying
 DATA                    sqluint16 length;    length character string
 (448 or 449)            char[n]
                       }

                       1<=n<=32 672
 LONG VARCHAR          struct {               Not null-terminated varying
 (456 or 457)            sqluint16 length;    length character string
                         char[n]
                       }

                       32 673<=n<=32 700
 CLOB(n)               struct {               Non null-terminated varying
 (408 or 409)            sqluint32 length;    length character string with
                         char data[n];        4-byte string length
                       }                      indicator

                       1<=n<=2 147 483 647
 BLOB(n)               struct {               Non null-terminated varying
 (404 or 405)            sqluint32 length;    binary string with 4-byte
                         char data[n];        string length indicator
                       }

                       1<=n<=2 147 483 647
 DATE                  char[11]               null-terminated character
 (384 or 385)                                 form
 TIME                  char[9]                null-terminated character
 (388 or 389)                                 form
 TIMESTAMP             char[27]               null-terminated character
 (392 or 393)                                 form
 Notes:
      The following data types are only available in the DBCS or EUC
      environment when precompiled with the WCHARTYPE NOCONVERT option.

 GRAPHIC(n)            sqldbchar[n+1] where n Fixed-length,
 (468 or 469)          is large enough to     null-terminated double-byte
                       hold the data          character string

                       1<=n<=127
 VARGRAPHIC(n)         sqldbchar[n+1] where n Not null-terminated,
 (400 or 401)          is large enough to     variable-length double-byte
                       hold the data          character string

                       1<=n<=16 336
 LONG VARGRAPHIC       struct {               Not null-terminated,
 (472 or 473)            sqluint16 length;    variable-length double-byte
                         sqldbchar[n]         character string
                       }

                       16 337<=n<=16 350
 DBCLOB(n)             struct {               Non null-terminated varying
 (412 or 413)            sqluint32 length;    length character string with
                         sqldbchar data[n];   4-byte string length
                       }                      indicator

                       1<=n<=1 073 741 823
  ------------------------------------------------------------------------

35.8 Chapter 21. Programming in Java

35.8.1 Java Method Signature in PARAMETER STYLE JAVA Procedures and
Functions

If specified after the Java method name in the EXTERNAL NAME clause of the
CREATE PROCEDURE or CREATE FUNCTION statement, the Java method signature
must correspond to the default Java type mapping for the signature
specified after the procedure or function name. For example, the default
Java mapping of the SQL type INTEGER is "int", not "java.lang.Integer".

35.8.2 Connecting to the JDBC Applet Server

It is essential that the db2java.zip file used by the Java applet be at the
same FixPak level as the JDBC applet server. Under normal circumstances,
db2java.zip is loaded from the Web Server where the JDBC applet server is
running, as shown in Figure 22 of the book. This ensures a match. If,
however, your configuration has the Java applet loading db2java.zip from a
different location, a mismatch can occur. Prior to FixPak 2, this could
lead to unexpected failures. As of FixPak 2, matching FixPak levels between
the two files is strictly enforced at connection time. If a mismatch is
detected, the connection is rejected, and the client receives one of the
following exceptions:

   * If db2java.zip is at FixPak 2 or later:

        COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver]
        CLI0621E  Unsupported JDBC server configuration.

   * If db2java.zip is prior to FixPak 2:

        COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver]
        CLI0601E  Invalid statement handle or statement is closed.
        SQLSTATE=S1000

If a mismatch occurs, the JDBC applet server logs one of the following
messages in the jdbcerr.log file:

   * If the JDBC applet server is at FixPak 2 or later:

        jdbcFSQLConnect: JDBC Applet Server and client (db2java.zip)
        versions do not match. Unable to proceed with connection., einfo= -111

   * If the JDBC applet server is prior to FixPak 2:

        jdbcServiceConnection(): Invalid Request Received., einfo= 0

  ------------------------------------------------------------------------

35.9 Appendix B. Sample Programs

The following should be added to the "Object Linking and Embedding Samples"
section:

   salarycltvc A Visual C++ DB2 CLI sample that calls the
               Visual Basic stored procedure, salarysrv.

   SALSVADO A sample OLE automation stored procedure (SALSVADO) and a
   SALCLADO client (SALCLADO), implemented in 32-bit Visual Basic and ADO,
            that calculates the median salary in table staff2.

  ------------------------------------------------------------------------

CLI Guide and Reference(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

36.1 Binding Database Utilities Using the Run-Time Client

The Run-Time Client cannot be used to bind the database utilities (import,
export, reorg, the command line processor) and DB2 CLI bind files to each
database before they can be used with that database. You must use the DB2
Administration Client or the DB2 Application Development Client instead.

You must bind these database utilities and DB2 CLI bind files to each
database before they can be used with that database. In a network
environment, if you are using multiple clients that run on different
operating systems, or are at different versions or service levels of DB2,
you must bind the utilities once for each operating system and DB2-version
combination.
  ------------------------------------------------------------------------

36.2 Using Static SQL in CLI Applications

For more information on using static SQL in CLI applications, see the Web
page at: http://www.ibm.com/software/data/db2/udb/staticcli/
  ------------------------------------------------------------------------

36.3 Limitations of JDBC/ODBC/CLI Static Profiling

JDBC/ODBC/CLI static profiling currently targets straightforward
applications. It is not meant for complex applications with many functional
components and complex program logic during execution.

An SQL statement must have successfully executed for it to be captured in a
profiling session. In a statement matching session, unmatched dynamic
statements will continue to execute as dynamic JDBC/ODBC/CLI calls.

An SQL statement must be identical character-by-character to the one that
was captured and bound to be a valid candidate for statement matching.
Spaces are significant: for example, "COL = 1" is considered different than
"COL=1". Use parameter markers in place of literals to improve match hits.

When executing an application with pre-bound static SQL statements, dynamic
registers that control the dynamic statement behavior will have no effect
on the statements that are converted to static.

If an application issues DDL statements for objects that are referenced in
subsequent DML statements, you will find all of these statements in the
capture file. The JDBC/ODBC/CLI Static Profiling Bind Tool will attempt to
bind them. The bind attempt will be successful with DBMSs that support the
VALIDATE(RUN) bind option, but it fail with ones that do not. In this case,
the application should not use Static Profiling.

The Database Administrator may edit the capture file to add, change, or
remove SQL statements, based on application-specific requirements.
  ------------------------------------------------------------------------

36.4 ADT Transforms

The following supercedes existing information in the book.

   * There is a new descriptor type (smallint)
     SQL_DESC_USER_DEFINED_TYPE_CODE, with values:

        SQL_TYPE_BASE 0      (this is not a USER_DEFINED_TYPE)
        SQL_TYPE_DISTINCT 1
        SQL_TYPE_STRUCTURED  2
        This value can be queried with either SQLColAttribute
          or SQLGetDescField (IRD only).

        The following attributes are added to obtain the actual type names:
             SQL_DESC_REFERENCE_TYPE
             SQL_DESC_STRUCTURED_TYPE
             SQL_DESC_USER_TYPE
        The above values can be queried using SQLColAttribute
          or SQLGetDescField (IRD only).

   * Add SQL_DESC_BASE_TYPE in case the application needs it. For example,
     the application may not recognize the structured type, but intends to
     fetch or insert it, and let other code deal with the details.
   * Add a new connection attribute called SQL_ATTR_TRANSFORM_GROUP to
     allow an application to set the transform group (rather than use the
     SQL "SET CURRENT DEFAULT TRANSFORM GROUP" statement).
   * Add a new statement/connection attribute called
     SQL_ATTR_RETURN_USER_DEFINED_TYPES that can be set or queried using
     SQLSetConnectAttr, which causes CLI to return the value
     SQL_DESC_USER_DEFINED_TYPE_CODE as a valid SQL type. This attribute is
     required before using any of the transforms.
        o By default, the attribute is off, and causes the base type
          information to be returned as the SQL type.
        o When enabled, SQL_DESC_USER_DEFINED_TYPE_CODE will be returned as
          the SQL_TYPE. The application is expected to check for
          SQL_DESC_USER_DEFINED_TYPE_CODE, and then to retrieve the
          appropriate type name. This will be available to SQLColAttribute,
          SQLDescribeCol, and SQLGetDescField.
   * The SQLBindParameter does not give an error when you bind
     SQL_C_DEFAULT, because there is no code to allow SQLBindParameter to
     specify the type SQL_USER_DEFINED_TYPE. The standard default C types
     will be used, based on the base SQL type flowed to the server. For
     example:

        sqlrc = SQLBindParameter (hstmt, 2, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_VARCHAR, 30,
                                                       0, &c2, 30, NULL);

  ------------------------------------------------------------------------

36.5 Chapter 3. Using Advanced Features

36.5.1 Writing Multi-Threaded Applications

The following should be added to the end of the "Multi-Threaded Mixed
Applications" section:

Notes:
     It is recommended that you do not use the default stack size, but
     instead increase the stack size to at least 256 000. DB2 requires a
     minimum stack size of 256 000 when calling a DB2 function. You must
     ensure therefore, that you allocate a total stack size that is large
     enough for both your application and the minimum requirements for a
     DB2 function call.

36.5.2 Scrollable Cursors

The following information should be added to the "Scrollable Cursors"
section:

36.5.2.1 Server-side Scrollable Cursor Support for OS/390

The UDB client for the Unix, Windows, and OS/2 platforms supports updatable
server-side scrollable cursors when run against OS/390 Version 7 databases.
To access an OS/390 scrollable cursor on a three-tier environment, the
client and the gateway must be running DB2 UDB Version 7.1, FixPak 3 or
later.

There are two application enablement interfaces that can access scrollable
cursors: ODBC and JDBC. The JDBC interface can only access static
scrollable cursors, while the ODBC interface can access static and
keyset-driven server-side scrollable cursors.

Cursor Attributes

The table below lists the default attributes for OS/390 Version 7 cursors
in ODBC.

Table 23. Default attributes for OS/390 cursors in ODBC
 Cursor Type    Cursor        Cursor         Cursor        Cursor
                Sensitivity   Updatable      Concurrency   Scrollable
 forward-onlya  unspecified   non-updatable  read-only     non-scrollable
                                             concurrency
 static         insensitive   non-updatable  read-only     scrollable
                                             concurrency
 keyset-driven  sensitive     updatable      values        scrollable
                                             concurrency
      a Forward-only is the default behavior for a scrollable cursor
      without the FOR UPDATE clause. Specifying FOR UPDATE on a
      forward-only cursor creates an updatable, lock concurrency,
      non-scrollable cursor.

Supported Fetch Orientations

All ODBC fetch orientations are supported via the SQLFetchScroll or
SQLExtendedFetch interfaces.

Updating the Keyset-Driven Cursor

A keyset-driven cursor is an updatable cursor. The CLI driver appends the
FOR UPDATE clause to the query, except when the query is issued as a SELECT
... FOR READ ONLY query, or if the FOR UPDATE clause already exists. The
keyset-driven cursor implemented in DB2 for OS/390 is a values concurrency
cursor. A values concurrency cursor results in optimistic locking, where
locks are not held until an update or delete is attempted. When an update
or delete is attempted, the database server compares the previous values
the application retrieved to the current values in the underlying table. If
the values match, then the update or delete succeeds. If the values do not
match, then the operation fails. If failure occurs, the application should
query the values again and re-issue the update or delete if it is still
applicable.

An application can update a keyset-driven cursor in two ways:

   * Issue an UPDATE WHERE CURRENT OF "<cursor name>" or DELETE WHERE
     CURRENT OF "<cursor name>" using SQLPrepare() with SQLExecute() or
     SQLExecDirect().
   * Use SQLSetPos() or SQLBulkOperations() to update, delete, or add a row
     to the result set.
     Notes:
          Rows added to a result set via SQLSetPos() or SQLBulkOperations()
          are inserted into the table on the server, but are not added to
          the server's result set. Therefore, these rows are not updatable
          nor are they sensitive to changes made by other transactions. The
          inserted rows will appear, however, to be part of the result set,
          since they are cached on the client. Any triggers that apply to
          the inserted rows will appear to the application as if they have
          not been applied. To make the inserted rows updatable, sensitive,
          and to see the result of applicable triggers, the application
          must issue the query again to regenerate the result set.

Troubleshooting for Applications Created Before Scrollable Cursor Support

Since scrollable cursor support is new, some ODBC applications that were
working with previous releases of UDB for OS/390 or UDB for Unix, Windows,
and OS/2 may encounter behavioral or performance changes. This occurs
because before scrollable cursors were supported, applications that
requested a scrollable cursor would receive a forward-only cursor. To
restore an application's previous behavior before scrollable cursor
support, set the following configuration keywords in the db2cli.ini file:

Table 24. Configuration keyword values restoring application behavior before
scrollable cursor support
 Configuration Keyword Setting      Description
 PATCH2=6                           Returns a message that scrollable
                                    cursors (both keyset-driven and
                                    static) are not supported. CLI
                                    automatically downgrades any request
                                    for a scrollable cursor to a
                                    forward-only cursor.
 DisableKeysetCursor=1              Disables both the server-side and
                                    client-side keyset-driven scrollable
                                    cursors. This can be used to force the
                                    CLI driver to give the application a
                                    static cursor when a keyset-driven
                                    cursor is requested.
 UseServerKeysetCursor=0            Disables the server-side keyset-driven
                                    cursor for applications that are using
                                    the client-side keyset-driven cursor
                                    library to simulate a keyset-driven
                                    cursor. Only use this option when
                                    problems are encountered with the
                                    server-side keyset-driven cursor,
                                    since the client-side cursor incurs a
                                    large amount of overhead and will
                                    generally have poorer performance than
                                    a server-side cursor.

36.5.3 Using Compound SQL

The following note is missing from the book:

   Any SQL statement that can be prepared dynamically, other than a query,
   can be executed as a statement inside a compound statement.

   Note: Inside Atomic Compound SQL, savepoint, release savepoint, and
   rollback to savepoint SQL statements are also disallowed. Conversely,
   Atomic Compound SQL is disallowed in savepoint.

36.5.4 Using Stored Procedures

36.5.4.1 Writing a Stored Procedure in CLI

Following is an undocumented limitation on CLI stored procedures:

   If you are making calls to multiple CLI stored procedures,
   the application must close the open cursors from one stored procedure
   before calling the next stored procedure. More specifically, the first
   set of open cursors must be closed before the next stored procedure
   tries to open a cursor.

36.5.4.2 CLI Stored Procedures and Autobinding

The following supplements information in the book:

The CLI/ODBC driver will normally autobind the CLI packages the first time
a CLI/ODBC application executes SQL against the database, provided the user
has the appropriate privilege or authorization. Autobinding of the CLI
packages cannot be performed from within a stored procedure, and therefore
will not take place if the very first thing an application does is call a
CLI stored procedure. Before running a CLI application that calls a CLI
stored procedure against a new DB2 database, you must bind the CLI packages
once with this command:

UNIX

     db2 bind <BNDPATH>/@db2cli.lst blocking all

Windows and OS/2

     db2bind "%DB2PATH%\bnd\@db2cli.lst" blocking

The recommended approach is to always bind these packages at the time the
database is created to avoid autobind at runtime. Autobind can fail if the
user does not have privilege, or if another application tries to autobind
at the same time.
  ------------------------------------------------------------------------

36.6 Chapter 4. Configuring CLI/ODBC and Running Sample Applications

36.6.1 Configuration Keywords

Disregard the last paragraph in the CURRENTFUNCTIONPATH keyword. The
correct information is as follows:

This keyword is used as part of the process for resolving unqualified
function and stored procedure references that may have been defined in a
schema name other than the current user's schema. The order of the schema
names determines the order in which the function and procedure names will
be resolved. For more information on function and procedure resolution,
refer to the SQL Reference.
  ------------------------------------------------------------------------

36.7 Chapter 5. DB2 CLI Functions

36.7.1 SQLBindFileToParam - Bind LOB File Reference to LOB Parameter

The last parameter - IndicatorValue - in the SQLBindFileToParam() CLI
function is currently documented as "output (deferred)". It should be
"input (deferred)".

36.7.2 SQLNextResult - Associate Next Result Set with Another Statement
Handle

The following text should be added to Chapter 5, "DB2 CLI Functions":

36.7.2.1 Purpose

Specification: DB2 CLI 7.x

36.7.2.2 Syntax

SQLRETURN   SQLNextResult       (SQLHSTMT       StatementHandle1
                                                         SQLHSTMT       StatementHandle2);

36.7.2.3 Function Arguments

Table 25. SQLNextResult Arguments
 Data Type    Argument           Use      Description
 SQLHSTMT     StatementHandle    input    Statement handle.
 SQLHSTMT     StatementHandle    input    Statement handle.

36.7.2.4 Usage

A stored procedure returns multiple result sets by leaving one or more
cursors open after exiting. The first result set is always accessed by
using the statement handle that called the stored procedure. If multiple
result sets are returned, either SQLMoreResults() or SQLNextResult() can be
used to describe and fetch the result set.

SQLMoreResults() is used to close the cursor for the first result set and
allow the next result set to be processed, whereas SQLNextResult() moves
the next result set to StatementHandle2, without closing the cursor on
StatementHandle1. Both functions return SQL_NO_DATA_FOUND if there are no
result sets to be fetched.

Using SQLNextResult() allows result sets to be processed in any order once
they have been transferred to other statement handles. Mixed calls to
SQLMoreResults() and SQLNextResult() are allowed until there are no more
cursors (open result sets) on StatementHandle1.

When SQLNextResult() returns SQL_SUCCESS, the next result set is no longer
associated with StatementHandle1. Instead, the next result set is
associated with StatementHandle2, as if a call to SQLExecDirect() had just
successfully executed a query on StatementHandle2. The cursor, therefore,
can be described using SQLNumResultSets(), SQLDescribeCol(), or
SQLColAttribute().

After SQLNextResult() has been called, the result set now associated with
StatementHandle2 is removed from the chain of remaining result sets and
cannot be used again in either SQLNextResult() or SQLMoreResults(). This
means that for 'n' result sets, SQLNextResult() can be called successfully
at most 'n-1' times.

If SQLFreeStmt() is called with the SQL_CLOSE option, or SQLFreeHandle() is
called with HandleType set to SQL_HANDLE_STMT, all pending result sets on
this statement handle are discarded.

SQLNextResult() returns SQL_ERROR if StatementHandle2 has an open cursor or
StatementHandle1 and StatementHandle2 are not on the same connection. If
any errors or warnings are returned, SQLError() must always be called on
StatementHandle1.

Notes:
     SQLMoreResults() also works with a parameterized query with an array
     of input parameter values specified with SQLParamOptions() and
     SQLBindParameter(). SQLNextResult(), however, does not support this.

36.7.2.5 Return Codes

   * SQL_SUCCESS
   * SQL_SUCCESS_WITH_INFO
   * SQL_STILL_EXECUTING
   * SQL_ERROR
   * SQL_INVALID_HANDLE
   * SQL_NO_DATA_FOUND

36.7.2.6 Diagnostics

Table 26. SQLNextResult SQLSTATEs
 SQLSTATE  Description           Explanation
 40003     Communication Link    The communication link between the
 08S01     failure.              application and data source failed before
                                 the function completed.
 58004     Unexpected system     Unrecoverable system error.
           failure.
 HY001     Memory allocation     DB2 CLI is unable to allocate the memory
           failure.              required to support execution or
                                 completion of the function.
 HY010     Function sequence     The function was called while in a
           error.                data-at-execute (SQLParamData(),
                                 SQLPutData()) operation.

                                 StatementHandle2 has an open cursor
                                 associated with it.

                                 The function was called while within a
                                 BEGIN COMPOUND and END COMPOUND SQL
                                 operation.
 HY013     Unexpected memory     DB2 CLI was unable to access the memory
           handling error.       required to support execution or
                                 completion of the function.
 HYT00     Time-out expired.     The time-out period expired before the
                                 data source returned the result set.
                                 Time-outs are only supported on
                                 non-multitasking systems such as Windows
                                 3.1 and Macintosh System 7. The time-out
                                 period can be set using the
                                 SQL_ATTR_QUERY_TIMEOUT attribute for
                                 SQLSetConnectAttr().

36.7.2.7 Restrictions

Only SQLMoreResults() can be used for parameterized queries.

36.7.2.8 References

   * "SQLMoreResults - Determine If There Are More Result Sets" on page 535
   * "Returning Result Sets from Stored Procedures" on page 120

  ------------------------------------------------------------------------

36.8 Appendix D. Extended Scalar Functions

36.8.1 Date and Time Functions

The following functions are missing from the Date and Time Functions
section of Appendix D "Extended Scalar Functions":

DAYOFWEEK_ISO( date_exp )
     Returns the day of the week in date_exp as an integer value in the
     range 1-7, where 1 represents Monday. Note the difference between this
     function and the DAYOFWEEK() function, where 1 represents Sunday.

WEEK_ISO( date_exp )
     Returns the week of the year in date_exp as an integer value in the
     range of 1-53. Week 1 is defined as the first week of the year to
     contain a Thursday. Therefore, Week1 is equivalent to the first week
     that contains Jan 4, since Monday is considered to be the first day of
     the week.

     Note that WEEK_ISO() differs from the current definition of WEEK(),
     which returns a value up to 54. For the WEEK() function, Week 1 is the
     week containing the first Saturday. This is equivalent to the week
     containing Jan. 1, even if the week contains only one day.

DAYOFWEEK_ISO() and WEEK_ISO() are automatically available in a database
created in Version 7. If a database was created prior to Version 7, these
functions may not be available. To make DAYOFWEEK_ISO() and WEEK_ISO()
functions available in such a database, use the db2updb system command. For
more information about db2updb, see the "Command Reference" section in
these Release Notes.
  ------------------------------------------------------------------------

36.9 Appendix K. Using the DB2 CLI/ODBC/JDBC Trace Facility

The sections within this appendix have been updated. See the "Traces"
chapter in the Troubleshooting Guide for the most up-to-date information on
this trace facility.
  ------------------------------------------------------------------------

øT©õø¥ÝãÏƒ¾U

  ------------------------------------------------------------------------

37.1 ù£ñoøT©õ¯P SQLSTATE ¯­¸£

¸R¾OÝ‘üBýzóû¦§¾i¾×¯­¸£ªO¾]õtøT©õ¯P SQLSTATE ðÔ¦§ús¦§ (¸×õ¢ús¦§) ¯­¸£­A ÝbøT
©õø¥ÝãÏƒ¾UÏÏ¸|¾¬ïœù¥­C

ðYðnñq¸R¾OÝ‘üBýzóûÆ¾šøT©õ­A«ÑÝbõ@ú~ùtý×¦§¸R¾Oïœ¾šÏU¨‚ÏJÏUÝC®¾O­G

db2 "? XXXnnnnn"

ù„ÏÏ XXX ¾N¦¡øT©õ¦§Ýrð§­FÝà nnnnn ¾N¦¡øT©õ«X­C

ùãÝp­Gdb2 "? SQL30081" ú|Æ¾šÇ”¸¢ SQL30081 øT©õ¦§¯­¸£­C

ðYðnñq¸R¾OÝ‘üBýzóûÆ¾š SQLSTATE Ï†Ýr­A«ÑÝbõ@ú~ùtý×¦§¸R¾Oïœ¾šÏU¨‚ÏJÏUÝC®
¾O­G

db2 "? XXXXX"

ù„ÏÏ XXXXX ¾N¦¡ SQLSTATE ðÔ­C

ùãÝp­Gdb2 "? 428F1" ú|Æ¾š SQLSTATE 428F1 ¦§Ï†Ýr­C
  ------------------------------------------------------------------------

37.2 Ýb DB2 Connect šõ¢¦§ SQLCODE ð®úsû‹ªM

DB2 Connect ¦§ûwü] SQLCODE ð®úsû‹ªMÝb¦¸¾¯ 7.2 ÏÏÏwšõ¢­Cú¡¾Dûq÷œ÷ˆ©’©wô€Ý^
SQLCODE ðÔ -567­A DB2 Connect ú|Ýbô€Ý^ SQLCODE ðÔù DB2 ñqŽíî÷Ïõ®eð®úsû‹ªM
SQLCODE ðÔù -551­C
  ------------------------------------------------------------------------

37.3 ús¦§¯Pšõ¢¦§øT©õ

¾HÏUÝC¾š¦§ªO DB2 øT©õø¥ÝãÏƒ¾U ¦¸¾¯ 7.1 ¾H® šõ¢¦§øT©õ«X­C ÝbùØ¾× DB2 ©ðYñz
ñæÝªùüoù€øT©õ¦§ù„ÏÏÏ@®h­A ñzñNú|ñæÝªùõ¢¾¨¦§úsøT©õ­FÝìªO­AüoøT©õú|æL¦kû‹·ü
ùøT©õø¥ÝãÏƒ¾UÏÏ¦§÷ˆøT­C

37.3.1 ¸I¾s¬hÝ÷Ïôðñ (CLI) øT©õ

     CLI0645E

     CLI0646E

     CLI0647E

37.3.2 DB2 øT©õ

     DB21086I

     DB210060E

     DB210061E

     DB210062E

     DB210113E

     DB210114E

     DB210115E

     DB210116E

     DB210117E

     DB210118E

     DB210120E

     DB210121E

     DB210200I

     DB210201I

37.3.3 DBI øT©õ

     DBI1172E

     DBI1793W

     DBI1794E

     DBI1795E

     DBI1796W

     DBI1797I

37.3.4 ÷ˆ©’ðš·xÏÏÏá (DWC) øT©õ

     DWC0000I

     DWC03504E

     DWC08900E

     DWC08901E

     DWC08902E

     DWC08903E

     DWC08904E

     DWC08907C

     DWC08908C

     DWC08909C

     DWC08910E

     DWC08911E

     DWC08912E

     DWC08913E

     DWC08914E

     DWC08915E

     DWC08917E

     DWC08919I

     DWC08930E

     DWC08931E

     DWC08932E

     DWC08933E

     DWC08934E

     DWC08935E

     DWC08936W

     DWC08937I

     DWC08938I

     DWC08939I

     DWC08940I

     DWC08941I

     DWC08960I

     DWC08961I

     DWC08962I

     DWC08963I

     DWC08964I

     DWC08965I

     DWC08966E

     DWC08967E

     DWC08968E

     DWC13239E

     DWC13300E

     DWC13301E

     DWC13302E

     DWC13304E

     DWC13603E

     DWC13700E

     DWC13701E

     DWC13702E

     DWC13703E

     DWC13705E

     DWC13706E

     DWC13707E

37.3.5 SQL øT©õ

     SQL0017N

     SQL0056N

     SQL0057N

     SQL0058N

     SQL0097N

     SQL0224N

     SQL0225N

     SQL0227N

     SQL0228N

     SQL0231W

     SQL0243N

     SQL0244N

     SQL0270N

     SQL0301N

     SQL0303N

     SQL0336N

     SQL0348N

     SQL0349N

     SQL0357N

     SQL0358N

     SQL0368N

     SQL0408N

     SQL0423N

     SQL0590N

     SQL0670N

     SQL0845N

     SQL0846N

     SQL1179W

     SQL1186N

     SQL1550N

     SQL1551N

     SQL1552N

     SQL1553N

     SQL1704N

     SQL2077W

     SQL2078N

     SQL2417N

     SQL2426N

     SQL2571N

     SQL2572N

     SQL2573N

     SQL2574N

     SQL2575N

     SQL2576N

     SQL4942N

     SQL5012N

     SQL6583N

     SQL20005N

     SQL20117N

     SQL20121N

     SQL20133N

     SQL20134N

     SQL20135N

     SQL20143N

     SQL20144N

     SQL20145N

     SQL20146N

     SQL20147N

     SQL20148N

     SQL20153N

     SQL21000N

  ------------------------------------------------------------------------

37.4 õ¢¾¨ SQLSTATES

¦¡ 27.
 42630     SQLSTATE ¸× SQLCODE š¬’ÝbÝû·“ûã¸w÷qªOæL©Ž¦§­C
 42631     ¦¡¾šÝ­¾ýôú®¸w¸¢ SQL ù‡¬’¦§ RETURN üîðzÝ­ÏÏ­C
 42632     Ýb SQL ù‡¬’¸×ÏŠ¦kÏÏ¾ýôúðnÝü RETURN üîðzÝ­­C
 428F2     Ýb SQL æ{õ€¦§ RETURN üîðzÝ­ÏÏ¾ýôúðnÝüóÆ¬’¦¡¾šÝ­­C
 560B7     û‹ÝhÝC INSERT ùà¯­­AùCÏ@ÝC¦§ NEXTVAL ôôõ€¦¡¾šÝ­¾×¦k¾ýôúªêÝP­C
  ------------------------------------------------------------------------

SQL Reference(æLÏÏÏ†¦¸)

  ------------------------------------------------------------------------

38.1 SQL Reference is Provided in One PDF File

The "Using the DB2 Library" appendix in each book indicates that the SQL
Reference is available in PDF format as two separate volumes. This is
incorrect.

Although the printed book appears in two volumes, and the two corresponding
form numbers are correct, there is only one PDF file, and it contains both
volumes. The PDF file name is db2s0x70.
  ------------------------------------------------------------------------

38.2 Chapter 3. Language Elements

38.2.1 Naming Conventions and Implicit Object Name Qualifications

Add the following note to this section in Chapter 3:

   The following names, when used in the context of SQL Procedures,
   are restricted to the characters allowed in an
   ordinary identifier, even if the names are delimited:

   - condition-name
   - label
   - parameter-name
   - procedure-name
   - SQL-variable-name
   - statement-name

38.2.2 DATALINK Assignments

A paragraph in this section has been changed to the following:

   Note that the size of a URL parameter or function result is the same
   on both input or output and is bound by the length of the DATALINK column.
   However, in some cases the URL value returned has an access token attached.
   In situations where this is possible, the output location must have
   sufficient storage space for the access token and the length of
   the DATALINK column. Hence, the actual length of the comment and
   URL in its fully expanded form provided on input should be restricted
   to accommodate the output storage space. If the restricted length is
   exceeded, this error is raised.

38.2.3 Expressions

38.2.3.1 Syntax Diagram

The syntax diagram has changed:

   .-operator------------------------------.
   V                                       |
>>----+-----+---+-function--------------+--+-------------------><
      +- + -+   +-(expression)----------+
      '- - -'   +-constant--------------+
                +-column-name-----------+
                +-host-variable---------+
                +-special-register------+
                +-(scalar-fullselect)---+
                +-labeled-duration------+
                +-case-expression-------+
                +-cast-specification----+
                +-dereference-operation-+
                +-OLAP-function---------+
                +-method-invocation-----+
                +-subtype-treatment-----+
                '-sequence-reference----'

operator

             (1)
|---+-CONCAT------+---------------------------------------------|
    +- / ---------+
    +- * ---------+
    +- + ---------+
    '- - ---------'


Notes:

  1. || may be used as a synonym for CONCAT.

38.2.3.2 OLAP Functions

The following represents a correction to the "OLAP Functions" section under
"Expressions" in Chapter 3.

aggregation-function

|--column-function--OVER---(--+------------------------------+-->
                              '-| window-partition-clause |--'

>----+--------------------------------------------------------------------+>
     '-| window-order-clause |--+--------------------------------------+--'
                                '-| window-aggregation-group-clause |--'

>---------------------------------------------------------------|

window-order-clause

              .-,-------------------------------------------.
              V                       .-| asc option |---.  |
|---ORDER BY-----sort-key-expression--+------------------+--+---|
                                      '-| desc option |--'

asc option

         .-NULLS LAST--.
|---ASC--+-------------+----------------------------------------|
         '-NULLS FIRST-'

desc option

          .-NULLS FIRST--.
|---DESC--+--------------+--------------------------------------|
          '-NULLS LAST---'

window-aggregation-group-clause

|---+-ROWS--+---+-| group-start |---+---------------------------|
    '-RANGE-'   +-| group-between |-+
                '-| group-end |-----'

group-end

|---+-UNBOUNDED FOLLOWING-----------+---------------------------|
    '-unsigned-constant--FOLLOWING--'


In the window-order-clause description:

NULLS FIRST
     The window ordering considers null values before all non-null values
     in the sort order.

NULLS LAST
     The window ordering considers null values after all non-null values in
     the sort order.

In the window-aggregation-group-clause description:

window-aggregation-group-clause
     The aggregation group of a row R is a set of rows, defined relative to
     R in the ordering of the rows of R's partition. This clause specifies
     the aggregation group. If this clause is not specified, the default is
     the same as RANGE BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW,
     providing a cumulative aggregation result.

     ROWS
          Indicates the aggregation group is defined by counting rows.

     RANGE
          Indicates the aggregation group is defined by an offset from a
          sort key.

     group-start
          Specifies the starting point for the aggregation group. The
          aggregation group end is the current row. Specification of the
          group-start clause is equivalent to a group-between clause of the
          form "BETWEEN group-start AND CURRENT ROW".

     group-between
          Specifies the aggregation group start and end based on either
          ROWS or RANGE.

     group-end
          Specifies the ending point for the aggregation group. The
          aggregation group start is the current row. Specification of the
          group-end clause is equivalent to a group-between clause of the
          form "BETWEEN CURRENT ROW AND group-end".

     UNBOUNDED PRECEDING
          Includes the entire partition preceding the current row. This can
          be specified with either ROWS or RANGE. Also, this can be
          specified with multiple sort-key-expressions in the
          window-order-clause.

     UNBOUNDED FOLLOWING
          Includes the entire partition following the current row. This can
          be specified with either ROWS or RANGE. Also, this can be
          specified with multiple sort-key-expressions in the
          window-order-clause.

     CURRENT ROW
          Specifies the start or end of the aggregation group based on the
          current row. If ROWS is specified, the current row is the
          aggregation group boundary. If RANGE is specified, the
          aggregation group boundary includes the set of rows with the same
          values for the sort-key-expressions as the current row. This
          clause cannot be specified in group-bound2 if group-bound1
          specifies value FOLLOWING.

     value PRECEDING
          Specifies either the range or number of rows preceding the
          current row. If ROWS is specified, then value is a positive
          integer indicating a number of rows. If RANGE is specified, then
          the data type of value must be comparable to the type of the
          sort-key-expression of the window-order-clause. There can only be
          one sort-key-expression, and the data type of the
          sort-key-expression must allow subtraction. This clause cannot be
          specified in group-bound2 if group-bound1 is CURRENT ROW or value
          FOLLOWING.

     value FOLLOWING
          Specifies either the range or number of rows following the
          current row. If ROWS is specified, then value is a positive
          integer indicating a number of rows. If RANGE is specified, then
          the data type of value must be comparable to the type of the
          sort-key-expression of the window-order-clause. There can only be
          one sort-key-expression, and the data type of the
          sort-key-expression must allow addition.

38.2.3.3 Sequence Reference

The following information should be added to the end of the Expressions
section (after "Subtype Treatment").

sequence-reference

|--+-| nextval-expression |-+-----------------------------------|
   '-| prevval-expression |-'

nextval-expression

|---NEXTVAL FOR--sequence-name----------------------------------|

prevval-expression

|---PREVVAL FOR--sequence-name----------------------------------|


NEXTVAL FOR sequence-name
     A NEXTVAL expression returns the next value for the sequence specified
     by sequence-name.

PREVVAL FOR sequence-name

     A PREVVAL expression returns the most recently generated value for the
     specified sequence for a previous statement within the current
     session. This value can be repeatedly referenced using PREVVAL
     expressions specifying the name of the sequence. There may be multiple
     instances of PREVVAL expressions specifying the same sequence name
     within a single statement and they all return the same value.

     A PREVVAL expression can only be used if a NEXTVAL expression
     specifying the same sequence name has already been referenced in the
     current user session (in the current or a previous transaction)
     (SQLSTATE 51035).

Notes:
        o A new sequence number is generated when a NEXTVAL expression
          specifies the name of the sequence. However, if there are
          multiple instances of a NEXTVAL expression specifying the same
          sequence name within a query, the counter for the sequence is
          incremented only once for each row of the result.
        o The most recently generated value for a sequence can be
          repeatedly referenced using a PREVVAL expression specifying the
          name of the sequence. There may be multiple instances of a
          PREVVAL expression specifying the same sequence name within a
          single statement.
        o The same sequence number can be used as a unique key value in two
          separate tables by referencing the sequence number with a NEXTVAL
          expression for the first row (this generates the sequence value),
          and a PREVVAL expression for the other rows (this instance of
          PREVVAL refers to the sequence value generated by the NEXTVAL
          expression in the previous statement), as shown below:

             INSERT INTO order(orderno, custno)
                VALUES (NEXTVAL FOR order_seq, 123456);

             INSERT INTO line_item  (orderno, partno, quantity)
                VALUES (PREVVAL FOR order_seq, 987654, 1);

        o Examples of where NEXTVAL and PREVVAL expressions can be
          specified are:
             + select-statement or SELECT INTO statement: within the
               select-clause as long as the statement does not contain a
               DISTINCT keyword, a GROUP BY clause, an ORDER BY clause, a
               UNION keyword, an INTERSECT keyword, or EXCEPT keyword
             + INSERT statement: within a VALUES clause
             + INSERT statement: within the select-clause of the fullselect
             + UPDATE statement: within the select-clause of the fullselect
               of an expression in the SET clause (either searched or
               positioned UPDATE statement)
             + VALUES INTO statement: within the select-clause of the
               fullselect of an expression
        o Examples of where NEXTVAL and PREVVAL expressions cannot be
          specified (SQLSTATE 428F9) are:
             + join condition of a full outer join
             + DEFAULT value for a column in a CREATE TABLE or ALTER TABLE
               statement
             + generated column definition in a CREATE TABLE or ALTER TABLE
               statement
             + condition of a CHECK constraint
             + CREATE TRIGGER statement
             + CREATE VIEW statement
             + CREATE METHOD statement
             + CREATE FUNCTION statement.
        o In addition, a NEXTVAL expression cannot be specified (SQLSTATE
          428F9) in :
             + CASE expression
             + parameter list of an aggregate function
             + subquery
             + SELECT statement that contains a DISTINCT operator
             + join condition of join
             + GROUP BY clause of a SELECT statement
             + SELECT statement that is combined with another SELECT
               statement using the UNION, INTERSECT, or EXCEPT set operator
             + nested table expression
             + parameter list of a table function
             + WHERE clause of a SELECT, DELETE, or UPDATE statement
             + ORDER BY clause
             + parameter list of a CALL statement.
        o When a value is generated for a sequence, that value is consumed,
          and the next time that a value is needed, a new value will be
          generated. This is true even when the statement containing the
          NEXTVAL expression fails.
        o If an INSERT statement includes a NEXTVAL expression in the
          VALUES list for the column, and if some error occurs at some
          point during the execution of the INSERT (it could be a problem
          in generating the next sequence value, or a problem with the
          value for another column), then an insertion failure occurs, and
          the value generated for the sequence is considered to be
          consumed. In some cases, reissuing the same INSERT statement
          might lead to success.

          For example, consider an error that is the result of the
          existence of a unique index for the column for which NEXTVAL was
          used and the sequence value generated already exists in the
          index. It is possible that the next value generated for the
          sequence is a value that does not exist in the index and so the
          subsequent INSERT would succeed.
        o If in generating a value for a sequence, the maximum value for
          the sequence is exceeded (or the minimum value for a descending
          sequence) and cycles are not permitted, then an error occurs
          (SQLSTATE 23522). In this case, the user could ALTER the sequence
          to extend the range of acceptable values, or enable cycles for
          the sequence, or DROP and CREATE a new sequence with a different
          data type that has a larger range of values.

          For example, a sequence may have been defined with a data type of
          SMALLINT, and eventually the sequence runs out of assignable
          values. To redefine the sequence as INTEGER, you would need to
          drop and recreate the sequence with the new definition.
        o A reference to PREVVAL in a select statement of a cursor refers
          to a value that was generated for the specified sequence prior to
          the opening of the cursor. However, closing the cursor can affect
          the values returned by PREVVAL for the specified sequence in
          subsequent statements, or even for the same statement in the
          event that the cursor is reopened. This would be the case when
          the select statement of the cursor included a reference to
          NEXTVAL for the same sequence name.

Examples:

These examples assume that there is a table called "order" and that a
sequence called "order_seq" is created as follows:

CREATE SEQUENCE order_seq
   START WITH 1
   INCREMENT BY 1
   NOMAXVALUE
   NOCYCLE
   CACHE 24

   * Some examples of how to generate an "order_seq" sequence number with a
     NEXTVAL expression for the sequence created above:

     INSERT INTO order(orderno, custno)
        VALUES (NEXTVAL FOR order_seq, 123456);

     or,

     UPDATE order
        SET orderno = NEXTVAL FOR order_seq
        WHERE custno = 123456;

     or,

     VALUES NEXTVAL FOR order_seq INTO :hv_seq;

  ------------------------------------------------------------------------

38.3 Chapter 4. Functions

38.3.1 Enabling the New Functions and Procedures

Version 7 FixPaks deliver new SQL built-in scalar functions. Refer to the
SQL Reference updates for a description of these new functions. The new
functions are not automatically enabled on each database when the database
server code is upgraded to the new service level. To enable these new
functions, the system administrator must issue the command db2updv7,
specifying each database at the server. This command makes an entry in the
database that ensures that database objects created prior to executing this
command use existing function signatures that may match the new function
signatures.

For information on enabling the MQSeries functions (those defined in the
MQDB2 schema), see MQSeries.

38.3.2 Scalar Functions

38.3.2.1 ABS or ABSVAL

>>-+-ABS----+--(expression)------------------------------------><
   '-ABSVAL-'


The schema is SYSIBM.

This function was first available in FixPak 2 of Version 7.1.

Notes:
     The SYSFUN version of the ABS (or ABSVAL) function continues to be
     available.

Returns the absolute value of the argument.

The argument is an expression that returns a value of any built-in numeric
data type.

The result of the function has the same data type and length attribute as
the argument. If the argument can be null or the database is configured
with DFT_SQLMATHWARN set to yes, then the result can be null; if the
argument is null, the result is the null value.

For example:

ABS(-51234)

returns an INTEGER with a value of 51234.

38.3.2.2 DECRYPT_BIN and DECRYPT_CHAR

>>-+-DECRYPT_BIN--+--------------------------------------------->
   '-DECRYPT_CHAR-'

>----(--encrypted-data--+--------------------------------+---)--><
                        '-,--password-string-expression--'


The schema is SYSIBM.

This function was first available in FixPak 3 of Version 7.1.

The DECRYPT_BIN and DECRYPT_CHAR functions return a value that is the
result of decrypting encrypted-data. The password used for decryption is
either the password-string-expression value or the ENCRYPTION PASSWORD
value (as assigned using the SET ENCRYPTION PASSWORD statement). The
DECRYPT_BIN and DECRYPT_CHAR functions can only decrypt values that were
encrypted using the ENCRYPT function (SQLSTATE 428FE).

encrypted-data
     An expression that returns a CHAR FOR BIT DATA or VARCHAR FOR BIT DATA
     value that is a complete, encrypted data string that was encrypted
     using the ENCRYPT function.

password-string-expression
     An expression that returns a CHAR or VARCHAR value with at least 6
     bytes and no more than 127 bytes (SQLSTATE 428FC). This should be the
     same password used to encrypt the data or decryption will result in an
     error (SQLSTATE 428FD). If the value of the password argument is null
     or not provided, the data will be decrypted using the ENCRYPTION
     PASSWORD value, which must have been set for the session (SQLSTATE
     51039).

The result of the DECRYPT_BIN function is VARCHAR FOR BIT DATA. The result
of the DECRYPT_CHAR function is VARCHAR. If the encrypted-data included a
hint, the hint is not returned by the function. The length attribute of the
result is the length attribute of the data type of encrypted-data minus 8
bytes. The actual length of the value returned by the function will match
the length of the original string that was encrypted. If the encrypted-data
includes bytes beyond the encrypted string, these bytes are not returned by
the function. If the first argument can be null, the result can be null; if
the first argument is null, the result is the null value.

If the data is decrypted on a different system using a code page other than
the code page in which the encryption took place, it is possible that
expansion may occur when converting the decrypted value to the database
code page. In such situations, the encrypted-data value should be cast to a
VARCHAR string with a larger number of bytes.

Also see 38.3.2.3, ENCRYPT and 38.3.2.4, GETHINT for additional information
on using this function.

Examples:

Example 1: This example uses the ENCRYPTION PASSWORD value to hold the
encryption password.

   SET ENCRYPTION PASSWORD = 'Ben123';
   INSERT INTO EMP (SSN) VALUES ENCRYPT('289-46-8832');
   SELECT DECRYPT_CHAR(SSN)
      FROM SSN;

The value returned is '289-46-8832'.

Example 2: This example explicitly passes the encryption password.

      SELECT DECRYPT_CHAR(SSN,'Ben123')
      FROM SSN;

The value returned is '289-46-8832'.

38.3.2.3 ENCRYPT

>>-ENCRYPT------------------------------------------------------>

>----(--data-string-expression--+----------------------------------------------------------------+---)->
                                '-,--password-string-expression--+----------------------------+--'
                                                                 '-,--hint-string-expression--'

>--------------------------------------------------------------><


The schema is SYSIBM.

This function was first available in FixPak 3 of Version 7.1.

The ENCRYPT function returns a value that is the result of encrypting
data-string-expression. The password used for encryption is either the
password-string-expression value or the ENCRYPTION PASSWORD value (as
assigned using the SET ENCRYPTION PASSWORD statement).

data-string-expression
     An expression that returns a CHAR or VARCHAR value to be encrypted.
     The length attribute for the data type of data-string-expression is
     limited to 32663 without a hint-string-expression argument and 32631
     when the hint-string-expression argument is specified (SQLSTATE
     42815).

password-string-expression
     An expression that returns a CHAR or VARCHAR value with at least 6
     bytes and no more than 127 bytes (SQLSTATE 428FC). The value
     represents the password used to encrypt the data-string-expression. If
     the value of the password argument is null or not provided, the data
     will be encrypted using the ENCRYPTION PASSWORD value, which must have
     been set for the session (SQLSTATE 51039).

hint-string-expression
     An expression that returns a CHAR or VARCHAR value up to 32 bytes that
     will help data owners remember passwords (for example, 'Ocean' as a
     hint to remember 'Pacific'). If a hint value is given, the hint is
     embedded into the result and can be retrieved using the GETHINT
     function. If this argument is null or not provided, no hint will be
     embedded in the result.

The result data type of the function is VARCHAR FOR BIT DATA.

The length attribute of the result is:

   * When the optional hint parameter is specified, the length attribute of
     the non-encrypted data + 8 bytes + the number of bytes to the next 8
     byte boundary + 32 bytes for the hint length.
   * With no hint parameter, the length attribute of the non-encrypted data
     + 8 bytes + the number of bytes to the next 8 byte boundary.

If the first argument can be null, the result can be null; if the first
argument is null, the result is the null value.

Notice that the encrypted result is longer than the data-string-expression
value. Therefore, when assigning encrypted values, ensure that the target
is declared with sufficient size to contain the entire encrypted value.

Notes:

   * Encryption Algorithm: The internal encryption algorithm used is RC2
     block cipher with padding, the 128-bit secret key is derived from the
     password using a MD2 message digest.
   * Encryption Passwords and Data: It is the user's responsibility to
     perform password management. Once the data is encrypted only the
     password used to encrypt it can be used to decrypt it (SQLSTATE
     428FD). Be careful when using CHAR variables to set password values as
     they may be padded with blanks. The encrypted result may contain null
     terminator and other non-printable characters.
   * Table Column Definition: When defining columns and types to contain
     encrypted data always calculate the length attribute as follows. For
     encrypted data with no hint:

     Maximum length of the non-encrypted data + 8 bytes + the number of
     bytes to the next 8 byte boundary = encrypted data column length.

     For encrypted data with embedded hint :

     Maximum length of the non-encrypted data + 8 bytes + the number of
     bytes to the next 8 byte boundary + 32 bytes for the hint length =
     encrypted data column length.

     Any assignment or cast to a length shorter than the suggested data
     length may result in failed decryption in the future and lost data.
     Blanks are valid encrypted data values that may be truncated when
     stored in a column that is too short.

     Sample Column Length Calculations

     Maximum length of non-encrypted data           6 bytes
     8 bytes                                        8 bytes
     Number of bytes to the next 8 byte boundary    2 bytes
                                                   ---------
     Encrypted data column length                  16 bytes

     Maximum length of non-encrypted data          32 bytes
     8 bytes                                        8 bytes
     Number of bytes to the next 8 byte boundary    8 bytes
                                                   ---------
     Encrypted data column length                  48 bytes

   * Administration of encrypted data: Encrypted data can only be decrypted
     on servers that support the decryption functions that correspond to
     the ENCRYPT function. Hence, replication of columns with encrypted
     data should only be done to servers that support the DECRYPT_BIN or
     DECRYPT_CHAR function.

Also see 38.3.2.2, DECRYPT_BIN and DECRYPT_CHAR and 38.3.2.4, GETHINT for
additional information on using this function.

Examples:

Example 1: This example uses the ENCRYPTION PASSWORD value to hold the
encryption password.

   SET ENCRYPTION PASSWORD = 'Ben123';
   INSERT INTO EMP (SSN) VALUES ENCRYPT('289-46-8832');

Example 2: This example explicitly passes the encryption password.

   INSERT INTO EMP (SSN) VALUES ENCRYPT('289-46-8832','Ben123','');

Example 3: The hint 'Ocean' is stored to help the user remember the
encryption password of 'Pacific'.

   INSERT INTO EMP (SSN) VALUES ENCRYPT('289-46-8832','Pacific','Ocean');


38.3.2.4 GETHINT

>>-GETHINT--(--encrypted-data--)-------------------------------><


The schema is SYSIBM.

This function was first available in FixPak 3 of Version 7.1.

The GETHINT function will return the password hint if one is found in the
encrypted-data. A password hint is a phrase that will help data owners
remember passwords (For example, 'Ocean' as a hint to remember 'Pacific').

encrypted-data

     An expression that returns a CHAR FOR BIT DATA or VARCHAR FOR BIT DATA
     value that is a complete, encrypted data string that was encrypted
     using the ENCRYPT function (SQLSTATE 428FE).

The result of the function is VARCHAR(32). The result can be null; if the
hint parameter was not added to the encrypted-data by the ENCRYPT function
or the first argument is null, the result is the null value.

Also see 38.3.2.2, DECRYPT_BIN and DECRYPT_CHAR and 38.3.2.3, ENCRYPT for
additional information on using this function.

Example:

In this example the hint 'Ocean' is stored to help the user remember the
encryption password 'Pacific'.

   INSERT INTO EMP (SSN) VALUES ENCRYPT('289-46-8832', 'Pacific','Ocean');
   SELECT GETHINT(SSN)
      FROM EMP;

The value returned is 'Ocean'.

38.3.2.5 IDENTITY_VAL_LOCAL

>>-IDENTITY_VAL_LOCAL--(--)------------------------------------><


The schema is SYSIBM.

This procedure was first available in FixPak 3 of Version 7.1.

The IDENTITY_VAL_LOCAL function is a non-deterministic function that
returns the most recently assigned value for an identity column, where the
assignment occurred as a result of a single row INSERT statement using a
VALUES clause. The function has no input parameters.

The result is a DECIMAL(31,0), regardless of the actual data type of the
corresponding identity column.

The value returned by the function is the value assigned to the identity
column of the table identified in the most recent single row INSERT
statement. The INSERT statement must be made using a VALUES clause on a
table containing an identity column. Also, the INSERT statement must be
issued at the same level 1 (that is, the value is available locally at the
level it was assigned, until it is replaced by the next assigned value).

The assigned value is either a value supplied by the user (if the identity
column is defined as GENERATED BY DEFAULT), or an identity value generated
by DB2.

The function returns a null value in the following situations:

   * When a single row INSERT statement with a VALUES clause has not been
     issued at the current processing level for a table containing an
     identity column.
   * When a COMMIT or ROLLBACK of a unit of work has occurred since the
     most recent INSERT statement that assigned a value 2 .

The result of the function is not affected by the following:

   * A single row INSERT statement with a VALUES clause for a table without
     an identity column.
   * A multiple row INSERT statement with a VALUES clause.
   * An INSERT statement with a fullselect.
   * A ROLLBACK TO SAVEPOINT statement.

Notes:

   * Expressions in the VALUES clause of an INSERT statement are evaluated
     prior to the assignments for the target columns of the INSERT
     statement. Thus, an invocation of an IDENTITY_VAL_LOCAL function
     inside the VALUES clause of an INSERT statement will use the most
     recently assigned value for an identity column from a previous INSERT
     statement. The function returns the null value if no previous single
     row INSERT statement with a VALUES clause for a table containing an
     identity column has been executed within the same level as the
     IDENTITY_VAL_LOCAL function.
   * The identity column value of the table for which the trigger is
     defined can be determined within a trigger, by referencing the trigger
     transition variable for the identity column.
   * The result of invoking the IDENTITY_VAL_LOCAL function from within the
     trigger condition of an insert trigger is a null value.
   * It is possible that multiple before or after insert triggers exist for
     a table. In this case each trigger is processed separately, and
     identity values assigned by one triggered action are not available to
     other triggered actions using the IDENTITY_VAL_LOCAL function. This is
     true even though the multiple triggered actions are conceptually
     defined at the same level.
   * It is not generally recommended to use the IDENTITY_VAL_LOCAL function
     in the body of a before insert trigger. The result of invoking the
     IDENTITY_VAL_LOCAL function from within the triggered action of a
     before insert trigger is the null value. The value for the identity
     column of the table for which the trigger is defined cannot be
     obtained by invoking the IDENTITY_VAL_LOCAL function within the
     triggered action of a before insert trigger. However, the value for
     the identity column can be obtained in the triggered action, by
     referencing the trigger transition variable for the identity column.
   * The result of invoking the IDENTITY_VAL_LOCAL function from within the
     triggered action of an after insert trigger 3 is the value assigned to
     an identity column of the table identified in the most recent single
     row INSERT statement invoked in the same triggered action that had a
     VALUES clause for a table containing an identity column. If a single
     row INSERT statement with a VALUES clause for a table containing an
     identity column was not executed within the same triggered action,
     prior to the invocation of the IDENTITY_VAL_LOCAL function, then the
     function returns a null value.
   * Since the results of the IDENTITY_VAL_LOCAL function are not
     deterministic, the result of an invocation of the IDENTITY_VAL_LOCAL
     function within the SELECT statement of a cursor can vary for each
     FETCH statement.
   * The assigned value is the value actually assigned to the identity
     column (that is, the value that would be returned on a subsequent
     SELECT statement). This value is not necessarily the value provided in
     the VALUES clause of the INSERT statement, or a value generated by
     DB2. The assigned value could be a value specified in a SET transition
     variable statement, within the body of a before insert trigger, for a
     trigger transition variable associated with the identity column.
   * The value returned by the function is unpredictable following a failed
     single row INSERT with a VALUES clause into a table with an identity
     column. The value may be the value that would have been returned from
     the function had it been invoked prior to the failed INSERT, or it may
     be the value that would have been assigned had the INSERT succeeded.
     The actual value returned depends on the point of failure and is
     therefore unpredictable.

Examples:

Example 1: Set the variable IVAR to the value assigned to the identity
column in the EMPLOYEE table. If this insert is the first into the EMPLOYEE
table, then IVAR would have a value of 1.

   CREATE TABLE EMPLOYEE
      (EMPNO   INTEGER GENERATED ALWAYS AS IDENTITY,
       NAME    CHAR(30),
       SALARY  DECIMAL(5,2),
       DEPTNO  SMALLINT)

Example 2: An IDENTITY_VAL_LOCAL function invoked in an INSERT statement
returns the value associated with the previous single row INSERT statement,
with a VALUES clause for a table with an identity column. Assume for this
example that there are two tables, T1 and T2. Both T1 and T2 have an
identity column named C1. DB2 generates values in sequence, starting with
1, for the C1 column in table T1, and values in sequence, starting with 10,
for the C1 column in table T2.

   CREATE TABLE T1
      (C1 INTEGER GENERATED ALWAYS AS IDENTITY,
       C2 INTEGER),
   CREATE TABLE T2
      (C1 DECIMAL(15,0) GENERATED BY DEFAULT AS IDENTITY
         (START WITH 10),
       C2 INTEGER),
   INSERT INTO T1 (C2) VALUES (5),
   INSERT INTO T1 (C2) VALUES (6),
   SELECT * FROM T1

which gives a result of:

      C1            C2
      -----------   ----------
                1            5
                2            6

and now, declaring the function for the variable IVAR:

   VALUES IDENTITY_VAL_LOCAL() INTO :IVAR

At this point, the IDENTITY_VAL_LOCAL function would return a value of 2 in
IVAR, because that was the value most recently assigned by DB2. The
following INSERT statement inserts a single row into T2, where column C2
gets a value of 2 from the IDENTITY_VAL_LOCAL function.

INSERT INTO T2 (C2) VALUES (IDENTITY_VAL_LOCAL());
   SELECT * FROM T2
      WHERE C1 = DECIMAL(IDENTITY_VAL_LOCAL(),15,0)

returning a result of:

             C1                  C2
      -----------------   ----------
                    10.            2

Invoking the IDENTITY_VAL_LOCAL function after this insert results in a
value of 10, which is the value generated by DB2 for column C1 of T2.

In a nested environment involving a trigger, use the IDENTITY_VAL_LOCAL
function to retrieve the identity value assigned at a particular level,
even though there might have been identity values assigned at lower levels.
Assume that there are three tables, EMPLOYEE, EMP_ACT, and ACCT_LOG. There
is an after insert trigger defined on EMPLOYEE that results in additional
inserts into the EMP_ACT and ACCT_LOG tables.

   CREATE TABLE EMPLOYEE
      (EMPNO SMALLINT GENERATED ALWAYS AS IDENTITY (START WITH 1000),
       NAME CHAR(30),
       SALARY DECIMAL(5,2),
       DEPTNO SMALLINT);

   CREATE TABLE EMP_ACT
      (ACNT_NUM SMALLINT GENERATED ALWAYS AS IDENTITY (START WITH 1),
       EMPNO SMALLINT);

   CREATE TABLE ACCT_LOG
      (ID SMALLINT GENERATED ALWAYS AS IDENTITY (START WITH 100),
       ACNT_NUM SMALLINT,
       EMPNO SMALLINT);

   CREATE TRIGGER NEW_HIRE
      AFTER INSERT ON EMPLOYEE
      REFERENCING NEW AS NEW_EMP
      FOR EACH ROW MODE DB2SQL
      BEGIN ATOMIC
         INSERT INTO EMP_ACT (EMPNO)
         VALUES (NEW_EMP.EMPNO);
         INSERT INTO ACCT_LOG (ACNT_NUM EMPNO)
         VALUES (IDENTITY_VAL_LOCAL(), NEW_EMP.EMPNO);
   END

The first triggered INSERT statement inserts a row into the EMP_ACT table.
This INSERT statement uses a trigger transition variable for the EMPNO
column of the EMPLOYEE table, to indicate that the identity value for the
EMPNO column of the EMPLOYEE table is to be copied to the EMPNO column of
the EMP_ACT table. The IDENTITY_VAL_LOCAL function could not be used to
obtain the value assigned to the EMPNO column of the EMPLOYEE table. This
is because an INSERT statement has not been issued at this level of the
nesting, and as such, if the IDENTITY_VAL_LOCAL function were invoked in
the VALUES clause of the INSERT for EMP_ACT, then it would return a null
value. This INSERT statement for the EMP_ACT table also results in the
generation of a new identity column value for the ACNT_NUM column.

A second triggered INSERT statement inserts a row into the ACCT_LOG table.
This statement invokes the IDENTITY_VAL_LOCAL function to indicate that the
identity value assigned to the ACNT_NUM column of the EMP_ACT table in the
previous INSERT statement in the triggered action is to be copied to the
ACNT_NUM column of the ACCT_LOG table. The EMPNO column is assigned the
same value as the EMPNO column of EMPLOYEE table.

From the invoking application (that is, the level at which the INSERT to
EMPLOYEE is issued), set the variable IVAR to the value assigned to the
EMPNO column of the EMPLOYEE table by the original INSERT statement.

   INSERT INTO EMPLOYEE (NAME, SALARY, DEPTNO)
   VALUES ('Rupert', 989.99, 50);

The contents of the three tables after processing the original INSERT
statement and all of the triggered actions are:

   SELECT EMPNO, SUBSTR(NAME,10) AS NAME, SALARY, DEPTNO
      FROM EMPLOYEE;

      EMPNO       NAME        SALARY                             DEPTNO
      ----------- ----------- ---------------------------------- -----------
             1000 Rupert                                  989.99          50

   SELECT ACNT_NUM, EMPNO
      FROM EMP_ACT;

      ACNT_NUM    EMPNO
      ----------- -----------
                1        1000

   SELECT * FROM ACCT_LOG;

      ID          ACNT_NUM    EMPNO
      ----------- ----------- -----------
              100           1        1000

The result of the IDENTITY_VAL_LOCAL function is the most recently assigned
value for an identity column at the same nesting level. After processing
the original INSERT statement and all of the triggered actions, the
IDENTITY_VAL_LOCAL function returns a value of 1000, because this is the
value assigned to the EMPNO column of the EMPLOYEE table. The following
VALUES statement results in setting IVAR to 1000. The insert into the
EMP_ACT table (which occurred after the insert into the EMPLOYEE table and
at a lower nesting level) has no affect on what is returned by this
invocation of the IDENTITY_VAL_LOCAL function.

VALUES IDENTITY_VAL_LOCAL() INTO :IVAR;

38.3.2.6 LCASE and UCASE (Unicode)

In a Unicode database, the entire repertoire of Unicode characters is
uppercase (or lowercase) based on the Unicode properties of these
characters. Double-wide versions of ASCII characters, as well as Roman
numerals, now convert to upper or lower case correctly.

38.3.2.7 MQPUBLISH

>>-MQPUBLISH---(------------------------------------------------>

>-----+-----------------------------------------------+--------->
      '-publisher-service--,--+--------------------+--'
                              '-service-policy--,--'

>----msg-data----+-----------------------------------+--)------><
                 '-,--topic--+--------------------+--'
                             |              (1)   |
                             '-,--correl-id-------'


Notes:

  1. The correl-id cannot be specified unless a service and a policy are
     previously defined.

The schema is MQDB2.

The MQPUBLISH function publishes data to MQSeries. This function requires
the installation of either MQSeries Publish/Subscribe or MQSeries
Integrator. Please consult www.ibm.com/software/MQSeries for further
details.

The MQPUBLISH function publishes the data contained in msg-data to the
MQSeries publisher specified in publisher-service, and using the quality of
service policy defined by service-policy. An optional topic for the message
can be specified, and an optional user-defined message correlation
identifier may also be specified. The function returns a value of '1' if
successful or a '0' if unsuccessful.

publisher-service
     A string containing the logical MQSeries destination where the message
     is to be sent. If specified, the publisher-service must refer to a
     publisher Service Point defined in the AMT.XML repository file. A
     service point is a logical end-point from which a message is sent or
     received. Service point definitions include the name of the MQSeries
     Queue Manager and Queue. See the MQSeries Application Messaging
     Interface for further details. If publisher-service is not specified,
     then the DB2.DEFAULT.PUBLISHER will be used. The maximum size of
     publisher-service is 48 characters.

service-policy
     A string containing the MQSeries AMI Service Policy to be used in
     handling of this message. If specified, the service-policy must refer
     to a Policy defined in the AMT.XML repository file. A Service Policy
     defines a set of quality of service options that should be applied to
     this messaging operation. These options include message priority and
     message persistence. See the MQSeries Application Messaging Interface
     manual for further details. If service-policy is not specified, then
     the default DB2.DEFAULT.POLICY will be used. The maximum size of
     service-policy is 48 characters.

msg-data
     A string expression containing the data to be sent via MQSeries. The
     maximum size is 4000 characters.

topic
     A string expression containing the topic for the message publication.
     If no topic is specified, none will be associated with the message.
     The maximum size of topic is 40 characters. Multiple topics can be
     specified in one string (up to 40 characters long). Each topic must be
     separated by a colon. For example, "t1:t2:the third topic" indicates
     that the message is associated with all three topics: t1, t2, and "the
     third topic".

correl-id
     An optional string expression containing a correlation identifier to
     be associated with this message. The correl-id is often specified in
     request and reply scenarios to associate requests with replies. If not
     specified, no correlation id will be added to the message. The maximum
     size of correl-id is 24 characters.

Examples

Example 1: This example publishes the string "Testing 123" to the default
publisher service (DB2.DEFAULT.PUBLISHER) using the default policy
(DB2.DEFAULT.POLICY). No correlation identifier or topic is specified for
the message.

VALUES MQPUBLISH('Testing 123')

Example 2: This example publishes the string "Testing 345" to the publisher
service "MYPUBLISHER" under the topic "TESTS". The default policy is used
and no correlation identifier is specified.

VALUES MQPUBLISH('MYPUBLISHER','Testing 345', 'TESTS')

Example 3: This example publishes the string "Testing 678" to the publisher
service "MYPUBLISHER" using the policy "MYPOLICY" with a correlation
identifier of "TEST1". The message is published with topic "TESTS".

VALUES MQPUBLISH('MYPUBLISHER','MYPOLICY','Testing 678','TESTS','TEST1')

Example 4: This example publishes the string "Testing 901" to the publisher
service "MYPUBLISHER" under the topic "TESTS" using the default policy
(DB2.DEFAULT.POLICY) and no correlation identifier.

VALUES MQPUBLISH('Testing 901','TESTS')

All examples return the value '1' if successful.

38.3.2.8 MQREAD

>>-MQREAD---(----+------------------------------------------+--->
                 '-receive-service--+--------------------+--'
                                    '-,--service-policy--'

>----)---------------------------------------------------------><


The schema is MQDB2.

The MQREAD function returns a message from the MQSeries location specified
by receive-service, using the quality of service policy defined in
service-policy. Executing this operation does not remove the message from
the queue associated with receive-service, but instead returns the message
at the head of the queue. The return value is a VARCHAR(4000) containing
the message. If no messages are available to be returned, a NULL is
returned.

receive-service
     A string containing the logical MQSeries destination from where the
     message is to be received. If specified, the receive-service must
     refer to a Service Point defined in the AMT.XML repository file. A
     service point is a logical end-point from where a message is sent or
     received. Service points definitions include the name of the MQSeries
     Queue Manager and Queue. See the MQSeries Application Messaging
     Interface for further details. If receive-service is not specified,
     then the DB2.DEFAULT.SERVICE will be used. The maximum size of
     receive-service is 48 characters.

service-policy
     A string containing the MQSeries AMI Service Policy used in handling
     this message. If specified, the service-policy must refer to a Policy
     defined in the AMT.XML repository file. A Service Policy defines a set
     of quality of service options that should be applied to this messaging
     operation. These options include message priority and message
     persistence. See the MQSeries Application Messaging Interface manual
     for further details. If service-policy is not specified, then the
     default DB2.DEFAULT.POLICY will be used. The maximum size of
     service-policy is 48 characters.

Examples:

Example 1: This example reads the message at the head of the queue
specified by the default service (DB2.DEFAULT.SERVICE), using the default
policy (DB2.DEFAULT.POLICY).

VALUES MQREAD()

Example 2: This example reads the message at the head of the queue
specified by the service "MYSERVICE" using the default policy
(DB2.DEFAULT.POLICY).

VALUES MQREAD('MYSERVICE')

Example 3: This example reads the message at the head of the queue
specified by the service "MYSERVICE", and using the policy "MYPOLICY".

VALUES MQREAD('MYSERVICE','MYPOLICY')

All of these examples return the contents of the message as a VARCHAR(4000)
if successful. If no messages are available, then a NULL is returned.

38.3.2.9 MQRECEIVE

>>-MQRECEIVE---------------------------------------------------->

>----(--+-------------------------------------------------------------+---)->
        '-receive-service--+---------------------------------------+--'
                           '-,--service-policy--+---------------+--'
                                                '-,--correl-id--'

>--------------------------------------------------------------><


The schema is MQDB2.

The MQRECEIVE function returns a message from the MQSeries location
specified by receive-service, using the quality of service policy
service-policy. Performing this operation removes the message from the
queue associated with receive-service. If the correl-id is specified, then
the first message with a matching correlation identifier will be returned.
If correl-id is not specified, then the message at the head of the queue
will be returned. The return value is a VARCHAR(4000) containing the
message. If no messages are available to be returned, a NULL is returned.

receive-service
     A string containing the logical MQSeries destination from which the
     message is received. If specified, the receive-service must refer to a
     Service Point defined in the AMT.XML repository file. A service point
     is a logical end-point from which a message is sent or received.
     Service points definitions include the name of the MQSeries Queue
     Manager and Queue. See the MQSeries Application Messaging Interface
     for further details. If receive-service is not specified, then the
     DB2.DEFAULT.SERVICE is used. The maximum size of receive-service is 48
     characters.

service-policy
     A string containing the MQSeries AMI Service Policy to be used in the
     handling of this message. If specified, the service-policy must refer
     to a Policy defined in the AMT XML repository file 4 . If
     service-policy is not specified, then the default DB2.DEFAULT.POLICY
      is used. The maximum size of service-policy is 48 characters.

correl-id
     A string containing an optional correlation identifier to be
     associated with this message. The correl-id is often specified in
     request and reply scenarios to associate requests with replies. If not
     specified, no correlation id will be specified. The maximum size of
     correl-id is 24 characters.

Examples:

Example 1: This example receives the message at the head of the queue
specified by the default service (DB2.DEFAULT.SERVICE), using the default
policy (DB2.DEFAULT.POLICY).

VALUES MQRECEIVE()

Example 2: This example receives the message at the head of the queue
specified by the service "MYSERVICE" using the default policy
(DB2.DEFAULT.POLICY).

VALUES MQRECEIVE('MYSERVICE')

Example 3: This example receives the message at the head of the queue
specified by the service "MYSERVICE" using the policy "MYPOLICY".

VALUES MQRECEIVE('MYSERVICE','MYPOLICY')

Example 4: This example receives the first message with a correlation id
that matches '1234' from the head of the queue specified by the service
"MYSERVICE" using the policy "MYPOLICY".

VALUES MQRECEIVE('MYSERVICE',MYPOLICY','1234')

All these examples return the contents of the message as a VARCHAR(4000) if
successful. If no messages are available, a NULL will be returned.

38.3.2.10 MQSEND

>>-MQSEND---(----+------------------------------------------+--->
                 '-send-service--,--+--------------------+--'
                                    '-service-policy--,--'

>----msg-data----+--------------------+--)---------------------><
                 |              (1)   |
                 '-,--correl-id-------'


Notes:

  1. The correl-id cannot be specified unless a service and a policy are
     previously defined.

The schema is MQDB2.

The MQSEND function sends the data contained in msg-data to the MQSeries
location specified by send-service, using the quality of service policy
defined by service-policy. An optional user defined message correlation
identifier may be specified by correl-id. The function returns a value of
'1' if successful or a '0' if unsuccessful.

msg-data
     A string expression containing the data to be sent via MQSeries. The
     maximum size is 4000 characters.

send-service
     A string containing the logical MQSeries destination where the message
     is to be sent. If specified, the send-service refers to a service
     point defined in the AMT.XML repository file. A service point is a
     logical end-point from which a message may be sent or received.
     Service point definitions include the name of the MQSeries Queue
     Manager and Queue. See the MQSeries Application Messaging Interface
     manual for further details. If send-service is not specified, then the
     value of DB2.DEFAULT.SERVICE is used. The maximum size of send-service
     is 48 characters.

service-policy
     A string containing the MQSeries AMI Service Policy used in handling
     of this message. If specified, the service-policy must refer to a
     service policy defined in the AMT XML repository file. A Service
     Policy defines a set of quality of service options that should be
     applied to this messaging operation. These options include message
     priority and message persistence. See the MQSeries Application
     Messaging Interface manual for further details. If service-policy is
     not specified, then a default value of DB2.DEFAULT.POLICY will be
     used. The maximum size of service-policy is 48 characters.

correl-id
     An optional string containing a correlation identifier associated with
     this message. The correl-id is often specified in request and reply
     scenarios to associate requests with replies. If not specified, no
     correlation id will be sent. The maximum size of correl-id is 24
     characters.

Examples:

Example 1: This example sends the string "Testing 123" to the default
service (DB2.DEFAULT.SERVICE), using the default policy
(DB2.DEFAULT.POLICY), with no correlation identifier.

VALUES MQSEND('Testing 123')

Example 2: This example sends the string "Testing 345" to the service
"MYSERVICE", using the policy "MYPOLICY", with no correlation identifier.

VALUES MQSEND('MYSERVICE','MYPOLICY','Testing 345')

Example 3: This example sends the string "Testing 678" to the service
"MYSERVICE", using the policy "MYPOLICY", with correllation identifier
"TEST3".

VALUES MQSEND('MYSERVICE','MYPOLICY','Testing 678','TEST3')

Example 4: This example sends the string "Testing 901" to the service
"MYSERVICE", using the default policy (DB2.DEFAULT.POLICY), and no
correlation identifier.

VALUES MQSEND('MYSERVICE','Testing 901')

All examples return a scalar value of '1' if successful.

38.3.2.11 MQSUBSCRIBE

>>-MQSUBSCRIBE---(---------------------------------------------->

>-----+------------------------------------------------+-------->
      '-subscriber-service--,--+--------------------+--'
                               '-service-policy--,--'

>----topic---)-------------------------------------------------><


The schema is MQDB2.

The MQSUBSCRIBE function is used to register interest in MQSeries messages
published on a specified topic. The subscriber-service specifies a logical
destination for messages that match the specified topic. Messages that
match topic will be placed on the queue defined by subscriber-service and
can be read or received through a subsequent call to MQREAD, MQRECEIVE,
MQREADALL, or MQRECEIVEALL. This function requires the installation and
configuration of an MQSeries based publish and subscribe system, such as
MQSeries Integrator or MQSeries Publish/Subscribe. See
www.ibm.com/software/MQSeries for further details.

The function returns a value of '1' if successful or a '0' if unsuccessful.
Successfully executing this function will cause the publish and subscribe
server to forward messages matching the topic to the service point defined
by subscriber-service.

subscriber-service
     A string containing the logical MQSeries subscription point to where
     messages matching topic will be sent. If specified, the
     subscriber-service must refer to a Subscribers Service Point defined
     in the AMT.XML repository file. Service points definitions include the
     name of the MQSeries Queue Manager and Queue. See the MQSeries
     Application Messaging Interface manual for further details. If
     subscriber-service is not specified, then the DB2.DEFAULT.SUBSCRIBER
     will be used instead. The maximum size of subscriber-service is 48
     characters.

service-policy
     A string containing the MQSeries AMI Service Policy to be used in
     handling the message. If specified, the service-policy must refer to a
     Policy defined in the AMT.XML repository file. A Service Policy
     defines a set of quality of service options to be applied to this
     messaging operation. These options include message priority and
     message persistence. See the MQSeries Application Messaging Interface
     manual for further details. If service-policy is not specified, then
     the default DB2.DEFAULT.POLICY will be used instead. The maximum size
     of service-policy is 48 characters.

topic
     A string defining the types of messages to receive. Only messages
     published with the specified topics will be received by this
     subscription. Multiple subscriptions may coexist. The maximum size of
     topic is 40 characters. Multiple topics can be specified in one string
     (up to 40 characters long). Each topic must be separated by a colon.
     For example, "t1:t2:the third topic" indicates that the message is
     associated with all three topics: t1, t2, and "the third topic".

Examples:

Example 1: This example registers an interest in messages containing the
topic "Weather". The default subscriber-service (DB2.DEFAULT.SUBSCRIBER) is
registered as the subscriber and the default service-policy
(DB2.DEFAULT.POLICY) specifies the quality of service.

VALUES MQSUBSCRIBE('Weather')

Example 2: This example demonstrates a subscriber registering interest in
messages containing "Stocks". The subscriber registers as
"PORTFOLIO-UPDATES" with policy "BASIC-POLICY".

VALUES MQSUBSCRIBE('PORTFOLIO-UPDATES','BASIC-POLICY','Stocks')

All examples return a scalar value of '1' if successful.

38.3.2.12 MQUNSUBSCRIBE

>>-MQUNSUBSCRIBE---(-------------------------------------------->

>-----+------------------------------------------------+-------->
      '-subscriber-service--,--+--------------------+--'
                               '-service-policy--,--'

>----topic---)-------------------------------------------------><


The schema is MQDB2.

The MQUNSUBSCRIBE function is used to unregister an existing message
subscription. The subscriber-service, service-policy, and topic are used to
identify which subscription is cancelled. This function requires the
installation and configuration of an MQSeries based publish and subscribe
system, such as MQSeries Integrator or MQSeries Publish/Subscribe. See
www.ibm.com/software/MQSeries for further details.

The function returns a value of '1' if successful or a '0' if unsuccessful.
The result of successfully executing this function is that the publish and
subscribe server will remove the subscription defined by the given
parameters. Messages with the specified topic will no longer be sent to the
logical destination defined by subscriber-service.

subscriber-service
     If specified, the subscriber-service must refer to a Subscribers
     Service Point defined in the AMT.XML repository file. Service point
     definitions include the name of the MQSeries Queue Manager and Queue.
     See the MQSeries Application Messaging Interface manual for further
     details. If subscriber-service is not specified, then the
     DB2.DEFAULT.SUBSCRIBER value is used. The maximum size of
     subscriber-service is 48 characters.

service-policy
     If specified, the service-policy must refer to a Policy defined in the
     AMT.XML repository file. A Service Policy defines a set of quality of
     service options to be applied to this messaging operation. See the
     MQSeries Application Messaging Interface manual for further details.
     If service-policy is not specified, then the default
     DB2.DEFAULT.POLICY will be used. The maximum size of service-policy is
     48 characters.

topic
     A string specifying the subject of messages that are not to be
     received. The maximum size of topic is 40 characters. Multiple topics
     can be specified in one string (up to 40 characters long). Each topic
     must be separated by a colon. For example, "t1:t2:the third topic"
     indicates that the message is associated with all three topics: t1,
     t2, and "the third topic".

Examples:

Example 1: This example cancels an interest in messages containing the
topic "Weather". The default subscriber-service (DB2.DEFAULT.SUBSCRIBER) is
registered as the unsubscriber and the default service-policy
(DB2.DEFAULT.POLICY) specifies the quality of service.

VALUES MQUNSUBSCRIBE('Weather')

Example 2: This example demonstrates a subscriber cancelling an interest in
messages containing "Stocks". The subscriber is registered as
"PORTFOLIO-UPDATES" with policy "BASIC-POLICY".

VALUES MQUNSUBSCRIBE('PORTFOLIO-UPDATES','BASIC-POLICY','Stocks')

These examples return a scalar value of '1' if successful and a scalar
value of '0' if unsuccessful.

38.3.2.13 MULTIPLY_ALT

>>-MULTIPLY_ALT------------------------------------------------->

>----(exact_numeric_expression, exact_numeric_expression)------><


The schema is SYSIBM.

This function was first available in FixPak 2 of Version 7.1.

The MULTIPLY_ALT scalar function returns the product of the two arguments
as a decimal value. It is provided as an alternative to the multiplication
operator, especially when the sum of the precisions of the arguments
exceeds 31.

The arguments can be any built-in exact numeric data type (DECIMAL, BIGINT,
INTEGER, or SMALLINT).

The result of the function is a DECIMAL. The precision and scale of the
result are determined as follows, using the symbols p and s to denote the
precision and scale of the first argument, and the symbols p' and s' to
denote the precision and scale of the second argument.

   * The precision is MIN(31, p + p')
   * The scale is:
        o 0 if the scale of both arguments is 0
        o MIN(31, s+s') if p+p' is less than or equal to 31
        o MAX(MIN(3, s+s'), 31-(p-s+p'-s') ) if p+p' is greater than 31.

The result can be null if at least one argument can be null or the database
is configured with DFT_SQLMATHWARN set to yes; the result is the null value
if one of the arguments is null.

The MULTIPLY_ALT function is a better choice than the multiplication
operator when performing decimal arithmetic where a scale of at least 3 is
needed and the sum of the precisions exceeds 31. In these cases, the
internal computation is performed so that overflows are avoided. The final
result is then assigned to the result data type using truncation where
necessary to match the scale. Note that overflow of the final result is
still possible when the scale is 3.

The following is a sample comparing the result types using MULTIPLY_ALT and
the multiplication operator.

 Type of argument 1Type of argument   Result using      Result using
                   2                  MULTIPLY_ALT      multiplication
                                                        operator
 DECIMAL(31,3)     DECIMAL(15,8)      DECIMAL(31,3)     DECIMAL(31,11)
 DECIMAL(26,23)    DECIMAL(10,1)      DECIMAL(31,19)    DECIMAL(31,24)
 DECIMAL(18,17)    DECIMAL(20,19)     DECIMAL(31,29)    DECIMAL(31,31)
 DECIMAL(16,3)     DECIMAL(17,8)      DECIMAL(31,9)     DECIMAL(31,11)
 DECIMAL(26,5)     DECIMAL(11,0)      DECIMAL(31,3)     DECIMAL(31,5)
 DECIMAL(21,1)     DECIMAL(15,1)      DECIMAL(31,2)     DECIMAL(31,2)

Example:

Multiply two values where the data type of the first argument is
DECIMAL(26, 3) and the data type of the second argument is DECIMAL(9,8).
The data type of the result is DECIMAL(31,7).

values multiply_alt(98765432109876543210987.654,5.43210987)
1
---------------------------------
 536504678578875294857887.5277415

Note that the complete product of these two numbers is
536504678578875294857887.52774154498 but the last 4 digits were truncated
to match the scale of the result data type. Using the multiplication
operator with the same values results in an arithmetic overflow since the
result data type is DECIMAL(31,11) and the result value has 24 digits left
of the decimal, but the result data type only supports 20 digits.

38.3.2.14 REC2XML

>>-REC2XML---(--decimal-constant---,--format-string------------->

>----,--row-tag-string----+------------------------+--)--------><
                          |  .------------------.  |
                          |  V                  |  |
                          '----,--column-name---+--'


The schema is SYSIBM.

The REC2XML function returns a string formatted with XML tags and
containing column names and column values.

decimal-constant
     The expansion factor for replacing column value characters. The
     decimal value must be greater than 0.0 and less than or equal to 6.0
     (SQLSTATE 42820).

     The decimal-constant value is used to calculate the result length of
     the function. For every column with a character data type, the length
     attribute of the column is multiplied by this expansion factor before
     it is added in to the result length.

     To specify no expansion, use a value of 1.0. Specifying a value less
     than 1.0 reduces the calculated result length. If the actual length of
     the result string is greater than the calculated result length of the
     function, then an error is raised (SQLSTATE 22001).

format-string
     The string constant that specifies which format the function is to use
     during execution.

     The format-string is case-sensitive, so the following values must be
     specified in uppercase to be recognized.

     COLATTVAL or COLATTVAL_XML
          These formats return a string with columns as attribute values.

          >>-<--row-tag-string-->----------------------------------------->

                .-------------------------------------------------------------------------.
                V                                                                         |
          >--------<--column-name--=--"column-name"--+->--column-value--</--column-->--+--+>
                                                     '-null="true"--</-----------------'

          >----</--row-tag-string-->-------------------------------------><


          Column names may or may not be valid XML attribute values. For
          those column names which are not valid XML attribute values,
          character replacement is performed on the column name before it
          is included in the result string.

          Column values may or may not be valid XML element values. If the
          format-string COLATTVAL is specified, for those column values
          which are not valid XML element values, character replacement is
          performed on the column value before it is included in the result
          string. If the format-string COLATTVAL_XML is specified,
          character replacement is not performed on column values (note
          that character replacement is still performed on column names).

row-tag-string
     A string constant that specifies the tag used for each row.

     If an empty string is specified, then a value of 'row' is assumed.

     If a string of one or more blank characters is specified, then no
     beginning row-tag-string or ending row-tag-string (including the angle
     bracket delimiters) will appear in the result string.

column-name
     A qualified or unqualified name of a table column. The column must
     have one of the following data types (SQLSTATE 42815):
        o numeric (SMALLINT, INTEGER, BIGINT, DECIMAL, NUMERIC, REAL,
          DOUBLE)
        o character string (CHAR, VARCHAR) 5
        o datetime (DATE, TIME, TIMESTAMP)
        o a user-defined type based on one of the above types

     The same column name cannot be specified more than once (SQLSTATE
     42734).

The result of the function is VARCHAR. The maximum length is 32672 bytes
(SQLSTATE 54006).

Consider the following invocation:

   REC2XML (dc, fs, rt, c1, c2, ..., cn)

If the value of fs is "COLATTVAL" or "COLATTVAL_XML"
     the result is the same as the following expression:

        '<' CONCAT rt CONCAT '>' CONCAT y1 CONCAT y2 CONCAT ... CONCAT yn
        CONCAT '</' CONCAT rt CONCAT '>'

     where yn is equivalent to:

        '<column name="' CONCAT xvcn CONCAT vn

     and vn is equivalent to:

        '">' CONCAT rn CONCAT '</column>'

     if the column is not null, and

        '" null="true"/>'

     if the column value is null.

     xvcn is equivalent to a string representation of the column name of
     cn, where any characters appearing in Table 29 are replaced with the
     corresponding representation. This ensures that the resulting string
     is a valid XML attribute or element value token.

     rn is equivalent to a string representation as indicated in Table 28.

Result Column Values:

Based on the data type of the column and the actual format-string
specified, the column values from the table may be transformed before being
concatenated into the result string. The following table shows the
transformations done on the column values.

Table 28. Column Values String Result
 Data type of cn                     rn

 CHAR, VARCHAR                       The value is a string. If the
                                     format-string does not end in the
                                     characters "_XML", then each
                                     character in cn is replaced with the
                                     corresponding replacement
                                     representation from Table 29, as
                                     indicated. The length attribute is:
                                     dc * the length attribute of cn.

 SMALLINT, INTEGER, BIGINT, DECIMAL, The value is LTRIM(RTRIM(CHAR(cn))).
 NUMERIC, REAL, DOUBLE               The length attribute is the result
                                     length of CHAR(cn). The decimal
                                     character is always the period
                                     character.
 DATE                                The value is CHAR(cn, ISO). The
                                     length attribute is the result length
                                     of CHAR(cn, ISO).

 TIME                                The value is CHAR(cn, JIS). The
                                     length attribute is the result length
                                     of CHAR(cn, JIS)

 TIMESTAMP                           The value is CHAR(cn). The length
                                     attribute is the result length of
                                     CHAR(cn).

Character Replacement:

Depending on the value specified for the format-string, certain characters
in column names and column values will be replaced to ensure that the
column names form valid XML attribute values and the column values form
valid XML element values.

Table 29. Character Replcements for XML Attribute Values and Element Values
 < is replaced by &lt;
 > is replaced by &gt;
 " is replaced by &quot;
 & is replaced by &amp;
 ' is replaced by &apos;

Examples:

   * Using the DEPARTMENT table, format the department table row, except
     the DEPTNAME and LOCATION columns, for department 'D01' into a string
     of valid XML. Since the data does not contain any of the characters
     which require replacement, the expansion factor will be 1.0 (no
     expansion). Also note that the MGRNO value is null for this row.

        SELECT REC2XML (1.0, 'COLATTVAL', '', DEPTNO, MGRNO, ADMRDEPT)
           FROM DEPARTMENT
           WHERE DEPTNO = 'D01'

     This example returns the following VARCHAR(117) string:

     <row>
        <column name="DEPTNO">D01</column>
        <column name="MGRNO" null="true"/>
        <column name="ADMRDEPT">A00</column>
     </row>

     Notes:
          REC2XML does not insert new line characters in the output. The
          above example output is formatted for the sake of readability.
   * A 5-day university schedule introduces a class with the name '&43<FIE'
     to a table called CL_SCHED, with a new format for the CLASS_CODE
     column. Using the REC2XML function, this example formats an XML string
     with this new class data, except for the class end time.

     The length attribute for the REC2XML call (see below) with an
     expansion factor of 1.0 would be 128 (11 for the '<row>' and '</row>'
     overhead, 21 for the column names, 75 for the '<column name=', '>',
     '</column>' and double quotes, 7 for the CLASS_CODE data, 6 for the
     DAY data, and 8 for the STARTING data). Since the '&' and '<'
     characters will be replaced, an expansion factor of 1.0 will not be
     sufficient. The length attribute of the function will need to support
     an increase from 7 to 14 characters for the new format CLASS_CODE
     data.

     However, since it is known that the DAY value will never be more than
     1 digit long, an extra 5 is calculated into the length that will never
     be used. Therefore, the expansion only needs to handle an increase of
     2. Since CLASS_CODE is the only character string column in the
     argument list, this is the only column value to which the expansion
     factor applies. To get an increase of 2 for the length, an expansion
     factor of 9/7 (approximately 1.2857) would be needed. An expansion
     factor of 1.3 will be used.

        SELECT REC2XML (1.3, 'COLATTVAL', 'record', CLASS_CODE, DAY, STARTING)
           FROM CL_SCHED
           WHERE CLASS_CODE = '&43<FIE'

     Returns the following string:

        <record>
           <column name="CLASS_CODE">&amp;43&lt;FIE</column>
           <column name="DAY">5</column>
           <column name="STARTING">06:45:00</column>
        </record>

     Notes:
          REC2XML does not insert new line characters in the output. The
          above example output is formatted for the sake of readability.
   * This example shows characters replaced in a column name.

        SELECT REC2XML (1.3,'COLATTVAL', '', Class, "time<noon")
           FROM (SELECT Class_code, Starting
                    FROM Cl_sched
                    WHERE Starting < '12:00:00')
           AS Early (Class, "time<noon")

     This query returns the following string:

        <row>
           <column name="CLASS">&amp;43&lt;FIE</column>
           <column name="time&lt;noon>06:45:00</column>
        </row>

     Notes:
          REC2XML does not insert new line characters in the output. The
          above example output is formatted for the sake of readability.
   * Assume that new rows have been added to the EMP_RESUME table, storing
     the resumes as strings of valid XML. The COLATTVAL_XML format-string
     is used so character replacement will not be performed. None of the
     resumes are more than 3500 characters in length. The following query
     could be used to select the XML version of the resumes from the
     EMP_RESUME table and format it into an XML document fragment.

     SELECT REC2XML (1.0,'COLATTVAL_XML', '', EMPNO, RESUME_XML)
        FROM (SELECT EMPNO, CAST(RESUME as VARCHAR(3500)) as RESUME_XML
                 FROM EMP_RESUME
                 WHERE RESUME_FORMAT = 'XML')
        AS EMP_RESUME_XML

38.3.2.15 ROUND

>>-ROUND---(expression1, expression2)--------------------------><


The schema is SYSIBM.

This function was first available in FixPak 2 of Version 7.1.

Notes:
     The SYSFUN version of the ROUND function continues to be available.

The ROUND function returns expression1 rounded to expression2 places to the
right of the decimal point if expression2 is positive or to the left of the
decimal point if expression2 is zero or negative.

If expression1 is positive, a value of 5 is rounded to the next higher
positive number. For example, ROUND(3.5,0) = 4. If expression1 is negative,
a value of 5 is rounded to the next lower negative number. For example,
ROUND(-3.5,0) = -4.

expression1
     An expression that returns a value of any built-in numeric data type.

expression2
     An expression that returns a small or large integer. When the value of
     expression2 is not negative, it specifies rounding to that number of
     places to the right of the decimal separator. When the value of
     expression2 is negative, it specifies rounding to the absolute value
     of expression2 places to the left of the decimal separator.

     If expression2 is not negative, expression1 is rounded to the absolute
     value of expression2 number of places to the right of the decimal
     point. If the value of expression2 is greater than the scale of
     expression1 then the value is unchanged except that the result value
     has a precision that is larger by 1. For example, ROUND(748.58,5) =
     748.58 where the precision is now 6 and the scale remains 2.

     If expression2 is negative, expression1 is rounded to the absolute
     value of expression2+1 number of places to the left of the decimal
     point.

     If the absolute value of a negative expression2 is larger than the
     number of digits to the left of the decimal point, the result is 0.
     For example, ROUND(748.58,-4) = 0.

The data type and length attribute of the result are the same as the data
type and length attribute of the first argument, except that the precision
is increased by one if the expression1 is DECIMAL or NUMERIC and the
precision is less than 31. For example, an argument with a data type of
DECIMAL(5,2) results in DECIMAL(6,2). An argument with a data type of
DECIMAL(31,2) results in DECIMAL(31,2). The scale is the same as the scale
of the first argument.

If either argument can be null or the database is configured with
DFT_SQLMATHWARN set to yes, the result can be null. If either argument is
null, the result is the null value.

Examples:

Calculate the number 873.726 rounded to 2, 1, 0, -1, -2, -3, and -4 decimal
places respectively.

    VALUES (ROUND(873.726, 2),
            ROUND(873.726, 1),
            ROUND(873.726, 0),
            ROUND(873.726,-1),
            ROUND(873.726,-2),
            ROUND(873.726,-3),
            ROUND(873.726,-4) )

This example returns:

1         2         3         4         5         6         7
--------- --------- --------- --------- --------- --------- ---------
  873.730   873.700   874.000   870.000   900.000  1000.000  0.000

Calculate a both positive and negative numbers.

    VALUES (ROUND(3.5, 0),
            ROUND(3.1, 0),
            ROUND(-3.1, 0),
            ROUND(-3.5,0) )

This example returns:

     1    2    3    4
     ---- ---- ---- ----
      4.0  3.0 -3.0 -4.0

38.3.2.16 WEEK_ISO

Change the description of this function to the following:

The schema is SYSFUN.

Returns the week of the year of the argument as an integer value in the
range 1-53. The week starts with Monday and always includes 7 days. Week 1
is the first week of the year to contain a Thursday, which is equivalent to
the first week containing January 4. It is therefore possible to have up to
3 days at the beginning of a year appear in the last week of the previous
year. Conversely, up to 3 days at the end of a year may appear in the first
week of the next year.

The argument must be a date, timestamp, or a valid character string
representation of a date or timestamp that is neither a CLOB nor a LONG
VARCHAR.

The result of the function is INTEGER. The result can be null; if the
argument is null, the result is the null value.

Example:

The following list shows examples of the result of WEEK_ISO and
DAYOFWEEK_ISO.

DATE       WEEK_ISO    DAYOFWEEK_ISO
---------- ----------- -------------
1997-12-28          52             7
1997-12-31           1             3
1998-01-01           1             4
1999-01-01          53             5
1999-01-04           1             1
1999-12-31          52             5
2000-01-01          52             6
2000-01-03           1             1

38.3.3 Table Functions

38.3.3.1 MQREADALL

>>-MQREADALL---(------------------------------------------------>

>-----+------------------------------------------+-------------->
      '-receive-service--+--------------------+--'
                         '-,--service-policy--'

>-----+-----------+--)-----------------------------------------><
      '-num-rows--'


The schema is MQDB2.

The MQREADALL function returns a table containing the messages and message
metadata from the MQSeries location specified by receive-service, using the
quality of service policy service-policy. Performing this operation does
not remove the messages from the queue associated with receive-service.

If num-rows is specified, then a maximum of num-rows messages will be
returned. If num-rows is not specified, then all available messages will be
returned. The table returned contains the following columns:

   * MSG - a VARCHAR(4000) column containing the contents of the MQSeries
     message.
   * CORRELID - a VARCHAR(24) column holding a correlation ID used to
     relate messages.
   * TOPIC - a VARCHAR(40) column holding the topic that the message was
     published with, if available.
   * QNAME - a VARCHAR(48) column holding the queue name where the message
     was received.
   * MSGID - a CHAR(24) column holding the assigned MQSeries unique
     identifier for this message.
   * MSGFORMAT - a VARCHAR(8) column holding the format of the message, as
     defined by MQSeries. Typical strings have a MQSTR format.

receive-service
     A string containing the logical MQSeries destination from which the
     message is read. If specified, the receive-service must refer to a
     service point defined in the AMT.XML repository file. A service point
     is a logical end-point from which a message is sent or received.
     Service point definitions include the name of the MQSeries Queue
     Manager and Queue. See the MQSeries Application Messaging Interface
     for further details. If receive-service is not specified, then the
     DB2.DEFAULT.SERVICE will be used. The maximum size of receive-service
     is 48 characters.

service-policy
     A string containing the MQSeries AMI Service Policy used in the
     handling of this message. If specified, the service-policy refers to a
     Policy defined in the AMT XML repository file. A service policy
     defines a set of quality of service options that should be applied to
     this messaging operation. These options include message priority and
     message persistence. See the MQSeries Application Messaging Interface
     manual for further details. If service-policy is not specified, then
     the default DB2.DEFAULT.POLICY will be used. The maximum size of
     service-policy is 48 characters.

num-rows
     A positive integer containing the maximum number of messages to be
     returned by the function.

Examples:

Example 1: This example receives all the messages from the queue specified
by the default service (DB2.DEFAULT.SERVICE), using the default policy
(DB2.DEFAULT.POLICY). The messages and all the metadata are returned as a
table.

SELECT *
   FROM table (MQREADALL()) T

Example 2: This example receives all the messages from the head of the
queue specified by the service MYSERVICE, using the default policy
(DB2.DEFAULT.POLICY). Only the MSG and CORRELID columns are returned.

SELECT T.MSG, T.CORRELID
   FROM table (MQREADALL('MYSERVICE')) T

Example 3: This example reads the head of the queue specified by the
default service (DB2.DEFAULT.SERVICE), using the default policy
(DB2.DEFAULT.POLICY). Only messages with a CORRELID of '1234' are returned.
All columns are returned.

SELECT *
   FROM table (MQREADALL()) T
   WHERE T.CORRELID = '1234'

Example 4: This example receives the first 10 messages from the head of the
queue specified by the default service (DB2.DEFAULT.SERVICE), using the
default policy (DB2.DEFAULT.POLICY). All columns are returned.

SELECT *
   FROM table (MQREADALL(10)) T

38.3.3.2 MQRECEIVEALL

>>-MQRECEIVEALL---(--------------------------------------------->

>-----+-------------------------------------------------------------+>
      '-receive-service--+---------------------------------------+--'
                         '-,--service-policy--+---------------+--'
                                              '-,--correl-id--'

>-----+--------------------+--)--------------------------------><
      '-+----+---num-rows--'
        '-,--'


The schema is MQDB2.

The MQRECEIVEALL function returns a table containing the messages and
message metadata from the MQSeries location specified by receive-service,
using the quality of service policy service-policy. Performing this
operation removes the messages from the queue associated with
receive-service.

If a correl-id is specified, then only those messages with a matching
correlation identifier will be returned. If correl-id is not specified,
then the message at the head of the queue will be returned.

If num-rows is specified, then a maximum of num-rows messages will be
returned. If num-rows is not specified, then all available messages are
returned. The table returned contains the following columns:

   * MSG - a VARCHAR(4000) column containing the contents of the MQSeries
     message.
   * CORRELID - a VARCHAR(24) column holding a correlation ID used to
     relate messages.
   * TOPIC - a VARCHAR(40) column holding the topic that the message was
     published with, if available.
   * QNAME - a VARCHAR(48) column holding the queue name where the message
     was received.
   * MSGID - a CHAR(24) column holding the assigned MQSeries unique
     identifier for this message.
   * MSGFORMAT - a VARCHAR(8) column holding the format of the message, as
     defined by MQSeries. Typical strings have a MQSTR format.

receive-service
     A string containing the logical MQSeries destination from which the
     message is recieved. If specified, the receive-service must refer to a
     service point defined in the AMT.XML repository file. A service point
     is a logical end-point from which a message is sent or received.
     Service point definitions include the name of the MQSeries Queue
     Manager and Queue. See the MQSeries Application Messaging Interface
     manual for further details. If receive-service is not specified, then
     the DB2.DEFAULT.SERVICE will be used. The maximum size of
     receive-service is 48 characters.

service-policy
     A string containing the MQSeries AMI Service Policy used in the
     handling of this message. If specified, the service-policy refers to a
     Policy defined in the AMT XML repository file. A service policy
     defines a set of quality of service options that should be applied to
     this messaging operation. These options include message priority and
     message persistence. See the MQSeries Application Messaging Interface
     manual for further details. If service-policy is not specified, then
     the default DB2.DEFAULT.POLICY will be used. The maximum size of
     service-policy is 48 characters.

correl-id
     An optional string containing a correlation identifier associated with
     this message. The correl-id is often specified in request and reply
     scenarios to associate requests with replies. If not specified, no
     correlation id is specified. The maximum size of correl-id is 24
     characters.

num-rows
     A positive integer containing the maximum number of messages to be
     returned by the function.

Examples:

Example 1: This example receives all the messages from the queue specified
by the default service (DB2.DEFAULT.SERVICE), using the default policy
(DB2.DEFAULT.POLICY). The messages and all the metadata are returned as a
table.

SELECT *
   FROM table (MQRECEIVEALL()) T

Example 2: This example receives all the messages from the head of the
queue specified by the service MYSERVICE, using the default policy
(DB2.DEFAULT.POLICY). Only the MSG and CORRELID columns are returned.

SELECT T.MSG, T.CORRELID
   FROM table (MQRECEIVEALL('MYSERVICE')) T

Example 3: This example receives all of the message from the head of the
queue specified by the service "MYSERVICE", using the policy "MYPOLICY".
Only messages with a CORRELID of '1234' are returned. Only the MSG and
CORRELID columns are returned.

SELECT T.MSG, T.CORRELID
   FROM table (MQRECEIVEALL('MYSERVICE','MYPOLICY','1234')) T


Example 4: This example receives the first 10 messages from the head of the
queue specified by the default service (DB2.DEFAULT.SERVICE), using the
default policy (DB2.DEFAULT.POLICY). All columns are returned.

SELECT *
   FROM table (MQRECEIVEALL(10)) T

38.3.4 Procedures

38.3.4.1 GET_ROUTINE_SAR

>>-GET_ROUTINE_SAR---------------------------------------------->

>----(--sarblob--,--type--,--routine_name_string--)------------><


The schema is SYSFUN.

This procedure was first available in FixPak 3 of Version 7.1.

The GET_ROUTINE_SAR procedure retrieves the necessary information to
install the same routine in another database server running the same level
on the same operating system. The information is retrieved into a single
BLOB string representing an SQL archive file. The invoker of the
GET_ROUTINE_SAR procedure must have DBADM authority.

sarblob
     An output argument of type BLOB(3M) that contains the routine SAR file
     contents.

type
     An input argument of type CHAR(2) that specifies whether the type of
     routine, using one of the following values:
        o P for a procedure.
        o SP for the specific name of a procedure.

routine_name_string
     An input argument of type VARCHAR(257) that specifies a qualified name
     of the routine. If no schema name is specified, the default is the
     CURRENT SCHEMA when the routine is processed.

Notes:
     The routine_name_string cannot include the double quote character (").

The qualified name of the routine is used to determine which routine to
retrieve. The routine that is found must be an SQL routine or an error is
raised (SQLSTATE 428F7). When not using a specific name, this may result in
more than one routine and an error is raised (SQLSTATE 42725). If this
occurs, the specific name of the routine must be used to get the routine.

The SAR file must include a bind file which may not be available at the
server. If the bind file cannot be found and stored in the SAR file, an
error is raised (SQLSTATE 55045).

38.3.4.2 PUT_ROUTINE_SAR

>>-PUT_ROUTINE_SAR---------------------------------------------->

>----(--sarblob--+-------------------------------------+--)----><
                 '-,--new_owner--,--use_register_flag--'


The schema is SYSFUN.

This procedure was first available in FixPak 3 of Version 7.1.

The PUT_ROUTINE_SAR procedure passes the necessary file to create an SQL
routine at the server and then defines the routine. The invoker of the
PUT_ROUTINE_SAR procedure must have DBADM authority.

sarblob
     An input argument of type BLOB(3M) that contains the routine SAR file
     contents.

new_owner
     An input argument of type VARCHAR(128) that contains an
     authorization-name used for authorization checking of the routine. The
     new-owner must have the necessary privileges for the routine to be
     defined. If new-owner is not specified, the authorization-name of the
     original routine definer is used.

use_register_flag
     An input argument of type INTEGER that indicates whether or not the
     CURRENT SCHEMA and CURRENT PATH special registers are used to define
     the routine. If the special registers are not used, the settings for
     the default schema and SQL path are the settings used when the routine
     was originally defined. Possible values for use-register-flag:

     0
          Do not use the special registers of the current environment

     1
          Use the CURRENT SCHEMA and CURRENT PATH special registers.

     If the value is 1, CURRENT SCHEMA is used for unqualified object names
     in the routine definition (including the name of the routine) and
     CURRENT PATH is used to resolve unqualified routines and data types in
     the routine definition. If the use-registers-flag is not specified,
     the behavior is the same as if a value of 0 was specified.

The identification information contained in sarblob is checked to confirm
that the inputs are appropriate for the environment, otherwise an error is
raised (SQLSTATE 55046). The PUT_ROUTINE_SAR procedure then uses the
contents of the sarblob to define the routine at the server.

The contents of the sarblob argument are extracted into the separate files
that make up the SQL archive file. The shared library and bind files are
written to files in a temporary directory. The environment is set so that
the routine definition statement processing is aware that compiling and
linking are not required, and that the location of the shared library and
bind files is available. The contents of the DDL file are then used to
dynamically execute the routine definition statement.

Notes:
     No more than one procedure can be concurrently installed under a given
     schema.

Processing of this statement may result in the same errors as executing the
routine definition statement using other interfaces. During routine
definition processing, the presence of the shared library and bind files is
noted and the precompile, compile and link steps are skipped. The bind file
is used during bind processing and the contents of both files are copied to
the usual directory for an SQL routine.

Notes:
     If a GET ROUTINE or a PUT ROUTINE operation (or their corresponding
     procedure) fails to execute successfully, it will always return an
     error (SQLSTATE 38000), along with diagnostic text providing
     information about the cause of the failure. For example, if the
     procedure name provided to GET ROUTINE does not identify an SQL
     procedure, diagnostic "100, 02000" text will be returned, where "100"
     and "02000" are the SQLCODE and SQLSTATE, respectively, that identify
     the cause of the problem. The SQLCODE and SQLSTATE in this example
     indicate that the row specified for the given procedure name was not
     found in the catalog tables.

  ------------------------------------------------------------------------

38.4 Chapter 5. Queries

38.4.1 select-statement/syntax diagram

The syntax diagram changes to:

>>-+---------------------------------------+--fullselect-------->
   |       .-,--------------------------.  |
   |       V                            |  |
   '-WITH-----common-table-expression---+--'

>----+-----------------+--+--------------------+---------------->
     '-order-by-clause-'  '-fetch-first-clause-'

>----*--+---------------------+--*--+---------------------+--*-->
        +-read-only-clause----+     '-optimize-for-clause-'
        |               (1)   |
        '-update-clause-------'

>-----+---------------+----------------------------------------><
      '-WITH--+-RR-+--'
              +-RS-+
              +-CS-+
              '-UR-'


Notes:

  1. The update-clause and the order-by-clause cannot both be specified in
     the same select-statement.

Add the following paragraph to the description below the syntax diagram:

     The optional WITH clause specifies the isolation level at which the
     select statement is executed.
        o RR - Repeatable Read
        o RS - Read Stability
        o CS - Cursor Stability
        o UR - Uncommitted Read

     The default isolation level of the statement is the isolation level of
     the package in which the statement is bound.

38.4.2 select-statement/fetch-first-clause

The last paragraph in the description of the fetch-first-clause:

   Specification of the fetch-first-clause in a select-statement
   makes the cursor not deletable (read-only). This clause
   cannot be specified with the FOR UPDATE clause.

is incorrect and should be removed.
  ------------------------------------------------------------------------

38.5 Chapter 6. SQL Statements

38.5.1 Update of the Partitioning Key Now Supported

Update the partitioning key is now supported. The following text from
various statements in Chapter 6 should be deleted only if the
DB2_UPDATE_PART_KEY=ON:

Notes:
     If DB2_UPDATE_PART_KEY=OFF, then the restrictions still apply.

38.5.1.1 Statement: ALTER TABLE

Rules

   * A partitioning key column of a table cannot be updated (SQLSTATE
     42997).
   * A nullable column of a partitioning key cannot be included as a
     foreign key column when the relationship is defined with ON DELETE SET
     NULL (SQLSTATE 42997).

38.5.1.2 Statement: CREATE TABLE

Rules

   * A partitioning key column of a table cannot be updated (SQLSTATE
     42997).
   * A nullable column of a partitioning key cannot be included as a
     foreign key column when the relationship is defined with ON DELETE SET
     NULL (SQLSTATE 42997).

38.5.1.3 Statement: DECLARE GLOBAL TEMPORARY TABLE PARTITIONING KEY
(column-name,...)

Notes:
     The partitioning key columns cannot be updated (SQLSTATE 42997).

38.5.1.4 Statement: UPDATE

Footnotes

   * 108 A column of a partitioning key is not updatable (SQLSTATE 42997).
     The row of data must be deleted and inserted to change columns in a
     partitioning key.

38.5.2 Larger Index Keys for Unicode Databases

38.5.2.1 ALTER TABLE

The length of variable length columns that are part of any index, including
primary and unique keys, defined when the registry variable
DB2_INDEX_2BYTEVARLEN was on, can be altered to a length greater than 255
bytes. The fact that a variable length column is involved in a foreign key
will no longer prevent the length of that column from being altered to
larger than 255 bytes, regardless of the registry variable setting.
However, data with length greater than 255 cannot be inserted into the
table unless the column in the corresponding primary key has length greater
than 255 bytes, which is only possible if the primary key was created with
the registry variable ON.

38.5.2.2 CREATE INDEX

Indexes can be defined on variable length columns whose length is greater
than 255 bytes if the registry variable DB2_INDEX_2BYTEVARLEN is ON.

38.5.2.3 CREATE TABLE

Primary and unique keys with variable keyparts can have a size greater than
255 if the registry variable DB2_INDEX_2BYTEVARLEN is ON. Foreign keys can
be defined on variable length columns whose length is greater than 255
bytes.

38.5.3 ALTER SEQUENCE

ALTER SEQUENCE

The ALTER SEQUENCE statement modifies the attributes of a sequence by:

   * Restarting the sequence
   * Changing the increment between future sequence values
   * Setting new minimum or maximum values
   * Changing the number of cached sequence numbers
   * Changing whether the sequence can cycle or not
   * Changing whether sequence numbers must be generated in order of
     request

¸I¾s

This statement can be embedded in an application program or issued through
the use of dynamic SQL statements. It is an executable statement that can
be dynamically prepared. However, if the bind option DYNAMICRULES BIND
applies, the statement cannot be dynamically prepared (SQLSTATE 42509).

Authorization

The privileges held by the authorization ID of the statement must include
at least one of the following:

   * Definer of the sequence
   * The ALTERIN privilege for the schema implicitly or explicitly
     specified
   * SYSADM or DBADM authority

Syntax

>>-ALTER SEQUENCE--sequence-name-------------------------------->

      .-------------------------------------------.
      V                                           |
>-------+-RESTART--+-------------------------+-+--+------------><
        |          '-WITH--numeric-constant--' |
        +-INCREMENT BY--numeric-constant-------+
        +-+-MINVALUE--numeric-constant--+------+
        | '-NO MINVALUE-----------------'      |
        +-+-MAXVALUE--numeric-constant--+------+
        | '-NO MAXVALUE-----------------'      |
        +-+-CYCLE----+-------------------------+
        | '-NO CYCLE-'                         |
        +-+-CACHE--integer-constant--+---------+
        | '-NO CACHE-----------------'         |
        '-+-ORDER----+-------------------------'
          '-NO ORDER-'


Description

sequence-name
     Identifies the particular sequence. The combination of name, and the
     implicit or explicit schema name must identify an existing sequence at
     the current server. If no sequence by this name exists in the
     explicitly or implicitly specified schema, an error (SQLSTATE 42704)
     is issued.

RESTART
     Restarts the sequence. If numeric-constant is not specified, the
     sequence is restarted at the value specified implicitly or explicitly
     as the starting value on the CREATE SEQUENCE statement that originally
     created the sequence.

     WITH numeric-constant
          Restarts the sequence with the specified value. This value can be
          any positive or negative value that could be assigned to a column
          of the data type associated with the sequence (SQLSTATE 42820) as
          long as there are no non-zero digits to the right of the decimal
          point (SQLSTATE 42894).

INCREMENT BY
     Specifies the interval between consecutive values of the sequence.
     This value can be any positive or negative value that could be
     assigned to a column of the data type associated with the sequence
     (SQLSTATE 42820), and does not exceed the value of a large integer
     constant (SQLSTATE 42815), without non-zero digits existing to the
     right of the decimal point (SQLSTATE 428FA).

     If this value is negative, then the sequence of values descends. If
     this value is positive, then the sequence of values ascends. If this
     value is 0 or greater than the range defined by MINVALUE and MAXVALUE,
     only one value will be generated, but the sequence is treated as an
     ascending sequence otherwise.

MINVALUE or NO MINVALUE
     Specifies the minimum value at which a descending sequence either
     cycles or stops generating values, or an ascending sequence cycles to
     after reaching the maximum value.

     MINVALUE numeric-constant
          Specifies the numeric constant that is the minimum value. This
          value can be any positive or negative value that could be
          assigned to a column of the data type associated with the
          sequence (SQLSTATE 42820), without non-zero digits existing to
          the right of the decimal point (SQLSTATE 428FA), but the value
          must be less than or equal to the maximum value (SQLSTATE 42815).

     NO MINVALUE
          For an ascending sequence, the value is the START WITH value, or
          1 if START WITH is not specified. For a descending sequence, the
          value is the minimum value of the data type associated with the
          sequence. This is the default.

MAXVALUE or NO MAXVALUE
     Specifies the maximum value at which an ascending sequence either
     cycles or stops generating values, or a descending sequence cycles to
     after reaching the minimum value.

     MAXVALUE numeric-constant
          Specifies the numeric constant that is the maximum value. This
          value can be any positive or negative value that could be
          assigned to a column of the data type associated with the
          sequence (SQLSTATE 428FA), without non-zero digits existing to
          the right of the decimal point (SQLSTATE 428FA), but the value
          must be greater than or equal to the minimum value (SQLSTATE
          42815).

     NO MAXVALUE
          For an ascending sequence, the value is the maximum value of the
          data type associated with the sequence. For a descending
          sequence, the value is the START WITH value, or -1 if START WITH
          is not specified. This is the default.

CYCLE or NOCYCLE
     Specifies whether the sequence should continue to generate values
     after reaching either its maximum or minimum value. The boundary of
     the sequence can be reached either with the next value landing exactly
     on the boundary condition, or by overshooting it in which case the
     next value would be determined from wrapping around to the START WITH
     value if cycles were permitted.

     CYCLE
          Specifies that values continue to be generated for this sequence
          after the maximum or minimum value has been reached. If this
          option is used, after an ascending sequence reaches its maximum
          value, it generates its minimum value; or after a descending
          sequence reaches its minimum value, it generates its maximum
          value. The maximum and minimum values for the sequence determine
          the range that is used for cycling.

          When CYCLE is in effect, then duplicate values can be generated
          for the sequence.

     NO CYCLE
          Specifies that values will not be generated for the sequence once
          the maximum or minimum value for the sequence has been reached.
          This is the default.

CACHE or NO CACHE
     Specifies whether to keep some preallocated values in memory for
     faster access. This is a performance and tuning option.

     CACHE integer-constant
          Specifies the maximum number of sequence values that are
          preallocated and kept in memory. Preallocating and storing values
          in the cache reduces synchronous I/O to the log when values are
          generated for the sequence.

          In the event of a system failure, all cached sequence values that
          have not been used in committed statements are lost (that is,
          they will never be used). The value specified for the CACHE
          option is the maximum number of sequence values that could be
          lost in case of system failure.

          The minimum value is 2 (SQLSTATE 42815). The default value is
          CACHE 20.

     NO CACHE
          Specifies that values of the sequence are not to be preallocated.
          It ensures that there is not a loss of values in the case of a
          system failure, shutdown or database deactivation. When this
          option is specified, the values of the sequence are not stored in
          the cache. In this case, every request for a new value for the
          sequence results in synchronous I/O to the log.

NO ORDER or ORDER
     Specifies whether the sequence numbers must be generated in order of
     request.

     ORDER
          Specifies that the sequence numbers are generated in order of
          request.

     NO ORDER
          Specifies that the sequence numbers do not need to be generated
          in order of request. This is the default.

After restarting a sequence or changing to CYCLE, it is possible for
sequence numbers to be duplicate values of ones generated by the sequence
previously.

Version

   * Only future sequence numbers are affected by the ALTER SEQUENCE
     statement.
   * The data type of a sequence cannot be changed. Instead, drop and
     recreate the sequence specifying the desired data type for the new
     sequence.
   * All cached values are lost when a sequence is altered.

Examples

Example 1: A possible reason for specifying RESTART without a numeric value
would be to reset the sequence to the START WITH value. In this example,
the goal is to generate the numbers from 1 up to the number of rows in the
table and then inserting the numbers into a column added to the table using
temporary tables. Another use would be to get results back where all the
resulting rows are numbered:

   ALTER SEQUENCE org_seq
   RESTART
   SELECT NEXTVAL for org_seq, org.*
      FROM org


38.5.4 ALTER TABLE

Changes to syntax fragments:

column-alteration

|--column-name-------------------------------------------------->

>-----+-SET--+-DATA TYPE--+-VARCHAR-----------+---(--integer--)--+-------+>
      |      |            +-CHARACTER VARYING-+                  |       |
      |      |            '-CHAR VARYING------'                  |       |
      |      '-EXPRESSION AS--(--generation-expression--)--------'       |
      +-ADD SCOPE--+-typed-table-name-+----------------------------------+
      |            '-typed-view-name--'                                  |
      '-+-| identity-alteration |--------------------------------------+-'
        '-SET GENERATED--+-ALWAYS-----+---+--------------------------+-'
                         '-BY DEFAULT-'   '-| identity-alteration |--'

>---------------------------------------------------------------|

identity-alteration

|---+-RESTART--+--------------------------+-+-------------------|
    |          '-WITH--numeric-constant---' |
    +-SET INCREMENT BY--numeric-constant----+
    |                    (1)                |
    +-SET--+-NO MINVALUE-----------------+--+
    |      '-MINVALUE--numeric-constant--'  |
    +-SET--+-NO MAXVALUE-----------------+--+
    |      '-MAXVALUE--numeric-constant--'  |
    +-SET--+-CYCLE----+---------------------+
    |      '-NO CYCLE-'                     |
    +-SET--+-NO CACHE-----------------+-----+
    |      '-CACHE--integer-constant--'     |
    '-SET--+-NO ORDER-+---------------------'
           '-ORDER----'


Notes:

  1. These parameters can be specified without spaces: NOMINVALUE,
     NOMAXVALUE, NOCYCLE, NOCACHE, and NOORDER. These single word versions
     are all acceptable alternatives to the two word versions.

Add the following parameters:

SET GENERATED
     Specifies whether values are to be generated for the column always or
     only when a default value is needed.

     ALWAYS
          A value will always be generated for the column when a row is
          inserted or updated in the table. The column must already be
          defined as a generated column (SQLSTATE 42837).

     BY DEFAULT
          The value will be generated for the column when a row is inserted
          into the table, unless a value is specified. The column must
          already be defined as a generated column (SQLSTATE 42837).

     RESTART or RESTART WITH numeric-constant
          Resets the state of the sequence associated with the identity
          column. If WITH numeric-constant is not specified, then the
          sequence for the identity column is restarted at the value that
          was specified, either implicitly or explicitly, as the starting
          value when the identity column was originally created. The
          numeric-constant is an exact numeric constant that can be any
          positive or negative value that could be assigned to this column
          (SQLSTATE 42820) as long as there are no non-zero digits to the
          right of the decimal point (SQLSTATE 42894). The column must
          already be defined with the IDENTITY attribute (SQLSTATE 42837).
          The numeric-constant will be used as the next value for the
          column.

     SET INCREMENT BY numeric-constant
          Specifies the interval between consecutive values of the identity
          column. The column must already be defined with the IDENTITY
          attribute (SQLSTATE 42837). This value is any positive or
          negative value that could be assigned to this column (SQLSTATE
          42820), and does not exceed the value of a large integer constant
          (SQLSTATE 42815), as long as there are no non-zero digits to the
          right of the decimal point (SQLSTATE 42894).

          If this value is negative, then the sequence of values for this
          identity column descends. If this value is positive, then the
          sequence of values for this identity column ascends. If this
          value is 0, or is greater than the range defined by MINVALUE and
          MAXVALUE, then DB2 will only generate one value, but the sequence
          is treated as an ascending sequence otherwise.

     SET MINVALUE numeric-constant or NO MINVALUE
          Specifies the minimum value at which a descending identity column
          either cycles or stops generating values, or the value to which
          an ascending identity column cycles to after reaching the maximum
          value. The column must already be defined with the IDENTITY
          attribute (SQLSTATE 42837).

          MINVALUE numeric-constant
               Specifies the minimum numeric constant value . This value
               can be any positive or negative value that could be assigned
               to this column (SQLSTATE 42820), without non-zero digits
               existing to the right of the decimal point (SQLSTATE 42894),
               but the value must be less than the maximum value (SQLSTATE
               42815).

          NO MINVALUE
               For an ascending sequence, the value is the START WITH
               value, or 1 if START WITH is not specified. For a descending
               sequence, the value is the minimum value of the data type of
               the column.

     SET MAXVALUE numeric-constant or NO MAXVALUE
          Specifies the maximum value at which an ascending identity column
          either cycles or stops generating values, or the value to which a
          descending identity column cycles to after reaching the minimum
          value. The column must already be defined with the IDENTITY
          attribute (SQLSTATE 42837).

          MAXVALUE numeric-constant
               Specifies the numeric constant that is the maximum value.
               This value can be any positive or negative value that could
               be assigned to this column (SQLSTATE 42820), without
               non-zero digits existing to the right of the decimal point
               (SQLSTATE 42894), but the value must be greater than the
               minimum value (SQLSTATE 42815).

          NO MAXVALUE
               For an ascending sequence, the value is the maximum value of
               the data type of the column. For a descending sequence, the
               value is the START WITH value, or -1 if START WITH is not
               specified.

     SET CYCLE or NO CYCLE
          Specifies whether this identity column should continue to
          generate values after generating either the maximum or minimum
          value. The column must already be defined with the IDENTITY
          attribute (SQLSTATE 42837).

          CYCLE
               Specifies that values continue to be generated for this
               column after the maximum or minimum value has been reached.
               If this option is used, then after an ascending identity
               column reaches the maximum value, it generates its minimum
               value; or after a descending sequence reaches the minimum
               value, it generates its maximum value. The maximum and
               minimum values for the identity column determine the range
               that is used for cycling.

               When CYCLE is in effect, then duplicate values can be
               generated for an identity column. Although not required, if
               unique values are desired, a single-column unique index
               defined using the identity column will ensure uniqueness. If
               a unique index exists on such an identity column and a
               non-unique value is generated, then an error occurs
               (SQLSTATE 23505).

          NO CYCLE
               Specifies that values will not be generated for the identity
               column once the maximum or minimum value has been reached.

     SET CACHE integer-constant or NO CACHE
          Specifies whether to keep some preallocated values in memory for
          faster access. This is a performance and tuning option. The
          column must already be defined with the IDENTITY attribute
          (SQLSTATE 42837).

          CACHE integer-constant
               Specifies how many values of the identity sequence are
               preallocated and kept in memory. When values are generated
               for the identity column, preallocating and storing values in
               the cache reduces synchronous I/O to the log.

               If a new value is needed for the identity column and there
               are no unused values available in the cache, then the
               allocation of the value requires waiting for I/O to the log.
               However, when a new value is needed for the identity column
               and there is an unused value in the cache, the allocation of
               that identity value can happen more quickly by avoiding the
               I/O to the log.

               When a database manager is stopped (database deactivation,
               system failure, or shutdown, for example), all cached
               sequence values that have not been used in committed
               statements are lost (that is, they will never be used). The
               value specified for the CACHE option is the maximum number
               of values for the identity column that could be lost in case
               of system failure.

               The minimum value is 2 (SQLSTATE 42615).

          NO CACHE
               Specifies that values for the identity column are not to be
               preallocated.

               When this option is specified, the values of the identity
               column are not stored in the cache. In this case, every
               request for a new identity value results in synchronous I/O
               to the log.

     SET ORDER or NO ORDER
          Specifies whether the identity column values must be generated in
          order of request. The column must already be defined with the
          IDENTITY attribute (SQLSTATE 42837).

          ORDER
               Specifies that the identity column values are generated in
               order of request.

          NO ORDER
               Specifies that the identity column values do not need to be
               generated in order of request.

38.5.5 Compound SQL (Embedded)

A prepared COMMIT statement is not allowed in an ATOMIC compound SQL
statement.

38.5.6 Compound Statement (Dynamic)

Compound Statement (Dynamic)

A compound statement groups other statements together into an executable
block. You can declare SQL variables within a dynamically prepared atomic
compound statement.

Invocation

This statement can be embedded in a trigger, SQL Function, or SQL Method,
or issued through the use of dynamic SQL statements. It is an executable
statement that can be dynamically prepared.

Authorization

No privileges are required to invoke a dynamic compound statement. However,
the authorization ID of the compound statement must hold the necessary
privileges to invoke the SQL statements embedded in the compound statement.

Syntax

dynamic-compound-statement

>>-+--------------+--BEGIN ATOMIC------------------------------->
   |        (1)   |
   '-label:-------'

>-----+-----------------------------------------------+--------->
      |  .-----------------------------------------.  |
      |  V                                         |  |
      '-----+-| SQL-variable-declaration |-+---;---+--'
            '-| condition-declaration |----'

      .-,-----------------------------.
      V                               |
>--------SQL-procedure-statement--;---+---END--+--------+------><
                                               '-label--'

SQL-variable-declaration

               .-,--------------------.
               V                      |
|---DECLARE-------SQL-variable-name---+--data-type-------------->

      .-DEFAULT NULL-------------.
>-----+--------------------------+------------------------------|
      '-DEFAULT--default-values--'

condition-declaration

|---DECLARE--condition-name--CONDITION--FOR--------------------->

                 .-VALUE-.
     .-SQLSTATE--+-------+---.
>----+-----------------------+---string-constant----------------|


Notes:

  1. A label can only be specified when the statement is in a function,
     method, or trigger definition.

Description

label
     Defines the label for the code block. If the beginning label is
     specified, it can be used to qualify SQL variables declared in the
     dynamic compound statement and can also be specified on a LEAVE
     statement. If the ending label is specified, it must be the same as
     the beginning label.

ATOMIC
     ATOMIC indicates that, if an error occurs in the compound statement,
     all SQL statements in the compound statement will be rolled back and
     any remaining SQL statements in the compound statement are not
     processed.

SQL-procedure-statement
     The following list of SQL-control-statements can be used within the
     dynamic compound statement:
        o FOR Statement
        o GET DIAGNOSTICS Statement
        o IF Statement
        o ITERATE Statement
        o LEAVE Statement
        o SIGNAL Statement
        o WHILE Statement

     The SQL statements that can be issued are:
        o fullselect 6
        o Searched UPDATE
        o Searched DELETE
        o INSERT
        o SET variable statement

SQL-variable-declaration
     Declares a variable that is local to the dynamic compound statement.

     SQL-variable-name
          Defines the name of a local variable. DB2 converts all SQL
          variable names to uppercase. The name cannot:
             + Be the same as another SQL variable within the same compound
               statement.
             + Be the same as a parameter name.
             + Be the same as column names.

          If an SQL statement contains an identifier with the same name as
          an SQL variable and a column reference, DB2 interprets the
          identifier as a column.

     data-type
          Specifies the data type of the variable.

     DEFAULT default-values or NULL
          Defines the default for the SQL variable. The variable is
          initialized when the dynamic compound statement is called. If a
          default value is not specified, the variable is initialized to
          NULL.

condition-declaration
     Declares a condition name and corresponding SQLSTATE value.

     condition-name
          Specifies the name of the condition. The condition name must be
          unique within the procedure body and can be referenced only
          within the compound statement in which it is declared.

     FOR SQLSTATE string-constant
          Specifies the SQLSTATE associated with the condition. The
          string-constant must be specified as five characters enclosed in
          single quotes, and cannot be '00000'.

Version

   * Dynamic compound statements are compiled by DB2 as one single
     statement. This statement is effective for short scripts involving
     little control flow logic but significant data flow. For larger
     constructs with nested complex control flow, a better choice is to use
     SQL procedures for details on using SQL procedures.

38.5.7 CREATE FUNCTION (Source or Template)

The syntax diagram changes to the following

>>-CREATE FUNCTION--function-name------------------------------->

>----(--+------------------------------------------+---)---*---->
        |  .-,----------------------------------.  |
        |  V                                    |  |
        '----+-----------------+---data-type1---+--'
             '-parameter-name--'

>----RETURNS--data-type2---*----+--------------------------+---->
                                '-SPECIFIC--specific-name--'

>----*---------------------------------------------------------->

>-----+-SOURCE--+-function-name--------------------------------+------------------+>
      |         +-SPECIFIC--specific-name----------------------+                  |
      |         '-function-name--(--+-------------------+---)--'                  |
      |                             |  .-,-----------.  |                         |
      |                             |  V             |  |                         |
      |                             '----data-type---+--'                         |
      |                   .-NOT DETERMINISTIC--.       .-EXTERNAL ACTION----.     |
      '-AS TEMPLATE--*----+--------------------+--*----+--------------------+--*--'
                          '-DETERMINISTIC------'       '-NO EXTERNAL ACTION-'

>----*---------------------------------------------------------><


Add the following to the "Description" section:

DETERMINISTIC  or  NOT DETERMINISTIC
     This optional clause specifies whether the function always returns the
     same results for given argument values (DETERMINISTIC) or whether the
     function depends on some state values that affect the results (NOT
     DETERMINISTIC). That is, a DETERMINISTIC function must always return
     the same table from successive invocations with identical inputs.
     Optimizations taking advantage of the fact that identical inputs
     always produce the same results are prevented by specifying NOT
     DETERMINISTIC.

     NOT DETERMINISTIC must be explicitly or implicitly specified if the
     body of the function accesses a special register or calls another
     non-deterministic function (SQLSTATE 428C2).

NO EXTERNAL ACTION  or  EXTERNAL ACTION
     This optional clause specifies whether or not the function takes some
     action that changes the state of an object not managed by the database
     manager. By specifying NO EXTERNAL ACTION, the system can use certain
     optimizations that assume functions have no external impacts.

     EXTERNAL ACTION must be explicitly or implicitly specified if the body
     of the function calls another function that has an external action
     (SQLSTATE 428C2).

38.5.8 CREATE FUNCTION (SQL Scalar, Table or Row)

The syntax diagram changes to:

>>-CREATE FUNCTION--function-name------------------------------->

>----(--+------------------------------------+---)---*---------->
        |  .-,----------------------------.  |
        |  V                              |  |
        '----parameter-name--data-type1---+--'

>----RETURNS--+-data-type2--------------------+--*-------------->
              '--+-ROW---+---| column-list |--'
                 '-TABLE-'

                                         .-LANGUAGE SQL--.
>-----+--------------------------+--*----+---------------+--*--->
      '-SPECIFIC--specific-name--'

      .-NOT DETERMINISTIC--.       .-EXTERNAL ACTION----.
>-----+--------------------+--*----+--------------------+--*---->
      '-DETERMINISTIC------'       '-NO EXTERNAL ACTION-'

      .-READS SQL DATA--.       .-STATIC DISPATCH--.
>-----+-----------------+--*----+------------------+--*--------->
      '-CONTAINS SQL----'

                              (1)
      .-CALLED ON NULL INPUT-------.
>-----+----------------------------+--*------------------------->

>-----+-----------------------------------------------------+--->
      |                                               (2)   |
      '-PREDICATES--(--| predicate-specification |--)-------'

>----| SQL-function-body |-------------------------------------><

column-list

       .-,--------------------------.
       V                            |
|---(-----column-name--data-type3---+---)-----------------------|

SQL-function-body

|---+-RETURN Statement-----------+------------------------------|
    '-dynamic-compound-statement-'


Notes:

  1. NULL CALL may be specified in place of CALLED ON NULL INPUT

  2. Valid only if RETURNS specifies a scalar result (data-type2)

Change the following parameters:

LANGUAGE SQL
     Specifies that the function is written using SQL.

This parameter section replaces the "RETURN expression, NULL, WITH
common-table-expression, fullselect" parameter section.

SQL-function-body
     Specifies the body of the function. Parameter names can be referenced
     in the SQL-function-body. Parameter names may be qualified with the
     function name to avoid ambiguous references.

     If the SQL-function-body is a dynamic compound statement, it must
     contain at least one RETURN statement and a RETURN statement must be
     executed when the function is called (SQLSTATE 42632). If the function
     is a table or row function, then it can contain only one RETURN
     statement which must be the last statement in the dynamic compound
     (SQLSTATE 429BD).

     For additional details, see Compound Statement (Dynamic) and RETURN.

38.5.9 CREATE METHOD

The syntax diagram changes to:

CREATE METHOD

Syntax

>>-CREATE------------------------------------------------------->

>-----+-METHOD--+-method-name----------+---FOR--type-name--+---->
      |         '-| method-signature |-'                   |
      '-SPECIFIC METHOD--specific-name---------------------'

>-----+-*----EXTERNAL--+-----------------------+--*----+------------------------------+--*--+>
      |                '-NAME--+-'string'---+--'       '-TRANSFORM GROUP--group-name--'     |
      |                        '-identifier-'                                               |
      '-| SQL-method-body |-----------------------------------------------------------------'

>--------------------------------------------------------------><

method-signature

|---method-name--(--+---------------------------------------------------------+---)-->
                    |  .-,--------------------------------------------------. |
                    |  V                                                    | |
                    '----+-----------------+---data-type1--+-------------+--+-'
                         '-parameter-name--'               '-AS LOCATOR--'

>----+------------------------------------------------------------------+->
     '-RETURNS--+-data-type2--+-------------+------------------------+--'
                |             '-AS LOCATOR--'                        |
                '-data-type3--CAST FROM--data-type4--+-------------+-'
                                                     '-AS LOCATOR--'

>---------------------------------------------------------------|

SQL-method-body

|---+-RETURN Statement-----------+------------------------------|
    '-dynamic-compound-statement-'


The following parameters replace the "RETURN scalar-expression or NULL"
section:

SQL-method-body
     The SQL-method-body defines the how the method is implemented if the
     method specification in CREATE TYPE is LANGUAGE SQL.

     The SQL-method-body must comply with the following parts of the method
     specification:
        o DETERMINISTIC or NOT DETERMINISTIC (SQLSTATE 428C2)
        o EXTERNAL ACTION or NO EXTERNAL ACTION (SQLSTATE 428C2)
        o CONTAINS SQL or READS SQL DATA (SQLSTATE 42985)

     Parameter names can be referenced in the SQL-method-body. The subject
     of the method is passed to the method implementation as an implicit
     first parameter named SELF.

     For additional details, see Compound Statement (Dynamic) and RETURN.

38.5.10 CREATE SEQUENCE

CREATE SEQUENCE

The CREATE SEQUENCE statement creates a sequence at the application server.

Invocation

This statement can be embedded in an application program or issued through
the use of dynamic SQL statements. It is an executable statement that can
be dynamically prepared. However, if the bind option DYNAMICRULES BIND
applies, the statement cannot be dynamically prepared (SQLSTATE 42509).

Authorization

The privileges held by the authorization ID of the statement must include
at least one of the following:

   * CREATEIN privilege for the implicitly or explicitly specified schema
   * SYSADM or DBADM authority

Syntax

                                         .-AS INTEGER-----.
>>-CREATE SEQUENCE--sequence-name---*----+----------------+--*-->
                                         '-AS--data-type--'

>-----+-------------------------------+--*---------------------->
      '-START WITH--numeric-constant--'

      .-INCREMENT BY 1------------------.
>-----+---------------------------------+--*-------------------->
      '-INCREMENT BY--numeric-constant--'

                    (1)
      .-NO MINVALUE-----------------.
>-----+-----------------------------+--*------------------------>
      '-MINVALUE--numeric-constant--'

      .-NO MAXVALUE-----------------.       .-NO CYCLE--.
>-----+-----------------------------+--*----+-----------+--*---->
      '-MAXVALUE--numeric-constant--'       '-CYCLE-----'

      .-CACHE 20-----------------.       .-NO ORDER--.
>-----+--------------------------+--*----+-----------+--*------><
      +-CACHE--integer-constant--+       '-ORDER-----'
      '-NO CACHE-----------------'


Notes:

  1. These parameters can be specified without spaces: NOMINVALUE,
     NOMAXVALUE, NOCYCLE, NOCACHE, and NOORDER. These single word versions
     are all acceptable alternatives to the two word versions.

Description

sequence-name
     Names the sequence. The combination of name, and the implicit or
     explicit schema name must not identify an existing sequence at the
     current server (SQLSTATE 42710).

     The unqualified form of sequence-name is an SQL identifier. The
     qualified form is a qualifier followed by a period and an SQL
     identifier. The qualifier is a schema name.

     If the sequence name is explicitly qualified with a schema name, the
     schema name cannot begin with 'SYS' or an error (SQLSTATE 42939) is
     raised.

AS data-type
     Specifies the data type to be used for the sequence value. The data
     type can be any exact numeric type (SMALLINT, INTEGER, BIGINT or
     DECIMAL) with a scale of zero or a user-defined distinct type for
     which the source type is an exact numeric type with a scale of zero
     (SQLSTATE 42815). The default is INTEGER.

START WITH numeric-constant
     Specifies the first value for the sequence. This value can be any
     positive or negative value that could be assigned to a column of the
     data type associated with the sequence (SQLSTATE 42820), without
     non-zero digits existing to the right of the decimal point (SQLSTATE
     428FA). The default is MINVALUE for ascending sequences and MAXVALUE
     for descending sequences.

     This value is not necessarily the value that a sequence would cycle to
     after reaching the maximum or minimum value of the sequence. The START
     WITH clause can be used to start a sequence outside the range that is
     used for cycles. The range used for cycles is defined by MINVALUE and
     MAXVALUE.

INCREMENT BY numeric-constant
     Specifies the interval between consecutive values of the sequence.
     This value can be any positive or negative value that could be
     assigned to a column of the data type associated with the sequence
     (SQLSTATE 42820), and does not exceed the value of a large integer
     constant (SQLSTATE 42815), without non-zero digits existing to the
     right of the decimal point (SQLSTATE 428FA).

     If this value is negative, then the sequence of values descends. If
     this value is positive, then the sequence of values ascends. If this
     value is 0 or greater than the range defined by MINVALUE and MAXVALUE,
     only one value will be generated, but the sequence is treated as an
     ascending sequence otherwise. The default is 1.

MINVALUE or NO MINVALUE
     Specifies the minimum value at which a descending sequence either
     cycles or stops generating values, or an ascending sequence cycles to
     after reaching the maximum value.

     MINVALUE numeric-constant
          Specifies the numeric constant that is the minimum value. This
          value can be any positive or negative value that could be
          assigned to a column of the data type associated with the
          sequence (SQLSTATE 42820), without non-zero digits existing to
          the right of the decimal point (SQLSTATE 428FA), but the value
          must be less than or equal to the maximum value (SQLSTATE 42815).

     NO MINVALUE
          For an ascending sequence, the value is the START WITH value, or
          1 if START WITH is not specified. For a descending sequence, the
          value is the minimum value of the data type associated with the
          sequence. This is the default.

MAXVALUE or NO MAXVALUE
     Specifies the maximum value at which an ascending sequence either
     cycles or stops generating values, or a descending sequence cycles to
     after reaching the minimum value.

     MAXVALUE numeric-constant
          Specifies the numeric constant that is the maximum value. This
          value can be any positive or negative value that could be
          assigned to a column of the data type associated with the
          sequence (SQLSTATE 428FA), without non-zero digits existing to
          the right of the decimal point (SQLSTATE 428FA), but the value
          must be greater than or equal to the minimum value (SQLSTATE
          42815).

     NO MAXVALUE
          For an ascending sequence, the value is the maximum value of the
          data type associated with the sequence. For a descending
          sequence, the value is the START WITH value, or -1 if START WITH
          is not specified. This is the default.

CYCLE or NO CYCLE
     Specifies whether the sequence should continue to generate values
     after reaching either its maximum or minimum value. The boundary of
     the sequence can be reached either with the next value landing exactly
     on the boundary condition, or by overshooting it.

     CYCLE
          Specifies that values continue to be generated for this sequence
          after the maximum or minimum value has been reached. If this
          option is used, after an ascending sequence reaches its maximum
          value it generates its minimum value; after a descending sequence
          reaches its minimum value it generates its maximum value. The
          maximum and minimum values for the sequence determine the range
          that is used for cycling.

          When CYCLE is in effect, then duplicate values can be generated
          for the sequence.

     NO CYCLE
          Specifies that values will not be generated for the sequence once
          the maximum or minimum value for the sequence has been reached.
          This is the default.

CACHE or NO CACHE
     Specifies whether to keep some preallocated values in memory for
     faster access. This is a performance and tuning option.

     CACHE integer-constant
          Specifies the maximum number of sequence values that are
          preallocated and kept in memory. Preallocating and storing values
          in the cache reduces synchronous I/O to the log when values are
          generated for the sequence.

          In the event of a system failure, all cached sequence values that
          have not been used in committed statements are lost (that is,
          they will never be used). The value specified for the CACHE
          option is the maximum number of sequence values that could be
          lost in case of system failure.

          The minimum value is 2 (SQLSTATE 42815). The default value is
          CACHE 20.

     NO CACHE
          Specifies that values of the sequence are not to be preallocated.
          It ensures that there is not a loss of values in the case of a
          system failure, shutdown or database deactivation. When this
          option is specified, the values of the sequence are not stored in
          the cache. In this case, every request for a new value for the
          sequence results in synchronous I/O to the log.

NO ORDER or ORDER
     Specifies whether the sequence numbers must be generated in order of
     request.

     ORDER
          Specifies that the sequence numbers are generated in order of
          request.

     NO ORDER
          Specifies that the sequence numbers do not need to be generated
          in order of request. This is the default.

Version

   * It is possible to define a constant sequence, that is, one that would
     always return a constant value. This could be done by specifying the
     same value for MINVALUE or MAXVALUE, or by specifying an INCREMENT
     value of zero. In either case, in order to allow for NEXTVAL to
     generate the same value more than once, CYCLE must be specified. A
     constant sequence can be used as a numeric global variable. ALTER
     SEQUENCE can be used to adjust the values that will be generated for a
     constant sequence.
   * A sequence can be cycled manually, by using the ALTER SEQUENCE
     statement. If NO CYCLE is implicitly or explicitly specified, the
     sequence can be restarted or extended using the ALTER SEQUENCE
     statement to cause values to continue to be generated once the maximum
     or minimum value for the sequence has been reached.
   * Caching sequence numbers implies that a range of sequence numbers can
     be kept in memory for fast access. When an application accesses a
     sequence that can allocate the next sequence number from the cache,
     the sequence number allocation can happen quickly. However, if an
     application accesses a sequence that cannot allocate the next sequence
     number from the cache, the sequence number allocation may require
     having to wait for I/O operations to persistent storage. The choice of
     the value for CACHE should be done keeping in mind the performance and
     application requirements tradeoffs.
   * The owner has the ALTER and USAGE privileges on the new sequence. Only
     the USAGE privilege can be granted by the owner and only to PUBLIC.
   * The following syntax is also supported: NOMINVALUE, NOMAXVALUE,
     NOCYCLE, NOCACHE, and NOORDER.

Examples

Example 1: Create a sequence called org_seq:

   CREATE SEQUENCE org_seq
      START WITH 1
      INCREMENT BY 1
      NO MAXVALUE
      NO CYCLE
      CACHE 24

38.5.11 CREATE TRIGGER

CREATE TRIGGER

Syntax

>>-CREATE TRIGGER--trigger-name----+-NO CASCADE BEFORE-+-------->
                                   '-AFTER-------------'

>-----+-INSERT-----------------------------+--ON--table-name---->
      +-DELETE-----------------------------+
      '-UPDATE--+------------------------+-'
                |    .-,--------------.  |
                |    V                |  |
                '-OF----column-name---+--'

>-----+----------------------------------------------------------------------+>
      |              .----------------------------------------------------.  |
      |              V   (1)    (2)          .-AS-.                       |  |
      '-REFERENCING-------------------+-OLD--+----+--correlation-name--+--+--'
                                      |     .-AS-.                     |
                                      +-NEW-+----+--correlation-name---+
                                      |           .-AS-.               |
                                      +-OLD_TABLE-+----+--identifier---+
                                      |           .-AS-.               |
                                      '-NEW_TABLE-+----+--identifier---'

>-----+-FOR EACH ROW---------------+--MODE DB2SQL--------------->
      |  (3)                       |
      '--------FOR EACH STATEMENT--'

>-----| triggered-action |-------------------------------------><

triggered-action

|--+-------------------------------+--SQL-procedure-statement---|
   '-WHEN--(--search-condition--)--'


Notes:

  1. OLD and NEW may only be specified once each.

  2. OLD_TABLE and NEW_TABLE may only be specified once each and only for
     AFTER triggers.

  3. FOR EACH STATEMENT may not be specified for BEFORE triggers.

Replace the description of "triggered-action" with the following:

triggered-action
     Specifies the action to be performed when a trigger is activated. A
     triggered-action is composed of an SQL-procedure-statement and an
     optional condition for the execution of the SQL-procedure-statement.

WHEN (search-condition)
     Specifies a condition that is true, false, or unknown. The
     search-condition provides a capability to determine whether or not a
     certain triggered action should be executed.

     The associated action is performed only if the specified search
     condition evaluates as true. If the WHEN clause is omitted, the
     associated SQL-procedure statement is always performed.

SQL-procedure-statement
     The SQL-procedure-statement can contain a dynamic compound statement
     or any of the SQL control statements listed in Compound Statement
     (Dynamic).

     If the trigger is a BEFORE trigger, then an SQL-procedure-statement
     can also include a fullselect or a SET variable statement (SQLSTATE
     42987).

     If the trigger is an AFTER trigger, then an SQL-procedure-statement
     can also include one of the following (SQLSTATE 42987):
        o an INSERT SQL statement
        o a searched UPDATE SQL statement
        o a searched DELETE SQL statement
        o a SET variable statement
        o a fullselect 7

     The SQL-procedure-statement cannot reference an undefined transition
     variable (SQLSTATE 42703) or a declared temporary table (SQLSTATE
     42995).

     The SQL-procedure-statement in a BEFORE trigger cannot reference a
     summary table defined with REFRESH IMMEDIATE (SQLSTATE 42997).

     The SQL-procedure-statement in a BEFORE trigger cannot reference a
     generated column, other than the identity column, in the new
     transition variable (SQLSTATE 42989).

The Notes section changes to the following:

   * The result of a fullselect specified in the SQL-procedure-statement is
     not available inside or outside of the trigger.
   * Inoperative triggers:  An inoperative trigger is a trigger that is no
     longer available and is therefore never activated.

     A trigger becomes inoperative if:
        o A privilege that the creator of the trigger is required to have
          for the trigger to execute is revoked.
        o An object such as a table, view or alias, upon which the
          triggered action is dependent, is dropped.
        o A view, upon which the triggered action is dependent, becomes
          inoperative.
        o An alias that is the subject table of the trigger is dropped.

     In practical terms, an inoperative trigger is one in which a trigger
     definition has been dropped as a result of cascading rules for DROP or
     REVOKE statements. For example, when an view is dropped, any trigger
     with an SQL-procedure-statement defined using that view is made
     inoperative.

     When a trigger is made inoperative, all packages with statements
     performing operations that were activating the trigger will be marked
     invalid. When the package is rebound (explicitly or implicitly) the
     inoperative trigger is completely ignored. Similarly, applications
     with dynamic SQL statements performing operations that were activating
     the trigger will also completely ignore any inoperative triggers.

     The trigger name can still be specified in the DROP TRIGGER and
     COMMENT ON TRIGGER statements.

     An inoperative trigger may be recreated by issuing a CREATE TRIGGER
     statement using the definition text of the inoperative trigger. This
     trigger definition text is stored in the TEXT column of
     SYSCAT.TRIGGERS. Note that there is no need to explicitly drop the
     inoperative trigger in order to recreate it. Issuing a CREATE TRIGGER
     statement with the same trigger-name as an inoperative trigger will
     cause that inoperative trigger to be replaced with a warning (SQLSTATE
     01595).

     Inoperative triggers are indicated by an X in the VALID column of the
     SYSCAT.TRIGGERS catalog view.
   * Errors executing triggers:  Errors that occur during the execution of
     triggered SQL statements are returned using SQLSTATE 09000 unless the
     error is considered severe.

     If the error is severe, the severe error SQLSTATE is returned. The
     SQLERRMC field of the SQLCA for non-severe error will include the
     trigger name, SQLCODE, SQLSTATE and as many tokens as will fit from
     the tokens of the failure.

     The SQL-procedure-statement could include a SIGNAL SQLSTATE statement
     or contain a RAISE_ERROR function. In both these cases, the SQLSTATE
     returned is the one specified in the SIGNAL SQLSTATE statement or the
     RAISE_ERROR condition.

38.5.12 CREATE WRAPPER

Linux uses libraries called LIBDRDA.SO and LIBSQLNET.SO, not LIBDRDA.A and
LIBSQLNET.A.

38.5.13 DECLARE CURSOR

Within the "DECLARE CURSOR" statement, near the end of the Notes section
the following sentence should be changed from:

An ambiguous cursor is considered read-only if the BLOCKING bind option is
ALL, otherwise it is considered deletable.

to:

An ambiguous cursor is considered read-only if the BLOCKING bind option is
ALL; otherwise, it is considered updatable.

The change is from the word "deletable" to the word "updatable".

38.5.14 DELETE

The searched DELETE syntax diagram changes to the following:

>>-DELETE FROM----+-table-name-------------------+-------------->
                  +-view-name--------------------+
                  '-ONLY--(--+-table-name-+---)--'
                             '-view-name--'

>-----+---------------------------+----------------------------->
      | .-AS-.                    |
      '-+----+--correlation-name--'

>-----+--------------------------+---+---------------+---------><
      '-WHERE--search-condition--'   '-WITH--+-RR-+--'
                                             +-RS-+
                                             +-CS-+
                                             '-UR-'


Positioned DELETE:

>>-DELETE FROM----+-table-name-------------------+-------------->
                  +-view-name--------------------+
                  '-ONLY--(--+-table-name-+---)--'
                             '-view-name--'

>----WHERE CURRENT OF--cursor-name-----------------------------><


Add the following to the description section:

WITH
     Specifies the isolation level used when locating the rows to be
     deleted.

     RR
          Repeatable Read

     RS
          Read Stability

     CS
          Cursor Stability

     UR
          Uncommitted Read

     The default isolation level of the statement is the isolation level of
     the package in which the statement is bound.

38.5.15 DROP

Add the following option:

>>-SEQUENCE--sequence-name--RESTRICT---------------------------><


Add the following parameters:

SEQUENCE sequence-name RESTRICT

     Identifies the particular sequence that is to be dropped. The
     sequence-name, along with the implicit or explicit schema name, must
     identify an existing sequence at the current server. If no sequence by
     this name exists in the explicitly or implicitly specified schema, an
     error (SQLSTATE 42704) is raised.

     The RESTRICT keyword enforces the rule that the sequence is not
     dropped if the definition of a table column refers to the sequence
     (through an IDENTITY column).

Notes:
        o System created sequences for IDENTITY columns cannot be dropped
          using the DROP sequence command.
        o When a sequence is dropped, all privileges on the sequence are
          also dropped.

The table showing the dependencies that objects have on each other (Table
27) needs to be updated as follows:

New row: DROP SEQUENCE The entry at the intersection of the new row "DROP
SEQUENCE" and the column "PACKAGE" will be an "A". The rest of the entries
in this new row will be "-"

38.5.16 GRANT (Sequence Privileges)

GRANT (Sequence Privileges)

This form of the GRANT statement grants privileges on a user-defined
sequence.

Invocation

This statement can be embedded in an application program or issued through
the use of dynamic SQL statements. It is an executable statement that can
be dynamically prepared. However, if the bind option DYNAMICRULES BIND
applies, the statement cannot be dynamically prepared (SQLSTATE 42509).

Authorization

The privileges held by the authorization ID of the statement must include
at least one of the following:

   * Owner of the sequence
   * SYSADM or DBADM authority

Syntax

>>-GRANT--USAGE--ON SEQUENCE--sequence-name--TO PUBLIC---------><


Description

USAGE
     Grants the USAGE privilege for a sequence.

ON SEQUENCE sequence-name
     Identifies the sequence on which the USAGE privilege is to be granted.
     The sequence-name, including the implicit or explicit schema
     qualifier, must uniquely identify an existing sequence at the current
     server. If no sequence by this name exists in the specified schema, an
     error (SQLSTATE 42704) is raised.

TO PUBLIC
     Grants the USAGE privilege to all users.

Examples

Example 1:  Grant any user the privilege on a sequence called MYNUM

   GRANT USAGE ON SEQUENCE MYNUM TO PUBLIC


38.5.17 INSERT

Syntax diagram changes to:

>>-INSERT INTO----+-table-name-+-------------------------------->
                  '-view-name--'

>-----+----------------------------+---------------------------->
      |    .-,--------------.      |
      |    V                |      |
      '-(-----column-name---+---)--'

                .-,------------------------------------.
                V                                      |
>-----+-VALUES------+-+-expression-+----------------+--+--------+>
      |             | +-NULL-------+                |           |
      |             | '-DEFAULT----'                |           |
      |             |    .-,-----------------.      |           |
      |             |    V                   |      |           |
      |             '-(------+-expression-+--+---)--'           |
      |                      +-NULL-------+                     |
      |                      '-DEFAULT----'                     |
      '-+---------------------------------------+---fullselect--'
        |       .-,--------------------------.  |
        |       V                            |  |
        '-WITH-----common-table-expression---+--'

>-----+---------------+----------------------------------------><
      '-WITH--+-RR-+--'
              +-RS-+
              +-CS-+
              '-UR-'


Add the following to the description section:

WITH
     Specifies the isolation level at which the fullselect is executed.

     RR
          Repeatable Read

     RS
          Read Stability

     CS
          Cursor Stability

     UR
          Uncommitted Read

     The default isolation level of the statement is the isolation level of
     the package in which the statement is bound.

38.5.18 SELECT INTO

The syntax diagram changes to:

                          .-,----------------.
                          V                  |
>>-select-clause--INTO-------host-variable---+--from-clause----->

>----+--------------+--+-----------------+--+---------------+--->
     '-where-clause-'  '-group-by-clause-'  '-having-clause-'

>-----+---------------+----------------------------------------><
      '-WITH--+-RR-+--'
              +-RS-+
              +-CS-+
              '-UR-'


Add the following to the description section:

WITH
     Specifies the isolation level at which the SELECT INTO statement is
     executed.

     RR
          Repeatable Read

     RS
          Read Stability

     CS
          Cursor Stability

     UR
          Uncommitted Read

     The default isolation level of the statement is the isolation level of
     the package in which the statement is bound.

38.5.19 SET ENCRYPTION PASSWORD

SET ENCRYPTION PASSWORD

The SET ENCRYPTION PASSWORD statement sets the password that will be used
by the encryption and decryption functions. The password is not tied to DB2
authentication, and is used for data encryption only.

This statement is not under transaction control.

Invocation

The statement can be embedded in an application program or issued
interactively. It is an executable statement that can be dynamically
prepared.

Authorization

No authorization is required to execute this statement.

Syntax

                             .-=-.
>>-SET--ENCRYPTION PASSWORD--+---+--+-host-variable---+--------><
                                    '-string-constant-'


Description

The ENCRYPTION PASSWORD can be used by the ENCRYPT, DECRYPT_BIN, and
DECRYPT_CHAR built-in functions for password based encryption. The length
must be between 6 and 127 inclusive. All characters must be specified in
the exact case intended as there is no conversion to uppercase characters.

host-variable
     A variable of type CHAR or VARCHAR. The length of the contents of the
     host-variable must be between 6 and 127 inclusive (SQLSTATE 428FC). It
     cannot be set to null. All characters must be specified in the exact
     case intended as there is no conversion to uppercase characters.

string-constant
     A character string constant. The length must be between 6 and 127
     inclusive (SQLSTATE 428FC).

Rules

   * The initial ENCRYPTION PASSWORD value is the empty string ('').
   * The host-variable or string-constant is transmitted to the database
     server using normal DB2 mechanisms.

Version

   * See 38.3.2.3, ENCRYPT and 38.3.2.2, DECRYPT_BIN and DECRYPT_CHAR for
     additional information on using this statement.

Examples

Example 1:  The following statement sets the ENCRYPTION PASSWORD.

   SET ENCRYPTION PASSWORD = 'bubbalu'

38.5.20 SET transition-variable

This section changes to the following:

SET Variable

The SET Variable statement assigns values to local variables or to new
transition variables. It is under transaction control.

Invocation

This statement can only be used as an SQL statement in either a dynamic
compound statement, trigger, SQL function or SQL method.

Authorization

To reference a transition variable, the privileges held by the
authorization ID of the trigger creator must include at least one of the
following:

   * UPDATE of the columns referenced on the left hand side of the
     assignment and SELECT for any columns referenced on the right hand
     side.
   * CONTROL privilege on the table (subject table of the trigger)
   * SYSADM or DBADM authority.

To execute this statement with a row-fullselect as the right hand side of
the assignment, the privileges held by the authorization ID of either the
trigger definer or the dynamic compound statement owner must also include
at least one of the following, for each table or view referenced:

   * SELECT privilege
   * CONTROL privilege
   * SYSADM or DBADM.

Syntax

>>-SET---------------------------------------------------------->

      .-,---------------------------------------------------------------------------------.
      V                                                                                   |
>--------+-| target-variable |--=--+-expression-+--------------------------------------+--+>
         |                         +-NULL-------+                                      |
         |                         '-DEFAULT----'                                      |
         |    .-,----------------------.               .-,--------------------.        |
         |    V                        |               V              (1)     |        |
         '-(-----| target-variable |---+---)--=--(--+----+-expression------+--+-+---)--'
                                                    |    +-NULL------------+    |
                                                    |    '-DEFAULT---------'    |
                                                    |                (2)        |
                                                    '-row-fullselect------------'

>--------------------------------------------------------------><

target-variable

|---+-SQL-variable-name--------+---+--------------------------+-|
    '-transition-variable-name-'   |  .--------------------.  |
                                   |  V                    |  |
                                   '----..attribute-name---+--'


Notes:

  1. The number of expressions, NULLs and DEFAULTs must match the number of
     target-variables.

  2. The number of columns in the select list must match the number of
     target-variables.

Description

target-variable
     Identifies the target variable of the assignment. A target-variable
     representing the same variable must not be specified more than once
     (SQLSTATE 42701).

     SQL-variable-name
          Identifies the SQL variable that is the assignment target. SQL
          variables must be declared before they are used. SQL variables
          can be defined in a dynamic compound statement.

     transition-variable-name
          Identifies the column to be updated in the transition row. A
          transition-variable-name must identify a column in the subject
          table of a trigger, optionally qualified by a correlation name
          that identifies the new value (SQLSTATE 42703).

     ..attribute name
          Specifies the attribute of a structured type that is set
          (referred to as an attribute assignment). The SQL-variable-nameor
          transition-variable-name specified must be defined with a
          user-defined structured type (SQLSTATE 428DP). The attribute-name
          must be an attribute of the structured type (SQLSTATE 42703). An
          assignment that does not involve the ..attribute name clause is
          referred to as a conventional assignment.

expression
     Indicates the new value of the target-variable. The expression is any
     expression of the type described in Chapter 2 of the SQL Reference.
     The expression can not include a column function except when it occurs
     within a scalar fullselect (SQLSTATE 42903). In the context of a
     CREATE TRIGGER statement, an expression may contain references to OLD
     and NEW transition variables and must be qualified by the
     correlation-name to specify which transition variable (SQLSTATE
     42702).

NULL
     Specifies the null value and can only be specified for nullable
     columns (SQLSTATE 23502). NULL cannot be the value in an attribute
     assignment (SQLSTATE 429B9), unless it was specifically cast to the
     data type of the attribute.

DEFAULT
     Specifies that the default value should be used.

     If target-variable is a column, the value inserted depends on how the
     column was defined in the table.
        o If the column was defined using the WITH DEFAULT clause, then the
          value is set to the default defined for the column.
        o If the column was defined using the IDENTITY clause, the value is
          generated by the database manager.
        o If the column was defined without specifying the WITH DEFAULT
          clause, the IDENTITY clause, or the NOT NULL clause, then the
          value is NULL.
        o If the column was defined using the NOT NULL clause and the
          IDENTITY clause is not used, or the WITH DEFAULT clause was not
          used or DEFAULT NULL was used, the DEFAULT keyword cannot be
          specified for that column (SQLSTATE 23502).

     If target-variable is an SQL variable, then the value inserted is the
     default as specified or implied in the variable declaration.

row-fullselect
     A fullselect that returns a single row with the number of columns
     corresponding to the number of target-variables specified for
     assignment. The values are assigned to each corresponding
     target-variable. If the result of the row-fullselect is no rows, then
     null values are assigned. In the context of a CREATE TRIGGER
     statement, a row-fullselect may contain references to OLD and NEW
     transition variables which must be qualified by their correlation-name
     to specify which transition variable to use (SQLSTATE 42702). An error
     is returned if there is more than one row in the result (SQLSTATE
     21000).

Rules

   * The number of values to be assigned from expressions, NULLs and
     DEFAULTs or the row-fullselect must match the number of
     target-variables specified for assignment (SQLSTATE 42802).
   * A SET Variable statement cannot assign an SQL variable and a
     transition variable in one statement (SQLSTATE 42997).
   * Values are assigned to target-variables under the assignment rules
     described in Chapter 2 of the SQL Reference.

     If the statement is used in a BEFORE UPDATE trigger, and the registry
     variable DB2_UPDATE_PART_KEY=OFF, then a transition-variable specified
     as target-variable cannot be a partitioning key column (SQLSTATE
     42997).

Version

   * If more than one assignment is included, all expressions and
     row-fullselects are evaluated before the assignments are performed.
     Thus references to target-variables in an expression or row fullselect
     are always the value of the target-variable prior to any assignment in
     the single SET statement.
   * When an identity column defined as a distinct type is updated, the
     entire computation is done in the source type, and the result is cast
     to the distinct type before the value is actually assigned to the
     column. 8
   * To have DB2 generate a value on a SET statement for an identity
     column, use the DEFAULT keyword:

        SET NEW.EMPNO = DEFAULT

     In this example, NEW.EMPNO is defined as an identity column, and the
     value used to update this column is generated by DB2.

The examples for this statement stay the same.

38.5.21 UPDATE

The searched UPDATE syntax diagram is changed to:

>>-UPDATE----+-table-name-------------------+------------------->
             +-view-name--------------------+
             '-ONLY--(--+-table-name-+---)--'
                        '-view-name--'

>-----+---------------------------+----------------------------->
      | .-AS-.                    |
      '-+----+--correlation-name--'

>-----SET--| assignment-clause |-------------------------------->

>-----+--------------------------+---+---------------+---------><
      '-WHERE--search-condition--'   '-WITH--+-RR-+--'
                                             +-RS-+
                                             +-CS-+
                                             '-UR-'


Add the following to the description section:

WITH
     Specifies the isolation level at which the UPDATE statement is
     executed.

     RR
          Repeatable Read

     RS
          Read Stability

     CS
          Cursor Stability

     UR
          Uncommitted Read

     The default isolation level of the statement is the isolation level of
     the package in which the statement is bound.

  ------------------------------------------------------------------------

38.6 Chapter 7. SQL Procedures now called Chapter 7. SQL Control Statements

Control statements are SQL statements that allow SQL to be used in a manner
similar to writing a program in a structured programming language. SQL
control statements can be used in the body of a routine, trigger or a
dynamic compound statement.

This chapter contains the syntax and descriptions of the supported SQL
control statements, along with the SQL-procedure-statement.

38.6.1 SQL Procedure Statement

The SQL Procedure Statement information changes to the following:

SQL Procedure Statement

This chapter contains syntax diagrams, semantic descriptions, rules, and
examples of the use of the statements that constitute the procedure body of
an SQL routine, trigger, or dynamic compound statement.

Syntax

>>-+---------+---+-| SQL-control-statement |-+-----------------><
   '-label:--'   '-| SQL-statement |---------'

SQL-control-statement

                                (1)
|---+-ALLOCATE CURSOR statement---------+-----------------------|
    |                      (1)          |
    +-assignment statement--------------+
    |                              (1)  |
    +-ASSOCIATE LOCATORS statement------+
    |                (1)                |
    +-CASE statement--------------------+
    |                            (2)    |
    +-dynamic-compound statement--------+
    +-FOR statement---------------------+
    +-GET DIAGNOSTICS statement---------+
    |                (1)                |
    +-GOTO statement--------------------+
    +-IF statement----------------------+
    +-ITERATE statement-----------------+
    +-LEAVE statement-------------------+
    |                (1)                |
    +-LOOP statement--------------------+
    |                              (1)  |
    +-procedure-compound statement------+
    |                  (1)              |
    +-REPEAT statement------------------+
    |                    (1)            |
    +-RESIGNAL statement----------------+
    +-RETURN statement------------------+
    +-SIGNAL statement------------------+
    '-WHILE statement-------------------'


Notes:

  1. This statement is only supported in the scope of an SQL Procedure.

  2. This statement is only supported within a trigger, SQL function, or
     SQL method. It must be the outermost statement.

Description

label:
     Specifies the label for an SQL procedure statement. The label must be
     unique within a list of SQL procedure statements, including any
     compound statements nested within the list. Note that compound
     statements that are not nested may use the same label. A list of SQL
     procedure statements is possible in a number of SQL control
     statements.

     In the context of a trigger, an SQL function or method, or a dynamic
     compound statement, only the dynamic compound statement, the FOR
     statement and the WHILE statement may be labeled.

SQL-statement
     In the body of an SQL procedure, all executable SQL statements can be
     contained, with the exception of the following:
        o CONNECT
        o CREATE any object other than indexes, tables, or views
        o DESCRIBE
        o DISCONNECT
        o DROP any object other than indexes, tables, or views
        o FLUSH EVENT MONITOR
        o REFRESH TABLE
        o RELEASE (connection only)
        o RENAME TABLE
        o RENAME TABLESPACE
        o REVOKE
        o SET CONNECTION
        o SET INTEGRITY

     Notes:
          You may include CALL statements within an SQL procedure body, but
          these CALL statements can only call another SQL procedure or a C
          procedure. CALL statements within an SQL procedure body cannot
          call other types of stored procedures.

38.6.2 FOR

FOR

The FOR statement executes a statement or group of statements for each row
of a table.

Syntax

>>-+---------+---FOR--for-loop-name--AS------------------------->
   '-label:--'

>-----+-------------------------------+--select-statement---DO-->
      |                         (1)   |
      '-cursor-name--CURSOR FOR-------'

      .-------------------------------.
      V                               |
>--------SQL-procedure-statement--;---+--END FOR----+--------+-><
                                                    '-label--'


Notes:

  1. This option can only be used in the context of an SQL Procedure.

Description

label
     Specifies the label for the FOR statement. If the beginning label is
     specified, that label can be used in LEAVE and ITERATE statements. If
     the ending label is specified, it must be the same as the beginning
     label.

for-loop-name
     Specifies a label for the implicit compound statement generated to
     implement the FOR statement. It follows the rules for the label of a
     compound statement except that it cannot be used with and ITERATE or
     LEAVE statement within the FOR statement. The for-loop-name is used to
     qualify the column names returned by the specified select-statement.

cursor-name
     Names the cursor that is used to select rows from the result table
     from the SELECT statement. If not specified, DB2 generates a unique
     cursor name.

select-statement
     Specifies the SELECT statement of the cursor. All columns in the
     select list must have a name and there cannot be two columns with the
     same name.

     In a trigger, function, method, or dynamic compound statement, the
     select-statement must consist of only a fullselect with optional
     common table expressions.

SQL-procedure-statement
     Specifies a statement (or statements) to be invoked for each row of
     the table.

Rules

   * The select list must consist of unique column names and the table
     specified in the select list must exist when the procedure is created,
     or it must be a table created in a previous SQL procedure statement.
   * The cursor specified in a for-statement cannot be referenced outside
     the for-statement and cannot be specified in an OPEN, FETCH, or CLOSE
     statement.

Examples

In the following example, the for-statement is used to iterate over the
entire employee table. For each row in the table, the SQL variable fullname
is set to the last name of the employee, followed by a comma, the first
name, a blank space, and the middle initial. Each value for fullname is
inserted into table tnames.

   BEGIN
      DECLARE fullname CHAR(40);
      FOR vl AS
         SELECT firstnme, midinit, lastname FROM employee
            DO
            SET fullname = lastname || ',' || firstnme ||' ' || midinit;
            INSERT INTO tnames VALUE (fullname);
      END FOR
   END

38.6.3 Compound Statement changes to Compound Statement (Procedure)

A procedure compound statement groups other statements together in an SQL
procedure. You can declare SQL variables, cursors, and condition handlers
within a compound statement.

The syntax diagram now has a title: procedure-compound-statement.

                         .-NOT ATOMIC--.
>>-+---------+--BEGIN----+-------------+------------------------>
   '-label:--'           '-ATOMIC------'

>-----+-----------------------------------------------+--------->
      |  .-----------------------------------------.  |
      |  V                                         |  |
      '-----+-| SQL-variable-declaration |-+---;---+--'
            +-| condition-declaration |----+
            '-| return-codes-declaration |-'

>-----+--------------------------------------+------------------>
      |  .--------------------------------.  |
      |  V                                |  |
      '----| statement-declaration |--;---+--'

>-----+-------------------------------------+------------------->
      |  .-------------------------------.  |
      |  V                               |  |
      '----DECLARE-CURSOR-statement--;---+--'

>-----+------------------------------------+-------------------->
      |  .------------------------------.  |
      |  V                              |  |
      '----| handler-declaration |--;---+--'

      .-------------------------------.
      V                               |
>--------SQL-procedure-statement--;---+---END--+--------+------><
                                               '-label--'

SQL-variable-declaration

               .-,--------------------.
               V                      |
|---DECLARE-------SQL-variable-name---+------------------------->

                     .-DEFAULT NULL-------.
>-----+-data-type----+--------------------+-+-------------------|
      |              '-DEFAULT--constant--' |
      '-RESULT_SET_LOCATOR--VARYING---------'

condition-declaration

|---DECLARE--condition-name--CONDITION--FOR--------------------->

                 .-VALUE-.
     .-SQLSTATE--+-------+---.
>----+-----------------------+---string-constant----------------|

statement-declaration

             .-,-----------------.
             V                   |
|---DECLARE-----statement-name---+---STATEMENT------------------|

return-codes-declaration

|---DECLARE----+-SQLSTATE--CHAR (5)--+---+--------------------+-|
               '-SQLCODE--INTEGER----'   '-DEFAULT--constant--'

handler-declaration

|---DECLARE----+-CONTINUE-+---HANDLER--FOR---------------------->
               +-EXIT-----+
               '-UNDO-----'

      .-,-----------------------------------.
      V               .-VALUE-.             |
>---------+-SQLSTATE--+-------+--string--+--+------------------->
          +-condition-name---------------+
          +-SQLEXCEPTION-----------------+
          +-SQLWARNING-------------------+
          '-NOT FOUND--------------------'

>----SQL-procedure-statement------------------------------------|


statement-declaration
     A statement-declaration declares a list of one or more names that are
     local to the compound statement. A statement name cannot be the same
     as another statement name within the same compound statement.

38.6.4 RETURN

RETURN

The RETURN statement is used to return from the routine. For SQL functions
or methods, it returns the result of the function or method. For an SQL
procedure, it optionally returns an integer status value.

Syntax

>>-RETURN--+---------------------------------------------------------+->
           +-expression----------------------------------------------+
           +-NULL----------------------------------------------------+
           '-+---------------------------------------+---fullselect--'
             |       .-,--------------------------.  |
             |       V                            |  |
             '-WITH-----common-table-expression---+--'

>--------------------------------------------------------------><


Description

expression
     Specifies a value that is returned from the routine:
        o If the routine is a function or method, one of expression, NULL,
          or fullselect must be specified (SQLSTATE 42630) and the data
          type of the result must be assignable to the RETURNS type of the
          routine (SQLSTATE 42866).
        o A scalar expression (other than a scalar fullselect) cannot be
          specified for a table function (SQLSTATE 428F1).
        o If the routine is a procedure, the data type of expression must
          be INTEGER (SQLSTATE 428E2). A procedure cannot return NULL or a
          fullselect.

NULL
     Specifies that the function or method returns a null value of the data
     type defined in the RETURNS clause. NULL cannot be specified for a
     RETURN from a procedure.

WITH common-table-expression
     Defines a common table expression for use with the fullselect that
     follows.

     fullselect
          Specifies the row or rows to be returned for the function. The
          number of columns in the fullselect must match the number of
          columns in the function result (SQLSTATE 42811). In addition, the
          static column types of the fullselect must be assignable to the
          declared column types of the function result, using the rules for
          assignment to columns (SQLSTATE 42866).

          The fullselect cannot be specified for a RETURN from a procedure.

          If the routine is a scalar function or method, then the
          fullselect must return one column (SQLSTATE 42823) and, at most,
          one row (SQLSTATE 21000).

          If the routine is a row function, it must return, at most, one
          row (SQLSTATE 21505).

          If the routine is a table function, it can return zero or more
          rows with one or more columns.

Rules

   * The execution of an SQL function or method must end with a RETURN
     (SQLSTATE 42632).
   * In an SQL table or row function using a dynamic-compound-statement,
     the only RETURN statement allowed is the one at the end of the
     compound statement (SQLSTATE 429BD).

Version

   * When a value is returned from a procedure, the caller may access the
     value using:
        o the GET DIAGNOSTICS statement to retrieve the RETURN_STATUS when
          the SQL procedure was called from another SQL procedure
        o the parameter bound for the return value parameter marker in the
          escape clause CALL syntax (?=CALL...) in a CLI application
        o directly from the SQLCA returned from processing the CALL of an
          SQL procedure by retrieving the value of SQLERRD[0] when the
          SQLCODE is not less than zero (assume a value of -1 when SQLCODE
          is less than zero).

Examples

Use a RETURN statement to return from an SQL stored procedure with a status
value of zero if successful, and -200 if not.

   BEGIN
   ...
      GOTO FAIL
   ...
      SUCCESS: RETURN 0
      FAIL: RETURN -200
   END

38.6.5 SIGNAL

The SIGNAL SQLSTATE Statement is no longer used, in favor of this usage.

SIGNAL

The SIGNAL statement is used to signal an error or warning condition. It
causes an error or warning to be returned with the specified SQLSTATE,
along with optional message text.

Syntax

                         .-VALUE-.
>>-SIGNAL----+-SQLSTATE--+-------+--sqlstate-string-constant--+->
             '-condition-name---------------------------------'

>-----+--------------------------------------------------------+-><
      +-SET--MESSAGE_TEXT-- = --+-variable-name--------------+-+
      |                         '-diagnostic-string-constant-' |
      |                         (1)                            |
      '-(--diagnostic-string--)--------------------------------'


Notes:

  1. This option is only provided within the scope of a CREATE TRIGGER
     statement for compatibility with older versions of DB2.

Description

SQLSTATE VALUE sqlstate-string-constant
     The specified string constant represents an SQLSTATE. It must be a
     character string constant with exactly 5 characters that follow the
     rules for SQLSTATEs:
        o Each character must be from the set of digits ('0' through '9')
          or non-accented upper case letters ('A' through 'Z').
        o The SQLSTATE class (first two characters) cannot be '00', since
          this represents successful completion.

     In the context of either a dynamic compound statement, trigger, SQL
     function, or SQL method, the following rules must also be applied:
        o The SQLSTATE class (first two characters) cannot be '01' or '02',
          since these are not error classes.
        o If the SQLSTATE class starts with the numbers '0' through '6' or
          the letters 'A' through 'H', then the subclass (the last three
          characters) must start with a letter in the range of 'I' through
          'Z'.
        o If the SQLSTATE class starts with the numbers '7', '8', '9', or
          the letters 'I' through 'Z', then the subclass can be any of '0'
          through '9' or 'A' through 'Z'.

     If the SQLSTATE does not conform to these rules, an error is raised
     (SQLSTATE 428B3).

condition-name
     Specifies the name of the condition. The condition name must be unique
     within the procedure and can only be referenced within the compound
     statement in which it is declared.

SET MESSAGE_TEXT=
     Specifies a string that describes the error or warning. The string is
     returned in the SQLERRMC field of the SQLCA. If the actual string is
     longer than 70 bytes, it is truncated without warning. This clause can
     only be specified if a SQLSTATE or condition-name is also specified
     (SQLSTATE 42601).

     variable-name
          Identifies an SQL variable that must be declared within the
          compound statement. The SQL variable must be defined as a CHAR or
          VARCHAR data type.

     diagnostic-string-constant
          Specifies a character string constant that contains the message
          text.

diagnostic-string
     An expression with a type of CHAR or VARCHAR that returns a character
     string of up to 70 bytes to describe the error condition. If the
     string is longer than 70 bytes, it will be truncated. This option is
     only provided within the scope of a CREATE TRIGGER statement, for
     compatibility with older versions of DB2. Regular use is not
     recommended.

Version

   * If a SIGNAL statement is issued, the SQLCODE that is assigned is:

          +438 if the SQLSTATE begins with '01' or '02'

          -438 otherwise
   * If the SQLSTATE or condition indicates that an exception (SQLSTATE
     class other than '01' or '02') is signaled:
        o Then the exception is handled and control is transferred to a
          handler, provided that a handler exists in the same compound
          statement (or an outer compound statement) as the signal
          statement, and the compound statement contains a handler for the
          specified SQLSTATE, condition-name, or SQLEXCEPTION;
        o If the exception cannot be handled, then control is immediately
          returned to the end of the compound statement.
   * If the SQLSTATE or condition indicates that a warning (SQLSTATE class
     '01') or not found condition (SQLSTATE class '02') is signaled:
        o Then the warning or not found condition is handled and control is
          transferred to a handler, provided that a handler exists in the
          same compound statement (or an outer compound statement) as the
          signal statement, and the compound statement contains a handler
          for the specified SQLSTATE, condition-name, SQLWARNING (if the
          SQLSTATE class is '01'), or NOT FOUND (if the SQLSTATE class is
          '02');
        o If the warning cannot be handled, then processing continues with
          the next statement.
   * SQLSTATE values are comprised of a two-character class code value,
     followed by a three-character subclass code value. Class code values
     represent classes of successful and unsuccessful execution conditions.

     Any valid SQLSTATE value can be used in the SIGNAL statement. However,
     it is recommended that programmers define new SQLSTATEs based on
     ranges reserved for applications. This prevents the unintentional use
     of an SQLSTATE value that might be defined by the database manager in
     a future release.
        o SQLSTATE classes that begin with the characters '7' through '9',
          or 'I' through 'Z' may be defined. Within these classes, any
          subclass may be defined.
        o SQLSTATE classes that begin with the characters '0' through '6',
          or 'A' through 'H' are reserved for the database manager. Within
          these classes, subclasses that begin with the characters '0'
          through 'H' are reserved for the database manager. Subclasses
          that begin with the characters 'I' through 'Z' may be defined.

Examples

An SQL procedure for an order system that signals an application error when
a customer number is not known to the application. The ORDERS table
includes a foreign key to the CUSTOMER table, requiring that the CUSTNO
exist before an order can be inserted.

   CREATE PROCEDURE SUBMIT_ORDER
      (IN ONUM INTEGER, IN CNUM INTEGER,
       IN PNUM INTEGER, IN QNUM INTEGER)
       SPECIFIC SUBMIT_ORDER
       MODIFIES SQL DATA
      LANGUAGE SQL
      BEGIN
         DECLARE EXIT HANDLER FOR SQLSTATE VALUE '23503'
            SIGNAL SQLSTATE '75002'
               SET MESSAGE_TEXT = 'Customer number is not known';
         INSERT INTO ORDERS (ORDERNO, CUSTNO, PARTNO, QUANTITY)
            VALUES (ONUM, CNUM, PNUM, QNUM);
      END

  ------------------------------------------------------------------------

38.7 Appendix A. SQL Limits

There is a change to Table 33, Database Manager Limits. With the registry
variable DB2_INDEX_2BYTEVARLEN set to ON, the longest variable index key
part (in bytes) can now be greater than 255.
  ------------------------------------------------------------------------

38.8 Appendix D. Catalog Views

A new catalog view has been added:

38.8.1 SYSCAT.SEQUENCES

The view SYSCAT.SEQUENCES is automatically generated for databases created
with FixPak 3 or later. For databases created prior to FixPak 3, run the
db2updv7 command in order to add the view to the database. See the Command
Reference update in the Release Notes for details.

This catalog view is updated during normal operation, in response to SQL
data definition statements, environment routines, and certain utilities.
Data in the catalog view is available through normal SQL query facilities.
Columns have consistent names based on the type of objects that they
describe.

Table 30. Columns in SYSCAT.SEQUENCES Catalog View
 Column Name      Data Type      NullableDescription
 SEQSCHEMA        VARCHAR(128)           Schema of the sequence.
 SEQNAME          VARCHAR(128)           Sequence name (generated by DB2
                                         for an identity column).
 DEFINER          VARCHAR(128)           Definer of the sequence.
 OWNER            VARCHAR(128)           Owner of the sequence.
 SEQID            INTEGER                Internal ID of the sequence.
 SEQTYPE          CHAR(1)                Sequence type

                                              S - Regular sequence

 INCREMENT        DECIMAL(31,0)          Increment value.
 START            DECIMAL(31,0)          Starting value.
 MAXVALUE         DECIMAL(31,0)  Yes     Maximal value.
 MINVALUE         DECIMAL(31,0)          Minimum value.
 CYCLE            CHAR(1)                Whether cycling will occur when a
                                         boundary is reached:

                                              Y - cycling will occur

                                              N - cycling will not occur

 CACHE            INTEGER                Number of sequence values to
                                         preallocate in memory for faster
                                         access. 0 indicates that values
                                         are not preallocated.
 ORDER            CHAR(1)                Whether or not the sequence
                                         numbers must be generated in
                                         order of request:

                                              Y - sequence numbers must be
                                              generated in order of
                                              request

                                              N - sequence numbers are not
                                              required to be generated in
                                              order of request

 DATATYPEID       INTEGER                For built-in types, the internal
                                         ID of the built-in type. For
                                         distinct types, the internal ID
                                         of the distinct type.
 SOURCETYPEID     INTEGER                For a built-in type, this has a
                                         value of 0. For a distinct type,
                                         this is the internal ID of the
                                         built-in type that is the source
                                         type for the distinct type.
 CREATE_TIME      TIMESTAMP              Time when the sequence was
                                         created.
 ALTER_TIME       TIMESTAMP              Time when the last ALTER SEQUENCE
                                         statement was executed for this
                                         sequence.
 PRECISION        SMALLINT               The precision defined for a
                                         sequence with a decimal or
                                         numeric type. Values are: 5 for a
                                         SMALLINT, 10 for INTEGER, and 19
                                         for BIGINT.
 ORIGIN           CHAR(1)                Sequence Origin

                                              U - User generated sequence

                                              S - System generated
                                              sequence

 REMARKS          VARCHAR(254)   Yes     User supplied comments, or null.
  ------------------------------------------------------------------------

IBM DB2 ·xÝsæ{õ€®÷móû

  ------------------------------------------------------------------------

39.1 Java 1.2 Ï„ï¸·xÝsæ{õ€®÷móû

DB2 ·xÝsæ{õ€®÷móûÏ„ï¸ Java ·xÝsæ{õ€ùØ¾× Java 1.2 ¾\î…­C ¾t¾~­A·xÝsæ{õ€®÷m
óûÏ„ï¸¶—ÝV¯yù¾­AÝp¦¸âõB¯y¸Mõ’õBùà¯y­A¸ãùØ¾×¦§ªO Java 1.2 ¦§ bi-di Ï„ï¸­C

ÝûÏ„ï¸¾u¾×¸¢ Windows NT ¾ð¾xÝàÏw­C

ªøÏF·xÝsæ{õ€®÷móû¨‰Ç¥¸MùØ¾× Java 1.2 ¦§¾\î…­A¸ã¾HðnôiÝ‘Ýw÷Ó Java 1.2­C

Ýw÷Ó Java 1.2­G

  1. JDK 1.2.2 Ýb DB2 UDB CD ¦§ DB2\bidi\NT ¾¨ìÏU­C
     ibm-inst-n122p-win32-x86.exe ªOÝw÷Óæ{Ý­­A ibm-jdk-n122p-win32-x86.exe
     ªO JDK Ï·øe­C ñNùƒðà·©ž«’¯sùæw§ÑÏW¦§¬Ô©¾¨ìÏÏ­A æM® ñq÷à¾¨ìøäÝ‘Ýw
     ÷Óæ{Ý­­C
  2. ñN¾ÝÝw÷ÓÝb <DB2PATH\java\Java12 ÏU­A<DB2PATH ªO DB2 ¦§Ýw÷Ó÷“©|­C
  3. JDK/JRE Ýw÷Óïœ¾š©­AÏœðn¨‹ù£ JDK/JRE ªøùtý× VM­C

Java 1.2 Ýw÷ÓÝù¾\® ­A¾H¾¨ñ`ÏŠÝ­ñãøÒ·xÝsæ{õ€®÷móû­C

ñìùØ¾× JDK 1.2 Ï„ï¸øäÝ‘ Java ·xÝsæ{õ€­A¾ýôúü]¸w÷ˆ©’©wÝ›¦Aóû·“ûãš¬’
DB2_USE_JDK12 ªøîu­A«ÑùØ¾×ÏUÝC®¾O­G

DB2SET DB2_USE_JDK12=TRUE

ÝP©­Aü]¸w JDK11_PATH ®ÝVÝw÷Ó Java 1.2 Ï„ï¸¦§¾¨ì­C «ÑùØ¾×ÏUÝC®¾Oùàü]¸wÝû
÷“©|­G

DB2 UPDATE DBM CFG USING JDK11_PATH

ñìøñÏŒùØ¾× Java 1.2­A«ÑÝb <DB2PATH>\java\Java12 ÏU÷¥øœÝw÷Ó JDK/JRE­A¸×õ¢õ‹
<DB2PATH>\java\Java12 Ý÷¾¨ì¦§ÝWÝr­C

ð®ðnù’ôæ­GÏœðnñN <DB2PATH>\java\Java12 ¸M <DB2PATH>\Java12 ýVýc­C
<DB2PATH>\Java12 ªO DB2 Ýw÷Ó¦§Ï@ü­¾ö­AùÇ¾B¾]ªA Java 1.2 ¦§ JDBC Ï„ï¸­C
  ------------------------------------------------------------------------

39.2 DB2 ·xÝsæ{õ€¦§¯ú§íøœ¨—

ðYðnùØ¾× UNIX ¸M Windows ¾ð¾x¦§ Java ¸M C ·xÝsæ{õ€Ïõ¯ú§íøœ¨—î…ÏO­A «ÑÝw÷Ó
IBM Distributed Debugger­CIBM Distributed Debugger ¾i¸¢ Visual Age for Java
Professional Edition CD Ï§ù£ño­Cøœ¨—óûñqŽíî÷¾uÝb Windows ¾ð¾xÏWøäÝ‘­CÏ„ï¸Ý›
¦Aóû¾ð¾x¾]ªA­GWindows­BAIX ¸M Solaris­C «ÑùØ¾×·xÝsæ{õ€®÷móûÏ§®¦§ SQL øœ¨—
î…ÏO­Aªø Windows ¸M UNIX ¾ð¾xøœ¨—¾¯§í¸M¯ú§í SQL ·xÝsæ{õ€­C Ýû©æL¦kÏ„ï¸
OS/2 ¾ð¾x­CÝüÇ” DB2 for OS/390 ·xÝsæ{õ€®÷móû¦§÷âýà÷ˆøT­A «ÑüsñæùÏUÝC§“
î÷­G http://www-4.ibm.com/software/data/db2/os390/spb/exciting

ñìÝb OS/390 ¾ð¾xôiÝ‘ SQL æ{õ€øœ¨—­AÏ]¾ýôúÝü OS/390 R1 ýœ®~¦§ IBM C/C++ ¯ýõU
ÏuùÆ­COS/390 R1 ¦§ IBM C/C++ ¯ýõUÏuùÆÏõ÷âýà÷ˆøT­A«ÑüsñæùÏUÝC§“î÷­G
http://www.ibm.com/software/ad/c390/pt/
  ------------------------------------------------------------------------

39.3 Ýb Windows­BOS/2 ¸× UNIX ¾ð¾xÏWô}æo SQL æ{õ€

Ýbñzî…øöùØ¾×·xÝsæ{õ€®÷móû¸¢ Windows­BOS/2 ¸× UNIX ÷ˆ©’©wÏWôôõQÝaô}æo SQL
æ{õ€Ïõ®e­A ¾ýôúª[§c SQL æ{õ€¦§Ý›¦Aóû­CÝüÇ”ÝpÝ¢ª[§c SQL æ{õ€¦§Ý›¦Aóû­A«Ñø¥ó\
34.3, ýŽ 4 üû ô}æo Java Applets ¸M·ü¾×æ{Ý­­C
  ------------------------------------------------------------------------

39.4 Ýb Solaris ¾ð¾xùØ¾× DB2 ·xÝsæ{õ€®÷móû

ñìÝb Solaris ¾ð¾xùØ¾× DB2 ·xÝsæ{õ€®÷móû­G

  1. ÏU÷¸MÝw÷Ó JDK 1.1.8­C Ýê JavaSoft §“î÷ÏU÷ JDK 1.1.8­C
  2. ü]¸w·“ûãš¬’ JAVA_HOME ÝšÝw÷Ó JDK ¦§Ý÷m­C
  3. ü]¸w DB2 JDK11_PATH ÝšÝw÷Ó JDK ¦§¾¨ìÏU­C

     ñìü]¸w DB2 JDK11_PATH­A«ÑùØ¾×ÏUÝC®¾O­G

     DB2 UPDATE DBM CFG USING JDK11_PATH.

  ------------------------------------------------------------------------

39.5 Ïw¦óøíÇD¯PððùŒ

   * ¾®e Windows 98 ùÇÏœÏ„ï¸ SQL æ{õ€­C
   * Ç”¸¢ Java ·xÝsæ{õ€­AJAR ID­BÇçõOÝW§ë¯PÏŠ¦kÝW§ëÏœ¾i¾]õt®D ASCII ÝrÏ÷­C
   * Ýb AS/400 ÏWÏUÝC V4R4 PTFs ú|Ïè¾×Ýš OS/400 V4R4­G

        - SF59674
        - SF59878

   * ·xÝsæ{õ€·xÝs¸¢÷ˆ©’©w©­AùÆ FOR MIXED DATA ¸× FOR SBCS DATA Ý÷Çç®ª¦§·x
     Ýsæ{õ€ø¥¬’­A ïNÏœú|Æ¾šÝb«s¨Šóûæ­©‘¦§ð¸l«XÏÏ­C
   * ¾®e¦§øíÇDªO Java ð¸l«XªO¾¥÷ˆ©’©w¶^ù£ùà¦§­C ¶^ù£©æ{Ý­«X¦§¯­¸£ú|õeý{
     ÝªÝX¦§ÏŠÝ­­C üoú|¬vTÝb®D ASCII Ýr«XðôÏWùØ¾× DB2 ·xÝsæ{õ€®÷móû¦§ùØ¾×
     ¦Þ­A Ý]ªø¾LðÞ¦§ñqŽíî÷¯PÝ›¦AóûùØ¾×ÏœÝP¦§Ýr«Xðô­C

  ------------------------------------------------------------------------

39.6 Ýbµc‚ÏÏÏ†¯yù¾·“ûãÏUùØ¾× DB2 ·xÝsæ{õ€®÷móû

Ýbµc‚ÏÏÏ†¯yù¾·“ûãÏUùØ¾× JDK ¸× JRE 1.1.8 ©ú|æo¾ÖøíÇD­C·xÝsæ{õ€®÷móûæ{Ý­
¦§ûØõ×Ý­Ïôðñ (¾]õt¾\î…¦¡­B«s¨ŠóûÏ†Ýr­BøT©õæ¾æ¾) æL¦kóAú¡Æ¾š­C÷¥ùMÏŠ©žªOðž
õ‹ font.properties.zh_TW ·©ž­A¾Ýú|ÝbÏUÝC¾¨ìÏÏ­G

   sqllib/java/jdk/lib
   sqllib/java/jre/lib

šõ¢­G

   monospaced.0=\u7d30\u660e\u9ad4,CHINESEBIG5_CHARSET,NEED_CONVERTED

õ‹ªø­G

   monospaced.0=Courier New,ANSI_CHARSET

  ------------------------------------------------------------------------

39.7 UNIX (AIX­BSun Solaris­BLinux) Ýw÷Ó¯P·xÝsæ{õ€®÷móû

Ýb Sun Solaris Ýw÷Ó©­AðYñzùØ¾× Java Development Kit ¸× Runtime ÝàÏœªOÝb
AIX ÏWÝw÷Ó UDB ¦§ÏŠÝ­­AñzïN¾ýôúñN·“ûãš¬’ JAVA_HOME ü]¸wùÏwÝw÷Ó Java ¦§÷“
©|ÏÏ (Ï]ïNªO÷à¾¨ìôúõt /bin ¯P /lib ¾¨ì)­C·xÝsæ{õ€®÷móû¾¬Ï„ï¸ Linux õ@ú~
ùtý×­AÝì¾iÝbÏwÏ„ï¸¦§¾ð¾xÏW®÷m¸×øäÝ‘ DB2 UDB for Linux ùtý×ÏW¦§·xÝsæ{õ€­C

Ï„ï¸¦§¾ð¾x¾]ªA¾×¸¢ñqŽíî÷¦§ AIX­BSolaris Ï× NT­A¯P¾×¸¢Ý›¦Aóû¦§ Aix­BSolaris
­BNT­BLinux­BOS/2­BHP-UX Ï× NUMA-Q­C
  ------------------------------------------------------------------------

39.8 ®÷m OS/390 ¦§ SQL ·xÝsæ{õ€

DB2 ·xÝsæ{õ€®÷móûÏ„ï¸Ýb OS390 V7 Ý›¦Aóû¦§ DB2 UDB ÏW®÷m SQL ·xÝsæ{õ€­C
  ------------------------------------------------------------------------

39.9 øœ¨— SQL ·xÝsæ{õ€

ý{Ýb­ASQL ·xÝsæ{õ€Ýb Windows Ï× UNIX ¾ð¾xÏW¦§øœ¨—­AÏw¦«ñæóÆÝXù DB2 ·xÝsæ{
õ€®÷móûÏÏ­C Ýbøœ¨—®Dûj¶ö (®H¾“¦§) SQL æ{õ€©­AKEEPDARI ÷ˆ©’©w§èýzð–ü]¸w¨‹
ôæ¾iü]¸wªø YES ¸× NO­FÝìªO­AÝbøœ¨—ûj¶ö (®D®H¾“¦§) SQL æ{õ€©­A¾ýôúü]¸wªøYES
(ûwü]ðÔ)­C «Ñø¥ó\·xÝsæ{õ€®÷móû¦§¯­¸£­A¾Hù£ñoÝüÇ”ùØ¾×óÆÝXøœ¨—óû¦§ù„¾L÷ˆøT­C
  ------------------------------------------------------------------------

39.10 ôž¾X Java ·xÝsæ{õ€

DB2 ·xÝsæ{õ€®÷móûý{ÝbÏ„ï¸ôž¾X Java ·xÝsæ{õ€­C ðYðnôž¾X Java ·xÝsæ{õ€­G

  1. Ýb·xÝsæ{õ€÷ˆ©’õùÏW®”Ï@ÏUú’û®¾kµ„­A®”Ï@ÏU­uôž¾X Java ·xÝsæ{õ€­v¾Hô}ñã
     ­uôž¾X Java ·xÝsæ{õ€­væ›æ­­C
  2. ¨‹ù£ñzðnôž¾X¦§·xÝsæ{õ€­AñN¾ÝðÞýóù­uÏw¨‹ù£¦§·xÝsæ{õ€­v¦«Ž‘­C
  3. ¨‹ù£ñzúQðn¦§¨‹ôæÏõ® ­A«Ñ®”Ï@ÏU­u«T¸w­v­C

  ------------------------------------------------------------------------

39.11 Ýb OS/390 ÏWï­ÏJ·xÝsæ{õ€

øwû‹øäÝ‘ OS/390 ¦§ DB2 ·xÝsæ{õ€®÷móû¦¸¾¯ 5 Ï×õ¢ús¦¸¾¯­A Ýp¦GñzùØ¾×§‰’Fùàï­
ÏJ·xÝsæ{õ€ùÇ®¾šæL WLM ·“ûã¨‹ôæ­A ®hýœ¾Ö¦§æ{Ý­«Xú|¾]õt¾HÏU¦§Ï†Ýr­GNO WLM
ENVIRONMENT­C üoÝ‘æ{Ý­«Xú|ì·xÝsæ{õ€Ýb SPAS Ýõ}¦ô­ÏÏùÞûwïµøäÝ‘­C Ýûðž¾¨æ{
Ý­÷¥ùMÝsÝb¸¢ DB2 ·xÝsæ{õ€®÷móû¦¸¾¯ 6 Ï×õ¢ús¦¸¾¯ÏÏ¦§øíÇD­C

¾Hðž¾¨æ{Ý­¸ãýœ¾Ö¦§æ{Ý­«XÆ¾šÝpÏU­G

       CREATE PROCEDURE SYSPROC.Proc2 (  )
           RESULT SETS 1
           LANGUAGE SQL
           MODIFIES SQL DATA
           COLLID TEST
           NO WLM ENVIRONMENT
           ASUTIME NO LIMIT
           RUN OPTIONS 'NOTEST(ALL,*,,VADTCPIP&9.112.14.91:*)'
       -------------------------------------------------------------------
       -- SQL Stored Procedure
       -------------------------------------------------------------------
       P1: BEGIN
           -- Declare cursor
           DECLARE cursor1 CURSOR WITH RETURN FOR
               SELECT * FROM SYSIBM.SYSPROCEDURES;

           -- Cursor left open for client application
           OPEN cursor1;

       END P1

  ------------------------------------------------------------------------

39.12 ÝbÏuõ@î÷Ý›¦AóûÏÏü]¸w SQL ·xÝsæ{õ€¦§®÷m¨‹ôæ

Ýb UNIX Ï× Windows ¾ð¾xÏWùØ¾× DB2 ·xÝsæ{õ€®÷móû©­A¾i¾Hªø¸ãÝü¦§ SQL ·xÝsæ{
õ€ü]¸w®÷m¨‹ôæ­C üoù€®÷m¨‹ôæ¾]õtÏUÝC¦§«sŽôóûÏ×®e÷m«sŽôóû DB2 ænøOš¬’­G

   * DB2_SQLROUTINE_PREPOPTS
   * DB2_SQLROUTINE_COMPILER_PATH
   * DB2_SQLROUTINE_COMPILE_COMMAND
   * DB2_SQLROUTINE_KEEP_FILES

µ”æM¾i¾HùØ¾× db2set ®¾Oü]¸wüoù€ænøOš¬’­A ùØ¾×·xÝsæ{õ€®÷móû¾i©›øœûˆ¯éÝsù£
÷ˆ©’©wÝ›¦Aóû¾Hæo¾X®¾O¸×øñÏŒ­A æM® ð®úsñãøÒÝ›¦AóûùØšõ¢¾Ö©Ž¦§¯íùD­C

ðYðnô}ñã­uSQL ·xÝsæ{õ€®÷m¨‹ôæ­væ›æ­­A«ÑÝbñM©žúõýÏ¦¡ÏÏ¦§÷ˆ©’©wüs«u®”Ï@ÏUú’
û®¾kµ„­A æM® ®”Ï@ÏU­uSQL ·xÝsæ{õ€®÷m¨‹ôæ­v­C ÝüÇ”ü]¸wüoù€¨‹ôæ¦§÷âýà÷ˆøT­A
«Ñø¥ó\ DB2 ·xÝsæ{õ€¯­¸£­C
  ------------------------------------------------------------------------

39.13 ÝêøÒï_ús OS/390 ÏW·xÝsæ{õ€®÷m¦§ WLM Ýõ}¦ô­

ú¡ñzôôõQÝaÝb OS/390 ÏW®÷mñNÝb WLM øäÝ‘¦§·xÝsæ{õ€Ïõ® ­ADB2 ·xÝsæ{õ€®÷móûñN
ÝêøÒï_ús WLM Ýõ}¦ô­­C
  ------------------------------------------------------------------------

39.14 Ýb OS/390 ô}æo Java ·xÝsæ{õ€

­uDB2 ·xÝsæ{õ€®÷móû­vÏ„ï¸ DB2 UDB for OS/390 ¦¸¾¯ 6 (¸×¾HÏW) ¦§ Java ·xÝs
æ{õ€¦§ô}æo­Cñz¾i¾H®¾áús¦§¸×šõ¢ý{Ýs¦§ Java ·xÝsæ{õ€­C
  ------------------------------------------------------------------------

39.15 ªø MQ Series ¯P OLE DB ®÷m DB2 ¦¡©‘ùØ¾×¦Þ¸w÷q¾\î… (UDF)

­uDB2 ·xÝsæ{õ€®÷móû­vïœù¥§‰’F¾Hù¢õUñz®¾á MQSeries ¯P OLE DB ¦§¦¡©‘ UDF­C
ñz¾i¾HùØ¾×­u®¾á OLE DB ¦¡©‘ UDF­v§‰’FÝsù£ OLE DB ÷ˆ©’ïœù¥¦Þ­CÝû§‰’Fú|®¾á
OLE ¦¡©‘ UDF ¯P¨‹¾×¦§¦¡©‘·Óæ›­Cñz¾i¾HùØ¾×­u®¾á MQSeries­v¦¡©‘ UDF §‰’Fùà®
¾áùÆÝü¨‹ôæ¦¡©‘·Óæ›¦§¦¡©‘ UDF­A ¾HÝsù£ MQSeries øT©õùÇð†¦R¸wÝ¬Ñã©‘Ý­ÏÏ¦§÷ˆ
©’­C
  ------------------------------------------------------------------------

Unicode õ¢ús

  ------------------------------------------------------------------------

40.1 ¶ýÏô

Unicode ¬Ñú€ªO©¥¬gÝrÏ÷Ï×Ï†ÝrÏŠðñ¾çýyüq¾×¦§ÝrÏ÷«s«XÏŠ¦k­C Unicode ªO¾×ÝhðàÝ
Ï÷ýåùà¦¡¾šÏ@ðàÝrÏ÷­C ¾Ý¸w÷qÏFÏ@§Ï@ðP¦§ÏŠÝ­ùàñNÝhøˆ¯yù¾Ï†Ýr«s«X­A ùØñoÏ†Ýr
÷ˆ©’¾iÝbøˆ¯éô­¾‘ï®­AùÇüÑ¾á¾@ªîün‚¦§ø•¶Ý­C

Unicode ïœù¥¾HÏUùƒ§«s«XÏŠ¦k­Cûwü]¦§«s«XÏŠ¦kªO UTF-16 (16 ÝÏ÷¦§«s«X©‘Ý­)­C
UCS-2 ªO UTF-16 ¦§Ïlôø­A ¾ÝùØ¾×ùƒðàÝÏ÷ýåùà¦¡¾šÏ@ðàÝrÏ÷­CUCS-2 üqñ`üQ¯{¾iªø
¾çýy¸Ò¦§Ýr«Xðô­A ¾Ýî…øö¦¡¾š¾®e¸ãÝüü‘ÝÏ÷ýåÝr«XðôÏ×¶—ÝÏ÷ýåÝr«Xðô¦§¾çü­¾ý¯í
ÝrÏ÷­CUCS-2 Ýb IBM ÏÏæ—¾UªøÝr«Xðô 1200­C

¾tÏ@ðà Unicode «s«X©‘Ý­ªO UTF-8­A¾ÝªOÝÏ÷ýåóÝV¦§­A ¾BªOüQü]ðpùàÏŠ®Ký{Ýü
ASCII ùtý×¦§ùØ¾×­CUTF-8 ùØ¾×Ïœ¸w¬’¾¦§ÝÏ÷ýå (üqñ`ªø 1-3­AÝü©ªO 4) ùà·xÝs
ùCðàÝrÏ÷­C æLšÏ’¦§ ASCII ÝrÏ÷ïN·xÝsªøü‘ÝÏ÷ýå­C¸ãÝüù„¾ÝÝrÏ÷ïNùØ¾×ÝhðàÝÏ÷
ýåùà·xÝs­Cüqñ` UTF-8 ÷ˆ©’¾iùÞóé®Dü]ðpªøÝhÝÏ÷ýåÝr«Xðô¦§Ýr«Xùàæ›ªø¶X¾R¦§
ASCII ÷ˆ©’­C UTF-8 Ýb IBM ÏÏæ—¾UªøÝr«Xðô 1208­C

·ü¾×æ{Ý­ðnÝã¬{ù÷ˆ©’ÝbøØøÝr«Xðô­BUCS-2 ¸M UTF-8 Ïõô­øæ¶…ï®©¦§¯íùD­A üoªO
®šð®ðn¦§­CùãÝp­A20 ðàÝrÏ÷Ýb UCS-2 ÏÏ¯íðnõûóÆ¦§ 40 ðàÝÏ÷ýå­A UTF-8 ®hÏô¸¢
20 ù 60 ðàÝÏ÷ýåÏõô­ (æ›ð¾ìùØ¾×¦§Ýr«XðôÏ×Ï†ÝrÝà¸w)­C

40.1.1 DB2 Unicode ÷ˆ©’©wÏ×·ü¾×æ{Ý­

ùØ¾× UTF-8 Ýr«Xôø®¾á¦§ Unix­BWindows ¸× OS/2 DB2 Universal ÷ˆ©’©w ¾i¾×ùà·x
Ýs UCS-2 Ï× UTF-8 ùƒ§©‘Ý­¦§÷ˆ©’­C üo¬Ó¦§÷ˆ©’©w¾iüQæ›ªø Unicode ÷ˆ©’©w­C
SQL CHAR ÷ˆ©’ªOùØ¾× UTF-8 ùà«s«X¦§­AÝà SQL GRAPHIC ÷ˆ©’ªOùØ¾× UCS-2 ùà«s«X
¦§­C üo¾i¾Hªêú¡¸¢Ýb CHAR ¦«Ž‘·xÝsü‘ÝÏ÷ýå (SBCS) Ï×ÝhÝÏ÷ýå (MBCS) Ýr«Xôø­A
¾HÏ×Ýb GRAPHIC ¦«Ž‘·xÝs¶—ÝÏ÷ýå (DBCS) Ýr«Xôø­C

·ü¾×æ{Ý­¦§Ýr«Xðô¾iî…¸M DB2 ¾×ùà·xÝs÷ˆ©’¦§Ýr«XðôÏœÏ@¬Ó­C Ýb®D Unicode ÷ˆ©’©w
ÏÏ­AÝbÝr«XðôÏœÏ@¬Ó©­A ÷ˆ©’©w§èýzæ{Ý­ú|¶…ï®ñqŽíî÷Ï×Ý›¦AóûÏõô­ô€øe¦§ÝrÏ÷Ï×ûØ
õ× (pure DBCS) ÷ˆ©’­C Ýb Unicode ÷ˆ©’©wÏÏ­AñqŽíî÷Ýr«Xðô¯P UTF-8 Ïõô­¦§ÝrÏ÷
÷ˆ©’¶…ï®ú|ÝêøÒ¾¥÷ˆ©’©w§èýzæ{Ý­ùàøäÝ‘­A ÝìªO¸ãÝü¦§ûØõ× (UCS-2) ÷ˆ©’Ïœ÷gûL¶…
ï®ïNÝbñqŽíî÷Ï×Ý›¦AóûÏõô­ô€øe­C

ûØ 7. ÷ˆ©’©w§èýzæ{Ý­¸ãøäÝ‘¦§Ýr«Xðô¶…ï®

    [÷ˆ©’©w§èýzæ{Ý­¸ãøäÝ‘¦§Ýr«Xðô¶…ï®]

æ—:

  1. ú¡üsñæù Unicode ÷ˆ©’©w­AÝp¦G·ü¾×æ{Ý­ü]¸w DB2CODEPAGE=1208­A ®høØøÝr
     «XðôªO UTF-8­A¸ã¾HÏœ¯íðnøæÝr«Xðô¶…ï®­C

  2. ú¡Ïwüsñæù Unicode ÷ˆ©’©w­ACLI ·ü¾×æ{Ý­Ï]¾iñNÝrÏ÷÷ˆ©’ú¡õ@ûØõ×÷ˆ©’ñæ
     Ýª­A ¾HÏ×ñNûØõ×÷ˆ©’ú¡õ@ÝrÏ÷÷ˆ©’­C

·ü¾×æ{Ý­ªO¾i¾H®¸w UTF-8 Ýr«Xðô­A¾H®¾X¾ÝñN¾× UCS-2 ùàô€øeÏ×ñæÝªûØõ×÷ˆ©’­A
ùÇ¾× UTF-8 ùàô€øeÏ×ñæÝªÝrÏ÷÷ˆ©’­C Ýû·ü¾×æ{Ý­Ýr«Xðô¾uÏ„ï¸ Unicode ÷ˆ©’©w­C

ùØ¾× Unicode ©ðnÝã¬{¦§ù„¾Ýôæ¾ªø­G

  1. ÷ˆ©’©wÝr«XðôªOÝb®¾á÷ˆ©’©w¦§©ðâùM¸w¦§­A ¾B¾Ý¦§ðÔûwü]ú|ñqõ@ú~ùtý×¯yù¾
     ·“ûã (¸×Ýr«Xðô) ùàùM¸w­C CODESET Ï× TERRITORY Ç”µ„Ýr¾i¾×ùà¸£«TÝa®¾á
     Unicode DB2 ÷ˆ©’©w­C ùãÝp­G

     CREATE DATABASE unidb USING CODESET UTF-8 TERRITORY US

  2. ·ü¾×æ{Ý­Ýr«XðôÏ]ûwü]ªøøØøÝr«Xðô­AÝìªOüo¾i¾×ÏUÝCÏŠ¦k¾¥ UTF-8 ùà÷mï®­G
        o ùØ¾×Ýû®¾OñN·ü¾×æ{Ý­Ýr«Xðôü]¸wªø UTF-8 (1208)­G

          db2set DB2CODEPAGE=1208

        o û‹¸¢ CLI/ODBC ·ü¾×æ{Ý­­A¾i¸I¾s SQLSetConnectAttr() Ï×ü]¸w
          SQL_ATTR_ANSI_APP ªø SQL_AA_FALSE­C ûwü]ü]¸wªO SQL_AA_TRUE­C

  3. GRAPHIC ¦«Ž‘ÏÏ¦§÷ˆ©’û‹¸¢ùCðà Unicode ÝrÏ÷ú|ùØ¾×õûóÆ¦§ùƒðàÝÏ÷ýå­A Ýà
     CHAR ¦«Ž‘ÏÏ¦§÷ˆ©’û‹¸¢ùCðà Unicode ÝrÏ÷ú|ùØ¾× 1 ù 3 ðàÝÏ÷ýå­C Ýb
     GRAPHIC ¦«Ž‘ÝrÏ÷ÏŠðñ¦§ SQL ððùŒüqñ`ªO CHAR ¦«Ž‘ÝrÏ÷¦§Ï@¾b­A ÝìÝbÝÏ÷ýå
     ÏŠðñªOÏ@¬Ó¦§­C CHAR ¦«Ž‘¦§üÞÏjÝrÏ÷¦›®žªO 254­C GRAPHIC ¦«Ž‘¦§üÞÏjÝrÏ÷
     ¦›®žªO 127­C ðY¯í÷âýà÷ˆøT­A«Ñø¥ó\ SQL Reference "Functions" üû÷`ÏÏ¦§
     MAX­C

  4. ûØõ×Ï†Ýr¾× G Ýrð§ùà¯PÝrÏ÷Ï†ÝrøØõO­C ùãÝp­G

     SELECT * FROM mytable WHERE mychar = 'utf-8 data' AND mygraphic = G'ucs-2 data'

     æ—:
          û‹¸¢ Unicode ÷ˆ©’©wïNÏœ¯íðn G Ýrð§­C
     «Ñø¥ó\"Literals in Unicode Databases"­Aù£ñoù„ól÷ˆøTÏ×õ¢ús¦§Ï„ï¸­C

  5. Ï„ï¸ CLI/ODBC ¸M JDBC ·ü¾×æ{Ý­ÏœÝP¸¢Ï„ï¸Ï§õt¦§·ü¾×æ{Ý­­C ðY¯í CLI/ODBC
     Ï„ï¸¦§ªêÇ”÷ˆøT­A«Ñø¥ó\40.3, "CLI Guide and Reference(æLÏÏÏ†¦¸)"­C

  6. UCS-2 ÷ˆ©’¦§ÝÏ÷ýåÝ÷õ€¾iî…Ý]¾ð¾xÝàýõ­C DB2 ÝbÏ§ü­ªOùØ¾× big-endian ©‘
     Ý­­C

40.1.2 Ï†¾¢õ¢ús

ÝûÏ†¾¢õ¢úsÏUÝCÝüÇ”Ýb DB2 ¦¸¾¯ 7.1 ÏÏùØ¾× Unicode ¦§÷ˆøT­G

   * SQL Reference:

          Chapter 3 Language Elements

          Chapter 4 Functions
   * CLI Guide and Reference:

          Chapter 3. Using Advanced Features

          Appendix C. DB2 CLI and ODBC
   * Data Movement Utilities Guide and Reference, Appendix C.
     Export/Import/Load Utility File Formats

ðY¯íÝüÇ”Ýb DB2 ÏÏùØ¾× Unicode ¦§÷âýà÷ˆøT­A«Ñø¥úà Administration Guide ¦§
Appendix J. National Language Support (NLS)­G "Unicode/UCS-2 and UTF-8
Support in DB2 UDB"­C
  ------------------------------------------------------------------------

40.2 SQL Reference(æLÏÏÏ†¦¸)

40.2.1 Chapter 3 Language Elements

40.2.1.1 Promotion of Data Types

In this section table 5 shows the precedence list for each data type.
Please note:

  1. For a Unicode database, the following are considered to be equivalent
     data types:
        o CHAR and GRAPHIC
        o VARCHAR and VARGRAPHIC
        o LONG VARCHAR and LONG VARGRAPHIC
        o CLOB and DBCLOB
  2. In a Unicode database, it is possible to create functions where the
     only difference in the function signature is between equivalent CHAR
     and GRAPHIC data types, for example, foo(CHAR(8)) and foo(GRAPHIC(8)).
     We strongly recommend that you do not define such duplicate functions
     since migration to a future release will require one of them to be
     dropped before the migration will proceed.

     If such duplicate functions do exist, the choice of which one to
     invoke is determined by a two pass algorithm. The first pass attempts
     to find a match using the same algorithm as is used for resolving
     functions in a non-Unicode database. If no match is found, then a
     second pass will be done taking into account the following promotion
     precedence for CHAR and GRAPHIC strings:

     GRAPHIC-->CHAR-->VARGRAPHIC-->VARCHAR-->LONG VARGRAPHIC-->LONG VARCHAR-->DBCLOB-->CLOB

40.2.1.2 Casting Between Data Types

The following entry has been added to the list introduced as: "The
following casts involving distinct types are supported":

   * for a Unicode database, cast from a VARCHAR or VARGRAPHIC to distinct
     type DT with a source data type CHAR or GRAPHIC.

The following are updates to Table 6. Supported Casts between Built-in Data
Types. Only the affected rows of the table are included.

Table 31. Supported Casts between Built-in Data Types
                                                L
                                                O
                                                N
                              L                 G
 Target Data Type             O             V   V
                              N             A   A
                              G             R   R
                         V    V        G    G   G
                         A    A        R    R   R    D
                         R    R        A    A   A    B
                     C   C    C    C   P    P   P    C
                     H   H    H    L   H    H   H    L
 Source Data Type    A   A    A    O   I    I   I    O
 V                   R   R    R    B   C    C   C    B
 CHAR               Y    Y   Y    Y   Y1   Y1   -    -

 VARCHAR            Y    Y   Y    Y   Y1   Y1   -    -

 LONGVARCHAR        Y    Y   Y    Y    -   -   Y1   Y1

 CLOB               Y    Y   Y    Y    -   -    -   Y1

 GRAPHIC            Y1  Y1   -    -    Y   Y    Y    Y

 VARGRAPHIC         Y1  Y1   -    -    Y   Y    Y    Y

 LONGVARGRAPHIC     -    -   Y1   Y1   Y   Y    Y    Y

 DBCLOB             -    -   -    Y1   Y   Y    Y    Y

1
     Cast is only supported for Unicode databases.

40.2.1.3 Assignments and Comparisons

Assignments and comparisons involving both character and graphic data are
only supported when one of the strings is a literal. For function
resolution, graphic literals and character literals will both match
character and graphic function parameters.

The following are updates to Table 7. Data Type Compatibility for
Assignments and Comparisons. Only the affected rows of the table, and the
new footnote 6, are included:

          Binary   Decimal Floating CharacterGraphic           Time- Binary
 Operands Integer  Number  Point    String   String  Date Time stamp String  UDT
 CharacterNo       No      No       Yes      Yes 6   1    1    1     No 3    2
 String
 Graphic  No       No      No       Yes 6    Yes     No   No   No    No      2
 String

6
     Only supported for Unicode databases.

String Assignments

Storage Assignment

The last paragraph of this sub-section is modified as follows:

When a string is assigned to a fixed-length column and the length of the
string is less than the length attribute of the target, the string is
padded to the right with the necessary number of single-byte, double-byte,
or UCS-22 blanks. The pad character is always a blank even for columns
defined with the FOR BIT DATA attribute.

Retrieval Assignment

The third paragraph of this sub-section is modified as follows:

When a character string is assigned to a fixed-length variable and the
length of the string is less than the length attribute of the target, the
string is padded to the right with the necessary number of single-byte,
double-byte, or UCS-22 blanks. The pad character is always a blank even for
strings defined with the FOR BIT DATA attribute.

2
     UCS-2 defines several SPACE characters with different properties. For
     a Unicode database, the database manager always uses the ASCII SPACE
     at position x'0020' as UCS-2 blank. For an EUC database, the
     IDEOGRAPHIC SPACE at position x'3000' is used for padding GRAPHIC
     strings.

Conversion Rules for String Assignments

The following paragraph has been added to the end of this sub-section:

For Unicode databases, character strings can be assigned to a graphic
column, and graphic strings can be assigned to a character column.

DBCS Considerations for Graphic String Assignments

The first paragraph of this sub-section has been modified as follows:

Graphic string assignments are processed in a manner analogous to that for
character strings. For non-Unicode databases, graphic string data types are
compatible only with other graphic string data types, and never with
numeric, character string, or datetime data types. For Unicode databases,
graphic string data types are compatible with character string data types.

String Comparisons

Conversion Rules for Comparison

This sub-section has been modified as follows:

When two strings are compared, one of the strings is first converted, if
necessary, to the encoding scheme and/or code page of the other string. For
details, see the "Rules for String Conversions" section of Chapter 3
Language Elements in the SQL Reference.

40.2.1.4 Rules for Result Data Types

Character and Graphic Strings in a Unicode Database

This is a new sub-section inserted after the sub-section "Graphic Strings".

In a Unicode database, character strings and graphic strings are
compatible.
 If one operand is...   And the other operand   The data type of the
                        is...                   result is...
 GRAPHIC(x)             CHAR(y) or GRAPHIC(y)   GRAPHIC(z) where z =
                                                max(x,y)
 VARGRAPHIC(x)          CHAR(y) or VARCHAR(y)   VARGRAPHIC(z) where z =
                                                max(x,y)
 VARCHAR(x)             GRAPHIC(y) or           VARGRAPHIC(z) where z =
                        VARGRAPHIC              max(x,y)
 LONG VARGRAPHIC        CHAR(y) or VARCHAR(y)   LONG VARGRAPHIC
                        or LONG VARCHAR
 LONG VARCHAR           GRAPHIC(y) or           LONG VARGRAPHIC
                        VARGRAPHIC(y)
 DBCLOB(x)              CHAR(y) or VARCHAR(y)   DBCLOB(z) where z =
                        or CLOB(y)              max(x,y)
 DBCLOB(x)              LONG VARCHAR            DBCLOB(z) where z =
                                                max(x,16350)
 CLOB(x)                GRAPHIC(y) or           DBCLOB(z) where z =
                        VARGRAPHIC(y)           max(x,y)
 CLOB(x)                LONG VARGRAPHIC         DBCLOB(z) where z =
                                                max(x,16350)

40.2.1.5 Rules for String Conversions

The third point has been added to the following list in this section:

For each pair of code pages, the result is determined by the sequential
application of the following rules:

   * If the code pages are equal, the result is that code page.
   * If either code page is BIT DATA (code page 0), the result code page is
     BIT DATA.
   * In a Unicode database, if one code page denotes data in an encoding
     scheme different from the other code page, the result is UCS-2 over
     UTF-8 (that is, the graphic data type over the character data type).1
   * Otherwise, the result code page is determined by Table 8 of the "Rules
     for String Conversions" section of Chapter 3 Language Elements in the
     SQL Reference. An entry of 'first' in the table means the code page
     from the first operand is selected and an entry of 'second' means the
     code page from the second operand is selected.

1
     In a non-Unicode database, conversion between different encoding
     schemes is not supported.

40.2.1.6 Expressions

The following has been added:

In a Unicode database, an expression that accepts a character or graphic
string will accept any string types for which conversion is supported.

With the Concatenation Operator

The following has been added to the end of this sub-section:

In a Unicode database, concatenation involving both character string
operands and graphic string operands will first convert the character
operands to graphic operands. Note that in a non-Unicode database,
concatenation cannot involve both character and graphic operands.

40.2.1.7 Predicates

The following entry has been added to the list introduced by the sentence:
"The following rules apply to all types of predicates":

   * In a Unicode database, all predicates that accept a character or
     graphic string will accept any string types for which conversion is
     supported.

40.2.2 Chapter 4 Functions

40.2.2.1 Scalar Functions

The following sentence has been added to the end of this section:

In a Unicode database, all scalar functions that accept a character or
graphic string will accept any string types for which conversion is
supported.
  ------------------------------------------------------------------------

40.3 CLI Guide and Reference(æLÏÏÏ†¦¸)

40.3.1 Chapter 3. Using Advanced Features

The following is a new section for this chapter.

40.3.1.1 Writing a DB2 CLI Unicode Application

There are two main areas of support for DB2 CLI Unicode Applications:

  1. The addition of a set of functions that can accept Unicode string
     arguments in place of ANSI string arguments.
  2. The addition of new C and SQL data types to describe data as ANSI or
     Unicode data. The following sections provide more information for both
     of these areas. To be considered a Unicode application, the
     application must set the SQL_ATTR_ANSI_APP connection attribute to
     SQL_AA_FALSE, before a connection is made. This will ensure that CLI
     will connect as a Unicode client, and all Unicode data will be sent in
     either UTF-8 for CHAR data or UCS-2 for GRAPHIC data.

Unicode Functions

The following is a list of the ODBC API functions that support both Unicode
(W) and ANSI (A) versions (the function name will have a W for Unicode):

SQLBrowseConnect        SQLForeignKeys          SQLPrimaryKeys
SQLColAttribute         SQLGetConnectAttr       SQLProcedureColumns
SQLColAttributes        SQLGetConnectOption     SQLProcedures
SQLColumnPrivileges     SQLGetCursorName        SQLSetConnectAttr
SQLColumns              SQLGetDescField         SQLSetConnectOption
SQLConnect              SQLGetDescRec           SQLSetCursorName
SQLDataSources          SQLGetDiagField         SQLSetDescField
SQLDescribeCol          SQLGetDiagRec           SQLSetStmtAttr
SQLDriverConnect        SQLGetInfo              SQLSpecialColumns
SQLDrivers              SQLGetStmtAttr          SQLStatistics
SQLError                SQLNativeSQL            SQLTablePrivileges
SQLExecDirect           SQLPrepare              SQLTables

Unicode functions that always return, or take, string length arguments are
passed as count-of-characters. For functions that return length information
for server data, the display size and precision are described in number of
characters. When the length (transfer size of the data) could refer to
string or nonstring data, the length is described in octet lengths. For
example, SQLGetInfoW will still take the length as count-of-bytes, but
SQLExecDirectW will use count-of-characters. CLI will return result sets in
either Unicode or ANSI, depending on the application's binding. If an
application binds to SQL_C_CHAR, the driver will convert SQL_WCHAR data to
SQL_CHAR. The driver manager maps SQL_C_WCHAR to SQL_C_CHAR for ANSI
drivers but does no mapping for Unicode drivers.

New datatypes and valid conversions

There are two new CLI or ODBC defined data types, SQL_C_WCHAR and
SQL_WCHAR. SQL_C_WCHAR indicates that the C buffer contains UCS-2 data.
SQL_WCHAR indicates that a particular column or parameter marker contains
Unicode data. For DB2 Unicode Servers, graphic columns will be described as
SQL_WCHAR. Conversion will be allowed between SQL_C_WCHAR and SQL_CHAR,
SQL_VARCHAR, SQL_LONGVARCHAR and SQL_CLOB, as well as between the graphic
data types.

Table 32. Supported Data Conversions
                                                S                 S
                                                Q                 Q
                                                L           S  S  L
                                                _           Q  Q  _
                                                C           L  L  C
                                          S  S  _           _  _  _
                                          Q  Q  T           C  C  D
                                 S        L  L  Y           _  _  B     S
                                 Q     S  _  _  P  S     S  C  B  C  S  Q
                       S     S   L  S  Q  C  C  E  Q     Q  L  L  L  Q  L
                    S  Q  S  Q   _  Q  L  _  _  _  L     L  O  O  O  L  _
                    Q  L  Q  L   C  L  _  T  T  T  _  S  _  B  B  B  _  C
                    L  _  L  _   _  _  C  Y  Y  I  C  Q  C  _  _  _  C  _
                    _  C  _  C   T  C  _  P  P  M  _  L  _  L  L  L  _  N
                    C  _  C  _   I  _  D  E  E  E  B  _  D  O  O  O  B  U
                    _  W  _  S   N  F  O  _  _  S  I  C  B  C  C  C  I  M
                    C  C  L  H   Y  L  U  D  T  T  N  _  C  A  A  A  G  E
                    H  H  O  O   I  O  B  A  I  A  A  B  H  T  T  T  I  R
                    A  A  N  R   N  A  L  T  M  M  R  I  A  O  O  O  N  I
 SQL Data Type      R  R  G  T   T  T  E  E  E  P  Y  T  R  R  R  R  T  C
 BLOB               X   X                           D           X
 CHAR               D   X  X  X  X   X  X  X  X  X  X  X              X  X
 CLOB               D   X                           X        X
 DATE               X   X                  D     X
 DBCLOB                 X                           X     D        X
 DECIMAL            D   X  X  X  X   X  X           X  X              X  X
 DOUBLE             X   X  X  X  X   X  D              X              X  X
 FLOAT              X   X  X  X  X   X  D              X              X  X
 GRAPHIC            X   X                                 D
 (Non-Unicode)
 GRAPHIC            X   X  X  X  X   X  X  X  X  X  X  X  D           X
 (Unicode)
 INTEGER            X   X  D  X  X   X  X              X              X  X
 LONG               D   X                           X
 VARCHAR
 LONG               X   X                           X     D
 VARGRAPHIC
 (Non-Unicode)
 LONG               X   X                           X     D
 VARGRAPHIC
 (Unicode)
 NUMERIC            D   X  X  X  X   X  X              X                 X
 REAL               X   X  X  X  X   D  X              X                 X
 SMALLINT           X   X  X  D  X   X  X              X              X  X
 BIGINT             X   X  X  X  X   X  X           X  X              D  X
 TIME               X   X                     D  X
 TIMESTAMP          X   X                  X  X  D
 VARCHAR            D   X  X  X  X   X  X  X  X  X  X  X              X  X
 VARGRAPHIC         X   X                                 D
 (Non-Unicode)
 VARGRAPHIC         X   X  X  X  X   X  X  X  X  X  X  X  D           X
 (Unicode)

Notes:

     D
          Conversion is supported. This is the default conversion for the
          SQL data type.

     X
          All IBM DBMSs support the conversion.

     blank
          No IBM DBMS supports the conversion.

        o Data is not converted to LOB Locator types, rather locators
          represent a data value, refer to Using Large Objects for more
          information.
        o SQL_C_NUMERIC is only available on 32-bit Windows operating
          systems.

Obsolete Keyword/Patch Value

Before Unicode applications were supported, applications that were written
to work with single byte character data could be made to work with double
byte graphic data by a series of cli ini file keywords, such as GRAPHIC=1,2
or 3, Patch2=7 etc. These workarounds presented graphic data as character
data, and also affected the reported length of the data.

These keywords are no longer required for Unicode applications, and in fact
should not be used otherwise there could be serious side effects. If it is
not known if a particular application is a Unicode application, we suggest
you try without any of the keywords that affect the handling of graphic
data.

Literals in Unicode Databases

In Non-Unicode databases, data in LONG VARGRAPHIC and LONG VARCHAR columns
cannot be compared. Data in GRAPHIC/VARGRAPHIC and CHAR/VARCHAR columns can
only be compared, or assigned to each other, using explicit cast functions
since no implicit code page conversion is supported. This includes
GRAPHIC/VARGRAPHIC and CHAR/VARCHAR literals where a GRAPHIC/VARGRAPHIC
literal is differentiated from a CHAR/VARCHAR literal by a G prefix.

For Unicode databases, casting between GRAPHIC/VARGRAPHIC and CHAR/VARCHAR
literals is not required. Also, a G prefix is not required in front of a
GRAPHIC/VARGRAPHIC literal. Provided at least one of the arguments is a
literal, implicit conversions occur. This allows literals with or without
the G prefix to be used within statements that use either SQLPrepareW() or
SQLExecDirect(). Literals for LONG VARGRAPHICs still must have a G prefix.

For more information, please see "Casting Between Data Types" in Chapter 3
Language Elements of the SQL Reference.

New CLI Configuration Keywords

The following three keywords have been added to avoid any extra overhead
when Unicode applications connect to a database.

  1. DisableUnicode

     Keyword Description:
          Disables the underlying support for Unicode.

     db2cli.ini Keyword Syntax:
          DisableUnicode = 0 | 1

     Default Setting:
          0 (false)

     DB2 CLI/ODBC Settings Tab:
          This keyword cannot be set using the CLI/ODBC Settings notebook.
          The db2cli.ini file must be modified directly to make use of this
          keyword.

     Usage Notes:

     With Unicode support enabled, and when called by a Unicode
     application, CLI will attempt to connect to the database using the
     best client codepage possible to ensure there is no unnecessary data
     loss due to codepage conversion. This may increase the connection time
     as codepages are exchanged, or may cause codepage conversions on the
     client that did not occur before this support was added.

     Setting this keyword to True will cause all Unicode data to be
     converted to the application's local codepage first, before the data
     is sent to the server. This can cause data loss for any data that
     cannot be represented in the local codepage.

  2. ConnectCodepage

     Keyword Description:
          Specifies a specific codepage to use when connecting to the data
          source to avoid extra connection overhead.

     db2cli.ini Keyword Syntax:
          ConnectCodepage = 0 | 1 <any valid db2 codepage>

     Default Setting:
          0

     DB2 CLI/ODBC Settings Tab:
          This keyword cannot be set using the CLI/ODBC Settings notebook.
          The db2cli.ini file must be modified directly to make use of this
          keyword.

     Usage Notes:

     Non-Unicode applications always connect to the database using the
     application's local codepage, or the DB2Codepage environment setting.
     By default, CLI will ensure that Unicode applications will connect to
     Unicode databases using UTF-8 and UCS-2 codepages, and will connect to
     non-Unicode databases using the database's codepage. This ensures
     there is no unnecessary data loss due to codepage conversion.

     This keyword allows the user to specify the database's codepage when
     connecting to a non-Unicode database in order to avoid any extra
     overhead on the connection.

     Specify a value of 1 to cause SQLDriverConnect() to return the correct
     value in the output connection string, so the value can be used on
     future SQLDriverConnect() calls.

  3. UnicodeServer

     Keyword Description:
          Indicates that the data source is a Unicode Server. Equivalent to
          setting ConnectCodepage=1208.

     db2cli.ini Keyword Syntax:
          UnicodeServer = 0 | 1

     Default Setting:
          0

     DB2 CLI/ODBC Settings Tab:
          This keyword cannot be set using the CLI/ODBC Settings notebook.
          The db2cli.ini file must be modified directly to make use of this
          keyword.

     Usage Notes:

     This keyword is equivalent to ConnectCodepage=1208, and is added only
     for convenience. Set this keyword to avoid extra connect overhead when
     connecting to DB2 for OS/390 Version 7 or higher. There is no need to
     set this keyword for DB2 for Windows, DB2 for Unix or DB2 for OS/2
     databases, since there is no extra processing required.

40.3.2 Appendix C. DB2 CLI and ODBC

The following is a new section added to this appendix.

40.3.2.1 ODBC Unicode Applications

A Unicode ODBC application sends and retrieves character data primarily in
UCS-2. It does this by calling Unicode versions of the ODBC functions ('W'
suffix) and by indicating Unicode data types. The application does not
explicitly specify a local code page. The application can still call the
ANSI functions and pass local code page strings.

For example, the application may call SQLConnectW() and pass the DSN, User
ID and Password as Unicode arguments. It may then call SQLExecDirectW() and
pass in a Unicode SQL statement string, and then bind a combination of ANSI
local code page buffers (SQL_C_CHAR) and Unicode buffers (SQL_C_WCHAR). The
database data types may be local code page or UCS-2 and UTF-8.

If a CLI application calls SQLConnectW or calls SQLSetConnectAttr with
SQL_ATTR_ANSI_APP set to SQL_AA_FALSE, the application is considered a
Unicode application. This means all CHAR data is sent and received from the
database in UTF-8 format. The application can then fetch CHAR data into
SQL_C_CHAR buffers in local code page (with possible data loss), or into
SQL_C_WCHAR buffers in UCS-2 without any data loss.

If the application does not do either of the two calls above, CHAR data is
converted to the applications local codepage at the server. This means CHAR
data fetched into SQL_C_WCHAR may suffer data loss.

If the DB2CODEPAGE instance variable is set (using db2set) to code page
1208 (UTF-8), the application will receive all CHAR data in UTF-8 since
this is now the local code page. The application must also ensure that all
CHAR input data is also in UTF-8. ODBC also assumes that all SQL_C_WCHAR
data is in the native endian format. CLI will perform any required
byte-reversal for SQL_C_WCHAR.

ODBC Unicode Versus Non-Unicode Applications

This release of DB2 Universal Database contains the SQLConnectW() API. A
Unicode driver must export SQLConnectW in order to be recognized as a
Unicode driver by the driver manager. It is important to note that many
ODBC applications (such as Microsoft Access and Visual Basic) call
SQLConnectW(). In previous releases of DB2 Universal Database, DB2 CLI has
not supported this API, and thus was not recognized as a Unicode driver by
the ODBC driver manager. This caused the ODBC driver manager to convert all
Unicode data to the application's local code page. With the added support
of the SQLConnectW() function, these applications will now connect as
Unicode applications and DB2 CLI will take care of all required data
conversion.

DB2 CLI now accepts Unicode APIs (with a suffix of "W") and regular ANSI
APIs. ODBC defines a set of functions with a suffix of "A", but the driver
manager does not pass ANSI functions with the "A" suffix to the driver.
Instead, it converts these functions to ANSI function calls without the
suffix, and then passes them to the driver.

An ODBC application that calls the SQLConnectW() API is considered a
Unicode application. Since the ODBC driver manager will always call the
SQLConnectW() API regardless of what version the application called, ODBC
introduced the SQL_ATTR_ANSI_APP connect attribute to notify the driver if
the application should be considered an ANSI or UNICODE application. If
SQL_ATTR_ANSI_APP is not set to SQL_AA_FALSE, DB2 CLI converts all Unicode
data to the local code page before sending it to the server.
  ------------------------------------------------------------------------

40.4 Data Movement Utilities Guide and Reference(æLÏÏÏ†¦¸)

40.4.1 Appendix C. Export/Import/Load Utility File Formats

The following update has been added to this Appendix:

The export, import, and load utilities are not supported when they are used
with a Unicode client connected to a non-Unicode database. Unicode client
files are only supported when the Unicode client is connected to a Unicode
database.
  ------------------------------------------------------------------------

üsñæù¾Dûq÷œùtý×

ü­¾ö¾¨ì

   * üsñæ·“ûã÷¾R÷ˆ©’
        o 41.1 Ýb VM ·“ûãÏUÝw÷Ó·ü¾×æ{Ý­Ý›¦Aóû
        o 41.2 CLI/ODBC/JDBC ª[§c PATCH1 ¸M PATCH2 ü]¸wðÔ

  ------------------------------------------------------------------------

üsñæ·“ûã÷¾R÷ˆ©’

  ------------------------------------------------------------------------

41.1 Ýb VM ·“ûãÏUÝw÷Ó·ü¾×æ{Ý­Ý›¦Aóû

ús¬WÏUÝC¾yÏlù­uïœù¥øØªq÷ˆøT­vüû÷`­A­u¸w÷q·ü¾×æ{Ý­Ý›¦Aóû­vÝ÷üû÷`¦§ýŽÏ@¾yÏl
Ïõ® ­G

   RDB_NAME ¾¥ SQLSTART EXEC ïœù¥­A¾iõ@ªø DBNAME ø¥¬’­C

  ------------------------------------------------------------------------

41.2 CLI/ODBC/JDBC ª[§c PATCH1 ¸M PATCH2 ü]¸wðÔ

CLI/ODBC/JDBC XøÒæ{Ý­¦§ª[§c¾i¾H¾¥ñqŽíî÷ª[§c¯ýõUæ{Ý­­BODBC XøÒæ{Ý­§èýzæ{Ý­
­]ðYùtý×ÝüÝw÷ÓÝûæ{Ý­­^­B«s¨Š db2cli.ini ·ùàõûÝù­C ÷âýà÷ˆ©’­A«Ñø¥ó\Ýw÷Ó¯Pª[
§c÷¾R¸× CLI Guide and Reference­C

ñz¾i¾HüzûL db2cli.ini ·­A¸×¦ÞüzûL SQLDriverConnect() ¸× SQLBrowseConnect()
CLI API­A ®¸w PATCH1 Ï× PATCH2 Ç”µ„Ýr¦§ðÔ­Aùàðžõ‹ DB2 CLI/ODBC XøÒæ{Ý­¦§
ûwü]Ý‘ªø­C

ñz¾i¾HñNùØ¾×¦ÞúQðnü]¸w¦§¸ãÝüÇ”µ„Ýr¾[ÝbÏ@ø_­A ùà®¸w PATCH1 Ç”µ„Ýr­C ùãÝp­A
Ýp¦G®¸wðž÷æ{Ý­ 1­B2 Ï× 8­A®h PATCH1 ¦§ðÔñNªO 11­C ÏUÝCªOXøÒæ{Ý­ÏWùCÏ@Ç”
µ„ÝrðÔÏ×ù„©Ž¦G¦§¯­¸£­G

 1 - üoùØñoXøÒæ{Ý­ñNújïM "count(exp)"­AùÇ¾H "count(distinct exp)"
     ÷mï®¾Ý­CÝ]ªøÝüù€¦¸¾¯¦§ DB2 Ï„ï¸ "count(exp)" ¯y¦k­A¾B÷à¯y¦k
     ªO¾¥ªYù€ ODBC ·ü¾×æ{Ý­¸ã®¾á¦§­A¸ã¾H¯íðnüo§©Ž¦G­C
     ú¡Ý›¦AóûÏœÏ„ï¸ "count(exp)" ¯y¦k©­AMicrosoft ·ü¾×æ{Ý­¯íðn¾Ý­C
 2 - ü­¾ö ODBC ·ü¾×æ{Ý­ú|üQü]üï­Aú¡ SQLGetTypeInfo() ù‡¬’ÏÏû‹¸¢ LITERAL_PREFIX
     ¸× LITERAL_SUFFIX ¦«Ž‘ô€Ý^ SQL_NULL_DATA ©­Cüoú|ñjùŒXøÒæ{Ý­õ‹Ýàô€Ý^Ï@ðà
     ¦ÝrÝˆ­CImpromptu 2.0 ú|¯íðn¾×ù­C
 4 - üoú|ñjùŒXøÒæ{Ý­ñN¨‚ÏJ©ô­¶WøO÷ˆ©’æ›ªøÏ‚ïµ÷ˆ©’­AÝp¦G©ô­¸M©ô­¶WøO¦§Ïp¬’
     ü­¾öªOûs­CMicrosoft Access ú|¯íðn¾×ù­C
 8 - Ýp¦G©ô­¶WøO¦§Ï‚ïµü­¾öªø 1899-12-30­Aüoú|ñjùŒXøÒæ{Ý­
     ñN¨‚ÏJ©ô­¶WøO÷ˆ©’æ›ªø©ô­÷ˆ©’­CMicrosoft Access ¯íðnüo§©Ž¦G­C
 16 - ÏœùØ¾×­C

 32 - üoú|ñjùŒXøÒæ{Ý­Ïœô€Ý^Ç”¸¢ SQL_LONGVARCHAR­BSQL_LONGVARBINARY Ï×
      SQL_LONGVARGRAPHIC ¦«Ž‘¦§÷ˆøT­CÝb·ü¾×æ{Ý­ªíùà­AïNÝnûüùÇÏœÏ„ï¸¦›Ž‘Ý­C
      Lotus 123 ú|¯íðn¾×ù­C
 64 - üoú|ñjùŒXøÒæ{Ý­¾H NULL ðÔýžÏŒûØõ×¨‚¾XÝrÝˆ­C
      ¶—ÝÏ÷ýå·“ûãÏÏ¦§ Microsoft Access ¯íðnüo§©Ž¦G­C
 128 - üoú|ñjùŒXøÒæ{Ý­ì "SELECT Config, nValue FROM MSysConf" ªd÷áùÝ›¦Aóû¾h­C
       ¾®eXøÒæ{Ý­ú|ô€Ý^¨—¯~­AªêÇ” SQLSTATE ðÔªO S0002 (õ„Ïœù¦¡©‘)­CÝp¦GùØ¾×¦Þ
       ÏwÝb÷ˆ©’©wÏÏ®¾áÏFÝûª[§c¦¡©‘¾Bõ’ñ‘·ü¾×æ{Ý­¾i¾HÝsù£©ú|¯íðn¾×ù­C
 256 - üoú|ñjùŒXøÒæ{Ý­Ýb SQLStatistics() ¸I¾sÏÏ¾ìô€Ý^¾Dðnµ„¦«Ž‘­C¾®e­AXøÒæ{Ý­
       ú|ùÞúàîµÏèÝW§ëô€Ý^Ïwñ’õ€¦§îµÏè­Aù§ªO¬Ñú€¦§ ODBC Ý‘ªø­C
 512 - üoú|ñjùŒXøÒæ{Ý­Ýb SQLGetFunctions() ÏÏû‹ SQL_API_SQLTABLEPRIVILEGES
       Ï× SQL_API_SQLCOLUMNPRIVILEGES ùƒ¦Þô€Ý^ FALSE­C
 1024 - üoú|ñjùŒXøÒæ{Ý­Ýb SQLExecute() ¸× SQLExecDirect() ÏÏô€Ý^ SQL_SUCCESS­A
        Ýà®D SQL_NO_DATA_FOUND­AÝp¦GøäÝ‘¦§ UPDATE ¸× DELETE üîðzÝ­ùSÝüû‹¾“Ý¢óŒÝC
        æo¾Öõ@¾×­CVisual Basic ·ü¾×æ{Ý­ú|¯íðn¾×ù­C
 2048 - ÏœùØ¾×­C

 4096 - ÝbÝêøÒ COMMIT ¬ãÝ­ÏÏ©­A¸¢Ç”üªï†¬Ñ® ­Aüoú|ñjùŒXøÒæ{Ý­
        Ïœæo¾X COMMIT­C
 8192 - üoú|ñjùŒXøÒæ{Ý­Ýb¸I¾s·xÝsæ{õ€® ô€Ý^ÇB¾~¦§æý¦Gôø­Cüoðàæý¦GôøªOÏ@ðàü‘Ï@
        óŒÝC¦§æý¦Gôø­A¾¥·xÝsæ{õ€¦§¨‚¾XðÔýåÝù­C¾iüQ Powerbuild ·ü¾×æ{Ý­ùàÝsù£­C
 32768 - üoú|ñjùŒXøÒæ{Ý­ùØ Microsoft Query ·ü¾×æ{Ý­î…ùØ¾×
         DB2 MVS ÝP÷qÝr­C
 65536 - üoú|ñjùŒXøÒæ{Ý­ÝêÝ‘ï­ÏJÏ@ðà "G" ùûˆ¯éÏWªøûØõ×Ï†Ýr¦§ÝrÏ÷Ï†Ýr®eðñ­C
         üoðàðž÷æ{Ý­Ýb¶—ÝÏ÷ýå·“ûãÏÏÏuõ@©Ï@¸wðnïœù¥­C
 131072 - üoú|ñjùŒXøÒæ{Ý­ñN©ô­¶WøO¦«Ž‘æ›ªøÏ@ðà CHAR(26) ¦«Ž‘­AÝb¾ÝªOÏ@ðàøáÏ@
          îµÏè¦§Ï@ü­¾ö©­CMicrosoft ·ü¾×æ{Ý­ú|¯íðn¾×ù­C
 262144 - üoú|ñjùŒXøÒæ{Ý­ùØ¾× pseudo-catalog ¦¡©‘ db2cli.procedures­AÝà®D
          SYSCAT.PROCEDURES Ï× SYSCAT.PROCPARMS ¦¡©‘­C
 524288 - üoú|ñjùŒXøÒæ{Ý­ùØ¾× SYSTEM_TABLE_SCHEMA­AÝà®D TABLE_SCHEMA­A
          Ýbû‹ DB2/400 V3.x ùtý×õ@ùtý×ªd÷á©­Cüo¬Ó¾iïœ¦@©Žî…­C
 1048576 - üoú|ñjùŒXøÒæ{Ý­üzûL SQLPutData() ñNûs¦›®ž¦§ÝrÝˆæ›ªø SQL_NULL_DATA­C

PATCH2 Ç”µ„ÝrÏœÝP¸¢ PATCH1 Ç”µ„Ýr­C Ýbüo§ñ­¦pÏÏ­AñNùØ¾×ür¶IÏ·ûjÝrÏ÷ùà®¸w
Ýhðàðž÷æ{Ý­­C ùãÝp­AÝp¦G®¸wÏFðž÷æ{Ý­ 1­B4 Ï× 5­A®h PATCH2 ñNùÆÝüðÔ
"1,4,5"­C ÏUÝCªOXøÒæ{Ý­ÏWùCÏ@Ç”µ„ÝrðÔÏ×ù„©Ž¦G¦§¯­¸£­G

 1 - üoú|ñjùŒXøÒæ{Ý­ñN CALL üîðzÝ­ÏÏ¦§·xÝsæ{õ€ÝW§ë¶…ï®ªøÏj¬gÝr‚­C
 2 - ÏœùØ¾×­C

 3 - üoú|ñjùŒXøÒæ{Ý­ñN§ä¾¸I¾s¦§¸ãÝüÏè¬’¶…ï®ªøÏj¬gÝr‚­C

 4 - üoú|ñjùŒXøÒæ{Ý­û‹¸¢§ä¾¸I¾s (Ï]ïNªO SQLColumns()­BSQLProcedureColumns() æ¾æ¾)
     ô€Ý^ÇçÝ¦¸¾¯ 2.1.2 ¦§æý¦Gôø­AÝà®DÇçÝ¦¸¾¯ 5 ¦§æý¦Gôø­C
 5 - üoú|ñjùŒXøÒæ{Ý­ÏœðnüÞù×Ï’¨‚ÏJ VARCHAR ¦«Ž‘¦§üBýz­A®ÝV÷ˆ©’¦§®¬Ñ¸M®ÝV¦›®ž¦§
     ®¬ÑÝbøOóÑ‚ÏÏªOüsŽ•¦§­C
 6 - üoú|ñjùŒXøÒæ{Ý­ô€Ý^ÏœÏ„ï¸¾iñýøÒï†¬Ñ¦§øT©õ­CVisual Basic æ{Ý­ú|¯íðn¾×ù­AÝp¦G
     DB2 ñqŽíî÷ªO¦¸¾¯ 5­A¾BÝ›¦AóûªO DB2 UDB ¦¸¾¯ 5­C
 7 - üoú|ñjùŒXøÒæ{Ý­ñN¸ãÝü GRAPHIC ¦«Ž‘÷ˆ©’Çç®ªû‹ªMù CHAR
     ¦«Ž‘÷ˆ©’Çç®ª­CÝb¶—ÝÏ÷ýå·“ûãÏÏ¯íðnüo§©Ž¦G­C
 8 - üoú|ñjùŒXøÒæ{Ý­¸¨ýÏ§ä¾¸I¾sÏÏ¦§¾¨ìújïMÏè¬’­C
 9 - ï†¬ÑïœÝðÇ”üª©Ïœðn COMMIT
 10 - ÏœùØ¾×
 11 - ü›õiÏ„ï¸¾¨ìÝW§ë, (VB ·xÝsæ{õ€)
 12 - ñq§ä¾¸I¾sÏè¬’øœ¾h¶—Ïè÷û, (Visual Interdev)
 13 - «ÑÏñN db2cli.ini ¦§Ç”µ„ÝrýK¾[ù¨‚¾XüsñæÝrÝˆ
 14 - ¸¨ýÏ SQLProcedures() Ï× SQLProcedureColumns() ÏW¦§§ä¾ÝW§ë
 15 - ùØ¾×¾y¶I¾N¦¡ÝrÏ÷¨‚¾XÏÏ¦§Ïp¬’¶Iý÷û
 16 - ñjð½ô€Ý^ùCÏ@ô}ñã¦§¯­¸£÷ˆøT
 17 - «ÑÏÝb¯­¸£ÏWô€Ý^¦«Ž‘ÝW§ë
 18 - ûµ÷å¾Hø¥¬’øO÷ûù£¾NÏ†Ýr
 19 - ¾®e­ADB2 MVS V4.1 ÏœÏ„ï¸ ODBC ¯y¦k­AÝ]ªø¾Ý©eü\Ýb¾~ü­æýÝXÏl¾yÏÏ¦§
      ON Ïl¾y¾iÝüªA¸ú­C
      ô}ñãüoðà PATCH2 ú|óðP IBM DB2 ODBC XøÒæ{Ý­Ýb¾~ü­æýÝXÏl¾yÝb ODBC
      ESC õ€ÝCÏÏ©ñNüsÝr÷ûøœ¾h­Cüoðà PATCH2 ¾uÝüÝbÏœõQ¸¢ DB2 MVS 4.1 ©Ï~ùØ¾×­C
 20 - ¾®e­AMVS ÏW¦§ DB2 ÏœÏ„ï¸ø¥¬’øO÷ûªøùƒðàûB§ƒÏ÷ (expression ? BETWEEN ?) ¦§
      BETWEEN ðzæ­Cô}ñãüoðàðž÷æ{Ý­ú|óðP IBM ODBC XøÒæ{Ý­ñNðzæ¶Ñ¬gªø
      (expression >= ? and expression <= ?)­C
 21 - ñN·xÝsæ{õ€¦§¸ãÝüôÔ OUTPUT ø¥¬’ü]¸wªø SQL_NULL_DATA
 22 - üoðà PATCH2 ú|óðP IBM ODBC XøÒæ{Ý­ü›õiÏœÏ„ï¸¾~ü­æýÝX (OUTER Join)­C
      üoóA¾×¸¢ÝbùØ¾×¾~ü­æýÝX©üîðzÝ­©ú|ýœ¾Ö SELECT DISTINCT col1 ¸×
      ORDER BY col1 ¦§·ü¾×æ{Ý­­Aù„ÏÏ col1 ¦§¦›®žÏj¸¢ 254 ðàÝrÏ÷­A¾BüyÝù
      DB2 UDB ô€Ý^¨—¯~ (Ý]ªø DB2 UDB ÝbÝû¾×¦kÏWÏœÏ„ï¸Ïj¸¢ 254 ðàÝÏ÷ýå¦§¦«Ž‘
 23 - «ÑÏüÞù×Ï’üzûL cbColDef=0 æýÝX¦§ø¥¬’Ïõ¨‚ÏJ
 24 - Ýsù£û‹ªM©ô­¦§ûˆùãªøÝrÏ÷
 25 - Ýsù£Ïp¬’¦«Ž‘¦§ûˆùã - øœ¾hÝrÏ÷üîðzõ·§í¦§ûs
 26 - ÏœñN SQL æ{Ý­ 464 ô€Ý^æû·ü¾×æ{Ý­ - ¦¡¾šÏwô€Ý^æý¦Gôø
 27 - ð½ùØ SQLTables ùØ¾× TABLETYPE Ç”µ„ÝrðÔ­AõYùØ·ü¾×æ{Ý­®¸wÏFÏ@ðàÝü©ŽðÔ
 28 - ¯­¸£ûˆ¯é¦§¦«Ž‘ªø¶—ð¨¦«Ž‘
 29 - Ïp¬’¦«Ž‘¦§ ADO ûˆùã - øœ¾h x ðÔ¦§®eóûs­Aù„ÏÏ x ªø 1 > x > -1­]ªYù€ MDAC ¦¸¾¯¯íðnÝû©Ž¦G­^
 30 - õ™ù£üÞù×Ï’©­AøñÏŒùØ¾×·xÝsæ{õ€
 31 - Ý^ü› SQLStatistics ¸I¾sõOÝW¦§ý×ðpðÔ
 32 - ÷mï® SQL æ{Ý­ -727 ðÝ]«X 4 üBýzæ{õ€
 33 - Ýb¶…ï®ÝùÝrÏ÷©­Aô€Ý^©ô­¶WøO¦§ ISO ¦¸¾¯
      (ªêû‹¸¢ ODBC ¦¸¾¯)
 34 - ¾H CHAR ÝW§ëùàÝ^ü› CHAR FOR BIT DATA ¦«Ž‘
 35 - SQL_DESC_BASE_TABLE_NAMER üQðnùDÏUÝ^ü›Ï@ðàæL©Ž¦§¦¡©‘ÝW§ë - ADO øá¦üÞù×Ï’
 36 - ®Oîd
 37 - ®Oîd

  ------------------------------------------------------------------------

Ï@î‰÷ˆøT

ü­¾ö¾¨ì

   * Ï@î‰÷ˆøT
        o 42.1 DB2 Universal Database Business Intelligence õ™ütóŽì
        o 42.2 DB2 Everywhere Ïwõ‹ªø DB2 Everyplace
        o 42.3 ú’û®¯íùD
        o 42.4 ÷åûØñq DB2 Run-time Client üsæýóðP­uõ„Ïœùüsæý·©ž­v¨—¯~
        o 42.5 Search ñïîµ (Search Discovery)
        o 42.6 HP-UX 11 ¦§øOóÑ‚æ›æ­
        o 42.7 dlfm client_conf ¾½©Ž©ùØ¾×¦ÞÏõøÒõ@
        o 42.8 ®šÏ™ùœ¦§ù’¾¢­G«’¯sñ`ónæ{Ý­Ýb dlfm øñÏŒ©ùSÝüøñÏŒ
        o 42.9 ÷¥øœÝw÷Ó DB2 DFS ñqŽíî÷ñãøÒæ{Ý­
        o 42.10 Windows NT ñqŽíî÷ùðÏ·‡Çã
        o 42.11 Ýb®¾áÏlæ{õ€© AutoLoader ¾iî…ú|ú¡ñ¬
        o 42.12 DATALINK ï_÷m
        o 42.13 Windows NT (CS/NT) ¦§ IBM Communications Ý›¦Aóû¸w÷qùØ¾×¦Þ
          ID ¸MüqÝ‘«X
             + 42.13.1 ÷`¶I¸w÷q
        o 42.14 µpÝXùtý×¦§ððùŒ
        o 42.15 DataJoiner ððùŒ
        o 42.16 Windows NT ¦§õ’õBùàÏ†÷ˆøT®ª¨ì§èýzæ{Ý­
        o 42.17 Microsoft SNA Server ¸M SNA Ýhî÷õ¢ús (ùƒô¾ªq«T¸w) Ï„ï¸
        o 42.18 ñãøÒ Windows Ïõ® æL¦kñãøÒ DB2 ¦§ SNA SPM
        o 42.19 DB2 §èýzÝ›¦Aóû¦§¯yù¾·“ûãü]¸w
        o 42.20 ñô©|æL©Ž
        o 42.21 Windows NT Ï× Windows 2000 ÏW¦§ DB2 ¦AøÔñbÏ ¯íùD
        o 42.22 Ýb¦¸¾¯ 6 ÏÏ®¾á¦§ Query Patroller ùØ¾×¦Þ¾½¾hÏF EXECUTE ñM¾×
          v
        o 42.23 Query Patroller ððùŒ
        o 42.24 ¯íðn«T¸w¸ãÝüú|Ýb÷ˆ©’ðš·xÏÏÏá(DWC)ÏÏùØ¾×¦§ùØ¾×¦Þ¸w÷qæ{Ý­
        o 42.25 ÷ˆ©’ðš·xÏÏÏá¸R¾OÝ‘ôž¾X¦§ús¨‹ôæ
        o 42.26 Backup Services APIs (XBSA)
        o 42.27 OS/390 ¾Nýzæ{Ý­
             + 42.27.1 Ýw÷Óúõ’[
             + 42.27.2 Ýw÷Ó¸£ýà
             + 42.27.3 ü]÷mÇB¾~¦§¾Nýzæ{Ý­ù‡¬’
             + 42.27.4 ¾×Žýæoæ{Ý­ñ’æ{ðš·xùB’J (XTClient)
             + 42.27.5 ¶…ï®æ{Ý­
             + 42.27.6 Ýsù£ DB2 ùtÝCÏõ¾~¦§÷ˆ©’©w
             + 42.27.7 øäÝ‘ DB2 for OS/390 Ï«¾×æ{Ý­
             + 42.27.8 õê¬g
             + 42.27.9 ¾Nýzæ{Ý­øO÷
        o 42.28 Windows NT ÏW¦§ñqŽíî÷§íõ™ù£
        o 42.29 Enterprise Edition UNIX CD-ROM ¦§÷å¾×ýœ®~
        o 42.30 DB2 Connect Enterprise Edition UNIX CD-ROM ¦§÷å¾×ýœ®~
        o 42.31 ñÓñ¢ Data Links Manager
        o 42.32 ùØ¾× SMIT ÷¥øœÝw÷Ó DLFM Ï÷¾¢¾iî…ú|øœ¾hÇB¾~¦§·©žôø
        o 42.33 Ýb Windows 2000 ÏWùØ¾× CLP ©æo¾Ö¨—¯~ SQL1035N
        o 42.34 SQL ¯ýõUæ{Ý­¦§¾[ñj¾\î…
        o 42.35 Linux ÏW¦§ DB2 ¦§ Gnome ¸M KDE ©…ðñóÆÝX
        o 42.36 Ýb Windows 2000 Terminal Server §èýz¬ãÝ­ÏUøäÝ‘ DB2
        o 42.37 ü’¾ö¯Pï_÷m®¾O¦§«uÏW¯­¸£
        o 42.38 "Warehouse Manager" ·üªø "DB2 Warehouse Manager"

  ------------------------------------------------------------------------

Ï@î‰÷ˆøT

  ------------------------------------------------------------------------

42.1 DB2 Universal Database Business Intelligence õ™ütóŽì

­uõ™ütóŽì­vÏœóA¾×¸¢ DB2 for Linux ¸× Linux/390­C

¾HÏp¦§ùtý×Ýr®ªøäÝ‘­uõ™ütóŽì­v­A¾i·•ñoüÞù×©Ž¦G­Cñz¾iî…¯íðn«åóÆ Web ¶sŽìóû¦§
Ýr®ªÏjÏp­A ¾H¾¨«TÝaÝb OS/2 ÏW·Óæ›­uõ™ütóŽì­v­C«Ñø¥úà Web ¶sŽìóû¦§¯­¸£­A¾H
ù£ño«åóÆÝr®ªÏjÏp¦§÷ˆøT­C ðYðn¾¨«TÝa·Óæ›­uõ™ütóŽì­v(ôÔóA¾×¸¢ SBCS)­A®Žüñz
ùØ¾× 8 ¶I¦§ Helv Ýr®ª­Cøwû‹Ï‚¾¯Ï×µ£øˆ®ÔÏ ­A®ŽüñzùØ¾× 8 ¶I¦§ Mincho Ýr®ª­C
ü]¸wÝr®ª¦§üáÝnü]¸w©­A«Ñ«T¸w¨‹ù£­uüáÝnü]¸w­væ›æ­­uÝr®ª­vðô¦§­uùØ¾×ûwü]Ýr
®ª­A÷mï®Ï†¾¢®¸w¦§Ýr®ª­v¨‹ôæ­C

ÝbªYù€ùãÏl÷Þ­A¾iî…ú|ÝbýŽÏGðà¶sŽìóûæ›æ­® ðññãøÒ­uõ™ütóŽì­v­C ðYðnõ¢¾¨üoðàøí
ÇD­A«ÑÇ”üª­uõ™ütóŽì­v­AùÇ¨¡ï` 2.4, ñãøÒ Netscape ©ýœ¾Ö¦§¨—¯~øT©õ ÷Þ¦§ùB
’J­C

ñãøÒ­uõ™ütóŽì­v©­Añz¾iî…ú|ñæÝªùÇçÝÏUÝCùƒÝ‘¦§ JavaScript ¨—¯~­G

   file:/C/Program Files/SQLLIB/doc/html/db2qt/index4e.htm­A65 Ý‘­G

   æ›æ­¾¬¸w÷q­C

üoðà JavaScript ¨—¯~ú|¦ìÏŒ­uõ™ütóŽì­vñãøÒðô index4e.htm­A ÝbñãøÒ­uõ™ütó
Žì­v® ÝêøÒÇ”üª­C¾i¶€¾¥Ç”üªÆ¾š index4e.htm ¦§¶sŽìóûæ›æ­ùàÇ”üª­uõ™ütóŽì­vñã
øÒðô­C

Ýb­uúsîS¸ÒÏôýÑ­vøØªq­A­u÷ˆ©’§èýz­v¾DÇD¦§ÏUÏŠïœù Ýb 7.1 ¦¸ÏÏÏ„ï¸­uõY©Ï‚¯x
®OÝsÏ„ï¸­v­Cù’ûˆÏWùÇÏœªOüo¬Ó­Cù„ÏÏÏ]ïœù­G

   Ï‚¯x·¦§ÏjÏpñq 4GB ¬W¾[ù 32GB­C

¾yÏl·üõ‹ªø­G

   ¾çü­¦§ý{Ý‘Ï‚¯x¦ô­Ïwñq 4GB ¬W¾[ù 32GB­C

¯­¸£ DB2 Data Links Manager ¦§øØªqÏÏÝüÏ@ðà¾yÏlÝpÏU­G

   Ýà¾B­A¾iÏ„ï¸ Veritas XBSA Ïôðñ¦§ùØ¾×­A
   ¾H®KùØ¾× NetBackup õ@ü’¾öÏ×ï_÷m­C

¾yÏl·üõ‹ªø­G

   Ýà¾B­A¾iÏ„ï¸ XBSA Ïôðñùàøæ·©ž¶k·Ï×Ý^ï_­C
   ·xÝs‚§èýzæ{Ý­Ï„ï¸¦§ XBSA Ïôðñ¾]õt
   Legato NetWorker Ï× Veritas NetBackup­C

  ------------------------------------------------------------------------

42.2 DB2 Everywhere Ïwõ‹ªø DB2 Everyplace

DB2 Everywhere ¦§ÝW§ëý{ÝbÏwõ‹ªø DB2 Everyplace­C
  ------------------------------------------------------------------------

42.3 ú’û®¯íùD

øœÏFæ›æ­Ïõ¾~­A¸ãÝü¦§¾ð¾xüœ¯íðnú’û®ùàùØ¾×ù„ÏÏ¦§ÏuùÆ­C
  ------------------------------------------------------------------------

42.4 ÷åûØñq DB2 Run-time Client üsæýóðP­uõ„Ïœùüsæý·©ž­v¨—¯~

Ý]ªø DB2 Run-time Client ùSÝüóÆýå¦§üsæý·©ž­A¸ã¾HæL¦kõûÝù GUI ÏuùÆ¦§üsæý­A
¾u¾i¾Hñq DB2 Administration Client õûÝù GUI ÏuùÆ¦§üsæý­C
  ------------------------------------------------------------------------

42.5 Search ñïîµ (Search Discovery)

Search ñïîµ¾uÏ„ï¸¬s¬«ïC‚­CùãÝp­ASearch ñïîµñNæL¦küzûL ATM øtñæ¾dùàõ@¾×­CÝì
ªO­AÝûôæððùŒùÇÏœóA¾×¸¢ Known ñïîµ­C
  ------------------------------------------------------------------------

42.6 HP-UX 11 ¦§øOóÑ‚æ›æ­

øOóÑ‚æ›æ­ªOù¥Ïj®ª HP 64 ÝÏ÷óöóû¦§ùØ¾×¦Þ¸ã¾×­A Ý]¾LðÞúQðnõQ¾× 32 ÝÏ÷·ü¾×
æ{Ý­ôWûL 1.75GB ¦§Ý@¾×øOóÑ‚­C Ýp¦GñzªOøäÝ‘ 64 ÝÏ÷¦¸¾¯¦§ DB2­AïNÏœ¯íðnøOóÑ
‚æ›æ­­C øOóÑ‚æ›æ­¾iùØùCÏ@æ{õ€¸×æ{õ€÷sýåÝUÝüÏ@ðà 1 GB ¦§Ý@¾×øOóÑ‚¾i¾×­C
üoñN©eü\©žùãùÆÝüÝêÏv¦§ 1GB Ý@¾×øOóÑ‚­AÝA¾[ÏW 0.75GB ¦§¬søÝ@¾×øOóÑ‚­C Ýp
¦GùØ¾×¦ÞúQðnæ«¾×üoðà·u¶I­A¾LðÞ¾i¾HøäÝ‘Ýhðà©žùã­AùCÏ@©žùãõ­ÝbÝêÏv¦§æ›æ­ÏÏøä
Ý‘­C ÏUÝCªOùØ¾×øOóÑ‚æ›æ­¦§¾ìùMñ›¾¢­G

   * DB2 EE ·“ûã
        o ðž÷æ{Ý­­GExtension Software 12/98 Ï× PHKL_17795­C
        o ¾ýôúû‹©žùãü]¸w $DB2INSTANCE š¬’­C
        o ñzÝbøOóÑ‚æ›æ­ÏUøäÝ‘¦§ùCÏ@ðà DB2 ©žùã­AÝb /etc/services.window ·
          ©žÏÏüœÝüæn¨ì­CùãÝp­G

             db2instance1 50
             db2instance2 60

                ü’æ—­GÝW§ëÏ× ID Ïõô­ôÔî…ÝüÏ@ðà¦©‘­C

        o ñz¾ýôúùØ¾× TCP/IP øj÷“ÏŠ¦k­AøäÝ‘¾“Ý¢ñzðnÝbÝ›¦AóûÏWøäÝ‘¾B¯íðnÝhðà
          ü‘Ï@üîðzÝ­¦§ DB2 ®¾O­C üoªOÝ]ªøú¡øOóÑ‚æ›æ­õûÝùýŽÏ@ðàüîðzÝ­¦§æ{
          õ€©­Ashell ñNýžÏŒøäÝ‘­C­uDB2 ¦AøÔæ{Ý­­v¦óûDÝpÝ¢õûÝùÝûôæõ@ú~­C
        o ¾“Ý¢ðnÝbøOóÑ‚æ›æ­ÏU¸ãøäÝ‘¦§©žùãÏ§øäÝ‘ DB2 ®¾O­A¾ýôú¾H db2win
          (ÝÝb sqllib/bin ÏÏ) õ@ªøÝrð§­CùãÝp­G

             db2win db2start
             db2win db2stop

        o øOóÑ‚æ›æ­¾~øäÝ‘¦§¾“Ý¢ DB2 ®¾O (ÝìøOóÑ‚æ›æ­¾¨ÝbøäÝ‘©) ·ü÷àô€Ý^
          1042­C ùãÝp­G

             db2win db2start <== OK
             db2 connect to db  <==SQL1042
             db2stop <==SQL1042
             db2win db2stop   <== OK

   * DB2 EEE ·“ûã
        o ðž÷æ{Ý­­GExtension Software 12/98 Ï× PHKL_17795­C
        o ¾ýôúû‹©žùãü]¸w $DB2INSTANCE š¬’­C
        o DB2_ENABLE_MEM_WINDOWS æn¨ìš¬’¾ýôúü]¸wªø TRUE­C
        o ñzÝbøOóÑ‚æ›æ­ÏU¸ãøäÝ‘¦§ùCÏ@ðà©žùã¦§ùCÏ@ðàè¨Š÷`¶I­AÝb
          /etc/services.window ·©žÏÏüœÝüæn¨ì­C ùCÏ@ðàæn¨ì¦§ýŽÏ@Ž‘ñNÝùªø¯P
          øÐ÷ûüsñæ¦§©žùãÝW§ë­CùãÝp­G

             === $HOME/sqllib/db2nodes.cfg for db2instance1 ===
               5 host1 0
               7 host1 1
               9 host2 0

             === $HOME/sqllib/db2nodes.cfg for db2instance2 ===
               1 host1 0
               2 host2 0
               3 host2 1

               === /etc/services.window on host1 ===
             db2instance10 50
             db2instance11 55
             db2instance20 60

               === /etc/services.window on host2 ===
               db2instance10 30
               db2instance20 32

               db2instance21 34

        o ñzÏœî…¾× db2win õ@ DB2 ®¾O¦§ô}·Y­A¾Ý¾uóA¾×Ýb EE ·“ûãÏU­C

  ------------------------------------------------------------------------

42.7 dlfm client_conf ¾½©Ž©ùØ¾×¦ÞÏõøÒõ@

Ýb DLFM ñqŽíî÷ÏÏ­AÝp¦G dlfm client_conf Ý]ªøªYù€ýz¾¥Ýà¾½ñ¥­A DB2 ®ª¨ìÏÏ¦§
"stale" ôæ¾¸×ü\ªOÝ]î·ÏõÏ@­C÷¥ùMÏŠ©žªøæo¾XÏUÝC®¾O­G

   db2 uncatalog db <dbname>
   db2 uncatalog node <node alias>
   db2 terminate

æM® ­AÝAûµ÷å dlfm client_conf­C
  ------------------------------------------------------------------------

42.8 ®šÏ™ùœ¦§ù’¾¢­G«’¯sñ`ónæ{Ý­Ýb dlfm øñÏŒ©ùSÝüøñÏŒ

üo§ñ­¦p®šÏ™æo¾Ö­Cú¡ùØ¾×¦Þæo¾X dlfm stop ®¾O¸×Ïœ¾¨ñ`Ç”óö©­A dlfm_copyd
(copy ñ`ónæ{Ý­) ùSÝüøñÏŒ­C Ýp¦Gæo¾Öüo§ñ­¦p­AÝbûµ÷åð®úsñãøÒ dlfm Ïõ®e­Aæo¾X
dlfm shutdown ®¾O­C
  ------------------------------------------------------------------------

42.9 ÷¥øœÝw÷Ó DB2 DFS ñqŽíî÷ñãøÒæ{Ý­

÷¥øœÝw÷Ó DB2 DFS ñqŽíî÷ñãøÒæ{Ý­Ïõ®e­Aroot ·ü÷à«T¸w DFS ·©žÏœÝbùØ¾×ÏÏ­A Ýà
¾BùSÝüùØ¾×¦ÞÝb DFS ·©ž¦ô­ô}ñã Shell­C ¾H root ùðÏ·æo¾XÏUÝC®¾O­G

   stop.dfs dfs_cl

·Óªd /... ÏœÝAüQ÷Ó÷­G

   mount | grep -i dfs

Ýp¦GùSÝüüo¬Óøæ­ADB2 DFS ñqŽíî÷ñãøÒæ{Ý­÷¥øœÝw÷Ó©­A÷àóöóû¯íðnð®úsñãøÒ­C
  ------------------------------------------------------------------------

42.10 Windows NT ñqŽíî÷ùðÏ·‡Çã

Windows NT ¦§·“ûãÏU­Aús¦§ DB2 æn¨ìš¬’ DB2DOMAINLIST ¯Pý{Ýs¦§ñqŽíî÷ùðÏ·‡Çã
óöùŒªêæýÝX­CWindows NT Ý›¦Aóû¦§ DB2 ¾iùØ¾×Ýûš¬’¸w÷qÏ@ðà¸×Ýhðà Windows NT
§“ø­C¾uÝü¸w÷q¸¢ÝûÝC¾šÏÏ¦§§“øùØ¾×¦Þ¦§üs«u¸×üsñæðnùDÏ~ú|üQñæù­C

¾uÝüÝbü‘î¶¦§ Windows NT §“ø·“ûãÏUøäÝ‘ DB2 Ý›¦Aóû¸MñqŽíî÷¦¸¾¯ 7 ¦§ñ­¦pÏU­A
Ï~¾iùØ¾×Ýûæn¨ìš¬’­C

ÝüÇ”Ýûæn¨ìš¬’¦§ü]¸w­A«Ñø¥Ýã Administration Guide: Performance Ï§¦§­uDB2
Registry and Environment Variables­vü­¾ö­C
  ------------------------------------------------------------------------

42.11 Ýb®¾áÏlæ{õ€© AutoLoader ¾iî…ú|ú¡ñ¬

AIX 4.3.3 ¾]õtÏFÏ@ðàðž¾¨æ{Ý­­A¾×¾H÷¥ùMÝb®¾áÏlæ{õ€©¾iî…óðP AutoLoader ÏÏ
¶_¦§ libc øíÇD­CAutoLoader ªOÏ@ðàÝhð®øäÝ‘§¦§æ{Ý­­Cù„ÏÏ¦§Ï@ðàøäÝ‘§ú|ø_¸l¾t
Ï@ðàæ{õ€­Cø_¸lÏ@ðàÏlæ{õ€­Aú|üyÝù¾·ôæ¦§øOóÑ‚¬vûü®¾áÝbÏlôæÏÏ­C

®š¾iî…ú|æo¾Ö­G¾¥ libc.a ¾×ùà§èýzÝhð®øäÝ‘§ñqªêÝPæ{õ€ÏÏÏõ÷ˆ©’ø‹øt÷møOóÑ‚¦§
¶ˆ¸w­A üQ®Dø_¸l¦§ (non-forking) øäÝ‘§¸ã®Oîd­CÝ]ªø®Dø_¸l¦§øäÝ‘§Ïœú|ÝsÝb¸¢
Ïlæ{õ€­A üoðà¶ˆ¸wñNÏœú|Ž·¾XæûÏlôæ­AÝ]ÝàüyÝùÝü©¾·ôæú|ÏÏ¶_­C
  ------------------------------------------------------------------------

42.12 DATALINK ï_÷m

÷ˆ©’©wï_÷mÏõ® ¸ãôiÝ‘¦§¶ö«uü’¾öï_÷m­AæL«žÝü¸×ùSÝü ROLL-FORWARD­A üœÏœú|ýoõŠ
ùõ™ütÏ@ðP¸Ò¦§üBýzæ{õ€­CÝûñ­¦pÏU­A·©žÇæýññùŒôæÏõÏUÝü DATALINK ¦«Ž‘¦§¸ãÝü
¦¡©‘ñNüQ÷m¸¢÷ˆ©’ÇæýÏ@ðP¸Ò·µ÷m (DRP) ¦ª§AÏU­C
  ------------------------------------------------------------------------

42.13 Windows NT (CS/NT) ¦§ IBM Communications Ý›¦Aóû¸w÷qùØ¾×¦Þ ID ¸MüqÝ‘«X

Ýp¦GñzùØ¾× APPC õ@ªø¯ú§í DB2 ñqŽíî÷¯P DB2 Ý›¦AóûüsñæÏõüqøTù¢¸w­A ÝP©­Añzõƒ
CS/NT ú¡Ýù SNA ýœ®~ùØ¾×­A«Ñ«T¸wñzÏwÝb CS/NT ª[§c·Ï§¾¨«T¦§ü]¸wÏFÏUÝCÇ”µ„
Ýr­Cüqñ`ñz¾i¾HÝb x:\ibmcs\private ¾¨ìÏUõ„Ýb÷à·­C

42.13.1 ÷`¶I¸w÷q

TG_SECURITY_BEHAVIOR
     Ýûø¥¬’©eü\ùØ¾×¦ÞùM¸w­AÝp¦G TP ÏœªOóöñK®O@¦§ª[§c­A÷`¶IªOÝpÝ¢üBýz¾Xý{Ýb
     ATTACH Ï§¦§Ýw¾ç÷ˆøT­C

IGNORE_IF_NOT_DEFINED
     Ýûø¥¬’©eü\ùØ¾×¦ÞùM¸wªOõ_ìóöñK®O@ø¥¬’¾Xý{Ýb ATTACH Ï§­AÝP©­AðY TP Ïœ
     ªOóöñK®O@¦§ª[§c©¾i¸¨ýÏ¾ÝðÞ­C

     ðYñzùØ¾× IGNORE_IF_NOT_DEFINED­A®hæLôú¸¢ CS/NT ¸w÷qùØ¾×¦Þ ID ¸MüqÝ‘
     «X­C

VERIFY_EVEN_IF_NOT_DEFINED
     Ýûø¥¬’©eü\ùØ¾×¦ÞùM¸wªOõ_ìóöñK®O@ø¥¬’¾Xý{Ýb ATTACH Ï§­A ùÇ‡Çã¾ÝðÞ­A
     õYùØ TP ¾¬ª[§cªøóöñK®O@­CüoªOûwü]ðÔ­C

     ðYñzùØ¾× VERIFY_EVEN_IF_NOT_DEFINED­A®h¾ýôú¸¢ CS/NT Ï§¸w÷qùØ¾×¦Þ ID ¸M
     üqÝ‘«X­C

ñì¸w÷q CS/NT ùØ¾×¦Þ ID ¸MüqÝ‘«X­A«ÑøäÝ‘ÏUÝCùB’J­G

  1. ô}¸l --> æ{Ý­ôø --> IBM Communications Server --> SNA Node
     Configuration­C õYô}ñã­uw¦‹ùØ¾× Communications Server ª[§cæ›æ­­v­C
  2. ¨‹óšñzðnðžõ‹¦§ª[§c·­C®”Ï@ÏU­uÏUÏ@ùB­v­C¸ã¨‹óš¦§ª[§cûˆøÔ«dùãæ›æ­ô}ñã­C
  3. ñj«åÆ¾š CPI-C, APPC ¸× 5250 ¬ã··æ{Ý­­C®”Ï@ÏU­uõûÝù­v­CõY¾iô}ñã
     Communications Server SNA ÷`¶Iæ›æ­­C
  4. ®”Ï@ÏU CPI-C ¸M APPC ©€Ç„¦§ [+] ÷û­C
  5. ®”Ï@ÏU LU6.2 óöñK®O@©€Ç„¦§ [+] ÷û­C
  6. ¾kÇ„®”Ï@ÏUùØ¾×¦ÞüqÝ‘«X­AùÇ¨‹ù£®¾á­C¸w÷qùØ¾×¦Þ ID üqÝ‘«X¦§æ›æ­ô}ñã­C
  7. ô¤¬gùØ¾×¦Þ ID ¸MüqÝ‘«X­C®”Ï@ÏU«T¸w­C ®”Ï@ÏUõûÝù¾Hñæùšõ¢­C

  ------------------------------------------------------------------------

42.14 µpÝXùtý×¦§ððùŒ

ÏUÝCªOóA¾×¸¢µpÝXùtý×¦§ððùŒ­G

   * ¾]õt¬ÒÝW¦§ªd÷áÏœÏ„ï¸ Oracle ÷ˆ©’Çç®ª NCHAR­BNVARCHAR2­BNCLOB Ï×
     BFILE­C
   * ­uññùŒÏÏÏá­vÏœÏ„ï¸­u®¾áÝ›¦Aóû¨‹ôæ­v­B­ušõ¢Ý›¦Aóû¨‹ôæ­vÏ×­uñÓñ¢Ý›¦Aóû
     ¨‹ôæ­v®¾O­CðYðnæo¾X¾HÏW¾“Ï@®¾O­A¾ýôúùØ¾×¸R¾OÝ‘üBýzóû (CLP)­C
   * øwû‹¾]õt¬ÒÝW¦§ªd÷á­ADB2 UDB ÏœªO¾Ç¯ú¨¡úà DFT_SQLMATHWARN ÷ˆ©’©w¦§ª[§c
     ¨‹ôæ­CÏØÏõ­ADB2 UDB ¦«ñæñq¯ú§í÷ˆ©’ùàú«ô€Ý^ûB§ƒ¦¡¾šÝ­¨—¯~¸×Žæõi­AÝà¸¨ýÏ
     DFT_SQLMATHWARN ü]¸w­C
   * CREATE SERVER OPTION üîðzÝ­Ïœ©eü\ COLSEQ Ý›¦Aóû¨‹ôæü]¸wªø 'I' (øwû‹ùÆ
     ÝüÏœøØÏ·ÏjÏp¬gû‹úàôôõ€¦§÷ˆ©’ùàú«)­C
   * ®¸wæL©Ž¦§¨‹ôæ©­AñNô€Ý^ ALTER NICKNAME üîðzÝ­­C
   * øwû‹ Oracle­BMicrosoft SQL Server Ï× Sybase ÷ˆ©’ùàú«­A¬’ðÔ÷ˆ©’Çç®ªæL¦k
     û‹ªMù DB2 ¦§ BIGINT ÷ˆ©’Çç®ª­C ùÞûwü]ðÔ­AOracle ¦§¬’Ýr (p,s) ÷ˆ©’Çç®ª
     (10 <= p <= 18 Ýà s = 0) ú|û‹ªMù DB2 ¦§ DECIMAL ÷ˆ©’Çç®ª­C

  ------------------------------------------------------------------------

42.15 DataJoiner ððùŒ

µpÝX·“ûãÏ§æo¾X¦§Ï·ïýÝ­ðnùDú|ùððªøøá¦õ@ú~­C
  ------------------------------------------------------------------------

42.16 Windows NT ¦§õ’õBùàÏ†÷ˆøT®ª¨ì§èýzæ{Ý­

­u÷ˆøT®ª¨ì§èýzæ{Ý­­vÏ÷¾¢¾ióA¾×¸¢õ’õBùàÏ†­A ùÇ¾BÝb DB2 Warehouse Manager for
Windows NT CD ÏWïœù¥­C

õ’õBùàÏ†¦§¶«Žôïœù¥¸¢ IL_ICM.ZIP üoðà·œµY·ÏÏ­A Ý¸¢ DB2 Warehouse Manager
for Windows NT CD ¦§ DB2\IL ¾¨ì÷Þ­C

ðYðnÝw÷Óõ’õBùàÏ†¶«Žô¦§­u÷ˆøT®ª¨ì§èýzæ{Ý­­v­A «Ñ¾ìÝw÷Óð^Ï†¦¸¦§ DB2 Warehouse
Manager for Windows NT­A ¾HÏ× Windows NT õ’õBùàÏ†¦¸¦§¸ãÝü¾ìùMñ›¾¢­C

Ýw÷Ó DB2 Warehouse Manager for Windows NT Ïõ® ­A ñq DB2\IL ¾¨ìñN
IL_ICM.ZIP ·©ž÷¥·œµYùÝw÷Ó DB2 Warehouse Manager for Windows NT ¦§¾¨ìÏW­C
«Ñ«T¸w÷¥·œµYæ{Ý­Ïw¨‹óš¾¨«T¦§¨‹ôæ­A¾HÝb·œµY·©ž÷Þ®¾á¾¨ìæý§c­C

·©ž÷¥·œµY® ­A¾çø·“ûãš¬’ LC_ALL ¾ýôúñq En_US šõ¢ªø Iw_IL­C ðYðnšõ¢ü]
¸w­G

  1. ô}ñã Windows NT ññùŒ¾x­AùÇÝbùtý×ûØ¾šÏW®”ùƒÏU­C
  2. Ýbùtý×Ï§©eæ›æ­­A®”Ï@ÏU·“ûã¬Ñã­A æM® ïMõ„ùtý×š¬’øØªqÏÏ¦§ LC_ALL š
     ¬’­C
  3. ®”Ï@ÏUš¬’­A¾HÆ¾š¬’ðÔ«s¨ŠÏŠ©÷Þ¦§ðÔ­CñNðÔñq En_US šõ¢ªø Iw_IL­C
  4. ®”Ï@ÏUü]¸w®”ôs­C
  5. Ç”üªùtý×Ï§©eæ›æ­Ï×ññùŒ¾x­C

ý{ÝbÏwÝw÷Óõ’õBùàÏ†¦¸¦§­u÷ˆøT®ª¨ì§èýzæ{Ý­­v­C
  ------------------------------------------------------------------------

42.17 Microsoft SNA Server ¸M SNA Ýhî÷õ¢ús (ùƒô¾ªq«T¸w) Ï„ï¸

ú¡ Microsoft SNA Server ªOùØ¾×ÏÏ¦§ SNA ýœ®~©­A ¾Dûq÷œ¸M AS/400 ·ü¾×æ{Ý­æL
¦kÝsù£ùØ¾× SNA ùƒô¾ªq«T¸w¦§ DB2 UDB Ý›¦Aóû­C¾“Ý¢¦¡¾šÏ„ï¸¾HÏW¾\î…¦§ DB2 UDB
¾X¦¸®~üœªOÏœ¾¨«T¦§­C¾ýôúðnÝü IBM Communications Server for Windows NT 5.02
¦¸¸×¾HÏW¦§¦¸¾¯­C

æ—:
     ùØ¾× DB2 UDB for Windows ùàÝsù£¾Dûq÷œÏ× AS/400 ÷ˆ©’©wÝ›¦Aóû¦§·ü¾×æ{Ý­
     ¾i¾HùØ¾× Microsoft SNA Server ¦¸¾¯ 4 Service Pack 3 ¸×¾HÏW¦¸¾¯ùàùØ¾×
     SNA ùƒô¾ªq«T¸w­C

  ------------------------------------------------------------------------

42.18 ñãøÒ Windows Ïõ® æL¦kñãøÒ DB2 ¦§ SNA SPM

ðYñzùØ¾× Microsoft SNA Server ¦¸¾¯ 4 SP3 ¸×¾HÏW¦§¦¸¾¯­A «Ñ‡Çã DB2 ¦§ SNA
SPM ¾iÝbð®úsñãøÒÏõ® ¾¨ñ`ñãøÒ­C·Óªd \sqllib\<©žùãÝW§ë>\db2diag.log ·©ž­A ¾H
ù£ñoÇçÝÏUÝC¸ã¾š¦§ôæ¾­G

2000-04-20-13.18.19.958000   Instance:DB2   Node:000
PID:291(db2syscs.exe)   TID:316   Appid:none
common_communication  sqlccspmconnmgr_APPC_init   Probe:19
SPM0453C  Ý]ªø Microsoft SNA Server ¾¬ñãøÒ­A¸ã¾HÝPùB¶I§èýzæ{Ý­¾¬ñãøÒ­C
2000-04-20-13.18.23.033000   Instance:DB2   Node:000
PID:291(db2syscs.exe)   TID:302   Appid:none
common_communication  sqlccsna_start_listen   Probe:14
DIA3001E ¾¬Ýù¾\ñãøÒ "SNA SPM"­C

2000-04-20-13.18.23.603000   Instance:DB2   Node:000
PID:291(db2syscs.exe)   TID:316   Appid:none
common_communication  sqlccspmconnmgr_listener   Probe:6
DIA3103E APPC üq®Hù¢¸wÏ„ï¸©æo¾Ö¨—¯~­CAPPC verb "APPC(DISPLAY 1
BYTE)". ¾Dðnô€Ý^«X "F004"­CÝ÷ðnô€Ý^«X "00000000"­C

ðY db2diag.log ·÷ÞÝüüoù€ôæ¾­A ¾B©ô­¶WøO¸MñzüÞ¦¤ð®úsñãøÒ¦§©ô­ªêý­Añz¾ý
ôú­G

  1. ¸I¾s db2stop­C
  2. ñãøÒ SnaServer ¦AøÔæ{Ý­ (ðY¸|¾¬ñãøÒ)­C
  3. ¸I¾s db2start­C

ÝAÝ÷·Óªd db2diag.log ·­A¾H«T¸wùSÝüÝAýK¾[ù„¾Lôæ¾­C
  ------------------------------------------------------------------------

42.19 DB2 §èýzÝ›¦Aóû¦§¯yù¾·“ûãü]¸w

«Ñ«T¸w DB2 §èýzÝ›¦Aóû©žùã¦§¯yù¾·“ûãªê©e¸¢ DB2 ©žùã¦§¯yù¾·“ûã­Cõ_®h­ADB2 ©ž
ùãæL¦k¯P DB2 §èýzÝ›¦Aóûúóüq­C

ðY LANG ·“ûãš¬’ùSÝüÝb DB2 §èýzÝ›¦Aóû¦§ùØ¾×¦Þü]¸w·÷Þü]¸w­A DB2 §èýzÝ›¦Aóû
ñN¾Hûwü]¦§ùtý×¯yù¾·“ûãñãøÒ­CðYùSÝü¸w÷qûwü]¦§ùtý×¯yù¾·“ûã­A DB2 §èýzÝ›¦AóûñN
ú|¾HÝr«Xðô 819 ùàñãøÒ­CðY DB2 ©žùãùØ¾×ªY§ DBCS ¯yù¾·“ûã­A¾B DB2 §èýzÝ›¦Aóû
ªO¾HÝr«Xðô 819 ùàñãøÒ­A ®h©žùãñNæL¦k¯P DB2 §èýzÝ›¦Aóûúóüq­CDB2 §èýzÝ›¦Aóû¸M
DB2 ©žùã¦§¯yù¾·“ûã¾ýôúªê©e­CùãÝp­AÝb¶ý‚ÏÏÏ† Linux ùtý×ÏW­A ·ü÷àÝb DB2 §èýz
Ý›¦Aóû¦§ùØ¾×¦Þü]¸w·÷Þü]¸w "LANG=zh_CN"­C
  ------------------------------------------------------------------------

42.20 ñô©|æL©Ž

ÝbªYù€¯yù¾÷Þ­Aû‹¸¢ UNIX ùtý×¸M OS/2 ÏW¦§­uññùŒÏÏÏá­vùà¯­­A Ýüù€µ„«Lñô©|æL
©Ž­C«ÑùØ¾×ú’û®ùà¨‹ù£¨‹ôæ­C
  ------------------------------------------------------------------------

42.21 Windows NT Ï× Windows 2000 ÏW¦§ DB2 ¦AøÔñbÏ ¯íùD

Ýb DB2 for Windows NT ¸× Windows 2000 ¦§Ýw÷Óïµô­­AÝw÷Óæ{Ý­ú|®¾á¬’ðà
Windows ¦AøÔ­A ùÇ®¸wùCÏ@ðà¦AøÔ¦§¦AøÔñbÏ ­CðYðnóAú¡ÝaøäÝ‘ DB2­AÝw÷Óæ{Ý­ú|ñ¶
¯PÏUÝCùØ¾×¦ÞvõQæû¯P DB2 ¦AøÔÝüÇ”µp¦§¦AøÔñbÏ ­G

   * õ@ªøõ@ú~ùtý×¦§Ï@ü­¾ö
   * ®¾á token ¦®¾¢
   * ¬W¾[øtÇB
   * ¾H¦AøÔÏŠÝ­ænÏJ
   * õ¢ï®æ{õ€¬h token­C

Ýp¦GñzðnùØ¾×ÏœÝP¦§¦AøÔñbÏ ù¥ DB2 ¦AøÔùØ¾×­Añz¾ýôúñNüoù€ùØ¾×¦ÞvõQñ¶¯P¦AøÔñb
Ï ­C

øœÏFüoù€ùØ¾×¦ÞvõQ­A¦AøÔñbÏ û‹¸¢Ýw÷Ó DB2 ýœ®~¦§¾¨ìÏ]¾ýôúÝü¬gÏJ¦§võQ­C

DB2 Administration Server ¦AøÔ (DB2DAS00 ¦AøÔ) ¦§¦AøÔñbÏ Ï]¾ýôúó™ÝüñãøÒÏ×øñ
ÏŒ ù„¾Ý DB2 ¦AøÔ (Ï]ïNªO¯­­A¦AøÔñbÏ ¾ýôúµäŽí¸¢ Power Users ÷sýå) ¦§vðð­A¾H
Ï×û‹¸¢ ¾“Ý¢¾Ý¸ã§èýz¦§ DB2 ©žùãó™Ýü DB2 SYSADM vðð­C
  ------------------------------------------------------------------------

42.22 Ýb¦¸¾¯ 6 ÏÏ®¾á¦§ Query Patroller ùØ¾×¦Þ¾½¾hÏF EXECUTE ñM¾×v

Ý]ªøü­¾öús¦§·xÝsæ{õ€ (IWM.DQPGROUP­BIWM.DQPVALUR­BIWM.DQPCALCT Ï×
IWM.DQPINJOB) ús¬Wù Query Patroller ¦¸¾¯ 7 ÏÏ­AQuery Patroller ¦¸¾¯ 6 ÏÏ¦§
ý{ÝsùØ¾×¦ÞïN¸¢ù§ù€ ÷ˆ©’¾]ÏœÝA®OÝü EXECUTE ñM¾×v­C ¾iÝêøÒõ¢¾¨ÝûøíÇD¦§·ü¾×æ{
Ý­Ïwús¬Wù FixPak 1 ÏÏÏF­C

ú¡ñzûµ÷åùØ¾× DQP ªd÷á§èýzùàðžõ‹ DQP ùØ¾×¦Þ÷ˆøT©­A«ÑÏœðn÷åæêñqùØ¾×¦ÞýMü‘ÏÏ
ýóøœ ý{Ýü¦§ùØ¾×¦Þ­C
  ------------------------------------------------------------------------

42.23 Query Patroller ððùŒ

Ý]ªø JVM (Java Virtual Machine) ¾ð¾xððùŒ­AÝb HP-UX Ï× NUMA-Q ÏWùÇÏœÏ„ï¸­uªd
÷áñãøÒæ{Ý­­v­CøœÝûÏõ¾~­AÝb NUMA-Q ÏWùÇÏœÏ„ï¸­uQuery Patroller øl¶šóû­v­CÝp
¦G¯íðn¸ãÝü¦§ Query Patroller ñqŽíî÷ÏuùÆ­A®ŽüñzùØ¾×ÏœÝP¦§¾ð¾x (Ï¤Ýp Windows
NT) ùàû‹ HP-UX ¸× NUMA-Q Ý›¦AóûøäÝ‘üoù€ÏuùÆ­C
  ------------------------------------------------------------------------

42.24 ¯íðn«T¸w¸ãÝüú|Ýb÷ˆ©’ðš·xÏÏÏá(DWC)ÏÏùØ¾×¦§ùØ¾×¦Þ¸w÷qæ{Ý­

Ýp¦GñzðnñN­uDB2 ·xÝsæ{õ€®÷móû­v¸ã®¾á¦§·xÝsæ{õ€ú¡õ@­u÷ˆ©’ðš·xÏÏÏá(DWC)­vÏÏ
¦§ ùØ¾×¦Þ¸w÷qæ{Ý­ùàùØ¾×­Añz¾ýôúï­ÏJÏUÝCüîðzÝ­ù·xÝsæ{õ€ con.close(); üîðzÝ­
®eðñ­G

   con.commit();

Ýp¦GùSÝüï­ÏJüoðàüîðzÝ­­A·xÝsæ{õ€¸ãøæ¦§šõ¢ú|Ýb·xÝsæ{õ€ñq DWC øäÝ‘©üQ
Rollback­C

û‹¸¢ DWC ÏÏ¸ãÝü¦§ùØ¾×¦Þ¸w÷qæ{Ý­­A¾ýôúðn¸£«TÝa COMMIT ¾“Ý¢Ï§õt¦§ DB2 ù‡¬’­A
¾HùØšõ¢î…Ýb÷ˆ©’©wÏÏ¾Ö©Ž­FÏ]ïNªO¯­­Añz¾ýôúñN COMMIT üîðzÝ­ ¾[ùùØ¾×¦Þ¸w÷qæ{
Ý­ÏÏ­C
  ------------------------------------------------------------------------

42.25 ÷ˆ©’ðš·xÏÏÏá¸R¾OÝ‘ôž¾X¦§ús¨‹ôæ

¸R¾OÝ‘ôž¾Xù¬Ñ¾š·ÝüÏFÏ@ðàús¦§¨‹ôæ­A/B­CÝû¨‹ôææL¦küzûL­u÷ˆ©’ðš·xÏÏÏá­vÏôðñ
ùàùØ¾×­C

iwh2exp2 ®¾O¦§ús¯y¦kªø­G

   iwh2exp2 filename.INP dbname userid password [PREFIX=table_schema] [/S] [/R] [/B]

ù„ÏÏ
       - filename.INP ªO INP ·©ž¦§õûóÆ÷“©|ÝW§ë
       - dbname ªO÷ˆ©’ðš·xÏÏÏáññùŒ÷ˆ©’©w¦§ÝW§ë
       - userid ªO¾×ùàænÏJ÷ˆ©’©w¦§ùØ¾×¦Þ ID
       - password ªO¾×ùàænÏJ÷ˆ©’©w¦§ñK«X
       - ¨‹¾×ø¥¬’ªø­G
         - PREFIX=table_schema­GññùŒ÷ˆ©’©w¦¡©‘¦§¦¡©‘§ä¾
           (ûwü]ðÔªø IWH)
         - /S­Gôž¾Xõt¨‹ù£ùB’J¦§©æ{¦¡
         - /R­GÏœðnôž¾Xõt¨‹ù£ùB’J¦§ðš·xùàú«
         - /B­GÏœðnôž¾Xõt¨‹ù£ùB’J¦§ contributing ùB’J

æ—:
     Ýp¦G®¸wÏF /R ¸× /B­Aú¡ôžÏJæý¦G¬Ñ¾š·©­Aðš·xùàú«¸× contributing ùB’J
     ¾ýôúÏw÷gÝsÝb­A õ_®hú|ô€Ý^¨—¯~­C

  ------------------------------------------------------------------------

42.26 Backup Services APIs (XBSA)

Backup Services APIs (XBSA) ÏwüQð^øˆ¦§ Open Group ¸w÷qªøÏ@ðàô}¸¤¦§·ü¾×æ{Ý­
æ{Ý­ü]ðpÏôðñ­A¾i¾×¸¢¯íðn÷ˆ©’·xÝs§èýz¦§·ü¾×æ{Ý­¸×óöî…Ïõô­õ@ü’¾ö¸×®OÝs­C üoøO
÷Ýb "Open Group Technical Standard System Management: Backup Services API
(XBSA)"­A Document Number C425 (ISBN: 1-85912-056-3)­C

ªøÏFÏ„ï¸üoðàÏôðñ­Aús®ÏFùƒðà DB2 æn¨ìš¬’­A¾®eÏ„ï¸ AIX­BHP­BSolaris Ï×
Windows NT­G

DB2_VENDOR_INI
     ®ÝVÏ@ðà¾]õt¸ãÝü¬tøà·“ûãü]¸w¦§·©ž­C ðÔú|Ýb÷ˆ©’©w§èýzæ{Ý­ñãøÒ©·•ño­C

DB2_XBSA_LIBRARY
     ®ÝV¬tøàïœù¥¦§ XBSA ·©ž©w­CÝb AIX ÏW­AÝp¦GÝW§ëÏœªO shr.o­Aù§¯•ü]¸wðÔ
     ¾ýôú¾]ªAÝ@¾×¦®¾¢­C HP­BSolaris Ï× Windows NT ÏœðnùDÝ@¾×¦®¾¢ÝW§ë­Cùã
     Ýp­AðYðnùØ¾× Legato ¦§ NetWorker Business Suite Module for DB2­AænøOš
     ¬’¾ýôúü]¸wÝpÏU­G

        db2set DB2_XBSA_LIBRARY="/usr/lib/libxdb2.a(bsashr10.o)"

XBSA Ïôðñ¾iüzûL BACKUP DATABASE ¸× RESTORE DATABASE ®¾Oùà¸I¾s­CùãÝp­G

   db2 backup db sample use XBSA
   db2 restore db sample use XBSA

  ------------------------------------------------------------------------

42.27 OS/390 ¾Nýzæ{Ý­

üoðàÏ†¾¢ÏÏÝüÏø¯•¸O­HÝw÷Ó OS/390 ¯Pù„îS¸Ò

¾¯Ï†ïœù¥ÝpÝ¢Ýw÷Ó OS/390 ¾Nýzæ{Ý­¦§®¾šÏ×ù„îS¸Ò¦§ªêÇ”÷ˆøT­C Ç”¸¢Ýw÷Óæ{õ€¦§õ™
üt«’ªd­A«Ñø¥ó\­uÝw÷Óúõ’[­v­A Ç”¸¢÷âýà¦§®¾š­A«Ñø¥ó\­uÝw÷Óýà÷`­v­C Ç”¸¢¾Nýz
æ{Ý­îS¸Ò¦§ªêÇ”÷ˆøT­A«Ñø¥ó\­uü]÷mÇB¾~¦§¾Nýzæ{Ý­¾\î…­v­B­u¶…ï®æ{Ý­­vÏ×­uÝsù£
DB2 ùtÝC¾H¾~¦§÷ˆ©’©w­v­C

úõ’[

DB2­uðš·xÏÏÏá­v¾]ªA OS/390 ¾Nýzæ{Ý­­Cñz¾i¾HÝb DB2 Universal Database for
OS/390 Ï×ù„¾Ý÷ˆ©’©wÏõô­ùØ¾×¾Nýzæ{Ý­ùàüq®H­A ¾]ªAù„¾Ý¾ð¾xÏW¦§ DB2 ÷ˆ©’©wÏ×®D
DB2 ÷ˆ©’©w­C¾Nýzæ{Ý­¾i¯PùØ¾× ODBC üs«u¦§÷ˆ©’ùàú«üq®H­C ¾Nýzæ{Ý­Ýb OS/390
UNIX ùtý×¦AøÔÏWøäÝ‘­C¾Ý¯íðn OS/390 V2R6 ¸×¾HÏW¦¸¾¯­AùÇ¾B¯P DB2 for OS/390
¦¸¾¯ 5­B6 Ï× 7 ªê©e­C

OS/390 ¾Nýzæ{Ý­Ï„ï¸ÏUÝCõ@ú~­G

   * ñqùàú« DB2 ÷ˆ©’©w«’¯s÷ˆ©’ù¾¬Ñ DB2 ÷ˆ©’©w
   * ù£¬Ó¦¡©‘¸×·©ž¦§Ï§©e
   * øäÝ‘ùØ¾×¦Þ¸w÷qæ{Ý­
   * üzûL IBM ¦§ DataJoiner æ{Ý­Ýsù£®D DB2 ÷ˆ©’©w
   * üzûL Cross Access ¦§ Classic Connect Ýsù£ VSAM ¸× IMS ÷ˆ©’
   * øäÝ‘ DB2 Universal Database for OS/390 Ï«¾×æ{Ý­
   * øäÝ‘­uIBM ÷ˆ©’ô€ó¸æ¨Ðóû­v¦§Ïè¾×Ïuõ@

42.27.1 Ýw÷Óúõ’[

üoù€ùB’Júõðn¯­¸£Ýw÷Óæ{õ€­CÝb­uÝw÷Ó¸£ýà­vÏ@÷`ÏÏïœù¥ÏFÝüÇ”üoù€ùB’J¦§õ¢Ýh÷ˆ
øT­C

  1. ñq DB2 Universal Database for OS/390 §ØñaÝw÷Ó OS/390 ¾Nýzæ{Ý­­C
  2. õ¢úsñzü]¸w·ÏÏ¦§·“ûãš¬’­C
  3. ü]¸wüs«u­G
        o ©™ÏáÏ×¾Nýzñ`ónæ{Ý­Ïõô­­C
        o ¾Nýzæ{Ý­Ï×ù„ñNÝsù£¦§÷ˆ©’©wÏõô­­C
  4. ¾¯§íüsæý CLI­Aüsæýù¾“Ý¢¯ú§í÷ˆ©’©w­C
  5. ü]÷mñz¦§ ODBC ø_¸lü]¸w·©ž­C
  6. ü]÷mñ¶v­A®hùØ¾×¦Þ­G
        o ¾iøäÝ‘¾Nýzñ`ónæ{Ý­­C
        o û‹üWû§ DSNAOCLI ÝüøäÝ‘vðð­C
        o û‹øO÷Ï× ODBC øl¶š¾¨ìÝü¦¬g¦§ñ¶v(Ýp¦G¯íðn)­C
  7. ñãøÒ¾Nýzñ`ónæ{Ý­­C

42.27.2 Ýw÷Ó¸£ýà

Ýw÷Ó OS/390 ¾Nýzæ{Ý­

OS/390 ¾Nýzæ{Ý­¦ç·H¸¢ DB2 Universal Database for OS/390 ¦¸¾¯ 7 §ØñaÏÏ­C«Ñø¥
ó\§Øña¸ã¦ç¦§æ{Ý­¾¨ì­A ¾Hù£ñoÝw÷Ó OS/390 ¾Nýzæ{Ý­¦§÷âýà÷ˆøT­C

ÝbÝw÷Ó OS/390 ¾Nýzæ{Ý­Ïõ®e­Añz¾ýôú¾ìÝb DB2 Ïlùtý×ÏWÏè¾× APAR PQ36585 ¸×
PQ36586­C

õ¢úsñzü]¸w·ÏÏ¦§·“ûãš¬’

š¬’ú|ñN¾Nýzæ{Ý­®ÝVÝh§ DB2 ·©ž©w­B¨‚¾X¾¨ìæ¾æ¾­C

ÏUÝC«dùãªO«dùã .profile ·©ž¦§Ï§©e­C.profile ·©žú|¸w÷q·“ûãš¬’­A ¾B¾Ý¾ýôú
ÝbñãøÒ¾Nýzñ`ónæ{Ý­¦§ùØ¾×¦Þ¦§ø_¸l¾¨ìÏÏ­G

export VWS_LOGGING=/usr/lpp/DWC/logs
export VWP_LOG=/usr/lpp/DWC/vwp.log
export VWS_TEMPLATES=usr/lpp/DWC/
export DSNAOINI=/usr/lpp/DWC/dsnaoini
export LIBPATH=usr/lpp/DWC/:$LIBPATH
export PATH=/usr/lpp/DWC/:$PATH
export STEPLIB=DSN710.SDSNEXIT:DSN710.SDSNLOAD

ü]÷müs«u

ðYðnü]¸w©™ÏáÏ×ñ`ónæ{Ý­üs«u­A«ÑñNÏUðñüoÝ‘¾[ÏJ /etc/services ·©ž¸×
TCPIP.ETC.SERVICES ·©ž­G

vwkernal 11000/tcp
vwd 11001/tcp
vwlogger 11002/tcp

ðYðnÝb OS/390 ¾Nýzæ{Ý­Ï×÷ˆ©’©wô­ü]¸wüs«u­AñN¾“Ý¢¯ú§í÷ˆ©’©wús¬Wù OS/390 üq
®H÷ˆ©’©w (CDB)­Cüo÷ÞªOü­¾ö«dùã CDB INSERT­G

INSERT INTO SYSIBM.LOCATIONS
        (LOCATION, LINKNAME, PORT)
VALUES
        ('NTDB','VWNT704','60002');

INSERT INTO SYSIBM.IPNAMES
        (LINKNAME, SECURITY_OUT, USERNAMES, IPADDR)
VALUES
        ('VWNT704', 'P', 'O', 'VWNT704.STL.IBM.COM');

INSERT INTO SYSIBM.USERNAMES
        (TYPE, AUTHID, LINKNAME, NEWAUTHID, PASSWORD)
VALUES
        ('O', 'MVSUID', 'VWNT704', 'NTUID', 'NTPW');

ðY¯íü]÷müs«u¦§÷âýà÷ˆøT­A«Ñø¥ó\ DB2 UDB for OS/390 Installation Guide
(GC26-9008-00) ÏÏ¦§­uConnecting Distributed Database Systems­vüû÷`­C

üsæý CLI

Ý]ªø OS/390 ¾Nýzæ{Ý­ùØ¾× CLI ùà¯P DB2 úóüq­A ñz¾ýôúñN CLI üWû§üsæýù¸ãÝüñz
¦§¾Nýzæ{Ý­ðnÝsù£¦§¯ú§í÷ˆ©’©w­C üo÷ÞªOÏ@ù€¾¯§í DB2 for OS/390 ÷ˆ©’©w¦§«dùãüs
æý÷ˆ©’¾]üîðzÝ­­G

BIND PACKAGE (DWC6CLI) MEMBER(DSNCLICS) ISO(CS)
BIND PACKAGE (DWC6CLI) MEMBER(DSNCLINC) ISO(NC)
BIND PACKAGE (DWC6CLI) MEMBER(DSNCLIRR) ISO(RR)
BIND PACKAGE (DWC6CLI) MEMBER(DSNCLIRS) ISO(RS)
BIND PACKAGE (DWC6CLI) MEMBER(DSNCLIUR) ISO(UR)
BIND PACKAGE (DWC6CLI) MEMBER(DSNCLIMS)
BIND PACKAGE (DWC6CLI) MEMBER(DSNCLIC1)
BIND PACKAGE (DWC6CLI) MEMBER(DSNCLIC2)
BIND PACKAGE (DWC6CLI) MEMBER(DSNCLIF4)


üo÷ÞªOÏ@ù€øäÝ‘Ýb Windows NT ÏW¦§ DB2 ÷ˆ©’©w¦§«dùã bind package üîðzÝ­­G

BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLICS) ISO(CS)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLINC) ISO(NC)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIRR) ISO(RR)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIRS) ISO(RS)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIUR) ISO(UR)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIC1)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIC2)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIQR)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIF4)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIV1)
BIND PACKAGE (NTDB.DWC6CLI) MEMBER(DSNCLIV2)


üo÷ÞªOÏ@ðà«dùã bind üîðzÝ­­AñN CLI ÷ˆ©’¾]Ï@ø_üsæýùüWû§ÏÏ­G

BIND PLAN(DWC6CLI) PKLIST(*.DWC6CLI.* )

ü]÷m ODBC ø_¸lü]¸w·©ž

«dùã ODBC ø_¸lü]¸w·©ž (inisamp) Ï§õtÝb usr/lpp/DWC/ ¾¨ìÏÏ­Cñz¾i¾H«s¨ŠÝû·
©ž¾HøtÝXñz¦§ùtý×ùØ¾×­A¸×¦Þ®¾áñzÝêÏv¦§·©ž­CðYðn«T¸w·©ž¾¨«TÝaûBõ@­A «Ñ‡Çã
ÏwóAú¡Ýaª[§c­G

   * DSNAOINI ·“ûãš¬’¾ýôú®ÝVø_¸lü]¸w·©ž­C
   * ·ÝW¾ýôúùØ¾× dsnaoini.location_name ¦§¸RÝW§Dùã­C
   * ·©ž¾ýôú¾]ªA CONNECTTYPE=2 Ï× MVSATTACHTYPE=CAF ø¥¬’­C

ðY¯íüsæý CLI ¯P DSNAOINI ·©ž¦§÷âýà÷ˆøT­A«Ñø¥ó\ DB2 UDB for OS/390 ODBC
Guide and Reference(SC26-9005)­C

ü]÷mñ¶v

OS/390 ¾Nýzæ{Ý­ªOÏ@ðàñ`ónæ{Ý­æ{õ€­Cñz¾i¾HùØ¾×Ï@î‰¦§ UNIX Ýw¾ç¸Ò¸× OS/390
UNIX Ýw¾ç¸ÒùàøäÝ‘¾Nýzñ`ónæ{Ý­­C

Ý]ªø¾Nýzæ{Ý­¯íðnñ`ónæ{Ý­vðð­A«Ñ¸w÷qüoù€¾Nýzæ{Ý­¾iøäÝ‘·ªø­uRACF æ{Ý­ññ
ùŒ­v­G

   * libtls4d.dll
   * iwhcomnt.dll
   * vwd

ñìÝb RACF æ{Ý­ññùŒÏÏ¸w÷q¾iøäÝ‘¦§æ{Ý­­A «ÑÏµï®Ýš­u÷ˆ©’ðš·xÏÏÏá­v¾iøäÝ‘·¸ãÝb
¦§¾¨ì­AøäÝ‘ÏUÝC®¾O­G

extattr +p libtls4d.dll
extattr +p iwhcomnt.dll
extattr +p vwd

ðYðnùØ¾×Ýü +p ø¥¬’¦§ extattr ®¾O­A ®hû‹¸¢ BPX.FILEATTR.PROGCTL FACILITY Çç
õOñzÝšÏ™¾ýôúó™Ýü¦ù£vðð­C ÏUÝC«dùãÆ¾š¾×ùàñNÝûü\¾ivæûÏ¸ùØ¾×¦Þ ID SMORG ¦§
RACF ®¾O­G

RDEFINE FACILITY BPX.FILEATTR.PROGCTL UACC(NONE)
PERMIT BPX.FILEATTR.PROGCTL CLASS(FACILITY) ID(SMORG) ACCESS(READ)
SETROPTS RACLIST(FACILITY) REFRESH

Ç”¸¢ñ¶v¦§÷âýà÷ˆøT­A«Ñø¥ó\ OS/390 UNIX System Services Planning (SC28-1890)
­C

ñãøÒ¾Nýzñ`ónæ{Ý­

ÝbñzõûÝùª[§cùtý×Ïõ® ­A«ÑñãøÒ¾Nýzñ`ónæ{Ý­­G

  1. Telnet ù OS/390 ÏW¦§ UNIX Systems Services­AüzûL OS/390 host Ï× USS
     øÐ­C
  2. ñãøÒ¾Nýzñ`ónæ{Ý­­G
        o ðYðnÝbðIï§ñãøÒñ`ónæ{Ý­­A«ÑÝb¸R¾OÝ‘ÏÏ¨‚ÏJ vwd­C
        o ðYðnÝbðIï§ñãøÒñ`ónæ{Ý­­A«Ñ¨‚ÏJ

          vwd>/usr/lpp/DWC/logs/vwd.log 2>&1 &

ðYðn‡Çã OS/390 ¾Nýzñ`ónæ{Ý­ªOõ_ÝbøäÝ‘ÏÏ­A«ÑÝb UNIX Shell ¸R¾OÝ‘¨‚ÏJÏUÝC®
¾O­G

ps -e | grep vwd

¸×¦Þ­AÝb OS/390 ¾Dññ¾x¨‚ÏJ D OMVS,a=all ­AùÇújïMÝrÝˆ vwd

42.27.3 ü]÷mÇB¾~¦§¾Nýzæ{Ý­ù‡¬’

DB2 Warehouse Manager ÷ˆ©’¾]¾]ªAÏUÝCùØ¾×¦Þ¸w÷qæ{Ý­­G

   * vwpftp­GøäÝ‘ FTP ®¾O·­C
   * vwpmvs­Gïœ¾X JCL Ïuõ@Ýˆªy­C
   * vwprcpy­GùØ¾× FTP «’¯s·©ž­C
   * XTClient­GñqŽíî÷Žýæoæ{Ý­­C
   * etidlmvs­GETI (Evolutionary Technologies International) ïœù¥¦§Ï«¾×æ{
     Ý­­F ¾iõRøœ MVS ÏW¦§·©ž­C
   * etircmvs­GETI ïœù¥¦§Ï«¾×æ{Ý­­F¾iÝb MVS ¾Dûq÷œÏWøäÝ‘ FTP­C
   * etiexmvs­GETI ïœù¥¦§Ï«¾×æ{Ý­­F¾iÝb MVS ÏWøäÝ‘ JCL­C

øœÝûÏõ¾~­Añz¾i¾HÝb­u÷ˆ©’ðš·xÏÏÏá­v®¾áùØ¾×¦Þ¸w÷qæ{Ý­Ï×·xÝsæ{õ€­COS/390 ¾Nýz
æ{Ý­Ï„ï¸¾“Ý¢¾iÝb UNIX ùtý×¦AøÔÏUøäÝ‘¦§¾iøäÝ‘·­C

Ï@ðàùØ¾×¦Þ¸w÷qæ{Ý­ú|®¸wæûÏ@ðà¸×ÝhðàùB’J­Cú¡ñzøäÝ‘ùØ¾×¦Þ¸w÷qæ{Ý­©­Aú|æo¾Ö
ÏUÝCøÒõ@­G

   * ¾Nýzæ{Ý­ñãøÒ­C
   * ¾Nýzæ{Ý­øäÝ‘ùØ¾×¦Þ¸w÷qæ{Ý­­C
   * ùØ¾×¦Þ¸w÷qæ{Ý­ô€Ý^Ý^¶Ñ«XÏ×Ý^äX·©žæû¾Nýzæ{Ý­­C
   * ¾Nýzæ{Ý­ñNæý¦Gô€Ý^©™Ïá­C

ªøÏFÝb OS/390 ÏWøäÝ‘ ETI­Añz¾ýôú¾ìñN FixPack 2 ©M¾×ù DB2 Universal
Database ¦¸¾¯ 7.1­C

ùØ¾× VWP_LOG ·“ûãš¬’ùà¸w÷qÏ@ðà¾¨ì­Aù¥ùØ¾×¦Þ¸w÷q¦§æ{Ý­¬gÏJ¨‚¾X­C

Ýp¦GñzùØ¾×ùØ¾×¦Þ¸w÷qæ{Ý­ùà¾× FTP ïœ¾XÏuõ@­A ñz¾ýôú¾ì®¾áðnïœ¾X¦§ JCL Ï×÷ˆ
©’­C JCL ÏÏ¦§Ïuõ@ÝW§ë¾ýôúªO USERIDx­A ù„ÏÏ x ªOÏ@ðàü‘Ï@ÝrÏ÷¦§Ýr¾·¸×¬’Ýr («d
ùã­GMYUSERA)­C¾]õtÝb JCL ÏÏ¦§ MSGCLASS Ï× SYSOUT ·©ž¦§¨‚¾XÇçõO¾ýôú®¸w
JES-held ¨‚¾XÇçõO­C

ððùŒ­G¸ãïœ¾XÏuõ@¦§üÞÏj LRECL ªO 254 ðàÝrÏ÷­CJES ¾uú|ñ«ïy JCL ¦§®e 72 ðàÝr
Ï÷­C

šõ¢­u÷ˆ©’ðš·xÏÏÏá­vFTP Ï„ï¸¦§¬ã¦O

­u÷ˆ©’ðš·xÏÏÏá­vÝw÷ÓÏFÏ@ðà JCL ¬ã¦O­Aù¥ùØ¾× FTP ¶…øe·©ž­CÝp¦Gñzðpû§ì
OS/390 ¾Nýzæ{Ý­ùØ¾× FTP ®¾O GET ¸× PUT ñqªY OS/390 ¾Dûq÷œô€øe·©žù¾tÏ@ðà
¯ú§í¾Dûq÷œ­Añz¯íðnªø OS/390 ùtý×šõ¢ JCL ¬ã¦OÏÏ¦§ñbÏ ÷ˆøT­G

  1. ¾HÏ@ðàÝüvððÝb /usr/lpp/DWC ¾¨ìÏÏ«’¯sÏ×õ¢ús·©ž¦§ ID ænÏJ­C
  2. ïMõ„ ftp.jcl­AùÇ¾×ús¦§·ÝW systemname.ftp.jcl «’¯s·©ž­A ù„ÏÏ
     systemname ªO OS/390 ùtý×¦§ÝW§ë­C
  3. ®¾áÝû·©ž¦§ø’¾¯æûùCÏ@ðàñzðnÝbù„ÏWøäÝ‘¶…ï®æ{Ý­ vwpmvs ¸× ETI extract
     ¦§ OS/390 ùtý×­CùãÝp­A Ýp¦GñzðnÝb STLMVS1 ÏWøäÝ‘¾“Ï@ðàæ{Ý­­A ®¾áÏ@ðà
     ÝW§ëªø STLMVS1.ftp.jcl ¦§·©žø’¾¯­C
  4. ùØ¾×Ï†Ýr«s¨Šæ{Ý­ùàÝêðq JCL­A¾HýÝXñzî÷¾x¦§¯íùD­C šõ¢ñbÏ ÷ˆøT¾HýÝXñz
     ¦§ MVS ùtý×¦§¬Ñú€ñbÏ ÷ˆøT­C«ÑÏšõ¢¾“Ý¢ÏŠªA¸ú ([) Ï§¦§ø¥¬’­A Ï¤Ýp
     [USERID] Ï× [FTPFILE]­C(ÏŠªA¸úÏ·õOªøÏQÏ¯ôiÝÝrÏ÷ x'AD' Ï× x'BD'­CðYñz
     ¦§ TSO ýž§íóöÇç®ªÝb SPF ¨‹ôæ 0 ÏÏ¾¬ü]Ýù 3278A­Aüoù€ðÔ¾iî…ú|Æ¾šÝùîS©¡
     ÝrÏ÷­AÝàÏœªOÏŠªA¸ú­C üoùÇÏœú|ªOøíÇD­A Ýp¦GñzùSÝüšõ¢ x'AD' ¸× x'BD'­A
     ¸×¦Þ¾“Ý¢ÝrÏ÷Ïõô­¦§÷ˆ©’­C)
  5. õ¢ús·“ûãš¬’ VWS_TEMPLATES­A®ÝV«’¯s¦§¬ã¦O·©ž¦§¾¨ì­C

­u÷ˆ©’ðš·xÏÏÏá­v¾]õtÝû«dùã JCL ¬ã¦O­G

//[USERID]A JOB , 'PUT/GET',
// CLASS=A,
// USER=&SYSUID,
// NOTIFY=&SYSUID,
// TIME=(,30),
// MSGCLASS=H
//STEP1 EXEC PGM=FTP,PARM='( EXIT'
//INPUT DD DSN=[FTPFILE],DISP=SHR
//OUTPUT DD SYSOUT=*
//SYSPRINT DD  SYSOUT=*

ù£¬Ó¦¡©‘¸×·©ž¦§Ï§©e

ñz¾iùØ¾× OS/390 ¾Nýzæ{Ý­ùàù£¬Ó DB2 ¦¡©‘¯Pî¶Ï†Ýr·¦§Ï§©e­A Ï¤Ýp UNIX ùtý×¦A
øÔ·©žÏ× OS/390 ð¾Öî¶Ï†Ýr·­CñzÏ]¾iùØ¾× OS/390 ¾Nýzæ{Ý­¾H Classic Connect
ù£¬Ó IMS ¸× VSAM ·©ž¦§Ï§©e­Cû‹¸¢î¶Ï†Ýr·­A¾Nýzæ{Ý­ú|ûŒªí·©ž¸w÷q¦§Ï§©eÏÏ¦§
ø¥¬’ùàõP¸w·©ž©‘Ý­­C

42.27.4 ¾×Žýæoæ{Ý­ñ’æ{ðš·xùB’J (XTClient)

ùØ¾×Žýæoæ{Ý­¾iñq OS/390 ¾ð¾xñ’æ{ðš·xùB’J­C ñz¸×ªO OS/390 Ïuõ@ñ’æ{æ{Ý­¾i¾Hïœ
¾XÏ@ðàú|Žýæo­u÷ˆ©’ðš·xÏÏÏá­vùB’J¦§Ïuõ@­CÝp¦GùB’JôôõQõûÝù­AJCL ÏÏ¦§Žýæoù‡Ý­
ùB’Jú|ô€Ý^Ý^¶Ñ«X 0­C

Ýb OS/390 UNIX ùtý×¦AøÔÏW¾ýôúÝw÷Ó JDK 1.1.8 ¸×õ¢ús¦¸¾¯¾HùØ¾×Žýæoæ{Ý­­CðYðn
ñãøÒŽýæoù‡Ý­­A «Ñ¾ìÝbøäÝ‘ðš·xÝ›¦Aóû¦§óöóûÏWñãøÒ XTServer­CÝûæ{õ€¾iùœ¸¢÷ˆ©’
ðš·xÏÏÏá§èýzÏƒ¾U¦§ýŽ 5 üû­A ¬ÑÇDªø­uñq÷ˆ©’ðš·xÏÏÏáÏõ¾~ñãøÒùB’J­v­CXTServer
ñãøÒÏõ® ­A«ÑÝb OS/390 ÏWñãøÒ XTClient­CÏUÝC«dùãÆ¾šñãøÒŽýæoù‡Ý­¦§ JCL «d
ùã­C

//DBA1A    JOB 1,'XTCLIENT',CLASS=A,MSGCLASS=H,
//         MSGLEVEL=(1,1),REGION=4M,NOTIFY=&SYSUID
//******************************************************
//* submit iwhetrig
//******************************************************
//BRADS    EXEC PGM=BPXBATCH,
//              PARM=('sh cd /usr/lpp/DWC/; java XTClient 9.317.171.133 1100x
//              9 drummond pw bvmvs2nt 1 1 100')
//STDOUT        DD PATH='/tmp/xtclient.stdout',
//           PATHOPTS=(OWRONLY,OCREAT),
//           PATHMODE=SIRWXU
//STDERR        DD PATH='/tmp/xtclient.stderr',
//           PATHOPTS=(OWRONLY,OCREAT),
//           PATHMODE=SIRWXU
//

æ—:
     ÏWðz«dùã JCL «XÆ¾šÝpÝ¢Ž~Ž•ø¥¬’ùÏUÏ@Ý‘­CÏŠ¦kªOµ„ÏJø¥¬’­AÏ@¦«ùýŽ 71
     ðà¦«Ž‘­AÝbýŽ 72 ðà¦«Ž‘¸¤Ï@ðà 'X'­A æM® ÝbÏUÏ@Ý‘¦§ýŽ 16 ðà¦«Ž‘Ž~Ž•­C

ø¥¬’ (cd /usr/lpp/DWC/;) ¦§ýŽÏ@ðàü­Ï·ñN¾¨ìšõ¢ùÝw÷Ó OS/390 ¾Nýzæ{Ý­¦§Ý
÷m­C ø¥¬’¦§ýŽÏGü­¾öñãøÒ XTClient ùÇô€¯¬ÏUÝC 8 ðàø¥¬’­G

   * ­u÷ˆ©’ðš·xÏÏÏá­vÝ›¦Aóû¾Dûq÷œÝW§ë¸× IP Ýõ}
   * ­u÷ˆ©’ðš·xÏÏÏá­vÝ›¦AóûøÐ (üqñ`ªø 11009)
   * ­u÷ˆ©’ðš·xÏÏÏá­vùØ¾×¦Þ ID
   * ­u÷ˆ©’ðš·xÏÏÏá­vüqÝ‘«X
   * ðnøäÝ‘¦§ùB’JÝW§ë
   * ­u÷ˆ©’ðš·xÏÏÏá­vÝ›¦Aóû®¾O­Aù„ÏÏ­G
        o 1 = ýóÏJùB’J
        o 2 = ñNùB’Jïœ¦@ùï£÷å¬ãÝ­
        o 3 = ñNùB’Jïœ¦@ù¾Öýœ¬ãÝ­
        o 4 = ñNùB’Jðøîùï£÷å¬ãÝ­
        o 5 = ñNùB’Jðøîùô}æo¬ãÝ­
   * ªOõ_æ¾®íùB’JõûÝù¦§¨‹ôæ­Aù„ÏÏ 1= ªO­A0 = õ_
   * üÞÏjÝC¬’ (ùØ¾× 0 ¸×¦¾åùàïœù£¸ãÝüóŒÝC)

42.27.5 ¶…ï®æ{Ý­

¶ýÏô

üo 12 ðà¶…ï®æ{Ý­ªO Java ·xÝsæ{õ€­Aïœù¥Ï@ù€ø•¾¯¦§÷ˆ©’¶…ï®­C ªøÏFøäÝ‘üoù€¶…ï®
æ{Ý­­Añz¾ýôú¾ìÝb DB2 Ïlùtý×ÏWü]¸w Java ·xÝsæ{õ€­C Ç”¸¢üoù€¶…ï®æ{Ý­¦§ù„¾L÷ˆ
øT­A «Ñø¥ó\ IBM DB2 Universal Database Data Warehouse Center §èýzÏƒ¾U ¦¸¾¯
7­ASC40-0496-00­C

IWH.CLEAN
IWH.PERIODTABLE
IWH.KEYTABLE
IWH.CHISQUARE
IWH.CORRELATION
IWH.STATISTICS
IWH.INVERTDATA
IWH.PIVOTDATA
IWH.REGRESSION
IWH.ANOVA
IWH.SUBTOTAL
IWH.MOVINGAVERAGE

ü]÷m­uJava ·xÝsæ{õ€­v

üoù€®¾OªOõûóÆ®¾š¦§§‰¶ý¦¸­A¯­¸£ÝpÝ¢ü]¸w Java ·xÝsæ{õ€­A«Ñø¥ó\ Application
Programming Guide and Reference for Java(TM)­ASC26-9018

  1. Ýb DB2 Ïlùtý×ÏWÏè¾× PTFs UQ46170 ¸M UQ46114­C
  2. Ýb OS/390 ùtý×ÏWÝw÷Ó Visual Age for Java 2.0 ¸×¾HÏW¦¸¾¯­C
  3. Ýb DB2 ÏWÝw÷Ó JDBC­AñN JDBC ©M¾¢üsæýÝš DB2 Ïlùtý×­C
  4. Ýb DB2 Ïlùtý×ÏWü]¸w RRS ¸M DB2 WLM ·xÝsæ{õ€­C
  5. ü]¸wñz DB2 ¦§ Java ·xÝsæ{õ€­C¾]ªAªø Java ·xÝsæ{õ€Ýõ}¦ô­®¾áÏ@ðà Java
     WLM ñãøÒæ{õ€­C
  6. Ýb WLM ÏõÏU­Añz¾ýôúñN Java WLM ñãøÒæ{õ€æýÝXÏ@ðà WLM ·“ûãÝW§ë­C«ÑùØ¾×
     WLM ·ü¾×æ{Ý­·“ûãæeðñ­u®¾á·ü¾×æ{Ý­·“ûã­vùàæýÝX·“ûãÝW§ë¸M JCL æ{õ€­C
  7. Ýb CREATE PROCEDURE ¸× ALTER PROCEDURE ¦§ WLM_ENVIRONMENT ¨‹ôæÏW®¸w
     WLM ·ü¾×æ{Ý­·“ûãÝW§ë­AñN·xÝsæ{õ€¸×ùØ¾×¦Þ¸w÷q¦§ù‡¬’æýÝXÏ@ðà·ü¾×æ{Ý­·“
     ûã­C
  8. «T¸wñz¦§ DB2 ñãøÒõ@ú~¦§ó™Ýü¦ÞùÆü’Ýsù£vùàÝsù£ Java WLM ñãøÒæ{õ€ÏÏ¦§·
     ©ž©w­C

ðš·x¶…ï®æ{Ý­¦§ü]÷mùB’J

üoù€®¾OªOõûóÆ®¾š¦§§‰¶ý¦¸­A«Ñø¥ó\IBM DB2 Universal Database Data Warehouse
Center §èýzÏƒ¾U ¦¸¾¯ 7­ASC40-0496-00

  1. ñN Fixpack 3 Ïè¾×Ýš DB2 Universal Database for NT ¦¸¾¯ 7­A ¸×ñN­uðš·x
     ññùŒ÷ˆ©’©w­võ¢úsÝù TRANSREGISTERED = 1 ¸M TRANSFENCED=1­C

     ñìõ¢ús­uðš·xññùŒ÷ˆ©’©w­v­A«ÑÝb DB2 Universal Database ¸R¾OÝ‘üBýzóûÏW¨‚
     ÏJÏUÝC SQL­G

     CONNECT TO your_vw_control_database
     UPDATE IWH.INFORESOURCE SET TRANSREGISTERED = '1' WHERE SUBDBTYPE = 'DB2 MVS'
     UPDATE IWH.INFORESOURCE SET TRANSFENCED = '1' WHERE SUBDBTYPE = 'DB2 MVS'

  2. ¸w÷q¶…ï®æ{Ý­ù DB2
        o ðYñzÝü DB2 for OS/390 ¦¸¾¯ 7­A«ÑùØ¾× /usr/lpp/DWC/createXfSQLV7
          ÏÏ¦§ SQL üîðzÝ­­C
        o ðYñzÝü DB2 for OS/390 ¦¸¾¯ 6­A«ÑùØ¾× /usr/lpp/DWC/createXfSQL ÏÏ
          ¦§ SQL üîðzÝ­­C
        o ðYñzÝü DB2 for OS/390 ¦¸¾¯ 5­A«ÑùØ¾× /usr/lpp/DWC/createXfSQL ÏÏ
          æ—÷¥¦§ SQL üîðzÝ­­C ýóøœ¸ãÝü CREATE PROCEDURE üîðzÝ­¦§æ—÷¥­C æM® 
          ýóøœ INSERT INTO SYSIBM.SYSPROCEDURES üîðzÝ­¦§æ—÷¥­A¾×ùà¸w÷q DB2
          for OS/390 ¦¸¾¯ 5 ¦§¶…ï®æ{Ý­­C

     ú¡ñzü]¸w Java ·xÝsæ{õ€©­AñzùØ¾× WLM ùàæýÝX Java WLM ñãøÒæ{õ€¸MÏ@ðà
     WLM ·“ûãÝW§ë­C·“ûãÝW§ë®¸w¸¢ CREATE PROCEDURE üîðzÝ­¦§ WLM ENVIRONMENT
     ¨‹ôæÏÏ­C DSNWLMJ ªOÏ§õt¸¢ÏWðz¶…ï®æ{Ý­¸w÷qÏÏ¦§ WLM ·“ûãÝW§ë­C ñz¾iús¬W
     DSNWLMJ ¦§ WLM Ç”µpÝW§ë­A¸×ñNùCÏ@ðà¶…ï®æ{Ý­¸w÷q¦§ WLM ENVIRONMENT ¨‹ôæ
     šõ¢ªøñzÏwæýÝXÝšñãøÒæ{õ€¦§ÝW§ë­C
  3. ñq UNIX ùtý×¦AøÔü]¸wÇæýùàüsæý IWH710.SIWHLOAD ÏÏ¦§¶…ï®æ{Ý­÷ÏJ¬ãýå­C
        o ¾H Telnet üsñæÝšñz OS/390 ¾Dûq÷œùtý×¦§ UNIX ùtý×¦AøÔ­C
        o Ïµï®ÝšñzÝw÷Ó OS/390 ¾Nýzæ{Ý­¦§¾¨ì­Cûwü]Ýw÷Ó¾¨ìªO /usr/lpp/DWC­C
        o ðYñzùØ¾× DB2 V7­A«Ñ÷äÝšùB’J 4­CðYñzùØ¾× DB2 V5 ¸× V6­A «ÑÝbÝw÷Ó¾
          ¨ìÏÏ«s¨Š trlinks ÷ˆ©’ôø­CÝbÝûÝ‘¦§ýŽÏ@Ž‘ÏÏ¾[ÏWÏ@ðà # ý÷ûùàæ—÷¥Ýû
          Ý‘­G

          ln -e IWHXFV7  xf.jll;

          ýóøœýŽÏ@Ž‘¦§ # ý÷ûùàýóøœÝûÝ‘¦§æ—÷¥­C

          #ln -e IWHXF  xf.jll;

          ·xÝsñz¦§šõ¢­C
        o µ„ÏJ trlinks ùÇ®”ÏU¨‚ÏJ­Cüoú|Ýb¾¨ìÏÏ®¾áÏ@ðà xf.jll Çæý­A¾×ùà®
          ¾š¾Nýzæ{Ý­÷ÏJ IWHXF ¸× IWHXFV7 ¬ãýå­C
  4. üzûL APF ñ¶v IWH710.SIWHPDSE­AæM® ús¬WÝš DB2 Java ·xÝsæ{õ€ñãøÒæ{õ€¦§
     STEPLIB üsñæ­C
  5. ñNñz¦§ xf.jll Çæý¸ãÝb¦§¾¨ì (ûwü]ðÔ­G/usr/lpp/DWC) ús¬WÝš WLM ·“ûã÷ˆ
     ©’ôøÏÏ¦§ CLASSPATH ¸M LIBPATH ·“ûãš¬’­C
        o ðYñzÏœ«T¸w WLM ÷ˆ©’ôø¦§Ý÷m­A«Ñªdªíñz¦§ DB2 Java ·xÝsæ{õ€ñãøÒæ{
          õ€­Cñz¦§ WLM ·“ûã÷ˆ©’ôøªOñz¦§ JAVAENV DD ¾d®ÝV¦§÷ˆ©’ôø­C
  6. ñãøÒ·xÝsæ{õ€­AæM® ®¾áùÇøäÝ‘ðš·xùB’J­C

Java ·xÝsæ{õ€¦§ððùŒ

Ï@ðà·xÝsæ{õ€¦§¬ÑøOÏÏ¦§ Java ¦®¾¢ôÔ¸¢ DB2 for OS/390 ¦¸¾¯ 7 ÏÏÏ~Ï„ï¸­CÝ]Ýû­A
¶…ï®æ{Ý­Ýb DB2 for OS/390 ¦¸¾¯ 5 ¸× 6 ¦§ø¥¬’ÏÏÏœÏ„ï¸ NULL ðÔ­CÝbüoù€¦¸¾¯
ÏÏ­AðYñzô€¯¬ NULL ðÔ­A®hú|æ›ªøûsùàüBýz­C ¦¸¾¯ 5 ¸M 6 ¶…ï®æ{Ý­ñNûsø¥¬’æ›ªø¦
ÝrÝˆ­C

DB2 ôÔ¸¢ DB2 for OS/390 ¦¸¾¯ 7 ÏÏÏ„ï¸ COMMIT SQL üîðzÝ­­CINVERTDATA ·xÝsæ{
õ€¾iÝb·xÝsæ{õ€Ï§ñÓñ¢ùÇð®®¦¡©‘­F Ý]Ýû¯íðn commit üîðzÝ­­C ø•¸¢Ýûýz¾¥­ADB2
for OS/390 ¦¸¾¯ 5 ¸×¦¸¾¯ 6 ÏœÏ„ï¸ IWH.INVERTDATA­C

DB2 for OS/390 ÏœÏ„ï¸ Java ùØ¾×¦Þ¸w÷q¦§ù‡¬’­A¸ã¾H 390 ¾ð¾xÏWÏœÏ„ï¸
IWH.FORMATDATE­C

Java ·xÝsæ{õ€¦§«dùãñãøÒæ{õ€

(¯­¸£¸¢­uDB2 for OS/390 Application Programming Guide and Reference for
Java­v)­G

//DSNWLMJ PROC DB2SSN=DSN,NUMTCB=5,APPLENV=DSNWLMJ   <-- WLM ENVIRONMENT value in
CREATE PROC
//*******************************************************************
//*      THIS PROC IS USED TO START THE WLM-ESTABLISHED SPAS        *
//*      ADDRESS SPACE FOR THE DSNWLMJ APPLICATION ENVIRONMENT     *
//*      V WLM,APPLENV=DSNWLMJ,RESUME                              *
//*******************************************************************
//DSNWLMJ EXEC PGM=DSNX9WLM,TIME=1440,REGION=0M,
//             PARM='&DB2SSN, &NUMTCB, &APPLENV'
//STEPLIB  DD  DSN=DSN.TESTLIB,DISP=SHR
//         DD  DSN=IWH710.SIWHPDSE,DISP=SHR     <--This has the transformers in it
//         DD  DSN=DSN.HPJSP.PDSE.JDBC,DISP=SHR <--HPJ DLLs from HPJ setup
//         DD  DSN=SYS1.PP.PDSELINK,DISP=SHR    <--HPJ runtime libraries
//         DD  DSN=DSN710.SDSNEXIT,DISP=SHR
//         DD  DSN=DSN710.SDSNLOAD,DISP=SHR
//         DD  DSN=SYS1.SCEERUN,DISP=SHR
//         DD  DSN=DSN.PDSE,DISP=SHR               <--HPJ setup info
//JAVAENV  DD  DSN=DSN.WLMENVJ.JSPENV,DISP=SHR  <--Environment variables, see below
//CEEDUMP  DD  SYSOUT=A
//DSSPRINT DD  SYSOUT=A
//JSPDEBUG DD  SYSOUT=A
//SYSABEND DD  SYSOUT=A
//SYSPRINT DD  SYSOUT=A


«dùã·“ûãš¬’÷ˆ©’ôø

(¯­¸£¸¢­uDB2 for OS/390 Application Programming Guide and Reference for
Java­v)­G

ENVAR("TZ=PST07",
"DB2SQLJPROPERTIES=/usr/lpp/db2/jdbc/db2710/classes/db2sqljjdbc.properties",
"LIBPATH=/usr/lpp/DWC",
"VWSPATH=/usr/lpp/DWC",
"CLASSPATH=/usr/lpp/db2/jdbc/db2710/classes:/usr/lpp/DWC:/usr/lpp/hpj/lib"),
MSGFILE(JSPDEBUG)

¶…ï®æ{Ý­¦§øˆ©a¯yù¾Ï„ï¸

OS/390 ¾Nýzæ{Ý­ýœ¾Ö¦§Ïjü­¾öøT©õªãô€øeÝš NT ¾ð¾xùà÷¥Žô­A ¸ã¾HÏjÝh¬’ñ­¦pÏU­A
øT©õ¯yù¾ùt©éóé UDB for NT ÝpÝ¢Ýw÷ÓÝà¸w­C ¶…ï®æ{Ý­ªOùã¾~­COS/390 ¾Nýzæ{Ý­ïœ
ù¥ÏUÝCøT©õ·©žù¥¶…ï®æ{Ý­ùØ¾×­G

File name:           For language:
Xf.properties_Fi_FI  Finnish in Finland
Xf.properties_No_NO  Norwegian in Norway
Xf.properties_Ru_RU  Russian in Russia
Xf.properties_Zh_CN  Chinese in China (People's Republic of China)
Xf.properties_Zh_TW  Chinese in Taiwan
Xf.properties_Da_DK  Danish in Denmark
Xf.properties_De_DE  German in Germany
Xf.properties_En_US  English in U.S.
Xf.properties_Es_ES  Spanish in Spain
Xf.properties_Fr_FR  French in France
Xf.properties_It_IT  Italian in Italy
Xf.properties_Ja_JP  Japanese in Japan
Xf.properties_Ko_KR  Korean in Korea
Xf.properties_Pt_BR  Portugese in Brazil
Xf.properties_Sv_SE  Swedish in Sweden

ðYñz¦§¶…ï®æ{Ý­øT©õÏœªOð^Ï†­A«Ñ¨‹ù£ÏWðzù„ÏÏÏ@ðà·©ž­AñNù„Ï§©e«’¯sù
Xf.properties­C

42.27.6 Ýsù£ DB2 ùtÝCÏõ¾~¦§÷ˆ©’©w

ðYðnÝsù£®D DB2 Universal Database ùtÝC¦§÷ˆ©’©w­AOS/390 ¾Nýzæ{Ý­ùØ¾×
DataJoiner­C DataJoiner ¾iì¾Nýzæ{Ý­ùØ¾×üqñ`¦§ DRDA Ýˆªy­A õØ¸¯¾ÝïNªO UDB
÷ˆ©’©w­CÝp¦G ODBC ðnùDüQóÏèùÏ@ðà®D DB2 ùtÝC÷ˆ©’©wùàú«­ADataJoiner ú|¸I¾s
¦ç¾[¬hÝ÷¦§æ{Ý­«XùàÝsù£¾~ü­¦§÷ˆ©’©w­C

DataJoiner ¾i¾HÝsù£ Oracle­BSybase­BInformix­BMicrosoft SQL Server­B
Teradata Ï×¾“Ý¢ù„¾ÝøäÝ‘Ýb Windows NT­BAIX ¸× Sun Solaris õ@ú~·“ûãÏWÝü ODBC
XøÒæ{Ý­¦§÷ˆ©’©w­COS/390 ¾Nýzæ{Ý­¾iÝsù£õ@ªøùàú«¦§ DataJoiner­A Ýìõ@ªø¾¬ÑïN
Ïœ¾i¾H­CDataJoiner ÏœÏ„ï¸ÏGô¾ªq¦§ COMMIT­C µ”æM DataJoiner Ýb¦¸¾¯ 2.1 Ï×
2.1.1 ÏÏÏ„ï¸ TCP/IP õ@ªø·ü¾×æ{Ý­ðnùDóû­A Ýì¾ÝùÇùSÝü·ü¾×æ{Ý­Ý›¦Aóû­CÝ]ªø
OS/390 ¾Nýzæ{Ý­ ¯íðn·ü¾×æ{Ý­Ý›¦AóûùàùØ¾× TCP/IP­A «Ñõ‹¾× SNA üs«uùàñq
OS/390 Ýsù£ DataJoiner­C

Ýb OS/390 ÏWÝsù£ IMS Ï× VSAM

Classic Connect ¾iðàõOñqðš·x¾Nýzæ{Ý­µÒôRÏ×Ýw÷Ó­C OS/390 ¾Nýzæ{Ý­üzûL
Classic Connect ODBC XøÒæ{Ý­ùàÝsù£ IMS Ï× VSAM­CClassic Connect ¾iìñzü]÷m
IMS Ï× VSAM ÷ˆ©’ôø¦§ DB2-like ¸w÷q­A æM® ùØ¾× ODBC ùàÝsù£¾ÝðÞ­C

OS/390 ¾Nýzæ{Ý­ú|©éóéðnùDªOõ_óÏèù Classic Connect ¸× DB2­A ùà÷ÏJ¾¨«T¦§
ODBC XøÒæ{Ý­­CÝp¦GñzðnÝsù£ DB2 ùàú«­A ¾Nýzæ{Ý­ú|÷ÏJ DB2 ODBC XøÒæ{Ý­­CÝp
¦Gñz¾¨ÝbÝsù£ VSAM ¸× IMS ùàú«­A ¾Nýzæ{Ý­ú|÷ÏJ Classic Connect ODBC XøÒæ{
Ý­­CæM® ïNú|üBýz¾Nýzæ{Ý­ðnùD­C

ü]÷m Classic Connect ODBC XøÒæ{Ý­¯Pðš·xÝsù£

Classic Connect ¾iðàõOñq OS/390 ¾Nýzæ{Ý­µÒôRÏ×Ýw÷Ó­C Classic Connect ¾iñNü‘
Ï@·©ž¸×Ï@ðà·©ž¦§Ï@ü­¾öæ›ªøÏ@¸×ÝhðàÇ”µpÝ­¦¡©‘­C ñz¾ýôúû‹ªM IMS ¸M VSAM ÷ˆ
©’­AÏ~î…ì Classic Connect Ýsù£­C ñz¾iÏƒøÒû‹ªM÷ˆ©’¸×ùØ¾× Microsoft Windows
Classic Connect ®DÇ”µpÝ­÷ˆ©’û‹ªMæ{Ý­­C

  1. Ýb OS/390 ÏWÝw÷Ó Classic Connect Data Server­C
  2. ¨‹¾×¸Ò­GÝb NT ÏWÝw÷Ó Classic Connect Data Mapper ýœ®~­C
  3. ¸w÷q Classic Connect ¦§è¨Š¦¡¸w÷q­Aì Classic Connect ¾iùÞÇ”®YùàÝsù£÷ˆ
     ©’­Cñz¾iùØ¾×÷ˆ©’û‹ªMæ{Ý­ùà®¾á IMS ¸M VSAM æý§c¦§¸w÷q­A¸×ÏƒøÒ®¾á¸w
     ÷q­C
  4. Ýbñzü]¸w Classic Connect Ïõ® ­Añz¾iü]¸wû‹¸¢ðš·x¦§Ýsù£vðð­G
       a. ®¾áÏ@ðà Classic Connect .ini ·©ž­C

          «dùã Classic Connect ·ü¾×æ{Ý­ª[§c· cxa.ini Ýb /usr/lpp/DWC/ ¾¨ì
          ÏÏ­A¾B¾Ýú|Ýbüo—«’¯sæûñz­G

          * national language for messages
          NL = US English
          * resource master file
          NL CAT = usr/lpp/DWC/v4r1m00/msg/engcat
          FETCH BUFFER SIZE = 32000
          DEFLOC = CXASAMP
          USERID = uid
          USERPASSWORD = pwd
          DATASOURCE = DJX4DWC tcp/9.112.46.200/1035
          MESSAGE POOL SIZE = 1000000

       b. õ¢ús .ini ·ÏÏ¦§ DATASOURCE Ý‘­CüoÏ@Ý‘¾]õtÏ@ðà÷ˆ©’ùàú«ÝW§ëÏ×Ï@ðà
          üq®Hù¢¸wÝõ}­C ÷ˆ©’ùàú«ÝW§ë¾ýôú¯P Classic Connect ÷ˆ©’Ý›¦AóûÏW¸w
          ÷q¦§ Query Processor ÝW§ëªêû‹·ü­A Ý÷mÝb÷ˆ©’Ý›¦Aóû¦§øt÷m·ÏÏ¦§
          QUERY PROCESSOR SERVICE INFO ENTRY­Cüq®Hù¢¸wÝõ}¾iÝbÝPÏ@ðà·©žÏÏ
          ¦§ TCP/IP SERVICE INFO æn¨ìõ„ù­Cüoðà·©ž÷Þ¦§ USERID Ï×
          USERPASSWORD ú|Ýb¸w÷qðš·x÷ˆ©’ùàú«©¾×ù­C
       c. ôž¾X CXA_CONFIG ·“ûãš¬’ù Classic Connect æ{Ý­·­A ¾ÝðÞüqñ`¯P
          .ini ·©žÝÝbªêÝP¦§¾¨ì­C
       d. õ¢ús LIBPATH ·“ûãš¬’­AñN÷“©|¾[ù Classic Connect æ{Ý­·­A üqñ`¸M
          .ini ·©žÝbªêÝP¦§¾¨ìÏÏ­C
       e. ¨‹¾×¸Ò­GùØ¾×ï£÷åæ{Ý­ cxasamp ùà‡ÇãÝw÷Ó­GÝbñz¦§.ini ·©ž¸ãÝb¦§¾
          ¨ìÏÏ¨‚ÏJ cxasamp­C location/uid/pwd ªO¸w÷q¸¢ .ini ·©žÏÏ¦§ data
          source name/userid/userpassword­C
       f. ¸w÷q÷ˆ©’ùàú«ùðš·x­AïNÝpÝPñz¸w÷q¾“Ý¢ DB2 ÷ˆ©’ùàú«­C

ñzÏœ¯íðn¾hõ¢ús dsnaoini ·©ž­A Ý]ªø DB2 for OS/390 ùSÝüXøÒæ{Ý­§èýzð–­C
Classic Connect ¦§XøÒæ{Ý­§èýzð–Ï§®Ýb OS/390 ¾Nýzæ{Ý­ÏÏ­C

42.27.7 øäÝ‘ DB2 for OS/390 Ï«¾×æ{Ý­

ñz¾ýôúñN APAR PQ44904 Ïè¾×Ýš OS/390 ¾Nýzæ{Ý­­A¾H®KùØ¾×¾Nýzæ{Ý­ùàøäÝ‘Ï«¾×æ{
Ý­­C

DSNUTILS ªOÏ@ðàÝb WLM ¯P RRS ·“ûãÏÏøäÝ‘¦§ DB2 for OS/390 ·xÝsæ{õ€­Cñz¾i¾H¾×
¾ÝùàøäÝ‘¾“Ý¢¶€¾¥ùØ¾×¦Þ¸w÷q·xÝsæ{õ€Ïôðñ¸ãÝw÷Ó¦§ DB2 Ï«¾×æ{Ý­­CDB2 for OS/390
LOAD­BREORG Ï× RUNSTATS Ï«¾×æ{Ý­ïœù¥Ï§©e¦¡­Aù¥ñz¾×ùàšõ¢Ï«¾×æ{Ý­ÝpÝ¢øäÝ‘­C
ñìšõ¢Ï«¾×æ{Ý­¦§Ï§©e­A«ÑÝbÏ«¾×æ{Ý­¦§­uüBýz¬ã®ªýœ¾Öóû­væ›æ­ÏW®”Ï@ÏU¾kµ„­AÝA
®”Ï@ÏUÏ§©e­C

Warehouse Manager ¾‡ïœù¥ DSNUTILS ¦§Ïôðñ­AìñzÝb Warehouse Manager ùB’JÏÏ¾i
ù™ÏJ DB2 Ï«¾×æ{Ý­­C

ðYðnü]¸w DSNUTILS ·xÝsæ{õ€­G

  1. ú¡Ýw÷Ó DB2 ©­AøäÝ‘ DSNTIJSG Ïuõ@ùàü]¸w¸Müsæý DSNUTILS ·xÝsæ{õ€­C«Ñ«T
     ¸w DSNUTILS ¦§¸w÷qÝü PARAMETER STYLE GENERAL­C
  2. ñã¾× WLM §èýz¦§·xÝsæ{õ€­C
  3. ü]¸w RRS Ï× WLM ·“ûã­C
  4. øäÝ‘ DB2 ïœù¥¦§«dùãõ†Ý÷ DSNUTILS æ{Ý­­C(ÝûùB’J®D¾ýðn­AÝì®ŽüøäÝ‘­C)
  5. ñN DSNUTILS üWû§¯P DSNCLI üWû§õ@üsæý­AÝpÝû CLI ïN¾i¾H¸I¾s·xÝsæ{õ€­G

                     BIND PLAN(DSNAOCLI) PKLIST(*.DSNAOCLI.*, *.DSNUTILS.*)

  6. ùØ¾× Warehouse Manager ü]¸wùB’JùÇøäÝ‘÷àùB’J­C¾·‚Çç®ª·ü÷àªO APPEND­CðY
     ÏœªO­A®høäÝ‘Ï«¾×æ{Ý­Ïõ®e­AWarehouse Manager ú|õRøœ¦¡©‘ÏÏ¦§¸ãÝüôæ¾­C

ùØ¾× LOAD Ï«¾×æ{Ý­Ýb DB2 for OS/390 ¦¡©‘Ïõô­«’¯s÷ˆ©’

øýü]ñzúQðnñN¦¡©‘ù›÷ÝšÏ@ðàî¶Ï†Ýr·ùà«’¯s¦¡©‘­AæM® ñNî¶Ï†Ýr·÷ÏJÝš¾tÏ@ðà¦¡
©‘­C ñzüqñ`¾ýôúù›÷÷ˆ©’­A«s¨Š÷ÏJññùŒüîðzÝ­ùàù›÷ýœ¾Ö¦§÷ˆ©’­A æM® ÷ÏJ÷ˆ
©’­CüzûLðš·x­Añz¾i®¸wñzðnð®ús÷ÏJÝšÏœÝP¦§¦¡©‘­A Ïœ¾ýÝbùB’JÏõô­øñÏŒ¸MÏƒøÒ«s
¨ŠññùŒüîðzÝ­­C øæ¦kÝpÏU­GùØ¾× Reorg/Generic Ïôðñùà®¾áÏ@ðàùB’J­A ù„ÏÏùØ¾×
UNLOAD Ï«¾×æ{Ý­¸× REORG TABLESPACE Ï«¾×æ{Ý­ùàù›÷Ï@ðà·©ž­CüoùƒðàÏ«¾×æ{Ý­ú|
ýœ¾Öùƒðà¨‚¾X÷ˆ©’ôø­A ù„ÏÏÏ@ðàõtÝü¦¡©‘÷ˆ©’­A¾tÏ@ðàõtÝü¾i¨‚ÏJÝš LOAD ¦§Ï«¾×æ{
Ý­ññùŒüîðzÝ­­C ÝbÏ«¾×æ{Ý­¸ãýœ¾Ö¦§ññùŒüîðzÝ­ÏÏ­A INTO TABLE ¦¡©‘ÝW§ëªOÏwù›÷
¦§¦¡©‘ÝW§ë­C¾HÏUÆ¾šñz¾iÝb Reorg Unload ùB’JÏÏùØ¾×¦§ DSNUTILS ø¥¬’«dùã­G

¦¡ 33. Reorg Unload ùB’J¦§Ï§©e
 UTILITY_ID                REORGULX
 RESTART                   NO
 UTSTMT                    REORG TABLESPACE DBVW.USAINENT UNLOAD EXTERNAL
 UTILITY_NAME              REORG TABLESPACE
 RECDSN                    DBVW.DSNURELD.RECDSN
 RECDEVT                   SYSDA
 RECSPACE                  50
 PNCHDSN                   DBVW.DSNURELD.PNCHDSN
 PNCHDEVT                  SYSDA
 PNCHSPACE                 3

ùØ¾× Reorg/Generic DSNUTILS Ïôðñùà®¾áÏ@ðà÷ÏJùB’J­C DSNUTILS Ï«¾×æ{Ý­üîðz
Ý­ø¥¬’üqñ`®¸wÏ@ðàÏ«¾×æ{Ý­ññùŒüîðzÝ­­C ðš·xÏ«¾×æ{Ý­Ïôðñ¾‡©eü\Ï«¾×æ{Ý­üîðzÝ­
Ž‘ÝÏÏ¾Xý{·ÝW­C ñz¾iùØ¾×Ç”µ„Ýr FILE ùà®¸w¾]õtÝü©ŽññùŒüîðzÝ­¦§·©ž­A ¾HÏ×
ùØ¾×Ç”µ„Ýr TABLE ùà®¸wñzðn÷ÏJ¦§¦¡©‘ÝW§ë­C ðYðnùØ¾× LOAD Ï«¾×æ{Ý­ùàùØ¾×¾ì
®e«dùã¦§¨‚¾X­A «ÑÝb LOAD Ï§©eÏÏÏè¾×ÏUÝCø¥¬’ðÔ­G

æ—:
     Ýb UTSTMT Ž‘ÝÏÏ­Aµ„ÏJÏ@ðà÷ÏJüîðzÝ­­A¸×µ„ÏJ REORG Ï«¾×æ{Ý­¸M UNLOAD
     EXTERNAL ¨‹ôæ¸ã¨‚¾X¦§·©žÝW§ë­C

¦¡ 34. LOAD ùB’JÏ§©e
 UTILITY_ID             LOADREORG
 RESTART                NO
 UTSTMT                 :FILE:DBVW.DSNURELD.PNCHDSN:TABLE:[DBVW].INVENTORY
 UTILITY_NAME           LOAD
 RECDSN                 DBVW.DSNURELD.RECDSN
 RECDEVT                SYSDA

üoû‹¸¢ªêÝP¸×ÏœÝP DB2 Ïlùtý×ÏW¦§¾“Ý¢ DB2 for OS/390 ùàú«¸M¾¬Ñ¦¡©‘ªãÝü¾×­C
ññùŒüîðzÝ­î¶Ï†Ýr·¾i¾HªO HFS ¸×ð¸l MVS ·©ž­C

ðY¯íõ¢ÝhÝüÇ” OS/390 ÏW¾i¾×¦§ DSNUTILS ¯P DB2 Ï«¾×æ{Ý­¦§÷âýà÷ˆøT­A «Ñø¥ó\
DB2 for OS/390 Utility Guide and Reference­C

42.27.8 õê¬g

ñz¾i¾HùØ¾× OS/390 ¾Nýzæ{Ý­ùàñN Data Propagator õê¬gÏè¾×ùB’JÝêøÒÏ’­Cõê¬g¯íðn
ÝüÏ@ðàùàú«÷ˆ©’©w­BÏ@ðàññùŒ÷ˆ©’©w­A¾HÏ×Ï@ðà¾¬Ñ÷ˆ©’©w­Cüoù€¾i¾HªOÏœÝP¸×ªêÝP
¦§÷ˆ©’©w­C Ï@ðà¶^ù£Ïu¦ù£ DB2 Ï‚¯xùàõP¶_ùàú«÷ˆ©’©wÏÏÏwús¬W­Bõ¢ús¸×šõ¢¦§
ÝC­C æM® ­AÝûÏuõ@ñNšõ¢¬gÏJÏ@ðàšõ¢÷ˆ©’¦¡­C æM® ú|øäÝ‘Ïè¾×Ïuõ@ñNšõ¢©M¾×ù
¾¬Ñ÷ˆ©’©wÏÏ­C DB2 Warehouse Manager ¾i®¾áõê¬gùB’J¾HÝêøÒÏ’Ïè¾×Ïuõ@­CùØ¾×
Warehouse Manager ¸w÷qðnøäÝ‘¦§Ïè¾×Ïuõ@Çç®ªÏ×øäÝ‘¦§©ô­­Cñz¾ýôúñN SASNLINK
·©ž©wôž¾Xù steplib ·“ûãš¬’­C

ús¬Wõê¬gÏ„ï¸ù­u÷ˆ©’ðš·xÏÏÏá­v¬ã¦O

­u÷ˆ©’ðš·xÏÏÏá­v¾]ªAÏFÏ@ðà JCL ¬ã¦Oæûõê¬gÏ„ï¸­C Ýp¦Gñzðpû§ðnùØ¾×üoðà OS/390
¾Nýzæ{Ý­ùàøäÝ‘Ïè¾×æ{Ý­­A ®hñz¾ýôúªøñz¦§ OS/390 ùtý×šõ¢Ýû¬ã¦OÏÏ¦§ñbÏ Ï×÷ˆ©’
ôø÷ˆøT­CðYðnšõ¢¬ã¦O­G

  1. ¾HÏ@ðàÝüvððÝb /usr/lpp/DWC/ ¾¨ìÏÏ«’¯sÏ×õ¢ús·©ž¦§ ID ænÏJ­C
  2. ïMõ„ apply.jcl­AùÇñNÝû·©ž¾tÝsªø systemname.apply.jcl­A ù„ÏÏ
     systemname ªO MVS ùtý×¦§ÝW§ë­C ùãÝp­AÝp¦GÝb STLMVS1 ÏW­A®¾á¦§·©žø’¾¯
     ÝWªø STLMVS1.apply.jcl­C
  3. ùØ¾×Ï†Ýr«s¨Šæ{Ý­ùàÝêðq JCL­A¾HýÝXñzî÷¾x¦§¯íùD­C šõ¢ñbÏ ÷ˆøT¾HýÝXñz
     ¦§ MVS ùtý×¦§¬Ñú€ñbÏ ÷ˆøT­A ùÇšõ¢ STEPLIB DD ¦§÷ˆ©’ôøÏ× MSGS DD­C
  4. Ýp¦G¯íðn­Ašõ¢ EXEC ¾dÏW¦§æ{Ý­ÝW§ë­C ðY¯íšõ¢æ{Ý­ÝW§ë¦§÷âýà÷ˆøT­A «Ñø¥
     ó\ DB2 ®®n¯Pø¥ÝãÏƒ¾U­C«ÑÏšõ¢¾“Ý¢ÏŠªA¸ú([) Ï§¦§ø¥¬’­A Ï¤Ýp [USERID]
     Ï× [APPLY_PARMS]­C(ÏŠªA¸úÏ·õOªøÏQÏ¯ôiÝÝrÏ÷ x'AD' Ï× x'BD'­CðYñz¦§ TSO
     ýž§íóöÇç®ªÝb SPF ¨‹ôæ 0 ÏÏ¾¬ü]Ýù 3278A­Aüoù€ðÔ¾iî…ú|Æ¾šÝùîS©¡ÝrÏ÷­AÝà
     ÏœªOÏŠªA¸ú­CüoùÇÏœú|ªOøíÇD­A Ýp¦GñzùSÝüšõ¢ x'AD' ¸× x'BD'­A¸×¦Þ¾“Ý¢Ýr
     Ï÷Ïõô­¦§÷ˆ©’­C)
  5. õ¢ús·“ûãš¬’ VWS_TEMPLATES­A®ÝV«’¯s¦§¬ã¦O·©ž¦§¾¨ì­C

ÏUÝC«dùãÆ¾š­u÷ˆ©’ðš·xÏÏÏá­vÏÏ¦§ JCL ¬ã¦O­G

Ïè¾× JCL ¬ã¦O­G

//[USERID]A  JOB ,MSGCLASS=H,MSGLEVEL=(1,1),
//  REGION=2M,TIME=1440,NOTIFY=&SYSUID
//* DON'T CHANGE THE FIRST LINE OF THIS TEMPLATE.
//* THE REMAINING JCL SHOULD BE MODIFIED FOR YOUR SITE.
//**********************************************
//* RUN   APPLY/MVS ON OS/390 DB2 6.1          *
//**********************************************
//ASNARUN  EXEC PGM=ASNAPV66,REGION=10M,
//  [APPLY_PARMS]
//STEPLIB  DD  DISP=SHR,DSN=DPROPR.V6R1M0.SASNLINK
//         DD  DISP=SHR,DSN=DSN610.SDSNLOAD
//MSGS     DD  DSN=DPROPR.V2R1M0A.MSGS,DISP=SHR
//ASNASPL  DD DSN=&&ASNASPL,DISP=(NEW,DELETE,DELETE),
//         UNIT=SYSDA,SPACE=(CYL,(10,1)),
//         DCB=(RECFM=VB,BLKSIZE=6404)
//SYSTERM  DD  SYSOUT=*
//SYSTSPRT DD  SYSOUT=*
//SYSPRINT DD  SYSOUT=*
//


42.27.9 ¾Nýzæ{Ý­øO÷

ü\Ýh DB2 Warehouse Manager Ï÷¾¢ (Ï¤ÝpÝ›¦Aóû­BÏ‚¯xóû­B¾Nýzæ{Ý­Ï×ü­¾ö­u÷ˆ©’ðš
·xÏÏÏá­v) ú|ñNÏ‚¯x¬gÏJùÏ‚¯x¾¨ì (®¸wÝb VWS_LOGGING ·“ûãš¬’ÏÏ)­CÏ‚¯x·ªø
î¶Ï†Ýr­C

ñz¾iñq­u÷ˆ©’ðš·xÏÏÏá­vñãøÒ¾Nýzæ{Ý­Ï‚¯x­C Ýb¾¦æ­©‘ÏÏ­A¾Hú’û®¾kµ„®”Ï@ÏUðš·x­A
ÝA®”Ï@ÏUÏ§©e­CÝb­uøl¶š¬hÝ÷­v¬ÑãÏW­AñNü]¸wðÔšõ¢Ýùñzðn¦§øl¶š¬hÝ÷­C ¾Nýzæ{Ý­
øl¶šÏ„ï¸¬hÝ÷ 0-4­G

   * ¬hÝ÷ 1 - ôiÏJ/¶öô}øl¶š
   * ¬hÝ÷ 2 - ¬hÝ÷ 1 ¾[ÏWøœ¨—øl¶š
   * ¬hÝ÷ 3 - ¬hÝ÷ 2 ¾[ÏW÷ˆ©’øl¶š
   * ¬hÝ÷ 4 - Ï§ü­«w«ŽøØøl¶š

ú¡øl¶š¦§ü]¸wø¦¸¢¬hÝ÷ 1­A©Žî…ñNú|÷–§C­C¾uÝüøœ¨—©Ï~·üô}ñãøl¶š­Cøl¶š÷ˆøTú|·x
ÝsÝb AGNTxxx.LOG ·©žÏÏ­A·“ûã÷ˆøTú|·xÝsÝb AGNTxxx.SET ·©žÏÏ­C
  ------------------------------------------------------------------------

42.28 Windows NT ÏW¦§ñqŽíî÷§íõ™ù£

Ýp¦GùØ¾×¦Þûµ÷å¾hÝsù£Ï@¾x Windows NT Server óöóûÏW¦§ READ PERM DB ·©ž­A Ýà
ÝbóöóûÏWªOùØ¾×õtÝü©ŽýøO¦§Ý@¾×§Ø§Ñóöùà®¾á DB2 ÷ˆ©’Çæý­A ·©žú|Ýpûwïµô}
ñã­CæMÝà­AÝbÝûÏõ® ­AùØ¾×ªêÝPýøO¦§® Ž•ô}ñãðnùDùÇÏœú|øeùÝ›¦Aóû­A ÝàªO¾¥ñqŽí
î÷ÏW¦§õ™ù£ùà¦AøÔ­CõYùØÝbýøOùïµÏõ® ­A ùØ¾×¦ÞÏï¾i¾Hªíù·©ž¦§Ï§©e­AÝ]ªøôæ¾
ÏïæMÝbõ™ù£ÏõÏÏ­CæMÝà­AÝp¦G·©žªOÝbÏ@¾x Windows NT Workstation ÏW­A®hÝûøíÇD
ùÇÏœú|æo¾Ö­C

÷¥ùMÏŠ©žªOÝb Windows NT Server ÏWñNæn¨ìôæ¾
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
Lanmanserver\Parameters\EnableOpLocks ü]¸wªø 0­C¶€¾¥Ýûæn¨ìü]¸w­AùCú¡üzûLÝ@
¾×§Ø§ÑóöñqñqŽíÏuõ@î÷Ýsù£Ý›¦AóûÏW¦§·©ž©­A ðnùDÏ@¸wú|øeùÝ›¦Aóû­AÝàÏœú|¾¥ñq
Žíî÷õ™ù£ùà¦AøÔ­CÝ]Ýû­A¸ãÝüðnùDüœú|ð®ús‡ÇãýøO­C

Ýû÷¥ùMÏŠ©ž¦§ðtðñ¬vTªOüo¬Óú|¬vT¸ãÝüüzûLÝ@¾×§Ø§ÑóöñqÝ›¦AóûÝsù£·©ž¦§óÆ‚©Ž
î…­CõYùØÝüÝûü]¸w­AÝp¦G·©žªOüzûLû‹ªMùÝ›¦Aóû¾¯ùð¦§Ý@¾×§Ø§ÑóöùàÝsù£¦§ (ú¡æL
¦kñqÏœÝP¦§ñqŽíî÷óöóû)­Aæý¦GªOÏïú|ñqõ™ù£ùà¦AøÔðnùD­CÝ]Ýû­AýøOûLïµùÇùSÝü¾Ö
©Ž­C

æ—:
     Ýb¸ãÝü¦§ñ­¦pÏU­AÝp¦G·©žÝsù£ªO¾¯§íÝsù£­A Ýà®DüzûLÝ@¾×§Ø§Ñóö­AýøO‡Çã
     Ï×® Ž•¦§ýøOûLïµú|Ýpûwïµæo¾Ö­C

  ------------------------------------------------------------------------

42.29 Enterprise Edition UNIX CD-ROM ¦§÷å¾×ýœ®~

óA¾×¸¢ UNIX ¾ð¾x¦¸¾¯ 6 Ï×¦¸¾¯ 7 ¦§ DB2 Universal Database (UDB) Enterprise
Edition (EE) CD-ROM­A ¾]õtÏ@©M 90 Ï¥¦§ DB2 Connect Enterprise Edition (CEE)
÷å¾×¦¸­C¾¥¸¢ DB2 Connect ¾\î…ªO®¾á¸¢ DB2 UDB EE ýœ®~ÏÏ­A ñzÏœ¯íðnÝbÏwÝw÷Ó
DB2 UDB EE ¦§ùtý×ÏWÝw÷Ó DB2 CEE ýœ®~ïNî…ùØ¾× DB2 Connect ¾\î…­C Ýp¦GñzÝw÷Ó
ÏF 90 Ï¥¦§ DB2 CEE ÷å¾×¦¸­AùÇ¾BùM¸w¦@îÝšñ¶v¦¸¾¯­AïN¾ýôúµÒôR DB2 CEE ýœ®~
ùÇÝw÷Ó DB2 CEE ñ¶v«X­CñzÏœ¯íðnð®úsÝw÷Óýœ®~­C Ýb DB2 EE ¸× DB2 CEE for UNIX
õ™ütÏJ¦—Ï@©¥ÏÏïœù¥ÏFÝw÷Óñ¶v«X¦§®¾š­C

Ýp¦GñzÏw·Hæê EE ¦§Ýw÷Ó­AÝw÷Ó÷å¾×¦§ CEE ýœ®~­A®oÏœúQðn¾ÇÏ[ÝaÝw÷Ó CEE­A ñz¾i
¾H¨¡ï`ÏUÝC®¾š­Aøœ¾h 90 Ï¥¦§ CEE ÷å¾×¦¸­CÝp¦Gñzøœ¾h Connect EE ¦§÷å¾×¦¸­A
ñNÏïæM¾i¾HùØ¾× DB2 EE ¦§ DB2 Connect ¾\î…­C

ðYðnøœ¾h DB2 Connect ¦¸¾¯ 7­A«ÑñqÝUðà¾ð¾x÷¥øœÝw÷ÓÏUÝC¦§·©žôø­G

   * Ýb AIX­A÷¥øœÝw÷Ó db2_07_01.clic ·©žôø­C
   * Ýb NUMA-Q Ï× Solaris õ@ú~·“ûã­A÷¥øœÝw÷Ó db2clic71 ©M÷Óün‚­C
   * Ýb Linux­A÷¥øœÝw÷Ó db2clic71-7.1.0-x RPM­C
   * Ýb HP-UX­A÷¥øœÝw÷Ó DB2V7CONN.clic ·©žôø­C

ðYðnøœ¾h DB2 Connect ¦¸¾¯ 6­A«ÑñqÝUðà¾ð¾x÷¥øœÝw÷ÓÏUÝC¦§·©žôø­G

   * Ýb AIX­A÷¥øœÝw÷Ó db2_06_01.clic ·©žôø­C
   * Ýb NUMA-Q Ï× Solaris õ@ú~·“ûã­A÷¥øœÝw÷Ó db2cplic61 ©M÷Óün‚­C
   * Ýb Linux­A÷¥øœÝw÷Ó db2cplic61-6.1.0-x RPM­C
   * Ýb HP-UX­A÷¥øœÝw÷Ó DB2V6CONN.clic ·©žôø­C

  ------------------------------------------------------------------------

42.30 DB2 Connect Enterprise Edition UNIX CD-ROM ¦§÷å¾×ýœ®~

óA¾×¸¢ UNIX ¾ð¾x¦¸¾¯ 6 Ï×¦¸¾¯ 7 ¦§ DB2 Connect Enterprise Edition (EE)
CD-ROM­A ¾]õtÏ@©M 90 Ï¥¦§ DB2 Universal Database (UDB) Enterprise Edition
(EE) ÷å¾×¦¸­Cïœù¥ 90 Ï¥¦§ DB2 UDB EE ÷å¾×¦¸õ@ªøæ–Ý“Ïõ¾×­A û‹ DB2 Connect ¦§
ûBõ@ùÇÏœªO¾ýðn¦§­C

Ýp¦GñzÝw÷ÓÏF 90 Ï¥¦§ DB2 UDB EE ÷å¾×¦¸­AùÇ¾BùM¸w¦@îÝšñ¶v¦¸¾¯­A ïN¾ýôúµÒôR
DB2 UDB EE ýœ®~ùÇÝw÷Ó DB2 UDB EE ñ¶v«X­C ñzÏœ¯íðnð®úsÝw÷Óýœ®~­CÝb DB2 EE
¸× DB2 CEE for UNIX õ™ütÏJ¦—Ï@©¥ÏÏïœù¥ÏFÝw÷Óñ¶v«X¦§®¾š­C Ýp¦GñzÏw·Hæê
Connect EE ¦§Ýw÷Ó­AÝw÷Ó÷å¾×¦§ UDB EE ýœ®~­A ®oÏœúQðn¾ÇÏ[ÝaÝw÷Ó CEE­Añz¾i¾H
¨¡ï`ÏUÝC®¾š­Aøœ¾h 90 Ï¥¦§ EE ÷å¾×¦¸­C Ýp¦Gñzøœ¾h DB2 UDB EE ¦§÷å¾×¦¸­AñNÏœ
¬vT DB2 Connect EE ¦§¾\î…­C

ðYðnøœ¾h DB2 UDB EE ¦¸¾¯ 7­A«ÑñqÝUðà¾ð¾x÷¥øœÝw÷ÓÏUÝC¦§·©žôø­G

   * Ýb AIX­A÷¥øœÝw÷Ó db2_07_01.elic ·©žôø­C
   * Ýb NUMA-Q Ï× Solaris õ@ú~·“ûã­A÷¥øœÝw÷Ó db2elic71 ©M÷Óün‚­C
   * Ýb Linux­A÷¥øœÝw÷Ó db2elic71-7.1.0-x RPM­C
   * Ýb HP-UX­A÷¥øœÝw÷Ó DB2V7ENTP.elic ·©žôø­C

ðYðnøœ¾h DB2 UDB EE ¦¸¾¯ 6­A«ÑñqÝUðà¾ð¾x÷¥øœÝw÷ÓÏUÝC¦§·©žôø­G

   * Ýb AIX­A÷¥øœÝw÷Ó db2_06_01.elic ·©žôø­C
   * Ýb NUMA-Q Ï× Solaris õ@ú~·“ûã­A÷¥øœÝw÷Ó db2elic61 ©M÷Óün‚­C
   * Ýb Linux­A÷¥øœÝw÷Ó db2elic61-6.1.0-x RPM­C
   * Ýb HP-UX­A÷¥øœÝw÷Ó DB2V6ENTP.elic ·©žôø­C

  ------------------------------------------------------------------------

42.31 ñÓñ¢ Data Links Manager

ñzý{Ýb¾i¾HñÓñ¢®¸w÷ˆ©’©w¦§ DB2 Data Links Manager­CªYù€÷ˆ©’µ„æýªêÇ”¦§ SQL
ðnùDÏõüBýzæ{õ€ ¯PÏ«¾×æ{Ý­Ï@¬Ó (ùãÝp­Aü’¾ö/ï_÷m)­A¾]õtÏF¯PÏwª[§c÷ˆ©’©w¦§ DLM
Ïõô­¦§üq®H­C Ýb¾H®e­ADB2 æL¦kñÓñ¢Ïwª[§c¦§ DLM­AõYùØ¾Ý¸|¾¬üQ¨‹¾×­C üoóðP
SQL Ï×Ï«¾×æ{Ý­üBýzæ{õ€¦ç¾[¦§ÇB¾~ðtý­C Ï@¾ûús¬W DLM­AÝbðnùD¦§üBýzæ{õ€ÏÏ¯P¾Ý
üq®H¦§Ïè·§­A¾iî…ú|óðPªYù€ SQL ðnùD¦§¾½ñ¥ (ùãÝp­A øœ¾h¦¡©‘/¦¡©‘¦ô­/÷ˆ©’
©w)­C
  ------------------------------------------------------------------------

42.32 ùØ¾× SMIT ÷¥øœÝw÷Ó DLFM Ï÷¾¢¾iî…ú|øœ¾hÇB¾~¦§·©žôø

ÝbñqÝw÷Ó Data Links Manager ¦§ AIX óöóûÏW÷¥øœÝw÷Ó DB2 (¦¸¾¯ 5­B6 ¸× 7) Ïõ
®e­A «Ñ¨¡ï`ÏUÝCùB’J­G

  1. ¾H root ¦§ùðÏ·­AùØ¾×ÏUÝC®¾Oü’¾ö /etc/vfs­G

     cp -p /etc/vfs /etc/vfs.bak

  2. ÷¥øœÝw÷Ó DB2­C
  3. ¾H root ¦§ùðÏ·­A¾×ùB’J 1 ¸ãøæ¦§ü’¾öù£¾N /etc/vfs­G

     cp -p /etc/vfs.bak /etc/vfs

  ------------------------------------------------------------------------

42.33 Ýb Windows 2000 ÏWùØ¾× CLP ©æo¾Ö¨—¯~ SQL1035N

Ýp¦GÝw÷Ó DB2 ù¾uÝüªYù€ùØ¾×¦Þ (ùãÝp­A§èýz¦Þ) Ï~ùÆÝü¬gÏJv¦§¾¨ì­A Ï@î‰ùØ¾×
¦Þú|Ýbûµ÷åùØ¾× DB2 ¸R¾OÝ‘üBýzóû©Ýªù¨—¯~ SQL1035N­C

ðYðn÷¥ùMÝûøíÇD­A·üÝb¸ãÝüùØ¾×¦ÞüœùÆÝü¬gÏJv¦§¾¨ìÏÏÝw÷Ó DB2­C
  ------------------------------------------------------------------------

42.34 SQL ¯ýõUæ{Ý­¦§¾[ñj¾\î…

SQL ¯ýõUæ{Ý­ÏuùÆý{ÝbÏûü\ùØ¾×¦Þªø¦¡©‘æýÝX®¸wÏœÝP¸¢ "=" ¦§æýÝXûB§ƒÏl­C ¾[ñj
¾\î…¦§­uæýÝXÇç®ª­vû‹÷š© (Ýb SQL ¯ýõUæ{Ý­ÏuùÆ¦§­uæýÝX­vðôÏW®”Ï@ÏU­uæýÝXÇç
®ª­v®”ôsïNî…ñãøÒ÷àû‹÷š©)­A ¾]õtæýÝXûB§ƒÏl¦§ÏU¸âÝC¾š­C

¾i¾×¦§ûB§ƒÏlÝü "="­B"<>"­B"<"­B">"­B"<=" Ï× ">="­C SQL ¯ýõUæ{Ý­ªOù¢õUùØ¾×¦Þ
®¾á¶ýÝ­ SQL üîðzÝ­¦§ÏuùÆ­C ¾Ý¾i¾×¸¢­u¸R¾OÏÏÏá­v(­u¾‘«ÖÝ­­v¬Ñã)­B­uññùŒÏÏ
Ïá­v(­u®¾áúõýÏ¦¡­vÏ×­u®¾áŽýæoù‡Ý­­vû‹÷š©)­B ·xÝsæ{õ€®÷móû (­uï­ÏJ SQL
·xÝsæ{õ€­v§‰’F) Ï×­u÷ˆ©’ðš·xÏÏÏá­v(SQL üBýzùB’J)­C
  ------------------------------------------------------------------------

42.35 Linux ÏW¦§ DB2 ¦§ Gnome ¸M KDE ©…ðñóÆÝX

DB2 ý{Ýbïœù¥Ï@ýåÏ«¾×æ{Ý­ùà®¾á DB2 ©…ÏW§èýzæ{Ý­÷ˆ©’õù¸MûØ¾š­A ¾×¾HÝb Gnome
¸M KDE ©…ÏW§èýzæ{Ý­ÏWñãøÒüÞñ`¾×¦§ DB2 ÏuùÆ­A ù¥¾H Intel ªøø•¶Ý¦§ Linux Ï·øe
æ{Ý­ùØ¾×­C DB2 Version 7.2 ùÞûwü]ðÔú|Ýw÷Óüoù€ÏuùÆ­A ¾B¾i¸¢Ýw÷ÓÏõ® ¾×ùà®¾á
¸Møœ¾hÏ@¸×ÝhðàùØ¾×¦Þ¦§©…ÏW§èýzæ{Ý­ûØ¾š­C

ñìús¬WÏ@ýå©…ÏW§èýzæ{Ý­ûØ¾šæûÏ@¸×ÝhðàùØ¾×¦Þ­A«ÑùØ¾×ÏUÝC®¾O­G

db2icons <user1> [<user2> <user3>...]

æ—:
     «Ñ¦`úN­AðYÝb Gnome ¸× KDE ©…ÏW§èýzæ{Ý­·“ûãøäÝ‘©ýœ¾ÖûØ¾š­A ùØ¾×¦Þ¾iî…
     ¯íðnÏƒøÒï_ús©…ÏW§èýzæ{Ý­Ï~î…ªíùœúsûØ¾š­C

ñìøœ¾hÏ@¸×ÝhðàùØ¾×¦Þ¦§Ï@ýå©…ÏW§èýzæ{Ý­ûØ¾š­A«ÑùØ¾×ÏUÝC®¾O­G

db2rmicons <user1> [<user2> <user3>...]

æ—:
     ñz¾ýôúùÆü’ùªøö¦§vððÏ~î…ýœ¾Ö¸×øœ¾hù„¾LùØ¾×¦Þ¦§ûØ¾š­C üqñ`­AÝp¦GñzªOÏ@
     î‰ùØ¾×¦Þ¦§÷š­Adb2icons ¸M db2rmicons ¾i¾×ùà®¾á¸×øœ¾hñzÝêÏv¦§ûØ¾š­AÝì
     øáÝüñzªO root ùØ¾×¦Þ¸×ªOùÆÝüvðð¬gÏJ®¸wÏõùØ¾×¦Þø_¸l¾¨ì¦§¾tÏ@ðàùØ¾×
     ¦Þ­AñzÏ~î…øö¾×üoùƒðà®¾Oùà®¾á¸×øœ¾hõOÏH¦§ûØ¾š­C

  ------------------------------------------------------------------------

42.36 Ýb Windows 2000 Terminal Server §èýz¬ãÝ­ÏUøäÝ‘ DB2

û‹¸¢ DB2 UDB Version 7.1­AFixPak 3 Ï×õ¢ø¦¦§¦¸¾¯­ADB2 ¾iÝb Windows 2000
Terminal Server §èýz¬ãÝ­ÏUøäÝ‘­CÝbÝûÏõ®e­AñzæL¦kÝb Windows 2000 Terminal
Server §èýz¬ãÝ­¦§ñqŽíî÷ô¾ªqõ@ú~ÏUøäÝ‘ DB2­C
  ------------------------------------------------------------------------

42.37 ü’¾ö¯Pï_÷m®¾O¦§«uÏW¯­¸£

Incorrect information appears when you type db2 ? backup. ¾¨«T¦§¨‚¾Xªø­G

BACKUP DATABASE database-alias [USER username [USING password]]
[TABLESPACE (tblspace-name [ {,tblspace-name} ... ])] [ONLINE]
[INCREMENTAL [DELTA]] [USE TSM [OPEN num-sess SESSIONS]] |
TO dir/dev [ {,dir/dev} ... ] | LOAD lib-name [OPEN num-sess SESSIONS]]
[WITH num-buff BUFFERS] [BUFFER buffer-size] [PARALLELISM n]
[WITHOUT PROMPTING]

ú¡ñzµ„ÏJ db2 ? restore ©­A¾Xý{Ïœ¾¨«T÷ˆøT­C¾¨«T¦§¨‚¾Xªø­G

RESTORE DATABASE source-database-alias { restore-options | CONTINUE | ABORT }";

restore-options:";
  [USER username [USING password]] [{TABLESPACE [ONLINE] |";
  TABLESPACE (tblspace-name [ {,tblspace-name} ... ]) [ONLINE] |";
  HISTORY FILE [ONLINE]}] [INCREMENTAL [ABORT]]";
  [{USE TSM [OPEN num-sess SESSIONS] |";
  FROM dir/dev [ {,dir/dev} ... ] | LOAD shared-lib";
  [OPEN num-sess SESSIONS]}] [TAKEN AT date-time] [TO target-directory]";
  [INTO target-database-alias] [NEWLOGPATH directory]";
  [WITH num-buff BUFFERS] [BUFFER buffer-size]";
  [DLREPORT file-name] [REPLACE EXISTING] [REDIRECT] [PARALLELISM n]";
  [WITHOUT ROLLING FORWARD] [WITHOUT DATALINK] [WITHOUT PROMPTING]";

  ------------------------------------------------------------------------

42.38 "Warehouse Manager" ·üªø "DB2 Warehouse Manager"

¸ãÝü¾Xý{Ýbýœ®~¨Çûä¸Mýœ®~Ï†¾¢¦§ "Warehouse Manager" üœ·ü¦ªø "DB2 Warehouse
Manager"­C
  ------------------------------------------------------------------------

¦ç¾[÷ˆøT

  ------------------------------------------------------------------------

¦ç¾[÷ˆøT

  ------------------------------------------------------------------------

43.1 DB2 Universal Database ¸M DB2 Connect «uÏWÏ„ï¸

DB2 ÷ˆøT¦§õûóÆ¸M®O®—üÞúsùàú«­A¾]ªAÝüÇ”ÝûÏ†¾¢¾X¦¸® øíÇDñïîµ¦§÷ˆøT­A «ÑùØ¾×
DB2 Universal Database & DB2 Connect «uÏWÏ„ï¸§“î÷­G
http://www.ibm.com/software/data/db2/udb/winos2unix/support­C
  ------------------------------------------------------------------------

43.2 DB2 Magazine

ÝüÇ” DB2 ýœ®~ùtÝC¦§üÞús÷ˆøT­Añz¾i¾Hðqó\õKôO¦§ DB2 Magazine­C «uÏW¦¸¦§¶›¯x¾i
¸¢ http://www.db2mag.com ù£ño­F Ýb§“ðôÏWÏ]Ýüðqó\¶›¯x¦§®¾š­C
  ------------------------------------------------------------------------

¦ç¨ì

  ------------------------------------------------------------------------

¦ç¨ì A. ¦`úNù’ôæ

ÝàÝbù„¾Ýøˆ©aÏÏ­AIBM ÏœùœñoÝüïœù¥¾¯©¥ÏÏ¸ãïœ¦§ÝUôæýœ®~­B¦AøÔ¸×¾\î…­C ðn¦óûDÝb
ñz¸ãÝbÏõøØªOõ_¾i¾×ùüoù€ýœ®~¯P¦AøÔ©­A«ÑÝVú¡Ýa¦§ IBM ¦AøÔ¾N¦¡ªd÷á­C¾¯©¥Ýbïœ
Ï× IBM ýœ®~­Bæ{Ý­¸×¦AøÔ©­AÏœ¦¡¾š¸×út¾š¾uî…ùØ¾× IBM ¦§ýœ®~­Bæ{Ý­¸×¦AøÔ­C¾u
ðn¾¬®I¾€ IBM ¦§ï¬¬zø]ýœv­A¾“Ý¢¾\î…ªêú¡¦§ýœ®~­Bæ{Ý­¸×¦AøÔüœ¾i¾Hù£¾N IBM ¦§
ýœ®~­Bæ{Ý­¸×¦AøÔ­CÏœûL­Aù„¾Ý®D IBM ýœ®~­Bæ{Ý­­B¸×¦AøÔÝbûBõ@ÏW¦§æ–¯—¯P‡Çã­A
ù„üd¾“Ží¸¢ùØ¾×¦Þ­C

Ýbüo¾¯©¥¸×Ï†¾¢ÏÏ¾iî…¾]õtæê IBM ¸ãó™ÝüÏõñMõQ¸×ñMõQ¾à«Ñ©ž­C ¾¯©¥ùØ¾×¦ÞùÇÏœù
Ýü®eðzñMõQÏõ¾“Ý¢ñ¶v­C ñz¾i¾H¾×©¥ðñÏŠÝ­ùàªd÷áñ¶v­Aùàù‡«ÑñHù­G

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

ðYðnªd÷áÝüÇ”ÏGÝÏ÷ýå (DBCS) ÷ˆøT¦§îSü\vððù’¸y­A «Ñµpæ÷ñzøˆ©a¦§ IBM ï¬¬zø]
ýœü­¦—­A¸×¦Þ¾×©¥ðñÏŠÝ­ñHù­G

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

ÏUÝCªq÷ùðY¯P÷àøˆÏõ¦k®áñ›ïé¸ŠŽý­AõYæ›ªøÏœóA¾×­G IBM ôÔ¾Hý{¦ªïœù¥¾¯©¥­AÝàÏœïœ
ù¥¾“Ý¢¸£¾š¸×·q¾šÏõ®OÇã (¾]ªAÝìÏœðð¸¢¾iøƒ ¸Ò¸×ýÝXîS¸w©Ž¾×¦§®OÇã)­CðYÝüù€Ýa
øØÝbªYù€¾‘¸”ÏWùÇÏœÏûü\ñ’øœÏWðz®OÇã­A ®h÷àñ’øœæL©Ž­C

¾¯©¥ÏÏ¾iî…ú|ÝüõèüNÏW¸×ñ’¦¸ÝLùˆÏW¦§ü_¯~­CÝ]Ýû­AIBM ú|¸wïµðžðq­F ùÇñNðžðq® ¦§
Ï§©eî€ÏJús¦¸ÏÏ­CÝP©­AIBM ño·H©õ‹ôiùÇ (¸×) šøÒ¾¯©¥ÏÏ¸ãïœÏ×¦§ýœ®~Ï× (¸×)
æ{Ý­­C

¾¯©¥û‹¸¢®D IBM §“î÷¦§ï¸Ïè¾uªOªøÏFÏŠ®KÝàïœù¥­AùÇÏœû‹üoù€§“î÷õ@¾“Ý¢¯{¾i­C÷àù€
§“î÷ÏW¦§Ï§©eùÇ®D¾¯ IBM ýœ®~Ï§©e¦§Ï@ü­¾ö­A¾×Ï ùØ¾×÷à§“î÷©·üÝêÝ‘¸àó ðú·I­C

ú¡ñzïœù¥÷ˆøTæû IBM ©­AñzõYñ¶vÏ¸ IBM ¾Hù„¯{ªøóAú¡¦§ÏŠÝ­ùàùØ¾×¸×Ï·øe÷ˆøT­A
ÝàÏœ¾ýû‹ñzðtø_¾“Ý¢üd¾“­C

¾¯æ{Ý­Ïõ·•ñ¶v¦ÞðYõ’ñ‘ù£ñoªêÇ”÷ˆ©’­A ¾H®KùØ¾×ÏUÝC÷ˆøT¦Þ¾iª½÷á IBM­C ù„ÏUÝC
÷ˆøT®¦§ªO­G (1) ¨W¾á®¾á¦§æ{Ý­¯Pù„¾Ýæ{Ý­ (¾]ªAÝûæ{Ý­) Ïõô­õ¢ï®÷ˆøT¦§ÏŠÝ­
(2) ªêÏªùØ¾×Ïw¾‘ï®Ïõ÷ˆøTÏŠ¦k­C ðYÝü¾“Ý¢øíÇD«Ñµpæ÷­G

IBM Canada Limited
Office of the Lab Director
1150 Eglinton Ave. East
North York, Ontario
M3C 1H7
CANADA

ÏWðz÷ˆ©’¦§ù£ñoÝüù„îS©¡ðn¾¢­AÝbªYù€ñ­¦pÏU¾ýôú¾IôOÏŠñoùØ¾×­C

¾¯©¥¸ãïyðz¦§¾“Ý¢æ{Ý­Ï×ù„¸ãÝü¾i¾×¦§ñ¶væêõ@ªO¾¥ IBM ¸ãïœù¥­AùÇùù­uIBM ®ÔÏ 
ÝXª—­v­B­uøˆ¯éæ{Ý­ñ¶vÝXª—­v¸×¶—ÏŠÏõô­¾“Ý¢ÝPæ¾ÝXª—ñ›ïéÏõüW«d­C

Ýûô­¸ãõtÏõ¾“Ý¢©Žî…÷ˆ©’­AªãªOñoÝêññùŒ¦§·“ûãÏõÏU­FÝ]ÝûÏœÝPõ@ú~·“ûãÏõÏU¸ãño¦§
æý¦G­A¾iî…ú|Ýü®šÏj¦§©týõ­Cü­¾öï£ôq¾iî…ªOÝbô}æoÏÏ¦§ùtý×ÏWøäÝ‘­AÝ]ÝûÏœ®OÇã¾i
¾HñqÏ@î‰¦§ùtý×·•ðPªêÝP¦§æý¦G­C ª’ÝšÝüü­¾ö¦§ï£ôq­AªOõQ¾×ï­÷¦kÝàño¦§Ý“ðpðÔ­A
ù„ûˆ¯éæý¦G¾iî…ú|Ýü¸ãÏœÝP­C¾¯©¥¦§ùØ¾×¦Þ·ü©éóéù„îSÝü¦§·“ûã­A‡Çã¾XóA¾×¦§÷ˆ
©’­C

¾¯©¥¸ãïœÏ×Ïõ®D IBM ýœ®~÷ˆøT­A®YÏ@¾¥ýœ®~¦§ù¥·üøà­A¸×ù„¾X¦¸¦§µn¸£¸×ù„¾Ý Ï«ô}
§èûDù£ño­CIBM ùÇ¾¬ï£÷åûLüoù€ýœ®~­AÏ]æL¦k«T¯{üoù€®D IBM ýœ®~¦§øäÝ‘©Žî…­B ªê
©e¸Ò­B¸×¾“Ý¢û‹ýœ®~¦§ù„¾Ý¾DñiªOõ_õû¾çæL¯~­C Ýp¦Gñzû‹®D IBM ýœ®~¦§¸Òî…Ýü¾“Ý¢
¦§§Çøí­A«ÑüwÝV÷àýœ®~¦§ù¥·üøàªd÷á­C

ÝüÇ” IBM ¾¬ùàøÒÝV¦§¾“Ý¢üîðz­AôÔ¾N¦¡ IBM ¦§¾¬ÑÝàÏw­AùÇ¾iî…¸¢¾¬ù’¾ìµn¸£¦§ñ­
¦pÏUÝü¸ãšøÒ¸×§MÝ^­C

¾¯©¥ÏÏõtÝüÏ‚ñ`øàú~ª­øÒ¸ã¾×¦§÷ˆ©’Ï×ü›õi«dùã­CªøÏFïœù¥õûóÆ¦§¯­¸£­A üoù€«dùã¾]
ªAðàÏH­BÏ«¾q­B¬tæP¸Mýœ®~¦§ÝW§ë­Cüoù€ÝW§ë¾çŽíæˆ§c­A ðY¯P¾“Ý¢Ï«¾q¦§ÝW§ë¸MÝ¡õ}
ûpÝP­Aî¶Ží¾¸ÝX­C

æêõ@vñ¶v­G

¾¯©¥¾]õtð¸l¯yù¾¦§«dùã·ü¾×æ{Ý­­A¾×¾H¯­¸£ÝU§õ@ú~¾ð¾xÏW¦§æ{Ý­ü]ðpõèüN­Cñz¾i
¾Hø•¸¢ªÆæo­BùØ¾×­BóPøƒ¸×ïýõGýÝXõ@ú~¾ð¾x (¾×¸¢øäÝ‘¸ã¬ô¬g¦§«dùãæ{Ý­) Ïõ·ü¾×
æ{Ý­ü]ðpÏôðñ¦§·ü¾×æ{Ý­æ¾¾ ¦§­A¾H¾“Ý¢õ×Ý­«’¯s­Bðžõ‹Ï×ïýõGüoù€«dùãæ{Ý­­AÝàæL
¯í¾IôOæû IBM­CÝìüoù€«dùãªã¾¬÷gûLõûóÆ¦§ï£÷å­C Ý]Ýû­AIBM Ïœú|®OÇã¸×út¾šüoù€æ{
Ý­¦§Çð¸w¸Ò­B¦AøÔî…ÏO¸×¾\î…­C

üoù€«dùãæ{Ý­¸×ªO¾“Ý¢ðl¾Öæêõ@¦§ùCÏ@¾ö®çù¸¸×¾“Ý¢ü­¾ö­Aüœ¾ýôúùÆÝüÏUÝC¦§æêõ@v
µn¸£­G

(c) (your company name) (year). Portions of this code are derived from IBM
Corp. Sample Programs. (c) Copyright IBM Corp. _enter the year or years_.
All rights reserved.
  ------------------------------------------------------------------------

A.1 øà¬Ñ

ÏUÝCüN¯y (¾HªP÷û (*) ¬Ñ¾š) ªO IBM Ï«¾qÝbªøˆ­Bù„¾Ýøˆ©a¸×ùƒ¦Þ¦§øà¬Ñ­C
 ACF/VTAM                        IBM
 AISPO                           IMS
 AIX                             IMS/ESA
 AIX/6000                        LAN DistanceMVS
 AIXwindows                      MVS/ESA
 AnyNet                          MVS/XA
 APPN                            Net.Data
 AS/400                          OS/2
 BookManager                     OS/390
 CICS                            OS/400
 C Set++                         PowerPC
 C/370                           QBIC
 DATABASE 2                      QMF
 DataHub                         RACF
 DataJoiner                      RISC System/6000
 DataPropagator                  RS/6000
 DataRefresher                   S/370
 DB2                             SP
 DB2 Connect                     SQL/DS
 DB2 Extenders                   SQL/400
 DB2 OLAP Server                 System/370
 DB2 Universal Database          System/390
 Distributed Relational          SystemView
 Database Architecture           VisualAge
 DRDA                            VM/ESA
 eNetwork                        VSE/ESA
 Extended Services               VTAM
 FFST                            WebExplorer
 First Failure Support TechnologyWIN-OS/2

ÏUÝCüN¯yªOù„¾ÝÏ«¾q¦§øà¬Ñ¸×æ—¾Uøà¬Ñ­G

Microsoft­BWindows­BWindows NT ªOúLünÏ«¾q¦§øà¬Ñ¸×æ—¾Uøà¬Ñ­C

Java ¾HÏ×¸ãÝü¯P Java ÝüÇ”¦§øà¬Ñ¯P¬Ñüû­A¾HÏ× Solaris ªO Sun Microsystems,
Inc. Ýbªøˆ­Bù„¾Ýøˆ©a¸×ùƒ¦Þ¦§øà¬Ñ­C

Tivoli ¯P NetView ªO Tivoli Systems Inc. Ýbªøˆ­Bù„¾Ýøˆ©a¸×ùƒ¦Þ¦§øà¬Ñ­C

UNIX ªO X/Open Company Limited Ýbªøˆ­Bù„¾Ýøˆ©a¸×ùƒ¦Þ¦§æ—¾Uøà¬Ñ­Aôú÷g÷àÏ«¾q
ñ¶v¸l¾iùØ¾×­C

ù„¾ÝÏ«¾q­Býœ®~¸×¦AøÔÝW§ë (¾Hùƒµ–ªP÷û (**) ¬Ñ¾š) ¾iî…ªOù„¾ÝÏ«¾q¦§øà¬Ñ¸×¦AøÔ
¬Ñ¯x­C
  ------------------------------------------------------------------------

1    A new level is initiated each time a trigger, function, or stored
     procedure is invoked.

2    Unless the automatic commit is turned off, interfaces that
     automatically commit after each statement will return a null value
     when the function is invoked in separate statements.

3    This applies to both FOR EACH ROW and FOR EACH STATEMENT after insert
     triggers.

4    A Service Policy defines a set of quality of service options that
     should be applied to this messaging operation. These options include
     message priority and message persistence. See the MQSeries Application
     Messaging Interface manual for further details.

5    A character string with a subtype of BIT DATA is not allowed.

6    A common-table-expression may precede the fullselect

7    A common-table-expression may precede a fullselect.

8    There is no casting of the previous value to the source type prior to
     the computation.
