Communications Server

Network Administration Guide


Chapter 5. Planning for Legacy Data Access

This chapter contains information about functions within Communications Server that enable you to access host information.


AS/400 OLE DB Provider

Applications that use OLE DB or ActiveX can communicate through Communications Server for record-level access to files on AS/400s. Access to AS/400 files requires you to define the remote AS/400, where the files are stored, as a partner LU.

The AS/400 OLE DB Provider can be installed as a component of Communications Server, or as a component of the SNA API client for Windows 95 or Windows 98. It can also be installed as a component of the SNA API client for Windows NT or Windows 2000; however, it requires Windows NT Workstation or Server 4.0 or later or Windows 2000. If you do not have the Microsoft Data Access Components (MDAC) Version 2.0 installed, Communications Server will install it for you when you install this component.

If you install the AS/400 OLE DB Provider on a machine that already has Client Access Version 3 Release 2 M0 (or earlier) installed, some Client Access function will be disabled, including support for ActiveX and OLE DB programs that use Client Access for access to AS/400 data queues, remote commands, distributed program calls, stored procedures, and SQL statements.

If you want to continue using these functions through Client Access Version 3 Release 2 M0 (or earlier), do not install the AS/400 OLE DB Provider component during the installation of Communications Server. If you install the AS/400 OLE DB Provider component during the installation of Communications Server, and you want to recover the Client Access functions, you can re-install Client Access. However, if you re-install Client Access, you can not use AS/400 OLE DB Provider over Communications Server.

When Client Access Version 3 Release 2 M0 (or earlier) is installed after Communications Server, registry information is overwritten. If you want to use AS/400 OLE DB Provider over Communications Server after Client Access is installed, you can run the REGSVR32.EXE tool against the cwbzzodb.dll and cwbzzidx.dll files to restore the AS/400 OLE DB Provider registry information.

You can use the AS/400 OLE DB Provider to connect Windows 95, Windows 98, Windows NT 4.0, and Windows 2000 clients through Communications Server to one or more AS/400s, as shown in Figure 27. This configuration gives clients that have the AS/400 OLE DB Provider installed access to specific records within files on the AS/400.

Figure 27. AS/400 OLE DB Provider


AS/400 OLE DB Provider

In this figure, all clients have the AS/400 OLE DB Provider installed. Alternatively, you can install and use the function from the server.

Documentation for this function, as well as information about developing OLE DB and ActiveX applications using Client Access, is provided in the ibmcs\sdk\pubs\oledb directory.


AS/400 Shared Folder Server

You can create disk devices on the server that communicate with AS/400 folders through the AS/400 Integrated File System (IFS). If the server shares these disk devices, clients can connect to and use these devices to get access to AS/400 drives without additional configuration or code installation on the client machine. Multiple clients can connect to folders on the AS/400 system as if they were drives on their workstations.

You enable shared folder support through the SNA Node Configuration application. When a disk device is available to the user, it acts as a system supported disk drive. Use the interfaces provided by Windows NT to control the device. Users can share the drive across the network, but maintain individual access rights.

The AS/400 shared folder server requires OS/400 Version 3.1 or higher.


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