Kbase 16010: Setting up DEC Pathworks (Win95) V1.0A for use with Progress
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Setting up DEC Pathworks (Win95) V1.0A for use with Progress
INTRODUCTION:
This Knowledgebase entry describes how to configure DEC Pathworks for
Win95 for use with Progress Windows clients
OPERATING SYSTEM REQUIREMENTS:
The VMS side: OpenVMS Alpha V6.x, V7.0
Progress V7.3Cxx or V6.2Nxx
The PC side: Windows '95
PATHWORKS for Windows '95 V1.0A (NOT V1.0)
Required patches and additions:
DECDNP.VXD V1.0.34 (patch obtained from Digital CSC)
PATHWORKS for Windows '95 1.0A unsupported utilities
(obtained from their Internet site (digital.com)).
PROGRESS V7.3C01 and higher and V8.0A and higher
Windows clients.
SETUP INSTRUCTIONS:
1. Obtain the replacement DECDNP.VXD, V1.0.34 or later, from
Digital's Customer Support Center.
2. Obtain the PATHWORKS for Windows '95 Unsupported Utilities from:
ftp://ftp.digital.com/pub/DEC/PCI/pww9510A.txt (description &
instructions)
ftp://ftp.digital.com/pub/DEC/PCI/pww9510A.zip (actual kit)
NOTE: Case is significant here. There's another set of files
in this directory, named pww9510a.txt and pww9510a.exe,
which are NOT the same. They're an updater kit to bring
a Pathworks for Windows '95 V1.0 installation to V1.0A.
Be sure to pull the correct files. This kit includes the
"NetBIOS LANA UTILITY" which is used to determine which
LANA Pathworks is running on. In order for Progress to work
properly, Pathworks must be running on LANA 0. If it is
not, Progress client will display a Progress error 1432
(could not connect to server for database) or error 733
(server servername unavailable) when attempting to connect
to the database.
3. Install PATHWORKS for Windows '95 V1.0A on the Win 95 PC.
4. Place the replacement DECDNP.VXD file in C:\WINDOWS\SYSTEM.
You MUST HAVE this replacement version or newer; the shipping
versions in Pathorks V. 1.0A WILL NOT WORK.
5. Install the PATHWORKS for Windows '95 1.0A Unsupported Utilities
kit.
6. Restart Windows 95.
7. Make DECnet the default protocol (this SHOULD ensure that it is
running on LANA # 0):
a. Go to Control Panels->Network.
b. Scroll through the list of protocols until "PATHWORKS
DECnet" is visible. Double-click on it.
c. In the resulting dialog box, select the "Advanced" tab.
d. Check the box labelled "Set this protocol to be the
default protocol".
8. Click on OK to close the DECnet protocol box. Click on OK to
close the Network control panel.
9. Open an MS-DOS window. Run NCP.
10. At the NCP prompt, make sure that the proper set of DECnet
remote adapter names are defined for the server(s) that the
PC will be connecting to. For example, if you were going to
connect to the SPORTS database on a VAX or Alpha VMS system
named MYHOST, offered with a service name of SPORTSERV, and
your PC is the first one being configured, you would make the
following entries:
NCP> DEFINE REMOTE-ADAPTER-NAME SPORTSERV NODE MYHOST
NCP> DEFINE REMOTE-ADAPTER-NAME SPORTSERV1 NODE MYHOST
NOTE: An entry for MYHOST must already exist in the NCP database.
If it is missing, the commands will fail, and you will
first have to define the node name using the NCP command
"DEFINE NODE x.yyy NAME MYHOST MS-NET" first.
11. In Windows 95, go to Control Panels and run the NetBIOS LANA
Utility.
It should show that the PATHWORKS DECnet network is attached to
LANA 0. NetBEUI, TCP/IP, and others should be attached to various
non-zero LANAs. If it does, go to step 12.
If it doesn't, it means that some other networking protocol
on the PC is usurping the default protocol slot and is
ignoring the settings of your check-boxes. This can be caused
by another protocol that was loaded before all the
Ethernet-based protocols which grabbed LANA #0.
The solution is to remove other protocol and then re-add them.
[You should not need the original distribution disk(s) as
the removal process does not physically delete the protocol's
files.]
If you need to remove these protocols, follow these steps:
a. Select the offending protocol(s) in the Network
control panel, and click Remove. After confirming
the change, close the control panel and restart.
b. Re-run the NetBIOS LANA Utility. PATHWORKS DECnet
should now be the preferred protocol. If not,
follow Step 5 above to ensure that DECnet is the
preferred protocol. Restart the computer and
re-run the NetBIOS LANA utility to verify.
c. Once DECnet is the preferred protocol, you can use
the Add button in the Network control panel to add
back the protocol that you removed in the steps
above. After restarting, check the NetBIOS LANA
Utility again. DECnet should still be the default,
and the newly-added protocol should be towards the
bottom of the list.
12. Make sure that your VAX or Alpha OpenVMS PROGRESS server is up
and running. Make sure that the DECnet node name of the PC is
defined in the server's NCP database.
Start the SPORTS database with the SPORTSERV service name using
the following command:
PROGRESS/MULTI=START/SERVICE=SPORTSERV/NETWORK=DECNET SPORTS
13.Start the PROGRESS Client. From the Procedure Editor window,
try to connect to the server. Using the hypothetical server
and service info from above, the CONNECT statement would be:
CONNECT SPORTS -N NETBIOS -S SPORTSERV -H MYHOST -Nn 1.
Press F2 to compile and execute this statement. If all is well,
a connection should take place within 10-15 seconds.
The "-Nn 1" switch directs Progress to request that the server
connect back to the client using the service name SPORTSERV1.
This name should already be defined in NCP using
DEFINE REMOTE-ADAPTER-NAME commands
RELATED DOCUMENATION:
KB ID 12103
KB ID 15586
KB ID 420
KB ID 15913
Progess Networks Guide
Progress Administrator Reference
Progress Software Technical Support Note # 16010