DB2 Universal Database Version 8.1.4 Release Notes (Version 8.1.4) Contents i) About the Release Notes What's New for Version 8.1.4 Application development enhancements DB2 family enhancements Manageability enhancements Performance enhancements Replication enhancements Known problems and workarounds (Version 8.1.4) Product and product-level support Alternate FixPaks on Linux and UNIX-based systems Back-level DB2 Universal Database server support Classic Connect unavailable Data Warehouse Center down-level server support restrictions DB2 license policy for DB2 Universal Database Workgroup Server Edition DB2 Universal Database Version 7 server access Data Warehouse Center not available in Simplified Chinese DB2 Web Tools Development Center APARs required for SQLJ and SQL Assist support on DB2 UDB for OS/390, Version 6 and DB2 UDB for z/OS, Version 7 Development Center limitations for 64-bit operating systems Development Center now supports Actual Cost information for SQL statements run on OS/390 or z/OS servers Development Center on the Linux operating system Federated systems restrictions High availability function is included in DB2 Universal Database Workgroup Server Edition IBM DB2 Development Add-In for Microsoft Visual Studio .NET Installation on AIX Installation on Linux License Center back-level versions not supported Microsoft Visual Studio, Visual C++ Microsoft XP fix needed on 64-bit operating systems MVS operating system not supported SNA support limitations in Version 8 Supported LDAP client and server configurations Tivoli Storage Manager for LinuxAMD64 Windows XP operating systems Application development Asynchronous execution of CLI CLI and ODBC on Windows 64-bit operating systems Configuration Assistant Unsupported bind options Configuration parameters NUM_LOG_SPAN configuration parameter on a multipartition database dasdrop limitation in multiple FixPak environments Data Warehouse Center ERwin 4.x metadata bridge Japanese names of remote objects Restrictions for the Clean Data transformer Using the warehouse agent for replication and accessing Client Connect warehouse sources Scheduling a warehouse process to run at intervals Replication Center restrictions on iSeries systems Restriction for import and export The Visual Warehouse 5.2 DB2 program "VW 5.2 Load flat file into DB2 UDB EEE (AIX only)" is not supported Limited support for CURSOR load DB2 Cube Views Cube Views sample application differs from sample source DB2 Data Links Manager Data Links server backup fails using Tivoli Storage Manager archive server (AIX, Solaris Operating Environment) DB2 Universal Database backup and restore Backup and restore on Linux 390 operating systems DB2 Universal Database replication Java Administrative API documentation for DB2 data replication Column mapping restrictions and the Replication Center Development Center Debugging Stored Procedures with double quotation marks SQLFLAG(STD) precompiler option error Documentation DB2 Replication Guide and Reference documentation DB2 Universal Database, Version 8 HTML documentation installation restriction (Windows) Documentation search may fail on AIX unless all documentation categories are installed Documentation search problem with Java 2 JRE1.4.0 Installation of the DB2 Information Center for languages that are not options during installation Official naming convention for DB2 Universal Database for Linux when used on host systems GUI tools Control Center plugin support Displaying Indic characters in the DB2 GUI tools GUI tools not supported for zSeries servers running Linux operating systems Load and Import Columns page does not support DBCS characters in IXF files Incorrect indicators given when a load operation fails Minimum display settings for GUI tools SQL1224N error when using the GUI tools on AIX Health Monitor Health Monitor off by default Health indicator restrictions Information Catalog Center Do not partition information catalog tables Log file not generated when importing tag language files Migrating DB2 Universal Database when using DataJoiner or replication Query Patroller Center Enhanced filtering abilities Secure Windows environments SQL Assist SQL Assist button disabled in the Command Center Two versions of SQL Assist are launched from DB2 System Monitor Event record size limitation Snapshot UDF restrictions Amount of Log to be Redone for Recovery monitor element undefined for V8.1.4 Throttled utility restrictions XML Extender XML Extender sample programs renamed Decomposing documents in XML Extender that contain non-unique attribute and element names Additional Information Change in Unicode server behavior Full message text is not returned when using SQLException.getMessage() IBM DB2 Universal JDBC driver Java functions and routines on Linux, UNIX, and Windows operating systems English Microsoft Data Access Components (MDAC) files are used for all national language versions of DB2 Universal Database, V8.1, unless translated MDAC files are installed first. The Simplified Chinese locale on AIX operating systems The Simplified Chinese locale on Red Hat, V8 operating systems Corrections to the documentation Administration Guide: Planning Application development: Call Level Interface (CLI) Data Links Manager Data Warehouse Center Information Catalog Center National languages Registry and environment variables XML Extender Online help corrections and updates Configuring the C environment for SQL stored procedures in the Development Center Enabling view docking when accessing Development Center with Hummingbird Exceed Microsoft Visual Studio .NET add-in information update in Development Center help Migrating DB2 XML Extender to Version 8.1.2 Path settings to enable Java routines to compile in the Development Center Runstats dialog - updated getting there information Specifying build options for a Java stored procedure in the Development Center Appendix. Notices Trademarks i) About the Release Notes Content The release notes contain the latest information for the following DB2(R), Version 8 products: DB2 Universal Database(TM) Personal Edition DB2 Universal Database Workgroup Server Edition DB2 Universal Database Workgroup Server Unlimited Edition DB2 Universal Database Enterprise Server Edition DB2 Personal Developer's Edition DB2 Universal Developer's Edition DB2 Warehouse Manager DB2 Warehouse Manager Sourcing Agent for z/OS(TM) DB2 Data Links Manager DB2 Net Search Extender DB2 Spatial Extender DB2 Intelligent Miner(TM) Scoring DB2 Intelligent Miner Modeling DB2 Intelligent Miner Visualization DB2 Connect(TM) Application Server Edition DB2 Connect Enterprise Edition DB2 Connect Personal Edition DB2 Connect Unlimited Edition DB2 Query Patroller Structure The release notes are divided into four parts: * The first part highlights what is new in this release. * The second part contains the details of the problems, limitations, and workarounds known at the time of publication that affect the products previously listed. Read these notes to become familiar with any known outstanding issues with this release of the DB2 family of products. * The third part contains corrections to previously released HTML, PDF, and printed documentation. * The fourth part contains corrections and updates to the information available in the product GUI tools help. The most up-to-date documentation is available in the latest version of the DB2 Information Center, which is accessed through a browser. The URL for downloading the latest documentation is provided in the Additional resources section below. Revision marks in the DB2 Information Center documentation indicate text that has been added or changed since the PDF information for version 8.1 was originally made available. A vertical bar (|) indicates information that was added at the time that version 8.1 was first released. A numeric indicator, such as a 1 or a 2, indicates that the information was added for the FixPak or level ending in the same number. For example, a 1 indicates that the information was added or changed in FixPak 1, a 2 indicates that the information was changed for Version 8.1.2. The Data Links Manager Administration Guide and Reference was updated in PDF form (book number SC27-1221-01) at the time of FixPak 1, and is available for download at the DB2 support site: http://www.ibm.com/software/data/db2/udb/winos2unix/support Additional resources Documentation for the DB2 Life Sciences Data Connect product is available for download from the IBM software site: http://www.ibm.com/software/data/db2/lifesciencesdataconnect/ If you want to view the DB2 documentation in HTML format, you can access the DB2 HTML Information Center online from http://publib.boulder.ibm.com/infocenter/db2help/. Alternatively, if you want to install the DB2 HTML Information Center on your system, a DB2 HTML Documentation CD-ROM image is available for download from the same site. Updates are made to the DB2 HTML documentation with every release. For the latest documentation, access the DB2 HTML Information Center online or download the DB2 HTML Documentation CD-ROM image for installation on your system. PDF documentation is updated less frequently. More information on the DB2 Development Center and DB2 for z/OS is available at http://www.ibm.com/software/data/db2/os390/spb/. For the latest information about the DB2 family of products, obtain a free subscription to DB2 Magazine. The online edition of the magazine is available at http://www.db2mag.com; instructions for requesting a subscription are also posted on this site. What's New for Version 8.1.4 This section provides a brief summary of the enhancements available with DB2 Universal Database Version 8.1.4. Detailed information on these new features can be found in the DB2 Information Center under Release information for Version 8.1.4. If you do not have Version 8.1.4 installed, you can access this information at http://publib.boulder.ibm.com/infocenter/db2help/. Application development enhancements KEEPDYNAMIC support for DB2 CLI/ODBC applications DB2 CLI/ODBC applications on the client can now take advantage of the KEEPDYNAMIC feature on servers that are DB2 UDB for z/OS and OS/390 Version 7 and later. DB2 CLI dynamic scrollable cursor support Dynamic scrollable cursors are now supported in DB2 CLI when accessing servers which are DB2 UDB for z/OS Version 8.1 and later. CLI LOAD fullselect support The CLI LOAD utility has been enhanced to support a fullselect on the INSERT statement. This feature allows you to load data from a table and execute the INSERT statement once instead of multiple times, as may be required when the VALUES clause is used. CLI/ODBC configuration keyword RETURNOLEDBCHARASWCHAR The IBM DB2 OLE DB Provider describes CHAR, VARCHAR, LONG VARCHAR, and CLOB data as DBTYPE_WSTR by default as of DB2 UDB Version 8.1.2. The CLI/ODBC configuration keyword OLEDBRETURNCHARASWCHAR allows you to change this default to have the previously stated character data types reported as DBTYPE_STR. Result set retrieval from SQL data-change operations In DB2 Version 8.1.4, you can use SELECT and SELECT INTO statements to retrieve result sets from SQL data-change operations (INSERT, UPDATE, and DELETE) embedded in the FROM clause. Searched INSERT, UPDATE, DELETE, and MERGE statements against fullselects As of DB2 Version 8.1.4 you can issue searched INSERT, UPDATE, DELETE, and MERGE statements on the results of fullselects. Support of SQL statements that modify SQL data within SQL Table Functions DB2 now supports the use of SQL statements that modify data within the body of SQL table functions. EXECUTE privilege on routine is required to invoke a routine As of DB2 Version 8.1 routine level EXECUTE authorization exists to ensure safe and manageable use of routines. The following authorizations are required so that a user can successfully invoke a routine (method, stored procedure, or user defined function). The EXECUTE authority on all routines migrated to DB2 version 8.1 from earlier releases has been GRANTED TO PUBLIC. Database administrators can manage the EXECUTE privileges on these routines with the GRANT and REVOKE commands. Any user that will be an invoker of the routine must have at least one of the following: * EXECUTE privilege on the routine * SYSADM or DBADM authority The definer of a routine (the user who issues the CREATE statement to register the routine) must have at least one of the following: * EXECUTE privilege on the routine * SYSADM or DBADM authority Any user with EXECUTE WITH GRANT OPTION privilege on the routine (this includes the routine definer unless the privilege has been explicitly revoked), SYSADM or DBADM authority must explicitly GRANT EXECUTE on a routine to PUBLIC or to the authorization IDs of users that will be invokers of the routine. Caution should be taken when granting EXECUTE privilege on a routine to PUBLIC as this allows any database user to invoke the routine. The owner of the package or packages associated with the routine, or any user with SYSADM or DBADM authority must GRANT EXECUTE on the packages to the routine definer. The package owner is the user who executes the BIND command to bind a routine package to the database (or the user specified in the OWNER precompile/bind option if it was overridden). The package owner, upon completion of a BIND, has EXECUTE WITH GRANT authority on the bound package. When a routine is invoked the authorization to run the routine is checked against the definers', and not the invokers', authorization to EXECUTE the packages associated with the routine. Thus, the definers' role is to encapsulate under one authorization ID the privileges of running the packages associated with a routine and to be a user capable of granting EXECUTE privileges to users that need to invoke the routine. To determine which users will be invokers of a routine, it is necessary to consider how a routine can be invoked. Routines can be invoked from a command window or can be embedded within an application program. In the case of methods and UDFs the routine reference will be embedded in another SQL statement whereas a procedure is invoked by using the CALL statement. For dynamic SQL in an application, the invoker is the runtime authorization ID of the immediately higher-level routine or application containing the routine invocation (however, this ID can also depend on the DYNAMICRULES option, with which the higher level routine/application was bound). For static SQL, the invoker is the value of the OWNER precompile/bind option of the package that contains the reference to the routine. These users will require EXECUTE authority on the routine. If a user attempts to invoke a routine that the user is not authorized to EXECUTE, an error (SQLSTATE 42501) is returned. This error is also returned when the definer of the routine is missing EXECUTE privilege on a package associated with the routine. Note: For SQL routines the routine definer is also implicitly the package owner. Therefore the definer will have EXECUTE WITH GRANT OPTION on the routine and on the routine package. External routines migrated to DB2 Version 8.1 Prior to DB2 Version 8.1, the privilege to invoke a routine by a user was managed by granting and revoking EXECUTE privileges on the packages associated with the routine. Upon database migration the following actions are taken: * GRANT EXECUTE WITH GRANT OPTION to the routine DEFINER of all existing routines * GRANT EXECUTE to PUBLIC for all existing functions, methods, and external stored procedures * For each SQL procedure, GRANT EXECUTE to all users who previously had EXECUTE privilege on the routine package These actions ensure that all users that were previously able to invoke a routine continue to be able to do so. Database administrators can REVOKE the EXECUTE privilege of routines from specific database users if they now wish to restrict the use of the routine. The db2undgp command, can be used by database administrators to both identify external stored procedures that access SQL and revoke from all database users the EXECUTE privilege on these procedures. This is useful for reverting all external stored procedures that access SQL data to a state where no one can execute them. The DBADM or SYSADM can then choose to GRANT EXECUTE on each routine to the particular users that are intended to invoke the procedure. DB2 family enhancements Data Links Manager online help and error message functionality This release enhances existing and adds new online help functions for the Data Links File Manager (DLFM) component of Data Links Manager. XML Extender environment variable DB2DXX_MIN_TMPFILE_SIZE DB2 XML Extender may place large documents in temporary files to avoid using too much memory during processing. The environment variable DB2DXX_MIN_TMPFILE_SIZE instructs XML Extender to use memory buffers, rather than temporary files, for processing documents smaller than the specified value. Control Center for DB2 Universal Database for z/OS and OS/390 enhancements The Control Center now supports the following features of DB2 Universal Database for z/OS and OS/390 Version 8.1: * support of long names in the DB2 catalog * an increase of the maximum number of partitions for table spaces from 254 to 4096 * 64-bit virtual addressing support Manageability enhancements Resource management (db2nodes.cfg) A new column has been added to the db2nodes.cfg file. The resourcename column is for multiple logical node (MLN) configurations and can give each node its own set of resources. Referential integrity The data definition language restrictions on referential constraints have been lifted (some restrictions still apply), such that it is now possible to have multiple referential constraints with different referential integrity actions on the same table in a delete-connected relationship. Row migration UNION ALL views DB2 UDB now offers complete transparency when you update rows through a UNION ALL view. In addition to supporting update, delete, or insert operations, DB2 can now move rows (during update operations) between the branches of a UNION ALL view. Online import The import utility now supports two locking modes: offline mode (ALLOW NO ACCESS) and online mode (ALLOW WRITE ACCESS). Offline mode is the default. Previous to Version 8.1.4, offline mode was the only import behavior available. sqluimpr API replaced by db2Import API The sqluimpr API has been replaced by db2Import API. The sqluimpr API is still supported, but new applications should call the db2Import API. Compressed backup Database backups can now be compressed to conserve disk space. Backup compression has been added as an option to the BACKUP DATABASE command and the db2Backup API. Support for the restoring of compressed backups has been added to the RESTORE DATABASE command and the db2Restore API. Setting buffer pool memory allocation size You can set the size for buffer pool memory allocations using the DB2_ALLOCATION_SIZE registry variable. Setting this variable to a higher value means that it will require fewer allocations to reach the desired amount of memory that is allocated to a buffer pool. Performance enhancements Range-clustered tables Range-clustered tables provide fast, direct access to data. Asymmetric index splitting The CREATE INDEX statement now has new clauses to allow greater control of the space used when index pages are split after becoming full. Temporary tables in SMS Storage for temporary tables in SMS table spaces will not be deleted by default once they are no longer needed. In cases where temporary tables are used repeatedly, this new feature avoids some of the overhead of deleting and reserving storage for temporary tables. Page cleaning enhancements Starting in Version 8.1.4, there is an alternate method of configuring page cleaning in your system. This alternate method differs from the default behavior in that page cleaners behave more proactively in choosing which dirty pages get written out at any given point in time. This new method of page cleaning differs from the default page cleaning method in two major ways: 1. Page cleaners do not respect the chngpgs_thresh configuration parameter. In this alternative method of page cleaning, page cleaners will no longer react in response to value of the chngpgs_thresh configuration parameter. Instead of attempting to keep some percentage of the buffer pool clean, the alternate method of page cleaning provides a mechanism whereby the agents are informed of the location of good victim pages that have just been written out, so that agents do not have to search the buffer pool to look for a victim. When the number of good victim pages drops below an acceptable value, the page cleaners are triggered, and proceed to search the entire buffer pool, writing out potential victim pages, and informing the agents of the location of these pages. 2. Page cleaners no longer respond to LSN gap triggers issued by the logger. When the amount of log space encompassing the log record which has updated the oldest page in the buffer pool and the current log position exceeds that allowed by the softmax parameter, it is said that the database is in an 'LSN gap' situation. Under the default method of page cleaning, when the logger detects than an LSN gap has occurred, it will trigger the page cleaners to write out all the pages which are contributing to the LSN gap situation. That is, it will write out those pages which are older than what is allowed by the softmax parameter. Page cleaners will be idle for some period of time while no LSN gap is occurring. Then, once an LSN gap occurs, the page cleaners are activated to write a large number of pages before going back to sleep. This can result in the saturation of the I/O subsystem, which then affects other agents which are reading or writing pages. The alternate method of page cleaning will modulate this behavior by spreading out the same number of writes over a greater period of time. The cleaners do this by proactively determining not only which pages are currently in an LSN gap, but also which pages will be in the LSN gap some period in the future based on the current level of activity. To use the new method of page cleaning, set the DB2_USE_ALTERNATE_PAGE_CLEANING registry variable to "ON". Monitoring network time New monitor elements for monitoring network time have been introduced. These elements are used to get a better idea of the database activity and network traffic at the database or application level. db2dlm_upd_hostname command In a Data Links Manager environment, the DB2 host name information is stored on the Data Links Manager server, and the Data Links Manager host name information is stored on the DB2 server in a configuration file. In order to update the DB2 or DLM host name, you can invoke the db2dlm_upd_hostname - Data Links Update Host Name command. Lock deferral To improve concurrency, DB2 now permits the deferral of row locks for CS or RS isolation scans in some situations until a record is known to satisfy the predicates of a query. Direct I/O support on AIX Currently Direct I/O is already supported on Windows via registry variable DB2NTNOCACHE. Now, limited Direct I/O support has been added to AIX. This new support is for all SMS containers except for long fields, LOB, and temporary table spaces. Replication enhancements Object name length Replication now supports schema and table names of up to 128 bytes on z/OS when DB2 UDB for z/OS Version 8 is run in new-function mode. Password file The asnpwd command allows you to list the aliases and user IDs contained in the password file. You can also use the encrypt parameter of the asnpwd command to encrypt either all of the entries in a file or just the password entry in a file. Data on Oracle sources The Apply program no longer needs to issue lock table statements for CCD tables on Oracle sources. To take advantage of this improvement, you must migrate any existing registrations and subscriptions for Oracle sources. Known problems and workarounds (Version 8.1.4) The following are the currently known limitations, problems, and workarounds for DB2(R) Universal Database Version 8.1.4. The information in this section applies only to the Version 8.1.4 release of DB2 Universal Database(TM), and its supporting products. Any limitations and restrictions might or might not apply to other releases of the product. Product and product-level support Alternate FixPaks on Linux and UNIX-based systems Prior to DB2 Universal Database Version 8, FixPaks only functioned as updates to installed DB2 Universal Database packages or filesets in one fixed location. Essentially, this meant that the installation of FixPaks would replace existing files with the updated ones provided within the FixPaks, and multiple DB2 FixPak levels on a single system was not a possibility. DB2 Universal Database Version 8.1 Enterprise Server Edition (ESE) with multiple FixPak levels can now coexist in the same system. This feature, supported in production operating environments since Version 8.1.2, is achieved using the following two FixPak types: regular FixPaks * Available not only for ESE, but for all supported DB2 V8.1 products for the related platforms * Can be installed directly on top of the existing installation either in /usr/opt/db2_08_01 on AIX(R) or /opt/IBM/db2/V8.1 on other platforms alternate FixPaks * Can be installed as a completely new copy of DB2 Universal Database ESE * Installed in a predefined location other than the location used for a regular DB2 Universal Database installation Notes: 1. You are not required to perform a multiple FixPak installation if you do not feel it is necessary for your environment. 2. Starting with IBM DB2 Universal Database Enterprise Server Edition (ESE) for Linux and UNIX(R), Version 8.1.2, FixPaks are supported in production operating environments when installed as Multiple FixPaks. To update a multiple FixPak instance to a different FixPak level, perform one of the following options: * Install the appropriate regular FixPak on the General Availability (GA) installation, and update the instance by running db2iupdt from the existing GA path. * Install the appropriate alternate FixPak to its own unique path, and update the instance by running db2iupdt from this path. For further information regarding downloading alternate FixPaks, visit the IBM(R) support site at http://www.ibm.com/software/data/db2/udb/winos2unix/support. Back-level DB2 Universal Database server support If you migrate your DB2 Universal Database client systems to version 8 before you have migrated all of your DB2 Universal Database servers to version 8, several restrictions and limitations apply. For version 8 clients to work with version 7 servers, you need to configure and enable the use of DRDA(R) application server capability on the version 7 server. For information on how to do this, refer to the version 7 Installation and Configuration Supplement. You cannot access a DB2 Connect(TM) Version 7 server from a DB2 Universal Database Version 8 client. When accessing version 7 servers from version 8 clients, there is no support available for: * The following data types: * Large object (LOB) data types * User-defined distinct types * DATALINK data types The DATALINK data type allows you to manage external data found in nonrelational storage. The DATALINK data type references files that physically reside on file systems external to DB2 Universal Database. * The following security capabilities: * Authentication type SERVER_ENCRYPT SERVER_ENCRYPT is a method to encrypt a password. The encrypted password is used with the user ID to authenticate the user. * Changing passwords You are not able to change passwords on the version 7 server from a version 8 client. * The following connections and communication protocols: * Instance requests that require an ATTACH instead of a connection ATTACH is not supported from a version 8 client to a version 7 server. * Network protocols other than TCP/IP. (SNA, NetBIOS, IPX/SPX, and others) * The following application features and tasks: * The DESCRIBE INPUT statement for all applications except ODBC/JDBC To support version 8 clients running ODBC/JDBC applications that access version 7 servers, apply a fix for DESCRIBE INPUT support to all version 7 servers where this type of access is required. This fix is associated with APAR IY30655. Use the "Contacting IBM" information in any DB2 Universal Database documentation set (PDF or HTML) to find out how to get the fix associated with APAR IY30655. The DESCRIBE INPUT statement is a performance and usability enhancement that allows an application requestor to obtain a description of input parameter markers in a prepared statement. For a CALL statement, this includes the parameter markers associated with the IN and INOUT parameters for the stored procedure. * Two-phase commit A version 7 server cannot be used as a transaction manager database when using coordinated transactions that involve version 8 clients, nor can a version 7 server participate in a coordinated transaction where a version 8 server may be the transaction manager database. * XA-compliant transaction managers An application using a version 8 client cannot use a version 7 server as an XA resource. This includes WebSphere(R), Microsoft(R) COM+/MTS, BEA WebLogic, and others that are part of a transaction management arrangement. * Monitoring * Utilities that can be initiated by a client to a server * SQL statements greater than 32 KB in size There are similar limitations and restrictions for version 8 tools working with version 7 servers. The following version 8 GUI tools, products, and Centers support only version 8 servers: * Control Center * Development Center * Health Center (including the Web version of this center) * Indoubt Transaction Manager * Information Catalog Center (including the Web version of this center) * Journal * License Center * Satellite Administration Center * Spatial Extender * Task Center * Tools Settings The following version 8 tools support version 7 servers (with some restrictions): * Command Center (including the Web version of this center) * Saving, importing, and scheduling of scripts are not supported by the Command Center. * Data Warehouse Center * Replication Center * The import/export configuration file function of the Configuration Assistant * SQL Assist * Visual Explain In general, any version 8 tool that is only launched from within the navigation tree of the Control Center, or any details view based on such a tool, will not be available or accessible to version 7 and earlier servers. You should consider using the version 7 tools when working with version 7 or earlier servers. Classic Connect unavailable The Classic Connect product is not available. Although you may find references to the Classic Connect product in the Data Warehouse documentation and elsewhere, these should be ignored, as they are no longer applicable. Data Warehouse Center down-level server support restrictions The following limitations exist for down-level server support for DB2 Universal Database (DB2 UDB) Enterprise Server Edition Version 8 Data Warehouse Center: Large Object (LOB) support * If you are using a warehouse control database on a server that is earlier than DB2 UDB Enterprise Server Edition Version 8 you will not be able to work with LOBs. You must upgrade the warehouse control database to the correct level, or move the control database to the system on which the DB2 UDB Enterprise Server Edition Version 8 warehouse server is installed and use it locally from that system. * To move LOBs between the Data Warehouse Center and DB2, you must upgrade to DB2 UDB Enterprise Server Edition Version 8. Sytems Network Architecture (SNA) support If you use SNA to connect to your warehouse sources and targets, you must change the configuration to be TCP/IP over SNA, or use the Windows NT(R) warehouse agent. Support for EXPORT and LOAD utilities When you upgrade your warehouse agent, you must also upgrade your source target databases, or replace the EXPORT and LOAD utilities in your warehouse processes with SQL Select and Insert steps. SQL Select and Insert steps use a DELETE* command followed by SELECT and INSERT commands. SQL Select and Insert steps require the database to log all transactions. As a result, the performance for SQL Select and Insert steps is not as efficient as it is for EXPORT and LOAD utilities. DB2 license policy for DB2 Universal Database Workgroup Server Edition Although the DB2 Quick Beginnings for Servers book and the online tools help for the License Center indicate otherwise, the Internet license policy is not valid for DB2 Universal Database Workgroup Server Edition. If you require a license for Internet users, you need to purchase DB2 Universal Database Workgroup Server Unlimited Edition. DB2 Universal Database Version 7 server access To access a DB2 Universal Database Version 7 server on a Linux, UNIX, or Windows(R) operating system from a version 8 client, you must have version 7 FixPak 8 or later installed on your server and have run the db2updv7 command. For instructions on installing the version 7 FixPaks, refer to the version 7 FixPak Readme and Release Notes. You cannot access a DB2 Connect Version 7 server from a DB2 Universal Database Version 8 client. Data Warehouse Center not available in Simplified Chinese The Data Warehouse Center is not available in Simplified Chinese. Therefore, the following dependent DB2 components are also unavailable in this environment: * The DB2 Warehouse Manager. * The DB2 Warehouse Manager Connector for the Web and the DB2 Warehouse Manager Connector for SAP, which are dependent on the installation of the DB2 Warehouse Manager. * The Information Catalog Center, which is dependent on the Manage Information Catalog wizard component of DB2 Warehouse Manager. DB2 Web Tools The application servers supported by DB2 Web Tools for the following languages are required to be compliant with the Servlet 2.3 specification: * Japanese * Korean * Simplified Chinese * Traditional Chinese * Russian * Polish Development Center APARs required for SQLJ and SQL Assist support on DB2 UDB for OS/390, Version 6 and DB2 UDB for z/OS, Version 7 When using the Development Center on an Application Development client for DB2 Universal Database Version 8 on Windows or UNIX operating systems, the following APARs need to be installed on the server to enable SQLJ and SQL Assist support: DB2 UDB for z/OS, Version 7 * PQ65125 - Provides SQLJ support for building Java SQLJ stored procedures * PQ62695 - Provides SQL Assist support DB2 UDB for OS/390(R), Version 6 * PQ62695 - Provides SQL Assist support Development Center limitations for 64-bit operating systems Debugging of Java stored procedures against a 64-bit server is not supported by the Development Center. Debugging SQL stored procedures is supported on 64-bit Windows operating systems. OLE DB and XML are not supported on 64-bit servers. Development Center now supports Actual Cost information for SQL statements run on OS/390 or z/OS servers The DB2 Development Center now provides Actual Cost information for SQL statements run on DB2 Universal Database for OS/390 and z/OS, Version 6 and Version 7.. The following Actual Cost information is provided: * CPU time * CPU time in external format * CPU time as an integer in hundredths of a second * Latch/lock contention wait time in external format * Number of getpages in integer format * Number of read i/o in integer format * Number of write i/o in integer format This functionality also allows you to view multiple sets of Actual Cost results for a single SQL statement with different host variable values. Actual Cost information is available in the Development Center from the Create SQL Stored Procedure and Create Java Stored Procedure wizards, within the SQL Statement window for OS/390 and z/OS connections. To use the Actual Cost functionality, click the Actual Cost button in the OS/390 and z/OS connection window in either of the Stored Procedure wizards. To use Actual Cost functionality, you must have the Stored Procedure Monitor Program (DSNWSPM ) installed on your DB2 OS/390 server . Development Center on the Linux operating system You cannot use the Development Center to debug Java(TM) stored procedures running on any of the Linux distributions (32-bit, 64-bit, Intel, zSeries, or iSeries). Federated systems restrictions For users of DB2 Universal Database for Linux, UNIX, and Windows Version 7.2 federated databases To create nicknames for tables and views in DB2 Universal Database (DB2 UDB) for UNIX and Windows, Version 8, you need to apply DB2 UDB for UNIX and Windows Version 7.2 FixPak 8 on your DB2 UDB for UNIX and Windows Version 7.2 federated database. If you do not apply FixPak 8 on your DB2 UDB for UNIX and Windows Version 7.2 federated database, an error will occur when you access the nicknames. LONG VARCHAR and LONG VARGRAPHIC support The federated documentation indicates that the LONG VARCHAR and LONG VARGRAPHIC data types used by the DB2 family of products are unsupported. This is not entirely accurate. You can create nicknames for DB2 Universal Database for Linux, UNIX, and Windows data source objects that contain LONG VARCHAR and LONG VARGRAPHIC data type columns. These remote columns will be mapped to DB2 Universal Database for Linux, UNIX, and Windows LOB data types. For the other DB2 family of products, you can create a view that omits or recasts these data types and then create a nickname for the view. WITH HOLD cursors You can use the WITH HOLD semantics on a cursor that is defined on a nickname or in a PASSTHRU session. However, you will receive an error if you try to use the semantics (with a COMMIT) and the data source does not support the WITH HOLD semantics. Data sources Previously unsupported data sources are supported as of Version 8.1.2 using DB2 Information Integrator relational and nonrelational wrappers. For a full list of supported data sources, see the DB2 Information Center for DB2 Information Integrator: Product Overview -> Federated systems - overview -> Data sources -> Supported data sources Support for DB2 Universal Database Server for VM and VSE Federated support for DB2 Universal Database Server for VM and VSE has been added in Version 8.1.2. Product support Previously unsupported products are now supported through Information Integrator: * DB2 Relational Connect is supported using DB2 Information Integrator relational wrappers. * DB2 Life Sciences Data Connect is supported using DB2 Information Integrator non relational wrappers. Unsupported operating systems Federated systems are not supported on the Windows ME operating system. Setting up the federated server to access data sources The COMPACT installation option does not install the necessary access to the DB2 family or Informix(TM) data sources. You must use the TYPICAL or CUSTOM installation to access the DB2 family data sources. The CUSTOM installation option is the only option you can use to install access to both the DB2 family and the Informix data sources. Update federated database in order to create wrapper If you are using a federated database with DB2 Universal Database (DB2 UDB) Version 8.1.2 or later that was created using DB2 UDB Version 8.1 or DB2 UDB Version 8.1 FixPak 1, you must update your federated database using the db2updv8 command. Syntax: >>-db2updv8--d--database-name--+--------------------------+---->< '--u--userid---p--password-' If you do not update your database to Version 8.1.2, you will get one of the following error messages when you try to create a wrapper from the Federated Database Objects folder in the Control Center: * java.lang.NullPointerException * [IBM][CLI Driver][DB2/NT] SQL0444N Routine "GET_WRAP_CFG_C" (specific name "SQL030325095829810") is implemented with code in library or path "\GET_WRAP_CFG_C", function "GET_WRAP_CFG_C" which cannot be accessed. Reason code: "4". SQLSTATE=42724 Cataloging DB2 family data sources in the federated system database directory When the name of the remote database is more than 8 characters, it is necessary to create a database connection services (DCS) directory entry. An example of cataloging an entry in the DCS directory for the database using the CATALOG DCS DATABASE command is: CATALOG DCS DATABASE SALES400 AS SALES_DB2DB400 where: SALES400 Is the name of the remote database you entered in the CATALOG DATABASE command. AS SALES_DB2DB400 Is the name of the target host database that you want to catalog. High availability function is included in DB2 Universal Database Workgroup Server Edition Though it is not mentioned explicitly in the topic DB2 Workgroup Server Edition, the high availability function of the DB2 Universal Database Enterprise Server Edition that is referred to in the topic DB2 Enterprise Server Edition is included in the DB2 Universal Database Workgroup Server Edition. IBM DB2 Development Add-In for Microsoft Visual Studio .NET The IBM DB2 Development Add-In for Microsoft Visual Studio .NET does not support the following: * DB2 Universal Database for z/OS and OS/390, Version 8 * DB2 Universal Database for iSeries, Version 8 Installation on AIX If the db2setup program is run from a directory whose path includes a blank, the setup will fail with the following error: : not found Place the installable image in a directory whose path does not include spaces. Installation on Linux When you install version 8.1 of DB2 Universal Database on Linux, the RPM-based installation attempts to install the IBM Java RPM (IBMJava2-SDK-1.3.1.-2.0.i386.rpm). If a later level of the RPM (such as IBMJava2-SDK-1.4.0.-2.0.i386.rpm) already exists, he back-level RPM is not installed. However, in this case, the installation leaves the JDK_PATH database configuration parameter pointing to the Java 1.3 path, /opt/IBMJava2-14/. As a result, none of the Java-dependant functionality, including the installation of the DB2 Tools Catalog, will work. To solve this problem, run the following command as the instance owner: db2 update dbm cfg using JDK_PATH /opt/IBMJava2-14 This will point DB2 Universal Database to the correct IBM Developer Kit. License Center back-level versions not supported If a version 7 License Center attempts a connection to a version 8 server, the License Center receives an "SQL1650 - Function not supported" error message indicating that the connection is not supported. Microsoft Visual Studio, Visual C++ Despite being mentioned in the DB2 Development Center online help as a possible solution for the Build not successful: -1 error, Microsoft Visual Studio Visual C++ Version 5.0 is not supported for the development of SQL stored procedures. However, Microsoft Visual Studio Visual C++ Version 6.0 is supported. Additional configuration information is available in the IBM DB2 Application Development Guide: Building and Running Applications. Microsoft XP fix needed on 64-bit operating systems If you are using the Microsoft XP operating system (2600) configured to use the NETBIOS protocol with the DB2 family of products, you need to obtain a hotfix from Microsoft. Contact Microsoft with the Knowledge Base article number Q317437. MVS operating system not supported Despite being mentioned in the documentation, the MVS(TM) operating system is no longer supported by DB2 Universal Database. MVS has been replaced with z/OS. SNA support limitations in Version 8 The following support has been withdrawn from DB2 Universal Database Enterprise Server Edition (ESE) for Windows and UNIX-based operating systems, Version 8, and from DB2 Connect Enterprise Edition (CEE) for Windows and UNIX-based operating systems, Version 8: * Multisite update (two-phase commit) capability using SNA cannot be used. Applications that require multisite update (two-phase commit) must use TCP/IP connectivity. Multisite update (two-phase commit) using TCP/IP to a host or iSeries(TM) database server has been available for several releases. Host or iSeries applications that require multisite update (two-phase commit) support can use the new capability of TCP/IP multisite update (two-phase commit) support within DB2 Universal Database ESE, Version 8. * DB2 Universal Database ESE or DB2 CEE servers no longer accept client connections using SNA. As of version 8, FixPak 1, DB2 Universal Database allows the 32-bit version of AIX, Solaris(TM) Operating Environment, HP-UX, and Windows-based applications to access host- or iSeries-based database servers using SNA. This support will allow applications access to host or iSeries database servers using SNA, but using only one-phase commit. * Sysplex support with DB2 Universal Database for z/OS(TM) is only available using TCP/IP. Sysplex support is not provided using SNA connectivity. * Change password support is no longer available using SNA connectivity to host database servers. * All SNA support will be withdrawn in the next version of DB2 Universal Database and DB2 Connect. Supported LDAP client and server configurations The following table summarizes the supported LDAP client and server configurations: Table 1. Supported LDAP client and server configurations +------------------+----------------+----------------+----------------+ | | IBM SecureWay | Microsoft | Netscape LDAP | | | Directory | Active | server | | | | Directory | | +------------------+----------------+----------------+----------------+ | IBM LDAP client | Supported | Supported | Supported | +------------------+----------------+----------------+----------------+ | Microsoft | Supported | Supported | Supported | | LDAP/ADSI client | | | | +------------------+----------------+----------------+----------------+ IBM SecureWay Directory Version 3.1 is an LDAP Version 3 server available for Windows NT, Windows 2000, and Windows 2003, AIX, and Solaris. SecureWay Directory is shipped as part of the base operating system on AIX and iSeries (AS/400), and with OS/390 Security Server. DB2 supports IBM LDAP client on AIX, Solaris, Windows 98, Windows XP, Windows NT, Windows 2000, and Windows 2003. DB2 supports IBM LDAP Version 3.2.2 on Linux IA32 and Linux/390. Microsoft Active Directory is an LDAP Version 3 server and is available as part of the Windows 2000 Server operating system. The Microsoft LDAP client is included with the Windows operating system. When running on Windows operating systems, DB2 supports using either the IBM LDAP client or the Microsoft LDAP client to access the IBM SecureWay Directory Server. To explicitly select the IBM LDAP client, use the db2set command to set the DB2LDAP_CLIENT_PROVIDER registry variable to the value IBM. Tivoli Storage Manager for LinuxAMD64 Tivoli Storage Manager support is now available for Linux on AMD Opteron - 64-bit systems. The minimum required level of TSM client API is TSM 5.2.0. Windows XP operating systems The Windows XP Professional operating system is only supported by Personal Edition and Workgroup Server Edition products. The Windows XP Home Edition operating system is only supported by Personal Edition products. Application development Asynchronous execution of CLI Asynchronous execution with CLI is not available. CLI and ODBC on Windows 64-bit operating systems You cannot use an application with mixed ODBC and DB2 CLI on a Windows 64-bit operating system. Configuration Assistant Unsupported bind options The Configuration Assistant does not support the following bind options: * CALL RESOLUTION * CLIPKG * CNULREQD * DBPROTOCOL * ENCODING * MESSAGES * OPTHINT * OS400NAMING * GENERIC * IMMEDIATE * KEEP DYNAMIC * PATH * SORTSEQ * TRANSFORM_GROUP * VALIDATE * VARS Configuration parameters NUM_LOG_SPAN configuration parameter on a multipartition database The NUM_LOG_SPAN specifies the maximum number of log files that a transaction can span. If at any time a transaction violates the NUM_LOG_SPAN setting, it is rolled back, and forces the application that caused the transaction off the database. However, in a multipartition system, the db2loggr process can only force an application if the coordinating node for the application and the node of the db2loggr process that detects the error are both the same. For example, you have a system with three nodes (0,1 and 2) and have set the NUM_LOG_SPAN parameter to 2 on all nodes. An application connects to node 2 of the database, and begins a long-running transaction, which spans more than two log files. If the db2loggr process on node 1 is the first to detect this error, then nothing will happen. However, if the violation also occurs on node 2, then the db2loggr process will notice the error, the transaction will be rolled back, and the application will be forced off. dasdrop limitation in multiple FixPak environments Alternate FixPaks install their own version of the dasdrop command. On AIX, it is installed in the /usr/opt/db2_08_FPn/ path. On other UNIX systems, it is installed in the /opt/IBM/db2/V8.FPn/ path. In both cases, n is the number of the FixPak. In a multiple FixPak Environment, you can only have one DAS set up at any one time. You can create the DAS against version 8.1 of the product, or against any of the alternate FixPaks. To drop a DAS that was created against version 8.1 of the product, you can use any version of dasdrop to drop it. However, to drop a DAS that was created against an alternate FixPak, you must use an alternate FixPak version of dasdrop. For example, consider the following scenario on the AIX operating system: * You install DB2 Universal Database, Version 8.1. * You install alternate FixPak 1. * You create a DAS using the version 8.1 code, with the following command: /usr/opt/db2_08_01/instance/dascrt dasusr1 * You want to drop the DAS. You can drop this DAS by using either of the following commands: /usr/opt/db2_08_01/instance/dasdrop /usr/opt/db2_08_FP1/instance/dasdrop Both will work properly. However, in this example: * You install DB2 Universal Database, Version 8.1. * You install the alternate FixPak 1. * You create a DAS using the alternate FixPak 1 code, with the following command: /usr/opt/db2_08_FP1/instance/dascrt dasusr1 * You want to drop this DAS. You must use the alternate FixPak 1 dasdrop command: /usr/opt/db2_08_FP1/instance/dasdrop Trying to use the version 8.1 dasdrop command will cause an error. This limitation only applies to version 8.1 of the product, and not to any of the regular FixPaks. For example: * You install DB2 Universal Database, Version 8.1. * You apply regular FixPak 1, which corrects the problem with the version 8.1 dasdrop. * You install the alternate FixPak 1. * You create a DAS using the alternate FixPak 1 code, with the following command: /usr/opt/db2_08_FP1/instance/dascrt dasusr1 * You want to drop this DAS. You can drop this DAS by using either of the following commands: /usr/opt/db2_08_01/instance/dasdrop /usr/opt/db2_08_FP1/instance/dasdrop Both will work properly because the version of dasdrop in the /usr/opt/db2_08_01/ path was corrected when you applied the regular FixPak. Data Warehouse Center ERwin 4.x metadata bridge ERwin 4.0 metadata cannot be imported on the Linux operating system. The ERwin 4.x bridge is supported on Windows 98 and WinME with the following restrictions: * The db2erwinimport command can only be run from the db2 command line processor. * You must fully qualify the XML and trace file names for the -x and -t parameters. Japanese names of remote objects Schema, table, and column names of remote sources in Japanese cannot contain certain characters. Unicode mapping differences may cause the names to be null. See http://www.ingrid.org/java/i18n/encoding/ja-conv.html for more information. Restrictions for the Clean Data transformer Linking restrictions You cannot link any OS/390 data resources such as tables or views with a new Clean Data step. You can still link OS/390 data resources with the deprecated programs Clean Data step. Parameter restrictions For the Find and Replace parameter: If your new Clean Data transformer rules table contains different data types for the Find and Replace columns, you must change the Target column data type in both the Target Table properties page and the Column Mapping page before you promote the transformer to test mode. For the Discretize parameter: If your new Clean Data rules table contains different data types for the Bounds and Replace columns, you must change the Target column data type in both the Target Table properties page and the Column Mapping page before you promote the transformer to test mode. iSeries platform restrictions On the iSeries platform, the new Clean Data transformer does not perform error processing. You can generate the All Matches match type only on the iSeries platform. Using the warehouse agent for replication and accessing Client Connect warehouse sources Using the warehouse agent for replication If the source, target, capture control, or apply control servers (databases) are remote to the client system, you must catalog the database with the same name, user ID, and password on both the client and the warehouse agent systems. After you catalog the source on the client and warehouse agent systems, verify that you can connect to the source, target, capture, and apply databases. If you cannot connect to the warehouse source, warehouse target, replication capture, or replication apply databases, verify that the environment variable DB2COMM on the remote system is set to TCP/IP, and that the port number matches the port number of the node that is cataloged on the client system. To verify the port number on the remote system, type the following command at a DB2 Universal Database command prompt: get dbm cfg | grep SVCENAME You specify the port number of the client system when you catalog the node. Accessing Client Connect warehouse sources using the warehouse agent When you access a warehouse source that was defined using Client Connect with a warehouse agent, the source must be cataloged with the same name, user ID, and password on both the client and warehouse agent systems. If you are using the ODBC version of the warehouse agent, you must also catalog the source as an ODBC source on both the warehouse agent and client sites. Otherwise, actions that require the warehouse agent to access the warehouse source will fail. Scheduling a warehouse process to run at intervals When scheduling a warehouse process to run at intervals, you must determine the longest time it takes to run all the production steps in the process and schedule the intervals accordingly. If a process exceeds the scheduled time interval, all subsequently scheduled occurrences of that process will not run and will not be rescheduled. Replication Center restrictions on iSeries systems Administrative tasks in IASPs When using the Replication Center, you cannot perform administrative tasks in IASPs on iSeries systems. Restrictions for replication steps that use iSeries control, source and target servers The iSeries control, source, and target servers are supported only on the DB2 Universal Database Enterprise Server Edition. For both default and remote agents, the iSeries servers must be cataloged on the local machine. For a remote agent, the iSeries servers must also be cataloged on the machine where the agent resides. If the source or the target servers are on an iSeries operating system, then you must specify the system name on the Database page of the Source or Target notebook. Restriction for import and export If a process with unlinked shortcuts is exported and then imported as a .tag file into another control database, the unlinked shortcut data will cause error DWC3142: was not found in the Data Warehouse Center control database. This error displays when the unlinked shortcut dirIDs are untranslated and they refer back to the original control database. The Visual Warehouse 5.2 DB2 program "VW 5.2 Load flat file into DB2 UDB EEE (AIX only)" is not supported The Visual Warehouse 5.2 DB2 EEE load step is not supported in DB2 Version 8. To load a delimited file into a partitioned table in version 8, perform the following steps: 1. Migrate the target database or table to DB2 Version 8 if it is not already at DB2 Version 8. One way to migrate the database is from the command line with the db2move command. 2. Open the Properties window of the Visual Warehouse 5.2 EEE load step, select the Parameters tab, and note the values for Column delimiter, String delimiter, and Decimal delimiter parameters. 3. Create a new process for the new load step or use the original process. If you plan to create a new process, add the source file and target table to the new process. Also add the new process to the appropriate warehouse security group. 4. Create a DB2 load step in the process that you are using. 5. Connect the source and target to the step. 6. Open the Properties window of the load step and select PARTITIONED in the Load mode field. If necessary, update the Column, Character strings, and Decimal point fields with the values used in the Column delimiter, String delimiter, and Decimal delimiter of the old step. 7. Click Advanced to start the Load wizard. From the Operation page, select Split and load data. 8. From the Type page, select Replace table data. 9. Accept the Load wizard's remaining default values. 10. The Summary page shows the final load command. Review the final load command and click Finish. 11. Close the Properties window. Limited support for CURSOR load The DB2 UDB Load step now allows a view or a table to be used as the source to the step, resulting in a LOAD FROM CURSOR. In order to map columns in the wizard for CURSOR load, the Map columns based on column positions found in the input file radio button must be selected. DB2 Cube Views Cube Views sample application differs from sample source DB2 Cube Views V8.1 provides a sample application called db2mdapiclient.exe that demonstrates some important functions of Cube Views. The source code for this application, db2mdapiclient.cpp, is included. In the initial release of DB2 Cube Views V8.1, the application was built using the source code. In version 8.1.4 the source code is unchanged, but the application has been modified. The source code is still valid but it does not exactly match the application. DB2 Data Links Manager Data Links server backup fails using Tivoli Storage Manager archive server (AIX, Solaris Operating Environment) Problem: When installing or migrating to DB2 Data Links Manager, Version 8.1, a Data Links File Manager (DLFM)-initiated backup of Data Links server data to a Tivoli(R) Storage Manager archive server fails. One of the following sets of error messages display, either on-screen or on the installation status report: DLFM129I: Automatic backup of DLFM_DB database has been triggered. Please wait for the backup to complete. DLFM901E: A system error occurred. Return code = "-2062". The current command cannot be processed. Refer to the db2diag.log file for additional information. -- or -- DLFM811E: The current DLFM database could not be backed up. SQL code = "-2062", Return code = "-2062" DLFM901E: A system error occurred. Return code = "-2062". The current command cannot be processed. Refer to the db2diag.log file for additional information. Cause: The DB2 Data Links Manager Installer program failed to set the variables required to use Tivoli Storage Manager as an archive (backup) server for a Data Links server. Tip: If you want to use Tivoli Storage Manager as an archive server, and you have not yet installed or migrated to DB2 Data Links Manager, Version 8.1, you can prevent this problem from occurring. First, do not use the "Tivoli Storage Manager" backup option from the Installer program. Then, manually configure the Data Links Manager Administrator's profile to include the appropriate Tivoli Storage Manager variables, as described in step 2 that follows. After you have completed both tasks, you can proceed with the installation or migration. Workaround: Perform the following tasks in the order listed. 1. Back up the DLFM database using this command: db2 backup where: * is the name of the DLFM database. By default, the database is called DLFM_DB. * is the directory path to the backup storage location of your choice. 2. Manually configure the Data Links Manager Administrator's profile to include the appropriate Tivoli Storage Manager variables. The manual configuration procedure and the required variables are described in the following documentation topics: * Using Tivoli Storage Manager as an archive server (AIX) * Using Tivoli Storage Manager as an archive server (Solaris Operating Environment) You can find these topics either online in the DB2 Information Center, or in the "System Management Options" chapter of the DB2 Data Links Manager Administration Guide and Reference. * If you are completing a new installation of DB2 Data Links Manager, Version 8.1, you are finished. * If you are migrating to DB2 Data Links Manager Version 8.1, rerun the Migration Utility program, db2dlmmg. DB2 Universal Database backup and restore Backup and restore on Linux 390 operating systems Backup and restore operations to and from multiple tape devices may not work if you are using the Linux 390 operating system. DB2 Universal Database replication Java Administrative API documentation for DB2 data replication If you are developing applications using the administrative functions available in DB2 DataPropagator, you can obtain documentation for the relevant administrative Java APIs by contacting IBM support. Column mapping restrictions and the Replication Center You cannot map an expression in a source table to a key column in a target table if the TARGET_KEY_CHG column of the IBMSNAP_SUBS_MEMBR table is "Y" for that target table. This means that when using the Replication Center to create a subscription-set member, you should not select the option Let the Apply program use before-image values to update target-key columns if a key column in the target table is mapped to an expression in the source table. Development Center Debugging Stored Procedures with double quotation marks The IBM DB2 Universal Database Development Center 8.1.4 and all previous releases does not support debugging for any stored procedure with double quotation marks (") in the stored procedure name, schema, or specific name. SQLFLAG(STD) precompiler option error Remove the SQLFLAG (STD) precompile option when using Development Center to create SQL stored procedure to run on DB2 for z/OS, Version 8. If the SQLFLAG(STD) precompile option is enabled it will cause the following error: Abend C6 occurred while running Precompile program DSNHPC Documentation DB2 Replication Guide and Reference documentation The solutions information at http://www.ibm.com/software/data/dbtools/datarepl.htm is no longer available. This information is referred to in the preface to the Replication Guide and Reference. DB2 Universal Database, Version 8 HTML documentation installation restriction (Windows) On Windows, do not install the DB2 Universal Database, Version 8 HTML documentation on a workstation or server where a DB2 Universal Database, Version 7 (or earlier) product is already installed. The installer detects the earlier version and removes the earlier product. A workaround does exist. If you need to install the DB2 Universal Database, Version 8 HTML documentation on a workstation where an earlier version of DB2 Universal Database is installed, you can manually copy the files and directories from the DB2 Universal Database, Version 8 HTML Documentation CD, rather than using the installer. The DB2 Information Center and full text search will work, but you will not be able to apply any HTML documentation FixPaks. Documentation search may fail on AIX unless all documentation categories are installed If you do not to install all of the categories of documentation on the DB2 HTML documentation CD, an attempt to search against "All topics" may fail with an InvalidParameterException reported in the Java console of your browser and no search results. To work around the documentation search problem do one of the following: * Narrow the scope of your search by selecting from the Search scope list box in the Search window. * Install all the documentation categories from the DB2 HTML documentation CD. Documentation search problem with Java 2 JRE1.4.0 If your browser uses Java 2 JRE V1.4.0 and your documentation is installed in a path that contains spaces (e.g., C:\Program Files\SQLLIB\doc\), the documentation search applet may fail with an InvalidParameterException reported in the Java console of your browser and no search results. This problems is fixed with JRE V1.4.1. To work around the documentation search problem, do one of the following: * Upgrade your browser's JRE version to 1.4.1, available at http://java.sun.com/j2se/1.4.1/download.html * Downgrade your browser's JRE version to 1.3.x, available at http://www.ibm.com/software/data/db2/udb/ad/v8/java/ Installation of the DB2 Information Center for languages that are not options during installation The DB2 Setup wizard can only install the DB2 HTML documentation for languages that it also installs with the DB2 product. As a result, the DB2 HTML documentation cannot be installed using the DB2 Setup wizard in the following languages: * Portuguese (restriction for UNIX only) * Danish, Finnish, Norwegian, Swedish (restriction for Linux only) * Dutch, Turkish (restriction for HP-UX, Solaris, Linux only) * Arabic (restriction for UNIX only) To install the DB2 Information Center for one of the languages listed previously: 1. Insert the DB2 HTML Documentation CD in your CD-ROM drive. 2. Copy the following directory to your computer: * /cdrom/program files/IBM/SQLLIB/doc/htmlcd/language where cdrom is where you have mounted the CD and language is the code for the language you want to use. It does not matter where you place the folder. You can also view the DB2 HTML documentation directly from the CD. For instructions on how to do so, see the "Viewing technical information online directly from the DB2 HTML Documentation CD" topic in the appendix of any DB2 Version 8 manual. Notes: 1. To view the documentation, you must use Microsoft Internet Explorer 5.0 or later, or Netscape 6.1 browsers or later. 2. As well, if you launch the documentation from your product, it will go to the documentation installed as part of your product install, and not to the documentation that you copied over manually. Official naming convention for DB2 Universal Database for Linux when used on host systems The official naming convention for DB2 Universal Database for Linux on host systems is DB2 on Linux for S/390(R) and zSeries(TM). S/390 refers to 32-bit and zSeries to 64-bit. In addition, it is important to note that the following terms are also obsolete: * 64-bit Linux/390 * Linux/SGI GUI tools Control Center plugin support The Control Center now supports custom folders. Custom folders can contain user-selected system or database objects. Creating Control Center plugins specifically for a custom folder is not supported, but plugins can be created for the object contained in custom folders. For more information about Control Center plugins, see the topic Introducing the plug-in architecture for the Control Center. Displaying Indic characters in the DB2 GUI tools If you have problems displaying Indic characters when using the DB2 GUI tools, you might not have the required fonts installed on your system. DB2 Universal Database has packaged the following IBM TrueType and OpenType proportional Indic language fonts for your use. You can find these fonts in the font directory on either of the following CDs: * IBM Developer Kit, Java Technology Edition, Version 1.3.1 for AIX operating systems on 64-bit systems * Java application development and Web administration tools supplement for DB2, Version 8.1 These fonts are to be used only in conjunction with DB2. You cannot engage in the general or unrestricted sale or distribution of these fonts: Table 2. Indic fonts packaged with DB2 Universal Database +-----------------------+----------------------+----------------------+ | Typeface | Weight | Font File Name | +-----------------------+----------------------+----------------------+ | Devanagari MT for IBM | Medium | devamt.ttf | +-----------------------+----------------------+----------------------+ | Devanagari MT for IBM | Bold | devamtb.ttf | +-----------------------+----------------------+----------------------+ | Tamil | Medium | TamilMT.ttf | +-----------------------+----------------------+----------------------+ | Tamil | Bold | TamilMTB.ttf | +-----------------------+----------------------+----------------------+ | Telugu | Medium | TeluguMT.ttf | +-----------------------+----------------------+----------------------+ | Telugu | Bold | TeleguMTB.ttf | +-----------------------+----------------------+----------------------+ Detailed instructions on how to install the fonts and modify the font.properties file can be found in the Internationalization section of the IBM development kit for Java documentation. In addition, the following Microsoft products also come with Indic fonts that can be used with our GUI tools: * Microsoft Windows 2000 operating system * Microsoft Windows XP operating system * Microsoft Publisher * Microsoft Office GUI tools not supported for zSeries servers running Linux operating systems With the exception of the DB2 Setup wizard, GUI tools will not work on zSeries servers running the Linux operating system. This limitation includes any items normally launched form the Install launchpad, such as the Quick Tour. If you want to use the GUI tools with one of these systems, install the administrative tools on a client system with a different system configuration, and use this client to connect to your zSeries server. Load and Import Columns page does not support DBCS characters in IXF files If you use the Load wizard or Import notebook to set up a load or import from an IXF input file containing DBCS characters, the Columns page will not correctly display the column names contained in the file. Incorrect indicators given when a load operation fails If a load fails, but only warnings were returned (not errors), then the task icon will still appear with a green checkmark in the Task Center. Be sure to double-check the success of any loads you carry out. Minimum display settings for GUI tools For the GUI tools such as the Control Center to work properly, you must have a screen resolution of at least 800 by 600 dpi, and be using a display palette of at least 32 colors. SQL1224N error when using the GUI tools on AIX If you are using the GUI tools on an AIX operating system, you may receive an SQL1224N error. This error is caused by a memory handling problem in DB2. The following workaround will help eliminate the error: Procedure To stop the SQL1224N error on AIX operating systems: 1. As the instance owner, run the following commands: export EXTSHM=ON db2set DB2ENVLIST=EXTSHM 2. Restart the instance with the following commands: db2stop db2start Once the instance restarts with the new environment variable settings, the SQL1224N errors should stop. Health Monitor Health Monitor off by default The default value for the database manager switch for the health monitor (HEALTH_MON) is OFF. Health indicator restrictions The health monitor is unable to execute actions for the db2.db2_op_status health indicator if the indicator enters the down state. This state can be caused, for example, when an instance that the indicator is monitoring becomes inactive because of an explicit stop request or an abnormal termination. If you want to have the instance restart automatically after any abnormal termination, you must configure the fault monitor to keep the instance highly available. Information Catalog Center Do not partition information catalog tables Tables that the Information Catalog Manager uses must be contained within a single database partition. Numerous methods are available to put the tables within a single partition. The following procedure is one approach that works. 1. Open a DB2 Command Line Processor and issue these commands: a. CREATE DATABASE PARTITION GROUP pgname ON DBPARTITIONNUM pnumber b. CREATE REGULAR TABLESPACE tsname IN DATABASE PARTITION GROUP pgname MANAGED BY SYSTEM USING ('cname') Click Start -> Programs -> IBM DB2 -> Set-up Tools -> Manage Information Catalog Wizard. On the Options page, specify the table space name in the Table space field. Log file not generated when importing tag language files If an Information Catalog Center log file is not generated when importing tag language files to the Information Catalog Center, perform the following troubleshooting steps: When running db2icmimport from a command line: * If output files were not generated (.xml, .out, .err, .log), then there is probably an error on the command line. Verify that the first five arguments, which are UserId, Password, Database, Catalog, and Tagfile, are correct. View the syntax by entering db2icmimport. If this does not solve the problem, modify db2icmimport to capture the output of db2javit by using the -g option to save the output to a file (for example, db2javit -j:com.ibm.db2.common.icm.tag.IcmImport -w: -i: -o:"-Xmx128m -Xms32m" -g:"d:\temp\myimport.trc" . . . ). * If a log file was not generated, it is usually a parsing error. Look at the .xml file and the .out file. If you can, insert a ":COMMIT.CHKPID(DEBUG)" command at the beginning of the tag language file. This command will generate debug report messages and check the .xml and .out files for parsing errors. * After parsing, errors should appear in the .log file. When the debug report is being generated, look at the .log file and the .out file for information. * Always check the .err file to see if there is a run-time error. When importing tag language files using the Information Catalog Center GUI: * When you import tag language files using the GUI interface, no .out or .err files are generated. * If a .log or .xml file is generated, try to debug by using those files. * If they are not generated or do not help, run the import process from a command line to get more information. Migrating DB2 Universal Database when using DataJoiner or replication If you want to migrate an instance of DataJoiner(R) or DB2 Universal Database for Linux, UNIX, and Windows on which you are running the Capture or Apply programs for DB2 Universal Database replication, you must prepare to migrate your replication environment before you migrate the DB2 Universal Database or DataJoiner instance. Detailed instructions for carrying out the required preparation are included in the migration documentation for DB2 DataPropagator(TM), Version 8. You can find migration documentation for DB2 DataPropagator, Version 8 at http://www.ibm.com/software/data/dpropr/replmigration.htm. Query Patroller Center Enhanced filtering abilities When you are using the Query Patroller Center to view the Managed Queries report and the Query Activity Over Time report, a significant number of rows might be displayed. A filter window can be used to display only the queries that meet the conditions based on the filtering criteria supplied for each report. For the Managed Queries report, you can filter on: * ID * Status * Submitter ID * Time Created * Time Completed * Query Class of the query For the Query Activity Over Time report, you can filter on: * Query ID * Submitter ID * Explain Run Notes: 1. For all Historical Analysis reports (such as Query Activity Over Time), you can also filter on completion time by using the time range fields that appear at the top of the Query Patroller Center when a historical object is selected. To open the Filter notebook from the Managed Queries folder: 1. Open the Query Patroller Center. 2. Expand the object tree under the Monitoring folder until you find the Managed Queries folder. 3. Right-click the Managed Queries folder and select Filter in the pop-up menu. The Filter notebook opens. To open the Filter notebook from the Queries folder: 1. Open the Query Patroller Center. 2. Expand the object tree under the Historical Analysis folder until you find the Queries folder. 3. Right-click the Queries folder and select Filter in the pop-up menu. The Filter notebook opens. The Filter notebook will also open automatically when a Managed Queries or Queries folder is selected, if both of the following conditions are met: * The number of objects in the folder exceeds the object count specified in the Filter notebook * The Filter notebook's Automatically display filter when object count is exceeded option is enabled Procedure: The procedure for filtering tables for historical analysis is described in DB2 Query Patroller Guide: Installation, Administration, and Usage manual. The following table shows the values expected for each column listed in the Filter dialog for Managed Queries: Table 3. Valid values for Filter dialog (Managed Queries) +----------------------------------+----------------------------------+ | Column | Value | +----------------------------------+----------------------------------+ | ID | Numeric value representing the | | | query ID | +----------------------------------+----------------------------------+ | Status | A single character representing | | | the status. Possible values are: | | | * H (for queries whose status | | | is Held ) | | | * Q (for queries whose status | | | is Queued) | | | * R (for queries whose status | | | is Running) | | | * A (for queries whose status | | | is Aborted) | | | * C (for queries whose status | | | is Cancelled) | | | * D (for queries whose status | | | is Done) | | | * U (for queries whose status | | | is Unknown) | +----------------------------------+----------------------------------+ | Submitter ID | A character string representing | | | the ID of the submitter | +----------------------------------+----------------------------------+ | Created | A timestamp representing the | | | time the query was created. For | | | Example: | | | 2003-07-29-00.00.00 | +----------------------------------+----------------------------------+ | Completed | A timestamp representing the | | | time the query was | | | completed. For Example: | | | 2003-07-29-00.00.00 | +----------------------------------+----------------------------------+ | Query Class | Numeric value representing the | | | ID of the query class used for | | | this query | +----------------------------------+----------------------------------+ The following table shows the values expected for each column listed in the Filter dialog for Historical Queries: Table 4. Valid values for Filter dialog (Historical Queries) +----------------------------------+----------------------------------+ | Column | Value | +----------------------------------+----------------------------------+ | ID | Numeric value representing the | | | query ID | +----------------------------------+----------------------------------+ | Submitter ID | A character string representing | | | the ID of the submitter | +----------------------------------+----------------------------------+ | Explain Run | A single character that | | | indicates whether the Historical | | | Analysis Data Generator has been | | | run on this query. Possible | | | values are: | | | * N (Historical Analysis Data | | | Generator has not yet run) | | | * S (Historical Analysis Data | | | Generator ran successfully) | | | * F (Historical Analysis Data | | | Generator ran unsuccessfully) | +----------------------------------+----------------------------------+ Secure Windows environments You may experience file permission problems if you are using DB2 Universal Database on Windows and are not an administrator on the Windows system. If you receive an SQL1035N, SQL1652N, or SQL5005C error message, possible causes and workarounds are as follows: User does not have sufficient authority on the sqllib directory Problem Received an SQL1035N or SQL1652N error when trying to open DB2 CLP or command window. The DB2 Universal Database code (core files) are installed into a directory structure where write privileges are limited, but some DB2 Universal Database tools need to write and create files in the DB2INSTPROF directory. Workaround Create a new directory where you can grant users, at minimum, the MODIFY permission and use either db2set -g db2tempdir to point to the new directory, or set the db2tempdir variable in the Windows system environment. User does not have sufficient authority to write to the sqllib\ directory even though user belongs to SYSADM_GROUP Problem Received an SQL5005C system error when trying to update the database manager configuration file (update dbm cfg). The user does not have the required NTFS permissions to write to the sqllib\instance_dir directory even though you have added this user to the SYSADM_GROUP. First workaround Grant the users, at minimum, the MODIFY permission on the instance_dir directory at the file system level. Second workaround Create a new directory where you can grant the user, at minimum, the MODIFY permission. Use the db2set db2instprof to point to the new directory. You will either need to recreate the instance so that the information is stored under the new instance directory specified by db2instprof, or you will need to move the old instance directory to the new directory. SQL Assist SQL Assist button disabled in the Command Center In the Command Center, the SQL Assist button only becomes enabled once a connection has been established. Two versions of SQL Assist are launched from DB2 You can invoke both version 7 and version 8 of SQL Assist from within DB2 Universal Database, Version 8.1. You can launch version 7 from the DB2 Data Warehouse Center. All other centers launch the latest version 8. The product online help has additional information for SQL Assist, Version 7. System Monitor Event record size limitation For deadlock event monitors and global detailed deadlock event monitors, the event record is limited by the size of a nonconfigurable internal buffer. If db2diag.log cannot write this logging entry due to the record size, the log will record a message such as "event record is larger than BUFFERSIZE." Snapshot UDF restrictions Snaphot user-defined functions (UDF) are intended to be used on databases whose Directory entry type value displays as Indirect or Home when the LIST DB DIRECTORY command is issued. If a UDF is used against a remote database, the UDF will fail with the following error: SQL1427N An instance attachment does not exist. The snapshot UDFs, introduced in V8.1 cannot be used in conjunction with the monitor switches commands and APIs or monitor reset commands and APIs. This restriction includes: * GET MONITOR SWITCHES * UPDATE MONITOR SWITCHES * RESET MONITOR This limitation is due to the fact that such commands use an INSTANCE ATTACH, while the snapshot UDFs make use of DATABASE CONNECTs. Amount of Log to be Redone for Recovery monitor element undefined for V8.1.4 In the Release information section of the Information Center for V8.1.4, log_to_redo_for_recovery is introduced as a new monitor element. The value of this monitor element is undefined for V8.1.4. This functionality is planned in a future release. Throttled utility restrictions The simultaneous execution of multiple throttled utilities is not supported. For example: * If you are running three online backups, only one can be throttled. The other two must have a priority of 0. * You can invoke a rebalance and backup at the same time, but either the rebalance or backup must have a priority of 0. If you invoke multiple throttled utilities at the same time, it can cause the utilities to run for excessively long periods of time. It can also cause the system impact to be more severe than the limit set by the impact policy (UTIL_IMPACT_LIM). XML Extender XML Extender sample programs renamed Conflicts between the system operations and XML Extender can cause some XML Extender sample programs to seriously damage your files. The following list shows the conflicting XML Extender sample programs as well as new replacement programs that are less likely to cause conflicts. Make sure to use the new sample programs in place of the old ones. Table 5. Replacement sample programs for XML Extender (Windows) +----------------------------------+----------------------------------+ | Old Program (Do not use) | New Program (Use) | +----------------------------------+----------------------------------+ | insertx.exe | dxxisrt.exe | +----------------------------------+----------------------------------+ | retrieve.exe | dxxretr.exe | +----------------------------------+----------------------------------+ | retrieve2.exe | dxxretr2.exe | +----------------------------------+----------------------------------+ | retrievec.exe | dxxretrc.exe | +----------------------------------+----------------------------------+ | shred.exe | dxxshrd.exe | +----------------------------------+----------------------------------+ | tests2x.exe | dxxgenx.exe | +----------------------------------+----------------------------------+ | tests2xb.exe | dxxgenxb.exe | +----------------------------------+----------------------------------+ | tests2xc.exe | dxxgenxc.exe | +----------------------------------+----------------------------------+ Table 6. Replacement sample programs for XML Extender (UNIX) +----------------------------------+----------------------------------+ | Old Program (Do not use) | New Program (Use) | +----------------------------------+----------------------------------+ | insertx | dxxisrt | +----------------------------------+----------------------------------+ | retrieve | dxxretr | +----------------------------------+----------------------------------+ | retrieve2 | dxxretr2 | +----------------------------------+----------------------------------+ | retrievec | dxxretrc | +----------------------------------+----------------------------------+ | shred | dxxshrd | +----------------------------------+----------------------------------+ | tests2x | dxxgenx | +----------------------------------+----------------------------------+ | tests2xb | dxxgenxb | +----------------------------------+----------------------------------+ | tests2xc | dxxgenxc | +----------------------------------+----------------------------------+ Using the new sample programs with the sample sqx files The source code (.sqx files) for the executables listed above are located in the samples\db2xml\c directory of your installation. The source files are still labeled with their old names. If you make changes to the source code, copy your newly compiled executables (with the old names) to the sqllib\bin directory. On Windows platforms, you must make an additional copy, rename it with its new name above, and copy it to the bin directory. Both copies replace the existing files in the bin directory. For example, after compiling your new version of shred.exe, you need to make two copies and replace the files in the bin directory: one labeled shred.exe and the other renamed dxxshrd.exe. On UNIX platforms, you only need to replace the file with the old name with your newly compiled version.. If you create new executable files from these samples, you must copy the new files from the \SQLLIB\samples\db2xml\c\ directory into the \SQLLIB\bin\ directory, and then make an additional copy, renaming them according to the table above. Decomposing documents in XML Extender that contain non-unique attribute and element names You can now decompose documents that contain non-unique attributes and/or non-unique element names that map to different columns (of the same or different tables) without receiving the DXXQ045E error. The following is an example of an XML document with non-unique attributes and non-unique element names: John Smith Jane Doe xxxx-xxxx 2 12.50 yyyy-yyyy 4 24.99 The accompanying DAD, which maps the duplicate elements/attributes to different columns, looks like this:
order_tab.order_id = detail_tab.order_id
detail_tab" />
The contents of the tables would look like the following after the document above is decomposed: ORDER _TAB: ORDER_ID CUST_ID CUST_NAME SALESP_ID SALESP_NAME 0001-6789 1111 John Smith 1234 Jane Doe DETAIL_TAB: ORDER_ID ITEMNO QUANTITY UNIT_PRICE 0001-6789 xxxx-xxxx 2 12.50 0001-6789 yyyy-yyyy 4 24.99 Note: Multiple element/attribute mappings to the same column of the same table are not allowed regardless of whether the element/attribute names are different or the same. Additional Information Change in Unicode server behavior In version 7, Unicode servers ignored any graphic code pages by applications at connect time and assumed that UCS2 Unicode (code page 1200) was being used. Version 8 Unicode servers now respect the code page sent by the client. Full message text is not returned when using SQLException.getMessage() By default, the DB2BaseDataSource.retrieveMessagesFromServerOnGetMessage property is disabled. If you enable this property, all calls to the standard JDBC SQLException.getMessage() invoke a server-side stored procedure, which retrieves the readable message text for the error. By default, the full message text is not returned to the client when a server-side error occurs. You can use the proprietary method DB2Sqlca.getMessage() to retrieve the fully formatted message text. A call to the SQLException.getMessage() method will start a unit of work only if retrieveMessagesFromServerOnGetMessage is enabled. A call to the DB2Sqlca.getMessage() method results in a stored procedure call, which starts a unit of work. Prior to FixPak 1, the DB2Sqlca.getMessage() method may throw an exception. IBM DB2 Universal JDBC driver The IBM DB2 Universal JDBC Driver cannot connect to databases that were created using the HP default character set, roman8. All SQLJ and JDBC applications that use the universal JDBC driver, must connect to a database created with a different character set. If your LANG is set to "C" or to a "roman8" locale, you must change it to the corresponding ISO locale. For instance, if your LANG is set to de_DE.roman8, it must be changed to de_DE.iso88591: export LANG=de_DE.iso88591 To run the DB2 SQLJ and JDBC sample programs with the universal JDBC driver, you can create the sample database with the following commands (in this case, using the ISO locale for US English): export LANG=en_US.iso88591 db2 terminate db2sampl Note that if the sample database already exists, you must drop it before executing these commands. Java functions and routines on Linux, UNIX, and Windows operating systems Due to limitations in the JVM, a Java routine defined as NOT FENCED will be invoked as if it had been defined as FENCED THREADSAFE. In version 8.1, all Java routines specified as NOT FENCED are treated as FENCED routines. Java UDFs defined with parameter style DB2GENERAL that contain a LOB locator in the argument definition of the UDF will not function. You must modify these functions to use a BLOB or CLOB argument instead of a locator. For Java UDFs, LOB locators are only supported as input arguments when the DB2JAVA parameter style is specified. English Microsoft Data Access Components (MDAC) files are used for all national language versions of DB2 Universal Database, V8.1, unless translated MDAC files are installed first. If you do not install the national language version of MDAC 2.7 prior to installing the national language version of DB2, then DB2 Universal Database installs English MDAC files by default. This causes the Windows ODBC Data Source Administrator panels to appear untranslated if your operating system is non-English. To fix this problem, you can install the "MDAC 2.7 RTM - Refresh" bundle from the Microsoft Web site at http://www.microsoft.com/data/download_270RTM.htm. Choose the language that you want to install, download the required executable, and run it. This will install the translated ODBC Data Source Administrator files. The Simplified Chinese locale on AIX operating systems AIX has changed the code set bound to the Simplified Chinese locale Zh_CN on: * AIX Version 5.1.0000.0011 or later * AIX Version 5.1.0 with maintenance level 2 or later The code set has been changed from GBK (code page 1386) to GB18030 (code page 5488 or 1392). Since DB2 Universal Database for AIX supports the GBK code set natively and the GB18030 code set via Unicode, DB2 Universal Database will default the Zh_CN locale's code set to ISO 8859-1 (code page 819), and in some operations will also default the locale's territory to the United States (US). To work around this limitation, you have two options: * You can override the locale's code set from GB18030 to GBK and the territory from US to China (whose territory ID is CN and territory code is 86). * You can use a different Simplified Chinese locale. If you choose to use the first option, issue the following commands: db2set DB2CODEPAGE=1386 db2set DB2TERRITORY=86 db2 terminate db2stop db2start If you choose to use the second option, change your locale from Zh_CN to either ZH_CN or zh_CN. The ZH_CN locale's code set is Unicode (UTF-8), while the zh_CN locale's code set is eucCN (code page 1383). The Simplified Chinese locale on Red Hat, V8 operating systems Red Hat, Version 8 has changed the default code set for Simplified Chinese from GBK (code page 1386) to GB18030 (code page 5488 or 1392). Since DB2 Universal Database for Linux supports the GBK code set natively and the GB18030 code set via Unicode, DB2 Universal Database will default its code set to ISO 8859-1 (code page 819), and in some operations will also default its territory to the United States (US). To work around this limitation, you have two options: * You can override the Red Hat default code set from GB18030 to GBK and the territory from US to China (whose territory ID is CN and territory code is 86). * You can use a different Simplified Chinese locale. If you choose to use the first option, issue the following statements: db2set DB2CODEPAGE=1386 db2set DB2TERRITORY=86 db2 terminate db2stop db2start If you choose to use the second option, issue any one of the following commands: export LANG=zh_CN.gbk export LANG=zh_CN export LANG=zh_CN.utf8 where the code set associated with zh_CN is eucCN or code page 1383, and with zh_CN.utf8 is code page 1208. Corrections to the documentation This section describes corrections to previously released HTML, PDF, and printed documentation. Updated versions of the affected topics will be available in a future version of the DB2(R) documentation. Administration Guide: Planning Topic Title: Space requirements for temporary tables Location in the DB2 Information Center accessed from a browser Concepts -> Administration -> Database design -> Physical -> Space requirements for database objects -> Temporary tables Correction Replace the first paragraph with the following: Some SQL statements require temporary tables for processing (such as a work file for sorting operations that cannot be done in memory). These temporary tables require disk space; the amount of space required is dependent upon the size, number, and nature of the queries, and the size of the returned tables. Your work environment is unique which makes the determination of your space requirements for temporary tables difficult to estimate. For example, more space may appear to be allocated for system temporary table spaces than is actually in use due to the longer life of various system temporary tables on disk. This could occur when the registry variable DB2_SMS_TRUNC_TEMP_THRESH is used. For more information on this registry variable, refer to the "Registry and Environment Variables" section in this release notes. Topic Title: Temporary table space design Location in the DB2 Information Center accessed from a browser Concepts -> Administration -> Database design -> Physical -> Table space design -> Temporary table space design Correction Add the following information: If you are reliant on system temporary tables in SMS system temporary table spaces because of your work environment, you may want to consider using the registry variable DB2_SMS_TRUNC_TEMP_THRESH. In the past when system temporary tables were no longer needed, they were truncated to a file size of zero. This was the default. The default has changed so that the file size is no longer truncated to zero but rather the file size is truncated to a non-zero size once the default threshold value is exceeded. The need for space for a new system temporary table would have a performance cost associated with reserving the disk space for it. Using this registry variable allows for leaving disk space allocated for system temporary tables even after they have been dropped, to avoid the performance cost of repeated space reservation and truncation of storage on disk for system temporary tables. This is particularly beneficial in environments where large numbers of system temporary tables are created. Topic Title: Enabling bidirectional support Location in the DB2 Information Center accessed from a browser Tasks -> Administering database systems -> Creating a database -> Enabling language support -> Enabling bidirectional support Correction Change the Restrictions section to include the following: When converting from one Arabic CCSID to another Arabic CCSID, DB2 UDB employs the following logic to deshape (or expand) the lam-alef ligature. Deshaping will occur when the Text Shaping attribute of the source Arabic CCSID is shaped but the Text Shaping attribute of the target Arabic CCSID is unshaped. The logic to deshape the lam-alef ligature is: 1. If the last character of the data stream is a blank character, then every character after the lam-alef ligature will be shifted to the end of the data stream, therefore making available an empty position for the current lam-alef ligature to be deshaped (expanded) into its two constituent characters: lam and alef. 2. Otherwise, if the first character of the data stream is a blank character, then every character before the lam-alef ligature will be shifted to the beginning of the data stream, therefore making available an empty position for the current lam-alef ligature to be deshaped (expanded) into its two constituent characters: lam and alef. 3. Otherwise, there is no blank character at the beginning and end of the data stream, and the lam-alef ligature cannot be deshaped. If the target CCSID does have the lam-alef ligature, then the lam-alef ligature remains as is; otherwise, the lam-alef ligature is replaced by the target CCSID's substitution character. Conversely when converting from an Arabic CCSID whose Text Shaping attribute is unshaped to an Arabic CCSID whose Text Shaping attribute is shaped, the source lam and alef characters will be contracted to one ligature character, and a blank character is inserted at the end of the target area data stream. Change the final paragraph in the Procedure to the following: For DRDA environments, if the HOST EBCDIC platform also supports these bidirectional CCSIDs, you only need to set the DB2CODEPAGE value. Note that you must not further specify the same CCSID on the BIDI parameter in the PARMS field of the DCS database directory entry for the server database, otherwise an extra bidi layout conversion would occur, and render any Arabic data to be incorrectly reversed. However, if the HOST platform does not support these CCSIDs, you must also specify a CCSID override for the HOST database server to which you are connecting. This is accomplished through the use of the BIDI parameter in the PARMS field of the DCS database directory entry for the server database. The override is necessary because, in a DRDA environment, code page conversions and layout transformations are performed by the receiver of data. However, if the HOST server does not support these bidirectional CCSIDs, it does not perform layout transformation on the data that it receives from DB2 UDB. If you use a CCSID override, the DB2 UDB client performs layout transformation on the outbound data as well. Please consult the "Handling BiDi data" section of the IBM DB2 Connect User's Guide for more information. Topic Title: Version 8 incompatibilities Location in the DB2 Information Center accessed from a browser Release information -> Incompatibilities between releases Correction Within the Messages subsection, the following item "DB2 Connect messages returned instead of DB2 messages" needs to add the following information: The messages affected by this change are related to bind, connection, or security errors. SQL errors for queries and other SQL requests are not affected by this change. Application development: Call Level Interface (CLI) Topic Title: Cursor Considerations in CLI Applications Location in the DB2 Information Center accessed from a browser Concepts -> Application development -> Programming features -> Cursors Correction The discussion of which cursor type to use should include dynamic scrollable cursors as a possible cursor type. Dynamic scrollable cursors are only supported when accessing servers which are DB2 UDB for z/OS Version 8.1 and later. Keyset-driven cursors are recommended over dynamic scrollable cursors when the application does not need to detect rows that are inserted by other cursors, and when it is acceptable for deleted rows to exist as "holes" in the result set. Dynamic cursors do not recognize deleted rows as "holes", but instead replace the deleted row with the next row in the result set, if one exists. Topic Title: Importing Data with the CLI LOAD Utility in CLI Applications Location in the DB2 Information Center accessed from a browser Tasks -> Developing applications -> Programming with application programming interfaces (APIs) -> CLI -> Processing transactions -> Inserting data Correction The restriction requiring parameter markers for each column of the target table in the prepared INSERT statement does not apply when a fullselect is used instead of the VALUES clause in the INSERT statement. The CLI LOAD utility now supports a fullselect on the INSERT statement, allowing you to load data from one table into another while executing the INSERT statement only once. Topic Title: Statement Attributes (CLI) List Location in the DB2 Information Center accessed from a browser Reference -> APIs (application programming interfaces) -> CLI attributes Correction For the SQL_ATTR_CURSOR_TYPE statement attribute, the SQL_CURSOR_DYNAMIC value is supported by DB2 CLI if the server is DB2 UDB for z/OS Version 8.1 and later. Data Links Manager Topic Title: Changing the diagnostic level for error message log files Location in the DB2 Information Center accessed from a browser Tasks -> Data Links Manager-> Working with the Data Links File Manager-> Logging Correction 1. Replace the first sentence of the first paragraph, which currently states: "Data Links maintains error message log files from the Data Links server and from the DB2 databases that manage DATALINK data files." with the following sentence: "DB2 Data Links Manager maintains error message log files from the Data Links server and from the DB2 host databases that manage linked files." 2. Remove all references to the DLFM_LOG_LEVEL registry variable from this entire topic. The DLFM_LOG_LEVEL registry variable is no longer supported. DB2 Data Links Manager information is now included in the DB2 trace functionality in this release. * Replace the first paragraph of the Procedure section with the following paragraph: "You control the level of detailed information that is written to the db2diag.log file on DB2 host and Data Links server computers by using the DIAGLEVEL configuration parameter." * Remove the entire third paragraph of the Procedure section. * Add Related reference links to the "DB2 trace (db2trc)" and "db2trc - Trace Command" topics. Add a Related concept link to the "DB2 traces" topic. Topic Title: Using Tivoli Storage Manager as an archive server (AIX) Location in the DB2 Information Center accessed from a browser Tasks -> Data Links Manager-> Configuring system management options Correction Replace the text in step 2 with the following text: "Register the Data Links server machine on which you installed the Tivoli Storage Manager client application with the Tivoli Storage Manager server. For more information, see your Tivoli Storage Manager product documentation." Topic Title: Using Tivoli Storage Manager as an archive server (Solaris Operating Environment) Location in the DB2 Information Center accessed from a browser Tasks -> Data Links Manager-> Configuring system management options Correction Replace the text in step 2 with the following text: "Register the Data Links server machine on which you installed the Tivoli Storage Manager client application with the Tivoli Storage Manager server. For more information, see your Tivoli Storage Manager product documentation." Topic Title: Using Tivoli Storage Manager as an archive server (Windows) Location in the DB2 Information Center accessed from a browser Tasks -> Data Links Manager-> Configuring system management options Correction 1. Replace the text in step 2 with the following text: "Register the Data Links server machine on which you installed the Tivoli Storage Manager client application with the Tivoli Storage Manager server. For more information, see your Tivoli Storage Manager product documentation." 2. Remove step 5 entirely. 3. In step 7, change the reference to the dsm.sys file to be to the dsm.opt file. The revised step reads as follows: "Set the PASSWORDACCESS option to generate in the c:\tsm\baclient\dsm.opt Tivoli Storage Manager system options file." Data Warehouse Center Topic Title: Syntax for starting the external trigger client Location in the DB2 Information Center accessed from a browser Reference -> Data warehouses -> Administration Correction When running a step from outside the Data Warehouse Center using the external trigger program, a seventh value for the command parameter is available. This new option is available on DB2 UDB, Version 8.1 FixPak 3 and later. In addition, a RowLimit option has been modified, and a new option is available for the XTClient to log traces to the XTClient.log file. The syntax for starting the external trigger client is as follows: >>-java------+---------------------------+--+---------------------------+--> '--DDWC_MIN=min_port_number-' '--DDWC_MAX=max_port_number-' >--db2_vw_xt.XTClient--TriggerServerHostName--TriggerServerPort--DWCUserID--> >--DWCUserPassword--StepOrProcessName--Command--+-----------------------+--+----------+--+-----------+->< '-WaitForStepCompletion-' '-RowLimit-' '-LogToFile-' The changes to the options are as follows: Command A new value has been added for the Command parameter: 7 Check to See Whether DWC Server is Running Verify that the Data Warehouse Center server is running. RowLimit Optional. Enter 0 to fetch all rows. LogToFile Optional. Enter 1 or 0 to log traces to the XTClient.log file. Topic Title: Clean Data transformer Location in the DB2 Information Center accessed from a browser Concepts -> Data warehouses -> Data transforms Correction The following paragraph is an addition to the current documentation and provides a restriction for the z/OS agent: The Data Warehouse Center z/OS agent only supports the Clean Data transformer when running interpreted Java stored procedures, which requires DB2 UDB for z/OS Version 7 and later. Also, clean type "Encode invalid values" requires DB2 for z/OS Version 8. Using "Encode invalid values" prior to DB2 UDB for z/OS Version 8 will return the SQLcode -443, %DWCQ-104 error. Information Catalog Center Topic Title: Configuring the Information Catalog Center for the Web with WebSphere Application Server 5 Location in the DB2 Information Center accessed from a browser Tasks -> Data warehouses -> Installing Warehouse Manager components -> Information Catalog Manager tools Correction In the fifth step "Update the application classpath," the following example is an incorrect classpath for Windows: C:\Program Files\ibm\sqllib\java\db2cmn.jar The correct classpath example is: C:\Program Files\ibm\sqllib\tools\db2cmn.jar In addition, you can connect to only one Information Catalog per Information Catalog Center for the Web application, because all of the Web users log on with the same user ID and password to access the catalog. National languages Topic Title: String comparisons in a Unicode database Location in the DB2 Information Center accessed from a browser Concepts -> Administration -> Unicode character encoding Correction Pattern matching is one area where the behavior of existing MBCS databases is slightly different from the behavior of a UCS-2 database. For MBCS databases in DB2 UDB, the current behavior is as follows: If the match-expression contains MBCS data, the pattern can include both SBCS and non-SBCS characters. The special characters in the pattern are interpreted as follows: * An SBCS halfwidth underscore refers to one SBCS character. * A non-SBCS fullwidth underscore refers to one non-SBCS character. * A percent (either SBCS halfwidth or non-SBCS fullwidth) refers to zero or more SBCS or non-SBCS characters. In a Unicode database, there is really no distinction between "single-byte" and "non-single-byte" characters. Although the UTF-8 format is a "mixed-byte" encoding of Unicode characters, there is no real distinction between SBCS and non-SBCS characters in UTF-8. Every character is a Unicode character, regardless of the number of bytes in UTF-8 format. In a Unicode graphic column, every non-supplementary character, including the halfwidth underscore (U+005F) and halfwidth percent (U+0025), is two bytes in width. For Unicode databases, the special characters in the pattern are interpreted as follows: * For character strings, a halfwidth underscore (X'5F') or a fullwidth underscore (X'EFBCBF') refers to one Unicode character. A halfwidth percent (X'25') or a fullwidth percent (X'EFBC85') refers to zero or more Unicode characters. * For graphic strings, a halfwidth underscore (U+005F) or a fullwidth underscore (U+FF3F) refers to one Unicode character. A halfwidth percent (U+0025) or a fullwidth percent (U+FF05) refers to zero or more Unicode characters. Note: You need two underscores to match a Unicode supplementary graphic character because such a character is represented by two UCS-2 characters in a GRAPHIC column. Only one underscore is needed to match a Unicode supplementary character in a CHAR column. For the optional "escape expression", which specifies a character to be used to modify the special meaning of the underscore and percent sign characters, the expression can be specified by any one of: * A constant * A special register * A host variable * A scalar function whose operands are any of the above * An expression concatenating any of the above with the restrictions that: * No element in the expression can be of type LONG VARCHAR, CLOB, LONG VARGRAPHIC, or DBCLOB. In addition, it cannot be a BLOB file reference variable. * For CHAR columns, the result of the expression must be one character or a binary string containing exactly one (1) byte (SQLSTATE 22019). * For GRAPHIC columns, the result of the expression must be one character (SQLSTATE 22019). Registry and environment variables Topic Title: Performance variables Location in the DB2 Information Center accessed from a browser Reference -> Registry and environment variables -> Performance variables Correction Add the following performance variable: Table 7. Performance variable DB2_SMS_TRUNC_TEMP_THRESH +------------------------------+-----------+--------------------------+ | Variable Name | Operating | Values | | | System | | +---------------------------------------------------------------------+ | Description | +------------------------------+-----------+--------------------------+ | DB2_SMS_TRUNC_TEMP_THRESH | All | Default=1 | | | | Values: -1, 0-n, where | | | | n=the number of extents | | | | per container that are | | | | to be maintained | +---------------------------------------------------------------------+ | Specifies a minimum file size threshold at which the file | | representing a temporary table will be maintained in SMS table | | spaces. Setting this variable to a value greater than 0 can reduce | | some of the system overhead involved in dropping and recreating the | | file each time a temporary table is used. By default, when a | | temporary table is no longer needed, the file for that table is | | truncated to 1 extent per container. If the file is already one | | extent or smaller in size, it is left as is. When the value of this | | variable is higher than 1, a larger file is maintained. | | If this variable is set to -1, then the file is not be truncated at | | all and the file will be allowed to grow indefinitely, restricted | | only by system resources. | | If this variable is set to 0, then no special threshold handling is | | done. Instead, once a temporary table is no longer needed, that | | file is truncated to 0. | +---------------------------------------------------------------------+ XML Extender Topic Title: Planning for XML columns Location in the DB2 Information Center accessed from a browser Tasks -> XML Extender -> Managing data in XML columns -> Planning for XML columns Correction The subsection of this topic titled 'The DAD file' incorrectly states that the DAD file for XML columns specifies the directory paths on the client for the DAD file and DTD. The DAD file for XML columns and XML collections does not specify directory paths on the client or the server for either type of files. Online help corrections and updates Configuring the C environment for SQL stored procedures in the Development Center If you are working with DB2(R) for Windows(R) on the server and you are using the Visual C++ compiler, you must configure your SQL build settings. You will be not be able to build SQL stored procedures until you configure your SQL Build options. Use the Database Connection Properties notebook in the Development Center to configure your SQL build settings. To configure the C compiler environment for SQL stored procedures: 1. On the SQL Build Settings page of the notebook, specify a compiler environment that you want to use for building SQL objects. * Click Refresh. * In the Compiler environment field, type the location of the VC98\BIN\VCVARS32.BAT file on your Windows server. 2. Click OK to close the notebook and save your changes. If you click Apply, the changes are saved and you can continue changing the properties. Enabling view docking when accessing Development Center with Hummingbird Exceed When accessing the Development Center on UNIX(R) with Hummingbird(R) Exceed, the XTEST extension version 2.2 must be enabled before you can move and dock views by dragging their title bars within the Development Center. To enable the XTEST extension: 1. From the Start menu, select Programs -> Hummingbird Connectivity 7.0 ->Exceed->XConfig. The XConfig window will open. 2. Optional: If your configuration requires a password, enter the XConfig password. 3. Double click the Protocol icon. The Protocol window will open. 4. Check the X Conformance Test Compatibility checkbox. 5. In the Protocol window, click the Extensions... button. The Protocol Extensions window will open. 6. In the Enable Extensions list, select the XTEST(X11R6) checkbox. 7. Click OK. Microsoft Visual Studio .NET add-in information update in Development Center help The "About the Development Center" help topic does not include information about the new Microsoft(R) Visual Studio .NET add-in in the list of development environment add-ins provided. The following information describes the .NET add-in that supports Development Center functionality in the Microsoft Visual Studio .NET development environment: DB2 Development Add-In for the Microsoft Visual Studio .NET development environment A new component of the DB2 Application Development Client is the IBM(R) DB2 Development Add-In for Microsoft Visual Studio .NET for the .NET framework version 1.0. This add-in extends the Visual Studio .NET IDE to provide tightly integrated DB2 application development support using the DB2 .NET Managed Provider as well as DB2 server-side development support. Using this add-in available in Microsoft Visual Studio .NET you can: * Develop DB2 specific database projects from the new IBM Projects folder with advanced script generation wizards. * Explore the DB2 catalogue information using DB2 data connections in the new IBM Explorer. * Make use of the extended intelligence features for DB2 table/view columns and procedure/function parameters. * Generate ADO.NET code for your windows forms using drag and drop. * Configure your DB2 Managed Provider objects using properties custom editors and wizards. * Launch various DB2 development and administration centers. * View add-in help from the existing dynamic help window. The DB2 Development Add-In for Microsoft Visual Studio .NET database connections are managed using the DB2 .NET managed provider and ADO.NET. Migrating DB2 XML Extender to Version 8.1.2 If you are migrating from a Version 7 FixPak, refer to each of the release notes for the Version 7 FixPak for more information on what changes are included when upgrading to Version 8.1.2. Each new FixPak contains all of the previous FixPaks' updates. To migrate DB2 XML Extender from previous versions to Version 8.1.2, complete the following steps. 1. From the DB2 Command Line, enter: db2 connect to database_name db2 bind dxxinstall\@dxxMigv.lst where dxxinstall is the directory path in which you installed DB2 Universal Database . 2. From the DB2 Command Line, enter: dxxMigv database_name Path settings to enable Java routines to compile in the Development Center The Development Center cannot compile Java(TM) routines unless it knows where your developer kit versions are installed. Default locations for these will be written to your $HOME/IBM/DB2DC/DB2DC.settings file when the Development Center starts for the first time. You may copy these into your $USER.settings file and modify them with a Unicode editor, or you may create symbolic links to your developer kit directories in the default locations. Runstats dialog - updated getting there information To open the Runstats notebook: 1. From the Control Center, expand the object tree until you find the Tables folder. 2. Click the Tables folder. Any existing tables are displayed in the contents pane. 3. Right-click all the tables that you want to run statistics on, and select Run Statistics from the pop-up menu. The Runstats notebook opens. Specifying build options for a Java stored procedure in the Development Center Use the Stored Procedure Properties notebook to specify the compile options that will be used when building a Java stored procedure. These steps are part of the larger task of changing stored procedure properties. To specify the build options of a stored procedure: 1. On the Build page of the Stored Procedure Properties notebook, specify the compile options for building the stored procedure. See your compiler documentation for information about available options. a. In the Precompile options field, type the DB2 Universal Database(TM) precompiler options that you want to use when building stored procedures. The package name must not exceed 7 characters. b. In the Compile options field, type the compiler options that you want to use when building stored procedures. 2. Click OK to close the notebook and save your changes. If you click Apply, the changes are saved and you can continue changing the properties. Appendix. Notices IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country/region or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country/region where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product, and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information that has been exchanged, should contact: IBM Canada Limited Office of the Lab Director 8200 Warden Avenue Markham, Ontario L6G 1C7 CANADA Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems, and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information may contain examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious, and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information may contain sample application programs, in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: (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. Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both, and have been used in at least one of the documents in the DB2 UDB documentation library. +----------------------------------+----------------------------------+ | ACF/VTAM | LAN Distance | | AISPO | MVS | | AIX | MVS/ESA | | AIXwindows | MVS/XA | | AnyNet | Net.Data | | APPN | NetView | | AS/400 | OS/390 | | BookManager | OS/400 | | C Set++ | PowerPC | | C/370 | pSeries | | CICS | QBIC | | Database 2 | QMF | | DataHub | RACF | | DataJoiner | RISC System/6000 | | DataPropagator | RS/6000 | | DataRefresher | S/370 | | DB2 | SP | | DB2 Connect | SQL/400 | | DB2 Extenders | SQL/DS | | DB2 OLAP Server | System/370 | | DB2 Universal Database | System/390 | | Distributed Relational | SystemView | | Database Architecture | Tivoli | | DRDA | VisualAge | | eServer | VM/ESA | | Extended Services | VSE/ESA | | FFST | VTAM | | First Failure Support Technology | WebExplorer | | IBM | WebSphere | | IMS | WIN-OS/2 | | IMS/ESA | z/OS | | iSeries | zSeries | +----------------------------------+----------------------------------+ The following terms are trademarks or registered trademarks of other companies and have been used in at least one of the documents in the DB2 UDB documentation library: Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.