Which Edition of DB2 Connect™ is Right for You?

Paul C. Zikopoulos Leon Katsnelson

IBM Canada Ltd. Updated September 2005 for DB2 V8.2.3

Trademarks

Trademarks

The following terms are trademarks or registered trademarks of the IBM Corporation in the United States and/or other countries: AIX, AS/400, CICS, Distributed Relational Database Architecture, DB2, DB2 Connect, DB2 Universal Database, DRDA, IBM, Informix, iSeries, i5/OS, OS/400 (here-in referred to as i5/OS unless otherwise noted) Lotus, OS/390 (here-in referred to as z/OS unless otherwise noted), Parallel SYSPLEX, pSeries, System/390, VM/ESA, WebSphere, z/OS, zSeries

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc.

Other company, product or service names may be the trademarks or service marks of others.

© Copyright International Business Machines Corporation 2005. All rights reserved.

Table of Contents What is DB2 Connect?.............................................................................................................................................................................. 5

DB2 Connect FAQ................................................................................................................................................................................ 10 DB2 Connect packaging and editions ................................................................................................................................................... 13

DB2 Connect Personal Edition (DB2 Connect PE).............................................................................................................................. 17 DB2 Connect PE FAQ...................................................................................................................................................................... 19

DB2 Connect Enterprise Edition .......................................................................................................................................................... 21 DB2 Connect EE FAQ...................................................................................................................................................................... 23

DB2 Connect Application Server Edition............................................................................................................................................. 26 DB2 Connect ASE FAQ ................................................................................................................................................................... 27

DB2 Connect Unlimited Edition........................................................................................................................................................... 31 DB2 Connect UE FAQ ..................................................................................................................................................................... 32

DB2 Connect Unlimited Edition for iSeries ......................................................................................................................................... 33 DB2 Connect UE FAQ ..................................................................................................................................................................... 34

Choosing the right edition for you......................................................................................................................................................... 36 About the authors ................................................................................................................................................................................... 37

Which Edition of DB2 Connect is Right for You?

Huge volumes of data in many large organizations around the world are managed by DB2® Universal Database™ (DB2). Much of this data is managed by midrange and mainframe database servers such as DB2 for i5/OS™ (formerly known as DB2 for AS/400®), DB2 for OS/390®, DB2 for z/OS™, and DB2 for VSE & VM®. Quite simple, applications – including off-the-shelf applications like Lotus® 1-2-3, Microsoft® Excel, Brio, Crystal Reports®, Microsoft Access®, Sybase PowerBuilder®, Microsoft Visual Basic .NET®, and more – need transparent access to this data. Today’s business environments require heterogeneous database solutions at both the software and the hardware layer. The demand for such solutions has grown out of the proliferation of reengineering, re-hosting, and reconsolidation schemes to distributed platforms (Windows®, UNIX®, and Linux®) – all designed to cut costs without sacrificing the value or quality of a company’s data. The proliferation to distributed computing is associated with two trends:

Distribution of applications – some applications are being pushed to distributed markets to leverage GUI-based tools and to offload millions of instructions per second (MIPS) costs.

Distribution of data – a movement of data to distributed platforms to increases local autonomy, improve performance

(data is closer to users), and reduce costs by changing data placement. At the same time, these decisions must be balanced with the tradeoffs that these decisions provide – for example, the gold standard of today’s availability is associated with the mainframe, as well as ability to handle concurrent varying workloads (OLTP and DSS), and more. A successful data access solution will simplify application maintenance, improve performance, and minimize costs through selective data placement. However, a key requirement for leveraging economies of scale from corporate data is for this data placement to be transparent to users and applications. DB2 Connect™ is IBM middleware for connectivity to zSeries- and iSeries-based DB2 systems, as well as IMS™ data sources. It can also be used to access mainframe resources such as CICS® or VSAM. With a product like DB2

Connect, you can leverage the cost economics of the distributed platform and synergize them with the characteristics that define the iSeries and zSeries platforms as the choice of the Fortune 500. However, DB2 Connect delivers so much more than connectivity. DB2 Connect delivers an integrated development platform, a central management point for zSeries™ DB2 installations, and an extensible federated integration server as well. You can learn more about all of the benefits of DB2 Connect at: www.ibm.com/software/data/db2/db2connect/ or by reading the multipart “An Introduction to DB2 Connect: It’s More Than Meets the Eye” series by Paul Zikopoulos and Leon Katsnelson. Hands down, DB2 Connect is the best-performing solution on the market today. With continued investment by IBM, each release of this product produces tighter and more efficient integration into the DB2 code on distributed platforms. Bottom line, a DB2 Connect solution can save you money. Different editions and pricing models for DB2 Connect are available to suit the needs of different businesses. This article presents a high level introduction to DB2 Connect and includes a detailed discussion of the different editions and their respective pricing models to help you decide which edition is right for you. This article does not provide a technical overview of DB2 Connect, or competitive information from a function, feature, and benefit perspective – for that kind of information, you can refer to the previously mentioned resources.

What is DB2 Connect? DB2 Connect is software that is designed to leverage your enterprise information no matter where it is stored. For information technology professionals that have made DB2 on iSeries and zSeries servers the cornerstone of their e-business solutions, DB2 Connect provides application enablement and a robust highly scalable communications infrastructure for connecting Web, Windows, UNIX, Linux, and mobile applications to data. Standard interfaces for database access can be used with DB2 Connect. For example, DB2 Connect provides JDBC, SQLJ, ODBC, OLE DB, ADO, ADO.NET, RDO, DB2 CLI, and Embedded SQL application programming interfaces (APIs). DB2 Connect (and DB2) also delivers full support for the Microsoft .Net programming model, along with its respective integrated development environment (IDE) tooling (Visual Studio.Net) and a native DB2 .NET Data Provider (of course, the support for J2EE development is just as rich with add-ins for Rational Application Developer and more). DB2 Connect can also be used to access non-database resources such as CICS, WebSphere® MQ, IMS, or VSAM. This can deliver cost savings to shops that use these backend systems.

Skilled development resources that understand J2EE, C#, C, Visual Basic.NET, are quite common and can be leveraged at a relatively low costs. Developers that can write applications for IMS or CICS are not so common. DB2 Connect can deliver common interfaces, for which skills are readily available in the marketplace, to connect to these non-database resources. Support for a native DB2.NET managed provider was added in DB2 V8.1.2. You can build DB2 applications using any of the support .NET languages like Visual Basic.NET or C# and gain all the benefits from tight integration into the Visual Studio.NET IDE like drag-and-drop, debugging, and more. You can learn more about DB2’s support for .Net at: http://www-106.ibm.com/developerworks/offers/lp/db2/?S_TACT=103AMW30&S_CMP=dmwinDB2Intranet. DB2 Connect supports TCP/IP (for any version) and SNA (requires DB2 Connect V8.1.1 or later) connections to DB2-based zSeries or iSeries databases; however, we strongly recommend you use TCP/IP (in fact, it’ll be the only supported protocol in the future for this product). DB2 Connect can be used to access data that resides on:

MVS, OS/390, and z/OS (cumulatively referred to as z/OS for the remainder of this article, unless otherwise noted) CICS, VSAM (via DB2 stored procedures) IMS (via DB2 stored procedures) DB2 Server for VSE & VM i5/OS and OS/400 (cumulatively referred to as z/OS for the remainder of this article, unless otherwise noted) Databases and other data sources through federated database support, Web services, and OLE DB functions.

Note:

For the remainder of this article, the term host data will be used to collectively refer to DB2 data that resides on any zSeries or iSeries system.

Distributed Relational Database Architecture™ Application Requester (DRDA® AR) functionality is used to access data that resides on systems that house host data. In DB2 Version 8.1, DB2RA (the private protocol used by DB2 on distributed platforms for client/server communications on those platforms) is no longer the wire protocol that is used to handle communications to database servers on Windows, UNIX and Linux systems (often referred to as multiplatforms or distributed systems). DRDA is now used for all communications within the DB2 family (Linux, UNIX, Windows, z/OS, i5/OS, etc.). This change is transparent to applications;

however, there will be a noticeable improvement in performance from this changed architecture, as well as seamless 32-bit 64-bit interconnectivity. The change to the use of the DRDA protocol for client-server communications to database servers on multiplatforms does not change the fact that access to DB2 for z/OS and DB2 for i5/OS servers requires a valid DB2 Connect license. DB2 clients do not provide direct connectivity to zSeries and iSeries servers without a DB2 Connect license. Each copy of DB2 Enterprise Server Edition (DB2 ESE) Version 8.1 includes the DB2 Connect component that comes with five registered user entitlements that can be used to access DB2 servers on iSeries and zSeries systems. A registered user is an actual person that is specifically identified (by name) as a licensee of the DB2 Connect component (think breathing person). In other words the five free DB2 Connect registered user licenses that come with DB2 ESE cannot be used by a batch program, a multiplexing program, WebSphere Information Integrators, or any process or product that acts on behalf of these end users.

An example of client-to-server communications using DRDA is shown in Figure 1.

Figure 1. Components involved in DRDA-based access to data.

A database server that wants to respond to requests from DRDA ARs must have the corresponding DRDA Application Server (DRDA AS) functionality. All DB2 servers (with the exception of DB2 Personal Edition) have DRDA AS functionality that comes free as part of the DB2 server license (in other words, you do not need to buy DB2 Connect to get an iSeries or zSeries machine to talk to a distributed version of DB2). Since the DB2 for z/OS and DB2 for i5/OS offerings come with integrated DRDA AR support, applications deployed on these platforms can natively act as a client to a DB2 for Linux, UNIX, and Windows server without additional components or software. When DB2 Connect software is implemented, DB2 clients on distributed platforms are licensed (they are always technically enabled since they share the same communications protocol) to provide a transparent and seamless flow to any DB2 data source, as shown in Figure 2.

Figure 2. Access to DB2 data anywhere with DB2 Connect.

DB2 Connect FAQ What’s new in DB2 Connect V8? DB2 Connect Version 8.1 offers enhancements in the areas of manageability, performance, integration, scalability, availability, and application development. For example:

• Manageability is improved through new tools such as the Health Monitor and the Health Center which alert you to potential system health issues before they become real problem (you know, the ones that affect system performance); there’s enhanced DB2 Control Center functions for DB2 for z/OS and DB2 for i5/OS administrators; simplified cross-system data movement and IMS system administration, and more.

• Application availability is improved by a further enhancement of the Connection Concentrator function and the Automatic Client Reroute (ACR) facility (introduced in V8.2)

• Application performance and scalability are enhanced through improved resource utilization, higher scalability, and better performance

• 64-bit versions of DB2 Connect that exploit modern server hardware and operating environments are available • Enhanced function and ease of building DB2 server-side objects (procedures, functions, and triggers), and improved

integration with popular integrated development environments (IDEs). Support for Web Services is provided through better tooling integration and the DB2 Development Center (see http://www7b.software.ibm.com/dmdd/zones/db2dc/ for more information) provides a point-and-click development environment for ‘non-developer’ DBAs building SQL/PL business objects – no development skills required.

• Application development is enhanced by improved drivers for popular APIs like ADO.NET, OLE DB, ODBC, CLI, JDBC, and SQLJ.

My understanding is that DB2 Version 8.1 ships a Java client (Type 4 JDBC driver), which has DRDA function built into it and therefore does not need a DB2 client or DB2 Connect. Does this mean that I will no longer need DB2 Connect to access my host data source if I use a Type 4 JDBC driver? You must license access by any means for distributed clients to zSeries- and iSeries-based versions of DB2. The JDBC drivers shipped with DB2 Version 8.1 may be used for connecting to a properly licensed DB2 databases on a Linux, UNIX, or Windows servers only without DB2 Connect. These JDBC drivers are not licensed for use with DB2 for z/OS and DB2 for i5/OS database servers without DB2 Connect – again, you must purchase an appropriate DB2 Connect product. You should be aware that a Type 4 JDBC driver will give you access to DB2 host and mainframe data through the JDBC or SQLJ API, but that's it. DB2 Connect is a middleware product that is far more than a ‘bag’ of drivers. DB2 Connect offers support for the following APIs: ODBC, JDBC, SQLJ, DB2 CLI, ADO, ADO.NET, and embedded SQL. DB2 Connect also gives users transparent access through heterogeneous joins across the DB2 family, Informix IDS; access to mainframe resources like CICS, VSAM, and IMS are easily exposed through stored procedures; a connection concentrator to maximize mainframe usage; automatic client reroute for transparent failover, complete application development support including the DB2 Development Center and plug-ins for the world’s most popular IDEs, a mobile database with a complete synchronization architecture, a heath monitoring system, and more. I am currently using DB2 for z/OS. I also have a DB2 Workgroup Server Edition for AIX® server and I want to replicate data from my host machine to the distributed DB2 using Data Propagator (DPropR). Do I need to purchase DB2 Connect? Yes. DPropR does not include DRDA AR functionality. You will also need to purchase the appropriate CAPTURE and APPLY programs for the zSeries server because they are not integrated components (as in the distributed offering). I am currently using DB2 for z/OS. I also have a DB2 Enterprise Server Edition for AIX® server and I want to replicate data from my host machine to the distributed DB2 using Data Propagator (DPropR). Do I need to purchase DB2 Connect? Yes. DPropR does not include DRDA AR functionality. You will also need to purchase the appropriate CAPTURE and APPLY programs for the zSeries servers because they are not integrated components (as in the distributed offering). Of course, DB2 Enterprise Server Edition (DB2 ESE) comes with 5 free named users of DB2 Connect. You could only use this feature to support this environment if you had 5 or less actual persons (not batch jobs, processes, and so on) involved in this scenario. If you had more than 5 named individuals, you would need to license your DB2 Connect server to support this environment from scratch. Another example

where you could use the 5 free users is when setting up a read-only copy of the data (for example, replicating data from a DB2 for z/OS database to a local database on Windows that will be opened up for READ-only operations – in this example, the data replicated must be copies initiated by the DBA, not end-users). I was told that I cannot install a DB2 Connect server on a DB2 Workgroup Server Edition or DB2 Workgroup Server Unlimited Edition server, is that true? No. When DB2 Connect V8.1 became generally available this restriction was inadvertently placed into the licensing terms. IBM has not been enforcing this term since the availability date of this product and removed the restriction from the licensing documentation when DB2 Connect V8.1.2 became generally available in May 2003. However, you should be aware that you cannot install DB2 Connect PE (unless you have purchased on of the DB2 Connect Unlimited Edition packages) on a DB2 server product (Express Edition, Workgroup Server Edition, Workgroup Server Unlimited Edition, or Enterprise Server Edition). In these cases, you must license a DB2 Connect server product (DB2 Connect EE, DB2 Connect ASE, DB2 Connect Unlimited Edition for iSeries, or DB2 Connect Unlimited Edition for zSeries). For example, let’s assume that you have a DB2 Workgroup Edition server and you want to stage read-only DB2 for z/OS-based data on it for repurpose operations by distributed clients. If you only need to license one connection to the DB2 for z/OS data source (it will depend on your application), you might be considering DB2 Connect PE; however this is not allowed. A minimum, you must at least purchase a DB2 Connect EE server license with one named or concurrent user (of course, as previously noted, if you have DB2 Enterprise Server Edition installed, you may be able leverage one of the five complimentary DB2 Connect licenses that comes with it). Where can I find more information about DB2 Connect? The following Web sites contain lots of DB2 Connect information and links to even more detailed information on this product:

http://www.ibm.com/software/data/db2/ http://www.ibm.com/software/data/db2/db2connect/

I want to connect a DB2 client on Windows to a DB2 for Linux on zSeries database – what edition of DB2 Connect do I need? None! DB2 for Linux on any architecture is just the distributed code base and therefore DB2 Connect is not needed.

DB2 Connect packaging and editions DB2 Connect comes in five editions:

DB2 Connect Personal Edition (DB2 Connect PE ) – not considered a DB2 Connect server product DB2 Connect Enterprise Edition (DB2 Connect EE) – considered a DB2 Connect server product DB2 Connect Application Server Edition (DB2 Connect ASE) – considered a DB2 Connect server product DB2 Connect Unlimited Edition for zSeries (DB2 Connect UE) – considered a DB2 Connect server product DB2 Connect Unlimited Edition for iSeries (DB2 iUE) – considered a DB2 Connect server product – this is a new edition of

DB2 Connect as of V8.2.3 (September 2005). For the most part, the server editions offer the same features, functions, and benefits to workstations that require access to zSeries- or iSeries-based DB2 data. There are, however, differences between the DB2 Connect PE and the DB2 Connect server offerings. DB2 Connect PE offers a direct connection to these data sources while the DB2 Connect servers offer gateway connections which can additionally provide federation, scalability, monitoring, connection pooling and concentration, availability, and more in addition to just connectivity (of course, direct connections can be made from this software as well). The DB2 Connect server editions are really packaging and licensing 'spin-offs' of the server editions. Figure 3 illustrates the DB2 Connect PE and DB2 Connect server pillars, as well as their available subsidiary editions. In Figure 3, DB2 Connect UE and DB2 Connect iUE are combined offerings of the DB2 Connect PE and DB2 Connect server products and are therefore shown as the combination of the two offerings by the dotted line.

Figure 3. Products in the DB2 Connect family

Some IBM products have special use agreements to bundle restricted use licenses of DB2 Connect with their applications (they are not shown in the diagram). The following editions of DB2 Connect are also available for trial use through these agreements (these products are not covered in this article and are included above for completeness – however, you should note that they come with varying restrictions and are generally not appropriate for production use):

DB2 Connect for Personal Communicator (DB2 Connect for PCOMM) DB2 Connect for IBM WebSphere Commerce Business Edition for Linux for IBM eServer, zSeries, and System/390® (DB2

Connect for WCBE) DB2 Connect PE licenses DRDA AR functionality to DB2 for z/OS or DB2 for i5/OS resources for the workstation on which it is installed. This configuration is often referred to as two-tier host access. A DB2 Connect server can act as communication server for DB2 clients and licenses them for zSeries- and iSeries-based connectivity. This configuration is referred to as three-tier host access. DB2 Connect PE and the DB2 Connect servers (the example only shows DB2 Connect EE) connectivity is summarized in Figure 4.

Figure 4. DB2 Connect PE and DB2 client access through a DB2 Connect server to zSeries- or iSeries-based DB2 data

The following table is a good ‘rule of thumb’ for when to use DB2 Connect PE or a DB2 Connect server edition:

Use DB2 Connect PE when... Use a DB2 Connect server when... The application has a typical 2-tier design. You are supporting Web-based applications (like

Microsoft IIS, BEA WebLogic, IBM WebSphere Application Server, iPlanet), TP Monitor applications, or multi-tier applications.

Native TCP/IP support is available. Your application leverages Java Applets. Very large results sets are expected by the application. You require advanced server functionality like

Connection Pooling and Connection Concentration, federation support, automatic client reroute, availability, load balancing, and more.

An intermediate server is not desired due to lack of administration skill.

You need to support mobile devices in your environment.

What’s New in DB2 Connect V8.2 DB2 Connect V8.2 extends the existing DB2 Mobility on Demand feature, previously available with all DB2 for Linux, UNIX, and Windows serves since DB2 V8.1.4, to all DB2 Connect V8.2 servers. With the DB2 Mobility on Demand feature, customers can easily extend the reach of their DB2 for z/OS and DB2 for i5/OS solutions to include mobile devices such as mobile phones, PDAs, and other pervasive devices. For example, with DB2 Mobility on Demand, users of PDAs and mobile phones are enabled to conduct business transactions in environments where physical connectivity to the database server is not available (or is not financially viable) and have these transactions synchronized with the enterprise data store when connection with the database server is available: for example, the device is in a synchronization cradle or within wireless network range. The DB2 Mobility on Demand features give users licensed access to the robust high-performance DB2 Everyplace components (both the database engine and the synchronization server) in a manner that is consistent with the way the DB2 Connect server is licensed. If you use the DB2 Everyplace Synchronization Server, it also must be collocated with the DB2 Connect server. For example, if you licensed a DB2 Connect EE server for 10 registered users, you could deploy 10 copies of the DB2 Everyplace software to clients on a

myriad of pervasive devices and those clients could synchronize data changes to back end data stores through the same DB2 Connect server. Since DB2 Connect ASE, DB2 Connect UE, and DB2 Connect iUE are all licensed in an unlimited deployment model, you could deploy as many DB2 Everyplace databases as you want with these editions of DB2 Connect. What’s New in DB2 Connect V8.2.3 A new edition of DB2 Connect has been added to the family: DB2 Connect Unlimited Edition for iSeries (DB2 Connect iUE). DB2 Connect iUE is a brand new offering for the DB2 Connect family targeted at iSeries servers. It is the industry-leading solution integrating iSeries data with client-server, Web, mobile, and Services Oriented Architecture (SOA) applications. It delivers unified application development, integrated data and pervasive data functionality to IBM eServer iSeries customers. Of course, these are all standard components of DB2 Connect, but this specific package offers them an unlimited deployment model that is tailored to their environments.

DB2 Connect Personal Edition (DB2 Connect PE) DB2 Connect PE makes your company's host data available directly to applications running on personal workstations in Linux and Windows operating environments. DB2 Connect PE is well suited for typical two-tier design applications and environments where native TCP/IP support is available and an intermediate server is not desirable due to a lack of available administrative skill. DB2 Connect PE is also appropriate for processing requests that are expected to return very large result sets. DB2 Connect PE provides a direct connection to host-based DB2 data sources using TCP/IP (as shown in Figure 4) and limited SNA support. Because DB2 Connect PE is designed to address the needs of applications running on personal workstations, it cannot act as a connectivity server and cannot accept inbound requests for data (also shown in Figure 4). However, installing DB2 Connect PE on a workstation fully enables the applications on this workstation to connect not only to DB2 servers running on zSeries and iSeries, but also to distributed DB2 servers as well. To simplify deployment of DB2 Connect PE to a large number of workstations, you can share the DB2 Connect PE code on a file server (a.k.a. code server). When DB2 Connect PE is installed in this manner, it is referred to as a DB2 Thin-Connect workstation. You can also install DB2 Connect PE in a Windows Terminal Server environment. Naturally, you must ensure that the number of DB2 Connect PE licenses you purchase is sufficient to support every person that will be using the product despite it only being physically installed in one place.

A DB2 Thin-Connect workstation is a special type of DB2 Connect PE installation in which the DB2 Connect PE code is installed on a shared network drive on a file server (called a DB2 Connect Code Server). When an application that uses DB2 Connect runs, it loads the DB2 Connect .DLLs and other code from a mapped network drive (instead of a local hard disk as is the case with usual applications). Once in memory, the DB2 Connect code does not act any differently then if it were installed on a local disk. This environment is shown in Figure 5 below. The yellow arrow represents the loading of the DB2 Connect PE code, and the lightning bolts represent the network connection to the remote DB2 server. An important point to remember here is that the code is loaded into memory on the DB2 Thin-Connect workstation. The workstation on which the DB2 Connect PE code is installed (the code server) is not acting as a gateway; it simply shares the disk drive on the network. In this environment, the only difference you typically notice is the time it takes to load the DB2 Connect PE code across the network and into the memory of the Thin-Connect workstation.

Figure 5. A DB2 Thin Connect workstation loads code from a code server and makes its own connection to the remote data source

Microsoft Windows Terminal Server can be used to turn a Windows server in to a multi-user system by running applications on the server itself and using a desktop system as display screen and keyboard and mouse device. Essentially in this environment a desktop system acts as a dumb terminal to a single-user application that is running on a server machine’s CPU. A Windows Terminal Server environment is shown in Figure 6.

Figure 6. A Windows Terminal Server DB2 Connect PE installation

Remember, in Figure 5 and Figure 6, DB2 Connect PE is licensed on a per workstation basis that loads or displays the code

DB2 Connect PE FAQ When is DB2 Connect PE a good choice? DB2 Connect PE is a good choice for providing direct connectivity to DB2 for z/OS and DB2 for i5/OS database servers for traditional 2-tier client-server applications running on desktop PCs. This product is not suitable and is not licensed for deployment on multi-user systems and application servers.

If I have three employees that use the same workstation to access DB2 data residing on a DB2 for z/OS server, how many licenses for DB2 Connect PE do I need to buy? Since only one user can be logged on to the workstation at any one time, you only need to buy one license. If this were a Thin-Connect environment, each workstation would load the code locally and therefore each workstation would need to be licensed. In a Windows Terminal Server/Citrix environment, if you had 10 dumb terminals making connections to a DB2 for z/OS server, you would need 10 DB2 Connect PE licenses because the code would be imaged for 10 machines. If I want to connect my DB2 Connect PE workstation to a distributed DB2 server, what extra charges will I have to pay? As far as the DB2 Connect PE workstation is concerned, the answer is none. DB2 licensing is controlled at the DB2 server level. DB2 client software is part of the DB2 Connect PE product and no work (other than setting up the cataloged connection) is needed to connect to the remote data store. If the DB2 server to which you are trying to connect was licensed by a named user (available with DB2 Express), registered user (available with DB2 Workgroup Server Edition) or authorized user (available with DB2 Enterprise Server Edition), that server’s administrator may have to adjust that DB2 server’s user license counts. Can I install DB2 Connect PE on a DB2 server? If not, how do I license an environment where a DB2 server has only one connection to a host database (for example, replicating DBA-driven data to a READ-only local data mart), but has many DB2 client connections accessing the data? DB2 Connect PE cannot be installed on any DB2 server. If you had an environment where many clients were connecting to a DB2 server whose database was populated by a single connection to a remote host data via a replication subscription, you would need to either use the integrated DB2 Connect component (if you had purchased DB2 ESE and in this case, each license can only be an actual person) or purchase the appropriate DB2 Connect server license. For example, let’s assume that you have a DB2 Workgroup Server Edition server and you want to stage DB2 for z/OS-based data on it for repurpose operations by distributed clients. Since you only need to license one connection to the distributed DB2 server (again, assuming this is a DBA-driven load and for READ-only purposes), many might consider a DB2 Connect PE license. However, this violates the licensing policy of DB2 Connect PE since it cannot be installed on a DB2 server. Again, a minimum, you must at least purchase a DB2 Connect server edition with a single license, or leverage one of the five free registered users that come with DB2 Enterprise Server Edition (assuming your environment doesn’t break the licensing rules associated with these users as discussed in this section).

Does DB2 Connect PE support SNA connections? When DB2 Connect PE became generally available, SNA connections were not supported. DB2 Connect PE V8.1.1 (a.k.a. Fix Pack 1) provided reduced SNA support when compared to previous versions of this product. DB2 Connect PE V8.1.1 and later only supports SNA connections from a DB2 Connect PE server (DB2 clients connecting to the gateway are not supported) to DB2 for z/OS and DB2 for i5/OS servers. In addition to this, users should be aware that there is no two-phase commit support. Clients the still leverage DB2 Connect servers and the SNA protocol should be aware that future releases will entirely deprecate support for this protocol. (Hint: change now or change later.)

DB2 Connect Enterprise Edition DB2 Connect Enterprise Edition (DB2 Connect EE) makes your company's host data directly available to any supported DB2 client. Supported DB2 Version 8 clients include: AIX, HP-UX, Linux, Solaris, and Windows. Because all DB2 and DB2 Connect server products have an integrated DB2 client built into their code-base, a DB2 Connect EE workstation can also access a remote distributed DB2 server (assuming the DB2 server has been licensed correctly). DB2 Connect EE acts as a DRDA AR gateway for applications running on desktop systems. In this environment, as previously shown in Figure 4, clients connect to a DB2 Connect EE gateway and are licensed for access to DB2 for z/OS and DB2 for i5/OS data sources. Connections to the DB2 Connect EE gateway are configured the same way that connections to distributed DB2 servers are configured. In the past, DB2 Connect EE was also used for supporting not just desktop clients, but also application servers. With the introduction of DB2 Connect ASE in V8.1 and the two unlimited editions (you will learn more about these in a bit), most customers will find that these other DB2 Connect server editions provide much more flexibility with the licensing and a better price point for supporting applications servers. Therefore, DB2 Connect EE should really be the choice for supporting traditional 2-tier (fat client) applications where the resource management and administration capability not provided by the DB2 Connect PE are required. DB2 Enterprise Server Edition (DB2 ESE) includes the DB2 Connect component to provide for occasional mainframe connectivity for data replication and server administration. The DB2 Connect component of DB2 ESE server licenses (at no extra charge) five registered users to access zSeries and iSeries servers. The number of licensed users cannot be increased. If additional users need access to zSeries and iSeries servers, an appropriate DB2 Connect server product needs to be purchased and installed. Keep in mind

that these five registered users are actual people – they cannot be batch processes, other programs, and so on. In the event that you want to license a batch process, other programs, etc., then these items cannot be servicing more than 5 individual people – or you’ll have to buy a DB2 Connect license. DB2 Connect EE is licensed based on the number of users accessing the server (think of this as the people that are deriving value from access to the zSeries and iSeries data). These users can be either registered or concurrent. A registered user is a person that can be identified (by name) as somebody that uses one or more DB2 Connect EE servers. A concurrent user is really a measure of the number of people that are using the same DB2 Connect EE server at the same time. In other words, a concurrent user is a measure of the licensed capacity of a DB2 Connect server. This capacity is measured by the number of individuals (not processes or connections) using the server at any one point in time. For example, if user Jim needs access to a DB2 for z/OS database, a registered or concurrent user license is required for Jim. If a single concurrent user license was purchased, George could use the license that was obtained for Jim to retrieve data; however, both Jim and George could not use the connection at the same time because only a single concurrent license was purchased. Jim could actually use the concurrent connection and make multiple connections to the database - so long as they are Jim’s connections (they can’t be multiplexed or concentrated by an application). If a registered user license were assigned to Jim, then George could not use it and would need to purchase his own. At times it can be confusing to determine just who is a user. A good rule of thumb is: “where is the SQL request coming from?” For example, if a bunch of clients put requests into an integration server for data, and that integration server on its own makes a connection using DB2 Connect to a remote data store and populates a local repository for direct use by the clients, each of the end users (despite not actually flowing the SQL request directly to DB2 Connect) should be licensed and considered a user. Enterprises that implement the WebSphere Information Integrator (W/S II) technology often miss this licensing nuance and consider the W/S II code to be a user, however this violates the licensing terms and conditions for this product. Another example is if a DBA sets up a staged table where client update the data in it and subsequently that data is replicated back to an end data store – they too must all be licensed. Quite simply, connections made to DB2 Connect EE through other products that act as connection concentrators must be counted as DB2 Connect registered or concurrent users based on the number of users before the concentration software is utilized. Registered and concurrent licensing is very hard, or even impossible, to implement and adhere to for applications that are based on Web technologies (both InTERnet and InTRAnet). Therefore, a registered user is the only available licensing model for Web-based applications with DB2 Connect EE when the user can be easily identified (for example, a banking application). Using registered user

licenses can be cost prohibitive for applications where the potential number of users is very large, as each potential user will have to be registered and would require a license (not to mention the cost associated with administering and tracking these licenses). For this reason, consider DB2 Connect ASE or one of the DB2 Connect Unlimited Editions (depending on the back-end data store) for Web-based applications. If you plan to use the DB2 Mobility on Demand feature that is available with DB2 Connect EE V8.2 or later, you are licensed to use the DB2 Everyplace components in a manner that is consistent with how you licensed your DB2 Connect EE server. For example, if you licensed your DB2 Connect EE server for 100 registered users, then you could only deploy a DB2 Everyplace engine on each of the 100 registered user’s devices and have them synchronize their data to the back-end data store. If you chose to license your DB2 Connect EE server using a concurrent license, you could deploy as many DB2 Everyplace database engines as you want, but only the number of concurrent licenses you purchased could synchronize at the same time to the back-end data store. In either case, the DB2 Everyplace Synchronization server must be installed on the DB2 Connect EE server that you’ve licensed.

DB2 Connect EE FAQ When is DB2 Connect EE a good choice? DB2 Connect EE is a good option for 2-tier client-server applications where the additional functionality of a mid-tier connectivity server is desirable. DB2 Connect EE is suitable for environments where number of concurrent users can be easily determined, or the number of registered users is relatively small. DB2 Connect EE is not a suitable choice for supporting multi-tier client-server applications or Web-based applications because in such environments, determining the number of concurrent users is not practical and licensing registered users may be cost prohibitive and time consuming. However, in some instances, a named user license may suffice. If we are using application server software in our environment, then pricing is based on either the number of registered or concurrent users of the application, correct? No. As of DB2 Connect Version 7.2, concurrent user pricing is only available for non-Web and non-connection concentrated environments. All users must be registered or an unlimited license (provided by one of the DB2 Connect Unlimited Editions or DB2 Connect ASE) must be used.

What is the difference between a registered user license and a concurrent user license? A registered user license defines how many users can connect to a particular DB2 Connect server at any one time before any connection concentration is performed. In this case, a user is a person. This is sometimes referred to as a “user capacity” license. A registered user license specifies the name of a specific user. Registered users are licensed to use any available DB2 Connect server. For example, if an enterprise had two DB2 Connect servers and 100 users, but each server had 75 connections at any one time, you would have to purchase 150 Concurrent licenses (75 for each server) with the two DB2 Connect EE server licenses. If the same 100 users accessed both servers, you could choose to purchase 100 registered user licenses with the two DB2 Connect EE server licenses to support this query environment. We have WebSphere Application Server (WAS) installed and it serves applications and data through an InTRAnet (a Web site that is inside our company’s firewall and for use by company personnel only). At any given time, WAS only has five concurrent database connections that are controlled or 'throttled' by applications. Can I purchase 5 concurrent user licenses? No. The number of connections established by the WebSphere server, or any other server for that matter, has no influence on the number of licenses that need to be purchased. DB2 Connect EE licensing is based on the number of actual users that are using the application rather then the number of connections that an application establishes through a DB2 EE Connect server. In this scenario, you would have to buy registered user licenses for every employee that will be using the application that is running on the WebSphere Application Server. Because this is a Web-based environment, concurrent user licensing cannot be used. If the number of potential users of the application is large, DB2 Connect ASE or one of the DB2 Connect Unlimited Editions should be considered instead of using DB2 Connect EE. If I know the number of users that may be accessing my data over an InTERnet or InTRAnet application, then is that is the number of users I need to license; if I don’t know the number of users (or the maximum number of users), then I have to go with one of the DB2 Connect Unlimited Editions, right? If data access is over the Web, all users must be registered. If you cannot determine this number, you must license using one of the DB2 Connect Unlimited Editions or DB2 Connect ASE.

Is it true that the only licensing option for DB2 Connect EE in a Web environment is a registered user? Yes! If you cannot count the registered users, you must buy one of the DB2 Connect Unlimited Editions or the new DB2 Connect ASE. Does a registered user license support multiple DB2 for z/OS database accesses through a single user ID license? A registered user is licensed to access as many databases through as many licensed DB2 Connect servers as needed – even if they reside on different physical servers. These databases can be anywhere (for example: iSeries, zSeries, on the same server, continents apart, in the same line of business, or throughout the organization). A registered user license is an entitlement to an individual person, and not to a database or a server. How many DB2 Connect EE user connections come with each processor entitlement of DB2 Universal Database Enterprise Server Edition (DB2 ESE) Version 8.1? The DB2 Connect component of the DB2 Enterprise Server Edition is not licensed by connection. It authorizes five individuals; that is, five registered users per server (actual people). To license additional users, you must purchase a separate copy of a DB2 Connect server product. For example, if you needed 10 registered user licenses, and bought DB2 ESE, you would need to buy a single DB2 Connect EE server license and five registered user licenses to go along with the five complimentary connections that you get with DB2 ESE. Remember, these five users have to be people, not applications, software, batch programs and so on. This is often a source of confusion for clients. As a rule of thumb, in most cases, you will not be able to leverage these free licenses in a production environment as stated throughout this article. An example where you could use this license is when a DBA initiates a replication/copy of data to a local database for READ-only operations, or where write-backs do not occur to the back-end data source. The data the DBA create a replication subscription for cannot be from a queued up batch of SQL request from end users.

Does DB2 Connect EE support SNA connections? When DB2 Connect EE became generally available, SNA connections were not supported. DB2 Connect EE V8.1.1 (a.k.a. Fix Pack 1) provided reduced SNA support when compared to previous versions of this product. DB2 Connect EE V8.1.1 and later only supports SNA connections from a DB2 Connect EE server (DB2 clients connecting to the gateway are not supported) to DB2 for z/OS and DB2 for i5/OS servers. In addition to this, users should be aware that there is no two-phase commit support. Clients the still leverage DB2 Connect servers and the SNA protocol should be aware that future release will entirely deprecate support for this protocol. (Hint: change now or change later.)

DB2 Connect Application Server Edition DB2 Connect Application Server Edition (DB2 Connect ASE) is an edition of DB2 Connect that first became available in the Version 8.1 release. DB2 Connect ASE is the same code and product as DB2 Connect EE (or any DB2 Connect server edition for that matter). DB2 Connect ASE offers different licensing terms that are meant to address the specific needs of those customers who need to deploy multi-tier client-server or Web server applications that require access to DB2 data on the zSeries or iSeries platforms. These types of applications are characterized by use of mid-tier application servers where the majority of the application logic is running. Examples of these applications include PeopleSoft, Siebel, WebSphere, BEA Weblogic, i2, Microsoft IIS, CICS, Microsoft MTS, Microsoft COM+, WebSphere DataStage, Brio, Business Objects, COGNOS, Microstrategies, and many others. DB2 Connect ASE license charges are based on the number of processors available to the Web or Application server that use DB2 Connect to access data. DB2 Connect ASE license charges are not based on the number of processors available to DB2 Connect itself, or to the size of the backend database to which it is connecting. For example, DB2 Connect ASE license charges are the same regardless of whether DB2 Connect ASE is co-located on the same server as the application server, or installed on a separate server. In fact, you could install multiple DB2 Connect ASE servers and you will still only pay for the number of processors attached to the Application or Web server. DB2 Connect ASE is suitable for customers who feel that the growth of their zSeries environment will be on the MSU side of the accounting ledger and thus are not subject to those increased costs as they would be for DB2 Connect Unlimited Edition. If you plan to use the DB2 Mobility on Demand feature that is available with DB2 Connect ASE V8.2+, you are licensed to use the DB2 Everyplace components in a manner that is consistent with how you licensed your DB2 Connect ASE server. For example, if you

licensed your DB2 Connect ASE server on a machine with 8 CPUs, you can deploy an unlimited number of DB2 Everyplace engines and all synchronization must occur through the licensed server.

DB2 Connect ASE FAQ When is DB2 Connect ASE a good choice? DB2 Connect ASE is designed to address the need of connecting application servers to zSeries data. DB2 Connect ASE presents an economical choice for users with a limited number of application servers connecting to relatively large servers. If the number of application server processors is very large (and/or the size of the iSeries or zSeries servers are small in relation to the Web farm), one of the DB2 Connect Unlimited Editions may be a more economical alternative. For iSeries-bound connection, typically, DB2 Connect Unlimited Edition for iSeries will be a better choice – in other words, DB2 Connect ASE is well suited for environments that connect to zSeries-based data where the growth is not in the Application Server farm, but rather the MIPs/MSU consumption on the zSeries server. DB2 Connect ASE is not suitable for deployment in 2-tier client-server environments as there are no application servers present in such deployments and this pricing model would therefore not be allowed. DB2 Connect PE or DB2 Connect EE should be used to support 2-tier client-server applications. If we purchased one of the DB2 Connect Unlimited Editions, and it now seems that DB2 Connect ASE is the right approach, what do we do? Is there a migration path from a DB2 Connect Unlimited Edition package to DB2 Connect ASE? There is no program to migrate any of the DB2 Connect Unlimited Editions to DB2 Connect ASE. Since DB2 Connect licenses cannot be transferred, the choice between DB2 Connect ASE and one of the DB2 Connect Unlimited Editions must be made with consideration of future growth plans.

How is DB2 Connect ASE licensed when the application server resides on a Linux for zSeries server? DB2 Connect ASE is always licensed per processor, based on the total number of processors available the application server used by an application. In the case where the application server is on Linux for zSeries server, the number of processors is counted as follows:

• If the application server is on Linux in an Integrated Facility for Linux (IFL) engine, then DB2 Connect ASE is licensed to all IFL engines (a.k.a. processors) on that server

• If the application server is on Linux in a standard (non-IFL) engine, then DB2 Connect ASE is licensed to all standard zSeries or (a.k.a. processors).

Regardless of whether Linux is running on a dedicated engine, as a guest under z/VM, or in an LPAR, DB2 Connect ASE will be licensed to all IFL processors or to all standard processors on that server. If we run two different applications on the same application server, how many DB2 Connect ASE licenses should be purchased? DB2 Connect ASE license charges are always based on the number of processors available to the application server, regardless of the number of applications running on that server. How is DB2 Connect ASE licensed in an environment in which the application runs on a UNIX- or Windows-based server? How many licenses would you need for one 12-way pSeries server, or three 4-way xSeries servers? DB2 Connect ASE must be licensed for all processors on the application server. In the first example, the pSeries server is the application server, and it has 12 processors; therefore, 12 licenses of DB2 Connect ASE are needed. In the second example, the xSeries servers are the application servers, and there are three 4-way xSeries servers; therefore, 12 licenses of DB2 Connect ASE are needed even if only one installation of DB2 Connect is installed on a completely different server and is used to load balance across the server farm.

Is DB2 Connect ASE applicable in a gateway environment where we rely on DB2 Connect for host connectivity from a personal application such as Microsoft Excel? No, DB2 Connect ASE is not available as a licensing option if there are no application servers. DB2 Connect PE, DB2 Connect EE, or one of the DB2 Connect Unlimited Editions are designed to address the needs of organizations that require robust connectivity from a variety of desktop systems to zSeries- and iSeries-based database servers. We bought DB2 Connect ASE and installed DB2 Connect on a 2-way Windows-based SMP server. We also installed WebSphere on a 4-way SMP Linux box. The DB2 Connect code connects to 2 physically disparate zSeries boxes that are running DB2 for z/OS. How many processors do I have to license? DB2 Connect ASE is licensed by the number of processors available to the application server(s), not the number of processors available to the DB2 Connect code or the size of the remote database server. In this example, you would have to purchase 4 licenses since the Linux box where the application server is installed is a 4-way SMP server. If in this example the application server resided on an IFL partition on the zSeries box, you would license all the engines of that partition. Does DB2 Connect ASE support SNA connections? When DB2 Connect ASE became generally available, SNA connections were not supported. DB2 Connect ASE V8.1.1 (a.k.a. Fix Pack 1) provided reduced SNA support when compared to previous versions of this product. DB2 Connect ASE V8.1.1 and later only supports SNA connections from a DB2 Connect ASE server (DB2 clients connecting to the gateway are not supported) to DB2 for z/OS and DB2 for i5/OS servers. In addition to this, users should be aware that there is no two-phase commit support. Clients the still leverage DB2 Connect servers and the SNA protocol should be aware that future release will entirely deprecate support for this protocol. (Hint: change now or change later.)

We have an environment that has a farm of application servers installed. This farm talks to another tier that has an application server, which eventually talks to our legacy DB2 servers. If we want to license DB2 Connect ASE, how would we license the following environment?

2 CPUs

2 CPU

s

8 CPU

s

2 CPU

s

It depends ☺. In order to properly license DB2 Connect ASE, you need to ask: “Where is the SQL being generated?” The above example could represent a typical Web deployment scenario where the presentation logic and the business logic are separated. If the 3 2-way SMP servers are simply running the HTTP server, and the 8-way SMP box is where the SQL is generated, then you would only be required to purchase 8 DB2 Connect ASE licenses.

DB2 Connect Unlimited Edition DB2 Connect Unlimited Edition (DB2 CUE) is a special licensing package of DB2 Connect software (there are no functional differences to the other DB2 Connect servers) designed for unlimited deployments on OS/390, z/OS, and VSE/VM environments (there is a separate edition for i5/OS or AS/400 data sources). DB2 Connect UE license charges are not based on the number of users that use the product or the size of any application servers. Instead, DB2 Connect UE license charges are based on the size of the DB2 for z/OS system that it provides connectivity for in addition to a base server charge. Because of its database server capacity-charge metric, DB2 Connect UE allows users to install an unlimited number DB2 Connect PE and/or DB2 Connect servers on any number of workstations to provide connectivity to a single DB2 for OS/390, DB2 for z/OS, or DB2 for VSE & VM database server. The pricing strategy for DB2 Connect UE is to license in a way that is consistent with the way that DB2 is licensed on the zSeries. A DB2 Connect UE MSU entitlement must be obtained for each MSU on the DB2 host system, in addition to a base server license. If the host system is part of a Parallel SYSPLEX® environment, the MSUs are based on the DB2 entitlements of the entire Parallel SYSPLEX. License charges for DB2 Connect UE are not affected by the choice of platform for DB2 Connect servers, the number of users utilizing the product, or the CPUs attached to the servers where the DB2 Connect code or application servers are running. Quite simply, to license this product, count the MSU entitlements for the DB2 for zSeries system and buy the corresponding number of DB2 CUE MSU licenses in addition to the required based DB2 CUE server license. Again, DB2 Connect UE is licensed with an initial server charge, plus an additional charge per MSU measured on the database server (you should be aware that the MSU unit costs for DB2 Connect were reduced by over 90% in September 2004). Discounts under the IBM Passport Advantage program apply to all DB2 Connect products including DB2 Connect UE. If you plan to use the DB2 Mobility on Demand feature that is available with DB2 Connect UE V8.2+, you are licensed to use the DB2 Everyplace components in a manner that is consistent with how you licensed your DB2 Connect UE server. Since DB2 Connect UE gives you unlimited access to DB2 Connect servers, you could dedicate a server to handle the synchronization logic and offload the connectivity piece provided by DB2 Connect to another server. Quite simply, when you license DB2 Connect UE, you don’t need to pay consideration to data access or DB2 Everyplace deployment.

DB2 Connect UE FAQ When is DB2 Connect UE a good choice? DB2 Connect UE is ideal for those customers who either today have many applications with the need for large amounts of zSeries-based data access, or in the future anticipate the need for many applications with large amounts of mainframe data access. If I license DB2 Connect UE to connect to DB2 for z/OS in a non-data sharing SYSPLEX environment, how is the MSU license calculated? DB2 Connect UE license charges are not based on the number of users, but on the MSU entitlements of the DB2 for z/OS, DB2 for OS/390, or DB2 Server for VSE & VM server to which you are connecting. Two separate types of licenses must be ordered with this product. The first is the DB2 Connect UE host server entitlement, and the second is the appropriate number of DB2 Connect UE MSU entitlements for the entire SYSPLEX. DB2 Connect UE charges apply to any single server to which users will be connecting. Again, if the mainframe system is part of a SYSPLEX environment, MSUs are based on the DB2 entitlements for the entire SYSPLEX. The DB2 Connect ASE licensing model may be a lower cost alternative for certain configurations. However, only 1 server licensed is required. If I have DB2 Connect UE and cannot count the number of users that access my corporate data on a zSeries server over the InTERnet, but I know the number of internal users that access the data source (they use DB2 Connect PE), how do I price this environment? You don’t have to. The benefit of the DB2 Connect UE pricing model is that you don’t care (from a licensing perspective) who accesses your data, or what DB2 Connect software they use to do it. DB2 Connect UE gives users an unlimited deployment of DB2 Connect PE and DB2 Connect servers, and is priced solely on the size of the DB2 server that users are connecting to.

Does DB2 Connect UE support SNA connections? When DB2 Connect UE became generally available, SNA connections were not supported. DB2 Connect UE V8.1.1 (a.k.a. Fix Pack 1) provided reduced SNA support when compared to previous versions of this product. DB2 Connect UE V8.1.1 and later only supports SNA connections from a DB2 Connect UE server (DB2 clients connecting to the gateway are not supported) to DB2 for z/OS and DB2 for i5/OS servers. In addition to this, users should be aware that there is no two-phase commit support. Clients the still leverage DB2 Connect servers and the SNA protocol should be aware that future release will entirely deprecate support for this protocol. (Hint: change now or change later.)

DB2 Connect Unlimited Edition for iSeries DB2 Connect Unlimited Edition for iSeries (DB2 Connect iUE) is a new (as of DB2 Connect V8.2.3) edition of the DB2 Connect server family (there are no functional differences to the other DB2 Connect servers) designed for unlimited deployments on i5/OS and OS/400 environments. DB2 Connect iUE license charges differ from the model used for DB2 Connect UE, but the package also delivers an unlimited number of DB2 Connect software (both DB2 Connect PE and DB2 Connect server) licenses in this case can only be used to access i5/OS- or OS/400-based data. While DB2 Connect UE has a base server charge with an additional MSU consumption charge, DB2 Connect iUE differs in that you license all of the managed processors that are attached to the i5/OS or OS/400 operating system (this is because the DB2 server product is built into the operating system for these platforms). DB2 Connect iUE is ideal for iSeries customers looking for an unlimited licensing model. Note that charges are in no way related to the number of processors attached to the DB2 Connect iUE software itself. If you plan to use the DB2 Mobility on Demand feature that is available with DB2 Connect iUE V8.2.3+, you are licensed to use the DB2 Everyplace components in a manner that is consistent with how you licensed your DB2 Connect iUE server. Since DB2 Connect iUE gives you unlimited access to DB2 Connect servers, you could dedicate a server to handle the synchronization logic and offload the connectivity piece provided by DB2 Connect to another server. Quite simply, when you license DB2 Connect iUE, you don’t need to pay consideration to data access or DB2 Everyplace deployment.

You can learn more about DB2 Connect iUE at: http://www-306.ibm.com/software/data/db2/db2connect/edition-uei.html.

DB2 Connect UE FAQ When is DB2 Connect iUE a good choice? DB2 Connect iUE is ideal for those customers who want to keep their DB2 UDB iSeries back-end data and stored procedures and extend them to multiple platforms and many modern application development environments (.NET, Java, and so on). DB2 Connect iUE allows unlimited users to join iSeries data to multiple sources including other iSeries servers/partitions, cross platform databases (including iSeries machines running other operating systems like Linux and Windows; DB2 UDB for Linux, UNIX and Windows and Informix Dynamic Server – access to z/OS-based data sources requires additional DB2 Connect licensing), and mobile devices. Your iSeries data can also be joined with a single SQL request to Oracle and Microsoft SQL Server when coupled with WebSphere Information Integrator. DB2 Connect iUE also provides a flexible application development environment, particularly with J2EE, .NET, and PHP along with a full suite of APIs. Quite simple, with this product, there is no need to move your stable iSeries data, yet you can still leverage today’s trends in computing (SOA, and so on). If I have DB2 Connect iUE and cannot count the number of users that access my corporate data on my iSeries server over the InTERnet, but I know the number of internal users that access the data source (they use DB2 Connect PE), how do I price this environment? You don’t have to. The benefit of the DB2 Connect iUE pricing model is that you don’t care (from a licensing perspective) who accesses your data, or what DB2 Connect software they use to do it. DB2 Connect iUE gives users an unlimited deployment of DB2 Connect PE and DB2 Connect servers, and is priced solely on the number of attached processors to the i5/OS or AS/400 operating systems.

If I have an IBM eServer that I’ve partitioned with multiple partitions, some running i5/OS and some not, how would I license DB2 Connect iUE in the following scenario: Licensing DB2 Connect iUE is perhaps the easiest DB2 Connect product to license because DB2 is built into the i5/OS operating system. In this example, you would need to buy 9 DB2 Connect iUE processors even if your applications never accessed the uniprocessor i5/OS partition (shown as 13 in the figure). How is DB2 Connect iUE licensed in an environment in which the DB2 Connect software runs on a UNIX- based server with 8 processors and connects to a server that has 4 processors running i5/OS? DB2 Connect iUE must be licensed for all processors attached to the i5/OS or AS/400 operating system on the remote server – even if access to separate partitions is not planned (see the previous question). In this example, you would need to buy 4 DB2 Connect iUE licenses. The 8 processors upon which the DB2 Connect server code is installed are irrelevant since DB2 Connect iUE licensing is controlled by the number or processors attached to the i5/OS or OS/400 operating system. Does DB2 Connect iUE support SNA connections? When DB2 Connect UE became generally available, SNA connections were not supported. DB2 Connect UE V8.1.1 (a.k.a. Fix Pack 1) provided reduced SNA support when compared to previous versions of this product. DB2 Connect UE V8.1.1 and later only supports SNA connections from a DB2 Connect UE server (DB2 clients connecting to the gateway are not supported) to DB2 for z/OS and DB2 for i5/OS servers. In addition to this, users should be aware that there is no two-phase commit support. Clients the still leverage DB2 Connect servers and the SNA protocol should be aware that future release will entirely deprecate support for this protocol. (Hint: change now or change later.)

Choosing the right edition for you The following chart will help you to identify the correct DB2 Connect edition for you.

Personal Edition

Enterprise Edition within

DB2 ESE

EnterpriseEdition

Application Server Edition

Unlimited Edition

Unlimited Edition for iSeries

Appropriate for Web-based applications licensing (or when the exact number of users cannot be determined).

Appropriate for named user licensing. 5 named users Appropriate for installation-based licensing. Appropriate for use with multiplexing or concentrating software.

Priced per user or installation. Priced by the size of the application server. Priced (in part since there is a base server charge) by the size (measured in MSUs) of the zSeries server.

Priced by the number of managed processors attached to the entire iSeries server running O/S 400 or i5/OS.

Can access data in DB2 for i5/OS or DB2 for OS/400 databases.

Can access data in DB2 for z/OS, DB2 for OS/390, or DB2 for VM/VSE databases.

About the authors

Paul C. Zikopoulos, BA, MBA, is an award-winning writer and speaker with the IBM Database Competitive Technology team. He has more than ten years of experience with DB2 UDB and has written over sixty magazine articles and several books about it. Paul has co-authored the books: DB2 Version 8: The Official Guide, DB2: The Complete Reference, DB2 Fundamentals Certification for Dummies, DB2 for Dummies, and A DBA's Guide to Databases on Linux. Paul is a DB2 Certified Advanced Technical Expert (DRDA and Cluster/EEE) and a DB2 Certified Solutions Expert (Business Intelligence and Database Administration). In his spare time, he enjoys all sorts of sporting activities, running with his dog Chachi, and trying to figure out the world according to Chloë – his new daughter. You can reach him at:

.paulz_ibm@msn.com

Leon Katsnelson works in the IBM Toronto Lab where he manages a team of product managers responsible for the IBM DB2 products. Leon is a recognized expert in the areas of DB2 application development and DB2 Connect. Leon has 18 years of experience with complex database and network systems. Over the years he has helped many customers to integrate DB2 into their solutions. Leon frequently presents his experiences at user group meetings and industry conferences.