If you want to access databases on host systems such as OS/390, MVS, OS/400, VM, or VSE, use the configuration shown in Figure 8. You will need to install DB2 Connect Enterprise Edition.
Connect clients to DB2 Connect Enterprise Edition for OS/2 or Windows NT using one of the supported protocols: APPC, IPX/SPX, Named Pipes (Windows NT only), NetBIOS, or TCP/IP. Connect clients to DB2 Connect Enterprise Edition for AIX, HP-UX, or Solaris using one of the supported protocols: APPC, IPX/SPX, or TCP/IP. DB2 Connect then connects to the appropriate host database management system using DRDA and either APPC or TCP/IP. (TCP/IP is supported on DB2 for OS/390 Version 5.1 or later.)
Figure 8. Configuration for Accessing Host Data
|
The amount of memory you need on your system depends on the number of concurrent clients you intend to connect. For the OS/2 or Windows NT DB2 Connect server, it is recommended that a minimum of 32 MB of memory be installed to accommodate five concurrent clients. We suggest that you have a minimum of 48 MB of memory to accommodate 25 concurrent clients and 64 MB of memory for 50 concurrent clients.
For the UNIX DB2 Connect server, it is recommended that a minimum of 64 MB of memory be installed to accommodate five concurrent clients. The diagram shows a scenario with five concurrent clients connected to a UNIX DB2 Connect server. We suggest that you have a minimum of 96 MB of memory to accommodate 25 concurrent clients and 128 MB of memory for 50 concurrent clients. Use these guidelines to determine the amount of memory necessary in your environment.
An administration client is shown in the diagram. This client can be on an OS/2, Windows 95, or Windows NT workstation and can be used to remotely manage the DB2 servers on your network. A minimum of 24 MB of memory is required to run all the graphical tools you will need for an administration client.
For the DB2 clients in your environment, the amount of memory required depends on the database applications you are running.