IBM DB2 Universal Database* for AIX* Version 5.2 Interim: U480150 ID: 05.02.0000.0065 +-- Note: ----------------------------------------------------------------+ | | To read this file more easily, set your font to monospace. | | If you have received interim fixes from IBM support after 09/29/01, | then you must contact IBM support instead of installing this FixPak, to | request an updated version of the interim fixes. By doing this, you are | assured that your system is in a consistent state and no interim fixes | are lost. | | Before installing this FixPak you must have DB2 UDB v5.2 installed. This | FixPak cannot be installed directly on a DB2 UDB v5.0 system. If you | currently have DB2 UDB v5.0, you must apply FixPak 6 before installing | this Fixpak. | +-------------------------------------------------------------------------+ This README file (located in Readme/En_US/Fixpak.Readme) contains information for the following products and components: AIX Specific ------------ DB2 Connect Enterprise Edition, V5.2 DB2 Universal Database Enterprise Edition, V5.2 DB2 Universal Database Extended Enterprise Edition, V5.2 DB2 Software Developer's Kit, V5.2 DB2 Client Application Enabler, V5.2 DB2 File Manager, V5.2 --------------------------------------------------------------------------- 1. Contents of FixPak 2. Installation Notes 2.1 Pre-requisites 2.1.1 Prerequisities for APAR IX73249 2.2 Prior to Installation 2.3 Installation Instructions 2.3.1 Applying Fixpak for Data Links Manager on UNIX 2.4 After Installation 2.4.1 Update Instances 2.4.2 Rebinding bind files 2.4.2.1 Rebinding to non-DRDA DB2 databases 2.4.2.2 Rebinding to DRDA databases 2.4.2.3 Rebinding Specific Packages 2.4.3 Searching the HMTL Documentation 2.4.3.1 Installing the HTML Search System 2.4.3.2 IBM NetQuestion runtime environment installation 2.4.4 Problem affecting NIS users on AIX Version 4.1.5 2.4.6 Building 32-bit Microfocus Cobol applications for UDB on OS/2 2.4.7 DB2 Support for ADSM Version 3 Clients 2.4.8 Updating db2.o for AIX CICS Users 2.4.9 DB2MEMDISCLAIM and DB2MEMMAXFREE 2.5 Removing the FixPak 3. Miscellaneous 3.1 Product and Service Technical Library 3.2 Customer Support 3.3 Corrective Service 3.4 DB2/NT UDB EEE Support with Multiple Communication Adapters and TCP/IP Addresses 3.5 Maximum log file size for NT 3.6 Bufferpool configuration parameters 3.7 Automatic Summary Tables 3.8 Correction of CREATE TABLE statement 3.9 New DB2 CLP option For additional information please see the following files: /usr/lpp/db2_05_00/Readme/%L/Release.Notes where %L is the locale name. =========================================================================== 2. Installation Notes 2.1 Pre-requisites You should apply the U459852 Fixpak (Fixpak 6 for V5.2) before installing this Fixpak. To determine if the the required pre-requistes are installed, issue the following command: lslpp -al "db2_05_00*" The output of the command should include the following: db2_05_00.client 5.2.0.x where 0 <= x <= 39 2.1.1 Prerequisites for APAR IX73249 Prerequisites for APAR IX73249 Incorrect Output for DB2 LIST DCS APPLICATIONS SHOW DETAIL The DB2 for MVS APAR PQ11645 must be applied in conjunction with DB2 Connect APAR IX73249 in order to provide the meaningful correlation token display on both the LIST DCS APPLICATIONS and the DB2 MVS DSP THD commands. 2.2 Prior to Installation Logon as root and do the following for each instance: su - ioname . $HOME/sqllib/db2profile db2 force applications all db2 terminate db2stop db2licd end (run at each physical node) exit where ioname is the instance owner name. Then, while still logged on as root, do the following: su - aname . $HOME/sqllib/db2profile db2admin stop exit /usr/sbin/slibclean where aname is the admin server name. 2.3 Installation Instructions Install the selected updates using either SMIT or installp. To list the installable options in this FixPak, use: installp -ld where is the name of the device where the updated image resides. To install DB2 UDB for AIX and all its prerequisites and leave them in apply state, select the following menu options in SMIT: smit update_all or /usr/lib/instl/sm_inst installp_cmd -T iems -q -a -g -S _update_all -d '' '-X' where is the name of the filesystem that contained the PTF images. For more information about the installp command or SMIT, refer to the online documentation by issuing `man installp` or `man smit`. Warning: If at a later time you add DB2 for AIX to a machine where the db2_05_00.client update is installed, you must then also install the db2_05_00.db2 update from this FixPak; otherwise the software will be in an inconsistent state. 2.3.1 Applying Fixpak for Data Links Manager on UNIX 1) As the DB2 Data Links Manager Administrator, bring down the DB2 Data Links Manager by running the following commands: dlfm stop dlfm stopdbm Ensure that there are no DB2 or DLFM processes remaining. 2) As root, unmount each of the dlfs filesystem(i.e. the filesystem which is controlled by the DB2 Data Links Manager) by running the following command: umount /filesystem_name where /filesystem_name is the name of the dlfs filesystem which you want to unmount. 3) As root, unload the DLFS device driver by running the following command: strload -uf /usr/lpp/db2_05_00/cfg/dlfs_cfg 4) Install the Fixpak (PTF...). 5) After successful installation of fixpak, as root, update the Data Links Manager instance by running the following command: /usr/lpp/db2_05_00/instance/dlfmupdt dlm_instance_name where dlm_instance_name is the name of the DB2 Data Links Manager Administrator. 6) As root, load the DLFS device driver by running the following command: strload -f /usr/lpp/db2_05_00/cfg/dlfs_cfg 7) As root, mount each of the dlfs filesystems by running the following command: mount -v dlfs /filesystem_name 8) As the DB2 Data Links Manager Administrator, run the following commands to bring up the DB2 Data Links Manager: dlfm bind dlfm start 9) Check the db2diag.log to ensure that the Data Links Manager is started properly. 2.4 After Installation 2.4.1 Update Instances Note that you need to be logged in as user root to update the instances. For each instance, issue the command: /usr/lpp/db2_05_00/instance/db2iupdt iname where iname is the instance name. For DAS instance, issue the command: /usr/lpp/db2_05_00/instance/dasiupdt dasname where dasname is the das instance name. 2.4.2 Rebinding bind files Due to the new bind (.bnd) files that have been shipped with this FixPak, you will need to rebind your DB2 utilities against all your databases after the FixPak installation. This step is necessary for the fixes in this FixPak to become effective. The procedure of rebinding, outlined below, only needs to be performed once per database. 2.4.2.1 Rebinding to non-DRDA DB2 databases After applying fixes, you must do the following: - At a command prompt: db2 terminate db2 CONNECT TO db2 BIND /@db2ubind.lst BLOCKING ALL GRANT PUBLIC db2 BIND /@db2cli.lst BLOCKING ALL GRANT PUBLIC db2 terminate or, - At the DB2 command line: TERMINATE CONNECT TO BIND /@db2ubind.lst BLOCKING ALL GRANT PUBLIC BIND /@db2cli.lst BLOCKING ALL GRANT PUBLIC TERMINATE Where is the name of a database to which the utilities should be bound, and where is the full path name of the directory where the bind files are located, such as /sqllib/bnd. Examine the DB2PATH environment variable to determine the correct path. DB2UBIND.LST and DB2CLI.LST contain lists of commonly required bind files used for DB2. If is a DB2 v1.x database, do not bind db2cli.lst. Instead, use the db2cliv1.lst or specifically bind db2clics.bnd, db2cliur.bnd, db2clirr.bnd, and db2cliv1.bnd individually. 2.4.2.2 Rebinding to DRDA databases If you are using DDCS to connect to host databases, you will also need to bind the new bind files to the host. As above, use the DB2 Command Line Processor to connect to the host database, and then bind the utilities as follows: HOST COMMAND ======= =================================================== MVS BIND /@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VM BIND /@ddcsvm.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE VSE BIND /@ddcsvse.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE OS400 BIND /@ddcs400.lst BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE Please refer to Chapter 4 "Binding Applications and Utilities" of the DDCS User's Guide for a list of what bind files are used for your specific client operating system. If a bind file changes but your clients do not use that bind file, you do not need to re-bind it. 2.4.2.3 Rebinding Specific Packages If you wish to bind only the specific .bnd files to the database, issue the following command for each database (where is the name of the bind file, and is the name of your database). - At a command prompt: db2 terminate db2 CONNECT TO db2 BIND / BLOCKING ALL GRANT PUBLIC db2 terminate or, - At the DB2 command line: TERMINATE CONNECT TO BIND / BLOCKING ALL GRANT PUBLIC TERMINATE 2.4.3 Searching the HMTL Documentation You can perform searches in the online documentation for IBM DB2 Universal Database (DB2 UDB) using an HTML search server. The following section describes how to set up the search server in a UNIX environment. 2.4.3.1 Installing the HTML Search System To install the search system: 1) Uncompress the HTML files and register the search indexes. The following command decompresses and untars the HTML files, creates links, and registers the indexes used by the search system. /usr/lpp/db2_05_00/doc/db2insthtml where : specifies the language directory, for example en_US for English You must issue this command for each language for which HTML documentation is installed. You must make sure that the original .tar.Z files are present before installing the fixpak and running this command. 2) Using the search server Once NetQuestion has been installed and the db2insthtml command has been run, the search system is ready to use. You can search the DB2 HTML documentation by opening the file db2srch.html in the doc/html subdirectory of DB2. (You will need the updated version of this file that comes with the fixpak.) 2.4.3.2 IBM NetQuestion runtime environment installation The IBM NetQuestion runtime environment consists of 3 installable product options: IMNSearch.rte.SBCS IBM NetQuestion SBCS search engine IMNSearch.rte.DBCS IBM NetQuestion DBCS search engine IMNSearch.rte.httpdlite IBM NetQuestion local HTTP daemon The local HTTP daemon will automatically be installed by either search engine you select during installation. System configuration requirements: Disk space: IMNSearch.rte.SBCS 10 MB IMNSearch.rte.DBCS 20 MB IMNSearch.rte.httpdlite 5 MB Memory: IMNSearch.rte.SBCS 8 MB + 0.5 MB per search request IMNSearch.rte.DBCS 8 MB + 0.7 MB per search request IMNSearch.rte.httpdlite 3 MB All three installation options can be installed/deinstalled via standard AIX installation procedure (either installp or SMIT). Once the selected components are installed, entries will be made for the selected search engine daemons and the HTTP daemon into "/etc/inittab", so that they will be started after the machine has been rebooted. The daemons will also be started by the post installation process. If for any reason you don't need the local HTTP daemon, (e.g. you already installed a HTTP server on your machine), you can remove the "/etc/inittab" entry for the local daemon with the following command: /usr/sbin/rmitab "httpdlite" Note: This command has to be executed with system administration privileges. IMPORTANT NOTICE: If you choose to use your installed HTTP server, ensure that the search CGIs and the search forms will be found by your server. The location of the search CGIs and forms can be found in the product documentation. They should generally be installed in: /var/docsearch/cgi-bin for the search CGIs /var/docsearch/html for the search forms 2.4.4 Problem affecting NIS users on AIX Version 4.1.5 On AIX Version 4.1.5 or higher, when a user is running Network Information System (NIS) for password authentication, the message DB21015E may be received when the command line processor times out. The command line processor back-end program cannot recognize the user-ID of the DB2 instance from the NIS master server in this case. To correct this problem: 1. Remove the user-ID from the NIS master server. 2. Create the user-ID in the "/etc/passwd" file locally on each machine, ensuring that the user-ID is placed before the NIS magic cookie in the file. The magic cookie looks like this: :!:::::: 2.4.6 Building 32-bit Microfocus Cobol applications for UDB on OS/2 When building 32-bit Microfocus Cobol applications for UDB on OS/2, you may encounter the following error when linking to db2gmf32.lib: "link386: fatal error 1104 x:\sqllib\lib\db2gmf32.lib: not a valid library" This is because the db2gmf32.lib library is not compatible with the link386 linker. Ilink must be used to link the library. Microfocus Cobol 4.0.20 and later will look first for the ilink executable in PATH. If it isn't found, Microfocus will call link386. The ilink linker is available at ftp.software.ibm.com under /ps/products/db2/tools. The file is called ilink.zip. It contains a readme with instructions for installing ilink. Note that the prerequisite for Microfocus Cobol is still 4.0.20 (or later). 2.4.7 DB2 Support for ADSM Version 3 Clients DB2 | DB2 Server |Planned | DB2 Service| ADSM Service Level Release | Platform |Availability* | Level | ========+============+==============+============+======================= DB2 UDB | All |Sept 26, 1998 | N/A | ADSM Client V2.1.5+ or V5.2 | | | | ADSM Client V313+ --------+------------+--------------+------------+----------------------- DB2 UDB | AIX 4.1.x |June 30, 1998 | PTF: | ADSM Client V313 V5.0 | | | U457227 | (U454538) | | | | (with AIX41313G patch) | | | | OR | | | | ADSM Client V 3.1.5/6 | | | | with IC21925E --------+------------+--------------+------------+----------------------- DB2 UDB | AIX 4.2.x |June 30, 1998 | PTF: | ADSM Client V313 V5.0 | | | U457227 | (U454539) | | | | (with AIX42313G patch)** | | | | OR | | | | ADSM Client V 3.1.5/6 | | | | with IC21925E (42) --------+------------+--------------+------------+----------------------- DB2 UDB | AIX 4.3.x |June 30, 1998 | PTF: | ADSM Client V313 V5.0 | | | U457227 | (U454539) | | | | (with AIX42313G patch)** | | | | OR | | | | ADSM Client V 3.1.5/6 | | | | with IC21925E (41) --------+------------+--------------+------------+----------------------- DB2 UDB | All Other |Sept 30, 1998 | To Be | To Be Determined V5.0 | | | Determined | --------+------------+--------------+------------+----------------------- DB2 | AIX 4.1.x |July 31, 1998 | PTF: | ADSM Client V313 V2.1.2 | | | U458628 | (U454538) | | | | (with AIX41313G patch) | | | | OR | | | | ADSM Client V 3.1.5/6 | | | | with IC21925E (42) --------+------------+--------------+------------+----------------------- DB2 | AIX 4.2.x |July 31, 1998 | PTF: | ADSM Client V313 V2.1.2 | AIX 4.3.x | | U458628 | (U454539) | | | | (with AIX42313G patch) | | | | OR | | | | ADSM Client V 3.1.5/6 | | | | with IC21925E (42) --------+------------+--------------+------------+----------------------- DB2 DB | AIX 4.1.x |July 31, 1998 | PTF: | ADSM Client V313 Server | | | U458629 | (U454538) V4.1.2 | | | | (with AIX41313G patch) | | | | OR | | | | ADSM Client V 3.1.5/6 | | | | with IC21925E (42) --------+------------+--------------+------------+----------------------- DB2 DB | AIX 4.2.x |July 31, 1998 | PTF: | ADSM Client V313 Server | AIX 4.3.x | | U458629 | (U454539) V4.1.2 | | | | (with AIX42313G patch) | | | | OR | | | | ADSM Client V 3.1.5/6 | | | | with IC21925E (42) --------+------------+--------------+------------+----------------------- DB2 | OS/2 |Oct 30, 1998 | To Be | To Be Determined V2.1.2 | | | Determined | --------+------------+--------------+------------+----------------------- DB2 | All Other |None | N/A | N/A V2.1.2 | | | | --------+------------+--------------+------------+----------------------- DB2 PE | AIX |None | N/A | N/A V1.2 | | | | * Note: The planned availability dates for the required DB2 fix packs are subject to change. ** Note2: There does not appear to be a copy of APARIC21925 for AIX 4.3. Please check with ADSM support to determine if this will be released soon. 2.4.8 Updating db2.o for AIX CICS Users AIX CICS users must perform the following three steps as documented in the CICS/6000 Administration Guide in section entitled: "Configuration steps for Database 2". 1) Create a DB2 UDB for AIX shared object from libdb2.a 2) Build DB2 Switchload file and place in proper directory as defined by the XA definition for the database(s) which use the switch load file. 3) If cobol, then re-run cicsmkcobol. 2.4.9 DB2MEMDISCLAIM and DB2MEMMAXFREE DB2MEMDISCLAIM Platform: AIX Default: (not set) Values: YES or NO Description: Depending on the workload being executed and the pool agents configuration you may run into a situation where the committed memory for each DB2 agent will stay above 32MB even when the agent is idle. This behaviour is expected and usually results in good performance as the memory is kept for fast re-use, however, on a memory constrained system, this may not be a desirable side effect. To avoid this condition issue the following: db2set DB2MEMDISCLAIM=yes Disclaiming memory tells the AIX operating system to stop paging the area so that it no longer occupies any real storage. Setting DB2MEMDISCLAIM to YES tells DB2 UDB to disclaim some or all memory once freed, depending on DB2MEMMAXFREE. This will ensure that the memory is made readily available for other processes as soon as it is freed. See also DB2MEMMAXFREE. ------------------------------------------------------------------------ DB2MEMMAXFREE Platform: AIX Default: (not set) Values: 4000000 to 256000000 Description: DB2MEMMAXFREE specifies the amount of free memory that is retained by each DB2 agent. The default is 256Mb. You may set this variable to a value between 4 to 256 Mb. We recommend that if you use this feature, you specify a value of 8Mb. See also DB2MEMDISCLAIM. db2set DB2MEMMAXFREE=8000000 2.5 Removing the FixPak To remove the FixPak, run smit and make the following selections starting from the main menu: -> Software Installation and Maintenance -> Maintain Installed Software -> Reject Applied Software Updates (Use Previous Version) In the "SOFTWARE name" field, hit F4 (List) to bring up a listing of filesets that can be rejected. Select all db2_05_00 filesets and begin the operation. Please see the online smit and installp man pages for more information. 3. Miscellaneous 3.1 Product and Service Technical Library For a complete and up-to-date source of DB2 information, including information on issues discovered after this readme was published, use the Product and Service Technical Library on the World Wide Web at: http://www.software.ibm.com/data/db2/library 3.2 Customer Support To speak to an IBM representative regarding assistance with this product, please call 1-800-CALL-AIX (1-800-225-5249). Customer support is also provided via Electronic Question and Answer (Q&A) forums. These forums are accessible through CompuServe, IBMLink, and Usenet Newsgroup. (1) CompuServe - To access the forums on CompuServe, execute GO IBMDB2. - If you don't have access to CompuServe, call 1-800-848-8199 for membership information in Canada or the US. (2) Usenet Newsgroup: comp.databases.ibm-db2 - This Internet Newsgroup is a general forum for discussing questions and/or problems encountered using the DB2 family of products. (3) (IBMLink) Talklink OS/2 BBS - To access the forums on IBMLink, go to the OS2BBS section. - If you don't have access IBMLink, call 1-800-547-1283 for membership information in Canada or the US. 3.3 Corrective Service Corrective service can be downloaded electronically from the Internet by either: (1) FTP to anonymous server ftp.software.ibm.com (previously known as ps.boulder.ibm.com) at 198.17.57.66. Go to ps/products/db2/fixes/%L/%P/ where %L is the appropriate locale (e.g. english-us, spanish, german, etc.), and %P is the product name/version (eg. db22v5, db2aixv5, etc.). or: (2) Use a World Wide Web (WWW) browser to connect to the DB2 Service and Support Page at: http://www.software.ibm.com/data/db2/db2tech/index.html If you do not have access to any of the above locations, please call 1-800-CALL-AIX (1-800-225-5249) to request these FixPaks be sent to you in the mail. For countries other than US and Canada, please contact your local DB2 Customer Service number for assistance in obtaining them. 3.4 DB2/NT UDB EEE Support with Multiple Communication Adapters and TCP/IP Addresses A Windows NT server can support: o A single communication adapter configured with one or more TCP/IP addresses o Multiple communication adapters each configured with one or more TCP/IP addresses However each Windows NT server can only be configured with a single hostname. When resolving the hostname to a TCP/IP address, the resulting TCP/IP address will not necessarily correspond to the hostname/address pair at the Domain Name server. (On the local system it may have multiple TCP/IP addresses to choose from.) The DB2 Fast Communications Manager (FCM) listens on a TCP/IP port that is bound to a specific TCP/IP address. To ensure that all systems in a DB2 EEE environment use the correct TCP/IP address, the Network Name field in the node configuration must be specified using a TCP/IP address. To update the Network Name use the db2nchg command as follows: db2nchg /n: /g: [ /i: ] where: /n: : the node number to modify /g: : the hostname or tcp/ip address for the FCM With multiple TCP/IP addresses and/or multiple TCP/IP adapters you should use TCP/IP addressing to specify the net_name parameter. For example: db2nchg /n:1 /g:9.2.26.61 /i:DB2MPP You can verify the current settings for the nodes by using the db2nlist command. If DB2 EEE is used in conjunction with Microsoft Cluster Server (MSCS) to provide high availablity, then a MSCS IP address resource must be used by the FCM. That is, a IP address resource must be created in the failover group and the TCP/IP address associated with the IP address resource must be used as the Network Name for the DB2 node. Alternatively a pre-online script may be used to modify the node configuration during failover. For example: @echo off echo Pre-online script for node "%DB2NODE%" running on machine "%COMPUTERNAME%" if "%COMPUTERNAME%" == "WOLF_NODE_0" goto wolf_node_0 if "%COMPUTERNAME%" == "WOLF_NODE_1" goto wolf_node_1 echo Error ! No script for this computer goto end :wolf_node_0 echo db2nchg /n:%DB2NODE% /g:9.9.9.2 db2nchg /n:%DB2NODE% /g:9.9.9.2 goto end :wolf_node_1 echo db2nchg /n:%DB2NODE% /g:9.9.9.3 db2nchg /n:%DB2NODE% /g:9.9.9.3 goto end :end echo End of pre-online script 3.5 Maximum log file size for NT In the Configure Database notebook of the Version 5.2 Control Center, on the Logs page, the hint for the Log File Size (logfilsiz) parameter says the range for NT is [4 - 4095] Pages(4KB). For NT, the range is actually [4 - 65535] Pages(4KB), as stated in the Administration Guide. 3.6 Bufferpool configuration parameters There are a new set of bufferpool configuation parameters that exist to tune bufferpools and bufferpool related functions. Below is a list of the parameters and instructions for using them. 1) create a file 2) set the parameters (see details below) in the file as desired 3) db2set DB2BPVARS= 4) db2stop;db2start;db2 connect to Note: When first using these parameters it's strongly recommended to temporarily set the dbm config parm diaglevel set to 4 so that you see all (if any) the error messages for invalid or incorrect parameters. The currently supported parameters are (please note that parameters may be added or removed in future releases): Per bufferpool: (set with =VALUE,BPID for a single bufferpool or =VALUE,* for all bufferpools) NUMHATESTACKS= Valid values are 1 to 254. Default is 1. Specifies the number of stacks of victim pages that are kept. Recommended value is 1. CHNGPGS_THRESH= Valid values are 0 to 99.99. Default is CHNGPGS_THRESH db cfg value. Allows you to have different CHNGPGS_THRESH per bufferpool. Recommendation: do not set this value (ie rely on the db cfg value). Instance and database wide: (set with =VALUE) NT_SCATTER_SMS NT only: Valid values 0=OFF or 1=ON. Default is OFF (0) Can be used to turn scatter read on for SMS tablespaces. This can only be enabled (turned ON) if DB2NTNOCACHE is set on the registry. A warning message will be written to the db2diag.log if DB2NTNOCACHE is OFF (or not set), and scatter read will remain disabled. Recommendation: do not set this parameter (ie rely on the default). Caching is typically more important. NT_SCATTER_DMSFILE NT Only: Valid values 0=OFF or 1=ON. Default is OFF (0). Can be used to turn scatter read on for DMS file containers. This can only be enabled (turned ON) if DB2NTNOCACHE is set on the registry. A warning message will be written to the db2diag.log if DB2NTNOCACHE is OFF (or not set), and scatter read will remain disabled. Recommendation: do not set this parameter (ie rely on the default). Caching is typically more important. NT_SCATTER_DMSDEVICE NT Only: Valid values 0=OFF or 1=ON. Default is OFF (0) can be used to turn scatter read on for DMS device containers. This can only be enabled (turned ON) if DB2NTNOCACHE is set on the registry. A warning message will be written to the db2diag.log if DB2NTNOCACHE is OFF (or not set), and scatter read will remain disabled. Recommendation: Consider a value of 1 for systems with a large amount of sequential prefetching against DMS tablespaces with device containers. LOG_CFG=4 Level at which the variables set in this file will be logged to db2diag.log Here's an example file: # Number of prefetch queues NUMPREFETCHQUEUES=2 # Number of hate stacks NUMHATESTACKS=5,* # Turn on scatter read for DMS device containers NT_SCATTER_DMSDEVICE=1 # Diaglevel at which configuration written LOG_CFG=4 # Override the changed pages threshold for buffer pool 1 (eg IBMDEFAULTBP). CHNGPGS_THRESH=0.99,1 3.7 Automatic Summary Tables 'Refresh Immediate' Automatic Summary Tables (ASTs) can be created by joining two or more tables. (In the past, each AST could reference only one table.) 3.8 Correction of CREATE TABLE statement In the CREATE TABLE IN tablespace1 statement, the algorithm for determining the tablespace chosen should read as follows: IF table space in the IBMDEFAULTGROUP nodegroup over which the user has USE privilege exists with sufficient page size THEN use it ELSE IF a table space over which the user has USE privilege exists with sufficient page size THEN use it ELSE issue an error (SQLSTATE 42727). 3.9 New DB2 CLP option A new db2 clp command line option -n has been added. This was first added in FP11 but now with improved behaviour in this interim. This option strips the newline character from a token running into more than one line, and concats the token without a space in between. For example, if the token is "xxxxx\nyyyyy", then, by using the new command line option 'n', the output would be "xxxxxyyyyy" instead of "xxxxx yyyyy", which is the current behaviour. The improvement in the interim is this: The trailing spaces before the newline will be maintained, earlier they were being stripped. --------------------------------------------------------------------------- * are trademarks or registered trademarks of IBM Corporation. ** are trademarks or registered trademarks of their respective owners. --------------------------------------------------------------------------- *************************************************************************** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2001. ** ALL RIGHTS RESERVED. ** ***************************************************************************