IBM Books

Quick Beginnings for OS/2 and Windows NT


Software Requirements

DB2 Connect Enterprise Edition products use communication software for establishing host connectivity and connectivity to DB2 Universal Database servers. In addition, DB2 Connect Enterprise Edition requires connectivity software to support connections from remote client workstations.

For the host connectivity, software requirements will depend on:

Server Product Requirements

Table 4 lists the operating system and communications software required for DB2 Connect.

Table 4. Software Requirements
Product Hardware/Software Requirements Communications
OS/2

  • DB2 Connect Enterprise Edition

  • OS/2 Warp Version 3 and Version 4

  • OS/2 Warp Connect Version 3

  • OS/2 Warp Server Version 4

  • OS/2 Warp Server Advanced V4

  • OS/2 Warp Server Advanced V4 with SMP Feature

  • OS/2 Warp Server for e-business

Versions of OS/2 with built-in communications capabilities such as OS/2 Warp Connect, Warp Server, Warp Server Advanced, and OS/2 Warp Version 4 are recommended.

Notes:

  1. If you plan to install DB2 Connect using TME 10 SystemView, you must have TME 10 SystemView LAN Client provided by the OS/2 Warp Server.

  2. The DB2 SNMP subagent requires DPI 2.0 support provided by the OS/2 Warp Server installed. If you plan to use DB2 SNMP subagent for system management, you will have to use OS/2 Warp Server.

APPC, IPX/SPX, NetBIOS, or TCP/IP

  • For local IPX/SPX connectivity, you require Novell NetWare Requester, Version 2.10 or later.

  • Named Pipes is supported locally in WIN-OS/2 sessions on OS/2 Warp Server.

  • For local NetBIOS connectivity, you require IBM NTS/2 Version 1.0, or IBM Communications Manager Version 1.x or later, or IBM OS/2 LAN Requester.

  • For TCP/IP connectivity, you require IBM TCP/IP Version 3.0 or later for OS/2 Warp Versions 3 and 4, and for OS/2 Warp Connect Version 3. The OS/2 Warp Server Version 4 base operating system provides TCP/IP connectivity, if selected during installation.

  • For SNA (APPC) connectivity, one of the following communications products is required:

    • IBM eNetwork Communications Server for OS/2 Warp Version 5

    • IBM eNetwork Personal Communications for OS/2 Warp Version 4.2

    • IBM Communication Server for OS/2 Version 4

Notes:

  1. If you plan to use DCE (Distributed Computing Environment) Security for authenticating users that connect to host databases, you do not have to install DCE products on your DB2 Connect workstation. However, you will have to:

    • Ensure that you are connecting to DB2 for OS/390 V5.1 database that is enabled for DCE support using OS/390 DCE Base Services Version 3 if you wish to use DB2 Connect. You must install DCE Directory Services on both the client and the DRDA Server, but you do not need DCE installed on the DB2 Connect Enterprise Edition server.

    • Ensure that client workstations, using DCE security, have a DCE product that is at OSF DCE Level 1.1 with the IBM Directory and Security Server for OS/2 Warp Version 4.

  2. If you plan to use two-phase commit with DB2 Connect and DRDA host systems, you must install the Syncpoint Manager (SPM) function and its prerequisites.

  3. The DB2 SNMP Subagent requires DPI 2.0 support provided by the OS/2 Warp Server.

  4. Installing clients and servers using TME 10 Netfinity requires TME 10 Netfinity LAN Client provided by the OS/2 Warp Server.
Windows 32-bit Operating Systems

  • DB2 Connect Enterprise Edition (Windows NT only)

  • Windows NT Version 4.0 with Service Pack 3, or later

APPC, TCP/IP, and MPTN (APPC over TCP/IP)

  • The Windows NT base operating system provides NetBIOS, IPX/SPX, Named Pipes, and TCP/IP connectivity.

For SNA (APPC) connectivity, one of the following communication products is required:

  • IBM Communications Server for Windows NT Version 5.01 or later

  • IBM Personal Communications for Windows NT Version 4.1 or later

  • Microsoft SNA Server Version 4 Service Pack 2 or later

Notes:

  1. If SNA two-phase commit is necessary, then IBM Communications Server for Windows NT Version 5.01 or later is required.

  2. If you plan to use DCE (Distributed Computing Environment) with Version 6 of DB2 Universal Database, you will need:

    • A DCE product that is at OSF DCE level 1.1 with IBM DCE for Windows NT Version 2.0.

    • To ensure that if you are connecting to DB2 for OS/390 V5.1 database that it is enabled for DCE support using OS/390 DCE Base Services Version 3.

    In addition, DB2 also supports Gradient PC-DCE for Windows 32-bit operating systems Version 2.0 Runtime Media Kit. For DB2 Connect support, you require DB2/MVS Version 5.1 plus its prerequisite, OS/390 DCE Base Services version 3 for DCE support.
    Note:With DB2 Connect, you must install DCE Directory Services on the client and the DRDA server. You do not need DCE installed on a DB2 Connect Enterprise Edition server.

  3. If you plan to use LDAP (Lightweight Directory Access Protocol), you require the IBM eNetwork LDAP Directory Client Version 3.1. For more information, refer to the Administration Guide.

  4. If you plan to use the ADSTAR Distributed Storage Manager (ADSM) facilities for backup and restore of your databases, you require the ADSM Client Version 3 or later.

  5. If you have the IBM Antivirus program installed on your operating system, it must be Version 3.0 or later.

  6. If you plan to use the Simple Network Management Protocol (SNMP) subagent, you require DPI 2.0 provided by IBM Netfinity Agent.

Client Product Requirements

Table 5 lists the software requirements needed for a DB2 Administration Client, DB2 Run-Time Client, or a DB2 Software Developer's Kit.

Table 5. Software Requirements for Clients
Component Hardware/Software Requirements Communications

  • DB2 Run-Time Client for OS/2

  • DB2 Administration Client for OS/2

  • DB2 Software Developer's Kit for OS/2

  • OS/2 Warp Version 3 and Version 4

  • OS/2 Warp Connect Version 3

  • OS/2 Warp Server Version 4

  • OS/2 Warp Server Advanced V4

  • OS/2 Warp Server Advanced V4 with SMP Feature

  • OS/2 Warp Server for e-business

APPC, IPX/SPX, NetBIOS, or TCP/IP

  • For APPC connectivity, you require IBM eNetwork Communications Server for OS/2 Warp Version 5 or IBM eNetwork Personal Communications for OS/2 Warp Version 4.2.

  • For IPX/SPX connectivity, you require the Novell NetWare client for OS/2 Version 2.10 or later. IPX/SPX can only be used to connect to local databases. It cannot be used to connect to host or AS/400 databases.

  • For NetBIOS connectivity, you require IBM NTS/2 Version 1.0, IBM eNetwork Communications Server for OS/2 Warp Version 5, IBM eNetwork Personal Communications for OS/2 Warp Version 4.2, or IBM OS/2 LAN Requester. NetBIOS can only be used to connect to local databases. It cannot be used to connect to host or AS/400 databases.

  • For TCP/IP connectivity, you require IBM TCP/IP Version 2.0 or later.

  • The OS/2 base operating system provides Named Pipes (Local) connectivity. Named Pipes is supported in DOS and WIN-OS/2 sessions.

Notes:

  1. Net.Data requires OS/2 Warp Version 3 or later and a Web server such as IBM's Internet Connection Server.

  2. For DCE Cell Directory Services Support (CDS) for DB2 Clients for OS/2, you must install IBM Distributed Computing Environment Cell Directory Service client, Version 2.10, on each client workstation.

  3. If you are planning to use ADSM, PTF 3 for ADSTAR Distributed Storage Manager (ADSM) Version 3 is required for an OS/2 client.

  • DB2 Run-Time Client for Windows 9x

  • DB2 Administration Client for Windows 9x

  • DB2 Software Developer's Kit for Windows 9x

  • Windows 95 4.00.950 or later

  • Windows 98

IPX/SPX, Named Pipes, NetBIOS, or TCP/IP

  • The Windows 9x base operating system provides NetBIOS, IPX/SPX, TCP/IP, and Named Pipes connectivity.
    Note:IPX/SPX connectivity is only supported to Windows NT servers.

  • If you plan to use LDAP (Lightweight Directory Access Protocol), you require the IBM eNetwork LDAP Directory Client Version 3.1. For more information, refer to the Administration Guide.

  • DB2 Run-Time Client for Windows NT

  • DB2 Administration Client for Windows NT

  • DB2 Software Developer's Kit for Windows NT

  • Windows NT Version 4.0 with Service Pack 3 or later

  • Windows Terminal Server (can only run the DB2 Run-Time Client)

APPC, IPX/SPX, Named Pipes, NetBIOS, or TCP/IP

  • 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:

    • IBM eNetwork Communications Server for Windows NT V5.01 or later.

    • IBM eNetwork Personal Communications for Windows NT V4.2 or later.

    • Microsoft SNA Server Version 4 Service Pack 2 or later

    • Wall Data Rumba
    If you plan to use DCE (Distributed Computing Environment) with Version 6 of DB2 Universal Database, you will need to ensure that if you are connecting to DB2 for OS/390 V5.1 database that it is enabled for DCE support using OS/390 DCE Base Services Version 3.

  • If you plan to use LDAP (Lightweight Directory Access Protocol), you require the IBM eNetwork LDAP Directory Client Version 3.1. For more information, refer to the Administration Guide.

  • If you plan to use the ADSTAR Distributed Storage Manager (ADSM) facilities for backup and restore of your databases, you require the ADSM Client Version 3 or later.

  • If you have the IBM Antivirus program installed on your operating system, it must be Version 3.0 or later.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]