IBM DB2 DB2 CONNECT RELEASE NOTES VERSION 5.2 FIXPAK 17 Document Number READDCS READDCS ---------------------------------------------------------------------- IBM DB2 DB2 CONNECT RELEASE NOTES (C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1999. ALL RIGHTS RESERVED. Before using this information and the product it supports, be sure to read the general information under Appendix A, "Notices." Contents WELCOME TO THE DB2 CONNECT VERSION 5.2 RELEASE NOTES! How This Document is Structured 1.0 GENERAL INFORMATION ABOUT DB2 CONNECT VERSION 5.2, FIXPAK 17 1.1 DB2 Technical Library 1.2 DB2 Service News Mailing Lists 1.2.1 Frequency of Mailings 1.2.2 Which Lists Should I Subscribe To? 1.2.3 Ways To Subscribe 1.2.4 Subscribing Manually 1.2.5 Unsubscribing 1.3 PTF Numbers for DB2 UDB FixPaks 6 and 17 1.4 APPC, CPI-C, and SNA Sense Codes Documentation 1.5 Red Book on Load Balancing DB2 Connect with Internet Network Dispatcher 1.6 Application Programming Enhancements 1.7 DB2 Connect for Personal Communications 1.8 Clarification to What's New Information about DRDA Syncpoint Manager 2.0 CHANGES TO DB2 CONNECT QUICK BEGINNINGS MANUALS 2.1 Recommended Software Fix Levels for Host and AS/400 Systems 2.1.1 Host and AS/400 Database Servers 2.1.2 Workstation Software Considerations 2.2 Bidirectional CCSID Support for DB2 Connect 2.2.1 Implementation 2.3 Providing Reasons for Security Failures on Windows 95, 98, and NT 2.4 DCE Support on Windows 95 and Windows NT 2.5 Client Configuration Assistant - Supported SNA Subsystems 2.6 IBM Communications Server for Windows NT 2.6.1 SNA API Client - Application does not restart 2.6.2 Using GUI Applications with Communications Server for Windows NT SNA API Client 2.7 Shared Memory Addresses - Windows NT 2.8 Message SQL30081N may be issued incorrectly instead of SQL30082N 2.9 Running DB2 Connect Personal Edition from a File Server 2.10 Changes to CATALOG DCS DATABASE Command Syntax 2.11 CCA Limitations and Defaults 2.12 SYSPLEX Information 2.13 Updated Information About Transaction Managers 2.14 Configuring IBM eNetwork Communications Server for SCO Unixware 2.15 Cataloging the SPM on Remote Clients 2.16 Log Path Parameter for the Syncpoint Manager 2.17 Message SQL1651, SQL5048N or SQL0901 Using Change Password Support 2.18 New CATALOG_NOAUTH Configuration Parameter 2.19 Changing Your MVS Password - Correction 3.0 CHANGES TO THE DB2 CONNECT USER'S GUIDE 3.1 CATALOG DCS DATABASE - Undocumented Parameter CHGPWD_SDN 3.2 CATALOG DCS DATABASE - Undocumented Parameter BIDI 3.3 Using Microsoft Access with DB2 Connect 3.4 Security -- Password Encryption APPENDIX A. NOTICES A.1 Trademarks A.2 Trademarks of Other Companies Welcome to the DB2 Connect Version 5.2 Release Notes! Set the font to monospace for better viewing of these Release Notes. This document, READDCS.TXT, contains Release Notes for Version 5.2 PLUS FIXPAK 17 of the following products (see 1.3, "PTF Numbers for DB2 UDB FixPaks 6 and 17"): o DB2 Connect Enterprise Edition Version 5.2 for AIX, HP-UX, SCO UnixWare, Solaris, OS/2, and Windows NT (formerly known as Distributed Database Connection Services (DDCS) Multi-user Gateway). o DB2 Connect Personal Edition Version 5.2 for OS/2, Windows 3.1, Windows 3.11 for Workgroups, Windows 95, Windows 98, and Windows NT (formerly known as DDCS Single-User). NOTE: This FixPak cannot be installed on top of existing DB2 UDB v5.0 code. You must be at DB2 Connect v5.2 level. In order to get to this v5.2 level, you can download and install FixPak 6. Once this is installed, you can then apply FixPak 17 on top of that new level. Some of the information in these Release Notes also pertains to users of the following products: o DB2 Universal Database Enterprise Edition Version 5.2, when the DB2 Connect component has been installed. o DB2 Universal Database Extended - Enterprise Edition Version 5.2, when the DB2 Connect component has been installed. o DB2 Connect for IBM eNetwork Personal Communications for Windows 95 and Windows NT. NOTE: If you have just installed DB2 Connect Version 5.2, the following document also contains information relevant to DB2 Connect customers: o RELEASE.TXT - the Release Notes for DB2 UDB Version 5.2. This file can be found in the directory where DB2 is installed. How This Document is Structured These Release Notes contain the following sections: o 1.0, "General Information About DB2 Connect Version 5.2, FixPak 17" o 2.0, "Changes to DB2 Connect Quick Beginnings Manuals" o 3.0, "Changes to the DB2 Connect User's Guide" 1.0 General Information About DB2 Connect Version 5.2, FixPak 17 Note: There are no additional changes for FixPak 17, except the PTF numbers for each platform (see section 1.3). This section lists general considerations affecting all users of DB2 Connect Version 5.2 products, as well as users of DB2 UDB Enterprise Edition and DB2 UDB Extended - Enterprise Edition connecting to host and AS/400 databases, and DB2 Connect for Personal Communications. 1.1 DB2 Technical Library The latest technical information about DB2 products, and many additional usage hints and tips, can be found in the DB2 Technical Libary on the World Wide Web. To access this: 1. Set your Web browser to the URL "http://www.software.ibm.com/data/db2/library". 2. Register as a user if you have not already done so. Use of the library is free. 3. Select "DB2 Universal Database" 4. Select the categories of information that you wish to search, for example "Technical Notes". 5. Enter a search keyword, such as "DB2 Connect" (only multi-word phrases require quotation marks). 6. Click on "Search". For example, some Technotes you can locate using the search argument "DB2 Connect" include: o How to Configure IBM PComm and Communications Server for Windows NT and 95 o How to Configure Microsoft SNA Server V3.0 for DDCS for NT V2.3.2 or DB2 Connect V5.0 o SNA Performance Tuning Tips for DDCS and DB2 Connect o Tuning ODBC/CLI Application Performance With CLI Keywords 1.2 DB2 Service News Mailing Lists The DB2 Service and Support Team has established three Internet mailing lists to keep DB2 users up-to-date on fixes and updates to DB2 products. The mailing lists provide subscribers with a summary of fix packs, PTFs, and other updates to DB2 products as they become available. They also provide subscribers with news about other DB2 service offerings and other items which may be of interest to DB2 customers. 1.2.1 Frequency of Mailings Mailings for each list will be sent out approximately four times a year, plus an occasional extra edition. You will not receive any other e-mail from these subscription lists, and IBM will not give or sell your user ID to any other list. 1.2.2 Which Lists Should I Subscribe To? There are presently three mailing lists available: db2udb-news - DB2 Universal Database Version 5 Service news db2v2-news - DB2 common server Version 2 Service news db2v1-news - DB2 Parallel Edition Version 1 Service news Users should subscribe to only those lists that address the products that they are using. For example, users running both DB2 Universal Database Version 5 and DB2 Parallel Edition Version 1 servers with both Version 2 and Version 5 clients should subscribe to all three lists. Users running only Version 5 servers and clients should subscribe to only the db2udb-news list. 1.2.3 Ways To Subscribe There are two ways to subscribe to these lists: 1.Request to be automatically subscribed to these lists when you become a registered user of the DB2 Library. 2.Subscribe manually. 1.2.4 Subscribing Manually To subscribe manually to any of these lists send an e-mail to majordomo@mail.software.ibm.com with the subscribe command and a list of the mailing lists to which you wish to subscribe, followed by the word end, as shown below. For example, to subscribe to just the DB2 Universal Database Version 5 list: To: majordomo@mail.software.ibm.com subscribe db2udb-news your@email.address.here end 1.2.5 Unsubscribing There is only one way to unsubscribe from these lists. To unsubscribe from any of these lists send an e-mail to majordomo@mail.software.ibm.com with the unsubscribe command and a list of the mailing lists to which you wish to subscribe, followed by the word end. For example, to unsubscribe from all three lists, To: majordomo@mail.software.ibm.com unsubscribe db2v1-news your@email.address.here unsubscribe db2v2-news your@email.address.here unsubscribe db2udb-news your@email.address.here end 1.3 PTF Numbers for DB2 UDB FixPaks 6 and 17 FixPak 17 is intended to be installed on top of DB2 Connect Version 5.2, which is itself equivalent to DB2 Connect Version 5.0 with FixPak 6 installed. The table below lists the PTF numbers by operating system for FixPak 17. +--------------------------------------------------------------------+ | Table 1. PTF Numbers for DB2 UDB FixPak 17 | +----------------------------------+---------------------------------+ | OPERATING SYSTEM | PTF NUMBER FOR DB2 UDB FIXPAK 17| +----------------------------------+---------------------------------+ | AIX | U480105 | +----------------------------------+---------------------------------+ | HP-UX v10 | U480152 | +----------------------------------+---------------------------------+ | OS/2 | WR21287 | +----------------------------------+---------------------------------+ | Solaris | U480151 | +----------------------------------+---------------------------------+ | Windows 95, Windows 98, and | WR21288 | | Windows NT | | +----------------------------------+---------------------------------+ | Windows 3.1 and Windows for | WR21289 | | Workgroups 3.11 | | +----------------------------------+---------------------------------+ | SCO | U480154 | +----------------------------------+---------------------------------+ | SGI | U480155 | +----------------------------------+---------------------------------+ Some incorrect PTF numbers were included in the readme files for DB2 Connect Version 5.2. Below are the correct PTF numbers by operating system for FixPak 6: +--------------------------------------------------------------------+ | Table 2. PTF Numbers for DB2 UDB FixPak 6 | +----------------------------------+---------------------------------+ | OPERATING SYSTEM | PTF NUMBER FOR DB2 UDB FIXPAK 6 | +----------------------------------+---------------------------------+ | AIX | U459852 | +----------------------------------+---------------------------------+ | HP-UX v10 | U459854 | +----------------------------------+---------------------------------+ | OS/2 | WR09073 | +----------------------------------+---------------------------------+ | Solaris | U459853 | +----------------------------------+---------------------------------+ | Windows 95, Windows 98, and | WR09074 | | Windows NT | | +----------------------------------+---------------------------------+ | Windows 3.1 and Windows for | WR09076 | | Workgroups 3.11 | | +----------------------------------+---------------------------------+ DB2 Connect FixPaks are normally cumulative. FixPak 17, however, can only be installed on top of DB2 Connect v5.2, hence it is not cumulative. Version 5.2 is the baseline installation for all subsequent FixPaks including future cumulative FixPaks. 1.4 APPC, CPI-C, and SNA Sense Codes Documentation The documentation on APPC, CPI-C, and SNA Sense Codes that was provided with DB2 Common Server Version 2 in the online-viewable IPF book with file name DB2APPC.INF has been repackaged. The new version of this documentation is provided as a PostScript file, and an HTML book (English only). The PostScript version of this book can be found on your DB2 Version 5.2 CD in the "\doc\en\ps" directory, The file name is as follows: o "db2ape51.ps.Z" on UNIX based operating systems (use uncompress to create the printable file) o "db2ape51.psz" on OS/2 and Windows operating systems (use PKUNZIP). The HTML copy of this book is always installed when DB2 Connect is installed, and this book is now integrated with the DB2 Information Center. 1.5 Red Book on Load Balancing DB2 Connect with Interactive Network Dispatcher The "red book" "IBM Interactive Network Dispatcher: Load-Balancing Internet Servers", SG24-4993, is helpful in setting up IND to load balance multiple DB2 Connect gateways. o The Interactive Network Dispatcher has recently been renamed "eNetwork Dispatcher"; however, the title of the red book has been retained in current editions. eNetwork Dispatcher and Interactive Network Dispatcher are one and the same product. See also "http://www.redbooks.ibm.com/redpieces.html" for information about other upcoming "red books". 1.6 Application Programming Enhancements In general all application programming-related enhancements to the DB2 CAE, JDBC, and ODBC API also apply to DB2 Connect. This includes Java applets, JDBC, and the JDBC server. 1.7 DB2 Connect for Personal Communications DB2 Connect for Personal Communications is a component of IBM eNetwork Personal Communications for Windows 95 and Windows NT. It provides many of the functions available with the DB2 Connect Personal Edition with the following limitations: o Native TCP/IP connectivity to AS/400 and host DB2 databases is not supported. o A maximum of 6 concurrent database connections can be open at the same time. o The ability to update multiple databases as part of the same transaction (2-phase commit) is not supported. IBM eNetwork Personal Communications customers that need these additional functions should upgrade to DB2 Connect Personal Edition or DB2 Connect Enterprise Edition products. 1.8 Clarification to What's New Information about DRDA Syncpoint Manager The DB2 UDB V5.2 "What's New" document mentions new functions provided by the DRDA Syncpoint Manager (SPM). These new functions apply to the following products on their supported operating systems: o DB2 Connect Enterprise Edition Version 5.2, on AIX, HP-UX, OS/2, Solaris, SCO UnixWare, and Windows NT o DB2 Universal Database Enterprise Edition Version 5.2, on AIX, HP-UX, OS/2, Solaris, SCO UnixWare, and Windows NT o DB2 Universal Database Enterprise - Extended Edition Version 5.2, on AIX, Solaris, and Windows NT. Customer applications which use an XA compliant transaction manager can now access host and AS/400 database servers via TCP/IP as well as SNA on all platforms, using multisite update (two phase commit). The DB2 Syncpoint Manager has been enhanced to allow this access. 2.0 Changes to DB2 Connect Quick Beginnings Manuals This section lists changes to the DB2 Connect Quick Beginnings manuals. The same considerations also apply to users of DB2 Connect for Personal Communications. 2.1 Recommended Software Fix Levels for Host and AS/400 Systems 2.1.1 Host and AS/400 Database Servers This section provides information about host and AS/400 database access using DB2 Connect or DB2 UDB. 2.1.1.1 DB2 UDB APAR IX73249 If you receive the following message in your DB2 diagnostic log: Contact DB2 Service and ask about APAR IX73249 then ensure you apply the latest service level to your host or AS/400 system as outlined in the remainder of this section. 2.1.1.2 Software Prerequisites for the SPM The list of host and AS/400 server maintenance provided in Chapter 24 "Enabling the DB2 Syncpoint Manager" of the DB2 Connect Enterprise Edition Quick Beginnings manual also applies in non-SPM situations. This affects all users of DB2 Connect. In some editions of this book the list may be formatted incorrectly. The list items "Windows NT SNA Connectivity" and "DB2 for MVS/ESA or DB2 for OS/390" should be at the same level as "OS/2 SNA Connectivity", and the contents of their subordinate lists should be one level higher in the parent unordered list. See also "AS/400 Software Prerequisite for Syncpoint Manager (SPM)." 2.1.1.3 DB2 for AS/400 RECOMMENDED FIXES FOR DB2 FOR AS/400: The following PTFs are recommended: +--------------------------------------------------------------------+ | Table 3. Recommended fixes for DB2 for AS/400 | +-----------------------------+-------------------+------------------+ | PROJECT | RELEASE | PTF | +-----------------------------+-------------------+------------------+ | 5763SS100 | VRM320 | SF46696 | +-----------------------------+-------------------+------------------+ | 5716SS100 | VRM370 | SF46697 | +-----------------------------+-------------------+------------------+ | 5769SS100 | VRM410 | SF46698 | +-----------------------------+-------------------+------------------+ | 5769SS100 | VRM420 | SF46350 | +-----------------------------+-------------------+------------------+ AS/400 SOFTWARE PREREQUISITE FOR SYNCPOINT MANAGER (SPM): In the manual DB2 Connect Enterprise Edition Quick Beginnings, in Chapter 24 "Configuring the DB2 Syncpoint Manager", the PTF SF27513 listed for DB2/400 V3R1 has been superseded by PTF number SF28227 (fixes for APAR SA48935). 2.1.1.4 DB2 for MVS and DB2 for OS/390 DB2 FOR OS/390 PREREQUISITE MAINTENANCE AND INFORMATIONAL APARS: The following informational APARS for DB2 for OS/390 are regularly updated with information about PTFs to install for various OS/390 components, particularly TCP/IP for OS/390. If you use TCP/IP connectivity with DB2 for OS/390 it is extremely important that you review and apply PTFs and APAR fixes described in the following DB2 for OS/390 information APARs: II11164 II11263 II10962 RECOMMENDED FIXES FOR DB2 FOR OS/390: o DB2 for MVS Version 3.1: PTF UQ13906 o DB2 for MVS Version 4.1: PTF UQ13907 o DB2 for OS/390 Version 5.1: PTF UQ13908, PTF UQ17755 2.1.2 Workstation Software Considerations This section of the Release Notes provides information about required software levels for communications subsystems and other workstation software required by DB2 Connect, and DB2 Universal Database (Workgroup Edition, Enterprise Edition, or Extended - Enterprise Edition). 2.1.2.1 IBM eNetwork Communications Server for AIX Version 5 The following APAR fixes for IBM eNetwork Communications Server for AIX Version 5 are required in order for DB2 Connect V5.2 to work: APAR IX76764 APAR IX77566 APAR IX77539 APAR IX82759 PTF U459869 2.1.2.2 IBM Communications Server for Windows NT Customers using IBM Communications Server for Windows NT (CS/NT) Version 5 should apply APAR fixes JR11529 and JR11170. These fixes are required to enable cancelling of queries in progress by using Ctrl+BREAK or issuing the SQLCancel ODBC/CLI call. 2.1.2.3 Microsoft SNA Server Version 4.0 Users may encounter problems when configuring CPIC Side information profiles in the CPIC Side Information Profile dialog box. This is a known bug in Microsoft SNA Server Version 4.0. In order to ensure a correct configuration users should specify a valid LU Alias rather than a fully qualified LU Name in the CPIC Side Info Profile dialog box. 2.2 Bidirectional CCSID Support for DB2 Connect The following Bidirectional (BiDi) attributes are required for correct handling of BiDi data on different platforms: o Text type (LOGICAL vs VISUAL) o Shaping (SHAPED vs UNSHAPED) o Orientation (RIGHT-TO-LEFT vs LEFT-TO-RIGHT) o Numeral shape (ARABIC vs HINDI) o Symmetric swapping (YES or NO) Since defaults on different platforms are not the same, problems appear when DB2 data is sent from one platform to another. For example, Windows platforms use LOGICAL UNSHAPED data, while data on MVS and OS/390 is usually in SHAPED VISUAL format. Therefore, without any support for BiDi attributes, data sent from DB2 for MVS or OS/390 to DB2 Connect on Windows, displays incorrectly. When data is exchanged between DB2 Connect and a database on a server, it is usually the receiver that performs conversion on the incoming data. The same convention would normally apply to BiDi layout transformation also, which is in addition to the usual code page conversion. However, currently no host DB2 product supports BiDi-specific CCSIDs or BiDi layout transformation. Therefore, DB2 Connect 5.2 has been enhanced with the optional ability to perform BiDi layout transformation on data it is about to send to the server database in addition to data received from the server database. 2.2.1 Implementation In order for DB2 Connect to perform BiDi layout transformation on outgoing data to a server database, the BiDi CCSID of the server database will have to be overridden (see Note 1). This is accomplished through the use of the new BIDI parameter in the PARMS field of the DCS database directory entry for the server database. The BIDI parameter is to be specified as the ninth parameter in the PARMS field along with the BiDi CCSID with which the user would like to override the default server database BiDi CCSID in the following format: ",,,,,,,,BIDI=xyz" where xyz is the CCSID override (see Note 2 below). For a list of what BiDi CCSIDs are supported along with their string types, please refer to the IBM DB2 Universal Database Administration Guide. The use of this feature is best illustrated with an example. Suppose you have a Hebrew DB2 client running CCSID 62213 (BiDi string type 5) and you would like to access a DB2 host database running CCSID 424 (BiDi string type 4). However, you know that the data contained in the DB2 host database is instead based on CCSID 8616 (BiDi string type 6). There are two problems in this situation. Problem one is that the DB2 host database does not know the difference in the BiDi string types with CCSIDs 424 and 8616. The second problem is that the DB2 host database does not recognize the DB2 client CCSID of 62213. It only supports CCSID 862, which is based on the same code page as CCSID 62213. You will need to make sure that data sent to the DB2 host database is in BiDi string type 6 format to begin with and also let DB2 Connect know that it has to perform BiDi layout transformation on data it receives from the DB2 host database. You will use the following cataloging for the DB2 host database: catalog dcs database nydb1 as TELAVIV parms ",,,,,,,,BIDI=8616" See also 2.11, "CCA Limitations and Defaults." What this does is tell DB2 Connect to override the DB2 host database CCSID of 424 with 8616. This override includes the following processing: 1. DB2 Connect will connect to the DB2 host database using CCSID 862. 2. DB2 Connect will perform BiDi layout transformation on data it is about to send to the DB2 host database from CCSID 62213 (BiDi string type 5) to CCSID 62221 (BiDi string type 6). 3. DB2 Connect will perform BiDi layout transformation on data it receives from the DB2 host database from CCSID 8616 (BiDi string type 6) to CCSID 62213 (BiDi string type 5). NOTES: 1. Please note that if you would like DB2 Connect to perform layout transformation on data it is about to send to the DB2 host database even though you do not have to override its CCSID, you still have to add the BIDI parameter in the DCS database directory PARMS field. In this case, the CCSID that you should provide would be the default DB2 host database CCSID. 2. The environment variable or registry value DB2BIDI has to be set to YES in order for the BIDI parameter to take effect. 3. In some cases, use of a bidirectional CCSID may cause the SQL query itself to be modified such that it is not recognized by DB2 server. Specifically, you should try to avoid using IMPLICIT CONTEXTUAL and IMPLICIT RIGHT-TO-LEFT CCSIDs when a different string type can be used. CONTEXTUAL CCSIDs can produce unpredictable results if the SQL query contains quoted strings. Avoid using quoted strings in SQL statements, and use host variables instead when possible. If a specific bidirectional CCSID is causing problems which cannot be rectified by following these recommendations, then you should set DB2BIDI=NO. 4. See also 2.11, "CCA Limitations and Defaults" for information about setting parameter values for DCS directory entries. 2.3 Providing Reasons for Security Failures on Windows 95, 98, and NT DB2 for OS/390 Version 5.1 can be configured to provide detailed information when security failures occur. For example, the user can be informed that a connection failed because the password has expired or because the user ID is locked out. For DB2 systems connected via SNA this information is transmitted using extended SNA Security Codes. Extended SNA Security Codes are not implemented by some SNA subsystem providers. This may affect customers using one or more of the following: o DB2 Universal Database (UDB) for Windows NT Version 5 (all editions). o DB2 Connect Enterprise Edition for Windows NT Version 5 o DB2 Connect Personal Edition Version 5 (when running on Windows 95, Windows 98, or Windows NT). DB2 will attempt to load db2cpic2.dll in order to support Extended SNA Security Codes in these environments. The new DLL was originally packaged with FixPak 1 for DB2 Universal Database Version 5. It is identical to the original DLL db2cpic.dll, except that it includes a call to extract secondary information (cmesi()). +--------------------------------------------------------------------+ | Table 4. Which version of db2cpic.dll is loaded by DB2? | +----------------------+----------------------+----------------------+ | IF YOU HAVE THIS SNA | ON WINDOWS NT, DB2 | ON WINDOWS 95 OR 98, | | SUBSYSTEM | LOADS | DB2 LOADS | +----------------------+----------------------+----------------------+ | IBM Communications | db2cpic2.dll (new) | db2cpic.dll (old) | | Server for Windows | | | | NT | | | +----------------------+----------------------+----------------------+ | IBM Personal | db2cpic2.dll | db2cpic.dll | | Communications for | | | | Windows (see note | | | | below) | | | +----------------------+----------------------+----------------------+ | Microsoft SNA Server | db2cpic.dll | db2cpic.dll | +----------------------+----------------------+----------------------+ | Wall Data RUMBA | db2cpic2.dll | db2cpic2.dll | | Office | | | +----------------------+----------------------+----------------------+ | DB2 Connect | db2cpic2.dll | db2cpic2.dll | | Integrated SNA | | | | Support | | | +----------------------+----------------------+----------------------+ If DB2 fails to load db2cpic2.dll, you can do the following in the directory where it has been installed: copy db2cpic2.dll db2cpic2.bak copy db2cpic.dll db2cpic2.dll This will make db2cpic2.dll the same as db2cpic.dll. NOTE: If you wish to use Extended Security Support with DB2 UDB Version 5.2 on Windows 95, we recommend using IBM Personal Communications (PComm) for Windows 95 Version 4.2 (not Version 4.1). Copy db2cpic.dll to db2cpic.bak and copy db2cpic2.dll to db2cpic.dll. This will make db2cpic.dll the same as db2cpic2.dll. 2.4 DCE Support on Windows 95 and Windows NT DB2 Universal Database and DB2 Connect Version 5.2 now provide support for: o Gradient DCE CDS on Windows NT and Windows 95 o IBM DCE CDS on Windows NT Two new DLLs have been provided: o db2dce.grd for Gradient DCE CDS o dcedce.ibm for IBM DCE CDS By default, "db2dce.grd" has been copied to "db2dce.dll." NOTE: DB2 will only load "db2dce.dll." You must copy "dcedce.ibm" to "db2dce.dll" if you want to use IBM DCE CDS. In addition to the existing support using APPC, IPX/SPX, NETBIOS, and TCP/IP, support for DCE using the Named Pipes (NPIPE) networking protocol is now provided. A control statement similar to the following example may now also be specified for a DCE object having the DB_Communication_Protocol attribute, with value: NPIPE;Computer_name;Instance_name To use IBM DCE security you must copy db2dcec.ibm to db2dcec.dll and db2dces.ibm to db2dces.dll. 2.5 Client Configuration Assistant - Supported SNA Subsystems On Windows NT, Windows 95, or Windows 98, when adding a database using APPC as the protocol, the Client Configuration Assistant (CCA) supports configuration of the SNA stack with: o DB2 Connect Integrated SNA Support o Wall Data RUMBA Office o IBM eNetwork Personal Communications for Windows 95 and Windows NT Version 4.2 o IBM Communications Server for Windows NT Version 5. Similar support is also provided on OS/2 when using IBM eNetwork Communications Server for OS/2 Version 5, IBM Communications Server for OS/2 Version 4, or IBM Communication Manager for OS/2 Version 1.11. 2.6 IBM Communications Server for Windows NT 2.6.1 SNA API Client - Application does not restart When using IBM Communications Server for NT, the application might not restart correctly after the SNA API Client connection to the server is lost. Most likely the SNA API Client DLLs and executables have not unloaded correctly from memory. In this case, the application may not restart even after the connection is re-established. If this occurs, the SNA API Client executables should be manually terminated. On Windows 95 or Windows NT there is a command-line utility called RESETAPI.EXE which can be used to terminate the SNA API Client DLLs and executables. This does not require a reboot of the client. This utility is installed with the SNA API client. The following is a list of SNA API Client DLLS and executables which might need to be terminated in such cases of abnormal termination of the application: o ATTMSG.EXE o ATTMGR.EXE o EHNAPPCD.EXE o EHNMGT2.EXE o LU62DIAL.EXE o LU62MGR.EXE Please also refer to the README file for IBM Communications Server for Windows NT. 2.6.2 Using GUI Applications with Communications Server for Windows NT SNA API Client In order to connect properly using IBM Communications Server for Windows NT SNA API Client, you should start the APING application prior to starting any GUI application that will connect via APPC. Such GUI applications include the Client Configuration Assistant, Control Center, and any ODBC GUI applications. 2.7 Shared Memory Addresses - Windows NT For Windows NT, in the "Managing Instances" section of the Quick Beginnings manual, the following revised information applies. The default database manager shared memory address for Windows NT is x'20000000'. When using a DB2 Connect direct client connection to a host or AS/400 database server, a shared resource address collision may occur. To fix this problem, this value can be modified to force the database manager instance to allocate its shared memory at a different address. Use the DB2DBMSADDR registry profile variable to assign an address value in the range of x'20000000' to x'B0000000' using increments of x'4000000'. For example, try the values: x'24000000', x'28000000', x'2C000000', and so on. The value of DB2DBMSADDR is in hexadecimal format without the preceeding 0x and may be set using the db2set profile registry command. For example, to set DB2DBMSADDR to x'24000000', use the following command: db2set DB2DBMSADDR=24000000 Note, the value should not be modified for Windows 95/98 since no address collision will occur. 2.8 Message SQL30081N may be issued incorrectly instead of SQL30082N When attempting an SNA connection to DB2 for OS/390 Version 5.1 from DB2 Connect Version 5, if an incorrect password is used, message SQL30081N may be issued incorrectly instead of message SQL30082N. This can occur in the following environments when using DB2 Connect Version 5 (Enterprise Edition or Personal Edition): o HP-UX with SNAPlus2 o Solaris with SunLink o Windows NT with DB2 Connect Integrated SNA Support, Wall Data RUMBA Office, or Microsoft SNA Server for Windows NT o Windows 95 or Windows 98 with DB2 Connect Integrated SNA Support, Wall Data RUMBA Office, IBM Communications Server for Windows NT SNA API Client, or IBM Personal Communications for Windows. For example, after issuing the following command: db2 connect to DBALIAS user USERID using BADPASSW you may receive: o On HP-UX, SQL30081N with rc=20. o On Solaris, SQL30081N with rc=26. o On Windows NT, SQL30081N with rc=24. On HP-UX, the unexpected message is: SQL30081N A communication error has been detected. Communication protocol being used: "APPC". Communication API being used: "CPI-C". Location where the error was detected: "". Communication function detecting the error: "cmrcv". Protocol specific error code(s): "20", "*", "*". SQLSTATE=08001 The expected message would be: SQL30082N Attempt to establish connection failed with security reason "2" ("PASSWORD INVALID"). SQLSTATE=08001 These misleading messages are caused by limitations in the SNA stacks on the respective platforms. If you receive these messages, your first troubleshooting step should be to confirm that the correct password was used. 2.9 Running DB2 Connect Personal Edition from a File Server When DB2 Connect Personal Edition is configured to run from a file server only a very small set of files need be installed on each user's workstation. The majority of the files required for execution can be accessed from a file server where the full product is installed. It is important to understand that delays introduced by loading DB2 Connect programs from the file server can adversely impact application performance. Installing DB2 Connect Personal Edition in such a configuration is a two-step process. First, a copy of DB2 Connect Personal Edition must be installed on the file server. Then, for each user licensed to run DB2 Connect Personal Edition, the "thin" DB2 Connect client file set must be installed on each user workstation. An administrator must set up the DB2 Connect configuration on each user machine. Detailed instructions for preparing DB2 Connect Personal Edition for a file server installation can be found in the IBM white paper "Implementing Thin Connect Architecture in Windows 32-bit Operating Systems". This paper is available on the internet at "http://www.software.ibm.com/data/pubs/papers/thinconnect/". 2.10 Changes to CATALOG DCS DATABASE Command Syntax See 3.0, "Changes to the DB2 Connect User's Guide" in this document, and also 2.11, "CCA Limitations and Defaults," and 2.18, "New CATALOG_NOAUTH Configuration Parameter" below. 2.11 CCA Limitations and Defaults The Client Configuration Assistant (CCA) has been enhanced to set the CHGPWD_SDN parameter when defining DCS database entries in the DB2 catalog (see also 3.0, "Changes to the DB2 Connect User's Guide" in this document). Note that the CCA cannot be used to set some parameters for DCS directory entries, and that it also sets defaults. In most cases, if you need to set parameters for DCS database directory entries you must set them manually using the CATALOG DCS DATABASE command. See also 2.18, "New CATALOG_NOAUTH Configuration Parameter" below. If a DCS DATABASE directory entry already exists for which you need to specify additional parameters, for example an entry that has been created previously by the CCA, then the existing entry must be uncataloged manually, and the CATALOG DCS DATABASE command must be used to set it up again with the required parameters. We recommend the following manual procedure: 1. First LIST DCS DIRECTORY, and review the contents of existing entries. 2. UNCATALOG DCS DATABASE to remove each entry that you wish to modify. 3. CATALOG DCS DATABASE, specifying all the parameters that you require, including any values that may have been set by the CCA. NOTE: The CCA provides the following defaults: 1. When a host connection is specified, AUTHENTICATION defaults to DCS; and when the APPC protocol is used, SECURITY defaults to PROGRAM. 2. When a LAN connection is specified, AUTHENTICATION defaults to NOT SPECIFIED; and when the APPC protocol is used SECURITY defaults to NONE. 3. INTERRUPT_ENABLED is set as the default for host connections. Use the CATALOG DATABASE command to change AUTHENTICATION, and the CATALOG APPC NODE command to change the SECURITY value for APPC nodes. You must use the appropriate UNCATALOG commands first, in order to delete the existing entries which are to be replaced. Prior to uncataloging and recataloging, use LIST DCS DIRECTORY to review the contents of the catalog, as indicated above. If you are connecting to a DB2 Version 1 or 2 server, client AUTHENTICATION needs to be changed from NOT SPECIFIED to SERVER. The DB2 Connect Quick Beginnings manuals will be updated accordingly. This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties and any statements provided in this manual should not be interpreted as such. Order publications through your IBM representative or the IBM branch office serving your locality or by calling "1-800-879-2755" in U.S. or "1-800-IBM-4YOU" in Canada. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. (C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1998. ALL RIGHTS RESERVED. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. 2.12 SYSPLEX Information In some editions of the DB2 Connect Enterprise Edition Quick Beginnings manual, the order of topics in Appendix E "DB2 Connect SYSPLEX Support" may be wrong. The sample scenario may appear on the second page, and the descriptive overview of the function on the third page. Read the entire appendix. See also 3.0, "Changes to the DB2 Connect User's Guide" in this document. 2.13 Updated Information About Transaction Managers Appendix F of the DB2 Connect Enterprise Editions Quick Beginnings manual erroneously states that "MTS and DB2 Connect EE currently cannot be run on the same NT machine because they both try to use the same shared memory address." This information is incorrect. DB2 Connect and Microsoft Transaction Server can both be installed and run on the same Windows NT machine. The information on transaction managers in the DB2 Connect Quick Beginnings manuals, particularly that dealing with Microsoft Transaction Server, has been further updated and expanded. Please refer to Chapter 9 of the DB2 Administration Guide Version 5.2, "Using DB2 with an XA-compliant Transaction Manager" for a more up-to-date overview of transaction managers. 2.14 Configuring IBM eNetwork Communications Server for SCO Unixware A "Technote" will be provided containing the necessary information. Set your Web browser to http://www.software.ibm.com/data/db2/library and search for Technotes using the keyword SCO. 2.15 Cataloging the SPM on Remote Clients When documenting interactions between TP Monitors (for example CICS) and the DB2 Connect SPM, earlier versions of the manuals indicated correctly that - in situations where a DB2 Connect server is used - the SPM was required to be cataloged at the client. This is no longer necessary. The SPM does not need to be cataloged at the DB2 Client for normal operations. However, in situations when the client will be used to issue the DB2 LIST DRDA INDOUBT TRANSACTIONS command, then the remote SPM must still be cataloged on the client. This is necessary in order for the client to be able to connect to the SPM and execute the command. 2.16 Log Path Parameter for the Syncpoint Manager Chapter 24 of the DB2 Connect Enterprise Edition describes configuring the DB2 Syncpoint manager. An additional parameter has been added under the section entitled "Database Manager Configuration Parameters for SPM." This is the SPM_LOG_PATH parameter. SPM_LOG_PATH specifies the directory where the Syncpoint Manager (SPM) logs are written. By default, the logs are written to the "sqllib" directory, which in a high volume transaction environment can cause an I/O bottleneck. You may use this parameter to have the SPM logs written on another directory or disk. This allows for better concurrency among the SPM agents. 2.17 Message SQL1651, SQL5048N or SQL0901 Using Change Password Support If message SQL1651, SQL5048N or SQL0901 is encountered when using the Change Password support that is provided in DB2 Connect and DB2 UDB Version 5.2, the most likely cause of the error is that the release level of the database client is not supported by the release level of the database server. This message may be returned from a CONNECT or ATTACH request for which a new password was specified and AUTHENTICATION=CLIENT is being used. If so, verify that the local database catalog entry for the named database alias does not specify AUTHENTICATION=SERVER. If the above error is returned from a CONNECT OR ATTACH request with a new password for a DB2 Common Server V2 or DDCS Version 2 multi-user gateway, then the local database catalog entry for the database alias must specify AUTHENTICATION=CLIENT. 2.18 New CATALOG_NOAUTH Configuration Parameter In some operating environments message SQL01092 may be encountered when adding a database using the Client Configuration Assistant (CCA) or when using the CATALOG or UNCATALOG commands from a DB2 command window (CLP). This indicates that the user does not have a sufficient level of authorization to update the DB2 catalog. In order to avoid the need for a user to be an administrator when using commands such as CATALOG NODE, CATALOG DATABASE, and CATALOG DCS DATABASE, a new database manager configuration parameter has been introduced with DB2 Connect and DB2 UDB Version 5.2. The CATALOG_NOAUTH configuration parameter can now be set to YES in order to avoid the need for users to be administrators when updating the DB2 catalog. Refer to Chapter 20 of the DB2 Administration Guide for further information about CATALOG_NOAUTH. To set this parameter to YES, an administrator must issue the following command: db2 update dbm cfg using catalog_noauth yes 2.19 Changing Your MVS Password - Correction DB2 Connect Enterprise Edition, Appendix B, "Changing Your MVS Password", erroneously asserts that "Changing MVS passwords from DB2 Connect workstations connected to DB2 for OS/390 V5.1 TCP/IP does not require special set up on either MVS host or the DB2 Connect Workstation." In fact the MVS host requires that the DB2 OS/390 Extended Security Field be set to "Yes". This field appears in the DB2 OS/390 DSNTIPR panel. For more information, please refer to the DB2 for OS/390 Administration Guide, under "Allowing Users to Change Expired Password." 3.0 Changes to the DB2 Connect User's Guide This section lists changes to to the DB2 Connect User's Guide. 3.1 CATALOG DCS DATABASE - Undocumented Parameter CHGPWD_SDN In Chapter 3 of the DB2 Connect User's Guide, and in the DB2 Command Reference, the CHGPWD_SDN parameter of the CATALOG DCS DATABAS E command is not documented. CHGPWD_SDN is used to specify the symbolic destination name to be used for Password Expiration Management (PEM). It must be specified in the eighth positional parameter of the PARMS string, and the value is case sensitive. The appendix "Changing Your MVS Password" in the DB2 Connect "Quick Beginnings" manuals, Step 2 shows an example of cataloging a dcs database directory using CHGPWD_SDN, as follows: catalog dcs database db1 as dsn_db_1 parms ",,,,,,,CHGPWD_SDN=pempgm" Both the Command Reference and the DB2 Connect User's Guide will be updated t o include this new parameter. Note that the CCA has been enhanced in order to set CHGPWD_SDN when configuring SNA connections using Password Expiration Management. What the CCA does is that it sets up the necessary catalog directory entries for the connection. See also 2.11, "CCA Limitations and Defaults" for further discussion about cataloging DCS directory entries. 3.2 CATALOG DCS DATABASE - Undocumented Parameter BIDI In Chapter 3 of the DB2 Connect User's Guide, and in the DB2 Command Reference, the BIDI parameter the CATALOG DCS DATABASE command is not documented. See 2.2, "Bidirectional CCSID Support for DB2 Connect" for further information in this document. Both the Command Reference and the DB2 Connect User's Guide will be updated t o include this new parameter. See also 2.11, "CCA Limitations and Defaults," and 3.1, "CATALOG DCS DATABASE - Undocumented Parameter CHGPWD_SDN" above for further information about cataloging DCS database directory entries. 3.3 Using Microsoft Access with DB2 Connect For further information, please set your Web browser to "http://www.software.ibm.com/data/db2/library" and search for "Technotes" using the Keywords "Access" or "#Deleted". (Leave out the double-quotes). Also, if you are using Microsoft Access to access data from a DB2 for OS/390 database via DB2 Connect, and the DB2 for OS/390 database uses a double-byte character set code page (DBCS), then you need to ensure that no columns that are tagged as single byte character set (SBCS) contain DBCS characters. Otherwise, a translation error will occur (SQLCODE -332). For example, if the REMARKS column is tagged in the system catalog tables as SBCS, then no values of this column, in any rows, should contain DBCS characters. 3.4 Security -- Password Encryption There are two new values for AUTHENTICATION to support password encryption: SERVER_ENCRYPT and DCS_ENCRYPT. These have the same semantics as SERVER and DCS in terms of authentication location, except that any passwords which flow will be encrypted at the source and require decryption at the target as specified by the authentication type catalogued at the source. Encrypted and non-encrypted values with matching authentication locations can then be used to choose different encryption combinations between client and gateway or gateway and server, while not affecting where authentication takes place. Here are some examples of how this might be used in a gateway scenario : +---------------+---------------+---------------+---------------+---------------+ | Authentication| Authentication| Authentication| Client-Gateway| Gateway-Server| | at Client | at Gateway | Location | Encryption | Encryption? | | | | | ? | | +---------------+---------------+---------------+---------------+---------------+ | SERVER_ENCRYPT| SERVER | gateway | yes | no | +---------------+---------------+---------------+---------------+---------------+ | DCS_ENCRYPT | DCS | server | yes | no | +---------------+---------------+---------------+---------------+---------------+ | DCS | DCS_ENCRYPT | server | no | yes | +---------------+---------------+---------------+---------------+---------------+ | DCS_ENCRYPT | DCS_ENCRYPT | server | yes | yes | +---------------+---------------+---------------+---------------+---------------+ The only APPC security parameter supported when either SERVER_ENCRYPT or DCS_ENCRYPT are used is SECURITY=NONE. Appendix A. Notices Any reference to an IBM licensed program in this publication is not intended to state or imply that only IBM's licensed program may be used. Any functionally equivalent product, program or service that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility. IBM may have patents or pending patent applications covering subject matter 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 the o IBM Director of Licensing o IBM Corporation o North Castle Drive o Armonk, NY 10504-1785 o U.S.A. 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 which has been exchanged, should contact: o IBM Canada Limited o Department 071 o 1150 Eglinton Ave. East o North York, Ontario o M3C 1H7 o CANADA Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. This publication 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. A.1 Trademarks The following terms are trademarks or registered trademarks of the IBM Corporation in the United States and/or other countries: +----------------------------------+---------------------------------+ | ACF/VTAM | MVS/ESA | | ADSTAR | MVS/XA | | AISPO | NetView | | AIX | OS/400 | | AIXwindows | OS/390 | | AnyNet | OS/2 | | APPN | PowerPC | | AS/400 | QMF | | CICS | RACF | | C Set++ | RISC System/6000 | | C/370 | SAA | | DATABASE 2 | SP | | DatagLANce | SQL/DS | | DataHub | SQL/400 | | DataJoiner | S/370 | | DataPropagator | System/370 | | DataRefresher | System/390 | | DB2 | SystemView | | Distributed Relational Database A|cVisualAge | | DRDA | VM/ESA | | Extended Services | VSE/ESA | | FFST | VTAM | | First Failure Support Technology | WIN-OS/2 | | IBM | | | IMS | | | Lan Distance | | +----------------------------------+---------------------------------+ A.2 Trademarks of Other Companies The following terms are trademarks or registered trademarks of the companies listed: C-bus is a trademark of Corollary, Inc. HP-UX is a trademark of Hewlett-Packard. Java, HotJava, Solaris, Solstice, and Sun are trademarks of Sun Microsystems, Inc. Microsoft, Windows, Windows NT, Visual Basic, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation. PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license. SCO is a trademark of The Santa Cruz Operation. SINIX is a trademark of Siemens Nixdorf. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, or service names, which may be denoted by a double asterisk (**), may be trademarks or service marks of others. ---------------------------------------------------------------------- Part Number READDCS (C) Copyright IBM Corp. 1999 ----------------------------------------------------------------------