Release Notes - DB2 Everyplace Version 7.2.1
This Release Notes file provides information about DB2 Everyplace Version
7.2.1
The latest Release Notes information can be found online at the
DB2 Everyplace Web site.
Always use the latest version of Release Notes.
For installation instructions, please view the Installation Notes.
Contents
DB2 Everyplace for Windows operating system CD:
- The main setup program name is <drive:>\DB2Everyplace\setup.exe
- The Installation Notes file name is <drive:>\DB2Everyplace\<language>\instnote.*
- The Release Notes file name is <drive:>\DB2Everyplace\<language>\release.*
DB2 Everyplace for Unix platform CD:
- The compressed installation file name is /DB2Everyplace_SyncServerInstall_[platform].tar
- The main setup program is packaged in the tar file
- The Installation notes are packaged in the tar file:
SyncServer/readme/<language-code>/<codepage>/instnote.html
- Release notes are packaged
in the tar file: SyncServer/readme/<language-code>/<codepage>/release.html
Unix platforms supported:
- AIX
- Linux including RedHat, Mandrake, SuSE, and Turbo Linux
- Solaris
Language codes are as follows:
ar Arabic
cs_CZ Czech
de_DE German
en_US US English
es_ES Spanish
fr_FR French (standard)
it_IT Italian
iw_IL Hebrew
ja_JP Japanese
ko_KR Korean
zh_CN Simplified Chinese
zh_TW Traditional Chinese
Publications are available from the DB2 Everyplace Web site.
The DB2 Everyplace Installation and User's Guide is
available in HTML and PDF format in the following languages:
o Czech
o English
o Korean
o Simplified Chinese
o Traditional Chinese
o Spanish
o Japanese
The DB2 Everyplace Application Development Guide is available
in HTML and PDF format in the following languages:
o English
o Korean
o Simplified Chinese
o Spanish
o Japanese
The DB2 Everyplace Sync Server Administration Guide is
available in HTML and PDF format in the following languages:
o English
o German
o Japanese
o Korean
o Simplified Chinese
The online help within the Mobile Devices Administration
Center (MDAC) is available in the national language that you select during installation.
English is provided with Arabic, Hebrew, and Czech versions.
This section describes how to set up the DB2 Everyplace Sync Server to use an existing
IBM WebSphere Application Server after you have installed Sync Server. It covers the following topics:
- Configuring Sync Server to use with WAS 3.5.4 Standard and Advanced Edition
- Configuring Sync Server to use with WAS 4.0 Advanced Edition
Configuring Sync Server for use with WAS 3.5.4 Standard and Advanced Edition
To configure Sync Server to use with WAS 3.5.4:
- Install DB2 Everyplace.
- Create a DB2 Everyplace instance (UNIX only).
- Start the IBM HTTP server.
- Start the Adminstration Server for WAS 3.5.4. When you start the WAS Administration Server, you must log in as a DB2 administrator on a Windows NT or Windows 2000 operating system, or as root user on the UNIX operating system. The WAS Administration Server must use the default port number 900 now, but you can change the server to use another port at a later time.
- Create an application server under your WebSphere node.
- For Windows NT or Windows 2000
- Open a Command Prompt window.
- Change the directory to %DSYINSTDIR%\WebSphere\ext-was-cfg\354\NT.
- Type
dsy_was354_install.bat WAS_installation_directory WAS_node_name %DSYINSTDIR% %DSYSQLLIBINSTDIR%
where WAS_installation_directory is the directory in which the WebSphere Application Server is installed and
WAS_node_name is the WAS node name under which you want to install Sync Server.
- For UNIX, open a terminal window and type $DSYINSTDIR/install/ext-was-cfg/354/unix/dsy_was354_install.sh. You will be prompted to provide a node under which to install the Sync Server application, and the name of the DB2 Everyplace instance you created.
An application server with the name IBM DB2 Everyplace is created.
Changing the transport port to resolve port conflict in WAS 3.5.4
The installation script creates an application server for IBM DB2 Everyplace
that uses 8999 for the transport port. If another application in WAS has used
the same port, a conflict occurs. You can change the transport port in two ways.
Method 1 requires you to change an XML script and execute the installation script
again. With method 2, you use the WAS Admin Console.
Method 1
- In a text editor, open the following file:
- For Windows NT or Windows 2000, %DSYINSTDIR%\WebSphere\ext-was-cfg\354\common\dsy_was354_install.xml
- For Linux and Solaris, /opt/DB2Everyplace72/install/ext-was-cfg/354/common/dsy_was354_install.xml
- Locate the following line:
<transport-port>8999</transport-port>
- Replace 8999 with a free port number you want to use (for example, 9003) and save the file.
- Repeat step 5 described above in "Configuring Sync Server for use in IBM WebSphere Application Server (WAS)."
Method 2
- Launch the WAS Admin Console.
- Change to the topolgy view.
- On the left pane, click WebSphere Administrative Domain -> your_node -> IBM_DB2_Everyplace -> DB2e_ServletEngine. Your_node is the node under which you have installed Sync Server.
- On the right pane, click the Advanced tab.
- In the port field, specify a free port (for example, 9003).
Configuring Sync Server to use with WAS 4.0 Advanced Edition
This section describes how to configure Sync Server to use with WAS 4.0 Advanced Edition. WAS 4.0 Advanced Single Server Edition is not supported.
To configure Sync Server to use with WAS 4.0 Advanced Edition:
- Install DB2 Everyplace.
- Create a DB2 Everyplace instance. (UNIX only).
- Configure WAS to use JDBC 2.0 (Windows NT or Windows 2000 only).
- Open a Command Prompt window.
- Change the directory to %DSYSQLLIBINSTDIR%\java12.
- Run usejdbc2.bat
- Start IBM HTTP Server.
- Start the Adminstration Server for WAS 4.0. When you start the Administration Server, you must log in as a DB2 administrator on a Windows NT or Windows 2000 operating system, or as root user on the UNIX operating system. The administration server must use the default port number 900 now, but you can change the server to use another port at a later time.
- Create an application server under your WebSphere node.
- For Windows NT or Windows 2000
- Open a Command Prompt window.
- Change the directory to %DSYINSTDIR%\WebSphere\ext-was-cfg\40\NT.
- Type
dsy_was40_install.bat WAS_installation_directory WAS_node_name %DSYINSTDIR% %DSYSQLLIBINSTDIR%
where WAS_installation_directory is the directory in which the WebSphere Application Server is installed and
WAS_node_name is the node name of the WebSphere Application Server.
- For UNIX, open a terminal window and type $DSYINSTDIR/install/ext-was-cfg/40/unix/dsy_was40_install.sh. You will be prompted to provide a node under which to install the Sync Server application, and the name of the DB2 Everyplace instance you created.
If during the execution of the script, an error message that indicates a duplicate port has been used appeared, follow the instructiions in "Resolving transport port conflict in WAS 4.0" below and then continue from here.
- Run the DB2 Everyplace installation wizard.
- Launch WAS Administration Console.
- On the left pane, expand the object tree until you see Enterprise Applications.
- Right-click Enterprise Application and select Install Enterprise Application. The Install Enterprise Application wizard starts.
- Make sure Install Application is selected on the Specify the Application or Module page.
- In the path field under Install Application, type:
- For Windows NT or Windows 2000, %DSYINSTDIR%\WebSphere\ext-was-cfg\40\common\IBM_DB2_Everyplace.ear.
- For UNIX, $DSYINSTDIR/install/ext-was-cfg/40/common/IBM_DB2_Everyplace.ear.
Alternatively, you can click Browse to locate the file.
- Click Next on all the pages that follow until you reach the page titled "Selecting Application Servers."
- On the Selecting Application Servers page, click Select Server. The Select a Server or Server Group window opens.
- Select IBM DB2 Everyplace from the Application Server list and then click OK.
- Click Next.
- Click Finish to complete the installation wizard.
- On the left pane of the WAS Administration Console, right-click the node under which you have installed DB2 Everyplace and select Regen Webserver Plugin. This makes all the change effective.
Changing the transport port to resolve port conflicts in WAS 4.0
The installation script creates an application server for IBM DB2 Everyplace that uses 8999 for the transport port. If another application in WAS has used the same port, a conflict happens. You can change the transport port by using the WAS Administration Console.
To change the transport port:
- Start the WAS Administration Console.
- On the left pane, click WebSphere Administration Domain -> Nodes -> Application Servers -> IBM DB2 Everyplace Server..
- On the right pane, click Services.
- Select Web Container Service from the Services list and then click Edit Properties.
- Specify a free port in the Transport port field and click OK.
The DB2 Everyplace database engine does not support multiple database
connections. Multiple read-only statement handles may be used. INSERT,
UPDATE, DELETE, CREATE, or DROP operations must be serialized to ensure
data integrity. Multithreaded operations must be serialized to ensure data
integrity.
Information about Neutrino client Versions
DB2 Everyplace Database supports Neutrino Version 6.0 and Version 6.1. The documentation refers to
Neutrino client package as DB2EveryplaceNTO.tar.gz. The file names should be changed to DB2EveryplaceNTO60.tar.gz and DB2EverylaceNTO61.tar.gz respectively.
Known Problems and considerations - DB2 Everyplace database
- The Install on Mobile Device tool requires the workstation-to-mobile-device
connection software to be installed on the local workstation. If the workstation
to mobile device connection software is not available for the selected
mobile device in the Install on Mobile Device tool, the Install on Mobile
Device tool will fail.
- The Install on Mobile Device tool for Symbian v6.0 has only been tested
on Nokia 9210 device. This tool may or may not work on other Nokia or non-Nokia
devices for Symbian v6.0.
Notes about the DB2 Everyplace Sync Server
JDBC subscriptions from a pre-7.2 beta release
Any non-Put JDBC subscriptions created using a version earlier than
V7.2 must be deleted using the Mobile Devices Administration Center before
you install the new version.
Information about Neutrino client Versions
DB2 Everyplace Sync Server supports Neutrino Version 6.0 and Version 6.1. The documentation refers to
Neutrino client package as ISyncNTO.tar.gz. The file names should be changed to ISyncNTO60.tar.gz and ISyncNTO61.tar.gz respectively.
Mirror table log space
During replication, mirror tables are updated with information from
the master table. Ensure that there is sufficient log space allocated on the
mirror database to accomodate these updates. If synchonization fails with the message
"DProprException: DataPropagator Process did not complete successfully (RC
= -1)", or the sqlcode "SQL0964C The transaction log for the database is
full" appears in the DataPropagator trace files, increase the log file
space by using the following commands on the DB2 command line:
db2 update db cfg for MIRROR_DATABASE using logfilsiz N
(where N is higher than the current setting of logfilsiz)
OR
db2 update db cfg for MIRROR_DATABASE using logprimary N
(where N is higher than the current setting of logprimary)
OR
db2 update db cfg for MIRROR_DATABASE using logsecond N
(where N is higher than the current setting of logsecond)
Remote and DBCS data sources and primary key
When creating a table subscription using a remote data source or
a DBCS data source, the primary key is not automatically assigned. Data
sources used in a table subscription must have a primary key. The primary
key can contain multiple columns. Use the Advanced button in the Define
Subscription dialog to select the primary key(s).
For JDBC drivers
You can set the JDBC driver you want to use with Sync Server by
modifying the Sync Server path in the DSYINSTDIR environment variable. To modify the variable:
Known Problems and considerations - DB2 Everyplace Sync Server
- After you have created a subscription, you cannot edit the row filtering for that subscription.
Filtering must be defined when you create the subscription.
- Before you install the Sync Server on UNIX operating systems, ensure that the DISPLAY variable has
been exported to the environment of the instance for which you are installing Sync Server.
For example, add the export statement to the profile file of the user (.profile for Korn shell, or .bashrc
for bash).
- For AIX, before you install the Sync Server on AIX, ensure that the control database has been changed
from DSYDB to DSYCTLDB. To migrate the Version 7.2 MDAC objects (such as subscriptions and groups):
- Backup your control database DSYDB.
- Drop control database DSYDB.
- Create database DSYCTLDB and restore all the tables in it from DSYDB.
- When a primary-key column of a look-up table is updated in a source database, you must perform a refresh on the client device.
- Oracle source databases do not support TIME and TIMESTAMP columns.
In these databases, the DATE column might include minutes and seconds.
- To enhance DB2 Everyplace performance when using Oracle source databases,
change the open_cursor variable using the following directions:
- In the installation directory, locate the sub-directory that has the same name as
the database. Open the sub-directory and locate the init.ora file.
- In the init.ora file, change the value of the variable open_cursors=nnn to 1000.
- Save the file and restart database services.
- When you add a table from an Oracle database, it is OK to ignore Sync Server warning messages
that occur when you use a wildcard (%) in both the source schema and source menu fields
of the Add Table dialog to retrieve the names of the Oracle system tables.
- The row filter statement for a subscription should be contained on a single line.
No new line characters are allowed within the statement.
- On Palm OS devices, you should check Drop connection after sync if you have
network connection problems. However, if this checkbox is
selected, your mobile device will be disconnected from your ISP modem connection
after every synchronization. You will need to dial-up again to re-establish the connection.
- If you have problems opening a connection when using Symbian OS Version 6, try resetting your
mRouter connection.
- For file subscriptions on Palm devices, when you synchronize to the Palm device,
the target file name field in a file subscription is ignored. The file name that is
created on the Palm device is always a default name.
- Warning: Do not change the user name of the source database when editing.
a JDBC subscription. This may cause replication to fail.
-
Warning: Table subscriptions should not be altered while client synchronization
sessions are in progress. In general, changes to subscriptions should be
applied by deleting the existing subscription and creating a new one which
incorporates the desired changes.
-
Warning: When creating or editing a table subscription, if you type an
invalid user ID or password into the fields on the Authentication page
DB2 will open several DB2 Login windows. Cancel the DB2 Login windows and
correct the user ID or password. Mobile Devices Administration Center does
not validate the user ID or password entered on the Authentication page.
-
Restriction: Sync Server does not synchronize DB2 Universal Database LOBs
or BLOBs at this time. Sync Server will synchronize a LONG VARCHAR FOR
BIT DATA from DB2 Universal Database to DB2 Everyplace. DB2 Everyplace
stores the LONG VARCHAR FOR BIT DATA as a BLOB. The restriction on LOBs
and BLOBs may be removed later.
-
Warning: The servlet should be stopped and restarted when any event occurs that
can bring down multiple synchronizable databases simultaneously on either
the mid-tier or source servers(for example, a
force application all command). If you do not stop and restart, all databases might
not be successfully recovered by the synchronization
server.
-
Warning: When using a Palm VII device with IBM Sync and a serial cradle,
you may receive a FATAL EXCEPTION dialog box after the Palm VII NetLib
has disconnected from the network. A soft reset will return the device
to normal operation.
-
Restriction: On all client platforms except Palm OS, a DB2 Everyplace application and
IBM Sync cannot be run simultaneously.
-
Warning: When installing the DB2 Everyplace Sync Server, the DB2 Univeral
Database services must be running. If the DB2 Universal Database services
are not running, the Mobile Device Administration Center database cannot
be created. The DB2 Everyplace install will not report this error. To manually
create the Mobile Device Administration Center database, the DSYCTLDB.bat
file should be run from a DB2 Command Prompt. Check the DSYCTLDB.log file
after creating the database. These files are in the SyncServer\Server directory.
-
Warning: In the DBCS languages, text files such as Readme.LINUX, Readme.SOLARIS,
or Readme.AIX may appear to have corrupted characters. Enlarging the screen
size by dragging the window border will solve this problem. This is due
to a wrapping problem when using the default size of the screen. Any EUC
supporting DBCS locales are potential candidates for this problem.
-
Restriction: SyncServer does not allow binary data in default values.
-
Warning: The double-byte data type is synchronized as a varchar to the client.
If the client enters an non-numeric value in this varchar column, the row
will be rejected during synchronization. A rejected row message will appear
in the client log.
-
Restriction: Control Center help and Mobile Device Administration Center
help doesn't work on AIX for all languages. In order to view help go
to ~/sqllib/doc/html/db2help/dsysync and view the file dsyhmsttfrm.htm
in a browser window.
-
Restriction: When using WebSphere Application Server on AIX for running
SyncServer, do not preload the servlet by sending in request from a browser
window. This would cause the servlet to initialise twice and would crash
SyncServer.
-
Warnings when using horizontal filtering
-
Horizontal filtering at the subscription level:
When horizontal filtering is imposed at the subscription level, symmetry
is not maintained between the source table and mirror table. Even though
updates to the table might fall outside the scope of the subscription filter,
they will be replicated to the source and are available to all other users
of the subscription, provided the updates meet the criteria for the group
and user filters.
If the updated rows are subsequently changed at the source, and do
not meet the subscription filter criteria, they will not be synchronized
to the users. If the updates are not synchronized to the users, a data
integrity violation will occur.
To avoid data integrity violations, impose constraints on the user
tables, and restrictions on the DB2e application.
- Horizontal filtering at the user level:
When horizontal filtering is imposed at the user level, the result is
an asymmetry between the mirror table and the user's table. Even though
a user update does not meet the user's filter criteria, it will be synchronized.
Any subsequent change to an updated row at the source, or by another user,
which fails to meet the user-filter criteria will result in a data integrity
violation for the user.
To avoid data integrity violations, impose constraints on the user
tables and application checking.
- An INSERT that is synchronized from a user in a relational database subscription that
results in a constraint violation on the source will not result in the record being removed from the
user's device.
HATs and FAQs - DB2Everyplace Sync Server
-
On Linux platforms with 2.4 kernels, if java or jre hangs soon after it
starts, you will need to export the following variable to start Java properly:
export LD_ASSUME_KERNEL=2.2.5
-
When adding a subscription to an application, for Data Propagator (DPropr)
subscriptions you need to stop and re-start both the asnccp process and
the SyncServer servlet. For JDBC subscriptions you only need to stor and
re-start the SyncServer servlet.
-
If re-starting asnccp for any reason, delete previous .CCP and .PID files
first.
-
Database parameters in the DB2 Control Center (db2cc) such as the size
of the locklist can be increased up from the database defaults of 100 to
1000 or higher to greatly improve performance for large tables and large
number of clients.
-
If the Mobile Device Administration Center (MDAC) or the SyncServer servlet
cannot start, ensure that the following files have not been accidently modified or deleted:
- On UNIX, dsysetenv.sh and dsysetjavahome.sh
- On Windows, dsysetenv.bat and dsysetjavahome.bat
For UNIX, the following system environment must also be defined (where <userhome>
represents your own directory name):
In the PATH variable:
/sqllib/bin
DSYPATH=/opt/DB2Everyplace72 (Your DB2Everyplace Install directory)
DB2PATH=<userhome>/sqllib
DSYINSTDIR=<userhome>/db2everyplace/SyncServer
DSYSQLLIBINSTDIR=<userhome>/sqllib
After installation, these values are placed into dsyprofile.sh in diectory $DSYINSTDIR/Server.
For Windows, verify that %DSYSQLLIBINSTDIR% and %DSYINSTDIR% are defined
correctly in the system environment variable.
-
To debug/troubleshoot, switch on tracing. In the DB2 Everyplace installation
directory run:
- For UNIX, dsytrace.sh 1
- For Windows, dsytrace.bat 1
These jobs generate dsy.n.trace files [n=0,1,2...,10].
-
To synchronize successfully, the language locale on the client
must be exactly the same as the locale on the DB2Everyplace SyncServer
instance.
Terms and conditions
Use of DB2 Everyplace is subject to the terms and conditions of the International
Program License Agreement. Other non-IBM code provided with DB2 Everyplace
is provided for the customer's convenience. The DB2 Everyplace warrantees
do not apply to such code.
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 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 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 which has been exchanged, should contact: IBM Canada
Limited
Office of the Lab Director
1150 Eglinton Ave. East
North York, Ontario
M3C 1H7
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 information 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 illustrates 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.
This product includes software developed by 3Com and its contributors.
Copyright (c) 1998 3Com/Palm Computing Division. All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-
Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
-
Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-
All advertising materials mentioning features or use of this software must
display the following acknowledgement: This product includes software developed
by 3Com and its contributors.
-
Neither 3Com nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE 3COM AND CONTRIBUTORS ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL 3COM OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Trademarks
The following terms, which may be denoted by an asterisk(*), are trademarks
of International Business Machines Corporation in the United States, other
countries, or both.
ACF/VTAM IBM
AISPO IMS
AIX IMS/ESA
AIX/6000 LAN DistanceMVS
AIXwindows MVS/ESA
AnyNet MVS/XA
APPN Net.Data
AS/400 OS/2
BookManager OS/390
CICS OS/400
C Set++ PowerPC
C/370 QBIC
DATABASE 2 QMF
DataHub RACF
DataJoiner DataPropagator RISC System/6000
DataRefresher RS/6000
DB2 S/370
DB2 Connect SP
DB2 Extenders SQL/DS
DB2 OLAP Server SQL/400
DB2 Universal Database System/370
Distributed Relational System/390
Database Architecture SystemView
DRDA VisualAge
eNetwork VM/ESA
Extended Services VSE/ESA
FFST VTAM
First Failure Support Technology WebExplorer
WIN-OS/2
The following terms are trademarks or registered trademarks of other companies:
Microsoft, Windows, and Windows NT are trademarks or registered trademarks
of Microsoft Corporation.
Java or all Java-based trademarks and logos, and Solaris are trademarks
of Sun Microsystems, Inc. in the United States, other countries, or both.
Tivoli and NetView are trademarks of Tivoli Systems Inc. in the United
States, other countries, or both.
UNIX is a registered trademark in the United States, other countries
or both and is 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.