IBM DB2 DataJoiner Version 2.1.1 -- New Spatial Extensions Can Increase the Value of Your Data
Software Announcement
July 28, 1998
Announcement Letter Number: 298-264
Table of Contents:
- At a Glance
- DESCRIPTION
- SUPPLEMENTAL INFORMATION
- EDUCATION SUPPORT
- PUBLICATIONS
- TECHNICAL INFORMATION
- ORDERING INFORMATION
- TERMS AND CONDITIONS
- CHARGES
- CALL NOW TO ORDER
In the At a Glance section, DB2 UDB Family was added. In the Supplemental section, under Planning Information, text under DB2 Spatial Extender Feature has been replaced. In the Terms and Conditions section, Education Allowance and Variable Charges do not apply.
(Corrected on August 14, 1998)
Sysbase was changes to Sybase in the At a Glance section.
At a Glance
DB2 DataJoiner V2.1.1 offers:
- Windows NT, AIX, and AS/400 (R) with IPCS feature platform support
- Spatial Data Support enabling Geographic-Business applications
- Native support for DB2 UDB Family, Microsoft (TM) SQL Server, Oracle 8, Oracle Rdb, Informix, Sybase and Sybase SQL Anywhere.
- Transparent Data Manipulation Language (DML) and Data Definition Language (DDL) support
- Integrated multi-vendor database replication including Microsoft Jet Databases
- Internet enablement -- transparent access to multi-vendor data sources via DB2 DataJoiner and Net.Data (TM)
- High Performance through Global Optimization Technology
- Powerful data type and SQL function mapping
- Global schema support for user-defined types and user-defined functions
- DRDA (R) Application Server (DRDA-AS) support for MVS (TM), VM, and OS/400 (R) Application Requestors (ARs) access to multi-vendor data via DataJoiner
- Continued support for IMS (TM) and VSAM via DataJoiner Classic Connect
-----------------------------------------
For ordering, contact:
Your IBM representative, an IBM
Business Partner, or IBM North America
Sales Centers at
800-IBM-CALL Reference: SE010
Overview
Have you ever wished you could query your databases like this? "Give me all homes with an annual household income over $40,000 a year that are located within a 10 mile radius of my store." Imagine being able to do that within a single SQL statement!
Now you can with the new and exciting DB2 (R) Spatial Extender, an optional priced feature of DB2 DataJoiner (R) V2.1.1. Using existing Geographic Information Systems (GIS) applications or a single SQL statement directly, the DB2 Spatial Extender can query spatial information and/or join this data with conventional business data from heterogeneous sources. With an estimated over 80 percent of all data embedded with "geographic" or "spatial" characteristics (for example, address), the competitive advantage spatial analysis offers you is clearly demonstrated.
Support for Oracle 8 and Sybase SQL Anywhere is available in the base offering of DB2 DataJoiner V2.1.1 thus continuing the commitment to increase the number of natively supported data sources. DB2 DataJoiner V2.1.1 provides transparent Data Definition Language (DDL) support, which allows greater flexibility in managing your heterogeneous environment.
DB2 DataJoiner Version 2.1.1 is a complete relational multi-vendor database tool, supporting complex configurations and large database needs. DB2 DataJoiner Version 2.1.1 is packaged for the AIX (R) and Windows NT (R) operating systems environments. See the Statement of Direction section for other UNIX (R) platforms.
Intended Customers
For customers having multiple homogeneous or heterogeneous data sources who need transparent access to this data, or the need to replicate data amongst the different heterogeneous data sources. Also, current Geographic Information Systems (GIS) customers who need to join traditional business data with spatial data, or any customer with the need to query spatial data using SQL.
Key Prerequisites
- DB2 DataJoiner Version 2.1.1 for Windows NT systems requires an Intel type micro-processor based computer, Windows NT 4.0 or higher, a CD-ROM reader, at least 140 MB of disk space, and 16 MB memory base plus 0.31 MB per remote client.
- DB2 DataJoiner Version 2.1.1 for AIX systems requires AIX V3.2.5 or higher, (or AIX V4.1.4 or higher to take advantage of the DB2 Spatial Extender option), a CD-ROM reader, at least 60 MB of disk space, and a 7 MB memory base plus 1 MB per concurrent user.
English/NLS Planned Availability Date
July 31, 1998
------------------------------
This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: http://www.ibm.com
With DB2 DataJoiner Version 2.1.1, you can access and join data from different data sources with a single Structured Query Language (SQL) statement and a single interface. That single interface hides all the differences you struggle with when accessing information from different vendor databases on different vendor platforms. With DataJoiner, there is one interface to one database image. It's like having one big database.
Server Platform Support
DB2 DataJoiner Version 2.1.1 is available on two platforms:
- AIX
- Windows NT
Powerful, Multi-Vendor Database Joins
You don't have to send multiple queries to multiple data sources to get an answer. With DB2 DataJoiner Version 2.1.1, you only need to send one query to get the answer from different data sources. These sources include DB2, IMS, VSAM, Oracle, Oracle Rdb, Sybase, Sybase SQL Anywhere, Microsoft SQL Server, Informix, and others. Global schema allows you to create joins and/or views across all of these data sources, easily and transparently.
Transparent Access to Multi-Vendor Data Sources
Single SQL Interface: There is only one SQL interface to deal with. SQL dialects, protocols, operating systems, data types, error codes, and functional differences are all transparent to your application. Similarly, client workstations attached to DB2 DataJoiner only need one client interface to DataJoiner and all other supported data sources are then available. This eliminates the need for each workstation to have client code for each data source and is very efficient and cost effective.
Compensation: One way DataJoiner provides data transparency is via compensation. DataJoiner can provide function not available at a data source, enriching the native SQL of the data source. For example, a client can submit a query via DataJoiner to a data source. If that function is not supported (such as Recursive SQL) at the data source, but is supported by DataJoiner, the query can complete successfully. DataJoiner will compensate by simulating the function, thus preserving transparent access.
DataJoiner SQL for Creating, Altering, and Deleting Data Source
Tables
Version 2.1.1 includes a new DataJoiner SQL statement for creating tables in different types of data sources. If the native SQL for creating tables in these data sources includes a unique option -- for example, the option in DB2 for OS/390 (R) for specifying what database you want a table to reside in -- you can code this option in the new DataJoiner statement. If you create a data source table with this new statement, you can also alter and delete it with DataJoiner SQL.
DB2 Spatial Extender Optional Priced Feature
DataJoiner now supports Geographic Information System (GIS) data (also known as spatial or geographic data). New data types, spatially-enabled columns, and spatial join capability allow you to take advantage of geographic data in your applications. Powerful two-dimensional functions are included that allow you to create specific relationships among the geographic objects you define. The following components are included with the DB2 Spatial Extender:
- A set of spatial data types
- A set of spatial operations and predicates
- A set of spatial index data types
Geographic-Business applications employ queries based on proximity, distance and driving times and provide the option to present the results as maps.
For your convenience, the DB2 DataJoiner base offering includes free of charge a 60 day trial license for the DB2 Spatial Extender. The DB2 Spatial Extender may be installed and used on a trail basis for 60 days from the date of first use of the feature. The DB2 Spatial Extender feature includes a time disabling service which will prevent its use upon expiration of the 60 day trail period. To permanently install and use this feature, a customer must purchase the DB2 Spatial Extender License Pack (31L1137).
This DB2 Spatial Extender was jointly developed by IBM and Environmental Systems Research Institute, Inc. (ESRI) a leading GIS company.
To support the 60 day trial of the DB2 Spatial Extender, a DB2 Spatial Extender Introductory Bundle is also included in the DB2 DataJoiner base offering.
The DB2 Spatial Extender Introductory Bundle includes the following items, including products provided by ESRI:
-
ArcView Coupon
SDE Books Coupon
SDE Getting Started Book V 3.0
ESRI Demo Disk -- CD-ROM
ESRI World Maps Data -- CD-ROM
US Street Maps Data -- CD-ROM
ArcView GIS Demo Disk -- CD-ROM
Object and SQL Enhancements
Many users of RDBMSs are moving toward nontraditional, object applications, requiring support for a wider variety of real-world data. Examples include more effective handling of text, voice, and image data within RDBMSs. This trend has been accelerated by client/server tools and fourth-generation languages (4GLs) with powerful user interfaces for nontraditional data.
DB2 DataJoiner offers extensive support for nontraditional applications as described below in addition to providing traditional application support that is fully integrated within the database architecture:
- Large Objects (LOBs): Large object support allows multimedia
objects such as documents, video clips, images, and sound
recordings to be stored in any data source (which support LOBs,
like DB2 UDB) and manipulated like other database objects. The
size of any one LOB can range up to 2 GB.
A powerful set of built-in functions, such as search, substring, and concatenation, are supported for LOBs. Additional functions can be defined any time by means of user-defined functions (UDFs).
- Global User-Defined Types (UDTs): Global UDTs allow users to
define new data types across multi-vendor data sources, which are
represented in the DB2 DataJoiner database using built-in types.
For example, a user can define two currency types: CDOLLAR data
type for Canadian dollars and USDOLLAR data type for U.S. dollars.
These types are distinct in the sense that they should not be
directly compared to one another or to the DECIMAL type, although
the DECIMAL type might be chosen for the internal representation
of both UDTs in the database.
Using DB2 DataJoiner in the above example with the CDOLLAR data type on DB2, and USDOLLAR data type on Oracle, DataJoiner would invoke strong type checking to alert the program to a type mismatch, that is, that the two currency types are of conflicting types without the proper exchange rate conversion.
UDTs, like built-in types, can be used for columns of tables as well as function parameters, including user-defined functions (UDFs). For example, a user can define a data type such as ANGLE (which varies between 1 and 360) and a set of UDFs to act on it, such as SINE, COSINE, and TANGENT.
- Global User-Defined Functions (UDFs): Application developers
often want to create their own suite of functions specific to
their application or domain. Global UDFs make this possible,
expanding the scope of DB2 DataJoiner to include customized
business or scientific functions that span multi-vendor data.
For example, a retail store could define a PRICE data type for tracking the cost of items it sells. This store might also wish to define a SALES_TAX function, which would take a given price value as input, compute the applicable sales tax, and return this data to the application.
These functions can operate over all global database types, including LOBs and UDTs. UDFs allow queries to contain powerful computation and search predicates to filter irrelevant data close to the source of the data. The global SQL optimizer treats global UDFs exactly like built-in functions, such as SUBSTR and LENGTH.
- Global bills-of-material queries, where a user wants to return
subparts of parts, and subparts of the subparts, and so on.
- Global path expression queries, where a user wants to calculate the lowest-cost plane fares on multi-hop routes. For example, the following query can be formulated using recursive SQL: Return all possible flights from San Jose to Perth without making a stopover in London or Chicago and with no more than three plane changes.
The combination of global user-defined types and functions can mask the multi-vendor representation of the data and the definition of a set of functions that interpret the multi-vendor data. The global types and functions enable the creation of global function libraries, which can be developed outside of the database and then added to it, thereby extending database functionality.
Stored Procedures: DB2 DataJoiner now supports the invocation of stored procedures. The SQL92 level of function for stored procedure calls is supported. Stored procedures can greatly improve the performance of applications by minimizing network traffic. A stored procedure is an executable module stored on the database server that is comprised of SQL statements and application logic that are performed frequently. When a call to a stored procedure is made, only the instruction to invoke a procedure is passed to the database server instead of passing individual SQL statements.
DB2 DataJoiner will compensate for those data sources which do not support stored procedures. In these situations, DB2 DataJoiner will run the stored procedure locally and create the instructions and SQL necessary for the remote data source to complete the work.
DB2 DataJoiner can be used to invoke stored procedures on database servers that support them such as DB2 for MVS Version 4 and DB2 for OS/400 Version 3.
DB2 DataJoiner can "cascade" stored procedures. This powerful feature means that a stored procedure could start on DataJoiner and call another stored procedure on Oracle, which in turn could cascade others.
Distributed Enhancements
With DB2 DataJoiner, application developers and database administrators have greater flexibility in distributing data and applications across various platforms:
DRDA Application Server: The Distributed Relational Database Architecture (TM) Architecture (DRDA) Application Server (AS) capability allows DB2 for MVS, DB2 for VSE and VM (SQL/DS (TM) ), and DB2 for OS/400 applications (or any other application that implements the DRDA Application Requestor functionality) to access data located in any of the supported data sources (Oracle, Sybase, and so forth). The DRDA AR support can function across SNA or TCP/IP, and DRDA AS support can function across SNA. With this capability, thousands of existing database applications running on the MVS, VSE, VM, and OS/400 platforms are able to access data stored in workstation databases. As an example, QMF (TM), in conjunction with DB2 DataJoiner, can now provide access to DB2 and non-DB2 data sources.
Distributed Unit of Work: Distributed Unit Of Work (DUOW) functionality, also known as Two-Phase Commit, provides the capability for an application to read and/or update tables in more than one database from within a single unit of work with full data integrity.
For example, you can query tax tables in a DB2 for MVS database and concurrently update an Oracle for HP-UX payroll database. Or, money withdrawn from a bank account in one country can be deposited into an account in another during the same transaction. Because these multiple units of work are performed during the scope of a single global transaction, the integrity of the data is assured via Two-Phase Commit feature, even in the case of equipment failure.
Note: On DB2 DataJoiner Two-Phase Commit will only be supported on those data sources which natively support Two-Phase Commit.
Integrated Replication
The replication features of DB2 DataJoiner are fully compatible with the DataPropagator (TM) log-CAPTURE and APPLY components for the DB2 Family as well as DataPropagator Non-Relational for IMS.
IBM's replication offers transaction consistency, condensing of hot spot updates to minimize network traffic, change propagation through DB2 views (including join views), and update anywhere replication between DB2 databases with transaction conflict detection and automatic compensation.
DB2 DataJoiner extends this capability with database transparency and automatic generation of change capture triggers for Oracle, Microsoft SQL Server, Informix, Sybase, and Sybase SQL Anywhere.
Where triggers are used to capture changes, the tables used to process these changes can be in different distributed tables to avoid a single point of failure. The processes that apply changes to targets can execute locally or on a remote system -- offering the same rich function regardless of their location in the network. For example, one such process executing on a Windows NT system provides the same function as it would executing on an MVS system!
A lightweight update-anywhere capability with row conflict detection -- designed for the Microsoft Office environment -- lets Microsoft Jet and Microsoft Access desktop database applications interoperate with corporate applications through database replication with DB2, Oracle, Microsoft SQL Server, Informix, Sybase, and Sybase SQL Anwhere. Microsoft Jet is supported for heterogeneous replication only.
DataJoiner also provides a graphical user interface administration tool for defining data sources and targets. The Replication Administration tool runs on Windows NT and Windows (TM) 95 and in DB2 DataJoiner Version 2.1.1 will be available only in English.
Performance Enhancements
Users and administrators of DB2 DataJoiner can benefit from significant performance improvements in a variety of scenarios:
- Global SQL Optimizer with Global Query Rewrite Capability: Major
enhancements to the Global SQL optimizer strengthen DB2
DataJoiner's leadership position in global query optimization for
traditional applications. This new global optimization technology
provides the function and performance needed by customers to
analyze and exploit vast amounts of valuable information stored in
their multi-vendor databases.
The increasing importance of decision support applications represents an important customer trend that can result in very complex, multi-vendor database queries. These global queries can be written by end users, generated by automatic tools, or produced as a result of many point-and-click application interfaces popular in today's DOS, Windows, OS/2 (R), and UNIX environments. The optimizer incorporates a very sophisticated query rewrite phase that automatically transforms a complex query into a simpler query that matches the capabilities of the data source.
The global optimizer also looks at a great number of alternatives in its search for the best query execution plan while employing sophisticated cost modeling techniques.
There are two key steps for improving query performance:
- Pushdown Analysis: The major task of this DB2 DataJoiner
function is to make a recommendation to the DataJoiner
optimizer about whether an operation can be remotely evaluated.
It is just a recommendation because the DataJoiner Optimizer
may choose not to perform an operation directly on a remote
data source because it is less cost effective. This
recommendation is based on the capabilities known to DataJoiner
about this data source, which may include data types, supported
functions, the data source specifics known to DataJoiner, and
additional server options that a user may have created.
- Remote SQL Generation: The final plan selected by the DataJoiner global optimizer might consist of a set of steps that can operate on the remote data source. For those operations that are to be performed by each data source, Remote SQL Generation is called to generate an efficient SQL statement based on the SQL dialect supported at the data source.
- Pushdown Analysis: The major task of this DB2 DataJoiner
function is to make a recommendation to the DataJoiner
optimizer about whether an operation can be remotely evaluated.
It is just a recommendation because the DataJoiner Optimizer
may choose not to perform an operation directly on a remote
data source because it is less cost effective. This
recommendation is based on the capabilities known to DataJoiner
about this data source, which may include data types, supported
functions, the data source specifics known to DataJoiner, and
additional server options that a user may have created.
- Global Explain Facility: The global explain facility offers
detailed information about the access plans chosen by DB2
DataJoiner to process multi-vendor SQL statements. This explain
information helps users in their database design by allowing them
to:
- Create more efficient database designs to achieve desired performance objectives
- Model the impact of environment changes on SQL statements
- Determine ways in which the performance of applications can be improved (adding indexes or updating table statistics)
- Global Visual Explain: Global visual explain is an easy-to-use and robust tool for analyzing and tuning multi-vendor SQL statements. This tool provides an intuitive graphical view of the access plan chosen by the DB2 DataJoiner global optimizer for an SQL statement.
Additional Function
Full Local Database Functionality: DataJoiner provides a full-function, industrial-strength relational database. You can use it to store query results, develop and manage snapshots of data from different data sources, and support concurrent transaction processing. The local database offers full backup and recovery, logging, and locking subsystems. DataJoiner also includes a global visual explain facility and a global performance monitor.
Extensive Tool and Application Support: DataJoiner is designed to support the 1000+ IBM and non-IBM query tools and application development tools that presently support the IBM DB2 family. A complete list of these products are provided in the IBM DB2 solutions directory. These tools include Decision Support tools like Microsoft Access, Crystal Reports, and Lotus (R) Approach (R). DB2 DataJoiner can also work with application builders like Power Builder, VisualAge (R), and VisualGen (R).
Access to Non-Relational and Relational Data through 3rd Party Gateways: DataJoiner is designed to support all the relational and non-relational data sources supported by CROSS ACCESS Corporation's CrossAccess Data Delivery System, Information Builders, Incorporated EDA/SQL, and the DB2 DataJoiner generic application programming Interface.
Solutions Included with DB2 DataJoiner Version 2.1.1
The following licensed products are currently included in the DB2 DataJoiner product box. For more information on the following products being included with DB2 DataJoiner, refer to the Packaging section of this announcement.
- Net.Data: OS/2, AIX, and Windows NT platforms. Businesses today
want to harness the power of the Web to reach the global
marketplace. With IBM Net.Data, you can build interactive
Web-sites with data from the sources that you have in your
business today relational data, file data, or even Lotus Notes (R)
data. Whether you are building interactive catalogs of products,
allowing customers to track orders, or conducting electronic
commerce, your Net.Data-driven application can get your data to
(and from) a worldwide audience.
You can leverage your existing client/server applications to the Web, using your existing business logic. Imbed dynamic SQL, Java (TM) applets and JavaScripts, Perl, and REXX programming into your Net.Data application; or, call DLLs written in C/C++. By exploiting your existing business applications, you can get your Web applications up and running quickly with Net.Data.
For more details on Net.Data, Refer to Software Announcement 297-364 dated September 16, 1997.
- Domino (TM) GO Webserver:
A complimentary licensed copy of Domino GO Webserver is included. Domino GO Webserver is a scalable high-performance Web server that runs on a broad range of platforms. Domino GO Webserver brings you all the features and functions found in the IBM Internet Connection Secure Server product, plus more! It includes state-of-the-art security, site indexing capabilities, and advanced server statistics reporting.
With Lotus Go, you can speed beyond your competition by exploiting the latest advances in technology, such as Java, HTTP 1.1, and Web site content rating. Domino GO can communicate through Net.Data to DB2 DataJoiner to access multi-vendor databases and provide real-time access and tremendous power to your web applications. You get all this and more in a Web server that's easy to install and maintain.
For more information on Lotus SmartSuite products, see the following Web site:
Year 2000
This product is Year 2000 ready. When used in accordance with its associated documentation, it is capable of correctly processing, providing, and/or receiving date data within and between the 20th and 21st centuries, provided all other products (for example, software, hardware, and firmware) used with the product properly exchange accurate date data with it.
The maintenance end date for this year 2000 ready product is January 31, 2001.
STATEMENT OF GENERAL DIRECTION
In addition, IBM plans to make DataJoiner available on two additional platforms, -- Solaris Operating Environment and HP-UX.
REFERENCE INFORMATION
This announcement replaces and supersedes Software Announcement 298-102 dated March 31, 1998.
Trademarks
Net.Data, MVS, IMS, Distributed Relational Database
Architecture, SQL/DS, QMF, and DataPropagator are trademarks of
International Business Machines Corporation in the United
States or other countries or both.
DB2, DataJoiner, AIX, AS/400, DRDA, OS/400, OS/390, OS/2,
VisualAge, and VisualGen are registered trademarks of
International Business Machines Corporation in the United
States or other countries or both.
Microsoft and Windows are trademarks of Microsoft Corporation.
Windows NT is a registered trademark of Microsoft Corporation.
Java is a trademark of Sun Microsystems, Inc.
UNIX is a registered trademark in the United States and other
countries exclusively through X/Open Company Limited.
Domino is a trademark of Lotus Development Corporation.
Approach, Lotus, Lotus Notes, Lotus SmartSuite, and SmartSuite
are registered trademarks of Lotus Development Corporation.
Other company, product, and service names may be trademarks or
service marks of others.
IBM provides the following customer education for DB2 (R) DataJoiner (R) Version 2.1.1
- Using DataJoiner (Course Code DW202)
- DataJoiner Administration (Course Code DW212)
The data replication courses, DataPropagator (TM) Relational Basic Usage (DW140) and DataPropagator Relational Advanced Usage (DW150), are recommended for all customers planning to install or migrate to DataPropagator Relational Capture and Apply for MVS (TM) Version 5.1. Curriculum will be updated as necessary to include new product enhancements.
Descriptions of all classroom and self-study courses are contained in the IBM Education and Training catalogs. HONE users can use the key word EDUCATION for descriptions and schedules of these and other courses.
For more information, visit the follow Web site:
For more information or to enroll in any IBM class, call 800-IBM-TEACH (426-8322) and refer to the IBM US course code.The hardcopy publications listed below are provided in the DB2 DataJoiner package. These publications can be ordered separately for a fee immediately after general availability. To order contact your IBM Marketing Representative or call the IBM NA Sales Center at 800-IBM-CALL (426-2255) and refer to Priority Code "SE010".
Order
Title Number
DB2 DataJoiner, V2.1.1 Planning, SC26-9145
Installation and Configuration Guide
for AIX (R) Operating Systems
DB2 DataJoiner, V2.1.1 Planning, SC26-9150
Installation and Configuration Guide
for Windows NT (R) Operating Systems
The publications listed below are provided in softcopy form in the DB2 DataJoiner package along with other pertinent DB2 publications. The specific publications listed below can be ordered in hardcopy form separately for a fee immediately after general availability. To order contact your IBM representative or call the IBM NA Sales Center at 800-IBM-CALL and refer to Priority Code "SE010".
Order
Title Number
DB2 DataJoiner V2.1.1 Administration SC26-9146
Guide
DB2 DataJoiner V2.1.1 Generic Access SC26-9147
API Reference
DB2 DataJoiner V2.1.1 Application SC26-9148
Programming and SQL Reference
Supplement
DB2 DataJoiner V2.1.1 Message and SC26-9149
Problem Determination Guide
IBM Replication Guide S95H-0999
The Order Number listed below includes all the publications mentioned above and other pertinent DB2 publications. This library of publications can be ordered for a fee immediately after general availability. To order, contact your IBM representative.
Order
Title Number
DB2 DataJoiner Library SBOF-5289
Displayable Softcopy Publications: Publications for DB2 DataJoiner Version 2.1.1 are offered in softcopy form, and are included in the basic machine-readable material as part of the install image. The files pertinent to each product are shipped on the product CD-ROM. To assist with the initial installation, each product's Planning, Installation, and Configuration Guide book is provided in hardcopy within the product box, as well as on the product CD-ROM in displayable form.
To see what manuals are provided on a particular product's CD-ROM, refer to the section on Packaging.
The displayable manuals can be viewed using an HTML browser installed on your system.
The CD-ROMs also contain Postscript files which are printable versions of the documents. These files can produce high-quality reproductions of the documentation on local laser printers.
Specified Operating Environment
Hardware Requirements
DB2 DataJoiner Version 2.1.1
Hardware Requirements for Windows NT Users: The following shows the minimum amount of disk space that is required and the minimum memory usage of each DataJoiner component. This information will be helpful in planning more sophisticated systems with a large number of concurrent clients or databases.
The amount of disk space and the amount of memory listed here are averages. The actual amounts that are required depend on the functions used.
To install DataJoiner, you need:
- An Intel type microprocessor-based system.
- AS/400 (R) with IPCS feature
- A CD-ROM reader.
To estimate the memory requirements and disk requirements for a particular configuration, add the recommended memory size for each installed function and application that is to be run concurrently. Include an allowance for your application data requirements and buffer requirements.
Working set memory includes the parts of a program's executable code and data areas that are being used intensively. Working set memory figures assume that default values are used.
The memory requirement is less if you do not run all installed functions and applications concurrently. (System memory requirements are based only on applications and operating system functions that run concurrently.)
Having less memory than the calculated recommended memory size can increase the time that is required to switch from one function application to another, reduce keystroke responsiveness, reduce throughput, and increase the size of the virtual memory paging space that is required.
Table for Estimating Disk and Memory Requirements
Memory Disk
DataJoiner Server (MB) (a) (MB)
DataJoiner (base) (b) 16 100
For first local application 2.2 5.4
For each additional remote
client 0.31 0.22
For each additional concurrent
database (c) 2 25
For each additional concurrent
instance 7 10
Administrator's Toolkit NA 24
East Asian Conversion Support NA 4.5
SDK Sample Programs NA 2
Online documentation in HTML
Format (English) NA 16
NA = Not applicable
(a) Additional memory for some database configuration parameters,
including the database buffer pool or the sort heap, might be
required depending on your workload.
(b) Assumes one remote process that is using the local database, on
one instance. DataJoiner base includes communications support
and the Apply program for replication.
(c) These recommended values do not reflect the resources needed to
create a database; they reflect resources needed to connect to
a database only.
The extra disk space for each additional database is for table definitions and internal structures for each database and does not include user data; therefore, the amount of extra disk space required is subject to many variables. Actual requirements may differ.
The default configuration allocates three log files, each 10 KB in size. These logs can be relocated to another file system, and can be made larger or smaller as required.
Hardware Requirements for AIX Users: This section identifies the hardware requirements for DataJoiner only.
The minimum hardware configuration for DataJoiner is a machine that is capable of:
- Reading a CD-ROM.
- Supporting the appropriate version of AIX, as documented under Software requirements.
- The fixed-disk requirements for installing product files on the target machine
- The fixed-disk requirements and memory requirements for each instance of the product
Memory and Disk Requirements: This section summarizes the memory requirements and disk requirements that are related to DataJoiner. To estimate the memory requirements and disk requirements for a particular configuration, add the recommended memory size for each installed function and application that you plan to run concurrently.
The memory requirement is less if you do not run all installed functions and applications concurrently. System memory requirements are based only on applications and operating system functions that run concurrently.
Using less than the calculated recommended memory size can increase the time that is required to switch from one function or application to another, reduce keystroke responsiveness, reduce throughput, and increase the size of the virtual memory paging space that is required.
Recommended Memory Sizes: The following table provides the recommended memory size in Megabytes (MB) for concurrent operation of various functions and the recommended disk size in MB. Use he the table to calculate your requirements.
Memory Disk
Functions (MB) (MB)
Requirements for Product Files (a)
DataJoiner base (djx) NA 60.0
DRDA (R) AR AS (drda_ar_as) NA 1.1
Classic SNA (djx_classic_sna) NA .22
SNA clients (djx_sna_clients) NA .17
DBA Tool (djx_dba) NA 1.1
DBA Tool messages per locale
(msg.*.dba) NA .9
Messages per locale
(msg.*.djx) NA 1.1
Requirements for each Instance of DataJoiner
Instance Base (b) buffer (c) +2.7 .75 (d)
Instance Base for
Classic Connect (b) buffer (c) 5.0 .75 (d)
For each additional
concurrent database buffer (c) +1.7 1.1 (d)
Memory Disk
Functions (MB) (MB)
DataJoiner Instance Requirements for each Client
Connection
For each concurrent local
user or application 1.0 NA
For each concurrent
spatial application n (e) * 1.2 NA
For each concurrent
remote client .75 NA
For each Informix data
source accessed .85 NA
For each Classic Connect
data source accessed 2.5 NA
For each other data source
accessed, other than Informix
or Classic Connect .18 NA
NA = Not applicable
(a) 15 MB of additional temporary space is required during
installation.
(b) Assumes one process using one local database on one instance.
(c) Additional memory for some database configuration parameters,
including the database buffer pool or the sort heap, might be
required depending on your workload. The buffer pool default
is 4 MB. If you decide later that the buffer size needs to
change, see the DB2 Administration Guide for instructions on
how to change it. The buffer pool applies to locally stored
DataJoiner data only, not data that is retrieved from data
sources. Keep this fact in mind when you read instructions in
the DB2 Administration Guide.
Working set memory includes the parts of a program's executable
code and data areas that are being used intensively. Working
set memory figures assume that default values were accepted.
(d) The extra disk space for each database is for table definitions
and internal structures for each database and does not include
user data. The extra disk space is subject to many variables,
so actual requirements might differ.
The default configuration allocates three log files, each 4 MB
in size. These logs can be relocated to another file system
and can be made larger or smaller as required. See the DB2
Administration Guide for more information.
(e) n is the maximum number of ADT parameters that are passed to a
spatial function in your query. For example, the query SELECT
cust_id FROM customers WHERE within (loc, buffer(loc, 100)) has
four parameters (100, loc, buffer(loc,100), and loc). If this
is the largest query in your application, the amount of working
set memory required is 4 * 1.2 = 4.8 MB.
Software Requirements
DB2 DataJoiner Version 2.1.1
Software Requirements for Windows NT Users: Machines running one of the following levels of the Windows NT operating system:
- Windows NT Workstation, Version 4.0
- Windows NT Server, Version 4.0
- Products running on Windows NT support communications with MVS,
OS/390 (R), VSE, VM and AS/400 databases using SNA (APPC), TCP/IP,
and MPTN (APPC over TCP/IP) protocols. These products can support
all of these protocols at the same time.
- For direct connection to MVS, OS/390, VSE, VM and AS/400 databases
via SNA (APPC), one of the following communications products is
required:
- IBM Communications Server for Windows NT Version 5.0, or later
- IBM Personal Communications for Windows NT Version 4.1, or later
- Microsoft (TM) SNA Server Version 2.11, or later
- For direct connections to host databases via TCP/IP, no additional software is required.
- DB2 Servers running on OS/2 (R) support communications with remote
clients via TCP/IP, NetBIOS, IPX/SPX, and SNA (APPC) protocols.
DB2 servers can support all of these protocols at the same time.
- Windows NT supplies all the communication support required to establish TCP/IP, NetBIOS, IPX/SPX, and Named Pipes connections. Therefore, no additional software is required for supporting remote clients or connecting to the DB2 Universal Database (R) Servers.
- IBM DataJoiner
- IBM DB2 Universal Database, Version 5.0
- IBM DB2 Common Server, Version 2 and higher
- IBM DB2/MVS V2R3 with APAR PN43153, UN75958, UN54600, UN56735
- IBM DB2/MVS V3R1 with APAR PN70612, UN42626, UN54601, UN56736,
UN73393
- IBM DB2/MVS V4R1 with APAR PN70612
- IBM DB2 for OS/390
- IBM SQL/400 (R) (DB2 for OS/400 (R)) V2R2 with PTFs SF13747 and
SF13748; or in a DBCS environment, IBM SQL/400 V2R2 with SF31979
- IBM SQL/400 (DB2 for OS/400) V3R1 with PTF SF23247 or higher; or
in a DBCS environment, IBM SQL/400 V3R1 with SF32970
- IBM DB2 for OS/400 V4R2
- IBM SQL/DS (TM) V3R3 with APAR PN43497 or higher
- IBM DB2 for AIX V1
- IBM DB2 for HP-UX V1.2
- IBM DB2 for Solaris Operating Environment V1 and V1.2
- IBM DB2/PE
- Oracle V7.0.13 or higher via Oracle SQL*Net or Oracle Net8
- Oracle V8 or higher via Oracle SQL*Net or Oracle Net8
- Oracle Rdb via Oracle ODBC driver
- Sybase V10 or higher via Sybase Open Client (CT (R)-LIB only)
- Sybase SQL Anywhere via ODBC driver
- Microsoft SQL Server V4.21 or higher via 32-bit ODBC driver
- Informix-OnLine V7.1 (non GLS, XPS, and SE versions only) via
Informix ESQL/RT or equivalent libraries
- ODBC, X/Open CLI-compliant data sources through the generic access
API and via Microsoft 32-bit ODBC driver
- Microsoft Jet Database (Replication only)
- Other relational and non-relational data sources (requires CROSS ACCESS Corporation's CrossAccess Data Delivery System or Information Builders Incorporated (IBI) EDA/SQL)
- Replication to Oracle Rdb
- V1.2 Runstats tool
- Native two-phase commit
- Multiple installations of DB2 products at the same time (example: DB2 DataJoiner, V2.1 and DB2 UDB, V5.0)
- Access to IMS (TM) and VSAM via DataJoiner Classic Connect
Software Requirement for AIX Users: IBM RS/6000 (TM) and Bull workstations running AIX Version 4.1.4 or higher
or
IBM AIX Version 3.2 for RS/6000 at modification 5 or higher with the following PTFs: U403173, U412397, U412815.
To take advantage of the DB2 Spatial Extender option, AIX Version 4.1.4 or higher is required.
Host Communications
- DB2 Connect (R) products running on AIX support communications
with MVS, OS/390, VSE, VM and AS/400 databases using SNA (APPC),
TCP/IP, and MPTN(APPC over TCP/IP) protocols. DB2 Connect
products can support all these protocols at the same time.
- For direct connection to MVS, OS/390, VSE, VM and AS/400 databases
via SNA(APPC), one of the following communication products is
required:
- IBM SNA Server for AIX V3.1.0 or later
- IBM Communications Server for AIX V4 or later
- Bull DPX/20 SNA/20
- For direct connections to host databases via TCP/IP, no additional software is required.
- IBM DataJoiner
- IBM DB2 Universal Database, V5.0
- IBM DB2 Common Server, V2 or higher
- IBM DB2/MVS V2R3 with APAR PN43153, UN75958, UN54600, UN56735
- IBM DB2/MVS V3R1 with APAR PN70612, UN42626, UN54601, UN56736,
UN73393
- IBM DB2/MVS V4R1 with APAR PN70612
- IBM DB2 for OS/390
- IBM SQL/400 (DB2 for OS/400) V2R2 with PTFs SF13747 and SF13748;
or in a DBCS environment, IBM SQL/400 V2R2 with SF31979
- IBM SQL/400 (DB2 for OS/400) V3R1 with PTF SF23247 or higher; or
in a DBCS environment, IBM SQL/400 V3R1 with SF32970
- IBM DB2 for OS/400 V4R2
- IBM SQL/DS V3R3 with APAR PN43497 or higher
- IBM DB2 for AIX V1
- IBM DB2 for HP-UX V1.2
- IBM DB2/PE
- IBM DB2 for the Solaris Operating Environment V1 and V1.2
- IBM IMS Version 2 or higher via DataJoiner Classic Connect
- IBM VSAM DFP V2.3 or DFSMS (TM) V1.1 via DataJoiner Classic
Connect V1.2
- Oracle V7.0.13 or higher via Oracle SQL*Net or Oracle Net8
- Oracle V8 or higher via Oracle SQL*Net or Oracle Net8
- Sybase V4R6 or higher via Sybase Open Client (DB-LIB only)
- Sybase V10 or higher via Sybase Open Client (CT-LIB or DB-LIB)
- Microsoft SQL Server V4.21 or higher via Sybase Open Client
(DB-LIB only) or Visigenic 1.1 or higher (for AIX 3.2.5) or
Visigenic 2.0 or higher (AIX 4.1 and above)
- Microsoft Jet Database (Replication only)
- Informix OnLine V5 or V6 via Informix Net V5.03 or higher and
ESQL/C V5.03 or higher libraries
- Informix OnLine V7.1 (non GLS, XPS, and SE versions only) via
Informix ESQL/RT or equivalent libraries
- ODBC, X/Open CLI-compliant data sources through the generic access
API (requires ODBC driver on the DataJoiner server)
- Other relational and non-relational data sources (requires CROSS ACCESS Corporation's CrossAccess Data Delivery System
- Replication to Oracle Rdb
- Access to Oracle Rdb
- V1.2 Runstats tool
- For Windows NT APPC connectivity, you must install the SNA client
support of Microsoft SNA Server, V2.11, or later.
- Net.Data (TM) for Windows NT
- Web Server: A CGI-compatible Web server
- Corequisite Software:
- Access to a local DataJoiner for Windows NT, V2.1,
-- or --
- Access to any remote DataJoiner through DDCS for Windows NT, V2.3, or later, or DB2 Client Application Enabler for Windows (TM) 95 and NT, V2.1, or later
- Access to a local DataJoiner for Windows NT, V2.1,
- Web Server: A CGI-compatible Web server
- Applications that access the DataJoiner Servers can be written in any of the languages supported for the platform on which you are developing. An application development environment is provided with each DB2 SDK. The supported languages include: C, C++, COBOL, and FORTRAN compiled languages and the REXX interpreter are supported where available.
The DB2 Client Application Enabler on either Windows 95 or Windows NT requires one of the following communications products:
- For IPX/SPX, NetBIOS, or TCP/IP, the base operating system
provides support.
- The DB2 SDK for Windows 95 and NT has the same software requirements as DB2 Client Application Enabler for Windows 95 and NT.
DB2 CAE, SDK and Net.Data for AIX
The CAE's have the same software requirements as DB2 DataJoiner Version 2.1.1
Note: If you want to use Distributed Computing Environment (DCE) you require a DCE product that is provided by the AIX Version 4.1.4 operating system with its latest DCE PTF.
DB2 CAE and SDK for HP-UX
Operating system- HP 9000 Series 700 or 800 system and the following:
- HP-UX Version 10.10, or later
- The following patches are required:
- For HP-UX Version 10.20: PHSS_10556, PHSS_10436,
- For HP-UX Version 10.10: PHSS_10437
- For systems with the ANSI C or C++ compilers: PHSS_10261, PHSS_7075, PHSS_9096 for C++
- APPC or TCP/IP
- For APPC connectivity, you require either of the following:
a) HP-UX V10.10 for SNAplusLink VA.10.10
b) HP-UX V10.10 for SNAplusAPI VA.10.10
- The HP-UX base operating system provides TCP/IP connectivity.
- Note:
a) To support database clients using IPX/SPX, the following IPX/SPX software must be installed: NetWare V3.12 for the HP 9000.
b) If you want to use DCE you require a DCE product that is provided by the HP-UX V10 or later base operating system.
- For APPC connectivity, you require either of the following:
Operating system- System 7.5, or later
Communications:
- TCP/IP
- For TCP/IP Connectivity you require MacTCP V2.0.6.
- Note:
- If you are running in a 68K environment, you need to install Apple Shared Library Manager (ASLM) V2.0, or later.
Operating system:
- OS/2 Warp Version 3 or Version 4
- OS/2 Warp Connect Version 3
- OS/2 Warp Server Version 4
- OS/2 Warp Server Advanced Version 4
- OS/2 Warp Server SMP
- APPC, IPX/SPX, Named Pipes (Local), NetBIOS, or TCP/IP
- For APPC connectivity you require IBM Communications Manager, V1.x, or later
- For NetBIOS connectivity, you require IBM NTS/2, V1.0, IBM Communications Manager, V1.1, or IBM OS/2 LAN Requester.
- For IPX/SPX connectivity you require Novell NetWare requester, V2.10, or later.
- For TCP/IP connectivity you require IBM TCP/IP, V2.0, or later.
- The OS/2 base operating system provides Named Pipes (Local) connectivity. Named Pipes is supported in DOS and WIN-OS/2 (R) sessions.
- OS/2 Warp Server provides the SystemView (R) LAN client that SystemView LAN needs for installing clients and servers.
- Net.Data requires OS/2 Warp Version 3, or later, and a Web server such as the IBM Internet Connection Server.
- For DCE Cell Directory Services Support (CDS) for DB2 Client Application Enabler for OS/2 you must install IBM Distributed Computing Environment Cell Directory Service client, V2.10, on each client workstation.
Operating system- Intel Based personal computer supported by SCO OpenServer and SCO OpenServer, V5.0.2, or later.
Communications:
- APPC, IPX/SPX, or TCP/IP
- For APPC Connectivity, you require Interface Systems CLEO SNA Version 4.1.1.1.
- The SCO OpenServer base operating system provides IPX/SPX and TCP/IP connectivity.
Operating system- Silicon Graphics IRIX, Version 5.3, or later
Communications:
- TCP/IP
- Note: The Silicon Graphics IRIX base operating system provides TCP/IP connectivity.
Operating system- Siemens Nixdorf RM200 or RM400 or RM600 system and the following:
- SINIX-N or SINIX-Y Version 5.42, or later
- Reliant UNIX (R)
- APPC or TCP/IP
- Note:
a) For APPC connectivity you require the following:
- SINIX TRANSIT-SERVER Version 3.3, SNA Communications Server
- SINIX TRANSIT-CLIENT Version 3.3 SNA Communications Server/ Local Function
- SINIX TRANSIT-CPIC Version 3.3 SNA LU6.2 Communication and CPI-C
Operating system: Solaris SPARCstation and the following:
- Solaris V2.5.1, or later,
- 103600-13
- 103640-08
- APPC or TCP/IP
- For APPC connectivity you require SunLink SNA 9.0 and the
following:
a) SunLink P2P (R) LU6.2 9.0
b) SunLink PU2.1 9.0
c) SunLink P2P CPI-C 9.0
- The Solaris base operating system provides TCP/IP connectivity
- For APPC connectivity you require SunLink SNA 9.0 and the
following:
- Note:
- For database clients using IPX/SPX the following IPX/SPX software must be installed: SolarNet PC Protocol Services 1.1 with IPX/SPX
- If you want to use DCE, you require Transarc DCE Version 1.1 for Solaris 2.5 and 2.5.1, patch level 18, or higher.
Operating system
- Microsoft Windows 3.1
- Microsoft Windows for Workgroups
- IPX/SPX, NetBIOS, or TCP/IP
- For IPX/SPX connectivity, you require the Novell NetWare client for Windows, which comes with Novell Netware Server, Version 3.x or 4.x; or Novell NetWare Workstation for Windows, Version 1.0, or later, with the latest update kit installed
- For NetBIOS connectivity, you require the LAN Adapter and
Protocol Support in any of these products:
a) IBM LAN Support Program Version 1.2.1, or later
b) DOS LAN Services (LAN Server 4.0)
c) Banyan Vines NetBIOS Version 5.52
d) NetBEUI (available with Microsoft Windows for Workgroups 3.11)
- For TCP/IP connectivity, you require one of the following:
a) IBM TCP/IP for DOS Version 2.1.1, or later
b) PC/TCP Network Software for DOS Version 2.3, or later, from FTP Software Inc.
c) TCP/IP compliant with the Windows Sockets, Version 1.1 specification
Operating system
- OS/2 Warp Version 3 or 4
- OS/2 Warp Connect Version 3
- OS/2 Warp Server Version 4
- OS/2 Warp Server Advanced Version 4
- OS/2 Warp Server SMP
- NetBIOS, IPX/SPX, TCP/IP, or Named Pipes (Local)
- For NetBIOS connectivity, you require IBM NTS/2, Version 1.0, IBM Communications Manager, Version 1.1, or IBM OS/2 LAN Requester
- For IPX/SPX connectivity, you require Novell NetWare client for OS/2, Version 2.10, or later, with virtual session support.
- For TCP/IP connectivity, you require IBM TCP/IP for OS/2 with the Windows Access kit.
Operating system- Windows 95 4.00.950, or later
Communications:
- NetBIOS, IPX/SPX, TCP/IP, or Named Pipes
- The Windows 95 base operating system provides NetBIOS, IPX/SPX, TCP/IP, and Named Pipes connectivity.
Operating system
- Windows NT, Version 3.51
- Windows NT, Version 4.0, or later
- APPC, NetBIOS, IPX/SPX, TCP/IP, or Named Pipes
- The Windows NT base operating system provides NetBIOS, IPX/SPX, TCP/IP, and Named Pipes connectivity.
- For APPC connectivity, you require one of the following
products:
a) IBM Communications Server for Windows NT, Version 5.0
b) Microsoft SNA Server, Version 2.11, or later, on the LAN. You do not have to install the SNA Server on the same workstation as the DB2 Client Application Enabler for Windows NT
c) PCOMM AS/400 and 3270 Version 4.1, or later
d) Wall Data Rumba
Replication Considerations: If you are planning on using DataJoiner to replicate data, here is some information you will need to know:
- The replication administration tool runs on a Windows 95 or NT
workstation and accesses DataJoiner via the DB2 CAE for either of
these Windows platforms. This means that you will configure the
DataJoiner for Windows NT instance for remote or local Client
Access, based on whether or not the replication administration
tool is installed on the same workstation as DataJoiner.
- Access to different types of data sources is achieved as follows:
- Both the replication administration tool and the Apply program
must use DataJoiner's data access modules to access non-IBM
data sources.
- To access DB2 for CS or DB2 Universal Database data sources,
the Apply program can use DataJoiner's DB2RA protocol, while
the replication administration tool can access these data
sources directly through the CAE.
- For replication that involves access to IBM IMS/ESA (R)
non-relational databases, you need DataPropagator NonRelational
(DPropnr).
- To access DB2/MVS data sources, Apply should go through
DataJoiner DRDA AR functionality, while the replication
administration tool can use DataJoiner DRDA AR functionality,
DRDA AR functionality on another workstation, or DB2 Connect on
another workstation.
Consider network performance when deciding how to access data sources. For example, using DDCS for Windows NT on the same workstation as opposed to going to another workstation to access DataJoiner DDCS and subsequently DB2/MVS. This is dependent on your site's network.
- Both the replication administration tool and the Apply program
must use DataJoiner's data access modules to access non-IBM
data sources.
- When replicating from one or more non-IBM relational databases,
one DataJoiner database is required for each non-IBM database.
Plan accordingly for the file space and memory impact. When
replicating to one or more IBM relational databases, all can be
accessed through a single DataJoiner database, thus saving
resources.
- When replicating from non-IBM databases to DB2/MVS databases,
Apply/MVS typically is used to replicate data. If Apply/MVS is to
be used rather than the Apply component within DataJoiner,
configure DataJoiner as a DRDA application server.
- When replicating from Oracle databases, the DataJoiner database
you create to access Oracle must be created with the COLLATE USING
IDENTITY clause.
- For existing replication installations that used DataPropagator
Relational (DPROPR) Version 1, there is no migration program to
IBM Replication (the replication tool used in DB2 UDB Version 5).
You must use DataJoiner's replication administration tool to set
up your replication configuration.
- The DPROPR V1 Capture program cannot be used with the DataJoiner Apply program; you must use the DB2 DataPropagator V5 Capture program.
The Client Application Enablers are the same as DB2 Universal Database V5.0. They will work with DataJoiner Version 1.1 and 1.2 as well as DB2 DataJoiner Version 2.1.1
Cryptography -- Domino (TM) Go Webserver
Limitations: DB2 DataJoiner Version 2.1.1 includes an administration tool for replication called DB2 DataJoiner Replication Administration, which runs on Windows NT or Windows 95. This tool is only available as a US English version. Our intent is to enhance the tool to include NLS languages in a later release.
Current limitations on the DB2 Spatial Extender apply to both the NT operating system and the AIX operating systems.
- The Geocoder shipped with DB2 DataJoiner V2.1.1 Spatial Extender
feature which converts address data into spatial data (that is,
latitudes and longitudes) requires address data to be in the
format of a U.S. address (that is, number, street name, street
designation, City, State, ZIP code). Geocoding to the street
level requires a country's street map data and a corresponding
utility to convert non-US address data to spatial data (for
example, latitudes and longitudes). Contact a local ESRI
Distributor in the respective country for information on how to
obtain these additional components for an additional charge. A
complete list of World Wide ESRI Distributors can be found in the
DB2 Spatial Extender Introductory Bundle which is included in the
product box.
- Spatial data can only be stored in DataJoiner; although, the DB2
Spatial Extender queries can span all the other supported data
sources. Only DataJoiner databases can be spatially enabled.
Nicknames, type mappings, and function mappings are not applicable
to spatially-enabled databases. Spatial function is available
from a remote DataJoiner server only by using pass-through.
Furthermore, replication between tables with spatially enabled
columns is not supported.
- The Spatial Extender implements the OpenGIS SQL specification
through spatial data types, spatial functions, and spatial
indexes. The currently supported data types are point, line, and
polygon. These can be used as column data types in both CREATE
TABLE and ALTER TABLE statements. However, the following
limitations apply:
- The with default clause is not allowed. Use of the clause will generate an error.
- The LOB options clause is not necessary, nor is it allowed. Use of the clause will produce a syntax error.
- Some general limitations on spatially-enabled columns are:
- The functions order by, group by, avg, sum, min, max, count, distinct, and length are not allowed.
- The column cannot be a primary key or foreign key. If it is, a syntax error will result.
- The columns cannot be included in the insert column list for import and load commands.
- The column cannot be included in the select column list for export.
- Capture and apply have the same restrictions for spatial data types as they do for LOBs.
- runstats will not gather statistics on spatial columns or spatial indexes.
- db2 reorg table cannot reorganize a table with a spatial index.
- db2 reorg will not recognize any LOB data for a table that has a spatially-enabled column.
- Replication to Oracle Rdb
- Access to Microsoft Jet Database
- V1.2 Runstats tool
- Native two-phase commit
- Multiple installations of DB2 products at the same time (example: DB2 DataJoiner Version 2.1.1 and DB2 UDB, Version 5.0)
- Access to IMS and VSAM via DataJoiner Classic Connect
- Replication to Oracle Rdb
- Access to Oracle Rdb
- Access to Microsoft Jet Database
- V1.2 Runstats tool
- The database system monitor can be used to:
- Better understand how the database manager works
- Improve database and application performance
- Tune configuration parameters
- Determine the source and cause of problems
- Understand user and application activity within the database manager.
- Visual explain graphically shows the access plan for an SQL
statement chosen by the database manager's optimizer. With this
information, you can:
- Tune SQL statements for better performance
- Model the impact of environmental changes on SQL statements
- Determine the source of problems in SQL statements.
- With the performance monitor you can:
- Define your own statistics, in addition to the default set provided
- Determine and analyze performance problems in the database manager or database applications
- Tune SQL statements for better performance
- Identify exception conditions based on thresholds you define.
IBM servers for Windows NT supports the use of the Windows NT Performance Monitor for the tracking of database events and usage at operating system level.
Planning Information
The following notes assist the planner in determining customer requirements for the licensing and entitlements. These comments supplement, and do not replace, those found in the Terms and Conditions and the Usage Restriction sections.
- The pricing and charges for DB2 DataJoiner Version 2.1.1, as shown
in the Charges Section are offered to enable customers to
purchase, and pay for, only the authorizations and entitlements
needed for their unique system setup. The DB2 DataJoiner
Version 2.1.1 entitlements must be obtained separately for
installs, processors, and users (which includes Microsoft Jet
Database replication users). Each of the DB2 DataJoiner
Version 2.1.1 program packages announced today come with
entitlements for installation on one server, by one user,
utilizing one processor, and any of the DB2 data sources, but no
non-DB2 data sources. Additional Entitlements must be purchased
if the customer
- a) Needs more than one installation. You can purchase additional Program Packages (complete with CD-ROMs, Planning, Installation and Configuration books) or purchase additional licenses that provide a Proof of Entitlement only. These are available at a slightly reduced price.
- b) Needs more than one user. If more users are required, then additional user entitlements may be purchased in quantities of 1.
- c) Needs Other Relational Data Sources. Where the customer requires access to a non-DB2 relational data source (Informix, Microsoft SQL Server, Oracle, Oracle Rdb, or Sybase), the customer must obtain additional Other Relational Data Source entitlements available in quantities of 1. DB2 DataJoiner Version 2.1.1 includes entitlement for access to all the DB2 family of databases, including all instances of DB2 databases. Orders for Other Relational Data Source entitlement result in the shipping of a Proof of Entitlement to the customer.
- d) Needs more than one processor. Additional Entitlements for processors may be purchased in quantities of 1 processor. Orders for these Entitlements result in the shipping of a Proof of Entitlement to the customer.
- When a customer purchases a DB2 DataJoiner Version 2.1.1 that product or entitlement will be provided with a Proof of Entitlement (PoE). This PoE is the sole source of evidence that the customer is entitled to use the product to the extent it is being used in their enterprise. Customers should safeguard against loss of the PoE and maintain their inventory against their purchase records. These PoEs are also used to identify eligible trade-ins when upgrading to follow-on DB2 DataJoiner product versions.
- DB2 Personal Developer's Edition, Version 5.0
- DB2 Universal Developer's Edition, Version 5.0
- Base License of DB2 DataJoiner Version 2.1.1 entitles the user to:
- 1 server installation
- 1 user
- 0 other relational data sources However, access to an unlimited number of DB2 data sources
- 1 processor
- Additional Licenses and Upgrades are available per server in
quantity of one for:
- Server install
- User
- Other relational data source
- Processor
- The pricing and charges for the Spatial Extender Feature, as shown
in the Charges Section, are offered to enable customers to
purchase, and pay for, only the authorizations and entitlements
needed for their unique system setup. The Spatial Extender Feature
entitlements must be obtained separately for installs and users.
- Non-Passport Advantage Licenses. The first installation in an
enterprise is entitled to ten users. Additional server installs
do not include any user entitlements. Hence each of the Spatial
Extender Feature License Packs comes with entitlements for
installation on one server and by ten users. Additional
Entitlements must be purchased if the customer:
- Needs more than one installation. You can purchase additional DB2 Spatial Extender licenses that provide a Proof of Entitlement only. These are available at a slightly reduced price.
- Needs more than ten users. If more users are required, then additional user entitlements may be purchased in quantities of one. A DataJoiner User Entitlement is a prerequisite for each DB2 Spatial Extender User Entitlement.
- Base License of Spatial Extender Feature entitles the user to:
- One server installation
- Ten users
- Additional Licenses are available in quantity of one for:
- server install
- user
- For Passport Advantage Licenses. Neither the Spatial Extender
Feature License Pack or Additional Server Install entitlements
include any user entitlements. Hence each of the Spatial Extender
Feature License Packs comes with entitlements for installation on
one server but without user entitlements. Additional Entitlements
must be purchased:
- If the customer needs more than one installation. You can purchase additional DB2 Spatial Extender licenses that provide a Proof of Entitlement only. These are available at a slightly reduced price.
- To cover the number of users planned. User entitlements may be purchased in quantities of one. A DataJoiner User Entitlement is a prerequisite for each DB2 Spatial Extender User Entitlement.
- Base License of Spatial Extender Feature entitles the user to:
- One server installation
- Additional Licenses are available in quantity of one for:
- server install
- user
- When a customer purchases a Spatial Extender Feature that feature or entitlement will be provided with a Proof of Entitlement (PoE). This PoE is the sole source of evidence that the customer is entitled to use the product to the extent it is being used in their enterprise. Customers should safeguard against loss of the PoE and maintain their inventory against their purchase records. These PoEs are also used to identify eligible trade-ins when upgrading to follow-on DB2 DataJoiner product versions.
User Entitlement: DB2 DataJoiner Version 2.1.1 products include entitlement for one concurrent or registered user, while the Spatial Extender Feature includes the entitlement for ten concurrent or registered users. Customers should plan on which of the two counting methods should be applied to the DB2 DataJoiner server products based on usage requirements and then obtain additional user entitlements to the extent required. A DataJoiner User Entitlement is a prerequisite for each DB2 Spatial Extender User Entitlement.
The definition of concurrent and registered users is as follows:
- Concurrent User Entitlement: A concurrent user is a person,
application (including Microsoft Jet Database replication), or
device that has established a connection to one or more databases
on one server. A user with multiple connections to a single
server counts as only one concurrent user. The one exception is
where multiple connections are made by a multiplexing program,
application server, or other program that connects to DB2
DataJoiner providing access on behalf of other users. When these
configurations are in use, customers need to consider each
concurrent user of that program as a concurrent DB2 DataJoiner
user. In the concurrent user model, the customer must ensure that
each server is licensed for the maximum number of users that will
use that server product at any one time.
The concurrent user licensing model is the only choice in situations where the identity of users is unknown. The concurrent user model is also appropriate where users require only occasional access to a particular server. Registered users may be the appropriate choice where there are many users, for example, at client workstations, who need to access databases on multiple database servers, or who connect to databases for long periods of time. Determining required licensing and monitoring the licensing requirements is the responsibility of the customer.
- Registered User Entitlement: A registered user is a person, application (including Microsoft Jet Database replication), or device that is entitled to establish one or more connections to any authorized server install of a DB2 DataJoiner Version 2.1.1 or DB2 Connect product in the customer's enterprise, either directly or through a multiplexing program or application server. Registered users of DB2 DataJoiner products are counted separately, and entitlements are not transferable between products. Customers should compare the total number of users requiring access to DB2 DataJoiner Version 2.1.1 with the sum of user entitlements provided with each install license, and obtain additional user entitlements if required.
Note:
- A connection is defined as any non-IBM relational database and associated catalog that DB2 DataJoiner is configured to access.
- Other Relational Data Sources can be measured within DataJoiner by a query of the DataJoiner "SYSSERVERS" catalog.
Processor Entitlement: The program package of DB2 DataJoiner Version 2.1.1 includes entitlement to install the server on a machine having up to one processor. Where the customer requires the DB2 server to be installed on a machine with a greater number of processors, the customer must obtain additional processor server entitlements.
Exception for Lotus (R) products: IBM allows an exception to the method for counting DB2 users as defined above for those customers who access their DB2 DataJoiner Version 2.1.1 product through Lotus Notes (R)/Domino Applications as follows: Customers do not need to count as users of their DB2 product those users who access local DB2 server data through their Lotus Notes/Domino applications. Consequently the customer will not have to purchase Proofs of Entitlement for those users. Refer to Software Announcement 298-025 dated February 3, 1998, for more information.
Installability: Database migration is supported from:
- DataJoiner for AIX, Version 1.1
- DataJoiner for AIX, Version 1.2
- DB2 DataJoiner, Version 2.1
DB2 DataJoiner Version 2.1.1 is distributed in the following
packaging configuration
DB2 DataJoiner Version 2.1.1:
- Publications:
- IBM DB2 DataJoiner V2.1.1 for AIX Operating Systems
Planning, Installation, and Configuration Guide
- IBM DB2 DataJoiner V2.1.1 for NT Operating Systems
Planning, Installation, and Configuration Guide
- IBM DB2 DataJoiner V2.1.1 for AIX Operating Systems
- Media:
- AIX -- DB2 DataJoiner Version 2.1.1 CD-ROM
- NT -- DB2 DataJoiner Version 2.1.1 CD-ROM
- CD-ROMs include a softcopy of the product documentation
- All supported hardware platforms are now provided in the same
product box.
- Net.Data, is the replacement for DB2WWW, and is included with the
DB2 DataJoiner product.
- Data Propagator Relational support (DPROPR) has been incorporated
as a base DataJoiner feature.
DataJoiner also provides a graphical user interface administration tool for defining data sources and targets. The Integrated Replication Administration tool runs on Windows NT and Windows 95 and in DB2 DataJoiner Version 2.1.1 will be available only in English.
- Domino GO Webserver has been included.
- The DB2 Spatial Extender feature trial version has been included, as well as the DB2 Spatial Extender Introductory Bundle.
- Other:
- IBM DB2 DataJoiner Getting Started Card
- IBM International Program License Agreement in Multi-language booklet
- International Program License Agreement pointer sheet
- Proof Of Entitlement
- International DB2 User Group membership card
- Client Application Enabler CD-ROMs
- Net.Data CD-ROM
- Domino GO Webserver, including CD-ROM media, license and documentation
Security, Auditability, and Control
These products use the security and auditability features of the host software.
The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.
Charges for DB2 DataJoiner Version 2.1.1 are now based on the number of installs, processors per machine, users, and other non-IBM relational data sources. Charges for DB2 Spatial Extender V2.1.1 are based on installs and users. For more detailed descriptions of these terms, and how they relate to the DB2 DataJoiner, please see the section on PLANNING.
DB2 DataJoiner Version 2.1.1: To order these programs, specify the order number, feature number, part number, program name and quantity. This package entitles the customer to run one install on a single processor, access to all DB2 data sources, and a single user.
Order
Type Feature Part
Program Name Number Number Number
DB2 DataJoiner, 5801-AAR 3049 04L9258
Version 2.1.1
ENG/NLS Program
Package -- CD-ROM
DB2 Spatial Extender, 5801-AAR 2716 31L1137
Version 2.1.1
-- License Pack
Additional Install and Use Entitlements: Authorizes the customer who has a program package to make a single copy of the program media and printed documentation. Authorization is for a machine with a single processor, access to all DB2 data sources, and a single user.
Customer must order the necessary entitlement for an additional data source, install license or processor.
Order
Type Feature Part
Program Name Number Number Number
DB2 DataJoiner, 5802-AAR 2864 31L1326
Version 2.1.1 1
additional Server
Install entitlement
DB2 Spatial Extender, 5802-AAR 2726 31L1758
Version 2.1.1
1 additional Server
Install entitlement
DB2 DataJoiner, 5807-AAR 8778 31L1327
Version 2.1.1
1 Other Relational
Data Source entitlement
for 1 Server
DB2 DataJoiner, 5807-AAR 8779 31L1328
Version 2.1.1
1 additional
Processor entitlement
for 1 Server
DB2 DataJoiner, 5807-AAR 8780 31L1329
Version 2.1.1
1 additional User
entitlement for
1 Server
DB2 Spatial Extender, 5807-AAR 1089 31L1759
Version 2.1.1
1 additional User
entitlement for
1 Server
Upgrades: Program package upgrades and media and entitles a customer to operate on a machine with a single processor, access to all DB2 data sources, and a single user.
Language: English/NLSOrder Type Feature Part Program Name Number Number Number
DB2 DataJoiner, 5803-AAR 0919 04L9340 Version 2.1.1 USA only Program Package Upgrade CD-ROM from DataJoiner for AIX, Version 1.1 or DataJoiner for AIX, Version 1.2
DB2 DataJoiner, 5803-AAR 0922 04L9341 Version 2.1.1 USA only Program Package Upgrade CD-ROM from DataJoiner for HP-UX, Version 1.1
DB2 DataJoiner, 5803-AAR 1586 04L9342 Version 2.1.1 USA only Program Package Upgrade CD-ROM from DB2 DataJoiner Version 2.1
Additional Install and Use Entitlement Upgrades: Authorizes the customer who has an additional license entitlement from a previous release to upgrade and make a single copy of the program media and documentation and to operate on a machine with a single processor, access to all DB2 data sources, and a single user.
The authorization is given by providing the customer with a Proof of Entitlement for Additional Install.
Language: English/NLSOrder Type Feature Part Program Name Number Number Number
DB2 DataJoiner, 5804-AAR 0963 31L1760 Version 2.1.1 1 addl. Server Entitlement from Upgrade DataJoiner for AIX, Version 1.1 from DataJoiner for AIX, Version 1.2
DB2 DataJoiner, 5804-AAR 0964 31L1761 Version 2.1.1 1 addl. Server Entitlement for Upgrade from DataJoiner for HP-UX, Version 1.1
DB2 DataJoiner, 5804-AAR 0965 31L1762 Version 2.1.1 1 addl. Server Entitlement for Upgrade from DB2 DataJoiner for AIX, Version 2.1
Upgrade Protection (Entitled Customers): Customers who have previously acquired Software Advantage Upgrade Protection part number 84H1228, 84H1229, 33H5881, 33H5882, 4305038, 04L7671, 04L7672, or 04L7673, and have not migrated to the Passport Advantage Offering will automatically receive their program upgrade shortly after general availability.
The DB2 DataJoiner Version 2.1.1 Passport Advantage upgrade package will grant the bearer the full CD-ROM package, a license for one processor and zero additional data source.
Licensing: IBM International Program License Agreement. Proofs of Entitlement (PoE) are required for all authorized use.
Limited Warranty Applies: Yes
Program Services: Program services will be available until January 31, 2001. The statement of service included with the program describes this service.
Money-back Guarantee: Two months, money-back guarantee for program packages
Copy and Use on Home/Portable Computer: No
Usage Restriction: Yes
DB2 Spatial Extender Feature Try and Buy: The DB2 Spatial Extender, an optional priced feature of DB2 DataJoiner V2.1.1, is shipped with each new order of DataJoiner V2.1.1, and is available for customer evaluation under a limited term trial license. The DB2 Spatial Extender trial version is licensed according to the terms of the IBM International License Agreement for Evaluation of Programs, included in the README file on the DataJoiner CD-ROM. The DB2 Spatial Extender trial version may be installed and used on a trial basis for 60 days from the date of first use of the feature. A full-use license for this feature may be obtained by ordering the appropriate billing feature in the pricing feature codes. The DB2 Spatial Extender trial version contains a time disabling device which will prevent its use upon expiration of the trial period.
Lotus Products: Lotus products included with DataJoiner V2.1.1 are licensed according to the terms and conditions of the Lotus End User License Agreement included in the DataJoiner product box.
ESRI Products: ESRI products included in the DB2 Spatial Extender Introductory Bundle are licensed according to the terms and conditions of the ESRI Desktop License Agreement included in the bundle.
Support Line: AIX
Upgrades: Customers may acquire upgrades up to the currently authorized level of use of the qualifying programs.
Volume Orders: Yes, contact your IBM representative
Passport Advantage Applies: Yes
AIX/UNIX Upgrade Protection Applies: No
Entitled Upgrade for Current AIX/UNIX Upgrade Protection Licensees: No
Variable Charges Apply: No
Academic Certified Products
Offered to: Students, faculty, staff of
qualifying higher-education
institutions
Available through: IBM Academic Certified
Remarketers Participating
college bookstores
This program is available in an Academic Edition which is offered solely to students, faculty, and staff of qualifying higher education institutions. The following Academic part numbers are available only through IBM Academic Certified Remarketers and participating college bookstores:
Part
Program Name Number
DB2 DataJoiner V2.1.1 (USA only) 04L9343
ENG/NLS Academic Edition
DB2 Spatial Extender V2.1.1 31L2004
Academic Edition
CHARGES
The charges provided in this announcement are suggested retail prices
for the U.S. only and are provided for your information only. Dealer
prices may vary, and prices may also vary by country. Prices are
subject to change without notice. For additional information and
current prices, contact your local IBM representative.
Program
Name/ Feature One-Time
Order Type Number Number Charge
Program Package 04L9258 3049 $14,999
1 additional Server 31L1326 2864 14,249
Install entitlement
Program
Name/ Feature One-Time
Order Type Number Number Charge
DB2 Spatial Extender 31L1137 2716 39,999
-- License Pack
DB2 Spatial Extender 31L1758 2726 39,249
-- additional install
1 Other Relational 31L1327 8778 3,749
Data Source
for 1 server
1 additional Processor 31L1328 8779 3,749
for 1 server
1 additional User 31L1329 8780 199
for 1 server
1 additional User 31L1759 1089 1,299
DB2 Spatial Extender
Upgrade from DataJoiner 04L9340 0919 10,999
for AIX Version 1.1, or
AIX Version 1.2
Upgrade from DataJoiner 04L9341 0922 10,999
for HP-UX Version 1.1
Upgrade from DataJoiner 04L9342 1586 7,999
DB2 Datajoiner,
Version 2.1
1 additional Server for 31L1760 0963 10,249
Upgrade from DataJoiner
for AIX Version 1.1, or
AIX Version 1.2
1 additional Server for 31L1761 0964 10,249
Upgrade from DataJoiner
for HP-UX Version 1.1
1 additional Server for 31L1762 0965 7,249
Upgrade from DataJoiner
for DB2 DataJoiner,
Version 2.1
Note: For additional Passport Advantage information, ordering information and charges, contact your IBM representative, authorized reseller, or go to the URL:
To order, contact the IBM North America Sales Centers, your local IBM representative, or your IBM Business Partner.
IBM North America Sales Centers, our national direct marketing organization, can add your name to the mailing list for catalogs of IBM products.
Phone: 800-IBM-CALL
Fax: 800-2IBM-FAX
Internet: ibm_direct@vnet.ibm.com
Mail: IBM North America Sales Centers
Dept. SE010
P.O. Box 2690
Atlanta, GA 30301-2690
Reference: SE010
To identify your local IBM Business Partner or IBM representative, call 800-IBM-4YOU.
Note: Shipments will begin after the planned availability date.
Trademarks
DataPropagator, MVS, SQL/DS, IMS, RS/6000, DFSMS, and Net.Data
are trademarks of International Business Machines Corporation
in the United States or other countries or both.
DataJoiner, DB2, AIX, AS/400, DRDA, OS/390, OS/2, DB2 Universal
Database, OS/400, SQL/400, CT, DB2 Connect, DB2 Client
Application Enablers, WIN-OS/2, SystemView, P2P, and IMS/ESA
are registered trademarks of International Business Machines
Corporation in the United States or other countries or both.
Microsoft and Windows are trademarks of Microsoft Corporation.
Windows NT is a registered trademark of Microsoft Corporation.
UNIX is a registered trademark in the United States and other
countries exclusively through X/Open Company Limited.
Domino is a trademark of Lotus Development Corporation.
Lotus and Lotus Notes are registered trademarks of Lotus
Development Corporation.
Other company, product, and service names may be trademarks or
service marks of others.