Kbase 16936: How to configure IBM Client Access on Win95 for SNA and AS/400
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/9/2003 |
|
Status: Unverified
GOAL:
How to configure IBM Client Access for SNA and AS/400.
FACT(s) (Environment):
Windows 95
Progress/400 DataServer
SYMPTOM(s):
Failed to connect to AS/400 database . (2467)
FIX:
If you use IBM's Client Access for Windows 95 for SNA connectivity to an AS/400 database, there are a few things you need to do to implement this correctly with Progress/400 DataServer. This product is a 32-bit application that, by default, will not run with our Progress/400 DataServer since Progress is a 16-bit application (pre 8.2A). However, Client Access has an option that can be turned on to enable a 16-bit application. This needs to be done before Client Access can connect to Progress/400 via SNA. In V8.2A, we provide the 32 bit client so this problem should go away. Please be aware there are other SNA connectivity tools that can be used that are easier to use and already have this 32 to 16 bit thunking built in (Netsoft and Rumba), but IBM's Client Access seems to be more widely used.
The latest version of IBM's Client Access for Windows 95 for the AS/400 is V3R1M2. A customer may be on a different operating level of the AS/400, but the latest Client Access software is V3R1M2. M2 is the important key to this. Most customers will be on a modification of M0 ex/V3R1M0
Within the Client Access software, there is an SNA router called
Netsoft which needs to be configured to allow the connection to the
AS/400. Netsoft built a new router for Client Access which is included in V3R1M2, but there is a known thunking problem (32 to 16 bit) in this software. Therefore, you will need to get a DLL from IBM that will fix this problem. It's called CWBAP32.DLL.
In summary, here are the requirements that you need in order to
successfully use Client Access for Windows 95 as the SNA connection
to the Progress/400 DataServer.
1) Install the Microsoft 32-bit DLC protocol on your PC:
You must have the Windows 95 Service Pack 1 or later
(see nbfserver2\software\win95 service pack). Go to the
Control Panel, Network, Add, Protocol, Add, Have Disk.
You can install this from the service pack. The name of
the protocol is MSDLC32. For more information, see page
15-1 in the book titled Client Access for Windows 95 Setup
(SC41-3512-00).
2) Order the Following Updates from IBM:
Client Access for Windows 95 V3R1M2
Client Access Service Pack - PTF Order Number is SF40828
CWBAP32.DLL - fixes the thunking problem
3) Configure 32 to 16 bit Thunking:
Follow the steps from the on-line Client Access Users Guide
(on-line help) "Enabling 16-Bit Applications for Client Access".
You will find the Client Access User Guide help icon in the
Client Access folder. Use the Find tab in the Help Topic:
Client Access and look for "16".
4) Configure the NS/Router:
See Page 76, 5.2 Netsoft NS/Router in IBM's Red Book titled
Inside AS/400 Client Access for Windows 95 (SG24-4748-00).
5) Configure the AS/400 Connection:
See Page 67, 5.1 Configuring a Connection in IBM's Red Book
titled Inside AS/400 Client Access for Windows 95 (SG24-4748-00).
TROUBLESHOOTING TIPS:
1) If you install Client Access for Windows 95 on your PC in the
default directory of the install, you will need to put the
following path name in your autoexec.bat (even though you are
using Windows 95).
C:\Progra~1\IBM\Client~1\Shared;C:\CAWIN
2) To verify you enabled the 16-bit application support within
Client Access, you can open up the properties of your Client
Access icon.
3) Look at your database log file for further information. If you
see an error "Unable to initialize AS4EHN.DLL = 0x06A", please
refer to kbase 16529 for more tips.