home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
db2sd71a.zip
/
READCON2.TXT
< prev
next >
Wrap
Text File
|
2000-05-10
|
9KB
|
204 lines
IBM* DB2* Connect Release Notes
------------------------------------------------------------------------
Table of Contents
IBM DB2 Connect Release Notes Version 7.1
* Please Review Information in RELEASE.TXT
* DB2's SNA SPM Fails to Start After Booting Windows
* Integrated SNA Support no longer Provided with DB2 Connect Personal
Edition for Windows V7.1
* Additional Patch Required for Solaris Version 2.6
* Terminal Server Application
* Limitations of JDBC/ODBC/CLI Static Profiling
* DB2 for OS/390(R) APAR Fix Prerequisites
o Kerberos and User ID Encryption
* Trademarks
------------------------------------------------------------------------
IBM DB2 Connect Release Notes Version 7.1
(C)Copyright International Business Machines Corporation 1996, 2000.
All rights reserved. Note to U.S. Government Users Restricted Rights --
Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
This file contains information about the following products that was not
available when the DB2 manuals were printed:
* IBM DB2 Connect Personal Edition, Version 7.1
* IBM DB2 Connect Enterprise Edition, Version 7.1
A separate installation notes file, installed as RELEASE.TXT, is provided
for the following products:
* IBM DB2 Universal Database Satellite Edition, Version 7.1
* IBM DB2 Universal Database Personal Edition, Version 7.1
* IBM DB2 Universal Database Workgroup Edition, Version 7.1
* IBM DB2 Universal Database Enterprise Edition, Version 7.1
* IBM DB2 Data Links Manager for AIX, Version 7.1
* IBM DB2 Data Links Manager for Windows NT, Version 7.1
* IBM DB2 Universal Database Enterprise - Extended Edition for AIX,
Version 7.1
* IBM DB2 Universal Database Enterprise - Extended Edition for Windows
NT, Version 7.1
* IBM DB2 Universal Database Enterprise - Extended Edition for the
Solaris Operating Environment, Version 7.1
* IBM DB2 Query Patroller for AIX, Version 7.1
* IBM DB2 Query Patroller for the Solaris Operating Environment, Version
7.1
* IBM DB2 Personal Developer's Edition, Version 7.1
* IBM DB2 Universal Developer's Edition, Version 7.1
A file that contains troubleshooting and other information about the
Control Center can be found at: sqllib/cc/prime/readme.htm.
The What's New book contains both an overview of some of the major DB2
enhancements for Version 7.1 and a detailed description of these new
features and enhancements.
------------------------------------------------------------------------
Please Review Information in RELEASE.TXT
RELEASE.TXT contains last minute information regarding DB2 Universal
Database. The majority of this information also applies to DB2 Connect.
------------------------------------------------------------------------
DB2's SNA SPM Fails to Start After Booting Windows
If you are using Microsoft SNA Server Version 4 SP3 or later, please verify
that DB2's SNA SPM started properly after a reboot. Check the
\sqllib\<instance name>\db2diag.log file for entries that are similar to
the following:
2000-04-20-13.18.19.958000 Instance:DB2 Node:000
PID:291(db2syscs.exe) TID:316 Appid:none
common_communication sqlccspmconnmgr_APPC_init Probe:19
SPM0453C Sync point manager did not start because Microsoft SNA Server has not
been started.
2000-04-20-13.18.23.033000 Instance:DB2 Node:000
PID:291(db2syscs.exe) TID:302 Appid:none
common_communication sqlccsna_start_listen Probe:14
DIA3001E "SNA SPM" protocol support was not successfully started.
2000-04-20-13.18.23.603000 Instance:DB2 Node:000
PID:291(db2syscs.exe) TID:316 Appid:none
common_communication sqlccspmconnmgr_listener Probe:6
DIA3103E Error encountered in APPC protocol support. APPC verb "APPC(DISPLAY 1
BYTE)". Primary rc was "F004". Secondary rc was "00000000".
If such entries exist in your db2diag.log, and the time stamps match your
most recent reboot time, you must:
1. Invoke db2stop.
2. Start the SnaServer service (if not already started).
3. Invoke db2start.
Check the db2diag.log file again to verify that the entries are no longer
appended.
------------------------------------------------------------------------
Integrated SNA Support no longer Provided with DB2 Connect Personal Edition
for Windows V7.1
DB2 Connect Personal Edition for Windows V7.1 no longer provides an
integrated SNA stack. Any references to the Integrated SNA stack in any DB2
Connect V7.1 publication is incorrect. If SNA connectivity is required, a
supported SNA product must be installed. Supported SNA products are listed
in the DB2 Connect Personal Edition Quick Beginnings V7.1 in the Planning
for Installation chapter, under Software Requirements and Hardware/Software
Requirements (refer to Table 1).
If you are migrating from previous versions of DB2 Connect Personal Edition
with the Integrated SNA stack installed, SNA connectivity may continue to
work. However, this is an unsupported configuration. It is strongly
recommended that you install one of the supported SNA stacks.
------------------------------------------------------------------------
Additional Patch Required for Solaris Version 2.6
DB2 Connect Version 7.1 for Solaris** Version 2.6 requires patch 106285-02
or higher, in addition to the patches listed in the DB2 Connect Quick
Beginnings for UNIX** book.
------------------------------------------------------------------------
Terminal Server Application
If Windows** 2000 is using terminal server as an application, terminal
server must be in install mode before you can install DB2 Connect. The
easiest way to do so is to use Add/Remove Programs in the Control Panel to
install DB2 Connect, since this automatically puts the terminal server in
install mode.
------------------------------------------------------------------------
Limitations of JDBC/ODBC/CLI Static Profiling
JDBC/ODBC/CLI static profiling currently targets straightforward
applications. It is not meant for complex applications with many functional
components and complex program logic during execution.
An SQL statement must have successfully executed for it to be captured in a
profiling session. In a statement matching session, unmatched dynamic
statements will continue to execute as dynamic JDBC/ODBC/CLI calls.
An SQL statement must be identical character-by-character to the one that
was captured and bound to be a valid candidate for statement matching.
Spaces are significant: for example, "COL = 1" is considered different than
"COL=1". Use parameter markers in place of literals to improve match hits.
When executing an application with pre-bound static SQL statements, dynamic
registers that control the dynamic statement behavior will have no effect
on the statements that are converted to static.
If an application issues DDL statements for objects that are referenced in
subsequent DML statements, you will find all of these statements in the
capture file. The JDBC/ODBC/CLI Static Profiling Bind Tool will attempt to
bind them. The bind attempt will be successful with DBMSs that support the
VALIDATE(RUN) bind option, but it fail with ones that do not. In this case,
the application should not use Static Profiling.
The Database Administrator may edit the capture file to add, change, or
remove SQL statements, based on application-specific requirements.
------------------------------------------------------------------------
DB2 for OS/390(R) APAR Fix Prerequisites
* APAR PQ34536: PTF UQ40226 for DB2 for OS/390 Version 6
* APAR PQ35121: PTF UQ41788 for DB2 for OS/390 Version 5
* APAR PQ35121: PTF UQ41789 for DB2 for OS/390 Version 6
Kerberos and User ID Encryption
* APAR PQ36732: PTF UQ41942 for DB2 for OS/390 Version 6
* APAR PQ36732: PTF UQ41941 for DB2 for OS/390 Version 5
------------------------------------------------------------------------
Trademarks
* The following terms are either registered trademarks or trademarks of
International Business Machines Corporation in the United States, other
countries, or both:
* DB2
* DB2 Connect
* IBM
* OS/390
** Microsoft, Windows, and Windows NT are either registered trademarks or
trademarks of Microsoft Corporation.
** Sun, Java, and Solaris are either registered trademarks or trademarks of
Sun Microsystems, Inc. in the United States and other countries.
** UNIX is a registered trademark of The Open Group in the United States
and other countries.
** Other company, product, and service names may be the trademarks or
service marks of others.